text:
Escaping Razor syntax with '@:' while preserving white-space

Hi there, I've been bashing my head against this problem for a while now and I can't seem to get through it.
I'm trying to iterate through a series of words and display them preserving whitespace. If certain words match a criteria, I need to display them differently, so I try to put them in a span tag with a certain class.
Some example code:
@{ var words = "the quick brown fox jumps over the lazy dog"; }

    @foreach (var word in words.Split(' '))
    {
        @if (word == "fox")
        {
            @:
        }
        @(word + " ")
        @if (word == "fox")
        {
            @:
        }
    }

The main issue with this is that the @: preserves the newline at the end of the span definition and closing tag, so it displays like this:
the quick brown
fox
jumps over the lazy dog

instead of simply
the quick brown fox jumps over the lazy dog

I've tried using the <text> tag, however that errors out on trying to do <text></text> stating that
The "text" element was not closed. All elements must be either self-closing or have a matching end tag.

                <text></text>

Encountered end tag "text" with no matching start tag. Are your start/end tags properly balanced?

                <text></text>

My only other option would be to use Html.Raw(), however I am using the experimental framework Blazor, which doesn't support the Html helpers yet, and while I don't see any way a user could potentially inject a script, I wouldn't like running the risk.
Is it possible to achieve what I want here?
(Also as an aside, the contributing guide currently returns a 404 (https://github.com/aspnet/Home/blob/dev/CONTRIBUTING.md))

@Worble the only way to accomplish what you're looking for is to save the text  into a variable and then spit that out via an @myClosingSpan.

Hi @NTaylorMullen, took me a little to understand what you meant, but after fiddling around with it I found out I was able to do this:
@{ var closingTag = "/span"; }
<text><closingTag></text>

And this would close the tag and render it properly without any errors, although razor does complain about the intial start tag not having an end one. Thanks a lot!

No prob 😉

authors: NTaylorMullen Worble

repo: aspnet/Razor


text:
Scaffolding fails with could not load System.Runtime version 4.2.0.0

From @twsouthwick at https://github.com/aspnet/Tooling/issues/1009
After removing the environment variable in #1008, I'm still getting an error, although a different one.
Steps to reproduce

Launch VS (I'm using a clean install of 15.0.26228.0)
Create an ASP.NET Core application (.NET Core App 1.1)
In project view, right click Controllers ->Add->New Scaffolded Item and then select MVC Controller - Empty
First time, select "Full dependencies", then repeat and fill in name

Expected behavior
New controller should be generated
Actual behavior
Get an error:
Error

There was an error running the selected code generator: 'Could not load file or assembly 'System.RUntime, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f...'. The system cannot find the file specified at...

@twsouthwick could you try clearing your NuGet cache please? You can find the button to do this at the bottom of the settings page in Tools -> Options -> NuGet Package Manager -> General

Clearing the cache fixed the problem for me, could you explain why?

This comes from a bad copy of the BrowserLink package that made it in to the CLI. When scaffolding runs, it causes a restore and build to be done by the CLI, which causes its first run experience to run, which attempts to put the bad package in the NuGet cache. Scaffolding then attempts to run the app to collect information about the available data contexts that get configured in the app's startup. If the CLI did not find BrowserLink in the cache & placed the bad package, the app gets restored with the bad package & then fails to run due to the .UseBrowserLink() call in the startup generated by the templates. Clearing the NuGet cache via VS ultimately ends up causing VS to place the BrowserLink package in the cache (when the app gets restored the next time), preventing the CLI from putting the bad package there, avoiding the issue.

source: gharchive/issue

authors: Sentinent mlorbetske

repo: aspnet/Scaffolding

license: MIT

license_type: permissive

license_source: github-api


text:
Moving all Exception strings to resource files.

cc @abpiskunov

Hi @prafullbhosale, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Did you sync up with someone on runtime side about how localized dlls would be generated out of resources you created?

:shipit:

Plan to bring up during the next design meeting.

source: gharchive/pull-request

authors: abpiskunov dnfclas prafullbhosale


text:
Microsoft.AspNet.SignalR.Core references & Newtonsoft 6.0

I've got a strange behavior.
I'm referencing Microsoft.AspNet.SignalR.Core in a web app application and also referencing Newtonsoft.Json 10.0.0 in a web application. Sometime when I build a reference to Newtonsoft 6.0 is copied to the output folder... the only reference I've found is

What can be the reason of such a behavior?

@advapiIT This is the wrong repository for this issue, it should be filed on github.com/SignalR/SignalR.

authors: advapiIT davidfowl

repo: aspnet/SignalR


text:
Issues #6838 Upgraded Event Cloud project to ABP 9.0

Closes #6838
The NuGet packages have been updated, and the target framework has been upgraded to .NET 8. ABP packages have been upgraded to version 9.0, and codes affected by the logic changes in the latest version have been corrected.

@dotnet-policy-service agree company="Volosoft"

Closing since same changes are committed to master branch.

authors: ismcagdas oguzhanagir

repo: aspnetboilerplate/eventcloud

license: mit

license_source: bigquery


text:
Crashing WiFi

A bit of a weird one here...
After running FS2FF for a while my entire router (MG7540) will stop working and need to be restarted. This causes everyone connected to lose internet until the router is reset.

That is odd the app is sending UDP traffic over port 49002.  Did you try setting the ip address of your EFB So it doesn't broadcast?

P.s. if that doesn't help you can try this fork of fs2ff that uses gdl90 protocol I stead of the text flight Sim protocol https://github.com/jeffdamp-wave/fs2ff/releases/tag/v1.1.16

I'll give that a shot, though it'll be a few days before I can try again. The issue is very intermittent.

license: Unlicense


text:
feat: Update pre-commit mirror script

Summary

pre-commit-mirror-maker is not suitable for generating multiple hooks in single .pre-commit-hooks.yaml file.
So replaced the script and github workflows.

Test Plan

Update pyproject.toml's ruff==0.0.290 into ruff==0.0.289, and run the script.

$ python3 mirror.py
...

Nice, thank you so much! We'd just discussed doing this internally, you read our minds... I will defer to @zanieb for review. (Zanie's out on vacation so will probably get to this next week.)

authors: charliermarsh sudosubin

repo: astral-sh/ruff-pre-commit


text:
RUF055: false negative for re.search(...)

import re

def test_cost_repeated_merge(errors):
    assert any(re.search("Duplicate merge", error.message) for error in errors)

$ ruff check d.py --select RUF055 --preview
All checks passed!

$ ruff --version
ruff 0.8.1

plarground: https://play.ruff.rs/9db437a8-cdfd-457c-a964-09fd788b9970

The issue here is that Ruff doesn't detect that re.search is used in a boolean position.

The issue here is that Ruff doesn't detect that re.search is used in a boolean position. I don't think it's worth special casing any (and many other functions that take boolean arguments)

Wouldn't it make more sence to rewrite re.search("Duplicate merge", error.message) to "Duplicate merge" in error.message to fit in boolean type?

It's not about the rewrite. It's that Ruff doesn't think it's safe the change the search call because it doesn't know that the re.search result is used in a boolean position - the code only tests if the result is true or false.

OK， I misunderstand. I thought that ruff know it's used as bool and decide not to report a issue.

repo: astral-sh/ruff


text:
Complete pyupgrade documentation

Summary
Completes the documentation for the pyupgrade rules.
Related to #2646.
Test Plan
python scripts/check_docs_formatted.py

Amazing, thank you!

authors: charliermarsh tjkuson


text:
Cannot rye sync with pypi

Steps to Reproduce
rye pin cpython@3.12
rye sync
rye pin pypy@3.10.13
rye sync

Expected Result
Sync to succeed.
Actual Result
Python version mismatch (found pypy@3.9.18, expected pypy@3.10.13), recreating.
Downloading pypy@3.10.13
Checking checksum
Unpacking
Downloaded pypy@3.10.13
Initializing new virtualenv in /home/zsmith/projects/janeiro/.venv
Python version: pypy@3.10.13
Generating production lockfile: /home/zsmith/projects/janeiro/requirements.lock
error: Failed to build editables
  Caused by: Failed to build editable: file:///home/zsmith/projects/janeiro
  Caused by: Build backend failed to determine extra requires with `build_editable()`:
--- stdout:

--- stderr:
Traceback (most recent call last):
  File "<string>", line 8, in <module>
ModuleNotFoundError: No module named 'hatchling'
---
error: could not write production lockfile for project

Caused by:
    failed to generate lockfile

Version Info
rye --version
rye 0.27.0
commit: 0.27.0 (43ee4fce0 2024-02-26)
platform: linux (x86_64)
self-python: cpython@3.12
symlink support: true
uv enabled: true

Stacktrace
No response

Can you share the contents of your pyproject.toml?

authors: mitsuhiko zacharyasmith

repo: astral-sh/rye


text:
uv toolchain uninstall repeats "No installations" message

Can we omit this in most cases? All cases?
❯ cargo run -- python uninstall 3.12
   Compiling uv v0.2.21 (/Users/crmarsh/workspace/uv/crates/uv)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 4.20s
     Running `target/debug/uv python uninstall 3.12`
warning: `uv python uninstall` is experimental and may change without warning.
Looking for Python installations matching Python 3.12 (any-3.12-any-any-any)
No installations found matching Python 3.12
No installations found matching the request

It's a little more sane with a couple requests:
❯ cargo run -q -- python uninstall 3.11 3.12
warning: `uv python uninstall` is experimental and may change without warning.
Looking for Python installations matching Python 3.11 (any-3.11-any-any-any)
No installations found matching Python 3.11
Looking for Python installations matching Python 3.12 (any-3.12-any-any-any)
No installations found matching Python 3.12
No installations found matching the requests

It seems like we could adjust it when there's one or make some tracing output?

Yeah agreed.

authors: charliermarsh zanieb

repo: astral-sh/uv


text:
--exact has no effect when used with --no-build-isolation in uv sync

uv sync --no-build-isolation is always inexact. Adding --exact has no effect.
Related: https://github.com/astral-sh/uv/issues/6580
➜ uv --version
uv 0.3.3 (Homebrew 2024-08-23)

➜ uv pip install ruff
Resolved 1 package in 81ms
Installed 1 package in 2ms
 + ruff==0.6.2

➜ uv sync --no-build-isolation
Resolved 1 package in 1ms
Audited 1 package in 0.07ms

➜ uv sync --no-build-isolation --exact
Resolved 1 package in 0.53ms
Audited 1 package in 0.04ms

➜ uv sync
Resolved 1 package in 0.50ms
Uninstalled 1 package in 0.67ms
 - ruff==0.6.2

Thanks, this seems like a bug.

authors: charliermarsh kabouzeid


text:
Consolidate concurrency limits

Summary
This PR consolidates the concurrency limits used throughout uv and exposes two limits, UV_CONCURRENT_DOWNLOADS and UV_CONCURRENT_BUILDS, as environment variables.
Currently, uv has a number of concurrent streams that it buffers using relatively arbitrary limits for backpressure. However, many of these limits are conflated. We run a relatively small number of tasks overall and should start most things as soon as possible. What we really want to limit are three separate operations:

File I/O. This is managed by tokio's blocking pool and we should not really have to worry about it.
Network I/O.
Python build processes.

Because the current limits span a broad range of tasks, it's possible that a limit meant for network I/O is occupied by tasks performing builds, reading from the file system, or even waiting on a OnceMap. We also don't limit build processes that end up being required to perform a download. While this may not pose a performance problem because our limits are relatively high, it does mean that the limits do not do what we want, making it tricky to expose them to users (https://github.com/astral-sh/uv/issues/1205, https://github.com/astral-sh/uv/issues/3311).
After this change, the limits on network I/O and build processes are centralized and managed by semaphores. All other tasks are unbuffered (note that these tasks are still bounded, so backpressure should not be a problem).

The terminology here is a little weird. From https://github.com/astral-sh/uv/issues/3311, what we want is to expose a way to limit the overall concurrency of downloads. However, for builds, we're really only limiting the number of parallel python processes we spawn. Technically those two are different, but I think sticking to one of concurrency vs. parallelism would be less confusing. Maybe these should be UV_PARALLEL_* instead?
Test Plan

There is one seemingly important limit left in https://github.com/astral-sh/uv/blob/main/crates/uv-resolver/src/resolver/mod.rs#L323, from https://github.com/astral-sh/uv/pull/1163. In practice this bound is quite large compared to our concurrent downloads and should not be a source of contention, it's mainly there to allow us to use a bounded channel and avoid starving the prefetcher.

Regarding parallel vs concurrent: I don't think that's important as a user-facing detail. "CONCURRENT" is fine.

I agree, I was just wondering which one would be more intuitive, regardless of which is technically correct.

👍 I think people have a broader understanding of "concurrency limits" than parallelism.

I've gotten comfortable just using the word "concurrency" because of this: https://doc.rust-lang.org/book/ch16-00-concurrency.html

I have a minor preference for our own setting over a RAYON variable if it's easy.

LGTM! There's maybe one other thing we care about here: the number of concurrent installs (which, today, is controllable by RAYON_NUM_THREADS). Once we've downloaded and built all the wheels, we then have to install them into the virtual environment, and we do this with Rayon. I think it's fine not to add a setting for that, but we could.

We almost might want a way to limit the size of tokio's blocking threadpool for fs operations (https://github.com/astral-sh/uv/issues/3311). Ideally those options could be combined. Installs are fs bound so maybe we should just use tokio's blocking pool instead of rayon for that as well?
Either way I think I'll keep this PR limited to network and build limits.

authors: charliermarsh ibraheemdev zanieb


text:
How does this interact with Astro 2.5's compressHTML config option?

Is HTML compression duplicative with the new Astro config option?

Anyway, it does not interact since astro-compress is a post build hook and won't break anything.

authors: NikolaRHristov maxcountryman

repo: astro-community/astro-compress


text:
Implement a stdout and ASCII logging in mmirs_qrp

Currently mmirs_qrp uses a astropy logging function. Need to switch to Python standard logging for both stdout and ASCII file loggin.

Implemented in 0281c7e with some code simplfication in b181a7d and fc2da87

repo: astrochun/MMTtools


text:
snowflake not included in the extras_require of amazon extra

Describe the bug
The RedshiftDataOperatorAsync utilizes the RedshiftDataHook, which has a dependency on the snowflake python package. This is not included in the extras_require of the amazon extra. This results in an import failure.
To Reproduce

Install astronomer-providers==1.17.1
Include the amazon extra.
Import RedshiftDataOperatorAsync:

>>> from astronomer.providers.amazon.aws.operators.redshift_data import RedshiftDataOperatorAsync
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.10/site-packages/astronomer/providers/amazon/aws/operators/redshift_data.py", line 6, in <module>
    from astronomer.providers.amazon.aws.hooks.redshift_data import RedshiftDataHook
  File "/usr/local/lib/python3.10/site-packages/astronomer/providers/amazon/aws/hooks/redshift_data.py", line 12, in <module>
    from snowflake.connector.util_text import split_statements
ModuleNotFoundError: No module named 'snowflake'
>>>

Instead of adding the extra, I worked on removing the snowflake dependency as suggested in Slack thread https://astronomer.slack.com/archives/C0387PMM2E7/p1690293653544339?thread_ts=1690244271.090079&cid=C0387PMM2E7
Have created a PR for the same #1260

authors: ReadytoRocc pankajkoti

repo: astronomer/astronomer-providers


text:
Refactoring catalog.py file

Raise errors instead of sys.exit
Change assert to raise errors for input validation
Add some comments and format docstrings
black formatting

I know there are some changes being worked on for the repo, and if you don't want to worry about merging a bunch of refactoring changes you can merge those first and I can rebase this branch.

Closing pull request. Please re-open if you'd still like to merge these changes.

authors: delucchi-cmu smcguire-cmu


text:
Regions describing masks

It will sometimes be useful to represent pixel masks as regions.  This should probably be implemented as a mask-to-polygon function with options for accuracy / contour smoothness.  The most expensive polygon would have 2-3 points per pixel covering each corner, which is still cheap enough to be useful in some cases.

Optionally we could literally have a mask-backed region separate from polygon, since a lot of the functionality can be implemented directly from the mask (area, __contains__, etc.)

Also, if your region has holes in it then a polygon won't do the trick

authors: astrofrog keflavich

repo: astropy/regions


text:
Change interfaces & unions to require enums

@sunli829 this is my first time working on a macro, so it might be bad.
I have found it weird that the #[async_graphql::Interface] macro replaces a struct definition with a enum definition. You can see me trying to extend an interface with diesel traits in https://github.com/phated/twentyfive-stars/blob/master/server/src/data/character_mode.rs - and you can see the "weird" behavior at https://github.com/phated/twentyfive-stars/blob/master/server/src/data/character_mode.rs#L116
By making this macro only usable on enums, we have a more natural usage pattern when extending it.

Why not call into directly?
UpgradeMode {
          id,
          title,
          stars,
          type_,
          faction,
          traits,
          attack_modifier,
          defense_modifier,
        }.into()

For the creation, .into() would work, but I am working on a new feature where I need to pattern match on the enum variants.
If you agree to this implementation, I will update the documentation and also make changes to Union. Please let me know

This adds some extra verbosity in the definition, but I believe it makes the code easier to understand when you need to use the data types in other parts of the server.

Someone really asked me why Interface would be a struct, and I told him it was actually an enumeration. In fact, when I first implemented the Interface, it was an enumeration, but I was lazy. I did n’t like to write any extra code. The enumeration forced me to make a repeated name, like this enum MyInterface {Foo (Foo)} , so changed to struct. But it does make the code difficult to understand. Thanks for your PR, I will merge later, because I need to change the Union to use enumeration.

Great! I will work on Union now!

Although you have a lot of open source responsibilities, I still want to add you to the collaborators, because your suggestions are very important to this project, are you willing? 😁

are you willing?

Yeah, I am happy to help where I can. Thank you! 🙇 I "watch" this project already, so I see all of the activity 😄

Great, let's do the best GraphQL library of rust together. 😄

@sunli829 the Union is implemented. I also added some tests and documentation for it. In addition, I updated the book examples.
Do you need me to update the examples or anything else?

Too fast, the code generation part I wrote is not very good, a little messy.😂
I will translate the book to Chinese, if you want, you can help update the Examples repo.

Too fast, the code generation part I wrote is not very good, a little messy.😂

@sunli829 do you need me to change something? Or are you going to improve on this?

I will translate the book to Chinese, if you want, you can help update the Examples repo.

The book doesn't mention struct, so I changed the example. I don't think anything else needs to be done.
I will work on the examples repo when we finish this. Probably tomorrow because it is late for me.
Thank you!

do you need me to change something? Or are you going to improve on this?
Now it seems unnecessary, after all, the amount of code is not too large. 😁

I will work on the examples repo when we finish this. Probably tomorrow because it is late for me.
Thanks, take a break early, good night. 😁

I will update the examples repo after the new version is released. This version changes a lot. 😁

repo: async-graphql/async-graphql


text:
fix: modelina supporting asyncapi v3

Description
Removing the check for spec v3 as now modelina support AsyncAPI spec v3.
Related issue(s)

See also https://github.com/asyncapi/cli/pull/1376

@Souvikns could you push a empty commit. The sonarcloud analysis seems to be stuck.

Sonarcloud is still not working @Shurtu-gal

@Shurtu-gal I have no idea. My fix is go to Sonarcloud, remove project, add project and works  Then again it fails. I suggest you folks to make it a non-mandatory check, so a check that even if fails, you may merge.
we need to work on https://github.com/asyncapi/.github/issues/306
but also in this issue you will see a hint from Sergio, that it might be just because of some silly change sonar did on their side with check name

/rtm

Can this be removed in generate fromTemplate as well?

authors: Shurtu-gal Souvikns adammfrank derberg

repo: asyncapi/cli


text:
feat: improve the log and correct the path name using optimise command

Correct the log command and name file after executing the optimise command,

Related issue(s)
Fixes https://github.com/asyncapi/cli/issues/764

/rtm

@allcontributors please add @AayushSaini101  for code


text:
No license = not possible to legally use

This project has no code license attached.  This means that (in many countries) it defaults to "all rights reserved" implied copyright.  This means it's technically copyright infringement to use this code.
I would suggest the MIT license, as it allows for anyone to use your code for anything they want, as long as they give you credit for it and include a copy of the MIT license.

added the MIT license 🙂

That was insanely fast!

authors: atarw skylarmt

repo: atarw/material-ui-swing


text:
🛑 Wedding HTTPS is down

In 233c29a, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in d8f3abf.

repo: atatkin/milos-uptime


text:
🛑 Wedding HTTPS is down

In 79f6b62, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in d83d8ba.


text:
🛑 Wedding HTTPS is down

In 5df8067, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 55e975e.


text:
🛑 Wedding HTTPS is down

In 7d8cc97, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in b7f4799.


text:
🛑 Wedding HTTPS is down

In d49c223, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 7f38bf5.


text:
Development mode still sending messages

Hello,
I just tried to put my mail server in "development mode" to see what would happen. Outgoing messages are held correctly, but incoming messages are still forwarded to my Address Endpoint. I was under the impression that they would be held as well?

When in Development mode, outgoing & incoming mail will be held and only visible in the web interface and will not be sent to any recipients or HTTP endpoints.

This is a documentation bug. In development mode, it should only stop outgoing messages. Incoming messages should be handled as normal.

Actually, it seems like holding incoming messages in development would be the best solution. Outgoing messages can be held in live services using credentials.
Fixed in 5e13d7d0526d7bbd078ce244cbd81709f9246965

authors: RLejolivet adamcooke

repo: atech/postal


text:
parent node居然是child node的child node, 我是哪里用的不对吗？

CASE_TEST(atbus_endpoint, is_child1)
{
atbus::node::conf_t p_conf;
atbus::node::default_conf(&p_conf);
p_conf.children_mask = 16;
atbus::node::conf_t c_conf;
atbus::node::default_conf(&c_conf);
c_conf.children_mask = 8;
{
    atbus::node::ptr_t p_node = atbus::node::create();
    p_node->init(0x12345678, &p_conf);

    atbus::node::ptr_t c_node = atbus::node::create();
    c_node->init(0x12345679, &c_conf);

    CASE_EXPECT_TRUE(p_node->is_child_node(c_node->get_id()));

    CASE_EXPECT_FALSE(c_node->is_child_node(p_node->get_id()));
}

}

@weinvest 这个会注册失败的，因为两个的 children_mask 。这个配置两个节点的子节点范围是 0x12345678/16 和 0x12345679/16 ，都是 0x12340000-0x1234FFFF 。互相注册会失败，会有失败回调。
如果需要点对点通信，可以把 children_mask 设成0，如果需要当作proxy使用，至少要 0x12345678/16 和 0x12355678/16 或者把16改小点。 这里16指ID的后16位

谢谢，明白了，我刚开始学习你的这个库，写的很不错呀。

parent node去连接child node原生是没有的。其实当时写parent和child是为了连接分组。实际业务里都不需要多层的，这里只是顺便实现成了支持多层，算是一种过度设计。
但是你可以parent层监听断开事件，自己去定期主动连接child

CASE_TEST(atbus_endpoint, is_child) {
  atbus::node::conf_t conf;
  atbus::node::default_conf(&conf);

  {
    conf.subnets.push_back(atbus::endpoint_subnet_conf(0, 16));
    conf.subnets.push_back(atbus::endpoint_subnet_conf(0x22345678, 16));

    atbus::node::ptr_t node = atbus::node::create();
    node->init(0x12345678, &conf);

    // 0值边界检测
    CASE_EXPECT_TRUE(node->is_child_node(0x12340000));
    CASE_EXPECT_TRUE(node->is_child_node(0x1234FFFF));
    CASE_EXPECT_FALSE(node->is_child_node(0x1233FFFF));
    CASE_EXPECT_FALSE(node->is_child_node(0x12350000));

    CASE_EXPECT_TRUE(node->is_child_node(0x22340000));
    CASE_EXPECT_TRUE(node->is_child_node(0x2234FFFF));
    CASE_EXPECT_FALSE(node->is_child_node(0x2233FFFF));
    CASE_EXPECT_FALSE(node->is_child_node(0x22350000));

    //测试子节点的父节点
    atbus::node::conf_t sub_conf;
    atbus::node::default_conf(&sub_conf);
    atbus::node::ptr_t sub_node = atbus::node::create();
    sub_node->init(0x12340000, &sub_conf);
    CASE_EXPECT_TRUE(sub_node->is_parent_node(0x12345678));

    // 自己是自己的子节点
    CASE_EXPECT_TRUE(node->is_child_node(node->get_id()));

    // 0值边界检测 - 静态接口
    CASE_EXPECT_TRUE(atbus::endpoint::is_child_node(0x12345678, 0x12345678, 16, 0x12340000));
    CASE_EXPECT_TRUE(atbus::endpoint::is_child_node(0x12345678, 0x12345678, 16, 0x1234FFFF));
    CASE_EXPECT_FALSE(atbus::endpoint::is_child_node(0x12345678, 0x12345678, 16, 0x1233FFFF));
    CASE_EXPECT_FALSE(atbus::endpoint::is_child_node(0x12345678, 0x12345678, 16, 0x12350000));

    // 自己是自己的子节点 - 静态接口
    CASE_EXPECT_FALSE(atbus::endpoint::is_child_node(0x12345678, 0x12345678, 16, 0x12345678));
  }

你好，我在你的测试用例里面加了一段代码，测试子节点的父节点，为什么判断子节点成功，翻过来子节点判断父节点却不对，想了解一下父节点的信息想怎样维护的

atbus::node 要完成通信注册，才能确认父节点。
详见: atbus_node_reg_test.cpp 的 928 行

有点明白了，所以atsf4g-co里面的gateway就是用来管理父子节点注册的是吧

对的，atproxy主要目的是用于转发消息的，收敛连接用。会用到父子节点的注册的特性。

authors: jswlives owent owt5008137 weinvest

repo: atframework/libatbus


text:
Prepare for new release of Bitbucket

Workflow links: https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/1077311684, https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/1077312379.

Integration test passed successfully, so I mark current version Bitbucket Server for Slack 3.0.4 as compatible with recent Bitbucket 7.15.0.


text:
Fix crowd fluentd config

local-home isn't mounted to fluentd sidecar
extraVolumes was sitting under elasticsearch stanza and wasn't actually used in fluentd container
replace default fluentd config to tail logs rather than to start as a server (yet, it's still recommended to write own fluentd config that fits the particular use case and infra)

Checklist

[x] I have added unit tests
[x] I have applied the change to all applicable products
[ ] The E2E test has passed (use e2e label)

How was it working before?

repo: atlassian/data-center-helm-charts


text:
Introduces sparse internal metrics

These are gauges which are only sent when the value changes. They're sent for several flush intervals, with the expectation that they are attached to error counters, so may need to survive a bursty failures.
Overall this will reduce the amount of data sent in the happy path when deployed in a forwarder configuration (2 metrics per host).

Looking at it again, I realize it's not as good as it sounds - the sparse backend metric will only be on the aggregation server, not the forwarder.  But still, it's something.  I've spoken to @MovieStoreGuy a bit about updating http.forwarder.*, but they're counters, so it's likely to break dashboards if they're changed to sparse gauges.

repo: atlassian/gostatsd


text:
Почистить все пакеты и тэги

Какого рода задача?
Наводим порядок
Что и где будем менять?
Тэги и пакеты
Укажите референс
Приводим репу к релизному виду. Снести нужно все пакеты и тэги кроме рабочих v1, v2

На будущее для тегов:
git tag -l | grep -wv 'v1' | grep -wv 'v2' | xargs -L1 git push --delete origin $1

repo: atls/uikit


text:
Atom.Object.defineProperty.get is deprecated.

atom.services is no longer available. To register service providers and
consumers, use the providedServices and consumedServices fields in
your package's package.json.
Atom.Object.defineProperty.get (C:\Users\Felipe\AppData\Local\atom\app-0.177.0\resources\app\src\atom.js:64:11)
Object.activate (C:\Users\Felipe\.atom\packages\autocomplete-snippets\lib\autocomplete-snippets.coffee:8:25)

Please check the repo before opening issues. Duplicate of #33.

authors: joefitzgerald majordookie

repo: atom-community/autocomplete-snippets


text:
Slow response of script/build when --help toggles

Prerequisites

[X] Can you reproduce the problem in safe mode?
[X] Are you running the latest version of Atom?
[X] Did you check the debugging guide?
[X] Did you check the FAQs on Discuss?
[X] Are you reporting to the correct repository?
[X] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.
Description
$ script/build --help

lags since we need toggle --help to see available options for manually building different packages (windows-installer, *.deb, *.rpm).
Plus, some may try script/build -h for help but it is not available.
Steps to Reproduce

clone atom then checkout to release branches
$ script/build --help

Expected behavior:
It prints out available options immediately then return.
Actual behavior:
It's lagging on terminal result: Installing script dependencies and finally prints out available options.
It looks like processing on this line of code (script/build, line 7):
require('./bootstrap')

Versions
$ atom --version
Atom    : 1.11.1
Electron: 0.37.8
Chrome  : 49.0.2623.75
Node    : 5.10.0

$ atom-beta --version
Atom    : 1.12.0-beta1
Electron: 1.3.6
Chrome  : 52.0.2743.82
Node    : 6.3.0

Here is the excerpt from my response to issue #13232.
Looking at the code, the usage section should just be moved to the top before requiring bootstrap, shouldn’t it?
const yargs = require('yargs')
const argv = yargs
  .usage('Usage: $0 [options]')
  .help('help')
  .describe('code-sign',  'Code-sign executables (macOS and Windows only)')
  .describe('create-windows-installer', 'Create installer (Windows only)')
  .describe('create-debian-package', 'Create .deb package (Linux only)')
  .describe('create-rpm-package', 'Create .rpm package (Linux only)')
  .describe('compress-artifacts', 'Compress Atom binaries (and symbols on macOS)')
  .describe('install', 'Install Atom')
  .wrap(yargs.terminalWidth())
  .argv

@paulmenzel thanks for the comment.
I tried what you said in #12979 and found that

but require('yargs') won't work since bootstrap installs the yargs dep

authors: liuderchi paulmenzel

repo: atom/atom


text:
Soft wrap settings reset when saving new file

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
If soft wrap is enabled on a new, unsaved file and you save that file, then soft wrap is disabled on that file.
Steps to Reproduce

Open a new, untitled window.
Put in enough text so as to require horizontal scrolling, and enable the soft wrapping under "View" -> "Toggle Soft Wrap"
Save the file

Expected behavior:
I expect the file to save and retain the soft wrap settings.
Actual behavior:
The file saves but soft wrap is reset, and you get a single long line of text.
Reproduces how often:
100% reproducible. Only happens when saving a new file - if you enable soft wrap again, make some changes in the file and save it again, then the soft wrap settings are retained.
Versions
Atom:
Atom    : 1.14.2
Electron: 1.3.13
Chrome  : 52.0.2743.82
Node    : 6.5.0

Apm:
apm  1.15.3
npm  3.10.5
node 4.4.5 x64
python 2.7.13
git 2.11.1

OS: OSX Sierra 10.12.3
$ uname -mprsv
Darwin 16.4.0 Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21 PST 2016; root:xnu-3789.41.3~3/RELEASE_X86_64 x86_64 i386

I can't reproduce this using Atom 1.16.0-dev-4422354, Windows 10 x64.
/cc @ungb

I tried this on atom 1.14.4, I didn't see this behavior either, that's really strange since softswrap is a setting in config.cson.

Still getting the same behavior in 1.14.4 - here's my repro:

I put in enough horizontal text to require scrolling again, then enabled soft wrapping.
Then I set a conditional breakpoint on this line:
https://github.com/atom/atom/blob/4a165e239388058bf9c77cfb432dd734211a7997/src/text-editor.coffee#L225
with the condition:
params['softWrapped'] === false
Then I saved the file and the breakpoint triggered - here's the resulting callstack and local variables:

If I go up one stack frame to text-editor-registry.js:327, it seems that textEditorParamsForScope is returning params with softWrapped: false, and going to the definition of that function, it seems that this.config.get('softWrapped', configOptions) on this line:
https://github.com/atom/atom/blob/4a165e239388058bf9c77cfb432dd734211a7997/src/text-editor-registry.js#L366
is returning false even though I have enabled soft wrap from the menu.

I am able to repro this on latest on master.
The following repro steps is what I followed(similar to what you provided)

Open a untitled window on atom
Paste in the text:

This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test This is a test

in Context menu, go to view -> Toggle Soft Wrap
Save the file as softwarpTest.txt

Noticed that softwrap is gone.  Weird thing is if you save it without the .txt the softwrap persist.

This issue actually did get fixed earlier this year (Jan 12) but I forgot to close it!

authors: 50Wliu arkadiyt daviwil ungb


text:
The Editor has crashed

Keep getting error message: The Editor has crashed

I'm seeing this as well with the Nightly release on my Mac. Is there some way to provide a crash log?

I’m not on it daily, but I’ll be sure to report it again if it happens. Thanks.
Sent from my iPhone

On Apr 30, 2020, at 12:16, Stefan Wrobel notifications@github.com wrote:

I'm seeing this as well with the Nightly release on my Mac. Is there some way to provide a crash log?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ditto, just upgraded some packages and I am getting this message every time I start Atom.

Atom has started crashing with a new Vue.js project I created today. It was OK with the initial state of the project, but after first build, the crashes appeared and so far I was unable to find out what's wrong. Atom is still OK with the previous projects and is able to open them.
Here's the crash report from Atom:

Here's the Vue.js project folder content (if it's of any help):

Here's list of Atom community packages in use:

===
Latest finding: if I disable all of the community packages, Atom will load the problematic Vue.js project with no crash! It seems that some of the package may be the culprit. Will continue investigating...

OK, that was quick... This community package caused the crash with Vue.js project:

When disabled, Atom loads the project/starts with no problem.
Hope it helps...

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way 😀

Thanks @lojza3d, since the problem appears to be a community package conflict, I will go ahead and close this one.
If you are still seeing this issue, please submit a new issue following the issue template.

Hello I have the same problem but every time I start it I get an error I have the latest version is just installed


text:
Atom is installed but not launching !!! I mean it's not starting but has shown up in the task manager !??!! Strnge

Prerequisites

[ ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Steps to Reproduce

 Tried to run as administrator (on windows) !!

 Hunted the installed location and then ran it , but invain

 Also reinstalled freshly and restarted the system !!

Expected behavior: Start normally

Actual behavior: Not even starting , but there is an entry in task manager !!

Reproduces how often: Everytime !!

Versions

Additional Information

My current atom ver 1.48

It seems that atom has ran into background process rather than ... being able to run directly !! I'm just not getting it to run on my system and even during the installation splash screen , after it installs it just vanishes away and nothing much !! In the task magaer it says updating rather than installing , why ??

My tip would be to compile atom from source if it's "updating".
https://flight-manual.atom.io/hacking-atom/sections/hacking-on-atom-core/#platform-windows

Have you plugged your laptop into an external display recently? I see this kind of effect when I do that (on Windows)

authors: WindowsExperiments2020 arixank eelstork


text:
getCurrentWordBufferRange doesn't seem to work correctly for words like change-case

I'm trying to get the current word under the cursor and the default options of getCurrentWordBufferRange should AFAIK enable matching words with non-space separators, but currently the regex seems to have been misconfigured so that it doesn't match word correctly.
Current code:
wordRegExp: ({includeNonWordCharacters}={}) ->
includeNonWordCharacters ?= true
nonWordCharacters = atom.config.get('editor.nonWordCharacters')
segments = ["^[\t ]*$"]
segments.push("[^\\s#{_.escapeRegExp(nonWordCharacters)}]+")
if includeNonWordCharacters
  segments.push("[#{_.escapeRegExp(nonWordCharacters)}]+")
new RegExp(segments.join("|"), "g")

Correct code:
wordRegExp: ({includeNonWordCharacters}={}) ->
includeNonWordCharacters ?= true
nonWordCharacters = atom.config.get('editor.nonWordCharacters')
segments = ["^[\t ]*$"]
if includeNonWordCharacters
  segments.push("[#{_.escapeRegExp(nonWordCharacters)}]+")
  segments.push("[^\\s]+")
else
  segments.push("[^\\s#{_.escapeRegExp(nonWordCharacters)}]+")
new RegExp(segments.join("|"), "g")

@deiga Can you share an example which demonstrates the problem and explain why you expected different behavior? Does using a different editor.nonWordCharacters help you get the behavior you expected?

I'm unable to reproduce. For the string foo-bar-baz and the cursor positioned like this foo-b|ar-baz, the result of calling getWordUnderCursor() is bar which is expected given the default config setting for non word characters which includes -. If I change that config setting so that it doesn't include -, getWordUnderCursor() returns foo-bar-baz, which is again expected. If you can still reproduce this problem -- please provide a full example.

Re-opening this since another issue I was just looking at helped me understand and reproduce the problem: https://github.com/atom/atom/issues/6538#issuecomment-140348629.

authors: deiga izuzak


text:
Atom freezes when clicking "view on atom.io"

Atom 0.190.0
Linux.
This happens both in normal, safe and --one mode; it seems to happen only when the browser (I use firefox) is not open yet.
Steps to reproduce: packages > [a package] > settings > view on atom; or release notes > view on atom. If the browser was already open, everything works fine; otherwise, the browser opens but Atom freezes and must be killed from task manager.

I noticed just now that the exact same thing also happens when clicking on the name of  a package to go to its home page on atom.io

I can reproduce this was well.

This might be a Electron issue as it has been happening to me in Slack as well. On Windows.

I have a similar issue and partial solution.
My problem occurs when I have the x-scheme-handler/https mime type set to chromium.desktop in ~/.local/share/applications/mimeapps.list. If I change it to firefox.desktop it opens in Firefox even if the browser is not open.
If I remove the mime-type altogether it opens midori, probably because it's the last browser I installed but I'm not too sure about that.
The real issue is that the editor blocks while I have the page open, eventually showing the dialog:
"Editor is not responding.
The editor is not responding. Would you like to force close it or just keep waiting?"
If I click "Keep waiting" with the browser open it stays blocked and then shows the same dialog.
If I close the browser and then click "Keep waiting" the editor returns to normal.

Reproduced with atom-editor-bin@1.2.0-1 from AUR, arch linux, using Firefox
Seems that Firefox does not return (or block) whenever a link is opened.
Try to use Firefox to open a link in terminal. Firefox does not give the shell back for us to use.
However, using chromium/chrome, we can use the shell after a page is opened.
This might be (in fact, I am quite sure) the cause of this issue. We need to async Firefox to fix this.

i have the same problem, but using chrome.
its my default browser, using launchy or xdg-open confirms.
Distribution: Archlinux
WindowManager: I3
$ google-chrome-stable --version
=> Google Chrome 44.0.2403.157
$ uname -r
=> 4.3.3-2-ARCH

happens also when my browser is opened.

Same problem: Ubuntu, Firefox, Atom 1.6.1.
@Holi0317's analysis looks sound:
If Firefox is launched with an existing browser window open, it returns immediately.
If Firefox is launched with no existing browser window open, it waits for Firefox to exit before returning.
This happens whenever the browser is launched from Atom. Help->Documentation causes the same issue.
For example, in atom/src/browser/atom-application.coffee:
 @on 'application:open-documentation', -> shell.openExternal('https://atom.io/docs/latest/?app')

I guess this is assuming that openExternal will return immediately, which doesn't happen if a Firefox window is not already open.
@benogle: are you awaiting any further reproductions?

Thanks for @sneakypete81 for pointing out the location. I have just dug into the electron code and find out the issue.
https://github.com/electron/electron/blob/v0.37.4/atom/common/platform_util_linux.cc#L34
I think that is the cause of this issue. As electron.shell.openExternal tries to get the exit code and return. This blocks the call until process is finished and freeze atom.

I've had a try at a fix, but Ican't work out how to use a custom build of Electron when building Atom. Any help with this would be appreciated.

Re-opening until Atom updates to a version of Electron that contains the linked fix.


text:
Regression: softWrapAtPreferredLineLength is ignored in 0.192

I normally want to see files soft-wrapped to the width of the window. In 0.188, I was able to set softWrap: true and it would do this. In 0.192, however, it soft-wraps to preferred line length, even if I explicitly set softWrapAtPreferredLineLength: false. I think this is a regression...or should I be doing something different?
(I'm using Mac OS X 10.10, if that makes any difference.)

Closing. After restarting the application, it worked. I'm not sure why I needed to restart, though.


text:
Need a way to show all keymap bindings and modify it.

At the current time, there is no way to looking kyemap things.

Go to Settings > Keybindings to show a list of all keybindings, there's also a filter function.
You can also modify/overwrite one by adding it to your keymap file

authors: arcticicestudio lygstate


text:
Serialize settings as JSON when sending them to the main process

Fixes #16789
Config settings of type Color should be written to the config file as a string like #af01cd. To achieve this, the class overrides toJSON .
When I refactored the config system to IPC settings to the main process for writing, this behavior was inadvertently broken because sending a value over electron's IPC does not serialize it as JSON; it uses its own serialization mechanism that does not preserve objects' toJSON methods.

Thanks! I dug far enough to figure out why it was breaking, but not where 😆.

@Arcanemagus Yeah, thanks so much for the info in your report. That made it very easy to fix!

authors: Arcanemagus maxbrunsfeld


text:
Fix for Issue #8794 Remove 'null' text from front-facing messages

Remove 'null' from alert messages if the item that is being printed is 'null'
This is the original message when the element is 'null':

This is the message now:

Hi! This does not belongs to the atom repository. open-on-github is a seperate package, that's why it was in node_modules...
Open on Github: https://github.com/atom/open-on-github/
The file: https://github.com/atom/open-on-github/blob/master/lib/github-file.coffee

Like @philipgiuliani mentioned, this PR should be made to the open-on-github repository, not here.


text:
fix typo

Broswer -> Browser

Thanks for fixing this :+1: :memo:

authors: ShiningRay kevinsawicki

repo: atom/electron


text:
webContents: provide responses for executeJavscript method

Fixes #4511

Wrong result will be returned when executeJavaScript is called for two webContents at the same time.

Fixed, thanks!

have addressed the comments, thanks!

The executeJavaScript test failed.
not ok 343 <webview> tag executeJavaScript should support user gesture
  TypeError: Cannot read property 'webkitRequestFullscreen' of null
      at <anonymous>:1:32
      at webview.listener2 (/Users/travis/build/atom/electron/spec/webview-spec.js:562:17)
      at WebViewImpl.dispatchEvent (/Users/travis/build/atom/electron/out/D/Electron.app/Contents/Resources/atom.asar/renderer/lib/web-view/web-view.js:188:29)
      at dispatchEvent (/Users/travis/build/atom/electron/out/D/Electron.app/Contents/Resources/atom.asar/renderer/lib/web-view/guest-view-internal.js:56:11)
      at EventEmitter.<anonymous> (/Users/travis/build/atom/electron/out/D/Electron.app/Contents/Resources/atom.asar/renderer/lib/web-view/guest-view-internal.js:67:28)
      at emitTwo (events.js:87:13)
      at EventEmitter.emit (events.js:172:7)

The executeJavaScript test failed.

webview.executeJavaScript was running in the embedders' context, have fixed it, but Is there a better way to acheive this for webview, right now webframe is initialised in the context in which it is required making it difficult to invoke directly from web-view.js.

:+1:

Hello.
The following script should work?
browser.execute JavaScript ('console.log ("hello world")', function () {console.log ('finish')})
I'm trying to run the callback but I can not, updated to the 0.36.9 release and has not worked.
Thank you.

Same here on 0.37.2. Javascript executes in the webContents but the callback is not fired.

@john-griffin can you open an issue with a reproducible example ?

@deepak1556 just wanted to let you know this pull is the most amazing thing I've seen all day.
I'm completely new to electron and spent the last 4+ hours stumbling through documentation and forum posts trying to figure out how to pass data between an electron renderer and a  before I found this and realized executeJavascript held the solution all along!

@TeamworkGuy2, Electron has built in IPC which can also be used for communicating between the main process and renderer process. I have also used Socket.IO with great success for doing the same thing. I'd venture to say there are other methods out there as well. Glad you found a solution that works for you. Cheers!

Thanks for the direction @frankhale!  I had looked into IPC, but I'm using devtool which runs in a renderer thread so I don't have access to ipcMain (the IPC documentation seems to indicate that you can only use IPC between a renderer and the main thread, not between two renderers or a renderer and a webview).
I'm loading 3rd party sites into a <webview> and require("electron") doesn't seem to work in webviews (maybe I'm missing something here) so no IPC and I'm guessing I'd have trouble getting Socket.IO running via an executeJavascript() injected code snippet.
I'll definitely look into IPC if I work with electron in the future.

authors: AllanVieira TeamworkGuy2 deepak1556 frankhale john-griffin zcbenz


text:
🛑 atraeclick is down

In 2f0bc7c, atraeclick (https://atraeclick.com) was down:

HTTP code: 403
Response time: 124 ms

Resolved: atraeclick is back up in 53fe6f6.

repo: atraeclick/status


text:
Add missing ADC pins for ATSAMD11D

Summary
The ATSAMD11D has 20 or 24 pins. Some of them are also ADC pins, however the traits were not implemented for them.
Checklist

[x] CHANGELOG.md for the BSP or HAL updated
[x] All new or modified code is well documented, especially public items
[x] No new warnings or clippy suggestions have been introduced (see CI or check locally)

@Tremoneck Just took a quick look at the datasheet. Unless I'm missing something, the pin multiplexing table calls out for PA02, PA03, PA04, PA05, PA06, PA07, PA10, PA11, PA14 and PA15 as ADC pins?

@jbeaurivage Sorry for the delay.
While they are ADC pins, they are also available with the C variant. the Traits for these pins is implemented when the feature samd11 is available. That part is right above the code added in this PR.

Right, I should've looked closed. My mistake! Looks good then.

authors: Tremoneck jbeaurivage

repo: atsamd-rs/atsamd


text:
Fix for flutter installed via brew

- What I did
Changed the method of getting the pub cache path.
Solves an issue with flutter installations via brew.
- How I did it
Used the pub_cache package from pub.dev.
- How to verify it
Pull the branch
Add a temporary print(hostedPubCachePath); at pub/bin/src/file/template_manager.dart:22
flutter pub global activate -s path ./pub
flutter pub global run at_app create testing

Verify that the pub cache path got printed (should be in the first few lines printed).
- Description for the changelog
Reliability for various flutter installation methods.

@cconstab I added a unit test for the issue you are facing, if you get the chance, please run the following:
cd pub
flutter test

I'm going to close this PR and reopen. One of the key issues is that the executable cannot be activated from local path due to the dependency on flutter_tools. I think the best approach going forward is to strip that dependency.


text:
export encryption_util.dart

This is used at the ServerDemoService it the most basic example and it can be confusing for newcomers not to know from where or why this is sending a pedantic error besides if your project is running flutter analyze this will fail, you can omit this rule (not recommended) but if it needs to be used in the method encryptKeyPairs from server_demo_service.dart  it should be exported.
This is the broken pedantic rule Don't import implementation files from another package.

@Arkangel12 change you have suggested is in the trunk branch.
https://github.com/atsign-foundation/at_client_sdk/blob/trunk/at_client/lib/at_client.dart


text:
🛑 Mehbn is down

In 1848450, Mehbn (https://atugatran-mehbn.onrender.com/db-status) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mehbn is back up in ff979d9 after 11 minutes.

repo: atual-dev/upptime


text:
🛑 Mehbn is down

In 2e3c79d, Mehbn (https://atugatran-mehbn.onrender.com/db-status) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mehbn is back up in 65d7e64 after 18 minutes.


text:
No Discovery on iOS

Android build is good, no issues.
iOS build the printer discovery result is blank
Using latest Xcode 11.4 and testing on latest iOS 13.4 with Ionic 4 / Angular 8
No errors thrown.  Response to discovery is empty.
Please advise.

I'm also experiencing this issue:
Code:
printTest(name: string = 'BT:PRNT Star') {
    this.starprnt.portDiscovery('All').then((res: any) => {
      console.log(res);
      this.starprnt.connect(name, 'EscPosMobile', false).subscribe(result => {
        console.log(result);

        const printObj: PrintObj = {
          text: 'Star Clothing Boutique\n123 Star Road\nCity, State 12345\n\n',
          cutReceipt: true,
          openCashDrawer: true
        };
        /*Send null to use a printer connected via StarIOExtManager using the connect() function*/
        this.starprnt.printRawText(name, 'EscPosMobile', printObj);
      }, error => {
        console.error(error);
      });
    }).catch((error: any) => {
      console.error(error);
    });
}

Output:
To Native Cordova ->  StarPRNT portDiscovery StarPRNT641613135 ["options": [All]]
2020-04-18 15:13:37.542834-0500 App[394:21139] [CoreBluetooth] XPC connection invalid
⚡  [log] - []
To Native Cordova ->  StarPRNT connect StarPRNT641613136 ["options": [BT:PRNT Star, EscPosMobile, 0]]
⚡  [error] - Printer not connected

Hi!
I had the same problem but figured it out.
First I had to actually build and run it on an iPad (for ios) and be connected to the printer on the iPad. Then I was able to list "all" connected devices. Did not work with the emulation on the mac and the mac connected to the printer.
You have to know which Emulation  you are going to use for connecting to the printer. Look at here to find out which one.
So when connecting you need to call (my printer is a 'StarPRNT'):
starprnt.connect(portName, 'StarPRNT', false, function(err, res){
    console.log(res);
    // TODO: make a printer object and call print function
});

Hope it helps :)

Any progress here? I'm also having this issue with nothing being returned from discovery.

I found the fix for Ionic/Angular using StarPRNT plugin.   Use async function for portDiscovery.
The Ionic and Github docs say:

Got it working after finding it is permission issue where you need to put 3 permission in the info.plist nsbluetoothalwaysusagedescription
nsbluetoothperipheralusagedescription
supported external accessory protocols (jp.star-m.starpro)
You will probably see XPC connection invalid error in @jeffleeismyhero  logs without proper setup.
ps: It is always there in the logs when I run ionic cap sync . For some reason, I've been ignoring it all the time...

Hey guys. Please advice. Tried all recommendations discussed here - nothing helped. Having Star TSP100Lan connected via Ethernet Cable to router. portDiscovery('All') returns empty array

authors: datazen iborschca jeffleeismyhero laiwf94 pep108 vikre

repo: auctifera-josed/starprnt


text:
unknown model for AUDI A3

excuse for my english.
for a few months, the Sensors in my home assistant, appear with prefix "NONE" and not with Audi A3.
example:

none doors
none oil chanhe distance
etc.

After changing the name of my car using the official audi app, the name is nickname is now filled in:
{
  "data": {
    "userVehicles": [
      {
        "vin": "WAXXXXXXX",
        "mappingVin": "WAXXXXXXX",
        "vehicle": {
          "core": {
            "modelYear": 2015
          },
          "media": {
            "shortName": null,
            "longName": null
          },
          "classification": {
            "driveTrain": "PHEV"
          }
        },
        "csid": "XXXXXX",
        "commissionNumber": null,
        "type": "EXISTING",
        "devicePlatform": "MBB",
        "mbbConnect": true,
        "userRole": {
          "role": "PRIMARY_USER"
        },
        "nickname": "Audi A3"
      }
    ]
  }
}

This is several years stale. Please submit an issue if any of these issues still exist.

authors: coreywillwhat luckyhtcsensation rklomp


text:
Start developing Carmel with VS 2017

Introduction
As of 3/13/2017, the application in the dotnet folder is verified as correctly running with the Visual Studio 2017 Community edition
This document describes the details of running and further evolving this application

Maintaining all * core version numbers
Carmel uses the dotnet core / ef core / Identity core components that were released as a part of Visual Studio 2017 Community edition as shown on this screenshot:

This is the dialog where these version numbers will be managed in the future, as needed.

Creating (and recreating) the Carmel database
The database can viewed (both the schema and content) using VS 2017 SQL Server Object Explorer:

As an example - here is the content of the Components table:

Here is the summary of steps taken to create a new version of this database. In order to avoid any unneeded complications with database migrations, this process assumes that the list of components and its parts comes from this file: 'https://aurelia-ui-toolkits.github.io/aurelia-kendoui-samples/samples.json', meaning that any changes to this file before Carmel can take care of itself without this file, will have to result with the database recreation using the new version of this 'samples.json' file
Step 1
Generate new code file which needs to be used as the replacement for this section of the CatalogContextSeedData.cs. As

Developing and testing Carmel API
In order to use the current Carmel app without its user interface clock on the Properties menu item of the Carmel project

and uncheck the Launch URL box shown below

Then run the app (from Visual Studio, at this time) and use Postman to interact with the app (note that the app uses localhost:8000 port)

This specific sample was obtained running the Get command with url http://localhost:8000/api/components/
which maps to this method in the ComponentController.cs

repo: aurelia-ui-toolkits/carmel


text:
Allow a callback to be passed as a parameter to withMessage()

Is it possible to have withMessage() accept a callback that would construct the message string ? For example to have access to VM instance.
Like this:
ValidationRules
  .ensure('field')
  .satisfies(() => !this.error)
  .withMessage(() => {
    return "There is an error " + this.error.message
  )

Try using:
const error = this.controller.addError(`There is an error  ${this.error.message}`, myObject, 'myField');
... later ...
this.controller.removeError(error);

authors: jdanyow swiftanthony

repo: aurelia/validation


text:
contentvec训练对数据的要求

如果使用业务场景的数据对contentvec重新训练，对数据的有什么要求吗，如果原始数据中包含一些噪声的话会有影响吗？（使用contentvec场景中也可能会包含一定噪声）

少量噪声应该问题不大

好的，感谢，大佬

大佬，再请教个问题，如果数据规模比较大，不好单独区分每个说话人ID的话，可以训练吗

有算法可以区分不同说话人的吧，完全没有speaker id是不行的

好的， 感谢，关于生成.km label这块直接使用fairseq提供的工具就可以吗？会不会少了论文中提到的voice conversion这一步骤。

对，voice conversion也是需要的

这个是单独离线自己使用工具把原始音频进行预处理吗？

对


text:
Connecting to elasticsearch without auth

Hi,
I get this bug "'elasticBeacon' object has no attribute 'auth'" . I have seen that fixes have been made regarding connecting to es without auth credentials so I don't understand why is it now a problem?
Thank you

I believe this issue has been fixed. Sorry for the delay in response.

authors: SMAPPER bolemebrige

repo: austin-taylor/flare


text:
Sebastian.01 login

Adjusted project to existing Swift code sample style and UI.
Changed project settings to include Auth0 placeholders
Added standarized headers to the source files

+1 @ntotten

authors: pablolvillar sebacancinos


text:
[SDK-2298] Update Sample applications

This PR updates the examples to work with the latest versions where appropriate:

Use the latest Auth0 SDKs
Use the latest Xamarin Forms
Build using a more recent Android version
Remove the Xamarin UWP example for now. If needed we can also retrieve it back from history.
Update supported Android versions to be up to date
Dropped unused dependencies where possible

[SDK-2298]


text:
Adding Retry Mechanism to Auth0 Client

🔧 Changes
We've been seeing a drastic uptick in integration test failures. We suspect that this is to do with the Go SDK's v1 change in handling retries no longer being by default but user-defined when instantiating the client. This PR adds the line of code necessary to perform retries on behalf of the user when 429 and 500 status codes are experienced, up to five retries.
📚 References

Similar addition to Auth0 Terraform Provider

🔬 Testing
Manually tested for now.
📝 Checklist

[x] All new/changed/fixed functionality is covered by tests (or N/A)
[x] I have added documentation for all new/changed functionality (or N/A)

Codecov Report
Patch coverage: 85.71% and project coverage change: +0.10% :tada:

Comparison is base (3bd5178) 71.97% compared to head (b57b549) 72.07%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #803      +/-   ##
==========================================
+ Coverage   71.97%   72.07%   +0.10%
==========================================
  Files          91       91
  Lines       11447    11463      +16
==========================================
+ Hits         8239     8262      +23
+ Misses       2703     2696       -7
  Partials      505      505

Files Changed
Coverage Δ

internal/cli/terraform_fetcher.go
100.00% <ø> (ø)

internal/cli/terraform.go
65.57% <73.68%> (+3.70%)
:arrow_up:

internal/cli/cli.go
46.42% <100.00%> (+0.64%)
:arrow_up:

internal/cli/rules.go
67.17% <100.00%> (+0.59%)
:arrow_up:

... and 1 file with indirect coverage changes

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

authors: codecov-commenter willvedd


text:
Invalid signature on the key/pem pait

I've created a private/public key pair using
openssl genrsa -out private.key 2048
openssl rsa -in private.key -pubout -out public.pem

When I try to sign/verify, it only works if I use the private key to both sign and verify.
If I use the public key to verify, I get the JsonWebTokenError: invalid algorithm error, no matter which key I used to sign.
And if I try to do it properly: sign with the public key and verify with the private key, I get the  JsonWebTokenError: invalid signature error.
var key = fs.readFileSync('ssl/private.key');
var pub = fs.readFileSync('ssl/public.pem');
var json = {
	jwtid: "sexy2puppy-" + new Date().getTime(),
	issuer: 'Sexy',
	audience: 'Puppy'
};
var s = jsonwebtoken.sign(json, key);	// signing with private key
var p = jsonwebtoken.sign(json, pub);	// signing with public key

console.log(jsonwebtoken.verify(s, key));	// works
console.log(jsonwebtoken.verify(s, pub));	// invalid algorithm
console.log(jsonwebtoken.verify(p, key));	// invalid signature
console.log(jsonwebtoken.verify(p, pub));	// invalid algorithm

Am I missing something here?

You need to specify an algorithm when signing. The #sign method defaults to HS256, so it's just treating your key as a passphrase for the HMAC.
The reason you were getting "Invalid Algorithm" is because #verify does look at the key, decides it must be for one of the public key algorithms (ES or RS), but sees that doesn't match up with the token's HS256.
The correct way would be to sign with the private key, specifying an algorithm (such as RS256) and then verifying with the public key (ideally also specifying the algorithm, but not necessary).

I understand your first part, about the default HS256 algorithm being the wrong one, that makes sense. I will try specifying RSA tomorrow at work for noth #sign and #verify, and play with that.
However, the second part is a little confusing. Granted, I am not a network security expert, but if the private key is private, and the public key is open publicly, then when I sign with the private key, wouldn't anyone then be able to verify (decode) that message, since anyone can have the public key?

You are signing the message, not encrypting it. You are there only one that has the private key, and so it can be verified with the public key with confidence that the token has not been tampered with.
Given we are not encrypting, anyone can read the token whether they have keys or not.

Darn it. I finally understand now! Thanks!
I had the wrong impression of JWT. I was under the impression that the secret was used to encrypt and decrypt the header.
Now I understand that the header and the payload is just encoded, and that the signature itself is the part used to verify the sender.
My bad.

authors: cope omsmith


text:
event for notification of auth failures

Hi, Is it possible to add an event callback for failures in socket-jwt.authorize? i.e. no token, invalid token, timer-initiated disconnect, etc.
I tried using a secondary middleware handler, but socketio-jwt doesn't pass the socket/connection along for additional handling.

+1

Server side or client side?

I'm currently struggling with this same thing. I'm loading the code and single page initial DOM from one server and then connecting socket.io to another server. On initial load, I have no way of knowing whether user is logged in or not. I was expecting that socket.on('error') will be called when I'm using outdated version of token, as per example on the Readme file, but it looks like it doesn't do that when using noQsMethodmethod, instead it simply disconnects socket instantly if wrong token was passed. But the reason the socket was disconnected is unknown, which could have happened because of internet problems, just as well.
So essentially it would be great if the socket.on('error') would work when using noQsMethod method, or something similar.

I was expecting that socket.on('error') will be called when I'm using outdated version of token

You can check the expiration client-side by using jwt-decode

Yeah that might be a good option, but I would think it would still be reasonable to be able to properly validate the token on a server, as it might still be valid locally, not expired, but invalidated on the server if you're a using technique such as when user logs out, all its clients are logged out as well. I hope that makes sense.
Currently for testing purposes I've modified the code to emit 'auth_error' with the error (timeout or invalid_token) just before disconnecting the socket and it seems to be working quite well. If I find a token stored in users local storage, I try to authenticate user and in case this results in error, I can easily navigate user to the login page.
Do you think such feature would be possible to implement here, or you see some concerns about it?

I think this is handled by #42

authors: drulia jfromaniello mhassman paramburu


text:
Fix incorrect function in uninstall hook

Description
Fix an incorrect function loaded in the uninstall hook

@lbalmaceda - There is but this one hook is odd in that it only works when the plugin is removed from the site, not like other hooks.


text:
Discuss: Extend guide with other translation repository strategies

Hi,
During the searches that led me to discover this nice guide, I found that there were at least two other translation repository strategies used by sphinx-doc projects, aside of the 'mono-branch' one described ATM:

Dual branch: translations are maintained in a separate, translation dedicated, branch.
I have to make a second pass to grasp the pros of this one and see if some use language specific branches.
Dual repo: translations are maintained in a separate repo.
Major pro of this strategy is avoiding cluttering the main repo history with translations commits.
Again, I have to dig deeper to get all the pros and cons.

If you don't mind, I'll announce publishing of this guide source and RFC to this in the few most significant issues where I've found the guide mentioned :)
Thanks again for sharing this
TY
J

Sure, feel free to share it!

authors: authoress silopolis

repo: authoress/sphinx-intl-guide


text:
Create API policy source

Create base policy source and refactor git policy source to work with it
Remove unused code of _cloned_from_remote
Added tar safe to our code base
Added config to support API policy source

How to test:
git flow:
as usual, without any changes in conf
API flow:
run with those env conf:
        "OPAL_POLICY_REPO_CLONE_PATH":"~/projects/opal-example-policy-api-repo",
        "OPAL_POLICY_REPO_URL":"http://localhost:1337",
        "OPAL_POLICY_SOURCE_TYPE":"API"

setup a simple python HTTP server on port 1337
and put bundle.tar.gz in this folder
override bundle.tar.gz with copy command
will send you my files @ slack

@asafc
To check this with docker you need to do this:
cd ~/projects/opal/docker
cd - ; docker build -t opal-server-local -f docker/Dockerfile ./ ; cd -

replace the image in the file docker/docker-compose-api-policy-source-example.yml to opal-server-local
run:
docker-compose -f ../docker/docker-compose-api-policy-source-example.yml up --force-recreate

verify that all the logs look good
run:
cd docker_files/bundle_files
mv bundle.tar.gz{,.bak1}; mv bundle.tar.gz{.bak,}; mv bundle.tar.gz.bak{1,}

see that your bundle is updating

repo: authorizon/opal


text:
Include re-exports in pyi file

The recent addition of the __init__.pyi file means VSCode's Pylance looks to that file for static analysis, rather than the .py file.
This PR copies re-exports to the .pyi file, allowing VSCode to resolve re-exported paths such as this:

from authzed.api.v1 import CheckPermissionRequest

# Without this PR, Pylance only resolves this path
# from authzed.api.v1.permission_service_pb2 import CheckPermissionRequest

Any thoughts on this one? It's pretty clunky to have to write imports like this to get type hints:
from authzed.api.v1.core_pb2 import RelationshipUpdate, SubjectReference
from authzed.api.v1.experimental_service_pb2_grpc import ExperimentalServiceStub
from authzed.api.v1.permission_service_pb2 import (CheckBulkPermissionsRequest, CheckBulkPermissionsRequestItem,
                                                   CheckBulkPermissionsResponse, CheckPermissionRequest,
                                                   CheckPermissionResponse, Consistency, DeleteRelationshipsRequest,
                                                   DeleteRelationshipsResponse, WriteRelationshipsRequest,
                                                   WriteRelationshipsResponse)
from authzed.api.v1.permission_service_pb2_grpc import PermissionsServiceStub
from authzed.api.v1.schema_service_pb2_grpc import SchemaServiceStub
from authzed.api.v1.watch_service_pb2_grpc import WatchServiceStub

@mateenkasim I'm a new maintainer and I'm also not super familiar with python library conventions around typing and interfaces. Is this a common pattern? It also looks like this is manually extending something that was manually created - does that match your understanding?
Do the import paths for the annotations match the import paths for the actual objects? Do they need to?
I think I'm generally good with this approach, but I want to make sure I understand the how and the why of it.

Sure, I'll put my understanding. The interfaces, or stubs, are meant to be a stripped-down version of the code itself, where the module path and code structure is the same, but implementation is missing. This gives something clean off of which you (or static-analyzers, like type-checkers) can read the type information. Sometimes types are enhanced in the stub file compared to the code file itself, since that's where analyzers are looking anyway. Example from an established project:

Django file for QuerySets: https://github.com/django/django/blob/main/django/db/models/query.py
Django stub file for QuerySets: https://github.com/typeddjango/django-stubs/blob/master/django-stubs/db/models/query.pyi

This can also hide information that you didn't intend to be publicly used, like imports of 3rd-party libraries that you need to use but don't want to re-export. In that case, you just don't put the import in the stub file.
In this case, I haven't checked the motivation or details of why __init__.pyi exists in the first place (maybe I should?). The Client/AsyncClient stuff isn't mine, so I didn't touch it. I do know it appeared here.

https://github.com/authzed/authzed-py/pull/149
https://discord.com/channels/844600078504951838/844600078948630559/1222604495867875369

All I know is that, if there is going to be a stub file in the first place, then it will need all the type/import information that we wanted publicly available from the implementation file.

Okay, that makes sense. I had a look too at what's autogenerated vs manually generated, and it looks like the current python protoc tooling doesn't create a __init__.py file anyway, so that was something that we built by hand. It looks like all you're doing in the pyi file is bringing it in line with what's in __init__.py and I'm here for it. I'm gonna go ahead and accept and merge this.
I'll talk with the team on Monday about getting a release cut.

One last question: if the .pyi file didn't exist and we just typed the __init__.py file, would it autodiscover? I suppose we can do that in future work if desird.

repo: authzed/authzed-py


text:
Fix Travis CI Build

The Travis CI build seems to be broken since the rename to sslpsk2, this PR should fix Travis builds and also add tests for python 3.9 and 3.10

Hmm travis does not seem to have support for python 3.10, i tried removing the test for python 3.10 via a force push, but travis still tries to test it.


text:
🛑 Mapa Městem na Kole § mapa.prahounakole.cz is down

In 1fe25ee, Mapa Městem na Kole § mapa.prahounakole.cz (https://mapa.prahounakole.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mapa Městem na Kole § mapa.prahounakole.cz is back up in d0cda1e after 15 minutes.

repo: auto-mat/automat-statuspage


text:
🛑 Automat eshop § obchod.auto-mat.cz is down

In c3a83b1, Automat eshop § obchod.auto-mat.cz (https://obchod.auto-mat.cz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Automat eshop § obchod.auto-mat.cz is back up in 49602a4.


text:
docs(sensor calibration): add lidar imu calibration tool

Description

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The Reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@LalithVipulananthan I create this new pr. Is it OK?


text:
build-and-test workflow is failing due to CUDA runtime version

@knzo25 starting from this PR, The CI for build-and-test started failing:

https://github.com/autowarefoundation/autoware.universe/actions/runs/9590002364/job/26444678737#step:15:22008

8: C++ exception with description "cudaErrorInsufficientDriver (35)@/__w/autoware.universe/autoware.universe/perception/lidar_centerpoint/include/lidar_centerpoint/cuda_utils.hpp#L80: CUDA driver version is insufficient for CUDA runtime version" thrown in the test body.

For some reason the has CI passed for the build-and-test-differential cuda yet it fails the build-and-test checks.
Originally posted by @xmfcx in https://github.com/autowarefoundation/autoware.universe/issues/6989#issuecomment-2186485659

@xmfcx
Kind of a nasty one as I run the tests a while ago with no errors. Will look into it asap, but this week I am full of deadlines...

@youtalk
I tried to reproduce the error using a docker and following the ci/cd commands whenever possible.
However, the tests pass:
9: -- run_test.py: invoking following command in '/home/kenzolobos/workspace/autoware/build/lidar_centerpoint':
9:  - /home/kenzolobos/workspace/autoware/build/lidar_centerpoint/test_preprocess_kernel
9: [==========] Running 4 tests from 1 test suite.
9: [----------] Global test environment set-up.
9: [----------] 4 tests from PreprocessKernelTest
9: [ RUN      ] PreprocessKernelTest.EmptyVoxelTest
9: [       OK ] PreprocessKernelTest.EmptyVoxelTest (45 ms)
9: [ RUN      ] PreprocessKernelTest.BasicTest
9: [       OK ] PreprocessKernelTest.BasicTest (7 ms)
9: [ RUN      ] PreprocessKernelTest.OutOfRangeTest
9: [       OK ] PreprocessKernelTest.OutOfRangeTest (7 ms)
9: [ RUN      ] PreprocessKernelTest.VoxelOverflowTest
9: [       OK ] PreprocessKernelTest.VoxelOverflowTest (7 ms)
9: [----------] 4 tests from PreprocessKernelTest (66 ms total)
9:
9: [----------] Global test environment tear-down
9: [==========] 4 tests from 1 test suite ran. (66 ms total)
9: [  PASSED  ] 4 tests.

Thanks @knzo25 , this explains why it specifically failed for the self hosted machines. I will try installing the dricer on the host machines and see.

I've installed CUDA 12.3 to both machines.
Running again:

common-runner-x64-01: https://github.com/autowarefoundation/autoware.universe/actions/runs/9676012953
leo-copper: https://github.com/autowarefoundation/autoware.universe/actions/runs/9675999034

They both failed with the same error: https://github.com/autowarefoundation/autoware.universe/actions/runs/9675999034/job/26698258077#step:15:22044
:confused:
Here is the results from host machine (leo-copper):
mfc@copper:~$ nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Wed_Nov_22_10:17:15_PST_2023
Cuda compilation tools, release 12.3, V12.3.107
Build cuda_12.3.r12.3/compiler.33567101_0
mfc@copper:~$ nvidia-smi
Wed Jun 26 13:44:42 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 555.42.02              Driver Version: 555.42.02      CUDA Version: 12.5     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce GTX 1070        Off |   00000000:01:00.0  On |                  N/A |
| N/A   52C    P8             11W /  125W |     356MiB /   8192MiB |      8%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A      1086      G   /usr/lib/xorg/Xorg                            237MiB |
|    0   N/A  N/A      1333      G   /usr/bin/gnome-shell                          115MiB |
+-----------------------------------------------------------------------------------------+

The host machine has the necessary stuff and I've updated the rest of the machine with sudo apt update && sudo apt dist-upgrade. Then restarted them for good measure too.
@knzo25 I don't know what is missing then :(

I have about the same as you :cry:
kenzolobos@desktop:~/workspace/autoware$ nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Wed_Nov_22_10:17:15_PST_2023
Cuda compilation tools, release 12.3, V12.3.107
Build cuda_12.3.r12.3/compiler.33567101_0
kenzolobos@desktop:~/workspace/autoware$ nvidia-smi
Wed Jun 26 19:59:29 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.54.15              Driver Version: 550.54.15      CUDA Version: 12.4     |

I was going to recommend a reboot but you already did it. In the past when changing versions, unload and reload the kernel modules worked when nvidia-smi did not work, but this is not the case. Do you have the cuda samples in that machine to check if those run?

Do you have the cuda samples in that machine to check if those run?

I followed the regular steps as always while installing from here: https://github.com/autowarefoundation/autoware/tree/main/ansible/roles/cuda#manual-installation
I will install the nvidia-driver-550 and try again. (this is what I have on my daily work pc as well)

I think I've understood everything now.
VoxelGeneratorTest.TwoFramesNoTf this test is failing.
What are the changes that caused it?
In the PR here

  auto points_d = cuda::make_unique<float[]>(capacity_ * config.point_feature_size_);
  cudaMemcpy(
    points_d.get(), points.data(), capacity_ * config.point_feature_size_ * sizeof(float),
    cudaMemcpyHostToDevice);

CUDA calls are being made.
I think before these, no serious CUDA calls were being made. Most of them could run on cpu too probably.
What are the runner specs?
GitHub hosted runners
These are CPU only, here are their specs.
Right now every job except:

ARM64 workflows
build-and-test
build-and-test-daily

are running on them.
Self-hosted runners
And we have 2 machines here:

leo-copper: has GTX1070
common-runner-x64-01 c6a.xlarge cpu-only

These run:

build-and-test
build-and-test-daily

⚠ nvidia_container_toolkit was not installed on these machines.
Then how did it pass the b&t-diff in the first place then?
This is the first fishy part from the lidar_centerpoint PR b&t-diff CI run:

Finished <<< lidar_centerpoint [1min 37s]

On my high end machine,

Finished <<< lidar_centerpoint [4min 45s]

This is too fast for this package.
And looking at its tests:
Almost no tests are performed, including VoxelGeneratorTest.TwoFramesNoTf
I didn't investigate deeper on why this didn't run.
Verdict
I think, until this PR, no serious CUDA code was in the colcon tests before.
Mostly simple stuff that could also be run on the CPU were tested.
For CUDA only tests to run, we need CUDA capable machines with GPUs.
These tests cannot be done on neither GitHub hosted machines nor the AWS cpu-only runner that we have.
I have now installed the nvidia_container_toolkit on the leo-copper machine with GTX1070 and restarted the machine.
Started the test again. But it will probably fail because I don't think when GitHub initiates the containers, it passes --gpus all flag to the containers.
I will look into it to see how I can do that for that machine.

Then how did it pass the b&t-diff in the first place then?

Found out the bug in:

https://github.com/autowarefoundation/autoware.universe/pull/7712#issuecomment-2191900752

Now it fails on build-and-test-differential too.

The tests are alright because when I've configured leo-copper machine, it passed entire build-and-test successfully.
See:

https://github.com/autowarefoundation/autoware.universe/pull/7721

But we will have to disable the tests that fail on non-cuda capable machines. Because we don't have the infrastructure ready to handle gpu based testing for every PR etc.
I will open up an issue to track disabled tests that should be re-enabled once CUDA capable machines are back.

With all the CI cache related issues are fixed, CI filter issues solved, GPU requiring tests are disabled and tracked, and most importantly, build-and-test now passing, I think we can close this issue.
If you have any questions left, please feel free to ask.


text:
fix(ground_segmentation): Change ground segmentation parameters

Description

This PR changes parameters for ground segmentation algorithm and fixes: https://github.com/autowarefoundation/autoware.universe/issues/669
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Can you check both:

https://github.com/autowarefoundation/autoware.universe/blob/main/perception/ground_segmentation/src/ray_ground_filter_nodelet.cpp
https://github.com/autowarefoundation/autoware.universe/blob/main/perception/ground_segmentation/src/scan_ground_filter_nodelet.cpp

Because ray_ground_filter_nodelet might work better than the scan_ground_filter_nodelet

@badai-nguyen @miursh May I ask for a review?

@xmfcx @djargot
We have developed new option for scan ground filter https://github.com/autowarefoundation/autoware.universe/pull/1899
You can still use conventional algorithm, but some option parameter is added https://github.com/autowarefoundation/autoware.universe/blob/main/launch/tier4_perception_launch/config/obstacle_segmentation/ground_segmentation/ground_segmentation.param.yaml#L26-L31.

What should we do about this PR?
If no reply within two weeks, I will close it.

What should we do about this PR? If no reply within two weeks, I will close it.

I believe it can be closed. The issue that this PR was supposed to solve was solved in a different way.

authors: djargot miursh piotr-zyskowski-rai xmfcx yukkysaito


text:
Update sbt-sonatype to 3.9.14

Updates org.xerial.sbt:sbt-sonatype from 3.9.13 to 3.9.14.
GitHub Release Notes - Release Notes
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.xerial.sbt", artifactId = "sbt-sonatype" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.xerial.sbt", artifactId = "sbt-sonatype" }
}]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #105.


text:
Fix Duplicate Lombok adapter generation

fix lombok generating duplicate noop adapters.
add primitives to the noop adapter

Will resolve #259

@rbygrave please review and deploy when you get time

repo: avaje/avaje-validator


text:
Icons in sub-children

I know icons in subchildren aren't native to AdminLTE, but I find it a nice addition. Would it be worth submitting the PR to make it work? Or is it considered out-of-scope?
I'm just overriding the macros template in my app/Resources at the minute.
Change is here: https://github.com/avanzu/AdminThemeBundle/compare/master...MartinLyne:patch-1
Edit: Also, how do I put label on this to question?

i like your idea :+1:

I like it too :+1:

That's a good contribution indeed. I think that we could enhance AdminLTE a bit with this kind of enhancements.
@MartinLyne : do you want to create a pull request on your own, or should we merge @sylvaincombes 's one?

Sorry for absence, great, seems @sylvaincombes PR (or my forked repo more likely) suffers the same issue I get whenever I try to modify files via github's editor, I'll make a new branch and edit code/documentation via normal means and make a new PR, see if that works.

Hi! No problem.
The best way to be to:

Clone your fork locally
Sync it
Create a branch
Make your changes, commit, push and create a PR from this branch

This will allow you to be up to date with the master branch and be sure that your PRs will be accepted :)
Thank you for your contribution!

@chteuchteu Yeah it's much easier locally, I guess github doesn't warn you that forked projects are out of sync
Now I update, i notice that there has been a significant change to the way the sidebar nav works in this commit: https://github.com/avanzu/AdminThemeBundle/commit/75c1d75983f701da9d7664a668cad9badaf2b747
Seems that top-level items with no route can no longer host children, does that look like an oversight I should amend, or is it desired restriction? Probably want to drop into child-bearing code if it has a route or it has children? (I'll give it a go)

That's unfortunate indeed... I don't know if it is a desired restriction, but anyways: I don't think that we should stick with this restriction.
Could you give it a try please?

That fix seems to work, I think worst case is we go back to whatever could have happened before, my non-route-with-children examples work okay, I added some top-levels-without-routes-no-children and they display as I think they should.
I'll prep the PR

Thank you for your work, I just merged the PR.

Great :metal: thanks to @MartinLyne @OskarStark @chteuchteu ! (I closed the pull request made from @MartinLyne first patch)

Brilliant! https://www.youtube.com/watch?v=S65ZzffW-Cw

:+1:

authors: MartinLyne OskarStark chteuchteu sylvaincombes

repo: avanzu/AdminThemeBundle


text:
chore: release main

:robot: I have created a release beep boop
dev-dependencies-client: 2.0.0
2.0.0 (2023-12-06)
⚠ BREAKING CHANGES

bumping breaking client dependencies - vite and vitest

Features

bumping breaking client dependencies - vite and vitest (a06a42e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/aversini/dev-dependencies/releases/tag/dev-dependencies-client-v2.0.0 :sunflower:

repo: aversini/dev-dependencies


text:
Keep nature of inner sources

Fixes #4.
Now pullable inner sources are now flattened to a pullable output source.
Works with synchronous, asynchronous, and hybrid sources.
The only assumtions are:

inner sources are homogeneous, i.e. not mixed listenable and pullable.
every message sent from the sink to the output source is a pull of the next item, and therefore be delivered to the first inner source until a value is pushed back.

The basic idea is:

Messages from the sink are added to a queue.
An index points to the next message to be sent to an inner source. Initially it is 0.
The oldest inner source is the current source. All messages are sent to the current source.
When the current source pushes data, the first message in the queue is considered delivered and therefore removed.
When the current source terminates, the index is reset to 0 and the oldes of the remaining inner sources becomes the current source.
Start over from sending all messages to the new current source.

I noticed that my changes introduced some problems when mapping a pullable input source to listenable inner sources.
In that case, the output is listenable, so the operator should itself pull inner sources from the input source.
Now I managed to handle this situation by pulling the input source whenever there is no inner source available.
For the described scenario, this means the input is pulled once in the beginning and then on each end of an inner source.
Note that this changes the behavior when inner sources are also asynchronous.

With the original eager approach, all inner sources are pulled eagerly. Many of them could be active at the same time and deliver items concurrently.
With the new lazy approach, only one inner source is active at a time. When that source ends, a new one is pulled from the input source.

The following example illustrates the difference:
pipe(
  range(1, 3),
  flatMap(i => pipe(
    interval(i * 100),
    take(),
    map(j => i + '-' + j)
  ),
  forEach(i => console.log(i))
);

With the original approach, this could log:
0-0, 0-1, 1-0, 0-2, 2-0, 1-1, 1-2, 2-1, 2-2
With the new approach, this will log:
0-0, 0-1, 0-2, 1-0, 1-1, 1-2, 2-0, 2-1, 2-2

I think it makes sense for a pullable input source to only be pulled when needed, but that is debatable.
I am also planning to publish a separate operator as callbag-flat-map-lazy with the described behavior, so everyone could choose the approach that fits the needs on a case-by-case basis.

Hi @mperktold , I've checked out the example, ran it with the current code(after adding a missing null check) I see the same expected output.
I'd really like to see if there are some other examples you have where the expected output is not returned by this code.
It's good that you created a new package for such use-cases so that users can pick what they want 👍

Do you mean the example I gave here? ai need to double-check that when I‘m back at my PC (I am currently in holidays), but that was more a comparison between two revisions of my change, not between my change and the original version. Sorry for the confusion.
The main reason I created this pull request is described in #4. It is about being able to create pullable output sources with this operator.
In the linked issue, I also gave an example, which you can run to see the difference.
Another possibility is to run the tests of the new version against the original implementation.

authors: avinashcodes mperktold

repo: avinashcodes/callbag-flat-map


text:
Image Stiching

Image Stiching
This be able to stitch two images together, creating a panorama of stitched images.
Sometimes , we click more than image if the object is close and large and then desire it to be in one frame.
Left view

Right view

Desired output in a frame

@ayush-raj8 updates on this?

@kaustubhgupta  I'll make pr within few days.

repo: avinashkranjan/Amazing-Python-Scripts


text:
[ADDED]: Ciphey Tool

Description
Added Script for Ciphey Tool
Fixes #406
Have you read the Contributing Guidelines on Pull Requests?

[X] Yes
[ ] No

Type of change
Please delete options that are not relevant.

[X] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I've edited the SCRIPTS.md and link to my code.
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

@avinashkranjan Can you review the PR.


text:
书签不能编辑在文件夹中的位置吗

如题，edge导出的书签导入进来后会在外面套几层文件夹，能不能加个更改位置的功能。或者有什么办法可以临时解决下吗？

好的 好的 感谢回复 期待增加功能

好的 好的 感谢回复 期待增加功能

已经初步实现！请查收！
（如果发现有什么事情不对，麻烦反馈给 Liny 去修（（(～o￣3￣)～ 谢谢你！！

简单使用了下，目前没有问题