Links to footnotes appear to be broken

Links to footnotes appear to be broken when rendered with mkdocs-print-site-plugin.
For example, the 1 & 2 footnotes in "Lorem ipsum dolor sit amet, consectetur adipiscing elit" on the example page link to
https://timvink.github.io/mkdocs-print-site-plugin/print_page.html#demo_content-fn:1
and
https://timvink.github.io/mkdocs-print-site-plugin/print_page.html#demo_content-fn:2
But those links do not resolve.

Thanks for reporting! Indeed an edge case, I will address it in next release. Feel free to submit a PR if you need a fix quickly.

Digging into this. This is how the footnotes link properly in the demo page itself:
1

Lorem ipsum dolor sit amet, consectetur adipiscing elit. ↩

On the print site page, only part of these links are updated, resulting in broken links.

    1

Lorem ipsum dolor sit amet, consectetur adipiscing elit. ↩

The cause was that I did not update the sup and li tags. Fixed now in v.1.1 https://github.com/timvink/mkdocs-print-site-plugin/releases


Add Google Container Builder config for k8s-metadata-proxy

GCB config to be used to automate build of Kubernetes addon images.

@rvkubiak can you have someone from your team LGTM this?

@mikedanese Sure, in fact I think we're going to end up closing these PRs and just submitting them to their own repo.  I've since transferred projects so waiting to hear on the final details, but I imagine I'll close this out soon.

SGTM, let me know if you need anything.

Moving these configs to their own repo.


Fix CI compile failure due to merge conflict

Which issue does this PR close?

Closes https://github.com/apache/datafusion/issues/13218
Rationale for this change
There was a logical conflict between these two PRs:

https://github.com/apache/datafusion/pull/13127
https://github.com/apache/datafusion/pull/13206

What changes are included in this PR?
Fix Build

Are these changes tested?

Are there any user-facing changes?

Yup, this is also preventing my main branch from building.

🚀  -- thanks @timsaucer


Gmapping Launch file / URDF axis Problem

Gmapping launch file needs to be changed according to MediBot.
Currently, it is impossible to map with it for new world because of It's CAD-> URDF axis does not sit right with conventions by ROS, hence they cause problems while mapping (But not with navigation).
Current links and joints names in robot_gmapping.launch file belong to a different simple wheeled robot to map the COS world, which needs to be updated ASAP / or the URDF to be fixed.

May be If you try it with the latest pull, gmapping will work.
If this was the issue, this issue can be closed.
Thanks


policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+

k8s 1.21 says: policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget

I migrated out zeebe gke cluster to 1.21. It makes sense now to update the manifests

Please check with Felix on what the support cadence should be for us - should we follow Kubernetes', or do we have data of our own that would inform another choice?

See https://camunda.slack.com/archives/CHBFBRFM2/p1656322979043949?thread_ts=1656074129.033929&cid=CHBFBRFM2

I will close this issue since we updated PodDisruptionBudget for all our resources.


Lots of information missing

This page, like most Microsoft documentation is missing crucial information on other settings and their impact of migrations customers are running.
For example https://learn.microsoft.com/en-us/sharepointmigration/mm-box-step5-map-identities is only a brief run down of this section. Upon looking at the settings it describes in a migration project there are more options available that are not touched on in the documentation.
For example the documentation just mentions mapping identities, but the GUI show other options such as  "Folders and File Permissions" This section isn't very clear, it suggests we need to tick the checkbox in order to reshare items if there is a valid user mapping, but the wording suggests this only affects files, the wording above the checkbox says that Folders are automatically shared when a valid user mapping exists. Does this mean If a folder was shared in Box then it is re-shared in OneDrive regardless of whether the checkbox is checked or not? Because folders and files are 2 different things.
We have been working on the assumption that nothing is re-shared as we have not checked the Re-share checkbox, but we have now had users reporting that folders they had access to in Box are now showing in OneDrive when the owners of the data have not shared it with them.
We have also tried to test this by removing user mappings and migrating shared folders from Box to OneDrive but cannot reproduce it. So it seems to be random as to what is re-shared. The users are 100% confident they have not re-shared any data from OneDrive.

Hello @mcloum
Many thanks for your feedback, I could get information that the article is currently being actively worked on to be updated.

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

How is this closed/resolved when nothing has changed with the documentation.


Missing attributes heat_demand_limited_by_outside_temperature and request_count

Before submitting a new issue

[x] I redownloaded the latest release and restarted Home Assistant
[x] I've checked known issues
[x] I've enabled debug logs and attached the relevant logs to this ticket

Problem description
The HA logs are filled with errors related to missing attribute heat_demand_limited_by_outside_temperature. The attribute heatDemandLimitedByOutsideTemperature is received from the API call, but in HA, it appears as unavailable.
It is sometimes followed by the missing attribute request_count error.
Logs
2024-11-06 01:30:29.767 DEBUG (MainThread) [custom_components.mypyllant] Refreshing DailyDataCoordinator
2024-11-06 01:30:29.767 DEBUG (MainThread) [custom_components.mypyllant.coordinator] Starting async update data for DailyDataCoordinator
2024-11-06 01:30:29.767 DEBUG (MainThread) [custom_components.mypyllant.coordinator] Waiting 119s until token refresh for<EMAIL_ADDRESS>2024-11-06 01:30:29.768 DEBUG (MainThread) [myPyllant.http_client] Starting GET to https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/homes
2024-11-06 01:30:29.816 DEBUG (MainThread) [myPyllant.http_client] Got response for GET to https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/homes: ...
2024-11-06 01:30:29.816 DEBUG (MainThread) [myPyllant.http_client] Starting GET to https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/systems/XXXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX/meta-info/time-zone
2024-11-06 01:30:29.884 DEBUG (MainThread) [myPyllant.http_client] Got response for GET to https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/systems/XXXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX/meta-info/time-zone: ...
2024-11-06 01:30:29.885 DEBUG (MainThread) [myPyllant.http_client] Starting GET to https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/systems/XXXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX/tli
2024-11-06 01:30:29.954 DEBUG (MainThread) [myPyllant.http_client] Got response for GET to https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/systems/XXXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX/tli:
{
    "state": {
        "system": {
            "outdoorTemperature": 3.3515625,
            "outdoorTemperatureAverage24h": 5.15625,
            "systemFlowTemperature": 36.25,
            "systemWaterPressure": 1.3,
            "cylinderTemperatureSensorBottomCH": 27.8125,
            "cylinderTemperatureSensorBottomDHW": 40.6875,
            "cylinderTemperatureSensorTopCH": 36.875,
            "cylinderTemperatureSensorTopDHW": 45.3125,
            "energyManagerState": "STANDBY",
            "systemOff": false
        },
        "zones": [
            {
                "index": 0,
                "desiredRoomTemperatureSetpointHeating": 19.0,
                "desiredRoomTemperatureSetpoint": 19.0,
                "currentSpecialFunction": "NONE",
                "heatingState": "IDLE",
                "quickVetoStartDateTime": "1970-01-01T00:00:00Z",
                "quickVetoEndDateTime": "1970-01-01T00:00:00Z"
            }
        ],
        "circuits": [
            {
                "index": 0,
                "circuitState": "HEATING",
                "currentCircuitFlowTemperature": 36.0625,
                "heatingCircuitFlowSetpoint": 33.681892,
                "calculatedEnergyManagerState": "HEATING_ACTIVE"
            }
        ],
        "dhw": [
            {
                "index": 255,
                "currentSpecialFunction": "REGULAR"
            }
        ],
        "ventilation": []
    },
    "properties": {
        "system": {
            "controllerType": "VRC720",
            "isLegionallaProtectionActivated": "OFF",
            "systemScheme": 8,
            "backupHeaterType": "CONDENSING",
            "backupHeaterAllowedFor": "DHW_AND_HEATING",
            "temporaryAllowBackupHeater": "DISABLED",
            "moduleConfigurationVR71": 6,
            "energyProvidePowerCutBehavior": "DISABLE_HEATPUMP_AND_BACKUP_HEATER",
            "smartPhotovoltaicBufferOffset": 10.0,
            "externalEnergyManagementActivation": false
        },
        "zones": [
            {
                "index": 0,
                "isActive": true,
                "zoneBinding": "NONE",
                "isCoolingAllowed": false,
                "associatedCircuitIndex": 0
            }
        ],
        "circuits": [
            {
                "index": 0,
                "mixerCircuitTypeExternal": "HEATING",
                "heatingCircuitType": "MIXER_CIRCUIT_EXTERNAL"
            }
        ],
        "dhw": [
            {
                "index": 255,
                "minSetpoint": 40.0,
                "maxSetpoint": 75.0
            }
        ],
        "ventilation": []
    },
    "configuration": {
        "system": {
            "continuousHeatingStartSetpoint": -26.0,
            "alternativePoint": -21.0,
            "heatingCircuitBivalencePoint": -20.0,
            "dhwBivalencePoint": -15.0,
            "adaptiveHeatingCurve": false,
            "dhwMaximumLoadingTime": 60,
            "dhwHysteresis": 5.0,
            "dhwFlowSetpointOffset": 25.0,
            "continuousHeatingRoomSetpoint": 20.0,
            "hybridControlStrategy": "BIVALENCE_POINT",
            "maxFlowSetpointHpError": 30.0,
            "dhwMaximumTemperature": 50.0,
            "maximumPreheatingTime": 10
        },
        "zones": [
            {
                "index": 0,
                "general": {
                    "name": "Topeni",
                    "holidayStartDateTime": "2015-01-01T00:00:00Z",
                    "holidayEndDateTime": "2015-01-01T00:00:00Z",
                    "holidaySetpoint": 15.0
                },
                "heating": {
                    "operationModeHeating": "MANUAL",
                    "setBackTemperature": 15.0,
                    "manualModeSetpointHeating": 19.0,
                    "timeProgramHeating": {
                        "metaInfo": {
                            "minSlotsPerDay": 0,
                            "maxSlotsPerDay": 12,
                            "setpointRequiredPerSlot": true
                        },
                        "monday": [
                            {
                                "startTime": 360,
                                "endTime": 1320,
                                "setpoint": 20.0
                            }
                        ],
                        "tuesday": [
                            {
                                "startTime": 360,
                                "endTime": 1320,
                                "setpoint": 20.0
                            }
                        ],
                        "wednesday": [
                            {
                                "startTime": 360,
                                "endTime": 1320,
                                "setpoint": 20.0
                            }
                        ],
                        "thursday": [
                            {
                                "startTime": 360,
                                "endTime": 1320,
                                "setpoint": 20.0
                            }
                        ],
                        "friday": [
                            {
                                "startTime": 360,
                                "endTime": 1320,
                                "setpoint": 20.0
                            }
                        ],
                        "saturday": [
                            {
                                "startTime": 420,
                                "endTime": 1380,
                                "setpoint": 20.0
                            }
                        ],
                        "sunday": [
                            {
                                "startTime": 420,
                                "endTime": 1380,
                                "setpoint": 20.0
                            }
                        ]
                    }
                },
                "cooling": {}
            }
        ],
        "circuits": [
            {
                "index": 0,
                "heatingCurve": 0.6,
                "heatingFlowTemperatureMinimumSetpoint": 20.0,
                "heatingFlowTemperatureMaximumSetpoint": 45.0,
                "heatDemandLimitedByOutsideTemperature": 20.0,
                "heatingCircuitFlowSetpointExcessOffset": 0.0,
                "setBackModeEnabled": true,
                "roomTemperatureControlMode": "NON",
                "epsilon": 2.0
            }
        ],
        "dhw": [
            {
                "index": 255,
                "operationModeDhw": "TIME_CONTROLLED",
                "tappingSetpoint": 50.0,
                "holidayStartDateTime": "2015-01-01T00:00:00Z",
                "holidayEndDateTime": "2015-01-01T00:00:00Z",
                "timeProgramDhw": {
                    "metaInfo": {
                        "minSlotsPerDay": 0,
                        "maxSlotsPerDay": 3,
                        "setpointRequiredPerSlot": false
                    },
                    "monday": [
                        {
                            "startTime": 900,
                            "endTime": 1440
                        }
                    ],
                    "tuesday": [
                        {
                            "startTime": 900,
                            "endTime": 1440
                        }
                    ],
                    "wednesday": [
                        {
                            "startTime": 900,
                            "endTime": 1440
                        }
                    ],
                    "thursday": [
                        {
                            "startTime": 900,
                            "endTime": 1440
                        }
                    ],
                    "friday": [
                        {
                            "startTime": 900,
                            "endTime": 1440
                        }
                    ],
                    "saturday": [
                        {
                            "startTime": 900,
                            "endTime": 1440
                        }
                    ],
                    "sunday": [
                        {
                            "startTime": 900,
                            "endTime": 1440
                        }
                    ]
                },
                "timeProgramCirculationPump": {
                    "metaInfo": {
                        "minSlotsPerDay": 0,
                        "maxSlotsPerDay": 3,
                        "setpointRequiredPerSlot": false
                    },
                    "monday": [
                        {
                            "startTime": 0,
                            "endTime": 1440
                        }
                    ],
                    "tuesday": [
                        {
                            "startTime": 0,
                            "endTime": 1440
                        }
                    ],
                    "wednesday": [
                        {
                            "startTime": 0,
                            "endTime": 1440
                        }
                    ],
                    "thursday": [
                        {
                            "startTime": 0,
                            "endTime": 1440
                        }
                    ],
                    "friday": [
                        {
                            "startTime": 0,
                            "endTime": 1440
                        }
                    ],
                    "saturday": [
                        {
                            "startTime": 0,
                            "endTime": 1440
                        }
                    ],
                    "sunday": [
                        {
                            "startTime": 0,
                            "endTime": 1440
                        }
                    ]
                }
            }
        ],
        "ventilation": []
    }
}

2024-11-06 01:30:29.956 DEBUG (MainThread) [myPyllant.http_client] Starting GET to https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/emf/v2/XXXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX/currentSystem
2024-11-06 01:30:30.019 DEBUG (MainThread) [myPyllant.http_client] Got response for GET to https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/emf/v2/XXXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX/currentSystem: ...
2024-11-06 01:30:30.021 DEBUG (MainThread) [myPyllant.http_client] Starting GET to https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/api/v1/ambisense/facilities/XXXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX/capability
2024-11-06 01:30:30.101 DEBUG (MainThread) [myPyllant.http_client] Got response for GET to https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/api/v1/ambisense/facilities/XXXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX/capability: ...
2024-11-06 01:30:30.105 DEBUG (MainThread) [myPyllant.models] Creating related models from state: { ... 'heat_demand_limited_by_outside_temperature': 20.0, ... }
2024-11-06 01:30:30.122 DEBUG (MainThread) [custom_components.mypyllant.coordinator] Getting daily data for XXXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX from 2024-11-06 00:00:00+01:00 to 2024-11-07 00:00:00+01:00
...
2024-11-06 01:30:31.312 DEBUG (MainThread) [custom_components.mypyllant.coordinator] Finished fetching myVAILLANT data in 1.545 seconds (success: True)
2024-11-06 01:30:31.357 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up mypyllant.binary_sensor
2024-11-06 01:30:31.371 INFO (MainThread) [homeassistant.setup] Setting up calendar
...
2024-11-06 01:30:31.416 INFO (MainThread) [homeassistant.components.climate] Setting up mypyllant.climate
...
2024-11-06 01:30:31.485 INFO (MainThread) [homeassistant.setup] Setting up datetime
2024-11-06 01:30:31.486 INFO (MainThread) [homeassistant.setup] Setup of domain datetime took 0.00 seconds
2024-11-06 01:30:31.488 INFO (MainThread) [homeassistant.components.datetime] Setting up mypyllant.datetime
2024-11-06 01:30:31.490 INFO (MainThread) [homeassistant.components.number] Setting up mypyllant.number
2024-11-06 01:30:31.491 ERROR (MainThread) [homeassistant.components.number] Error adding entity number.myvaillant_circuit_0_heat_demand_limited_by_outside_temperature for domain number with platform mypyllant
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 595, in _async_add_entities
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 909, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1366, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1005, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state
    self.__async_calculate_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1067, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1011, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/number/__init__.py", line 359, in state
    return self.value
           ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/number/__init__.py", line 398, in value
    if (native_value := self.native_value) is None:
                        ^^^^^^^^^^^^^^^^^
  File "/config/custom_components/mypyllant/number.py", line 232, in native_value
    return self.circuit.heat_demand_limited_by_outside_temperature
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Circuit' object has no attribute 'heat_demand_limited_by_outside_temperature'

2024-11-06 01:30:31.495 INFO (MainThread) [homeassistant.components.sensor] Setting up mypyllant.sensor
2024-11-06 01:30:31.495 DEBUG (MainThread) [custom_components.mypyllant.sensor] Creating system sensors for [ ... 'heat_demand_limited_by_outside_temperature': 20.0, ... ]
2024-11-06 01:30:31.498 DEBUG (MainThread) [custom_components.mypyllant.sensor] Creating SystemDevice sensors for Device(...)
2024-11-06 01:30:31.499 DEBUG (MainThread) [custom_components.mypyllant.sensor] Creating SystemDevice sensors for Device(...)
2024-11-06 01:30:31.499 DEBUG (MainThread) [custom_components.mypyllant.sensor] Creating SystemDevice sensors for Device(...)
2024-11-06 01:30:31.499 DEBUG (MainThread) [custom_components.mypyllant.sensor] Creating Zone sensors for Zone( ... 'heat_demand_limited_by_outside_temperature': 20.0, ... )
2024-11-06 01:30:31.500 DEBUG (MainThread) [custom_components.mypyllant.sensor] Creating Circuit sensors for Circuit( ... 'heat_demand_limited_by_outside_temperature': 20.0, ... )
2024-11-06 01:30:31.501 DEBUG (MainThread) [custom_components.mypyllant.sensor] Creating Domestic Hot Water sensors for DomesticHotWater(...)
2024-11-06 01:30:31.502 ERROR (MainThread) [homeassistant.components.sensor] Error adding entity sensor.vaillant_api_request_count for domain sensor with platform mypyllant
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 595, in _async_add_entities
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 909, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1366, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1005, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state
    self.__async_calculate_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1067, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1011, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 542, in state
    value = self.native_value
            ^^^^^^^^^^^^^^^^^
  File "/config/custom_components/mypyllant/sensor.py", line 1121, in native_value
    return self.coordinator.api.aiohttp_session.request_count
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'ClientSession' object has no attribute 'request_count'. Did you mean: '_request_class'?

It seems your installation is broken, because in the latest verison of the integration the underlying library definitely has the heat_demand_limited_by_outside_temperature attribute. Could you try reinstalling? If that doesn't help, there should be a debug log after startup that prints out the versions of the intergation, its library, and some of the core 3rd party libraries being used. Searching for "version" should hopefully be enough. Please post that!


Finalize all corrections to the thesis and submit to the graduate college. Also update the arXiv.

Just waiting for the graduate college to sign off. Then I can upload the final version to arXiv as a revision.


Always starts activated

Here is my configuration:
<style name="SVProgressBar" parent="SmoothProgressBar">         <item name="spb_stroke_separator_length">12dp</item>         <item name="spb_sections_count">2</item>         <item name="spb_speed">1.2</item>         <item name="spb_colors">@array/progressColors</item>         <item name="spb_progressiveStart_speed">2</item>         <item name="spb_progressiveStop_speed">4.4</item>         <item name="spb_interpolator">spb_interpolator_acceleratedecelerate</item>         <item name="spb_progressiveStart_activated">false</item>     </style>
<fr.castorflex.android.smoothprogressbar.SmoothProgressBar         android:id="@+id/progressBar"         android:layout_width="match_parent"         android:layout_height="wrap_content"         android:indeterminate="true"         app:layout_anchor="@+id/content_search" />
it always starts activated.
Device: android 7.1 emulator

I second this.

Hello,
I don't really get what the issue is. Is it that the indeterminate progress always shows up? Or is it that the progressiveStart is always enabled?

Hey man.
Yes. I think it makes more sense for the indeterminate progress bar to be started explicitly.

Same problem when activity comes in foreground 1st time SmoothProgressBar is activated+visible hence i explicitly set it to progressiveStop in onCreate which results in ProgressiveStop is visible until progressiveStop ends on activity coming in foreground

#35


cancel_batch_order Parameter logic encoding error

Revise：
def cancel_batch_order(self, symbol: str, orderIdList: list= None, origClientOrderIdList: list= None, **kwargs):
elif (orderIdList is not None):
run error：{"code":-1130,"msg":"Data sent for parameter 'orderIdList' is not valid."}

@1163849662 thanks for raising the issue, we have fixed it, please pull the latest version, thanks!

Hello, this does not seem to be fixed in 3.1.1:
[2022-06-02 08:44:58,565: DEBUG/ForkPoolWorker-8] https://testnet.binancefuture.com:443 "DELETE //fapi/v1/batchOrders?symbol=BTCUSDT&origClientOrderIdList=61cb41a6-a0b9-43d1-93d1-2a9050ae61cd&origClientOrderIdList=94e24acf-c3ba-4045-b359-1c9d3b7d75fd&origClientOrderIdList=dbd364ff-cf33-43a1-be48-1155c536e2f0&timestamp=1654159497710&signature=XXX HTTP/1.1" 400 84

origClientOrderIdList is not encoded as a list.

yes. I am facing the same issue


perf(reactivity): avoid unnecessary recursion in removeSub

I stumbled across an edge case where the performance of computed can go awry:

Playground - 3.5.11

The time taken grows exponentially with the value of LAYERS. I used 22 in the example, but you may need to tweak it depending on your hardware.
The problem is with cleaning up the subs. removeSub() calls itself recursively if dep.subs is undefined. But in this example, deps.subs is always undefined for all deps, so it ends up calling removeSub() a huge number of times. The same links are being removed over and over.
I've attempted to fix it by additionally checking that deps.subs wasn't already undefined.
The diff makes the change look more complicated than it actually is. I've moved the if (dep.subs === link) { part further down and wrapped it around the clean-up section.

Playground - this PR

/ecosystem-ci run

/ecosystem-ci run quasar


How to split the "\n" newline character and save the sentences separately?

"PersistRichTextMode=Fragment"
It is known that text can be split to make it easier to match.
Example
｛
Attack!<color=#00000000>=Attack!<color=#00000000>
<color=#a71edf>Expert Offers=<color=#a71edf>Expert Offers
Movement Speed: <color=#4BBE42>+18=移动速度: <color=#4BBE42>+18
｝
Effect
｛
Attack!=Attack!
Expert=Expert
Offers=Offers
Movement Speed:=Movement Speed:
{{A}}={{A}}
｝
May I ask if a similar split operation can be performed on the \n newline character?
Example
｛
Unlock Condition: 25 With a single blow\n\nUnlock a Sign: The Sign of The Tornado=Unlock Condition: 25 With a single
blow\n\nUnlock a Sign: The Sign of The Tornado
Unlock Condition: Win an attempt at 5 Difficulty\n\nYou acquire a Defender's shield.=Unlock Condition: Win an attempt at 5
Difficulty\n\nYou acquire a Defender's shield.
｝
Expected Result
｛
Unlock Condition: 25 With a single blow=Unlock Condition: 25 With a single blow
nUnlock a Sign: The Sign of The Tornado=nUnlock a Sign: The Sign of The Tornado
Unlock Condition: Win an attempt at 5 Difficulty=Unlock Condition: Win an attempt at 5 Difficulty
You acquire a Defender's shield.=You acquire a Defender's shield.
｝
Because the text obtained by unpacking the "resources.assets" file lacks newline symbols such as \n, it cannot match the text automatically generated by "XUnity.AutoTranslator."
(My English is not very good; this is the text I translated using ChatGPT. I hope it doesn't affect readability.)

sr:"^([\s\S]+)(\\n)+([\s\S]+)$"=$1$2$3
This will split any string with \n in the middle in two and translate them separately
You can test regular expressions here


JDK 1.8.x  javax.net.ssl.SSLException: Received fatal alert: protocol_version

Starting after Github updated their certificates I started to receive the below error message. Which is very similar to #634.  With one exception, I'm running Java 1.8 which should default to TLS 1.2
I've found that restarting my jenkins instance resolves the issue. However it will start up again after some time. Restart always seems to resolve it, but that isn't the ideal solution ;)
This is happening on two of my Jenkins environments each running different jenkins versions. (2.89.2 and 2.21). One is also running on linux, the other on osx.
I'm not sure if the issue is in this plugin or the underline github-api plugin. I do see this ticket:
https://github.com/kohsuke/github-api/issues/418

Mar 02, 2018 1:11:07 PM hudson.triggers.Trigger checkTriggers
WARNING: org.jenkinsci.plugins.ghprb.GhprbTrigger.run() failed for hudson.model.FreeStyleProject@4853e929[android-phoenix-qa-emulator]
java.lang.Error: org.kohsuke.github.HttpException: Server returned HTTP response code: -1, message: 'null' for URL: https://api.github.com/repos/nytm/android-phoenix/pulls?state=open
        at org.kohsuke.github.Requester$PagingIterator.fetch(Requester.java:516)
        at org.kohsuke.github.Requester$PagingIterator.hasNext(Requester.java:481)
        at org.kohsuke.github.PagedIterator.fetch(PagedIterator.java:44)
        at org.kohsuke.github.PagedIterator.hasNext(PagedIterator.java:32)
        at org.kohsuke.github.PagedIterable.asList(PagedIterable.java:41)
        at org.kohsuke.github.GHRepository.getPullRequests(GHRepository.java:697)
        at org.jenkinsci.plugins.ghprb.GhprbRepository.check(GhprbRepository.java:138)
        at org.jenkinsci.plugins.ghprb.GhprbTrigger.run(GhprbTrigger.java:294)
        at hudson.triggers.Trigger.checkTriggers(Trigger.java:278)
        at hudson.triggers.Trigger$Cron.doRun(Trigger.java:226)
        at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: org.kohsuke.github.HttpException: Server returned HTTP response code: -1, message: 'null' for URL: https://api.github.com/repos/nytm/android-phoenix/pulls?state=open
        at org.kohsuke.github.Requester.parse(Requester.java:633)
        at org.kohsuke.github.Requester.parse(Requester.java:594)
        at org.kohsuke.github.Requester.access$200(Requester.java:73)
        at org.kohsuke.github.Requester$PagingIterator.fetch(Requester.java:505)
        ... 17 more
Caused by: javax.net.ssl.SSLException: Received fatal alert: protocol_version
        at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
        at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)
        at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:2023)
        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1125)
        at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
        at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
        at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1512)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
        at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
        at org.kohsuke.github.Requester.parse(Requester.java:602)
        ... 20 more

Which java / jenkins / plugin versions are you running?

On one Jenkins server I am running:
Java: 1.8.0_60-b27
Jenkins:
ghprb plugin: 1.33.1
githup api plugin: 1.90
The other Jenkin's instance I don't have access to the managment console at the moment but I know it it is on Java 1.8.x and github api plugin 1.90. I'm assuming it is the latest ghprb plugin but will verify tomorrow.
I was going to try hardcoding the TLS version even though I'm on JDK 1.8 to see if that made any difference.

@cybo42, how'd it go?  We're seeing this issue as well in some instances.

Fingers crossed, but so far since I hardcoded the TLS version -Dhttps.protocols=TLSv1.2  I haven't seen the issue come up again.
It bothers me that I'd have to do that since JDK 1.8 should default to 1.2. But maybe something is causing it fallback. Maybe a persistent connection or something like that. (grasping at straws)

@cybo42
Can you please tell the detailed explanation stating where you actually changed the things.

This fixed it for us, but not sure why the plugin would not use TLS1.2 if that's the default.  The non-PR jobs were running fine.

Thanks so much @cybo42.
@dmewadamobi on linux I added this to my bash file: export JAVA_TOOL_OPTIONS="-Dhttps.protocols=TLSv1.2"
I'm not sure if there is a better place to put that though.

Issue seems to be resolved by using latest jdk version or harcoding tls version.

We've had the same issue. After our Nexus has been moved to TLS 1.2 the Jenkins was not able to connect to it. Restarting Jenkins solved the issue. Our Java Version is "1.8.0_101"


[MLIR] tf-opt can not run with -debug option

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):Linux Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:No
TensorFlow installed from (source or binary):source
TensorFlow version (use command below): 2.0.0
Python version:3.7
Bazel version (if compiling from source):1.0.1
GCC/Compiler version (if compiling from source):6.4.0
CUDA/cuDNN version: 10
GPU model and memory: V100

Describe the current behavior
in current tensorflow dialect (implemented in tensorflow/compiler/mlir)， we use LLVM_DEBUG in various place to print some debug information during compilation , and if we run tf-opt , it's expected to print these informations with -debug option added, this is also the behavior with mlir-opt, but in current master branch , if I pass a -debug option to tf-opt ,an error occured
#bazel-bin/tensorflow/compiler/mlir/tf-opt -debug
tf-opt: Unknown command line argument '-debug'.  Try: 'bazel-bin/tensorflow/compiler/mlir/tf-opt --help'
tf-opt: Did you mean '--help'?

but if I run mlir-opt with -debug:
#bin/mlir-opt -debug
Args: bin/mlir-opt -debug

I've also compared the main function between tf-opt(https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/mlir/tf_mlir_opt_main.cc ) and mlir-opt  (https://github.com/tensorflow/mlir/blob/master/tools/mlir-opt/mlir-opt.cpp ) and see no apparent difference between the two files
Describe the expected behavior
tf-opt can run with -debug so I can use the debug info to debug the compilation process

In InitMlir we parse the flags with the two different command libraries in use: if no -- is on the line, then all are passed to LLVM's cl, if -- then the part before -- is passed to LLVM and those after to TF's flags. Try
tf-opt -debug --
Please reopen if this doesn't resolve it.


Support btrfs as /usr filesystem

postinstall: support btrfs as /usr filesystem
When btrfs is used to fit more content into the partition, mounting
fails because ext2/3 was hardcoded.
Also try to mount as btrfs if mounting as ext2/3 fails. The
norecovery options makes sure that the filesystem isn't touched even if
the it is corrupted.

utils: support btrfs
With btrfs it's not possible in general to find a single underlying
block device because there could be many, but still it is possible for
our case since we have a single partition. However, rootdev failed to
find it because it uses the device minor and major pair from a "stat"
syscall on the mount point. This doesn't work with btrfs because it
gives a logical pair instead of one belonging to a block device.
Instead of using the minor and major pair, find the underlying block
device of a mount point by looking it up in /proc/mounts. The existing
traversal code to find the lowest backing device is kept in place by
getting the minor and major pair for the found block device.
Based on the new code in seismograph's rootdev under src/rootdev/main.c from https://github.com/kinvolk/seismograph/pull/6

How to use/Testing done
This was built and tested with the coreos-overlay branch kai/bootengine-verity-hashoffset from https://github.com/kinvolk/coreos-overlay/pull/1106 and flatcar-scripts branch kai/btrfs-usr-oem from https://github.com/kinvolk/flatcar-scripts/pull/131 in http://jenkins.infra.kinvolk.io:8080/job/os/job/manifest/3029/cldsv/ where the Flatcar image that has a btrfs /usr partition and OEM partition.
While the actual switch to a btrfs filesystem on the /usr partition is only possible when all changes are part of a Stable release because update-engine needs to know how to handle the new filesystem when updating, we can already do the switch for the OEM partition.

(CI fails until https://github.com/kinvolk/seismograph/pull/6 is merged)

(CI fails until kinvolk/seismograph#6 is merged)

CI will fail anyway - see: https://github.com/kinvolk/Flatcar/issues/282#issuecomment-849414267 :)

Hm, I need to find why update-engine still doesn't find the right partition ( utils.cc:420] rootdev found a device name with no device node)

Testing locally didn't run into that message but into the problem that conceptually two identical filesystems can't be mounted at the same time, this prevents testing to update from the same version because update-engine has to mount the new partition to copy the kernel over to /boot. Updating to the same image is a no-op and one could add a workaround to use ' /usr'  directly instead.

This change doesn't affect the dm-verity r/o aspect?

The temporary mounting to copy the new kernel over to the boot partition is done without setting up dm-verity


Card component

As said in the previous PR, I took a new approach to create this component.
ATM, card is just about styles! No need to have several components. It's more easier to use like that. If someday we need to add some behavior like "Ripple" I already created the individual component.
What we need to do is to plug CardStyles to MKTheme but I think it's a work to do on the all lib not only on the Card component. Right?
Feedbacks are welcome :)

card is just about styles

Couldn't agree more. And also about the theme thing, there should be a global theme which affects all the components, like MDL does, but let's worry about it later, after most of the functionalities are done.


Attempt codesign .framework
codesign --force --sign "Developer ID Application: Comp (TeamID)" --timestamp --options runtime /path/Vault_mobile.xcframework/macos-arm64_x86_64/Vault_mobile.framework

What did you see happen?

Result of code signing framework: unsealed contents present in the root directory of an embedded framework
Context: shipping macos app for direct distribution fails to pass any binary/framework that isn't codesigned. The notarytool cli from xcode produces the following (regardless of if the xcframework is signed or not:

### Package Issues
###
Status: Invalid
Archive contains critical validation errors
[[ Safe ]]
• MyApp.app/Contents/MacOS/MyApp
• [ERROR] The signature of the binary is invalid.
• [ERROR] The signature of the binary is invalid.

What did you expect to see?
Expected contents to be sealed in the root directory of an embedded framework.
I realize this might be just an XCode issue, but considering the posts I've read about info.plists and bundling problems with the lastest XCode I figured I'd give it a shot. Any insights appreciated.

@hyangah, any clues?

Sorry I have no clue. Does codesign ... --verbose give more hints any chance?
It's possible that the framework bundle doesn't meet recent codesign's expected layout.

@hyangah

Sorry I have no clue. Does codesign ... --verbose give more hints any chance? It's possible that the framework bundle doesn't meet recent codesign's expected layout.

Not much that tells me anything. But maybe you it'll inform you. I'm using -vvv for verbosity:
codesign -vvv --deep --strict /MyApp.app
--prepared:/MyApp.app/Contents/Frameworks/Vault_mobile.framework/Versions/Current/.
/Volumes/CLIENT_APPS/client/tokenx/codesign-vault-only TEST/codesign-vault-only 2024-03-19 14-21-12/codesign-vault-only.app: unsealed contents present in the root directory of an embedded framework
In subcomponent: /MyApp.app/Contents/Frameworks/Vault_mobile.framework

XCFramework file tree, for ref:
Vault_mobile.xcframework
├── Info.plist
├── ios-arm64
│   └── Vault_mobile.framework
│       ├── Headers -> Versions/Current/Headers
│       ├── Info.plist
│       ├── Modules -> Versions/Current/Modules
│       ├── Resources -> Versions/Current/Resources
│       ├── Vault_mobile -> Versions/Current/Vault_mobile
│       └── Versions
│           ├── A
│           │   ├── Headers
│           │   │   ├── Universe.objc.h
│           │   │   ├── Vault_mobile.h
│           │   │   ├── Vault_mobile.objc.h
│           │   │   └── ref.h
│           │   ├── Modules
│           │   │   └── module.modulemap
│           │   ├── Resources
│           │   │   └── Info.plist
│           │   └── Vault_mobile
│           └── Current -> A
├── ios-arm64_x86_64-simulator
│   └── Vault_mobile.framework
│       ├── Headers -> Versions/Current/Headers
│       ├── Info.plist
│       ├── Modules -> Versions/Current/Modules
│       ├── Resources -> Versions/Current/Resources
│       ├── Vault_mobile -> Versions/Current/Vault_mobile
│       └── Versions
│           ├── A
│           │   ├── Headers
│           │   │   ├── Universe.objc.h
│           │   │   ├── Vault_mobile.h
│           │   │   ├── Vault_mobile.objc.h
│           │   │   └── ref.h
│           │   ├── Modules
│           │   │   └── module.modulemap
│           │   ├── Resources
│           │   │   └── Info.plist
│           │   └── Vault_mobile
│           └── Current -> A
└── macos-arm64_x86_64
    └── Vault_mobile.framework
        ├── Headers -> Versions/Current/Headers
        ├── Info.plist
        ├── Modules -> Versions/Current/Modules
        ├── Resources -> Versions/Current/Resources
        ├── Vault_mobile -> Versions/Current/Vault_mobile
        └── Versions
            ├── A
            │   ├── Headers
            │   │   ├── Universe.objc.h
            │   │   ├── Vault_mobile.h
            │   │   ├── Vault_mobile.objc.h
            │   │   └── ref.h
            │   ├── Modules
            │   │   └── module.modulemap
            │   ├── Resources
            │   │   └── Info.plist
            │   └── Vault_mobile
            └── Current -> A

34 directories, 28 files

@ianmcfall @hyangah @dr2chase I guess the issue is due to Info.plist under macos-arm64_x86_64/Vault_mobile.framework/, as Apple has pointed out that The framework’s root must contain only the Versions directory and symlinks. Don’t place any other content there. Doing so causes code-signing problems.
Pleases refer: https://developer.apple.com/documentation/bundleresources/placing_content_in_a_bundle

@ianmcfall iOS requires an Info.plist located under framework root when running on Xcode 15.3 and above. So the best solution would be create an alias of Info.plist under framework root from Info.plist under {$framework root}/Resources/, which will work for both iOS and Mac OS.

My fix for another issues seems to fix this as well: https://go-review.googlesource.com/c/mobile/+/574055
I can repo a code signing issue before, but not after. Different error message though.
@ianmcfall want to verify?

Thanks for the help, everyone. Closing.

My fix for another issues seems to fix this as well: https://go-review.googlesource.com/c/mobile/+/574055
I can repo a code signing issue before, but not after. Different error message though.
@ianmcfall want to verify?
@Simon-Zeng the suggested symlink will fix this issue, but will cause other issues. Good call on cause!

Apologies @scosman, not sure how I can help to verify that update.

@ianmcfall Steps would be:

sync git@github.com:scosman/gomobile.git
cd cmd/gomobile
go build
The run the produced gomobile binary in cmd/gomobile to bind your library, and check it all works

...and check it all works

@scosman I just confirmed your git@github.com:scosman/gomobile.git passes the codesign checks successfully for a macOS app.


nav-item dropdown stretching navbar on smaller screens

Not sure if this an issue, feature request or something I am missing.
I want a fairly simple navbar with the main menu items to the left in a .navbar-collapse, but on the right a separate .nav-item dropdown that is always visible (it will hold a login/logout form).
On larger screens it works fine, but once the collapse has kicked in, although the trigger still displays fine, the dropdown pushes the whole navbar down. I want it to work exactly the same as it does on larger screens.
It seems a fairly common thing that people may want to utilise and googling did turn up a few instances of the same or similar question, but the best solution I saw was a hugely complicated structure and a host of extra css.  I do not think it is browser specific but have tried it in Chrome 64 and FF 54 with the same results.
jsfiddle

What you are trying to do can be easily achieved with bs4. The problem lies in your markup.
Please see this fiddle for a working -but not perfect- example.

Thanks @bakedbird
It wan't quite there as the right trigger was dropping but a bit of tweaking has got it nearly there as per this Fiddle, albeit I think it hacky as I simply moved the right trigger to before the nav button in the code. The only thing is it appears dropdown-menu-right is not working but that may work locally as I can see no reason it wouldn't.

Right-aligned dropdown menus appear to work as intended in the latest release. Sorry for getting to this so late, but I think it's safe to close out.


Adding E2E for webhook/nic

Description
This change adds:

E2E test for the validation/mutation webhook, as well as
E2E tests for internal lb annotations on the NIC
Moving the DefaultNicReconciler to use control loop

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. Is it a breaking change which will impact consuming tool(s)?

[x] All E2E Tests

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 25 (40.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 76.673%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/controller/nginxingress/default.go
10
25
40.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
2784

Relevant Lines:
3631

💛  - Coveralls


Is there a license file for this package?

I was looking for a LICENSE file, but maybe I missed something?

Send a PR.
By the way, see https://github.com/zendframework/ZendXml/blob/1c8d4b424824d605b203a33729bbb3a3f7c4616b/composer.json#L5

@Ocramius I've converted this issue to a PR, and attached the license file.

Merged, thanks!
master: zendframework/ZendXml@3dcfc87ccd6378360d987d7f467a086c5d598c2c
develop: zendframework/ZendXml@12f30b2584f5ba2917ef2f07063e1a9a66a1572f

Cool, Thanks!


Tried on 2 devices with LineageOS 18 and 19 not working. (android 11 and 12)

The app asks for root permission after it crashes.

Got the code from: /data/data/com.august.luna/shared_prefs/PeripheralInfoCache.xml


Testing 1

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
What are the significant changes in functionality due to this change request?

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual.
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Regression tests have to complete successfully.
[ ] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test.
[ ] 6. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.

git revert will make sure that a new commit is created to revert the effects of that unwanted merge. This is in contrast to git reset, where we effectively "remove" a commit from the history. That's also the reason why git revert is a better solution in cases where you've already pushed to a remote.
The -m 1 option tells Git that we want to keep the parent side of the merge (which is the branch we had merged into).
Finally, also make sure to provide the correct commit hash: for the git reset example above, we had to provide the commit before the merge; when using git revert, however, we have to specify the actual merge commit's hash.

I think this can be closed.


Remove FromPlutusType / ToPlutusType, Improve organisation of conversion modules

Closes: https://github.com/Plutonomicon/cardano-transaction-lib/issues/452

@errfrom After fixing the merge conflicts, could you also add a line to the changelog under ## [Unreleased] (using the heading ### Removed)` please?


training loss = nan on custom dataset

A slice training process is like the following:
Iter 496 training loss = 65.174 , time = 2.39
epoch 41 total training loss = nan
Iter 497 training loss = 124.104 , time = 2.38
epoch 41 total training loss = nan
Iter 498 training loss = 143.243 , time = 2.34
epoch 41 total training loss = nan
Iter 499 training loss = 102.472 , time = 2.36
epoch 41 total training loss = nan
Iter 500 training loss = 54.147 , time = 2.34
epoch 41 total training loss = nan
Iter 501 training loss = 76.837 , time = 2.38
epoch 41 total training loss = nan
Iter 502 training loss = 67.174 , time = 2.36
epoch 41 total training loss = nan
Iter 503 training loss = 58.369 , time = 2.31
epoch 41 total training loss = nan
Iter 504 training loss = 76.735 , time = 2.37
epoch 41 total training loss = nan
Iter 505 training loss = 150.376 , time = 2.33
epoch 41 total training loss = nan
Iter 506 training loss = 76.206 , time = 2.27
epoch 41 total training loss = nan
Iter 0 3-px error in val = 94.037
Why? Could you give some advise?

@JiaRenChang hi, I use the Apollo depth dataset to train the model, the learning rate is calculated by the following formular 'lr = 0.01 * 0.1 ** (epoch // 30)'.   Recently, I found the apollo depth dataset didn't    do the work of Epipolar Geometry between the left image and right image, I think it's the main reason for the appearing of nan.  Is that right?

@passion3394
Yes, I thought about it too.
It seems that there are only background depth maps in the Apollo dataset.

@JiaRenChang Hi, If we use the depth map of only background to train, and try to apply the trained model to the images with movable objects, the precision would be terrible?

@passion3394
(1) I think that the precision will be pretty bad because the movable objects usually have large disparities. But the background depth maps usually have small disparities.
The strong imbalance may cause the problem of generalization.
(2) and (3)  We actually tried testing PSMNet on the "real world (required by web cameras, weak camera calibration, and outdoor)" image pairs. We still can achieve pretty good results.

@passion3394 @JiaRenChang
hello, I have also used apollo depth dataset to train, but I will get an error
"IndexError: too many indices for tensor of dimension 3"
can you help me
thank you very much!

@hnsywangxin sorry, may be more error info?

@passion3394 thank you for your replay,my error like this:
Traceback (most recent call last):   File "finetune.py", line 266, in <module>     main()   File "finetune.py", line 231, in main     loss = train(imgL_crop,imgR_crop, disp_crop_L)   File "finetune.py", line 169, in train     loss = 0.5*F.smooth_l1_loss(output1[mask], disp_true[mask], size_average=True) + 0.7*F.smooth_l1_loss(output2[mask], disp_true[mask], size_average=True) + F.smooth_l1_loss(output3[mask], disp_true[mask], size_average=True)  IndexError: too many indices for tensor of dimension 3
my input is depth map of apollo dataset,my batch_size =4,other parameter was as the same as original program

@passion3394 thank you for your replay,my error like this:
Traceback (most recent call last):
File "finetune.py", line 266, in <module>
main()
File "finetune.py", line 231, in main
 loss = train(imgL_crop,imgR_crop, disp_crop_L)
File "finetune.py", line 169, in train
loss = 0.5*F.smooth_l1_loss(output1[mask], disp_true[mask], size_average=True) + 0.7*F.smooth_l1_loss(output2[mask], disp_true[mask], size_average=True) + F.smooth_l1_loss(output3[mask], disp_true[mask], size_average=True)
IndexError: too many indices for tensor of dimension 3
my input is depth map of apollo dataset,my batch_size =4,other parameter was the same as original program

hi, hnsywangxin, have you find the solution? I have the same error


Geocoding deferRequestBy a bit low

I noticed that we curently use 'deferRequestBy: 5`. The value is given in ms ["Number of miliseconds to defer Ajax request"]. 5 ms seemse pretty low, maybe a value like 200-500 ms would be more appropriate to reduce the usage of the API key?

Yes, good idea. 200ms should be completely fine.
It looks there is also some duplication of the libraries (?)
https://github.com/graphhopper/graphhopper/search?q=deferRequestBy&unscoped_q=deferRequestBy


Remove redis dependency

The examples pollute the go.mod file a bit. If we keep adding examples, the go.mod file will bloat further.
suggest name: hollywood-examples.

We should keep the examples in the main repo. Examples that have other dependencies, like Redis, should have a go mod file?

The Go binaries won't include these examples during compilation. Having easily available examples may help adoption.

@anthdm Having a go.mod file isn't great. We had that on one example (mdns). The problem is that it locks on to a specific version of Hollywood. Less of a problem if we stop changeing master as much as we've done lately.
If this was an application I'd be less concerned about the size of the go.mod, but as it's a framework, it'll be pulled into many, many applications (at least that is the goal).
There are currently two examples that add things to the go.mod-file:

Redis.

I think I can change this just to use file IO and kick the dependency that way. The semantics will be the same, will probably improve the value of the example as you wouldn't need Redis to run the thing.

mdns, adds dep on zeroconf. This example is really quite cool and might actually be something we wanna have inside hollywood. Having a cluster autoconfigure itself by multicast DNS rather than be finding an existing node is really useful.

@perbu Agreed here. So I will update the "Persistance middleware example" to use something more simple (inmem). Like you mentioned the semantics will be the same.
Regarding zeroconf, that is something that will be available inside the cluster once that update is merged.

Ok. I've re-scoped the issue to reflect the discussion. I can do the work so I've assigned myself to the issue.
The zeroconf depency will likely stay as @anthdm seem to like the idea of using it for service discovery.


Ensure let blocks are evaluated only once per example

This resolves #433.

Instead of holding a direct reference to its block, KWLetNode now turns it into a future (using https://github.com/mikeash/MAFuture).

When a node is evaluated, its pointer and all its children's pointers are assigned a reference to the future. The important difference here is that the block still hasn't been evaluated. Because it's now a future, the block isn't evaluated until the first time the future object is messaged, at which point the block is invoked and the message send is proxied to the real object.
That is, we now have real lazy evaluation, just like RSpec! Yay! 🎉

The let node tree is now unlinked, and the values reset, at the end of each example (rather than after the last example in a context, which was incorrect).

I'm still not 100% certain that this was the only solution. But figuring out the correct order in which to evaluate let nodes, in order to "simulate" lazy evaluation, was a big headache. Introducing futures made this problem go away by decoupling let node tree evaluation (assigning object references to let helper variables) from actual let block evaluation. So when the tree is evaluated we can just

without worrying about side effects. And then when a future is actually used the block is lazily evaluated as needed.
Hope that makes sense! 😅
And here's the functional test that verifies the behaviour: https://github.com/sharplet/Kiwi/blob/let-futures/Tests/KWFunctionalTests.m#L207-226.

If everyone's happy to go ahead with this, the question of the best way to import a third-party dependency still remains. I've just copied the source code from MAFuture HEAD into the tree for now, for testing. For CocoaPods, I've exported the code as a subspec. Would a git submodule be better for bringing in the source? Additionally, it's also bringing in a significant chunk of code that's still MRC, which doesn't make me super happy given the awesome progress recently on converting to ARC!

This looks like an interesting experiment, and I've just discussed this with @sharplet and @modocache and the complexity it adds probably isn't worth it. So, as it's been inactive for over two years, I'm closing this.
As ever - this PR can be re-opened if the idea is worth bringing back up, but it looks like discussion has petered out.


replace and replaceAll should allow op2 to be white-space

I came across this template when I had a simple need -
I needed to convert all the spaces in a variable to _.
When I try to use replace or replaceAll,
if I put   (a single space) as op2 - I get an error saying:
The value must not be empty.

you could try to change the template and get rid of the validation rule there, but I expect the editor to "auto trim" the value to be empty again. Additionally, it seems to kill the server if you try to use the template in that way and I guess this happens due to an error when the API sandbox executes the replace function with a value that gets "sanitized" to an empty string.
However, there seems to be no way of configuring a working parameter field for whitespace input like that. I can try to enhance the template to use regex here without making it even more complex to use but this will take a while.
In the meantime you can create and use a simple template for this specific task.

add a new variable template and enter a name
add a text input field on the "Fields" tab and call it "textInput" (or keep the name "text1" and adjust the code line below)
on the "Code" tab, enter the following code line: return data.textInput.split(" ").join("_");
save the template and use this to create a variable that converts all spaces from the input value to underscores.

hope that helps

Wow, thanks @mbaersch !
I didn't expect such elaborate response...
I've since found a workaround for my need, because usually I don't get responses for Issues I open.
I think a replaceRegex is the best option here.
Perhaps replaceSpace is also a good option.
I might try and open a pull-request for this, I don't promise.
Thank you very much for your support!

yes, please: contribute whenever you find the time and motivation 😉

closed for now


env for pipeline name

Clear and concise description of the problem
When I send notify, I want to include the pipeline name, e.g. the miniapp & app-server for below build

Suggested solution
how about CI_PIPELINE_NAME
Alternative
No response
Additional context
No response
Validations

[X] Checked that the feature isn't part of the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Nice idea. Would name it CI_WORKFLOW_NAME and also add CI_STEP_NAME for the step name.


adding component label on pod

Signed-off-by: Rahul Varghese<EMAIL_ADDRESS>What this PR does / why we need it:
Adding component label as server in the deployments.yaml. Having a component label is fairly common practice is helm charts.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[ ] Variables are documented in the README.md

@ruehowl please rebase your branch and fix the conflict.

@ruehowl please rebase your branch and fix the conflict.
Good to go now. 👍
the component is useful when you have other deployments or stateful set together in the same chart, like a front-end database ... looks like here is not the case

That is correct. The use case here is when it comes to metrics discovery and especially Prometheus setup.  Optional labels like component are commonly used for Job labeling and discovering metrics for services by Prometheus. Since chaoskube does not need/have a service object, having the component label will help set up Prometheus metrics for pods and treat it similar as a service.
i.e, we can rewrite the value label __meta_kubernetes_service_name with -.
The fact that chaoskube does not have a service endpoint make it difficult to accommodate it with a service metrics monitoring system. It seems having a component label can avoid this gap by making some mapping in Prometheus configuration and effectively treat the metrics coming out of chaoskube similar to the metrics form any service endpoints.

/lgtm


Use managed identity from container group?

I would like to deploy a container group using the yaml configuration from a github action (or any CD pipeline) but it seems to require hard coding the registry credentials. I was hoping by assigning a userassigned managed identity to the container group, and granting AcrPull access to that identity, the container group could pull the images, but this doesn't seem to be the case. Should that be supported? Or is there an alternate recommendation?

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

ID: 9d1bf6a2-95e7-4b50-e03e-9bf212dc5214
Version Independent ID: 79ee1b51-6a22-0a57-2a28-7eb5a65c9778
Content: Authenticate with managed identity - Azure Container Registry
Content Source: articles/container-registry/container-registry-authentication-managed-identity.md
Service: container-registry
GitHub Login: @dlepow
Microsoft Alias: danlep

@turing-complet managed identities works well with ACI.
https://docs.microsoft.com/en-us/azure/container-instances/container-instances-managed-identity
Pease go through this document to setup managed identities with ACI.
This is the yaml reference for ACI.
https://docs.microsoft.com/bs-latn-ba/azure/container-instances/container-instances-reference-yaml
this had identity as the key. We need to set identities there.  Please try this and let me know

That document shows how to access keyvault using a managed identity, it doesn't say anything about container registry access. I have already tried this and get the following error:
'BadRequest':'InaccessibleImage':'The image 'myregistry.azurecr.io/myImage:latest' in container group 'myContainerGroup' is not accessible. Please check the image and registry credential.'

Just to reiterate - the scenario I'm talking about is deploying to a multi-container group, in such a way that it can pull images from a container registry. I'm aware of two ways to do this:

hard code the registry admin credentials in the aci yaml file
use an ARM template and pass in the registry admin credentials

So I'm wondering if there is a way to use managed identity instead. This page describes a way to use a service principal for single containers, but I cannot see a way to do this for a container group.
Also, as it is the aci yaml is not useful for CI/CD scenarios using acr if it requires credentials and has no mechanism to parameterize or read from the environment.

That document shows how to access keyvault using a managed identity, it doesn't say anything about container registry access. I have already tried this and get the following error:

Nice. Did you added the acr pull role for the manged identity?
each identity has a service principal. you can exract the service principal using this command.
https://docs.microsoft.com/en-us/azure/container-instances/container-instances-managed-identity#create-an-identity
Then you need to assign scrpull role to that service principal with the scope to the target registry.
Then in yaml or CLi while creating the ACI, you need to specify the identity.
i think you are using YAML to create the ACI in the piepline.  If not, let me know the method which you are using

Thanks, yes I'm using a yaml file which has the following identity which is assigned AcrPull on the registry.
identity:
  type: UserAssigned
  userAssignedIdentities: {
    "/subscriptions/<guid>/resourceGroups/<rg>/providers/Microsoft.ManagedIdentity/userAssignedIdentities/<name>" : {}
  }

I grabbed the principalId for the managed identity, but don't see a way to assign that to the registry. Looking in the portal at the registry access control here:

When I choose the "Azure AD user, group, or principal" option it doesn't support the principalId (can't save even if I paste in the guid), however I was able to add the managed identity. Shouldn't that be the same thing? I would guess/hope that using a managed identity removes the need to deal with the underlying principal as well.

@turing-complet @jakaruna-MSFT - Apologies for jumping in late here. Unfortunately, a managed identity  enabled in a container group can't be used to pull an image from ACR to create a container. The identity is only available within a running container, not at create time. I have a documentation work item to update the ACI managed identity article with that information.
For your scenario, would the Resource Manager template and service principal credentials for registry access work out?

@dlepow thanks, that makes sense. I was thinking the managed identity would apply to the container group resource, as opposed to the containers themselves. The arm template solution is fine, still wish the yaml file deployment supported environment variables, but that's a different issue. Feel free to close this out.

@dlepow Thanks for the information.
Since you have a work item in place for doc enhancement, i will assign this issue to you.
Based on the work items status, plan to close this issue

Doc update published. Closing this issue.
#please-close

Is this still the case? I see the new version of the schema doc has identity option for imageRegistryCredentials but tried w/ an identify that has AcrPull role and got error attached. Is this now possible to do (and I'm just making mistake with the identity settings)?

https://docs.microsoft.com/en-us/azure/container-instances/container-instances-reference-yaml#schema

How about System Managed Identity, In docs, we can only find  service principal or user managed  Identity.
The problem is, It tries to start the container as soon as it creates  the container group.

I opened a new issue for this since this one is closed and people have changed https://github.com/MicrosoftDocs/azure-docs/issues/117644


Chart cache timeout is ignored when dataset cache is set

A clear and concise description of what the bug is.
Chart cache timeout is ignored, I only tested with dataset cache timeout set but looking at the code I think it will be ignored irrespetive of dataset cache timeout config.
How to reproduce the bug

start redis locally, and setup redis cache in config for data
create any chart on 1 dataset
set dataset cache timeout to 120 seconds
set chart cache timeout to 5 seconds (from properties modal).
open chart, and click on update chart
use redis cli, to check the expiry set on the cache key using ttl {cache_key} -> it will be 120 seconds.
after a minute backend still gives cached data, and we see cached a minute ago tag on top right corner.

Expected results
Chart cache timout should override dataset timeout setting, and return actual data from database after 5 seconds.
Actual results
Chart cache timout setting is ignored, and dataset cache timeout is used for checking existing cached data..
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
(please complete the following information):

browser type and version: chrome
superset version: latest master (last commit sha: 71bf2673071d5db6688fbaefd4457aeeae3464bb)
python version: python --version: 3.9
node.js version: node -v: 16
any feature flags active: No

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[ ] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

@mayurnewase Oh interesting. Apparently buildQuery isn't passing along the custom cache timouts from form data to the chart data request. I believe this needs to be fixed in @superset-ui/core. I can take a look, hoping it will be a simple fix.

ouch, so custom_cache_timeout was supposed to be used even by the frontend?
I thougth it was for overriding all other timeouts while using that api in other automations.
I already added 1 pr: https://github.com/apache/superset/pull/21637
will close it.
@villebro


Contextual Content API for Conversational Agents

Proposal: Contextual Content API for Conversational Agents

Summary

The contextual content API would allow the ConversationalAgent to have access to general information from the current foreground app(s). This may include visible images and text. Applications may optionally provide additional context to the conversational agent, so it can produce more intelligent output.
Rationale

This capability is present in other systems such as Android, Chrome OS, and (maybe) iOS; and would make bringing conversational agents to the Windows platform more compelling.
Future accessibility features could leverage the context provided for app information to enhance the functionality.
Conversational agents like Cortana and Alexa would be empowered to provide output relevant to the apps you're viewing.
This could leverage the existing Windows.Media.Ocr APIs to capture general data from foreground application(s)

This may not be on the roadmap for Project Reunion, which is completely fine, but the Conversation Agent APIs were added to WinRT with the latest stable Windows version (19041). This seems like a logical step forward to enhance their functionality.

Scope

Capability
Priority

Allow developers to capture general information from foreground app(s) for use in their conversational agents upon it being invoked
Must

Provide a way for end users to revoke access to this general information in Privacy Settings from conversational agents
Must

Easily empower developers to enhance conversational agent output by providing relevant context with the general information captured
Must

Provide a way for developers of conversational agents to check if their app is granted this capability.
Must

Facilitate exclusion of some/all general information by app developers
Could

Make changes to Cortana so it make use of this newly provided capability
Won't

Important Notes

This could introduce a new capability for packaged conversational agent apps: "contextualDataReceiver" .
Additionally, developers can enable their agent apps so users can easily invoke the conversational agent while, say, viewing a picture online. Saying "Add this to my document" will add the image to their open Word document. No more copying, pasting, and reformatting! The possibilities for users AND developers are endless here.
Open Questions

Should this functionality be limited to the default conversational agent only?
What format should the contextual information from app developers be provided in? (i.e., JSON, WinUI image/text property)
How can we encourage developers from both areas to make use of this technology?
How else can this technology be used for accessibility purposes?
Are there any form factors where granting this capability to conversational agents would NOT make sense?

In Windows, foreground means the single application which will receive keyboard or other non-locator input. This sounds like the more general idea of any app that has content visible on the screen, is that right?

Have there been any discussions with the clipboard #63 and drag and drop #70 teams?  There are a number of similarities to some of the scenarios this enables that might benefit from some commonality or integration.


Use DockerSuite for PullClientDisconnect test

Cleanup for #15646, sorry
Doesn't have meaningful significance for 1.8.2
@aaronlehmann @icecrime
Signed-off-by: Tonis Tiigi<EMAIL_ADDRESS>

LGTM


ENH: added Q_INVOKABLE to methods for python wrapping to work

Jc, please review and commit to slicer CTK

Thanks for your contirbution.
After addressing these two comment, it should be good to go.

OK, I removed extra Q_INVOKABLE. Could you integrate this into slicer?
Thanks,
Alex

Thanks. Will integrate this afternoon when I am back in the office.
On Fri, Feb 13, 2015 at 12:37 PM, ayarmarkovich<EMAIL_ADDRESS>wrote:

OK, I removed extra Q_INVOKABLE. Could you integrate this into slicer?
Thanks,
Alex
—
Reply to this email directly or view it on GitHub
https://github.com/commontk/CTK/pull/539#issuecomment-74293290.

--
+1<PHONE_NUMBER>

+1
This is exactly the kind of helpful exchange that makes the pull requests and the "social coding" model work so well.  Have a great weekend!

Integrated in 23971

Thanks for your contribution :+1:


Profile selection via Env

Goal
Allow configuring of emacs profiles via a environment variable.

/assign @BobyMCbobs

It appears that the default emacs profile comes from value inside ~/.emacs-profile.
A bash wrapper could be the first thing to be run, setting this based off of $HUMACS_EMACS_PROFILE.

This can actually be done in the container build stage.
A container pull FROM humacs/humacs and runs echo $PROFILE > /etc/skel/.emacs-profile


Get titles for requests to put in place of URL's

@markmacgillivray can you confirm when this is working?

It is working, I will update you at the meeting about getting them for old
data.
On Mon, Oct 10, 2016 at 1:28 PM, Joseph McArthur<EMAIL_ADDRESS>wrote:

@markmacgillivray https://github.com/markmacgillivray can you confirm
when this is working?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OAButton/backend/issues/259#issuecomment-252604525,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAuXCPRae80F3AR-zdw4u3_kJr4sPKrPks5qyi-FgaJpZM4KJwjo
.

Just tried it! Working nicely.


Search a 2D Matrix

Enter your question -
Write an efficient algorithm that searches for a value in an m x n matrix. This matrix has the following properties:
Integers in each row are sorted from left to right.
The first integer of each row is greater than the last integer of the previous row.
Enter link to the question(if question belongs to any online platform) -
https://leetcode.com/problems/search-a-2d-matrix/
Tags for the question(eg - Array, Basic, Stack, etc.) -
Array, Matrix, Binary search
@SarthakKeshari kindly assign this to me.

@niranjana687,
Kindly place your solution in "leetcode" folder.
Deadline - 03/10/2021


Failure to parse instructions with headers

The parser fails when groups of instructions are separate by headers. For example:
https://simplyhomecooked.com/air-fryer-chicken-tenders/#recipe
https://www.triedandtruerecipe.com/creamy-broccoli-pasta/

thanks for posting this. so sorry for the late reply.
hopefully have a fix shortly. keep you updated.

Fixed in 0.16.0. Thanks again for posting this.


Add search bar in docs

The problem faced currently?
How can we solve it?

If you want this feature to be implemented, give it a thumbs up reaction, so that we can determine which features are important to you.
👍

Implemented


Thread priority changes make app more easily to be stuck in production

Recently we upgraded our app to flutter 3, but received much more ANR reports from our customers than before, especially on iOS devices. From our analysis nearly 70% of them occurred right after our app becoming active from background, or switching to FlutterViewController from other view controllers, and the app usually became stuck at surfaceUpdated method in main thread.
Following is one of the stack trace samples from our reports:
Thread 0:
0   libsystem_kernel.dylib          __psynch_cvwait + 8
1   libsystem_pthread.dylib         _pthread_cond_wait$VARIANT$mp + 1180
2   libc++.1.dylib                  std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 24
3   Flutter                         fml::AutoResetWaitableEvent::Wait() (waitable_event.cc:74)
4   Flutter                         flutter::Shell::OnPlatformViewCreated(std::__1::unique_ptr<flutter::Surface, std::__1::default_delete<flutter::Surface> >) (shell.cc:827)
5   Flutter                         -[FlutterViewController surfaceUpdated:] (memory:2519)
6   our_app                         -[MTFlutterViewController surfaceUpdated:] (MTFlutterViewController.m:309)
7   libdispatch.dylib               _dispatch_call_block_and_release + 24
8   libdispatch.dylib               _dispatch_client_callout + 16
9   libdispatch.dylib               _dispatch_main_queue_callback_4CF$VARIANT$mp + 896
10  CoreFoundation                  __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
11  CoreFoundation                  __CFRunLoopRun + 2480
12  CoreFoundation                  CFRunLoopRunSpecific + 572
13  GraphicsServices                GSEventRunModal + 160
14  UIKitCore                       -[UIApplication _run] + 1052
15  UIKitCore                       UIApplicationMain + 164
16  our_app                         main (main.m:49)
17  libdyld.dylib                   start + 4

An interesting point is that when app get stuck, there is usually a thread doing some image decoding works, like this:
Thread 12:
0   libsystem_kernel.dylib          __psynch_mutexdrop + 8
1   libsystem_pthread.dylib         _pthread_mutex_firstfit_wake + 24
2   libsystem_pthread.dylib         _pthread_mutex_firstfit_unlock_slow$VARIANT$mp + 256
3   libc++.1.dylib                  std::__1::mutex::unlock() + 12
4   Flutter                         std::__1::__function::__func<fml::internal::CopyableLambda<flutter::ImageDecoder::Decode(fml::RefPtr<flutter::ImageDescriptor>, unsigned int, unsigned int, std::__1::function<void (flutter::SkiaGPUObject<SkImage>)> const&)::$_1::operator()()::'lambda'()>, std::__1::allocator<fml::internal::CopyableLambda<flutter::ImageDecoder::Decode(fml::RefPtr<flutter::ImageDescriptor>, unsigned int, unsigned int, std::__1::function<void (flutter::SkiaGPUObject<SkImage>)> const&)::$_1::operator()()::'lambda'()> >, void ()>::operator()() (functional:1838)
5   Flutter                         fml::MessageLoopImpl::FlushTasks(fml::FlushType) (ref_ptr.h:124)
6   Flutter                         fml::MessageLoopDarwin::OnTimerFire(__CFRunLoopTimer*, fml::MessageLoopDarwin*) (message_loop_darwin.mm:81)
7   CoreFoundation                  __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 28
8   CoreFoundation                  __CFRunLoopDoTimer + 1004
9   CoreFoundation                  __CFRunLoopDoTimers + 324
10  CoreFoundation                  __CFRunLoopRun + 1912
11  CoreFoundation                  CFRunLoopRunSpecific + 572
12  Flutter                         fml::MessageLoopDarwin::Run() (message_loop_darwin.mm:52)
13  Flutter                         void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, fml::Thread::Thread(std::__1::function<void (fml::Thread::ThreadConfig const&)> const&, fml::Thread::ThreadConfig const&)::$_0> >(void*) (message_loop_impl.cc:0)
14  libsystem_pthread.dylib         _pthread_start + 288

After digging a little deeper I believe the problem came from the thread priority changes introduced in https://github.com/flutter/engine/pull/30605.
According to https://github.com/flutter/engine/blob/44b86a87925124f96b33189c7e5f0fc8e823adfd/shell/common/shell.cc#L803-L826
OnPlatformViewCreated in platform thread must wait for all works to finish in IO thread, but if there are many images being queued for decoding, the app will be stuck for a long time since IO thread has the lowest priority specified in https://github.com/flutter/engine/pull/30605
Steps to Reproduce
Unfortunately I can not reproduce it locally. It just occurs in production, mostly on low-end devices.

Logs
[✓] Flutter (Channel stable, 3.0.4, on macOS 12.4 21F79 darwin-arm, locale zh-Hans-CN)
    • Flutter version 3.0.4 at /Users/yeatse/Developer/Repo/flutter/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 85684f9300 (9 days ago), 2022-06-30 13:22:47 -0700
    • Engine revision 6ba2af10bb
    • Dart version 2.17.5
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/yeatse/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /opt/homebrew/Cellar/openjdk/18.0.1/libexec/openjdk.jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment Homebrew (build 18.0.1+0)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Microsoft Edge.app/Contents/MacOS/Microsoft Edge

[!] Android Studio
    • Android Studio at /Users/yeatse/Applications/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] VS Code (version 1.68.1)
    • VS Code at /Users/yeatse/Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.44.0

[✓] Proxy Configuration
    • HTTP_PROXY is set
    • NO_PROXY is <IP_ADDRESS>,localhost,::1
    • NO_PROXY contains localhost
    • NO_PROXY contains <IP_ADDRESS>
    • NO_PROXY contains ::1

[✓] Connected device (3 available)
    • iPhone 13 Pro Max (mobile) • 01EC24DA-8AD5-4B00-AD76-5A308C04C440 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-5 (simulator)
    • macOS (desktop)            • macos                                • darwin-arm64   • macOS 12.4 21F79 darwin-arm
    • Chrome (web)               • chrome                               • web-javascript • Microsoft Edge 103.0.1264.51
    ! Error: CC’s iPhone 12 Pro is not connected. Xcode will continue when CC’s iPhone 12 Pro is connected. (code -13)

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Hi @Yeatse, Thanks for filing the issue.
The log seems to point at the thread that crashed. Do you have the complete crash log? Also is the crash affecting any specific set of devices?

Hi @Yeatse, Thanks for filing the issue.
The log seems to point at the thread that crashed. Do you have the complete crash log? Also is the crash affecting any specific set of devices?

It's not a crash.  It's just a stack trace collected by our monitoring tool when our app was not responding. This issue should be fixed after https://github.com/flutter/engine/pull/34568 is merged.

Closing as the related pr is merged to main branch.


How to train text-guided diffusion?

I don't think this repository supports text-to-image. You would need to add a text encoder component that injects information from your prompt into your backward diffusion process and use a contrastive loss to measure the similarity of the generated images with the respective prompts. I can refer you to this and this but I believe HuggingFace already provides a training facility for your desired task.

I see, thank you!


Duplicate route names with prefix_and_default strategy

Version
v5.3.0
Reproduction link
https://codesandbox.io/s/ql7wx2mvk6
Steps to reproduce

Configure nuxt-i18n module with these settings:

    [
      "nuxt-i18n",
      {
        locales: [
          { code: "pt", iso: "pt-PT", file: "pt.json" },
          { code: "us", iso: "en-US", file: "en.json" }
        ],
        langDir: "locales/",
        lazy: true,
        strategy: "prefix_and_default",
        defaultLocale: "us"
      }
    ]

Load the root path.
Look at the console (the server one, at the bottom of the codesandbox UI)

What is expected ?
No warnings about duplicated routes.
What is actually happening?
Getting console warnings:
[vue-router] Duplicate named routes definition: { name: "about___us", path: "/us/about" }
[vue-router] Duplicate named routes definition: { name: "index___us", path: "/us" }

Additional comments?
Appears to be due to using strategy: "prefix_and_default", setting which creates routes with duplicate names for default locale.

This bug report is available on Nuxt community (#c153)

Just ran into this as well and it's super annoying because it generates this console message for every single route in the app on every single page hit. With lots of routes this is huge amount of log spam.

For those that encounter this problem, you can fork the project as per the instructions in the README.md file for the project, then change line 94 in src/helpers/routes.js from routes.push({ ...localizedRoute, path }) to localizedRoute.alias = path in order to change the behavior from adding a duplicate route to simply creating an alias to the route.
Just be aware of that this will also make it so that using localePath for routing will result in users being redirected to e.g. /en/contact instead of /contact for the default language as well. /contact would be a valid and functioning route, it's just that localePath doesn't work as you might expect. I'm looking into this currently since the behavior I want is for people on /en/contact should be routed to /en/other/route, and /contact should be routed to /other/route.

Another alternative to the above solution is to use routes.push({ ...route, path }) instead of routes.push({ ...localizedRoute, path }). This will still create a new route for the default route (which you might want for e.g. SEO purposes) but its name will be set to the base name of the route. For example, a contact route is currently generated into e.g. contact___en, but with this change the default locales routes name would just be contact.
Note that localePath will still move you to e.g. /en/contact from /contact, I still need to find a solution to that.

Sorry, I added a strategy of prefix_and_default . (#111)
I think how to solve this problem.


[macOS] Update android commandlinetools for macOS 15

Description
The command line tools for android SDK were updated.
Related issue:
https://github.com/actions/runner-images/issues/10814
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

@Alexey-Ayupov @sarathrajsrinivasan Was that published to the microsoft hosted agent macOS-15 already? If not: Are you able to provide an ETA on that?

It seems that this is still an issue. My Maui pipelines were using macos-14 image with xcode 16 as required by the MAUI SDK. Now that XCode 16 has been removed ive changed the hosted image to macos-15 and my android build task is failing with
/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.Android.Sdk.Darwin/34.0.145/targets/Microsoft.Android.Sdk.Tooling.targets(31,5): error XA5205: Cannot find aapt. Please install the Android SDK Build-Tools package with the /Users/runner/Library/Android/sdk/tools/android program. [/Users/runner/work/1/s/App/App.csproj::TargetFramework=net8.0-android]


No longer works with DnD 5e 3.0 update

The big DnD 5e 3.0 update came out today and the custom skills didn't carry over. I tried removing and re-adding the module to no avail.
When I go to Configure Settings and click on Custom Abilities & Skills Configuration, the button does nothing - it doesn't open a new window or do anything. The box highlights orange and that's it.

I believe this is more of an issue with the fact the 3.0 update bricked something rather than specifically an issue with the module, as it was working perfectly before.

I know, what I didn't know is that the dnd5e was going to change that radically.
I'm sorry but the structure of the actors changed completely the module is not compatible right now with dnd3.0.0+.
This will need an update, I will probably make a different branch specifically for this version. I can't say how long will take.

looks like many modules won't work, on the officially reddit they suggest to stay on version 2+ for now until modules are updated.

I don't know if it's right to report it here, but it's also true that the form has been abandoned (if so, I apologize).
I solved it with TheRipper93's System Customizer.

I know, what I didn't know is that the dnd5e was going to change that radically. I'm sorry but the structure of the actors changed completely the module is not compatible right now with dnd3.0.0+.
This will need an update, I will probably make a different branch specifically for this version. I can't say how long will take.

Will the new branch be a separate mod or just update when completed for future versions?

the latest update should fix this


Enable Replace in Jupyter Notebooks

Find (Ctrl+F) works in a Jupyter Notebook, but Replace (Ctrl+H) does not. Replace is a critical tool when writing code. Could this be added to Jupyter Notebooks in VS Code? I realize there is the complication of the underlying JSON. Replace should work just on code cells, and not throughout the underlying JSON.

@abergerSRS this will be available once Jupyter extension ships this feature to Stable users.


feat/WAL-533

So the ticket was about disabling the input of the pin code. in my opinion, this only "disables" more input, it does not disable the deleting of input. so i wonder if you are still able to remove input while it is executing

@BtencateSphereon after we spoke, made a few changes, removed the redundant value assignment as you suggested. also disabled accepting input after we hit the max input length


RuntimeError: invalid argument 0: Sizes of tensors must match except in dimension 1. Got 66 and 67 in dimension 2 at C:\w\1\s\windows\pytorch\aten\src\TH/generic/THTensor.cpp:689

Hello everyone,
Hope you are all doing well. I have been facing some challenges while trying to run the demo file. In effect, I have read the paper related to this repository and I have noticed that the model was trained with images of 1280 × 1024. When I try running the demo with RGB images of size 1080×1920, it gives the following error.
mask = model(input_image)
File "C:\ProgramData\Anaconda3\lib\site-packages\torch\nn\modules\module.py", line 541, in call
result = self.forward(*input, **kwargs)
File "e:\Tools_Seg\robot-surgery-segmentation-master\models.py", line 112, in forward
dec5 = self.dec5(torch.cat([center, conv5], 1))
RuntimeError: invalid argument 0: Sizes of tensors must match except in dimension 1. Got 66 and 67 in dimension 2 at C:\w\1\s\windows\pytorch\aten\src\TH/generic/THTensor.cpp:689
However, if I resize my image to a size smaller or equal to that of the images used during training, It works perfectly.
Please, has anyone faced the same problem? How can I solve it?
Any comments or suggestions would be highy appreciated.
Best regards,

Hi!
Both dimensions must be modulo of power of 2. If I recall, 32.

Thank you very much for your prompt reply.

Hi!
Both dimensions must be modulo of power of 2. If I recall, 32.

Thank you for your prompt reply.


Add Fabric Text Adapter

The basic implementation is in, the only thing which needs to be changed is to fix the build for fabric since codesigning seems to conflict with fabric's remapSourcesJar task. Hence why it is a draft PR for now.
This is build error:
Cannot call Task.dependsOn(Object...) on task ':text-adapter-fabric:signArchives' after task has started execution.
Related to #11

https://github.com/KyoriPowered/adventure-platform-fabric