Crashlytics reports not showing on the dashboard.

Crashes are not being reported on the dashboard even though with debugging enabled its says the report was delivered successfully. Ive pretty much tried everything possible and also every stack overflow suggestion going and it still doesn't show any crash reports. One thing of interest is event though the reports are not showing the crash statistics is being affected and decreasing every time i do a crash test. Ive attached the debug log.
Using iOS 12.4, iPhone XS & Xcode 11
2019-09-19 11:16:50.884738+0100 Sprint-iOS[19664:1731535] [Crashlytics] Version 3.14.0 (144) 2019-09-19 11:16:50.884841+0100 Sprint-iOS[19664:1731535] [Crashlytics] Running on iPhone11,2, 12.4.1 (16G102)     "com.twitter.crashlytics.ios" = "3.14.0"; 2019-09-19 11:16:51.513922+0100 Sprint-iOS[19664:1731825] [Crashlytics:Crash:Reports] Packaged report with id '10eed41e8bcc46e2b2fba3d57a323c15' for submission 2019-09-19 11:16:51.514001+0100 Sprint-iOS[19664:1731825] [Crashlytics:Crash:Reports] Submitting report 2019-09-19 11:16:51.514133+0100 Sprint-iOS[19664:1731825] [Crashlytics:Crash:Reports] Submitting async /var/mobile/Containers/Data/Application/0481E460-7E05-4FD1-8C4E-485F602E00FD/Library/Caches/com.crashlytics.data/com.tricktrack.sprint/v3/prepared/8D821963-AF43-48B7-8CA5-BB01B805796A.multipartmime 2019-09-19 11:16:51.514981+0100 Sprint-iOS[19664:1731825] [Crashlytics:Crash:Reports:Event] Sending event. 2019-09-19 11:16:51.704549+0100 Sprint-iOS[19664:1731825] [Crashlytics:Crash:Reports] completed submission of /var/mobile/Containers/Data/Application/0481E460-7E05-4FD1-8C4E-485F602E00FD/Library/Caches/com.crashlytics.data/com.tricktrack.sprint/v3/prepared/02857779-A04A-4AF4-8E1F-A2473F6859DC.multipartmime 2019-09-19 11:16:51.705684+0100 Sprint-iOS[19664:1731825] [Crashlytics:Crash] report submission successful 2019-09-19 11:16:51.873884+0100 Sprint-iOS[19664:1731846] [Answers] Attempting to log app_crashed 2019-09-19 11:16:52.265520+0100 Sprint-iOS[19664:1731838] [Crashlytics:Crash:Reports] completed submission of /var/mobile/Containers/Data/Application/0481E460-7E05-4FD1-8C4E-485F602E00FD/Library/Caches/com.crashlytics.data/com.tricktrack.sprint/v3/prepared/8D821963-AF43-48B7-8CA5-BB01B805796A.multipartmime 2019-09-19 11:16:52.265749+0100 Sprint-iOS[19664:1731838] [Crashlytics:Crash] report submission successful
Anyone have any suggestions?

Have you uploaded any symbol files to Crashlytics?

Not manually.... Ill try it though.

any update on this? I have the same bug. Is there a version that I can use there isn't with the bug?
Actually I started to investigate why. In the beginning I wasn't getting any log about Crashlytics on Xcode. The reason was my old integration with Fabric. I had to remove the Fabric key that was in the plist and the key that was in the build fase run script. If I try to follow just the tutorial I was getting:
Mismatched configuration: Fabric entry found in app's Info.plist, but no API Key provided to the run script. If this app was set up in Fabric, or linked to Firebase, pass your API key to the run script as the first argument. If this app was onboarded via Firebase, remove the Fabric entry in your Info.plist
After that I could start getting logs about Crashlytics. But now I think I have the same bug, because the logs say that it's working. (The log is from an old version, but the result in the same with the Crashlytics version 3.14.0):
**[Crashlytics] Version 3.13.4 (143)
[Crashlytics] Running on iPhone9,3, 12.3.1 (16F203)
[Answers] Initialized
[Fabric] Initialized with kit versions: {
"com.twitter.answers.ios" = "1.4.1";
"com.twitter.crashlytics.ios" = "3.13.4";
"io.fabric.sdk.ios" = "1.10.2";
[Crashlytics:Crash:Reports] Packaged report with id '9e06ebd6aae240108cead10eafda56e1' for submission
[Crashlytics:Crash:Reports] Submitting report
[Crashlytics:Crash:Reports] Submitting async /var/mobile/Containers/Data/Application/744E4402-3A20-4D6C-9E8A-972F37050CBA/Library/Caches/com.crashlytics.data/APP_NAME/v3/prepared/9FDBC984-17B9-408A-84FE-77BF8EE7C5C6.multipartmime
[Crashlytics:Crash:Reports:Event] Sending event.
[Crashlytics:Crash:Reports] completed submission of /var/mobile/Containers/Data/Application/744E4402-3A20-4D6C-9E8A-972F37050CBA/Library/Caches/com.crashlytics.data/APP_NAME/v3/prepared/9FDBC984-17B9-408A-84FE-77BF8EE7C5C6.multipartmime
[Crashlytics:Crash] report submission successful**

@elanovasconcelos, I'm assuming you have all the dSYMs uploaded as well? I initially had assumed that the root of this issue was Crashlytics console not showing unsymbolicated crashes, but since you mentioned Fabric migration it's possible there's something else going on.

should I have to upload even for a debug version? The isn't any missing dSYMs listed on firebase.
I always upload the dSYMs file after send to Apple. I have to send a new version, so now I'll send with Crashlytics version 3.14.0 and hope that now it's only missing the dSYMs file. =(

Debug versions shouldn't need a dSYM file if the debug information isn't stripped out of the binary.
@TKBurner have you seen this issue before?

There are still some instances where a crash report can fail to be sent to the dashboard even when there are no missing dSYMs and the report upload looks successful as per the logs. @elanovasconcelos, @Neilfau could you reach out to<EMAIL_ADDRESS>so we can dig into more logs and potentially some project files?

sure, I'll send an email now.

Closing this issue since it's no longer actionable here. If you're unable to see crashes in your dashboard and you've completed all migration steps, please file a support ticket to Firebase.

@morganchen12 I am getting the same exact issue of @elanovasconcelos. Can u please help me to solve this

@elanovasconcelos Bro, Can u please let me know, how you resolved this

@Rahulkhandal hi, sorry for the late response. I fix my bug. Did you migrate from Fabric to Firebase? That was my scenario.
I may be crazy, but I think an old tutorial of how to migrate Fabric to Firebase said to remove the line: Fabric.with([Crashlytics.self]), after added it back it start working again. Today the tutotial is just a website migration. But before that I tried a lot of things. So please try this:

before all, did you get any log about Crashlytics on Xcode? (like crash sent, version etc)
update the pods to the last version
unlink the Fabric -> Firebase integration (Settings -> Project settings -> Fabric)
on Xcode: make sure the Run script is the last one in the list and add $(SRCROOT)/$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH) to the Input Files
make sure that the Fabric key is in the run script
make sure that Fabric key is on the info.plist
make sure that you're calling: Fabric.with([Crashlytics.self])
link the Fabric -> Firebase integration on the Fabric website

I hope that this can help. =)

@elanovasconcelos Thanks for your response Bro. Yes I migrated from fabric to firebase . I am getting same issue what u described. I will try what u said.
Just a confustion over your solution: Fabric.with([Crashlytics.self]) should be removed right ?

@Rahulkhandal I talked with Fabric support and it was one of the suggestion that they give to me and I did it. So I added on the list.


Skip dead links in the OS 3.24 legal page

These links are in the legal page and cannot be modified or fixed, so skipping them:
4:09:55 PM: ==>Origin: http://localhost:4242/calico/3.24/reference/legal/projectcalico
4:09:55 PM: http://fsf.org/&gt is dead (404)
4:09:55 PM: ==>Origin: http://localhost:4242/calico/3.24/reference/legal/projectcalico
4:09:55 PM: http://unlicense.org/&amp is dead (404)
4:09:55 PM: ==>Origin: http://localhost:4242/calico/3.24/reference/legal/projectcalico
4:09:55 PM: http://www.openssl.org/)&amp is dead (404)
4:09:55 PM: ==>Origin: http://localhost:4242/calico/3.24/reference/legal/projectcalico
4:09:55 PM: https://docs.tigera.io/calico/3.24/reference/legal/projectcalico is dead (404)
4:09:55 PM: ==>Origin: http://localhost:4242/calico/3.24/reference/legal/projectcalico
4:09:55 PM: https://proxy.golang.org/github.com/ is dead (404)
4:09:55 PM: ==>Origin: http://localhost:4242/calico/3.24/reference/legal/projectcalico
4:09:55 PM: https://proxy.golang.org/github.com/antlr/antlr4/runtime/ is dead (404)
4:09:55 PM: ==>Origin: http://localhost:4242/calico/3.24/reference/legal/projectcalico

Product Version(s):
Calico OS 3.24
Issue:

Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

@girishshankaran Can we close this PR? The build seems to be working okay now without these skip rules.

Closing this, as we have these skip rules already in place.


sensor.scrape Issues On Hassio 0.77.0

Home Assistant release with the issue:
0.77.0
Last working Home Assistant release (if known):
0.70.0
Operating environment (Hass.io/Docker/Windows/etc.):
Hassio
Component/platform:
Scrape
**Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
sensor:
  # 检测高唐信息港房产页面新帖子
  - platform: scrape
    resource: https://www.gaotang.cc/house/chushou/?dqid=1&key=&lx=0
    name: 'xxg_message_time'
    select: "span.news"
  - platform: scrape
    resource: https://www.gaotang.cc/house/chushou/?dqid=1&key=&lx=0
    name: 'xxg_message_detail'
    select: "span.list_word"
    value_template: '{{ value.split("(高唐)")[0] }}'
  - platform: scrape
    resource: https://www.gaotang.cc/house/chushou/?dqid=1&key=&lx=0
    name: 'xxg_message_title'
    select: " dt.dt2 a"
  - platform: scrape
    resource: https://www.gaotang.cc/house/chushou/?dqid=1&key=&lx=0
    name: 'xxg_message_price'
    select: "span.price"

Stacktrace:
Traceback (if applicable):
2018-08-28 21:50:06 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.xxg_message_detail fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 199, in async_update_ha_state
    yield from self.async_device_update()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 322, in async_device_update
    yield from self.hass.async_add_job(self.update)
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/sensor/scrape.py", line 115, in update
    raw_data = BeautifulSoup(self.rest.data, 'html.parser')
  File "/usr/local/lib/python3.6/site-packages/bs4/__init__.py", line 246, in __init__
    elif len(markup) <= 256 and (
TypeError: object of type 'NoneType' has no len()
2018-08-28 21:50:53 ERROR (SyncWorker_13) [homeassistant.components.sensor.rest] Error fetching data: <PreparedRequest [GET]> from https://www.gaotang.cc/house/chushou/?dqid=1&key=&lx=0 failed with HTTPSConnectionPool(host='www.gaotang.cc', port=443): Max retries exceeded with url: /house/chushou/?dqid=1&key=&lx=0 (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x6dbb1c70>: Failed to establish a new connection: [Errno -3] Try again',))
2018-08-28 21:50:53 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.xxg_message_price fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 199, in async_update_ha_state
    yield from self.async_device_update()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 322, in async_device_update
    yield from self.hass.async_add_job(self.update)
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/sensor/scrape.py", line 115, in update
    raw_data = BeautifulSoup(self.rest.data, 'html.parser')
  File "/usr/local/lib/python3.6/site-packages/bs4/__init__.py", line 246, in __init__
    elif len(markup) <= 256 and (
TypeError: object of type 'NoneType' has no len()
2018-08-28 21:55:37 ERROR (SyncWorker_13) [homeassistant.components.sensor.rest] Error fetching data: <PreparedRequest [GET]> from https://www.gaotang.cc/house/chushou/?dqid=1&key=&lx=0 failed with HTTPSConnectionPool(host='www.gaotang.cc', port=443): Max retries exceeded with url: /house/chushou/?dqid=1&key=&lx=0 (Caused by ConnectTimeoutError(<urllib3.connection.VerifiedHTTPSConnection object at 0x6e0bd4d0>, 'Connection to www.gaotang.cc timed out. (connect timeout=10)'))
2018-08-28 21:55:37 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.xxg_message_time fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 199, in async_update_ha_state
    yield from self.async_device_update()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 322, in async_device_update
    yield from self.hass.async_add_job(self.update)
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/sensor/scrape.py", line 115, in update
    raw_data = BeautifulSoup(self.rest.data, 'html.parser')
  File "/usr/local/lib/python3.6/site-packages/bs4/__init__.py", line 246, in __init__
    elif len(markup) <= 256 and (
TypeError: object of type 'NoneType' has no len()
2018-08-28 21:56:03 ERROR (SyncWorker_15) [homeassistant.components.sensor.rest] Error fetching data: <PreparedRequest [GET]> from https://www.gaotang.cc/house/chushou/?dqid=1&key=&lx=0 failed with HTTPSConnectionPool(host='www.gaotang.cc', port=443): Max retries exceeded with url: /house/chushou/?dqid=1&key=&lx=0 (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x72ee8070>: Failed to establish a new connection: [Errno -3] Try again',))

scrape sensor works fine. You have a timeout error.
Connection to www.gaotang.cc timed out. (connect timeout=10)'))

Duplicate of #14806


az requires a writable home, even when there's no reason for it

Related command

az storage blob upload
Describe the bug
Traceback (most recent call last):
  File "/opt/az/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/opt/az/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/opt/az/lib/python3.8/site-packages/azure/cli/__main__.py", line 38, in <module>
    az_cli = get_default_cli()
  File "/opt/az/lib/python3.8/site-packages/azure/cli/core/__init__.py", line 903, in get_default_cli
    from azure.cli.core.azlogging import AzCliLogging
  File "/opt/az/lib/python3.8/site-packages/azure/cli/core/azlogging.py", line 30, in <module>
    from azure.cli.core.commands.events import EVENT_INVOKER_PRE_CMD_TBL_TRUNCATE
  File "/opt/az/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 25, in <module>
    from azure.cli.core.extension import get_extension
  File "/opt/az/lib/python3.8/site-packages/azure/cli/core/extension/__init__.py", line 18, in <module>
    az_config = CLIConfig(config_dir=GLOBAL_CONFIG_DIR, config_env_var_prefix=ENV_VAR_PREFIX)
  File "/opt/az/lib/python3.8/site-packages/knack/config.py", line 40, in __init__
    ensure_dir(config_dir)
  File "/opt/az/lib/python3.8/site-packages/knack/util.py", line 115, in ensure_dir
    raise e
  File "/opt/az/lib/python3.8/site-packages/knack/util.py", line 112, in ensure_dir
    os.makedirs(d)
  File "/usr/bin/../../opt/az/lib/python3.8/os.py", line 223, in makedirs
    mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/opt/proggy/.azure'

To Reproduce
Run az with a non-writable home directory. E.g., in the above example, we are running az storage blob upload with our credentials coming from AZURE_STORAGE_KEY.
Expected behavior
If the command can execute, then it should. (If a home dir is required, e.g., if I am asking az login to store an access token, then there's no way around it and an error is appropriate.)
Environment summary
Debian, apt-get.

I'd tell you what version of az, but…
$ az --version
Traceback (most recent call last):
  File "/opt/az/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/opt/az/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/opt/az/lib/python3.8/site-packages/azure/cli/__main__.py", line 38, in <module>
    az_cli = get_default_cli()
  File "/opt/az/lib/python3.8/site-packages/azure/cli/core/__init__.py", line 903, in get_default_cli
    from azure.cli.core.azlogging import AzCliLogging
  File "/opt/az/lib/python3.8/site-packages/azure/cli/core/azlogging.py", line 30, in <module>
    from azure.cli.core.commands.events import EVENT_INVOKER_PRE_CMD_TBL_TRUNCATE
  File "/opt/az/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 25, in <module>
    from azure.cli.core.extension import get_extension
  File "/opt/az/lib/python3.8/site-packages/azure/cli/core/extension/__init__.py", line 18, in <module>
    az_config = CLIConfig(config_dir=GLOBAL_CONFIG_DIR, config_env_var_prefix=ENV_VAR_PREFIX)
  File "/opt/az/lib/python3.8/site-packages/knack/config.py", line 40, in __init__
    ensure_dir(config_dir)
  File "/opt/az/lib/python3.8/site-packages/knack/util.py", line 115, in ensure_dir
    raise e
  File "/opt/az/lib/python3.8/site-packages/knack/util.py", line 112, in ensure_dir
    os.makedirs(d)
  File "/usr/bin/../../opt/az/lib/python3.8/os.py", line 223, in makedirs
    mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/opt/proggy/.azure'

dpkg says it is 2.36.0-1~bullseye.
Additional context
Security teams & audit reviews want containers to be non-writable these days, unless there is a business reason for them to be otherwise. It is for that reason that ~ is read-only here. Here, we have to explicitly make ~ writable for az, even though nothing about this particular invocation requires it. (In practice, I'm hoping that I can get away with just a writable ~/.azure.)

@evelyn-ys for awareness

To be simple, CLI may need to create a .azure folder to store some local info, eg, installationId, config, local cache, etc.


Feature/user_service

Enhanced support for softlayer_user_customer resource, as needed by Terraform library.

Added fields to SoftLayer_User_Customer type. Defined new types for user permissions, and user delete.
Implemented CreateObject(), GetObject(), EditObject(), DeleteObject()
Implement RemoveApiAuthenticationKey()
Implemented AddBulkPortalPermission(), RemoveBulkPortalPermission(), GetPermissions()
Added unit tests for each of the above APIs along with the necessary test_fixtures.

Rebased this branch on top of sl-dev.


appending

Is there an appropriate way to append text into an existing FTCoreTextView? Should I be keeping a separate buffer of the text and calling -setText every time I append something new to the buffer? Or does there need to be an -appendText method on FTCoreTextView that handles things more efficiently internally?

Hi there,
The drawRect method will rewrite the entire text every time so even implementing an appendText method would not help much in terms of performances.
Francesco.

Hi!
I'm afraid we haven't had the use of appending text to an existing FTCoreText view so a method like "-appendText" doesn't exist. The overhead of re parsing the whole string shouldn't be too important though, depending on the length of the final string of course. Are you thinking of letting the user input text directly in an FTCoreText view?
Cheers,
Baldoph
On 22 Feb 2012, at 22:31, sirbarrence wrote:

Is there an appropriate way to append text into an existing FTCoreTextView? Should I be keeping a separate buffer of the text and calling -setText every time I append something new to the buffer? Or does there need to be an -appendText method on FTCoreTextView that handles things more efficiently internally?

Reply to this email directly or view it on GitHub:
https://github.com/FuerteInternational/FTCoreText/issues/7

Sort of. The Core Text view needs to update dynamically with new data from a server and the user. The user doesn't need to type into the Core Text view though.
I was probably just trying to optimize too early. Now that I think about it, it's not so unusual for a text view to have no append method. UITextView and UITextField don't either. I've just been using a UIWebView where I used JavaScript to append new content into the document.


Revert "Add HOSTNAME to env by default for pod containers"

This reverts commit 4c3e195db36e67d65bebd48b9987596799d9d543.
See reason: https://github.com/containerd/cri/pull/895#issuecomment-419261967
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

/lgtm

From the kube-addon-manager log:
INFO: Leader is bootstrap-e2e-master
INFO: Not elected leader, going back to sleep.
INFO: Leader is bootstrap-e2e-master
INFO: Not elected leader, going back to sleep.
INFO: Leader is bootstrap-e2e-master
INFO: Not elected leader, going back to sleep.
INFO: Leader is bootstrap-e2e-master

The addon manager did not think it's the leader bootstrap-e2e-master and refused to continue creating all the addons (including the cluster roles):
https://github.com/kubernetes/kubernetes/blob/d0439d417b0563d44c65b6e400e2070964dea7d1/cluster/addons/addon-manager/kube-addons.sh#L162-L164

By the way, kube-addon-manager runs in the host network

By the way, kube-addon-manager runs in the host network

kubelet probably doesn't set hostname for pods running in the host network. Not sure how docker handles this.

Interesting; it definitely looks like HOSTNAME is part of the problem here.
This is the code where Docker engine sets up HOSTNAME as a default env var in every container (https://github.com/moby/moby/blob/master/container/container.go#L694-L718), which is called from the OCI spec generator without any kind of checking if netns == host.
I also looked at dockershim and don't see any env replacement or changes happening; I can't even find the string "HOSTNAME" in any files in pkg/kubelet. So, something is definitely different, but I'm not sure what is occurring here.

hmm, looks like the missing piece is that by the time that code runs in Docker, if --net=host it has set the metadata config's hostname to the actual host hostname; not sure if that is the case with the way this is happened here; Docker for Mac example:
docker run --rm --net=host alpine sh -c 'echo $HOSTNAME'
linuxkit-025000000001

The container's hostname is the LinuxKit VM hostname.

I also looked at dockershim and don't see any env replacement or changes happening; I can't even find the string "HOSTNAME" in any files in pkg/kubelet. So, something is definitely different, but I'm not sure what is occurring here.

Kubelet passes the hostname through the podsandbox config, but it doesn't add an env variable directly.

hmm, looks like the missing piece is that by the time that code runs in Docker, if --net=host it has set the metadata config's hostname to the actual host hostname

That sounds reasonable. Docker probably derives this information before passing it through the config.

https://github.com/moby/moby/blob/master/daemon/container_operations.go#L936-L943
I'll make the change.


HW: Possible wiring issue with the I2C on the PMIC

The I2C2 pins appear to be swapped at the PMIC.

The DVS should be at 0x12 on the PMIC I2C2. We don't seem to have a driver loaded to use it. I'm still researching if any software should be using it.


Silver Dragon Head Bug

The silver dragon head is not right positioned in the body its kinda floating

Not just the head. The wings and legs are also kinda detached. The parts aren't anchored properly. It also looks bizarre when it turns its everything to look at you. And there's a flashing texture thing on the wings, like it's got 2 different textures at the same time.

also in the version 0.0.8 the standing model floats in air and wings only appear when flying

Thanks. Yes, we have an open invitation for a coder that can fix this stuff. The plan is to fix these eventually, but we didn't want to delay the release just for these visual bugs. Having no wings on the ground is on purpose, we will be adding a "folded wing" look eventually when the dragon is on the ground. If the wings were rendered on the ground, they would be all the way open, but the dragon on the ground isn't that wide, so I don't show them.

Assigned to LRA. Issue with animation appears to be either in the model or the animation created in MCA.


Unable to load mysql extension after compiling latest PHP 7

I have compiled the latest php 7 version using makephp 7.
I am now getting the following startup error:
testvagrant@php7dev:~$ php -v
PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/local/php70-debug/lib/php/extensions/debug-non-zts-20151012/mysql.so' - /usr/local/php70-debug/lib/php/extensions/debug-non-zts-20151012/mysql.so: cannot open shared object file: No such file or directory in Unknown on line 0

Warning: PHP Startup: Unable to load dynamic library '/usr/local/php70-debug/lib/php/extensions/debug-non-zts-20151012/mysql.so' - /usr/local/php70-debug/lib/php/extensions/debug-non-zts-20151012/mysql.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP 7.1.0-dev (cli) (built: Nov  1 2015 10:39:59) ( NTS DEBUG )
Copyright (c) 1997-2015 The PHP Group
Zend Engine v3.1.0-dev, Copyright (c) 1998-2015 Zend Technologies
    with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2015, by Zend Technologies

That's because the API version changed and the mysql extension is not shipped with PHP anymore. It is a separate build. You can fix it by doing:
cd ~/src/mysql
make clean
phpize
./configure
make
sudo make install
Or if you grab the latest version of the image it is updated there.

Great, thank you! That worked.


Add support for GNOME 40

This is a simple change to support GNOME 40 (and probably 3.38 too)

@TheWeirdDev
Thanks!  That works for me.

It worked, thanks

someone do something for 47 :sob:

@NormTurtle, did something change in 47? Can you open a new issue and we can discuss it there?
I'm going to close this pull request because as it seems a bit outdated by now...

@maiself im sorry i can't give much about on technical changes related to this project.
im a just a user not a developer.
i want that extension to get worked.
to save my eyees in deep night when watching lectures with white boards.

but, you can still see how other have some workarounds.
https://github.com/cg505/gnome-shell-grayscale-window
https://github.com/JackKenney/gnome-true-color-invert ( too old i guess?)

I just looked thru the 47 release notes and didn't see anything that might affect this extension, so it may be as simple as adding version 47 to metadata.json.
I see that the grayscale extension already has 47 listed, so it should be easy to compare for any changes. I don't know when I'll be able to upgrade to 47 to test tho.
If you know how to find it and edit it, adding the version to the list in metadata.json and then restarting may get things work right away. Otherwise please be patient until I can get around to updating things. Thanks for bringing this to my attention. I know how important dark mode and brightness inversion can be, I get headaches from bright screens, it's why I created this extension in the first place 🙂

@NormTurtle, just send a new version off for review, so should update automatically in a day or two when it passes. All that was needed was adding version 47 to the metadata file.

Thank you so much


Check dependencies by resources

Build scan link

Plugin version
0.65.0 (on latest version :module:projectHealth doesn't work, don't find out  why yet)
Gradle version
6.7
Android Gradle Plugin (AGP) version
4.1.1
Describe the bug
I have special module for fonts only. When connected as a dependency and run :fonts-module:projectHealth then plugin tells that I should remove it, which is wrong. And the same behavior with other dependencies by resource like themes, strings & etc
Expected behavior
No recommendations to delete this dependency

I am almost certain that this is due to a known limitation described here. If your gradle.properties is missing
android.namespacedRClass=true

then that is the issue.
Since a number of people have already upvoted this, I will explain a bit further. It would actually be impossible to conclusively determine the provenance of a resource when those resources aren't namespaced, thanks to the way that AGP merges resources as it traverses up the dependency graph towards your app module. The best we could do is to have a heuristic such that, when seeing something like R.what.ever, don't recommend removing any dependency that supplies a what.ever resource. And this would be quite complicated to code.
In the meantime, you can configure the plugin to ignore certain issues. In your specific case, you could add the following to your root build.gradle
dependencyAnalysis
  issues {
    all {
      onUnusedDependencies {
        exclude(':fonts-module')
      }
    }
  }
}

and that module will no longer be reported as "unused."
PS: Regarding "the latest version doesn't work", there was a bug in 0.67.0 that would cause a crash due to an NPE in certain circumstances. That was resolved in 0.68.0 (released yesterday). Please give it a try and, if you still have an issue, please file so I can take a look.

Thank you for fast and detailed response!
Yes, I don't have android.namespacedRClass=true in my project because it's very big and I'll need refactor a lot.
I understand problem and use now exclude
P.S. 0.68. works fine
but, i still have those null instead of api/implementation some times, do you know why this happening?

@Jacks0N23 could you file a new issue with more information?

For anyone coming to this late..
android.namespacedRClass=true
is now named:
android.nonTransitiveRClass=true

I think the problem still remains when resources (e.g. drawables or colors) are used only in another module's XML files (e.g. layouts). I have an icon in a library module and when I use it in another module's XML layout, the library module with an icon is indicated as unused. I'm using version 1.0.0-rc02.

@bartek-wesolowski do you have a minimal reproducer?

It seems that the problem appears when using library resources marked as private. They probably shouldn't be used anyway, so it's not the plugin's fault.

Closing. Please re-open if any actionable information makes itself known.


ci: workflow to manually trigger windows pkg creation

closing as right now we can re-run windows pipeline again


FYI: global regional vaccination data

Hi!
This is just an "FYI" message. First of all, thanks for your amazing resource. Inspired by OWID's project, I started a global collection of regional vaccination data and I am using yours (see sociepy/covid19-vaccination-subnational) 😄 !
So far I have referenced it in a reference table in the README file, but please let me know if you'd like it to be referenced differently.
Have a great day and feel free to close this issue!

That's amazing! I was hoping people would use this data for their own projects. I love the CSV structure you're outputting, very clean. Thanks for letting me know about your project! I'll add a link to it from this project's README 👍

That's amazing! I was hoping people would use this data for their own projects. I love the CSV structure you're outputting, very clean. Thanks for letting me know about your project! I'll add a link to it from this project's README 👍

Thanks for your words (and your work, again) @mathiasbynens, appreciate it! =)

Thanks for your words (and your work, again) @mathiasbynens, appreciate it! =)


check_dict: Add missing fields for validators.

I think all but the last one here are pretty much no-brainers to merge.

I addressed the comments; it's ready for review again.

Merged as the series ending with 2fb67b3f324e89eaf9b27c7fd3efc0ef844a5d69, after undoing the subscription_fields -> all_stream_fields change; the extra fields are literally from the Subscription model, so the old name was better.  (And fixing the little issue mentioned above).
Thanks @showell!


import flash_attn_2_cuda as flash_attn_cuda

import flash_attn_2_cuda as flash_attn_cuda
this how to install a ?

Does anyone answer this question?

solve??

same issue

You can try to install it by
pip install flash-attn --no-build-isolation
or install by compiling the source code
python setup.py install
also you can directly download the whl package compiled by the author for pip installation. The flash_attn_2_cuda you mentioned is actually a C++ interface package wrapped by pybind11, which will be installed automatically when flash_atten is installed. You can just use the docker image I built, which contains everything about flashattention, and you can start the container and use it by
docker pull jayce0625/cuda12.3_torch2.3.0_flashattn2.5.6:latest


HBASE-25596: Fix NPE and avoid permanent unreplicated data due to EOF

Please find the details in jira:
https://issues.apache.org/jira/browse/HBASE-25596

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
3m 52s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
11m 17s
branch-1 passed

+1 :green_heart:
compile
0m 59s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
compile
1m  0s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
checkstyle
2m 19s
branch-1 passed

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

+1 :green_heart:
javadoc
1m  7s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
1m  0s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+0 :ok:
spotbugs
4m 13s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
4m  8s
branch-1 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
1m  3s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

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

+1 :green_heart:
compile
1m  4s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

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

+1 :green_heart:
checkstyle
2m 14s
hbase-server: The patch generated 0 new + 0 unchanged - 10 fixed = 0 total (was 10)

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

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

+1 :green_heart:
hadoopcheck
6m 48s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 57s
hbase-server-jdkAzulSystems,Inc.-1.8.0_262-b19 with JDK Azul Systems, Inc.-1.8.0_262-b19 generated 0 new + 6 unchanged - 2 fixed = 6 total (was 8)

+1 :green_heart:
javadoc
1m  3s
hbase-server-jdkAzulSystems,Inc.-1.7.0_272-b10 with JDK Azul Systems, Inc.-1.7.0_272-b10 generated 0 new + 6 unchanged - 2 fixed = 6 total (was 8)

+1 :green_heart:
findbugs
4m 37s
the patch passed

_ Other Tests _

-1 :x:
unit
150m 16s
hbase-server in the patch failed.

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

211m 35s

Reason
Tests

Failed junit tests
hadoop.hbase.regionserver.TestSplitTransactionOnCluster

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2975/1/artifact/out/Dockerfile

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

JIRA Issue
HBASE-25596

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux f81601d65ef1 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2975/out/precommit/personality/provided.sh

git revision
branch-1 / f9a9148

Default Java
Azul Systems, Inc.-1.7.0_272-b10

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:Azul Systems, Inc.-1.8.0_262-b19 /usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_272-b10

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2975/1/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
3660 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

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

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 38s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  1s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
10m 48s
branch-1 passed

+1 :green_heart:
compile
1m  8s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
compile
1m  6s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
checkstyle
2m 28s
branch-1 passed

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

+1 :green_heart:
javadoc
1m  3s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
0m 56s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+0 :ok:
spotbugs
4m 21s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
4m 18s
branch-1 passed

-0 :warning:
patch
4m 28s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 59s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javac
0m 59s
the patch passed

+1 :green_heart:
compile
1m  1s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

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

+1 :green_heart:
checkstyle
2m 16s
hbase-server: The patch generated 0 new + 0 unchanged - 10 fixed = 0 total (was 10)

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

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

+1 :green_heart:
hadoopcheck
5m 56s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 33s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
0m 43s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
findbugs
3m  9s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
122m 57s
hbase-server in the patch passed.

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

178m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2975/3/artifact/out/Dockerfile

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

JIRA Issue
HBASE-25596

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 471c6b614fb2 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2975/out/precommit/personality/provided.sh

git revision
branch-1 / 9e9301a

Default Java
Azul Systems, Inc.-1.7.0_272-b10

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:Azul Systems, Inc.-1.8.0_262-b19 /usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_272-b10

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

Max. process+thread count
3693 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

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

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.

Unless there is a change in review status I will merge this in a couple of hours.


Using BTCPay as Full Node for Liquid

Hi
Im setting up a Liquid Sidechain and id like to use my NBitcoin from my Azure PayServer to be the full node for the Liquid Side chain.
Any tuts in getting this moving are appreciated.
Thanks

Wrong repository. Post on btcpayserver https://github.com/btcpayserver/btcpayserver-docker please.
The best is that you put liquid in a docker image then you add a custom fragment with Liquid container inside.

You can close this, already done: https://github.com/btcpayserver/btcpayserver-docker/blob/master/docker-compose-generator/docker-fragments/liquid.yml


关于集群三节点下，中间输出了一些error日志，是怎么回事呢？

Issue Type
Others
Source
binary
Secretflow Version
0.8.0b0
OS Platform and Distribution
centos7
Python version
3.8.13
Bazel version
No response
GCC/Compiler version
No response
What happend and What you expected to happen.
以下是demo程序运转打印的日志：
INFO:root:Run secretflow in simulation mode.
2023-04-11 09:39:38,517 INFO worker.py:1352 -- Connecting to existing Ray cluster at address: <IP_ADDRESS>:6379...
2023-04-11 09:39:38,531 INFO worker.py:1538 -- Connected to Ray cluster.
(SPURuntime pid=6462, ip=<IP_ADDRESS>) 2023-04-11 09:42:49.593 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E111]Fail to connect Socket{id=0 addr=<IP_ADDRESS>:6337} (0x0x3874640): Connection refused [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
(SPURuntime pid=25995, ip=<IP_ADDRESS>) 2023-04-11 09:39:41.431 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E111]Fail to connect Socket{id=0 addr=<IP_ADDRESS>:6337} (0x0x4967c80): Connection refused [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
(_run pid=27553) INFO:jax._src.xla_bridge:Unable to initialize backend 'cuda': module 'jaxlib.xla_extension' has no attribute 'GpuAllocatorConfig'
(_run pid=27553) INFO:jax._src.xla_bridge:Unable to initialize backend 'rocm': module 'jaxlib.xla_extension' has no attribute 'GpuAllocatorConfig'
(_run pid=27553) INFO:jax._src.xla_bridge:Unable to initialize backend 'tpu': INVALID_ARGUMENT: TpuPlatform is not available.
(_run pid=27553) INFO:jax._src.xla_bridge:Unable to initialize backend 'plugin': xla_extension has no attributes named get_plugin_device_client. Compile TensorFlow with //tensorflow/compiler/xla/python:enable_plugin_device set to true (defaults to false) to enable this.
(_run pid=27553) WARNING:jax._src.xla_bridge:No GPU/TPU found, falling back to CPU. (Set TF_CPP_MIN_LOG_LEVEL=0 and rerun for more info.)
(_run pid=6464, ip=<IP_ADDRESS>) INFO:jax._src.xla_bridge:Unable to initialize backend 'cuda': module 'jaxlib.xla_extension' has no attribute 'GpuAllocatorConfig'
(_run pid=6464, ip=<IP_ADDRESS>) INFO:jax._src.xla_bridge:Unable to initialize backend 'rocm': module 'jaxlib.xla_extension' has no attribute 'GpuAllocatorConfig'
(_run pid=6464, ip=<IP_ADDRESS>) INFO:jax._src.xla_bridge:Unable to initialize backend 'tpu': INVALID_ARGUMENT: TpuPlatform is not available.
(_run pid=6464, ip=<IP_ADDRESS>) INFO:jax._src.xla_bridge:Unable to initialize backend 'plugin': xla_extension has no attributes named get_plugin_device_client. Compile TensorFlow with //tensorflow/compiler/xla/python:enable_plugin_device set to true (defaults to false) to enable this.
(_run pid=6464, ip=<IP_ADDRESS>) WARNING:jax._src.xla_bridge:No GPU/TPU found, falling back to CPU. (Set TF_CPP_MIN_LOG_LEVEL=0 and rerun for more info.)
--------------------------------------------
obj: <secretflow.device.device.spu.SPUObject object at 0x7f45286084c0>
--------------------------------------------
(_run pid=25996, ip=<IP_ADDRESS>) INFO:jax._src.lib.xla_bridge:Unable to initialize backend 'tpu_driver': NOT_FOUND: Unable to find driver in registry given worker:
(_run pid=25996, ip=<IP_ADDRESS>) INFO:jax._src.lib.xla_bridge:Unable to initialize backend 'cuda': module 'jaxlib.xla_extension' has no attribute 'GpuAllocatorConfig'
(_run pid=25996, ip=<IP_ADDRESS>) INFO:jax._src.lib.xla_bridge:Unable to initialize backend 'rocm': module 'jaxlib.xla_extension' has no attribute 'GpuAllocatorConfig'
(_run pid=25996, ip=<IP_ADDRESS>) INFO:jax._src.lib.xla_bridge:Unable to initialize backend 'tpu': INVALID_ARGUMENT: TpuPlatform is not available.
(_run pid=25996, ip=<IP_ADDRESS>) INFO:jax._src.lib.xla_bridge:Unable to initialize backend 'plugin': xla_extension has no attributes named get_plugin_device_client. Compile TensorFlow with //tensorflow/compiler/xla/python:enable_plugin_device set to true (defaults to false) to enable this.
(_run pid=25996, ip=<IP_ADDRESS>) WARNING:jax._src.lib.xla_bridge:No GPU/TPU found, falling back to CPU. (Set TF_CPP_MIN_LOG_LEVEL=0 and rerun for more info.)
(SPURuntime pid=6462, ip=<IP_ADDRESS>) 2023-04-11 09:42:50.594 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
(SPURuntime pid=25995, ip=<IP_ADDRESS>) 2023-04-11 09:39:42.431 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
(SPURuntime pid=6462, ip=<IP_ADDRESS>) 2023-04-11 09:42:51.594 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
(SPURuntime pid=25995, ip=<IP_ADDRESS>) 2023-04-11 09:39:43.432 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
(SPURuntime pid=6462, ip=<IP_ADDRESS>) 2023-04-11 09:42:52.595 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
(SPURuntime pid=25995, ip=<IP_ADDRESS>) 2023-04-11 09:39:44.432 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
[10 12 10 12]

Reproduction code to reproduce the issue.

Hi @xiaoran33
这些只是 jax 的 warning message 而已，可以直接忽略

Hi @xiaoran33
这些只是 jax 的 warning message 而已，可以直接忽略

(SPURuntime pid=6462, ip=<IP_ADDRESS>) 2023-04-11 09:42:50.594 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
(SPURuntime pid=25995, ip=<IP_ADDRESS>) 2023-04-11 09:39:42.431 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
(SPURuntime pid=6462, ip=<IP_ADDRESS>) 2023-04-11 09:42:51.594 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
(SPURuntime pid=25995, ip=<IP_ADDRESS>) 2023-04-11 09:39:43.432 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
(SPURuntime pid=6462, ip=<IP_ADDRESS>) 2023-04-11 09:42:52.595 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
(SPURuntime pid=25995, ip=<IP_ADDRESS>) 2023-04-11 09:39:44.432 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
这种error的也是可以直接忽略的吗？

Hi @xiaoran33
这些只是 jax 的 warning message 而已，可以直接忽略

(SPURuntime pid=6462, ip=<IP_ADDRESS>) 2023-04-11 09:42:50.594 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 (SPURuntime pid=25995, ip=<IP_ADDRESS>) 2023-04-11 09:39:42.431 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 (SPURuntime pid=6462, ip=<IP_ADDRESS>) 2023-04-11 09:42:51.594 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 (SPURuntime pid=25995, ip=<IP_ADDRESS>) 2023-04-11 09:39:43.432 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 (SPURuntime pid=6462, ip=<IP_ADDRESS>) 2023-04-11 09:42:52.595 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 (SPURuntime pid=25995, ip=<IP_ADDRESS>) 2023-04-11 09:39:44.432 [error] [context.cc:operator():132] connect to rank=0 failed with error [external/yacl/yacl/link/transport/channel_brpc.cc:368] send, rpc failed=112, message=[E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R1][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R2][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0 [R3][E112]Not connected to <IP_ADDRESS>:6337 yet, server_id=0
这种error的也是可以直接忽略的吗？

这些是节点A在连接到节点B失败的时候打出来的 message，但是 SPU 在连接失败以后会进行几次重试。如果一个节点拉起时间比较长，就会看到几个这样的 error message，但是如果最终连接成功了就可以忽略
这个 message 比较有误导性，我们也已经注意到了，会在下次更新的时候解决


[0003] Numeric Constants - Detailed Design

Which proposal does this relate to?
0003 - Numeric Constants
Describe the issue or outstanding question.
This feature needs a completed detailed design. Since this feature implements a replacement for a non-conformant HLSL language feature that we may not want to implement in Clang, it would be nice to get this feature into HLSL 202x so that users can adopt the new feature in DXC before transitioning to Clang.
Additional Context
I did some experimentation in Clang and came up with these two source files as a proof of concept for a Clang header-based implementation:
hlsl_limits.h.txt
hlsl_type_traits.h.txt

you'd have to actually provide a constexpr for functions as well,
My own numeric traits define the members as static const variables simply so I can feed them into templates later ( numeric_limits with int types)

Also I'm happy to donate whatever parts of my own type_traits you'd find useful
https://github.com/Devsh-Graphics-Programming/Nabla/blob/923c1c56168a4a316094c25a9369527d5ae48c24/include/nbl/builtin/hlsl/type_traits.hlsl
Dont mind the macros at the end, they're just copium for working around the lack of alignof and typeid


proto: proper expand

Fails

:no_entry_sign:
Non-approved dependencies were detected. It is necessary to obtain approvals and register them in `approvedPackages` file before merge.

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

:warning:
Package (or peer) dependencies changed. Make sure you have approval before merging!

Changed dependencies are detected.
Changed dependencies in packages/react/package.json

package
before
after

inline-style-expand-shorthand
-
^1.2.0

Non-approved dependencies are detected.
The following package version constraints missing approved candidate:

failed constrains
approved candidates

<EMAIL_ADDRESS><EMAIL_ADDRESS>

  Generated by :no_entry_sign: dangerJS


Prerequisites show Docker for Windows as supported configuration - which is not correct

Please remove Docker for Windows from the list of prerequisites - according to the discussion at https://github.com/MicrosoftDocs/sql-docs/issues/4742, SQL Server Machine Learning Services do only run on Docker for Ubuntu 16.04 (nothing else is a supported configuration).
Likely the same is true for Docker for Mac?

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

ID: d6a10dd4-ef5f-f9a4-f4cb-36346ef183be
Version Independent ID: 567e43d3-67dd-a771-fcd4-566c84b44dde
Content: Install on Docker - SQL Server Machine Learning Services
Content Source: docs/linux/sql-server-linux-setup-machine-learning-docker.md
Product: sql
Technology: machine-learning
GitHub Login: @cawrites
Microsoft Alias: chadam

@ogsadmin I understand you are referring to the other issue that has been closed. It was identified that the specific server-based configuration you identified has not been that was tested. The documentation provides general guidance. You also reported error messages that were specifically related to your install, or an incomplete uninstall. To engage the product team to look at the specific configuration you are attempting to use, you need to ask someone within your organization to open a support ticket. The product team has the ability to track reported issues, once a support ticket has been created. Please contact support : https://www.microsoft.com/en-us/industry/services/support

@cawrites, it was you who explained to me that Docker for Windows is not a supported configuration - if that is true, then please update the documentation accordingly.
I have already found a solution for my initial issue and I now have a working setup - so I don't see the need to open a support case (and waste weeks going back and forth until somebody actually takes action - we've been through this a few times before).
I was only trying to help, ...
Best regards!

@ogsadmin I am glad you were able to work with a fellow contributor and find the solution you need. The team has access to all comments so no going back and forth is needed. Offering  support is an option we provide to all of the community but it is certainly not a requirement.
My only ask at this point is to continue to work with your PR to keep the conversation single threaded for discovery purposes. Microsoft appreciates your support and we will work with the product team to apply whatever documentation updates are needed.
We closed this thread so you can focus on updating just one. If you can support that effort it would be greatly appreciated.


[Bug Report] Input field doesn't work in google map search box while we validate it

Element UI version
2.3.9
OS/Browsers version
MacOS High Sierra / Any Browsers
Vue version
2.5.16
Reproduction Link
https://jsfiddle.net/hlaporthein/6vh1670w/6/
Steps to reproduce
https://jumpshare.com/v/tab1oKO78uzBx0nlQyBU
What is Expected?
I wanna input field to be ok with google map search box while we validate it.
What is actually happening?
Input field doesn't work with google map search box while we are validating input. If no validation for field, it works. So, I believe there would be an error in validating trigger. Here is the screencast of the problem https://jumpshare.com/v/tab1oKO78uzBx0nlQyBU

Also when you select a google autocomplete result it doesn't get updated in the input v-model, I think it has to do with the fact that the Google Autocomplete API changes the input value directly and Vue/Element don't see the value update.

Maybe you forget to set model for el-form.
https://jsfiddle.net/6vh1670w/7/

Hi @jikkai , adding el-form doesn't solve the project. I have tested raw html input, it worked well. But, when I use el-input, it doesn't work

@jikkai try entering "Paris" and click on the result, it will not be set in the el-input v-model and you will see a flicker of the input's value. Any idea how to fix this?

I created a demo: https://jsfiddle.net/6vh1670w/9/
Whatever you validate the input or not, you should set the input v-model by yourself.

@jikkai Ok this changes the v-model but the flicker is still there.
For example when you type "Paris" in the input move down with the down key and highlight the first result

Right before you click or hit enter the input value will be "Paris Town Gali No 6, Batala Rd, Amritsar, Punjab 143001, Inde"
When you select the result the input value will switch to "paris"
Then the place_changed gets triggered and the input value is set correctly to "Paris Town Gali No 6, Batala Rd, Amritsar, Punjab 143001, Inde" again.

Is there a way to fix this using an el-input? If not maybe there is a way to make our own input and make the el-form rules check the custom input value with the form validation?

@jikkai Do you see the problem I am describing? To me it's not a complete solution if the user sees a flicker. Any idea on a suggested workaround?

@Bounty31
What about this https://jsfiddle.net/6vh1670w/47/

@Bounty31 What about this https://jsfiddle.net/6vh1670w/48/

@jikkai That's better, I think with v-model instead of @change it's even simpler, see https://jsfiddle.net/y2z73Lw3/1/ also with the on result click changing the v-model

what if the filed element is ueditor or something but
data and validation logic is right, but event does not fire when data changes
how to fire the validation


Extremely slow compilation; resolving generics?

TypeScript Version:  3.5.0-dev.20190405
Search Terms: slow compilation generics
Code
example.zip
Expected behavior:
Compilation should take a reasonable amount of time
Actual behavior:
On my MacBook Pro, compilation takes 31 seconds before any error messages appear.
I suspect this may have to do with the compiler trying to resolve generic types. A few comments:

The code is hard to read, because I had to obfuscate it. Sorry about that.
This is a hacked-up version of some of our real code. The real version compiles successfully (unlike this hacked-up one which produces errors). This is based on a TypeScript module we have that takes two minutes to compile. It only has 19,000 lines of .ts files plus 100,000 lines of .d.ts files. Most of our similar-sized modules take about 30 seconds.
Take a look at the declaration of create at the bottom of src/sb_by_hr.ts. If you take out all the fancy generics, and instead put export const create = React.createFactory(Component);, compilation takes only 2 seconds.
You'll notice that lib/a.d.ts has a fairly large number of type declarations. The declare module "a/dm/ps" section is about 2800 lines of one- or two-line type declarations, and declare module "a/dm/pm" is about 3800. If you delete large chunks of type declarations from either one of those blocks, the compilation times goes down. It seems to go down. For example, if you delete about half of the types from "a/dm/ps", compilation time goes from 31 seconds down to 11.8 seconds. Similarly, if you delete about half of the types from "a/dm/pm", the time goes down to 11 seconds.

Related Issues:
These may or may not be related:

TypeScript Extremely Slow
Super slow compilation in rare cases when mixing explicit typing, generis and type inference

I would even say more, my project compilation fails with heap overflow.
This issue is somewhat connected to #30663

Thanks for the links, @Veetaha, that's interesting. But I don't think my issue is directly related to #30663, because of the version where the slowdown started. That issue is a new one that appeared in 3.4.1. I just did some testing with old versions, and the slowdown for my issue was introduced all the way back in 2.6.1 (a very long time ago).

I've encountered what sounds like a similar performance issue in 3.4.5 that persists in 3.5-rc.
Repo to reproduce the problem is here: https://github.com/richard-viney/typescript-performance-issue
It's easy to get compilation times up into the 10-20-30 second mark or more just by duplicating a single line of code. There are two workarounds documented in the README, both related to generics.
Trying to reduce to a simpler self-contained repro case proved tricky, as reducing the amount of type definitions being pulled in also progressively reduced the performance problem, as if there was a scaling issue inside the compiler itself where internal lookup/resolution times aren't scaling as they should.

I should also add that we were stuck on 3.2.x for a while because of this issue, it originally cropped up in TS 3.3.0 and we've ended up working around it in our app code (by using fewer generics) so that we can stay on the latest TS release.

Hi folks, sorry this one took a while to look at - I explored it a few times and I've come back to give it a shot for 4.0.
Some notes: the example.zip still is about 60s  when using the generics:
Files:                          15
Lines:                       35448
Nodes:                      171313
Identifiers:                 59172
Symbols:                     85089
Types:                       39287
Memory used:               772879K
Assignability cache size:    53456
Identity cache size:            12
Subtype cache size:         214809
Strict subtype cache size: 7305744
I/O Read time:               0.01s
Parse time:                  0.51s
Program time:                0.57s
Bind time:                   0.31s
Check time:                 52.88s
transformTime time:          0.03s
commentTime time:            0.00s
I/O Write time:              0.00s
printTime time:              0.04s
Emit time:                   0.04s
Total time:                 53.80s

vs 5 without
Files:                          15
Lines:                       35448
Nodes:                      171267
Identifiers:                 59152
Symbols:                     84954
Types:                       30552
Memory used:               127370K
Assignability cache size:    53396
Identity cache size:            12
Subtype cache size:              9
Strict subtype cache size:       0
I/O Read time:               0.01s
Parse time:                  0.53s
Program time:                0.58s
Bind time:                   0.32s
Check time:                  2.90s
transformTime time:          0.02s
commentTime time:            0.00s
I/O Write time:              0.00s
printTime time:              0.04s
Emit time:                   0.04s
Total time:                  3.84s

Pretty wild difference in the subtype checking caches between them.

FYI the repro case that I mentioned above back on 18 May 2019 has been resolved by an intervening TS release (not sure which one though).

OK, I re-ran the checks with wes against different versions of TypeScript including nightly and it looks like this is fixed in 3.9 and still is in master
For 3.6, 3.8 and 3.8 we were looking at 60s but for 3.9 and nightly it was ~2s for the example. We did a bunch of perf work on handling large unions then which likely are the candidate for the fix 👍


Reimplement attributes view for component debug screen

This PR brings back the Debug view in the Attribute Panel, with some cleanups along the way:

Created debug modules for the various Node types on the graph: Socket, Attribute Prototype, Attribute Value, Component
Moved logic out of SDF and into the DAL
Moved the debug components into a Debug folder in app/web
Fixed up the interfaces a bit there for this data
Created a AttributeValuePath struct to consolidate path creation for attribute values for props and sockets (including the key/index for child attribute values of maps/arrays)
Includes input/output socket and attribute value debug data!
One realllllllllly basic integration test, but this should be expanded

bors try

bors try

bors cancel

bors try

bors try

Really awesome work @britmyerss 🥳

bors try

bors merge


Blocking Factor validation

The Blocking Factor defines the number of Records within a block (a block is 940 characters). For all Files moving between a DFI and an ACH Operator (either way), the value “10” must be used. If the number of Records within the File is not a multiple of ten, the remainder of the block must be filled with “9’s.”

closed with #96


Add proximity and buffer_metric functionalities with metric option based on finding local UTM

Summary
This PR adds a proximity() function to the Vector and Raster classes that mirrors GDAL's proximity not implemented in rasterio (https://github.com/rasterio/rasterio/issues/319), and a buffer_metric() method for the Vector class to avoid the trouble of reprojecting from geographic system, buffer, than reverse-projecting, based on finding a local UTM zone.
It also adds a Raster method equal_georeferenced_grid to check if two rasters have the same georeferencing.
In details
Proximity
The proximity is computed using scipy.distance_transform_edt (https://docs.scipy.org/doc/scipy/reference/generated/scipy.ndimage.distance_transform_edt.html).
The functioning is as follows:

For Raster classes, the proximity can be either computed directly from target values of the array self.data, or from a Vector passed as argument that is automatically rasterized on self. For target values, the default behaviour is the same as GDAL: a list of any number of values can be passed. If none are passed, all non-zero values are targets. For the distance unit, I also implemented both "pixel" and "georeferenced", but put the default as "georeferenced" contrary to GDAL's "pixel".

For Vector classes, the proximity can be computed from self by passing a Raster object to rasterize the vector on.

The resulting proximity values are thoroughly tested against GDAL Python's gdal.ComputeProximity() with artificial and real Raster data. All results are the same, except for very complex case where a few percentage of values (<1%) differ by ~1% (not even a floating point issue, GDAL's algorithm is simply slightly different for some cases).
Additionally, any geometry_type can be passed to rasterize the Vector object with (default: boundary, which is the most common). And an in_or_out option can be passed to include only the outside or inside proximity for a geometry that have an area (Polygon, MultiPolygon, etc).
Buffer metric
This function is to avoid the trouble of reprojecting a Vector in a local metric system for buffering without deformation, and then reverse-projecting. This involves finding the local metric system wanted, reprojecting to it, recreating ageopandas.GeoDataFrame object in the right CRS with the buffer geopandas.GeoSeries, and reverse-projecting.
For now this function only supports reprojecting in the local UTM which, for speed, is approximated by the latitude/longitude coordinates of the centroid of non-projected vector (centroid are not exactly the same depending on projections, but generally robust enough?).
Two new functions latlon_to_utm and utm_to_epsg in projtools help converting coordinates to UTM zone and to related EPSG (maybe there's some new stuff out there, but a couple years ago the utm Python package didn't allow UTM zones near poles, which was annoying, and I didn't know of any package that could interpret the UTM zone into an EPSG code).
All functions of projtools and the buffer_metric method in Vector are tested. I also added the metric argument in buffer_without_overlap function, which does the same procedure.
Issues closed
This PR:

Resolves #330,
Resolves #267,
Resolves #145,
Resolves #202.

And adds tests for all.

Tests all passing locally (= will be all good PR #335 is merged)

Merging here as well!


Black screen when booting without uefi

when i boot with uefi i get stuck on an interactive shell, when i exit i go to the bios screen but when i exit the bios, im back at the shell, when i boot without uefi, i just get a black screen that never seems to change
this is on an iphone Xr on the Altstore version

EFI shell means you did not install an UEFI-compatible operating system in the VM.


Migration tool: Remove or fix exact nullability

We are disabling exact nullability because we currently don't have a good way to test its usefulness, and we've found a few bugs in it over time.
We need to either remove it or fix these bugs or figure out a different design, etc.

Previous exact nullable issues as well that have come up but been fixed: #40181

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


Init spilt method creates sub init methods with same name

Description:
When we have large init methods in both module and its test module, init sub methods are created with same name. This causes java verification issues.

Closing since this is fixed with https://github.com/ballerina-platform/ballerina-lang/pull/18933


Fix performance issue and connection leakage

1)Use the layer digest as the name of the layer when calling Clair API
2)Add header "Connection":"close"

Coverage increased (+0.02%) to 54.431% when pulling bf13d92dc07a82924c0e1b7bd0ef413ef8e0ca6e on reasonerjt:master into<PHONE_NUMBER>c0ec3ecce026d8fadb4132a9c718cd on vmware:master.

Coverage decreased (-0.01%) to 54.396% when pulling 3328c84e6ebb0a79cf5143f3632f5ca584c4690b on reasonerjt:master into<PHONE_NUMBER>c0ec3ecce026d8fadb4132a9c718cd on vmware:master.

closing the PR as seen some issue of dup layer name.  May need to reconsider the way to generate the unique and re-usable layer name.


set.intersect() fails inside withMutations if sharing elements with set.add/intersect

Running this in node
Immutable.Set(['a', 'd']).withMutations(function(set) {
      set.add('b');
      set.union(['c']);
      set.intersect(['b', 'c', 'd']);
})

will fail with a TypeError: Cannot read property '1' of undefined. It seems that intersect() does not play well when add() or union() calls before it that share similar elements.

I thought I'd check up on this - could I get feedback / acknowledgement that this has been seen?

Seen. Certainly there shouldn't be a TypeError, I'll look into that. But this is also not legal code. Union and Intersection always return new collections - even within a withMutations block, so this should result in the Set ['a', 'b', 'd'].

I see. Thanks!

A possible suggestion, inside src_Set__Set.prototype.intersect, should the inner call back return false to stop the iteration?
src_Set__Set.prototype.intersect = function() {var iters = SLICE$0.call(arguments, 0);
    if (iters.length === 0) {
        return this;
    }
    iters = iters.map(function(iter ) {return SetIterable(iter)});
    var originalSet = this;
    return this.withMutations(function(set ) {
        originalSet.forEach(function(value ) {
            if (!iters.every(function(iter ) {return iter.includes(value)})) {
                set.remove(value);
                // <--- return false here?
            }
        });
    });
};

Suggestion, inside src_Set__Set.prototype.intersect, the values to be removed inside the callback could be locally accumulated and then removed. For example:
src_Set__Set.prototype.intersect = function() {var iters = SLICE$0.call(arguments, 0);
if (iters.length === 0) {
return this;
}
iters = iters.map(function(iter ) {return SetIterable(iter)});
var originalSet = this;
return this.withMutations(function(set ) {
        var acc = [];

        originalSet.forEach(function(value ) {
            if (!iters.every(function(iter ) {return iter.includes(value)})) {
                acc.push(value)
            }
        });

        acc.forEach(function (value) {
            set.remove(value);
        })
    });
};

Thank you for reporting this issue and appreciate your patience. We've  notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

@magnus-madsen you were right all along. #1083 implements that approach for the fix. Better late than never!


Revert "File list support"

Reverts apple/swift-driver#144

@swift-ci please test

CC: @DougGregor @cltnschlosser

@owenv Just opened this as a fix as well: https://github.com/apple/swift-package-manager/pull/2924 @compnerd

Great, let's fix forward then


Add ecosystem chooser to homepage form

Reticketed from https://github.com/gratipay/gratipay.com/pull/4598.

Dropping this per https://github.com/gratipay/inside.gratipay.com/issues/1160#issuecomment-333257027.


Build problems due to module redacted

Was trying to build the API locally and was running into the following problem;
   Compiling qvet-api v0.1.2 (/{REDACTED}/qvet/qvet-api)
error[E0583]: file not found for module `redacted`
  --> qvet-api/src/lib.rs:15:1
   |
15 | mod redacted;
   | ^^^^^^^^^^^^^
   |
   = help: to create the module `redacted`, create file "qvet-api/src/redacted.rs" or "qvet-api/src/redacted/mod.rs"

error[E0432]: unresolved import `crate::redacted::Redacted`
 --> qvet-api/src/runtime.rs:5:5
  |
5 | use crate::redacted::Redacted;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ no `Redacted` in `redacted`

Some errors have detailed explanations: E0432, E0583.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `qvet-api` due to 2 previous errors

I'm guessing there's a Cargo.toml change sat in your working tree? I didn't want to PR anything in, in the event that you'd defined a custom module yourself.

Ah sorry this is a missed file in git. Will fix now - on my todo list to add a ci check, so will do that now.

Added ci in https://github.com/tommilligan/qvet/pull/4


Crash while analyzing libbinaryninjacore

Version and Platform (required):

Binary Ninja Version: 4.0.4844-dev, 94ce4c18
OS: macos
OS Version: 14.3
CPU Architecture: arm64

Bug Description:
It appears that BN crashes when attempting to analyze the libbinaryninjacore.1.dylib file from the Mac ARM build of BN. I assume this is not intended behaviour in order to block reverse engineering of BN itself 😄
Steps To Reproduce:

Open libbinaryninjacore.1.dylib in BN
Wait for the crash

Did you happen to do something like navigate using the symbols list?

Fixed in 4.0.4845-dev.


Use net_http as default HTTP adapter for Jruby

Fixes #123
Currently excon does not work out of the box with Jruby due to a more restrictive cipher set.  In order to prevent usability issues this sets the default adapter to net_http for Jruby

Coverage increased (+0.02%) to 96.966% when pulling 01cbd0a4a43d4bc085df1a7d564804908e2971e9 on bmulvihill:default-jruby-adapter into 72c51d3ad20d0358808f2dd5b05038c17ab23750 on dashofcode:master.

@bmulvihill the update for JRuby looks good. Can you add JRuby to the list of Ruby versions that are verified by TravisCI? This will make sure it doesn't get broken in the future.
https://github.com/dashofcode/tracker_api/blob/master/.travis.yml#L9


auto closing brackets not working on vscode 1.57

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.57
OS Version: ubuntu 20.04.2 LTS

Steps to Reproduce:

open a js file on code
type a opening bracket (
expected result ()
actually getting (
bracket is not auto closing

@alexdima I set editor.autoClosingBrackets always.
can you kindly watch the screenrecord ->
https://www.loom.com/share/cf6818f399d441be90fcce5d7b77c5da

I had the same issue suddenly this morning, but I finally get this work by specify the language

But it's still not work globally, only the language specified.

@0wx language specific way it worked. Thanks.

Encountered this issue as well.
It stopped working suddenly, in the middle of coding session. Not working in JS and Python.
Adding "editor.autoClosingBrackets": "always" globally does not solve the issue. Only language-specific settings work.

I also just got this problem as well.

This might be defined by an extension. Are you by any chance using copilot?

using copilot?

I have it installed, but not working yet, because I'm not in the preview program yet.

Copilot is defining these default language settings that can be overwritten only using language specific settings. They do that to workaround an issue in vscode tracked at https://github.com/microsoft/vscode/issues/125663 . Once we ship our next stable release (sometime this week), they will be free to remove that workaround. Until then you can disable the extension if you are not in the preview program yet or you can define the language specific setting e.g.:
"[typescript]": { "editor.autoClosingBrackets": "languageDefined" }

Copilot is defining these default language settings that can be overwritten only using language specific settings. They do that to workaround an issue in vscode tracked at #125663 . Once we ship our next stable release (sometime this week), they will be free to remove that workaround. Until then you can disable the extension if you are not in the preview program yet or you can define the language specific setting e.g.:
"[typescript]": { "editor.autoClosingBrackets": "languageDefined" }

This fixed it for me.

I was running into this and it looks like it is the new CoPilot plugin that causes this to stop working. Just uninstall and you should be back to normal.

i uninstalled copilot and yet the issue persists. it WAS caused by copilot as it occured immediately after i installed it, but i disabled it and it still hasnt gotten rid of it. any fixes yet?

i tried installing copilot again and it just doesn't work at all.

I also have this issue after installing copilot. Disabling it and reopening the vs code works for me.

I also just got this problem as well. It is on always. But when i edit my code the auto closing brackets doesnt work.

i just install copilot and the problem happen, so just disable and i hope that will fix :+1:

Same thing is happening with me but with python instead. Weirdly it doesn't happen if its a text file and even in a IPython notebook

@unownone You can workaround using "[python]": { "editor.autoClosingBrackets": "languageDefined" }

@alexdima do i have to do this on every language individually? or is there a way to do it for all

I FOUND A SOLUTION!
go into settings.json and delete this:

and save, and it's fixed!

I had the same issue, but it went away after I disabled the Copilot extension.

i had the same issue but...just right "editor.autoClosingBrackets": "always" in your settings.json
and note : it only happens in copilot don't you think

Copilot is defining these default language settings that can be overwritten only using language specific settings. They do that to workaround an issue in vscode tracked at #125663 . Once we ship our next stable release (sometime this week), they will be free to remove that workaround. Until then you can disable the extension if you are not in the preview program yet or you can define the language specific setting e.g.:
"[typescript]": { "editor.autoClosingBrackets": "languageDefined" }

This fixed it for me.

An extension breaking a basic feature of editor and being silent about it does not look good.

Uninstalled copilot and tried using the feature, it's working now. It's because of the extension, it's breaking down.

i reinstalled copilot (got into the technical preview) and i'm loving it, but the issue has risen again. how do i get this to work again WITH copilot still enabled?

@crackerberries please see Alexs comment:

Copilot is defining these default language settings that can be overwritten only using language specific settings. They do that to workaround an issue in vscode tracked at #125663 . Once we ship our next stable release (sometime this week), they will be free to remove that workaround. Until then you can disable the extension if you are not in the preview program yet or you can define the language specific setting e.g.:
"[typescript]": { "editor.autoClosingBrackets": "languageDefined" }

You need to do that for every language that you use.

For me it was Colpilot. I have removed and it is working flawlessly.

I think it's bcz of github copilot ,i uninstalled it now it is working fine.

it IS because of copilot, but i actually kinda like copilot and don't wanna remove it

using copilot?

I have it installed, but not working yet, because I'm not in the preview program yet.

using copilot?

I have it installed, but not working yet, because I'm not in the preview program
Yes bro, it is working after removing copilot

Same here, it was copilot. Disabled.

How do i do the language specific thing for jsx?

This might be defined by an extension. Are you by any chance using copilot?

Thanks sir this worked for me

How do i do the language specific thing for jsx?

Check the language of the file in the bottom right corner of the editor. With JSX, the language is usually javascriptreact or typescriptreact. You can then disable it as mentioned above:
{
    "[javascriptreact]": { "editor.autoClosingBrackets": "languageDefined" }
}

How do i do the language specific thing for jsx?

Check the language of the file in the bottom right corner of the editor. With JSX, the language is usually javascriptreact or typescriptreact. You can then disable it as mentioned above.
{
    "[javascriptreact]": { "editor.autoClosingBrackets": "languageDefined" }
}

In case you're wondering where to put this, it should be put inside the .vscode/settings.json file, at the root of your project. This defines a set of settings for the workspace and overrides global settings.

Thanks a lot, was looking for the javascriptreact tag, works now.

Thank U So Much

using copilot?

I have it installed, but not working yet, because I'm not in the preview program yet.

doesn't matter. if you have copilot (even not activated by GitHub) auto-closing brackets are not gonna work.

This might be defined by an extension. Are you by any chance using copilot?

Yes , and after uninstalling it works!!!

Disabling copilot does the job

This might be defined by an extension. Are you by any chance using copilot?

this was my issue, after un-installing the extension it works now, thank you

Yeah,
I can confirm that CoPilot did that for me. Anyway, for Javascript and Typescript I've used this setting:
},       "[typescript]": {           "editor.autoClosingBrackets": "always"       },       "[javascriptreact]": {           "editor.autoClosingBrackets": "always"       },      "[javascript]": {          "editor.autoClosingBrackets": "always"      }

I just updated to VS code 1.59 and then this happened, so I was worried. But it was indeed copilot, as soon as I uninstalled it it worked.
I hadn't noticed right away because I've been learning svelte, and the problem with the brackets wasn't there. I don't know if it's because of their recommended formatter, or if copilot simply doesn't mess with .svelte files.
Afterwards I reinstalled copilot, giving it a second chance, and set individual language specific settings in the settings.json file like everyone else, and I got my auto closing brackets back.
"[typescript]": {
  "editor.autoClosingBrackets": "always"
},
"[javascriptreact]": {
  "editor.autoClosingBrackets": "always"
}

The question is, will this be the only breaking feature?

This might be defined by an extension. Are you by any chance using copilot?

Thanks buddy

This might be defined by an extension. Are you by any chance using copilot?

I laughed. Installed it 2 hours prior to this. Thanks for the quick solution, disabling GitHub Copilot worked for me.

Same issue....I disabled copilot and the auto close bracket functionality is working....
I think copilot dev will soon fix this bug!

disable copilot works for me


Fix event recorder not to log events without a reference

#4974 removed a return statement that prevented panics when an ObjectReference couldn't be obtained from an object passed to Event.

@lavalamp PTAL

LGTM - merging this because it just restores behavior from a prior regression.


1.10.x into dev

Merged 1.10.x into dev.
@sebastienros @HermesSbicego-Laser
We need to verify the approach we chose for solving conflicts with the migrations for CommonPartRecord:
https://github.com/LaserSrl/Orchard/blob/799b3a920d3c1134a87e152cc79a83d7714275af/src/Orchard.Web/Core/Common/Migrations.cs#L186
basically we considered the version from 1.10.x "right" and had the conflicting migrations from dev follow it. This is a breaking change for dev.

@sebastienros  I fixed what we discussed yesterday for that migration, so I'll go ahead and merge this into dev.
I will also close the PRs regarding the new version of log4net, since the upgrade of that is included here.


Deploy SSIS Project with PowerShell - Azure DevOps + ADF IR + Azure SQL Database - Issue

Hello,
I get an error when I want to deploy an ispac from Azure DevOps with a PowerShell script (as this one) to an Azure SQL Database:
Connecting to SSIS Instance server ...
Enumerating all folder in the project code
ISPAC File ==>  TEST
Project File Name Fullname ==>  TEST.ispac
Deploying  TEST project ...
##[command]Disconnect-AzureRmAccount -Scope Process
##[command]Clear-AzureRmContext -Scope Process
##[error]Exception calling "DeployProject" with "2" argument(s): "Failed to deploy the project. Try again later."
##[section]Finishing: Azure PowerShell script: Deploy SSIS Package
Have you ever met this error ? If yes, do you know how to solve it ?
Thank you

@bertrandpons Are you following any tutorial or sourcing any documentation for guidance. I am providing this document: Deploy an SSIS project with PowerShell as a reference that will help with the PowerShell + SSIS part of the equation. It appears you might be attempting to execute this via Azure DevOps for an Azure Data Factory project? The document I provided should help with getting the SSIS package to deploy via PowerShell commands. Please provide any documentation you are attempting to use for this tutorial. Thanks!

@Mike-Ubezzi-MSFT Thank you for your reply.
I use the script attached that I run through the task Azure PowerShell in my Release Pipeline on Azure DevOps.
The Script Arguments are: '$(ETL_USER)' '$(ETL_SERVER_ENDPOINT)' '$(ETL_ISPAC_FILEPATH)' '$(ETL_FOLDER_NAME)' '$(ETL_FOLDER_DESCRIPTION)' -etl_password_param '$(ETL_PASSWORD)', variables that I set in the dedicated tab in the Release Definition.
[DeploySSISPackage]AzurePS.txt

@Mike-Ubezzi-MSFT I have been able to deploy SSIS package with this script

@Mike-Ubezzi-MSFT Well actually it doesn't work that well... Either it deploys without error but when I go to Integration Services with SSMS, I see that it did not deployed all the parts, or it raises a timeout error or an "Exception calling "DeployProject" with "2" argument(s): "Failed to deploy the project. Try again later.""

@Mike-Ubezzi-MSFT I finally solved the issue. It is related to the powershell script that requires that the ispac filename be the same as the dtproj filename. As I had a project named Test.SSIS.dtproj and an ispac file named Test.ispac, the powershell script was not able to run correctly. I had to set the ispac filename as Test.SSIS.ispac

@bertrandpons Thanks for updating this issue with a resolution. It assists others who might be experiencing the same issue. Thanks again for your interest in Azure cloud services.


Revert "Fix security vulnerabilities in proteus and webapps"

Reverts apache/drat#145

Solr doesn't work for Proteus after these updates. Have to revert.


Feature/control point

Feature Update for the Polar H10
I'm working on support for using the PMD data and Control Point streams to get other sensor data from the H10. Some features that I've been working to add / improve on version 0.0.1.
Features

[x] Ability to subscribe to PMD data
[x] Read multiple samples with one notification from PMD data
[x] Struct to read data from PMD data
[x] Fix ControlResponse to read responses properly (more below)
[x] Add function to EventHandler returns a boolean of should the event loop stop (more below)
[x] Fix start_measurement to allow users to request different data types
[x] Add unit testing throughout the code
[x] Add support to read features of your device
[x] Add structure for hr data to store rr interval as well as bpm
[x] Reinstate public functions for start/stop measurement
[x] Test with multithreaded example
[x] Prevent user from starting event loop without subscribing to anything

Fix ControlResponse to read responses properly
When using start_measurement the response code gets an invalid number (0xf0) which will cause the program to not work properly. The first byte isn't supposed to be interpreted as a response code, but instead tells you what the data is. In this case, a "control point response". All you have to do when validating this first byte is check that it matches 0xf0. The rest of the interpretation seems to work fine.
Add function to EventHandler returns a boolean of should the event loop stop
Right now, the only way to stop the event loop is for the Bluetooth connection to break for some reason or to keyboard interrupt the program, which aren't exactly great solutions. I'm wondering if you have any thoughts for a solution. I thought to add a function to the EventHandler trait that will be checked within the event loop if the loop should stop. For example, the program could asynchronously listen for input and when the user presses enter, the end loop function can return false and the program can send stop_measurement to end the program gracefully. To retain the same functionality as right now, the function can just return true always.
This is a WIP pull request. I was wondering if you had any thoughts.

I fixed the control response in efc77306761c82d7779c0a10f97c026a895293b3. The response is received by notification from PMD control point. I just had to modify the settings and start/stop measurements functions to temporarily subscribe to PMD CP, and then unsubscribe to it after.

Hey, thank you very much for the PR! I didn't notice it was happening until now, so sorry for not responding to the issue earlier.
Whenever this is ready for review I'll plug in my H10 and test it out.

Right now, the only way to stop the event loop is for the Bluetooth connection to break for some reason or to keyboard interrupt the program, which aren't exactly great solutions. I'm wondering if you have any thoughts for a solution.

I think having a cancel function that returns a boolean is an okay solution for now. The only thing I worry about is the possibility of the cancel check function taking too much time away from the event loop, but if people aren't throwing heavy checks in there it should be fine.

I think having a cancel function that returns a boolean is an okay solution for now. The only thing I worry about is the possibility of the cancel check function taking too much time away from the event loop, but if people aren't throwing heavy checks in there it should be fine.

I was thinking something like another thread could be running in the background and be polled for true/false so as not to interfere with the event loop.

Hey @Roughsketch I just made an example for how the should_continue function for the event handler should work. It's titled multi-threaded under examples/. This is the general idea of what I was thinking the should_continue function should be used for, do you have any thoughts?

Hey @Roughsketch I just made an example for how the should_continue function for the event handler should work. It's titled multi-threaded under examples/. This is the general idea of what I was thinking the should_continue function should be used for, do you have any thoughts?

That seems sensible to me. I don't know of any particularly better ways to do it in Rust and this seems to follow the same sort of flow I've seen in other libraries.
Also I want to note that I may take some time in-between reviews due to work or other plans, so sorry if it takes me a bit to respond.

Hey @Roughsketch, I've finished my additions. It's ready to be reviewed. I made another example demonstrating some of the features called cli-app. It doesn't have support for heart rate as is, but demonstrates one simple way to use the library.

Hey, I understand that you're busy, no worries. :)

Hey @Roughsketch just following up, can you take a look at my pr. Is there any changes you want? Thanks

I can potentially take a look later today, or at the very least sometime this weekend.

@Roughsketch I've fixed the issues. If this is everything I'll rebase the changes again.

Thanks for your attention, glad I could help.

It's late for me now, but I'll tidy up the base readme and publish this soon. Thanks again!