Always notifyFailed on ProxyService

If a class that extends ProxyService throw an exception from handlePermanentError, notifyFailed is never called. That prevent any user of this service from handling issue from this ApiService.
For context, we are currently facing some race condition in the AssigningSubscriber which cause it to fail without notifying the listener. We sometimes are getting new assignment from the server, which cause the client to close some SinglePartitionSubscriber. For some reason, this sometime an error with offset trying to be committed after the stream being close. This failure bubble up to the AssigningSubscriber that close all the SinglePartitionSubscriber. But since one of them is in failed state, this line throw an exception. This bubble up to here. Since this exception is not handled, notifyFailed is not called and we can’t catch the exception and restart our pod.
I'll create a separate issue for this race condition.
com.google.api.gax.rpc.ApiException:
	at com.google.cloud.pubsublite.internal.CheckedApiException.<init>(CheckedApiException.java:51)
	at com.google.cloud.pubsublite.internal.CheckedApiException.<init>(CheckedApiException.java:55)
	at com.google.cloud.pubsublite.internal.ExtractStatus.toCanonical(ExtractStatus.java:48)
	at com.google.cloud.pubsublite.internal.wire.ApiServiceUtils.blockingShutdown(ApiServiceUtils.java:61)
	at com.google.cloud.pubsublite.cloudpubsub.internal.AssigningSubscriber.stop(AssigningSubscriber.java:73)
	at com.google.cloud.pubsublite.cloudpubsub.internal.AssigningSubscriber.handlePermanentError(AssigningSubscriber.java:79)
	at com.google.cloud.pubsublite.internal.ProxyService.onPermanentError(ProxyService.java:73)
	at com.google.cloud.pubsublite.cloudpubsub.internal.AssigningSubscriber.access$000(AssigningSubscriber.java:41)
	at com.google.cloud.pubsublite.cloudpubsub.internal.AssigningSubscriber$1.failed(AssigningSubscriber.java:109)
	at com.google.api.core.AbstractApiService$1.failed(AbstractApiService.java:69)
	at com.google.common.util.concurrent.AbstractService$5.call(AbstractService.java:562)
	at com.google.common.util.concurrent.AbstractService$5.call(AbstractService.java:559)
	at com.google.common.util.concurrent.ListenerCallQueue$PerListenerQueue.run(ListenerCallQueue.java:205)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
	Caused by: java.lang.IllegalStateException: Expected the service InnerService [FAILED] to be TERMINATED, but the service has FAILED
	at com.google.common.util.concurrent.AbstractService.checkCurrentState(AbstractService.java:379)
	at com.google.common.util.concurrent.AbstractService.awaitTerminated(AbstractService.java:336)
	at com.google.api.core.AbstractApiService.awaitTerminated(AbstractApiService.java:104)
	at com.google.cloud.pubsublite.internal.wire.ApiServiceUtils.blockingShutdown(ApiServiceUtils.java:58)
	... 16 common frames omitted
	Caused by: com.google.api.gax.rpc.ApiException: Committed after the stream shut down.
	at com.google.cloud.pubsublite.internal.CheckedApiException.<init>(CheckedApiException.java:51)
	at com.google.cloud.pubsublite.internal.CheckedApiException.<init>(CheckedApiException.java:59)
	at com.google.cloud.pubsublite.internal.CheckedApiPreconditions.checkState(CheckedApiPreconditions.java:38)
	at com.google.cloud.pubsublite.internal.wire.CommitterImpl.commitOffset(CommitterImpl.java:137)
	at com.google.cloud.pubsublite.internal.wire.ApiExceptionCommitter.commitOffset(ApiExceptionCommitter.java:37)
	at com.google.cloud.pubsublite.cloudpubsub.internal.AckSetTrackerImpl.onAck(AckSetTrackerImpl.java:138)
	at com.google.cloud.pubsublite.cloudpubsub.internal.AckSetTrackerImpl.access$100(AckSetTrackerImpl.java:39)
	at com.google.cloud.pubsublite.cloudpubsub.internal.AckSetTrackerImpl$Receipt.onAck(AckSetTrackerImpl.java:76)
	at com.google.cloud.pubsublite.cloudpubsub.internal.SinglePartitionSubscriber$1.ack(SinglePartitionSubscriber.java:92)

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> ☕

Hello gpoulin,
Apologies for this defect, but thank you so much for identifying the issue. I'm going to fix this in #860 and push to a release, I'll follow up once a release with this fix exists with the version number.
Please don't hesitate to reach out if you have other issues, even if you don't have a resolution or full root cause.
-Daniel


Update deno versions

This adds the latest 120 releases to the selectable versions.
BTW, the data was generated by this small tool :guitar:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Marc Redemske seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@mgred Thanks for the PR!
Could you please re-create this PR to a GitLab MR where the new home of rules_deno? The repo is now at https://gitlab.com/aspect-build/rules_deno.
We migrated the home of rules_deno to GitLab since we needed some of our open source repositories on GitLab to serve as demonstration GitLab deployments of Aspect Workflows.
This PR migrated to an MR but the author attribution was lost on the migration so I closed that one.


Update to 1.19.11

https://minecraft.azureedge.net/bin-win/bedrock-server-<IP_ADDRESS>.zip
https://feedback.minecraft.net/hc/en-us/articles/7803469757581
1.19.11 was released and may contain a fix (related to command blocks). Please update bdsx

Thanks for reporting it.
It's updated now.


[Bug]: Requirement parse wrong for transformers

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
It shows 'transformers>=4.15.0' but transformers is 4.20.0 which is indeed satisfying this condition
Installing collected packages: transformers
  Attempting uninstall: transformers
    Found existing installation: transformers 2.3.0
    Uninstalling transformers-2.3.0:
      Successfully uninstalled transformers-2.3.0
Successfully installed transformers-4.20.0
2022-06-20 18:53:31,958 -<PHONE_NUMBER> - test_image_text_embedding.py-test_image_text_embedding:61 - ERROR: Fail to run blip - {'model_name': 'blip_base'}
ERROR MESSAGE: (transformers 2.3.0 (/Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages), Requirement.parse('transformers>=4.15.0'))

The completed log:
Requirement already satisfied: tabulate in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from towhee->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 4)) (0.8.9)
Requirement already satisfied: tqdm>=4.59.0 in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from towhee->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 4)) (4.64.0)
Requirement already satisfied: ruamel.yaml<=0.16.6 in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from towhee->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 4)) (0.16.6)
Requirement already satisfied: pyyaml>=5.1 in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from transformers>=4.15.0->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 6)) (6.0)
Requirement already satisfied: huggingface-hub<1.0,>=0.1.0 in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from transformers>=4.15.0->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 6)) (0.7.0)
Requirement already satisfied: packaging>=20.0 in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from transformers>=4.15.0->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 6)) (21.3)
Requirement already satisfied: filelock in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from transformers>=4.15.0->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 6)) (3.7.1)
Requirement already satisfied: tokenizers!=0.11.3,<0.13,>=0.11.1 in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from transformers>=4.15.0->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 6)) (0.12.1)
Requirement already satisfied: regex!=2019.12.17 in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from transformers>=4.15.0->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 6)) (2022.6.2)
Requirement already satisfied: pyparsing!=3.0.5,>=2.0.2 in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from packaging>=20.0->transformers>=4.15.0->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 6)) (3.0.9)
Requirement already satisfied: idna<4,>=2.5 in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from requests->torchvision>=0.10.0->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 2)) (3.3)
Requirement already satisfied: charset-normalizer~=2.0.0 in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from requests->torchvision>=0.10.0->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 2)) (2.0.12)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from requests->torchvision>=0.10.0->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 2)) (1.26.9)
Requirement already satisfied: certifi>=2017.4.17 in /Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages (from requests->torchvision>=0.10.0->-r /Users/binbin/.towhee/hub/image-text-embedding/blip/main/requirements.txt (line 2)) (2022.6.15)
Installing collected packages: transformers
  Attempting uninstall: transformers
    Found existing installation: transformers 2.3.0
    Uninstalling transformers-2.3.0:
      Successfully uninstalled transformers-2.3.0
Successfully installed transformers-4.20.0
2022-06-20 18:53:31,958 -<PHONE_NUMBER> - test_image_text_embedding.py-test_image_text_embedding:61 - ERROR: Fail to run blip - {'model_name': 'blip_base'}
ERROR MESSAGE: (transformers 2.3.0 (/Users/binbin/Towhee_projects/towhee-test-env-3.8-0.7-new/lib/python3.8/site-packages), Requirement.parse('transformers>=4.15.0'))

Expected Behavior
No error
Steps To Reproduce
import logging
import os
#import ipdb
import subprocess
from towhee import ops

logger = logging.getLogger()
log_path = 'image_text_embedding.log'

image_text_embedding = {
    'blip': [
        {'model_name': 'blip_base'}
    ]
}

def test(data_path):
    if not os.path.isfile(data_path):
        subprocess.call(
            f'wget -O {data_path} https://bair.berkeley.edu/images/BAIR_Logo_BlueType_Tag.png',
            shell=True
        )

    image_decoder = ops.image_decode.cv2()
    # Since the image_decoder returns generator, need to extract output from generator for repetitive usage
    #input_data = [x for x in image_decoder(data_path)]
    input_data = image_decoder(data_path)
    handler = logging.FileHandler(log_path)
    logger.addHandler(handler)
    #ipdb.set_trace()
    for k, v in image_text_embedding.items():
        init_op = getattr(ops.image_text_embedding, k)
        for args in v:
            try:
                op_img = init_op(**args, modality='image')
                img_emb = op_img(input_data)
                op_text = init_op(**args, modality='text')
                text_emb = op_text('using a test description')
                assert img_emb.shape[0] > 0
                print('{}, embedding shape is {}'.format(k, img_emb.shape))
                assert img_emb.shape == text_emb.shape
            except Exception as e:
                logger.error('Fail to run %s - %s', k, str(args))
                print(f'ERROR MESSAGE: {e}')
                pass

if __name__ == '__main__':
    test('bear.jpg')

Environment
- Towhee version(e.g. v0.1.3 or 8b23a93):latest on branch0.7
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:

Anything else?
No response

Now the behavior is:
if the dependency module is not satisfied, will report error, and let user to install the correct version. Then it could go on correctly. so close it.


Frontend Restructuring + MCA/AYIM Overhaul + Discord Bot and Tournament Implementation

REMINDER TO NOT USE PRE-SEEDED MIGRATIONS FOR PROD
Currently contains the following changes:

Removal of MCA-AYIM folder
Centralize API routes
Reorganization of components to be able to reuse common ones between all sites as needed
Restructuring of vuex store
Nominating/voting specific difficulties instead of sets
Website interface for interacting with mapper influence data (Base implemented)
Design overhaul for MCA/AYIM (Base implemented)
osu! api/v2 rewrite + chat bot integration
Migrate admin pages to Corsace instead of multiple admin pages on every site
Fix https://github.com/Corsace/Corsace/issues/186
Fix https://github.com/Corsace/Corsace/issues/193
Rework Discord Bot

Yo nice pr, proud of u man

thanks winber wanna code some shit ,

What's my tc

What's my tc

same as mine (0)

Made under construction page and put that on all the pages that dont have designs from kaetwo yet so that we can get stuff pushed into master for Corsace Open

Thanks winber here's your TC

Dude you forgot to rebase

Good morning winber,
Thanks,
Sincerely,
vinxis


[Feature][Task Plugin] Add Kubeflow task plugin for MLOps scenario #12166

Purpose of the pull request
Overview
Kubeflow task type is used to create tasks on Kubeflow.
The backend mainly uses the kubectl command to create kubeflow tasks, and continues to monitor the resource status on Kubeflow until the task is completed.
Now it mainly supports creating kubeflow tasks using yaml files. If you need to publish kubeflow pipeline tasks, you can use the python task type.
Here are some specific parameters for the Kubeflow plugin

Namespace：The namespace parameter of the cluster
yamlContent：CRD YAML file content

close: #12166
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #12843 (0726ba3) into dev (1347a8f) will increase coverage by 0.09%.
The diff coverage is 80.00%.

@@             Coverage Diff              @@
##                dev   #12843      +/-   ##
============================================
+ Coverage     39.14%   39.23%   +0.09%
- Complexity     4211     4231      +20
============================================
  Files          1046     1051       +5
  Lines         39740    39804      +64
  Branches       4578     4567      -11
============================================
+ Hits          15557    15619      +62
- Misses        22412    22413       +1
- Partials       1771     1772       +1

Impacted Files
Coverage Δ

...r/server/master/runner/task/BaseTaskProcessor.java
16.73% <0.00%> (ø)

...olphinscheduler/plugin/task/api/TaskConstants.java
0.00% <0.00%> (ø)

...scheduler/plugin/kubeflow/KubeflowTaskChannel.java
0.00% <0.00%> (ø)

...er/plugin/kubeflow/KubeflowTaskChannelFactory.java
0.00% <0.00%> (ø)

...lphinscheduler/plugin/kubeflow/KubeflowHelper.java
86.84% <86.84%> (ø)

...dolphinscheduler/plugin/kubeflow/KubeflowTask.java
90.00% <90.00%> (ø)

...nscheduler/plugin/kubeflow/KubeflowParameters.java
100.00% <100.00%> (ø)

...eduler/server/worker/task/WorkerHeartBeatTask.java
70.83% <0.00%> (-10.42%)
:arrow_down:

...eduler/api/dto/schedule/ScheduleCreateRequest.java
83.33% <0.00%> (-2.39%)
:arrow_down:

...e/dolphinscheduler/service/queue/TaskPriority.java
51.31% <0.00%> (-1.25%)
:arrow_down:

... and 30 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Generic Thermostat - Add AUTO support with heat/cool switches

Description:
Add the possibility to have AUTO with temperature_high and temperature_low when component configured to use two switches (one controlling heating and one cooling)
Notes

Decided to renamed heater in heater_control to avoid some users of ac_mode to get undesired behaviour after upgrade if they didn't read breaking changes
It also keeps current functionality if you only specify heater_control or ac_control
away_temp_cool and away_temp_heat are used based on the operation_mode that the thermostat is in
Introduced target_temp_high and target_temp_low for AUTO mode

Breaking changes:

Modified initial_operation_mode to support 'auto', 'heat', 'cool', 'off' when restarting Hass setting operation_mode state, previously just 'off' was being used
Renamed heater to heater_control
Removed ac_mode
Added ac_control to replace ac_mode and enable the new functionality
Removed away_temp and added away_temp_cool and away_temp_heat for the corresponding modes

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#4355
Example entry for configuration.yaml (if applicable):
climate:
  - platform: generic_thermostat
    name: Study
    heater_control: switch.study_heater
    ac_control: switch.study_ac
    target_sensor: sensor.study_temperature

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

@tinloaf sorry for the squash and messing commits, but I failed to do a proper rebase.

This extended version should do what I want indeed but can't get this one to work either. First the target sensor error:
  - platform: mqtt
    state_topic: "tele/dual_cv/SENSOR"
    name: "dual_cv_sensor_bme680_temperature"
    value_template: '{{ value_json.BME680.Temperature }}'

Error:
2018-02-06 18:41:27 ERROR (MainThread) [homeassistant.components.climate.generic_thermostat] Unable to update from sensor: None is not a recognized temperature unit.
But also missing the target temperature buttons no matter what setting:
climate:
  - platform: generic_thermostat
    name: cv_heating
    #heater: switch.basic_woonkamer_bank
    heater_control: switch.basic_woonkamer_bank
    ac_control: switch.basic_woonkamer_bank
    target_sensor: sensor.dual_cv_target
    #min_temp: 18
    #max_temp: 23
    #ac_mode: False
    #target_temp: 21.5
    cold_tolerance: 0.1
    hot_tolerance: 0.3
    min_cycle_duration:
      seconds: 60
    keep_alive:
      minutes: 3
    #initial_operation_mode: "auto"
    #away_temp_heat: 18
    #away_temp_cool: 22
    #temperature_low:
    #temperature_high:

To get away from the sensor error you can use the below:
sensor:
  - platform: mqtt
    state_topic: "tele/dual_cv/SENSOR"
    name: "dual_cv_sensor_bme680_temperature"
    value_template: '{{ value_json.BME680.Temperature }}'
    unit_of_measurement: '°C'

I used the above and published on the topic:
{
   "BME680":{
      "Temperature": "19"
   }
}

or
{
   "BME680":{
      "Temperature": 19
   }
}

All of the above worked using
climate:
  - platform: generic_thermostat
    name: cv_heating
    heater_control: switch.basic_woonkamer_bank
    ac_control: switch.basic_woonkamer_bank
    target_sensor: sensor.dual_cv_sensor_bme680_temperature
    cold_tolerance: 0.1
    hot_tolerance: 0.3
    min_cycle_duration:
      seconds: 60
    keep_alive:
      minutes: 3

I will look on why the temperature controls don't appear when sensor data is not available as now I was able to reproduce this.

 Please add this to the Wiki because more people will struggle with it I presume (just like me, haha). How more info in advance how easier to use ;)
  - platform: mqtt
    state_topic: 'tele/dual_cv/SENSOR'
    name: 'dual_cv_sensor_bme680_temperature'
    unit_of_measurement: '°C'

Allthough the sensor is working now the controls still don't :(

@pascalsaul I'll try to find a workaround in the code, but for this PR i've marked https://github.com/home-assistant/home-assistant-polymer/pull/849 as dependency.

When HA is started it doesn't trigger the heating when it's below the target temperature. In my case the sensor was 21.1 and the target temperature is 21.5 and it didn't call the heating switch....

@pascalsaul please don't comment with feature requests to PRs.

I have removed the test with "logging" however now I have a lot more errors. Unsure if something changed that causes my tests to fail or the tests are wrongly written

This PR seems to have gone stale. Closing it. You can reopen it when you're ready to finish it.

@ciotlosm got around to testing your branch and have some odd behavior when using F units I think, target_temp_low seems to not respond to jump from 21 to 45 and there are only service calls for the target_temp_high control. Will dig around closer tonight.

- platform: generic_thermostat
  name: 1st Floor Thermostat
  heater_control: switch.first_floor_thermostat_heating
  ac_control: switch.first_floor_thermostat_cooling
  target_sensor: sensor.first_floor_thermostat_temperature
  away_temp_cool: 27
  away_temp_heat: 21


[Bug]: WSL2 Ubuntu CLI 3 Gem error nokogiri

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
shopify theme dev should have served my theme successfully and create localhost + editor linkgs
Actual behavior
Got error for nokogiri failure of gem file.
Stack trace
An error occurred while installing nokogiri (1.13.10), and Bundler cannot
continue.

In Gemfile:
  shopify-cli was resolved to 2.33.0, which depends on
    theme-check was resolved to 1.12.1, which depends on
      nokogiri
Fetching gem metadata from https://rubygems.org/.............
Resolving dependencies...
Using ast 2.4.2
Using concurrent-ruby 1.1.10
Using bundler 2.4.2
Using ffi 1.15.5
Using liquid 5.4.0
Using rb-fsevent 0.11.2
Using mini_portile2 2.8.1
Using racc 1.6.2
Using parser <IP_ADDRESS>
Using bugsnag 6.25.1
Using rb-inotify 0.10.1
Using listen 3.7.1
Installing nokogiri 1.13.10 with native extensions
    at makeError (file:///home/linuxbrew/.linuxbrew/lib/node_modules/@shopify/theme/node_modules/execa/lib/error.js:59:11)
    at handlePromise (file:///home/linuxbrew/.linuxbrew/lib/node_modules/@shopify/theme/node_modules/execa/index.js:119:26)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Module.exec (file:///home/linuxbrew/.linuxbrew/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/dist/system.js:41:9)
    at async bundleInstallShopifyCLI (file:///home/linuxbrew/.linuxbrew/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/dist/public/node/ruby.js:197:5)
    at async Task.task (file:///home/linuxbrew/.linuxbrew/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/dist/public/node/ruby.js:131:21)
    at async Task.run (file:///home/linuxbrew/.linuxbrew/lib/node_modules/@shopify/theme/node_modules/listr2/dist/index.js:960:11)
    at async /home/linuxbrew/.linuxbrew/lib/node_modules/@shopify/theme/node_modules/p-map/index.js:57:22 {
  tryMessage: null,
  type: 0,
  nextSteps: undefined,
  command: 'bundle',
  args: [ 'install' ]

Reproduction steps

npm install -g @shopify/cli @shopify/theme in ubuntu 20 on windows machines WSL2
shopify theme dev
failure

Operating System
Windows, WSL 2, Ubuntu
Shopify CLI version (check your project's package.json if you're not sure)
3.31.1
Shell
Terminal
Node version (run node -v if you're not sure)
v16.19.0
What language and version are you using in your application?
ruby 3.2

Got the same issue on node 19.4.0. Super annoying

@Shopify/theme-developer-tools

@matteodepalo Actually, the fix for this issue seems to live at CLI UI kit level (so, I've updated the area)

I see to have solved the issue by changing node version for the project and using a single ruby package installer. Somehow had multiple configured.
So just check which ruby and ruby -v on your machine.
I really dislike WSL, mac setup is so much easier


Applause Application for Zaru

This feature will allow users who enter into Zaru to applaud in desktop and HMD mode. In desktop mode, the user will get a button on the screen and be able to clap with a keyboard key press. In HMD mode, the user will be able to shake their hand controllers to allow them to generate applause sounds and heart particles.
Test Plan - App Setup

In a domain where you have rez permissions, add a cube and put https://hifi-content.s3-us-west-1.amazonaws.com/liv/Prototypes/Clapping-V4/loadApplauseApp.js into the script URL field.

Confirm that the button appears on your HUD / tablet.

Reload scripts (CTRL + R)

Confirm that you do not get multiple instances of the button

Leave the domain and return

Confirm that the button is removed when you exit your domain, and returns when you come back to the domain close to where the cube is.
Test Plan - Desktop Mode

Click on the button for the applause app on your HUD.

Confirm that you are presented with a UI that explains the app and has a toggle to enable the applause setting.

Toggle on the applause setting

Confirm that you see a button with instructions, a toggle for using the particle effects, and a new overlay button has been added to the bottom left corner of your screen.
Confirm that when you click the buttons or press the 't' key on your keyboard that you see applause. Configure the app and open and close it to check that states remain the same when enabling and disabling the components. Toggling off 'use particles' should keep the hearts from showing. Confirm that your avatar scaling changes and that the particles still come from the position of your avatar's head. You should hear audio playing for the clapping.
Test Plan - HMD Mode

Open up the tablet app for the applause app in your HMD.

Confirm that you see the tablet UI and a toggle.

Toggle on the applause setting.

Confirm that you see a gif that shows you how to move your hands.

Try clapping.

Confirm that as you bring your hands close while applause is enabled, your hands flatten out and return to their usual state when pulled away. Confirm that the desktop button overlay is not present around you somewhere in world. Confirm that the particles follow your hands and that the audio plays.

Switch between desktop and VR mode. Confirm that the app cleans up appropriately between swapping (e.g. your hands do not stay flattened, your overlay returns) and maintains your configurations from the app.

Testing complete:
Unfortunately, I was unable to get the script to work on the cube created, to confirm: I had full rez/admin rights in a sandbox and put the URL into the "Script URL" in the cubes Create properties. I was able to open the .js with Running Scripts window as an alternative, but could not get it to do anything on the cubes part.
Fail

Oops. That's the wrong URL for the cube link. That's my mistake in the test plan, not a bug with the script. It's updated now.

(forgot to add comment to say testing, just finishing up)
Testing.

Testing complete:
Test Plan - App Setup
In a domain where you have rez permissions, add a cube and put https://hifi-content.s3-us-west-1.amazonaws.com/liv/Prototypes/Clapping-V4/loadApplauseApp.js into the script URL field.
Confirm that the button appears on your HUD / tablet. Check
Reload scripts (CTRL + R)
Confirm that you do not get multiple instances of the button Check
Leave the domain and return
Confirm that the button is removed when you exit your domain, and returns when you come back to the domain close to where the cube is. Check
Test Plan - Desktop Mode
Click on the button for the applause app on your HUD.
Confirm that you are presented with a UI that explains the app and has a toggle to enable the applause setting. Check
Toggle on the applause setting
Confirm that you see a button with instructions, a toggle for using the particle effects, and a new overlay button has been added to the bottom left corner of your screen. Check
Confirm that when you click the buttons or press the 't' key on your keyboard that you see applause. Configure the app and open and close it to check that states remain the same when enabling and disabling the components. Toggling off 'use particles' should keep the hearts from showing. Confirm that your avatar scaling changes and that the particles still come from the position of your avatar's head. You should hear audio playing for the clapping. Check
Test Plan - HMD Mode
Open up the tablet app for the applause app in your HMD.
Confirm that you see the tablet UI and a toggle. Check
Toggle on the applause setting.
Confirm that you see a gif that shows you how to move your hands. Check
Try clapping.
Confirm that as you bring your hands close while applause is enabled, your hands flatten out and return to their usual state when pulled away. Confirm that the desktop button overlay is not present around you somewhere in world. Confirm that the particles follow your hands and that the audio plays. Check
Switch between desktop and VR mode. Confirm that the app cleans up appropriately between swapping (e.g. your hands do not stay flattened, your overlay returns) and maintains your configurations from the app. Check
This is a Pass in terms of test plan, though I do have one bug to report: The bottom left overlay button when pressed turns black briefly (as the pressed state), I assume this is an error, bug filed for this: 16097
Notes:
Very first time testing I did have an odd issue where the Clap app was not returning upon going back to domain where it resides, cleared my settings which resolved and wasn't able to repro.


Fix a typo

Hi there,
I noticed this small typo in the docs :)
Kind regards,
Hampus Kraft.

Bah, thank you for catching!


Use newer versions of AFNetworking and JWT

This makes StreamHub compatible with use_frameworks in cocoapods. Fixes https://github.com/Livefyre/StreamHub-iOS-SDK/issues/76

@dimat Thank you for the pull! We will take a look and merge after reviewing.


New version: Microsoft.Edge.Beta version 99.0.1150.11

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 2391
Microsoft Reviewers: Open in CodeFlow

Let me see if my PR works...


Ansys QRenderer report convergences and plot

What is the feature being requested?
QRenderer should be able to do this for Q3D, HFSS and  Driven Modal
This needs to be something like
renderer.sim_report()
Use my code from pyEPR

What are use cases for this feature?

This is now being worked on under the analysis-dashboard, which also leads to some modifications of the analysis/renderers for standard results data storage/representation.


Unit Testing new script to generate strandard scenario

To test all the functions of the projects, we could create a script that will generate a list of scenario,
based on the datasets and federated learning approaches currenty supported.
This list would be used as arguments in tests.py to test more complex functions such as split_data (Functions that need scenario mpl dataset objects as arguments)

Obsolete


Feature Request: T-Countdown Timer

It would be amazing if this also had an entity for how long until the next launch, not just the time of the next launch. I'd love to be able to press a button on my dashboard and have one of my media players say "Next SpaceX launch in T-1 day, 2 hours, 3 minutes and 34 seconds" and so on. I've been meaning to figure this out on my own but dealing with dates in HA has been a bit confusing.
Thanks for the great integration!

Released in version 019 which should now be available through HACS.

@julianrinaldi FYI this adds next_launch_countdown which will be in DD:HH:MM:SS format but also has an attribute called t0_countdown which provides an english version of that X days, X hours, X minutes, X seconds until the launch of [mission_name] if you want to use that for Google Broadcast / TTS.

Wow, that's amazing. Thanks!


No eval warning on var e = eval; e("1+1");

http://jshint.com/ doesn't warn about eval in the following code:
var e = eval;
e("1+1");

That's true, but unfortunately, identifying this pattern for all but the most
trivial cases is a very difficult problem. For example,
function foo() { return 'eval'; }
var e = window[ foo() ];
e('1 + 1');

So while I'm no fan of eval, I don't think there is any meaningful way to
address the larger issue here. There's just no substitute for careful code
review!


CI for #6381

What this PR solves / how to test
Running CI for https://github.com/cloudflare/workers-sdk/pull/6381
Author has addressed the following

Tests

[ ] TODO (before merge)
[ ] Included
[ ] Not necessary because:

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[ ] Required / Maybe required
[ ] Not required because:

Changeset (Changeset guidelines)

[ ] TODO (before merge)
[ ] Included
[ ] Not necessary because:

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s):
[ ] Not necessary because:

Moving to #6392


cmd/cgo: undefined reference when linking a program that refers to SIG_DFL.

cgo appears to be unable to link Go programs that refer to SIG_DFL or SIG_IGN.
(This is admittedly an esoteric use-case, since Go programs should generally not be using signal.h in any way.  However, it may be a symptom of some other bug around cgo's handling of function pointers and macros.)
Platform:
$ go version
go version go1.6.1 linux/amd64
$ uname -srio
Linux 3.13.0-83-generic x86_64 GNU/Linux

Source:
$ cat src/sig_dfl/sigdfl.go
package main

import "fmt"

/*
#include <signal.h>
static const void* sig_dfl = SIG_DFL;
*/
import "C"

func main() {
        fmt.Println("%p", C.SIG_DFL)
        fmt.Println("%p", C.sig_dfl)
}

Error:
$ go build sig_dfl
# sig_dfl
/tmp/go-build592850176/sig_dfl/_obj/_cgo_main.o:(.data.rel+0x0): undefined reference to `sig_dfl'
/tmp/go-build592850176/sig_dfl/_obj/_cgo_main.o:(.data.rel+0x8): undefined reference to `SIG_DFL'
collect2: error: ld returned 1 exit status

In general, cgo does a poor job with macros.
The workaround is to not refer to the macro directly, and not make the variable static.
package main

import "fmt"

/*
#include <signal.h>
const void* sig_dfl = SIG_DFL;
*/
import "C"

func main() {
        fmt.Printf("%p\n", C.sig_dfl)
}

Yes, the need for a static variable seems like a reasonable restriction (and not a terribly surprising one).  The problem is that the static variable doesn't work either:
$ cat src/sig_dfl/sigdfl.go
package main

import "fmt"

/*
#include <signal.h>
static const void* sig_dfl = SIG_DFL;
*/
import "C"

func main() {
        fmt.Println(C.sig_dfl)
}

bcmills@midgar:~$ go build sig_dfl
# sig_dfl
/tmp/go-build960726934/sig_dfl/_obj/_cgo_main.o:(.data.rel+0x0): undefined reference to `sig_dfl'
collect2: error: ld returned 1 exit status

Nor does dropping the pointer down to a uintptr_t:
#include <signal.h>
#include <stdint.h>
static const uintptr_t sig_dfl = (uintptr_t)SIG_DFL;

Nor dropping the pointer down to a typedef of void*:
#include <signal.h>
#include <stdint.h>
typedef void* sa_handler_t;
static const sa_handler_t sig_dfl = (sa_handler_t)SIG_DFL;

The only reliable workaround I've found so far is to introduce a static function to return the value, which is suboptimal because it means that I can't define Go constants based on the C constants (the Go values have to become vars).
package main

import "fmt"

/*
#include <signal.h>
static const void* sig_dfl() { return SIG_DFL; };
*/
import "C"

func main() {
	fmt.Println(C.sig_dfl())
}

The need to introduce a variable seems like a reasonable restriction.  The constraint that it cannot be static is surprising given that static functions do work:
package main

import "fmt"

/*
#include <signal.h>
static const void* sig_dfl() { return SIG_DFL; };
*/
import "C"

func main() {
	fmt.Println(C.sig_dfl())
}


Import strategy: Add a back to login button

Import strategy has no button to go back to login
Although it might make sense if there are no accounts in the database, it doesn't in the opposite situation
Once fixed, the back button in inputAccountInfo should redirect to import strategy

Interactive optimization and navigation to landing pages

https://github.com/nemfoundation/symbol-desktop-wallet/pull/96  @evias @decentraliser


Add SPDX license to Solidity files

Without an SPDX license in the Solidity files, some tools will complain:
Warning: SPDX license identifier not provided in source file. Before publishing, consider adding a comment containing "SPDX-License-Identifier: <SPDX-License>" to each source file. Use "SPDX-License-Identifier: UNLICENSED" for non-open-source code. Please see https://spdx.org for more information.

Fixed in #236


Include

After LLVM patch https://reviews.llvm.org/D150997, <variant> is no longer included transitively here.

The shadercache builds failed with "SPIRV-Headers was not found - please checkout a copy under external/" so I'm going to ignore them.


Not able to import python 2 package in tar.gz format

When I want to upload python 2 package in tar.gz format, and I browse to a file location on my computer, the file is grayed out and I am not able to select that file. The file is less than 100MB.
The documentation clearly says that it should be possible to upload a tar.gz file format.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ba1e6e7b-0891-1ec9-8811-ee6d036104a0
Version Independent ID: bfff0c73-1853-f501-49d0-7a2b2a56070b
Content: Manage Python 2 packages in Azure Automation
Content Source: articles/automation/python-packages.md
Service: automation
Sub-service: process-automation
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

Thanks for your comment. We are actively investigating and will get back to you shortly. Thanks for your patience.

@aleksmark Thanks for the feedback! I have tried to reproduce your issue of file getting grayed out while trying to import python 2 packages (distributed archive packages in .whl or .tar.gz format) that are generated from either custom python projects or from here and couldn't see any such grayed out issue but in some scenarios could observe issue like unable to automatically resolve dependencies as I believe while trying to extract the imported .tar.gz package it internally tries to convert that .tar.gz to .whl but would fail if unexpected number of wheel files are created.
Other reference is CSS case<PHONE_NUMBER>02017.
@snehithm @msvijayn @ananthradhakrishnan Can you please review and provide your insights to understand if this is product bug or not.

@KrishnaG-MSFT It seems that the issue only exists on macOS. I am on macOS (10.14.6) and I tried from Chrome/Firefox/Safari. Same issue on all browsers. Check this video for details. https://drive.google.com/file/d/1GJB6BuL0whKyisI2LJN9GiCWgmgGe7xW/view
My coworker tested from windows and she is able to select to file and start the upload. However, the upload fails with error

@aleksmark  Thanks for additional information. Yes, in my previous comment I have mentioned regarding same error which pops up in one scenario i.e., when tried importing using most of .tar.gz packages from here. I have tested this in edge, firefox, chrome.
But importing of .tar.gz packages doesn't have any issue which got generated from simple custom projects i.e., say a simple python project that has empty init.py file, build script setup.py for setuptools, LICENSE and README.md. And if we just generate distribution archives by something like "python2 -m pip install --user --upgrade setuptools wheel" and "python2 setup.py sdist bdist_wheel".

@KrishnaG-MSFT Ok, I see, I did not realize we are talking about the same import error.
So we have two separate issues here?

Not able to select the tar.gz file for upload on macOS
Import fails for some python packages (not OS related)

Escalating to @jaspkaur28 to review and respond.

@aleksmark : For Point 2.  we have an update from the engineering team . During import, Python2 tar.gz packages are converted to .whl file as an intermediate step. The conversion would succeed if the tar.gz package is a simple source only package that doesn’t need compilation. The limitation here is the conversion might fail for some packages which needs compilation because the sandbox environment might not have necessary compilers installed.
It is always preferable to use the .whl file for the module if that is available. In case it is not available, as a workaround you can always convert the package to .whl file with python 2.7 pip on a 64 bit widows machine with required compilers installed.
For example – Numpy import from tar.gz source fails in automation because VC9 compiler is not part of SQLPAL. SQLPAL is built from Windows 10, which does not have VC9 as a default.
For point 1. we need to investigate on why the files show as greyed out for macOS. We've created a bug for the engineering to look into .

PG team is currently working on other high priority items . Please expect a response to it by Q4 CY20.

re-assigning to @jaspkaur28

@femsulu this has not been updated for quite a while, the issue still persists for MacOS, though. Please review


Async ViewDistance

Hi, I have a cool idea!
Your plugin generates chunks, but if you can implement visibility like this plugin, it will be a breakthrough!
https://www.spigotmc.org/resources/fartherviewdistance.84950/

https://github.com/YatopiaMC/C2ME-fabric/issues/17


Add rainbow parens

Rainbow parens provide a nice visual cue about where you are in nesting them:

Plus it's kind of cute, which can make nightmod even more fun :wink:

Since this functionality comes from Nightcode I'll close this issue. See the relevant ticket on that repo: https://github.com/oakes/Nightcode/issues/17


Fixed #1361 sd_cancelBackgroundImageLoadForState

Fixed sd_cancelBackgroundImageLoadForState in sd_setBackgroundImageWithURL method

Thanks @muer2000. I will soon have a look.


Chore/bump sec pymongo

Dependabot security update to 4.6.3

Can we run checks before we merge it?


Windows Update

There are four Windows containers available on the Microsoft Container Registry (MCR), they are:

Windows (aka Windows Workstation)
Windows Server
Windows Server Core
Nano Server
https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-base-images

C:\Users\Administrator>docker exec --rm -it mcr.microsoft.com/windows:ltsc2019
Microsoft Windows [Version 10.0.17763.5458]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\>systeminfo

Host Name:                 484C716DA479
OS Name:                   Microsoft
OS Version:                10.0.17763 N/A Build 17763
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation

The Windows (Workstation) images have many tags, but the current ones are these (and are all the same image):

ltsc2019
10.0.17763.5458
1809
1809-KB5034768
ltsc2019-amd64
10.0.17763.5458-amd64
1809-amd64
1809-KB5034768-amd64

ltsc2019 is always the latest edition.
PS C:\Users\Administrator> docker run --rm -it mcr.microsoft.com/windows/server:ltsc2022
Microsoft Windows [Version 10.0.20348.2322]
(c) Microsoft Corporation. All rights reserved.

C:\>systeminfo

Host Name:                 77E7714D53CC
OS Name:                   Microsoft Windows Server 2022 Datacenter
OS Version:                10.0.20348 N/A Build 20348
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Server
OS Build Type:             Multiprocessor Free
Registered Owner:          N/A
Registered Organization:   N/A
Product ID:                00454-60000-00001-AA992

The Windows Server images also have many tags, but the current ones are these (and are all the same image):

ltsc2022-KB5034770
ltsc2022
10.0.20348.2322
10.0.20348.2322-amd64
ltsc2022-KB5034770-amd64
ltsc2022-amd64

ltsc2022 is always the latest edition.
Interestingly, Server Core still supports LTSC 2016, 2019 and 2022.
In src-opam/distro.ml we have tried to maintain a list of Windows 10 releases which historically could be used to map to the tag on MCR, however, the current version of Windows is 22H2 but there is no tag.  There are some other tags such as 20H2 and 2004 but they have been deprecated since 2022.  We cover this discrepancy by having win10_latest_image and win10_latest_release.
We have also have a table of Latest Cumulative Updates (LCU) dates and Knowledge Base (KB) article numbers in win10_lcus. This table is a mix of Windows Server and Windows workstation releases. Given the fragment below:

KB5032198 applies to Windows Server 2022
KB5032189 applies to Windows (Workstation) 21H2 and 22H2
KB5032196 applies to both Windows Server 2019 and Windows (Workstation) 1809

let win10_lcus : ('a * int * win10_release list) list =
  [
    (`LCU20231114, 5032198, [ `V21H2 ]);
    (`LCU20231114, 5032189, [ `V21H1 ]);
    (`LCU20231114, 5032196, [ `V1809 ]);

We have been treating Windows Server as a later build of Windows (Workstation).
This PR acknowledges this difference by adding WindowsServer as a type in os_family_of_distro. Then updates distro to recognize the two variants:
@@ -554,81 +327,15 @@ let distros : t list =
     `Ubuntu `V23_10;
     `Ubuntu `Latest;
     `Ubuntu `LTS;
+    `Cygwin `Ltsc2016;
+    `Cygwin `Ltsc2019;
+    `Cygwin `Ltsc2022;
+    `Windows (`Mingw, `Ltsc2019);
+    `Windows (`Msvc, `Ltsc2019);
+    `WindowsServer (`Mingw, `Ltsc2022);
+    `WindowsServer (`Msvc, `Ltsc2022);
   ]

In summary, rather than having a table of Windows editions and loosely mapping that on to the available Docker images, this approaches it from what Docker images are available and surfacing those as the Windows releases. This approach more closely matches that of the Linux distributions and standardizes much of the file layout.
This will also simplify maintenance as the base image builder will automatically pull the latest revision on the weekly rebuild cycle.

I am struggling to get the KB number: from within Windows, we can list the installed hotfixes and the associated KB numbers, e.g. Get-Hotfix, but the commands don't return a single KB. They return several, such as the latest SSU, and .Net CU and the Windows CU.
The Microsoft Container Registry API (aka the Docker API) doesn't directly provide a way to list tags which point to the same image.  We can list tags with curl -s -H "Accept: application/vnd.docker.distribution.manifest.list.v2+json" https://mcr.microsoft.com/v2/windows/manifests/ltsc2019 and iterate over them curl -s -H "Accept: application/vnd.docker.distribution.manifest.list.v2+json" https://mcr.microsoft.com/v2/windows/manifests/$tag to find images with the same digest.
We could use ver to get something like 10.0.17763.5576.  This is published as a tag; thus, FROM mcr.microsoft.com/windows/servercore:10.0.17763.5576 would work.
The next issue is getting that value into the base image builder.  OCaml-CI has the same issue as it wants to obtain various opam vars from a Docker image, and we do that by running the image on the OCaml-CI server.  The challenge is that Microsoft Windows containers can't be executed on a Linux server.
We can create an obuilder job spec as below and submit that to the cluster.  Ocluster/obuilder jobs don't return anything other than the image ID, so we would need to parse the log output.  ocluster-client -c ~/mtelvers.cap submit-obuilder --pool windows-1809-x86_64 --local-file ver.spec
 ((from mcr.microsoft.com/windows/servercore:ltsc2019)
 (run (shell "ver")))

However, it occurs to me that, in terms of repeatability, even if we say from windows:ltsc2019, providing the log indicates the actual version/image that was used, anyone trying to reproduce the exact set of conditions would be able to do so.  As it stands, this information is available:
Step 1/56 : FROM mcr.microsoft.com/windows:ltsc2019 as winget-builder
ltsc2019: Pulling from windows
Digest: sha256:5a7c981ca39d069ae40bd344fe464494465b329d19c2fa262c4a556780008c7d
Status: Image is up to date for mcr.microsoft.com/windows:ltsc2019

At some future point, when the tag ltsc2019 has moved forward, we could reproduce this step with:
FROM mcr.microsoft.com/windows:ltsc2019@sha256:5a7c981ca39d069ae40bd344fe464494465b329d19c2fa262c4a556780008c7d as winget-builder

We could add a specific RUN step to output the current KBs, Windows version or the entire output of systeminfo.


Text is invisible on mobile phone

Text becomes invisible in iPhone as shown above. It's fine on desktop browsers though.
Workaround for now:
<FloatingWhatsApp
        accountName='ABC'
        phoneNumber='1234567890'
        style={{color: '#111111'}}    // <----- override color here
/>

This maybe again happening due to styles clashing and, if this is the case, we can resolve this in a couple of ways:

Add !important to all css styles you have defined.
Provide override ability for all the elements like you have for the main div and main whatsapp button.
Wrap your React component in a secluded style context to prevent such a clash.

I had the same issue in light mode. But I fix it by wrapping the component in a div and adding css styles to the div as you suggested @rampatra.
I was wondering if it's possible to set sync the darkMode with the screen preference. So it will change when I use my ThemeToggler


Remove shared subscriptions prefix when matching topics

My MQTT broker (VerneMQ) allows shared subscriptions even when running v3... though I believe technically they're a v5 feature (https://www.hivemq.com/blog/mqtt5-essentials-part7-shared-subscriptions/).
I'm honestly not thrilled about this particular implementation - it was the easy route but requires a regex on each receive.  A better solution would probably be to re-architect subscriptions and separate the topic from the filter (since those can be different in the case of shared subscriptions).
So mostly just throwing this out there to see what you think.

probably better to do something like

filter_array = filter.split('/')
filter_array = filter_array[2..-1] if filter_array.first.starts_with?("$")

Add a spec too and I'll merge :)


Fix build for release automation

I failed to cut a release with my previous attempt. This PR changes the build config to stop using Gradle tasks and uses plain Kotlin functions instead. I was spending a lot of time trying to debug why the tasks were not running, and realized we don't get any benefits from using Gradle tasks anyways (like automatic caching).
Test plan
Green CI.

OK, I think this is ready to go. CI is taking 8 minutes though, which is not great so I want to fix that


Wrong display

How can i fix this?

are u overriding styles ?
please tell how you are using submit button.
how can i reproduce this ?

@ronak301 I just import SubmitButton from 'react-native-submit-button'; and call <View style={{flex:1}}>         <SubmitButton />       </View>

Can u please try now. I have updated.

The same, I'm using android simulator 4.2.2

Please follow below steps :
1 ) remove react-native-submit-button from node modules.
2 ) remove entry from package.json
3 ) run npm install --save react-native-submit-button
4 ) rnpm link


Fix citation file

The cff-version on the cff file was updated by bump-my-version. Also, the URL to the repo was not valid.
The cff file has been fixed and a validation workflow has been added.

So we now in 2 separate places ensure that such mistakes don't happen again:

in the release workflow, we are checking that the CFF is valid.
the bump-version settings are more explicit to ensure only the correct lines get bumped

I can't comment on a file that is not changed, so:
actions/checkout@v3 in cffconvert.yml is deprecated and should be replaced with actions/checkout@v4. See warning here: https://github.com/EIT-ALIVE/eitprocessing/actions/runs/11627693839 and docs blogpost here: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Sure, I'll update it

I assume this can just be merged to main without making a new release. Could you also merge it to develop? #314 may have a conflict with this PR, so I need to rebase that before merging with develop.

I can also just merge to develop and the changes go with the next release. Also, a release will be necessary to update the reference in Zenodo, because it was broken and it is not up to date.

I can also just merge to develop and the changes go with the next release. Also, a release will be necessary to update the reference in Zenodo, because it was broken and it is not up to date.

In that case I think this PR could be used to make a patch release via https://github.com/EIT-ALIVE/eitprocessing/actions/workflows/release_github.yml, which will automatically be merged to develop.

I can also just merge to develop and the changes go with the next release. Also, a release will be necessary to update the reference in Zenodo, because it was broken and it is not up to date.

In that case I think this PR could be used to make a patch release via https://github.com/EIT-ALIVE/eitprocessing/actions/workflows/release_github.yml, which will automatically be merged to develop.

@psomhorst , if everything is now ok, please go ahead and do the release.


Style renderer example

This pull request adds an example that shows how to use a custom style renderer.

See https://deploy-preview-11467--ol-site.netlify.app/examples/style-renderer.html for a preview of the new example.


xds: always use :: and IPv4Compact for dynamic listener

this's a huge changes seperated from https://github.com/envoyproxy/gateway/pull/4690.
we still need a PR to fix the bootstrap, especially for admin endpoint.

@zirain let's hold this after v1.2.2 because it changes too many files and make cherry-picking harder.

@zirain let's hold this after v1.2.2 because it changes too many files and would make cherry-picking harder.

@zhaohuabing imo this should of v1.2 since its part of the dual stack feature

@zirain let's hold this after v1.2.2 because it changes too many files and would make cherry-picking harder.

@zhaohuabing imo this should of v1.2 since its part of the dual stack feature

OK, let's cherry-pick this to v1.2.2

LGTM thanks.
Non-blocking: Envoy now listens on all IP Families by default including IPv4 and IPv6, regardless of the IPFamily setting. It might be usefult to clarify this in the IPFamily docs to avoid potential confusion.

LGTM thanks!
One non-blocking comment: Envoy now listens on all IP Families by default including IPv4 and IPv6, regardless of the IPFamily setting. It might be usefult to clarify this behavior in the IPFamily API docs to avoid potential confusion.

Will update these once we make an agreement on admin endpoint.


Add noble cryptographic libraries.

Hey there!
Adding a few awesome modules. The basic idea was that indunty/elliptic and friends have like 100 dependencies each, and every dep there could get hacked and screwed. One thing that's extremely important for cryptographic primitives is trustworthiness, and modern libs don't have it.
So, i've created noble libraries - they don't use any deps, are self-contained and written in TypeScript. All of them use built-in js bigints, so this is something not yet supported by almost any competition lib. Another goal for noble was to write code that can be audited by non-cryptographers. Easy!

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks Ryan!


Understanding the Cost Volume

I refer to this section of the code:
        cost = Variable(torch.FloatTensor(refimg_fea.size()[0], refimg_fea.size()[1]*2, self.maxdisp/4,  refimg_fea.size()[2],  refimg_fea.size()[3]).zero_()).cuda()

        for i in range(self.maxdisp/4):
            if i > 0 :
             cost[:, :refimg_fea.size()[1], i, :,i:]   = refimg_fea[:,:,:,i:]
             cost[:, refimg_fea.size()[1]:, i, :,i:] = targetimg_fea[:,:,:,:-i]
            else:
             cost[:, :refimg_fea.size()[1], i, :,:]   = refimg_fea
             cost[:, refimg_fea.size()[1]:, i, :,:]   = targetimg_fea
        cost = cost.contiguous()

Cost volume is of size (64, 48, 96, 312) where its made of 32 [48,96,312] tensor for left image and 32 [48,96,312] tensor for right image. But the way it is filled with the feature vector is very confusing. I cannot understand this part

             cost[:, :refimg_fea.size()[1], i, :,i:]   = refimg_fea[:,:,:,i:]
             cost[:, refimg_fea.size()[1]:, i, :,i:] = targetimg_fea[:,:,:,:-i]

Why is it that for increasing disparity, you only fill a subset of the columns? What is the rationale for this?

@soulslicer
This operation is to match the left and right features at  the corresponding disparity.

Yes, but the cost volume is containing repeating information from the feature maps.
From what I see here, as the disparity increases, you fill less and less features for the left image, and more and more features from the right image in the columnwise direction.
I still cannot understand the rationale. Obviously, having larger disparity requires a larger observation of the features spatially, so it makes sense to increase it for the right image, but why decrease it for left?

We assume that there are 1x5 images need to match as below.
Left: ■▼◆★▲    ;     Righ: □▽◇☆△
According to our matching code, the cost volume will become
at disp 0:     |     at disp 1:   |     at disp 2:
■▼◆★▲    |    0▼◆★▲    |    00◆★▲
□▽◇☆△     |    0□▽◇☆     |    00□▽◇
The occlusion will be filled with zeros.


Encoding tests against VRF gives error in runner

When the encoding test is started, the following message appears in the TC Runner log output.
tc-runner_1                     | 2018-09-26 08:06:09,175 : JMSTestRunner:onMessageConsumer:run: de.fraunhofer.iosb.tc_encodingrulestester.TC0001
tc-runner_1                     | 2018-09-26 08:06:09,183 : JMSTestRunner:onMessageConsumer:run: tsRunFolder is /root/conf/TestSuites/TS_HLA_EncodingRulesTester-1.0.1/bin
tc-runner_1                     | 2018-09-26 08:06:09,184 : JMSTestRunner:onMessageConsumer:run: TC DIR is /root/application
tc-runner_1                     | 2018-09-26 08:06:09,185 : JMSTestRunner:onMessageConsumer:run: The test case class is: de.fraunhofer.iosb.tc_encodingrulestester.TC0001
tc-runner_1                     | Exception in thread "Thread-3" java.lang.NullPointerException
tc-runner_1                     |       at de.fraunhofer.iosb.testrunner.JMSTestRunner$TestScheduleRunner.extendThreadClassLoader(JMSTestRunner.java:140)
tc-runner_1                     |       at de.fraunhofer.iosb.testrunner.JMSTestRunner$TestScheduleRunner.run(JMSTestRunner.java:183)
tc-runner_1                     |       at java.lang.Thread.run(Thread.java:745)
```

The line (JMSTestRunner.java:140) is a memory allocation of an array of urls. This is not currently checked for allocation of zero nember of urls, which may lead to this exception.
The root of the problem seems to be that no files are found/readable in the "IVCT_Runtime\TestSuites\TS_HLA_EncodingRulesTester-1.0.1\lib" folder. Is it possible to check whether the contents of this folder is accessible?

The volume handling got changed last week (irt Kubernetes). The shipsim composition was not correct anymore. I just fixed it and committed a corrected version. Works now.


Add AssociationAuthorization Calls to list_Route53

route53:CreateVPCAssociationAuthorization
route53:DeleteVPCAssociationAuthorization
route53:ListVPCAssociationAuthorization
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Internal ticket number CFN-7119


unit test changes

We need to have googletest-release-1.8.0.zip in the third_party folder and do “unzip -o googletest-release-1.8.0.zip” from the third_party folder.

I think this can be merged now. Please let me know if any more changes are needed.


Can't generate example, missing gogo.proto

Sorry to bother you, I have another issue. I just tried the example and it fails on gogo.proto. I've tried to install it but it seems to be not effective.
❯ go get -u github.com/gogo/protobuf/proto
go: found github.com/gogo/protobuf/proto in github.com/gogo/protobuf v1.3.1
❯ ~/go/bin/gen --sqltype=postgres \
        --connstr "user=postgres dbname=postgres sslmode=disable password=pass port=5432 host=<IP_ADDRESS>" \
        --database main  \
        --json \
        --gorm \
        --guregu \
        --rest \
        --out ./example \
        --module example.com/rest/example \
        --mod \
        --server \
        --makefile \
        --json-fmt=snake \
        --generate-dao \
        --generate-proj \
        --overwrite
Generating code for the following tables (3)
[0] goose_db_version
[1] orders
[2] products
github.com/gogo/protobuf/gogoproto/gogo.proto does not exist on path - install with
go get -u github.com/gogo/protobuf/proto

I think I found the issue but I am not sure that I understand why we need this :
	srcPath := filepath.Join(gopath, "src")
	gogoPath := filepath.Join(gopath, "src/github.com/gogo/protobuf/gogoproto/gogo.proto")
	gogoImportExists := dbmeta.Exists(gogoPath)

Personal I don't have the src directory and of course all the rest. For me is installed in the pkg

GO111MODULE=off go get  github.com/gogo/protobuf/proto


[SPARK-29774][SQL] Date and Timestamp type +/- null should be null as Postgres

#26157 # What changes were proposed in this pull request?

Date time literals +/- nulls produce nulls not exceptions
Why are the changes needed?

Feature Parity between PostgreSQL and Spark
Does this PR introduce any user-facing change?

Yes, select date '1999-12-31' - null;  is null, not exception now.
How was this patch tested?

add ut

Test build #113314 has started for PR 26412 at commit 0b293db.

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-K8s/18219/
Test PASSed.

cc @maropu and @MaxGekk

Test build #113314 has finished for PR 26412 at commit 0b293db.

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/113314/
Test FAILed.

Test build #114511 has started for PR 26412 at commit e7225a3.

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-K8s/19341/
Test PASSed.

Ah, I see. The change looks reasonable to me. Just in case, can you check behaivours in the other systems?

also check with presto
presto> select date('1900-01-01') - null;
 _col0
-------
 NULL
(1 row)

Query 20191127_065501_00001_9md27, FINISHED, 1 node
Splits: 17 total, 17 done (100.00%)
0:00 [0 rows, 0B] [0 rows/s, 0B/s]

Test build #114511 has finished for PR 26412 at commit e7225a3.

This patch fails due to an unknown error code, -9.
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/114511/
Test FAILed.

retest this please

Test build #114528 has started for PR 26412 at commit e7225a3.

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-K8s/19357/
Test PASSed.

Test build #114534 has started for PR 26412 at commit b925517.

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-K8s/19363/
Test PASSed.

Test build #114528 has finished for PR 26412 at commit e7225a3.

This patch fails SparkR 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/114528/
Test FAILed.

Test build #114534 has finished for PR 26412 at commit b925517.

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/114534/
Test PASSed.

IIUC, the NullIntolerant is not for this type coercion thing.

I think it's all because we hack the Add operator to do date add. Now we need to add more hacks in the type coercion rules.
How about we create UnresolvedAdd in the parser, and convert it to either Add or DateAdd in the analyzer?

I think it's all because we hack the Add operator to do date add. Now we need to add more hacks in the type coercion rules.
How about we create UnresolvedAdd in the parser, and convert it to either Add or DateAdd in the analyzer?

This is better, I will follow this sugguestion, thanks.

Test build #114718 has started for PR 26412 at commit e8b75ba.

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-K8s/19543/
Test PASSed.

Test build #114718 has finished for PR 26412 at commit e8b75ba.

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/114718/
Test FAILed.

Test build #114723 has started for PR 26412 at commit 02b3738.

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-K8s/19547/
Test PASSed.

Test build #114723 has finished for PR 26412 at commit 02b3738.

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/114723/
Test FAILed.

Test build #114726 has started for PR 26412 at commit e89d806.

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-K8s/19550/
Test PASSed.

Test build #114733 has started for PR 26412 at commit 0694e07.

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-K8s/19557/
Test PASSed.

Test build #114726 has finished for PR 26412 at commit e89d806.

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/114726/
Test FAILed.

Test build #114733 has finished for PR 26412 at commit 0694e07.

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/114733/
Test FAILed.

Test build #114754 has started for PR 26412 at commit 0f5618b.

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-K8s/19576/
Test PASSed.

Test build #114754 has finished for PR 26412 at commit 0f5618b.

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/114754/
Test FAILed.

Test build #114762 has started for PR 26412 at commit efab3ec.

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-K8s/19584/
Test PASSed.

Test build #114762 has finished for PR 26412 at commit efab3ec.

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/114762/
Test FAILed.

Test build #114780 has started for PR 26412 at commit 1c27be1.

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-K8s/19601/
Test PASSed.

Test build #114788 has started for PR 26412 at commit 5df6980.

Test build #114780 has finished for PR 26412 at commit 1c27be1.

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/114780/
Test FAILed.

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-K8s/19610/
Test PASSed.

Test build #114791 has started for PR 26412 at commit 9817d2d.

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-K8s/19612/
Test PASSed.

Test build #114792 has started for PR 26412 at commit 9808b9c.

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-K8s/19613/
Test PASSed.

Test build #114793 has started for PR 26412 at commit b190612.

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-K8s/19614/
Test PASSed.

Test build #114788 has finished for PR 26412 at commit 5df6980.

This patch fails Spark unit 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-K8s/19617/
Test PASSed.

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/114788/
Test FAILed.

Test build #114795 has started for PR 26412 at commit e544137.

Test build #114792 has finished for PR 26412 at commit 9808b9c.

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/114792/
Test FAILed.

Test build #114791 has finished for PR 26412 at commit 9817d2d.

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/114791/
Test FAILed.

Test build #114793 has finished for PR 26412 at commit b190612.

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/114793/
Test FAILed.

Test build #114795 has finished for PR 26412 at commit e544137.

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/114795/
Test FAILed.

Test build #114818 has started for PR 26412 at commit 83705fd.

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-K8s/19641/
Test PASSed.

Test build #114824 has started for PR 26412 at commit 846802d.

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-K8s/19647/
Test PASSed.

Test build #114818 has finished for PR 26412 at commit 83705fd.

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/114818/
Test FAILed.

Test build #114825 has started for PR 26412 at commit 4af7edb.

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-K8s/19648/
Test PASSed.

Test build #114824 has finished for PR 26412 at commit 846802d.

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/114824/
Test FAILed.

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-K8s/19652/
Test PASSed.

Test build #114829 has started for PR 26412 at commit a67be30.

Test build #114830 has started for PR 26412 at commit 9a1affd.

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-K8s/19653/
Test PASSed.

Test build #114832 has started for PR 26412 at commit ae70022.

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-K8s/19655/
Test PASSed.

Test build #114825 has finished for PR 26412 at commit 4af7edb.

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/114825/
Test FAILed.

Test build #114839 has started for PR 26412 at commit 571225b.

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-K8s/19662/
Test PASSed.

Test build #114830 has finished for PR 26412 at commit 9a1affd.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #114832 has finished for PR 26412 at commit ae70022.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #114829 has finished for PR 26412 at commit a67be30.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #114839 has finished for PR 26412 at commit 571225b.

This patch fails due to an unknown error code, -9.
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/114839/
Test FAILed.

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/114832/
Test FAILed.

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/114830/
Test FAILed.

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/114829/
Test FAILed.

retest this please

Test build #114843 has started for PR 26412 at commit 571225b.

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-K8s/19666/
Test PASSed.

Test build #114843 has finished for PR 26412 at commit 571225b.

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/114843/
Test FAILed.

retest this please

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-K8s/19678/
Test PASSed.

Test build #114855 has started for PR 26412 at commit 571225b.

Test build #114855 has finished for PR 26412 at commit 571225b.

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/114855/
Test FAILed.

retest this please

Test build #114867 has started for PR 26412 at commit 571225b.

File "/home/jenkins/workspace/SparkPullRequestBuilder/python/pyspark/sql/dataframe.py", line 1334, in pyspark.sql.dataframe.DataFrame.selectExpr
Failed example:
    df.selectExpr("age * 2", "abs(age)").collect()
Differences (ndiff with -expected +actual):
    - [Row((age * 2)=4, abs(age)=2), Row((age * 2)=10, abs(age)=5)]
    + [Row(unresolvedmultiply(age, 2)=4, abs(age)=2), Row(unresolvedmultiply(age, 2)=10, abs(age)=5)]
**********************************************************************
   1 of   1 in pyspark.sql.dataframe.DataFrame.selectExpr
***Test Failed*** 1 failures.

There is an actual error

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-K8s/19690/
Test PASSed.

The result is unexpected. In ResolveAlias, we only generate the alias if expression is resolved. How does pyspark generate alias for its Row object? cc @HyukjinKwon

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-K8s/19695/
Test PASSed.

Test build #114872 has started for PR 26412 at commit 6052e5a.

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-K8s/19696/
Test PASSed.

Test build #114873 has started for PR 26412 at commit 928fd86.

Test build #114867 has finished for PR 26412 at commit 571225b.

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/114867/
Test FAILed.

Test build #114872 has finished for PR 26412 at commit 6052e5a.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class UnresolvedAdd(left: Expression, right: Expression) extends UnresolvedBinaryExpression

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/114872/
Test FAILed.

Test build #114873 has finished for PR 26412 at commit 928fd86.

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/114873/
Test FAILed.

Test build #114886 has started for PR 26412 at commit 5dd632c.

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-K8s/19709/
Test PASSed.

It seems like UnresolvedBinaryExpression brings some troubles and may add maintenance overhead.
How about this:

We still create Add in the parser
type coercion rules only deal with the normal Add operation, e.g. int + int, interval + interval.
the new rule ResolveBinaryArithmetic finds the unresolved Add, and turn them into DateAdd, etc. depending on the data types.

Test build #114886 has finished for PR 26412 at commit 5dd632c.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class UnresolvedBinaryExpression(operator: String)
case class UnresolvedAdd(left: Expression, right: Expression)

It seems like UnresolvedBinaryExpression brings some troubles and may add maintenance overhead.
How about this:

We still create Add in the parser
type coercion rules only deal with the normal Add operation, e.g. int + int, interval + interval.
the new rule ResolveBinaryArithmetic finds the unresolved Add, and turn them into DateAdd, etc. depending on the data types.

Simply replace the UnresolvedXX and change them back to the old ones

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/114886/
Test FAILed.

Test build #114893 has started for PR 26412 at commit c84d46e.

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-K8s/19716/
Test PASSed.

Test build #114893 has finished for PR 26412 at commit c84d46e.

This patch fails due to an unknown error code, -9.
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/114893/
Test FAILed.

retest this please

Test build #114896 has started for PR 26412 at commit c84d46e.

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-K8s/19718/
Test PASSed.

Test build #114897 has started for PR 26412 at commit a44948e.

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-K8s/19719/
Test PASSed.

looks pretty good, let's see how tests go this time.

Test build #114896 has finished for PR 26412 at commit c84d46e.

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/114896/
Test PASSed.

Test build #114897 has finished for PR 26412 at commit a44948e.

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/114897/
Test PASSed.

thanks, merging to master!

Sorry, @cloud-fan, I just checked the cc.

The result is unexpected. In ResolveAlias, we only generate the alias if expression is resolved. How does pyspark generate alias for its Row object? cc @HyukjinKwon

I don't think there's any differences for the column names being generated PySpark specifically.

@yaooqinn Thanks for the work, but I don't know the behavior before this PR from the PR description and discussions. I would suggest adding that in the PR description as well.
I have to check with Spark 2.4.4 to find the previous behavior:
> spark.sql("select timestamp'1999-12-31 00:00:00' - null").show()
org.apache.spark.sql.AnalysisException: cannot resolve '(TIMESTAMP('1999-12-31 00:00:00.0') - NULL)' due to data type mismatch: differing types in '(TIMESTAMP('1999-12-31 00:00:00.0') - NULL)' (timestamp and null).; line 1 pos 7;
'Project [unresolvedalias((946627200000000 - null), None)]
+- OneRowRelation

Hi @gengliangwang, thanks for your suggestion, I have updated the description. Can you check whether it is clear enough.

date_add/date_sub functions only accept int/tinynit/smallint as the second arg

Do you mean time_add/time_sub? BTW we should have a migration guide for it.

It is date_add and date_sub, we have made them ExpectsInputTypes . I'll raise a followup to add a migration guide.


KubeCon CloudNativeCon Hong Kong 24

https://events.linuxfoundation.org/kubecon-cloudnativecon-open-source-summit-ai-dev-china/program/call-for-proposal/#submit-your-proposal

We need to ask how we apply for a slot in the sandbox "corner" (kiosk something)
https://contribute.cncf.io/resources/project-services/outreach-events/

Form to submit for HK for in-kiosk: https://events.linuxfoundation.org/kubecon-cloudnativecon-open-source-summit-ai-dev-china/program/project-opportunities/#request-to-participate

Deadline is 31st of May

or 18th of June, not sure:

We are writing to notify you that your submission, Unlocking the Potential of Edge Computing with Kairos: Bridging the Gap Between Cloud and Edge, has been added to our waitlist.
...
Overall, the co-chairs were impressed with your submission and should a slot become available by Friday, 5 July, we will reach out to inquire whether you would like us to include it in the conference.

Fort Kairos talk was not accepted

Still making sure people got their t-shirts but I will close, there isn't much to see here.


[iOS] Create FlutterViewControllers at same time will result in crash.

Steps to Reproduce

While Adding Flutter to existing App, I found it's easy to crash when some  FlutterViewControllers launch at same time.

- (void)handleButtonAction {
    FlutterViewController *controller = [[FlutterViewController alloc]init];
    FlutterViewController *controller1 = [[FlutterViewController alloc]init];
    FlutterViewController *controller3 = [[FlutterViewController alloc]init];
    FlutterViewController *controller4 = [[FlutterViewController alloc]init];
    FlutterViewController *controller5 = [[FlutterViewController alloc]init];
    FlutterViewController *controller6 = [[FlutterViewController alloc]init];
    FlutterViewController *controller7 = [[FlutterViewController alloc]init];

    [controller setInitialRoute:@"loginCenter"];
    [controller.view setBackgroundColor:[UIColor clearColor]];
    controller.modalPresentationStyle = UIModalPresentationOverCurrentContext;
    controller.viewOpaque = NO;
    self.modalPresentationStyle = UIModalPresentationCurrentContext;

    controller.hidesBottomBarWhenPushed = YES;
    [self presentViewController:controller animated:NO completion:nil];
}

As I triggered the method above, it will crash in FlutterViewController's viewWillAppearmethod.
Guess engine over-released some resources.
This is a particular situation while I didn't really write like this. However, I'm working on a hybrid app. When launching this app, in some cases, similar situation will happen .

Target Platform: iOS
Target OS version/browser: all
Devices: all
Logs

[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.15.1 19B88, locale zh-Hans)
    • Flutter version 1.9.1+hotfix.6 at /Users/gzh/dev/flutter
    • Framework revision 68587a0916 (3 months ago), 2019-09-13 19:46:58 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/gzh/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.2.1, Build version 11B500
    • CocoaPods version 1.8.3

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 40.2.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] Connected device (1 available)
    • iPhone 11 Pro Max • 6C179851-5A92-42B6-84A8-1176EABA62D4 • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-2 (simulator)

Hi @MrLittleStrong
could you please provide your flutter run --verbose  ?
Thank you

Hi @MrLittleStrong
could you please provide your flutter run --verbose ?
Thank you

this command seems too long to paste.
flutter_run_verbose.txt

From the example, it is not clear if you built with or without ARC. If you built with ARC, it could be that the error is in engine teardown instead of creation. A symbolicated stack trace would be useful too.

Hi @MrLittleStrong
Can you please details asked above https://github.com/flutter/flutter/issues/45802#issuecomment-643550162
Can you please provide your flutter doctor -v your flutter run --verbose and a complete reproducible minimal code sample
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.