Deprecated Functions in HA Core 2025.1.

Looking at my HA logs and noticed the following messages. Not urgent, but please fix in upcoming release. Love your work, couldn't live without the air con integration into HA!
2024-01-27 14:58:36.554 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_TEMPERATURE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.TEMPERATURE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:36.557 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_ENERGY was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.ENERGY instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:36.558 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_HUMIDITY was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.HUMIDITY instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:36.560 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_GAS was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.GAS instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:36.562 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_CURRENT was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.CURRENT instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:36.563 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_VOLTAGE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.VOLTAGE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:36.564 WARNING (MainThread) [homeassistant.const] VOLUME_CUBIC_METERS was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfVolume.CUBIC_METERS instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:36.566 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_BATTERY was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.BATTERY instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.057 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_HUMIDITY was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.HUMIDITY instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.058 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_POWER was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.POWER instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.059 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_TEMPERATURE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.TEMPERATURE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.061 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_ENERGY was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.ENERGY instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.062 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_CURRENT was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.CURRENT instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.063 WARNING (MainThread) [homeassistant.const] POWER_WATT was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.WATT instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.064 WARNING (MainThread) [homeassistant.const] TEMP_CELSIUS was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.065 WARNING (MainThread) [homeassistant.const] ENERGY_WATT_HOUR was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.WATT_HOUR instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.066 WARNING (MainThread) [homeassistant.const] VOLUME_CUBIC_METERS was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfVolume.CUBIC_METERS instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.067 WARNING (MainThread) [homeassistant.const] ELECTRIC_CURRENT_AMPERE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfElectricCurrent.AMPERE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.069 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_GAS was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.GAS instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.070 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_VOLTAGE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.VOLTAGE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.071 WARNING (MainThread) [homeassistant.const] ELECTRIC_POTENTIAL_VOLT was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfElectricPotential.VOLT instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.084 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_TARGET_TEMPERATURE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.TARGET_TEMPERATURE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.086 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_FAN_MODE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.FAN_MODE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.088 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_SWING_MODE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.SWING_MODE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.090 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_PRESET_MODE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.PRESET_MODE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.091 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_OFF was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.OFF instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.093 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_HEAT was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.HEATING instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.094 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_COOL was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.COOLING instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.095 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_DRY was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.DRYING instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.096 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_IDLE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.IDLE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.097 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_FAN was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.FAN instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.099 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_HEAT was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.HEAT instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.100 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_COOL was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.COOL instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.101 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_HEAT_COOL was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.HEAT_COOL instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.102 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_DRY was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.DRY instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.103 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_FAN_ONLY was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.FAN_ONLY instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.104 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_OFF was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.OFF instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.107 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_PRESET_MODE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.PRESET_MODE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.109 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_DIRECTION was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.DIRECTION instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.111 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_SET_SPEED was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.SET_SPEED instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.112 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_OSCILLATE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.OSCILLATE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.114 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_PRESET_MODE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.PRESET_MODE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.115 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_DIRECTION was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.DIRECTION instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.117 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_SET_SPEED was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.SET_SPEED instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues
2024-01-27 14:58:37.118 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_OSCILLATE was used from echonetlite, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.OSCILLATE instead, please create a bug report at https://github.com/scottyphillips/echonetlite_homeassistant/issues

Already fixed with latest version (see release notes). Please update the custom component.


AssertionError in ScheduledFutureTask

WARNING Unexpected exception in the selector loop.
java.lang.AssertionError
    at io.netty.util.concurrent.ScheduledFutureTask.setConsumed(ScheduledFutureTask.java:112)
    at io.netty.util.concurrent.AbstractScheduledEventExecutor.pollScheduledTask(AbstractScheduledEventExecutor.java:134)
    at io.netty.util.concurrent.SingleThreadEventExecutor.fetchFromScheduledTaskQueue(SingleThreadEventExecutor.java:284)
    at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:461)
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:497)
    at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
    at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
    at java.lang.Thread.run(Thread.java:748)

Happens relatively frequently ever since we upgraded our application from 4.1.42 to 4.1.45. This is caused by JVM returning the same nanoTime value on consecutive calls. In debugger I found that value returned by nanoTime was exactly equal to deadlineNanos.
Fix is pretty simple: change the check in ScheduledFutureTask.java:112 or the one in AbstractScheduledEventExecutor.java:130 so they are consistent,
Steps to reproduce
N/A
Netty version
4.1.45, but the problematic assertion was introduced in https://github.com/netty/netty/commit/feb804dca8579c93ff3224564aafcf5938bb2c52#diff-a6871cf1d78dcb4ff1db3d6bb5e117b9, so presumably all versions since 4.1.44 are affected.
JVM version (e.g. java -version)
8u232
OS version (e.g. uname -a)
Windows 10

@djelinski interested in doing a PR ?


Is there a way to disable jaegar tracing?

I need to disable jaegar tracing completely as I am doing microsecond scale latency analysis and want to minimize any such overheads. Is there a reliable way to do this or is there a branch/release of the repo without jaegar which I could use?

In nginx-web-server/jaeger-config.json, change the sampler "param" from 0.2 to 0.0


Switch to BufferedOutputStream in DexMaker.java

Android's StrictMode will throw exceptions and crash because this file uses unbuffered io. This switches to BufferedOutputStream and adds try/finally blocks to ensure subsequent errors are prevented should something fail.
This can be seen using mockito's mock() and spy() functions.

The change looks reasonable to me


Added preloader for improved user experience

i was not able to preview the website due to unable to setup django file, but i previewed it in the separete file with found no error in it, You may crosscheck it.

GSSoC 24 has been completed Finally'
It was a great experience working with you all
Thanks💗 for your valuable contributions!
PA nomination has been started, Do fill out the forms soon. Share your experiences and let's connect on socials


fix

What
fix file name on copy
@matskiv could you take a look at this one. I made a mistake when redoing the change on the related pr

@wei-lee this change needs to be in also. I made an coopy paste error when re-doing the changes after dropping the commit during our discussion yesterday.


Migrate to using a ROCK

This PR addresses the following:

Replace the Dockerfile with a rockcraft.yaml
Update the CI workflows to publish a ROCK to ghcr.io
Use the ROCK in the charm

Merged manually at the command line


Allow Bugsnag to return current metadata

Description
In #747 access to the breadcrumbs was provided. Thanks! It would be nice to also have read access to the current metadata.
Describe the solution you'd like
Clients can write to the metadata, but cannot read it. If they could read it, it would be useful. Basically it will allow clients to use Bugsnag as a data store for "interesting developer information" that could be surfaced in an in-app bug reporter. This way our in=app bug reports will have the same data as crash reports, making for a terrific developer experience.
Describe alternatives you've considered
Clients could track everything being sent to Bugsnag, but this would create duplication of data. It may also be error prone.
Additional context
Our app has an in-app bug report mechanism, and the data there isn't the same as in crash reports. We have a goal of making the developer experience better when something "bad" happens, and a common data store would help out in that regard.

Hey @bolsinga, the metadata is retrievable

at event send-time in a callback using the event.getMetadata() method: https://docs.bugsnag.com/platforms/ios/customizing-error-reports/#getmetadata
at any other time using Bugsnag.getMetadata().

For example, the following:
let config = BugsnagConfiguration.loadConfig()
config.addMetadata("Acme Co.", key:"name", section:"account")
config.addMetadata(true, key:"paying_customer", section:"account")

config.addOnSendError { (event) -> Bool in
    dump(event.getMetadata(section:"account"))
    return true
}

// ...
// Wrapped in an @IBAction of a button
dump(Bugsnag.getMetadata(section:"account"))

Results in the following for both the onSend callback, and @IBAction call:
▿ Optional({
    name = "Acme Co.";
    "paying_customer" = 1;
})

Hopefully this helps cover what you're looking to achieve! You mentioned that you were unable to read the metadata in your original post, so If I've misinterpreted your question, please do get back in touch 😄

Hi @xander-jones Yes, I saw that about meta data for a given section. I'd like to get all the meta data, since I do not know what sections my clients may add. Those API would work if I could also get all the sections back via something like -getSections. What do you think? Thanks.


Your device was reachable but we could not correctly detect it

Hello,
As indicated in the logs, I create an issue here (Your device was reachable but we could not correctly detect it)
Error obtained for an KM2.
Don't know what's going on.
What would you need to help in debug?
Error while setting up deltasol platform for sensor
10:54:32 – (ERREUR) Capteur (intégration personnalisée)
Unexpected error fetching deltasol_km2_sensor data: Your device was reachable but we could not correctly detect it, please file an issue at: https://github.com/dm82m/hass-Deltasol-KM2/issues/new/choose
10:54:31 – (ERREUR) deltasol (intégration personnalisée)
Stopping Deltasol Resol integration due to previous error: Your device was reachable but we could not correctly detect it, please file an issue at: https://github.com/dm82m/hass-Deltasol-KM2/issues/new/choose
10:54:31 – (ERREUR) deltasol (intégration personnalisée)
Your device was reachable but we could not correctly detect it, please file an issue at: https://github.com/dm82m/hass-Deltasol-KM2/issues/new/choose
10:54:31 – (ERREUR) deltasol (intégration personnalisée)
Frantz

Can you please enable debug log, restart your home assistant and post the logs again:
https://github.com/dm82m/hass-Deltasol-KM2#troubleshooting

Thank you!
Done :
Cette erreur provient d'une intégration personnalisée
Logger: custom_components.deltasol
Source: custom_components/deltasol/deltasolapi.py:71
Integration: deltasol (documentation, issues)
First occurred: 11:21:06 (1 occurrences)
Last logged: 11:21:06
Unexpected error fetching deltasol_km2_sensor data: Your device was reachable but we could not correctly detect it, please file an issue at: https://github.com/dm82m/hass-Deltasol-KM2/issues/new/choose
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 205, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 164, in _async_update_data
return await self.update_method()
File "/config/custom_components/deltasol/sensor.py", line 80, in async_update_data
raise error
File "/config/custom_components/deltasol/sensor.py", line 76, in async_update_data
data = await hass.async_add_executor_job(api.fetch_data)
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/deltasol/deltasolapi.py", line 104, in fetch_data
raise error
File "/config/custom_components/deltasol/deltasolapi.py", line 89, in fetch_data
product = self.detect_product()
File "/config/custom_components/deltasol/deltasolapi.py", line 71, in detect_product
raise IntegrationError(error)
homeassistant.exceptions.IntegrationError: Your device was reachable but we could not correctly detect it, please file an issue at: https://github.com/dm82m/hass-Deltasol-KM2/issues/new/choose
and:
Logger: homeassistant.components.sensor
Source: custom_components/deltasol/sensor.py:55
Integration: Capteur (documentation, issues)
First occurred: 11:21:07 (1 occurrences)
Last logged: 11:21:07
Error while setting up deltasol platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 250, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/deltasol/sensor.py", line 95, in async_setup_platform
await update_unique_ids(hass, coordinator.data)
File "/config/custom_components/deltasol/sensor.py", line 55, in update_unique_ids
for unique_id, endpoint in data.items():
AttributeError: 'NoneType' object has no attribute 'items'
Hope this helps.

no, that is not all I need, there should be information like these:
2022-07-21 08:14:34 INFO (SyncWorker_1) [custom_components.deltasol] Auto detecting Resol Deltasol product from http://<IP_ADDRESS>/cgi-bin/get_resol_device_information
2022-07-21 08:14:34 DEBUG (SyncWorker_1) [custom_components.deltasol] response: vendor = "RESOL"
product = "KM2"
serial = "XXX"
version = "1.2.0"
build = "rc1"
name = "KM2-XXX"
features = "vbus,km2"
2022-07-21 08:14:34 INFO (SyncWorker_1) [custom_components.deltasol] Detected Resol Deltasol product: km2
2022-07-21 08:14:34 DEBUG (SyncWorker_1) [custom_components.deltasol] Retrieving data from km2
2022-07-21 08:14:34 DEBUG (SyncWorker_1) [custom_components.deltasol] KM2 requesting sensor data url http://<IP_ADDRESS>/cgi-bin/resol-webservice

you can use home assistant logging and filter based on the keyword 'deltasol' and then post the full log content here.

Oh OK, I hope I'm good this time :
2022-07-25 11:18:13 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration deltasol which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-07-25 11:21:06 INFO (SyncWorker_10) [custom_components.deltasol] Auto detecting Resol Deltasol product from http://<IP_ADDRESS>/cgi-bin/get_resol_device_information
2022-07-25 11:21:06 DEBUG (SyncWorker_10) [custom_components.deltasol] response: vendor = "RESOL"
2022-07-25 11:21:06 ERROR (SyncWorker_10) [custom_components.deltasol] Your device was reachable but we could not correctly detect it, please file an issue at: https://github.com/dm82m/hass-Deltasol-KM2/issues/new/choose
2022-07-25 11:21:06 ERROR (MainThread) [custom_components.deltasol] Stopping Deltasol Resol integration due to previous error: Your device was reachable but we could not correctly detect it, please file an issue at: https://github.com/dm82m/hass-Deltasol-KM2/issues/new/choose
2022-07-25 11:21:06 ERROR (MainThread) [custom_components.deltasol] Unexpected error fetching deltasol_km2_sensor data: Your device was reachable but we could not correctly detect it, please file an issue at: https://github.com/dm82m/hass-Deltasol-KM2/issues/new/choose
File "/config/custom_components/deltasol/sensor.py", line 80, in async_update_data
File "/config/custom_components/deltasol/sensor.py", line 76, in async_update_data
File "/config/custom_components/deltasol/deltasolapi.py", line 104, in fetch_data
File "/config/custom_components/deltasol/deltasolapi.py", line 89, in fetch_data
File "/config/custom_components/deltasol/deltasolapi.py", line 71, in detect_product
homeassistant.exceptions.IntegrationError: Your device was reachable but we could not correctly detect it, please file an issue at: https://github.com/dm82m/hass-Deltasol-KM2/issues/new/choose
2022-07-25 11:21:06 DEBUG (MainThread) [custom_components.deltasol] Finished fetching deltasol_km2_sensor data in 0.235 seconds (success: False)
2022-07-25 11:21:06 DEBUG (MainThread) [custom_components.deltasol] Checking for sensors with old ids in registry.
2022-07-25 11:21:07 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up deltasol platform for sensor
File "/config/custom_components/deltasol/sensor.py", line 95, in async_setup_platform
File "/config/custom_components/deltasol/sensor.py", line 55, in update_unique_ids

within your network, please open this url in a web browser and post the result: http://<IP_ADDRESS>/cgi-bin/get_resol_device_information

Done :
vendor		= "RESOL"
product		= "VBus/LAN Adapter"
serial		= "001e66423ecb"
version		= "2.0"
build		= "rc1-WL-MAR"
name		= "RESOL-LAN-Atelier"
features	= "vbus"
pcbserial	= "4032220"

seems that you are not having a KM2 or DL2 or DL3 device. instead you are having the vbus lan adapter. this plugin is not working with the vbus lan adapter.
see: https://github.com/dm82m/hass-Deltasol-KM2/issues/17

Oh Yes, sorry! It's true that I wanted to buy the KM2, but it was not avaialble so I bought the vbus LAN adaptor. But as I used successfully the json-live-data server tool provided here I thought it could maybe use the same way to read data.
Sorry to have disturbed you and thank you very much for your prompt answers.

yes if you run this server and emulate a km2 you can use our plugin here to grab the data from the emulated km2.

I don’t have that skill, but maybe with a few tips, to understand how to emulate a km2, I could try to make it by myself?

@frantzphilippe I created an Home Assistant addon to run the json-live-data-server. Would you like to be a test candidate?


no license specified

I was interested in possibly using your code, but I don't see a license specified.
Please include a license for your code.  Thanks.

Done. Thank you, I was wrongly assuming no licence = Open Source / Free


V3: In namespaced mode, Argo UI's /workflows tries to serve all workflows across the cluster

Summary
What happened/what you expected to happen?
In Argo v2, in namespaced server mode, going to /workflows in the Argo UI served only the workflows for the corresponding namespace of the server you're connected to. In v3, it appears to serve the workflows across the cluster, even though you're connecting to the server of a specific namespace. This forces you to go to /workflows/namespace to view your workflows if you are not permissioned to view workflows in the cluster. Before, it wasn't even possible to view cluster-wide workflows in namespaced mode, which I think is the more expected behavior.
Is this behavior intentional? Did something change about how routes are served?
Diagnostics
What version of Argo Workflows are you running?
v3.0.0

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Can I please request...

Screenshot.
Contents of localStorage, found in Javascript console. Looks like:

Storage {managedNamespace: "argo", loglevel:webpack-dev-server: "INFO", ListOptions/options: "{"selectedPhases":[],"selectedLabels":[],"paginationLimit":500}", current_namespace: "", length: 4}

E.G.

Storage {managedNamespace: "s-workflow-platform", ListOptions/options: "{"selectedPhases":[],"selectedLabels":[],"paginationLimit":500}", current_namespace: "", length: 3}
ListOptions/options: "{"selectedPhases":[],"selectedLabels":[],"paginationLimit":500}"
current_namespace: ""
length: 3
managedNamespace: "s-workflow-platform"
__proto__: Storage

When I browse to the base URL, it auto redirects me to /workflows/s-workflow-platform
But I can manually delete the namespace name, whereupon it will serve (or attempt to, if I'm not permissioned) all workflows in the cluster.  My expectation would be that there is no way to view cluster-wide workflows from a namespaced server, which is how it behaved in V2.

I see the same error.

This needs to be fixed here:
https://github.com/argoproj/argo-workflows/blob/master/ui/src/app/workflows/components/workflows-list/workflows-list.tsx#L198
Basically we need to check to see if managed namespace is set.
Would anyone like to submit a PR?

Are you suggesting that we just filter down to the managed namespace on all fetchWorkflow calls?
To go in hand with this, we should probably also change the redirect from base URL to just go to /workflows/ when there is a managed namespace, too, right?

Either that - or there's a bug in app-router?

I just edited my like 30 seconds ago so not sure if you saw it -- but I linked where I think this might be happening https://github.com/argoproj/argo-workflows/blob/master/ui/src/app/app-router.tsx#L167 .. if any namespace is set, which will always be true I think since we have a managed namespace in this case .. it directs there.
So perhaps we should update it to just redirect to /workflows if we're in managed-namespace mode and then add the logic to filter workflows where you linked. What say you to that?

I wonder if the order of those elements is important and the redirect should be top of the list?

Bump! @Radolumbo are you still investigating?

I definitely still intend on coming back to this! I've been on vacation for the last week so haven't had a chance. If someone else feels like they want to make the fix they can, else I'll be working on it next week!

Related:
fix(ui): Fix editor. Fixes #5613 Fixes #5617 (#5620)

I think this may have been fixed on master.

I'll test it out in a bit, and see!

I could not reproduce this. Can anyone volunteer to debug via Zoom?

I could do so. I just got back to looking at this, and I think I understand what's happening, though I haven't decided exactly the best way to approach it, yet.

I should at least have a draft PR soon for one way we can approach this. I think it's a little hacky, but it's similar to what was being done in V2, and should at least start a discussion.

Please see https://github.com/argoproj/argo-workflows/pull/5729


Merge upstream

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 5 committers have signed the CLA.:x: ljharb:x: kaplanmaxe:x: bl00mber:x: hanzhijue:x: lencioniYou have signed the CLA already but the status is still pending? Let us recheck it.


Add Fargate section

Following PR adds a section about recently announced service called AWS Fargate.
Thanks a lot @ThanosBaskous for reviewing my drafts.
Regards,
pgrzesik

Thanks for putting this together @pgrzesik!
Note: reviewed in Quip new section doc.

🎉  cool!


(BSO) webhooks & trip return messages

🐛 Bug Report
I will try to describe this so that it actually makes sense, but honestly I’m still beyond confused by the situation.

Basically, about 3 days ago with the release of the repeat trip button I noticed that the bot wouldn’t repeat my dungeoneering trips via said button (which is still the case, but that’s in another bug report I just posted).

after noticing the repeat trip button wouldn’t respond I did the discord bot equivalent of “have you tried turning it off and then on again”, meaning I kicked the BSO bot from my server and re-added it again

I then came into the much more frustrating problem of no longer getting trip return messages for dungeoneering and farming trips

Maybe a day later (2 days ago) I decided to make a separate test channel to see if it was just dungeoneering and farming commands having issues, and much to my surprise other commands did get trip return messages. In hindsight I should’ve tested the dungeoneering/farming commands in the test channel, but for whatever reason I didn’t and just assumed that the issue was related to those commands

fast forward to last night, I kicked the bot again because it obviously worked so well the first time, but I still wasn’t getting trip return messages and I was desperate at this point. This is when I realized the issue was related to the channel/server, not specific commands because I no longer got trip return messages in my test channel.

I created a 2nd test channel and again, got trip return messages in that one but still not in any of the pre-existing channels. At this point I started looking at channel/server settings

To sum it up:

The bug:
The bot deletes all of its webhooks when it leaves a server, thus somehow disabling trip return messages in channels existing prior to re-adding the bot. It still responds to commands and starts trips perfectly fine, there’s just no indication that the trip ended and you won’t see what loot you received afterwards (even though trip loot does go in the bank). I couldn’t find any way to manually add webhooks to pre-existing channels.
The server side semi-fix:
It’s been years since I coded anything so I can’t really offer any help on the code side of things, but if this happens to anyone else in their server the thing that worked for me was just creating new channels
one last thing:
When messing with the webhooks, I realized you can manually switch the channel it’s linked to, but this just made things significantly more confusing. When changing the webhook from Channel B to Channel A, when starting a trip in Channel A you still wouldn’t receive a trip return message. However, when starting a trip in Channel B, the trip return message would be sent from the bot in Channel A. Essentially: manually switching the webhooks channel (from B to A) only changed the final output location (A), the input still had to come from the original channel (B).

issue fixed in next update


fix-exception

In some case defaultAbiCoder.decode will throw exception even if set the tryAggregate

Hey thanks for PR! Have you got an example of a broken one I can test it with?

here is a example: https://github.com/Yohox/multicall-exception
when invoke a contract but address is not a contract address or correct address it will throw exception which even if set tryAggregate true

Thanks a lot will test and look tomorrow


Add exclusions feature

Using existing function addAll to avoid adding any dependency found in exclude to depsIndex.

@kessler could you please let me know if you have any feedback on this PR. Otherwise, I am happy to close it.
Thanks

I need this feature, any timeline on whether it will be merged?

published @2.2.0
sorry for the delayed response


How can we save pre-processed images as png - what is used during training

I know --debug option but it is very very slow
Are there any option to what is being used in the training? Like when pre-processing images and prompts we can save final used image and the prompt?
Thank you @kohya-ss

that would be great to double check what is being used in the traiining, or perhaps an output of each image's resolution scaled down or cropped. I am gonna try --debug but to be able to save processed png files or "see" insode of pnz files to understand the latent representaion better


remove-customer-scenario-assumption-for-decimal

remove the decimal test scenario for 0.1 + 0.1 + 0.1 = 0.3 as it's about customer side scenario, which is out of the scope of cadl ranch testing. If service side expect their customer to use decimal for math calculation, we should suggestion them to use @encode(string), which is pending https://github.com/microsoft/typespec/issues/2762

I assume the intention was to make sure the decimal type works like a decimal, instead of float.
Do we know the owner of this 2 tests?
Java is kind of fine, we had ours in emitter https://github.com/Azure/autorest.java/blob/main/typespec-tests/src/test/java/com/type/scalar/DecimalTests.java#L34-L54

I think @tadelesh added this https://github.com/Azure/cadl-ranch/pull/451

I assume the intention was to make sure the decimal type works like a decimal of infinite precision, instead of float.
Do we know the owner of this 2 tests?
Java is kind of fine, we had ours in emitter https://github.com/Azure/autorest.java/blob/main/typespec-tests/src/test/java/com/type/scalar/DecimalTests.java#L34-L54

I noticed that in java test, you are using string to create the BigDecimal too.

I noticed that in java test, you are using string to create the BigDecimal too.

This is for Java type for that decimal. BigDecimial has ctor of String.
I can use other ctor e.g. https://docs.oracle.com/javase/8/docs/api/java/math/BigDecimal.html#valueOf-long-int-
Just choose the easy one.

The test is aimed to make sure client side generate the right precision for decimal. .NET has native decimal128 type, which means not all languages need to use string to do ser/deser.

The test is aimed to make sure client side generate the right precision for decimal. .NET has native decimal128 type, which means not all languages need to use string to do ser/deser.

the math calculation is suggesting we are testing customer user scenarios which is out of the scope of cadl-ranch, however, what cadl ranch should be testing is the type expression and api interface.

The test is aimed to make sure client side generate the right precision for decimal. .NET has native decimal128 type, which means not all languages need to use string to do ser/deser.

the math calculation is suggesting we are testing customer user scenarios which is out of the scope of cadl-ranch, however, what cadl ranch should be testing is the type expression and api interface.

Since we don't have a good way to test the edge number of decimal, we use this calculation to ensure client generate the right type. If removed, do you mean language generator should ensure it?

We need test that check if the TypeSpec has Decimal as input or output, the SDK has a strategy to deal with it. The exact strategy for that, is up for SDK. Even if we're adding encode(string), we still need "naked" tests with no decorators. So we should not remove those tests.
However, the test is designed to force the SDK person to sum 0.1+0.1+0.1 on the client side and get 0.3 in return, which is a math operation that requires Decimal support. I'm ok if TypeScript were to hardcode to return 0.3, with a comment that says that given JS limitation, it's not possible to do 0.1+0.1+0.1 in JS. I read all the JS issues, and @bterlson long comment about it, I don't think this is in opposition of the spirit of what we are trying to accomplish. IOW, I'd like language that can to have the possibility to show what they can do, without forcing languages that can't to be blocked. Removing the test, remove the ability to write anyything at all, which I think is a contradiction of the intent of cadl-ranch.

I am fine to not remove it and work around it in JS by passing 0.3 for this case.


The minimum size of a terminal should be an option in Settings

[(https://github.com/Microsoft/vscode/issues/45678)]
The related issue was closed, but I think it need more work!
Some terminal can be resized to a small size if they are not important. In some case, showing multiple terminals is just to notify the user whether they are running. Currently the minimum size of terminal is fixed and too large.
I suggest that the minimum size of a terminal should be an option in Settings.

@Tumiz do you have a better suggestion for the minimum size (currently 250px)? #45678 was purely to prevent a broken layout in the terminal space and having terminals get hidden.

Some terminal is OK as small like this. In this case, I only need a few lines to show a program's status. So partly hidden is also acceptable.
It will be better if the minimum size can be configured in Settings.


docs: Add additional CMake documentation

Add some additional documentation for how to integrate this into another CMake project.

Coverage remained the same at 100.0% when pulling dae12d6e7960a04626a7bba9b5d40d272f855f9c on chuckatkins:add-more-cmake-docs into c8231eff75ca51a03416976b490d876f3dcd93f6 on nlohmann:develop.

@nlohmann TOC fixed and cleaned up.

Looks like Travis got a little borked.  I'll kick the branch to cycle the CI again.

@nlohmann this should be good to go now to once CI finishes.

Thanks!


New windows?

Feature Request: New windows?
As of now (Beta 1.0 - commit 04269eea998950c108a3f3992866d3558877e349) Textual creates views through div elements.
The New Stuff

Instead of using divs, Textual would use new windows that display the content of a .html file.

Pros
This would make the index.html file less cluttered.
Cons
There would be no opening animations.

I will create a new branch for experimenting with this.


test on osx on travis

I'm pretty sure a couple of the tests are failing on OSX right now, pushing this up to verify

oh right.. i forgot this feature isn't available on all travis accounts.


optimize: skip fatal when pubsub/jetstream server don't start in unit test

=== RUN   TestAuthentication
=== RUN   TestAuthentication/Valid_jwt_and_valid_seed
err: nats: no servers available for connection
    authentication_test.go:56: Did not expect error during connect nats: no servers available for connection
=== RUN   TestAuthentication/Valid_jwt_and_invalid_seed
err: dial tcp [::1]:4222: connect: network is unreachable
=== RUN   TestAuthentication/Invalid_jwt_and_valid_seed
err: nats: no servers available for connection
--- FAIL: TestAuthentication (0.00s)
    --- FAIL: TestAuthentication/Valid_jwt_and_valid_seed (0.00s)
    --- PASS: TestAuthentication/Valid_jwt_and_invalid_seed (0.00s)
    --- PASS: TestAuthentication/Invalid_jwt_and_valid_seed (0.00s)
FAIL
FAIL    github.com/dapr/components-contrib/tests/e2e/pubsub/jetstream/authentication    0.009s
FAIL

Normally, tests in the e2e folder don't run when running make test.
However, I understand the issue and I think it should be fixed. But, if the server isn't ready, the test should be skipped entirely and not just avoiding a fatal log.
See how binding.ipfs does it: if you want to run the test, you need to pass an environmental variable; otherwise, the entire test is skipped:
https://github.com/dapr/components-contrib/blob/master/bindings/ipfs/ipfs_test.go#L36-L43

If this is an integration test I think we should use build tags! Please don't use environment variables to trigger the test unless this is needed for configuring the server etc, still I think build tags are the way to go.
FYI @ItalyPaleAle

berndverst
ItalyPaleAle
/cc @berndverst @ItalyPaleAle. Thanks, i added a e2etest buildtag for the unit test jetstream  file.

Please change to use an env var to make the tests run. See example in bindings.ipfs: https://github.com/dapr/components-contrib/blob/master/bindings/ipfs/ipfs_test.go#L36-L43

IPFS_TEST: "1"
      if utils.IsTruthy(os.Getenv("IPFS_TEST")) {
                  log.Println("IPFS_TEST env var is not set to a truthy value; skipping tests")
                  os.Exit(0)
      }

IPFS_TEST=1 don't execute this unit test. Why not 0?

IPFS_TEST=1 don't execute this unit test. Why not 0?

It should! Did you export IPFS_TEST=1?

If this is an integration test I think we should use build tags! Please don't use environment variables to trigger the test unless this is needed for configuring the server etc, still I think build tags are the way to go.

Whatever the boss (@berndverst) says :) However, the downside of build tags is that you need to configure your IDE too or the language server won't scan them...

IPFS_TEST

the env variable IPFS_TEST is a neutral word, if  change to IPFS_TEST_OFF is more appropriate?

Oh I see now. It is missing a ! before utils.IsTruthy. Want to open another PR to fix that?

Oh I see now. It is missing a ! before utils.IsTruthy. Want to open another PR to fix that?

hah, i do it.

Once we create certification tests for this component we should move this into a certification test instead! Does someone know how to enable NATS jetstream with a Docker image? Or ideally how to create the Docker-compose file? A lot of configuration seems to be required there.

Once we create certification tests for this component we should move this into a certification test instead! Does someone know how to enable NATS jetstream with a Docker image? Or ideally how to create the Docker-compose file? A lot of configuration seems to be required there.

We may need readme and makefile in this e2e example.


audio support g711

I refactored the PR and added full support for it in this PR:
https://github.com/pedroSG94/RootEncoder/pull/1358
In this PR. I added support for G711 encoding and rtsp streaming with G711 codec.

This branch was merged with my refactor. Now, you can use G711A in RTSP


acceptance = backscale x exposure

Fix acceptance handling in ogip dataset reader

@registerrier could you merge this please?


Format /pages intro actions with a

Fixes the awkward spacing that occurs when the third buttons wraps (typically on mobile devices):

@rita3ko @signalnerve Please double check I preserved the link hrefs properly, but otherwise I think this should be good to go.

ty @adamschwartz <3


Java indexer: do not mark local classes as anonymous in their MarkedSource [phab:D2118]

Created by schroederc at 2018-01-16 18:04:41:

salguarnieri accepted this revision at 2018-01-16 18:11:20

schroederc closed via commit ca5dcfc1701f1b39abd01c9257fb63befe3e6744 at 2018-01-16 18:17:22


References and links to "wdp-pipeline-schemas" repo and internal github

While browsing the wiki I found references to "wdp-pipeline-schemas" repository in a few different places and some links that give a 404, I believe this should now be referring to the elyra-ai/pipeline-schemas repo.
test harness source:

https://github.com/elyra-ai/canvas/blob/master/canvas_modules/harness/src/client/components/common-properties-conditions.jsx#L284-L286

canvas controller source:

https://github.com/elyra-ai/canvas/blob/master/canvas_modules/common-canvas/src/common-canvas/canvas-controller.js#L216 , and lines 228, 334, 364, 381

references to github.ibm.com in source files: https://github.com/elyra-ai/canvas/search?q="github.ibm.com"&unscoped_q="github.ibm.com"
And in the wiki at these pages:

https://github.com/elyra-ai/canvas/wiki/2.0-Common-Canvas-Documentation#step-3--set-the-model-and-palette-data

https://github.com/elyra-ai/canvas/wiki/2.4-Canvas-Controller-API#pipeline-flow-methods and "Palette methods" section

links in this section https://github.com/elyra-ai/canvas/wiki/3.0-Common-Properties-documentation#helpclickhandler

https://github.com/elyra-ai/canvas/wiki/3.6-Common-Properties-Controller#datasetmetadata-methods

Thanks for reporting these issues.  I fixed everything now. Let us know if you spot anything else. Thanks!


Revert the PR that killed CustomizeUI extension

The PR #166126 killed the extremely popular extension CustomizeUI (~160k downloads) a while ago (discussion here). There was a lot of backlash from the community in the PR comments, but the PR was merged and I can't see any issues mentioning this problem right now.
Customizing the UI was such a fundamental feature of vscode and I believe most people would agree that it's much more important than cutting down 1.8MB of bundle size. For me personally, CustomizeUI saved a lot of real estate by:

moving the activity bar icons to a horizontal setting
hiding the top bar
making the tab bar shorter

The difference in real estate is so much that I've been considering switching entirely to nvim for this reason alone. I'd love to be able to customize my vscode like before.
Are there any plans to allow fully customizing the UI through some other means, or to simply revert the PR changes?

Yeah 1.8MB is NOTHING compared to UI customization. NOTHING. PLEASE revert the PR.

I have locked this issue as for being too heated.
We have explained our reasoning and background here https://github.com/microsoft/vscode-discussions/discussions/257#discussioncomment-4788068
To summarise: nothing has been killed, there is no evil intent, what CustomizeUI did is still possible, and us (the people reading these comments) are just people like you.
Extensions like CustomizeUI extend VS Code not by using the API but by applying reverse-engineered patches. These patches break whenever something "inside" VS Code changes. We tolerate extensions taking such an approach but we can support them (it would me we cannot change VS Code any further). Doing private property mangling was a lot of those changes but fundamentally patches still work, we also publish source maps that include the reverse mapping from mangles to original name. So, anyone with constructive energy can step up and fix CustomizeUI, we are happy to help with source maps but we won't revert mangling.


golint lies about missing comment

test.go:
package test

const Test = 1 // comment

$ golint
test.go:3:7: exported const Test should have comment or be unexported

The constant HAS the bally comment, by Jove. The warning should be rephrased.
Previous issue (closed without discussion): https://github.com/golang/lint/issues/208

stringer has a cmd param : -linecomment . Cannot be used.


feat: add C implementation for stats/base/dists/binomial/variance

Resolves #3477
Description

What is the purpose of this pull request?

This pull request:

Adds C implementation for binomial Variance
Includes benchmarks for the C implementation.
Provides examples demonstrating the usage of the binomial Variance in C.

Related Issues

Does this pull request have any related issues?

This pull request:

resolves #3477

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

/stdlib update-copyright-years

/stdlib update-copyright-years

@Planeshifter Make all the changes. Please review all the changes.


LOD-BPM-PVS - Trial Account Problems

LOD-BPM-PVS Please assist with the following as suggested below:-
Can you please raise a ticket on LOD-BPM-PVS component. This could be a product issue or an issue with your trial account. The dev teams might need your cloud account details to look into it and update your account if needed.
Details of issue are as follows:-
Tutorial: https://developers.sap.com/tutorials/cp-starter-ibpm-employeeonboarding-5-run.html
Write here what you need help with ... This is the second time I have logged this issue. It was previously closed (Closed #6104.) as I did not have the time to check whether it had been fixed..
I get all the way passed the successful Importing of the EmployeeOnboardingEvents JSON file but when I try to filter it there is no file to be found so I cannot continue with the tutorial.
Thanks for your support

@IsabellaMasselli - Have you raised a BCP ticket on LOD-BPM-VIS component?

@IsabellaMasselli - Have you raised a BCP ticket on LOD-BPM-VIS component?

I have raised a LOD-BPM-VIS component issue on this forum, I don't think I have access to BCP??

I have raised a LOD-BPM-VIS component issue on this forum, I don't think I have access to BCP??

@IsabellaMasselli - We checked internally on many other trial accounts and we did not face the issue. Can you check and confirm (a) if the name you are using to search is "onboard" (without quotes and without any leading or trailing spaces) and (b)  click on the Errors tab, to see if there were any issues while importing the events.

@IsabellaMasselli - We checked internally on many other trial accounts and we did not face the issue. Can you check and confirm (a) if the name you are using to search is "onboard" (without quotes and without any leading or trailing spaces) and (b)  click on the Errors tab, to see if there were any issues while importing the events.

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


Any possibility to use skype channel as human?

That is really an awesome work. But can you say like how to use skype as channel for human agent. I mean like instead of using WebChat channel as agent, i need to use Skype channel as agent.

Sorry for late response. I don't foresee any problem in using Skype. As long as you correctly register the agent things should work out. Did you try it out? Are you facing any issues?


[Bug]: Better handling of empty and non-existent files with wsh edit

Feature description
Because wsh edit doesn´t create new files, a new file needs to be created using the touch command. This command creates a 0-byte file. When trying to wsh edit this file i get the message Unable to determine mimetype for: <file>.
Implementation Suggestion
The new behavior should be that whenever the MIME type is unknown or a 0-byte file is to be edited, wsh edit needs to assume it's a text file.
Anything else?
Related to https://github.com/wavetermdev/waveterm/issues/925.

Fixed with #963


Move channels and their mutex to a separate class

I've tried to implement the request from this comment from https://github.com/ably/ably-asset-tracking-android/pull/773 and wanted to create a quick draft PR to validate whether I'm following the correct approach.

I like this approach :)

Closing as we won't use the mutex based approach


Can the pinpoint support struts ?

I have find that Spring is wrote in the Pinpoint Supported Modules , so could the Pinpoint support Struts ?
Or is there any plugin witch could make Pinpoint support struts ?
Thanks for your team

Unfortunately, Pinpoint Team has no plan to support struts.

Oh , it seems that I have to find another way for my project .


code style: rename vars, use a function to compute LevelDB keys

Will submit another PR that changes to tabs everywhere. Or do you prefer a different indentation style that I should apply?

Also, I would like to move the database opening logic out of import and instead pass it in as a parameter. What do you think?


golang protobuf bump

README for https://github.com/golang/protobuf says:

It has been superseded by the google.golang.org/protobuf module, which contains an updated and simplified API, support for protobuf reflection, and many other improvements. We recommend that new code use the google.golang.org/protobuf module.
Versions v1.4 and later of github.com/golang/protobuf are implemented in terms of google.golang.org/protobuf. Programs which use both modules must use at least version v1.4 of this one.

Meaning we need to either switch to google.golang.org/protobuf, or at least use github.com/golang/protobuf v.1.4+.

This needs to be coordinated with runc of course.

Should be ixed by https://github.com/checkpoint-restore/go-criu/pull/38 and https://github.com/checkpoint-restore/go-criu/pull/43

Tested with runc: https://github.com/opencontainers/runc/pull/2807. Had to made a change for debug print of criu options as they are now represented slightly different (XXX_* are gone, all-lowercase are added).
@adrianreber can you please make a release?

Since https://github.com/checkpoint-restore/go-criu/pull/46 we'll have to switch to v5 anyway, so maybe make a release once you merge it @adrianreber

Fixed by #38 and #43, with #46 as a follow-up.


Foundation 6.4.1 custom build - number of grid columns is ignored

How to reproduce this bug:

Step one

Visit: http://foundation.zurb.com/sites/download.html/

Step two

Choose "Custom Build" and add another number to "The Grid # of columns" f.ex. "24"

Step three

Click "Download custom build"
What should happen:
The downloaded CSS-Files should have 24 columns for the grid
What happened instead:
They support only 12 columns instead
Browser(s) and Device(s) tested on:
Chrome latest, FF latest, Win10
Foundation Version(s) you are using:
6.4.1

Yes, I have same problem. Always 12 column...

Pushed an update in the customizer repo, @rafibomb please deploy when you get a chance

The current customizer uses the right column settings. At least I can see small-24, small-23 and so on. So I guess this is already resolved?

The current customizer uses the right column settings. At least I can see small-24, small-23 and so on. So I guess this is already resolved?

@colin-marshall do you see the same or can you still reproduce the initial issue?

cc @ncoden @SassNinja @JeremyEnglert

Closing as we did not receive any further feedback.


[SP-4406] Backport of PDI-17033 - Put a File with SFTP Step Throws A …

…'Path Not Found' Error When You Attempt to Create Nested Subdirectories (8.1 Suite)
Didn't backport changes to chdir method as these need to be reverted in master.
@ricardosilva88 @cravobranco

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'engine' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/job/entries/sftp/SFTPClient.java
  engine/src/test/java/org/pentaho/di/job/entries/sftp/SFTPClientTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.trans.steps.calculator.CalculatorMetaFunction

Branch Change: -8.7% :small_red_triangle_down:
Complexity Change: -3% :small_red_triangle_down:
Instruction Change: -0.7% :small_red_triangle_down:
Line Change: -0.9% :small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Branch Change: -2.6% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupsert.SalesforceUpsertMeta

Instruction Change: -0.1% :small_red_triangle_down:


[Sprint 1] Add 3-6 additional flight maps to CASEI

Context
Back in FY24.1, we started visualizing flight paths for campaigns on CASEI. We started with 5 (see epic: https://github.com/NASA-IMPACT/admg-casei/issues/576) and have since expanded to ~8 (see YAML files https://drive.google.com/drive/u/0/folders/1R92_4YxYTo8oml0NHMCLFYJ-t-dHaWIR).

Example of a flight map for a campaign
Known Challenges
We learned through past efforts in trying to automate the data collection and visualization process that currently it is NOT possible to fully automate this process for these reasons:

Inconsistent data formats as in NASA's case airborne data ownership is split across 12 DAACs that all do things a bit differently
Different ways to define measurement variable names. This might not seem like a big deal but it really makes it hard/slow to get buy-in when building out features quickly as terminology is for queries and UI filters gets challenged back and forth. There are initiatives on streamlining language, for example the official GCMD science keywords (which is a string of keywords) but each DAAC also has their own views and it’s an ongoing discussion.
Incomplete data. To get the full set of historical data to even visualize flights (let along instruments on each flight deployment), in many cases you’ll need to manually look for data that’s lock in PDFs still or old canned films for example that are not digitized. This is what the ADMG data curators have been doing and filling in for CASEI

Goal

We will continue to collect and visualize campaigns in batches (of around 3-6) because each campaign may need some manual data fixes.
We will incorporate fixes to common data issues along the way, and continue to learn about the extent to which we can still create a pipeline for visualizing nav data in the cloud without having to do it locally and save out GeoJSON files

Acceptance Criteria

3-6 additional nav data sets saved as YAML files https://drive.google.com/drive/u/0/folders/1R92_4YxYTo8oml0NHMCLFYJ-t-dHaWIR
Static locations for those campaigns https://docs.google.com/spreadsheets/d/17v-ZfeWoPZoCAVSs57Y3Q1gKUe6S49fZ8rC2KOO_myY/edit#gid=1924471089
3-6  flight tracks visualized and deployed to CASEI in staging
Deploy from staging to production

Future note for @LanesGood to move out of backlog and label the correct PI Iteration and PI Sprint for the project board once the team has it set up the project board for the next PI.

Updated to reflect conservative estimate of adding 5 flight paths in this PI - we'll add 2 paths in the first sprint, rather than 3-6.

@als0076 I've deployed 4 campaigns to staging, could you check if the data looks ok?
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/IPHEx
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/FIREX-AQ
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/GCPEx
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/DISCOVER-AQ (this one can take some time to load the map, as the geojson file is quite big)

@willemarcel still waiting on DISCOVER-AQ to load but the rest look ready to deploy to production

@willemarcel DISCOVER-AQ finally loaded and it looks good to go!

@als0076 We are having a problem deploying DISCOVER-AQ data, but now you can access it.

@willemarcel -- i am having to move the map around first to see anything -- when i initially scroll down the page/see the box for where map should be it's only a black box, once i move it around/zoom  in or out, it shows up fine -- is this expected?
Also:   Can we try to revisit the icons being used for the non-moving platforms?  Is there a bank you're pulling from and/or would it be helpful if i suggested some from a place like noun project??

@smwingo That problem is not expected, although I've noticed a few times that the map took a bit more long to load. @als0076 Have you experienced that problem too?
We got the icons from Font Awesome.

@willemarcel I did not have any issues with the maps loading

Some alternate icons options:
Balloon Launch Site:
fine as it is now :)
Vehicle:
fine as it is now :)
Field Site:
observation tower icon
Permanent Land Site:
bold obs tower icon

@als0076 I've processed a new campaign: http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/ACCLIP
Could you check if the data looks correct?

@willemarcel ACCLIP looks correct

Thanks, @als0076! It's now deployed to production.

@willemarcel added 5 additional flight maps this sprint:

ACCLIP
IPHEx
FIREX-AQ
GCPEx
DISCOVER-AQ


Update iot-support-help.md

Add the following note:
If you are asking about an issue on a new support request that happened more than a certain period ago, it is unlikely that we will still have logs to investigate. Please let us know more quickly in the future if you observe the issue again.

@aktsuda : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#re-assign: @asergaz

Working on this.

@aktsuda thank you so much for your contribution. I made some changes and the information is now live. Appreciate your contribution and hope we can partner again :)!
#please-close


org-roam: Enable reflinks in property drawers

Meh, over-engineering. Just use definition lists or something for similar use case.


[pegtl] Update to 3.2.6 for MSVC and GCC fixes

What does your PR fix?
Recent versions of MSVC and GCC changed the behavior of built-in macros and template parsing, which breaks the PEGTL demangle function when it's used in cppgraphlgen. This shows up as a build break in the cppgraphqlgen port. This version of PEGTL includes workarounds/updates to work with these compiler versions.

Which triplets are supported/not supported? Have you updated the CI baseline?
All, No.

Does your PR follow the maintainer guide?
Yes.

Yes.

@BillyONeal I think this will unblock the cppgraphqlgen port with the latest CI baselines/VMs.

OK, I pushed a commit to remove those from the baseline then. I didn't remove the Linux one since the comment there says it's about newer GCC needed rather than older.

Thanks for such a quick fix!


Update Action Testing

Most components require testing for their functionality - typically found in the actions.js folders.
A lot of features have been added lately and the tests need to be keeping up.
Refer to #122 for a starting point.

Hacktoberfest:
This issue can provide for multiple pull requests.

I'd like to try this. Please assign it to me

I was thinking more about an integrations test approach, where we mock the activity of a user to make sure changes don't necessarily alter that functionality. So, for instance, if the ContractEditor has a clause template in it:

is the user unable to edit text?
Is the user able to edit the variables?
can the user click on a conditional variable?

Related to #336

Closing for https://github.com/accordproject/web-components/issues/15


Entry point wrong for k8s container images

What happened:
Entry point wrong for kube-scheduler image
What you expected to happen:
To run kube-scheduler
How to reproduce it (as minimally and precisely as possible):
% docker run  public.ecr.aws/eks-distro/kubernetes/kube-scheduler:v1.22.15-eks-1-22-13
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/usr/local/bin/go-runner": stat /usr/local/bin/go-runner: no such file or directory: unknown.
ERRO[0000] error waiting for container: context canceled

Anything else we need to know?:
works
docker run --entrypoint kube-scheduler public.ecr.aws/eks-distro/kubernetes/kube-scheduler:v1.22.15-eks-1-22-13

Environment:

EKS Distro Release Channel:
EKS Distro Release: 1.22

from https://github.com/aws/eks-distro/blob/main/projects/kubernetes/kubernetes/docker/Dockerfile#L26

Can you please tell me exactly which files needs to be updated for api-server?


Type excluded from validation still honors the IValidatableObject implementation on the type.

For the following setup:
public class Customer
{
    public int Id { get; set; }

    [Required]
    [MaxLength(5)]
    public string Name { get; set; }

    public Address Address { get; set; }
}
public class Address : IValidatableObject
{
    public string City { get; set; }

    public string State { get; set; }

    public IEnumerable<ValidationResult> Validate(ValidationContext validationContext)
    {
        return new[] { new ValidationResult("Something went wrong, bro!") };
    }
}
//-------------------------------
public class CustomersController : Controller
{
    public IActionResult Create(Customer customer)
    {
        if (!ModelState.IsValid)
        {
            return HttpBadRequest(ModelState);
        }

        return Json(customer);
    }
}
//------------------------------
services.ConfigureMvc(options =>
{
    options.ValidationExcludeFilters.Add(typeof(Address));
});

Following is the current behavior:
Request
POST http://localhost:24628/Customers/Create HTTP/1.1
User-Agent: Fiddler
Content-Type: application/x-www-form-urlencoded
Host: localhost:24628
Content-Length: 54

Id=100&Name=John&Address.City=Redmond&Address.State=WA

Response
HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=utf-8
Server: Microsoft-IIS/10.0
X-SourceFiles: =?UTF-8?B?RDpcVmVyaWZ5TW9kZWxWYWxpZGF0aW9uVW5pZmljYXRpb25cU2FtcGxlV2ViQXBwXHNyY1xTYW1wbGVXZWJBcHBcd3d3cm9vdFxDdXN0b21lcnNcQ3JlYXRl?=
X-Powered-By: ASP.NET
Date: Wed, 01 Apr 2015 22:09:41 GMT
Content-Length: 42

{"Address":["Something went wrong, bro!"]}

Expected: Since the type Address was excluded from validation, we shouldn't ideally honor the IValidatableObject implementation?

This also happens with a ValidationAttribute implementation. Example type:
public class Customer
{
    public int Id { get; set; }

    [Required]
    [MaxLength(5)]
    public string Name { get; set; }

    [AddressValidator]
    public Address Address { get; set; }
}

public class AddressValidator : ValidationAttribute
{
    protected override ValidationResult IsValid(object value, ValidationContext validationContext)
    {
        return new ValidationResult("Something went wrong, bro!");
    }
}

A slightly unusual scenario because why would the type even implement IValidatableObject if it wasn't going to be validated. Nevertheless, a valid bug.

Right, the scenario was more from point that the type having the validation is not owned by the user using in his application.

Yeah, it would just seem odd that someone would bother implementing validation logic on something that shouldn't be validated in a scenario (even though the two types are owned by different people). It's certainly possible, but seems odd.

@rynowak please check this out, bro.

Investigated this, clearing triage with results.
Really, it's clear from looking at the code that the intent of the implementation is to exclude the properties of the type from validation.
Ex:
public class MyModel
{
    [Required]
    [MyValidationAttribute(Message = "Validator1")]
    public MySpecialType Special { get; set; }
}

[MyValidationAttribute(Message = "Validator2")]
public class MySpecialType
{
    [MyValidationAttribute(Message = "Validator3")]
    public int Id { get; set; }
}

If you exclude MySpecialType from validation, then the validators on MyModel.Special and MyspecialType will run, and the validators on MySpecialType.Id will never run. We ask the validation system for validators for MyModel.Special and 3 will be returned (1 instance of Required and 2 instances of MyValidationAttribute.
Like was mentioned above, it's a wierd scenario. Asking for validators for a property gives you validators on the property itself, and on the property's type, and I don't think we want to change that. There's nothing unexpected going on in the code, it's doing what it's intended to do.
Recommend won't fix and updating the docs to reflect the real behavior.

@rynowak Is there any particular reason not to change this behavior? My intuition is that if I exclude a type from validation then none of the validators on the type should ever get run.

@rynowak Is there any particular reason not to change this behavior?

There's no reason we can't/shouldn't as long as we don't impact more-primary scenarios.
Is the intent to run validators on the property but not the type or to skip all validation?
If the former, it w ill require some extra plumbing that we don't currently have, as we currently look for all validators on both the property and type all the time. If the latter, it's very easy to fix.

@rynowak are you talking about a scenario such as:
  public class Model
  {
    [Required]
    public IFormFile File { get; set; }
  }

?
If so, I suggest applying the RequiredAttribute makes sense even though the IFormFile type is excluded from validation. Realize this is a bit more difficult but, fortunately, we already maintain the property and type attributes separately. So we're well on the way to maintaining the validators separately :smiling_imp:

@rynowak it's the former - respecting just the validation on the property declaration itself. That would seem to be the most logical approach, even if it's perhaps difficult to implement. (I'm not strongly suggesting we change anything; I'm merely arguing for what I think is the most logical/correct.)

(I'm not strongly suggesting we change anything; I'm merely arguing for what I think is the most logical/correct.)

It comes back to an earlier discussion we had. An exclude filter (in it's current form), just basically serves to stop traversal of the model graph, for things that have properties but aren't interesting for validation.
If you're using an exclude filter for a type that you attached validators to, then that's a bit strange.

Maybe it's just the wrong feature then... let's discuss tomorrow.

If you're using an exclude filter for a type that you attached validators to, then that's a bit strange.

What about Required? What about a case where I normally don't care about validating a particular type, but in one exceptional case I do? Or what if I don't like the validation logic on a type I don't control and I want to override it for just one particular case?

[Required] only applies to properties. Using [Required] on a property with an excluded type will perform validation.

After having discussed this at length let's just close this issue and leave the property as is. The property was added for a very specific use case and is not worth generalizing. The semantics of the property can be clarified in the API ref docs.


Extra slash included in URL paths

I'm using Readeck 0.15.3, Freshrss 1.24.3, and I'm trying to set up this extension. After creating my API token and pasting it in the extension settings, I found that attempting to connect failed with a HTTP 308. I looked in my Readeck logs and found that the request was sent to the path /api//profile instead of the expected /api/profile. I opened the button controller class and edited the URL fragment, changing it from /profile to profile.
https://github.com/Joedmin/xExtension-readeck-button/blob/bba60680e3c06cd64365e855acc258c616aac23a/Controllers/readeckButtonController.php#L46
After making this change, I was able to log in, but I could not save any items in Readeck as other actions are using the double slash, the POST request to /api//bookmarks is now also failing with a 308. It would be nice if Readeck's router filtered out the extra slashes but it seems that it rejects them.
time="2024-10-30T05:38:10Z" level=info msg=http @id=boxxie/VkKQuDNrGc-000442 elapsed_ms=0.07885 http_method=GET http_proto=HTTP/1.1 length=65 path=/api//profile remote_addr=<IP_ADDRESS> status=308 ua=
time="2024-10-30T05:44:48Z" level=info msg=http @id=boxxie/VkKQuDNrGc-000445 elapsed_ms=0.968694 http_method=GET http_proto=HTTP/1.1 length=494 path=/api/profile remote_addr=<IP_ADDRESS> status=200 ua=

time="2024-10-30T05:46:08Z" level=info msg=http @id=boxxie/VkKQuDNrGc-000451 elapsed_ms=0.051613 http_method=POST http_proto=HTTP/1.1 length=0 path=/api//bookmarks remote_addr=<IP_ADDRESS> status=308 ua=

Hello, thank you for reporting this issue. I must say I did not notice this isse, it's working fine for me (i gues Apache somehow handles this). I'm releasing a new version with this fix.

Can confirm it's fixed in 0.6, thank you for the quick turnaround!


[bundler] Bundled output contains exports from file URLs

When building https://github.com/PolymerLabs/polymer-redux-hn with polymer build and the included polymer.json, build/esm-bundled/src/components/hn-item.js contains this:
import{...,fetchItemIfNeeded,loadFavorites,...,currentItemSelector,...}from"./hn-app.js";
export{fetchItemIfNeeded}from"file:///Users/keanulee/Code/PolymerLabs/polymer-redux-hn/src/actions/items.js";
export{currentItemSelector}from"file:///Users/keanulee/Code/PolymerLabs/polymer-redux-hn/src/reducers/items.js";

...

var hnItem={HnItemElement:HnItemElement,currentItemSelector:currentItemSelector,fetchItemIfNeeded:fetchItemIfNeeded};
export{...,HnItemElement};

The source of hn-item.js exports fetchItemIfNeeded and currentItemSelector, but those two functions are already imported:
import { ..., fetchItemIfNeeded } from '../actions/items.js';
import ..., { currentItemSelector } from '../reducers/items.js';

...

export { currentItemSelector, fetchItemIfNeeded };

Expected
The export from file URL statements shouldn't be there as they aren't needed.

Resolved for now.


Minor spelling issues on the website

Describe the bug
"Performance" is spelled as "performence" on the website
To Reproduce
Steps to reproduce the behavior:

Go to https://theultimatefoxos.dev/
Read the first sentence

Expected behavior
Expected that Performance would be wrote correctly
Additional context
TLDR: Performance isn't correctly spelled in the first sentence

Thanks for the report it should be fixed now.


Portuguese (pt-br) Translation

Hi!
This seems to be a good hit in Brazil. There's no much content in Portuguese for ASP.NET Core. Since English is not so widespread there, I believe a bunch of devs can benefit from it. Even if they know English, a pt-br version would be optimal for some.
I could help translating it.. just let me know if you are interested.. and we could proceed from that.
Cheers.

I would love to have a Portuguese translation! I just released a new version (1.1) that includes a lot of copy changes so now is a great time to perform the translation. Let me know how I can help.
I'm curious, do you know how folks in Brazil finding the book?

Cool! I have some limited time, but I'm definitely excited in working on this!
Since this is new to me, maybe you can fill me in on how was the coordination for the other translations? I was thinking on creating a pt-br branch where I would work. Of course, keep merging in master or whatever branch has new things.. until it's released?
Hum.. probably through just googling, but in Portuguese! I know bunch of people devs that still Google stuff in Portuguese.. so if we manage to 'disseminate' the contents of the book in Portuguese, via blogs or other channels... people will find it in the end. I have a blog, so I can definitely write a post and share with my network, which is not much but.. it's a start :).

I liked your idea on #35, could pursue like that. Not sure about the Gitbook part though. Do you want to keep them all in the same project, or should I host it on my personal account like the others did?

The gitbook stuff is a little weird, but we can figure that out later. I think a fork + branch is the best approach, like this one: https://github.com/windsting/little-aspnetcore-book (see branch master and zh-cn).
The hard/time-consuming part is translating it. I can help with publishing and gitbook stuff when it's ready!

Yeah, I just spent 1 hour on Gitbook. It's a mess. I did the integration on the new Gitbook, since cannot create account in the legacy anymore. I managed to import my pt-br branch into it.. but it did lot's of changes.
Just gonna give up for now on setting up Gitbook, and will only focus on translating it.

Ugh, sorry about that. If you do the translation in a fork, then we can figure all that stuff out later. 👍

No worries. Will keep this updated :).

@joaopgrassi, do you need help to translate this book?
I can help you!

Yes, I think splitting by chapter.
Can we use Project board in your project?
Just to see all pending chapters...

That's a good idea. I'll add a project board.. and you as contributor. Since I didn't started anything.. you can pick any chapter.. but first I would need to create all tasks on the board.. maybe I can do it this weekend. We'll have to find a chat so we don't spam everyone here. Skype's cool for you?

Ok so @nicolastarzia I added a project for the translation.. and also created issues so we assign to ourselves and have a nice track of who's doing what. Thanks for the idea! Also, I need you guys specially @nicolastarzia  to check this: https://github.com/joaopgrassi/little-aspnetcore-book/issues/11. I need your opinion on the Title of the book in Portuguese.

Hi guys
I'm looking for projects that need translation. If I can, please let me know. I am not an expert, but I believe that with your supervision everything will work out.

@joao-marcos See @joaopgrassi's fork here: https://github.com/joaopgrassi/little-aspnetcore-book/issues
He's got issues defined for translating each chapter of the book. Check with him to see if he needs help!

Nice! @joaopgrassi if theres no problem, I can take the chapter "MVC basics", ok?

@joao-marcos any help is welcome :). Please, fork my fork of the book, and make sure you branch out of https://github.com/joaopgrassi/little-aspnetcore-book/tree/pt-br branch. I'm using a pattern for the branch names, of chapter/{chapter_name}. See the one I'm working on for an example.
Also, make sure you assign yourself the issue and update it accordingly in the project board.
When you are ready, create a pull request so we can review it.
Thanks.

Also, I think it's a good idea to merge the pt-br branch into your branch to avoid merge conflicts. This way it's always a fast-forward.

All right! Thank you

I forked your fork and I will start to translate "add-external-packages" chapter first.

@oliveiramarcio see my previous comment for @joao-marcos on how to get started. I will add you as a contributor.. so you assign the chapter ticket to yourself and move the tickets on the project. But before you start, I would assign you to review the chapter that I translated and it's pending review. Can you do that?

Also @oliveiramarcio that chapter is already picked by @nicolastarzia. Always check the board to see who's doing what. https://github.com/joaopgrassi/little-aspnetcore-book/projects/1

Hi @joaopgrassi!
I'll review the "introduction" chapter and report you soon.
The after the review I'll start translating "add-external-packages" chapter.

Cool. I've sent you a collaborator invite. Once you accept, you can assign the ticket to you and move it on the board. Thanks!

Hey all. It's been a while since we started on the pt-BR translations. As always, things happen and a lot has changed since I started with this project. Unfortunately, I don't think I can contribute more as my time is limited and I'm swamped with other stuff atm. To not lose all hard work we've done, I
transferred the fork to @nicolastarzia, so you guys can continue working on this.
I would like to thank you all that helped to translate it so far, and I'm sorry for not having been much active on it.

Thank you @joaopgrassi, you made a good job.
When you have some time, would be awesome that you can translate with us! :v:

Hi Guys!
Is this translation work still on going? Would you be willing to accept an extra pair of hands on the work? I had never worked on such project before, but I would love to learn to help on the job to translate it to Brazilian portuguese, as I understood this book would be of great help to some non-english enthusiasts.


Conflict between Homebridge-Wink (and Wink3) vs Homebridge-hue

Issue
Hello !
Since a few days, I have a conflict between whatever Wink plugin I'm using and Homebridge-hue.
Here's the log message below. Let me know if I can do something else.
Thanks !
Log Messages
[2020-3-14 13:34:17] [Hue] Philips hue 2.0: bridge request 1: get /
[2020-3-14 13:34:17] [Hue] Philips hue 2.0: bridge communication error: TypeError [ERR_INVALID_ARG_TYPE]: The "listener" argument must be of type function. Received an instance of Object
    at checkListener (events.js:109:11)
    at ClientRequest.once (events.js:431:3)
    at new ClientRequest (_http_client.js:194:10)
    at Object.request (https.js:314:10)
    at Object.<anonymous> (C:\Users\julie\AppData\Roaming\npm\node_modules\homebridge-wink-schmittx\node_modules\agent-base\patch-core.js:25:22)
    at Object.request (C:\Users\julie\AppData\Roaming\npm\node_modules\homebridge-wink-schmittx\node_modules\socks-proxy-agent\node_modules\agent-base\patch-core.js:23:20)
    at HttpClient.request (C:\Users\julie\AppData\Roaming\npm\node_modules\homebridge-hue\node_modules\homebridge-lib\lib\HttpClient.js:226:32)
    at HueClient._request (C:\Users\julie\AppData\Roaming\npm\node_modules\homebridge-hue\lib\HueClient.js:351:41)
    at HueBridge.request (C:\Users\julie\AppData\Roaming\npm\node_modules\homebridge-hue\lib\HueBridge.js:1109:43)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async HueBridge.getFullState (C:\Users\julie\AppData\Roaming\npm\node_modules\homebridge-hue\lib\HueBridge.js:316:17)
    at async HueBridge.accessories (C:\Users\julie\AppData\Roaming\npm\node_modules\homebridge-hue\lib\HueBridge.js:93:19)
    at async Promise.all (index 0)
    at async HuePlatform.accessories (C:\Users\julie\AppData\Roaming\npm\node_modules\homebridge-hue\lib\HuePlatform.js:310:29)

See #652.


Loosing Slim\App & Di\Container in callback context (Action)

Hi everyone,
I'm a beginner on Slim Framework, which is really great so far :-)
Did someone else loosing capability to use Slim\App or Di\Container in Models/Action(s) ?
Why Strategies don't inject Di into callbacks ? like :
public function __invoke(
  callable $callable,
  Di\Container $container,
  ServerRequestInterface $request,
  ResponseInterface $response,
  array $routeArguments
) {
    // [...]
    return call_user_func($callable, $container, $request, $response, $routeArguments);
    }

An Action could look like this...
class MyAction {
    public __construct( ... my DI stuff )  { }

    public function __invoke($request, $response, $args)  {
        return $response;
    }
}

@geggleto Well, it's Slim\CallableResolver which construct our Callable via Strategies with ($request, $response, $args). So __construct() with no arguments right ?

@orykami Actually, CallableResolver will pass the container into the construct when it creates it: https://github.com/slimphp/Slim/blob/3.x/Slim/CallableResolver.php#L64

Note that this is not available in 3.0.0-RC1.

@akrabat I'm on 3.0.0-RC1, that's why i mentionned it.

@orykami this will be in RC2 which will be out over the weekend or next week, just need to finalise some bits with @akrabat.


⚠ api.piste.gouv.fr healthcheck has degraded performance

In 659c909, api.piste.gouv.fr healthcheck (https://api.piste.gouv.fr/cassation/judilibre/v1.0/healthcheck) experienced degraded performance:

HTTP code: 200
Response time: 4599 ms

Resolved: api.piste.gouv.fr healthcheck performance has improved in 20a95d1.


Disable debugging logs

Hello,
I'd like a way to disable the debug logging that is spamming the console. It looks like there is a _DEBUG_ flag, but it seem to be hardcoded to true, with no way that i could find to disable it.
Is there a solution that i'm missing ? :)
Thanks a lot !

Hi,
You are right and I am removing this flag as I already did externalize this part of code (in a proper ES6 module) that I need to commit. I have also converted most console.log to console.timeStamp in order to see them inside devtools performance inspector panel (i.e. only useful for HbbTV developers)
Regards.


Bug: trsync_manager crashes when doing a permanent delete

Hi,
When I do a "permanent delete" (introduced in Tracim 4.9.0) from the web interface, trsync_manager crashes with the following messages:
[2024-10-17T20:24:33Z INFO  trsync::remote::watcher] remote event : content.deleted.html-document (14642)
[2024-10-17T20:24:33Z INFO  trsync::run2] Proceed event Remote(Deleted(ContentId(14642)))
[2024-10-17T20:24:33Z INFO  trsync::remote::watcher] remote event : content.deleted.html-document (14642)
[2024-10-17T20:24:33Z INFO  trsync::run2] [my.tracim.fr::682] Set activity to ☁❌ ?
[2024-10-17T20:24:33Z INFO  trsync::operation::operator] Proceed event : Remote(Deleted(ContentId(14642)))
[2024-10-17T20:24:33Z INFO  trsync::run2] [my.tracim.fr::682] Set activity to En veille
[2024-10-17T20:24:33Z INFO  trsync::run2] Proceed event Remote(Deleted(ContentId(14642)))
[2024-10-17T20:24:33Z INFO  trsync::run2] [my.tracim.fr::682] Set activity to ☁❌ ?
[2024-10-17T20:24:33Z INFO  trsync::operation::operator] Proceed event : Remote(Deleted(ContentId(14642)))
[2024-10-17T20:24:33Z ERROR trsync::run2] Operate error : Operator error: Executor error: Unexpected error: Expect content 14642
[2024-10-17T20:24:33Z INFO  trsync::run2] [my.tracim.fr::682] Set activity to Erreur

To be precise, It does not really crashes (because the process stays running), but it can not sync anything until being restarted.
It does not happen when I do a "classical delete" from the web interface:
[2024-10-17T20:32:58Z INFO  trsync::remote::watcher] remote event : content.deleted.file (143299)
[2024-10-17T20:32:58Z INFO  trsync::run2] Proceed event Remote(Deleted(ContentId(143299)))
[2024-10-17T20:32:59Z INFO  trsync::run2] [my.tracim.fr::682] Set activity to ☁❌ my_file-deleted-2024-10-17T<IP_ADDRESS>7309.ods
[2024-10-17T20:32:59Z INFO  trsync::operation::operator] Proceed event : Remote(Deleted(ContentId(143299)))
[2024-10-17T20:32:59Z INFO  trsync::run2] [my.tracim.fr::682] Set activity to En veille
[2024-10-17T20:33:00Z INFO  trsync::run2] Proceed event Local(DiskEventWrap("test.ods", Deleted("test.ods")))
[2024-10-17T20:33:00Z INFO  trsync::run2] [my.tracim.fr::682] Set activity to 🖴❌ test.ods
[2024-10-17T20:33:00Z INFO  trsync::operation::operator] Ignore event (planned ignore) : Local(DiskEventWrap("test.ods", Deleted("test.ods")))
[2024-10-17T20:33:00Z INFO  trsync::run2] [algoo.tracim.fr::682] Set activity to En veille

Will take a look thanks !


add WebXRDomOverlay information

please wait for next release (alpha.23) when available on NPM before merging.

I think this belongs in the AR features more than here. What do you think?

I think this belongs in the AR features more than here. What do you think?

Absolutely - I definitely put in wrong place. Will move it to https://doc.babylonjs.com/divingDeeper/webXR/webXRARFeatures


Backport 2.7: Reduce the timing tests complexity

This is a backport of #2383

@hanno-arm please give this a review.

@hanno-arm ping for review - this is a longstanding painful issue and your review on backports is the last step required before it's ready for merge


Closed state for posts.

Post must contain flag/state, indicating that it's closed. If it's true, there must be simplified upvote/downvote logic, which allows action and exits early: just after storing new weight value (non-consensus). Add this logic.

[x] Add state field to post object
[x] Change state to "closed" on payout
[ ] Exit set_vote early (after get_post) if state is "closed", update vote object:

modify existing vote object or create new one
don't check count and previous weight
set count to -1

#115


Stack using Priority Queue

Issue  #379
✔ Check List (Check all the applicable boxes)
My code follows the code style of this project.
This PR does not contain plagiarized content.
The title of my pull request is a short description of the requested changes.
##Problem Statement
Here we will take the numbers input from user and with the help of priority queue we need to implement stack.
Priority queue is a special type of queue in which the numbers are dequeue based on their priority. Every no has some priority along with its data.
The data having the highest priority is popped first.
In priority queue, we assign priority to the elements that are being pushed. A stack requires elements to be processed in Last in First Out manner.
The idea is to associate a count that determines when it was pushed. This count works as a key for the priority queue. So the implementation of
stack uses a priority queue of pairs, with the first element serving as the key.
For ex:
User enters input : 4 1 2
so in queue -> [(2,3) (1,2) (4,1)]
📷 Screenshots
Output for program in C

Output for program in C++

Output for program in Java

Output for program in Python

Kindly mention issue number as hyperlink to your issue

I have mention the issue as hyperlink.
Please kindly check.


pip-Installable package

Changes the folders structure separating the Tools and the Runtime+Stdlib. Allows to test and publish both parts separately. The Tools are tested via pytest, not the Makefile.
The Tools are to be published as grumpy-tools package and Runtime as grumpy-runtime package.
TODO:

[X] Publish-able on Python Package Index (PyPI)
[x] Update the README
[x] Better way to bump the version then editing files. (Maybe via bumpversion?)
[x] ~Fix a find: 'compiler': No such file or directory Makefile warning~

I gave up on find: 'compiler': No such file or directory. Too little make skills here; too advanced Makefile there.
Contributions on this front are appreciated ;)
I do consider this PR merge-able.


Internal Server Error

Describe the bug
Please provide as much information as you can.
Did this error occur while using dotnet try or online?

[x] dotnet-try
[ ] online

What kind of error was it?

[x] User Interface (UI):  For example the output never displayed
[x] Service Error: For example "The service is temporarily unavailable. We are working on it"
[ ] Other:

Screenshots
If applicable, add screenshots to help explain your problem.

Please complete the following:

OS

[ ] Windows 10
[x] macOS
[ ] Linux (Please specify distro)
[ ] iOS
[ ] Android

Browser

[x] Chrome
[ ] Edge
[ ] Safari

Which version of dotnet try are you using?

@jonsequitur  --version 1.0.19553.4

Same issue with me in Windows 10, Chrome Browser, version 1.0.19553.4
Error found in Console:

@logeshpalani98 try using microsoft.dotnet-try, had the same issue which got resolved by updating the package.

I am also having this same issue and have the most up to date version

@DylPickle11 Could you post the results of dotnet --info and dotnet tool list -g?

@jonsequitur
Absolutely! .NET Core SDK (reflecting any global.json):
Version:   3.1.402
Commit:    9b5de826fd
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.14
OS Platform: Darwin
Base Path:   /usr/local/share/dotnet/sdk/3.1.402/
Host (useful for support):
Version: 3.1.8
Commit:  9c1330dedd
.NET Core SDKs installed:
3.0.100 [/usr/local/share/dotnet/sdk]
3.1.301 [/usr/local/share/dotnet/sdk]
3.1.402 [/usr/local/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.0.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.5 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.8 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.19 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.22 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.8 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

dotnet tool list -g
Package Id                Version          Commands
microsoft.dotnet-try      1.0.20268.1      dotnet-try

Try with uninstalling dotnet try and reinstall it with:
> dotnet tool install -g --add-source "https://dotnet.myget.org/F/dotnet-try/api/v3/index.json" Microsoft.dotnet-try
CC: @colombod


fix: 🐛 allow useFileUpload to be reused

Fixes https://github.com/nhost/nhost/issues/865

Codecov Report

Merging #1459 (8568354) into main (812a6e5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1459   +/-   ##
=======================================
  Coverage   85.92%   85.92%
=======================================
  Files          83       83
  Lines        9236     9236
  Branches      498      498
=======================================
  Hits         7936     7936
  Misses       1300     1300

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


SSCS-10766 - Create Set Aside Granted Document  - CALL

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/SSCS-10766
Change description
Changes to ccd-def to allow postHearingReview actions for particular users (see auth changes).
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

missing version bump


refactor: use pre-commit with some opinonated linters

fixes #33

Sure, exclusion is not problem. I'll have a look,later.