Add muscle terms

This PR add terms for somatic muscles, where “muscle” is to be understood as representing the entire anatomical structure made of both actual muscle cells and the associated tendon cells.
Having proper terms for muscles, instead of terms for muscle cells only, is among other things needed for the fly anatomograms, for which a technical requirement is that cells must always be part_of a precise anatomical structure. This will also increase consistency with the Uberon and CL cross-species ontologies (even though for now Uberon itself is not entirely consistent in its way of representing muscles, see obophenotype/uberon#2350 for how this will be fixed).
In details, this PR:

adds somatic muscle, as the root of the entire hierarchy of somatic muscle terms;
for each descendant of somatic muscle cell, create a corresponding muscle term and make the cell term a part_of the newly added muscle term.

The definitions for the new muscle terms are taken from the old definitions of the cell terms, before those were updated last year when we renamed all muscle cell terms to better indicate that they were about cells and not the muscle themselves.
When muscle cell terms have part_of, attached_to, attached_to_part_of, capable_of_part_of relationships, those relationships are moved over to the corresponding muscle terms. has_characteristic, overlaps, and receives_synaptic_input_from_neuron relationships are copied over to the corresponding muscle terms, but also left to the cell terms. Other relationships (expresses, develops_from) are left to the cell terms only.
related to #1128

There still seem to be 'attached to' relationships in EquivalentTo axioms on some of the cell terms

(above would also apply to grouping terms like 'adult pharynx muscle cell')

Yes, when I mentioned the attached_to relationships, I only meant the relationships that are not part of logical definitions (so SubClassOf, not EquivalentTo). I have left all logical definitions untouched.
I agree with the idea of logically defining all muscle cell terms in terms of 'muscle cell' part_of some <corresponding muscle>.

If we do define all somatic muscle cells as 'muscle cell' and (part_of some '<muscle X>'), I think we should also re-define somatic muscle cell as 'muscle cell' and (part_of some 'somatic muscle'), so that all somatic muscle cells are automatically classified as such.
The alternative would be to define individual muscle cells as 'somatic muscle cell' and (part_of some '<muscle X>'), but automatic classification seems more logical to me.

Yes, all should follow the same pattern (would be nice to properly patternise this with DOSDP at some point).

FBbt:00058859 and FBbt:00058955 have labels beginning with 'a ', which isn't good. Can also be removed from respective cell type terms.
Also 'midgut muscle' and 'foregut muscle' are missing 'cell' from the label.
I am wondering if it would be better to just auto-generate the cell definitions (i.e. replace with ".", so they will become "any muscle cell that is part of some .") and keep the more detailed definitions on the muscle terms. Some of them currently read a bit awkwardly (especially where there is more than one sentence).
I also see a lot of cases where we have unnecessary grouping classes (only one child exists) and that problem will now be doubled, but I think maybe that is not a problem to be solved today.
Otherwise this is looking pretty good now, the hierarchy of muscle cells looks nice.

Also 'midgut muscle' and 'foregut muscle' are missing 'cell' from the label.

Those were missed during last year’s mass renaming of muscle to muscle cell – I’ll fix them now.

I am wondering if it would be better to just auto-generate the cell definitions (i.e. replace with ".", so they will become "any muscle cell that is part of some .") and keep the more detailed definitions on the muscle terms. Some of them currently read a bit awkwardly (especially where there is more than one sentence).

I agree. The original definitions were written as if they were about the muscles, not the cells. Turning them into definitions about cells (by adding “Muscle cell of…” or similar at the beginning) was bound to give sometimes imperfect results.
All the original definitions are now carried by the muscle terms, so we wouldn’t lose any information by removing the definitions on the cell terms. If you agree with that I’ll do it in this PR.

I also see a lot of cases where we have unnecessary grouping classes (only one child exists) and that problem will now be doubled, but I think maybe that is not a problem to be solved today.

Another problem that was left untouched for now is about the synonyms. Some of the synonyms that are carried by the cell terms should either be amended or transferred to the corresponding muscle term.
For example, if we take lunula muscle cell (which is now part of some lunula muscle), it has an EXACT synonym lunular muscle – this is no longer exact. We should either rename the synonym to lunular muscle cell, or move it to the lunula muscle term (or even do both).
I was planning to leave that for a future PR.

Looks good to me now (except for synonym and redundant term issues to fix later).


Adding few shot example for language generation

@wannaphong maybe good to add an example for training language generation in the notebook?

Are you mean Text Generation?

Yes, I think adding a text generation script to notebooks with few-shot learning would be a good example.

OK, I added a text generation notebook.
https://github.com/PyThaiNLP/padthai/blob/main/notebooks/text_generation.ipynb

Looks great! Close this issue!


Slack is down. Do we have a better way to communicate?

keralarescue.slack.com is no longer accessible, and the slack status page says they are having problems. If there is a different way to communicate, please list on this issue.

Yeah, slack failed at most required time. Let use IRC

Flock is an alternative for slack
'https://flock.com'

irc will be fine

+1 for IRC #keralarescue?

Telegram would be fine right ?

Telegram ?

Will suit our purpose. Lets hope slack will be online soon

@biswaz can you tell me wts the issue with slack I can help you with that.

It's their server issue

https://webchat.freenode.net/?url=irc://irc.freenode.net/keralarescue

There is no issue with their server. Because I am using slack now too.

I registered a channel #keralarescue in freenode. Let's use that for till slack comes back.

slack is back up

@jishnunand your location?

Slack is Active now. I'm closing this Issue

Great, Slack is back 👍

Bangalore

Check this 'https://status.slack.com' @jishnunand

@biswaz can you invite me to keralarescue.slack.com channel?
<EMAIL_ADDRESS>

I can't create an account on slack. Any help is appreciated.


CDN Errors on "Launch and Manage Your Site" Page

WEB PART NOT LOADING: If you are getting the error: "Microsoft 365 learning pathways has a configuration issue. Ask your administrator for assistance". Please review the Diagnosing Pre-Check guidance before submitting your bug.

Describe the bug
Receiving "Microsoft 365 learning pathways has a configuration issue" error when loading the "Launch and Manage Your Site" page.  Provisioning went okay but this is the first error I found.  Seems to be related to the CDN in some way.  I'm not very familiar with how that works, other than what a CDN is.
To Reproduce
Attempt to load the "Launch and Manage Your Site" page.
Expected behavior
Not sure!  I've never been able to load the page.
Screenshots
LandM Error

Learning Pathways version number
I just installed it today.  Unfortunately I'd have to get our tenant admin to look at the version - I'm prevented from seeing it in Azure.
Additional context
Browser Dev Logs:
custbank.sharepoint.com-1611936235889 - all.log
custbank.sharepoint.com-1611936201389 - errors.log

First try to go to the CustomLearningAdmin.aspx page first. If you provision from the provisioning service, the page is linked under the Home menu -> Learning pathways administration.
See if that loads correct, if it does that I think you're probably all set.

First try to go to the CustomLearningAdmin.aspx page first. If you provision from the provisioning service, the page is linked under the Home menu -> Learning pathways administration.
See if that loads correct, if it does that I think you're probably all set.

Hi Julie,
I went to the admin page but I'm getting the same error.  It has a slightly different URL than you described, "Success-site-administration.aspx" but I'm pretty sure I'm in the right place.  Is there something else I can try, as a next step?

Hi Julie,
I went to the admin page but I'm getting the same error.  It has a slightly different URL than you described, "Success-site-administration.aspx" but I'm pretty sure I'm in the right place.  Is there something else I can try, as a next step?

Sorry, I didn't understand that you were talking about the SharePoint Sucess site not Learning pathways site, my directions were based on the learning pathways site.
Anyway, watch this video to see what the process is for deploying the SharePoint success site, I believe you skipped the last step which is to add the content pack to learning pathways administration.

Sorry, I didn't understand that you were talking about the SharePoint Sucess site not Learning pathways site, my directions were based on the learning pathways site.
Anyway, watch this video to see what the process is for deploying the SharePoint success site, I believe you skipped the last step which is to add the content pack to learning pathways administration.

Ah, that was it!  I forgot to go back to Learning Pathways and click “Complete”. Thanks for the help!

Ah, that was it!  I forgot to go back to Learning Pathways and click “Complete”. Thanks for the help!


Docs: Action button of sponsor section overlapping with the vertical background lines

Documentation is

[ ] Missing
[ ] Outdated
[ ] Confusing
[ ] Not sure?

Explain in Detail
On the Landing Page, at the end of the Sponsors Section, in the Sponsor Actions, the action button saying 'Become a Sponsor' overlaps with the element with lines effect in the background. It creates a visual inconsistency, making the text appear distorted. It is appears on large screens.
Your Suggestion for Changes
Make the button background opaque (if it already isn't) and raise the z-index level to be more than that of the lines element
Reproduction
No response
Steps to reproduce

Go to https://vite.dev/
Go to the section saying 'Free & open source'
Notice the action button saying 'Become a Sponsor'

I wasn't able to reproduce it. I guess you're using adblock or something else that removes some elements and that is causing that.

Perhaps related to this? https://github.com/vitejs/vite/pull/18547


Stash/Bitbucket server documentation should add DRONE_STASH_CONSUMER_RSA_STRING

The docs for the Stash/Bitbucket Server documentation should be modified to add
DRONE_STASH_CONSUMER_RSA_STRING
Bitbucket Server oauth1 private key file as string value used if DRONE_STASH_CONSUMER_RSA is not provided

PR in the Docs repo - https://github.com/drone/docs/pull/210


Skidded lmao

This script isn’t urs its from .gg/termed the owner made it
You told me on a call u know python and look at this 😆

LMAOOOO

Nigga what??? Who are you 1 and 2 I do know python look at my other repos why would I skid like 16 lines of code.

Yes I do have proof just look at the credits page and use common sense


Add raichu card

Added a card for raichu

I request you to make a PR again and please read the code thoroughly. You actually added the card in middle of another card which broke the website. Also, do use an image thats similar in size to the other images. If you use images too large, it would not be possible to accomodate them properly

I just checked the code in my pr and I didn't add my code between another card.  It was another pr that broke it. But I will fix the issue anyway 👍

I just checked the code in my pr and I didn't add my code between another card.  It was another pr that broke it. But I will fix the issue anyway 👍

Sorry, my bad. I messsed up the merging order.  Please make another PR. Sorry for the inconvenience.

no problem, I have fixed the issue, I will make pr now :-)


Update: dragged to the last

Hi @tam11a Thanks for adding your portfolio. However, the screenshot is quite large (~1MB). We have a lot of images in the repo, so we try to make them as low in size as possible.
Kindly compress it using compressnow or tinypng, and then reupload.
Thanks for your understanding :)

Compressed the picture on my repository. Thanks @israelmitolu

Hi @tam11a Thanks for adding your portfolio. However, the screenshot is quite large (~1MB). We have a lot of images in the repo, so we try to make them as low in size as possible.
Kindly compress it using compressnow or tinypng, and then reupload.
Thanks for your understanding :)

Compressed the picture on my repository. Thanks @israelmitolu

The picture doesn't exist on your repository anymore. If you need more help, you can follow the steps in the guideline
For now, I'll go ahead to merge your PR and add the picture.
Thanks again for adding your portfolio!


RI-520 Update Pike Dependencies in Master

I think the Octavia gate is deploying pike from master and is using the
wrong version of rpc-maas.  This updates the SHAs in master to reflect
those in pike.
Issue: RI-520
Issue: RI-520

Thank you for submitting a pull request to this project!
Once all check jobs have passed and the pull request has received a
sufficient number of reviews, the repository's gate jobs can be triggered by
adding a comment of :shipit: to this pull request.
When the gate jobs have completed successfully, this pull request will get
merged automatically.

Yeah, that's what I thought, but I was unaware of that card.  I agree, and I think we should remove or at least comment out the single branch deployment tooling until/if we decide to use it.

@d34dh0r53 My vote would be to remove. There is no point in carrying unused code, commented or not. All it does is confuse everyone, just like this has right from the start.


Add instructions to add ballerina executable to path - for zip users

To avoid problems with VSCode extension trying to auto detect the distribution path or user trying to configure ballerina.home setting,
We should ask all zip users to create an link in /usr/local/bin (on unix) or add Ballerina executable to PATH somehow.

Moved to https://github.com/wso2/ballerina-plugin-vscode/issues/24


Feature: Add folders in studio

As per recommendation from @pofider in issue #11
Would it be possible to add ability to organize templates (and other items, scripts, data, etc, etc) in foders?
Often I have same "logical" report but it has 3-4 different templates with different layouts and recipes
Having a folder where I can group templates per report would make it easier to organize things...
Having a flat list makes it difficult to navigate when there is a lot of reports...
Thanks
Z!

Thinking if we will go the folders way or tag/labels way.
The tags/labels give us probably more powerful and flexible solution:

User can create a custom tag and label the entities.
User can filter the entity tree panels by tags
User can filter the entity tree with standard tags like give me entities with particular recipe or with particular script

The downside is that visual user experience with labels is probably not so good as with folders. You get just raw list in which you need to filter.
I'll have to give it some more thoughts, every suggestion is welcome.

Folders would give you hierarchical organization.
Tags/labels are more "taxonomy" oriented.
And with labels, as you mention, you still have (initially) a long list to contend with.
I imagine as the number of items in thee grows, folders would help with faster loading (expand on AJAX request) instead of loading everything...
But I like labels idea also.
Can we have both? :)

The implementation will have impact on several extensions, so I moved it to the main repo.
https://github.com/jsreport/jsreport/issues/250


Stuck at this screen

New to Wine, sorry if this seems like an ignorant issue!

Hey @scordd ... Here is the solution for your problem: https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux/issues/124 :+1:


Sort log output by line then column

All warnings are output in order of detekt provider type. They should be logged in order: by line, then column. This makes it easier to review the list of issues detekt finds.

This issue is stale because it has been open 90 days with no activity. Please comment or this will be closed in 7 days.

This issue was closed because it has been stalled for 7 days with no activity.

This one should be a really easy one. And once #6884 is merged it will be even simplier. All the changes should be done in MessageCollectorExtensions. The "more complex" part is to write the tests to ensure that it works.
As a side note, probably sort by textChar is easier here and will provide exactly the same effect.

*Working on this


Defining styles resets complete default structurizr style

I really like the default styling when exporting a dsl file to structurizr plantuml format. What I would like to do now is to easily add icons for certain element types (tags) but keep the rest. Using styles and the themes (did not try it yet) I can easily add icons and other style information.
But when styles is being used in a dsl then automatically all styling is gone/reset. My proposal would be that there should be a switch whether using styles in a dsl resets the complete styling or the given default styles should just override the specific style settings.
As a workaround getting the complete default styling to be added to the dsl and changing it where required would also be fine.

Yes, the default styles are only added to the workspace when no styles are present. The set of default styles are listed here though, so you can easily add them into your DSL file -> https://github.com/structurizr/cli/blob/master/docs/defaults.md#styles
The theme support in the Structurizr render allows you to define a basic set of styles as a theme, and override them at the workspace level ... but I have a feeling that it doesn't work like that for the PlantUML exports.

Thanks for the fast answer. I still do have two small questions and then we could also close this issue from my point of view since the workaround is really simple.

Regarding themes: When you say "override" you mean the complete style of the related element is overwritten or just the part that has been defined in the workspace?
"but I have a feeling that it doesn't work like that for the PlantUML exports." You mean all of the Plantuml formats including the default plantuml/structurizr format? This only works when uploading to the structurizr server?

Just the part of the style defined in the workspace. For example:

I just checked, and this functionality is not supported with any of the exports (PlantUML, Mermaid, etc) - it's only supported with the Structurizr renderer at the moment.

Ok, thank you. Feel free to close this issue. It would be nice though to add your comments to my questions to the official docs so that it is clear how styles and themes work.
Ideally a small pseudo algorithm how styles are applied would be very nice.
e.g. If no style then default style is applied, if styles are used then no default style is used at all.
If themes are used with styles then...
Nevertheless I got the information I was seeking so I will close the issue. Thank you.

Will do. Just to confirm though:

which "official docs" are you referring to?
what do you feel is missing?

At the moment, here are the docs pointed to by the DSL language reference:

Structurizr - Notation
Structurizr - Themes


problemMatcher: location always shows (line,col) format

VSCode Version:

Version 1.20.0
Commit c63189deaa8e620f650cc28792b8f5f3363f2c5b
Date 2018-02-07T17:10:31.920Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture ia32
OS Version:

Using a custom problemMatcher, in the "Problems" window, location is always shown as (line,col) format, even when the location match group only contains a single number.
I'm currently building MASM assembly code in VSCode and decided to create a custom problemMatcher to match the error output of ml.exe. Some example errors are formatted as such:
AW4.asm(25) : error A2008: syntax error : someVariable
AW4.asm(24) : error A2071: initializer magnitude too large for specified size
AW4.asm(24) : error A2206: missing operator in expression

My problemMatcher is as follows:
"problemMatcher": {
                "owner": "masm",
                "fileLocation": ["relative", "${workspaceFolder}"],
                "pattern": {
                    "regexp": "^(.*)\\((\\d+)\\)\\s+:?\\s+(error|warning)\\s+([A-z]+\\d+):\\s+(.*)$",
                    "file": 1,
                    "location": 2,
                    "severity": 3,
                    "code": 4,
                    "message": 5,
                    "loop": true
                }
            }

Notice the 2nd match group is a number matching the line of code where the error occurred. There is no comma, so the format used by location should be (line). However, it still defaults to (line,column) format (and arbitrarily chooses 5 as a column) as seen here:

If I hover over location, the description reads:
"The match group index of the problem's location. Valid location patterns are: (line), (line,column) and (startLine,startColumn,endLine,endColumn). If omitted (line,column) is assumed."

Does this issue occur when all extensions are disabled?: Yes
I've attached my tasks.json.
Please let me know if you need any more info, or if I'm just doing something wrong...
P.S.: I'm really loving VSCode and I use it every day, so thanks for all your hard work.
tasks.json.txt

@ozyx can you let me know how the lines look like that have and error. If not column is specified we try to use the first non space character as the column. Your matcher is correct in that sense.


Please don't let this die. ElastAlert usecase is very strong.

Sorry for being repetitive but I wanted to emphasize this.
@Qmando I've heard you are divorcing with the project, so that wanted to ask you to not let this gem of a software simply die.
Usecase for ElastAlert is pretty unique and it stands well in the ELK ecosystem as an open source alternative to licensed Elastic alerting features. Moreover, the functionality is way way richer than what Elastic guys have under the hood as of August 2020.
You did a great job with building and maintaining it, now please hand it over to someone who deserves.
Cheers!

I'm the maintainer of the following ElastAlert related tools.
I am also interested in future trends of ElastAlert.
However, I think it is difficult to give a clear answer at this point.
ElastAlert Server・・・forked from ServerCentral/elastalert-server
https://github.com/johnsusek/elastalert-server
ElastAlert Kibana Plugin・・・forked from bitsensor/elastalert-kibana-plugin
https://github.com/nsano-rururu/elastalert-kibana-plugin
Praeco
https://github.com/johnsusek/praeco

Hi @nsano-rururu ,
I would like to know:

I have never used Docker before. Does this work like a VM inside Linux?
Would Praeco do the same work (or similar) that ElastAlert Kibana Plugin does?
I have Nginx running on the same server where I would install Praeco. Would that be an issue or create a conflict with other apps needing Nginx in the server.

Thank you

I think that @nsano-rururu should be made an admin on this project (if you agree!), as he seems to be active on the dev side!
@Qmando, that would be great to grant the admin rights to other devs, as the development of this project could continue!

Hi. Sorry that this has remained dormant for quite a while and the PR/issues have gotten completely out of hand.
We do plan on handing the project over to new maintainers, stay tuned. I'll try to get that ball rolling on that before the end of the year.

@mrfroggg we already have a Gitter channel for the same: https://gitter.im/Yelp/elastalert

It's true that there are too many unresolved issues and it's difficult to see them all. I'm pretty tired just looking at a part of it.
travis-ci

Issue
Remarks

travis-ci.org will be completely closed by December 31, 2020, so you need to move to travis-ci.com #3018

document

Issue
Remarks

The contents of Read the Docs is old #3002

Elasticsearch 7.x / 8.x

Issue
Remarks

doc_type is deprecated and will be removed in ES 8

Removal of doc_type #2523

doc_type is no longer supported in ES > 7.x , however use_count_query and use_terms_query still check for it #2424

Office 365

Issue
Remarks

Elastalert send to SMTP Office 365 relay with SSL/TLS #2449

Issue with TLS 1.2 #2357

bug

Issue
Pull Request
Remarks

Is the module "cffi" used in ElastAlert? #3008
https://github.com/Yelp/elastalert/pull/3009

Is the module "configparser" used in ElastAlert? #3007
https://github.com/Yelp/elastalert/pull/3010

Seems to forget to document slack_ca_certs #3003
https://github.com/Yelp/elastalert/pull/3004

blist no longer works in Python 3.9 #2983

Need to change blist to another library when supporting Python 3.9

Only timezones from the pytz library are supported #2968
https://github.com/Yelp/elastalert/pull/3013
APScheduler has a problem that it does not work properly when tzlocal is set to 3.0b1.

Error on loading yaml because of incorrect dependency version (PyYAML)
https://github.com/Yelp/elastalert/pull/3000

Slack SSL Verification Disabled by Default #2955
https://github.com/Yelp/elastalert/pull/2760

ERROR:root:Error writing alert info to Elasticsearch: RequestError(400, 'mapper_parsing_exception', "failed to parse field [match_body.weblog.body_bytes_sent] of type [long] in document with id 'iiC6m3MBDLealW5s7dvq'") #2899
https://github.com/Yelp/elastalert/pull/3016
Addressed Elasticsearh 6.x issues. 7. Is the effect of x unconfirmed?

Disabled rule can't be returned after deletion #2893

InsecureRequestWarning: #2856

bug repport?

No matching distribution found for elastalert==0.2.1 #2748

Is elastalert 0.2.1 released on pypi?

[Bug report] Some codes are missing when python pip download #2660

[Bug report] Multiple queries after adding new rule #2659

While installing I am facing this Issue #2652

Problems with windows environment only?

Zabbix alert module error #2621
#2818 #2794 #2640

What's about jira lib? #2610
https://github.com/Yelp/elastalert/pull/2676

Error when using alert type command: "ResourceWarning: subprocess NNN is still running" [bug] #2587

PagerTree not mapped loaders.py #2571
https://github.com/Yelp/elastalert/pull/2934

Issue in elastalert.py #2556
https://github.com/Yelp/elastalert/pull/2991

Line notify is missing #2516
https://github.com/Yelp/elastalert/pull/2783

@Qmando I understand that the project may be too big for a single maintainer to keep working on (even harder if its just a part-time work). It'll be better if you can assign ownership to more than one person (who is active on the project) so as the issues are resolved & addressed quickly and a single person doesn't become a bottleneck for the same.

@Qmando
I think it will work if multiple maintainers work in their respective fields of expertise.
I want to be the ElastAlert maintainer. Please give me authority.
I can handle problem investigation, bug fix, operation check, document fix, issue organization (completion, labeling), and docker related questions.
For example, it is a fix of the problem that an error occurs in the test rule when the version of elasticsearch-py below is increased. Fix it as follows.
test_rules.py
Line86
res = es_client.search(index, size=1, body=query, ignore_unavailable=True)
↓
res = es_client.search(index=index, size=1, body=query, ignore_unavailable=True)
Line112
res = es_client.count(index, doc_type=doc_type, body=count_query, ignore_unavailable=True)
↓
res = es_client.count(index=index, doc_type=doc_type, body=count_query, ignore_unavailable=True)
Line 156
res = es_client.search(index, size=args.max_query_size, body=query, ignore_unavailable=True)
↓
res = es_client.search(index=index, size=args.max_query_size, body=query, ignore_unavailable=True)

I'm really interested in how the maintenance handover or involvement turns out, it's almost EOY (https://github.com/Yelp/elastalert/issues/2947#issuecomment-716822515), and @nsano-rururu seems to be all over into EA based on his Github activity across multiple projects, so I think it would be in good hands.
Reference for other similar issues without existing connection to this one: https://github.com/Yelp/elastalert/issues/2946,  https://github.com/Yelp/elastalert/issues/2911

@Qmando
It's a reminder. Don't forget to do the following.

Hi. Sorry that this has remained dormant for quite a while and the PR/issues have gotten completely out of hand.
We do plan on handing the project over to new maintainers, stay tuned. I'll try to get that ball rolling on that before the end of the year.

@Qmando
Anyone can take over the maintainer to anyone who @Qmando wants to take over? .. Many people are in trouble.

There are still a few days until the year ends, let's hope for the best.

@nsano-rururu I also believe strongly in this project and would be willing to be a maintainer/contributor

@Qmando
Didn't you take any action by today?
Was it a lie?

Hi. Sorry that this has remained dormant for quite a while and the PR/issues have gotten completely out of hand.
We do plan on handing the project over to new maintainers, stay tuned. I'll try to get that ball rolling on that before the end of the year.

I think we have 2 options:

Check with Yelp (Github root of this project) to add new maintainers to Elastalert
If no answer from Yelp, create an official fork to continue Elastalert's development on another github repo.

I think we should wait until next week as most employees are on vacation during this time. I agree with @mrfroggg on both options.

@mrfroggg @devdua
I will stop being involved in this matter.
Develop with your own forked repository.
All 30 pull requests to ElastAlert have been closed.

@mrfroggg @devdua
I will stop being involved in this matter.
Develop with your own forked repository.
All 30 pull requests to ElastAlert have been closed.

As much as I would like somebody to take over active development of ElastAlert, I think the current situation and way of communication leaves a bad taste, it's just not that professional as it could be, almost hostile. I understand the accumulated frustration here but we shouldn't give up maintaining a communication style that is not harmful for other human beings and the project itself. What @mrfroggg suggested, is totally reasonable, we either ask the team behind the project (nicely) that here are some devs that are worthy of being new maintainers, or just create an official fork, and merge the PRs there, comment on all issues that reopen them there, etc.

As much as I would like somebody to take over active development of ElastAlert, I think the current situation and way of communication leaves a bad taste, it's just not that professional as it could be, almost hostile. I understand the accumulated frustration here but we shouldn't give up maintaining a communication style that is not harmful for other human beings and the project itself. What @mrfroggg suggested, is totally reasonable, we either ask the team behind the project (nicely) that here are some devs that are worthy of being new maintainers, or just create an official fork, and merge the PRs there, comment on all issues that reopen them there, etc.

Hi @Qmando, Happy New Year! Is there a plan to hand over this project?

Hi @Qmando, Happy New Year! Is there a plan to hand over this project?

I looked around and I have no idea who to contact @ Yelp.
I saw that there is a try to create an official Fork, and many PR were commited so far:
https://github.com/jertel/elastalert

I looked around and I have no idea who to contact @ Yelp.
I saw that there is a try to create an official Fork, and many PR were commited so far:
https://github.com/jertel/elastalert

Hi @Qmando I wonder whether there are some updates? This is a very helpful and useful project!

Hi @Qmando I wonder whether there are some updates? This is a very helpful and useful project!

I think we need to as a community move the project on. It has been over two months since Qmando last replied.

+1 This is a wonderful project!

If you're trying to use the ability to hand over a GitHub repository to another owner or organization, you should be able to do that by working with GitHub.
https://docs.github.com/en/github/administering-a-repository/transferring-a-repository

In the meanwhile I have just been using Nsano-rururu's fork as he has been doing amazing work there and merged all the outstanding pull's and even the documentation . Thanks by the way.
https://github.com/nsano-rururu/elastalert

People can follow on this discussion here to pitch in their opinions about an official fork and the process of it: https://github.com/jertel/elastalert/discussions/77

@markus-nclose
https://github.com/nsano-rururu/elastalert has been removed. Please use the following elastalert2 in the future.
https://github.com/jertel/elastalert2

It just feels sad to see the laid-back response from official authors. This is a gem of a project, but it's disappointing to see how it's being handled :(

@Qmando
If there is a demand for people who want to use what yelp has officially decided to take over, I think it's a good idea to donate the current project to the Apache Software Foundation.


multi: readonly and admin macaroon session

part of https://github.com/lightninglabs/lightning-node-connect/issues/17
depends on https://github.com/lightninglabs/lightning-node-connect/pull/26

With this PR, we can create a admin or readonly macaroon session type. This bakes a macaroon for a session and adds it to the Noise authData payload so the client can use the mac to authorise requests instead of just the UI password.
After this is in, the UI can start defaulting to creating a readonly session and can add an option for the user to select that they want to create an admin session. Once that is done (ie, there is no way to create a UIPassword session anymore), we can add a DB migration diff that downgrades all existing UIPassword sessions to Readonly sessions

@guggero , i have updated this to include the readonly session type. I think the DB migration diff should be in a separate PR after the UI changes that allow you to pick a session type have been done.

Thanks for the review! I have updated accordingly and went for "at bake time" approach.

Ah, we also discussed adding a DB migration to the session DB to migrate over any existing UI password sessions to admin macaroon ones. But I don't think we can do that just yet, since first we need a way to make the super macaroon work with remote faraday/loop/pool. I have an idea of how to do that, can discuss it offline.

@roasbeef: review reminder

@roasbeef: review reminder

@ellemouton, remember to re-request review from reviewers when ready

@ellemouton, remember to re-request review from reviewers when ready

@ellemouton, remember to re-request review from reviewers when ready

!lightninglabs-deploy mute

muting this until the dependent PRs are complete. (should probably add an option to lbot so that it can depend on prs outside of the current repo)

I have pushed a new version based on the latest dynamic auth pr & addressed some of the comments in the previous review. Note that for testing: LNC on the client must be updated to the dynamic auth version

hmmm what 4 byte id do we want to give the in memory super mac? a fixed one or can we just randomly generate?

This is ready for re-review now that https://github.com/lightninglabs/lightning-node-connect/pull/27 is in 👍


Add support for non-ellipsis open date windows

STAC Pydantic currently supports open datetime windows with ellipsis ("DATETIME/.." or "../DATETIME") but it appears as though it ought to also support datetimes with non-ellipsis open windows. Such windows have the form "/DATETIME" or "DATETIME/" This PR corrects that oversight.

Codecov Report

Merging #103 (e90090c) into master (d222206) will decrease coverage by 0.16%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #103      +/-   ##
==========================================
- Coverage   96.38%   96.21%   -0.17%
==========================================
  Files          19       20       +1
  Lines         442      476      +34
==========================================
+ Hits          426      458      +32
- Misses         16       18       +2

Flag
Coverage Δ

unittests
96.21% <100.00%> (-0.17%)
:arrow_down:

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

Impacted Files
Coverage Δ

stac_pydantic/api/search.py
96.29% <100.00%> (+1.05%)
:arrow_up:

stac_pydantic/links.py
98.21% <0.00%> (-1.79%)
:arrow_down:

stac_pydantic/api/landing.py
100.00% <0.00%> (ø)

stac_pydantic/api/__init__.py
100.00% <0.00%> (ø)

stac_pydantic/api/collections.py
90.90% <0.00%> (ø)

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 d222206...e90090c. Read the comment docs.


Update Support for Bedrock 1.16

I have a Problem the BedrockProtocol doesnt support MCPE 1.16, ist possible to Update that?

The normal Nukkitx is just currently a bit Struggeling, but you could use the 1.16 Branch https://ci.nukkitx.com/job/NukkitX/job/Nukkit/job/feature%252F1.16/ otherwise you need to wait.

Also the develop branch of the protocol library supports 1.16

Thank you for the quick help


MapBox GL JS fix for map render

Description
A known issue with Mapbox GL JS 2.0 is preventing the map from rendering in production (it works properly in development).  At this time MapBox recommended the fix as described on this github issues page.
Type

[x] This is a bugfix.
[ ] This is a new feature.
[ ] This is part of a feature.

Organization

[ ] Have you linked this pull request to a Trello card?
[x] Have you named the branch in the format of feature/describe_feature_or_change OR bug/describe_bug_this_is_fixing

Review

[ ] Is this a work in progress?
[x] Is this ready to be reviewed?
[x] Have you added two reviewers to this pull request?

I was hoping that the AWS preview would allow me to see if this fix worked in production, unfortunately the settings in Okta are causing CORs issues for the preview deployment which prevent this. It seems only merging to main will allow this fix to be tested.

I was hoping that the AWS preview would allow me to see if this fix worked in production, unfortunately the settings in Okta are causing CORs issues for the preview deployment which prevent this. It seems only merging to main will allow this fix to be tested.


Save VectorStore in IndexedDB?

I encountered this error 'IDBObjectStore': An object could not be cloned. when trying to save VectoreStore in IndexedDB using localForage.

code sample?


[: install test as [ as well

Closes #2420.
This installs test as [ as well. When test is called with a binary name that ends with [, it changes its behavior a bit.
I would rather add [ as its own utility instead of changing the behavior of test based on its binary name,
but I ran into problems trying to do that because [ is not a valid crate/feature name. Working around it in build.rs and in GNUmakefile adds complexity and feels easy to get wrong... In any case we can't convince cargo to create a binary called [, which we can't work around if uutils is installed via cargo install.
There are plans for cargo to support creating arbitrarily named binaries, which would mean we'd only have to work around the restriction for the feature name.
Maybe we can solve this problem in some other way?

I would rather add [ as its own utility instead of changing the behavior of test based on its binary name,
but I ran into problems trying to do that because [ is not a valid crate/feature name.

I think your approach as it is right now is a valid workaround.
The manpage speaks of another subtle difference:

NOTE:  [  honors the --help and --version options, but test does not.  test treats each of those as it treats any other nonempty STRING.

NOTE: [ honors the --help and --version options, but test does not. test treats each of those as it treats any other nonempty STRING.

Thanks for pointing this out! Are we allowed to copy the help text from GNU, or do we have to come up with our own?

I am on 2177b8dc37d9c8705b3c59efe7c5e10a69dce182 and the alias is not installed for me.


[Backend migration] Implement a visual Admin interface

Airtable is very convenient because we have a visual interface to check and manipulate the database easily. Migrating to our own server and database means we would have to ssh into the server and query the database manually anytime we want to do the same thing.
My suggestion is to implement a visual Admin interface for easy manipulation of the database by the project admins (@ann-kilzer , @yanarchy and @tuttiq ). Rails has some convenient libraries to easily implement something like that:

ActiveAdmin seems to be the most popular
Rails Admin comes in second place
Administrate is the third place

Popularity ranking reference: https://www.ruby-toolbox.com/categories/rails_admin_interfaces

This project is now in maintenance mode, so I'm going to close some of these feature issues due to lack of resources. 🙏


add sparkmagic(jupyter notebook)

I have two notes:

Title should be less verbose. sparkmagic alone without  on Jupyter(IPython Notebook) should be enough.
I think it would be a good idea to emphasize that it is a Livy tool.

what should we do about this ? I don't want to merge as is. I'd rather applying the notes that you've mentioned.

@eliasah  I don't have any strong feelings about it. It looks like niche tool so I don't think we loose much by leaving it open until @cycorey decides to adjust it. Unless you really want it to be merged now and are willing to do the work.

Ok then I'm not touching it.

I have update the description, @zero323 thanks.


Fix non-absolute path handling in ReadWriterFactory

Currently, if a non-absolute path is passed to ReadWriterFactory, the program blows up with a CouldNotCreateOutputFile due to a NPE. This is a bug that comes from checkOutputAndCreateDirs, which is fixed with:

Handle correctly paths while creating intermediate folders (calling toAbsolutePath before getting the parent)
Catching only IOException when creating the directories, to avoid overseen errors due to other causes.

Codecov Report

Merging #135 into master will not change coverage.

@@             Coverage Diff             @@
##              master      #135   +/-   ##
===========================================
  Coverage     86.686%   86.686%
  Complexity       731       731
===========================================
  Files             71        71
  Lines           2088      2088
  Branches         252       252
===========================================
  Hits            1810      1810
  Misses           214       214
  Partials          64        64

Impacted Files
Coverage Δ
Complexity Δ

...gicdgs/readtools/utils/read/ReadWriterFactory.java
71.429% <50%> (ø)
21 <ø> (ø)
:x:

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 117a902...8fcce78. Read the comment docs.

Codecov Report

Merging #135 into master will not change coverage.

@@             Coverage Diff             @@
##              master      #135   +/-   ##
===========================================
  Coverage     86.686%   86.686%
  Complexity       731       731
===========================================
  Files             71        71
  Lines           2088      2088
  Branches         252       252
===========================================
  Hits            1810      1810
  Misses           214       214
  Partials          64        64

Impacted Files
Coverage Δ
Complexity Δ

...gicdgs/readtools/utils/read/ReadWriterFactory.java
71.429% <50%> (ø)
21 <ø> (ø)
:x:

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 117a902...8fcce78. Read the comment docs.

Codecov Report

Merging #135 into master will increase coverage by 0.096%.

@@               Coverage Diff               @@
##              master      #135       +/-   ##
===============================================
+ Coverage     86.686%   86.782%   +0.096%
  Complexity       731       731
===============================================
  Files             71        71
  Lines           2088      2088
  Branches         252       252
===============================================
+ Hits            1810      1812        +2
+ Misses           214       212        -2
  Partials          64        64

Impacted Files
Coverage Δ
Complexity Δ

...gicdgs/readtools/utils/read/ReadWriterFactory.java
75% <100%> (+3.571%)
21 <ø> (ø)
:x:

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 91decf0...daaf528. Read the comment docs.

Codecov Report

Merging #135 into master will increase coverage by 0.096%.

@@               Coverage Diff               @@
##              master      #135       +/-   ##
===============================================
+ Coverage     86.686%   86.782%   +0.096%
  Complexity       731       731
===============================================
  Files             71        71
  Lines           2088      2088
  Branches         252       252
===============================================
+ Hits            1810      1812        +2
+ Misses           214       212        -2
  Partials          64        64

Impacted Files
Coverage Δ
Complexity Δ

...gicdgs/readtools/utils/read/ReadWriterFactory.java
75% <100%> (+3.571%)
21 <ø> (ø)
:x:

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 91decf0...0d063d4. Read the comment docs.


refactor check functions in sc_src

Could you write some unit tests for this?

Could you write some unit tests for this?

It's covered by ut_scargo_check, isn't it? If you mean find_files, it's a helper function, an implementation detail, and as such it should not be tested directly.

Could you write some unit tests for this?

It's covered by ut_scargo_check, isn't it? If you mean find_files, it's a helper function, an implementation detail, and as such it should not be tested directly.

Sorry for not being a bit more specific. If you check coverage (actions ->artifacts -> unit-integration-test-report) you will see that some of these functions aren't really tested.


Get hourly data for selected ISPs added to page

This PR gets hourly data for client ISPs in the store and available to LocationPage. Quickly set up rendering multiple charts but they need to be cleaned up in the future- this is just a start. They do not have labels or different colors nor do they share axis extents.

ping @vlandham

+1


operationId is not generated

I would expect the generated code contains something like this:
"/product/get-product-list/": {
      "get": {
        "operationId": "product_get-product-list_list",
        "description": "",
        "parameters": [...]

However, operationId is not being generated. This causes issues with some front-end generators based on swagger.

This is fixed in #44 and also in my fork. Hopefully, the maintainer can take another look at these.

OK, I'll take a look.

I have adopted @alexkreidler 's fork and released as v1.11.0.
Thank you!


Bower Installs Empty Directory for angular#1.3.13

I'm unable to install angular#1.3.13 via bower. I'm unsure if this is a bower or an angular.js issue.
Here is a test case that I ran against a completely empty temp dir:
➜  nvm use v0.10.21
Now using node v0.10.21

➜  bower install angular#1.3.13
bower angular#1.3.13            cached git://github.com/angular/bower-angular.git#1.3.13
bower angular#1.3.13          validate 1.3.13 against git://github.com/angular/bower-angular.git#1.3.13
bower angular#1.3.13           install angular#1.3.13

angular#1.3.13 bower_components/angular

➜  tree -a bower_components
bower_components
└── angular
    └── .bower.json

1 directory, 1 file

➜  bower install angular#1.3.12
bower angular#1.3.12            cached git://github.com/angular/bower-angular.git#1.3.12
bower angular#1.3.12          validate 1.3.12 against git://github.com/angular/bower-angular.git#1.3.12

Unable to find a suitable version for angular, please choose one:
    1) angular#1.3.12 which resolved to 1.3.12
    2) angular#1.3.13 which resolved to 1.3.13 and is required by dfgdgdfPrefix the choice with ! to persist it to bower.json

? Answer:: 1
bower angular#1.3.12           install angular#1.3.12

angular#1.3.12 bower_components/angular

➜  tree bower_components/angular
bower_components/angular
├── README.md
├── angular-csp.css
├── angular.js
├── angular.min.js
├── angular.min.js.gzip
├── angular.min.js.map
├── bower.json
└── package.json

0 directories, 8 files

➜  bower install angular#1.3.13
bower angular#1.3.13            cached git://github.com/angular/bower-angular.git#1.3.13
bower angular#1.3.13          validate 1.3.13 against git://github.com/angular/bower-angular.git#1.3.13
bower angular#1.3.13           install angular#1.3.13

angular#1.3.13 bower_components/angular

➜  tree -a bower_components/angular
bower_components/angular
└── .bower.json

0 directories, 1 file

The diff between the bower.json file present under the tags (v1.3.12 and v1.3.13) in the angular repo are minimal, which leads me to believe this isn't an issue on the angular.js side:
--- /dev/fd/11	2015-02-13 13:46:11.000000000 -0500
+++ /dev/fd/12	2015-02-13 13:46:11.000000000 -0500
@@ -1,8 +1,8 @@
 {
   "name": "angular",
-  "version": "1.3.12",
+  "version": "1.3.13",
   "main": "./angular.js",
   "ignore": [],
   "dependencies": {
   }
 }

I generated this via diff -U10 <(git show v1.3.12:bower.json) <(git show v1.3.13:bower.json) run from a checkout of: https://github.com/angular/bower-angular

Could you try to bower cache clean and re-do installation?

This solved it. I did not realize that bower had a global cache at ~/.caches/bower. Thanks.


switched github reference for AssemblyReader to private fork (issue #1601)

seealso: https://github.com/fsprojects/Paket/issues/1601


Shop Zone - Basic Theft Prevention

This PR introduces basic theft prevention to the shop.
Testplan: https://highfidelity.testrail.net/index.php?/cases/view/1931

Tessting

PASS


Tests started failing

Some of the tests started failing and need to be fixed. See https://travis-ci.org/gentlecat/steam-locomotive/jobs/350140725.

It looks like they don't allow CSV in the appids anymore. Can also be seen in this client: https://github.com/Autarc/steam-store/blob/c3d86a002c300333e2475dc6fed495da5221c577/lib/api/steam.js#L132

There is almost no documentation? Only a unofficial one..  🤔


Inconsistent customer email validation in ASM

Environment Details

Spartacus:  develop, last commit f1f3c1d0d48fb640374f8ad559287e5933a19c0a
Browser: chrome 77
OS: ubuntu 18
Other environment details: ec 19.5.5

Steps to Reproduce

open storefront with ASM mode
login as asm agent
try to emulate "empty" and "invalid" customer email

Observed Results
Error messages appears in differnet places
Expected Results
Error messages appears in same place

Won’t fix
This behaviour is intentional.  It is a convention across the storefront that basic field validation messages (like a required field) appear next to the invalid form field, and processing error messages appear in the global error message area.
Moreover, starting a session with a non-existing customer will not be possible anymore with the planned ASM for Spartacus roadmap. The customer emulation UI will likely evolve to behave like it did in the accelerator: the agent will chose from a list of existing customers before the start emulation button is enabled.


Prevents PHPUnit tests

This PR aims to prevent PHPUnit tests in the codebase. I've opted for the following rules:
A class is a PHPUnit test if it:

Is inside the configured test directory (tests by default)
Is a class
Has a filename ending in the configured suffix (Test.php by default)
Has a classname ending in the configured suffix (Test by default)
Extends a class

Test directories can be configured using the testDirectories array and the suffix can be configured using the testSuffix string.

Actually, seen as PHPStan doesn't support Pest, that isn't really an option atm.


Trying to fix extensions... wip

FYI https://github.com/cloudevents/spec/issues/508 - I think the spec needs some more baking regarding extensions.

Current issues that are affecting my testing: JSON marshal unmarshal turns extension values into raw JSON binary values, instead of canonical strings. Per latest spec and types.Value work, the approach should be to always use either canonical strings or the "preferred" go types defined in types/doc.go, and to use types.ValueOf() when in doubt to smooth over possible conversion issues.

We have done a lot of work around extensions and this is no longer needed.


Update imports after repo move

The repo has been moved from
github.com/kubernetes-sig-testing/frameworks to
github.com/kubernetes-sigs/testing_frameworks.

/test pull-frameworks-test


Permission Denied @dir_s_mkdir - /app/...

First things first, great project!
I tried to run it  on an digital ocean vm with ubuntu 20.04 and docker 19.03.12 and I got this error when running the web service:
 => Booting Puma
web_1       | => Rails <IP_ADDRESS> application starting in development
web_1       | => Run `bin/rails server --help` for more startup options
web_1       | Exiting
web_1       | /usr/local/lib/ruby/3.0.0/fileutils.rb:253:in `mkdir': Permission denied @ dir_s_mkdir - /app/tmp/cache (Errno::EACCES)

I tried to add a chmod to the Dockerfile:
...
RUN mkdir /app
RUN chmod 777 /app
...

among other things, but without success. Do you guys know what could be happening? Everything works normally on my local machine (ubuntu 20.04 and Docker 20.10.7). I tried to use the same version on the digital ocean vm, but without success too.
Anyway, great project! Thanks

Hi,
Thanks.
This very much looks like your DigitalOcean user doesn't have 1000:1000 as its uid:gid.
Can you run the id command from your DO box and check the output near the beginning? For example mine says uid=1000(nick) gid=1000(nick). If your values aren't 1000:1000 then it explains the permission error.
Unfortunately fixing this isn't easy. There's a billion cans of worms that get opened to address this in a way that's portable. Are you in a position to be able to change your user's uid:gid?

Great! I was able to make it work
It was as a root, without the 1000:1000 (uid=0(root) gid=0(root) groups=0(root))
Now I created a new user uid=1000(nicknish) gid=1000(nicknish) in the digital ocean vm and it worked! For someone who maybe will want to deploy to a digital ocean or other vms, here is how I created the user: digital ocean user setup
Thanks again.

Cool. Yeah having a non-root user is a good idea in the end, this is also why I'm ok with leaving things mostly how they are because in practice it's an issue that goes away just by doing business as usual.

Unfortunately fixing this isn't easy.

@nickjj How could one fix this?
I am running on an Oracle Cloud compute instance, which out of the box creates a user with uid:gid 1000 😦

@mobilutz  You mentioned it using 1000:1000, it should work out of the box.


net/http/httptest: clarify that Server.Client is only good for Server.URL

The docs don't make it clear that the http.Client returned by httptest.Server.Client is only good for hitting httptest.Server.URL.
That is, the http.Client's Transport doesn't redirect all dials of any hostname to the test server. (Maybe it should? Would that break existing users?)
/cc @Capstan

If a test is testing that a client configures the right host and port, it'd be nice if there were a recipe for how to use httptest.Server with that, ideally without much or heavyweight (e.g., cert generation on the fly) boilerplate.

If a test is testing that a client configures the right host and port, it'd be nice if there were a recipe for how to use httptest.Server with that, ideally without much or heavyweight (e.g., cert generation on the fly) boilerplate.

I think one can already use a roundtripper e.g. https://play.golang.org/p/UBfwFeTxK2n or inlined below
package main

import (
	"fmt"
	"io/ioutil"
	"log"
	"net/http"
	"net/http/httputil"
	"strings"
)

type hostnameChecker string

func (hnc hostnameChecker) RoundTrip(req *http.Request) (*http.Response, error) {
	if g, w := req.URL.Hostname(), string(hnc); g != w {
		return nil, fmt.Errorf("Hostname mismatch: %q, wanted %q", g, w)
	}
	res := &http.Response{
		Status:        "OK",
		StatusCode:    200,
		Body:          ioutil.NopCloser(strings.NewReader("Hello")),
		ContentLength: 5,
	}
	return res, nil
}

func main() {
	hnc := hostnameChecker("golang.org")
	req, _ := http.NewRequest("GETT", "http://example.org", nil)
	client := &http.Client{Transport: hnc}
	res, err := client.Do(req)
	if err != nil {
		log.Fatal(err)
	}
	blob, _ := httputil.DumpResponse(res, true)
	println(string(blob))
}

so that use case can already be handled, unless am mistaken.

The docs don't make it clear that the http.Client returned by httptest.Server.Client is only good for hitting httptest.Server.URL.

As you obviously already know, the client created here is the bare minimum http client
Start
https://github.com/golang/go/blob/46be01f4e06a2ef1d2450a81dd855671eac5b855/src/net/http/httptest/server.go#L122-L124
and then just configured with the same certs as the server
StartTLS
https://github.com/golang/go/blob/46be01f4e06a2ef1d2450a81dd855671eac5b855/src/net/http/httptest/server.go#L139-L169
and the docs https://golang.org/pkg/net/http/httptest/#Server.Client

loosely talk about that client being for making calls to server but don't emphasize exclusive allegiance to the server.
I think that changing dials of any hostname to the test server might break users whose tests might be comparing HTTP responses served by a handler to those from an external server during say integration tests.
Perhaps to help us compare and find the usage of (*httptest.Server).Client() with other URLs, I'll kindly ping the Sourcegraph people who've indexed source code publicly available and examine some usages @sqs @vanesa or even Github's BigQuery corpus as well.
Ultimately, thought I think it is reasonable to tighten all redirects regardless of hostname to the test server, and if anyone is using the client from net/http/httptest, they should instead switch to using net/http.


修复fastjson 高危命令执行漏洞

修复fastjson 高危命令执行漏洞
https://github.com/alibaba/fastjson/releases/tag/1.2.69

Thank's , and it's fixed


DataFrame.apply(func, axis=1) returns Series with unmatched index

Env: koalas 0.27.0, Databricks DBR 6.2.
Consider the following code for pandas:
df = pd.DataFrame({"timestamp":[0.0, 0.5, 1.0, 0.0, 0.5, 100.0, 101.0, 102.0],
              "car_id": ['A','A','A','B','B', 'C', 'C', 'C'],
              "battery_charge": [100, 90, 80,100,90, 50, 60, 70]
              })

df2 = df.groupby("car_id").sum()

def calc_somthing(row) -> float:
  # doing some job per row
  return row['battery_charge']/(row['timestamp'] +1)

print(df2.apply(calc_somthing, axis=1))

That prints a series with the proper index:
car_id
A    108.000000
B    126.666667
C      0.592105
dtype: float64

But if we do the same for koalas, we get a wrong index (and also wrong name, BTW):
0    126.666664
1    108.000000
2      0.592105
Name: 0, dtype: float32

That causes a lot of problems when merging that index with a new df, e.g.
df2["newcol"] = df2.apply(calc_somthing, axis=1)

The workaround is to always reset_index before apply.

The problem here is that we can't tell what's the index given the type hints. So the index is being lost currently. Yes, reset_index is a nice workaround.
We should find a proper way to specify index type in the type hint... Let me at least document it for now.

Hmm, not sure why couldn't we just get the same index as the originating df?
Especially for df.apply(func, axis=1) that returns single type value per row.

It's because the output index can be different from the original DataFrame:
>>> import pandas as pd
>>> pd.DataFrame({'a': [1,2,3]}).apply(lambda _: pd.Series([1,2,3], index=["a", "b", "c"]))
   a
a  1
b  2
c  3

We can't detect the index type before the function execution. That's why it can return index type properly when the type hints are not specified (hence the type is inferred after executing the function once).

Do you actually have any good idea to specify the index type? One possibility is we leverage https://docs.python.org/3/library/typing.html#typing.NamedTuple and have a reserved name to specify index type. I was thinking about supporting this but there would be no way for Python 3.5 to use because this is new from. Python 3.6

Eh, I feel like it's tricky, every solution I can think of is just so nasty and not convenient..
But anyway, I actually don't understand.. for kdf.apply() that is:

Row-based - axis=1
Apply function returns a single value (NOT ks.Series or ks.DataFrame)
We can just take the same index from the row that is processed, right?
And then we can just make index parameter as not supported for that operation.

I believe 90% of the applications of row-based apply are actually returning single value, I never in my life returned multiple values from row-based apply.. But that's just me.
Let me know if it makes sense.

Is there currently a clean way to add a dataframe column based on udf accepting rows (axis=1)
I also tried
def func(row) -> int: return row['a']

df['col'] = df.apply(func, axis=1)

But it does not work with distributed index. Any suggestions how to implement without hopping back to spark and using withColumn? This to_spark/to_koalas() method bloat the code
Most likely there are other ways to do that, but quick search didn't reveal anything

I think you should probably use pandas_wraps for now; however, yes I think we should have a more elegant way.

@HyukjinKwon , yes, it works, thanks for lightning-fast reply!


[CI] Update GitHub workflows to prevent initiation of Netlify builds unless changes to /docs

Deploy preview for meshery-docs ready!
Built with commit 88755e1cb9c2c0eadee83a2a5a3f0cc373fe0128
https://deploy-preview-2487--meshery-docs.netlify.app
Originally posted by @netlify in https://github.com/layer5io/meshery/pull/2487#issuecomment-788175738

@ramrodo I know this was taken care of in the past, but behavior has resurfaced. Ideally, this is configuration that we make inside of the workflows (not leveraging netlify's configuration or logic).

@leecalcote I think I finally fixed it. I followed this hack for ignoring dependabot updates also:
https://www.netlify.com/blog/2020/04/27/ignore-unnecessary-builds-to-optimize-your-build-times/
adding this to our Netlify config:
https://github.com/layer5io/meshery/pull/2487/commits/eb99ee094549916b28439510d43b0e702ad458a6#diff-ab8f79b68b7adff7a07db953bf453f3c5aa6ade98d2b1b67d8432b36392489edR5
And as you can see here:
https://app.netlify.com/sites/meshery-docs/deploys/603d76e4bafc0d0008a69355
it was finally canceled.


[5.7] Refactor method in console/application

Just was scanning this file and noticed this method was the least readable in the file, and figured a quick refactor couldn't hurt.
Functionality didn't change in any way, just some minor syntax for readability.

Thanks for the PR, however I actually think this makes the readability worse.

maybe for a genius it makes the readability worse.


[21812 ] Add new functionalities to spy CommandLine interface

Merge after: https://github.com/eProsima/DDS-Pipe/pull/134

Check CI here


[Models][330][transformer]swin_transformer_v2

If this is your first time, please read our contributor guidelines: https://gitee.com/mindspore/mindspore/blob/master/CONTRIBUTING.md
Is your feature request related to a problem? Please describe.
https://github.com/rwightman/pytorch-image-models/blob/main/timm/models/swin_transformer_v2.py
https://arxiv.org/abs/2111.09883
Describe the solution you'd like
model.py
readme
config

duplicate of #634
solved in #673


Remove 3.4 Trove classifier

EOL Python 3.4 was removed in https://github.com/hugovk/pyasn1-modules/commit/a6f62cc801d49e0f4ba087771aa7fbe7a80599cb#diff-2eeaed663bd0d25b7e608891384b7298, also remove the classifier for PyPI.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #106   +/-   ##
=======================================
  Coverage   99.36%   99.36%
=======================================
  Files          98       98
  Lines        5990     5990
=======================================
  Hits         5952     5952
  Misses         38       38

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 238ef5e...7cce286. Read the comment docs.

Oh, thank you!


mod_php pcre groups are broken with pcre.jit = true

Issue description
<?php
  preg_match('/(42)/', '42', $result);
  var_dump($result);
?>

Should dump, among other things, "42", but instead results in no match at all. This appears to happen whenever groups are used at all, but simple matches work (eg. '/\d\d/' or simply '/42/' will match '42')
This seems quite severe.
Steps to reproduce
I've prepared a nixos-test in a gist. It should fail when pcre.jit is set to true (the bug) and succeed when set to false.
Technical details

System: 18.03.git.292f605 (Impala)
Nix version: 1.11.15
Nixpkgs version: 292f605 (nixos-unstable)
Sandboxing enabled: true

I don't fully understand what might be the full implications of doing that but FWIW building PHP against Nix provided pcre package (rather than the one bundled with PHP) fixes this particular issue.

Following the suggestions in #31499, this patch indeed does fix the issue.
I am unsure whether we should prefer applying that over using our own pcre.

Can confirm, I rebuilt PHP with (mostly the same) upstream patch from https://github.com/php/php-src/commit/5ef10d08ec2d0823fb21ad189dacfb43d900a0b5 and that clears the issue for me as well, but am also not sure what would be the preferred solution :/.


Ctrl+Z in Notebooks hides the Run All button and changes it to Stop (no way to recover)

https://github.com/microsoft/vscode/issues/115717

Fixed


Speeding up with indexes

Should we use that to display and add missing indexes? The app still seems to be still slow.
https://github.com/plentz/lol_dba
http://rakeroutes.com/blog/increase-rails-performance-with-database-indexes/
http://weblog.rubyonrails.org/2011/12/6/what-s-new-in-edge-rails-explain/

I think it is already pretty fast :) But let's discuss that in the evening at the Monstas meeting.

done!


feat: docs building

What I did
Build plugin docs using sphinx.

fixes: #
How I did it
How to verify it
This is how the docs looks when it builds the repo through github actions: https://dtdang.github.io/ape-vyper/latest/
Checklist

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

Thoughts from viewing the demo:

The logo is really small on desktop

That is actually my only note, it looks amazing!

Thoughts from viewing the demo:
1. The logo is really small on desktop

That is actually my only note, it looks amazing!

I'm thinking of asking Alex to combine the icon and name in one long logo instead to make it easier to see on the docs page since it does look really small there. I don't think there's a way to have 2 images side by side for the logo natively


Introducing '.js' file causes errors with TypeScript code

From https://www.reddit.com/r/programming/comments/3ux8fs/announcing_typescript_17/cxo5ldn?context=3.

I just updated VSCode to the latest version (0.10.3) and reduced this problem to a small case, and I'm really confused:

A simple internal module, a simple .d.ts referencing it. Everything works fine: http://i.imgur.com/O8uIQFT.png

2. I create a plain .js file. Even without writing to it or saving it again, I get Schrodinger's interface: http://i.imgur.com/siOf1AV.png

At this point, the errors about the interface file won't go away. After I close the .js file in the editor, close the folder, and reopen the folder, things go back to normal. But as soon as I open a plain .js file, they come back just like before. After the errors get triggered, I can close the .js file and they stay in the status bar. If I then add both the module and the .d.ts to the "working files" list, then remove .d.ts from it, the errors vanish again.

We're not sure what sort of interaction might be going on with the TypeScript language service, so we felt it would be better filed here.

These errors are produced by the JS language service. The owner is javascript/semantic. Since the view.d.ts file is a declare file it is loaded into the JS language service and that doesn't know anything about the all.ts file which defines the mystery namespace.

Moving to @jrieken

The issue is understood, removing the important label.

This is how the current JS implementation works. It only considers .js and .d.ts files, but no .ts files. We won't fix that for the current JS language service but it might go away once we use project Salsa.


Make subscript left align by left-aligning the complete div, #141

Pull Request Test Coverage Report for Build 566

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.166%

Totals

Change from base Build 564:
0.0%

Covered Lines:
1382

Relevant Lines:
1642

💛  - Coveralls


Redesigned Footer section (v1.0.0)

Description
Completely redesigned the Footer Section of SMP site
Initial footer (v1.0.0) was -

New redesigned footer -

$ Updates :-

Included SMP logo.
Changed background color to #222
Added twitter card.
& much more :p

This PR fixes #105
Notes for Reviewers

Currently 100% optimized for desktop view. Next update (Footer revamp 1.0.1) will consist responsive view / mobile view support!

Currently the mobile view looks like this.

We also need to fix the spilling over of the page (marked on the right side on above screenshot)

Refer to this!
Signed commits

[x] Yes, I signed my commits.

The new footer looks so cute. Well done @Neilblaze and @lolyparty

Thanks @KarenEfereyan :smile:

The new footer looks so cute. Well done @Neilblaze and @lolyparty

Thanks to @Neilblaze


Github CI doesn't cache files when trusted setup setting

What is the bug?
CI doesn't cache file fpr structed setup. This made CI run for very long time.

Fix in PR #102


Add Lyra2Z algorithm

@MikalaiR Thanks for the PR. It will be merged once you taken care of the following things:

Make sure that the indenting matches the rest of the code (tabs/spaces)
Add tests for LyraZ

@MikalaiR Please resolve conflict, fixing all indentions, and test for merging. If nothing is done by end of June, I will close this PR.


Add --dns flag for resin local push

This is required to work around DNS issues during build

dns configuration apparently can't be passed as a docker build option

So how to solve this issue?


ImageNet training setup

Hi!
Your BNN model has good performance and I really appreciate your work.
I would like to reproduce your ImageNet experiment, but cannot find hyperparameters you used.
(i.e. number of blocks, learning rate, epochs, optimizer, ...)
Did you use the same training setup used on ReActNet paper?
Or, I would really appreciate if you upload the codes you used for ImageNet training.
Thanks!

Plus, I would like to know if you tried scaling the model for different sizes, or you only experimented with the proposed model size for fair comparison with the previous paper. Thanks.

Hi resurgo97,
The training setup and hyperparameters are discussed in Section 5.1 in the paper.
Plus, we've just released the official code and the pre-trained models for reproducing the results in the paper, including the ImageNet model. Please check the pointer updated in the Readme file.
We haven't tried to scale the model, but this is definitely an interesting thing to do.
Best,
Yichi


Add collapse all threads option

When multiple threads are unfolded, it's difficult to find unfolded threads.

Two x escape key now closes all threads (one escape key closes the current, second one closes the rest). This should probably be written in some help popup somewhere, but for now, I'll consider this done.

Great to have the functionality, but I'd be wary of undocumented keybindings. Can we have a clickity buttony thing? Or does that not make sense?
I suspect that the answer is: it depends. It depends on whether we want power users, or whether all users are power users, etc.

Also depends on the "TOO MANY BUTTONS" nightmare we could face at some point. I'd really love some input from some UI folks with more insight into how one does that :)

Yes, too many buttons is bad, to few is also bad. And the question remains: power users or not?
Let's take gmail for example (I know, I know). You can basically do everything with buttons, but also with keybindings. That sort of approach would be ideal IMO.
For now I think this can remain closed since the functionality is there. We just need to unify the UI and tie it to the app features.


Support transforming animated webp

When transforming animated webp the service throws an exception.
This feels related:
http://imagemagick.org/discourse-server/viewtopic.php?t=28286

https://github.com/ImageMagick/ImageMagick/issues/1111

https://github.com/ImageMagick/ImageMagick/issues/22

It seems there isn't alot of development on imagemagick anymore. Especially for new formats as webp.
We could look into using the decoder dwebp and encoder cwebp for webp instead.


Split segment by search type

Description
For exact search, it is not required to perform
qunatization during rescore with oversamples.
However, to avoid normalization between segments from
approx search and exact search, we will first identify
segments that needs approxsearch and will perform oversamples
and, at end, after rescore, we will add scores from segments that
will perform exact search.
Related Issues
#2215
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] API changes companion pull request created.
[ ] Commits are signed per the DCO using --signoff.
[ ] Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Should we skip quantization on indexing if we are not using it here then?

Should we skip quantization on indexing if we are not using it here then?

+1. I think it is valid point. We should do that too. But @VijayanB there were couple of more ideas that we were discussing on how to fix this issue. Did you put some thoughts on that like why we should split the segments by search type?

Should we skip quantization on indexing if we are not using it here then?

+1. I think it is valid point. We should do that too. But @VijayanB there were couple of more ideas that we were discussing on how to fix this issue. Did you put some thoughts on that like why we should split the segments by search type?

Another option could be to read the quantized values directly from the native engine file, as discussed here: https://github.com/opensearch-project/k-NN/issues/2266. This approach would also address cases where the search results are fewer than k, allowing us to fall back to an exact search.


Loading X images or x pages in advance

Hi,
Is there a parameter to set in order to load x images or x pages in advance? On slow network it takes time for image to load and therefor the image is not loaded when the user gets to the viewable position of the image

Hey @yanivhyped ,
the answer is YES, you can use either the threshold or the thresholds options. Check the reference in the API section of the documentation.
If you want to load a page in advance and your scroll direction is vertical, you could set thresholds: "100vw 0" in the options object.


Link broken: https://redux.js.org/api-reference/store#subscribelistener

Below link is broken, please fix it. Please refer to attached screenshots for more reference.
_https://redux.js.org/api-reference/store#subscribelistener_
What is the current behavior?
Below link is broken:
_https://redux.js.org/api-reference/store#subscribelistener_
Please fix the broken link.
Steps to Reproduce
Navigate to _https://redux.js.org/api-reference/store#subscribelistener_

Where are you seeing the original link in the first place?

Can you submit a PR? An issue isn't really the best format for this.

That said, we should add redirects to handle old incoming links and point them to the current URLs.  I know I have a bunch in there already, but looks like I might have missed some.


@usedapp/components

A simple library of components build on top of @usedapp/core, example components:

Account bar (connection status, address, count of pending transactions)
Network (show current network - Mainnet, Kovan, Goerli, Unsupported network)
Transactions (list of transactions made by user)
Notifications (bubble with notifications: wallet connected, transaction started, failed)
In progress dialog (generic in progress dialog for transaction with custom icon)
Send button (states: none, mining, success, error, validation? )
Connect Wallet Dialog (aka Web3Modal)

@alexcherman Up for implementing this?

You bet! Let's make a call and discuss it. I have few ideas how to make it flexible.

Scheduled for late April/early May.


Delete segments of a given time range

There are occasional asks from users to delete segments of a given range. (.e.g from 4days ago to yesterday). Since the segment metadata has the range info, it's possible for such deletion at the day's level for offline tables.

I think we need a more formal definition for this feature before we consider the implementation.
For example,

do we only support absolutely aligned segment time boundaries? (e.g. do not touch any segment that are across the start/end timestamp)

if so, what happen to those that cross the start/end timestamp?
also what happen if data were reuploaded?

also i felt like this can be achieve via a 2 step action - first query the segments by time range, and then use the delete segment endpoint.

Agreed. Perhaps there's a way for the user to review the identified segments (via dryrun), and then choose.


Building without nix fails on latest master

nix develop followed by cargo build works, so the Rust environment provided by Nix works. It provides rustc version 1.70.0, so if you are using an older version of Rust, it may not compile.


[Feature]: Support circular-dependency-plugin

What problem does this feature solve?
While the optimizeModules hook was added in #2758 to support circular-dependency-plugin. The Module interface does not include the dependencies property the plugin uses to iterate through the dependencies of the module. Additionally the Compilation interface does not include the moduleGraph property the plugin uses.
What does the proposed API of configuration look like?
compilation.hooks.optimizeModules.tap('PluginName', (modules) => {
    const seenModules = {};
    for (const module of modules) {
        seenModules[module.debugId] = true;

        for (const dependency of module.dependencies) {
            if (
                dependency.constructor &&
                dependency.constructor.name === 'CommonJsSelfReferenceDependency'
            ) {
                continue;
            }

            const depModule = compilation.moduleGraph.getModule(dependency);

            // Check things on depModule
        }
    }
});

The plugin uses the following properties:

Module.dependencies: in Webpack this is an array of HarmonyImportSideEffectDependency
Module.debugId: a number
Compilation.moduleGraph.getModule(dependency: HarmonyImportSideEffectDependency): Module: a method on the module graph that resolves a dependency to its Module

We're not intended to expose complex data structures like ModuleGraph, Dependency, ChunkGrpah, etc. You may port this plugin to Rust instead.

this proved to be a very important plugin in webpack recently i faced a issue because of circular dependency which took lot of time will be good to have feature in rspack also

this plugin can actually be implemented using stats.json，someone want to give it a try？

I implemented a very basic version using the stats at https://github.com/kialo/rspack-circular-dependency-plugin.
For our use case it works, but note that the tests that came with the original plugin do not pass, as I haven't found the time to fix them yet. Therefore it also doesn't have an official release. I'm happy to take contributions.

thanks @ska-kialo worked for me but was returning ids instead of readable names/path extracted modulesById[currentModule].name and resonModule.name working as expected now

@saifislamrepos ah yes, I assume you're running in production mode? I hadn't considered that when implementing it.

@ska-kialo yes as in production it takes moduleids as deterministic i guess

this will cause performance issue and we suggest do this check in lint tools like eslint | biome

I disagree with this choice. The bundler is what actually generates runtime code, and therefore, is the safest and most accurate place to check for cycles—which can cause crashes.
Additionally, how will it harm performance? Checking for cycles is O(V+E), so will scale ~roughly linearly in practice with the number of modules. If one throws a quick check after module resolution and before prod bundling, will that really take that much time?
I would ask that y'all reconsider this :) I think it would be valuable and can be done performantly.

I disagree with this choice. The bundler is what actually generates runtime code, and therefore, is the safest and most accurate place to check for cycles—which can cause crashes.
Additionally, how will it harm performance? Checking for cycles is O(V+E), so will scale ~roughly linearly in practice with the number of modules. If one throws a quick check after module resolution and before prod bundling, will that really take that much time?
I would ask that y'all reconsider this :) I think it would be valuable and can be done performantly.

if it's implemented in rust side it could be done performantly, but if it need to be done in js side it will cause huge module graph communication which will hurt performance

Ah, I see. I think the general question of "should we support cyclic dependency checking" is worth considering.
Would the rspack team be open to that being a feature of rspack, even though it is not one of webpack? Or would the recommendation be to build this as a rust-based plugin ourselves? (For more clarity: we at Discord really want cycle checking).

we will reconsider what is the best way to do it

Yes.

+1


SOLR-16531: Disable unused Jersey features

https://issues.apache.org/jira/browse/SOLR-16531
Description
Jersey has several optional features that we don't need or use.  Disabling these keeps our use of Jersey as lightweight as possible.
Solution
These features are disabled by setting particular configuration props in each Jersey 'application' that gets created.
Tests
Manually tested via log-message inspection.  Manual validation of the improved Jersey app-startup performance.  Existing tests continue to pass.
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[x] I have run ./gradlew check.

This PR consists mainly of a snippet that I've had in a variety of other Jersey-related PRs, and that has been previously reviewed.  Pulling it into its own PR here, so that it's better documented in the git-log, can be reverted or cherry-picked independently, etc.


GEP 713: merged inherited policy may cause unexpected result

Considering people have two inherited policies like this:
Gateway level:
spec:
   targetRef:
     ...
     kind: Gateway
default:
     ext_auth:
         http_service:
             ...

HTTPRoute level:
spec:
   targetRef:
     ...
     kind: HTTPRoute
default:
     ext_auth:
         grpc_service:
             ...

The merged result will be:
default:
     ext_auth:
         http_service:
            ...
         grpc_service:
             ...

If the ext_auth is defined to use either http_service or grpc_service, then merging between sane policies may cause an unexpected result.
If we change the definition of ext_auth to:
   kind: http / grpc
   http_service:
            ...
   grpc_service:
            ...

the problem will be solved.
It would be better to mention that people need to take care of their definition when defining inherited policy.

Another case is to merge field with a default value.
For example, considering we want to merge rule B into A,
the rule A is:
feature:
  foo: true
  bar: 1

the rule B is:
feature:
  bar: 2

so it seems the result is:
feature:
  foo: true
  bar: 2

However, if the feature section has a default value false for field foo (either because the Go language provides a default value for unset field or because the CRD has a default value), then the final result is:
feature:
  foo: false
  bar: 2

even the foo: false is not explicitly written out in rule B!

/cc


feat(api): Expand the supported resource pack operations for 1.20.3

This PR makes it easy to handle multiple resource packs, and adds a callback system to track pack application.
(note, this does change some API used in snapshots so it'd be a binary break for any current testers)

hm, looking at adding Iterable overloads, type erasure means we can't support all the individual types for each method. Right now, i feel like the best signature for implementations would be thing(List<RPRequest>), where for API end users, the thing(Iterable<? extends RPRequestLike>) signature would make most sense -- but then we have to be careful about unboxing *Like instances pretty eagerly maybe?

Looking at Vanilla again, it appears that while the client will accept multiple packs, it only uses the last required and prompt values sent, not one per pack. Maybe we want to push those values up to Request from Info?


Write a JPAStreamer Quarkus starter template

Closing as this is probably not that helpful. We are better off referring users to the JPAStreamer demo repository.