[Bug] No importers found for file (swagger 2.0)

Insomnia Version: 6.3.2
Operating System: windows 10_x64

Details
I'm trying to import my swagger.json into Insomnia, but got an error: No importers found for file. Swagger version is 2.0. What i'm doing wrong?

Can you post an example swagger.json that reproduces the problem?

Same here on the latest version

We're facing the same issue. We have been supplied three swagger.json files and only one of them can get imported.

any progress? 🙄

I have tried to import the following Swagger 2.0 spec without success: "No importes found for file"
https://raw.githubusercontent.com/Azure/azure-rest-api-specs/master/specification/containerservice/resource-manager/Microsoft.ContainerService/stable/2019-02-01/managedClusters.json

A lot of people experiencing with bug. Will you provide further info?

Just took a look at this and it seems like $ref attributes are causing the issues.
@alxpsr's example file returns the following error:
Error resolving $ref pointer "/Users/gschier/Workspace/insomnia/desktop/packages/insomnia-app/#/definitions/Dto.Document.DocumetnDto".
Token "definitions" does not exist.

@dominik-lekse's example returns the following error:
Error opening file "/Users/gschier/Workspace/insomnia/desktop/packages/insomnia-app/examples/ManagedClustersList.json"
ENOENT: no such file or directory, open '/Users/gschier/Workspace/insomnia/desktop/packages/insomnia-app/examples/ManagedClustersList.json'

It looks like $refs are only for linking to documentation reference so there errors probably should be ignored. I just refactored the import module to try continuing if the Swagger validation fails. This should fix the problem I think.

Also, thank you @alxpsr for the test case file. I've included it in the test suite fixtures

I figured out that there is the same bug in OpenAPI importer (openapi3.js). Here is the output of my console:
openapi3.js?9a64:87 SyntaxError: Error resolving $ref pointer "/(...)/insomnia/packages/insomnia-app/#/components/schemas/api-version".

I guess we could apply the same fix ?

Here is my patch: #1515


Fix linux build errors

Notes:

Removed radio.png and chat.png references from project since it doesn't appear to be used anymore (See issue 138 and commit efa30d9)
Commented out CWallet::Lock() prototype from wallet.h since there is no implementation and the parent class already has an implementation (unless there are plans to override this method...)
Some small file checking and directory creation check in go.sh to prevent some errors that may be misleading.

Looks like I accidentally fixed the Windows build too..! Happy days.

I think removing those png breaks the build:
make[1]: *** No rule to make target qt/res/icons/chat.png', needed by qt/qrc_bitcoin.cpp'.  Stop.

@JBetser  I was able to build it locally on my ubuntu 16 VM before pushing to remote. Also, the travis build was successful as you can see in this thread.
Based on the commit link in my description I assumed that these two png are not to be used again and can therefore be removed.
If it's failing when you build it then please post your execution logs here.

Thats correct, I just ran the build with master and ran into:
  CXX      qt/qt_libbitcoinqt_a-moc_qrcodedialog.o
  GEN      qt/moc_walletmodel.cpp
  CXX      qt/qt_libbitcoinqt_a-moc_walletmodel.o
make[1]: *** No rule to make target 'qt/res/icons/chat.png', needed by 'qt/qrc_bitcoin.cpp'.  Stop.
make[1]: Leaving directory '/opt/crypto/verge/vergecurrency/VERGE/src'
Makefile:524: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

So I tested the branch with fixes and all builds fine:
make[2]: Leaving directory '/opt/crypto/verge/vergecurrency/VERGE/src/leveldb'
  CXXLD    VERGEd
  CXX      qt/qt_VERGE_qt-bitcoin.o
  OBJCXXLD qt/VERGE-qt
make[1]: Leaving directory '/opt/crypto/verge/vergecurrency/VERGE/src'
make[1]: Entering directory '/opt/crypto/verge/vergecurrency/VERGE'
make[1]: Nothing to be done for 'all-am'.
make[1]: Leaving directory '/opt/crypto/verge/vergecurrency/VERGE'

@thomasmodeneis , i also confirm

ok I originally was compiling without your change, thinking I had the latest, looks good

I'll approve this merge when I get home in the morning. cheers!


Created accessor for desiredCapabilities

Closes #202

Please also add tests to cover changed code.

I'm new to this process, so I'm not sure why that failed.  If there's something I need to address please let me know, I'd be happy to help!

Please let me know if you have any insight as to why scrutinizer failed.  I'm actually working on a Mac, and all the tests pass fine.  I did correct the filename/classname issue.

Looks good. Merging, thanks @cmacnaughton-al .


Version 0.3.8

Hold on a second, I just noticed a mistake in one of my PRs that was merged today..

Opened #34, just noticed that this got lost when rebasing. Sorry!

Not sure if we need to wait for confirmation from someone else?

We should be good to go, thanks


chore: fixed image not downloading functionality and ImageWidget cypr…

Description
In this PR I have modified 3 file chages.

I have created helper.tsx file *app/client/src/widgets/ImageWidget/helper.ts in which I have defined one method urlToBase64 which will convert imageurl into base64Url.

app/client/src/widgets/ImageWidget/component/index.tsx: In this I have  made one new state called downloadUrl which will takes the value from urlToBase64 method and later define the href value.

app/client/cypress/e2e/Regression/ClientSide/Widgets/Image/Image3_Spec.ts: I have modified the downloadImage test case according to this implementation.

summary:
As we are fetching image url for base64 conversion. Therefore, this  solution only works for images that are hosted on server which allows cross origin request and for images that are hosted on server which doesn't allow cross origin request (getting cors error) the functionality will works as it was working previously.
suggestion for Restiricted Images:
for images hosted on server which does not allow cross origin request, the backend should create base64 url and return to frontend.
Fixes #24632

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[x] No

Summary by CodeRabbit

New Features

Added base64 conversion for image downloads in the ImageComponent.
Introduced download functionality for images in the ImageComponent.

Tests

Introduced a comprehensive test suite for the ImageComponent, covering image rendering, download button interactions, and edge cases for image URLs.

Hi @rajatagrawal , I have added RTL unit test cases for Image Widget , could you please review this PR.

Hi @rajatagrawal @ApekshaBhosale @sagar-qa007 , please review this PR else it will be auto closed in some days.

@rahulbarwal Can you please help review the PR ?

@rajatagrawal @rahulbarwal please look into this PR.


the run.sh file inputs/outputs got a lil confused

This PR addresses issue https://github.com/covid-projections/covid-data-model/issues/235
Please Check

[ ] Will the current schema in api docs be updated with this PR?
[X] Are tests passing?

running https://github.com/covid-projections/covid-data-model/actions/runs/79171934


Improve the editor gizmos

PR Details
small enhancements to the gizmos
Description
The old gizmos weren't very nice to look at so this pr makes them look better and more user-friendly, it also changes how the rotation gizmo works (see discussion in discord ui-ux) and adds scale planes to the scale gizmo.
This pr also changes the text on the CameraOrientationGizmo to be XYZ instead of right/left... but there's a setting under the viewport settings that swaps it back to the old text

Motivation and Context
makes the gizmos look better and makes it easier to use the rotation gizmo
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

 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.:x: salahchafai sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Nice, thanks for the contribution !


[cherry-pick] upgrade mybatis-plus to 3.4.3

cherry-pick issue: https://github.com/apache/dolphinscheduler/issues/8513
pr: https://github.com/apache/dolphinscheduler/pull/8515

Codecov Report

:exclamation: No coverage uploaded for pull request base (2.0.4-release@d91d403). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             2.0.4-release    #8539   +/-   ##
================================================
  Coverage                 ?   21.06%
  Complexity               ?     1590
================================================
  Files                    ?      536
  Lines                    ?    22506
  Branches                 ?     2666
================================================
  Hits                     ?     4741
  Misses                   ?    17279
  Partials                 ?      486

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 d91d403...5438528. Read the comment docs.


Typescript types no longer generated in 1.2.4

Starting version 1.2.4, the Typescript types get no longer generated.
Working okay in 1.2.2
To reproduce:

Install 1.2.4

Visit the dist folder: TS types are not generated

Install 1.2.2

Visit the dist folder: TS types are generated

Also came accross this issue. Types are no longer part of the package:

I was about to lose my mind when I came across this issue. Please fix this people.

Same here

completely broke my app

Workaround: Fix the package version to 1.2.2 in your package.json

@mauryaratan pinging in case you haven't seen this yet - it's likely just a matter of rebuilding locally and publishing a new version.

this needs to be fixed


Bump version: 0.2.0 → 0.3.0

Closes #24

Why isn't this triggering a build?

Integration not set up I guess. Here is the link to the CI build: https://travis-ci.org/jmrivas86/django-json-widget/builds/567069160

@jmrivas86 Can you take a look and see if this is good to merge?

This seems inactive, should anyone fork it and release it PyPI with the latest changes? @dgrant @jmrivas86

@imaka @dgrant  The project is not inactive, I have been a father a few months ago and the dedication time is less but I am working on getting a new version with all the issues fixed and some more updates


RIIR

Have you considered rewriting it in rust ? That language could make nocode faster and more reliable.
Migration should be pretty fast too as it would take no time to do it.

RUST do not support nocode. Sorry


Typo "@provstr"→"@provstr"

bold with escape characters
https://github.com/MicrosoftDocs/sql-docs/blob/live/docs/relational-databases/native-client/features/service-principal-name-spn-support-in-client-connections.md

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Verified the update.
@hyoshioka0128 Thanks for submitting the fix.


Nested Layer saving with tf.train.Checkpoint

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.13.1
Python version: 3.5.6

Describe the current behavior
tf.train.CheckPoint fails to save variables associated with the child layer, but displays the variables associated with it.
Describe the expected behavior
tf.train.CheckPoint should save variables associated with the child layer
I was trying to compare model saving between nested and non-nested tf.keras layers, since I need a nested layer for my task.
I put together a simple script and its corresponding output.
In the first case, the Linear Layer is its own parent and in the second case, the Linear layer is made the child of an NestedLinear layer. A tf.keras.Model is setup with the inputs and outputs and the trainable variables are printed out. After initializing, I attempt to save a checkpoint and list the variables in the checkpoint.
If you see the output, the number of trainable variables are the same in both cases and the child layer variables are joined to the parent layer.
I assumed that the Checkpoint saving would work in a similar fashion with gathering all variable tensors and having a mapping between the Tensor and its position in the graph topology and save them but the checkpoints fail to save the Linear layer variables in the second case.
Maybe there is something I missed, and would like some help on this.
Code
import tensorflow as tf
import numpy as np
from tensorflow.keras import layers
import os
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '2'

class Linear(layers.Layer):

  def __init__(self, units=32, input_dim=32):
    super(Linear, self).__init__()
    self.w = self.add_weight(shape=(input_dim, units),
                             initializer='random_normal',
                             trainable=True, name="W")
    self.b = self.add_weight(shape=(units,),
                             initializer='zeros',
                             trainable=True, name='b')

  def call(self, inputs):
    return tf.matmul(inputs, self.w) + self.b

class NestedLinear(layers.Layer):

  def __init__(self):
    super(NestedLinear, self).__init__()
    self.linear_1 = Linear(32)

  def call(self, inputs):
    x = self.linear_1(inputs)
    return x

inputs = layers.Input(shape=(32,))

print("SAVING SINGLE LAYER")
outputs = Linear(32)(inputs)

model = tf.keras.Model(inputs=inputs, outputs=outputs)
for var in model.trainable_variables:
    print(var)
ckpt = tf.train.Checkpoint(model=model)

sess = tf.Session()
sess.run(tf.global_variables_initializer())
with sess.as_default():
    ckpt.save("ckpt")

for var in tf.train.list_variables("./"):
    print(var)

print("--------------------------------------")

nl_layer = NestedLinear()
outputs = nl_layer(inputs)

print("SAVING NESTED LAYER")

model = tf.keras.Model(inputs=inputs, outputs=outputs)
for var in model.trainable_variables:
    print(var)
ckpt = tf.train.Checkpoint(model=model)

sess = tf.Session()
sess.run(tf.global_variables_initializer())
with sess.as_default():
    ckpt.save("ckpt")

for var in tf.train.list_variables("./"):
    print(var)

Output
SAVING SINGLE LAYER
<tf.Variable 'W:0' shape=(32, 32) dtype=float32>
<tf.Variable 'b:0' shape=(32,) dtype=float32>
('_CHECKPOINTABLE_OBJECT_GRAPH', [])
('model/.ATTRIBUTES/OBJECT_CONFIG_JSON', [])
('model/layer-0/.ATTRIBUTES/OBJECT_CONFIG_JSON', [])
('model/layer_with_weights-0/.ATTRIBUTES/OBJECT_CONFIG_JSON', [])
('model/layer_with_weights-0/W/.ATTRIBUTES/VARIABLE_VALUE', [32, 32])
('model/layer_with_weights-0/b/.ATTRIBUTES/VARIABLE_VALUE', [32])
('save_counter/.ATTRIBUTES/VARIABLE_VALUE', [])
--------------------------------------
SAVING NESTED LAYER
<tf.Variable 'W_1:0' shape=(32, 32) dtype=float32>
<tf.Variable 'b_1:0' shape=(32,) dtype=float32>
('_CHECKPOINTABLE_OBJECT_GRAPH', [])
('model/.ATTRIBUTES/OBJECT_CONFIG_JSON', [])
('model/layer-0/.ATTRIBUTES/OBJECT_CONFIG_JSON', [])
('model/layer_with_weights-0/.ATTRIBUTES/OBJECT_CONFIG_JSON', [])
('save_counter/.ATTRIBUTES/VARIABLE_VALUE', [])

Can you try with a more recent version of TensorFlow? 1.14 should have this fixed I believe. sub-Layer tracking was not automatic like Model's in 1.13.

That worked, yes, thanks!


Generated rinpop adapter does not compile when there is service extension

service Foo {
   string ping()
}

service Bar extends Foo {
}

The generated code fails with this error:
cannot use adapter (type *RingpopBarAdapter) as type TChanBar in return argument:
	*RingpopBarAdapter does not implement TChanBar (missing Ping method)

Examples of how tchannel-go thrift gen template handles it  https://github.com/uber/tchannel-go/blob/dev/thrift/thrift-gen/tchannel-template.go#L55
https://github.com/uber/tchannel-go/blob/dev/thrift/thrift-gen/tchannel-template.go#L45

I am also seeing the same problem. Can we prioritize this?


OMIM ingest - 240212

ROBOT template: https://docs.google.com/spreadsheets/d/1Jph0vcyJ1Fcg97v4Xlc-8MDldDoUk38CCeA6gmFYwg0/edit#gid=0

@sabrinatoro who is in charge to merge this? And does it still need to wait for the question about the missing parents?


Consider a 'catch-all' server block

Another suggestion from @peterbourgon is to have a way to specify directives that apply to all server blocks declared in a Caddyfile. For lots of servers, using import isn't always practical.
The syntax of the Caddyfile forbids directives from appearing outside a server block, but we may be able to do define a special sever name that means its contents will be applied to all other servers. For example:
all {  # or maybe 'default' or '*'
    # directives here
}

I can see the value in this, however, I want to give this a lot of careful thought before going forward, if we do this. I don't want to choose a solution that paints us into a corner for possible future changes.
We would need to ensure that the behavior of all directives is consistent in how they handle repeated uses. Some may favor the first, others the last, and yet others may use all of them, depending on what they do.

There needs to be a way to negate directives if we need a setting for all but one server.
But I'd love such a feature to be able to specify my email address (tls <email>) for all servers in one place in the Caddyfile instead of giving it as a parameter during startup.

Maybe a 'default' instead of a catch-all?
Could be a helpful feature.

FWIW, I'm not so hot about the idea of having to negate directives... in other words, allowing overlapping server blocks doesn't appeal to me. If they do overlap, only the most specific match should be used, not a mixture of them.
Thanks for the feedback so far! Closing this issue to funnel the discussion into #619.


Feature/82 versioned object poc

Original task was to research VERSIONED_OBJECT capabilities with our code base. This PR went from research to actual implementation of four REST endpoints, from access layer to presentation layer.
Endpoints: see the four VERSIONED_EHR_STATUS ones here https://specifications.openehr.org/releases/ITS-REST/latest/ehr.html#ehr_status-versioned_ehr_status
OriginalVersion*, RevisionHistory* and VersionedObjectResponseData to map the service output to the specified format.
Controller for the endpoints: OpenehrVersionedEhrStatusController
EhrServiceImp got new methods to generate new necessary data and invoke access layer methods.

Specifically important is generation of the OriginalVersion<> wrapper, VersionedEhrStatus and RevisionHistory to comply with the endpoints (especially the Attestations included in RevisionHistoryItem needed many new changes).

Access layer:

EhrAccess

Has new associated StatusAcess, instead of embedded StatusRecord so all status methods can be maintained in one place (still needs refactoring).
Some new methods, like one to determine the time of the oldest Status version

StatusAccess

Basically whole implementation of CRUD like methods.
Includes internal handling of associated audit and contribution if appropriate.

AttestationAccess

Has associated AuditDetailsAccess to model Attestation being a subclass of AuditDetails
Only reading/retrieval functionality for now
Retrieval of all attestations related to the given attestation_ref (see below)

And some small changes to other Access classes

DB schema changes:

"obfuscation" table attestation_ref to allow pointing from version objects of any kind to attestations without breaking the internal postgres type checking
new attestation_ref field for all objects that can be/have ORIGINAL_VERSION and there can have associated attestations.
Removal of versioning (via temporal tables) of audit_details to improve maintainability

closes ehrbase/project_management#82

I have a some questions/comments:

What is the relationship between version_uid f.e. preceding_version_uid and history table? In other words, whenever a composition is amended, how does this materialize at DB level?
I've noticed the state of the contribution is not saved, does this mean that whenever we want to query the history of changes for a composition (e.g. creation, amend, etc.) we are getting a list of items without state?
I think some UML (Use Case and Sequence Diagram) could help a lot to understand this implementation.

NB. My concern is to understand the impact of the above to implement AQL querying on RM object history (f.e. TIME WINDOW)

@chevalleyc

I haven't introduced those columns nor worked on composition in this PR.
So in a general scope: Amendment is handled about the same as modifications for now. A new version will be created, i.e. the current entry from, for instance, the composition table will be moved to the composition_history table, while the new one will be written into composition, with the same ID. But since you know that, I'm not sure what your question is.
The preceding_version_uid depends on the use case. In a REST request with the If-Match header it semantically equals the current version. While in other cases it means "second latest", which can be queried by looking into the *_history table.
Where? That wouldn't be intentional. In my tests there were some cases where the state wasn't saved (older tech dept), but in general it was.
Great idea! Do you think about this PR's scope or the whole access layer?

Many thanks for the explanation Jakes!


API Docs Enhancement: Public and Private URLs

Business Need
Each time VA Notify onboards a client we have to manually explain the public and private URLs and guide them to use the appropriate one. Currently, our API docs only list the private URLs, though it does not explicitly state that they are private.
The private URL will only work if the triggering application is within the VA Network. We want clients to know the public URL exists, but the preference is that they should be using private unless their application is outside the VA Network.

see suggestion from QA in the comments below in the event I am OOO

[x] Discussed with QA

User Story(ies)
As a VA business line integrating with VA Notify
I want to know which API URL is appropriate to use
So that I can successfully send notifications from my application
Additional Info and Resources

Public URLs below. Please note we only want clients using these when their application is outside the VA network. We should make the requirements clear to avoid extra traffic routing through public unnecessarily.

https://dev-api.va.gov/vanotify
https://staging-api.va.gov/vanotify
https://api.va.gov/vanotify

Current API Docs:

Engineering Checklist
Required

[x] Update API documents to include both private and public URLs as well as an explanation of when to use each

[x] Add perf as an available environment in the computed URL section for both private and public URL
[x] Get Kyle & Melanie's approval on content

[x] Ping Strike team when this change is complete/merged so they can run the script that pulls in the api docs to portal at their next deployment

Acceptance Criteria
Required
GIVEN a technical user wants to trigger a notification from an application hosted behind the VA Network
WHEN they navigate to the API documentation in the Self Service UI
THEN they can identify the right type of URL to use for their desired environment
GIVEN a technical user wants to trigger a notification from an application which is hosted outside the VA Network
WHEN they navigate to the API documentation in the Self Service UI
THEN they can identify the right type of URL to use for their desired environment
QA Considerations
For QA to populate. Leave blank if QA is not applicable on this ticket.

Works in swagger (since we aren't validating Portal) and is clear on which URL to use in which circumstance

Potential Dependencies
Leave blank if n/a
Out of Scope
Leave blank if n/a

Portal Deployment
Validating Portal

Hey team! Please add your planning poker estimate with Zenhub @cris-oddball @EvanParish @justaskdavidb2 @k-macmillan @kalbfled @ldraney @nikolai-efimov

Team will ping Strike to give a heads-up once this ticket is done.

Suggestions for whomever picks up this ticket; there are at least two ways to go here.
Docs

Declare everything in an array

servers:
  - url: 'https://api.notifications.va.gov'
    description: Production VPC endpoint
  - url: 'https://api.staging.notifications.va.gov'
    description: Staging VPC endpoint
  - url: 'https://perf.notifications.va.gov'
    description: Perf VPC Endpoint
  - url: 'https://dev.notifications.va.gov'
    description: Dev VPC Endpoint
  - url: 'https://api.va.gov/vanotify'
    description: Production Public Endpoint
  - url: 'https://staging-api.va.gov/vanotify'
    description: Staging Public endpoint
  - url: 'https://sandbox-api.va.gov/vanotify'
    description: Perf Public Endpoint
  - url: 'https://dev-api.va.gov/vanotify'
    description: Dev VPC Endpoint

Private Zenhub Image
Private Zenhub Image

Use enums and descriptions (probably more aesthetically pleasing)

servers:
  - url: 'https://{environment}.notifications.va.gov'
    description: VPC endpoints; must be on the VA network
    variables:
      environment:
        enum:
          - api
          - staging-api
          - perf-api
          - dev.api
        default: api
  - url: 'https://{environment}.va.gov/vanotify'
    description: Public Endpoints for use outside of the VPC
    variables:
      environment:
        enum:
          - api
          - staging-api
          - sandbox-api
          - dev-api
        default: api

Private Zenhub Image
Private Zenhub Image

Made modifications based on Kyle's feedback, pinged Strike, closing this ticket!


fix: "Invalid permissions on Lambda function" on path parameter

Issue #, if available:
#110
Description of changes:
fix the issue #110
Description of how you validated changes:
Deployed the following template successfully on CloudFormation.
Also I confirmed deployed APIs works well.
Resources:
  HelloWorldFunction:
    Type: AWS::Serverless::Function
    Properties:
      CodeUri: hello_world/
      Handler: app.lambda_handler
      Events:
        HttpGetUserExampleExample:
          Type: Api
          Properties:
            Path: '/users/example/example'
            Method: GET
        HttpGetUserGroupIdUserId:
          Type: Api
          Properties:
            Path: '/users/{groupId}/{userId}'
            Method: GET
        HttpGetGroupAster:
          Type: Api
          Properties:
            Path: '/groups/{proxy+}'
            Method: GET

Checklist:

[ ] Write/update tests

If this pull request is on the right path, I will add some tests

[x] make pr passes
[x] Update documentation
[x] Verify transformed template deploys and application functions as expected
[x] Add/update example to examples/2016-10-31

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #992 into develop will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           develop     #992   +/-   ##
========================================
  Coverage    94.71%   94.71%
========================================
  Files           69       69
  Lines         3160     3160
  Branches       606      606
========================================
  Hits          2993     2993
  Misses          85       85
  Partials        82       82

Impacted Files
Coverage Δ

samtranslator/model/eventsources/push.py
88.85% <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 88df20c...9107b75. Read the comment docs.

Thanks for this contribution! This pr is against develop which is correct, could you please add tests as well?

Thank you for your response.
I will add some tests soon.

@praneetap
I've added tests.
I don't know why travis failing but all tests(make pr) has passed on my local machine.

rebased on current develop branch

rebased on current develop branch

Thanks! Could you also add an input/output test?

@brettstack
Thank you for your response.
Does an input/output test is like this...? https://github.com/awslabs/serverless-application-model/pull/992/commits/9208fde3ad9907a7f16d1d86b4cd533a922d275d


Sampling problems when no_model_error=True

Similarly to Added small amount to pollution event size #139, a small non-zero value is needed for epsilon when no_model_error=True  to avoid sampling problems and prevent NaNs in gradient of log-probability.
Instead of adding a small amount, taking the maximum may be "cleaner".

CORRECTION: the issue was not the sampling but the fact that Yerror=0. The error was zero because mf_variability was used instead of mf_repeatability, while using averaging_period = ['4H', '4H', '4H', '4H']. The solution is to use averaging_period = [None, None, None, None] and averaging_error = False.


[dateTimePicker] miss 'Empty date` support

What package is this for?

[ ] React
[x] Angular

Describe the bug
miss 'Empty date` support
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Please create a reduced test case in CodeSandbox:
https://codesandbox.io/s/github/IBM/carbon-addons-iot-react/tree/master/examples/codesandbox

Expected behavior
A clear and concise description of what you expected to happen.
Environment/versions:

OS: [e.g. MacOS, Windows]
Browser: [e.g. chrome, safari]
carbon-addons-iot-react version: [e.g. v2.60.0]

Additional context
If applicable, add screenshots to help explain your problem.
Add any other context about the problem here.
Specific timeline issues / requests
Do you want this work within a specific time period? Is it related to an
upcoming release?
NB: The core contributors will try to work with your timeline, but it's not
guaranteed. The earlier you make a request in advance of a desired delivery
date, the better!

@sophiiae I assume this is for Angular, since your other DateTIme bugs have been for Angular?

@sophiiae I assume this is for Angular, since your other DateTIme bugs have been for Angular?

Yes, it's for Angular, thank you Jordan.


Change floating label placeholder's color

Description
Changed the floating labels placeholder's text color from black to light gray (opacity: 0.65).
I removed the styling from the other label tags under .form-select and .form-control:-webkit-autofill parents as every label should now have the same behavior.
Motivation & Context
As requested in issue #39420
Type of changes

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

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
[ ] My change introduces changes to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://deploy-preview-39494--twbs-bootstrap.netlify.app/docs/5.3/forms/floating-labels/#example/
Related issues

#39420

👍 Yes! I've often been confused by the current text color since it looks like a value rather than a placeholder.

I think it's fine as-is.

Is there anything preventing this from being merged?

Is there anything preventing this from being merged?

For the moment, the target of this one is v5.4.0. The next version will probably be a v5.3.x. We'll evaluate when to merge it at the appropriate time.


RPC: starknet_simulateTransactions endpoint

The goal is to enable starknet_simulateTransactions endpoint from the new trace spec that allows to dry run a batch of transactions (declare, deploy, invoke) and get execution trace (with all the internal calls).
Depends on (need to change dependency urls before merging):

https://github.com/keep-starknet-strange/starknet-api/pull/10
https://github.com/keep-starknet-strange/blockifier/pull/9
https://github.com/0xs34n/starknet.js/pull/694 (for tests)

Notes:

Supports both starknet_simulateTransaction (legacy starknet.js compatible) and starknet_simulateTransactions (spec 0.4.0-rc2)
Works with declare v1 transactions only (serde cannot handle v2 for some reason)

Big thanks to @tdelabro and @greged93 for the help :heart:
Cc @Eikix
Created in Starknet Hacker House :croissant:

I will add few more tests to the pallet (to increase codecov and check some edge cases) also need to resolve failing integration tests.


convert batch to graph data format on the fly

❓ Questions & Help
Hi! I have a batch of graphs with the same "graph structure" (the same number of nodes, the same connectivity matrix, the same node order, but different features). I want to do something like this on the fly:
def forward(self, x):
    # some my operations
    # x.size() = (batch_size, num_nodes, num_features)
    x = convert_to_acceptable_format(x)
    x = GCNConv(x, same_edge_index_for_all_graph_in_batch)
    x = convert_back_to_tensor(x) # of size (batch_size, num_nodes, num_features)
    # some my operations
    return x

I searched through the documentation but did not found something directly relevant.
Could you recommend a solution, please

Please see this issue https://github.com/rusty1s/pytorch_geometric/issues/817


#117: use scriptoni for linting (closes #117)

Closes #117
Test Plan
tests performed

npm run lint ✅
npm run lint-fix ✅
npm run lint-style ✅
npm run lint-style-fix ✅

tests not performed (domain coverage)

At times not everything can be tested, and writing what hasn't been tested is just as important as writing what has been tested.

An example of partial test is a field displaying 4 possible values. If 3 values are tested, with screenshots, and 1 is not, then it should be mentioned here.}

npm run lint-style seems to fail:

PS: I did a clean install this time :P

@FrancescoCioria should be fixed now. I fixed scriptoni to force styelint version ^7.8.0


[unstable] gnome3.glade does not build

Issue description
glade-signal-editor.c:855:3: warning: 'gtk_style_context_get_background_color' is deprecated: Use 'gtk_render_background' instead [-Wdeprecated-declarations]
   gtk_style_context_get_background_color (context, state, &rgba);
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /nix/store/18gpnj11bvvg2r6mx1a207yhn5cl7078-gtk+3-3.22.24-dev/include/gtk-3.0/gtk/gtkicontheme.h:27:0,
                 from /nix/store/18gpnj11bvvg2r6mx1a207yhn5cl7078-gtk+3-3.22.24-dev/include/gtk-3.0/gtk/gtk.h:123,
                 from ../gladeui/glade-property-class.h:6,
                 from ../gladeui/glade-widget-adaptor.h:5,
                 from glade.h:25,
                 from glade-signal-editor.c:35:
/nix/store/18gpnj11bvvg2r6mx1a207yhn5cl7078-gtk+3-3.22.24-dev/include/gtk-3.0/gtk/gtkstylecontext.h:1201:6: note: declared here
 void gtk_style_context_get_background_color (GtkStyleContext *context,
      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  CC       libgladeui_2_la-glade-signal-model.lo
glade-signal-model.c:68:1: error: conflicting types for 'g_ptr_array_find'
 g_ptr_array_find (GPtrArray *array, gpointer data)
 ^~~~~~~~~~~~~~~~
In file included from /nix/store/kbh1dk6k8chjh853w5d6sadlkdh94j74-glib-2.54.1-dev/include/glib-2.0/glib.h:31:0,
                 from /nix/store/kbh1dk6k8chjh853w5d6sadlkdh94j74-glib-2.54.1-dev/include/glib-2.0/gobject/gbinding.h:28,
                 from /nix/store/kbh1dk6k8chjh853w5d6sadlkdh94j74-glib-2.54.1-dev/include/glib-2.0/glib-object.h:23,
                 from glade-signal-model.h:23,
                 from glade-signal-model.c:23:
/nix/store/kbh1dk6k8chjh853w5d6sadlkdh94j74-glib-2.54.1-dev/include/glib-2.0/glib/garray.h:186:12: note: previous declaration of 'g_ptr_array_find' was here
 gboolean   g_ptr_array_find               (GPtrArray        *haystack,
            ^~~~~~~~~~~~~~~~
make[3]: *** [Makefile:1210: libgladeui_2_la-glade-signal-model.lo] Error 1
make[3]: Leaving directory '/tmp/nix-build-glade-3.20.0.drv-0/glade-3.20.0/gladeui'
make[2]: *** [Makefile:715: all] Error 2
make[2]: Leaving directory '/tmp/nix-build-glade-3.20.0.drv-0/glade-3.20.0/gladeui'
make[1]: *** [Makefile:505: all-recursive] Error 1
make[1]: Leaving directory '/tmp/nix-build-glade-3.20.0.drv-0/glade-3.20.0'
make: *** [Makefile:435: all] Error 2
builder for ‘/nix/store/hmxi2jw1qnq12ma382c8yds39qknc8xz-glade-3.20.0.drv’ failed with exit code 2
error: build of ‘/nix/store/hmxi2jw1qnq12ma382c8yds39qknc8xz-glade-3.20.0.drv’ failed
/run/current-system/sw/bin/nix-shell: failed to build all dependencies

Steps to reproduce
nix-shell -p gnome3.glade
Technical details

System: 18.03pre118631.66b63d2f5a (Impala)
Nix version: nix-env (Nix) 1.11.15
Nixpkgs version: "18.03pre118631.66b63d2f5a"
Sandboxing enabled: build-use-sandbox = true

See, https://bugzilla.gnome.org/show_bug.cgi?id=782161. I thought I had fixed it somewhere but cannot find it ATM.


Add Conway parameters in ProtocolParameters

Changelog
- description: |
    Add Conway parameters in ProtocolParameters
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - improvement    # QoL changes e.g. refactoring
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context
Fix of https://github.com/IntersectMBO/cardano-cli/issues/729
I'm not exactly sure of the design, confirmation or negation welcome :pray:
How to trust this PR

I ran cabal test all on CLI, with a SRP to this PR; and all tests passed
I executed tests of cardano-node with this PR and they pass: https://github.com/IntersectMBO/cardano-node/pull/5826

Checklist

[X] Commit sequence broadly makes sense and commits have useful messages
[X] Behavior is tracked with a golden test in cardano-node: https://github.com/IntersectMBO/cardano-node/blob/ee89cd85388d9c6db77ac55034446b28590f6666/cardano-testnet/test/cardano-testnet-test/Cardano/Testnet/Test/Cli/Queries.hs#L92
[X] Self-reviewed the diff

Probably superseded by https://github.com/IntersectMBO/cardano-cli/pull/758 and will be closed soon

Superseded by https://github.com/IntersectMBO/cardano-cli/pull/758, so closing


WFCORE-384 - Server does wrongly reference a list of socket binding groups

This currently correctly limits the s-b-g to 1 per server / host. Rather than make extensive changes to the sbg constructors at the moment to use maxOccurs, this just changes the resource descriptions to match what is currently allowed.

There were a couple of other issues that came up during testing this, which I'll open seperate tickets for:
(A) - You can perform /host=master/server=server-one/socket-binding-group=standard-sockets:remove and the operation completes. However, if you try to add, you get:
/host=master/server=server-one/socket-binding-group=standard-sockets:add
{
"outcome" => "failed",
"result" => undefined,
"failure-description" => "WFLYCTL0249: Operation 'add' targeted at resource '[("socket-binding-group" => "standard-sockets")]' was directly invoked by a user. User operations are not permitted to directly update the persistent configuration of a server in a managed domain.",
"response-headers" => {"process-state" => "reload-required"},
"rolled-back" => true
}
Should the add be allowed, or the remove be prevented? On reload after the remove, the previous value is restored, so it isn't being persisted.
B) /host=master/socket-binding-group=test1:add(default-interface=public)
This completes as expected, however, removing it and re-adding generates the following exception:
[Host Controller] 19:27:34,481 ERROR org.jboss.as.controller.management-operation WFLYCTL0013: Operation ("add") failed - address: ([
Host Controller,
Host Controller
[Host Controller] ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.socket-binding-manager is already registered
[Host Controller] at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
[Host Controller] at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
[Host Controller] at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
[Host Controller] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
[Host Controller] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
[Host Controller] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
[Host Controller] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
[Host Controller] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
[Host Controller] at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:2114)
[Host Controller] at org.jboss.as.server.services.net.BindingGroupAddHandler.performRuntime(BindingGroupAddHandler.java:112)
[Host Controller] at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:337)
[Host Controller] at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151)
[Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
[Host Controller] at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
[Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
[Host Controller] at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1329)
[Host Controller] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:400)
[Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:222)
[Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208)
[Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
[Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:152)
[Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:148)
[Host Controller] at java.security.AccessController.doPrivileged(Native Method)
[Host Controller] at javax.security.auth.Subject.doAs(Subject.java:422)
[Host Controller] at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
[Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:148)
[Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)
[Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472)
[Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[Host Controller] at java.lang.Thread.run(Thread.java:745)
[Host Controller] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
[Host Controller]

Windows Build 3139 outcome was FAILURE using a merge of afe2cbe402c0174c5f9756bfa1f0798e89db5f89
Summary: Execution timeout (new); tests passed: 3555, ignored: 56 Build time: 01:00:19

retest this please

retest this please

@luck3y re: your question (A):
Any config write op from a user that directly addresses a domain server resource should fail. User's can't directly touch a domain server's config; only their HC can, as part of the HC's processing a user request targeting a domain-wide or host-specific resource.
What you've described here is another variant of the https://issues.jboss.org/browse/WFCORE-771 bug. It's an absolutely critical bug if the ops are actually changing the server state in some way.

Re your (B):
Does the remove include the normal "reload-required" stuff in the response? If not that's a bug. If so, it's the usual WFCORE-1106 scenario.

@bstansberry Yes, it does show reload-required, this whole sequence is:
[domain@localhost:9990 /] /host=master/socket-binding-group=test1:add(default-interface=public)
{
"outcome" => "failed",
"result" => {},
"failure-description" => {"host-failure-descriptions" => {"master" => "WFLYCTL0212: Duplicate resource [
("host" => "master"),
("socket-binding-group" => "test1")
]"}},
"rolled-back" => true
}
[domain@localhost:9990 /] /host=master/socket-binding-group=test1:remove
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined,
"response-headers" => {"process-state" => "reload-required"}
}
[domain@localhost:9990 /] /host=master/socket-binding-group=test1:add(default-interface=public)
{
"outcome" => "failed",
"result" => {},
"failure-description" => {"host-failure-descriptions" => {"master" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.socket-binding-manager is already registered"}},
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
}

Ah, I just read 1106, got it ;)

@luck3y this doesn't look quite right:
[domain@localhost:9990 /] /host=master/socket-binding-group=test1:remove
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined,
"response-headers" => {"process-state" => "reload-required"}
}

Under the "response-headers" node I also expect to see "operation-requires-reload" => true.
So something is missing in the reporting on the op. But still, the preceding add op didn't report the host being in reload-required, while the remove op did, so my deduction is the remove op is what put the host in r-r! ;) And so this is the 1106 situation.

Windows Build 3148 outcome was FAILURE using a merge of afe2cbe402c0174c5f9756bfa1f0798e89db5f89
Summary: Execution timeout; tests passed: 3551, ignored: 56 Build time: 01:00:12

The issue I mentioned with "operation-requires-reload" => true not being present seems to be a problem with DomainFinalResultHandler. Any response-header data reported by the individual hosts is not getting aggregated into the overall response. I'm not sure exactly how it should be aggregated.


HBASE-28153 Upgrade zookeeper to a newer version

: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:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 46s
branch-2 passed

+1 :green_heart:
compile
4m 56s
branch-2 passed

+1 :green_heart:
spotless
0m 44s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
4m 54s
the patch passed

+1 :green_heart:
javac
4m 54s
the patch passed

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

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

+1 :green_heart:
hadoopcheck
13m 22s
Patch does not cause any errors with Hadoop 2.10.2 or 3.2.4 3.3.6.

+1 :green_heart:
spotless
0m 41s
patch has no errors when running spotless:check.

_ Other Tests _

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

33m 55s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac hadoopcheck spotless xml compile

uname
Linux 2e9b8745715b 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Eclipse Adoptium-11.0.17+8

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

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

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

versions
git=2.34.1 maven=3.8.6

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
2m 22s
Docker mode activated.

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

_ Prechecks _

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 53s
branch-2 passed

+1 :green_heart:
compile
1m 48s
branch-2 passed

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

+1 :green_heart:
javadoc
2m 39s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
260m 12s
root in the patch failed.

294m 22s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f6b8b01dc3d9 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Eclipse Adoptium-11.0.17+8

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

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

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

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

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

versions
git=2.34.1 maven=3.8.6

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
2m 26s
Docker mode activated.

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

_ Prechecks _

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 27s
branch-2 passed

+1 :green_heart:
compile
1m 25s
branch-2 passed

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

+1 :green_heart:
javadoc
2m 14s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

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

409m 10s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 5c9d0178f2c0 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Temurin-1.8.0_352-b08

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

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

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

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

versions
git=2.34.1 maven=3.8.6

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 14s
Docker mode activated.

_ Prechecks _

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

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

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
4m  9s
branch-2 passed

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

+1 :green_heart:
spotless
0m 47s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
6m 29s
the patch passed

+1 :green_heart:
javac
6m 29s
the patch passed

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

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

+1 :green_heart:
hadoopcheck
17m 16s
Patch does not cause any errors with Hadoop 2.10.2 or 3.2.4 3.3.6.

+1 :green_heart:
spotless
0m 48s
patch has no errors when running spotless:check.

_ Other Tests _

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

43m 43s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac hadoopcheck spotless xml compile

uname
Linux 66813b6fe861 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Eclipse Adoptium-11.0.17+8

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

modules
C: hbase-zookeeper hbase-server hbase-it . U: .

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

versions
git=2.34.1 maven=3.8.6

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 45s
Docker mode activated.

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

_ Prechecks _

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 55s
branch-2 passed

+1 :green_heart:
compile
1m 48s
branch-2 passed

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

+1 :green_heart:
javadoc
2m 25s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
261m 12s
root in the patch failed.

293m  4s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 98ae3bc9e04c 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Eclipse Adoptium-11.0.17+8

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

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

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

modules
C: hbase-zookeeper hbase-server hbase-it . U: .

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

versions
git=2.34.1 maven=3.8.6

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
1m 17s
Docker mode activated.

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

_ Prechecks _

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
3m 48s
branch-2 passed

+1 :green_heart:
compile
1m 59s
branch-2 passed

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
358m 33s
root in the patch failed.

396m 19s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7ae40b308743 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Temurin-1.8.0_352-b08

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

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

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

modules
C: hbase-zookeeper hbase-server hbase-it . U: .

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

versions
git=2.34.1 maven=3.8.6

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 36s
Docker mode activated.

_ Prechecks _

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

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

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 47s
branch-2 passed

+1 :green_heart:
compile
4m 59s
branch-2 passed

+1 :green_heart:
spotless
0m 43s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

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

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

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

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

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

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

+1 :green_heart:
hadoopcheck
13m 37s
Patch does not cause any errors with Hadoop 2.10.2 or 3.2.4 3.3.6.

+1 :green_heart:
spotless
0m 42s
patch has no errors when running spotless:check.

_ Other Tests _

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

34m 11s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac hadoopcheck spotless xml compile

uname
Linux ab3fcaac2546 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Eclipse Adoptium-11.0.17+8

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

modules
C: hbase-zookeeper hbase-server hbase-it . U: .

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

versions
git=2.34.1 maven=3.8.6

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 41s
Docker mode activated.

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

_ Prechecks _

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 56s
branch-2 passed

+1 :green_heart:
compile
1m 49s
branch-2 passed

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

+1 :green_heart:
javadoc
2m 26s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
266m 16s
root in the patch failed.

298m 47s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f357ff6ccb2d 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Eclipse Adoptium-11.0.17+8

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

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

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

modules
C: hbase-zookeeper hbase-server hbase-it . U: .

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

versions
git=2.34.1 maven=3.8.6

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 47s
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 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 26s
branch-2 passed

+1 :green_heart:
compile
1m 26s
branch-2 passed

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
384m 55s
root in the patch passed.

414m  5s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ab94e4cb35e2 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Temurin-1.8.0_352-b08

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

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

modules
C: hbase-zookeeper hbase-server hbase-it . U: .

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

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

Ah, a bit strange...
Let me check the pom for hbase-backup on branch-2.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 34s
branch-2 passed

+1 :green_heart:
compile
4m 54s
branch-2 passed

+1 :green_heart:
spotless
0m 41s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

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

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

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

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

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

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

+1 :green_heart:
hadoopcheck
13m 38s
Patch does not cause any errors with Hadoop 2.10.2 or 3.2.4 3.3.6.

+1 :green_heart:
spotless
0m 42s
patch has no errors when running spotless:check.

_ Other Tests _

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

34m  2s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac hadoopcheck spotless xml compile

uname
Linux 61ca94c25f1a 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Eclipse Adoptium-11.0.17+8

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

modules
C: hbase-zookeeper hbase-server hbase-backup hbase-it . U: .

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

versions
git=2.34.1 maven=3.8.6

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 41s
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 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 39s
branch-2 passed

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

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

+1 :green_heart:
javadoc
2m 33s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
268m 24s
root in the patch passed.

300m 50s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 441cc7af1fbd 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Eclipse Adoptium-11.0.17+8

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

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

modules
C: hbase-zookeeper hbase-server hbase-backup hbase-it . U: .

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

versions
git=2.34.1 maven=3.8.6

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 42s
Docker mode activated.

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

_ Prechecks _

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 26s
branch-2 passed

+1 :green_heart:
compile
1m 27s
branch-2 passed

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

+1 :green_heart:
javadoc
2m 10s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
313m 49s
root in the patch failed.

341m 32s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9f8e40f385ea 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4f3e63e5de

Default Java
Temurin-1.8.0_352-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5484/4/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-root.txt

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

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

modules
C: hbase-zookeeper hbase-server hbase-backup hbase-it . U: .

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

versions
git=2.34.1 maven=3.8.6

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 36s
Docker mode activated.

_ Prechecks _

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

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

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 36s
branch-2 passed

+1 :green_heart:
compile
4m 57s
branch-2 passed

+1 :green_heart:
spotless
0m 41s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
4m 58s
the patch passed

+1 :green_heart:
javac
4m 58s
the patch passed

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

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

+1 :green_heart:
hadoopcheck
13m 33s
Patch does not cause any errors with Hadoop 2.10.2 or 3.2.4 3.3.6.

+1 :green_heart:
spotless
0m 42s
patch has no errors when running spotless:check.

_ Other Tests _

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

33m 55s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5484/5/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac hadoopcheck spotless xml compile

uname
Linux 954a38c67e0c 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / a208ba2a14

Default Java
Eclipse Adoptium-11.0.17+8

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

modules
C: hbase-zookeeper hbase-server hbase-backup hbase-it . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5484/5/console

versions
git=2.34.1 maven=3.8.6

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 43s
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 Compile Tests _

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

+1 :green_heart:
mvninstall
2m 56s
branch-2 passed

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
226m 17s
root in the patch failed.

258m  4s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5484/5/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 6c81163ca544 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / a208ba2a14

Default Java
Eclipse Adoptium-11.0.17+8

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5484/5/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-root.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5484/5/testReport/

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

modules
C: hbase-zookeeper hbase-server hbase-backup hbase-it . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5484/5/console

versions
git=2.34.1 maven=3.8.6

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 42s
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 Compile Tests _

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

+1 :green_heart:
mvninstall
2m  5s
branch-2 passed

+1 :green_heart:
compile
1m 25s
branch-2 passed

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

+1 :green_heart:
javadoc
2m 10s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
314m  3s
root in the patch failed.

341m 22s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5484/5/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e52ad57a9cd8 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / a208ba2a14

Default Java
Temurin-1.8.0_352-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5484/5/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-root.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5484/5/testReport/

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

modules
C: hbase-zookeeper hbase-server hbase-backup hbase-it . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5484/5/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.


cannot find all dependencies, unable to resolve root package?

Describe the bug
github.com/name/project/app/modA/api cannot find all dependencies, unable to resolve root packag
** The struct of proejct looks like **
+project
+-internal
+--token
+--others
+-app
+--modA
|----internal
|---main.go
|-go.mod
|-go.sum
To Reproduce
// current path project root
go env -w GO111MODULE="on"
swag init -g app/mod/api/main.go  --parseDependency --parseInternal
Your swag version
swag version v1.7.0
Your go version
go 1.16 dawin/amd64

I'm having the same issue -- this used to work fine.  The only thing that changed I think is that I updated my go version recently.  Current version I am on is go version go1.16.3 darwin/amd64

if local go version is different from the version used to compile and build swag, you need to compile and build swag again. I think this issue is caused by swag's dependency package depth, see https://github.com/KyleBanks/depth/issues/15

For me the problem was resolved with executing: go get github.com/swaggo/swag/cmd/swag

The solution from @ilyulev solve it for me as well.

For me the problem was resolved with executing: go get github.com/swaggo/swag/cmd/swag

I use go1.17, and I solved it by:
go install github.com/swaggo/swag/cmd/swag@latest


Enqueue hydra with other hydra (compound requests)

I like the compositional nature of hydra; you can define what needs to happen once requests complete.
But for complex operations you might want to split up the hydra movements into different functions.
Was Hydra designed to enqueue other hydra?

@fatuhoku thanks for your question! Hydra was designed for that type of workload. Hydra wraps libcurl's multi, you can read more about its capabilities and limitations here: https://curl.haxx.se/libcurl/c/libcurl-multi.html.


new app environment enum

Goal

Testing

Release Notes

WHAT:
WHY:
WHO:

#546
#517
#516
#613  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nelsitoPuglisi and the rest of your teammates on  Graphite


PDF Rendering Issue at 100%

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: Chrome 114.0.5735.199 (Official Build) (64-bit)
Operating system and its version: Windows 10
PDF.js version: 3.9.167
Is a browser extension: No

Steps to reproduce the problem:

Load PDF into the mozilla pdfjs viewer
174-437_Pharma_Page_Rev2.pdf

Choose display at actual size

What is the expected behavior? (add screenshot) It should render correctly - Renders correctly in the Chrome native built in viewer.
What went wrong? (add screenshot) Renders a very blurry image that is only about 20% of the actual file.
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Duplicate of #14982


Support Google Cloud Storage

Currently Nebula defines file system interface in its storage component. Under this interface, there are a few implementations such as

local file system
S3 file system

There two are mostly used so far, now we're asking a new support to allow Nebula read and write data with GCS. This will be needed for nebula deployment in Google Cloud Platform.

checked in a basic version that can build #90 , but test still crash - most likely is problems with CURL, but not easy to figure out, added a test in TestStorage.cpp to ensure the crash (exception) can be fixed - https://github.com/varchar-io/nebula/blob/master/src/storage/test/TestStorage.cpp#L220
The test can be executed on Mac, with upload scenario success and failed in download.

@samprasyork
Status of running this test:

On Mac: upload works fine, I can see it uploads the file to gs://nebula-com, download failed due to CURL exception
On Linux: crashed on std:badalloc exception which is from CurlRequestBuilder::AddOption

related:  https://github.com/googleapis/google-cloud-cpp/issues/5970


Incorrect escaping for metric names

What's the rationale for merging 0fdfff5ee5b799e5f4226a0265bf9ad5f2be7c11? Icinga's Graphite module escapes dots in metric names (because Graphite uses them to put the metrics into a hierarchy).

Nevermind, I just realized this was already fixed. :)


HOSTED_FIELDS_TIMEOUT in SPA

General information

SDK version: 3.36.0
Environment: Production
Browser and OS: Chrome 70.0.3538.110 (64-bit) on MacOS 10.14.1

Issue description
Hello.
We use hosted fields and PayPal integrations for a while in our React based SPA.
After upgrading Braintree JS SDK we've noticed a huge amount of HOSTED_FIELDS_TIMEOUT errors in our errors tracking system.
I've made some investigation and find the following scenario when this error occurs:

User opens payment form popup.
Braintree client and hosted fields instance initialization start
User clicks on 'PayPal' tab in the payment form before hosted fields initialization finished
Tab content with credit card form removed from the DOM but teardown method of the hosted fields cannot be called because of the hosted fields instance can be accessed only in the callback of hostedFields.create.
After 60 seconds SDK throws HOSTED_FIELDS_TIMEOUT error

Could you please give some advice how to avoid this error?

The root cause of this is that there's currently no way to cancel Hosted Fields from loading once it's started. We've gotten a number of reports of people needing this, so I'm thinking we could add something like:
var hostedFieldsCreatePromise = braintree.hostedFields.create(options);

braintree.hostedFields.cancel(hostedFieldsCreatePromise).then(function () {
  // hosted fields setup was succesfully cancelled
});

Just need to figure out a few details, like, what's the behavior when cancel is called after Hosted Fields is already set up?

Thank you for the response. Looks like the best solution for my case is to ignore HOSTED_FIELDS_TIMEOUT error if payment form component is unmounted.
The example you've proposed looks good. The one question I have is how to deal with it if callbacks are used instead of promises.
As for calling cancel after Hosted Fields is already set up, I'd propose to return an error (in callback or promise rejection) with a code like HOSTED_FIELDS_INITIALIZED.

We gave the cancel method a go in a spike and decided against it. The API for keeping state about whether or not you could use the cancel method turned out to be pretty gnarly, and, as you mentioned, it's impossible to use with the callback API.
The greatest bottleneck in the Hosted Fields creation should be at the client creation level. We've developed a new pattern for instantiating Hosted Fields that allows it to create a client for itself in the background. This dramatically speeds up the time it takes Hosted Fields to set up. Update to v3.39.0 and you can try it out with:
braintree.hostedFields.create({
  authorization: 'client_token_or_tokenization_key',
  // the rest of your hosted fields setup, skipping the client
}, function (err, instance) {
  // set up button
});

In addition, if you're using a client token for your authorization, but are not using 3D Secure, you may want to switch to a tokenization key.
This should solve most of the issue you are seeing, the few that might still trickle through from overzealous page navigation can be safely ignored. We're planning to address the few edge cases where you would still see an error like this in the next major version.

👋 We're going to close this issue, but if you continue to experience problems after switching to the suggested approach above, please let us know and we can re-open this.


Mysql syntax fix

Discussion: https://github.com/orgs/usememos/discussions/4062 and potentially this issue https://github.com/usememos/memos/issues/4105
The mysql syntax is missing a closing "
Note: I dont have a mysql db instance so this change untested. Apologies for not testing

I'm having a shocker with this pr. will delete and resubmit with a clean change history


fix(treesitter): set highlight of TSModuleInfo signs

The default color for signs in the :TSModuleInfo view is very bright and inconsistent with the colorscheme.
before

after

First off, thanks a lot for all these PRs the small appreciation :) It means a lot.
Maybe it's better to use ui_* colors here? The way I see it, if it's not code, then we should probably use ui colors.
I plan to add contribution guidelines explaining stuff like this soon.