fix(ios): fix multiple instances of same device object during ble scan

Allowing duplicates for ble scanning on ios is messing up the peripheral delegate callbacks due to the construction of a new Device object on every discovery callback. This leads to timeouts in all kinds of callbacks inside the Device class if the scan stays active during connecting, because only the most recent Device instance gets the peripheral callbacks.
This proposed fix only constructs a single Device object per peripheral.
For debugging purposes we have added some logs that clearly show this issue.
⚡  To Native ->  BluetoothLe initialize 111738470
⚡  [log] - start scanning
⚡  To Native ->  OverlayCamera stopPreview 111738471
⚡  TO JS undefined
⚡  BluetoothLe - Resolve initialize BLE powered on
⚡  TO JS undefined
⚡  To Native ->  BluetoothLe addListener 111738472
⚡  To Native ->  BluetoothLe requestLEScan 111738473
⚡  BluetoothLe - Resolve startScanning Scan started.
⚡  TO JS undefined
[BLE] Device 5FBB58D1-47F1-40A5-A3ED-FE394CF27629 initialized for name: IMU_8e3f7f
⚡  BluetoothLe - New device found:  IMU_8e3f7f
⚡  TO JS {"rssi":-60,"localName":"IMU_8e3f7f","uuids":["80030001-e629-4c98-9324-aa7fc0c66de7"],"txPower":127,"manufacturerData":{"89":"01 00 64 63 "},"device":{"deviceId":"38E794BA-6B6F-BD3F-6501-29C6BA367A52","name":"IMU_8e3f7f"}}
⚡  [log] - received new scan result: {"rssi":-60,"localName":"IMU_8e3f7f","uuids":["80030001-e629-4c98-9324-aa7fc0c66de7"],"txPower":127,"manufacturerData":{"89":{}},"device":{"deviceId":"38E794BA-6B6F-BD3F-6501-29C6BA367A52","name":"IMU_8e3f7f"}}
[BLE] Device 1B988F6D-838F-4FCA-A0CD-49C991B6988F initialized for name: IMU_8e3f7f
⚡  BluetoothLe - New device found:  IMU_8e3f7f
⚡  TO JS {"uuids":["80030001-e629-4c98-9324-aa7fc0c66de7"],"localName":"IMU_8e3f7f","device":{"name":"IMU_8e3f7f","deviceId":"38E794BA-6B6F-BD3F-6501-29C6BA367A52"},"rssi":-65,"txPower":127,"manufacturerData":{"89":"01 00 64 63 "}}
⚡  [log] - received new scan result: {"uuids":["80030001-e629-4c98-9324-aa7fc0c66de7"],"localName":"IMU_8e3f7f","device":{"name":"IMU_8e3f7f","deviceId":"38E794BA-6B6F-BD3F-6501-29C6BA367A52"},"rssi":-65,"txPower":127,"manufacturerData":{"89":{}}}
⚡  [log] - Babylon.js v6.25.0 - WebGL2 - Parallel shader compilation
[BLE] Device 6E6C243C-C347-42FF-A8BC-A1F6C6975E45 initialized for name: IMU_8e3f7f
⚡  BluetoothLe - New device found:  IMU_8e3f7f
⚡  TO JS {"rssi":-63,"uuids":["80030001-e629-4c98-9324-aa7fc0c66de7"],"localName":"IMU_8e3f7f","manufacturerData":{"89":"01 00 64 63 "},"txPower":127,"device":{"deviceId":"38E794BA-6B6F-BD3F-6501-29C6BA367A52","name":"IMU_8e3f7f"}}
[BLE] Device A73FD2F9-4707-42E9-9E17-2FB565803FC6 initialized for name: IMU_8e3f7f
⚡  BluetoothLe - New device found:  IMU_8e3f7f
⚡  TO JS {"rssi":-63,"device":{"name":"IMU_8e3f7f","deviceId":"38E794BA-6B6F-BD3F-6501-29C6BA367A52"},"uuids":["80030001-e629-4c98-9324-aa7fc0c66de7"],"manufacturerData":{"89":"01 01 64 61 "},"txPower":127,"localName":"IMU_8e3f7f"}
⚡  [log] - received new scan result: {"rssi":-63,"uuids":["80030001-e629-4c98-9324-aa7fc0c66de7"],"localName":"IMU_8e3f7f","manufacturerData":{"89":{}},"txPower":127,"device":{"deviceId":"38E794BA-6B6F-BD3F-6501-29C6BA367A52","name":"IMU_8e3f7f"}}
⚡  [log] - received new scan result: {"rssi":-63,"device":{"name":"IMU_8e3f7f","deviceId":"38E794BA-6B6F-BD3F-6501-29C6BA367A52"},"uuids":["80030001-e629-4c98-9324-aa7fc0c66de7"],"manufacturerData":{"89":{}},"txPower":127,"localName":"IMU_8e3f7f"}
⚡  To Native ->  BluetoothLe addListener 111738474
⚡  To Native ->  BluetoothLe connect 111738475
[BLE] 2023-11-01 12:28:02 +0000 callbackMap of device A73FD2F9-4707-42E9-9E17-2FB565803FC6 contains keys: ["connect"]
[BLE] 2023-11-01 12:28:02 +0000 timeout for key connect created
⚡  BluetoothLe - Connecting to peripheral <CBPeripheral: 0x6000026ae220, identifier = 38E794BA-6B6F-BD3F-6501-29C6BA367A52, name = IMU_8e3f7f, mtu = 0, state = disconnected>
[BLE] Device 4FE917F2-A89B-473F-8558-62870CD8E8F5 initialized for name: IMU_8e3f7f
⚡  BluetoothLe - New device found:  IMU_8e3f7f
⚡  TO JS {"manufacturerData":{"89":"01 01 64 61 "},"txPower":127,"uuids":["80030001-e629-4c98-9324-aa7fc0c66de7"],"localName":"IMU_8e3f7f","rssi":-64,"device":{"deviceId":"38E794BA-6B6F-BD3F-6501-29C6BA367A52","name":"IMU_8e3f7f"}}
⚡  [log] - received new scan result: {"manufacturerData":{"89":{}},"txPower":127,"uuids":["80030001-e629-4c98-9324-aa7fc0c66de7"],"localName":"IMU_8e3f7f","rssi":-64,"device":{"deviceId":"38E794BA-6B6F-BD3F-6501-29C6BA367A52","name":"IMU_8e3f7f"}}
⚡  BluetoothLe - Connected to device <CBPeripheral: 0x6000026ae220, identifier = 38E794BA-6B6F-BD3F-6501-29C6BA367A52, name = IMU_8e3f7f, mtu = 247, state = connected>
⚡  BluetoothLe - Resolve connect|38E794BA-6B6F-BD3F-6501-29C6BA367A52 Successfully connected.
⚡  BluetoothLe - Connected to peripheral. Waiting for service discovery.
⚡  BluetoothLe - didDiscoverServices
⚡  BluetoothLe - didDiscoverCharacteristicsFor 1 1
[BLE] More services: 1/1 characteristics: 0 / 2 have to be discovered
[BLE] More services: 1/1 characteristics: 1 / 2 have to be discovered
[BLE] Enough services and characteristics found
[BLE] 2023-11-01 12:28:03 +0000 Resolve for key connect in device 4FE917F2-A89B-473F-8558-62870CD8E8F5 ... Valid keys: []
[BLE] no callback for key connect
[BLE] 2023-11-01 12:28:03 +0000 Resolve for key discoverServices in device 4FE917F2-A89B-473F-8558-62870CD8E8F5 ... Valid keys: []
[BLE] no callback for key discoverServices
[BLE] 2023-11-01 12:28:13 +0000 Reject for key connect in device A73FD2F9-4707-42E9-9E17-2FB565803FC6 ... Valid keys: ["connect"]
⚡  BluetoothLe - Reject connect Connection timeout
[BLE] 2023-11-01 12:28:13 +0000 callbackMap of device A73FD2F9-4707-42E9-9E17-2FB565803FC6 contains keys: []
[BLE] 2023-11-01 12:28:13 +0000 timeout for key connect cancelled
ERROR MESSAGE:  {"message":"Connection timeout","errorMessage":"Connection timeout"}
⚡  [error] - {"message":"Connection timeout","errorMessage":"Connection timeout"}

may be related to #530

Thank you for this fix!


sdr2mqtt stops reporting due to error

Out of the blue this error starting occuring and ive only realized it due to uptime kuma that ive setup letting me know. This is a screen shot of whats happening in the logs.

same problem
DEBUG:Received Device Data from SDR and sent to MQTT: rtl_433/events : {"time": "2024-09-30 21:30:53+0300", "protocol": 17, "model": "Cardin-S466", "dipswitch": "---+-oo+-", "rbutton": "00L?", "mod": "ASK", "freq": 433.97059, "rssi": -5.21573, "snr": 12.84607, "noise": -18.0618} Exception in thread Thread-1 (_thread_main): Traceback (most recent call last):   File "/usr/lib/python3.12/threading.py", line 1075, in _bootstrap_inner     self.run()   File "/usr/lib/python3.12/threading.py", line 1012, in run     self._target(*self._args, **self._kwargs)   File "/usr/lib/python3.12/site-packages/paho/mqtt/client.py", line 3591, in _thread_main     self.loop_forever(retry_first_connection=True)   File "/usr/lib/python3.12/site-packages/paho/mqtt/client.py", line 1756, in loop_forever     rc = self._loop(timeout)          ^^^^^^^^^^^^^^^^^^^   File "/usr/lib/python3.12/site-packages/paho/mqtt/client.py", line 1164, in _loop     rc = self.loop_read()          ^^^^^^^^^^^^^^^^   File "/usr/lib/python3.12/site-packages/paho/mqtt/client.py", line 1556, in loop_read     rc = self._packet_read()          ^^^^^^^^^^^^^^^^^^^   File "/usr/lib/python3.12/site-packages/paho/mqtt/client.py", line 2439, in _packet_read     rc = self._packet_handle()          ^^^^^^^^^^^^^^^^^^^^^   File "/usr/lib/python3.12/site-packages/paho/mqtt/client.py", line 3033, in _packet_handle     return self._handle_publish()            ^^^^^^^^^^^^^^^^^^^^^^   File "/usr/lib/python3.12/site-packages/paho/mqtt/client.py", line 3327, in _handle_publish     self._handle_on_message(message)   File "/usr/lib/python3.12/site-packages/paho/mqtt/client.py", line 3570, in _handle_on_message     on_message(self, self._userdata, message)   File "/scripts/rtl_433_mqtt_hass.py", line 593, in mqtt_message     bridge_event_to_hass(client, msg.topic, data)   File "/scripts/rtl_433_mqtt_hass.py", line 667, in bridge_event_to_hass     logging.warning("Device Id:{} doesn't appear to be a actual device. Skipping..".format(data['id']))                                                                                ~~~~^^^^^^ KeyError: 'id'


Change "tools" on wiki edit page to "capabilities"

Change "tools" on wiki edit page to "capabilities"

marking as fixed


Status code extension

I propose two status code extensions:
/* ---------------------------------------------------------------------------------------------- */
/* Status codes (general purpose) - extensions                                                    */
/* ---------------------------------------------------------------------------------------------- */

/**
 * The operation failed with an unexpected error.
 */
#define ZYAN_STATUS_UNEXPECTED ZYAN_MAKE_STATUS(1u, ZYAN_MODULE_ZYCORE, 0xFFFFu)

/**
 * The operation was not implemented.
 */
#define ZYAN_STATUS_NOT_IMPLEMENTED ZYAN_MAKE_STATUS(1u, ZYAN_MODULE_ZYCORE, 0x78u)

p.s. there was also a typo in the comments of Zycore/Status.h:
 /**
- * The operation failed with an generic error.
+ * The operation failed with a generic error.
  */
 #define ZYAN_STATUS_FAILED \
     ZYAN_MAKE_STATUS(1u, ZYAN_MODULE_ZYCORE, 0x01u)

Where in Zycore would you like to use this?

UNEXPECTED seems to be the same as the existing FAILED status. Both are used to signal generic failures.
Contrary to exceptions, unexpected errors should not exist with status codes as per design every return value MUST be checked. Not doing that is a bug.
NOT_IMPLEMENTED would be ok to add for me, but is not as useful as a NotImplementedException IMO. It's probably better to call printf() and halt(), abort(), etc in the corpus of an unimplemented function. There is no meaningful runtime action to handle a NOT_IMPLEMENTED code. For the exception case, this is different as it at acts as a shortcut for 1) crashing the program and 2) signaling that the function never returns. In the end, using NOT_IMPLEMENTED or NotImplementedException is always a bug in the code.

UNEXPECTED is more like a guard (e.g. __builtin_unreachable) but with a defined behavior instead. NOT_IMPLEMENTED is for platform-dependent support. I hope this clears the confusion.

Regarding NOT_IMPLEMENTED: I think we have NOT_SUPPORTED for the mentioned use-case.

Not in Zycore:


Differences between statesman and simpy?

Thank you for developing the nice package.
Can you elaborate on the differences between statesman and simpy?  As far as I know, both work for discrete event simulations.
Thank you.
@blakewatters @linkous8

@FanwangM unfortunately I don't really have an answer for you. I've only been conducting barebones maintenance on this repo to support its use in another code base both of which fell onto my plate when Blake left our organization.
If evaluating which one to use, simpy is probably a more mature solution.

Thank you very much!
@linkous8


Adding INCLUDE ORIGINAL to a changefeed causes Surrealist to semi-freeze

Describe the bug
Adding INCLUDE ORIGINAL to a changefeed causes Surrealist to freeze up for a while.
To Reproduce
Try the example that we have in the
REMOVE TABLE reading;
DEFINE TABLE reading CHANGEFEED 3d INCLUDE ORIGINAL;

-- Create some records in the reading table
CREATE reading SET story = "Once upon a time";
CREATE reading SET story = "There was a database";
UPDATE reading SET story = story + "!";

SELECT * FROM reading;

-- Replay changes to the reading table
SHOW CHANGES FOR TABLE reading SINCE 1 LIMIT 10;

No error is shown, but Surrealist will just sit there. Interestingly it isn't an outright freezing as the rest of the app continues to work, including the Run query button. It works again after reloading.
(The same behaviour happens both on the web version and desktop app, and this all works on the CLI)
Expected behavior
The query should display.
Environment:
Platform: Web
Navigator: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>
Version: 2.0.5
Flags: featureFlags: false, models_view: true, apidocs_view: true, themes: false, newsfeed: true
and
Platform: Desktop
OS: Windows_NT
Architecture: x86_64
WebView: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>
Version: 2.0.5
Flags: featureFlags: false, models_view: true, apidocs_view: true, themes: false, newsfeed: true

Closing as clarified by https://github.com/surrealdb/surrealdb/issues/4268#issuecomment-2205816055
Support for INCLUDE ORIGINAL has been hidden from the UI for now


Update examples

I moved all the old examples to examples_legacy_HubInstance. The folder examples now only pertains to the new Client.
This is to ensure new users do not accidentally start using HubInstance.

Hi @gsnyder2007, is it okay to merge this in before publishing 1.0.0 or would you rather wait as it's code freeze?

Will keep examples as is for now as there is at least one KB article that refers to a script:
https://community.synopsys.com/s/article/Black-Duck-Data-Retention-and-Archiving-Best-Practices
Closing this PR.


Bugfix/fix variable name for delete participation (build issue fix)

Checklist

[x] ~I tested the changes and all related features on the test server https://artemistest.ase.in.tum.de.~
[x] ~I documented my source code using the JavaDoc / JSDoc style.~
[x] ~I added integration test cases for the server (Spring) related to the features~
[x] ~I added integration test cases for the client (Jest) related to the features~
[x] ~I added screenshots/screencast of my UI changes~
[x] ~I translated all the newly inserted strings~

Motivation and Context

Description

Regression from https://github.com/ls1intum/Artemis/pull/718
Steps for Testing

Log in to ArTEMiS
Navigate to Course Administration
...

Screenshots

Thanks, it seems the refactoring did not work properly


iona box support

Hi,
probably not the right place to ask this question, but i played around this evening with a device called "iona" from EON Group Germany. After a little bit of research i found this repository and for me, it looked like the python lib might work on this device:
Traceback (most recent call last):   File "/home/tokem/.local/lib/python3.9/site-packages/net2grid/net2grid.py", line 72, in request     response.raise_for_status()   File "/home/tokem/.local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 1004, in raise_for_status     raise ClientResponseError( aiohttp.client_exceptions.ClientResponseError: 401, message='Unauthorized', url=URL('http://<IP_ADDRESS>/meter/now')
When i open the device in browser im getting a blank page, but for me it looks like /meter/now is available.
Do you have any idea/information what i could do next? I was successfull  at getting a bearer token +  some JSON data on their public cloud to which the german app is connected - but im more interested in doing stuff like this locally - maybe to integrate it in homeassistant then
greetings

Currently there is only support for the SmartBridge SBWF3102, which is only sold by Pure Energie under their own white label brand. For any other kind of smartbridge model from Net2Grid I will first have to find out and test what the possibilities are.

looks like the iona box or a similar device is not listed there. based on the information i got it is a lora gateway.
{
    "status": "ok",
    "data": {
        "current_status": "CONNECTED_WITH_METER",
        "meter_txrssi": -62,
        "wlan_rssi": -55,
        "lora_mode": 0,
        "ready_for_meter_inclusion": {
            "inclusion_started": true,
            "KMS_activation_counter": 9,
            "timestamp": "2022-02-09T05:11:32+01:00"
        },
        "contact_with_meter": {
            "connection": true,
            "activation_counter": 9,
            "timestamp": "2020-10-24T10:09:10+02:00"
        },
        "connected_with_meter": {
            "inclusion": true,
            "status": 0,
            "timestamp": "2022-02-09T15:11:32+01:00"
        },
        "timestamp": "2022-02-09T15:14:02+01:00"
    }
}

let me now if i can help you somehow

The question is a bit which API endpoints does it have that we can access. Isn't there something like a model number on the outside?

You can contact me on Discord (Mister Nicolaz#7558), then we can explore the possibilities further.

Would still be nice if we can provide support for the iona device.

Just adding to this discussion as I want to get this working as many other too.
I've found this endpoint in the n2g api docs:
https://api.net2grid.com/reference/v2getlantoken
Which you can call with the Bearer token you receive from the login to their customer frontend (eon smartcontrol etc).
It returns a user_lan_token which expires after 24h.
What I'm struggling with, as I seem unable to catch the calls going to and from the SPLR4911, as my router does not allow me at this point to send everything through a debug proxy and I have no device available right now to intercept the traffic from it, and so I'm not able to figure out how this token is supposed to be used for getting access to /meter/now
So far I've attempted using the mac address as user and the token as password - nope
Same applies for using it as bearer token or as query string.
Potentially this might be the missing key to regain access to the endpoint.
I also wrote an email to net2grid a couple of days ago, but I sadly don't expect an answer from them to be honest ...

Note that /meter/now is not mentioned in those API docs. Unfortunately, I don't have an EON device, so I have to rely on others to test remotely.

Yes correct, the endpoint on the local device, be it the plug or the dongle without the plug, is not directly related to the enduser interface they offer (to which their API docs are related to).
Basically what we do as endusers (without the local API) is connect to a 'broker' of n2g for one of their clients, which is whitelabeled.
The backend of this entire system is ... N2G.
Same as the hardware, (https://www.net2grid.com/hardware) it's from n2g.
All in all the whole thing is an entire ecosystem running on the same infrastructure. It does not matter if my device came from EON or not as the device technical aspect is the same as the one from any other. The device is sold as white-label product from N2G.
For instance, I can use the N2G api docs to interact with my EON (they call it SmartControl) account, through the Bearer token. So all api calls in their docs are available to me.
The local device however, is sadly nowhere documented.
Weirdly enough, approx 2 months ago they introduced the user_lan_token which is approximately around the time (or a bit later) when the firmware rolled out which requires auth for /meter/now
PS. EON told me they have no idea and I should possibly try to get in touch with N2G.

Just an update to this case, as I've received a reply from N2G directly:

So in order to access the local API you have to follow these steps:

Login to the interface/web app your Energy provider gave you access to. In my case that's https://smartcontrol.eon.de/
Grab the bearer token from any API call that has been done in the 'Networking' debug console and save it as you require it as auth for the next call
Check the base URL which is used for the actual API call too in your browser networking. In my case that is api.n2g-iona.net
Next, make a call to https://insertYourBackendApiUrlHere/v2/lan/token with the bearer token from 2.
This'll return the auth token for the local api
You can now call all endpoints in the local device by setting this header: Authorization: N2G-LOCAL-LAN token="yourTokenHere"

Now to the issues with this:

The Bearer token can only be received through logging in in their broker web app. You cannot get the token programmatically through an API call as you as an 'End user' lack the client_id and secret_id which you require to make this call. As per N2G, they intend to implement an End user facing API at some point, but ultimately it is up to your Energy provider (who manages the access to the broker platform) if they make this available to you or not.
The Bearer token expires in 5 minutes. So you can't really store it for long and reuse it all the time.
The Local API token expires in 24 hours. So you're forced to call at least once a day to get a new token.

BUT, apparently you can access the local api just fine if your energy provider deactivates the remote access (and management) to the device. But again, this is up to your Energy provider if they do that, can do that, or are even aware of this functionality. I apparently have this functionality through the EON interface, but it does not work. Even by turning on the 'offline mode' the local device still requires auth in my case.
TL;dr: For automating it, it's a mess (I still managed to do it with a lot of extra steps, but nothing I would ship to a userbase to be honest). It's up to your energy provider to re-activate local access as they apparently manage this functionality from their own backend.

@Exquitas check out https://github.com/tobit6795/homeassistant-smartcontrol
its not pefect, but mostly does it job. it is new to me, that the bearer token expires in 5min, as far as i remember it expires in 60min. Getting the token wasnt a big deal. You can ping me if you want on discord and i can explain it. Anyway thank you for your findings, i just talked with nicholas about this lan token last week. that helps further investigations. im tobit#0746 on dc

That an Energy provider has the choice to deactivate remote access is known to me, have good contacts with someone at Pure Energie and they chose to deactivate it with a new firmware update.

/info

{
 "id": "84df:0c00:0080:0110",
 "mf": "NET2GRID",
 "model": "iONA4901",
 "fw": "1.7.28",
 "hw": 1,
 "batch": "ION-KES-180802"
}
```

Probably define device lists / dicts?

@klaasnicolaas
From what I understood from the Emails between N2G and me (the above posted one and the subsequent emails) is that the Firmware is rolled out by N2G themselves.
The energy companies only give you access to a prettifyed front end with their brand labelling on it, while the entire communication of the physical device that you have, happens directly with N2G and not with the energy company.
The energy company may choose to add some additional things to this front end, but ultimately the entire data from your physical device is sent to N2G.

that you have to request a token remotely first and then request your data locally

That's correct. You need the Bearer Token first (or access token) which you'll get by logging into their webapp with email + password. Then using this Bearer Token, you can talk to the backend api directly (ie. directly to n2g) and request the user_lan_token , which in turn you have to use to access the local physical device that you have.
I know, it's messy and I don't like it either, but that's how things with N2G devices work currently.

That's right, N2G is rolling out that firmware.  Thanks to the output of @tobit6795 I finally see that there are differences in devices, because Pure Energie users have a different model and batch value.


[Scenario] CD2 - Crown of Destiny

Greetings,
I have created a new Descent 2E quest for Valkyrie.  Can you please add it to the mission list?
Name: CD2 - Crown of Destiny
What kind of mission do you want to add (mark with an X, e.g. [X] Descent)?

[ ] Mansions of Madness
[X] Descent

Please enter the GitHub Url to your scenario here
Link: https://github.com/afellowspelunker/CrownofDestiny

Added to the manifest and to the statistics.
Thanks for creating this quest, @afellowspelunker
You can now close this issue, too.

Looks good on the front end, thank you @vidimus for the quick response and encouragement.
Closing this issue, too.


ToMap cannot be materialized for case classes with a single attribute.

import shapeless._
import shapeless.labelled._
import shapeless.ops.record._

case class Foo(x: String)
case class Bar(x: String, y: Int)

def func[T, R <: HList](arg: T)(
  implicit gen: LabelledGeneric.Aux[T, R],
  toMap: ToMap.Aux[R, Symbol, Any]
): Map[Symbol, Any] =
  toMap(gen.to(arg))

// Causes a compile error, because toMap could not be implicitly materialized.
func(Foo("test"))

// Compiles and returns Map[Symbol,Any] = Map('y -> 123, 'x -> test)
func(Bar("test", 123))

I think most likely an issue with ToMap on records.

It only fails when I specify the types of toMap.Key and toMap.Value. If I do not specify them, then the code properly compiles.
import shapeless._
import shapeless.labelled._
import shapeless.ops.record._

case class Foo(x: String)
case class Bar(x: String, y: Int)

def func[T, R <: HList](arg: T)(
  implicit gen: LabelledGeneric.Aux[T, R],
  toMap: ToMap[R]
): Map[toMap.Key, toMap.Value] =
  toMap(gen.to(arg))

// Compiles and returns.
func(Foo("test"))

// Compiles and returns.
func(Bar("test", 123))

Ahh ... I see. Yes in your first example, you've constrained the value type to Any, but the actual value type in the single element case is String.
So this is actually as expected.

Is it expected though? Shouldn't a Map be covariant in its value?

@ashwin153, I think this is due to the fact that although map is covariant, type parameters are contravariant. So, for B <: A Aux[L, K, B] is not a subtype of Aux[L, K, A]. I had some problems similar to this one recently and couldn't find a satisfying workaround, so if anyone has some suggestions, that would be super-useful. (Maybe going OT here)


UI: enable button which allows user to add token to metamask watched assets

docs
how coingecko does it:

addressed by: #324


Scrollable list for pods and namespaces for IntelliJ extension

closes #610

bors r+

thanks @jbeaudetupgrade for opening the issue!


kernel: thread exit domain locking

We don't need to call z_mem_domain_exit_thread() with
sched_spinlock held; it's enough that the thread isn't
running on any CPU and will never be again.
Signed-off-by: Andrew Boie<EMAIL_ADDRESS>

not sure how this PR got opened twice, closing


Added public register links

Add the navigation links for the public register for authenticated and unauthenticated users.

Except the nav conflict, just fixed that! :P

Ah! Glad we spotted that :)


Add loading indicator to the apply annotations file upload

It takes some time for the file upload request to come back, we need an indicator showing the user that there's something going on and they need to be patient.

Also need to double check if the annotations get applied if users close the file upload window.
We can disable that, however if the user clicks out of the file upload dialog or closes it in the middle of the upload - perhaps they do want to cancel that upload?

I think closing upload dialog would mean cancel, but clicking out side of the dialog would not. Does this seem reasonable?

yeah, makes sense, we'll do that


Add "draft" flag to unfinished mini stories so they don't build

Instead of merging lots of PRs to a dev branch while a new mini is in development, let's set this repo up so that any folder with a "draft" flag does not get built. This way we can merge new PRs to main without getting a dev branch wildly out of sync from main.
When a story is ready to deploy, we can remove the "draft" flag.

[x] Set up template so all new stories have the draft flag.
[ ] Add draft flag to all unfinished stories (RadWave & AnnularEclipse)

#146 now has some functionality to only deploy non-draft stories (and the template sets up new stories to have draft: true in the package.json). It seems to run fine in my local testing but I'm not sure whether we can test it on here without merging it in.


Support non String keys in Pulsar IO: Record#getLogicalKey() and Record#getKeyBytes()

Is your enhancement request related to a problem? Please describe.
In Pulsar IO we have Record#getKey that returns an Optional, this way you cannot support non String keys.
You can write Non string keys with:

with KeyValue
With MessageBuilder#keyBytes

Describe the solution you'd like
I would like to see a Record#getKeyObject() (or other name) that returns the key as Object:

String if it is a string
byte[] if we have a base64encoded byte[]
Object in case of KeyValue payload (especially with SEPARATED encoding)

Describe alternatives you've considered
Using Record#getMessage#getKeyBytes() but it is not required for a Record to carry the original message
Additional context
This feature is needed in order to implement more advanced Sinks, in particular to be able to map the record key from Pulsar to Kafka and also in order to leverage Records that are using a GenericRecord as Key (see KeyValue with SEPARATED encoding)

cc @dlg99

As the message value, the message key could be Json, Avro, Protobuf or whatever. So we could have a way to store byte[] returned by Schema.encode() as a base64.

Here I am talking more about the Sink part, that is when we read from Pulsar.
But yes, my idea is that we are able to ready the "logical key", whatever it is.

raw byte[]
String
KeyValue  - SEPARATED
KeyValue - INLINE

May you coud have in Record:
default Optional<byte[]> getKeyBytes() {
return getKey().map(s -> Base64.getDecoder().decode(s));
}
And if the schema is a KeyValueSchema<Object,Object>, you should get the actual ket with getKey() properly decoded with  the ObjectSchema of the key.

That was my first idea.
We can add that as well.
But in Pulsar we are used to automatic decoding of the value, so probably it is good to add getLogicalKey as well, otherwise the Sink code will have to deal explicitly with KeyValueSchema and I believe that it is some kind of implementation detail that is better to hide.
In my mind I have that only the KeyValue class is usable by the Sink code, like GenericRecord

I think Record, Sink and Source should be concret class of KeyValue<Object,Object> , because we want generic connectors working whatever is the schema or encoding. So we would have Record like this:
   /**
     * Return the SEPARATED key if the message has one associated (stored in metdata properties).
     */
    default Optional<String> getKey() {
        return Optional.empty();
    }

    default Optional<byte[]> getKeyBytes() {
       return getKey().map(s -> Base64.getDecoder().decode(s));
    }

    default KeyValueSchema<Object,Object> getSchema() {
        return null;
    }

    /**
     * Retrieves the actual data of the record.
     *
     * @return The record data
     */
    KeyValue<Object, Object> getValue();

    default public Optional<Object> getRecordKey() {
        if (getSchema() != null) {
            switch(getSchema().getKeyValueEncodingType()) {
                case SEPARATED:
                    Schema<Object> objectSchema = getSchema().getKeySchema();
                    return (objectSchema != null)
                            ? Optional.of(objectSchema.decode(getKeyBytes().get()))
                            : Optional.of(getKey().get());
                case INLINE:
                    return Optional.of(getValue().getKey());
            }
        }
        return Optional.of(getValue().getKey());
    }

    default public Object getRecordValue() {
        return getValue().getValue();
    }

The sink connectors would use getRecordKey() and getRecordValue() to get the concret key and value object, and they can query the schema to process it properly, and whatever the key is INLINE or SEPARATED.

@vroyer
that's something I would like to achieve but we have to take into account compatibility with the past
with https://github.com/apache/pulsar/pull/9896 we will open the way to Sink , and in that case Record.getValue() will contain your KeyValue object if you are coming from a KeyValue encoded message.
we could also create a new interface KeyValueRecord with your code and add some
Record#toKeyValueRecord() converter that maps the Record to the new API

Why pulsar functions depends on pulsar-io Record ? Record is not only used by pulsar-io connectors ?

Pulsar-IO Sinks and Sources are special instances of Functions :-)

Partial support for KeyValue records with separate schema for Key and Value is provided by https://github.com/apache/pulsar/blob/3b2c8526a96fc90e948dbeb510e8400a628c749a/pulsar-functions/api-java/src/main/java/org/apache/pulsar/functions/api/KVRecord.java#L31
but it looks useful only to Sources
it is used for Kafka Connect Source, that encodes directly the key and the value to byte[]
https://github.com/apache/pulsar/blob/86e39a25e961d148a485be4a7c9fc186d5b8f8bc/pulsar-io/kafka-connect-adaptor/src/main/java/org/apache/pulsar/io/kafka/connect/KafkaConnectSource.java#L76

It was implemented by @tuteng  in #6034

The issue had no activity for 30 days, mark with Stale label.

now you can use Sink and in case of KeyValue you will get the KeyValue object in record.getValue().getNativeObject()
closing


APIs please :)

What's the problem?
I find integrating Bloop into my Open-Sourcerer project challenging due to the lack of comprehensive documentation and APIs for specific features. This makes it difficult to efficiently utilize Bloop's capabilities for indexing repositories, storing knowledge maps in a vector store, and retrieving them.
What's the solution?
I propose enhancing the documentation and providing well-defined APIs for key features of Bloop. This would greatly streamline the integration process and enable projects like Open-Sourcerer to leverage Bloop's unique capabilities more effectively.
Additional context
Integrating Bloop holds the potential to significantly enhance the functionality of Open-Sourcerer. Having clear documentation and APIs would foster collaboration and innovation within the open-source community while making it easier for developers to harness the power of Bloop in their projects.

please :)

Same here. I'd like to utilize Bloop in a langchain, but it doesn't appear Bloop offers an API.

+1 here. Is there any plan to release an API ? I imagine third parties would pay good money for API access to bloops context retrieval for use in building their own tools

Still couldn't find api doc in 2024...I started bleep instance as standalone but the only query that returns response is :curl -v "localhost:7878/api/repos/indexed" | jq


Virtualmin sorting by size problem

Similiar issue as #103. The ordering seems to be off when I go to "List Virtual Servers" and I configured to show Total quota and Total used.
The Virtualmin Framed Theme has the same issue, so I don't know if it is a Virtualmin issue or a theme issue. Isn't there a default ordering algorithm somewhere in Virtualmin that's used for lists?

Sorting does work at the Edit Users list (which was #103) and at Webmin -> System -> Disk quota:

I think I know why it's happening. I will send you the patch to try a bit later. Stay tuned.

After investigating on the issue, it appears that I should not be fixing it. It should be done in Virtualmin by adding label bytes. It should be 0 bytes not just 0.

Do you have an example of a page in Webmin that is showing "0" instead of "0 bytes" ?

It's in Virtualmin. Can be seen in the first picture of this post. (Marked red, column Total Used)

I don't see "0" in that list though. Also, Webmin already uses "0 bytes" when printing a nicely formatted size of 0 : https://github.com/webmin/webmin/blob/master/web-lib-funcs.pl#L8373

Jamie, virtual-server-lib-funcs.pl, line 3432:
# Quota used
if ($d->{'alias'} || $d->{'parent'}) {
        # Alias and sub-servers have no usage
	push(@cols, "0");
}

push(@cols, "0"); should be push(@cols, &nice_size(0));

Doh! I don't know how I missed that - I'll fix it in the next release.


FC002: Avoid string interpolation where not required

I have following code and got the warning but I don't know how to get rid of the warning. I tried to change from find '#{node['node-js']['install_folder']}/bin' to 'find node['node-js']['install_folder']/bin but still didn't work. Any thought?
bash "symlink-local-bin-#{node['node-js']['install_folder']}/bin" do
  code <<-EOH
    find '#{node['node-js']['install_folder']}/bin' -maxdepth 1 -xtype f -perm -u+x -exec bash -c -e '
      for file
      do
        ln -f -s "${file}" "/usr/local/bin/$(basename "${file}")"
      done' bash '{}' \\;
  EOH
  only_if { ::File.directory?("#{node['node-js']['install_folder']}/bin") }
end

FC002: Avoid string interpolation where not required: cookbooks/node-js/recipes/install.rb:38

line 38 is at the find command

Try double quotes:
find "#{node['node-js']['install_folder']}/bin" -maxdepth 1 ......

@chazzly  I tried that too but did not work!

+1, please fix.  There's no reason for this to be raised in here-docs that use interpolation.

I'm also getting this issue with interpolation in heredocs. It appears to only be an issue with Ruby 2.2 though, the same suite on 1.9.3, 2.0.0 and 2.1.15 is fine.

Seems that this issue has been fixed months ago in https://github.com/acrmp/foodcritic/commit/aaf7a9d3beb5975dbfd7d8b02e3de463420e9d77. Is there any chance of getting a release tagged?


Naive Bayes on Titanic Dataset

💥 Proposal
(A clear and concise description of what the proposal is.)
I want to implement Naive Bayes algorithm from scratch in Python without any SK-learn functions for titanic dataset . This implementation includes Data pre-processing , Visualization of final results , And also Normalization . I would ignore all the irrelevant attributes and would only consider the required and necessary features from the dataset

Hi, we have a similar issue. Hence, we cannot assign you this issue.


fix: print version number that updater.writeVersion returns

Copy of https://github.com/conventional-changelog/standard-version/pull/670
BEGIN_COMMIT_OVERRIDE
fix: When a custom updater reports a version other than the new computed semver, that version is now correctly reported in log output
END_COMMIT_OVERRIDE

For custom updaters that derive the new version from the file contents (e.g. newVersion = oldVersion + 1), the log output was showing the new computed semver version, rather than the actual version applied by the updater. This PR corrects the output for such custom updaters.
Closes expo-community/standard-version-expo#18.
Closes expo-community/standard-version-expo#10.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f6a7430). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #11   +/-   ##
=========================================
  Coverage          ?   97.62%
=========================================
  Files             ?       26
  Lines             ?     1177
  Branches          ?        0
=========================================
  Hits              ?     1149
  Misses            ?       28
  Partials          ?        0

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Targeted component

Not sure if it is related to changes made here, but the tests appear to have gotten a lot less deterministic on Travis, despite consistently passing locally. Will investigate before asking for a review.

Going to switch things around so ember-popper requires an explicit target while a new component, ember-popper-targeting-parent (name pending), automatically sets the target to the parent, and cannot be given a target.
The thought here is that most consumers of ember-popper likely require doing something with the target (tooltip/popover libs, for example), so the base component should reflect that.

@pzuraq it looks like overriding the popperTarget argument in the legacy {{ember-popper-targeting-parent}} isn't overriding its superclass correctly. Am I right in thinking this is a bug in ember-decorators/argument?

Finally found the time to fix this up. @pzuraq @simonihmig @rwwagner90 any thoughts on this?

@kybishop working on a new attempt at #72, I came across this change you added here.
It seems you are excluding ember-popper-targeting-parent for Ember < 2.10, is that right? If so, what's the reason for this? And how come it does not break the tests which use it? E.g. this one, as the tests are still running for those scenarios and are passing... 🤔
I am a bit confused, hope you can shed some light? 😝
FWIW, one test is failing only for those Ember versions in my WIP branch, so might be related...

Hey @simonihmig. There is also a -ember-popper-targeting-parent-legacy component. This component is renamed to ember-popper-targeting-parent for Ember versions lower than 2.10, while the current component (as you linked) is removed.

@simonihmig ahh sorry I should've looked closer at which treeFor you had linked to. This looks funky because the legacy ember-popper-targeting-parent doesn't actually need its own template, it simply uses the same template as legacy ember-popper.
So if we are on < 2.10, we don't need to export a custom template for ember-popper-targeting-parent, only the original template from legacy ember-popper. Please feel free to comment as much in your PR to avoid future confusion!


Return Loco Result in workers

When working with workers in perform function the result is sidekiq results.
We need to convert this error to LocoResults

After investigation, it is better now to keep it simple and return an error with .map_err(Box::from)? and not wrap the workers with a custom logics


Try to update calc on init

This is my proposal for #79
In this PR, a calculator will try to update its value during initialization. If the update fails, a warning with the title of the error is logged. Also, the full traceback of the error is logged to the debug logger.
Example 1:
>>> import liesel.model as lsl
>>>
>>> a = lsl.Data(1.0)
>>> b = lsl.Calc(lambda x: x / 0, a)
liesel.model.nodes - WARNING - Calc(name="") was not updated during initialization, because the following exception occured: RuntimeError('Error while updating Calc(name="").'). See debug log for the full traceback.

Example 2:
>>> import logging
>>> import liesel.model as lsl
>>>
>>> logger = logging.getLogger("liesel")
>>> logger.handlers[0].setLevel(logging.DEBUG)
>>>
>>> a = lsl.Data(1.0)
>>> b = lsl.Calc(lambda x: x / 0, a)
liesel.model.nodes - WARNING - Calc(name="") was not updated during initialization, because the following exception occured: RuntimeError('Error while updating Calc(name="").'). See debug log for the full traceback.
liesel.model.nodes - DEBUG - Calc(name="") was not updated during initialization, because the following exception occured:
Traceback (most recent call last):
  File "/Users/johannesbrachem/Documents/git/liesel/liesel/model/nodes.py", line 526, in update
    self._value = self.function(*args, **kwargs)
  File "<string>", line 1, in <lambda>
ZeroDivisionError: float division by zero

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/johannesbrachem/Documents/git/liesel/liesel/model/nodes.py", line 500, in __init__
    self.update()
  File "/Users/johannesbrachem/Documents/git/liesel/liesel/model/nodes.py", line 528, in update
    raise RuntimeError(f"Error while updating {self}.") from e
RuntimeError: Error while updating Calc(name="").

@wiep this is something we discussed briefly during the weekly on August 30. You had some reservations about the general idea to try to update a calculator on initialization - so to enrich the conversation about this proposal, I created this PR which shows how I think the update could be implemented without breaking the calculator's ability to be initialized without a working update. What do you think?

Converted back to draft, because I just saw that with this implementation, we get the following warnings during model initialization:
liesel.model.nodes - WARNING - Calc(name="_model_log_prior") was not updated during initialization, because the following exception occured: RuntimeError('Error while updating Calc(name="_model_log_prior").'). See debug log for the full traceback.
liesel.model.nodes - WARNING - Calc(name="_model_log_prob") was not updated during initialization, because the following exception occured: RuntimeError('Error while updating Calc(name="_model_log_prob").'). See debug log for the full traceback.

This is not pretty, because it is just intended behavior and I think probably users should not be warned about this. Before this PR is ready for review, I would like to come up with a nicer solution for this case.

i'm still not super happy with the default warnings. so far, we say liesel you can build a partial graph but that would trigger warnings what is not really what should happen. usually i do not like this magic, but here it might be justified: a context manager that turns the updates on (or off). i think that is better than fiddling with the log levels.
with lsl.instant_evaluation():
     a = lsl.Data(1.0)
     b = lsl.Calc(lambda x: x / 0, a)

I don't really think the magic context manager would bring us a lot of joy here. Manually, the desired functionality can already be achieved by
a = lsl.Data(1.0)
b = lsl.Calc(lambda x: x / 0, a).update()

This makes it more obvious what is happening than the context manager.
The idea of this PR is mostly to make it easier for users to spot errors in their code early without introducing additional manual work. If you don't know the internals of how, when and why exactly a calculator gets updated, it is currently easy to get tripped up. At least that is what happened to me.
I think an alternative to the work this PR could lie in documentation.

i think that is better than fiddling with the log levels.

You only need to change the log levels if you have no other way of accessing the original traceback. When you are working interactively, say in quarto, you can just run b.update() manually one time to get the error message. If you can't do that, activating the "debug" log-level for debugging is reasonable I think.
What is true is that this code looks a little fiddly:
logger = logging.getLogger("liesel")
logger.handlers[0].setLevel(logging.DEBUG)

This is a result of how we set up our logging. I think we could (and should) change the setup such that you can set the log level like this:
logger = logging.getLogger("liesel")
logger.setLevel(logging.DEBUG)

But that is a different issue.

Building a non-initialized model is possible without warnings is imho a crucial aspect of Liesel. However, the proposed implementation may require users to turn off logging, build the non-initialized model, and then turn the logging back on. I find that not ideal. Checking the calculations during initialization is often beneficial from a user's perspective, though. Therefore, I think, it may be necessary to have two different modes to cater to both scenarios.
One possible solution is to enable updates by default and disable them only when a particular setting is altered. For example, a ctx manager could be used to adjust the settings temporarily.
lsl.update_on_creation = False
# build model

# or

with lsl.disable_updates_on_construction():
    # build model

We can discuss this further during one of our upcoming weekly meetings.

We could also simply add an init parameter to calculators:
a = lsl.Data(1.0)
b = lsl.Calc(lambda x: x / 0, a, update_on_init=False)

This could be set to True by default.

do you think that would be more straightforward to the user than a context manager?

Yep, I think it would be both easier to use and also easier to find, because it would be right there in the api documentation.

i like this definitely more than the logging. compared to a context manager it's just very cumbersome if you have many nodes that require no initialization.

Fair point. Why not both, the init argument for everyday use and the context manager as an option for bulk operations by advanced users? Or, another option: an alternative constructor like Calc.lazy()?

Also, a good idea. However, I would always include the keyword new to indicate that the static method is a constructor Calc.new_lazy(...).
So far, we do not use ctx manager anywhere because when using them it might be less obvious how some things work.
Maybe we should have an implementation to try things out.
Signature:
Calc(..., update_value: Optional[bool] = None)

Meaning:

update_value is None => ctx manger decides
update_value is True => update
update_value is False => do not update
Calc.new_lazy(...) => alias for Calc(..., update_value=False)

Quite the elaborate setup, but I guess this can make us both happy :)

we do not keep all of it, was more like an signature for an implementation to try things out. if that's too much work, we can also implement only one version and see if it has short comings.

I guess at least the combination of context manager and init argument would make sense, because then we have both use cases covered, i.e. a) general default of update on init with b) the option to deactivate the update for a bunch of variables at a time.

We will go with the init argument, which defaults to True. We can add a context manager later, if it turns out we want one.

@wiep if you got a notification for this PR, you can ignore it. @GianmarcoCallegher is doing the review.

LGTM


Pex cannot resolve fbprophet

python -m pex.cli lock create --style=universal    --interpreter-constraint 'CPython>=3.8,<3.9'  fbprophet==0.7.1

Fails on ModuleNotFoundError: No module named 'numpy'.
What's going on is: fbprophet is distributed as an sdist, and its setup.py invokes its own code to precompile models, and that ends up evaluating an __init__.py that imports numpy, which isn't present.
Note that pip install fbprophet==0.7.1 works, I guess because the numpy dep is installed prior to fbprophet's setup.py being invoked, and is available for it to use.

This is a dup of #1751. Unfortunately there is nothing that can be done in general with sdists like this except to pre build a wheel out of band. See #1751 though for a workaround you might use in this case. There is an unreleased fix for the fbprophet build you can use via VCS requirement.


DT Implement text for About page

Implement MVP quality 'about' page.
Tasks remaining for initial testing:

[ ] any issues with headers
[ ] add external links
[ ] Review what sub-pages are needed for initial testing and -
[ ] a) Implement sub-pages and  b) add to the menu

Adding @ComfE-2662 for implementation.
App pages (those which draw content from the database) should be created ast .txt documents only, for transfer to the app page when created (by developers).
Should app pages be created in Figma?

@ComfE-2662 have you had a chance to look at this?

@PatReynolds Please post a link to the About page here so I can have a look.
Still not entirely sure about what needs changing

Ah! I see the About page link in the top bar disappears when one is logged in.  I'll create a new story about that.
the page is here: https://test3.freebmd.org.uk/cms/about
The spreadsheet shows what should be going into it.
some of that content is not a normal refinery page, but an App page (will have to be a sub-page, linked from the index and, possibly, within the text). @Vino-S do @KatyMawhood or @Daniel-silve1ra have to design in the App pages?

All App pages are to be sub-pages.
@ComfE-2662 to check that the spreadsheet is marked up with what are the App pages, and that the other pages are marked as being either for the main About page, or for a sub-page of the About page.

@PatReynolds what is left to do with this one?

Hi @richpomfret @PatReynolds
May I comment?
test3 has a live About page at https://test3.freebmd.org.uk/cms/about but it has headers, for instance, that are non-standard in respect of font-colour (light "gold") and header-fonts; some un-made hyperlinks; and sub-pages that are very "thin".
While Pat was away on leave (so I understand), Denise, Alison and I discussed working on Help, which was in a similar condition, to bring it up to the Standard - but without adding new content. Alison is currently reviewing that draft page; but its sub-pages will also need to be completed and signed off (as up to to standard) before an interim version of Help is ready to replace the current page.
The About page, itself,  was  going to be next, but Pat is back now. So I need to know whether I should work on an interim draft of About . Like Help, its likely to be a two stage process: 1st - get it to the standard; 2nd - add missing content / missing sub-page.
The news and history sub-page, for instance, has not been updated. FreeBMD(1) had a lot of FAQs and some of them were to be part of About and some part of Help - none of these FAQs subpages have been done, but some of the content has been moved into the top-level pages. We appear to have a FreeUKGenealogy draft standard for FAQ pages, which has been used in formatting a new Help-page "Reporting errors in transcriptions".
So, the About page could be brought to standard fairly soon, but that will not include adding any new content - if needed, nor making any improvements to sub-pages.

I think it is so close to ready that there is no need for an interim draft. 'ready' meaning 'in a state that can be used for initial testing on beta.freebmd.org.uk' rather than MVP.
I think the 'gold' issue is CSS not htlm.  I searched the code for 'gold' and found nothing.  The page displays as expected, and the style code is identical to that used in FreeREG.  @AlOneill can you see anything that needs doing?
There are some links (external) to be added - can you do that please @PhilipClarke712 ?
There is some text missing (I'll find and add that).
Sub-pages with links from the menu are complete.
I will review what the sub pages are that need to be in asap (for initial testing) and what is MVP. Sub pages that are not ready simply won't be in the list of sub-pages.

The good news is that the only part of testing that requires a visit to a sub-page of about asks for information on the news page.  I think it fine to leave the 'Etc.' for the first tests, because it does indicate that there is more to come.
So, once any CSS or other style issues are resolved, this page is ready for initial testing.

Hi  @PatReynolds  @AlOneill
It's close to being ready for review.
From experience Alison tends to be "more strict at review" than perhaps is my natural inclination; and Alison is the one that needs to "sign off  a  new draft copy this page".

You are correct, the colour of the h2 headers is being changed by css - the colour appears to be   #895f49; / "brown - brighter" - which to my eyes looks to be "light gold".
There are quite a few working hyperlinks to FreeBMB(1) which page-switch to FreeBMD(1).  The navigation side bar looks to be different to what is specified for FreeBMD1. These are minor problems, just change the html to open the page in a new window and warn the user so that it does not come as a surprise.

All these above are minor problems and easily fixed, but if I were to send that page, as it is now to Alison  I would anticipate that it would be returned to me without review and I  get told to validate it.
Note: I need to make a copy of the page and do the work on that; and do and the external links. I also propose to treat FreeBMD(1) as an external site.
I also need to remind that a draft page that is considered fit for "sign off" will not be signed off until all its subpages are "sign off"
I also have time constraints; after today I will have no time for working on Refinery - so today I have to work on a draft of this page, test the changes to #291  #348 (#350); and (hopefully) persuade Alison to tell me make minor changes to a page that she is currently reviewing to take account of #348 (hopefully) being  fixed.
Time may run out before those are all done.

@PatReynolds @PhilipClarke712 I've fixed the inappropriate styling that was a result of copying wholesale from FreeREG.
You are correct, Philip: this page has never been signed off for HTML and other technical stuff; visually, the page is still different from our usual setup; there are links to pages that are lacking layout (and thus not signed off); there is at least one broken link; there may well be other issues to address when checked fully.
The urgent question is do I review and fix the page as it is now or wait until Philip has made changes?
I note that there is no link to "About" in the main navigation but can only assume that there will be a link in time for testing?

Hi @AlOneill @PatReynolds
I've copied the current About page onto a new page DRAFT - About - draft for beta  which sits in Refinery immediately above About. That is where I'll be putting my changes.

Thanks, @PhilipClarke712 . Yes, @AlOneill please hold off until Phillip has done what he can.

Please don't apologize, Phillip - you are a volunteer, and a much
appreciated one.  Dratted Covid!!
I have made a story for the Accessibility Policy (and moved the draft to
its proper place in the structure (under about).  I'm meeting with Alison
this lunchtime so can ask her then to refresh my memory what needs to be
done with this page (on all our sites).
Best wishes,
Pat
On Thu, 10 Jun 2021 at 20:38, PhilipClarke712 @.***>
wrote:

Hi @PatReynolds https://github.com/PatReynolds , @AlOneill
https://github.com/AlOneill
I have worked on this page -
https://test3.freebmd.org.uk/cms/draft-about-draft-for-beta - with help
from Alison along the way, and it has the "look" and the "house-style" that
I think is required under "Marking up pages in Refinery". I have made
live hyperlinks to all pages, expect one which is in Refinery as a Draft
page - a mark-up hyperlink is given, instead. That is marked up in "dayglow
yellow" (perhaps not the precise colour used by css)
It has been spell checked and Validated against W3C html5. I think that
there is some duplication of text, but I would be inclined to recommend
that it be reviewed as a replacement for the existing About page for
running on Beta. The decision is not mine to make and Alison has far
more experience than I do.
 This is something I should have done last
September, but Covid-19 has delayed it more often than I would have wished.
Have a good weekend.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FreeUKGen/FreeBMD2/issues/171#issuecomment-858970992,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQLSBTJRY4UMPIZP43KUVDTSEIFBANCNFSM4JL3WCBQ
.

--
- -
Dr Pat Reynolds
Executive Director
A Charitable Incorporated Organisation registered in England and Wales,
number 1167484
VAT registration: 233 0105 70
Join us on social:
[image: : https://www.facebook.com/FreeUKGEN]
https://www.facebook.com/FreeUKGEN https://twitter.com/FreeUKGen
https://www.instagram.com/freeukgenealogy/
https://www.pinterest.co.uk/FreeUKGenealogy/
Please read our Privacy Notice
https://www.freeukgenealogy.org.uk/files/Documents/Privacy-Notice.pdf for
information on how we will protect and use your data.
https://www.easyfundraising.org.uk/causes/freeukgenealogy/?utm_campaign=raise-more
+44 1723 362616   +44 7943 145387
Westwood House,Westwood, Scarborough YO11 2JD, UK

@PhilipClarke712
Is the draft About page ready for HTML and technical checking?

Hi @AlOneill
Yes it is ready,
I though that I had sent it to you via GitHub almost a week ago - I restarted work on it last Monday afternoon (14th).
If I did, sent it to you (last Tues afternoon at the earliest), I obviously I did not use this story. Perhaps I intended to send it and never did.

@PhilipClarke712 Thank you.
@PatReynolds Have checked and fixed https://test3.freebmd.org.uk/cms/draft-about-draft-for-beta, then promoted page to About.
Next I'll give the pages that this one links to a quick check and some layout: Why is FreeBMD changing?, News and History, Your Reviews.

Have checked and fixed HTML, CSS, typographical issues and similar on: Why is FreeBMD changing?, News and History, Your Reviews.

@PatReynolds to do final review.

To do: correct the statement that automatic citations are available currently.

Statement re automatic citations has been corrected.


Improve UI

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Firstly, we can improve our Google Chrome Extension UI.

I have updated some improvements, like "sidebar".

see my pull req.

Improvements:

add Customize Options, which make users can select target website and price range;
display user's selections on the subtitle;
add Quick Action panel to open a new page;
highlight the final result link;


Errors when running the web app

The first error in the console is      if (scope.tweetNumber !=== 90) { which make sense since !=== is not valid. (https://github.com/fossasia/open-event-webapp/blob/master/src/appComponents/twitterwall/singletweet.js#L58) I fixed it to !== but no I see this error:
SessionsController.js:23 Uncaught SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
angular.js:68 Uncaught Error: [$injector:modulerr] Failed to instantiate module openevent due to:
Error: [$injector:modulerr] Failed to instantiate module oe.sessions due to:
Error: [$injector:nomod] Module 'oe.sessions' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
http://errors.angularjs.org/1.5.5/$injector/nomod?p0=oe.sessions
    at http://localhost:8080/libs/angular.js:68:12
    at http://localhost:8080/libs/angular.js:2070:17
    at ensure (http://localhost:8080/libs/angular.js:1994:38)
    at module (http://localhost:8080/libs/angular.js:2068:14)
    at http://localhost:8080/libs/angular.js:4564:22
    at forEach (http://localhost:8080/libs/angular.js:322:20)
    at loadModules (http://localhost:8080/libs/angular.js:4548:5)
    at http://localhost:8080/libs/angular.js:4565:40
    at forEach (http://localhost:8080/libs/angular.js:322:20)
    at loadModules (http://localhost:8080/libs/angular.js:4548:5)
http://errors.angularjs.org/1.5.5/$injector/modulerr?p0=oe.sessions&p1=Erro…oadModules%20(http%3A%2F%2Flocalhost%3A8080%2Flibs%2Fangular.js%3A4548%3A5)
    at http://localhost:8080/libs/angular.js:68:12
    at http://localhost:8080/libs/angular.js:4587:15
    at forEach (http://localhost:8080/libs/angular.js:322:20)
    at loadModules (http://localhost:8080/libs/angular.js:4548:5)
    at http://localhost:8080/libs/angular.js:4565:40
    at forEach (http://localhost:8080/libs/angular.js:322:20)
    at loadModules (http://localhost:8080/libs/angular.js:4548:5)
    at createInjector (http://localhost:8080/libs/angular.js:4470:19)
    at doBootstrap (http://localhost:8080/libs/angular.js:1746:20)
    at bootstrap (http://localhost:8080/libs/angular.js:1767:12)
http://errors.angularjs.org/1.5.5/$injector/modulerr?p0=openevent&p1=Error%…bootstrap%20(http%3A%2F%2Flocalhost%3A8080%2Flibs%2Fangular.js%3A1767%3A12)

Steps to reproduce:
docker run -p 80:5000 dengyiping/open-event-orga-server
git clone git@github.com:fossasia/open-event-webapp.git
cd open-event-webapp
npm install
node_modules/.bin/bower update
node_modules/.bin/bower gulp
http://localhost:8080

@oren , check this #188

thanks!


Dat.json

makes dat.json part of the create command

@karissa rebase master and should fix the dat.land server errors in those tests.

Wait maybe I didn't fix that

no sounds right the PR branch is green so we can merge


Add missing external flag indicator in secrets

Proposed changes
This is required otherwise it tries to read a non-existing file and should make it clear for anyone following along
Related issues (optional)
None

@ndeloof Could you PTAL?


Tests for solvers in macroeco_distributions

Do we want tests for solvers in macroeco_distributions and if we do, how extensive should they be? I'm kind of on the fence, and would love to hear what others think.

I'm leaning toward just doing some basic sanity testing, with values that aren't absurdly extreme.  We just want to test that future changes won't break anything horribly, not that everything is correct to the seventeenth decimal place, I think.

Makes sense. If that's what we want, we can estimate the parameters for a few SADs using the current version and save the output for future tests.
@ethanwhite does it sound good to you?

Works for me :+1:

fixed in #44


is:issue how to sum string type load from csv? and how to convert string column to timestamp?

my csv file column fields: date, username,  vol,  type
all fields are string fromat.
can't  load as double, but when load as string,
I can't sum vol column, and can't select rows by date range.
how to convert string column to int or double?
and how to convert string column to timestamp?
PS: why I can't find any doc and issue about my question? why others didn't have this issue?
thanks!

my mistake.this is about xtensor ,not python.


Add orange border on nodes with warnings

Split out of #8678 as the corresponding PR was merged without support for this specific feature.

The UI should (?) match with the existing orange border present on GUI1.

pinging @AdRiley as a heads up.
(@ anyone - feel free to edit the description to be clearer, and/or include screenshots.)

I'm not sure if we need strictly orange border - maybe just warn sign next to node? We plan making icons for errors too: https://github.com/enso-org/enso/issues/8677

Do we need a design? I guess the user requirement is to be able to see a component has warnings even when the component is not hovered or selected. And then hover/select shows you the warning.

We will go with the icon, as it's easier than making a working border.
Soon new icons will be merged. We should display them with the following colors:

Also info from @jdunkerley:

it should appear to the left of the node, to the left of the menu if shown


Ursa Wren crew

** Fly Casual Release Version**
Which version did the bug occur in? Latest
Describe the bug
Ursa Wren crew isn't there for rebels to select.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error
N/A

Expected behavior
Should be available and then give the equipped ship the option of taking a lock action (if not stressed or already done a lock action) against any enemy ship in range.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform/Device (please complete the following information):

Android

Additional context
Add any other context about the problem here.

Confirmed missing, I'm working on pulling Ursa Wren (as well as others) from the Fly Casual Legacy fork right now. Will update and close with commit when finished.


[core] Fix missing typings in /es folder

When I created the additional ES output in /es, I forgot to adapt the scripts copying the typings. Right now, if I import the files via material-ui/es/<Component>, I get no editor / TypeScript support. This PR should fix this.

@NeoLegends Thank you 📦


in _httpUpdate , after httpAddrClose(http->fd), not reset http->fd . or not need?

in function _httpUpdate :
if (http->status == HTTP_STATUS_SWITCHING_PROTOCOLS && !http->tls)
{
if (_httpTLSStart(http) != 0)
{
httpAddrClose(NULL, http->fd);
*status = http->status = HTTP_STATUS_ERROR;
return (0);
}
*status = HTTP_STATUS_CONTINUE;
return (0);
}
----after httpAddrClose ,does it need to reset http-fd = -1?

Apple CUPS:
[bug-fix-rollup-1 1f3d159e4] Fix one other spot where http->fd isn't reset to -1 (Issue #5915)
OpenPrinting CUPS:
[master 0c92c5feb] Fix one other spot where http->fd isn't reset to -1 (Issue #5915)


Test cases are passing on iOS but failing on android emulator

What are you trying to achieve?
Test cases are passing on passing on iOS but same test cases are failing in android emulator in sauce labs.
What do you get instead?
Test case fails after 7-8 minutes on android emulator on sauce labs.
Details

CodeceptJS version: 0.5.0
NodeJS Version: 6.9.2
Operating System:OS X EI Capitan (v10.11.6)
WebDriverIO : 4.6.2
Configuration file: codecept.conf.js

"desiredCapabilities":{
     "android": {
        "deviceName": "Android Emulator",
        "browserName": "Browser",
        "name": "TEST_ANDROID",
        "deviceOrientation": "portrait",
        "platform": "Android",
        "version": "5.1"
    }
 }

What is wrong in this? Can someone help me ?

what is the output if you use --verbose ?

Hi @joelgrimberg,
I am trying to check if I can see the element after a click operation is performed. I.see("element CSS path"). The css path is correct but still I.see fails which means it is not able to find element. --verbose won't give any logs since this is a test condition fail.
Thanks,
Shrikanth

@shrikanthkm07 I.see command validate text on page, not element visibility. To test element visibility you have to use I.seeElement, but I recoment to useI.waitForVisible("element CSS path") to prevent false negative errors, related to element loading time

Close due inactivity


Adding docs for PaddleNLP

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

hi @osanseviero . I think this is ready for review

@osanseviero addressed your comments

@radames would you be up for taking a look into the images?

I've added the images please check @osanseviero @sijunhe thanks


securitykey.js

Authenticate Users on the Systems/Applications you make available to them or make them unlock the data they store in their Storages/Servers with a key that only they can access. Requires Security Key (Hardware).

I have two suggestions. The bright green makes it a bit hard to read the white text, and the icon is hard to see in dark mode.

Maybe you could make the green a bit darker, and put the icon into a green circle?

@XmerStudio

Something happened to the icon...
Also, you should probably use a separate block icon from menu icon. The icon was only a problem in the menu.

Sorry, last thing, I forgot, the id should have your username (eg. XmerSecurityKey)

this is client-side authentication, has the same problem as sharkpool captcha extension in not providing any actual security


Deprecate namespace setter, undo deprecating getGeneratedKeys

Fixes #1353 and #1351
/cc @lesv

Coverage decreased (-0.004%) to 83.896% when pulling 502334c845e057788a2ca36e39f0161fba158831 on mziccard:datastore-rename into e7063d4e9a620908e15f7526c8e3bdd14fff79b8 on GoogleCloudPlatform:master.


s/Api::Settings/Api::ApiConfig/

Originally we wanted to have a Settings object nested under the Api
namespace that looked and behaved just like the top-level Settings.
Furthermore, we enforced a nested style of class/module children so that
constants would not have to be fully qualified.
That turned out to be problematic. First, if the top-level Settings
was loaded before that of Api, the latter may never be loaded, meaning
that all those unqualified Settings' would point to the wrong object.
Second, we were using both Api::Settings and ::Settings in the API
code, leading to confusing constructs such as:
::Settings[Settings.base.module]

Since we want unqualified constants in the API code, it seemed
acceptable to introduce some redundancy in renaming Api::Settings to
Api::ApiConfig. Further, we preferred "Config" over "Settings" since
for the most part we refer to this thing as "config" everywhere
else (e.g. it's persisted in config/api.yml, methods such as
api_config, CollectionConfig, etc.)
@miq-bot add-label api, refactoring, technical debt
@miq-bot assign @abellotti
/cc @Fryguy

Nice 🎼  !!

👍

@abellotti based on your removal of euwe/yes label, assuming this should be labeled as euwe/no?

correct, issue was fixed in E-release, so this is for our sanity going forward.  Thanks.


Add log events in Service Fabric project

Fixes https://github.com/microsoft/reverse-proxy/issues/559

Thank you!


Revert "Updated selected transaction If getting new updates"

Reverts Expensify/App#49829 to Fix https://github.com/Expensify/App/issues/50286

@cretadn22 How is the fix coming along? I'm planning on deploying within a couple hours so if we could get something merged by then that would be ideal


Move Advanced > Keygen Token Transfer from Old Library to New Manual

Move Advanced > Keygen Token Transfer from Old Library to New Manual

Should be moved in https://github.com/threefoldtech/info_grid/pull/77

@sasha-astiadi
I was working on this issue and the link that mentioned here was a part of the missing docs I added, I mentioned the PR above, you can check if the advanced tab included.

@Mahmoud-Emad thank you i will check

done on staging https://www2.manual.grid.tf/advanced/token_transfer_keygenerator.html thank y9ou @Mahmoud-Emad


METRON-2041 RegularExpressionsParser in wrong source folder

Contributor Comments
https://issues.apache.org/jira/browse/METRON-2041
This is moving a parser class that ended up in the test directories back to src.
Origination here - https://github.com/apache/metron/pull/1249/files#diff-a6c16544ef9e7a3e932eca63ee1eedb5
Testing

Travis should pass
Verify - RegularExpressionsParser should be bundled with metron-parsers-common.

Pull Request Checklist
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

n/a Have you included steps or a guide to how the change may be verified and tested manually?

n/a Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh

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

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

[ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

n/a Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

+1 Ouch.  Good catch.


Added drop table statements to some of the ctas tests

Abhishek,
I added drop table statements for most of the ctas tests. I had a functional run with known issues. Can you kindly review it?

Rahul

Looks good. +1


feat: add usageDescription option for darwin/mas targets

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] The changes are appropriately documented (if applicable).
[x] The changes have sufficient test coverage (if applicable).
[x] The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:
Adds a convenience option to set usage descriptions for the macOS store, on darwin/mas targets.
Reference: https://github.com/electron/electron/pull/19871#pullrequestreview-278011263

Codecov Report

Merging #1049 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1049      +/-   ##
==========================================
+ Coverage   99.42%   99.42%   +<.01%
==========================================
  Files          14       14
  Lines         695      699       +4
==========================================
+ Hits          691      695       +4
  Misses          4        4

Impacted Files
Coverage Δ

src/mac.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ce21c5d...525c04d. Read the comment docs.


"No such file or directory" when building with drush makefile

Issue Type

Bug Report / Support Request

Your Environment
Vagrant 1.8.7
VirtualBox 5.1.10r112026

ansible <IP_ADDRESS>
  config file = /etc/ansible/ansible.cfg
  configured module search path = Default w/o overrides

Your OS

Linux (Ubuntu 16.04)

Full console output
https://gist.github.com/ameenshake/dee57a0558c7b3b4496b4cd6944a03f3
Summary
Building new DrupalVM from scratch throws the following error:
TASK [Generate Drupal site with drush makefile.] *******************************
fatal: [drupalvm]: FAILED! => {"changed": false, "cmd": "/usr/local/bin/drush make -y /tmp/drupal.make.yml --no-gitinfofile", "failed": true, "msg": "[Errno 2] No such file or directory", "rc": 2}
	to retry, use: --limit @/home/ameenshake/drupalVM/drupal-vm/provisioning/playbook.retry

PLAY RECAP *********************************************************************
drupalvm                   : ok=138  changed=0    unreachable=0    failed=1

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

Not sure what to do here. I have tried deleting .vagrant and .vagrant.d. I have tried sshing into the VM and doing "composer install". Please help.
This is my drupal.make.yml: https://gist.github.com/ameenshake/8ad57b9e9c6e21f51d5f43df7198db14

Are you using the latest master of Drupal VM? We recently made the drush installation optional and it seems you might be using an outdated config.yml.
Make sure you have drush listed in installed_extras.

Ah yes that is it, I was using the latest master with the old config.yml. Thank you very much, you saved the day.


Fixed iOS 9 deprecation warnings in PFAlertView, PFPushUtilities.

If used with Cocoapods and minimum deployment target is set to iOS 9 - these two places were providing warnings.

Added compile time check for PFAlertView
Made PFPushUtilities use PFAlertView

@nlutsenko with this one i'm getting now an issue... i updated to 1.10.0 through pods...
My target is set to iOS 8
getting now the following..
..../Pods/Parse/Parse/Internal/PFAlertView.h:22:1: 'showAlertWithTitle:message:cancelButtonTitle:otherButtonTitles:completion:' has been explicitly marked unavailable here
..../Pods/Parse/Parse/Internal/Push/Utilites/PFPushUtilities.m:63:18: 'showAlertWithTitle:message:cancelButtonTitle:otherButtonTitles:completion:' is unavailable: not available on iOS (App Extension)
have an extension for today widget.
Thanks much for feedback and best regards,
Christian

@code-K, the issue is fixed in #642 and will be included in the new release of the SDK.
You can get it faster - by referncing master of the repo in your Podfile.

@nlutsenko Thanks much for the feedback! Works fine with master! :+1:


ONNX: export failure: Unsupported: ONNX export of operator adaptive pooling

Thank you for your work. I encountered an error while trying to convert best.pt to ONNX. How can I resolve it?
ONNX: export failure: Unsupported: ONNX export of operator adaptive pooling, since output_size is not constant.. Please feel free to request support or submit a pull request on PyTorch GitHub.

Updating to torch version 2.2.2 resolved this issue.

谢谢你的工作。尝试将 best.pt 转换为ONNX时遇到错误。我该如何解决？
ONNX: export failure: Unsupported: ONNX export of operator adaptive pooling, since output_size is not constant.. Please feel free to request support or submit a pull request on PyTorch GitHub.

Hello,I want to know where is data?How to run?Can you tell me?Thank you very much

python3.8 detect.py --weights ./best.pt --source mydata/test/1.png --data data/coco.yaml This way works. the --data parameter has no effect.

sorry,I  still don't quite understand what you mean,"We have looked through the code content and did not find any specific code related to fatigue driving. We are not sure where the dataset is. Could you please confirm if you have run it?"


Update LND guide to v0.16.2

What
Updates LND guide to newly released v0.16.2.
Why
Keeping up with latest developments and improvements (see release notes).
Scope

[X] significant change to core configuration
[ ] independent bonus guide
[ ] simple bug fix

Is it worth swapping it to use a VERSION variable assignment to be consistent with the way we're going with the other guides?
$ VERSION = "0.16.2-beta"
$ wget https://github.com/lightningnetwork/lnd/releases/download/v0.16.1-beta/lnd-linux-arm64-v$VERSIONa.tar.gz
etc..

Is it worth swapping it to use a VERSION variable assignment to be consistent with the way we're going with the other guides?
$ VERSION = "0.16.2-beta"
$ wget https://github.com/lightningnetwork/lnd/releases/download/v0.16.1-beta/lnd-linux-arm64-v$VERSIONa.tar.gz
etc..

PR related abandoned:
https://github.com/raspibolt/raspibolt/pull/1200

Is it worth swapping it to use a VERSION variable assignment to be consistent with the way we're going with the other guides?
$ VERSION = "0.16.2-beta" $ wget https://github.com/lightningnetwork/lnd/releases/download/v0.16.1-beta/lnd-linux-arm64-v$VERSIONa.tar.gz
etc..

Let's not mix different things in a single PR, that is out of the scope.

Line 256 still shows old version number 0.16.0 (though log timestamps are old and don't match as well). So up to you if you wanna touch the log output.

Fixed in 6af4ad1b1a7bef2e33d6101abf9d85aca191d33a


Domain activation is Failed - CNAME activation fails but CNAMEs do not previously exist.

App Id: d1wa0wwusudt8t
Region: us-west-2
Step: Domain activation
Status: Failed
Issue/question
Domain activation tells me One or more of the CNAMEs you provided are already associated with a different resource. but I can confirm that this is not the case. I start by manually deleting the associated CNAMEs in R53, then Retry domain activation and the same message occurs.
Error message
One or more of the CNAMEs you provided are already associated with a different resource.

It looks like the issue was that I had moved the old WWW CNAME record to from www.domain.com to www.old.domain.com. Renaming that to old.domain.com fixed the issue.


Dark toggle

Hey have you tried adding a dark theme toggle. Ive been trying to add following this tutorial, but was only successful in making a toggle switch not actually changing the colors.

I added this piece of code
body.dark-mode,
body.dark-mode main * {
    background: rgb(45, 45, 45);
    color: #f5f5f5;
}

to ramium.css and you can see the result below

Would greatly appreciate if you can include this feature by default. All other changes to partials were added in the site root /layout

Or an automatic setting where the site chooses dark or light mode based on the browser settings as in the  hugo-coder theme

@chain-ed-reaction
Thank you for taking an interest in Ramium. Although adding a dark mode was not what I had planned, I'll see if it is feasible to add it. It may take some time though.


virus-like installation behaviour

Microsoft PowerToys version
0.49.1
Running as admin

[ ] Yes

Area(s) with issue?
General
Steps to reproduce
Hello, I'd not seen the message below when installing previously !
The setup must update files or services that cannot be updates while the system is running. If you choose to continue, a reboot will be required to complete the setup.
So, what services and files ?
Separately, it spent AGES at pre-installation, it turns out it was looking at all of my spun-down external USB drives because it finally proceeded and wanted to do stuff with my I: drive.
No, do not touch ANY of my other drives unless I tell you to, I have good reasons for keeping them EXACTLY as I arrange them with no other "funny software" toying with them !
It seems to be virus-like behaviour !
✔ Expected Behavior
Plain installation where I tell it to !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Do not "invisibly" *uck with my hard drives !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
And also tell me what is being stopped/started/etc like other well behaved software !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I'll be uninstalling the old version ASAP until I'm convinced this is good and safe software.
❌ Actual Behavior
wanted to stop/start services and replace files and reboot.
tried to invisibly *uck with my external hard drives.
(it was directly downloaded from the github release page and "checked" with virustotal)
Other Software
No response

Related to #13007, #13041

I assume this is related to the SVG/MD/PDF preview or thumbnails.
Perhaps Windows requested for a preview/ thumbnail for a file in your external drives?

I'm sure this must be solved by now

I assume this is related to the SVG/MD/PDF preview or thumbnails. Perhaps Windows requested for a preview/ thumbnail for a file in your external drives?

Well, no other software I've installed over the years has done that.
I do not generally believe in "it's OK" nor in coincidences, having worked in IT for a few decades ;)

@hydra3333 Latest version is .58 now. Although there are a few (different) known issues for some, what is the status for this issue now?

Sorry, @Jay-o-Way I do not know.
After the issue occurred the product removed and I am not willing to try again.
Something like that indicates a level of QA which I'm uncomfortable with.


additional status return

Feature-request
Description
Add additional status output beside success-flag and error-message, which is necessary for libKitsunemimiHanamiMessaging.

also made some internal restructuring regarding the forwarding of error-messages.


Mention availability zones

In the SLA section it would be good to mention Availability Zones and the 99.99% SLA.

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

ID: 4b12d12e-2ae0-5aeb-72fe-ec2712e1167f
Version Independent ID: c96264a2-0898-887f-d945-cd9cee2e788e
Content: SAP HANA availability on Azure VMs - Overview
Content Source: articles/virtual-machines/workloads/sap/sap-hana-availability-overview.md
Service: virtual-machines-linux
GitHub Login: @msjuergent
Microsoft Alias: juergent

Thanks for the feedback! We are currently investigating and will update you shortly.

@dohughes-msft good catch! I have updated the doc and also updated the link to the latest SLA documentation. Once the PR merges the changes will go live after a few hours.


Getting warning message "Matches multiple schemas when only one must validate." in host.json file

I have created a default python v2 http triggered function in vs code. When I clicked on host.json file, I can see Matches multiple schemas when only one must validate. warning message.
host.json-
{
    "version": "2.0",
    "logging": {
      "applicationInsights": {
        "samplingSettings": {
          "isEnabled": true,
          "excludedTypes": "Request"
        }
      }
    },
    "extensionBundle": {
      "id": "Microsoft.Azure.Functions.ExtensionBundle",
      "version": "[4.*, 5.0.0)"
    }
  }

It looks correct and matches with the ms doc but still throwing warning. My function works as expected after having the warning message.
I tried to restart the vs code and Azure function extension too but neither helped.
I am using latest version of vs code(1.88.1) and latest core tool as well.

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

ID: 27150c55-615f-fb44-d5e4-7b5815631c7d
Version Independent ID: 271006dc-afce-99f3-0790-41fa2e35b22b
Content: host.json reference for Azure Functions 2.x
Content Source: articles/azure-functions/functions-host-json.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@ikhtesam
Thanks for your feedback! We will investigate and update as appropriate.

I encountered the same issue @ikhtesam. However, it's more related to the Functions extensions tooling. I've created a new issue in that repo linking this issue. Please feel free to follow that one.
#please-close

Hi @ikhtesam, the issue I created was resolved. It comes down to multiple extensions adding a validation schema. So, you can disable extensions you don't need on that workspace, like Logic Apps.


Swizzling not in regular Pod

The pod code does not include the +load method for object swizzling.  It's in the sample as part of the development pod.  Thanks for putting this together!

Thanks @anderkh! We'll bump the pod version shortly once we resolve a couple more issues. I'll leave this open to note that needs to be done.

Bump.
Any update on this? The pod version (0.1.0) also doesn't have the new selection event features. It would be nice to get this as soon as possible!
Thanks for the work.

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

I think that's the same as my issue here https://github.com/Instagram/IGInterfaceDataTable/issues/27