Adds top and first-level nav items configuration file

Adds top and first-level nav items configuration file to remove hardcoded
navigation menu items.
Additions

Added top and first-level navigation items config file for removing hardcoded navigation menu items in the main menu.
Adds TODO comment for commented out Español code block.

Changes

Builds main menu from global nav-items configuration file.

Testing

Main menu should function/look the same.

Review

@jimmynotjim
@KimberlyMunoz
@sebworks

Notes

Part of DF-1963, because I need a list for the sidenav menu to build the structure from. This is a self-contained change so I wanted to spin it off for feedback while I worked on the sidenav implementation.

Pushed an edit in https://github.com/cfpb/cfgov-refresh/commit/30257a21a8351b915835f60096e12fa1474430c8, forgot that the About button needs an empty href to show the hand cursor and that the empty menu items were producing hidden submenu HTML.

:+1: I'm not sure if the Spanish content is ever going to come back, would be worth checking in on but not something that needs to happen here.

Let's get another sign-off so we can merge this one.

:+1:

In @anselmbradford's absence I'm going to go ahead and merge this so we can review the Sprint PR


About transferability experiment

Hi Justin,
Thank you for the great toolkit. Can you tell me which data augmentation methods were used in the transferability experiment of the paper？

I think Table 5 mentions that they use DSA Augmentation ....


Assert at End of TestSuite Setup (Before Tests)

A great strategy for "ensuring" a controller or resources is to have a step 0 assert of that instance running
see https://github.com/kudobuilder/kudo/pull/1473
test/e2e/cli-install-uninstall/00-assert.yaml
apiVersion: v1
kind: Pod
metadata:
  labels:
    app: kudo-manager
    control-plane: controller-manager
  namespace: kudo-system
status:
   phase: Running

Assuming you may want this as a precondition on all tests... it would be great to assert this at the end of TestSuite setup prior to tests.

something like:
apiVersion: kudo.dev/v1beta1
kind: TestSuite
crdDir: ./config/crds/
manifestDirs:
- ./test/manifests/
testDirs:
- ./test/integration
commands:
  - command: ./bin/manager
    background: true
startControlPlane: true
setup-assert:
    controller-running.yaml


stack upgrade test: pull lifecycle image

The paketo bionic builder is now dead, and so its lifecycle image version is not in lockstep with jammy builder anymore.
Fixes error "failed to build: fetching lifecycle image: image 'buildpacksio/lifecycle:0.16.5' does not exist on the daemon"
(Note: you see this error if you flip the order of builders in integration.json. Currently the error is hidden because this test on bionic is run after tests on jammy)
Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

Approving, though I'm not a Php maintainer.


Update dependencies

This PR:

Updates dependencies to get it working again
Adds a more clear message
Adds a README file

Thanks for the PR


Feature/intermediate representation data format

This pull request fixes #1560 and provides the ability to ask the IntermediateEventRepresentation for the Serializer and if its data can be converted to a target format.
This is useful if you want to detect if the Upcaster can upcast an event which is serialized in a certain way.
See https://discuss.axoniq.io/t/upcasters-for-json-and-xml/2799 for more details.

@abuijze you are probably right, there is no reason to have it inside the upcaster. And if you need it, you can access it via Injection... So I removed the access method and the test...


Dependency Chaos

Describe the bug
There are some weird dependencies.
For example @nxext/tailwind requires @nxext/svelte which needs a lot other peerDependencies.
Additionally @nxext/stencil requires<EMAIL_ADDRESS>which does not exist in NPM.
Currently I get a lot of warnings related to missing peer dependencies because of this.
Expected behavior
Clean and working dependencies.

The peerDependencies are not all needed, if you don't use all functionalities. e.g. the tailwind package (which will be removed soon) have both as a peer dependency cause they can generate the Tailwind config for stencil and svelte, but you don't need both to get them working. It'll need stencil for the stencil generator and svelte for the svelte generator


The name 'import/Mul' refers to an Operation not in the graph

#12736  This did not work for me is there any other solution for this ?
I changed my code as following
input_height = 299
input_width = 299
input_mean = 0
input_std = 299
input_layer = "Mul"
output_layer = "final_result"

input_name = "import/" + input_layer
output_name = "import/" + output_layer
input_operation = graph.get_operation_by_name(input_name)
output_operation = graph.get_operation_by_name(output_name)

Please suggest me a solution
Thank you

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce
Mobile device

This does not appear to be a bug in TensorFlow, and so might be more appropriate for Stack Overflow. However, if there is no node in the graph called "import/Mul"  and we don't know what the graph is or how it was produced, there's no chance that anyone will be able to suggest an answer. You might try printing the list of operations using graph.get_operations() and attempting to locate an appropriate-sounding node.


v10.1.0 - MarkerType.ArrowClosed not working

Describe the Bug
Hello.
I've just installed the new version (worked with version 9.x previously), and refactored my code to work as described in the docs.
I can't get the MarkerType.ArrowClosed setting to work.
here's how i define my edge:
edges.push({
            id: `edge-${nodes[i].id}-${nodes[i+1].id}-from`,
            source: nodes[i].id,
            target: nodes[i+1].id,
            markerEnd: { type: MarkerType.ArrowClosed },
          })

The result is a simple edge with no arrow. MarkerType.Arrow doesn't work either.
the html (svg) code generated for the edge is:
<g class="react-flow__edge react-flow__edge-default nopan"><path d="M832,29 C832,87.5 832,87.5 832,146" class="react-flow__edge-path" marker-end="url(#type=arrowclosed)" marker-start="url(#)"></path></g>

Note that the marker-end property is added as expected, but the arrow drawing doesn't include the arrow.
However, the defs section of the edges container is completely empty. so the type=arrowclosed marker is undefined
Is it a bug? or am I doing something wrong?
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Start with an empty canvas, and dynamically add a couple of nodes and an edge with an end marker as i've pasted in the description..
Expected behavior
I expect the edge to end with an arrow head.
Screenshots or Videos
No response
Platform
Google Chrome | 99.0.4844.51 (Official Build) (64-bit)
Revision | d537ec02474b5afe23684e7963d538896c63ac77-refs/branch-heads/4844@{#875}
OS | Linux
JavaScript | V8 <IP_ADDRESS>
Additional context
No response

I've done a bit of research, and it seems like the useMemo function in MarkerDefinitions is not called again as I add edges - even though the edges array is changing.
This is because the edges array is addressed by reference, and we get the same array in every run, just different values.
When I change the ReactFlow edges prop to edges={[...edges]} the arrows are indeed drawn. but this means i will make the useMemo function irrelevant since the array will change on every re-render even if there is no change to the edges.

Hey @noams-unbiased
when you are adding a new edge or node you should create a new array. Otherwise React Flow can't recognize the changes. Don't create a new array on every render but just when you add a new edge or node.


Ci fixes

Bumped some deps too pass ci

1 workflow awaiting approval
First-time contributors need a maintainer to approve running workflows. Learn more.
=(


Load Dataset I for CCA

I would like to add/load the dataset1 and analyze the results using the Session class into CCA code inside the +featextraction folder. I am suffering doing that as my Matlab skills are not very good, appreciate your support.

I managed to solve the above issuse but have the same other concerns, the codes do not have documentation and/or guidance files, for example, I was trying to use CCA.mat and faced several issues that need hours of debugging because I don't know what are the expectations of this code for the inputs and other details.

I managed to solve the above issuse but have the same other concerns, the codes do not have documentation and/or guidance files, for example, I was trying to use CCA.mat and faced several issues that need hours of debugging because I don't know what are the expectations of this code for the inputs and other details.

Dear Bayarisko,
before using the CCA.m, which is a function, you must clone the whole
processing toolbox, as there are several dependencies among the functions.
I recommend that you start by using one of the provided CCA examples (e.g.
[1], [2]) to better understand the use of the toolbox.
Best regards,
Kostas Georgiadis
[1]
https://github.com/MAMEM/eeg-processing-toolbox/blob/master/exampleCombiCCA.m
[2]
https://github.com/MAMEM/eeg-processing-toolbox/blob/master/exampleITCCA.m
On Sat, Jan 30, 2021 at 1:09 PM Bayarisko<EMAIL_ADDRESS>wrote:

I managed to solve the above issuse but have the same other concerns, the
codes do not have documentation and/or guidance files, for example, I was
trying to use CCA.mat and faced several issues that need hours of debugging
because I don't know what are the expectations of this code for the inputs
and other details.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MAMEM/eeg-processing-toolbox/issues/68#issuecomment-770195629,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADYVQYGYQ2DYAJSI42PWR63S4PSIJANCNFSM4VBSHCXA
.

Dear Bayarisko,
before using the CCA.m, which is a function, you must clone the whole
processing toolbox, as there are several dependencies among the functions.
I recommend that you start by using one of the provided CCA examples (e.g.
[1], [2]) to better understand the use of the toolbox.
Best regards,
Kostas Georgiadis
[1]
https://github.com/MAMEM/eeg-processing-toolbox/blob/master/exampleCombiCCA.m
[2]
https://github.com/MAMEM/eeg-processing-toolbox/blob/master/exampleITCCA.m
On Sat, Jan 30, 2021 at 1:09 PM Bayarisko<EMAIL_ADDRESS>wrote:

I managed to solve the above issuse but have the same other concerns, the
codes do not have documentation and/or guidance files, for example, I was
trying to use CCA.mat and faced several issues that need hours of debugging
because I don't know what are the expectations of this code for the inputs
and other details.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MAMEM/eeg-processing-toolbox/issues/68#issuecomment-770195629,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADYVQYGYQ2DYAJSI42PWR63S4PSIJANCNFSM4VBSHCXA
.


Donut Update

Changed:

Code used to clear the terminal/cmd window is now smaller and simpler.
Added a print statement with \n\n to make the doughnut not be all the way at the top of the screen and instead down a few lines. (Looks better)

still doesn't work has a lot of indent errors pls fix :]

still doesn't work has a lot of indent errors pls fix :]

That weird indentation was done my github as it was not there before making a patch. I'll still try to fix it.

I can confirm that the indentation was being automatically done by github.


Music

Pull Request Template
Description
Music Stream Neptune is a music streaming application developed in Kotlin. The application allows users to play, pause, shuffle, and repeat songs. It also provides a feature to like songs and maintain a list of liked songs. Using Firebase for database and cloud storage for music storing, UI build using jetpack compose framework.
Screenshots:

Additional Notes:
Open Source

added my music streaming app to showcase my project , and also edited playstore link column to download link, so anyone provide there app link , who had not publish it to playstore.

@navneet851 please follow the Pull Request Template
Also, don't add drive link, github link is sufficient.

@anandwana001 i made changes sir. will you please confirm.


Physics student sign-up flow

Adds Physics changes alongside the Ada components for the new sign-up flow (no noticeable changes should be visible on Ada).

Had a play around with this again and spotted a couple of minor issues:

You have to press tab twice to shift focus from Password to Confirm password, it must be focusing on something in between.
Invalid DoB (You must be over 10 years old to create an account.) doesn't prevent form submission as it's not a required field - maybe this is fine since the user has already confirmed they're old enough, but it's a bit weird for the message to show up.


Maybe rename this repo too?

To the NetlistDB respectively.

That the thing I would like to discuss with you. Do you like the name? Also what do you think about the roadmap also it would be great if we can come up some plane about integration to other tools.
This week I will finish verilog serializer and add rest of the hardware types, this will be the step which allows users to use this library.
It would be great if we can then discuss how to propagate this library. Because even in 2019 peoples still think that the verilog and tcl api are the best combination for hw developement https://github.com/abk-openroad/OpenSTA.
I do have verilog/vhdl parser https://github.com/Nic30/hdlConvertor. I planing to remove dependency on python and add support for this library. I think that this could be the main think for the users. But as I am alone it would take a time...

ROADMAP and name look good, yeah. I will be able to help with some parts, if it can be split up to the issues.

I think it is better to setup a Gitter channel for this project.

Excellent! Tomorrow I am going on a business trip then I do have to finish something for Open vSwitch. Then I will be able to finally finish the serialization to Verilog. From there it will be possible to parallelize development. As a start I would like to get rid of TBB because it is not flexible (replace by boost).

renamed, gitter established


Deployment errors while building | core-js compatibility error

Hi here is what I am doing, I am deploying the angular application using deploybot
here I have used 2.7.2 typescript
here is my package.json
{
  "name": "apex",
  "version": "4.1.0",
  "license": "",
  "scripts": {
    "start-server": "node server.js",
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "master-build": "ng build --prod --named-chunks",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@agm/core": "^1.0.0-beta.5",
    "@agm/js-marker-clusterer": "^1.0.0-beta.5",
    "@angular/animations": "^6.1.10",
    "@angular/common": "^6.1.10",
    "@angular/compiler": "^6.1.10",
    "@angular/core": "^6.1.10",
    "@angular/forms": "^6.1.10",
    "@angular/http": "^6.1.10",
    "@angular/platform-browser": "^6.1.10",
    "@angular/platform-browser-dynamic": "^6.1.10",
    "@angular/platform-server": "^6.1.10",
    "@angular/router": "^6.1.10",
    "@ng-bootstrap/ng-bootstrap": "^1.0.4",
    "@ngrx/store": "^5.2.0",
    "@ngx-share/core": "^6.0.1",
    "@ngx-translate/core": "^9.0.2",
    "@ngx-translate/http-loader": "^2.0.1",
    "@qontu/ngx-inline-editor": "^0.2.0-alpha.12",
    "@swimlane/ngx-charts": "^7.1.0",
    "@types/chartist": "^0.9.44",
    "@types/d3-shape": "^1.3.1",
    "agm-direction": "^0.5.9",
    "angular-calendar": "^0.23.7",
    "angular-formio": "^3.16.2",
    "angular-wizard-form": "^0.4.1",
    "angular2-signaturepad": "^2.8.0",
    "angular2-wizard": "^0.4.0",
    "angularfire2": "^5.1.3",
    "bootstrap": "^4.3.1",
    "bootstrap-material-design": "^4.1.1",
    "bourbon": "^4.3.4",
    "chartist": "^0.11.0",
    "classlist.js": "^1.1.20150312",
    "core-js": "^2.6.9",
    "d3": "^4.13.0",
    "firebase": "^5.11.1",
    "intl": "^1.2.5",
    "jquery": "^3.4.1",
    "js-marker-clusterer": "^1.0.0",
    "jspdf": "^1.5.3",
    "moment": "^2.24.0",
    "ng-chartist": "^1.1.1",
    "ng-lazyload-image": "^5.1.2",
    "ng-socket-io": "^0.2.4",
    "ng2-charts": "^1.6.0",
    "ng2-ckeditor": "1.2.2",
    "ng2-file-upload": "^1.3.0",
    "ng2-nouislider": "^1.8.2",
    "ng2-select2": "^1.0.0-beta.16",
    "ng2-validation": "^4.2.0",
    "ngx-chips": "^1.9.8",
    "ngx-color-picker": "^5.3.8",
    "ngx-text-overflow-clamp": "0.0.1",
    "ngx-toastr": "^9.2.0",
    "ngx-ui-switch": "^1.6.0",
    "node-sass": "^4.10.0",
    "nouislider": "^11.0.3",
    "ramda": "0.25.0",
    "resize-observer-polyfill": "^1.5.1",
    "rxjs": "6.0.0",
    "rxjs-compat": "6.2.2",
    "screenfull": "^3.3.3",
    "select2": "4.0.6-rc.1",
    "slick-carousel": "^1.8.1",
    "sweetalert2": "^7.33.1",
    "web-animations-js": "^2.2.5",
    "zone.js": "^0.8.29"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^0.11.4",
    "@angular/cli": "^6.2.9",
    "@angular/compiler-cli": "^6.1.10",
    "@angular/language-service": "^6.1.10",
    "@types/core-js": "^0.9.43",
    "@types/jasmine": "^2.8.16",
    "@types/jquery": "^3.3.29",
    "@types/jspdf": "^1.3.0",
    "@types/node": "^9.6.48",
    "@types/slick-carousel": "^1.6.33",
    "agm-overlays": "^1.3.3",
    "codelyzer": "^4.5.0",
    "jasmine-core": "^2.99.1",
    "jasmine-spec-reporter": "^4.2.1",
    "karma": "^3.1.4",
    "karma-chrome-launcher": "^2.2.0",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.4.3",
    "karma-jasmine": "^1.1.2",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "^5.4.2",
    "ts-node": "^4.1.0",
    "tslint": "^5.16.0",
    "typescript": "2.7.2"
  }
}

I am getting this error which is confusing to me,
ERROR in ./node_modules/formiojs/WebformBuilder.js
output Module not found: Error: Can't resolve 'core-js/modules/es.array.concat' in '/source/node_modules/formiojs'
output ERROR in ./node_modules/formiojs/Component.js
output Module not found: Error: Can't resolve 'core-js/modules/es.array.concat' in '/source/node_modules/formiojs'
output ERROR in ./node_modules/formiojs/Wizard.js
output Module not found: Error: Can't resolve 'core-js/modules/es.array.concat' in '/source/node_modules/formiojs'
output ERROR in ./node_modules/formiojs/EventEmitter.js
output Module not found: Error: Can't resolve 'core-js/modules/es.array.concat' in '/source/node_modules/formiojs'
output ERROR in ./node_modules/formiojs/Webform.js
output Module not found: Error: Can't resolve 'core-js/modules/es.array.concat' in '/source/node_modules/formiojs'
output ERROR in ./node_modules/formiojs/Form.js
output Module not found: Error: Can't resolve 'core-js/modules/es.array.concat' in '/source/node_modules/formiojs'
output ERROR in ./node_modules/formiojs/Formio.js
output Module not found: Error: Can't resolve 'core-js/modules/es.array.concat' in '/source/node_modules/formiojs'
output ERROR in ./node_modules/formiojs/components/address/Address.form.js

I have tried dowgrading the version of formio but still it is throwing same error.. Please help.

updating core-js to 3.1.3 will resolve your problem.

@saajidsyed this fixed the previously mentioned issue but now I am gettings issue on polyyfills.ts like
<EMAIL_ADDRESS>Module not found: Error: Can't resolve 'core-js/es7/reflect' in 'E:\xampp\htdocs\vpanel\node_modules\@angular-devkit\build-angular\src\angular-cli-files\models'

The issue is with an upgrade of core-js versions in formiojs. We can possibly fix this by making core-js a dependency in this library. I will make a new version that I hope resolves the problem.

Please try version 3.19.0 and let me know if it resolves this problem.

No, it didn't help me in fixing the issue that I am facing.

polyfills

Have you tried by clearing node modules and reinstall it? If not please delete node modules folder and reinstall. it may resolve your problem inshallah.

@saajidsyed Yes I have tried that thing fr each time, but it is still not working

@mudasserzahid Can you try by adding "core-js": 2.6.9 to your package file and reinstall node modules. it will solve your problem inshallah.

@saajidsyed , bro if you see in my first question. I used also "core-js": "2.6.9" and "core-js": "62.6.9" version.

@mudasserzahid If you do have "core-js": "2.6.9" in your application, when you type npm install you should see the following structure added to your "node_modules" folder.

node_modules

core-js
package.json version = 2.6.9
angular-formio

node_modules

core-js package.json version = 3.1.3

If you do not see this, then this tells me that NPM is confused. Please upgrade your NPM and then try to install again.

@saajidsyed , bro if you see in my first question. I used also "core-js": "2.6.9" and "core-js": "62.6.9" version.

Remove cap before the version number and try to install @mudasserzahid


Allow arbitrary headers in input/output components

See https://github.com/rayo/xmpp/pull/96 and https://github.com/rayo/xmpp/commit/4c8dbe3511eb3cd1210dc54b41136d8fc579b565
Fixes #232. Fixes #233

Coverage increased (+0.0%) to 99.07% when pulling c56a307549d88ed40fe43b9acfc611a43fa9a2a8 on feature/arbitrary_media_headers into 4050c59b7bc35beaca114e561cdfc28088832d83 on develop.

Coverage increased (+0.0%) to 99.07% when pulling c56a307549d88ed40fe43b9acfc611a43fa9a2a8 on feature/arbitrary_media_headers into 4050c59b7bc35beaca114e561cdfc28088832d83 on develop.


URLClassLoader and GraalVM

I wrote a Driver which is using GraalVM JS. The driver is loaded into an application using URLClassLoader.
This line of code from the driver is getting an exception
Context.newBuilder("js").allowAllAccess(true).build();

exception
No language and polyglot implementation was found on the classpath. Make sure the truffle-api.jar is on the classpath.

I tried also
Context.newBuilder("js").hostClassLoader(urlClassLoader).allowHostClassLoading(true).allowAllAccess(true).build();

and didn't work
In Gradle.properties I use :
implementation 'org.graalvm.js:js:22.2.0'
implementation 'org.graalvm.js:js-scriptengine:22.2.0'

and tried also
implementation "org.graalvm.sdk:graal-sdk:<IP_ADDRESS>"
implementation "org.graalvm.truffle:truffle-api:<IP_ADDRESS>"

I checked, and the truffle.jar is in passed to the URLCLassLoader. How can I fix this?

Hi, could you please share a reproducer code for this?

Duplicates https://github.com/oracle/graal/issues/4814


Incorrect Instant serialization to JSON

We are using dgc-java in Slovenia, forked at https://github.com/ixtlan-team/dgc-java
We have prepared the DGCs and found that for "test" DGCs that include sc field, we get a value of:
"sc": "2021-06-04T10:46:25.619935900Z"
This value is not well recieved by the verification app, as fraction has too many digits (9).
We have also found that in samples submitted by SE, value is
'"sc": "2021-06-02T06:02:13.262564Z"'
This value is correct, it has 6 digits in fraction.
You can disregard this issue and mark it closed and we will try and resolve the issue on our own.
From what we found the correct way would be to fix the 'ObjectMapper jsonMapper' in 'DigitalCovidCertificate'.
Alternative would be to add JsonFormatter to the Instant field in 'TestStatement'

@jozemlakar Thanks for pointing it out. The PR https://github.com/DIGGSweden/dgc-java/pull/67 fixes this.

PR #67 removes all fractions. As test show, it should hold EXACTLY 6 digits for fractions.

6 fractions? From where did you get that information?
From the specification:
The date and time when the test sample was collected. The time MUST include information on the time zone. The value MUST NOT denote the time when the test result was produced.
Exactly 1 (one) non-empty field MUST be provided.
One of the following ISO 8601 formats MUST be used. Other options are not supported.
YYYY-MM-DDThh:mm:ssZ
YYYY-MM-DDThh:mm:ss[+-]hh
YYYY-MM-DDThh:mm:ss[+-]hhmm
YYYY-MM-DDThh:mm:ss[+-]hh:mm

Examples:
"sc": "2021-08-20T10:03:12Z"	(UTC time)
"sc": "2021-08-20T12:03:12+02"	(CEST time)
"sc": "2021-08-20T12:03:12+0200"	(CEST time)
"sc": "2021-08-20T12:03:12+02:00"	(CEST time)

Yes, I am aware of the spec. However test on dgc-testdata denied samples with 0 fraction digits. Tests might be wrong.

It’s not the first time they are wrong. I’ll bring it up with them.

7 juni 2021 kl. 21:03 skrev Jože Mlakar @.***>:

Yes, I am aware of the spec. However test on dgc-testdata denied samples with 0 fraction digits. Tests might be wrong.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.


Set line-height explicitly in #_vit

Pages that have the line-height set can cause the tool have display issues.
For example, if a page has line-height: 1.5; set on its body, the message about mail-in ballots will look like this:

Notice that the "Continue" button is mostly outside the containing div.
But by setting the line-height on #_vit, we see:

This is currently causing problems for CO voters.
Reproducible in IE on the VIP website: http://votinginfoproject.org/projects/vip-voting-information-tool/

Great -- thank you! I will stage this and verify.

Hi @tie-rack -- this is live now. I'm seeing the line-height at 1 irrespective of the containing elements line-height:

@alexkonrad Awesome. Thank you!


Twitch Channel Feed Issue - Not posting seemingly when announced from Dashboard.

8:46 PM] santa2452: Just an update on the intermittent issue with my channel feed,  I posted an update through the twitch app and it seemed to be announced, so far the only time I notice it not being announced was when I did it through the dashboard. I may be able to test that later tonight before I go live.

From santa2452

I dont have a github account, but I just tested the dashboard theory, here is a picture (if it will help). C for channel update, D for dashboard, App for the twitch app.


Add installation instructions for RHEL 7 and 8

This hopefully fixes #34 and #37 for regular end users of non-latest RHEL version.

Awesome @robert-scheck! Do you need @jluthman to test it out or can I merge directly? I have no way to test it ATM.
Thanks a lot

While I did some testing of the installation steps to ensure latest ipcalc, I didn't fully test asn itself. So cross-testing is indeed appreciated.

Based on https://github.com/nitefood/asn/issues/37#issuecomment-1310441161 it should be safe to merge this.


HBASE-26044 Add CompactionServer Web UI

The web UI of compaction server:

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  4s
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.

_ HBASE-25714 Compile Tests _

+1 :green_heart:
mvninstall
4m 19s
HBASE-25714 passed

+1 :green_heart:
compile
3m 24s
HBASE-25714 passed

+1 :green_heart:
checkstyle
1m 14s
HBASE-25714 passed

+1 :green_heart:
spotbugs
2m 16s
HBASE-25714 passed

_ Patch Compile Tests _

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

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

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

-0 :warning:
checkstyle
1m 14s
hbase-server: The patch generated 1 new + 84 unchanged - 0 fixed = 85 total (was 84)

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

+1 :green_heart:
hadoopcheck
19m 53s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

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

_ Other Tests _

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

51m 59s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-25714 / 20b7c8b286

Default Java
AdoptOpenJDK-1.8.0_282-b08

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3694/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 32s
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 _

_ HBASE-25714 Compile Tests _

+1 :green_heart:
mvninstall
4m 33s
HBASE-25714 passed

+1 :green_heart:
compile
1m 13s
HBASE-25714 passed

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

+1 :green_heart:
javadoc
0m 47s
HBASE-25714 passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
javadoc
0m 44s
the patch passed

_ Other Tests _

-1 :x:
unit
146m 33s
hbase-server in the patch failed.

179m 15s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 184480a4d358 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-25714 / 20b7c8b286

Default Java
AdoptOpenJDK-11.0.10+9

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

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ HBASE-25714 Compile Tests _

+1 :green_heart:
mvninstall
3m 57s
HBASE-25714 passed

+1 :green_heart:
compile
1m  1s
HBASE-25714 passed

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

+1 :green_heart:
javadoc
0m 39s
HBASE-25714 passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
javadoc
0m 39s
the patch passed

_ Other Tests _

-1 :x:
unit
149m 47s
hbase-server in the patch failed.

180m  3s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-25714 / 20b7c8b286

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
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.

_ HBASE-25714 Compile Tests _

+1 :green_heart:
mvninstall
4m 36s
HBASE-25714 passed

+1 :green_heart:
compile
3m 56s
HBASE-25714 passed

+1 :green_heart:
checkstyle
1m 28s
HBASE-25714 passed

+1 :green_heart:
spotbugs
2m 30s
HBASE-25714 passed

_ Patch Compile Tests _

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

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

-0 :warning:
javac
3m 42s
hbase-server generated 6 new + 187 unchanged - 6 fixed = 193 total (was 193)

+1 :green_heart:
checkstyle
1m 17s
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.

+1 :green_heart:
hadoopcheck
21m  6s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

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

_ Other Tests _

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

55m 37s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac hadoopcheck xml compile spotbugs hbaseanti checkstyle

uname
Linux 208c3d5deef3 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-25714 / 20b7c8b286

Default Java
AdoptOpenJDK-1.8.0_282-b08

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3694/2/artifact/yetus-general-check/output/diff-compile-javac-hbase-server.txt

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 33s
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 _

_ HBASE-25714 Compile Tests _

+1 :green_heart:
mvninstall
4m 33s
HBASE-25714 passed

+1 :green_heart:
compile
1m  7s
HBASE-25714 passed

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

+1 :green_heart:
javadoc
0m 41s
HBASE-25714 passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
javadoc
0m 47s
the patch passed

_ Other Tests _

-1 :x:
unit
234m 59s
hbase-server in the patch failed.

268m 20s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-25714 / 20b7c8b286

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
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.

_ HBASE-25714 Compile Tests _

+1 :green_heart:
mvninstall
5m 30s
HBASE-25714 passed

+1 :green_heart:
compile
3m 42s
HBASE-25714 passed

+1 :green_heart:
checkstyle
1m 25s
HBASE-25714 passed

+1 :green_heart:
spotbugs
2m 28s
HBASE-25714 passed

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
checkstyle
1m 17s
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.

+1 :green_heart:
hadoopcheck
23m  9s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

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

_ Other Tests _

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

61m  3s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac hadoopcheck xml compile spotbugs hbaseanti checkstyle

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-25714 / 20b7c8b286

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ HBASE-25714 Compile Tests _

+1 :green_heart:
mvninstall
5m 14s
HBASE-25714 passed

+1 :green_heart:
compile
1m 31s
HBASE-25714 passed

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

+1 :green_heart:
javadoc
0m 43s
HBASE-25714 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

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

175m 14s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-25714 / 20b7c8b286

Default Java
AdoptOpenJDK-11.0.10+9

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  8s
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 _

_ HBASE-25714 Compile Tests _

+1 :green_heart:
mvninstall
4m 19s
HBASE-25714 passed

+1 :green_heart:
compile
1m  5s
HBASE-25714 passed

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

+1 :green_heart:
javadoc
0m 40s
HBASE-25714 passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
javadoc
0m 40s
the patch passed

_ Other Tests _

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

257m 58s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux a5331c6baf85 4.15.0-143-generic #147-Ubuntu SMP Wed Apr 14 16:10:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-25714 / 20b7c8b286

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  9s
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.

_ HBASE-25714 Compile Tests _

+1 :green_heart:
mvninstall
4m 13s
HBASE-25714 passed

+1 :green_heart:
compile
3m 20s
HBASE-25714 passed

+1 :green_heart:
checkstyle
1m 13s
HBASE-25714 passed

+1 :green_heart:
spotbugs
2m 14s
HBASE-25714 passed

_ Patch Compile Tests _

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

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

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

-0 :warning:
checkstyle
1m 12s
hbase-server: The patch generated 1 new + 84 unchanged - 0 fixed = 85 total (was 84)

+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.

+1 :green_heart:
hadoopcheck
19m 52s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

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

_ Other Tests _

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

51m 24s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac hadoopcheck xml compile spotbugs hbaseanti checkstyle

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-25714 / 20b7c8b286

Default Java
AdoptOpenJDK-1.8.0_282-b08

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3694/4/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 30s
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 _

_ HBASE-25714 Compile Tests _

+1 :green_heart:
mvninstall
4m 14s
HBASE-25714 passed

+1 :green_heart:
compile
1m 13s
HBASE-25714 passed

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

+1 :green_heart:
javadoc
0m 40s
HBASE-25714 passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
javadoc
0m 40s
the patch passed

_ Other Tests _

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

170m 55s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-25714 / 20b7c8b286

Default Java
AdoptOpenJDK-11.0.10+9

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  9s
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 _

_ HBASE-25714 Compile Tests _

+1 :green_heart:
mvninstall
4m 42s
HBASE-25714 passed

+1 :green_heart:
compile
1m 11s
HBASE-25714 passed

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

+1 :green_heart:
javadoc
0m 43s
HBASE-25714 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

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

276m 49s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-25714 / 20b7c8b286

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.


Generators should list edited files in addition to created files.

Currently, when running ng generate, we list the files being created.
We never list the files we edit though. This can happen when doing codegen, mostly auto-adding imports to NgModules.
Followup to https://github.com/angular/angular-cli/issues/2299#issuecomment-267849706
/cc @Brocco

I think this is a great idea!


chore(docs): docs and change log updated

Description

Change log updated
Docs updated

Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

Please take a look at this TRG and adjust your images accordingly.

@sachinargade123  please review

Looks good, but I still have 2 remarks to consider:

The documentation contains ArgoCD description which in my opinion does not make much sense in open source as we use ArgoCD in specific environments only.
You could reference the move from png to svc in the PR description/changelog

@almadigabor Argocd reference removed from documents.

merge before #65


The newest version will appear some tmp file when edit files.

I think it is not a good user experience. Blink files will move our attention. But the old version don't has this problem.

Hello,
Note: We now put the required temporary files in the project directory to help racer spot the projects "Cargo.toml" file so that it can help you complete even with your dependencies.
(We soon will even put those temp files in the same directory where your current edited file is).
That's to explain why we changed and dont put those files in the system temp folder.
Now about your problem:
Firstly, it's strange you have multiple temp files, they should disappear once the call to racer is completed.
Secondly, we shaped them as ".XXXXX" because the ".*" is ignored by default by Atom.
Check your Atom Settings:

Open Settings > Packages
Search the core package called tree-view, click Settings
Check the box called Hide Ignored Names

You can control what is ignored in the main Atom settings top panel.
That, at least, should remove the flickers due to those temp files being hastily created and destroyed as racer is called.

Thx. It isn't appear temp file When I check the box called Hide Ignored Names. :smile:
I think should write this tips to readme file. Perhaps you can add this check box to atom-racer.

I'll certainly add that to the readme soon.
And about adding a settings to toggle ignore on tree-view, I'm kinda reluctant to change a settings owned by another package.
Glad it fixed your problem anyway :)

Any chance you will allow to set tmp directory via configuration? or even avoid tmp files in the future? sounds like it's pointless hdd/ssd rewrite operations

You could.. also store this temp folder in some user ~/.blbla hidden directory. So the Atom project will not flicker anymore since the default installation of both racer + atom gives unwanted this behaviour.


Add possibility to define custom css template

I'm missing this in the documentation, so I'm using the HTML example for rendering custom Scss files, which is, well, bad. Is there, or could there be a way to define a path to an example sprite.(less|sass|scss|css|styl).mustache and save that to a sprite.(less|sass|scss|css|styl)?

Excuse me, wrong repo.


Memory leaks

http://prntscr.com/ao2w98
This repo has some memory leaks it seems. They weren't anything big in my project to care much about but some others might have problems. Its worth taking a look. I'm using Instruments in this ss

Hey, thank you for bringing this to my attention. Can you narrow down the memory leak to a test case? I can't think of a legitimate reason a leak could happen in the subscript setter…
Maybe it's a Swift bug, and when you pass an array to the setter (which gets converted to NSArray), a leak happens there…
Have you tested on Xcode 7.3?

Yes this is tested on 7.3 only. I'll narrow it down to a test case the next time I'm debugging memory bugs

Maybe it is related to this swift bug?

me too!

Have you seen the issue since then @goktugyil?

Here are some screenshots I took:
http://prnt.sc/elfcyb
http://prnt.sc/elfd7d
http://prnt.sc/elfdhy
http://prnt.sc/elfk33
There seems to be something wrong while writing. I'm guessing this probably happens to everyone, because I only use the standard features of the library.

That's so strange. Why would there be array appends? SwiftyUserDefaults doesn't maintain any internal array state… are you doing any setting of arrays? Perhaps there's something wonky going on during casting when you do that?

I think those might be steps before. I'm not sure on how to read this data.
I have a lot of stuff stored in arrays.
Example:
struct DBSlot1Keys {

     static let playerRecipeIds = DefaultsKey<[String]>("playerRecipeIds")
}

let recipeIds = Defaults[DBSlot1Keys.playerRecipeIds] //load
Defaults[DBSlot1Keys.playerRecipeIds] = recipeIdArray //save

@radex If a fix to this issue is merged, can we close this issue?

@kaunteya yeah good call. If any new memory leaks happen in the future, let’s open a new thread for that.


Check table version before calling UEFI 2.0+ functions

The create_event_ex function (in boot services) and query_variable_info (in runtime services) were added to their respective tables in UEFI 2.0. In earlier versions these functions can't be called, so check the table revision before using these function pointers.

What platform is this relevant for? EFI 1.10 (the last EFI) only supports ia32 and ia64. ia64 is not supported by Rust or LLVM, and I don't know of a single 32-bit x86 device that uses EFI 1.10 or older. Also the crate is called uefi and not efi, so I'd assume requiring UEFI is reasonable.

What platform is this relevant for? EFI 1.10 (the last EFI) only supports ia32 and ia64. ia64 is not supported by Rust or LLVM, and I don't know of a single 32-bit x86 device that uses EFI 1.10 or older. Also the crate is called uefi and not efi, so I'd assume requiring UEFI is reasonable.

Unfortunately some x86_64 machines use the ia32 mode of UEFI (for example some Intel Compute Sticks). The specific machines I had in mind with this change though are old Apple machines, which were stuck on EFI 1.10 for a long time. See https://github.com/torvalds/linux/commit/f5390cd0b43c2e54c7cf5506c7da4a37c5cef746 for example.

Unfortunately some x86_64 machines use the ia32 mode of UEFI (for example some Intel Compute Sticks).

I knew about those, but they're all UEFI already, not stuck on EFI

The specific machines I had in mind with this change though are old Apple machines, which were stuck on EFI 1.10 for a long time. See torvalds/linux@f5390cd for example.

I see. The mentioned Linux patch disables using 2.0 features on Apple hardware even when they're reported as supported. Should this be replicated here too then? As from what I understand without this the single platform this patch targets still won't work.

Oops, I somehow edited your comment instead of replying, sorry about that. I believe I have restored your comment to its original form :)

The mentioned Linux patch disables using 2.0 features on Apple hardware even when they're reported as supported. Should this be replicated here too then? As from what I understand without this the single platform this patch targets still won't work.

For older Macs that report 1.10 this change will work fine, but you are right that for the MacBookPro16,1 described here it will still be broken. I don't think we have a way to check for system vendor here currently though.


WebServer: static content module

Follow up from #1217

Move the static content support to a separate module and Implement directory listing (maps to a feature as well)

+1


Return templates when topic doesn't have a campaign

What's this PR do?
Modifies parsing the response of a GET /topics/id request to return a templates property, even if the topic doesn't have a campaign reference set.

Adds check for when the campaignId field on a campaign entry doesn't exist in Phoenix, which is currently happening on GET /v1/topics/5fpmfk4ETe4ss6qogEcGSi

How should this be reviewed?

👀
Set env vars to Contentful Preview API and verify GET v1/topics and GET /v1/topics/5fpmfk4ETe4ss6qogEcGSi return success responses

Any background context you want to provide?
Preview API is fun because Contentful creates an ID as soon as an editor opens the form to create a new entry. I ran into this error when working on https://github.com/DoSomething/gambit-conversations/pull/328 per continuing https://github.com/DoSomething/gambit-conversations/pull/336
Checklist

[x] Tested on staging.

You probably already noticed, but wanted to flag. Since the campaign doesn't exist. The rendered property contains the same raw mustache templates.
        "startPhotoPost": {
          "raw": "Thanks for signing up for {{title}}! Text {{cmd_reportback}} to submit a post.",
          "override": false,
          "rendered": "Thanks for signing up for {{title}}! Text START to submit a post."
        },

Yup - that's intentional for now. Users shouldn't receive any messaging from a topic without a campaign -- as we save a campaign to their conversation, and lookup the topic to use via GET /campaigns/:id -- which has a topics array property of nested topics for the given campaign id.


MD5, SHA-1, or SHA-256 hashes

There is no way to validate that the downloaded MSI is legitimate. The document should include an MD5, SHA-1, or SHA-256 hash.
Reference: https://docs.microsoft.com/en-us/MicrosoftTeams/msi-deployment

Hi. Thanks for the feedback. I'm investigating this and trying to find a PM that I can assign this issue. Thanks, Tony

I've assigned two PMs from the product group to lend you a hand. We appreciate the feedback. If there are addition/corrections/suggestions to the docs, please edit the topic by clicking Edit (on the right side of the topic) or use VsCode/GtiHub desktop. Let me know how I can help further.

This is resolved and newer downloads should include the signatures on the msi. Thanks for the report.

Should we included a note in the topic?


Node Install Error

Hello,
I have installed the WebSocket Node in the Node.js folder as a module, but when I try to run a server script it can't find the module.
C:\Users...\Downloads\WebSocket-Node-master\WebSocket-Node-master>node ws_server.js
module.js:442
throw err;
^
Error: Cannot find module 'C:Program Files
odejs
ode_moduleswebsocket'
at Function.Module._resolveFilename (module.js:440:15)
at Function.Module._load (module.js:388:25)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Object. (C:\Users...\Downloads\WebSocket-Node-master\WebSocket-Node-master\ws_server.js:2:23)
at Module._compile (module.js:541:32)
at Object.Module._extensions..js (module.js:550:10)
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
So I am trying to installe the websocketnode in the folder, where I am trying to run the script but I am getting the following error:
C:\Users...\Downloads\WebSocket-Node-master\WebSocket-Node-master>npm install websocket
npm ERR! Windows_NT 10.0.10240
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "websocket"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3
npm ERR! code ENOSELF
npm ERR! Refusing to install websocket as a dependency of itself
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     https://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users...\Downloads\WebSocket-Node-master\WebSocket-Node-master\npm-debug.log
Can someone help?
Thanks

I have installed the WebSocket Node in the Node.js folder as a module

Why?
Have you seen the error you get?:

"Refusing to install websocket as a dependency of itself"

Please, learn how Node.js and npm works.


[QUESTION]

Please describe.
When I run a robot test case that uses Firefox geckodriver, inside a container, from the vstudio code terminal everything runs fine.
When trying to use robotcode GUI, clicking on the "play" button of the same test case, we get an error as Firefox won't load any webpage. (that is on the same environment, same python version, same container)
For running cases inside a container we use studio code with dev-containers plugin, along with robotcode.
The question is what is different running from terminal (robot command) vs running using the robotcode GUI in studio code that could cause this error?
Some additional info,
The error I see in geckodriver.log (Firefox log) is the following:
DevTools listening on ws://<IP_ADDRESS>:35795/devtools/browser/341ea008-762b-4602-a652-7cf251fb74f4
1700221454475	Marionette	INFO	Stopped listening on port 35951
WARNING: A blocker encountered an error while we were waiting.
          Blocker:  Waiting for ping task
          Phase: TelemetryController: Waiting for pending ping activity
          State: (none)
WARNING: Error: Phase "profile-before-change" is finished, it is too late to register completion condition "OS.File: flush I/O queued before profileBeforeChange"
WARNING: addBlocker@resource://gre/modules/AsyncShutdown.sys.mjs:727:15
addBlocker@resource://gre/modules/AsyncShutdown.sys.mjs:523:26
addBlocker@resource://gre/modules/AsyncShutdown.sys.mjs:458:15
setupShutdown@resource://gre/modules/osfile/osfile_async_front.jsm:1548:28
@resource://gre/modules/osfile/osfile_async_front.jsm:1568:16
@resource://gre/modules/osfile.jsm:12:30
@resource://gre/modules/TelemetryStorage.sys.mjs:10:28
_checkPendingPings@resource://gre/modules/TelemetrySend.sys.mjs:863:17
setup@resource://gre/modules/TelemetrySend.sys.mjs:803:18
setup@resource://gre/modules/TelemetrySend.sys.mjs:241:30
setupTelemetry/this._delayedInitTask<@resource://gre/modules/TelemetryControllerParent.sys.mjs:829:36
observe@resource://gre/modules/AsyncShutdown.sys.mjs:576:16

It closely resembles this issue refered in SeleniumHQ github:
https://github.com/SeleniumHQ/selenium/issues/11795
This only occurs when we use robotcode to run via studio code. It does not happen from a terminal within the container. I was hoping maybe there is an idea of what might be different in execution that may be causing this.
Desktop (please complete the following information):

VS Code Version: 1.84.2
RobotCode Version 0.63.0
OS: Windows or Linux does not seem to change things
Python Version 3.10.x
RobotFramework Version 6.1.1
Additional tools: robocop

Thanks

Here is the translation to English:
Unfortunately, I can't say exactly what could be causing this.
What error message does the test abort with when you start it from VSCode? What error is in the Robot log.html?
And how do you start the test run in the terminal? Maybe something needs to be configured in VSCode to make the same call. Or have you already done that?

ok, because I have not received any feedback, I assume that the error has been fixed and close this issue.


Nothing in the "Main Window" after "Send to ExtendedMacro"

burpsuite 1.7.26 with jdk 1.8.0_102
Extender -> Extensions -> ExtendedMacro can be Loaded, but does not work:

Select one item from HTTP History, and then right click choose "Send to ExtendedMacro",
the "Extended Macro" tab is changed to orange color, but no message was there, nothing,  empty. i.e. the item was not sent to "Main Window".

I tried another version of jdk, it's even cannot be loaded.
2. burpsuite 1.7.26 with jdk_1.7.0_17
Extender -> Extensions -> ExtendedMacro,  can not be loaded with error message:
java.lang.UnsupportedClassVersionError: burp/BurpExtender : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:266)
at burp.sue.a(Unknown Source)
at burp.sue.(Unknown Source)
at burp.mn.a(Unknown Source)
at burp.ooh.run(Unknown Source)
at java.lang.Thread.run(Thread.java:722)
The extension could not be loaded because it requires a later version of Java. To use this extension you will need to start Burp with the required or later Java version.

Hi, the problem is, that you are running burpsuite (probably bundle) with Java 1.7.0_17 what is version 51, with Java 1.8.0 (version 52) it should work,  i am using 1.8.0_162 amd it works.
Could you please send me stacktrace from java 1.8 run?

Sorry, I dont know how to extract "stacktrace" information, but I tried jdk 1.8.0_162, the problem still exist.
OS:   Windows 7 64 bit
JDK:  java -version
java version "1.8.0_162"
Java(TM) SE Runtime Environment (build 1.8.0_162-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode)
BurpSuite v1.7.26  can be downloaded  from https://pan.baidu.com/s/1jJv7eF8 password: l3p2

oh man :(...you should by one license, its quite cheap ;) https://portswigger.net/burp
It works with java 1.8 without problems.


Hive Views are not working

I running trino with Ranger. But, when I query Views created in Athena, I get access denied. How can I solve this?
Access Denied: View owner does not have sufficient privileges: Cannot access catalog

If I delete view and create it again from Trino, it works. What could be the reason behind it, any idea?

Hey, @bhargav2427 I haven't tried Trino and Ranger with the recent version but I can try to help. The error message is your biggest clue. It looks like the root user is trying to login. Can you confirm if the user name configured on the Trino service is available and can authenticate to the Trino instance? Adding a debugging level to logs also helps.


Piazzetta URL and Customer Code

Hi,
Just for information, here are elementary connection details for Piazzetta brand (app name "MyPiazzetta" - they also distribute products under "Superior" brand, with a corresponding "MySuperior" app, I don't know if same hostname/code would work):

URL: https://piazzetta.agua-iot.com
Customer Code: 458632

The MyPiazzetta app is actually not talking to piazzetta.agua-iot.com directly, but rather to what seems to be a Web proxy service (https://piazzetta.iot.web2app.it/api/bridge/endpoint); most certainly so they can collect usage statistics and so.
The WiFi module is however talking to piazzetta.agua-iot.com directly.
Regards.

Hi @securechicken !
Thanks for the information, I've updated the README 👍


The terminal process terminated with exit code:<PHONE_NUMBER>

Issue Type: Bug
Unclear how I ended up in this state (VSCode had been open for a day or two), but closing exiting and re-opening VSCode hasn't resolved the issue: Each time I try to open a new terminal it quickly closes. It flashes a message stating "An install, uninstall, or upgrade is in progress for this distribution."
I noticed there was an update available which I installed, but nothing has changed.
In the dev tools, the console displays a different error message:
  ERR Cannot resize a pty that has already exited: Error: Cannot resize a pty that has already exited
    at WindowsPtyAgent.resize (c:\Program Files\Microsoft VS Code\resources\app\node_modules.asar\node-pty\lib\windowsPtyAgent.js:132:23)
    at WindowsTerminal.<anonymous> (c:\Program Files\Microsoft VS Code\resources\app\node_modules.asar\node-pty\lib\windowsTerminal.js:130:26)
    at WindowsTerminal._defer (c:\Program Files\Microsoft VS Code\resources\app\node_modules.asar\node-pty\lib\windowsTerminal.js:155:24)
    at WindowsTerminal.resize (c:\Program Files\Microsoft VS Code\resources\app\node_modules.asar\node-pty\lib\windowsTerminal.js:129:14)
    at S.resize (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3110:500)
    at E.setDimensions (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3984:437)
    at e._resize (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:4012:108)

VS Code version: Code 1.43.1 (fe22a9645b44368865c0ba92e2fb881ff1afce94, 2020-03-18T07:01:20.184Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 x 3600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.92GB (7.71GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (11)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.1.1

prettier-vscode
esb
3.20.0

vscode-svelte-snippets
fiv
0.3.0

svelte-vscode
Jam
0.9.3

vscode-edit-csv
jan
0.2.6

rainbow-csv
mec
1.6.0

remote-wsl
ms-
0.42.4

vetur
oct
0.24.0

code-settings-sync
Sha
3.4.3

prettier-vscode
Sim
1.1.22

vscode-icons
vsc
10.0.0

Please try these:

Disable legacy console mode in cmd.exe/conhost's properties, or
Try tweaking the terminal.integrated.windowsEnableConpty setting

Thanks @Tyriar its looks like this isn't actually a bug related to VSCode but WSL, which I have as my terminal.
Switching the terminal cmd to cmd.exe has the terminal working correctly.

I found this to be helpful, https://code.visualstudio.com/docs/editor/integrated-terminal#_configuration

The terminal process terminated with exit code:<PHONE_NUMBER>   :please suggest something to solve this error.


Update README.md

Summary
Fixes #

Occurred changes and/or fixed issues

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

@MridulSharma03 Please can you fill out the issue template

superseded by https://github.com/rancher/dashboard/pull/10007


Breaks in IE8

In the extend implementation in utils.js,  the function checks to see if Object.defineProperty exists and then uses it if it is. This is not IE8-compatible, though, because while IE8 includes an implementation of defineProperty, it only works on DOM objects.
if (Object.getOwnPropertyDescriptor && Object.defineProperty) {
    var propertyDescriptor = Object.getOwnPropertyDescriptor(source, prop);
    Object.defineProperty(obj, prop, propertyDescriptor);
} else {
    obj[prop] = source[prop];
}

I know that the goal was to avoid importing lodash/underscore, but maybe importing only _.assign would be an acceptable solution? https://github.com/lodash/lodash/blob/3.2.0-npm-packages/lodash.assign/index.js

Same in Safari.

@ce07c3 which version of Safari?

Safari 9. It should work, though, but I am getting an error specifically for the defineProperty call. However, not for every instance of the obj argument.

I'm planning to use Object.assign instead, that way you only need to use a ES6 shim that is IE8 compatible.

:+1:

@spoike Using Object.assign() this test would fail.  Rather than copying the getter descriptor, the getter is accessed and its value is copied.

@devinivy: Well, that's a weird test and must have missed it when I accepted the associated PR... Reflux stores (and actions) aren't supposed to have getters and setters, the data should be passed through the event instead.
Anyone have any issues with this functionality removed? I will probably have to bump up the minor version number for this if there is.

Ah, I haven't seen the associated PR for this.  Maybe this issue was worked-around in some way?

Not a bug, just a really old browser.


chore(dependencies): update and bind dependencies to newest version

This way no dependency that introduces a breaking change with a minor or patch will break Alva.
Greenkeeper will remind us to update these dependencies and will also automatically test them against  build-lsg and build.
I would be interested about other opinions on this topic.

LGTM, but we should consider using a lockfile for this and check if Greenkeeper supports those or switch to renovateapp if it doesn't.

Greenkeeper supports lockfiles. What benefits would the lockfile have over the current approach?
(Currently the package-lock.json is also ignored. A few versions ago windows and mac generated different package-lock.jsons every time)

I will also look at renovateapp. Looks very interesting #239

Lockfiles pin dependencies for the entire tree instead of controlling only the first layer


track open handles and auto close when calling CloseFile(fileId)

related to Read Attributes #201

Can I suggest you make handles disposable as I've done in my limited H5 implementation?
https://github.com/PhilPJL/HDF5Test.

@PhilPJL Interesting!
thanks for sharing


Errors with .txt & .xlsx files.

System Info
I pulled random info online for the .xlsx.
I used state of the union for the .txt
.docx works without error
.pdf works without error
All data was coded using documentation here:
https://python.langchain.com/en/latest/modules/indexes/document_loaders.html
versions:
python-3.10.11-amd64
langchain                   0.0.192
chromadb                    0.3.23
I just need to know how to install a version that works by the looks of this error.
.xlsx error:
Traceback (most recent call last):
  File "C:\*\buildchroma.py", line 93, in <module>
    CreateVectorExcelFiles( x );
  File "C:\*\buildchroma.py", line 77, in CreateVectorExcelFiles
    loader = UnstructuredExcelLoader(doc_path+x, mode="elements")
  File "C:\Users\*\AppData\Local\Programs\Python\Python310\lib\site-packages\langchain\document_loaders\excel.py", line 16, in __init__
    validate_unstructured_version(min_unstructured_version="0.6.7")
  File "C:\Users\*\AppData\Local\Programs\Python\Python310\lib\site-packages\langchain\document_loaders\unstructured.py", line 31, in validate_unstructured_version
    raise ValueError(
ValueError: unstructured>=0.6.7 is required in this loader.
PS C:\*> pip install UnstructuredExcelLoader
ERROR: Could not find a version that satisfies the requirement UnstructuredExcelLoader (from versions: none)
ERROR: No matching distribution found for UnstructuredExcelLoader

Text files should work since it is an example from the start. I copy/pasted the state of union txt files from right here in github.
.txt error:
Traceback (most recent call last):
  File "C:\Users\*\AppData\Local\Programs\Python\Python310\lib\site-packages\langchain\document_loaders\text.py", line 41, in load
    text = f.read()
  File "C:\Users\*\AppData\Local\Programs\Python\Python310\lib\encodings\cp1252.py", line 23, in decode
    return codecs.charmap_decode(input,self.errors,decoding_table)[0]
UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 1225: character maps to <undefined>

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "C:\*\buildchroma.py", line 87, in <module>
    CreateVectorTxtFiles( x );
  File "C:\*\buildchroma.py", line 40, in CreateVectorTxtFiles
    txtdocuments = txtloader.load()
  File "C:\Users\*\AppData\Local\Programs\Python\Python310\lib\site-packages\langchain\document_loaders\text.py", line 54, in load
    raise RuntimeError(f"Error loading {self.file_path}") from e
RuntimeError: Error loading C:\*\source_documents\state_of_the_union.txt

Who can help?
No response
Information

[X] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[ ] LLMs/Chat Models
[X] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[X] Document Loaders
[X] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
import os
from langchain import OpenAI

from langchain.document_loaders import UnstructuredWordDocumentLoader
from langchain.document_loaders import UnstructuredExcelLoader
from langchain.document_loaders import PyPDFLoader
from langchain.embeddings.openai import OpenAIEmbeddings
from langchain.text_splitter import CharacterTextSplitter
from langchain.vectorstores import Chroma
from langchain.document_loaders import TextLoader

persist_directory = 'db'
embeddings = OpenAIEmbeddings()

Excel:
	loader = UnstructuredExcelLoader(filepath, mode="elements")
	docs = loader.load()
	vectordb = Chroma.from_documents(documents=docs, embedding=embeddings, persist_directory=persist_directory)
	vectordb.persist()
	vectordb = None

Txt:
	txtloader = TextLoader(filepath)
	txtdocuments = txtloader.load()
	text_splitter = CharacterTextSplitter(chunk_size=1000, chunk_overlap=0)
	docs = text_splitter.split_documents(txtdocuments)
	vectordb = Chroma.from_documents(documents=docs, embedding=embeddings, persist_directory=persist_directory)
	vectordb.persist()
	vectordb = None

Expected behavior
Just needs to load and create vectorstores for .xlsx and .txt files without errors.

What's the encoding of the text file? If you don't specify the encoding then the constructor would use the system encoding which may be different than the one in the text file.
TextLoader(file_path: str, encoding: Optional[str] = None, autodetect_encoding: bool = False)
You could try to set autodetect_encoding to True or define the encoding parameter to see if that solves the issue.

i removed state of the union and it loaded the other txt files so it must be something to do with copy/pasting right from github which is a little weird. this issue is technically resolved now.


TTL for columns and tables

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
For changelog. Remove if this is non-significant change.
Category (leave one):

New Feature

Short description (up to few sentences):
Implements TTL for columns and tables.
Detailed description (optional):
TTL is set while creating MergeTree-family table as expression: DateTime column + interval:
CREATE TABLE t (d DateTime, a Int TTL d + INTERVAL 1 DAY) engine = MergeTree ...
Then merges are assigned considering TTLs and expired values are removed at needed time while merge executing.

Abort here https://pastebin.com/TZTyMCcP.

TODO
[] save min-max TTL for specific columns and table

Stress test failure doesn't seem like known error.

@CurtizJ Your own tests failed.


Open source build instructions unclear

I intended to add details to the README regarding the runtime tests and building/testing with NPM/yarn (i.e., via yarn build and yarn test) when I realized I cannot get the Maven build to work anymore, now that pom.xml is no longer in the root directory. Despite my best efforts to repair this (moving POM to pom.xml, adding project.source version to silence "source version must be > 8" errors, etc.) so that mvn -DskipTests and so on execute as expected, I cannot the project to compile successfully.
Any help from someone more experienced with Maven would be greatly appreciated. I will send my README PR as soon as this is working again.

I believe we only intend to support building via Bazel instead of Maven now: https://github.com/google/closure-compiler#using-bazel. (@nreid260 would know better than me)
Most of the development on Closure Compiler is done in Google's internal repo via the internal version of Bazel. Most of the Closure Compiler devs are more familiar with Bazel / its internal version, so switching from Bazel to Maven reduced a lot of friction for us & made the internal -> external sync easier, with the tradeoff that non-Google contributors will probably be more familiar with Maven.
Do the Bazel build instructions work for you?

Thank you so much for clarifying Laura, I will update the package.json scripts in my PR and adjust it to build with Bazel. I forgot that this change was made a few releases ago.

@nreid260 could you comment on this + close if  appropriate? Thanks

@nreid260 could you comment on this + close if  appropriate? Thanks

@lauraharker I think this should stay open until #3746 is merged - I have a README PR draft to add documentation as well.

@lauraharker I think this should stay open until #3746 is merged - I have a README PR draft to add documentation as well.

I can confirm that we no longer intended to support a Maven build. Bazel is the current build tool. We do however continue to publish Maven compatible artifacts to Sontaype.

I can confirm that we no longer intended to support a Maven build. Bazel is the current build tool. We do however continue to publish Maven compatible artifacts to Sontaype.

Understood. This would be closed by updating the runtime tests to use Bazel with #3746.

Understood. This would be closed by updating the runtime tests to use Bazel with #3746.


Bring back EOL Python support for 0.5.1 release

Add missing settings for Python 12 support

Thank you for your effort on this PR. However, I noticed a few confusing places:

The title of this PR mentions bringing back versions 2.7, 3.6, and 3.7, yet the description references the addition of 3.12. Could you clarify this discrepancy?
The initial PR #40 seemed to take a reasonable step by discontinuing support for EOL releases. Could you explain the rationale behind reintroducing these versions in the current PR?

It would be beneficial for followers of this project if all PRs were a bit clearer in their intentions so that the community understand and support the project's direction more effectively.

Thank you for your effort on this PR. However, I noticed a few confusing places:

The title of this PR mentions bringing back versions 2.7, 3.6, and 3.7, yet the description references the addition of 3.12. Could you clarify this discrepancy?

It's in the second line of the PR/commit message.

The initial PR Remove support for EOL Python 2 #40 seemed to take a reasonable step by discontinuing support for EOL releases. Could you explain the rationale behind reintroducing these versions in the current PR?

As mentioned in the title, it's for 0.5.1 release.
We'll EOL Python 2 in the next major version (0.6.0)

@droideck thanks for sharing the information. Now it's clear.


SurrealDB as a database

Feature Description
Add SurrealDB as a storage layer for Gitea. Indirectly, this will allow for the usage of many storage engines underneath from FoundationDB, TiKV to RocksDB, and eventually SurrealKV.
With a massive growth in installations and adoptions, Surreal is a viable option for Gitea and its wider community.
Screenshots
No response

It seems no Golang standard driver support from SurrealDB. Since Gitea depends on xorm, it's impossible to use a database that xorm doesn't support.

I don't think it's a problem since we also support MSSQL which is the close source. We just need to check the driver's license.

Is it really feasible? SurrealDB uses a different syntax than SQL.

Is it really feasible? SurrealDB uses a different syntax than SQL.

I don't think SurrealDB uses standard SQL or works with Gitea SQL statements. If it is not feasible, I think this proposal could be closed. Correct me if I am wrong.

Is it really feasible? SurrealDB uses a different syntax than SQL.

I don't think SurrealDB uses standard SQL or works with Gitea SQL statements. If it is not feasible, I think this proposal could be closed. Correct me if I am wrong.

Unfortunately, surreal does not use standard SQL, as there is far too many features they provide than what standard SQL syntax allows for intuitively and also doesn't work with Gitea SQL statements at this time.

I think we have to refuse this proposal at this time. Maybe we can reopen once upstream supports it.

SurrealDB developer here. I can confirm we aren't a standard dialect of SQL and only support SurrealQL which has a lot of differences. So I think this can be closed. Thank you for the interest and efforts though! We may try to open it in the future again if we get true SQL support.


Unlaunch doesn't autolaunch SuperCardDSTwo plus

Tried to autoboot/launch supercard ds two plus from unlaunch but the cart appears with this name: "ooooooooooooooooo" and when selected to autoboot, it won't boot, just a blank screen.

Not an issue with the guide. Please mention this to nocash on the NESDEV forums


Add benchmarks

From @adriancole on November 17, 2015 3:21
Some aspects of code need to be benchmarked as they will be run a lot.
Here's some ideas... feel free to contribute!
For each scenario, use traces of 1-5 depth and 10-200 width, where spans range from local to remote w/up to 2KB annotation sizes.
Library Microbenchmarks:

thrift and json codec
time skew adjustment

Integration Benchmarks (ex server running against each spanstore impl)

accepts/second for 1, 10, 100 length spans in json vs thrift
at rest size of 10K - 1M traces:
service/span name query latency
duration query latency
dependency query latency

Copied from original issue: openzipkin/zipkin-java#45

#55 is a start, benchmarking the sampling algo

serialization benchmarks added https://github.com/openzipkin/zipkin-java/pull/173

related work:
zipkin-reporter has a micro(ish)benchmark which tests the throughput of senders like Kafka (not directly to a zipkin server, but could be rejigged to)
Ex. https://github.com/openzipkin/zipkin-reporter-java/blob/master/benchmarks/src/main/java/zipkin/reporter/HttpSenderBenchmarks.java
The sender itself is used by many instrumentation projects (like brave, spring etc), but it was also made to facilitate benchmarking a real setup. The idea was to use something like jbender and hook it up to a reporter and a generator. It would need a plugin to monitor backup etc.
There was also an idea to use spigo to simulate loads. This stopped working at some point and also needs help to route through our go library as opposed to creating dump files.
Another idea was to use storage-specific benchmarks, such as Rally for elasticsearch #1354 or stress tool for cassandra. While not flow tests, these could help isolate storage performance concerns (like indexing)
We've also had a number of ad-hoc tests where people make python scripts to test kafka. Here's an example of such a script: https://github.com/openzipkin/zipkin/issues/1141#issuecomment-228514983
Another way you could test is shoving traffic through an existing system as a black box. For example, you could look at polyglot-zipkin and drive traffic through that (via grinder or similar) and watch side-effects on the storage system or collector metrics of zipkin

used a quick and dirty wrk benchmark to measure overhead reduction of tomcat -> undertow https://github.com/openzipkin/zipkin/pull/1806

here's a lua file for wrk, though it is a bit crap as it uses the same post every time (and the trace ID gen is janky)
-- crappy trace id generator
local random = math.random
local trace_template ='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
local trace_id = string.gsub(trace_template, '[xy]', function (c)
  local v = random(0, 0xf) or random(8, 0xb)
  return string.format('%x', v)
end)

-- ex luarocks-5.1 install luaposix
local P = require "posix"
local tim = P.gettimeofday()
local timestamp = tim.sec..tim.usec
local timestamp_foo = tim.sec..(tim.usec + 2500)
local timestamp_bar = tim.sec..(tim.usec + 10500)

wrk.method = "POST"
wrk.headers["Content-Type"] = "application/json"
wrk.headers["Origin"] = "http://foobar.com"
wrk.body   = '[{"traceId":"'..trace_id..'","id":"4d1e00c0db9010db","kind":"CLIENT","name":"get","timestamp":'..timestamp..',"duration":207000,"localEndpoint":{"serviceName":"frontend","ipv6":"7::<IP_ADDRESS>"},"remoteEndpoint":{"serviceName":"backend","ipv4":"<IP_ADDRESS>","port":9000},"annotations":[{"timestamp":'..timestamp_foo..',"value":"foo"},{"timestamp":'..timestamp_bar..',"value":"bar"}],"tags":{"http.path":"/api","clnt/finagle.version":"6.45.0"}}]'


Extraneous empty text nodes when formatting .hbs

Formatting htmlbars templates adds extra text nodes at the beginning and end of component elements. e.g.:

  {{text}}

node.childNodes will render: [#text, "test text", #text], whereas {{text}} will render ["test text"].
This is a problem for us, as we're using contenteditable divs and sanitizing nodes is a bit of a pain. The alternative is to keep everything on one line. It'd be nice to have the option to minify/trim the output.

I totally agree but I'm not sure what a good solution is, because we want to capture the semantics of HTML as closely as possible.
For a quick fix, you can write this particular template in a compile-to-handlebars language like http://emblemjs.com/ or http://www.hbars.io/ which has more control over whitespace.

Got it, thanks. One-liner is fine for now.

@skanderm , what was your solution?

@reneelung It's a hack, but I moved any control statements outside of any important elements and kept the contents on one line:
{{#if isCondition}}
  {{text}}
{{else}}
  {{otherText}}
{{/if}}

@skanderm You can also use the whitespace controller feature of Handlebars:

  {{~ text ~}}

is exactly equivalent to
{{text}}


Add external database (MongoDB)

Description
Please include a summary of the changes and the related issue.
Type of change

[ ] 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 not work as expected)
[ ] Documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works

Current dependencies on/for this PR:

develop

PR #47

PR #48

PR #49   👈

PR #50

This stack of pull requests is managed by Graphite.

Merge activity

Nov 7, 11:59 PM: @akotadi started a stack merge that includes this pull request via Graphite.


Can't script ServerlessContainers for CI - always promts users input

Describe the bug
amplify-cli/packages/amplify-cli/sample-headless-scripts/headless_configure_project.sh script not working anymore. It prompts
Do you want to enable container-based deployments? (y/N)
but it used to work 1 month ago.
Amplify CLI Version
4.41.2
To Reproduce
to run the script
Expected behavior
no promts
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):
Ubuntu
Additional context
Attempt like this:
REACTCONFIG="{\ \"SourceDir\":\"src\",\ \"DistributionDir\":\"out\",\ \"BuildCommand\":\"npm run-script build\",\ \"StartCommand\":\"npm run-script start\",\ \"ServerlessContainers\":false\ }"
not working either with the same result

Hi all, I'd like to take this issue up. :)

I'm removing this from bug bash, as I think this needs a few things:

When running amplify configure project, there is a prompt that asks if you want to configure project information, AWS profile settings, or "Advanced: Container-based deployments." As far as I can tell, there is no officially documented way to bypass this question headlessly.
If you select the "Advanced: Container-based deployments" option, there doesn't appear to be a documented way to configure this.
Currently, the ServerlessContainers container setting is stored under frontend configuration, which also feels a bit odd.

Marking as a p3 but we should look at this as a part of the headless refactor for consistency


Team association & customization for Users

Team association currently doesn't have any UI thru the site, it's all done on the admin side. Profiles are also just read-only so far. We can add functionality to the profile page so that Teams might be addable, removeable, renameable, etc. Other info on the User page could also be adjusted - e-mail, name, any other fields that end up being added.

Teams now associable/disassociable in https://github.com/mawilson/survivor_draft/pull/64. Renaming & other User customization yet to be done.

Done in https://github.com/mawilson/survivor_draft/pull/68 & https://github.com/mawilson/survivor_draft/pull/69.


We are not getting Notification into HmsMessageService on onMessageReceived file in Android

I am using your example send_notify_message.js file from HUAWEI Push Kit(NodeJs). I get a success message in NodeJs log.
{
code: '80000000',
msg: 'Success',
requestId: '160213898154027353000507'
}
I can see Notification appears at top of the mobile but somehow we are not able to see into our Android log.
Normally any notification comes it should be handled by HmsMessageService method onMessageReceived. Based on that we further take programmatic action.
But in Huawei Notification does not appear in HmsMessageService. Currently, we are not able to take any action.
We have also tried to send notification via HUAWEI Push Kit from app gallery. Then also it does not appear into HmsMessageService. It only shows on top of mobile but it is useless for us we can not take any programmatic action.

Here is the link to HUAWEI Push Kit from the app gallery
https://www.screencast.com/t/oAfcSIWq5J

I am using your example send_notify_message.js file from HUAWEI Push Kit(NodeJs). I get a success message in NodeJs log.
{
code: '80000000',
msg: 'Success',
requestId: '160213898154027353000507'
}
I can see Notification appears at top of the mobile but somehow we are not able to see into our Android log.
Normally any notification comes it should be handled by HmsMessageService method onMessageReceived. Based on that we further take programmatic action.
But in Huawei Notification does not appear in HmsMessageService. Currently, we are not able to take any action.
We have also tried to send notification via HUAWEI Push Kit from app gallery. Then also it does not appear into HmsMessageService. It only shows on top of mobile but it is useless for us we can not take any programmatic action.

I was working on React Native
In my case, onMessageReceived was triggered only by DataMessages, at least it was I found out while testing this library.
From documentation here

Example of message that worked for me:
const payload = {
     // anything you want here
     test: 'test'
}

const notification = {
      title: 'Condivisione Messaggio',
      body: 'Message Shared',
    };

const message = {
      data: JSON.stringify({ ...notification, payload }), // added also this one for being sure will be passaed to onMessageReceived
      android: {
        collapse_key: -1,
        urgency: 'HIGH',
        ttl: '10000s',
        data: JSON.stringify({ ...notification, payload }), // this one is important
      },
      token: [
        pushChannel,
      ],
    };


Truncated Tweets

Hi, any way to set tweet_mode to extended so I can access non-truncated tweets? Thanks.

has there been any solution to this issue?

As a workaround, and following #34 , you can this:
tso.arguments.update({'tweet_mode':'extended'})

and it will return an object that instead of a text key, has a full_text key, with the full text. I've tested it, and it works.
A PR should be fairly easy to implement, following said #34 .

Hi,
when setting tweet_mode to extended it indeed returns the full text tweets. However, it doesn't work with retweets. I have tried to set "retweet_mode" to "extended" as well, but it doesn't seem to work.
Any hint? Thanks!

I believe that is a limitation from the Twitter API. Retweets do not come with the original tweet's full text. I think, however, that you have an object inside the RT that is the original tweet. And you also get the tweet id of the original tweet, so you could query the original tweet and pass the extended parameter.
But for RTs, yes, you are right. Twitter API returns truncated text. As far as I know. Sorry about that.