Unable to build

Hi
I get several errors building.
error: aborting due to 43 previous errors

Some errors have detailed explanations: E0034, E0308.
For more information about an error, try `rustc --explain E0034`.
error: could not compile `bitvec`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed

VSC also shows me
could not compile 'ff' in Cargo.toml
What  am I doing wrong or is there a known issue right now?

Hi @FudiHub! Can you provide us a fully detailed log?
What's your OS and what command are you using to build it?
I just ran cargo build --release on a clean copy of the repository and it compiled fine.

Hi @notdanilo

What's your OS and what command are you using to build it?

I am on MacOS 11.2.1. I built with cargo build or cargo build --release
This is the complete output:
full_log.txt
Thanks for your help

Hi @FudiHub, I was able to replicate the issue.
I am already working on it. And I will also add macOS, Ubuntu, and Windows environments in our CI checks so it will never happen again.
Thanks for reporting it!

Hi @notdanilo
thats great news. Thanks. Maybe you are so kind to look into this issue as well? https://github.com/nash-io/openlimits-python/issues/6
I have similar issues with nash-io/openlimits-python
Thanks!!

I just tracked it down to https://github.com/bitvecto-rs/bitvec/issues/105, which is really bad because we have 3 dependency layers above bitvec (elliptic-cursve -> ecdsa -> k256).
funty v1.2.0
└── bitvec v0.18.4
    ├── elliptic-curve v0.6.6
    │   ├── ecdsa v0.8.5
    │   │   ├── k256 v0.5.10
    │   │   │   ├── nash-mpc v1.2.0
    │   │   │   │   └── nash-protocol v0.1.24
    │   │   │   │       ├── nash-native-client v0.1.18
    │   │   │   │       │   └── openlimits v0.1.9-alpha.0 (/home/notdanilo/dev/nash-io/openlimits)

Hi, I have completely same error, when I try to compile openlimits-python version. Commented in the relevant issue for openlimits-python: https://github.com/nash-io/openlimits-python/issues/6#issuecomment-782080594

@Bi0max hi! The fix for the funty issue is being delivered soon. Regarding the missing gmp.lib file, I just faced it myself when setting up the automated checks for Windows. Please check these links:
https://github.com/ZenGo-X/kms-secp256k1/issues/25
https://github.com/vhnatyk/gmp-release
I will add proper documentation describing this pre-req.

Hi, sorry, I missed the previous comment ... created https://github.com/nash-io/openlimits/pull/168 to avoid issue with funty.

@Bi0max hi! The fix for the funty issue is being delivered soon. Regarding the missing gmp.lib file, I just faced it myself when setting up the automated checks for Windows. Please check these links:
ZenGo-X/kms-secp256k1#25
https://github.com/vhnatyk/gmp-release
I will add proper documentation describing this pre-req.

@notdanilo, thank you for the hint. I managed to install 32-bit version of GMP from the link you provided.
But now I get another compilation error:
 maturin build --release
≡ƒöù Found pyo3 bindings
≡ƒæ╜ 3.9 is installed as 64-bit, while the target is 32-bit. Skipping.
≡ƒæ╜ 3.8 is installed as 64-bit, while the target is 32-bit. Skipping.
≡ƒæ╜ 3.8 is installed as 64-bit, while the target is 32-bit. Skipping.
≡ƒæ╜ 3.7 is installed as 64-bit, while the target is 32-bit. Skipping.
≡ƒæ╜ 3.7 is installed as 64-bit, while the target is 32-bit. Skipping.
≡ƒæ╜ 3.7 is installed as 64-bit, while the target is 32-bit. Skipping.
≡ƒæ╜ 3.7 is installed as 64-bit, while the target is 32-bit. Skipping.
≡ƒæ╜ 3.7 is installed as 64-bit, while the target is 32-bit. Skipping.
≡ƒÉì Found CPython 3.8 at C:\Users\Maksim\Miniconda3\envs\arb32\python
   Compiling pyo3 v0.12.4
   Compiling proc-macro2 v1.0.24
   Compiling typenum v1.12.0
   Compiling winapi v0.3.9
   Compiling libc v0.2.86
   Compiling memchr v2.3.4
   Compiling tokio v1.2.0
   Compiling crossbeam-utils v0.8.2
   Compiling memoffset v0.6.1
   Compiling miniz_oxide v0.4.3
   Compiling indexmap v1.6.1
   Compiling num-integer v0.1.44
   Compiling log v0.4.14
   Compiling getrandom v0.1.16
   Compiling proc-macro-hack v0.5.19
   Compiling radium v0.4.1
   Compiling ryu v1.0.5
   Compiling num-bigint v0.2.6
   Compiling getrandom v0.2.2
   Compiling proc-macro-nested v0.1.7
   Compiling unicode-normalization v0.1.17
   Compiling http-body v0.4.0
   Compiling kernel32-sys v0.2.2
   Compiling ws2_32-sys v0.2.1
   Compiling httparse v1.3.5
   Compiling rayon v1.5.0
   Compiling pkcs8 v0.3.3
   Compiling doc-comment v0.3.3
   Compiling encoding_rs v0.8.28
   Compiling num-traits v0.2.14
   Compiling num_cpus v1.13.0
   Compiling aho-corasick v0.7.15
   Compiling combine v3.8.1
   Compiling rand_core v0.5.1
   Compiling want v0.3.0
   Compiling quote v1.0.9
   Compiling bitvec v0.18.4
   Compiling generic-array v0.14.4
   Compiling generic-array v0.12.3
   Compiling rand_core v0.6.2
   Compiling rand_chacha v0.2.2
   Compiling idna v0.2.2
   Compiling regex v1.4.3
   Compiling syn v1.0.60
   Compiling paste-impl v0.1.18
   Compiling digest v0.8.1
   Compiling block-buffer v0.7.3
   Compiling backtrace v0.3.56
   Compiling digest v0.9.0
   Compiling block-buffer v0.9.0
   Compiling crypto-mac v0.9.1
   Compiling crypto-mac v0.10.0
   Compiling crypto-mac v0.8.0
   Compiling rand_chacha v0.3.0
   Compiling rand v0.7.3
   Compiling crossbeam-epoch v0.9.2
   Compiling crossbeam-channel v0.5.0
   Compiling url v2.2.1
   Compiling sha2 v0.8.2
   Compiling Inflector v0.11.4
   Compiling paste v0.1.18
   Compiling ff v0.8.0
   Compiling signature v1.2.2
   Compiling sha2 v0.9.3
   Compiling sha-1 v0.9.4
   Compiling ripemd160 v0.9.1
   Compiling sha3 v0.9.1
   Compiling hmac v0.9.0
   Compiling hmac v0.10.1
   Compiling hmac v0.8.1
   Compiling rand v0.8.3
   Compiling crossbeam-deque v0.8.0
   Compiling bs58 v0.3.1
   Compiling socket2 v0.3.19
   Compiling parking_lot_core v0.8.3
   Compiling ntapi v0.3.6
   Compiling schannel v0.1.19
   Compiling time v0.1.43
   Compiling net2 v0.2.37
   Compiling winreg v0.7.0
   Compiling group v0.8.0
   Compiling rayon-core v1.9.0
   Compiling synstructure v0.12.4
   Compiling pyo3-derive-backend v0.12.4
   Compiling miow v0.3.6
   Compiling parking_lot v0.11.1
   Compiling native-tls v0.2.7
   Compiling elliptic-curve v0.6.6
   Compiling elliptic-curve v0.8.5
   Compiling miow v0.2.2
   Compiling mio v0.7.9
   Compiling tungstenite v0.12.0
   Compiling ecdsa v0.8.5
   Compiling ecdsa v0.10.2
   Compiling mio v0.6.23
   Compiling p256 v0.5.2
   Compiling k256 v0.5.10
   Compiling k256 v0.7.2
   Compiling mio-named-pipes v0.1.7
   Compiling serde_derive v1.0.123
   Compiling tokio-macros v1.1.0
   Compiling futures-macro v0.3.13
   Compiling tracing-attributes v0.1.13
   Compiling pin-project-internal v1.0.5
   Compiling failure_derive v0.1.8
   Compiling thiserror-impl v1.0.24
   Compiling ghost v0.1.2
   Compiling indoc-impl v0.3.6
   Compiling ctor v0.1.19
   Compiling async-trait v0.1.42
   Compiling async-recursion v0.3.2
   Compiling inventory-impl v0.1.10
   Compiling derive_more v0.99.11
   Compiling tokio-macros v0.2.6
   Compiling pyo3cls v0.12.4
   Compiling futures-util v0.3.13
   Compiling failure v0.1.8
   Compiling indoc v0.3.6
   Compiling tracing v0.1.25
   Compiling inventory v0.1.10
   Compiling thiserror v1.0.24
   Compiling pin-project v1.0.5
   Compiling graphql-parser v0.2.3
   Compiling tokio v0.2.25
   Compiling tracing-futures v0.2.5
   Compiling serde v1.0.123
   Compiling futures-executor v0.3.13
   Compiling futures v0.3.13
   Compiling tokio-util v0.6.3
   Compiling tokio-native-tls v0.3.0
   Compiling tokio-stream v0.1.3
   Compiling tokio-tungstenite v0.13.0
   Compiling h2 v0.3.0
   Compiling serde_json v1.0.62
   Compiling chrono v0.4.19
   Compiling serde_urlencoded v0.7.0
   Compiling bigdecimal v0.1.2
   Compiling serde_urlencoded v0.6.1
   Compiling rust_decimal v1.10.3
   Compiling graphql-introspection-query v0.1.0
   Compiling rust-gmp-serde v0.5.0
   Compiling graphql_client_codegen v0.9.0
   Compiling rust-bigint v1.1.0
   Compiling paillier-common v0.1.1
   Compiling nash-mpc v1.2.0
   Compiling hyper v0.14.4
   Compiling graphql_query_derive v0.9.0
   Compiling graphql_client v0.9.0
   Compiling nash-protocol v0.1.26
   Compiling hyper-tls v0.5.0
   Compiling reqwest v0.11.1
   Compiling nash-native-client v0.1.21
   Compiling openlimits v0.1.10
   Compiling openlimits-python v0.1.0 (D:\projects\openlimits-python)
warning: unused import: `tokio::sync::mpsc::UnboundedSender`
 --> src\lib.rs:3:5
  |
3 | use tokio::sync::mpsc::UnboundedSender;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

warning: unused import: `tokio::sync::Mutex`
 --> src\lib.rs:4:5
  |
4 | use tokio::sync::Mutex;
  |     ^^^^^^^^^^^^^^^^^^

warning: unused import: `std::sync::Arc`
 --> src\lib.rs:5:5
  |
5 | use std::sync::Arc;
  |     ^^^^^^^^^^^^^^

warning: unused imports: `Either`, `select`
  --> src\lib.rs:38:28
   |
38 | use futures_util::future::{select, Either, Future};
   |                            ^^^^^^  ^^^^^^

error[E0308]: mismatched types
   --> src\lib.rs:129:54
    |
129 |         let ws_client: OpenLimitsWs<AnyWsExchange> = runtime.block_on(ws_client_future);
    |                        ---------------------------   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `OpenLimitsWs`, found enum `Result`
    |                        |
    |                        expected due to this
    |
    = note: expected struct `OpenLimitsWs<AnyWsExchange>`
                 found enum `Result<OpenLimitsWs<_>, OpenLimitsError>`

error[E0308]: mismatched types
   --> src\lib.rs:133:13
    |
133 |             client,
    |             ^^^^^^ expected enum `AnyExchange`, found enum `Result`
    |
    = note: expected enum `AnyExchange`
               found enum `Result<_, OpenLimitsError>`

error[E0063]: missing field `order_status` in initializer of `GetOrderHistoryRequest`
   --> src\lib.rs:243:19
    |
243 |         let req = GetOrderHistoryRequest {
    |                   ^^^^^^^^^^^^^^^^^^^^^^ missing `order_status`

warning: unused import: `tokio::stream::StreamExt`
 --> src\lib.rs:2:5
  |
2 | use tokio::stream::StreamExt;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^

warning: unused import: `Exchange`
 --> src\lib.rs:7:65
  |
7 |     exchange::{OpenLimits, ExchangeAccount, ExchangeMarketData, Exchange},
  |                                                                 ^^^^^^^^

warning: unused import: `ExchangeWs`
 --> src\lib.rs:8:33
  |
8 |     exchange_ws::{OpenLimitsWs, ExchangeWs},
  |                                 ^^^^^^^^^^

error: aborting due to 3 previous errors; 7 warnings emitted

Some errors have detailed explanations: E0063, E0308.

For more information about an error, try `rustc --explain E0063`.

error: could not compile `openlimits-python`

To learn more, run the command again with --verbose.
≡ƒÆÑ maturin failed
  Caused by: Failed to build a native library through cargo
  Caused by: Cargo build finished with "exit code: 101": `cargo rustc --message-format json --manifest-path Cargo.toml --release --lib --`

@Bi0max the plan is to fix this issue today. Let's follow this up here: https://github.com/nash-io/openlimits-python/issues/6


Simplify and update gen2 rgb depth align experiment

The gen1 rgbd example looked promising, but it seems like the push to migrate this to gen2 lost steam or the original dev got busy. I had to write this for my own use and wanted to share my work since I benefited so much from the existing depthai examples.
This boils down the experiment into two files:

visualize depth or rgbd image as a 2d image and 3d pointcloud (supports gen2's aligning on device option as well as aligning on the host. Not sure why I get those weird lines aligning on host though :thinking: )
extension of the projector_3d.py utility for doing 1 and 2 that supports downsampling the depth image / pointcloud since all those depth to 3d deprojections can be heavy on old laptops like mine :sweat_smile: .

Also, depending on the lighting, the oak-d-lite struggles to estimate depth on my plain white wall (regardless of how much post-processing I throw at it), but I think that is just a passive stereo issue. However, I really like that it knows that the depth is bad and thus has a low confidence score allowing me to filter it out :smiley:
Result for 1:

Result for 2 (align on device):

Result for 2 (align on host):

Thanks.  So actually I think we do have a better version on Gen2 already.  But I think this was probably a great way to learn/practice all the math, so worth it anyway.
CC: @saching13 for any comments here.

Hi,
Looks like you improved on the existing PR.
Thanks alot for the additional improvements. Will review it soon.

Ah cool thanks!


Specify the OpenXR components the loader can interact with

See https://github.com/GodotVR/godot_openxr_loaders/issues/22#issuecomment-1423046256 for reference.

cc @rbessems

@m4gr3d tested to work on ML2.


fix: Improvements for small screens

Hi!
Here are a few improvements for small screens:

The NavBar gains 2 pixels
The tagline tries to find a few pixels
The title of the tagline uses an AutoSizeText
The title of a scan card uses an AutoSizeText
The "tap for more info" button scales down if there's not enough space
The "not found" scan card is scrollable and fully clickable only on small screens (irrelevant for bigger ones)
Product compatibility on the product page: the percentage doesn't scale

Until we destroy the carousel, we can't have a real fix for this screen.

Codecov Report
Attention: Patch coverage is 0% with 37 lines in your changes missing coverage. Please review.

Project coverage is 6.49%. Comparing base (4d9c7fc) to head (4a28e44).
Report is 559 commits behind head on develop.

Files with missing lines
Patch %
Lines

...s/product_cards/smooth_product_card_not_found.dart
0.00%
24 Missing :warning:

...ges/smooth_app/lib/pages/product/summary_card.dart
0.00%
9 Missing :warning:

...ib/pages/scan/carousel/main_card/scan_tagline.dart
0.00%
3 Missing :warning:

.../cards/product_cards/smooth_product_base_card.dart
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           develop   #6036      +/-   ##
==========================================
- Coverage     9.54%   6.49%   -3.06%
==========================================
  Files          325     441     +116
  Lines        16411   24991    +8580
==========================================
+ Hits          1567    1624      +57
- Misses       14844   23367    +8523

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Prerendering failed because - MouseEvent is not defined

Hello!
I got the latest version of repo and when I run the project, I got this error:

Hey there! So it looks like you've added a library or code within your app that is using things that aren't available on the server. What were you trying to add in there?
Sometimes it can be as easy as only importing it in the browser NgModule and injecting it in components with @Optional(), other times you have to mock an implementation out for the server NgModule to use instead, and worst case you have to use webpack to manually swap out libraries and provide mocked classes/exports for them.
Let me know, so we can try and figure it out!

I've got the exact same problem with the latest version of the repo, haven't added anything just ran the code as described in the Readme

Oh wow really? Might be a third party library out of no where that updated in a strange way. I'll have to take a peak in the morning, very strange!

Indeed, thanks for the quick response 👍

I've got the exact same problem. I did nothing else than downloading the project from the repository, and then tried to run it. I didn't dig too deep into the problem, but it seems like ngx-bootstrap causes the problem. I removed it from the project, and now it works. Except the ngx-Bootstrap demo page of course ;)

@thomasm how or what exactly did you remove? Just the declaration and routing part in app.module?

@casni Yes, i removed the Ng2BootstrapModule and NgxBootstrapComponent imports and declarations, and the routing part in app.module.ts. I also removed the ngx-bootstrap folder in "app/containers/" , but that was probably not necessary.

Had the same problem. Culprit was ngx-bootstrap version v2.0.0-beta.4, fixing the dependency to version v2.0.0-beta.3 solved the issue.

About ngx-bootstrap package versions:
v2.0.0-beta.3 - doesn't work.
v2.0.0-beta.4 - works!
v2.0.0-beta.5 (latest) -  - doesn't work.

For me 1.9.3(Stable release) is working fine.
@MarkPieszak
BTW, why we are trying to setup the beta? any reasons ?

@davidsekar there is a known bug where the non-beta version of bootstrap gives a template error in the console. vnext has  fix for this.

Switching to another version of bootstrap takes care of the MouseEvents error, but gives another error:
NodeInvocationException: Prerendering failed because of error: TypeError: Cannot read property 'forRoot' of undefined
I tried with 1.9.3, and beta 03 & 04.

I'll pin it to beta.3 for now to fix the issue with anyone pulling a fresh copy of the repo, sorry about that guys! Third party libraries are never easy to deal with :)
@davidsekar I think someone set it up since it was complaining about 1.x versions since they used <template> tags instead of <ng-template> etc. I'll try to contact Dmitry the ngx-bootstrap author to let him know MouseEvent is breaking Universal.


[icu] update to 75.1

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[ ] The "supports" clause reflects platforms that may be fixed by this new version.
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

I see direct failures for

boost-locale (CMake)
cppcms (CMake)
harfbuzz (meson)
libphonenumber (CMake)

but more trouble might be waiting in the resulting cascades.
icu can't easily pass on the C++17 usage requirement. Mitigations:

pkg-config: I don't know.
CMake: vcpkg cmake wrapper.
Meson: I don't know.


change texture of elevator

Describe the solution you'd like
It would be nice if you can change the texture of the elevator to any block
Additional context
The elevator would be more fitting in the floor of the buildings

I have no plans to enable to change textures because this is the "Quartz" Elevator.
If you really want to change the textures, you can manually modify the model files.
https://minecraft.fandom.com/wiki/Model
quartz-elevator.jar
└── assets
        └── quartzelv
                └── models
                        ├── block
                        │       ├── smooth_quartz_elevator.json  <- edit
                        │       └── quartz_elevator.json  <- edit
                        └── item
                                 ├── smooth_quartz_elevator.json  <- edit
                                 └── quartz_elevator.json  <- edit

If you're bothered by particles, you can hide them. (ModMenu > Quartz Elvator > Display particles: Yes -> No)


Parse PDFs as XML

Possibly using Grobid? This would retain some structural info about the PDF, allowing us to check in probable locations for the GitHub Link (or first of all, do a sample analysis of where relevant links are usually located).

I installed and built grobid in our EIDF VM, but can't make it work. Both a local install+build if the service and a docker service terminate without any error messages after about half a minute when being queried. There is nothing in the logs the docs point to, and the only message I get is a "remote disconnect" in the client script. Everything works fine when using the demo server, but I don't think we should try and use that for our analysis.
I've combed through the issues in grobid's repository but have found nothing helpful so far.
I'm wondering how important this is to us - do we want to spend time trying to implement Grobid? It might be very time-consuming to make it work and then also to run it on each PDF (it wants GPUs but our VM doesn't have them). To be fair, I have not had a look at a sample of our PDF data to manually check how well our fulltext search for git links performs and how many false positives we get. Should we spend time on that before dealing with Grobid again?

We can use the page the link was found on as a proxy for now, though we should definitely do some validation of that method as it's not as common as going by sections.


[GUI - V1] White screen when publishing an empty data.

I'm submitting a ...

[X] bug report
[ ] feature request
[ ] support request

Do you want to request a feature or report a bug?
bug

What is the current behavior?
When I publish an empty data, I come across a white screen in the device details

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
1º Create a template, dynamic and string

2º Link template to a device.

3º Detail the device

4º publish an empty data
mosquitto_pub -p 1883 -t admin:258436/attrs -m '{ "1teste": ""}' -q 1 -u admin:258436

5º Click on the f5 button, reload the page

6º Click on the button the attribute 1test, white screen again

NOTE:  THE SAME HAPPENS ON THE KUBERNETES

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Version: 0.6.0-rc2 - Gui - v1
Environment: [kubernetes, docker-compose]
Operating system: [Ubuntu 18.04]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Teste realizado [docker-compose v0.7.0-rc.1]


Debugging gen manifest status

Signed-off-by: Ricardo Zanini<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors' guide
[ ] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[ ] Pull Request contains a link to the JIRA issue
[ ] Pull Request contains a description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster

@sutaakar for our joy!! \o/


Offer a Global view for Tagged objects.

Environment

Python version:  3.5
NetBox version:  2.4.6

Proposed Functionality
At the moment we are only able to view tags by object type. i.e. Just circuits or just routers with a specific tag. yet we are able to tag multiple types of object with the same tag.
When clicking a tag we remain within the object that the tag was selected in. I.e if the tag was in circuits then clicking "TESTTAG" would result in https://netbox/circuits/circuits/?tag=TESTTAG
This request is to create a view that allows us to view tags applied to multiple objects similar to how the search function currently looks. The proposed view would list all objects types with that same tag applied.

In the admin view we are able to see multiple objects with the same tag applied, so making a view with this same functionality shouldn't require any database changes as the functionality looks to already exist.

From here we could link the current tags view to a list of all objects under that tag.

Use Case
We are looking at implementing tags to track what objects make up a service. This can include interfaces, routers, vlans, sites, etc.
Being able to click on a tag and have all of these tagged objects show up would make this a great visual reference of what objects have been linked together. This could also be used to see what part of a network impacts another part if they are tagged together.

Database Changes
None, this is already viewable under the Taggit page in the admin panel, it should only require a view and url addition.

External Dependencies
None. This will leverage the current Taggit dependency.

To be clear, you're proposing a complete list of all objects assigned to a single tag, correct? As opposed to a view which lists all objects assigned to all tags?
Also, a tangent: The current admin UI should have been removed in the v2.4 release. Manually assigning tagged objects in that manner obviously isn't very user-friendly.

Correct. A view that shows a complete list of all objects assigned to a single tag.
The admin view was just an example of how this functionality could be seen at the moment. I wont be planning on using this to assign objects to tags going forward.
Thanks.


Added markdown support for italics and bold

Created 2 new functions, italicize and boldify which will be applied to any lines containing either markdown symbols in a loop until all markdown is converted to HTML appropriately
Simplified a few lines with size_t checks to just check string.find results instead

The changes look good, the only few things would be for the if statements at Line 167, I would wrap them in an if statement checking for fileType 2 instead of adding that into all the if statements, that way it is cleaner when more syntax is added. And you might be missing a != string::npos in that if statement, if my understanding is correct.
Also, the functionality where when first line is followed by two blank lines and it turns the first line into the title and header. I think this functionality should only happen when the file is a .txt file. So add an if statement that handles the title for both .txt and .md files.

The if statement at Line 134 needs fixing. It currently will skip the html if the file isn't a .txt, so .md will won't be a proper html file. You need to either place the if statement somewhere better to avoid this or add logic to fix this.
Also, what I meant by wrapping the if statements was to do:
if (filetype == 2){
    if (line.find("**") != string::npos || line.find("__") != string::npos){}

    if (line.find("*") != string::npos || line.find("_") != string::npos){}
}

Please update these if statements here.

Almost what I wanted. Just fix the redundant if statement by merging them instead.
Merge this and this so it matches my previous example.
if (filetype == 2){
    if (line.find("**") != string::npos || line.find("__") != string::npos){
          line = boldify(line);
    }

    if (line.find("*") != string::npos || line.find("_") != string::npos){
          line = italicize(line);
    }
}


[layer] object initialization bugfix

Added bugfix to object initialization
Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #170. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/170-202006151738330.0037870407104492-ca72bf624f82a01d9433f4fb3d0ef92375afb489/.


Bug: If no localization was loaded, the application crashes instead of displaying an error message and closing it

Fixed by 6659c1a commit

Fixed by 6659c1a commit


Client side decorations

I think that proper CSD's could make WebCord look much more native and blend much better with desktop additionally saving some vertical space by eliminating the need of titlebar.
Here is a quick mockup in style of GTK4/libadwaita that i made to get an idea on how that could look like in practice. Personally i think it could be pretty slick.

Beautiful!

Considering Electron depends on GTK, this might be possible to do if Electron has a way to customize the CSD.

@SpacingBat3 Electron already depends on GTK, so why would it matter to try not use the entire GTK lib?

@SpacingBat3 Electron already depends on GTK, so why would it matter to try not use the entire GTK lib?

Well, consider that for non-Linux platforms. Electron there doesn't depend on GTK and uses native APIs instead.
As for other reasons, I believe module itself is quite complicated to implement in case of Electron, especially it needs to be avoided to be used within preload scripts. Avoiding native modules has also a benefit of shorter compilation time and better cross-platform support, since we don't have to care about making modules compatible with different architectures. This also makes the build on its own a bit less complex.

Wouldn't this CSD be Linux-only, though? I don't believe Windows and macOS support CSDs (I've heard macOS supports DWD, though)

Wouldn't this CSD be Linux-only, though? I don't believe Windows and macOS support CSDs (I've heard macOS supports DWD, though)

Yeah, but the module itself would have to be still installed on Windows and MacOS, it's quite hard to have a static types and optional modules…
Usually that means it has to be resolved on module side (either if it is native or not) and probably bypass some TypeScript / ESLint protections (to use require on CommonJS or dynamic import on EcmaScript modules and infer proper types).


VSCode

i don't know if it's the good repo to report this but windows-rs is unusable on vscode with rust-analyzer extension, at least auto-completion isn't available, and
mod bindings {
    ::windows::include_bindings!();
}

throw "could not resolve macro self::include"
and if you use the rust extension, the whole Cargo.html become red while it say that it fail to run build command

I'm pretty sure you need to do the following to get it to work:
1.) You need to have a "bindings" sub-crate. (examples: https://github.com/kennykerr/samples-rs)
2.) You need to enable “Cargo: Load Out Dirs From Check” in the rust-analyzer settings.

I'm pretty sure you need to do the following to get it to work:
1.) You need to have a "bindings" sub-crate. (examples: https://github.com/kennykerr/samples-rs)
2.) You need to enable “Cargo: Load Out Dirs From Check” in the rust-analyzer settings.

Yes, rust-analyzer is your best bet even as it has a few limitations and struggles with the sheer volume of code. We are investing in rust-analyzer so I am hopeful that it will improve in time. Give @Josh015's suggestions a try, but any feedback about rust-analyzer should probably go here: https://github.com/rust-analyzer/rust-analyzer/issues

Yes, rust-analyzer is your best bet even as it has a few limitations and struggles with the sheer volume of code. We are investing in rust-analyzer so I am hopeful that it will improve in time. Give @Josh015's suggestions a try, but any feedback about rust-analyzer should probably go here: https://github.com/rust-analyzer/rust-analyzer/issues


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
ef9143b -> ab267b7

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.25.6 -> v1.26.1

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.26.1
Compare Source
Bug Fixes

deps: update gomod (#726) (a42f8cf)

v1.26.0
Compare Source
Features

expose checkConsistency with public function (#724) (f9ab5b8)

v1.25.8
Compare Source
Bug Fixes

deps: update gomod (#723) (7596e10)

v1.25.7
Compare Source
Bug Fixes

deps: update gomod (#721) (addd7eb)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

:tada: This PR is included in version 1.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


api/v1: Allow fetching specific blueprint version (HMS-4512)

Allow fetch specific Blueprint version, to allow versioning diff in the UI.

@lzap rebased, could you give it another look? :)


Login Popup Come

Describe the bug
I implemented this traccar API in my website so there was one popup coming when I entered first time in browser.
Screenshots
This popup comes when start my web-app.

Here in API's session and server API called but there was token API status was pending.

When I give username and password and then press signin button on popup then traccar API working fine. But when I press cancel button of popup then token and all other API cancelled and HTTP 401 Unauthorized-WebApplicationException(SecurityRequestFilter: 126<...) this error gives by all the cancelled API's.
So Please gives me suggestion how I will fix it.

Please use the forum for questions.


Do you support scripts for Linux/Ubuntu yet?

I saw you provided the laptop script for Ubuntu in this blog.
From blog:

bash <(wget -qO- https://raw.githubusercontent.com/thoughtbot/laptop/master/linux)

But that script is not available anymore.

Hi @remy727 We dropped Linux support a long time ago, and have no current plans to bring it back, as it is not something any of the maintainers use and wasn't realistic to keep up support.
I will think how best to update that blog post, either by removing the linux example, or just providing a call out at the top of the post that Linux is no longer supported.
Thanks.

Got it. Thank you for letting me know. I will close the issue for now.
Please feel free to update the blog post.
Thank you!


The dependency IdentityServer4 >= 1.0.0-beta4-update1 could not be resolved.

When I open up the IdentityServer4.xproj, Package restore is failing on on IdentityServer4 1.0.0-beta4-update1.
The error says "The dependency IdentityServer4 >= 1.0.0-beta4-update1 could not be resolved.
Any tip on how i can get this project to build? Thanks!

Mare sure the Nuget.org Package source is enabled.

That worked. For some reason I didn't have all the nuget sources enabled. Thank you.


Slovakia Flags

Give filename the extention .netkan

FATAL CKAN.NetKAN.Program (null) - Module contains no files to install.

Hmmmm

Merged with thanks!


feat: Ability to mount volumes

For sources like source-file where someone wants to access a local CSV, we wont be able to access them from inside the docker container. Maybe we should add the ability to configure a volume, it could be hidden or defaulted to meltano root for most sources.

This is completed via a new config option named docker_mounts which takes a list of maps which follows the specification here
I included an integration test for it too.
Example:
{
  "docker_mounts": {"source": "/local/path", "target": "/container/path", "type": "bind"}
}

This is great! I also was able to get this working easily.


What is the advantage of this lock?

https://github.com/apache/dubbo/blob/317e62f73fd0a9bac4b34eb8b2c31bbae591ef91/dubbo-rpc/dubbo-rpc-dubbo/src/main/java/org/apache/dubbo/rpc/protocol/dubbo/DubboProtocol.java#L458-L494
Why not use the key to lock
synchronized (key.intern()) {
 // ...... content
}

see, maybe he doesn't want to affect multiple locks because of the key string

Have a look at the situation like this:
When thread A finishes executing locks.putIfAbsent(key, new Object()),
another thread B which holding the lock executes locks.remove(key),
and then thread A executes synchronized (locks.get(key)).

You raise a good question, when you say this, he will have a null pointer exception.
你提出了一个好问题，当出现你说的这种情况下，他就会出现空指针异常。


onMessageReceived does not work ios after the application has been opened using push notifications.

Bug report
FirebasePlugin.onMessageReceived does not work ios after the application has been opened using push notifications.
Downloading application and memory.
Send a push.
By clicking on the received push, the application opens and processes FirebasePlugin.onMessageReceived.
Without closing the application, I send another push.
Nothing happens (

CHECKLIST

[x] I have read the issue reporting guidelines

[x] I confirm this is a suspected bug or issue that will affect other users

[ ] I have reproduced the issue using the example project or provided the necessary information to reproduce the issue.

[ ] I have read the documentation thoroughly and it does not help solve my issue.

[x] I have checked that no similar issues (open or closed) already exist.

Current behavior:

Expected behavior:

Steps to reproduce:

Screenshots

Environment information

Cordova CLI version

cordova -v

Cordova platform version

cordova platform ls

Plugins & versions installed in project (including this plugin)

cordova plugin ls

Dev machine OS and version, e.g.

OSX

sw_vers

Windows 10

winver

Runtime issue

Device details

ipad air 2 ( 13.5.1)

iOS build issue:

Node JS version

node -v - v12

XCode version
last

Related code:
insert any relevant code here such as plugin API calls / input parameters

Console output

console output

// Paste any relevant JS/native console output here

Other information:

See Foreground notifications documentation.
Please use the example project as a known working codebase for reference.

@dpa99c
You are wrong, because the message is delivered without problems even without "notification_foreground": "true"


angular and chartist are installed in subdirectory /node_modules upon npm install

When you have a project that depends on angular, chartist and angular-chartist, angular-chartist installs its own versions of angular and chartist in a subdirectory /node_modules, like this:
/your-project
  /node_modules
    /angular
    /chartist
    /other_modules
    /angular-chartist.js
      /node_modules
        /angular    <--again?
        /chartist   <--again?

This makes it impossible to make angular-chartist rely on a different fork of chartist other than the official one
This bundles angular right in a browserify bundle, even when you want it out of your bundle and loading through a CDN

Taking them out of dependencies in package.json and bower.json will solve this. (The versions of chartist are not even the same across these files)

As far as I know, declaring the dependencies of the package is the correct way to distribute npm modules. As an example, see Browserify and Angular

This makes it impossible to make angular-chartist rely on a different fork of chartist other than the official one

Are you sure about this? Have you tested this? I have several projects where I declare whatever version I want and that is the one that gets used, despite what other packages might want.

This bundles angular right in a browserify bundle, even when you want it out of your bundle and loading through a CDN

I have a feeling that this is not an issue specific to this repo and is something other Browserify users have dealt with. A quick google search gives me these two results. Perhaps these will help?

(The versions of chartist are not even the same across these files)

Are you sure?

If you can find me some official documentation that support your case, I will be happy to look at over.

I uninstalled and reinstalled angular-chartist.js, and lo and behold, it works and now takes my own fork of Chartist! I am confused though as to why so many other directives don't declare their dependencies in package.json. See here, here or here.

Very odd, but I feel like declaring it in dependencies is the right way to go. It could be that they are going against the grain to avoid having nested dependencies (like you alluded to).
Glad you got it worked out though!


RNVectorIconsModule not available Android

I'm having a problem with using .getImageSource() on Android (although I still haven't tested it on iOS)
RNVectorIconsModule not available, did you properly integrate the module? Try running `react-native link react-native-vector-icons` and recompiling.
ensureNativeModuleAvailable
    create-icon-set.js:96:10
getImageSource
    create-icon-set.js:110:4
registerApp
    index.js:35:22
<unknown>
    index.android.js:8:12
loadModuleImplementation
    require.js:174:12
guardedLoadModule
    require.js:119:45
_require
    require.js:110:20
global code

I've tried everything:
react-native link or react-native link react-native-vector-icons (both throw an error while trying to link iOS)
And the manual installation as well, but it still doesn't work
I've added everything as the instruction says: in build.gradle, settings.gradle and MainApplication.java
I'm using:
react-native v.0.48.3
react-native-vector-icons v.4.4.2
Am I missing something here?

Try installing manually

same issue !

I followed all the steps, including the modification in MainApplication.java but didn't manage to solve this problem.

I'm having the same problem. Any progress?

Following the the manual installation steps solved the problem in my case

Assuming this is fixed now we have auto linking


Circle radius

Sorry, guys, but you have a problem with your understanding of circle radius. Change it to "circle diameter", please.
Here link to Wiki: https://en.wikipedia.org/wiki/Radius

Sorry, guys, but you have a problem with your understanding of circle radius. Change it to "circle diameter", please.
Here link to Wiki: https://en.wikipedia.org/wiki/Radius

Don't be so smart :)


Could i apply this method to image colorization

Hi, could i apply this method to image colorization and remove the temporal consistency loss?
BTW, how to get the pairs.txt/pairs_mid.txt/pairs_bad.txt used in videoloader_imagenet.py?

Yes, for image colorization you can remove the temporal consistency loss.
You can use this repo https://github.com/hmmlillian/Gray-Image-Retrieval to retrieve paired images for ImageNet dataset. You can measure the similarity of image pairs according to the matching score, and put good matchings, intermediate matchings and bad matchings into the corresponding files.

Hi, I want to follow up to see how to remove the temporal consistency loss? Thank you!


Add support for Hub XMLRPC API container

What does this PR change?
This PR add support for Hub XMLRPC API container.
It creates the systemd service on install and handles it on start, stop, restart,status and uninstall commands.
It includes also a bugfix - restart of postgres after installing new certificate - this is needed for reportdb access from hub.
The service depends on https://github.com/uyuni-project/uyuni/pull/8710
Test coverage

No tests: add explanation

[ ] DONE

Links
https://github.com/uyuni-project/uyuni-tools/issues/292
https://github.com/uyuni-project/uyuni/pull/8710

[ ] DONE

Changelogs
Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository
If you don't need a changelog check, please mark this checkbox:

[ ] No changelog needed

If you uncheck the checkbox after the PR is created, you will need to re-run changelog_test (see below)
Before you merge
Check How to branch and merge properly!

I have rebased it and added a fix for utils.Errorf. Now the PR should be complete, except for kubernetes support.


#50 Make a few session-related types and initializers public

What
Making a few session related properties, initializers and types public, so that #50 people can inject URLSession.
Why
See ticket #50.
Affected Areas

API should be backward compatible.

Please let me know this is now a mergeable state.


Dependency updates

Currently using PyUp but it somehow missed its dependency update for December and is quite limited anyway (only Python so will not help with other projects)
Snyk has a lot of features (eg. code scanning) but can't get it to make dependency updates other than for security (despite turning on "automatic dependecy update pull requests")
GitHub's built-in Dependabot might be good, nice to have everything in GitHub, though maybe not as fully featured as Snyk.

Seems like Dependabot can't group updates together which creates a lot of noise https://github.com/dependabot/dependabot-core/issues/1190

Renovate needs some config but I use it for work, probably about the same features as Dependabot https://github.com/rparini/cxroots/pull/111

But it can't support environment markers in the requirements.txt which we currently need to test against Python2: https://github.com/renovatebot/renovate/issues/12727

From a security point of view this was quite clever: https://github.com/rparini/cxroots/pull/122
Snyk updated an indirect dependency even though it wasn't listed explictly in the requirements.txt

PyUp have decided to require all users to have paid accounts from 1st August so I'll need to find an alternative


Pydata theme for documentation

See discussion at #28. We thought TOC trees doesn't work in this theme but it just requires a different syntax.
Also includes minor fixes/rewording of documentation content.

@ziw-liu I ran into error when installing the dependencies with
pip install "<path_to_iohub>[doc]
Details

Processing /Users/shalin.mehta/Documents/code/iohub
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [43 lines of output]

....
....
 File "/private/var/folders/2w/3lz_vt297916ljyjzhtwvsf00000gp/T/pip-build-env-_levik4c/overlay/lib/python3.9/site-packages/setuptools_scm/version.py", line 271, in _bump_dev
          raise ValueError(
      ValueError: choosing custom numbers for the `.devX` distance is not supported.
       The 0.1.0.dev1 can't be bumped
      Please drop the tag or create a new supported one ending in .dev0
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.

@mattersoflight try installing with #125.

Made some minor edits. Merging.


Passing port as string fails

Hi
If you're using releases and want to pass in the port as an ENV variable, you'll likely be using the REPLACE_OS_VARS approach
config :logger, :gelf_logger,
  host: "${GRAYLOG_HOST}",
  port: "${GRAYLOG_PORT}"

Problem with that is that the port gets interpreted as a string, which fails when calling the gen_udp module.
It'd be nice if the library could handle casting the port to an integer before being used

I've released a new version that converts a binary into an integer when appropriate. I'll publish it to hex in just a minute. Let me know if this solves your problem.

That was quick! It's perfect, thanks


export tests: ensure pod readiness before command exec

What this PR does
This may or may not help with flakes. "ready" is a bit of a stronger indication than "running".
error dialing backend: write tcp: use of closed network connection

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

NONE

/cc @mhenriks

/approve


Fixes on CSV, Twitter Username, and Emoji

I'm using python csv module, and added the emoji. I'm also fixes the username not being pulled into Tweet class.

i think the development of this repository is over


Update to windows-rs 0.48

I don't know if this is the correct procedure, especially around a winmd file, but the sample worked.

It seems that the winmd file does not need to be updated, so I deleted the second commit.

Looks like there's a conflict with some of the new interface implementations I just added in options.rs. Feel free to update them, or I can take a deeper look in a little while.

Once this is merged, I'll bump the version numbers and publish the changes in all 3 crates to crates.io.

OK, I'll do that. Just a moment, please.

done.


Service calls from HomeAssistant fail due to "unknown error"

Is there an existing issue for this?

[X] I have searched both the existing open issues & recently closed issues and did not find a duplicate of this issue.

I have read about the Fleet API and understand I may need to use it

[X] I understand issues relating to read only commands will be auto closed if not using the Fleet API.

Version of the Tesla component
3.21.0
Version of the Tesla car software
2024.3.25
Model
Model 3
Current Behavior
Service calls initiated from HomeAssistant fail due to unknown error and there is no response from the car.
Expected Behavior
The service call (eg climate, covers) should produce the desired response from the car (eg trunk opened or closed, HVAC turned on or off).
Debug logs
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:239
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 11:56:57 AM (4 occurrences)
Last logged: 12:06:34 PM

[140461828665920] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 239, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2738, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2779, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 975, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1047, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/config/custom_components/tesla_custom/cover.py", line 115, in async_open_cover
    await self._car.toggle_trunk()
  File "/usr/local/lib/python3.12/site-packages/teslajsonpy/car.py", line 1135, in toggle_trunk
    data = await self._send_command("ACTUATE_TRUNK", which_trunk="rear")
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/teslajsonpy/car.py", line 775, in _send_command
    raise ex
  File "/usr/local/lib/python3.12/site-packages/teslajsonpy/car.py", line 760, in _send_command
    data = await self._controller.api(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/teslajsonpy/controller.py", line 1367, in api
    response = await self.__post_with_retries(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/tenacity/_asyncio.py", line 88, in async_wrapped
    return await fn(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/tenacity/_asyncio.py", line 47, in __call__
    do = self.iter(retry_state=retry_state)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/tenacity/__init__.py", line 325, in iter
    raise retry_exc.reraise()
          ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/tenacity/__init__.py", line 158, in reraise
    raise self.last_attempt.result()
          ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/concurrent/futures/_base.py", line 449, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
  File "/usr/local/lib/python3.12/site-packages/tenacity/_asyncio.py", line 50, in __call__
    result = await fn(*args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/teslajsonpy/controller.py", line 1390, in __post_with_retries
    return await self.__connection.post(command, method=method, data=data, url=url)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/teslajsonpy/connection.py", line 166, in post
    return await self.__open(url, method=method, headers=self.head, data=data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/teslajsonpy/connection.py", line 218, in __open
    raise TeslaException(resp.status_code)
teslajsonpy.exceptions.TeslaException

Anything else?
No response

Sorry, having poked around a bit I'm guessing this is related to the old api being deprecated in favour of fleet api, but if I am wrong, please let me know.

Also experienced the same on two Tesla Model3's running 2024.14.3
As Ar-eh said above feels like not working in relation to the api.

If you are able to get data from the car/API but no commands will work and you are not using the fleet API then you need to use the fleet API.
I'm going to assume that is the case and close this, but feel free to reopen if I'm wrong


Support plugin type in docker inspect

- What I did
This fix tries to address the proposal raised in #28946 to support plugins in docker inspect.
The command docker inspect already supports "container", "image", "node", "network", "service", "volume", "task". However, --type plugin is not supported yet at the moment.
- How I did it
This fix address this issue by adding the support of --type plugin for docker inspect.
- How to verify it
An additional integration test has been added to cover the changes.
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)

This fix fixes #28946.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

/cc @icecrime @vieux @tiborvass

LGTM

LGTM ping @tiborvass @anusha-ragunathan

Thanks @tiborvass for the review. This PR is loosely related to #28789
In case of plugin name without tag. If #28789 is merged in then the issue is resolved.
I added a couple of test cases for plugin name without tag. The test cases will fail at the moment, but should be able to pass after #28789 is in.
Alternatively, if we want to defer the merging of #28789 after 1.13, then I could also update this PR to only include related changes to make the test cases (plugin name without tag) pass for this PR.
Please take a look at this PR and #28789.

Very nice, but as @tiborvass mentioned, proper treatment of plugins without version (defaulting to latest) is needed. Perhaps #28789 could go into 1.13.0 as well?

LGTM. We can merge this after 28789 is merged.

@tiborvass @anusha-ragunathan Since #28789 has been merged in, I did a rebase to this PR.
Now it is possible to specify docker inspect  without the plugin tag. It is shown in the case of the added integration tests.
Please take a look and let me know if there are any issues.

The Jenkins failure is caused by:
21:06:49 Set build name.
21:06:49 Workspace is not accessible
21:06:49 Build was aborted
21:06:49 [PostBuildScript] - Execution post build scripts.
21:06:49 Notifying endpoint 'HTTP:https://leeroy.dockerproject.org/notification/jenkins'
21:06:50 Finished: ABORTED

I think triggering the Jenkins for WindowsRS1 again will likely make it pass.

Thanks @yongtang!


"SystemJS.fetch is not a function" with SystemJS 0.20

I got a "SystemJS.fetch is not a function" error using plugin-typescript (6.0.1) with SystemJS 0.20.
I found this if it can help :
https://github.com/systemjs/systemjs/issues/1543

The error is thrown at plugin.js:431. Basically, this breaks the library, or am I wrong?

Yes this breaks the library when you have typescriptOptions.tsconfig set. I am working on a fix, will hopefully release tonight but there are other issues with type-checking in 0.20

FYI: Updated to 6.03, now getting Error: SystemJS.locate is not a function instead.

This will no longer be an issue from 7.0.0 onwards.


Splits not working when there are multiple other files

I just noticed that when there are multiple other files and one selects with the pop-up menu, then the horizontal or vertical splits are not used but the selected other file opens in the current window. See video recording:
https://user-images.githubusercontent.com/175286/198975454-3ed92e49-ab88-4614-8c6d-8f32f0cf2876.mov
In this video I select "a" in the menu for both tries of the split commands.

Hi,
I see that you are confused when using :OtherSplit and a filepicker shows up that the default action does not open the file in a split. That was actually always the case, as I intended to use the OtherSplit and OtherVSplit for perfect matches.
What you could always do was:

To open the selected line without split press <cr> or o
To open the selected line in a split press v
To open the selected line in a vertical split press s

But as it seems, I forgot to document that 😠 (Which I will do now)
After our last pr I also introduced the shortcuts and additional keymaps.

To open a file by its shortcut without split press <shortcutkey>
To open a file by its shortcut in a split press <shift-shortcutkey> (so basically uppercase shortcutkey)
To open a file by its shortcut in a vertical-split press <c-shortcutkey>

Does this help you with the issue or do you think it makes sense to change the default-behaviour in the filepicker (pressing <cr> or o or <shortcutkey>) depending on how the filepicker was called initially (:Other, :OtherSplit or :Othervsplit).

Hi,
you can now configure the default keybinding :)


0.1.0 release

CC @vhdirk
I'd like to do a first release of this to crates.io, so we have it available from there already when needed somewhere (like in your application or next time I do a gst-plugin-rs release).
Are there any things we should do before that, any changes you'd like to see before?

I think it's ready as is for a first release. I'm using the git version in my own application already, and so far it's working exactly as expected.
I suspect that for crates.io you would list the dependencies (glib, etc) from crates.io and not the git version?

I suspect that for crates.io you would list the dependencies (glib, etc) from crates.io and not the git version?

Yes, I don't think it's even possible to upload otherwise

It isn't. Not sure why I even asked :)
On Wed, 2 May 2018 at 10:31, Sebastian Dröge<EMAIL_ADDRESS>wrote:

I suspect that for crates.io you would list the dependencies (glib, etc)
from crates.io and not the git version?
Yes, I don't think it's even possible to upload otherwise
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sdroege/gobject-subclass/issues/4#issuecomment-385903464,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABW8ZlHku1SocTl6JTg_xikg3CcdYDiSks5tuW7ngaJpZM4Tu8Ep
.

I've also added https://github.com/sdroege/gobject-subclass/commit/3bfecd8f0037be2ae50d6f239aee621cc92a1a94 . Good that I noticed before releasing :)

Will do release this evening unless something else comes up


Use Dockerfile and script for building in container instead of running the entire job in the container

As I mentioned in #23 and in https://github.com/libgdx/libgdx/issues/7477, the upload-artifact and download-artifact@v3 versions will be deprecated on November 30th. As v4 and v5 require node 20, when this happens it will break the existing linux job that uses a docker container for the whole job as the container uses glibc 2.17 which doesn't work with node 20.
This isn't fully ready yet, but I've changed the setup so that hopefully it continues to work with newer versions of actions like upload-artifact and setup-java. I've done this by moving the docker setup into its own action (which is local to the repo) that runs a script in the container that builds the natives and snapshots, but doesn't use any third party actions - meaning it should not be need node 20 to be used in the container.
Inspired by https://docs.github.com/en/actions/sharing-automations/creating-actions/creating-a-docker-container-action#introduction
The action does seem to run properly but of course I haven't tested it fully and there could be other issues with it.

Is this ready to merge since the pr to the main repo was merged?


[Feature Request] Support deno field for package.json#exports

Since esm.sh is only used for Deno (correct me if I'm wrong) I believe esm.sh should support a deno field for package.json#exports.
For example:
{
  "name": "react-streaming",
  "exports": {
    "./server": {
      "node": "./dist/cjs/server.js",
      "deno": "./dist/esm/server.js"
    },
    "./client": {
      "browser": "./dist/esm/client.js"
    }
  }
}

Note the field package.json#exports['./server'].deno.
Also note that using import instead of deno is problematic because dist/esm/server.js doesn't work with Node.js.

it supports, check https://github.com/ije/esm.sh/blob/266caad395b62b19646914f4c6613e96a790d511/server/nodejs.go#L436

Neat 👌.


Installation of the Library

I would like to use tools from this library in one of my projects, but I'm having some difficulties with the installation process on a Linux cluster.
I have extracted and set the library path to the shared object files for cuDSS following the directions given here. After installing CUDSS.jl, I tried to execute the following test:
using CUDA, CUDA.CUSPARSE, CUDSS, LinearAlgebra, SparseArrays
A = CuSparseMatrixCSR(sprand(100, 100, 0.1))
solver = CudssSolver(A, "G", 'F')

On the third line, I receive the following error message:
ERROR: UndefVarError: `libcudss` not defined

I'm not sure what I am doing wrong. I have also tried setting the environment variable JULIA_CUDSS_LIBRARY_PATH which is used to set the path for libcudss. Something is not being set properly. I'm using CUDA.jl (v5.4.3) and CUDSS.jl (v0.3.1) on Julia v1.9, if that helps.

@i3s93 You don't neee to install anything.
I suppose that you didn't used Julia before we already download and install cuDSS for the users.

Thank you @amontoison  for your rapid response. I actually started with the base installation in the README.md, but encountered the same error message. That is why I tried to manually set the path, but neither approach worked for me. Here is what I see on my end when I execute the code from my previous comment:
ERROR: UndefVarError: `libcudss` not defined
Stacktrace:
  [1] macro expansion
    @ ~/.julia/packages/CUDA/Tl08O/lib/utils/call.jl:218 [inlined]
  [2] macro expansion
    @ ~/.julia/packages/CUDSS/2E89a/src/libcudss.jl:245 [inlined]
  [3] #31
    @ ~/.julia/packages/CUDA/Tl08O/lib/utils/call.jl:35 [inlined]
  [4] retry_reclaim(f::CUDSS.var"#31#32"{Base.RefValue{Ptr{CUDSS.cudssMatrix}}, Int64, Int64, Int32, CuArray{Int32, 1, CUDA.DeviceMemory}, CuPtr{Nothing}, CuArray{Int32, 1, CUDA.DeviceMemory}, CuArray{Float64, 1, CUDA.DeviceMemory}, DataType, DataType, String, Char, Char}, retry_if::CUDSS.var"#retry_if#49")
    @ CUDA ~/.julia/packages/CUDA/Tl08O/src/memory.jl:434
  [5] check
    @ ~/.julia/packages/CUDSS/2E89a/src/error.jl:45 [inlined]
  [6] cudssMatrixCreateCsr
    @ ~/.julia/packages/CUDA/Tl08O/lib/utils/call.jl:34 [inlined]
  [7] CudssMatrix(A::CuSparseMatrixCSR{Float64, Int32}, structure::String, view::Char; index::Char)
    @ CUDSS ~/.julia/packages/CUDSS/2E89a/src/helpers.jl:81
  [8] CudssMatrix
    @ ~/.julia/packages/CUDSS/2E89a/src/helpers.jl:78 [inlined]
  [9] _
    @ ~/.julia/packages/CUDSS/2E89a/src/interfaces.jl:40 [inlined]
 [10] CudssSolver(A::CuSparseMatrixCSR{Float64, Int32}, structure::String, view::Char)
    @ CUDSS ~/.julia/packages/CUDSS/2E89a/src/interfaces.jl:39
 [11] top-level scope
    @ REPL[3]:1

Can you remove the environnement variable and try to recompile CUDSS.jl with:
force_recompile(package_name::String) = Base.compilecache(Base.identify_package(package_name))
force_recompile("CUDSS")
using CUDSS

If it's still not working, what is your NVIDIA GPU and operating system / architecture?

I tried your solution, but I'm still seeing the same problem. I'm running with an NVIDIA A100 GPU with an AMD EPYC 7763 processor. The operating system is SUSE Linux Enterprise Server 15 SP4.

Did you install CUDSS.jl on a node with a GPU initially?
I will try to force Julia to reinstall the artifacts with:
rm -rf ~/.julia/artifacts/*

Can you also display the output of:
julia> CUDSS_jll.host_platform
Linux x86_64 {cuda=none, cuda_local=false, cxxstring_abi=cxx11, julia_version=1.10.4, libc=glibc, libgfortran_version=5.0.0, libstdcxx_version=3.4.30}

On my laptop I don't have an NVIDIA GPU so the shared library of cuDSS is not installed.
Are the NVIDIA drivers installed on your computer?

Okay, I have removed the artifacts as you have suggested. When I installed the package, I was on a node with the A100. Here is the output you requested:
julia> CUDSS_jll.host_platform
Linux x86_64 {cuda=12.2, cuda_local=true, cxxstring_abi=cxx11, julia_version=1.9.4, libc=glibc, libgfortran_version=5.0.0, libstdcxx_version=3.4.30}

I still see the same error message.

Just to follow up, I was able to install and run the code from the package locally on a laptop with an NVIDIA GPU. So far, I have only been able to see this issue when I try to install the package on a remote cluster. I will reach out to the system administrators and see if something on their end is disrupting the installation.

Are you using a module on the cluster to get Julia? (I.e. module load ...) If so, can you post the output of module show ...?
It seems that you're trying to use a local cuda. Assuming that wasn't your intention and own doing, it might be a global preference that is set when you load a Julia module.
Btw, which cluster is this?

@carstenbauer: This is on Perlmutter, if that helps. Here is the output of module load
Currently Loaded Modules:
  1) craype-x86-milan     3) craype-network-ofi                      5) PrgEnv-gnu/8.5.0   7) cray-libsci/23.12.5   9) craype/2.7.30    11) perftools-base/23.12.0  13) craype-accel-nvidia80  15) julia/1.9.4
  2) libfabric/<IP_ADDRESS>   4) xpmem/2.6.2-2.5_2.38__gd067c3f.shasta   6) cray-dsmml/0.2.2   8) cray-mpich/8.1.28    10) gcc-native/12.3  12) cpe/23.12               14) gpu/1.0                16) cudatoolkit/12.2 (g)

  Where:
   g:  built for GPU

I can run any of my Julia CUDA codes fine without the CUDA modules, so the CUDA Toolkit is not necessary. I see the same error regardless of whether not this module is loaded.

@i3s93 I just tested this on Perlmutter.  However if I unset JULIA_LOAD_PATH (to get rid of the global Julia preferences set by the module) and also module unload cudatoolkit, your test above works without any issues.

The environment in the global JULIA_LOAD_PATH is used to specify the CUDA version (to stop Julia from installing a version of the CUDA runtime that is incompatible with the system) and the MPI configuration. I suspect the later has no effect here.
@i3s93 did unsetting JULIA_LOAD_PATH cause pkg> add CUDSS to install a newer version of CUDA?

@i3s93 did unsetting JULIA_LOAD_PATH cause pkg> add CUDSS to install a newer version of CUDA?

@JBlaschke I assume the question was for me, because I was the one that did the (successful) test with unset JULIA_LOAD_PATH. And to answer it, yes, afterwards I get
julia> CUDA.versioninfo()
CUDA runtime 12.5, artifact installation
CUDA driver 12.0
NVIDIA driver 525.105.17

CUDA libraries:
- CUBLAS: 12.5.3
- CURAND: 10.3.6
- CUFFT: 11.2.3
- CUSOLVER: 11.6.3
- CUSPARSE: 12.5.1
- CUPTI: 2024.2.1 (API 23.0.0)
- NVML: 12.0.0+525.105.17

Julia packages:
- CUDA: 5.4.3
- CUDA_Driver_jll: 0.9.1+1
- CUDA_Runtime_jll: 0.14.1+0

Toolchain:
- Julia: 1.9.4
- LLVM: 14.0.6

1 device:
  0: NVIDIA A100-PCIE-40GB (sm_80, 38.984 GiB / 40.000 GiB available)

It looks like we don't have a version on Perlmutter yet. I might go and check the artifact install of CUDA. If that doesn't work I'd need to develop a module.

@JBlaschke Do you mean the artifact of cuDSS?
The recent version 0.3.0 works fine without segmentation faults.

@amontoison no I meant running CUDA.jl using the artifact CUDA (instead of the one provided by the OS)

On Perlmutter

@carstenbauer Thank you for taking the time to help resolve this issue! I can also confirm that unsetting unset JULIA_LOAD_PATH worked for me.
@JBlaschke Thank you for your help as well! My tests with cuDSS are a small scale, so I am fine with unsetting the environment variable until a better solution becomes available.
@amontoison I greatly appreciate the timely feedback and for having a look at this problem. Since this does not appear to be an issue with CUDSS.jl, I'm fine with closing this issue, unless the others would like to continue the discussion!

Am I wondering hiw relevant it will be to detect a local installation of cuDSS:
https://github.com/exanauts/CUDSS.jl/issues/55
cuDSS is still in preview so every minor release breaks the API, and it requires the local installation to be always the most recent version, which is hard to maintain.

@amontoison in the past CUDA would not work at all unless you used the local install on Perlmutter. It might be the case that this is no longer necessary.
I haven't had a chance to test this. Will do so soon. If it is the case that running CUDA_jll is unstable on Perlmutter, then we have no choice but to also use a local CUDSS install...

@carstenbauer @JBlaschke @i3s93
May I ask one of you to test my PR #57?
It should help to detect a local install on Perlmutter.
Do you know why Tim checks whether precompiling in this function __init__, which I based my PR on?
Is it to avoid an error when precompiling on a cluster node without GPUs?"


UI: Refactor async job polling codebase-wide

Description
Related #4762
This PR to enhance asynchronous job exploration and improve load performance

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[x] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
BEFORE:

AFTER:

How Has This Been Tested?
Create VM -> Submit -> check the networks tab in browser developer tools

@blueorangutan ui

@utchoang a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. [S]

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/4782 (SL-JID-20)

@utchoang this looks like a major codebase-wide feature change, I'm moving to 4.16/master. Thanks.

Hi @utchoang can you please resolve the conflicts and target the PR to the main branch?

@blueorangutan ui

@shwstppr a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_multiplication_x:
(SL-JID-358)

@blueorangutan ui

@utchoang a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/4782 (SL-JID-359)

@blueorangutan ui

@davidjumani a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/4782 (SL-JID-362)

@utchoang Had to clear the cache, my bad

@blueorangutan ui

@davidjumani a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/4782 (SL-JID-367)

@blueorangutan ui

@utchoang a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/4782 (SL-JID-368)

Thanks @davidjumani for testing
@utchoang one concern raised by @davidjumani, I've seen the network providers addition has been refactored as well, were you able to test them?

@blueorangutan ui

@davidjumani a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_multiplication_x:
(SL-JID-377)

@utchoang
/jenkins/workspace/acs-ui-builder/ui/src/views/infra/network/providers/AddNetscalerLoadBalancer.vue
  295:17  error  'jobId' is assigned a value but never used  no-unused-vars

@blueorangutan ui

@utchoang a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/4782 (SL-JID-378)

Tested the Network Providers, the async job calls work fine, @utchoang Can you close the add network providers forms after submitting it rather than waiting for the async jobs to complete

@blueorangutan ui

@utchoang a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/4782 (SL-JID-381)

Thanks @davidjumani @utchoang


added quality options

thank you for your great work, i've added video quality options using "videojs-quality-selector" plugin, the modified extension can be found on my profile,
regards.

This is an interesting feature, I could add it when I have time. But if you know how it works you could make a pull request if you want to contribute.

hi, some modifications in app.js:
const fullUrl = domain + "/360p30/index-dvr.m3u8";
const fullUrl480 = domain + "/480p30/index-dvr.m3u8";
const fullUrl720 = domain + "/720p60/index-dvr.m3u8";
const fullUrlsource = domain + "/chunked/index-dvr.m3u8";
const fullUrl160 = domain + "/160p30/index-dvr.m3u8";
checkUrl(fullUrl).then((_, statut) => {
if (statut === "success") {
// Insert the new player
contentStream.html(
<div data-setup="{}" preload="auto" class="video-js vjs-16-9 vjs-big-play-centered vjs-controls-enabled vjs-workinghover vjs-v7 player-dimensions vjs-has-started vjs-paused vjs-user-inactive ${className}" id="player" tabindex="-1" lang="en" role="region" aria-label="Video Player">                     <video id="video" class="vjs-tech vjs-matrix" controls> 						<source src="${fullUrlsource}" type="application/x-mpegURL" id="vod4" res="source" label="source" selected="true"> 						<source src="${fullUrl720}" type="application/x-mpegURL" id="vod3" res="720" label="720p60"> 						<source src="${fullUrl480}" type="application/x-mpegURL" id="vod2" res="480" label="480p"> 						<source src="${fullUrl}" type="application/x-mpegURL" id="vod" res="360" label="360p"> 						<source src="${fullUrl160}" type="application/x-mpegURL" id="vod0" res="160" label="160p">                     </video>                 </div>
then under playback speed function i've added this :
//Add quality selector
videojs('video', {}, function() {
var player = this;
player.controlBar.addChild('QualitySelector');
});
and of course i included the plugin js files in \src\scripts :
selector.js
silvermine-videojs-quality-selector.min.js
and the css file in src\style :
quality-selector.css
and on the manifest file....

Thanks for the help! It's now added (https://github.com/besuper/TwitchNoSub/commit/39240c721931028ab38f05b5f2d918a88f4f00f6)


Join Us in the Header is not working

Description
When clicking the "Join Us" button, it should scroll to the "Join the Effort section"
Acceptance Criteria

[x] Add an anchor

For some reason, an offset of 80 pixels was not working even though the header height is only 80px (it was showing a pixel of the section above). Current fix was to set the offset as 79 pixels


Revamped Character Map scenario to be amaze

I must have something very important to be doing, because I'm clearly writing code as a way of procrastinating.
This PR massively updates Character Map:

Now supports keyboard and mouse navigation/selection of glyphs.

Single click selects
Double click shows message box with info
Right click provides Copy Glyph and Copy value context menu
Home, End, PageUp, PageDown, Up, Down, Right, Left all work

New "jump to glyph" textfield takes decimal or hex values to jump to a particular glyph
Copied all ranges from TableEditor.cs and changed radio group to a listbox

I've wanted a way of getting a glyph to the clipboard forever; this makes it easy.
⚽⛔➗⏰

Very nice, Please keep procrastinating!


Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
Cannot upgrade Mailbird.Mailbird. Installer failed with exit code: 1603
Steps to reproduce
winget upgrade Mailbird.Mailbird --silent

Actual behavior
winget upgrade Mailbird.Mailbird --silent
Found Mailbird [Mailbird.Mailbird] Version 2.9.68
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Successfully verified installer hash
Starting package install...
Installer failed with exit code: 1603

Expected behavior
Upgrade the package without any error codes.
Environment
Windows Package Manager v1.3.2691
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19044.2130
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Screenshots and Logs

https://learn.microsoft.com/windows/win32/msi/error-codes
Without knowing what is causing the installer to throw a 1603 error, this will be hard to troubleshoot. Is the package running while you're trying to perform the update? Can you share the logs from the installer?


Add Azure RTOS threadx support

Can I submit a PR to add two Azure RTOS threadx samples? Here are my thoughts. This benefits user who want use Codethink driver API under threadx RTOS.
First one will be the classic demo_threadx projects for testing. I would like to submodule the official threadx 6.1 repo.
The Second one is to demonstrate how to use async peripheral API together with RTOS semaphore and mutex to make it as a blocking API in a RTOS environment.
Now I have a small 'blocker' when I'm making the first project. The default threadx cortex-m4 porting (.S) need two CMSIS compatible symbol 'PendSV_Handler' and 'SysTick_Handler'. I can directly modify VectorTable.c file in lib folder, but I want to make it as a submodule to be more consistent like other sample project. So I create a copy version under project root to do this.
Do you think it makes sense to rename all Exceptional handler name in VectorTable.c to align with CMSIS naming?
extern const pFunc __Vectors[240];
       const pFunc __Vectors[240] __attribute__((used, section(".vectors"))) = {
  (pFunc)(&__StackTop),                     /*     Initial Stack Pointer */
  Reset_Handler,                            /*     Reset Handler */
  NMI_Handler,                              /* -14 NMI Handler */
  HardFault_Handler,                        /* -13 Hard Fault Handler */
  MemManage_Handler,                        /* -12 MPU Fault Handler */
  BusFault_Handler,                         /* -11 Bus Fault Handler */
  UsageFault_Handler,                       /* -10 Usage Fault Handler */
  0,                                        /*     Reserved */
  0,                                        /*     Reserved */
  0,                                        /*     Reserved */
  0,                                        /*     Reserved */
  SVC_Handler,                              /*  -5 SVCall Handler */
  DebugMon_Handler,                         /*  -4 Debug Monitor Handler */
  0,                                        /*     Reserved */
  PendSV_Handler,                           /*  -2 PendSV Handler */
  SysTick_Handler,                          /*  -1 SysTick Handler */

  /* Interrupts */
  ...
};

Hey, I think the easiest solution for now would be to use aliases to handle the handler function naming differences, see:
https://www.keil.com/support/man/docs/armcc/armcc_chr1359124980906.htm
https://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcc/Function-Attributes.html
I have no strong preference about the vector table naming, only that to change it now might cause compatibility issues. If the aliasing approach can work then we could merge those changes to make future attempts to use CMSIS code easier.

The problem is the arch porting file (.S) is within threadx repo and it hardcode to PendSV_Handler. And vector table are within mt3620-m4-drivers repo. If I want to submodule both without a change, I guess this alias attribute will NOT solve this problem?
    .global  PendSV_Handler
    .global  __tx_PendSVHandler
    .thumb_func
PendSV_Handler:
    .thumb_func
__tx_PendSVHandler:
@
@    /* Get current thread value and new thread pointer.  */
@
__tx_ts_handler:

#ifdef TX_ENABLE_EXECUTION_CHANGE_NOTIFY
@
@    /* Call the thread exit function to indicate the thread is no longer executing.  */
@
    CPSID   i                                       @ Disable interrupts
    PUSH    {r0, lr}                                @ Save LR (and r0 just for alignment)
    BL      _tx_execution_thread_exit               @ Call the thread exit function

Also suggest we provide individual function implementation with weak attribute for all exceptions, even it is just while(1). Currently all faults go to DefaultExceptionHandler() and make difficulty for user to debug.
Once have this changed, if a user is using a old naming PendSV() as or SysTick(), the code will go to a specific weak implementation and soon to correct the naming, or do whatever they like

Wait no, sorry not thought that through, we'd need a file, which has CMSIS stubs like:
// CMSIS Compatibility Stubs
void PendSV(void) { PendSV_Handler(); }

emm... PendSV() and Systick() are heavily invoked exception handler during OS context switching.. Having this stub will degrade performance which count every cpu cycle.
I can override by providing my own implementation of VectorTable.c for this single project if you think this is acceptable.

@xiongyu0523 - the problem is we don't want to cause compatibility issues for code that already depends on our drivers. If you could write a VectorTable.c with the threadx naming convention, then I think that would be best. We might want to split out the CPU_Freq stuff into it's own source file to minimise duplication.

Sounds good. I will submit PR for Azure RTOS 6.1 port with standard demo_threadx project and wait for https://github.com/CodethinkLabs/mt3620-m4-drivers/issues/17 close to submit a I2C RTOS blocking example.


Add table spanning support

Bug/issue #, if applicable: 98017748
Summary
Adds support for Table col and row spanning, based on the initial DocC draft proposal.

Note:
This is still experimental and needs to be synced with actual DocC RenderJSON. For now think of this as a POC.
Dependencies

DocC PR - https://github.com/apple/swift-docc/pull/385

Testing
Use the provided JSON.
example_tablespan.json.zip
Steps:

Paste it in your doccarchive of choice
Visit the page
Assert a table is rendered with row and col spans.

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran npm test, and it succeeded
[x] Updated documentation if necessary

@swift-ci test

@marinaaisa no, I have not updated the example since @QuietMisdreavus changed the spec

@swift-ci test

@marinaaisa test it again :)

@marinaaisa @dobromir-hristov It should also be noted that the current implementation in Swift-Markdown and Swift-DocC uses ^ symbols as a row-span marker, not ". That's part of what's happening here.

@marinaaisa @dobromir-hristov It should also be noted that the current implementation in Swift-Markdown and Swift-DocC uses ^ symbols as a row-span marker, not ". That's part of what's happening here.

Tested it, works like a charm. Thanks. We just need to clear up some styling confusion and we are good to go.

Okay, now it looks as expected :) thanks @dobromir-hristov @QuietMisdreavus !

@swift-ci test


PowerShell use Chinese character “” just like "" ?

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Both these two lines of code work in PowerShell.
Write-Host “这是一段中文: This a paragrah of Chinese”
Write-Host "这是一段中文: This a paragrah of Chinese"

Did PowerShell just mean to do so or it was just a mistake of our developers ?
I was thinking if it is related to UTF-8 character set.

As you can see from the picture above, my Windows was not set to use UTF-8 character set.
Here is the output of $OutputEncoding of my PowerShell
Preamble          :
BodyName          : utf-8
EncodingName      : Unicode (UTF-8)
HeaderName        : utf-8
WebName           : utf-8
WindowsCodePage   : 1200
IsBrowserDisplay  : True
IsBrowserSave     : True
IsMailNewsDisplay : True
IsMailNewsSave    : True
IsSingleByte      : False
EncoderFallback   : System.Text.EncoderReplacementFallback
DecoderFallback   : System.Text.DecoderReplacementFallback
IsReadOnly        : True
CodePage          : 65001

Expected behavior
`Write-Host “这是一段中文: This a a paragrah of Chinese”`
Code like this perhaps ought to be wrong.

Actual behavior
`Write-Host “这是一段中文: This a a paragrah of Chinese”`
Code like this works fine in PowerShell.

Error details
No response
Environment data
PSVersion                      7.4.1
PSEdition                      Core
GitCommitId                    7.4.1
OS                             Microsoft Windows 10.0.22631
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

PowerShell - by perhaps surprising - design, allows interchangeable use of ASCII-range and non-ASCII-range ("Unicode") punctuation for syntactic purposes.
E.g., " (QUOTATION MARK, U+0022) and “ (LEFT DOUBLE QUOTATION MARK, U+201C) can be used interchangeably, and can even be mixed in a given string literal; e.g.:
# OK, despite use of two different quotation marks.
"Hi!“

For more information and a complete list of interchangeable characters, see this Stack Overflow answer.

P.S.: $OutputEncoding only comes into play when sending data from PowerShell commands to external (native) programs, and its default value is UTF-8 statically, i.e. it doesn't vary based on the current culture / system locale.

my Windows was not set to use UTF-8 character set

When I was using Windows I chose utf8 as the system locale and it was the best option. All applications, editors, file managers, cmd.exe, pwsh.exe and powershell.exe simply began to understand each other without additional actions.

For clarification, I should add:
With respect to the issue at hand:

None of the following matter: $OutputEncoding , [Console]::OutputEncoding, the system locale (aka language for non-Unicode programs) or current culture (Get-Culture) - they only matter when PowerShell communicates with external (native) programs.

Irrespective of the settings above, PowerShell-native code such as Write-Host “这是一段中文: This a paragrah of Chinese” is (in memory) always represented as UTF-16LE, and therefore supports the full range of Unicode characters, including CJK characters and non-ASCII-range punctuation such as  “

As noted, the interchangeable use of " and “ (with analogous interchangeability of other punctuation characters with syntactic function) is by design.

As an aside, @237dmitry:

Using the system locale's UTF-8 option sets both the OEM and the ANSI code pages to 65001 (UTF-8).

Unless prevented by backward-compatibility concerns (see below), this option is indeed preferable, as it makes most problems with respect to PowerShell's interaction with external (native) programs disappear, as you state.

That said, existing code can break for the following reasons:

Using the system locale's UTF-8 option fundamentally changes the interpretation of preexisting BOM-less files: Any such files that were encoded based on a legacy ANSI Ior - less likely - OEM encoding), such as Windows-1252 (or - less likely - CP437) on US-English systems, will then be interpreted as  UTF-8-encoded.

Any such file that contains characters outside the ASCII range will then be misinterpreted, because such characters require multi-byte sequences in UTF-8.

Notably, the following applications, which rely on the ANSI code page, are  affected:

Windows PowerShell
Python

Acknowledged, thanks for your answers.

Using the system locale's UTF-8 option sets both the OEM and the ANSI code pages to 65001 (UTF-8)

Yes, it was very convenient. There were no troubles at all.
As for the issue, it is very bad that pwsh uses other characters as quotes.  Moreover, not all of them, for example `u{ab} and `u{bb} work as expected, but `u{201c} and `u{201d} no:
$ «text»   # «text»: The term '«text»' is not recognized as...
$ “text”   # no error

I had no problem with Windows PowerShell, I did not use Python on Windows

I was clarifying the backward compatibility concerns in general, also for future readers.
In neither environment will you have problems with ASCII files, but any existing files that were encoded based on a legacy ANSI code page containing non-ASCII characters will by default be misinterpreted by existing scripts in ANSI-based environments, which could include source-code files. Additionally, ANSI-based environments such as Windows PowerShell (Set-Content) and Python will then start creating BOM-less UTF-8 files by default, potentially breaking consumers of such files that make the fixed assumption that the legacy ANSI encoding is used.

bad that pwsh uses other characters as quotes.

I agree that this permissiveness was never a good idea (and is incomplete, as  you point out), but we're stuck with it now.
I presume that the original design intent was to also accommodate source code created with word processors rather than plain-text editors, as the former have features such as auto-correcting " (QUOTATION MARK, U+0022) to “ (LEFT DOUBLE QUOTATION MARK, U+201C), and - (HYPHEN-MINUS, U+002D) to – (EN DASH, U+2013).

I spoke about personal experience; I simply have no local ASCII files left after ten or so years of using UTF8. If I come across such things, for example cue-files, I will recode them to UTF8:
(gc file.cue -enc ansi) | sc file.cue

@237dmitry, as a general tip: After being told that your personal circumstances aren't really relevant to the discussion, I suggest not following that up with further discussion of them.

as a general tip

Thanks, I know what to do without your advices. I did not ask you to answer.

Whether you asked for the tip or not is similarly irrelevant, as are assertions of your autonomy devoid of any other content.
I realize that I am adding to the existing distraction with the following, but hopefully it will inform future behavior:

The issue at hand has nothing to do with system locales or code pages, unlike what @MMMMMoris originally thought.

While it's worth briefly mentioning why the latter do not apply (as I did), their detailed discussion, including apparent guidance, amounts to a distraction.

Yet you provided guidance, whose specific content I consider problematic, because it suggests a cure-all to character-encoding woes that comes with serious caveats, which weren't mentioned.

To counteract that, for the benefit of future readers, I spelled out those caveats - any given user can then decide whether they apply to them or not.

After you continued with what I perceive to be a distraction, talking about your specific situation, I suggested no longer doing so.

Therefore, allow me to offer more advice:

Before posting, please consider whether the contribution is relevant to the core issue; if distractions/tangents are warranted, I suggest clearly labeling them as such.

Please refrain from cantankerous comments such as your previous one. (By contrast, my suggestion - to not continue discussing your personal situation as part of what was itself a distraction - contained actionable advice, which you're free to agree or disagree with, and free to take or not.)

As an aside

my suggestion - to not continue discussing your personal situation

What was this “as an aside” for? I just answered you.


maps: remove old map names

Remove leftover map names cilium_ep_config_* from tests, as per the comment in pkg/datapath/maps/map.go. This prefix is no longer used.
Also remove old map names created in earlier versions of the tests, as per the comment in pkg/datapath/loader/loader_test.go (see also issue referenced below).
Fixes: #6701

test-me-please

Coverage increased (+0.03%) to 46.65% when pulling 9e8062b0163ce9cc2674bd8536ce7222e20df009 on pr/qmonnet/clean_old_map_names into 5c18df5af35f9eca063ee81985c473b5468e22be on master.

restart-ginkgo

restart-ginkgo

Ginkgo hit known flake on XDP nodeport.
restart-ginkgo
test-gke

restart-ginkgo

test-gke


Some tidying while reading

@jean Please do not put linebreaks into sentences. See http://docs.plone.org/about/documentation_styleguide.html#documentation-structure-styleguide
The 80-character rule does not apply to docs.

@jean please rebase and remove the linebreaks.

@pbauer I like semantic linebreaks. See the discussion on https://github.com/apiaryio/api-blueprint/pull/324 for a PR where I was trying to introduce semantic linebreaks to a project (the relevant commits were squashed).
However semantic linebreaks is not about keeping a sentence on a single line.
It is about breaking at clause or thought boundaries, and not reflowing unnecessarily.
See http://docs.plone.org/about/rst-styleguide.html which is linked from "follow this ReST styleguide and use semantic linefeeds". Note the linebreaks in the example there, and the following:

manually insert line breaks after full stops, commas, or upon "grammatical" boundaries (and not merely word ones).

See also Brandon Rhodes's original post, itself linked from python.org: http://rhodesmill.org/brandon/2012/one-sentence-per-line/ where he responds to Limi, regarding the original title of the post:

Limi: Minor nit: When I first saw the headline of the article, I was confused — isn’t it more like “one idea” or “one concept” per line?

Brandon Rhodes: You are quite correct, as usual, Alex — the title is a significant compromise, given how many sentences themselves need to be split into several lines on a standard 80-column terminal.

This goes back to Kernighan in 1974:

Start each sentence on a new line. Make lines short, and break lines at natural places, such as after commas and semicolons, rather than randomly.

Semantic linebreaks are about using linebreaks for readability, ease of editing, for avoiding unnecessary reflowing (i.e. don't reflow a whole paragraph just to tidy things up), and for generating short diffs showing just what changed (diffs in the middle of long lines aren't great).
It's a matter of judgement, and I agree some of the breaks in my PR were ugly. I've pushed a commit that fixes a couple (and I'll try to improve more) .. but it also introduces some more linebreaks, which I think are improvements and that are in accordance with the intent of semantic linebreaks.
You are of course free to prefer not breaking sentences across lines, but I ask that you then acknowledge that this diverges from the original formulation and the python.org style guide.
I hope you reconsider though and really go for semantic linebreaks :)
Anyway, now to properly read the rapido chapter ..

Thank you :bow: