[@svelteui/core]: actionicon add onclick event

Description
I want to be able to make an action, when an action button is clicked. I could wrap a div around, but I think thats a very silly workaround and a responsibility of the component. Therefore I also had to adapt the Box Component to bubble up the onclick event
Before submitting the PR, please make sure you do the following

[ ] Read the Contributing guide
[x] Prefix your PR title with [@svelteui/core], [@svelteui/actions], [@svelteui/motion], [@svelteui/core], [core], or [docs].
[x] Include a description of the changes made in the PR description and in the commit messages.
[ ] Include screenshots/videos of the changes made.
[ ] Verify that the linter and tests are passing, with yarn lint and yarn test or just run yarn prepush.

I'm a backend dev and have no turbo installed on my maschine and it didn't work installing the dependencies and also not after installing turbo globally, so it's currently untestet. Please test it yourself 🙂

after retesting, it worked. already wondered why it didn't work. But seems like I did some sort of error


[GOBBLIN-1634] Add retries on flow sla kills

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1634

Description

[x] Here are some details about my PR, including screenshots (if applicable):
On Gobblin as a Service flows can fail SLAs if they do not receive a Kafka event in some designated amount of time.

Since GaaS supports retrys on failures, these failures due to SLAs should also be retryable.
However, if the flow is cancelled from a user specified event through the API we do not want to retry.
Additionally, we also do not want to retry if a flow is skipped due to concurrent jobs running at the same time, as it is unlikely without a more sophisticated waiting algorithm that the job will be finished by the time the job is retried again, wasting resources.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3495 (7bbd673) into master (172d879) will increase coverage by 1.79%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3495      +/-   ##
============================================
+ Coverage     46.70%   48.50%   +1.79%
+ Complexity    10400     7728    -2672
============================================
  Files          2077     1442     -635
  Lines         81150    56993   -24157
  Branches       9059     6570    -2489
============================================
- Hits          37898    27642   -10256
+ Misses        39769    26777   -12992
+ Partials       3483     2574     -909

Impacted Files
Coverage Δ

.../org/apache/gobblin/metrics/event/TimingEvent.java
70.00% <ø> (ø)

...in/java/org/apache/gobblin/cluster/HelixUtils.java
31.70% <0.00%> (-4.27%)
:arrow_down:

...preduce/avro/MRCompactorAvroKeyDedupJobRunner.java
43.69% <0.00%> (-1.69%)
:arrow_down:

.../gobblin/runtime/retention/DatasetCleanerTask.java
0.00% <0.00%> (ø)

...anagement/copy/replication/ConfigBasedDataset.java
68.87% <0.00%> (ø)

...blin/service/modules/orchestration/DagManager.java

.../service/monitoring/KafkaAvroJobStatusMonitor.java

...blin/service/monitoring/KafkaJobStatusMonitor.java

...main/java/org/apache/gobblin/r2/D2ClientProxy.java

...che/gobblin/metrics/graphite/GraphiteReporter.java

... and 633 more

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 172d879...7bbd673. Read the comment docs.

nice work!
this seemed an important element (from your PR summary):
Additionally, we also do not want to retry if a flow is skipped due to concurrent jobs running at the same time

yet I'm having trouble finding anything related to this in the impl. (a comment saying the same at the least...). does it just come down to some CANCELED ones not bearing a isFlowSlaKilled.equals(true)?

In this scenario I'm describing the timing event emitted is SKIPPED, which is emitted from the Orchestrator. Since the dag isn't created I believe a retry would be overriding the check, which is done in the DagManager (which comes after Orchestration). Also it's unlikely that the concurrent flow actually finished by the time the retry is processed anyways, since we do not have waits before retries.

Functionally speaking it's just a cancellation event which isn't user initiated that doesn't have the flag that it was killed due to exceeding the start/runtime SLA

would it be worth adding a comment when preparing that internal cancellation saying that it won't be retried because it's missing the flag?
per our conversation recently about 'semantic naming', we could always consider naming that flag something like:
-  public static final String IS_FLOW_SLA_KILLED = "isFlowSlaKilled";
+ public static final String DOES_CANCELED_FLOW_MERIT_RETRY = "doesCanceledFlowMeritRetry";

?

Ah I got my events mixed up, the SKIPPED_TIME is actually emitted by Helix in GobblinCluster so it's never actually sent from GaaS' internal system, and shouldn't be retried. I think the switch statement not having the comment is fine if we go with the semantic naming like you suggested.


Implement Environmental Damages

Fire Damage on Lava, Fire, ...
Damage from Cactus

And this should either use #106 or https://github.com/aresrpg/aresrpg/blob/master/src/player_statistics.js


[3pt] Look into abnormal runtimes for two FR FIM3 hucs

HUCS 04220001 & 04160003 are both taking more than 180 minutes to complete in recent FIM3 runs. This is 50%+ longer than any of the other HUCs. Perhaps there is a valid reason for this, but potentially worth looking into for better runtimes.

In fim4 testing, 04220001 is no longer included as it was exclusively in Canada. 04160003 is now quite fast as it is partly Canada and now clips the Canadian part out.


doc: crate documentation

Fixes #3.
This PR adds the missing crate documentation and adds a compile time warnings if is missing the documentation.

@dadamu please check this so we can merge it

@manu0466 if you fix the requested changes, I guess later we can merge it


Add booleans for remote, permanent, freelance and ability to search on them.

Hi,
Just found this site yesterday and I love it!
But I miss the ability to make more detailed selections.
I would like to be able to search for remote, permanent and/or freelance/contract position.
I guess I have to program it myself and offer a PR?
But before I do, some feedback on this would be very welcome.
Regards,
Jeroen Baten

Hi kwoot, and a warm welcome to the small fossjobs community!
Yes, you judged the situation correctly. We use a copy of the abandoned Jobberbase PHP, and over time I've done some changes in hackish ways to keep it running and did some small adjustments here and there, but no major features. I am personally happy with what we have; maybe there is a better platform to migrate to out there, but so far nobody has complained too much, and it seems to be serving its purpose well enough.
You are welcome to continue to brainstorm and add ideas and feature requests, even if you don't plan on picking up the work yourself. Maybe it inspires someone else to pick things up, and it can serve as a wishlist, in case anyone thinks they found a better alternative.


Add the ability to match on phrase instead of word.

There are some cases where it is require to match exact phrases and not
words. Thus I have created a PhraseLoader and PhraseMatcher for the
purpose of working with phrases.
That means that if you have the phrase "awesome stuff", the term "awes"
will match, but the term "stuf" will not.
I have not yet enabled phrase loading through the CLI, only by
explicitly loading with a PhraseLoader class. The PhraseLoader has an
identical interface to the standard Loader, it just refrains from
normalising anything, because that gets messy with phrases.
When it comes to matching, supplying phrase=true as part of the query
string will tell the Soulmate::Server to use the PhraseMatcher, and
successfully match the loaded phrases.

Closing since this is unmaintained. Please use soulheart instead!


[Gpr_To_Absl_Logging] Fixing bugs

[Gpr_To_Absl_Logging] Fixing bugs
Problem 1
Context :
gpr_log() internally calls gpr_log_message() .
gpr_log_message() may either call gpr_default_log() or a user provided logging function.
gpr_default_log() uses absl LOG. This is the default. Most users will log this way.
For the small percentage of users who have customized the logging function, gpr_log will log to custom this function.
Problem :
We have converted half the instances of gpr_log to absl LOG().
For users who use the defaults - there will be no issue.
For the users who use a customized logging function

All the absl LOGs will log to the absl log sink.
All the gpr_log statements will log via this user provided function.
This is in-consistent behaviour and will cause confusion and difficulty in debugging.

Solution:
All logs should go to the same sink.
So we decided to make gpr_set_log_function a no op in this release.
The function will be deleted in the next release.
https://github.com/grpc/proposal/pull/425
Problem 2
Context :
gpr_should_log is used to avoid computing expensive stuff for logging if the log is not going to be visible.
Problem :
gpr_should_log was referencing the GRPC_VERBOSITY flag and values set by gpr_set_log_verbosity .
However, actual logging happens based on the absl settings.
This is incorrect. Because if the old settings are not honoured, they should not be checked and no decision in code should be made based on settings which are not going to get used.
Solution :
Given the above changes in Problem 1, since all custom logging is disabled, all logging from gRPC with honour the absl LOG settings. Hence we modified the gpr_should_log function to refer to absl settings.

no, let's not do this. Let's wait for the original PR to get merged. Doing it this way will make future backports harder


Exclude self from tribute reduction

Check if the card in hand is myself before attempting to see if a tribute reduction was applied.
Should solve https://github.com/adambennett/StS-DuelistMod/issues/46

Hey @Rauell, could you please raise this PR into the dev branch? I typically only push code to release/steam when I am ready to push an update out to the workshop.

@adambennett makes sense! I've changed the target branch.


Implementation of Endpoints for Image Edit and Image Variation

I created another init() function which takes the old APIKEY and passes it to the new Config structure.
Because Images are handled by different libraries in IOS and MacOS, there is no error handling.
Images have to be the correct size (256x256, 512x512, 1024x1024 and less than 4MB)
Images must be png files and passed as image.pngData(). (same for the Mask in Image Edit endpoint)
For Editing, if no mask is supplied (its optional) then the image/png file MUST have an alpha channel. (RGBA).
Any of the above Failures result in "Success" results, but "Errors" in the response, which aren't handled by the Decoder.

This update includes the Jan 2024 Endpoints and Models including gpt4-turbo.


make shutdown timeout configurable

this patch makes the shutdown timeout configurable and sets the default timeout to 60 seconds, so server processes which take a few seconds to shutdown gracefully get a chance to do so

Thanks! Sorry I never noticed that you addressed my comments :( I don't think GH gives any notification.


optimize: optimize StatementProxyTest unit test

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #3383 (f6cff68) into develop (5d4c991) will decrease coverage by 0.11%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #3383      +/-   ##
=============================================
- Coverage      51.55%   51.44%   -0.12%
  Complexity      3329     3329
=============================================
  Files            616      616
  Lines          20198    20172      -26
  Branches        2531     2484      -47
=============================================
- Hits           10413    10377      -36
+ Misses          8739     8728      -11
- Partials        1046     1067      +21

Impacted Files
Coverage Δ
Complexity Δ

...obuf/convertor/BranchRegisterRequestConvertor.java
90.47% <0.00%> (-9.53%)
3.00% <0.00%> (ø%)

...otobuf/convertor/BranchReportRequestConvertor.java
90.90% <0.00%> (-9.10%)
3.00% <0.00%> (ø%)

...obuf/convertor/BranchRollbackRequestConvertor.java
92.00% <0.00%> (-8.00%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalBeginResponseConvertor.java
92.59% <0.00%> (-7.41%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalCommitRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalStatusRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...obuf/convertor/GlobalRollbackRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...protobuf/convertor/RegisterTMRequestConvertor.java
94.73% <0.00%> (-5.27%)
3.00% <0.00%> (ø%)

...protobuf/convertor/RegisterRMRequestConvertor.java
90.47% <0.00%> (-4.77%)
3.00% <0.00%> (ø%)

...tobuf/convertor/BranchReportResponseConvertor.java
95.45% <0.00%> (-4.55%)
3.00% <0.00%> (ø%)

... and 26 more


chore: added codeowner file

@dizcology Could you review this small PR?

@TheRoyalTnetennba Can u merge it for me?


How can I solve MismatchSenderId?

PUSH_NOTIFICATIONS_SETTINGS = {
    "CONFIG": "push_notifications.conf.AppConfig",

    "APPLICATIONS": {
        "poink_fcm": {
            "PLATFORM": "FCM",
            "API_KEY": "AAAAiLBT9n8:.......",
            # "POST_URL": "https://code.google.com/apis/console/#project:501751185459",
            # "POST_URL": "https://fcm.googleapis.com/fcm/send",
        },
        "poink_ios": {
            "PLATFORM": "APNS",
            "CERTIFICATE": "./Certificate/pushcert.pem",
            "TOPIC": "com.magicboxasia.push_test",
        }
    }
}

In the GCMDevice I select
In [12]: vars(t2)
Out[12]:
{'_state': <django.db.models.base.ModelState at 0x10edf31d0>,
 'active': True,
 'application_id': 'poink_fcm',
 'cloud_message_type': 'FCM',
 'date_created': datetime.datetime(2018, 4, 2, 9, 35, 13, 857711, tzinfo=<UTC>),
 'device_id': None,
 'id': 4,
 'name': 'token2',
 'registration_id': 'dfS4v7BTDo0:APA91bECVPe-D-jMGJbdZsGQlwsQFWhTMwPbb5RHIcJX_DzD0ZL06Vq58E_hYemjRVTc8dG2LSJNh4bowM5Gg9E7FBf5yyMZylH-VG8WbYuNFg8FPtxkBOJB914Lw2MpGqkzd7I58vdL',
 'user_id': None}

In [13]: t2.send_message("hello")

GCMError:
{
  'multicast_id':<PHONE_NUMBER>264268090,
  'success': 0,
  'failure': 1,
  'canonical_ids': 0,
  'results': [
    {
      'error': 'MismatchSenderId',
      'original_registration_id': 'dfS4v7BTD......'
    }
  ]
}

requirements.txt
django-push-notifications==1.6.0
django==2.0.3
It does not mention anywhere in the docs nor wiki
How can I solve MismatchSenderId?

Did the device register correctly from your client app?  If you log into the Firebase console, can you send a message directly to that device?

@jamaalscarlett Thank you for you response.

Did the device register correctly from your client app?  If you log into the Firebase console, can you send a message directly to that device?

I can send a message directly to the device. Then I assume my device register correctly.

In [8]: k1.application_id = 'poink_fcm'

In [9]: k1.save()

In [10]: k1.send_message("Test with new API_KEY")
Out[10]:
{'canonical_ids': 0,
 'failure': 0,
 'multicast_id':<PHONE_NUMBER>226783327,
 'results': [{'message_id': '0:1522729006070111%f2995967f2995967'}],
 'success': 1}

@jamaalscarlett I was on my side. My colleague gave me wrong API_KEY!
This application is good 👍


Unable to use latest [v0.2.5] Bell Claim on 1.21

Behavior
Click on the "Create Claim" item after opening the claim menu does nothing and causes an error in the console.
- [Fri 12:43:51 ERROR BellClaims] Exception while handling click event in inventory 'Claim Creation', slot=4, item=BELL
java.lang.NoSuchMethodError: 'org.bukkit.craftbukkit.v1_21_R1.inventory.view.CraftAnvilView com.github.stefvanschie.inventoryframework.nms.v1_21.AnvilInventoryImpl$ContainerAnvilImpl.getBukkitView()'
    at BellClaims-0.2.5.jar//com.github.stefvanschie.inventoryframework.nms.v1_21.AnvilInventoryImpl.openInventory(AnvilInventoryImpl.java:64)
    at BellClaims-0.2.5.jar//com.github.stefvanschie.inventoryframework.gui.type.AnvilGui.show(AnvilGui.java:171)
    at BellClaims-0.2.5.jar//dev.mizarc.bellclaims.interaction.menus.ClaimManagementMenu.openClaimNamingMenu(ClaimManagementMenu.kt:126)
    at BellClaims-0.2.5.jar//dev.mizarc.bellclaims.interaction.menus.ClaimManagementMenu.openClaimNamingMenu$default(ClaimManagementMenu.kt:84)
    at BellClaims-0.2.5.jar//dev.mizarc.bellclaims.interaction.menus.ClaimManagementMenu.openClaimCreationMenu$lambda$4(ClaimManagementMenu.kt:79)
    at BellClaims-0.2.5.jar//com.github.stefvanschie.inventoryframework.gui.GuiItem.callAction(GuiItem.java:178)
    at BellClaims-0.2.5.jar//com.github.stefvanschie.inventoryframework.pane.StaticPane.click(StaticPane.java:238)
    at BellClaims-0.2.5.jar//com.github.stefvanschie.inventoryframework.gui.InventoryComponent.click(InventoryComponent.java:205)
    at BellClaims-0.2.5.jar//com.github.stefvanschie.inventoryframework.gui.type.ChestGui.click(ChestGui.java:161)
    at BellClaims-0.2.5.jar//com.github.stefvanschie.inventoryframework.gui.GuiListener.onInventoryClick(GuiListener.java:84)
    at com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor204.execute(Unknown Source)
    at org.bukkit.plugin.EventExecutor$2.execute(EventExecutor.java:77)
    at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:84)
    at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:70)
    at io.papermc.paper.plugin.manager.PaperEventManager.callEvent(PaperEventMan

Info
Plugin version: 0.2.5
PaperMC version: 1.21 (notice: not 1.21.1)
Previous used version: 0.2.2
Reason for issue
Though updating to 1.21.1 may fix the issue. The mod is listed on Modrinth with support for "1.21.x" which 1.21 falls under, which is/can be misleading.

Can you let me know the exact PaperMC build you are using? I have tested Paper-1.21-130 with Bell Claims 0.2.5, working with full functionality.

Definitely, it seems like it is 1.21-109-master@5a5035b
This server is running Paper version 1.21-109-master@5a5035b (2024-07-23T08:16:30Z) (Implementing API version 1.21-R0.1-SNAPSHOT)

I have confirmed that PaperMC 1.21 builds prior to 1.21-128 do not work with the latest 0.2.5 build of Bell Claims. This is likely due to the Bukkit upstream parity with the 1.21.1 version that the IF dependency relies on to have it function with both 1.21 and 1.21.1 versions.
Is there any reason why you cannot update to a newer build? While I would like to support as many versions as possible, there would be additional complication involved in order to support builds prior to 1.21-128.

I had some complications with other plugins during the update to 1.21.1. So I wanted to double check and also inform you regarding this bug because I wasn't able to use the latest version that "supposedly" worked with 1.21.
Thank you for the information, effort in collecting it and providing this awesome plugin. I know now how to continue from here.

Thanks for letting me know! I do aim to backport the plugin to older versions when it's in a more stable position, for now I hope the support for 1.21 and subsequent minor versions can continue to be supported at least within the latest PaperMC builds as much as I can. I'll update the description to provide further information on the matter.


[HOTFIX] Fix documentation error

Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?
No
[x] Any backward compatibility impacted?
No
[x] Document update required?
Changed documentation
[x] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.
NA
[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

LGTM

LGTM

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2278/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3515/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3362/


GEODE-3751: a single place for client protocol loading, logic.

Load a single service, ClientProtocolService.

(well, authenticators are still separate).

Move several interfaces to geode-protobuf from core.
Client protocol state and statistics are now stored on the new
ClientProtocolPipeline interface. This will allow us to keep
connection logic for core separated from protocol logic.

This will allow us to make further refactors and add handshake logic to
the new client protocol.
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[x] Have you written or updated unit tests to verify your changes?

[n/a ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

@PivotalSarge have a look if you like.

rebased.


Connecting TO ATP

Check 4: Can we talk to the J2EE server?
Error occured: ORA-29273: HTTP request failed ORA-06512: at "SYS.HTTPURITYPE", line 38 ORA-29024: Certificate validation failure ORA-06512: at "SYS.UTL_HTTP", line 380 ORA-06512: at "SYS.UTL_HTTP", line 1209 ORA-06512: at "SYS.HTTPURITYPE", line 23
We couldn't make a successful connection to https://example:443.
This can be ignored when the other tests are successful. Sometimes the J2EE server doesn't have a working index page (mostly for security reasons).
Please make sure:
The J2EE server is up and accepting connections
The firewalls allow the communication from the database to the J2EE server (if not installed locally)
While Testing with Oracle Autonomous Database (ATP) getting this issue. I have granted the ACL's too but same.
i have replaced the url with https://example:443 my actual url is using https as i have enabled ssl on tomcat.
Kindly share solution if you have.
Thanks & Regards

This is a common problem when you connect to a site using HTTPS but have not set up the wallet correctly.
I will close the ticket because it is not an issue with the code.
If you need further assistance, please post your request in the forum: https://gitq.com/daust/JasperReportsIntegration.
Best
~Dietmar.


Fix get_mediawiki_variable() function for cases when PHP outputs errors

nice fix, thanks!

It works fine in Taqasta image without the patch and we need to see the error messages. I created PR to revert this https://github.com/WikiTeq/Taqasta/pull/11


chore(docs): added missing checkboxes component from the docs

Checkboxes component was missing from the docs sidebar:
https://design-system.hackney.gov.uk/components/checkboxes/

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix for issue 4518, bad example

The problem
Bad example:
isa-ok $resources, Hash;

Solution provided
Correct error by showing the correct class name:
isa-ok $resources, Distribution::Resources;

Thanks!


Fixed API limit issue

If you're a Hubspot user with multiple products, the API limit endpoint will return an array of products. Unfortunately, the CRM API limits isn't always the first value returned.
This is what's returned when you hit the https://api.hubapi.com/integrations/v1/limit/daily endpoint (for our use case):
[{"name":"api-calls-daily","usageLimit":40000,"currentUsage":119,"collectedAt":1510256051744,"fetchStatus":"SUCCESS","resetsAt":1510290000000},{"name":"sales-pro-seats","usageLimit":2,"currentUsage":2,"collectedAt":1510256051753,"fetchStatus":"SUCCESS","resetsAt":null}]

Ah, good call.
Shouldn't we just return the full array then?

I guess we could, but the other member of the array isn't actually an API limit, which is strange, it's just how many seats we've purchased for that particular product (which I'm not sure even has an associated API).


Fix pypi dependencies and slight modifications to Dockerfile

This PR fixes pypi dependencies by adding subdependencies which were somehow elided earlier. Pip tools created different requirements between then and now.
In addition there's two additions to Dockerfile:

add DEBIAN_FRONTEND=noninteractive to apt install command
add Git to apt install command

Merging this with v001dev and submitting a new pull request


[SPARK-13808] Don't build assembly in dev/run-tests

As of SPARK-9284 we should no longer need to build the full Spark assembly JAR in order to run tests. Therefore, we should remove the assembly step from dev/run-tests in order to reduce build + test time.
Most of the changes in this PR were originally part of #11178.

Test build #53094 has started for PR 11701 at commit 2c10193.

Test build #53110 has started for PR 11701 at commit 267aaf9.

/cc @vanzin, this patch removes the need to build an assembly before running tests.

LGTM if tests pass; although a have a comment about the pyspark tests workaround.

Test build #53120 has started for PR 11701 at commit 1154eb4.

Test build #53094 has finished for PR 11701 at commit 2c10193.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53094/
Test FAILed.

Merged build finished. Test FAILed.

Test build #53120 has finished for PR 11701 at commit 1154eb4.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53120/
Test FAILed.

Test build #53110 has finished for PR 11701 at commit 267aaf9.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53110/
Test FAILed.

Merged build finished. Test FAILed.

Jenkins, retest this please.

Test build #53133 has started for PR 11701 at commit 1154eb4.

Test build #53133 has finished for PR 11701 at commit 1154eb4.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53133/
Test FAILed.

Merged build finished. Test FAILed.

Jenkins, retest this please.

Test build #53148 has started for PR 11701 at commit 1154eb4.

Test build #53148 has finished for PR 11701 at commit 1154eb4.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53148/
Test FAILed.

Merged build finished. Test FAILed.

Test build #53158 has started for PR 11701 at commit 1fd489c.

Test build #53158 has finished for PR 11701 at commit 1fd489c.

This patch fails from timeout after a configured wait of `250m`.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53158/
Test FAILed.

Merged build finished. Test FAILed.

Jenkins, retest this please.

Test build #53209 has started for PR 11701 at commit 1fd489c.

Test build #53209 has finished for PR 11701 at commit 1fd489c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53209/
Test FAILed.

Jenkins, retest this please.

(Pretty sure that something is wrong here, but hoping that maybe it's just flaky; I'll dig in more when I have time.)

Test build #53285 has started for PR 11701 at commit 1fd489c.

Test build #53285 has finished for PR 11701 at commit 1fd489c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53285/
Test PASSed.

Jenkins, retest this please.

(Going to quickly make sure this also works with Maven tests, just to sanity-check)

Test build #53332 has started for PR 11701 at commit 1fd489c.

Test build #53332 has finished for PR 11701 at commit 1fd489c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53332/
Test FAILed.

retest this please

Test build #53333 has started for PR 11701 at commit 1fd489c.

Test build #53333 has finished for PR 11701 at commit 1fd489c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53333/
Test FAILed.

16/03/16 11:43:23.870 SparkLauncherSuite-2 INFO OutputRedirector: Failed to find Spark jars directory (/home/jenkins/workspace/SparkPullRequestBuilder@2/assembly/target/scala-2.10).
16/03/16 11:43:23.870 SparkLauncherSuite-2 INFO OutputRedirector: You need to build Spark before running this program.

Looks like some adjustment is needed in my previous change?

Perhaps changing this in bin/spark-class:
if [ ! -d "$SPARK_JARS_DIR" ] && [ -z "$SPARK_TESTING" ] ; then
  echo "Failed to find Spark jars directory ($SPARK_JARS_DIR)." 1>&2
  echo "You need to build Spark before running this program." 1>&2
  exit 1
fi

Test build #53336 has started for PR 11701 at commit 20d2e2a.

Test build #53336 has finished for PR 11701 at commit 20d2e2a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53336/
Test FAILed.

Hmmm. I think this is because this code in load-spark-env.sh:
if [ -z "$SPARK_SCALA_VERSION" ]; then
  USER_SCALA_VERSION_SET=0
  ASSEMBLY_DIR2="${SPARK_HOME}/assembly/target/scala-2.11"
  ASSEMBLY_DIR1="${SPARK_HOME}/assembly/target/scala-2.10"

  if [[ -d "$ASSEMBLY_DIR2" && -d "$ASSEMBLY_DIR1" ]]; then
    echo -e "Presence of build for both scala versions(SCALA 2.10 and SCALA 2.11) detected." 1>&2
    echo -e 'Either clean one of them or, export SPARK_SCALA_VERSION=2.11 in spark-env.sh.' 1>&2
    exit 1
  fi

  if [ -d "$ASSEMBLY_DIR2" ]; then
    export SPARK_SCALA_VERSION="2.11"
  else
    export SPARK_SCALA_VERSION="2.10"
  fi
else
    USER_SCALA_VERSION_SET=1
fi

Since the assembly build is being skipped, it's defaulting to scala 2.10 and failing to find the classes.

BTW, I'm just waiting for this patch before working on SPARK-13579; so it's probably ok to keep building the assembly in the maven build, because it will become a lot cheaper once I implement that change (basically just copy files around).

Yeah, I literally just found the same issue with the defaults in load-spark-env.sh. I wonder whether it would make sense to just have Maven set that variable appropriately based on the profile.

Since all of this code is going to be changed heavily / removed after your final patch, I'm going to go ahead and just leave the Maven test path unchanged so that we can get this merged.

Test build #53345 has started for PR 11701 at commit 0900b13.

Jenkins, retest this please.

Test build #53364 has started for PR 11701 at commit 0900b13.

Test build #53345 has finished for PR 11701 at commit 0900b13.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53345/
Test FAILed.

Test build #53364 has finished for PR 11701 at commit 0900b13.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53364/
Test PASSed.

Okay, so this passes all Scala tests but is failing PySpark Maven tests...

Are the failures legitimate? When I looked before it seemed only one of the python interpreters failed, which generally screams "flaky test" to me...

Jenkins, retest this please.

Test build #53443 has started for PR 11701 at commit 0900b13.

Test build #53443 has finished for PR 11701 at commit 0900b13.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53443/
Test FAILed.

Jenkins, retest this please.

Test build #53453 has started for PR 11701 at commit 0900b13.

Test build #53453 has finished for PR 11701 at commit 0900b13.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53453/
Test FAILed.

I'm going to close this in favor of @vanzin's #11796


Some In/Exists Subqueries will generate wrong PhysicalPlan

Describe the bug
Datafusion can't execute non-correlated subquery now, like in/exists.
So these queries should return NotImplemented("Physical plan does not support logical expression In/Exists error. But currently the filter will be pushdown to the TableScan.
> explain select * from t1 where exists(select 1 from t2 where t2.t2_id > 0);
+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| plan_type     | plan                                                                                |
+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| logical_plan  | Projection: t1.t1_id, t1.t1_name, t1.t1_int                                                                                |
|               |   TableScan: t1 projection=[t1_id, t1_name, t1_int], full_filters=[EXISTS (<subquery>)]                                                                     |
|               |     Subquery:                                                                                |
|               |       Projection: Int64(1)                                                                                |
|               |         Filter: CAST(t2.t2_id AS Int64) > Int64(0)                                                                                |
|               |           TableScan: t2                                                                                |
| physical_plan | ProjectionExec: expr=[t1_id@0 as t1_id, t1_name@1 as t1_name, t1_int@2 as t1_int]                                                                           |
|               |   CsvExec: files={1 group: [[home/work/tools/datafusion-test-data/join-context/t1.csv]]}, has_header=false, limit=None, projection=[t1_id, t1_name, t1_int] |
|               |                                                                                |
+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+

For the above query, the subquery filter will be  lost in the final physical_plan.
To Reproduce
As above.
Expected behavior
The query should return NotImplemented("Physical plan does not support logical expression In/Exists error.
Additional context
Add any other context about the problem here.

I remember the filters will be added to wrong side. I can work on this and provide a fix.

Here is a full reproducer:
echo "1,2" > data.csv

The run sql

> create external table t1(t1_id int, t2_name int) stored as csv location 'data.csv';
0 row(s) fetched.
Elapsed 0.019 seconds.

> create external table t2(t2_id int, t2_name int) stored as csv location 'data.csv';
0 row(s) fetched.
Elapsed 0.007 seconds.

> explain select * from t1 where exists(select 1 from t2 where t2.t2_id > 0);
+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------+
| plan_type     | plan                                                                                |
+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------+
| logical_plan  | TableScan: t1 projection=[t1_id, t2_name], full_filters=[EXISTS (<subquery>)]                                                                   |
|               |   Subquery:                                                                                |
|               |     Projection: Int64(1)                                                                                |
|               |       Filter: CAST(t2.t2_id AS Int64) > Int64(0)                                                                                |
|               |         TableScan: t2                                                                                |
| physical_plan | CsvExec: file_groups={1 group: [[Users/andrewlamb/Software/datafusion2/datafusion-cli/data.csv]]}, projection=[t1_id, t2_name], has_header=true |
|               |                                                                                |
+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------+
2 row(s) fetched.
Elapsed 0.019 seconds.

take


Mission Statement 2.0

Missions as currently stated are here. Question is if we should write a more marketing friendly version of it.

Our mission at Josephine is threefold:

Labor
We believe in creating more inclusive opportunities in food for people who need it the most - stay at home parents, immigrants, and people of underrepresented minority groups. Cooking is the most fundamental lever of economic empowerment, and the food industry has taken that away through its strict barriers to entry.

Food Justice
We seek to increase access to healthy food options, specifically in areas suffering from issues like food deserts. Home cooking can empower healthy decision-making in communities that haven’t had the privilege of nutritional education - the appeal of home cooking exists across all cultures and geographies. Home cooking also allows for the decolonization of ethnic foods by making sure that cooks and communities are directly benefiting from their own food and culture.

Tech Equity
We want to contribute to a more diverse and inclusive tech culture. Our platform serves everyone from ESL immigrants to mothers and retirees – not all of whom have computers or are comfortable with smartphone apps. We try to not only lead through example, but also to acknowledge and mitigate our displacing effect through support of initiatives and organizations that are building a more inclusive tech ecosystem.

I do feel like what we have on the site now is the most direct and succinct way for us to illustrate our mission, and that rewriting it may risk making it too fluffy.

That's fine by me. Does that mean we can close this issue?

While I don't think that we need to re-articulate our mission to make it more marketing-friendly, I do think that there needs to be better succinct ways to articulate what Josephine is. A one liner, a two liner, and a paragraph version would be super helpful. These can be more marketing-y.

Agreed with @joyjding — I think that what we have right now, plus a more easily digestible version is ideal. That said, if there's no way to distill the three aspects of the mission w/o it being fluffy, I say we leave it as is minus this edit:
From this:

We seek to increase access to healthy food options, specifically in areas suffering from issues like food deserts.

To this:
We seek to increase access to healthy food options, particularly in food deserts.

Sika! I'm soooooo glad that you pointed this out. This has been a snail
poop on my foot in the mission for WEEKS. I personally took it out of each
job posting cuz it's squirmy feeling.
On Fri, Feb 5, 2016 at 4:13 PM, Sika Gasinu<EMAIL_ADDRESS>wrote:

Agreed with @joyjding https://github.com/joyjding — I think that what
we have right now, plus a more easily digestible version is ideal. That
said, if there's no way to distill the three aspects of the mission w/o it
being fluffy, I say we leave it as is minus this edit:
From this:
We seek to increase access to healthy food options, specifically in areas
suffering from issues like food deserts.
To this:
We seek to increase access to healthy food options, particularly in food
deserts
http://americannutritionassociation.org/newsletter/usda-defines-food-deserts
.
—
Reply to this email directly or view it on GitHub
https://github.com/josephine/handbook/issues/31#issuecomment-180631642.

agreed. mission statements are good, and not convinced we have a clear vision on how to improve them, so any adjusting would likely make them muddier.
@sike13 +1 for that edit.
@joyjding +1 for one and two liners. and paragraph form. something for our BD & Comms human to do :)

Agreed with all of the above.
Love this as another aspect of justice: "Home cooking also allows for the decolonization of ethnic foods by making sure that cooks and communities are directly benefiting from their own food and culture."

[Updated Mission Statement] (https://github.com/josephine/handbook/blob/master/Mission Statement.md)