[tcp] implement TCP Circular Send Buffer and incorporate it into CLI tool and tests

This pull request is a follow-up to Pull Request #7584. It implements the TCP circular send buffer API proposed in that pull request. It also integrates the circular send buffer into the TCP CLI tool, allowing the expect test for TCP to test its functionality as well. I also ran the code manually on NRF 52840-DK boards, and verified that the achievable TCP goodput both with the circular buffer and without it are about the same, verifying that the circular buffer does not materially reduce TCP goodput.
This completes the circular buffer library for TCP proposed in Pull Request #6491.

Just rebased this onto main.

I just pushed an update fixing the Build / pretty test. A few other tests are failing, but looking at the output for those tests, I don't think it has to do with the code in this pull request...
@jwhui and @abtink, please review the code and, if everything looks OK, feel free to merge it.

@abtink I just pushed an update addressing your comments. I also rebased onto the latest main branch.

@abtink Ah, it looks like I missed some of your original comments --- GitHub collapsed many of them together into a single link that said "15 hidden messages", and I had neglected to click on that to see the full list of comments...

I'll address the rest of your comments tomorrow.

@abtink Ah, it looks like I missed some of your original comments --- GitHub collapsed many of them together into a single > link that said "15 hidden messages", and I had neglected to click on that to see the full list of comments...
I'll address the rest of your comments tomorrow.

No worries. SGTM. Thanks :)

@abtink Thanks again for your comments. I think I've addressed all of them now.


Merge branch 'bugfix' into 'master' - [merged]

Merges cherry-pick-079b71fe -> 0.6
fixed failing online test
Closes #123
See merge request LMSAL_HUB/aia_hub/aiapy!148
(cherry picked from commit 079b71fe04def61f99963a2647a07e1f46d8bf88)
66314faf fixed test and astropy issue
6bed8c8c code review
e3a41ffb undo

approved this merge request

mentioned in commit 8c2613adada07eab45144a48d66a132589d165e2


Pre-project expression histories no longer saved

As described here https://forum.openrefine.org/t/is-the-facet-creation-history-tab-meant-to-be-able-to-show-the-source-projects/1242 ,  the "From" column in the History tab of the custom expression modal always shows as "This project" even when the corresponding expression was created in another project (than the current one).

There are two related bugs here, both introduced by the conflict resolution of a single commit revert in 2018:

Expression history is no longer saved in the local project
Global expression history entries are always displayed as "This project" rather than "Other project"

I've identified the missing pieces and "just" need to pull them together into a PR.


bug/childCount not correct in search query

Describe the bug
When trying to search for a folder inside of an item in the OneDrive api, the folder -> childCount is always set to zero. But when the folder is accessed directly, the childCount is displayed correctly.
To Reproduce

Make the following request in a folder with child folders which you know have childs:
GET https://graph.microsoft.com/v1.0/me/drive/items/{{folder_id}}/search(q='{search_term}')
See that the folder -> childCount property is set to 0 and copy the id of that folder
Make the following request with the previous id:
GET https://graph.microsoft.com/v1.0/me/drive/items/{{previous_folder_id}}
folder -> childCount property is not 0

Expected behavior
The childCounts should be consistent
Screenshots

Notice that the folder with id '01RASYKTIE76MUOKLKWBA32BC77ZCMFK5G' has a childCount which is different in the 2 images.
Desktop (please complete the following information):

OS: MacOS
Browser Arc
Version 1.13.1 (42579)

@ncarvajalc this is a detailed analysis you've provided.
We are going to mark this as a API: Graph issue since it is likely an issue with the Graph API


installed 2 version of neverwinter  [1.5.9, 1.6.3], report error on package if remove any one of them

On package Error: Could not locate gff utility: is nwn_gff installed?
On unpackage Error: Could not locate erf utility: is nwn_erf installed?
environment (Windows 10 22H2):
blarg  [0.1.1]
docopt  [0.7.0]
glob  [0.11.2]
nasher  [0.20.2]
neverwinter  [1.5.9, 1.6.3]
nimble  [0.14.2]
nwnt  [1.4.1]
regex  [0.20.2]
unicodedb  [0.12.0]

is this normal?

Not sure how it works on Windows, but on Linux nimble handles multiple installations of a binary package by symlinking the desired version from ~/.nimble/pkgs/${pgkname}-${pkgver}/${bin} to ~/.nimble/bin/${bin}. So the things to check would be:

that the Windows equivalent of ~/.nimble/bin is in your path so the shell can locate the binaries, and
that the appropriate binary is linked to from ~/.nimble/bin.

Not sure how it works on Windows, but on Linux nimble handles multiple installations of a binary package by symlinking the desired version from ~/.nimble/pkgs/${pgkname}-${pkgver}/${bin} to ~/.nimble/bin/${bin}. So the things to check would be:
1. that the Windows equivalent of `~/.nimble/bin` is in your path so the shell can locate the binaries, and

2. that the appropriate binary is linked to from `~/.nimble/bin`.

oh, if so, multiple installation would override each other in ~/.nimble/bin/${bin}!
problem solved!


csv file content exmaple for SSM.py

I can not find a csv example file for script SSM.py input, Could you please offer me an example?

Hi @fayina,
The SSM.py script is meant for use with a dataset represented by a CSV of mutations and PDB structure. It expects data in the format of the ProtDDG-Bench repository, which you can find here.
Hope this helps!
Henry


updating project by id with hidden as false

When updating a project by id if the hidden requirement is not marked as "true" then it states that hidden does not exist and did not pass requirement validation.
project: {
	"id": 1,
        "data_entry_date": "date #1",
        "data_entry_time": "time #1",
        "data_entry_user_id": 1,
        "title": "title #1 updated",
        "status": "active",
        "project_category": 1,
        "image_directory":
        "/image/project/project#1.jpeg",
        "summary": "summary #1",
        "description": "description #1",
        "hidden": true
}

works fine but
project: {
	"id": 1,
        "data_entry_date": "date #1",
        "data_entry_time": "time #1",
        "data_entry_user_id": 1,
        "title": "title #1 updated",
        "status": "active",
        "project_category": 1,
        "image_directory":
        "/image/project/project#1.jpeg",
        "summary": "summary #1",
        "description": "description #1",
        "hidden": false
}

states that hidden is not passed when it is.
Validation is found in project middleware - validateProjectUpdateContent

Because hidden is a bool, when you check if it does not exist with if (!project[requirement] it returns true as in the value of the bool is true, stating that it does not exist and to error.
I have fixed this by removing the bool from the ForEach statement and checked it independently afterwards.
fixed in: #3


Mast: Watch pcpapa.net

Mast requests the watch of the watch_keyword pcpapa\.net. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

pcpapa\.net has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Integrated Bevy into a third party iOS app

Hi,
I have a quick question about how to implement bevy in an existing third party iOS app. Im aware of how to link everything properly form xcode setup perspective but I would like to know if I just can call main_rs and put the UIKit Elements on top.
Alternatively is it possible that you can share the link to the iOS code generation which might help a bit more.
kind regards
Schr3da

Winit drives the main event loop: https://github.com/rust-windowing/winit/blob/6474891f1e04d66704e3ed84ee585cd8b02ba19f/src/platform_impl/ios/event_loop.rs#L123 I don't think you can use it inside an existing app for that reason. Bevy is very modular, so it should be possible to write a replacement for bevy_winit that handles integration with an existing app though.

Thanks for the quick reply - will close the ticket now


v3.3.0 - Preparing client for the new Wall

This update brings compatibility with the new, authentication-based, CodyColorWall. Some small changes have been done in order to communicate in particular with the server component, that suffered far greater changes.
In order to make the Client component operational, an update to the version 3.2.1 is requested also in the Server module.
Additionally, a fixed is introduced to correct the issue #14, relative to firebaseUI problems.

Updated some files for compatibility with new Wall features (auth + battle royale). Also, some configuration has been hided inside settings.js. Contact me before deploying for the correct setting file.


[APEXMALHAR-1978] Replaced usages of {groupId} with {project.groupId}

There were no instances of this within the Malhar project.
Fixed usages within Core

@ilganeli The issue was fixed in the Malhar project. Please see my comments in JIRA for details. Changes in this PR are not necessary as files modified are archetype prototype pom.xml files and {groupId} will be replaced with user specified groupId during archetype plugin execution.


Issue: Lack of Mobile View Support for User Interface

Description:
The current User interface does not provide support for mobile view.
Expected Behavior:

The interface should be responsive and provide an optimal viewing experience on all devices, including mobile phones and tablets.
Elements should scale and adjust their layout dynamically based on the screen size.
The mobile version should follow best practices for mobile-friendly design, such as touch-friendly controls and clear, readable text.

Proposed Solution:

Review and Refactor CSS: Update the CSS stylesheets or implement a responsive design framework (like Bootstrap or Tailwind CSS) to ensure that the interface adapts to different screen sizes.
Use Media Queries: Add CSS media queries to detect screen sizes and adjust the layout accordingly for mobile devices.
Test on Multiple Devices: Test the layout on various mobile devices with different screen resolutions to ensure compatibility.
Mobile Navigation: Implement a mobile-friendly navigation menu, such as a hamburger menu, for better user experience.
Font and Image Scaling: Ensure that fonts and images scale correctly for smaller screens.

Priority:
High

@vaibhavyadav-dev  i would like to work on this issue

@vaibhavyadav-dev pls assign me this issue under hacktoberfest. I would like to work on this and bring the expected result

@vaibhavyadav-dev i would like to work on this issue I can implement Tailwind CSS to create a responsive design that adapts to different screen sizes.

ok @rairohit17 you can take it and make sure you've an idea about the webapp and to implement it fully.

@vaibhavyadav-dev pls assign me this issue under hacktoberfest. I would like to work on this and bring the expected result

Hey @dharshini2022 there's lot to contribute on this repo, look around, you'll definitely find bug to work upon.

@rairohit17 are you working on this issue ?

yes @vaibhavyadav-dev  i am working on this issue
i have replaced the classes of index page with the tailwind classes
Screencast from 2024-10-21 00-38-43.webm
but i need to know do i have to add tailwind css to every rpage , as it will take a lot of time as all the class needed to be written again

@rairohit17 any update ?


select will not materialize to SelectQuery

writing
CFNAME.select

return
ROOTSELECTBLOCK that doesn't have a where definition
while distinct and count returns SelectQuery which does have a where method.
Seems like I am missing something but what? This worked fine on 1.5.0

Hi @raam86 ,
You are missing one of the following:

The import com.websudos.phantom.dsl._ import at the top, which has an implicit conversion from RootSelectBlock to SelectQuery.
An implicit keySpace definition in the scope where you are trying to compose the query.
An implicit session definition in the scope where you are running the query.

The former 2 are fixed by using connectors, revisit this blog post for more details or have a look at the tests/phantom-activator-template.
Hope this helps!

@alexflav23 Thank you for your help.
I actually tried running with distinct and got the keySpace error. after running with distinct I was able to use the dsl as usual.
Maybe it was the keySpace but it failed too early?
Anyways,
Cheers,

Hi @raam86,
I think you have successfully circumvented all written documentation on phantom, which I believe may be the root cause of this. The approach you are taking is dangerous as you are introducing blocking behaviour to a Netty channel.
val connector = ContactPoints(hosts).keySpace("test")
That will just give you the inner trait connector.Connector that you can mix in anywhere you need the implicit session and implicit keyspace. Use database objects as intended by the framework.

Thanks alex I would love a link ContactPoints docs.

HI @raam86,
The blog post in question is here.
Regards.

Thanks. That was helpful


[Feature Request]: Shorten names when duplicating runs multiple times

Feature description
When cloning pipeline runs the name for the new run automatically gets a "Duplicate of" added to the original run name. If not changed and cloned multiple times run names can become long and hard to read, e.g. Duplicate of Duplicate of Duplicate of original_run. The UI could leave out "Duplicate of" or shorten/consolidate it in some way to make run names easier to read.
Describe alternatives you've considered
No response
Anything else?
No response

Thanks for logging the issue @ykoyfman!
Yeah this is not awesome after a few duplicates. We definitely left it very basic logic with our first implementation of it. But Duplicate of is prefixed to avoid duplicate names and allows for "quick repeating" a run. It's not ideal because how do you find the one you care about in the mix...
We could probably look at filter listing all resources with the given name after Duplicate of and see how many they are... we could just add a number after that for how many there are... it won't be perfect, but you may end up with Duplicate of Test 12 or we could even go so far as saying Test 12 🤔
cc @yannnz thoughts on our duplicate name generation? It definitely could use the work.

Thanks for your thoughts on this.

Duplicate of Test 12 or we could even go so far as saying Test 12 🤔

Something like "Test 12" or "Test {12}" seems reasonable. It would of course be great to also have a clickable link to the parent run there, but obviously that would be a much bigger change.

UX Context
https://github.com/opendatahub-io/odh-dashboard/issues/1929#issuecomment-1751364481

I think we can do something similar to Google Docs: Whenever you copy a document, it opens a modal with a text box with "Copy of" appended and leave it to the user to modify.

@yannnz do we want to prompt a quick little dialog? We can't really verify it at this state -- maybe there is a way to generate extra focus in the name field on the form? It's hard to do so when the API is not really supporting these kind of early discovery things. We could probably validate the name of the run at this point in time (a quick filter and compare against that name) but it guarantees nothing between this modal and the completing of the run form.

@andrewballantyne @manaswinidas I am not sure about having an extra modal specific for the name modification. In google doc, that is the only modal popped up, and it always generates "Copy of" appended + doc name no matter if the user modified the previous copy name, which means google allows duplicated names. And as a google doc user, I normally don't change the name before it opens the copy doc page, which in our case will not avoid a long name at the first place.
IMHO, we already have the creation modal and the user can modify the name there, which is similar to google doc, but without highlighting the name field as google doc does.  Can we put effort on generating a better name as suggested above?  Duplicate {12} of Test or something to indicate the test has been duplicated of several times, and this is the 12th duplication.

@yannnz We can definitely give it a shot... can't promise you (like version naming) if we can get the right number of duplication... but a unique number may be possible though.

@yannnz We can definitely give it a shot... can't promise you (like version naming) if we can get the right number of duplication... but a unique number may be possible though.

I think make it short with a unique number is fine if we don't get the right number of duplication. At least, it solves the issue of a long name.

Migrated to jira:  https://issues.redhat.com/browse/RHOAIRFE-14


global read method can't be limited by allowIO or redirected by fileSystem

global read method can't be limited by allowIO or redirected by fileSystem

Thanks for the report! We'll fix that.

Does this apply to readFully as well? I am currently debugging an issue with readFully not honouring a custom filesystem, and this might be the cause.. any ETA on a fix? This would seem to be a pretty big gap for FS operations..

Hi nhoughto,
you are correct, this polyglot feature has not yet been implemented in Graal.js. It is on our TODO list for this quarter. I think support (at least for the core JavaScript engine) will land in the release early October.

Ah ok great, best way to know when this lands is to subscribe to this issue? Will be closed when the release goes out?
On 22 Aug 2018, 6:29 PM +1000, Christian Wirth<EMAIL_ADDRESS>wrote:

Hi nhoughto,
you are correct, this polyglot feature has not yet been implemented in Graal.js. It is on our TODO list for this quarter. I think support (at least for the core JavaScript engine) will land in the release early October.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

We usually close the issue when the feature has landed in the master branch of this repo. You can then use it if you build Graal.js from source yourself. If you depend on our pre-built binaries, the feature should typically be in the following release (unless it misses the feature freeze, around a week before the release).

We have implemented the feature for the GlobalBuiltins (read[Fully], readbuffer, load). Again, this only affects the core JavaScript engine; no work has been done for our Node.js implementation.
This feature is on the master branch of graal.js (https://github.com/graalvm/graaljs/commit/cda6016c628e0010ce474d0b3ec6bf94d5afc263) and will land in the RC6 release early September.

What about loadWithNewGlobal ? 🤞


IMPROVED DOCS

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind user-interface

/kind content

/kind translation

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area videos

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

ddddf90 Update _index.md

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign kris-nova
You can assign the PR to them by writing /assign @kris-nova in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @Rishabh4303! It looks like this is your first PR to falcosecurity/falco-website 🎉

We believe that this being opened by  a bot and we are closing this PR.
We had many interactions on this repository coming from bots and we limited the interactions to existing contributors until this is solved (starting with one day)
Read more at: https://lists.cncf.io/g/cncf-falco-dev/message/164
/close

@fntlnz: Closed this PR.

In response to this:

We believe that this being opened by  a bot and we are closing this PR.
We had many interactions on this repository coming from bots and we limited the interactions to existing contributors until this is solved (starting with one day)
Read more at: https://lists.cncf.io/g/cncf-falco-dev/message/164
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

We believe that this being opened by a bot and we are closing this PR.
We had many interactions on this repository coming from bots and we limited the interactions to existing contributors until this is solved (starting with one day)
Read more at: lists.cncf.io/g/cncf-falco-dev/message/164
/close


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/145 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit ff83795:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-10-09-15-25-28 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-10-09-15-25-28

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


feat: give ClientModule access to the final Client

Dev call: this will allow us to get rid of extension traits


fix(style): toast-inner

:tada: This PR is included in version 1.3.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[wallet][master] browser interacts with wallet

how does sendTransfer get intercepted and trigger something?
how to send to the wallet? wss or qr or deeplink?
how to send signed tx back from the wallet? wss or qr or link?

answers:
perfer wss because

it is secure and
there is no size limit of the payload
two-way communication

QR is still very user-friendly when size is small enough

final decision:
QR and redirect for certain size of payload

2019-06-02 16:02 update: let's use wss for its flexibility and security

add socket server / client / certificate
add open separate window service
add sign envelop
(optional) add sign message
final CB pass back tx hash
(optional) display pending tx


alchemical analysis crashes when calc-lambda-neighbors=1

If the user performs a simulation with calc-lambda-neighbors = 1, the script correctly detects that it can't do MBAR, but will attempt to calculate using other methods. But, it crashes when trying to do the following in slice_data:
u_klt[state, s1:s2, :nsnapshots[state]] = P.beta * ( data[r1:r2, :] + data[-1,:] )

The full error is here.

We've moved this to https://github.com/mobleylab/alchemical-analysis and hopefully will have a fix there. We decided the workflow would be easier going forwards if alchemical-analysis is separated from pymbar. Thanks for your input and hopefully we'll have a fix soon (or submit a Pull Request there if you have one).

We believe this was fixed by https://github.com/MobleyLab/alchemical-analysis/pull/12. This issue can be closed and any further issues relating to this can be on the alchemical-analysis GitHub site.


gRPC API

gRPC API w/ JSON HTTP proxy (via grpc-gateway) implementation for the IAVL library.
TODO:

[ ] Define gRPC service
[ ] Define all message types
[ ] Implement service implementation
[ ] Implement JSON HTTP proxy server
[ ] Tests
[ ] Fix build/CI

closes: #183
/cc @blinky3713 @charlescrain

Just a comment after checking on on the status here, will there also be a Rollback endpoint? Is there a different API for the mutable tree vs immutable ?

@blinky3713 I've implemented what I believe to be a majority of the implementation. To answer, your question, the API currently works on a mutable tree. If we'd like to differentiate and support both tree types, that can be done later down the line after this is reviewed and merged.
However, there is still some work to be done which I'd like your help on as I can no longer dedicate too much time to this atm. The work needed to be done:

Update makefile to install proto dependencies (if needed)
Implement Server#GetWithProof with unit tests
Implement unit tests for Server#{Rollback|VerifyAbsence|VerifyItem|Verify}
Docs (can be simple usage instructions in the main README).

This can be done as a separate PR (forked off of this one) with the PR merging directly into this PR (which I'll keep open).
Also, another outstanding item. Do we want to support the automatic loading of the latest version (e.g. if 0 is provided)?

I believe this will need to extended after the pruning PR is merged #158

thanks for merging from f-o-a-m/ival @marbar3778 , do I understand that yall's team will now take care of the remaining issues?

@blinky3713 I've updated the PR to return the grpc status code, do you mind verifying it on your end?

proto-breakage will fail until this is merged into master

@marbar3778 I think this is ready to merge, any more reviews?

Havent read much into it since the updates but does it support the new pruning logic?
can you also make sure that all the check boxes in the body of the PR are checked if they are completed?

@marbar3778 Just checked the boxes and updated the flags to include pruning options

I understand the use-case for accessing IAVL in other languages without a writing a wrapper. However, going from an embedded database library to a networked database server is a pretty fundamental change - are we sure this is something we want to do?
In particular, I am thinking of concurrency control. IAVL is not concurrency safe, but gRPC is fundamentally concurrent. There is also an expectation that a network server can handle multiple clients, but IAVL is not built for this and will likely not perform well.
If we want do to this, we should wrap the database in a RWMutex as a first step, limit simultaneous connections to e.g. 2, and also document thoroughly that the gRPC service is meant for use by a single client. To achieve good multi-client performance we will need to use a database backend with proper concurrency control built-in (e.g. BadgerDB), and should also support something approximating ACID transactions to avoid conflicts between clients. This is related to #241.
Thoughts?

I have to agree with @erikgrinaker here. At the very least, we need to add smart mutex locking and think carefully around multi-client use and ensure we're ACID-compliant -- at least multi-client reads.

I'm not sure I understand why the full enterprise solution of a distributed database is required before the grpc layer is implemented. The semantics can remain undefined in the event that you have multiple concurrent writes -- just leave a big warning or mark the feature as experimental.
Unless I'm severely mistaking, the original intended use case of the grpc api is unaffected by concurrency, which was to be able to use the cosmos iavl storage from a non-golang abci application. When we have one tendermint client + abci application, the transactions are executed sequentially during block execution, and the transactions themselves are sequential. There are no race conditions for writes. As for reads, the applications is responsible for keeping the appropriate indices for writes -- e.g. the index used for query or checkTx commands points to committed storage, hence there are no race conditions there either.
Would it not be reasonable to just commit the work that the tendermint team and @charlescrain already did here and then open up separate issues to discuss the possible dirrections to allow concurrency?

I'm not sure I understand why the full enterprise solution of a distributed database is required before the grpc layer is implemented. The semantics can remain undefined in the event that you have multiple concurrent writes -- just leave a big warning or mark the feature as experimental.

At the very least, we should wrap the tree in an RWMutex.

Unless I'm severely mistaking, the original intended use case of the grpc api is unaffected by concurrency, which was to be able to use the cosmos iavl storage from a non-golang abci application.

Yes, this is your  use-case (and I totally get that use-case). However, others are quite likely to start using this for other use-cases that it's not well-suited for, and then get sad when things don't work out very well.

Would it not be reasonable to just commit the work that the tendermint team and @charlescrain already did here and then open up separate issues to discuss the possible dirrections to allow concurrency?

Personally I'm a bit worried about the additional maintenance overhead, since IAVL is already a but under-maintained. Maybe we could split this out as a separate package that could be maintained on a best-effort basis?
@aaronc Since you will be taking over IAVL maintainership shortly, perhaps you'd like to weigh in here.

I think the limitations that @erikgrinaker proposes are reasonable.
Regarding maintenance overhead, this is a relatively small layer on top of the go API so it would likely be easier to maintain within this source tree because bugs would ideally be caught by tests. I do think we should mark this as an alpha API so that we don’t make any strong compatibility guarantees.
https://github.com/google/trillian, a similar project, also has a gRPC interface so this is not unprecedented.
I would like to see some tests which I think should be possible in process by just spinning up a server at a random port in a separate thread and sending requests to it.
We don’t currently have the internal bandwidth to finish this work quite yet. But I know the Kepler team needs this and if they have the bandwidth to wrap up this work with adequate test coverage I would support merging it.
I do want to add the disclaimer that big changes may be coming to IAVL, hopefully big improvements. But hopefully this doesn't affect the user facing API too much.

@aaronc I have started the work here https://github.com/f-o-a-m/iavl/tree/martin/grpc . I was able to bring it up to speed with master and all tests are passing.  When I submit the PR you can explain what changes to make to them or what needs to be added.

Sounds good, thanks!

I would propose closing this in favor of #296

Closing this in favor of #296, discussion is continued there.


Task name and error message joined when stderr tied to stdout and redirected to file

Expected Behavior
The task name and error message must be on different lines as in when stderr and stdout are not redirected to file:

Current Behavior
The task name and error are on the same line and are joined with no separator.  Here is a screen shot demonstrating the problem:

Context
Tools like emacs-gradle-mode that work by tying stderr and stdout together and redirecting them to file are unable to provide their users with working feedback (e.g., press a key to go to the first build error) because the output isn't in the expected format.
Steps to Reproduce (for bugs)

Extract compilejava-bug-test.zip
Run gradle build > output.txt 2>&1.
Open output.txt.
Notice that the message describing the compilation error is joined to :compileJava as in the screen shot above.

Your Environment

Build scan URL: https://gradle.com/s/v7nv6efwrlnfy

Duplicate of #4306

Closing as duplicate


Adding in typescript_type to the js_sys types

This gives proper TypeScript types to all of the js_sys types, so they won't show up as any.
This is technically a breaking change, but I think that's okay because:

I expect the breakage to be very minimal since it would only affect people who were passing in the wrong type.

By default TypeScript doesn't halt compilation when an error happens, so TypeScript errors are really more like warnings.

If the user's code does break, they can just use foo as any to fix it.

Nice!


Stacked timeseries scale with parsing disabled throws TypeError

Expected Behavior

Should display a stacked timeseries chart with 1 or more datasets.
Current Behavior

Calls to Chart.update() fail resulting in Uncaught TypeError: Cannot read property 'length' of undefined
Full Trace:
Uncaught TypeError: Cannot read property 'length' of undefined
    at updateStacks (chart.js:2975)
    at BarController.parse (chart.js:3182)
    at BarController._resyncElements (chart.js:3491)
    at BarController.buildOrUpdateElements (chart.js:3137)
    at Chart.update (chart.js:6614)

Steps to Reproduce

Can be reproduced at https://www.chartjs.org/docs/latest/samples/scales/time-line.html
Steps:

Open Javascript Console
Under the Config tab add stacked: true to scales.y
Under the Setup tab modify the dataset object with label: 'Dataset with point data' by adding parsing: false
Replace the dataset's data with the following

data: [{
  x: Utils.newDate(0).getTime(),
  y: Utils.rand(0, 100)
}, {
  x: Utils.newDate(5).getTime(),
  y: Utils.rand(0, 100)
}, {
  x: Utils.newDate(7).getTime(),
  y: Utils.rand(0, 100)
}, {
  x: Utils.newDate(15).getTime(),
  y: Utils.rand(0, 100)
}]

Click the Randomize action.

Context

Trying to improve performance for timeseries data with large sample counts - disabling parsing breaks the chart.
Environment

Chart.js version: 3.11
Browser name and version: Chrome 90.0.4430.72

Edit: Updated reproduction steps.

The sample uses date strings. Values need to be in the internal format of the scale for chart to work without parsing.
See https://www.chartjs.org/docs/latest/axes/cartesian/time.html#date-formats

My apologies, I was referring to the wrong page when writing the steps. However the bug is still reproducable.
Along with listed steps, replace the data of the last dataset with:
data: [{
  x: Utils.newDate(0).getTime(),
  y: Utils.rand(0, 100)
}, {
  x: Utils.newDate(5).getTime(),
  y: Utils.rand(0, 100)
}, {
  x: Utils.newDate(7).getTime(),
  y: Utils.rand(0, 100)
}, {
  x: Utils.newDate(15).getTime(),
  y: Utils.rand(0, 100)
}]

And it will throw exceptions.

I think its because the stacks are  build when parsing and are stored in the parsed data.
Not sure if we can support stacked charts with gained speed compared to parsing: true.

Hmm, is there no way to propagate the dataset through the parsing stages for stacked?


Batch bump PR feature

Feature Request
Hi, thanks for the amazing github action, I added it to clojure-lsp and it worked very well!
One feature that would be nice is to generate the PR with all the bumps instead of one by bump, a option like batch: true would be great.

Glad to hear it worked!
(For implementation / Note to Self)
I think in the instance that batch is set to true, that the only other thing that'll need to change with the above is the branch naming convention (In the case that branches aren't being cleaned up after merging for the repository in question). I'm assuming something like dependencies/clojure/${DATE} will be fine for most consumers

Glad to hear it worked!
(For implementation / Note to Self)
I think in the instance that batch is set to true, that the only other thing that'll need to change with the above is the branch naming convention (In the case that branches aren't being cleaned up after merging for the repository in question). I'm assuming something like dependencies/clojure/${DATE} will be fine for most consumers

@ericdallo This has been implemented as of tag v3!

@ericdallo This has been implemented as of tag v3!

Cool, I'll update it, thank you !!

Cool, I'll update it, thank you !!


Remove Tar archiving

#4050

Removed ArchiveFormat abstraction
Instead use Zip directly. The zip-specific stuff is still grouped together in an object - this might be more readable and I suppose it saves some duplication at callsites
Removed metadata type parameter and hardcode to Akka's ArchiveMetadata for zips
Remove tar-ey tests and make ArchiveDownloadSpec specific to zips (no longer an abstract class)

@shinyhappydan I'm getting a failing test which doesn't fail locally 🤔  it fails on a future which populates a file from a stream


Add more details on "What" Conditions are, with some examples.

Expected Behavior
The Condition documentation should explain to a new user what conditions are, and what are the various scenarios in which we can use them in Pipelines.
Actual Behavior
Currently, the docs page on conditions - https://github.com/tektoncd/pipeline/blob/master/docs/conditions.md  provides a detailed view on how to define/create conditions in a pipeline. However, there is NO information on what conditions are, and why should we use them in a Pipeline.
Steps to Reproduce the Problem
N/A
Additional Info
Some of the information from this link can be leveraged to update the conditions.md topic:
https://github.com/tektoncd/pipeline/blob/master/docs/pipelines.md#conditions

/kind documentation

/remove-lifecycle rotten
/remove-lifecycle stale
/reopen

@vdemeester since we're completely changing the structure of conditions via https://github.com/tektoncd/community/blob/master/teps/0007-conditions-beta.md i'm not sure this issue is relevant?

/close


Build make check fbp bin v2

Changes

v2 (since #694):

run-fbp-tests:

fixed issues pointed by @lpereira in the previous review;
changed the output handling to use logging instead of simply printing out;

with that also introduced the --log argument, so the user may specify the logging level;

Makefile.target:

dropped the *.txt copy from check-fbp-bin rule - we're skipping the reader/writer tests, as result we're not using these files at all;

Rationale
Add's check-fbp-bin rules, for that changes and adaptations were required on run-fbp-tests scripts so we can query the "wanted" tests to be compiled with that the build system can handle the compilation itself. Also in the process of changing the run-fbp-tests scripts we incorporated a bunch of improvements and design changes.

LGTM with harmless comments.

applied, thanks...


add Filters copy change

I'm adding the proposed copy from @vylc

Codecov Report

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

@@           Coverage Diff           @@
##           master    #6885   +/-   ##
=======================================
  Coverage   63.73%   63.73%
=======================================
  Files         419      419
  Lines       20482    20482
  Branches     2233     2233
=======================================
  Hits        13055    13055
  Misses       7293     7293
  Partials      134      134

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ec6657a...c9b4c14.


Old version being added in node modules

When I install this module using NPM, an older version is added to my node modules that uses React.PropTypes in QRscanner.js and uses react-native-camera version 0.7.0 which crashes

Yes, this is annoying :(

How do you solve it?


PublishDate Not Working

The field PublishDate seems to return nil on every page.

I've given an initial implementation and opened a PR here https://github.com/advancedlogic/GoOse/pull/52
Hope you find it useful!


Add autoResize Prop to VTextarea Component

Description:
I would like to request the addition of an autoResize prop to the VTextarea component in the Morpheme UI library. This prop would enable the textarea to automatically resize vertically based on the content, improving user experience by eliminating the need for manual resizing.
Use Case:
The autoResize prop is valuable in scenarios where the content length varies significantly, such as:

Forms and Surveys: Users can write responses of varying lengths without being constrained by a fixed textarea size, ensuring all text is visible without scrolling.
Chat Applications: Messages can expand naturally, accommodating short and long texts alike without excess space.
Content Management Systems: Writers can see their full text as they type, enhancing readability and ease of use.

Currently, developers have to implement custom JavaScript or CSS to achieve this functionality, which can be cumbersome and inconsistent across projects. Integrating autoResize directly into the VTextarea component would streamline development and improve the component's usability.
Example Implementation:
Here's an example of how the autoResize prop could be utilized in a Vue component:
<template>
  <VTextarea
    v-model="message"
    autoResize
    label="Message"
    placeholder="Type your message here..."
  />
</template>

Hi, thanks for the request. Unfortunately, currently we focus on stabilization and preparation for releasing v1. In the meantime, You can use useTextareaAutosize from @vueuse https://vueuse.org/core/useTextareaAutosize/ as the alternative. Or maybe integrating it with VTextarea.


Use HTTP Error codes for dispatch API

The dispatch api should use proper error codes. Currently all requests return OK with a message

I'm already on it will be fixed in the next PR.

Addressed in #1484


Consider allowing to optionally use Elastic.CommonSchema.NLog.EcsLayout for providing Elastic Common Schema support

Hi,
It looks Elastic as a part of Elastic Common Schema ('ECS') effort introduced NLog support in form of specialized NLog Layout (named 'EcsLayout') that renders LogEventInfo structure to proper JSON representation (as per ECS definition) which is ready to be submitted to Elastic via their Elastic Low Level Client (check https://github.com/elastic/ecs-dotnet/tree/master/src/Elastic.CommonSchema.NLog and https://github.com/elastic/ecs-dotnet/tree/master/src/Elastic.CommonSchema).
Can this be considered as a proper way of supporting ECS in NLog.Targets.ElasticSearch?
It seems we would need just a pass through option where RenderLogEvent(Layout, logEvent) output is just sent to Elastic (assuming Layout is properly set to EcsLayout).

The library is still BETA-stage:
https://github.com/elastic/ecs-dotnet/pull/65
But yes when the API can be considered stable, then it would make sense to inject pure Json into the LowLevel-Client.
Please make a PR that can take the output from the Target.Layout and pass as raw Json to the LowLevel-Client. Then you can use this Target together with Elastic.CommonSchema.NLog right now.

@xprzemekw Have created #125 that allows you to use JsonLayout (or EcsLayout) for generating document-payload. (

@markmcdowell When #125 has been released, then this issue can be resolved.

Closed by #125 thanks to @snakefoot

Remember to update release notes for 7.3.0 about change in default DocumentType from logevent to _doc
Sent from my Sony Xperia
---- Mark McDowell wrote ----
Closed by #125https://github.com/markmcdowell/NLog.Targets.ElasticSearch/pull/125 thanks to @snakefoothttps://github.com/snakefoot
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/markmcdowell/NLog.Targets.ElasticSearch/issues/122#issuecomment-631437164, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACXZ7HDD6FGVKT4TQDH6U2LRSPC4VANCNFSM4M47RY2A.


Add codecov integration to Travis-CI config

This configures upload of our Jacoco coverage results to https://codecov.io. The coverage report from this branch is at https://codecov.io/github/kennknowles/incubator-beam?ref=codecov.
I chose codecov because it provides browser extensions to overlay the coverage information onto pull requests, where it can supplement our review process.
As with Travis-CI, this requires activation for any fork that it is going to run against. Any contributor can activate their own fork. Activating this or another code coverage tool for Apache's fork will require some trivial work from infra. It can also be used with Jenkins, if desired.
(To forestall any concerns about downloading and executing an arbitrary script: Travis-CI already does this in the form of running the script specified by pull requests, which are much more likely to be malicious or erroneous.)

R: @davorbonaci
Side note: why do we change the phase in which Jacoco runs?

Jenkins failure is a known breakage not related to this PR.

Current coverage is 71.46%

Branch #89 has no coverage reports uploaded yet.

No diff could be generated. No reports for master found.

Powered by Codecov. Updated on successful CI builds.

There are other alternatives, like coveralls.io, proposed here.
I'm not sure which one is better, but I prefer the concept of the Maven plugin more than executing random scripts outside the build process. All other things being equal (which is probably not the case), I'd prefer that approach.

I don't have a strong preference, except to choose one and have it running right away. Both are free for open source, both are trivial to set up. We can change at any time. We can even use both to see which makes us happier.
It does look like there is also a coveralls browser extension, though unsupported. Getting coverage data into the pull request is a must-have for it to be useful to me.
As I noted in the PR description, we already execute random scripts. Any user can add their own script to .travis.yml and it will be executed.

The build integration part is not about security. If it is integrated into the Maven build lifecycle, it is one-step does it all, as opposed to having to execute two separate steps.

This is actually a feature. A failure of the coverage upload does not fail the build. We can and should configure Jenkins the same way.

Not a feature; and completely orthogonal point. Plugins can be configured not to fail the build on errors. In this case, the configuration property is called failOnServiceError.

It seems codecov is not compatible with Apache policies, so I am closing this and will proceed with coveralls.


Stucking on "Setting up splash screen" at initializing new project on Windows

First of all thanks for applying my request to add Splash, but a quick look at the issues shows it made a lot of problems. There is another one, While I'm creating a new project using ignite new SampleApp, after adding ignite-ir-boilerplate-bowser it says:
- ? setting up splash screen an error occured while installing ignite-ir-boilerplate-bowser boilerplate.   Error: Command Failed: sed -i 's/SplashScreenPatch/igniteApp/g' ***path to project***   'sed' is not recognized as internal or external command...
 Also I know I can install sed for Windows, but guys please take care of us and try use commands that are globally available for all OS users! also using the new react-native v56 makes sense (due to updating android gradle plugins). Thanks for your absolute boiler plate that is a good source for learning typescript too.

Hey @AlirezaAkbarix and @Reaperxxxxx , the issue is because sed is not in the normal Windows path.
You'll want to use the Linux subsystem in Windows 10 which will fix this problem.

I'd like to create a better developer experience here for this.

I wonder if a plugin might be more cross platform?

the problem is I tested it on the bash of windows 10 and faced the same thing, I tested 0.42 react native it worked I can create a new project. but the things is I cloned a test project I can run it fine and work on it.
temporary solution for now

pinging @kevinvangelder the resident windows fanboy expert for an opinion too, does ms still take it to heart when you use / instead of \ ?

$ ignite new ttApp
An unfair headstart for your React Native apps.
https://infinite.red/ignite
🔥 igniting app ttApp
? Which boilerplate would you like to use? Bowser (in Beta) (React Navigation, MobX State Tree, & TypeScript)
✔ using the Infinite Red boilerplate v3 (code name 'Bowser')
✔ added React Native 0.55.4 in 129.83s
✔ added ignite-ir-boilerplate-bowser in 192.68s
⠹ ▸ setting up splash screen: cleaningan error occured while installing ignite-ir-boilerplate-bowser boilerplate.
Error: Command failed: git apply /ttApp/ttApp/patches/splash-screen/splash-screen.patch
error: android/app/src/main/java/com/ttApp/MainActivity.java: No such file or directory
⠸ ▸ setting up splash screen: cleaning
*/-------------------------------------------------------------------------------------------*
$ignite doctor
System
platform linux
arch x64
cpu 8 cores Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz
directory /mnt/c/Windows/System32
JavaScript
node 10.7.0 /usr/bin/node
npm 6.1.0 /usr/bin/npm
yarn 1.7.0 /usr/bin/yarn
React Native
react-native-cli 2.0.1
Ignite
ignite 2.1.1 /usr/bin/ignite
Android
java 1.8.0_171 /usr/bin/java
android home - /root/android-sdk-linux

I just created a new project,name of the project all LOWERCASE it worked fine , windows and bash windows 10

@Reaperxxxxx, Ssstrange!

I'm closing this issue because it's been fixed by #69.
If you found this thread after encountering the same issue in the latest release, please feel free to create a new issue. Thanks!


Python3.5 + compatible

Python3.5 + compatible. In the file 'uwsgi_sloth/models.py', line 43, fp needs to be encoded or a type error will be reported.For example: fp = fp. encode ()

if type error in 43 number,add :    fp = fp. encode ()

The latest version 3.0.0+ should be compatible with Python 3.5+, please provide more details on this bug.


user should able to add more custom section like "objectives"

Because sometimes need to add personal talks like "What I want", "Extra Activites" which are not part of objectives or work experience . Please consider this. Thanks

Closing this in favor of Reactive Resume v3 release.
If you continue to face this issue, please raise a new one and I'll have a look at it as soon as I can.
In the meantime, if you are able to, please consider donating to keep supporting the project: https://www.buymeacoffee.com/AmruthPillai :)
Thank you!


Formatter: decimalSeparator does not work when currency+intl are used

config:
        'formatter' => [
            'defaultTimeZone'        => 'Europe/Moscow',
            'locale'                 => 'ru_RU',
            'currencyCode'           => 'RUB',
            'numberFormatterSymbols' => [
                \NumberFormatter::CURRENCY_SYMBOL           => 'руб.',
            ],
            'decimalSeparator'       => '.',
            'thousandSeparator'      => ' ',
        ],

GridView DataColumn:
[
            'class'              => 'kartik\grid\DataColumn',
            'attribute'          => 'orderPlacesSum',
            'label'              => 'Сумма',
            'contentOptions'     => ['class' => 'text-center'],
            'pageSummaryOptions' => ['class' => 'text-center'],
            'format'             => 'currency',
            'pageSummary'        => true,
        ],

result:

A dot will use only if I specify NumberFormatter :: MONETARY_SEPARATOR_SYMBOL in numberFormatterSymbols
       'formatter' => [
            'defaultTimeZone'        => 'Europe/Moscow',
            'locale'                 => 'ru_RU',
            'currencyCode'           => 'RUB',
            'numberFormatterSymbols' => [
                \NumberFormatter::CURRENCY_SYMBOL           => 'руб.',
                \NumberFormatter::MONETARY_SEPARATOR_SYMBOL => '.',
            ],
            'decimalSeparator'       => '.',
            'thousandSeparator'      => ' ',
        ],

Can You add this string in Formatter.php? this will help the problem

Is there a use case for configuring it separately from decimal separator?

I did not quite understand the question. My english is probably bad

You're setting both GROUPING_SEPARATOR_SYMBOL and MONETARY_SEPARATOR_SYMBOL to the same value. Can there be a situation when these two need to have different value?

1)GROUPING_SEPARATOR_SYMBOL used with thousandSeparator, in my case it is ' '
2)MONETARY_SEPARATOR_SYMBOL used with decimalSeparator, in my case it is '.'
Maybe your mean DECIMAL_SEPARATOR_SYMBOL and MONETARY_SEPARATOR_SYMBOL?
If I set DECIMAL_SEPARATOR_SYMBOL=MONETARY_SEPARATOR_SYMBOL = '.'
Result
        echo(Yii::$app->formatter->asDecimal(123.45));//123.45
        echo(Yii::$app->formatter->asCurrency(123.45));//123.45 руб.

Without MONETARY_SEPARATOR_SYMBOL result will be
        echo(Yii::$app->formatter->asDecimal(123.45));//123.45
        echo(Yii::$app->formatter->asCurrency(123.45));//123,45 руб.

Yeah. I've meant that. I suspect setting these separately may be required for non-Russian language.

Therefore, introducing separate monetary separator sounds like a good way to handle it.

thanks a lot

@XPOHOC269 how about preparing a pull request to speed things up?

Ok? I will do it


feat: support async

Support async chunkers
To test:
Run the test, or update the call methods in the docs examples

resolves #15


save all channel_update

issue #1627
Save all channel_update whether receiving channel_announcement or not for routing.

https://github.com/lightningnetwork/lightning-rfc/blob/master/07-routing-gossip.md#requirements-3

MUST NOT send a created channel_update before funding_locked has been received.

対策しない。


Fix for TIKA-2672

@tballison @chrismattmann @thammegowda test and merge, did some refactoring too.

it is now pulling weight files from https://github.com/USCDataScience/tika-dockers/releases/tag/v0.1
dl4j model of vgg16 will be cached in: $HOME/.tika-dl/models/dl4j/vgg16
keras model of inception v3 will be cached in $HOME/.tika-dl/models/keras/inception-v3

@chrismattmann updated. Thanks prof :100:

awesome my guy I will review and test and get committed today!

I'm unable to build this locally, @ThejanW. I keep getting:
[ERROR] Failed to execute goal on project tika-dl: Could not resolve dependencies for project org.apache.tika:tika-dl:jar:2.0.0-SNAPSHOT: Could not find artifact org.bytedeco.javacpp-presets:openblas:jar:linux-x86:0.3.0-1.4.2-SNAPSHOT in oss-sonatype (https://oss.sonatype.org/content/repositories/snapshots/) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
nonas:tika-dl mattmann$

Any ideas @thammegowda or @agibsonccc?

BTW I rebuilt with mvn -U and it still didn't resolve this... @ThejanW @thammegowda @agibsonccc

oops! unit tests worked fine for me, we can safely exclude javacpp from tika-dl, then I got a dependency convergence issue:

Dependency convergence error for net.java.dev.jna:jna:4.1.0 paths to dependency are:
+-org.apache.tika:tika-dl:2.0.0-SNAPSHOT
+-org.apache.tika:tika-parsers:2.0.0-SNAPSHOT
+-edu.ucar:netcdf4:4.5.5
+-net.java.dev.jna:jna:4.1.0
and
+-org.apache.tika:tika-dl:2.0.0-SNAPSHOT
+-org.deeplearning4j:deeplearning4j-nn:1.0.0-SNAPSHOT
+-com.github.oshi:oshi-core:3.4.2
+-net.java.dev.jna:jna-platform:4.3.0
+-net.java.dev.jna:jna:4.3.0

In my latest commit, I have excluded jna in edu.ucar dependencies of tika-parsers and have added jna as a direct dependency. Any objections for that? @chrismattmann @tballison, I built the entire Tika project, the build was a success in my linux machine.

@ThejanW I'll give this a try.

@ThejanW I pulled your latest, and I'm stilling getting this error:
Downloading: https://oss.sonatype.org/content/repositories/snapshots/org/nd4j/nd4j-native/1.0.0-SNAPSHOT/nd4j-native-1.0.0-20180709.142828-3573-windows-x86_64.jar
Downloaded: https://oss.sonatype.org/content/repositories/snapshots/org/nd4j/nd4j-native/1.0.0-SNAPSHOT/nd4j-native-1.0.0-20180709.142828-3573-windows-x86_64.jar (7.0 MB at 505 kB/s)
Downloading: https://oss.sonatype.org/content/repositories/snapshots/org/nd4j/nd4j-native/1.0.0-SNAPSHOT/nd4j-native-1.0.0-20180709.141635-3571-linux-ppc64le.jar
Downloaded: https://oss.sonatype.org/content/repositories/snapshots/org/nd4j/nd4j-native/1.0.0-SNAPSHOT/nd4j-native-1.0.0-20180709.133434-3566-ios-x86_64.jar (6.6 MB at 467 kB/s)
Downloaded: https://oss.sonatype.org/content/repositories/snapshots/org/nd4j/nd4j-native/1.0.0-SNAPSHOT/nd4j-native-1.0.0-20180709.131559-3561-ios-arm64.jar (5.7 MB at 383 kB/s)
Downloaded: https://oss.sonatype.org/content/repositories/snapshots/org/nd4j/nd4j-native/1.0.0-SNAPSHOT/nd4j-native-1.0.0-20180709.141635-3571-linux-ppc64le.jar (5.9 MB at 382 kB/s)
Downloaded: https://oss.sonatype.org/content/repositories/snapshots/org/bytedeco/javacpp-presets/mkl-dnn/0.14-1.4.2-SNAPSHOT/mkl-dnn-0.14-1.4.2-20180708.232718-45-linux-x86_64.jar (43 MB at 2.2 MB/s)
Downloaded: https://oss.sonatype.org/content/repositories/snapshots/org/bytedeco/javacpp-presets/mkl-dnn/0.14-1.4.2-SNAPSHOT/mkl-dnn-0.14-1.4.2-20180708.202304-44-windows-x86_64.jar (43 MB at 2.0 MB/s)
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ tika-dl ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (enforce) @ tika-dl ---
[WARNING] The metadata /Users/mattmann/.m2/repository/org/deeplearning4j/deeplearning4j-parent/1.0.0-SNAPSHOT/maven-metadata-scala-tools.org.xml is invalid: end tag name
 must match start tag name
 from line 40 (position: TEXT seen ... personal-sites-and-blogs
... @41:47)
[WARNING] The metadata /Users/mattmann/.m2/repository/org/deeplearning4j/deeplearning4j/1.0.0-SNAPSHOT/maven-metadata-scala-tools.org.xml is invalid: end tag name
 must match start tag name
 from line 40 (position: TEXT seen ... personal-sites-and-blogs
... @41:47)
[WARNING] The metadata /Users/mattmann/.m2/repository/org/nd4j/nd4j-backend-impls/1.0.0-SNAPSHOT/maven-metadata-scala-tools.org.xml is invalid: end tag name
 must match start tag name
 from line 40 (position: TEXT seen ... personal-sites-and-blogs
... @41:47)
[WARNING]
Dependency convergence error for net.java.dev.jna:jna:4.1.0 paths to dependency are:
+-org.apache.tika:tika-dl:2.0.0-SNAPSHOT
  +-org.apache.tika:tika-parsers:2.0.0-SNAPSHOT
    +-edu.ucar:netcdf4:4.5.5
      +-net.java.dev.jna:jna:4.1.0
and
+-org.apache.tika:tika-dl:2.0.0-SNAPSHOT
  +-org.deeplearning4j:deeplearning4j-nn:1.0.0-SNAPSHOT
    +-com.github.oshi:oshi-core:3.4.2
      +-net.java.dev.jna:jna-platform:4.3.0
        +-net.java.dev.jna:jna:4.3.0

[WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
Failed while enforcing releasability. See above detailed error message.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 34.640 s
[INFO] Finished at: 2018-07-09T09:34:43-07:00
[INFO] Final Memory: 36M/556M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce (enforce) on project tika-dl: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
nonas:tika-dl mattmann$

please try mvn clean -U install

fixed thanks amigo!
 SUCCESS [  1.716 s]
[INFO] Apache Tika core ................................... SUCCESS [ 35.099 s]
[INFO] Apache Tika parsers ................................ SUCCESS [05:19 min]
[INFO] Apache Tika XMP .................................... SUCCESS [  1.894 s]
[INFO] Apache Tika serialization .......................... SUCCESS [  1.723 s]
[INFO] Apache Tika batch .................................. SUCCESS [02:11 min]
[INFO] Apache Tika language detection ..................... SUCCESS [  3.235 s]
[INFO] Apache Tika application ............................ SUCCESS [01:07 min]
[INFO] Apache Tika OSGi bundle ............................ SUCCESS [ 30.278 s]
[INFO] Apache Tika translate .............................. SUCCESS [  3.081 s]
[INFO] Apache Tika server ................................. SUCCESS [ 24.401 s]
[INFO] Apache Tika examples ............................... SUCCESS [ 12.374 s]
[INFO] Apache Tika Java-7 Components ...................... SUCCESS [  2.331 s]
[INFO] Apache Tika eval ................................... SUCCESS [ 28.734 s]
[INFO] Apache Tika Deep Learning (powered by DL4J) ........ SUCCESS [04:21 min]
[INFO] Apache Tika Natural Language Processing ............ SUCCESS [ 26.923 s]
[INFO] Apache Tika ........................................ SUCCESS [  0.021 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15:53 min
[INFO] Finished at: 2018-07-09T10:03:37-07:00
[INFO] Final Memory: 210M/1749M
[INFO] ------------------------------------------------------------------------
nonas:tika2.0.0 mattmann$

I'm going to test it and if it looks good I'll go ahead and commit shortly.

OK, tested VGG16, looks awesome, and works, FYI (note I had to rm $HOME/.tika-dl/ and folks may also want to rm -rf $HOME/.deeplearning4j*):
VGG16 server outputs:
Jul 09, 2018 10:12:35 AM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: J2KImageReader not loaded. JPEG2000 files will not be processed.
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.

Jul 09, 2018 10:12:35 AM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: Tesseract OCR is installed and will be automatically applied to image files unless
you've excluded the TesseractOCRParser from the default parser.
Tesseract may dramatically slow down content extraction (TIKA-2359).
As of Tika 1.15 (and prior versions), Tesseract is automatically called.
In future versions of Tika, users may need to turn the TesseractOCRParser on via TikaConfig.
Jul 09, 2018 10:12:35 AM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: org.xerial's sqlite-jdbc is not loaded.
Please provide the jar on your classpath to parse sqlite files.
See tika-parsers/pom.xml for the correct version.
INFO  Starting Apache Tika 2.0.0-SNAPSHOT server
INFO  Using custom config: tika-dl/src/test/resources/org/apache/tika/dl/imagerec/dl4j-vgg16-config.xml
INFO  Loaded [CpuBackend] backend
INFO  Number of threads used for NativeOps: 2
INFO  Number of threads used for BLAS: 2
INFO  Backend used: [CPU]; OS: [Mac OS X]
INFO  Cores: [4]; Memory: [3.6GB];
INFO  Blas vendor: [MKL]
WARN  java.io.UTFDataFormatException: malformed input around byte 11
java.lang.RuntimeException: java.io.UTFDataFormatException: malformed input around byte 11
	at org.nd4j.linalg.api.buffer.BaseDataBuffer.read(BaseDataBuffer.java:1509)
	at org.nd4j.linalg.compression.CompressedDataBuffer.readUnknown(CompressedDataBuffer.java:83)
	at org.nd4j.linalg.factory.Nd4j.read(Nd4j.java:2725)
	at org.deeplearning4j.util.ModelSerializer.restoreComputationGraph(ModelSerializer.java:564)
	at org.deeplearning4j.util.ModelSerializer.restoreComputationGraph(ModelSerializer.java:476)
	at org.apache.tika.dl.imagerec.DL4JVGG16Net.initialize(DL4JVGG16Net.java:95)
	at org.apache.tika.parser.recognition.ObjectRecognitionParser.initialize(ObjectRecognitionParser.java:94)
	at org.apache.tika.config.TikaConfig$XmlLoader.loadOne(TikaConfig.java:644)
	at org.apache.tika.config.TikaConfig$XmlLoader.loadOverall(TikaConfig.java:554)
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:191)
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:172)
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:165)
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:129)
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:124)
	at org.apache.tika.server.TikaServerCli.main(TikaServerCli.java:156)
Caused by: java.io.UTFDataFormatException: malformed input around byte 11
	at java.io.DataInputStream.readUTF(DataInputStream.java:656)
	at java.io.DataInputStream.readUTF(DataInputStream.java:564)
	at org.nd4j.linalg.api.buffer.BaseDataBuffer.read(BaseDataBuffer.java:1450)
	... 14 more
ERROR Can't start
org.apache.tika.exception.TikaConfigException: java.io.UTFDataFormatException: malformed input around byte 11
	at org.apache.tika.dl.imagerec.DL4JVGG16Net.initialize(DL4JVGG16Net.java:115)
	at org.apache.tika.parser.recognition.ObjectRecognitionParser.initialize(ObjectRecognitionParser.java:94)
	at org.apache.tika.config.TikaConfig$XmlLoader.loadOne(TikaConfig.java:644)
	at org.apache.tika.config.TikaConfig$XmlLoader.loadOverall(TikaConfig.java:554)
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:191)
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:172)
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:165)
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:129)
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:124)
	at org.apache.tika.server.TikaServerCli.main(TikaServerCli.java:156)
Caused by: java.lang.RuntimeException: java.io.UTFDataFormatException: malformed input around byte 11
	at org.nd4j.linalg.api.buffer.BaseDataBuffer.read(BaseDataBuffer.java:1509)
	at org.nd4j.linalg.compression.CompressedDataBuffer.readUnknown(CompressedDataBuffer.java:83)
	at org.nd4j.linalg.factory.Nd4j.read(Nd4j.java:2725)
	at org.deeplearning4j.util.ModelSerializer.restoreComputationGraph(ModelSerializer.java:564)
	at org.deeplearning4j.util.ModelSerializer.restoreComputationGraph(ModelSerializer.java:476)
	at org.apache.tika.dl.imagerec.DL4JVGG16Net.initialize(DL4JVGG16Net.java:95)
	... 9 more
Caused by: java.io.UTFDataFormatException: malformed input around byte 11
	at java.io.DataInputStream.readUTF(DataInputStream.java:656)
	at java.io.DataInputStream.readUTF(DataInputStream.java:564)
	at org.nd4j.linalg.api.buffer.BaseDataBuffer.read(BaseDataBuffer.java:1450)
	... 14 more
nonas:tika2.0.0 mattmann$ cat tika-dl/src/test/resources/org/apache/tika/dl/imagerec/dl4j-vgg16-config.xml
<?xml version="1.0" encoding="UTF-8"?>

<properties>
    <parsers>
        <parser class="org.apache.tika.parser.recognition.ObjectRecognitionParser">
            <mime>image/jpeg</mime>
            <params>
                <param name="topN" type="int">3</param>
                <param name="minConfidence" type="double">0.015</param>
                <param name="class" type="string">org.apache.tika.dl.imagerec.DL4JVGG16Net</param>
                <param name="modelType" type="string">VGG16</param>
                <param name="serialize" type="bool">true</param>
            </params>
        </parser>
    </parsers>
</properties>
nonas:tika2.0.0 mattmann$ ls /Users/mattmann/.tika-dl/
models
nonas:tika2.0.0 mattmann$ rm -rf $HOME/.tika-dl/
nonas:tika2.0.0 mattmann$ tika --config=tika-dl/src/test/resources/org/apache/tika/dl/imagerec/dl4j-vgg16-config.xml
Jul 09, 2018 10:13:56 AM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: J2KImageReader not loaded. JPEG2000 files will not be processed.
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.

Jul 09, 2018 10:13:56 AM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: Tesseract OCR is installed and will be automatically applied to image files unless
you've excluded the TesseractOCRParser from the default parser.
Tesseract may dramatically slow down content extraction (TIKA-2359).
As of Tika 1.15 (and prior versions), Tesseract is automatically called.
In future versions of Tika, users may need to turn the TesseractOCRParser on via TikaConfig.
Jul 09, 2018 10:13:56 AM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: org.xerial's sqlite-jdbc is not loaded.
Please provide the jar on your classpath to parse sqlite files.
See tika-parsers/pom.xml for the correct version.
INFO  Starting Apache Tika 2.0.0-SNAPSHOT server
INFO  Using custom config: tika-dl/src/test/resources/org/apache/tika/dl/imagerec/dl4j-vgg16-config.xml
INFO  Loaded [CpuBackend] backend
INFO  Number of threads used for NativeOps: 2
INFO  Number of threads used for BLAS: 2
INFO  Backend used: [CPU]; OS: [Mac OS X]
INFO  Cores: [4]; Memory: [3.6GB];
INFO  Blas vendor: [MKL]
WARN  Preprocessed Model doesn't exist at /Users/mattmann/.tika-dl/models/dl4j/vgg-16/vgg16.zip
INFO  Using cached model at /Users/mattmann/.deeplearning4j/models/vgg16/vgg16_dl4j_inference.zip
INFO  Verifying download...
INFO  Checksum local is<PHONE_NUMBER>, expecting<PHONE_NUMBER>
INFO  Starting ComputationGraph with WorkspaceModes set to [training: NONE; inference: SINGLE], cacheMode set to [NONE]
INFO  Saving the Loaded model for future use. Saved models are more optimised to consume less resources.
INFO  Recogniser = org.apache.tika.dl.imagerec.DL4JVGG16Net
INFO  Recogniser Available = true
INFO  Setting the server's publish address to be http://localhost:9998/
INFO  jetty-8.y.z-SNAPSHOT
INFO  Started SelectChannelConnector@localhost:9998
INFO  Started Apache Tika server at http://localhost:9998/
INFO  rmeta (autodetecting type)
INFO  Time taken 1427ms
INFO  Add RecognisedObject{label='lion' (eng), id='lion', confidence=0.9999885559082031}
INFO  Add RecognisedObject{label='chow' (eng), id='chow', confidence=1.1340579476382118E-5}
INFO  Add RecognisedObject{label='dhole' (eng), id='dhole', confidence=8.046561106311856E-8}

VGG16 client
nonas:imagerec mattmann$ curl -T lion.jpg http://localhost:9998/rmeta | python -mjson.tool
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 45971    0  1530  100 44441    916  26617  0:00:01  0:00:01 --:--:-- 26627
[
    {
        "Content-Type": "image/jpeg",
        "OBJECT": [
            "lion (0.99999)",
            "chow (0.00001)",
            "dhole (0.00000)"
        ],
        "X-Parsed-By": [
            "org.apache.tika.parser.CompositeParser",
            "org.apache.tika.parser.recognition.ObjectRecognitionParser"
        ],
        "X-TIKA:content": "\n\n<meta name=\"org.apache.tika.parser.recognition.object.rec.impl\" content=\"org.apache.tika.dl.imagerec.DL4JVGG16Net\" />\n<meta name=\"X-Parsed-By\" content=\"org.apache.tika.parser.CompositeParser\" />\n<meta name=\"X-Parsed-By\" content=\"org.apache.tika.parser.recognition.ObjectRecognitionParser\" />\n<meta name=\"OBJECT\" content=\"lion (0.99999)\" />\n<meta name=\"OBJECT\" content=\"chow (0.00001)\" />\n<meta name=\"OBJECT\" content=\"dhole (0.00000)\" />\n<meta name=\"Content-Type\" content=\"image/jpeg\" />\n<title></title>\n\n
\t
 lion [eng](confidence = 0.999989)
\n\t
 chow [eng](confidence = 0.000011)
\n\t
 dhole [eng](confidence = 0.000000)
\n
\n",
        "X-TIKA:parse_time_millis": "1495",
        "org.apache.tika.parser.recognition.object.rec.impl": "org.apache.tika.dl.imagerec.DL4JVGG16Net"
    }
]
nonas:imagerec mattmann$

Now I'll try Inception.

Inceptionv3 works great!
Inception server
nonas:tika2.0.0 mattmann$ tika --config=tika-dl/src/test/resources/org/apache/tika/dl/imagerec/dl4j-inception3-config.xml
Jul 09, 2018 10:18:53 AM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: J2KImageReader not loaded. JPEG2000 files will not be processed.
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.

Jul 09, 2018 10:18:53 AM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: Tesseract OCR is installed and will be automatically applied to image files unless
you've excluded the TesseractOCRParser from the default parser.
Tesseract may dramatically slow down content extraction (TIKA-2359).
As of Tika 1.15 (and prior versions), Tesseract is automatically called.
In future versions of Tika, users may need to turn the TesseractOCRParser on via TikaConfig.
Jul 09, 2018 10:18:53 AM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: org.xerial's sqlite-jdbc is not loaded.
Please provide the jar on your classpath to parse sqlite files.
See tika-parsers/pom.xml for the correct version.
INFO  Starting Apache Tika 2.0.0-SNAPSHOT server
INFO  Using custom config: tika-dl/src/test/resources/org/apache/tika/dl/imagerec/dl4j-inception3-config.xml
INFO  Cache doesn't exist. Going to make a copy
INFO  This might take a while! GET https://github.com/USCDataScience/tika-dockers/releases/download/v0.2/inception_v3_keras_2.h5
INFO  Cache doesn't exist. Going to make a copy
INFO  This might take a while! GET https://github.com/USCDataScience/tika-dockers/releases/download/v0.2/imagenet_class_index.json
INFO  Going to load Inception network...
INFO  Unexpected end-of-input: expected close marker for OBJECT (from [Source: {"config": {"output_layers": [["predictions", 0, 0]], "layers": [{"class_name": "InputLayer", "name": "input_1", "config": {"batch_input_shape": [null, null, null, 3], "dtype": "float32", "sparse": false, "name": "input_1"}, "inbound_nodes": []}, {"class_name": "Conv2D", "name": "conv2d_1", "config": {"activity_regularizer": null, "strides": [2, 2], "padding": "valid", "kernel_regularizer": null, "kernel_initializer": {"class_name": "VarianceScaling", "config": {"scale": 1.0, "distribution": "uniform", "mode": "fan_avg", "seed": null}}, "data_format": "channels_last", "activation": "linear", "bias_regularizer": null, "kernel_size": [3, 3], "dilation_rate": [1, 1], "use_bias": false, "trainable": true, "kernel_constraint": null, "bias_constraint": null, "bias_initializer": {"class_name": "Zeros", "config": {}}, "filters": 32, "name": "conv2d_1"}, "inbound_nodes": [[["input_1", 0, 0, {}]]]}, {"class_name": "BatchNormalization", "name": "batch_normalization_1", "config": {"center": true, "gamma_initializer": {"class_name": "Ones", "config": {}}, "beta_constraint": null, "gamma_constraint": null, "moving_variance_initializer": {"class_name": "Ones", "config": {}}, "moving_mean_initializer": {"class_name": "Zeros", "config": {}}, "scale": false, "momentum": 0.99, "gamma_regularizer": null, "trainable": true, "epsilon": 0.001, "axis": 3, "beta_initializer": {"class_name": "Zeros", "config": {}}, "beta_regularizer": null, "name": "batch_normalization_1"}, "inbound_nodes": [[["conv2d_1", 0, 0, {}]]]}, {"class_name": "Activation", "name": "activation_1", "config": {"activation": "relu", "trainable": ....suppressed
{"activity_regularizer": null, "strides": [1, 1], "padding": "same", "kernel_regularizer": null, "kernel_i; line: 1, column: 64001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@7c711375; line: 1, column: 36001]
INFO  Unexpected end-of-input within/between OBJECT entries
 at [Source: java.io.StringReader@57cf54e1; line: 1, column: 40001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@5b03b9fe; line: 1, column: 44001]
INFO  Unrecognized token 'tru': was expecting 'null', 'true', 'false' or NaN
 at [Source: java.io.StringReader@37d4349f; line: 1, column: 56001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@434a63ab; line: 1, column: 52001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@6e0f5f7f; line: 1, column: 56001]
INFO  Unexpected end-of-input: expected close marker for ARRAY (from [Source: java.io.StringReader@2805d709; line: 1, column: 45999])
 at [Source: java.io.StringReader@2805d709; line: 1, column: 60001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@3ee37e5a; line: 1, column: 64001]
INFO  Unexpected end-of-input in FIELD_NAME
 at [Source: java.io.StringReader@2ea41516; line: 1, column: 68001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@3a44431a; line: 1, column: 72001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@3c7f66c4; line: 1, column: 76001]
INFO  Unexpected end-of-input: was expecting closing quote for a string value
 at [Source: java.io.StringReader@194bcebf; line: 1, column: 80001]
INFO  Unexpected end-of-input in FIELD_NAME
 at [Source: java.io.StringReader@17497425; line: 1, column: 84001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@f0da945; line: 1, column: 88001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@4803b726; line: 1, column: 92001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@ffaa6af; line: 1, column: 96001]
INFO  Unexpected end-of-input: was expecting closing quote for a string value
 at [Source: java.io.StringReader@53ce1329; line: 1, column: 68001]
INFO  Unexpected end-of-input: expected close marker for ARRAY (from [Source: java.io.StringReader@316bcf94; line: 1, column: 67972])
 at [Source: java.io.StringReader@316bcf94; line: 1, column: 80001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@6404f418; line: 1, column: 76001]
INFO  Unexpected end-of-input in FIELD_NAME
 at [Source: java.io.StringReader@3e11f9e9; line: 1, column: 80001]
INFO  Unexpected end-of-input in FIELD_NAME
 at [Source: java.io.StringReader@1de5f259; line: 1, column: 84001]
INFO  Unexpected end-of-input within/between OBJECT entries
 at [Source: java.io.StringReader@729d991e; line: 1, column: 88001]
INFO  Unexpected end-of-input in FIELD_NAME
 at [Source: java.io.StringReader@31fa1761; line: 1, column: 92001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@957e06; line: 1, column: 96001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@32502377; line: 1, column: 100001]
INFO  Unexpected end-of-input in FIELD_NAME
 at [Source: java.io.StringReader@2c1b194a; line: 1, column: 104001]
INFO  Unexpected end-of-input within/between ARRAY entries
 at [Source: java.io.StringReader@4dbb42b7; line: 1, column: 108001]
INFO  Unexpected end-of-input within/between OBJECT entries
 at [Source: java.io.StringReader@66f57048; line: 1, column: 112001]
INFO  Unexpected end-of-input: was expecting closing quote for a string value
 at [Source: java.io.StringReader@550dbc7a; line: 1, column: 116001]
INFO  Unexpected end-of-input in FIELD_NAME
 at [Source: java.io.StringReader@21282ed8; line: 1, column: 120001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@36916eb0; line: 1, column: 124001]
INFO  Unrecognized token 'fals': was expecting 'null', 'true', 'false' or NaN
 at [Source: java.io.StringReader@7bab3f1a; line: 1, column: 160001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@437da279; line: 1, column: 100001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@23c30a20; line: 1, column: 104001]
INFO  Unexpected end-of-input in FIELD_NAME
 at [Source: java.io.StringReader@1e1a0406; line: 1, column: 108001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@3cebbb30; line: 1, column: 112001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@12aba8be; line: 1, column: 116001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@290222c1; line: 1, column: 120001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@67f639d3; line: 1, column: 124001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@6253c26; line: 1, column: 128001]
INFO  Unexpected end-of-input: was expecting closing quote for a string value
 at [Source: java.io.StringReader@49049a04; line: 1, column: 132001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@71a8adcf; line: 1, column: 136001]
INFO  Unexpected end-of-input in FIELD_NAME
 at [Source: java.io.StringReader@27462a88; line: 1, column: 140001]
INFO  Unexpected end-of-input in FIELD_NAME
 at [Source: java.io.StringReader@82de64a; line: 1, column: 144001]
INFO  Unexpected end-of-input within/between ARRAY entries
 at [Source: java.io.StringReader@659499f1; line: 1, column: 148001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@51e69659; line: 1, column: 152001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@47e2e487; line: 1, column: 156001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@201a4587; line: 1, column: 160001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@61001b64; line: 1, column: 132001]
INFO  Unexpected end-of-input: was expecting closing quote for a string value
 at [Source: java.io.StringReader@4310d43; line: 1, column: 136001]
INFO  Unexpected end-of-input in FIELD_NAME
 at [Source: java.io.StringReader@54a7079e; line: 1, column: 140001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@26e356f0; line: 1, column: 144001]
INFO  Unexpected end-of-input: was expecting closing quote for a string value
 at [Source: java.io.StringReader@47d9a273; line: 1, column: 148001]
INFO  Unexpected end-of-input: was expecting closing quote for a string value
 at [Source: java.io.StringReader@4b8ee4de; line: 1, column: 152001]
INFO  Unexpected end-of-input: was expecting closing '"' for name
 at [Source: java.io.StringReader@27f981c6; line: 1, column: 156001]
INFO  Unexpected end-of-input: expected close marker for OBJECT (from [Source: java.io.StringReader@1b11171f; line: 1, column: 143942])
 at [Source: java.io.StringReader@1b11171f; line: 1, column: 160001]
INFO  Unrecognized token 'tru': was expecting 'null', 'true', 'false' or NaN
 at [Source: java.io.StringReader@1151e434; line: 1, column: 182001]
INFO  Loaded [CpuBackend] backend
INFO  Number of threads used for NativeOps: 2
INFO  Number of threads used for BLAS: 2
INFO  Backend used: [CPU]; OS: [Mac OS X]
INFO  Cores: [4]; Memory: [3.6GB];
INFO  Blas vendor: [MKL]
INFO  Starting ComputationGraph with WorkspaceModes set to [training: ENABLED; inference: ENABLED], cacheMode set to [NONE]
INFO  Loaded the Inception model. Time taken=2657ms
INFO  Recogniser = org.apache.tika.dl.imagerec.DL4JInceptionV3Net
INFO  Recogniser Available = true
INFO  Setting the server's publish address to be http://localhost:9998/
INFO  jetty-8.y.z-SNAPSHOT
INFO  Started SelectChannelConnector@localhost:9998
INFO  Started Apache Tika server at http://localhost:9998/
INFO  rmeta (autodetecting type)
INFO  Time taken 1014ms
INFO  Add RecognisedObject{label='lion' (en), id='291', confidence=0.9375439286231995}

Inception Client
nonas:imagerec mattmann$ curl -T lion.jpg http://localhost:9998/rmeta | python -mjson.tool
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 45617    0  1176  100 44441    920  34790  0:00:01  0:00:01 --:--:-- 34801
[
    {
        "Content-Type": "image/jpeg",
        "OBJECT": "lion (0.93754)",
        "X-Parsed-By": [
            "org.apache.tika.parser.CompositeParser",
            "org.apache.tika.parser.recognition.ObjectRecognitionParser"
        ],
        "X-TIKA:content": "\n\n<meta name=\"org.apache.tika.parser.recognition.object.rec.impl\" content=\"org.apache.tika.dl.imagerec.DL4JInceptionV3Net\" />\n<meta name=\"X-Parsed-By\" content=\"org.apache.tika.parser.CompositeParser\" />\n<meta name=\"X-Parsed-By\" content=\"org.apache.tika.parser.recognition.ObjectRecognitionParser\" />\n<meta name=\"OBJECT\" content=\"lion (0.93754)\" />\n<meta name=\"Content-Type\" content=\"image/jpeg\" />\n<title></title>\n\n
\t
 lion [en](confidence = 0.937544)
\n
\n",
        "X-TIKA:parse_time_millis": "1086",
        "org.apache.tika.parser.recognition.object.rec.impl": "org.apache.tika.dl.imagerec.DL4JInceptionV3Net"
    }
]


add support for tailwind-merge

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #2566

PR #2567

PR #1772

PR #1895

PR #1777

PR #2549

PR #2568   👈
PR #2550

PR #2551

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: lD3buYhoj2XN6gyFTJN3


Cannot install xmlrpc on Mac BigSur with python 3.8.6

✗ pkg-config --cflags xmlsec1
-D__XMLSEC_FUNCTION__=__func__ -DXMLSEC_NO_SIZE_T -DXMLSEC_NO_GOST=1 -DXMLSEC_NO_GOST2012=1 -DXMLSEC_NO_CRYPTO_DYNAMIC_LOADING=1 -DXMLSEC_CRYPTO_OPENSSL=1 -I/usr/local/Cellar/libxml2/2.9.10_2/include/libxml2 -I/usr/local/Cellar/libxmlsec1/1.2.32/include/xmlsec1<EMAIL_ADDRESS><EMAIL_ADDRESS>
 ✗ pip install xmlsec
Collecting xmlsec
  Using cached xmlsec-1.3.9.tar.gz (62 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
    Preparing wheel metadata ... done
Requirement already satisfied: lxml>=3.8 in /Users/slysenko/.pyenv/versions/3.8.6/lib/python3.8/site-packages (from xmlsec) (4.6.3)
Building wheels for collected packages: xmlsec
  Building wheel for xmlsec (PEP 517) ... error
  ERROR: Command errored out with exit status 1:
   command: /Users/slysenko/.pyenv/versions/3.8.6/bin/python3.8 /Users/slysenko/.pyenv/versions/3.8.6/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py build_wheel /var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/tmp72ud_82q
       cwd: /private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-install-eocity2i/xmlsec_6b9b499ff62c45b3871ae6c495b2cc34
  Complete output (51 lines):
  running bdist_wheel
  running build
  running build_py
  /private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-build-env-9voggw_z/overlay/lib/python3.8/site-packages/setuptools/dist.py:642: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
    warnings.warn(
  /private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-build-env-9voggw_z/overlay/lib/python3.8/site-packages/setuptools/dist.py:642: UserWarning: Usage of dash-separated 'build-requires' will not be supported in future versions. Please use the underscore name 'build_requires' instead
    warnings.warn(
  /private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-build-env-9voggw_z/overlay/lib/python3.8/site-packages/setuptools/dist.py:642: UserWarning: Usage of dash-separated 'upload-dir' will not be supported in future versions. Please use the underscore name 'upload_dir' instead
    warnings.warn(
  package init file 'src/xmlsec/__init__.py' not found (or not a regular file)
  creating build
  creating build/lib.macosx-11.2-x86_64-3.8
  creating build/lib.macosx-11.2-x86_64-3.8/xmlsec
  copying src/xmlsec/py.typed -> build/lib.macosx-11.2-x86_64-3.8/xmlsec
  copying src/xmlsec/tree.pyi -> build/lib.macosx-11.2-x86_64-3.8/xmlsec
  copying src/xmlsec/__init__.pyi -> build/lib.macosx-11.2-x86_64-3.8/xmlsec
  copying src/xmlsec/constants.pyi -> build/lib.macosx-11.2-x86_64-3.8/xmlsec
  copying src/xmlsec/template.pyi -> build/lib.macosx-11.2-x86_64-3.8/xmlsec
  running build_ext
  building 'xmlsec' extension
  creating build/temp.macosx-11.2-x86_64-3.8
  creating build/temp.macosx-11.2-x86_64-3.8/private
  creating build/temp.macosx-11.2-x86_64-3.8/private/var
  creating build/temp.macosx-11.2-x86_64-3.8/private/var/folders
  creating build/temp.macosx-11.2-x86_64-3.8/private/var/folders/yr
  creating build/temp.macosx-11.2-x86_64-3.8/private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp
  creating build/temp.macosx-11.2-x86_64-3.8/private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T
  creating build/temp.macosx-11.2-x86_64-3.8/private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-install-eocity2i
  creating build/temp.macosx-11.2-x86_64-3.8/private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-install-eocity2i/xmlsec_6b9b499ff62c45b3871ae6c495b2cc34
  creating build/temp.macosx-11.2-x86_64-3.8/private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-install-eocity2i/xmlsec_6b9b499ff62c45b3871ae6c495b2cc34/src
  clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include -I/usr/local/opt/libxml2/include -D__XMLSEC_FUNCTION__=__func__ -DXMLSEC_NO_SIZE_T -DXMLSEC_NO_GOST=1 -DXMLSEC_NO_GOST2012=1 -DXMLSEC_NO_CRYPTO_DYNAMIC_LOADING=1 -DXMLSEC_CRYPTO_OPENSSL=1 -DMODULE_NAME=xmlsec -DMODULE_VERSION=1.3.9 -I/usr/local/Cellar/libxml2/2.9.10_2/include/libxml2 -I/usr/local/Cellar/libxmlsec1/1.2.32/include/xmlsec1<EMAIL_ADDRESS><EMAIL_ADDRESS>-I/private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-build-env-9voggw_z/normal/lib/python3.8/site-packages/lxml/includes -I/private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-build-env-9voggw_z/normal/lib/python3.8/site-packages/lxml -I/private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-build-env-9voggw_z/normal/lib/python3.8/site-packages/lxml/includes/libxml -I/private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-build-env-9voggw_z/normal/lib/python3.8/site-packages/lxml/includes/libxslt -I/private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-build-env-9voggw_z/normal/lib/python3.8/site-packages/lxml/includes/libexslt -I/private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-build-env-9voggw_z/normal/lib/python3.8/site-packages/lxml/includes/__pycache__ -I/Users/slysenko/.pyenv/versions/3.8.6/include/python3.8 -c /private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-install-eocity2i/xmlsec_6b9b499ff62c45b3871ae6c495b2cc34/src/constants.c -o build/temp.macosx-11.2-x86_64-3.8/private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-install-eocity2i/xmlsec_6b9b499ff62c45b3871ae6c495b2cc34/src/constants.o -g -std=c99 -fPIC -fno-strict-aliasing -Wno-error=declaration-after-statement -Werror=implicit-function-declaration -Os
  /private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-install-eocity2i/xmlsec_6b9b499ff62c45b3871ae6c495b2cc34/src/constants.c:321:5: error: use of undeclared identifier 'xmlSecXkmsNs'
      PYXMLSEC_ADD_NS_CONSTANT(XkmsNs, "XKMS");
      ^
  /private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-install-eocity2i/xmlsec_6b9b499ff62c45b3871ae6c495b2cc34/src/constants.c:311:45: note: expanded from macro 'PYXMLSEC_ADD_NS_CONSTANT'
      tmp = PyString_FromString((const char*)(JOIN(xmlSec, name))); \
                                              ^
  /private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-install-eocity2i/xmlsec_6b9b499ff62c45b3871ae6c495b2cc34/src/common.h:19:19: note: expanded from macro 'JOIN'
  #define JOIN(X,Y) DO_JOIN1(X,Y)
                    ^
  /private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-install-eocity2i/xmlsec_6b9b499ff62c45b3871ae6c495b2cc34/src/common.h:20:23: note: expanded from macro 'DO_JOIN1'
  #define DO_JOIN1(X,Y) DO_JOIN2(X,Y)
                        ^
  /private/var/folders/yr/b4_dyc6s0l74d73fbrqk9h9w0000gp/T/pip-install-eocity2i/xmlsec_6b9b499ff62c45b3871ae6c495b2cc34/src/common.h:21:23: note: expanded from macro 'DO_JOIN2'
  #define DO_JOIN2(X,Y) X##Y
                        ^
  <scratch space>:12:1: note: expanded from here
  xmlSecXkmsNs
  ^
  1 error generated.
  error: command 'clang' failed with exit status 1
  ----------------------------------------
  ERROR: Failed building wheel for xmlsec
Failed to build xmlsec
ERROR: Could not build wheels for xmlsec which use PEP 517 and cannot be installed directly

libxml2-2.9.10_2
libxmlsec1--1.2.32
pkg-config--0.29.2_3

Suggest to remove XKMS support because it was removed from xmlsec library many years ago https://github.com/lsh123/xmlsec/blob/master/ChangeLog#L69-L70

I could confirm the same issue with Catalina and latest xmlsec version, proposed workaround fixes it.

A new version 1.3.10 is released that has this issue fixed. Kudos to @Roman513 for the contribution!