Open API data for Nottingham Public Transport

Hi @simonprickett
A very Interesting project you created with the scraping of the NCT website to format it into a JSON API.
I too have been on a quest to understand where the live timing data for Nottingham Public Transport comes from. A potential project I wanted to look at was displaying the latest times for public transport at certain times on digital signage within Nottingham College (my employer) at our campuses, but the lack of reliable/official API is somewhat of a barrier!
A long time ago there was an open API for the NET Tram under robinhood.arcticapi.com, this went NXDOMAIN a few years ago, credit to @mrrothe, who did some DNS analysis of the mobile app and came across it and created a real-time display as a PoC, although the benefit of this, was that the API had a specification and had production usage: https://github.com/mrrothe/Realtime-Tram-Display. Suprisingly, it was completely open with no authentication at all, it was however just for NET Tram data, but seemed to be the real data matching the stop displays. I even used it for a time, to check when Trams were coming before leaving the office, back when Nottingham College had a Beeston campus on HIgh Road.
For NCT, they announced in 2019 around supporting Open Data initivates with various data sources available, but not the real-time info. I did potentially come across a GOV.UK open data API: https://www.travelinedata.org.uk/traveline-open-data/nextbuses-api/, it is unclear if NCT real-time data is present, but I was potentially going to enquire as it appears to free for a certain amount of requests in a 6 month period, the usage rates seem generous too. In theory it covers operators across Great Britian, so Trentbarton and others too, but I don't know if real-time is there, as the API access is behind authentication, which you have to fill out a form on to access.
I don't know if you've considered loading the mobile apps on a mobile device which is routed through a proxy where you can MITM the traffic to see if there's any interesting API related calls that might provide further clues on how this data is being sourced? I was going to have a look potentially. Given the various bus stops in Nottingham now display multiple operators under a single stop, I suspect that the Robin Hood Network must have some form involvment that covers all major operators, but the open API availability is unlikely.
I could never find anyone in the know who could provide information around official API information or how it works.
From general press releases from Transport Nottingham, there's small clues on how the infrastructure behind it, might work, but just very small bits: https://www.transportnottingham.com/projects/upgrading-real-time/

Some very low investigation, but interestingly that domain for the NET Tram that was NXDOMAIN, NCT, has their own: nctx.arcticapi.com, judging by the requests made by the app. I need to potentially MITM the traffic to see full requests, which is tricky, given newer Android app level changes.
https://nctx.arcticapi.com/operator for example, returns data.
Interestingly arcticapi.com clearly seems to be tied to the wider network.

BIngo!
https://nctx.arcticapi.com/network/stops/3390FO07/visits
There's your API data hiding away!

Plenty of API data, here's the live disruptions data: https://nctx.arcticapi.com/network/disruptions, which is possibly very useful for a use case I've been looking at.

Here's a summary of what Passenger told me about the arcticapi URLs:

You asked about an API. We don't have an official public API, and we don't tend to tell people about this, but we were impressed so I wanted to let your know that our json endpoint for stop departures currently does not require authentication and so is open for you to use for the moment
I can't promise we won't change it, and we're likely to be adding authentication here at some point.

BTW if you did want to use my API feel free - it's nowhere near its resource limits on Cloudflare so it won't cause me any issues.

Interesting information! At the moment the API looks pretty open and if very much like the NET Tram one, I have no idea what domain that is under now, although it was interesting it was called "robinhood" and not "nettram" or similar. I will potentially inspect the mobile app and see if it's querying another arcticapi endpoint,.
For example you can get the same data behind the service disruptions page on the NCT website, which is likely the most useful for our project/uses. Getting stop data is cool, but we've got a lot of students from different areas in the city, so listing them all, not easy or relevant! I do however appreicate the effort you've put in on this project. It was a fun read of your blog.
I'd be cool if they added authentication, providing they would allow access through API key/OAuth. Rate limiting, fair use, maximum requests in a timeframe, would be happy to play ball under guidelines providing it. I can guess if too many external services start calling this API, they might move on doing that.

Just for further info, I came across http://nottingham.tramlive.co.uk/ for tram times, as it uses AJAX it is easy to see the HTTP requests being made for the stop data e.g. http://api.tramlive.co.uk/api/N17 which is Forest Recreation Ground, looking at the API data it does not appear to be real-time. I suspect this data is coming from the NextBuses API which is being provided by the this open dataset: https://www.travelinedata.org.uk/traveline-open-data/traveline-national-dataset/.
I believe National Rail Enquiries provides real-time data through something called Darwin, which is openly accessible, providing you register an account with personal/company information and be approved.
It is frustrating though, because so far I'm up to three different entities in terms of accessing different datasets for different services.

Passenger Group which now appears to be just for NCT.
Traveline for the NextBuses API which may or may not have real-time data but possibly covers all major operators in the city.
National Rail Enquiries for real-time train information at different stations which in this case would be for Nottingham Station.

Using the mobile apps for clues/possible APIs is actually a bit more of challenge given use of TLS and MITM on app traffic is rather difficult given Google's more recent changes to Android, I mean obviously I understand why as normally a MITM on SSL/TLS is bad news, although possible running an Android Emulator may be an alternative, given the need to mess with a lot of root/high level stuff to achieve it.
Haven't looked at Trentbarton, I vaguely remember there being a Hugo app for live times, which still seems to be working and displays other transport providers, other than Trentbarton so that must be also be provided by another party that's not just itself.
Yay for reverse engineering with no information what so ever!

Sadly it is a possibility that due to the council's financial situation live bus displays may go away (and I guess the system behind them too).  See https://twitter.com/nct_buses/status/1746584770492891171

Yeah they're raising car parking costs on street and in city council car parks, while also talking about closing the two big bus based park and ride locations to save money.

@jamesmacwhite FYI my service is broken at the moment due to changes in the underlying HTML on NCT's website.
I'm addressing it here:
https://github.com/simonprickett/nctx-stop-api/pull/9

Thank you, I've ended up sticking with just travel disruption data from NCT, rather than live times, as there's far too many journey variables to display accordingly that's relevant for the 10 campuses at Nottingham College.
I have found various different APIs and services from different providers during my research, I even had a contact at Trentbarton kindly provide how the Nottingham real-time data for operators works and where they all feed into.
Happy to drop you an email with the details if you find it useful.

FYI @jamesmacwhite you might want to have a read of this thread. https://x.com/acsnottingham/status/1757081554260471950

@simonprickett Interesting stuff! Inspecting the mobile app with HTTPS interception the endpoints of interest are:
https://nctx.arcticapi.com/ticketing/topups - Lists all ticket products
With an example ticket product (Single Help for Households):
https://nctx.arcticapi.com/ticketing/topups/736e399f-a651-4c25-aa17-4c95c2ac1470
Or another example (City Zone):
https://nctx.arcticapi.com/ticketing/topups/1e41e45d-43dc-4005-afe1-d0cccf2c4be1
It's great that real-time fare data is something that is implemented in the BODS specification.

@simonprickett

In response, officers managed to change the proposals in "small ways", including finding money to retain Linkbus services, including Easylink, keeping real-time information at bus stops as well as saving the Queens Drive and Racecourse Park and Ride sites from closure.

https://www.bbc.co.uk/news/uk-england-nottinghamshire-68288969
Looks like Nottingham City Council will be keeping the real-time stops alive!


Question on defining the Sequential SRAM

Hi! I was wondering if there is a way to define a Sequential SRAM on CiMLoop.
Thanks!

Closing for inactivity. Please reopen if the issue is still active.


Workload Port UI issues

Rancher versions: 2.0 master 3/2
Steps to Reproduce:

Go to Add Workload
Click on Add Port button

Results:

[x] Nodes running on a Pod text is running into the "v" area of the drop-down

[x] If Source Port is missing the error says Public Host Port.  It should say Source Port so it matches the UI

[ ] Source Port is required so add a * to it

Version - 2.0 master 3/3
Verified fixed


Add mypy.ini

A copy from https://github.com/google/scaaml
Fix https://github.com/google/sedpack/issues/13 and https://github.com/google/sedpack/issues/61

As you started moving things to pyproject.toml, just letting you know that mypy configuration can also live in the toml file


Add new InterruptNumber trait

This is a first go at the new trait needed for https://github.com/rust-embedded/svd2rust/pull/455 since we removed Nr from bare-metal.
In this case I've written it as unsafe trait InterruptNumber: Into<u16> rather than providing a conversion method inside the trait; I think this is neat and idiomatic but please correct me if there's a reason to not do it like this.
Here's a playground link showing an example implementation.

r? @korken89
(rust_highfive has picked a reviewer for you, use r? to override)

I like it! I'm also a big fan of the Into<u16> idea. 😉

I've updated to fix the failing CI (due to the use of some &InterruptNumber types; Into isn't implemented on reference types). The new trait now requires Copy and I've removed use of references.

As discussed in todays meeting this should be adjusted to lose the Into<u16> trick and provide a number method instead. Everything else seems ready to go.


INFINITY-1793 Fix strict mode tests for foldered services (probably)

Foldered services are exercised as /test/integration/svcname which maps to a role of test__integration__svcname-role
Removes svcname2 role setup, as grep -R 2 frameworks/*/tests/ shows that tests aren't installing a separate 2 instance anymore. Comments imply this was once the case in dcos-hdfs-service which is now long gone.

retest this please (unit test timeout flake)


Add quiet description and touch ups

Signed-off-by: TomSweeneyRedHat<EMAIL_ADDRESS>Adds verbiage to the quiet command an makes few other touch ups.

@rh-atomic-bot r+ 0d51d09


fix(table): broaden abstraction for filtering

Currently the user can customize the MatTableDataSource's filtering by providing a custom function of how to convert a data object into a filter string.
This may be too in-depth for most users and not as intuitive.
This PR broadens the abstraction so that users instead will define a function that accepts data and a filter string, and returns true/false depending on if the data matches.
This also allows the data source some freedom in defaulting to a behavior where it trims/lowercases the filter but allows users to override that behavior easily.

Renamed the filter function to filterPredicate


Roboto: Font request failed with reason code: -1

Requesting a font. Query: name=Roboto&weight=400&width=100.0&italic=0.0&besteffort=true

Did you install the beta version of Google Play Services?
https://developers.google.com/android/guides/beta-program

@thagikura No, I didn't. In the official guideline there is no word about it as I see it:
https://developer.android.com/preview/features/downloadable-fonts.html
Maybe there is a problem, thanks.

It's mentioned in the README in this sample app, not in the documents on developer.android.com since this is a workaround until the v11 version of the Google Play Services (which has the feature for behaving as a font provider) becomes a public version.

Please reopen this if you still see the issue after you install the beta version of Google Play Services.


Ferature Request: Add support for Batch Requests

As documented here: https://developers.google.com/gmail/api/guides/batch it would be ideal to also add support for batch requests.

This is something I overlooked in the first iteration to gain simplicity (we now have three or four request methods used for all calls). This probably needs a way to represent requests as objects that can be sent one-at-a-time or multiple at once by a call.

I was wondering here - with async operations, is there a big difference between sending batch requests in the first place and sending several requests at once, and join!ing/join_alling them? And given that the batch interface is usually "concatenate raw HTTP requests into a multipart/mixed body", which brings considerable complexity into the picture, this may actually be not that bad as an alternative (caveat: as long as hyper does this the way I hope it does, i.e. using HTTP/2 as it is intended to be used, with concurrent streams etc.)
It shouldn't make a big difference in terms of quota, or transferred data volume, while keeping the logic much more simple. What am I missing?


Checkmate

Sent an email to support and sales. No api docs online or obvious way to setup a developer account.
I did start a free account only to find out it is a 2 week trial.
https://start.1password.com/open/i?a=5LPILPRDUBGWBPJWYS6QHHHLRE&v=j5rloag3ijafxntkpw5wct23dy&i=fptu7vnhymdd2hs66iwsih5ruq&h=ethyca.1password.com

This will need to be a maildrop connector!

Reopened as we have been given the checkmate api docs https://openapi-itsacheckmate.readme.io/reference/getting-started

The api docs for Checkmate do not include any personal data endpoints. We know they have to exist to populate the Customer Portal. The api docs state we can get the postman collection if we go to the Platform App. The free trial account we setup does not have the Platform App.
We are reaching out to Checkmate to get their postman collection.


Sqlx depend on libsqlite3-sys if sqlite feature is disabled

Bug Description
Sqlx depend on libsqlite3-sys if sqlite feature is disabled.
Minimal Reproduction
❯ mkdir sqlx-test
❯ cd sqlx-test
❯ cargo init

add the following dependecies to the Cargo.toml
matrix-sdk = { version = "0.7.1", default-features = false, features = ["native-tls", "e2e-encryption"], optional = true }
sqlx = { version = "0.8.2", optional = true, default-features = false, features = ["runtime-tokio", "migrate", "postgres", "macros"] }

❯ cargo run
    Updating crates.io index
error: failed to select a version for `libsqlite3-sys`.
    ... required by package `rusqlite v0.30.0`
    ... which satisfies dependency `rusqlite = "^0.30.0"` of package `matrix-sdk-sqlite v0.7.0`
    ... which satisfies dependency `matrix-sdk-sqlite = "^0.7.0"` of package `matrix-sdk v0.7.1`
    ... which satisfies dependency `matrix-sdk = "^0.7.1"` of package `sqlx-test v0.1.0 (/home/lukas/test/sqlx-test)`
versions that meet the requirements `^0.27.0` are: 0.27.0

the package `libsqlite3-sys` links to the native library `sqlite3`, but it conflicts with a previous package which links to `sqlite3` as well:
package `libsqlite3-sys v0.30.1`
    ... which satisfies dependency `libsqlite3-sys = "^0.30.1"` of package `sqlx-sqlite v0.8.2`
    ... which satisfies dependency `sqlx-sqlite = "=0.8.2"` of package `sqlx v0.8.2`
    ... which satisfies dependency `sqlx = "^0.8.2"` of package `sqlx-test v0.1.0 (/home/lukas/test/sqlx-test)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the `links = "sqlite3"` value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

failed to select a version for `libsqlite3-sys` which could resolve this conflict

Additional Info
Looks like this only happen if the migrate is enabled.
Info

SQLx version: 0.8.2
SQLx features enabled: "runtime-tokio", "migrate", "postgres", "macros"
Database server and version: no idea. do not even get to this stepp
Operating system: Arch Linux
rustc --version: rustc 1.81.0 (eeb90cda1 2024-09-04)

thanks, for the fast feedback. sadly the other version is out of my control.

a small hack to workaround this issue is to use [patch.crates-io], to patch one  libsqlite3-sys version to not use the c dependency anymore.
Cargo.toml:
[patch.crates-io]
libsqlite3-sys = { path = "./dummy-libsqlite3-sys" }

dummy-libsqlite3-sys/Cargo.toml:
[package]
name = "libsqlite3-sys"
version = "0.30.1"

[features]
default = []
bundled = []
pkg-config = []
unlock_notify = []
vcpkg = []

dummy-libsqlite3-sys/src/lib.rs:
//! Hack, due cargo bug


Cannot record simple voice chat

Replay has no voice, after "record_voice_chat" was set to true.
Client has replay-voice-chat installed, and has no problem recording and playing voices in single-player replay recordings.
server replay version: 1.1.1+mc1.21
simple voice chat version: 1.21-2.5.18
replay voice chat version: 1.21-1.3.8
fabric loader verison: 0.15.11

Please update ServerReplay. See #47


Selecting multiple data points by selecting a rectangular area on map.

Hello, my main goal is to make multiple selection of points by selecting an area on the map.
Is it possible to make a selection of points by mousedown+move. I know that this action will make map to pan, ctrlKey+mousedown+ move can be an option. Any help will be useful.

My apologies for the delayed response - my day job has been busy recently.  I'm sure this is possible with a little bit of work.  I'll try to post an example soon.  In the meantime, you could also try reaching out to the primary Leaflet developers, since others might have this question with Leaflet in general.


editor configuration

So I don't know if I missed something in the readme or config.md but I had to search in the code to see that the EDITOR variable had to be set if I wanted to use something other than vi when selecting files. Would it be possible to add a config option to set the command for the editor in the config file ? And if nothing is set, use the EDITOR variable, and if it's not set, vi.

Tried doing contributing for the first time in my life to an open source project, so I don't know if I've done things right ^^'
https://github.com/dzfrias/projectable/pull/18

Looks great, and it works for me too! Thanks for contributing!


Inline form-groups for compound controls

There's a need to be able to align form controls horizontally sometimes. The date-of-birth picker is one example, but there are others (units-per-time-period for example).
Rather than have a date-specific style, why not have a generic 'inline-form-groups' wrapper?
That's what this pull request does. As it stands, I've removed the old date styles, so it's a breaking change for anyone who's used them.
Also, this request relies on #81 (fixed width form controls) - but I added it again as a commit here (sorry).

I've moved the styles for generic inline-form-groups over to:
https://github.com/alphagov/govuk_elements/tree/add-test-form-page
Rather than make this a breaking change, I'll leave the form-date pattern - and mark it as deprecated,
this will mean it won't break for anyone using it - but we can let them know to update the html to use the new pattern. I'll also update the examples so they show how to use the new inline wrapper.


GraphQL: fix handling of DATE type

CustomScalar.DATE uses the following to parse GraphQL values:
o -> java.sql.Date.valueOf(o.toString())

This is not going to work. That value is later passed to QueryBuilder.literal(), which uses the default Java driver mappings. DATE maps to java.time.LocalDate, not java.sql.Date.

I'll do it as part of scalar revisit #272 and validation #261


Ability to get Requirements linkings and properties

The API should provide ways to get Requirements linkings to Test Cases (for example, it should give the Map of requirements linked to TC-1) and their properties (for example, Req Status, Coverage, Relations ...)

+1

+1

@basraouik agree with it, but when you say "The API", remember this Java API is just a mere facade to the PHP XML-RPC API. In case you know of a method (even if it's in the JSON API, we can start working on the JSON client too) feel free to update the ticket, as that would make it easier to check how hard it would be to implement it.

Closing as this needs to be discussed in the PHP backend. See methods related to requirements in the latest (1.9.19) release:

uploadRequirementSpecificationAttachment
uploadRequirementAttachment
assignRequirements
getRequirementCustomFieldDesignValue
getRequirements

Once the PHP API gets a new method, we can add the Java new call.


no me carga mis proyectos cuando los descomprimos

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


elixir: 1.15 -> 1.16

Description of changes
Switch the main elixir to 1.16
Someone generously fixed elixir_ls building with 1.16 so this should be fine to switch now.
I'm going to leave this open for a couple of days to make sure everyone has time to have a look if they want to.
@NixOS/beam
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 299592 run on x86_64-linux 1

4 packages failed to build:

elixir
elixir-ls
elixir_1_15
mix2nix

Result of nixpkgs-review pr 299592 run on x86_64-linux 1

3 packages built:

elixir
elixir-ls
mix2nix


The error was: 'dict object' has no attribute u'b8: 27:

Hi Jeff,
Thank's for the "Ansible for..” book & your amazing open source pidramble project.
I'm having trouble running Ansible <IP_ADDRESS> on my MacOS Sierra PB:
ansible-playbook -i inventory main.yml
…..
set_fact:
dramble_hostname: "{{ mac_address_mapping[dramble_mac_address].name }}”
...
"FAILED! => {" Failed ": true," msg ":" the field 'args' has an invalid value, which appears to include a variable that is undefined. The error was: 'dict object' has no attribute u'b8: 27: eb: ec: ff: 3d '\ n "
"{{mac_address_mapping [dramble_mac_address] .name}}"
What I ...understand Ansible can not read the ”mac_address_mapping” syntax, has the syntax changed?
Or Am I missing some additional Ansible extension  …?
I’ve followed your instructions…  carefully?smile.png
Best regards / p

It looks like that might be a quoting issue—can you paste in an example of how you changed the networking settings? It should be like:
mac_address_mapping:
  "d8:eb:97:b3:88:27":
    name: bal1.pidramble.com
    ip: "<IP_ADDRESS>"
  ...

Notice the quotes around the entire d8:eb:97... part — without those quotes, the YAML parser will get very confused by all the colons.

This is pat of the changes:
mac_address_mapping:
"B8:27:EB:EF:7D:B1":
name: bal1.pidramble.com
ip: "<IP_ADDRESS>"
"bB8:27:EB:EC:FF:3D":
name: www1.pidramble.com
ip: "<IP_ADDRESS>"
....
/p

Resolved! "bB8:27:EB:EC:FF:3D": to many bees:) and now all in lowercase letters, do not know if it matters /p


Backup is very... very... slow

The app takes a considerably long time to back up, even just SMS. It has taken from 10:56AM EST to now 2:27PM EST to get only 5649 SMS backed up, not including MMS.
Logs state the backup finished at 10:56AM EST as well, but I know that is not true.
I am running SMSBackup+ v1.5.10 on the HTC 10 (US Unlocked) with the latest software updates. Android version is 7.0 Nougat.
See below for the app logs with extra debugging information:

07-15 10:56 Backup requested (manual)
07-15 10:56 Starting backup (MANUAL)
07-15 10:56 Skipped (no items found)
07-15 10:56 BackupState{currentSyncedItems=0, itemsToSync=0, backupType=MANUAL, exception=null, state =FINISHED_BACKUP}
07-15 10:56 Backup finished
07-15 10:56 Backup requested (manual)
07-15 10:56 Starting backup (MANUAL)
07-15 10:56 Skipped (no items found)
07-15 10:56 BackupState{currentSyncedItems=0, itemsToSync=0, backupType=MANUAL, exception=null, state =FINISHED_BACKUP}
07-15 10:56 Backup finished
07-15 10:56 Backup requested (manual)
07-15 10:56 Starting backup (MANUAL)
07-15 10:56 Skipped (no items found)
07-15 10:56 BackupState{currentSyncedItems=0, itemsToSync=0, backupType=MANUAL, exception=null, state =FINISHED_BACKUP}
07-15 10:56 Backup finished
07-15 10:56 Backup requested (manual)
07-15 10:56 Starting backup (MANUAL)
07-15 10:56 Skipped (no items found)
07-15 10:56 BackupState{currentSyncedItems=0, itemsToSync=0, backupType=MANUAL, exception=null, state =FINISHED_BACKUP}
07-15 10:56 Backup finished

I also had this problem.  The progress pace was like 1... 2... 3... 4... and so on. Happy to provide more info if needed.

+1: Anyway to speed it up?
(Another user with 50k messages - seems, I had restored from GMail once, and now I cannot choose to do a part upload :-( )


Jsdoc tooltip showing raw tags

The tooltip is showing all the jsdoc information except for the @param tags.
Eg. jsdoc:
/**
 * Filters a path based on a regexp or glob pattern.
 * @param {String} basePath The base path where the search will be performed.
 * @param {String} pattern A string defining a regexp of a glob pattern.
 * @param {String} type The search pattern type, can be a regexp or a glob.
 * @param {Object} options A object containing options to the search.
 * @return {Array} A list containing the filtered paths.
 */
function pathFilter(basePath, pattern, type, options){
//...
}

The tooltip shows like this:

I'm using the january version without Salsa enabled.

Also the type paramater of the type argument is shown as any in the parameter hints

This issue was moved to Microsoft/TypeScript#7136


How to Improve the Stability of Clustering Results with VGAE?

Thank you for sharing your code and great work! I have been running the code and using the VGAE to extract features for clustering. However, I’ve noticed that the clustering results are inconsistent across different runs—sometimes the results are good, and other times they are less optimal. I assume this variation is due to the randomness involved in the VGAE feature extraction process.
I would like to ask for your advice on the following:
1、How can I achieve more stable and consistent clustering results? Are there any techniques to minimize the variability in the features extracted by the VGAE?
2、Could adjusting the model or clustering algorithm parameters, or applying some kind of post-processing (e.g., dimensionality reduction or regularization), help to improve the stability of the clustering results?

@heheyiyi   This is caused by the implementation of train_with_dec. If you use train_without_dec, the result can be very stable and the performance only decrease slightly.


Need to clear indexed-db during version migration

https://github.com/penumbra-zone/web/blob/2fffe0f76a2cf1d5a0405d9fe27023832221254f/packages/storage/src/indexed-db/index.ts#L44
If we increase the indexed-db version, the upgrade function will try to create new object stores, but all of them already exist and we will get an error
Uncaught DOMException: Failed to execute 'createObjectStore' on 'IDBDatabase': An object store with the specified name already exists.

I think we need to run clearCache() before creating new object stores
In the future it makes sense to do custom indexed-db version migrations that will preserve existing data, but for testnet we can just delete and re-create the tables

I thought if we bump the dbVersion, it needs to re-create those tables anyway because the structure of them could have changed. Are we not doing the standard way?

The problem is that we are not deleting tables, but trying to recreate them

UPD: we don't need clearCache()

for (const objectStoreName of db.objectStoreNames) {
						db.deleteObjectStore(objectStoreName)
					}

We should be doing something like this

But why isn't that in any of the upgrade examples in the documentation? https://github.com/jakearchibald/idb#readme
They all seem to be creating tables in the upgrade function without deleting any

Probably because in most cases these are examples of creating indexed-db tables, not migrating them.
Besides, the case of migration when we delete all data and recreate it is quite rare in practice, more often there is a need to save data during migrations.

At least right now migration doesn't work for us, you can try increasing the indexed-db version and updating the existing extension to get errors


Citation not working

When I cite your project in my paper using your bibtex from the GitHub page, the second link (arxiv) is not working.

Hi @andreagemelli
You need to use a BibTeX csl file that can interpret correctly the archivePrefix attribute in the BibTeX entry.
For example if the  unsrt (unsorted) BibTeX style, which is one of the four standard bibliography styles in BibTeX, it will generate this citation:

If you can't update/change your citation style, you will need to remove the archivePrefix attribute and find what's more appropriate in this style.


Add upcoming feature flag annotations

Based on conversations with the LSG, this PR adds an annotation to each upcoming feature flag that is enabled by default in an announced Swift language mode.
There is no annotation for flags enabled by default in a future, unannounced language mode.
For example, the ExistentialAny flag introduced with SE-0335 is not enabled by default in Swift 6 language mode and therefore does not have an added annotation (or appear in this PR).

Other proposals might also need updating, with the following upcoming features:

UPCOMING_FEATURE(StrictConcurrency, 0337, 6)

UPCOMING_FEATURE(ImplicitOpenExistentials, 352, 6)

UPCOMING_FEATURE(GlobalConcurrency, 412, 6)

UPCOMING_FEATURE(RegionBasedIsolation, 414, 6)

I'll take a closer look at these.


WIP adding status to Integration

Trying to keep it as simple as possible by simply adding two fields to  Integration: statusType and statusPhase.
In PUT request on /integrations/ the statusType can be set to 'Activated' or 'Deactivated'. This would then trigger Activation or Deactivation of the integration. The runtime (kubernetes watcher?) will update the statusPhase.
Comments welcome.

LGTM thanks!

Just waiting on checks to finish to merge.


[Style] [Ready] Update treebeard and misc modals to fit style guide

Purpose
Addresses Github issue https://github.com/CenterForOpenScience/osf.io/issues/3693
as well as other aspects of modals like buttons and headers.
Changes
Required a treebeard change where the modal structure now includes a modal header and classes are in alignment with bootstrap (i.e. using .modal-body instead of .tb-modal-content)  https://github.com/caneruguz/treebeard/commit/01707a0824f48c48d536d238ad3a0f92cc936f5c
On OSF side a large number of modal changes to reflect the new method of using tb.modal.update
Side Effects
Should not break any other treebeard instance as it only gets run with modals in treebeard. Checked with files and project overview pages and project organizer. Should not have any side effects.
Example of new look with adjustments

@sloria this is ready for review

Looks good. @caneruguz Can you make sure the treebeard SHA is correct and get this PR up to date with develop? Once those are done, this should be good to merge.


Can I hide the taskbar icon?

Description of the new feature / enhancement
Can I hide the taskbar icon?
Scenario when this would be used?
Can I hide the taskbar icon?
Supporting information
No response

/dup #9526

我是李柏霖，邮件已收到，谢谢！


[SUPPORT] How can I control the number of archive files

When I use clustering async, I generate a lot of archive files, similar to commits. archive. xx_ 1-0-1
how to control or clean up the number of these files
Environment Description

Hudi version : 0.9.0

Spark version : 2.4.7

Hive version : ~

Hadoop version : 3.1.1

Storage (HDFS/S3/GCS..) : HDFS

Running on Docker? (yes/no) : no

Hi @JoshuaZhuCN , I also meet this issue when using S3.
https://github.com/apache/hudi/pull/4078
Hope this PR can help you.

Hi @JoshuaZhuCN , I also meet this issue when using S3. Maybe the storage you used is not support append action. So that each time archive will create a new archive file no matter you use clustering or not. #4078 Hope this PR can help you.

thx，i try it again

Closing this issue as we have a patch out to trim the archive files. Feel free to reopen if you have more issues apart from the patch posted.


Draft expense errors when no amount is set

The expense flow lets you draft an expense without enforcing any amount. But if you try to submit it, you get a cryptic error from the API:

Validation error: Validation min on amount failed: Validation min on amount failed

Suggested solution
Enforce the amount to be set in the frontend.

@Betree, it looks like this issue is already fixed in the main branch.

@la-costa You're not trying with the "Invite" flow, where most fields are supposed to be optional. To trigger it, you need to pick a special value in the "Payee step":

We get a lot of occurences for this one: https://open-collective.sentry.io/issues/4637984981/?project=5199682&query=is%3Aunresolved&referrer=issue-stream&statsPeriod=90d&stream_index=13


fix(aws): Use EC2 Transit Gateway's region for the attachments

These resources don't return an ARN from the AWS API so we can't tell the region, but we can get it from their transit gateway

Fixes https://github.com/infracost/infracost/issues/349

Fixes https://github.com/infracost/infracost/issues/349

i'm really appreciate your support and involvement with bug fixing. You are amazing!!!

i'm really appreciate your support and involvement with bug fixing. You are amazing!!!

There are two parts to bug fixing (finding them and fixing them) - thanks you for helping us with the first part @dawidmalina!

There are two parts to bug fixing (finding them and fixing them) - thanks you for helping us with the first part @dawidmalina!


Minimum coverage?

Depending on the company/team's goals, they may prefer to have a minimum of coverage, and understand that they don't need to reach 100%.
Does it make sense to think of a solution within jest-it-up? Example: jest-it-up --minimum 70

What would be the expected behavior in that case? I suppose once the minimum coverage is reached, there would be no need for this tool anymore?


Do not attempt to switch variant when already on the correct property name

Describe the desired behavior
When an instance is on "Theme=Dark" already, and the "from Variant" is empty, do not attempt to switch anything
Describe the current behavior
It switches. This might cause the instance to reset (need to double check)

Received a bug report in the shared pxb email address today that is likely caused by this.


Build main components for the Artisan screen

Single artisan component
quotes component

@sunny775 can you provide me with more details as to how the component(s) should look like?


Feature Request: Water Shutoff Option

Some of the softeners support an optional water shutoff valve feature.  Could the presence, state and control of the valve be added to this integration?

please

The basic code exists, but someone needs to put it in.  My skills are not remotely good enough to do it, but someone probably can!  I wish they would.

Ill take a crack at it.

I can test it as I installed the feature in my system.

Ill take a crack at it.

You get anywhere with it? I spent some time today digging and i realized the work on a different fork to group everything as a device is huge improvement and it might make sense to start from there.
https://github.com/briis/homeassistant-iqua-softener
Not sure why he hasn't made a PR yet to merge those changes.
I've also got the valve installed to test with and may give it a shot myself in the near future. Haven't done any work in HA python code since the project started though.

Funny you ask. Been working on it as we speak.

I was also going to add a refresh interval to it.

Ran into some issues, would love some help with this.

Ran into some issues, would love some help with this.

Create a fork and publish what you have

https://github.com/mikedhanson/homeassistant-iqua-softener
Here are my changes.
The main thing that I could not figure out is how the integration downloads the code from https://github.com/jmacul2/iqua-softener to use the iqua.py
I hope someone can get this working.

Home Assistant handles the dependency by the manifest.json where requirements can be specified. iqua-softener is published on pypi and home assistant will automatically acquire it on launch.
A core problem might be that the published version doesn't include the water valve code yet. I think we need @arturzx to publish a new version of the iqua-softener package to fix this fully, or include the iqua-softener manually.
https://pypi.org/project/iqua-softener/#history
I'll see if I can sit down and test this out this weekend. It has been several years since I did any code work in home assistant, so no guarantees I can figure it out. I may just have to resign myself to writing a quick script that directly uses the iqua-softener to make it happen.

Any updates? @demonspork @arturzx

Any updates? @demonspork @arturzx

I'm sorry but I haven't had time to work on this project.

baby come back. You can blame it all on me.


Fix log-api module

Purpose
$subject.

Codecov Report

:exclamation: No coverage uploaded for pull request base (jballerina@00277ef). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             jballerina   #15843   +/-   ##
=============================================
  Coverage              ?   13.35%
  Complexity            ?     3377
=============================================
  Files                 ?     1488
  Lines                 ?    75396
  Branches              ?     9846
=============================================
  Hits                  ?    10070
  Misses                ?    64348
  Partials              ?      978

Impacted Files
Coverage Δ
Complexity Δ

.../ballerinalang/stdlib/log/AbstractLogFunction.java
0% <0%> (ø)
0 <0> (?)

...ain/java/org/ballerinalang/stdlib/log/LogInfo.java
0% <0%> (ø)
0 <0> (?)

...in/java/org/ballerinalang/stdlib/log/LogDebug.java
0% <0%> (ø)
0 <0> (?)

...in/java/org/ballerinalang/stdlib/log/LogTrace.java
0% <0%> (ø)
0 <0> (?)

...in/java/org/ballerinalang/stdlib/log/LogError.java
0% <0%> (ø)
0 <0> (?)

...ain/java/org/ballerinalang/stdlib/log/LogWarn.java
0% <0%> (ø)
0 <0> (?)

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 00277ef...22d02b9. Read the comment docs.

Should this be sent to master?


Hot key Window key + T key to open Window Terminal

Description of the new hot key
When users press Window key and T key, Window Terminal should open in the folder if they are in one, if not then open in Desktop.

Maybe you are talking about this? https://github.com/microsoft/terminal/issues/3158

Hmm I have read the comments until I found this The idea of that comment is similar to this. Therefore you can mark this one duplicate and close it or just close this when you push commits to add this feature.

If you're in explorer.exe, you can press ctrl+l, then type wt -d ., and that'll open the Terminal automatically in the current working directory.
I'm pretty confident that it's not possible to install a global hotkey on the system that can read the state of the active window and get the CWD of that process unfortunately. So I'll just resolve this as a /dup of #878, /dup #3158, /dup #653 for now.


Route53 latency support

Hi Team,
I need support for latency based policy DNS entries, octodns-route53 doesn't seems support this.
So, I propose an implementation based on existing structure for GeoLocation with an additional parameters mode to specify if this should be deployed with GeoLocation or Region.
I create a file (based on geo_data@octoDNS) to add mapping between GeoCodes & Region.
Tests & Coverage are been done
Please be free to comment or add requests

just dropping a note that I've seen this and have it on my TODO list. It's a big enough change and in a new enough are that it'll be a few days before I get to sit down and dig in and research it enough to get my bearings and evaluate things.

For your information and to assist you, the PR proposes a fully functional solution that incorporates the existing "octo-dns" behavior for dynamic records and "geos" structure. This solution features a revert mapping between specific country codes and AWS regions that can be enabled with a specific flag for the route53 provider. Although this type of feature is DNS-provider specific (such as AWS implementation and region names), I believe it can be seamlessly managed by the plugin.
But in an ideal world, the octodns core would include the capability to define another type of "dynamic records," such as "pops" or "latency" that would provide direct "identifier" support for each providers. However, this would require a significant overhaul, which is a larger change.

Thanks for your feedback.
I agree with you to expose this feature more directly without mapping, the only advantage of my idea is to permit an easy migration to another provider without configuration change because the record will be automatically converted into "geo-dynamic record" (if other provider support this) but the complexity tradeoff (and fallback requirement) is too expensive.
I think it's a good idea to use the pool name (and ignore rules).
I will try an implementation based on your comments (probably next week).
Last point, your internal implementation for this kind of record (rrset) is mainly based on "_Route53DynamicRule" class, so I think use it "transparently" to avoid duplicate code.

the only advantage of my idea is to permit an easy migration to another provider without configuration

Yeah. I throught about it for a bit too. I think portability can still be accomplished with naming pools for regions (which makes sense anyway since that's where the stuff would be running) and having rules that do what the user wants for non-Route53 providers should still be OK. The behaviors won't match up between Route53 and the other provider(s) but they wouldn't anyway since it's geo-ip rather than latency.
This did get me thinking about how octoDNS might provide users with pre-built rules. I don't think it'd be possible currently, but may fit in with some of the potential future work on sharing data between records.

Right.
So, I will rework PR to use pool name as region with specific flag for latency.
Thanks

Hi @ross, you can find here an update version implement your feedback.
Some notes :

octodns core rules validation (octodns/record/__init__.py) are strict and required rules without not-used pools for dynamic record (and don't allow duplicate default or something else to bypass the validation) after thinking and test, implement "rules" with geos (not used in latency context) permit allowing portability to another provider (with geolocation) and keep compatible with existing behavior (you can README to check final usage that seems to me clean)
a "default" rules in "latency" context is nonsense (doesn't support by R53 - no catch-all Region) and this can't be mixed (Geographical and Region) so I consider this case as a non-supported use case

And finally to be retrocompatible, I check that proposed config is compatible with older version of plugin (fallback to Geographical) with success.
Keep me in touch if you see something else.

octodns core rules validation (octodns/record/__init__.py) are strict and required rules without not-used pools for dynamic record (and don't allow duplicate default or something else to bypass the validation) after thinking and test, implement "rules" with geos (not used in latency context) permit allowing portability to another provider (with geolocation) and keep compatible with existing behavior (you can README to check final usage that seems to me clean)

Yeah. It would be my expectation that users still provide rules that make sense to them even though they won't be used when Route53Provider is configured in latency mode. This would allow them to push the records to another provider, either normally or in an emergency.
If they really don't want to bother they could either put a dummy list of geos in, one for each pool or use lenient on the record to turn the validation errors into warnings.

a "default" rules in "latency" context is nonsense (doesn't support by R53 - no catch-all Region) and this can't be mixed (Geographical and Region) so I consider this case as a non-supported use case

Makes sense. We'll just want to document that behavior.

Was doing some testing starting with the config example in the doc. Tweaked it avoid warnings in terms of key order and rules and came up with:
test:
  dynamic:
    pools:
      us-east-1:
        values:
        - status: obey
          value: <IP_ADDRESS>
      us-west-1:
        values:
        - status: obey
          value: <IP_ADDRESS>
    rules:
      - geos:
          - NA-US-VA
        pool: us-east-1
      - pool: us-west-1
  octodns:
    route53:
      dynamic_mode: latency
  ttl: 60
  type: A
  value: <IP_ADDRESS>

When I tried to apply it I got the following error:
botocore.errorfactory.InvalidChangeBatch: An error occurred (InvalidChangeBatch) when calling the ChangeResourceRecordSets operation: [RRSet with DNS name test.geo-latency.com., type A, SetIdentifier 0-us-east-1-NA-US-VA, and routing to [country = (*, Default)} cannot be created because a non-GEO RRSet with the same name and type already exists.]

The above error appears to be linked to having a catch-all rule (no geos) at the end of the rules section as best practices dictate.
I'm also running into similar errors if there are multiple geos specified for a rule, e.g.
      - geos:
          - NA-US-CA
          - NA-US-OR
        pool: us-west-1

botocore.errorfactory.InvalidChangeBatch: An error occurred (InvalidChangeBatch) when calling the ChangeResourceRecordSets operation: [RRSet with DNS name test.geo-latency.com., type A, SetIdentifier 1-us-west-1-NA-US-CA, and Region Name=us-west-1 cannot be created because a latency RRSet with the same name, type and region already exists.]

Sooo the more I looked into/explore this the more involved things got. The changes turned out to be too involved to just add as comments as a PR review here as there's some changes to approach required to get things to truly ignore rules and to be able to go back and forth between dynamic_modes cleanly. It actually required tracking down/fixing a bug, or perhaps better put shortcoming, in _extra_changes where it was just stuffing in the desired for both the new and existing items in the change.
Anyway, code that is working afaik to push/pull things with the correct behaviors is in https://github.com/octodns/octodns-route53/pull/53. There may very web more changes required after further testing and writing unit tests to get all the new paths fully covered. I've run out of time to look into this today. Please take a look at it.

About your tests AWS error is normal you have test exactly the use case not-supported  :

You have defined a "default" rules pool and this mean mix latency based record with a fallback wildcard Geographical Record (and this is impossible) your first example should be :

rules:
      - geos:
          - NA-US-VA
        pool: us-east-1
      - geos:
          - NA-US-CA
        pool: us-west-1

(like in README.rd latency example)
2) Your second example will impact (regarding rules implementation design) to create a RuleSet by Geoloc with pool name, in this case is impossible too (only one Record by Region)
I think README should be clearer and explicit this to case as not-supported
Regarding your comment about capabiity to completly ignore "rules" this is a good idea but a lot of core logic depends "rules" config (in dynamic records use case like "Id" Naming and thisimpact reversing from RRset and finally diff detection) so from my mind you can choose between some options  :

consider README as reference (with this specific tricks)
pre-process record config to remove default pool in rules and use only one (first) geos but I don't find anything in plugin architecture to do it (managed by core)
update core to delegate rules validation to plugin and in this case rules can be ignored for this specific use case
or if we imagine more generic pattern why use "rules" ? we can imagine define "geos" or "latency_pop" directly in pool like

pools:
      apac:
        # An optional fallback, if all of the records in this pool fail this pool should be tried
        fallback: na
        # One or more values for this pool
        values:
        - value: <IP_ADDRESS>
        - value: <IP_ADDRESS>
        geos:
         - AF-ZA
         - AS
         - OC
       latency_pop:
       - ap-southeast-1
      eu:
        fallback: na
        values:
        - value: <IP_ADDRESS>
          # Weight for this value, if omitted the default is 1
          weight: 2
        - value: <IP_ADDRESS>
          weight: 3
       geos:
       - AF
       - EU
       latency_pop:
       - eu-west-1
      na:
        # Implicit fallback to the default pool (below)
        values:
        - value: <IP_ADDRESS>
        - value: <IP_ADDRESS>
        - value: <IP_ADDRESS>
        geos:
        - *

(and select geo or latency regarding specific parameter... but this is a breaking change)

I check and test your commit that seems to be a good compromise, thanks

About your tests AWS error is normal you have test exactly the use case not-supported :

That is the case with things as implemented in this PR where it's still use _Route53DynamicRules, but that approach isn't ideal b/c it would limit what could be done when pushing the records to multiple providers. It's not a viable multi-provider setup if the record can only have 1 geo per rule.
We need to be able to fully utilize NS1/Azure/... with traditional rules even if Route53 is in latency mode.
https://github.com/octodns/octodns-route53/pull/53 adds _Route53DynamicLatency to specifically handle this case. There's a single one of those per pool. It should also makes going back and forth between modes more robust. It seemed theoretically possible to get rrset naming conflicts reusing rules.

No problem you have right, much better approach.
I try and test deeper your PR and found a bug :

you check all rrset to determine if a dynamic mode change (loop) exist but we can combine in same zone record a latency and geos records .. and so change detection fail in this case (unwanted change geos to latency record)

I propose to rework my PR with your version and propose a fix, readme update and coverage fix

you check all rrset to determine if a dynamic mode change (loop) exist but we can combine in same zone record with latency and with geos records .. so change detection fail in this case (unwanted change geos to latency record)

Can you comment on my PR where you see the issue. Not sure I follow.
I propose to rework my PR with your version and propose a fix, readme update and coverage fix
👍

Record method and emit warning about : "missing rules", "unused pools".. with "ignore rules" mindset there is no way to rebuild a virtual valid rules definition (like in my own PR), what we can imagine to bypass it ? (core change, fake rules, .. ?)

Yeah. I didn't see a way around this really. We could stuff in some "fake" rules just to make things happy enough for that check to pass. I'm not sure whether that's worth it.

Hi @ross,
I add comment in your PR to mention error that can be easily fix, and I found an improvement to clean internal Record object before zone diff computing (add rules reset in _process_desired_zone if dynamic_mode == latency) to be clean (permit compare Record from RRset and from Config without any rules in latency mode case)
Finally as you "expected", the "fake" rules isn't possible to workaround the Record Validator (from RRset reverse).. because if record is dynamic and "no rules" => warnings display (but INFO level without blocking) and if we compute a "fake" rules that doesn't exactly match with config rules the zone diff create a drift (not fixable / loop)
in summary :

only my first version (where rules definition impact RRset and can be reverted for retrieve exact definition) works with this logic but we have seen this doesn't allow global fallback or multi geos definition => bad idea
fake rules to workaround validator => doesn't work because imply matching exactly rrset & config else create a drift

So, I have no idea to have clean result without deeper change.
In my opinion, validate "dynamic" record structure should be a provider-related thing (especially because this only display a message and can be different for each provider) or maybe to be in global logic imagine a - lenient_rules: true in octodns record metadata that permit to avoid dynamic rules validation (and inject automatically this parameter in provider in this usecase)
Keep me in touch if you have a better idea

I add comment in your PR to mention error that can be easily fix,

Commented there. There is a problem with my code, but not sure the proposed fix would work, e.g. if the pool rrsets happened to be in the rrsets before the ones with the Region.

Finally as you "expected", the "fake" rules isn't possible to workaround the Record Validator (from RRset reverse).. because if record is dynamic and "no rules" => warnings display (but INFO level without blocking) and if we compute a "fake" rules that doesn't exactly match with config rules the zone diff create a drift (not fixable / loop)

This should be fine. I believe the populate phase of things always runs in lenient=True mode for this reason, so that it won't blow up if things aren't best practices.

only my first version (where rules definition impact RRset and can be reverted for retrieve exact definition) works with this logic but we have seen this doesn't allow global fallback or multi geos definition => bad idea

As mentioned earlier, that version could reproduce some rules, but not rules that would be meaningful in the real world since they could only have 1 geo defined per pool. People would never be able to use Route53 latency along side any other dynamic providers as the behavior in the other providers would be flawed.
I'd prefer the path where Route53Provider ignores the rules and gets some warnings during populate to preventing its use with other providers since the whole purpose/origin of octoDNS was to make multiple providers easier/doable.

fake rules to workaround validator => doesn't work because imply matching exactly rrset & config else create a drift

The _include_change stuff in my PR addresses the drift, where it removes rules from the desired data and then compares it to the ruleless existing. If we were to stuff in fake rules to get rid of the warnings that would just need to be udpated to remove the rules from the existing data as well.

Commented there. There is a problem with my code, but not sure the proposed fix would work, e.g. if the pool rrsets happened to be in the rrsets before the ones with the Region.

if the pool rrsets happened before the 'Region' it's not an issue, because the pool rrsets is a standard rrsets, only the principal record (that should point to pool rrset) have Region and can be define without any precedence or dependencies.
But maybe I don't see exactly what you mean and if you can give me a zone example where an error case happened,
I can try to find a workaround for both.

The _include_change stuff in my PR addresses the drift, where it removes rules from the desired data and then compares it to the ruleless existing. If we were to stuff in fake rules to get rid of the warnings that would just need to be udpated to remove the rules from the existing data as well.

Exactly, and like you said this impact warning log (without fail regarding lenient mode) look like :
2023-04-21T20:21:45  [xxx] WARNING Record Invalid latency.xtest.com.
  - missing rules
  - unused pools: "xx-west-1", "xx-east-1"

In my option, it's anxiety-provoking because it suggests a problem and for a critical service like DNS, this isn't a good idea.
Let me know, your final position about it, and if you consider warning acceptable I can rework my commit (readme, tests, coverage) to have a final version with your proposed behavior.

In my option, it's anxiety-provoking because it suggests a problem and for a critical service like DNS, this isn't a good idea.

I don't disagree, but that's preferable to forcing a broken set of rules that wouldn't work in any other provider.
I'm fairly sure that it'll be possible to stuff in some fake rules and then ignore the resulting change if only the rules changed, but I haven't gotten a chance to dig into it in depth yet and it'll be a bit longer until I get there. Probably best to hold off on any further work until I get a chance to do more research to avoid any potential thrashing.


DEV: Change variable names to prevent errors

This PR changes the variable names of link and prettyPubDate to prevent errors in the current version of Ghost.
When adding a custom option for result_template and using {{link}} an error is given that you cannot use {{#link}} without an href attribute.
{{prettyPubDate}} has been changed to pubDate elsewhere, but was not changed in the default result_template.

i coppied your changes locally and postLink not working :(
postLink in not replaced with an actual value


Provide a sensible fallback when no previous sorting values were defined

This PR provides a sensible fallback for those cases where you add sortable behaviour on existing resources and the values of the sortable column is null.
With the previous code, there would be no update as you would again set the value of the sorting column to null. With the new code, the value of the sorting column will be the value of $increment.

Hi! I implemented my own version of the same thing and released it in version 2.1.0. Thank you for the PR!

Hi! I implemented my own version of the same thing and released it in version 2.1.0. Thank you for the PR!

@Tarpsvo no problem!

@Tarpsvo no problem!


"Compile and run the Razor Pages project" fails to deploy to public endpoint

This is autogenerated
Describe the bug
Command Name
az webapp up
Errors:
'NoneType' object has no attribute 'upper'
Traceback (most recent call last):
python3.6/site-packages/knack/cli.py, ln 206, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 603, in execute
    raise ex
cli/core/commands/__init__.py, ln 661, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
cli/core/commands/__init__.py, ln 652, in _run_job
    cmd_copy.exception_handler(ex)
...
cli/command_modules/appservice/custom.py, ln 2993, in webapp_up
    create_app_service_plan(cmd, rg_name, plan, _is_linux, False, sku, 1 if _is_linux else None, location)
cli/command_modules/appservice/custom.py, ln 1390, in create_app_service_plan
    sku = _normalize_sku(sku)
cli/command_modules/appservice/utils.py, ln 20, in _normalize_sku
    sku = sku.upper()
AttributeError: 'NoneType' object has no attribute 'upper'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Complete units 1-3 in this exercise
az webapp up

Expected Behavior
Environment Summary
Linux-4.15.0-1063-azure-x86_64-with-debian-stretch-sid
Python 3.6.5
Shell: bash

azure-cli 2.0.76

Additional Context

Duplicate of #11100

Please upgrade to 2.0.77 Thanks!


ISSUE-889 Retain Window configuration when running test topology with…

… WindowedRule

also loosen type checking with timestamp extractor

it didn't work with test topology with short value of field (not strictly long)

This closes #889

@arunmahadevan
Addressed review comment. You can refer the last commit to narrow the diff. I'll squash the commits once you approve the patch.

@HeartSaVioR , tested with storm 1.1.1. Processing and event time windows works.
However I had some extra field in the JSON and it throws an exception in the log,
Caused by: java.lang.IllegalArgumentException: Field list doesn't match to output schema.
	at com.hortonworks.streamline.common.SchemaValueConverter.convertMap(SchemaValueConverter.java:37)

It will be good to put the missing or extra fields in the exception so that users can quickly identify and fix it.
In the UI the exception is not propagated. Will raise a separate issue for this.

I think this PR can be merged after 1 is addressed.
Anther issue:
Sometimes the storm process keeps on running and the test run never completes until one manually kills the storm local mode process. As discussed we can,

Provide a kill API to forcefully stop the test run
Show the events in the UI as it becomes available. I think the API already returns the events, UI needs to poll and show the results.

That way even if the process gets stuck, the user can stop the test run after they have seen the expected results and even if the process does not get stuck it will be useful in general. Will raise issues for the above two.

@arunmahadevan
Thanks for the testing. I addressed 1.
Please note that each value is converted and conversion gets stopped at first occurrence of error case, so the values are having different fields unfortunately, only first error case would be reported.

@arunmahadevan Filed an issue https://github.com/hortonworks/streamline/issues/894 for the second part of your previous comment.

+1


Add MethodRunExpander for run_specs_extra.conf

This doesn't really type-check because not all adapters work with all run spec functions. Currently this is implemented by passing a method argument to the run spec function, which seems fine.


Why don't you allow to use 'do_predict'?

The predict operation was allowd.
Reference here: https://github.com/kyzhouhzau/BERT-NER/blob/d190281df54263b84cedde570a5b7a90019538b7/BERT_NER.py#L659

Ok,  so the prediciton mode is working? I wondered because if I start it from the script with
    --do_train=False   \     --do_predict=True	\     --do_eval=False   \
this line causes an error.

--do_train=False \ --do_predict=True \ --do_eval=True \
```
will work

hi but if want to test performance on new data with no labels, is it possible?
going through your code i made some changes to exclude label_ids from being used in prediction but haven't succeeded yet.
Any help would be appreciated!

@anupamsingh610 I wanted to do the same thing as you. After making changes to the exception it raises in the main function, and making a dummy list of label_ids labels right before the label_ids list is passed to InputFeatures in the convert_single_example function, the script will run with only do_eval as False and do_predict as True, and will print out predicted labels for each token in an output file. It took me a little tweaking to get to work rght, but that's the gist of it. Providing a dummy list will not change the output of the trained model if you are not training.
To answer your PS, the label_ids are passed as a feature because that is the way the class is implemented in the original google script. By passing the label_ids in the InputFeatures class, the model is able to access these during training.

@saverymax Thanks for the reply! I figured the same and provided [CLS] as the dummy label_ids. Also I removed the assertion of having at least one of do_train and do_eval flag to be set to True and now it runs fine with just do_predict set to True.
And regarding PS I still think its not intuitive :)


Log Cumulative Returns does not do log() calculation?

In function plot_cumulative_returns_by_quantile(), the data( cum_ret) used to plot "Cumulative Return by Quantile Figure"  has not been processed by a log fucntion?

Please see #194


Align Replace Menu

This aligns the ReplaceMenu with the one of the Camunda Modeler. Furthermore, it adds missing replace options to ensure forward-and-backward type switching, e.g. in modeling events or tasks.

Additionally, it re-structures the overall test suite for the ReplaceMenuProvider and adds test coverage for several replace scenarios (e.g. boundary events, event-sub-processes, participants).
Closes #115

@pinussilvestrus It seems like the multi instance stuff is missing from undefined tasks. Here's a screenshot from Zeebe:

Here's the same from Camunda modeler:

That's intended, since they are only support for ReceiveTask, MessageTask and SubProcess, cf. https://github.com/zeebe-io/zeebe-modeler/issues/82

Not directly related to the PR itself but we can add another "=" here based on this comment of Philipp

Since we have this 2-lines-between-tests rule, we can add an extra space here and here, also can remove the additional space here.

Done, thanks!

🎸 🎸


Pass dateOptions to the month name format call

Hello,
I noticed the month name wasn't localized when displayed.
After further inspection, I noticed the dateOptions weren't passed through to this format call, so here's a quickfix to solve this.
Have a good day !

great!
thank you for PR 👊

Will be released next alpha version next week


Ensure SBIN Merger is handled correctly

SBI has published a list of new IFSC codes for their merged branches: https://www.onlinesbi.com/nri/remittances/sbinri_merged_bran_swfcode.html
Need to verify this, and maybe provide an easy upgrade path to users?

This is done, but SBI is claiming 1400 bank branches.

We already took care of this list: https://www.onlinesbi.com/nri/remittances/sbinri_merged_bran_swfcode.html
But SBI created more lists at https://bank.sbi/portal/web/services/merger-of-associate-banks that we need to take care of.


Bug w byłym upstream

https://github.com/pradoslaw/coyote/issues/769#issue-2401333808

@emabrey in the light of dev changes, can this be marked solved & closed?


Change forwarding format (rfc5424) + add instance metadata

Commit messages best describe it along with the README update. Note that this significantly affects/breaks the format messages are transmitted. The change is intentional and brings it inline with existing rfc5424 standards. This does not try to influence the message format that programs log their messages in.
Example messages received from a test deployment...
<14>1 2017-01-25T13:25:03.18377Z <IP_ADDRESS> etcd - - [instance@47450 director="test-env" deployment="cf" group="diego_database" az="us-west1-a" id="83bd66e5-3fdf-44b7-bdd6-508deae7c786"] [INFO] the leader is [https://diego-database-0.etcd.service.cf.internal:4001]
<14>1 2017-01-25T13:25:03.184491Z <IP_ADDRESS> bbs - - [instance@47450 director="test-env" deployment="cf" group="diego_database" az="us-west1-a" id="83bd66e5-3fdf-44b7-bdd6-508deae7c786"] {"timestamp":"1485350702.539694548","source":"bbs","message":"bbs.request.start-actual-lrp.starting","log_level":1,"data":{"actual_lrp_instance_key":{"instance_guid":"271f71c7-4119-4490-619f-4f44694717c0","cell_id":"diego_cell-2-41f21178-d619-4976-901c-325bc2d0d11d"},"actual_lrp_key":{"process_guid":"1545ce89-01e6-4b8f-9cb1-5654a3ecae10-137e7eb4-12de-457d-8e3e-1258e5a74687","index":5,"domain":"cf-apps"},"method":"POST","net_info":{"address":"<IP_ADDRESS>","ports":[{"container_port":8080,"host_port":61532},{"container_port":2222,"host_port":61533}]},"request":"/v1/actual_lrps/start","session":"418.1"}}

Tested by...

deploying a test with forwarder + storer (there's a related commit to storer to make it log the raw messages instead of using a different format... makes it easier to review and verify the transport format)
deployed storer, and then forwarder as an addon to a small CF deployment
testing messages received by the storer against several rfc5424-compatible parsers, including logstash with an included example

Further thoughts...

the syslog.director setting could be made optional if director name were accessible by the template spec
chose to make syslog.director/director SD-ELEMENT mandatory, rather than potentially adding it further down the road and causing other breakages

This PR is a follow up to this Google doc where there was some discussion about it.
This fixes #3 and is related to #7.

/cc @dpb587, @mrdavidlaing

do we hace access to some dns domain thing that could be used in place if director?
Sent from my iPhone

On Jan 25, 2017, at 8:09 AM, Danny Berger<EMAIL_ADDRESS>wrote:
Commit messages best describe it along with the README update. Note that this significantly affects/breaks the format messages are transmitted. The change is intentional and brings it inline with existing rfc5424 standards. This does not try to influence the message format that programs log their messages in.
Example messages received from a test deployment...
<14>1 2017-01-25T13:25:03.18377Z <IP_ADDRESS> etcd - - [instance@47450 director="test-env" deployment="cf" group="diego_database" az="us-west1-a" id="83bd66e5-3fdf-44b7-bdd6-508deae7c786"] [INFO] the leader is [https://diego-database-0.etcd.service.cf.internal:4001]
<14>1 2017-01-25T13:25:03.184491Z <IP_ADDRESS> bbs - - [instance@47450 director="test-env" deployment="cf" group="diego_database" az="us-west1-a" id="83bd66e5-3fdf-44b7-bdd6-508deae7c786"] {"timestamp":"1485350702.539694548","source":"bbs","message":"bbs.request.start-actual-lrp.starting","log_level":1,"data":{"actual_lrp_instance_key":{"instance_guid":"271f71c7-4119-4490-619f-4f44694717c0","cell_id":"diego_cell-2-41f21178-d619-4976-901c-325bc2d0d11d"},"actual_lrp_key":{"process_guid":"1545ce89-01e6-4b8f-9cb1-5654a3ecae10-137e7eb4-12de-457d-8e3e-1258e5a74687","index":5,"domain":"cf-apps"},"method":"POST","net_info":{"address":"<IP_ADDRESS>","ports":[{"container_port":8080,"host_port":61532},{"container_port":2222,"host_port":61533}]},"request":"/v1/actual_lrps/start","session":"418.1"}}
Tested by...
deploying a test with forwarder + storer (there's a related commit to storer to make it log the raw messages instead of using a different format... makes it easier to review and verify the transport format)
deployed storer, and then forwarder as an addon to a small CF deployment
testing messages received by the storer against several rfc5424-compatible parsers, including logstash with an included example
Further thoughts...
the syslog.director setting could be made optional if director name were accessible by the template spec
chose to make syslog.director/director SD-ELEMENT mandatory, rather than potentially adding it further down the road and causing other breakages
This PR is a follow up to this Google doc where there was some discussion about it.
This fixes #3 and is related to #7.
You can view, comment on, or merge this pull request online at:
https://github.com/cloudfoundry/syslog-release/pull/13
Commit Summary
Change syslog_storer to write the raw messages
Change forwarding format + add instance metadata
File Changes
M README.md (16)
M jobs/syslog_forwarder/spec (3)
M jobs/syslog_forwarder/templates/rsyslog.conf.erb (24)
M jobs/syslog_storer/templates/rsyslog.conf.erb (7)
A scripts/logstash-filters.conf (19)
Patch Links:
https://github.com/cloudfoundry/syslog-release/pull/13.patch
https://github.com/cloudfoundry/syslog-release/pull/13.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Not sure. It'd be nice if director name was accessible from spec, but didn't want to wait on that happening or not.
Are you thinking spec.dns_domain_name[4:] sort of thing? Few people change the TLD though, so it doesn't like we should rely on that. Can't think of anything else clever.
Or we could default the property to bosh just so people aren't required to configure it to use the release. Thought that might get a little confusing if we're calling it the director field though.
Other ideas?

From the point of view of someone consuming the recieving the aggregated logs (e.g., a central security team) anything we can do to encourage a useful value for director being set is advantageous.
For example, if I had several CF environments running (each in a different region with their own BOSH director) all sending their logs to a central security management system; I really need to know which cf environment a specific log comes from.
I think that until we can automatically populate the field; we should default to empty string ( or maybe make it required? ) rather than a generic word; since that is a clearer indication that it hasn't been set ( and should be )

@cppforlife - Who should we work with to get this change merged?


Block hover colour attribute

[x] Add possibility to change hover block colour with unity attributes
In BaseBlock class, when adding hover colour variable instead of changing colour unity make object transparent on exit.

Redundant.


feat(AppHeaderCatalogDropdown): added AppHeaderCatalogDropdown component

Overview

PR Checklist

[ ] Related to designs:
[x] Related to JIRA ticket: DISC-545
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.1178dd.0@codecademy/gamut-labs@31.3.4-alpha.1178dd.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://624dc82f6d782b00c28bfe80--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.09db70.0@codecademy/gamut-labs@31.3.4-alpha.09db70.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://624dd40470e0820e1e06010f--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.8808d8.0@codecademy/gamut-labs@31.3.4-alpha.8808d8.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://624dda13d016f50094c8aa94--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.b112ba.0@codecademy/gamut-labs@31.3.4-alpha.b112ba.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://624e04212cc9c60abb35c83f--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.4657b8.0@codecademy/gamut-labs@31.3.4-alpha.4657b8.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://624e142677f85211d8bae7b6--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://624e3f92b62e7a00b3a19b64--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.dc85ae.0@codecademy/gamut-labs@31.3.4-alpha.dc85ae.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://624e43ba19cd0802278adfc2--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.4a75bf.0@codecademy/gamut-labs@31.3.4-alpha.4a75bf.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://624eefb1c27b8f00614986c2--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.5e62ff.0@codecademy/gamut-labs@31.3.4-alpha.5e62ff.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://624f4bb93afaed08b425d937--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.278839.0@codecademy/gamut-labs@31.3.4-alpha.278839.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://624f5fb2de434805276e1811--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.e63ce0.0@codecademy/gamut-labs@31.3.4-alpha.e63ce0.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.b5d1a1.0@codecademy/gamut-labs@31.3.4-alpha.b5d1a1.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6254a3b35360a2351f2113ab--gamut-preview.netlify.appDeploy Logs


Simplify NAN boxing macro setting

@bnoordhuis Should we have a 32bit CI as a canary?

I'll put it on the mental backlog ;-)


Submoduled cf-operator

Description
Pinning cf-operator on a specific commit that is known to work with kubecf.
Test plan
Verify that using the pinned cf-operator works with kubecf.

Instead of submoduling or referencing a pre-built binary, we will reference a published chart (which indirectly references a binary).


Error while setting up environment fatal: repository 'https://github.com/zilch/pyigl/' not found

Hi @Daisy-1227 ,
While trying to set up the environment, the command pip install git+https://github.com/zilch/pyigl outputs an error: fatal: repository 'https://github.com/zilch/pyigl/' not found. Indeed, this repository doesn't exist.
Could you point me to the correct one which should be used?

Hi @anticdimi,
After checking, I found that there was an error in this URL. It should actually be 'https://github.com/zzilch/pyigl' instead of 'https://github.com/zilch/pyigl'. Thank you for the reminder, and I will update the README.

Thanks for the prompt reaction!
I will close this issue :smile:

Actually, while I'm here, I would like to ask one more question.
Do you plan to release the code to train the RDIF model? Or is it already here on the repo and I missed it?
I can't seem to find any instructions in README..

@anticdimi
The training of the RDIF model was done by Zeyu Huang, who has graduated.
If you need further details, you can refer to the training details of DIF. Also, I will try to organize and release this code when I have some free time  (I am currently busy with another project 😂).

Oh okay. If you have time at some point, it'd be great.
But given what you write in supplementary materials and main paper, the training should be exactly as the one of DIF-Net; so theoretically, I could just re-use their training loop?
Feel free to close this issue, I will follow the repository for updates regarding this.


GATT Server API for decriptors is incompatable with BLE spec (IDFGH-14165)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Hello,
According to BLE spec (e.g. Bluetooth® Core Specification Version 5.4)
GATT services characteristics and descriptors have have very clear tree structure as  shown on page 37:

Services have characteristics and characteristics have descriptors.
The following ESP32 calls violate this structure:

esp_err_t esp_ble_gatts_add_char_descr(uint16_t service_handle, esp_bt_uuid_t *descr_uuid, esp_gatt_perm_t perm, esp_attr_value_t *char_descr_val, esp_attr_control_t *control)
Accepts service handle while have to accept characteristic handle. Even function names says that descriptor belongs to characteristic, not service

struct gatts_add_char_descr_evt_param have field service_handle instead of characteristic handle

Suche vilation prohibits having same decriptor id within different characteristics.
E.g. having CCCD for each characteristics within same service

After spending day in looking for possible quick fix I found that both characteristics and descriptors are stored in "service database" and treated equally as service attributes.
This is the main reason there can not be multiple descriptors with same UUID within the same service even though they related to different characteristics.
Will try to fix it locally fro my self but hope this misleading architecture will be fixed officially in near future.

Thank you for reporting this issue.
Currently, Bluedroid supports two methods for creating GATT server databases:

Native Method
This is the approach you are currently using, which is consistent with the example found at esp-idf/examples/bluetooth/bluedroid/ble/gatt_server.

Recommended Method
This method involves defining a GATT server using a table-like data structure, allowing you to clearly add descriptors. It supports multiple descriptors per characteristic and multiple characteristics per service.
You can refer to the example at:
esp-idf/examples/bluetooth/bluedroid/ble/gatt_server_service_table

Addressing Your Concern:
You pointed out that the native method has issues with the following aspects:

The function esp_ble_gatts_add_char_descr(uint16_t service_handle, ...) accepts a service_handle but should accept a characteristic_handle.
The struct gatts_add_char_descr_evt_param contains a service_handle instead of a characteristic_handle.

Let me clarify why using the service_handle is intentional and not problematic:
In the database, services, characteristics, and descriptors are all treated as attributes, and Bluedroid organizes these attributes sequentially during database creation. Here’s how it works:

Create Service:
The esp_ble_gatts_create_service function assigns an attribute index for the service.

Add Characteristic:
The esp_ble_gatts_add_char function adds the characteristic, assigning an attribute index sequentially after the service.

Add Descriptors:
The esp_ble_gatts_add_char_descr function adds descriptors, assigning their attribute indices sequentially after the characteristics.

The service_handle is used to locate the service to which the descriptor belongs. The exact placement of the descriptor (i.e., which characteristic it is associated with) is determined by the sequence in which attributes are added.
You can verify the attribute hierarchy and sequence using the esp_ble_gatts_show_local_database API.

If you require multiple descriptors or characteristics within the same service, the database creation process will handle this seamlessly, as each attribute is assigned a unique index (or handle) sequentially.
If you still have concerns or require further clarification, feel free to reach out. We're here to help!

Thansk for reply
I'm aware that if descriptors are being added by esp_ble_gatts_add_char_descr immediately after adding characteristic by esp_ble_gatts_add_char then it sort of added to the last characteristic. Even though I see it as not the best code architecture I'm fine with it.
The problem I'm addressing is the follows.
Let's say I want to have this serivce structure:

Service 0x180f

Characteristic 0x2a19

Descriptor 0x2902

Service 0x181c

Characteristic 0x2000

Descriptor 0x2902

Characteristic 0x2001

Descriptor 0x2902

Characteristic 0x2002

Descriptor 0x2902

Characteristic 0x2003

Descriptor 0x2902

Service 0x180a

Characteristic 0x2a00

Descriptor 0x2902

To create it I call esp_ble_gatts_create_service, esp_ble_gatts_start_service, esp_ble_gatts_add_char and esp_ble_gatts_add_char_descr and get the service three exactly as I described above.
Now I wait for ESP_GATTS_ADD_CHAR_EVT and ESP_GATTS_ADD_CHAR_DESCR_EVT to save attribute handles for further handling of read/write events.
Let's say I receive ESP_GATTS_ADD_CHAR_DESCR_EVT:
param->add_char_descr.descr_uuid.uuid.uuid16: 0x2902
param->add_char_descr.service_handle: 0x28
param->add_char_descr.attr_handle: 0x2b

How do I distiguish to which of my characteristics (0x2000, 0x2001, 0x2002 or 0x2002) this descriptor was added?
Later, when ESP_GATTS_READ_EVT/ESP_GATTS_READ_EVT arrives I have only attribute handle and need to find which one of all attributes it is by search through saved handles, but I can't because of the previous problem.
If you find that "sequential adding" concept fine and don't want to chage esp_ble_gatts_add_char_descr  signature could you at least add parent characteristic uuid or handle to gatts_add_char_descr_evt_param so that added descritpr can be bound to characteristic as it should?

If you're unsure how to manage this sequence, I recommend using a table-based approach to create your database.

@leonid-galperin Does the table-based approach address your issue?


Bicep parameter file experimental feature

This document doesn't describe that you have to enable an experimental to use it.

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

ID: cdf73225-d2e6-b23e-b355-fbb9d3fcdca3
Version Independent ID: fa832878-9821-f222-5f15-ad8646737a04
Content: Create parameters files for Bicep deployment - Azure Resource Manager
Content Source: articles/azure-resource-manager/bicep/parameter-files.md
Service: azure-resource-manager
Sub-service: bicep
GitHub Login: @mumian
Microsoft Alias: jgao

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

@mumian To review

bicepparam is no longer a experimental feature.  The information is documented in https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/parameter-files?tabs=Bicep
#please-close


it does'nt works

it dont work

Hello @OpenSrcerer!
We are deeply sorry about your issues.
If you experience any future issues, please consider contacting us at<EMAIL_ADDRESS>Even though we'd rather not hear from you again.
Have a splendid afternoon.

It's borked


Use winapi

Now that winapi 0.3 is here we can depend on winapi without waiting eons for it to compile.

Thanks for the PR! This was originally done for compile times and the current compile time (on one machine at least) is 1.7s while this PR takes it to 5.1s. For now as these are functional I'll probably leave them as-is, but if they're modified again seems like a great PR to merge!

Is the measured cost of the compilation time counting the time to compile winapi or is it just the time to compile cc-rs? I suspect in practice there are not many real-life projects that build on Windows and require cc-rs and don't already require winapi, so I think the cost of downloading/building winapi on Windows shouldn't be a big enough concern to re-implement parts of winapi. That's why I chainged ring in a similar way recently.

I'm going to close this since it's quite old at this point, but it can of course always be reconsidered later.


#498 Enhancement Finished

Created Search Service which is instantiated by the controller instance.

Closing this PR. Will create fresh PR with changes


Not working/Partially working textfield types

The following textfield types are not rendered correctly or are partially working (i.e. missing right button feature):

Date
Time
Datetime-local
Month
Week
Color
File

Demo and comparison with browser default

These types of text fields are not fully supported and may have missing features or undefined designs. You may find that some things need to be manually added, like icon buttons or a width.


BGE Wizard - Defaults - Date Picker not showing for Donation Date

Critical Changes
Changes
Using the old getLightningDataType function from the controller instead of the ones in the utils class.
Issues Closed
New Metadata
Deleted Metadata

**lurch:attach W-031192

Tracking W-031192