add slashes to end of URL - home page tiles

resolves:
https://federal-spending-transparency.atlassian.net/browse/FDG-6144

hmm, even after adding in the trailing slashes, I'm not seeing them when hovering over the images. could it be because of this Gatsby feature? Let me know your thoughts @tompurkaple thx
https://www.gatsbyjs.com/docs/reference/built-in-components/gatsby-link/#relative-links

@fzafrb If you add a slash at the start of the path as well, then the trailing slash will appear when hovering over the image

hmm, even after adding in the trailing slashes, I'm not seeing them when hovering over the images. could it be because of this Gatsby feature? Let me know your thoughts @tompurkaple thx
https://www.gatsbyjs.com/docs/reference/built-in-components/gatsby-link/#relative-links

@fzafrb If you add a slash at the start of the path as well, then the trailing slash will appear when hovering over the image

that did the trick thx!


Trampoline hooks %rip patching improvements

Now uses as and objdump to parse human-readable at&t asm instead of raw bytes.
Tested a bit, but @DreamMaoMao for further testing (hycov) and @jbeich for potential clang/bsd comments.
Seems to work alright on my end.
Should work with %rip being used in mov, lea and call

Hyprland, built from branch main at commit 191fa587f4daf9f3bf3e3f791de9e2dc5e95a459  (windowrules: add initialTitle and initialClass (4259)).
Date: Wed Dec 27 06:47:46 2023
Tag: v0.33.1-92-g191fa587
flags: (if any)

it seem that the problem is still exist

you didn't checkout to this mr :P

my bad ,
Hyprland, built from branch trampoline-rip-improvements at commit d8ca95be7668375a4c576f8116bc6066281cc56f  (use cc instead of as).
Date: Wed Dec 27 02:35:45 2023
Tag: v0.33.1-88-gd8ca95be
flags: (if any)
debug
it work normally now.

cool :D


Python 3.12

Not immediately working. E.g.:
https://github.com/dan-fritchman/Hdl21/actions/runs/8443756151/job/23127988377
(Or at least our CI is not immediately working.)

Noting https://github.com/Vlsir/Vlsir/pull/98 (basically the same topic for VLSIR) worked, without any real changes.
Presumably just updates to our dependencies in the test environment.

Awesome!
could we make a new release?

Should probably actually fix this one first.
You wanna do a quick PR for it?

the tests worked for me

So I don't see it passing anywhere on the CI runs?
E.g. the most recent run:
https://github.com/dan-fritchman/Hdl21/actions/runs/9786217659
We explicitly enable "continue on error" for py3.12 here:
https://github.com/dan-fritchman/Hdl21/blob/5633bc66b19dfecedbda23f69ec3e4818021afe2/.github/workflows/test.yaml#L43
Maybe just PR that out, and enough stuff "behind the scenes" will have changed to make it "just work".

#232 "fixes" this.
Which is to say, fixes our test setup.
Particularly I split out the big matrix of Python and pydantic test-versions from the containerized simulation tests.

Just in time for Python 3.13's release on October 1:
https://peps.python.org/pep-0719/

OK well spoke to soon, #232 doesn't quite work yet.
Appears the combination of Python 3.12 & Pydantic 1.9 don't play nice. E.g.:
https://github.com/dan-fritchman/Hdl21/actions/runs/10733148162/job/29766001200
Noting for Python 3.7-3.8 it's "the other way around". Pydantic v1 works, v2 fails.
I don't see what we're gonna be able to do about that, other than maybe writing a more elaborate dependency specification (if that's possible). Probably just like a note or table.


Update Rust toolchain to 2023-10-03

Source changes required by the following upstream commits:

rust-lang/rust@5a0a1ff0cd move ConstValue into mir
rust-lang/rust@ea22adbabd adjust constValue::Slice to work for arbitrary slice types
rust-lang/rust@c94410c145 rename mir::Constant -> mir::ConstOperand, mir::ConstKind -> mir::Const
rust-lang/rust@44ac8dcc71 Remove GeneratorWitness and rename GeneratorWitnessMIR.
rust-lang/rust@4ed4913e67 Merge ExternProviders into the general Providers struct
rust-lang/rust@3c52a3e280 subst -> instantiate
rust-lang/rust@6a02baaa3d Partially outline code inside the panic! macro

Fixes: #2784
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

The changes (seemingly) required by https://github.com/rust-lang/rust/commit/4ed4913e67cab329bd3cca92dff1cf558cc3575e break stubbing. I have now issued #2806, which is as far as we can go until we have to face this change.

It seems that three of the already-slow tests got even slower. Not sure what to do about this.

Sometimes, this is due to noise, so I suggest running them locally multiple times to check whether the slow-downs are real.


python312Packages.aioairzone-cloud: 0.6.1 -> 0.6.2

Diff: https://github.com/Noltari/aioairzone-cloud/compare/refs/tags/0.6.1...0.6.2
Changelog: https://github.com/Noltari/aioairzone-cloud/releases/tag/0.6.2
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

5 packages built:

home-assistant-component-tests.airzone_cloud
python311Packages.aioairzone-cloud
python311Packages.aioairzone-cloud.dist
python312Packages.aioairzone-cloud
python312Packages.aioairzone-cloud.dist


Use go-sdk v0.3.7

The field name changes don't result in some additional changes here to the models in use etc?

The field name changes don't result in some additional changes to the models in use etc? Just the dependency bump will suffice?

Yes. The content from the file will just map to the corresponding types referenced by the new version.


Create validation test for datasets

Having a way to create dataset splits (eg, validation split from the train set) in the YAML would be useful for reporting validation metrics, and to avoid over-fitting the test set when using spearmint.

Hi Séb,
neon already supports the notion of validation dataset partitions, and typically the user would divide their dataset into train/test/validation prior to using neon.
That being said I agree that its occasionally useful to take an existing train/test divided dataset and have the ability to carve some of the training set cases out for validation purposes.  This functionality already exists in neon for datasets that utilize the BatchWriter class like imageset.py.  We could do a better job documenting it, but there is a dataset parameter called validation_pct that can be passed to this dataset and during the first load() call will be used to randomly select a portion of the training cases to use for validation purposes.

Closing this as validation_pct functionality has been merged in as part of #60


RatioAnalysis() doesn't appear to exist

Traceback (most recent call last):
File "C:/Python/StocksLoader/yFinance_Fundamentals.py", line 10, in
print(fa.ratio_analysis(symbol))
AttributeError: module 'FundamentalAnalysis' has no attribute 'ratio_analysis'

My fault.  It's ratio_analysis() in the docs, but ratios_analysis() in the code.


How can I make a violin plot in ECharts?

What problem does this feature solve?
Violin plot is very useful. Example here: https://seaborn.pydata.org/generated/seaborn.violinplot.html
What does the proposed API look like?
I don't know the API, but I want the feature.

A few examples at:

http://bl.ocks.org/z-m-k/5014368 (no license)
https://plot.ly/javascript/violin/
https://github.com/datavisyn/chartjs-chart-box-and-violin-plot

Would this be better as a module or within the main library?

ECharts have many chart types now and we are more cautious when considering adding new chart types because it adds to the package size and we need to consider if this chart type is frequently used enough.
For your case, I'd suggest implementing it using the custom series mechanism by yourself.
The document is https://echarts.apache.org/en/option.html#series-custom . The examples and API documents should be enough for you to create by yourself, but you do need spend some time understand it.
If you think there are some extra API needed when you use the custom series, do let me know.

Thanks @bkmgit and @Ovilia

Thanks @bkmgit and @Ovilia

Hi, @frankyaorenjie.
I also have to use echarts to plot violin plots.  I'm a newbie, though I've already read the document of custom series mechanism, I still didn't have an idea on how to plot it.
If you plotted it successfully, could u pls give me some advice and guidance?
Thanks a million!

@Kittywyk Hi, you make checkout these similar examples:

https://echarts.apache.org/examples/en/editor.html?c=cycle-plot
https://echarts.apache.org/examples/en/editor.html?c=custom-profit
https://echarts.apache.org/examples/en/editor.html?c=custom-error-bar

The only difference is the shape. You may probably use bezierCurve to draw the shape. As for how to implement the violin shape with bezier curves, you may refer to online resources or the chart implementations as mentioned above.

@Kittywyk Hi, you make checkout these similar examples:

https://echarts.apache.org/examples/en/editor.html?c=cycle-plot
https://echarts.apache.org/examples/en/editor.html?c=custom-profit
https://echarts.apache.org/examples/en/editor.html?c=custom-error-bar

The only difference is the shape. You may probably use bezierCurve to draw the shape. As for how to implement the violin shape with bezier curves, you may refer to online resources or the chart implementations as mentioned above.

Thank you very much. I'll have a try.

Update: It should be polygon + smooth instead of bezierCurve because the later cannot be multiple curves.

Violinplot, errorbar are widely used and have already been used for many years in scientific community. It seems that they are becoming more and more popular in recently years. Hope you can add them to echarts. Vega-lite and plotly support violinplot and errorbar now. A lot of users of echarts are lack of the skill to customize a new series, So hope you can support these plots.

Matplotlib and seaborn also support violinplot and errorbar, both of them are absolutely frequently used.

violinplot 用到小提琴样式但是没有，又不想再引入别的框架，只能自定义了，不知哪位大神已经造了轮子，能否提供帮助

Duplicate of #18878

It would have been better to merge the newer issue into this older one as this already has 10 upvotes and likely more people are subscribed here than in the new issue...


html event abstraction, phase 1

To #3602
Part 1.

Main changes are in the first commit - new zif_gui_event, zcl_gui_event and their usage in gui
the rest tons of code are the adjustments in pages and router - no logic changes. Except Router also have minor refactoring in prev_page related code (commit 2)

Part 1 is to just wrap existing event attrs into an interface. Part 2 will be about merging with action_utils.
Would be nice to merge it soon. To continue with part 2.

looks good to me, thanks 👍


Add MaxChanceNodesInHistory() to Game API.

This PR properly addresses issue raised in #360 and adds following methods to Game:
MaxChanceNodesInHistory, MaxMoveNumber and MaxHistoryLength both in C++ and Python. For some games I didn't know how to make the bound tight fast, so I left a TODO and just used the MaxGameLength() call-through value. Some games had a wrong declaration of chance mode in their game type. The first_sealed_auction was kind of weird, I left a comment.

Changing MaxChanceNodesInHistory to have a default implementation that errors "unimplemented". We cannot make the API not backward-compatible at this point.

SGTM

Actually we have a few changes to request, which are easier to do here.

@elkhrt can you add your comments too?

There are 2 comments unresolved, but otherwise I implemented all the changes.


Analyze some popular python projects on github to find out, which language features are actually used

[ ] Statically check if __gettatr__, __setattr__ and other special attributes are accessed or overloaded in the code
[ ]  check for metaclasses in inheritance
[ ] Instrumentalize classes the code with our own __setattr__ in order to find if attributes are dynamically added via the usual syntax (like using o.x = 1 in case when object o does not have an attribute x)

I wanted to do this in order to decide what language features to support. Other ways to decide were used in fact.


dev: collect all tracing max_level features into a separate feature

Background
Currently, risingwave enables release_max_level_info in crate cmd and cmd_all. Because we are using hakari for workspace hack, all crates depending on workspace-hack.toml will be infected. But crates like bench may need to use release_max_level_trace to enable TRACE level log of some interested targets.
Design
Collect all *_max_level_* tracing features into a separate feature, and only enable it when building productional targets.
Future Optimizations
No response
Discussions
No response
Q&A
No response

@BugenZhao @skyzh @wangrunji0408 Any ideas?

You can ignore risingwave_cmd_all for hakari.

You can ignore risingwave_cmd_all for hakari.

I'm afraid that may cause recompiling between unit tests and e2e tests, which is not friendly to developers.

Also if something is really important in benches, set it to info level and filter by event name.

Also if something is really important in benches, set it to info level and filter by event name.

The thing is some events are in storage crate. 🤣
BTW, I tried to separate the features, but hakari still counts our self-defined features in the workspace-hack.
I'll try another way (e.g. let hakari exclude the features) first.

@BugenZhao @skyzh I imitate static-link and write a PR #5725 . Will it help?


Don't preserve space for empty values on category axis

What problem does this feature solve?
In my case I have different categories and multiple series (bar), where not every series has data for each category (i.e. some null values exist).  Currently, ECharts preserves the space for each category in each series. The goal would be to don't preserve space for null values, i.e. no leaks within a category. Therefore each category can be of a different length.
I haven't found a way to handle this with the existing functionality which ECharts provides.
Currently:

Goal:

What does the proposed API look like?
A setting on axis or series level which defines if space for empty values is preserved
Would be great to get some feedback on that :)

Duplicate of #9899 .


How do I know which open source protocol is used for open source components?

Hello, how do I know which open source protocol is used for open source components? If any label on the component?

goproxy.io does't manage the license. You need check it by yourself.
the go toolchain does't care about the license either.
even private, go get could also fetch if you have access of the repo.

ref:

Go Modules Reference

Thanks


Fix compatibility with ZSH versions <=5.0.8

While ZSH 5.0.8 does pass the tests, there is some local:*: not valid in this context warnings during the unit tests, as can be seem below:
zsh 5.0.8 (x86_64-unknown-linux-gnu)
Running test: test_zit_aliases
test_alias_zit_in
test_alias_zit_lo
test_alias_zit_il
test_alias_zit_up

Ran 4 tests.

OK

Running test: test_zit_get_branch
test_valid_https_without_branch
test_valid_https_with_branch
test_valid_git_without_branch
test_valid_git_with_branch
test_valid_ssh_without_branch
test_valid_ssh_with_branch
test_invalid_url

Ran 7 tests.

OK

Running test: test_zit_get_repo
test_valid_https_without_branch
test_valid_https_with_branch
test_valid_git_without_branch
test_valid_git_without_branch
test_valid_ssh_without_branch
test_valid_ssh_with_branch

Ran 6 tests.

OK

Running test: test_zit_install
test_install_without_branch
test_install_without_branch:local:1: not valid in this context: /tmp/tmp.2mzOoChk4h/zit
test_install_with_branch
test_install_with_branch:local:1: not valid in this context: /tmp/tmp.QZ9W3gPOom/zit
test_install_multiple_times

Ran 3 tests.

OK

Running test: test_zit_install_load
test_repo_directory
test_repo_directory:local:1: not valid in this context: https://github.com/m45t3r/zit
zit=''
test_repo_directory_dotzsh
test_repo_directory_dotzsh:local:1: not valid in this context: https://github.com/m45t3r/zit
zit=''

Ran 2 tests.

OK

Running test: test_zit_load
test_loading_module_with_dot_zsh_param
test_loading_module_with_dot_zsh_param:local:1: not valid in this context: World!
test_loading_module_without_dot_zsh_param
test_loading_module_without_dot_zsh_param:local:1: not valid in this context: World!
test_loading_module_with_glob_in_dot_zsh_param
test_loading_module_with_glob_in_dot_zsh_param:local:1: not valid in this context: World!

Ran 3 tests.

OK

Running test: test_zit_update
test_update_without_repos
test_update_with_repos
test_update_with_repos:local:3: not valid in this context: /tmp/tmp.eXKFxn6tXg/a
git=''
pull=''

Ran 2 tests.

OK

The integration tests works normally, and this seems to be a issue with this specific version:
https://github.com/zsh-users/zsh-autosuggestions/issues/127
https://github.com/bhilburn/powerlevel9k/pull/326
However, if this specific version of ZSH should be support (used in Ubuntu 14.04 LTS, for example), this bug should be fixed.

Fixed in ffa2a4b2b96ae6627a198f24992f6823b84278c2.


"Collect email addresses" setting now uses a new field and is an enum

The field added in e3075cccaffc466f6f59433c374e72a8c2d5fb93 (see #11) is the new "Collect email addresses" setting. Today the old field was removed.
The new field has possible values 1 (do not collect addresses), 2 (verified addresses - requires sign in, probably may affect other fields) and 3 (responder input - the old setting).
Also there's another unknown change in an unused field (see diff).
# 05_dump_test.py::test_settings_dump[settings_email]
E       AssertionError: assert [None, [None, None, ['', 1, 0, 0, 0], None, None, [None, 0], None, None, '20.1_email', 52, [None, 0, None, 2, None, None, 3], None, None, None, None, [2], [[1, 1, 1, 1, 1], 1], None, None, None, None, None, None, None, None, [None, '20.1_email']], '/forms', '20.1_email', None, None, None, '', None, 0, 0, None, '', 0, '0000000000000000000000000000000000000000000000000000000000', 0, '[]', 0, 0] == [None, [None, None, ['', 1, 0, 0, 0], None, None, [0, 0], None, None, '20.1_email', 52, [None, 0, None, 2, 1, None, 3], None, None, None, None, [2], [[1, 1, 1, 1, 1], 1], None, None, None, None, None, None, None, None, [None, '20.1_email']], '/forms', '20.1_email', None, None, None, '', None, 0, 0, None, '', 0, '0000000000000000000000000000000000000000000000000000000000', 0, '[]', 0, 0]
E         At index 1 diff: [None, None, ['', 1, 0, 0, 0], None, None, [None, 0], None, None, '20.1_email', 52, [None, 0, None, 2, None, None, 3], None, None, None, None, [2], [[1, 1, 1, 1, 1], 1], None, None, None, None, None, None, None, None, [None, '20.1_email']] != [None, None, ['', 1, 0, 0, 0], None, None, [0, 0], None, None, '20.1_email', 52, [None, 0, None, 2, 1, None, 3], None, None, None, None, [2], [[1, 1, 1, 1, 1], 1], None, None, None, None, None, None, None, None, [None, '20.1_email']]
E         Full diff:
E           [
E            None,
E            [None,
E             None,
E             ['', 1, 0, 0, 0],
E             None,
E             None,
E         -   [0, 0],
E         ?    ^
E         +   [None, 0],
E         ?    ^^^^
E             None,
E             None,
E             '20.1_email',
E             52,
E         -   [None, 0, None, 2, 1, None, 3],
E         ?                     ---
E         +   [None, 0, None, 2, None, None, 3],
E         ?                            ++++++
E             None,
E             None,
E             None,
E             None,
E             [2],
E             [[1, 1, 1, 1, 1], 1],
E             None,
E             None,
E             None,
E             None,
E             None,
E             None,
E             None,
E             None,
E             [None, '20.1_email']],
E            '/forms',
E            '20.1_email',
E            None,
E            None,
E            None,
E            '',
E            None,
E            0,
E            0,
E            None,
E            '',
E            0,
E            '0000000000000000000000000000000000000000000000000000000000',
E            0,
E            '[]',
E            0,
E            0,
E           ]```

Fixed in c9ac3e0a0eb72acb66a5ec9d2a38051e27fd49aa


Devcontainer and dependency updates

This turned out to be a much bigger change than anticipated:

switched to using poetry and consolidated all requirements in pyproject.toml to centralize dependencies
updated all dependencies, and completed upgrade of SQLAlchemy and Pydantic
Added a devcontainer to make it easier to run the project
Added debugger support, with hot reloading

Leaving the PR in draft for now as I am still sorting out some issues with the BDD tests

Opening this for review. BDD tests @Endorsements-006 and @Endorsements-007 are failing, but I have not been able to determine why since there is no stack trace logged in the endorser service when this happens.
I have logged #99 and #100 to deal with the missing bits, rather than dragging this (already bigger than expected) PR along for much longer.


CI test build with RAM overflow

Describe the bug
The mem_protect test isn't run during sanity because build detect a RAM overflow
This test shouldn't be skipped
To Reproduce
Any sanity on mainline
Expected behavior
mem_protect test executed
Impact
Can't detect regression (memory domain, permission inheritance, kobject access,...) on future merge for RISC-V arch.
Logs and console output
INFO    - 12/18 hifive1_revb              tests/kernel/mem_protect/mem_protect/kernel.memory_protection SKIPPED (RAM overflow)
Additional context
For now, this test is manually ran and succeed on a similar board with more RAM.

if a test binary does not fit in flash/ram, then we there is not much we can do beside optimizing the test code to be smaller, otherwise it will be skipped and is not reported as a failure.

if a test binary does not fit in flash/ram, then we there is not much we can do beside optimizing the test code to be smaller, otherwise it will be skipped and is not reported as a failure.

The ask is really unclear but what he wants is for the mem_protect test to work on RISC-V with 16K of RAM. This is important to maintain code coverage of memory protection on this arch.
It works on ARM with 16K of ram, so some analysis is necessary to find out why this overflows on RISCV.

For now, this test is manually ran and succeed on a similar board with more RAM.

which board is that?
/home/nashif/bin/zephyr-sdk-0.12.0-beta-2/riscv64-zephyr-elf/bin/../lib/gcc/riscv64-zephyr-elf/10.2.0/../../../../riscv64-zephyr-elf/bin/ld: region `RAM' overflowed by 10864 bytes
This is 10K overflow, not sure how we are going to get this into 16k of RAM. This board just needs to be excluded from this test IMO.
@andrewboie  which ARM board with 16K works with this test?

@andrewboie which ARM board with 16K works with this test?

frdm_k64f:
[149/160] Linking C executable zephyr/zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       72644 B         1 MB      6.93%
            SRAM:       14276 B       192 KB      7.26%
        IDT_LIST:          88 B         2 KB      4.30%
[160/160] Linking C executable zephyr/zephyr.elf

I think I see where this got muddled, ram-report has different numbers:
$ ninja ram_report
[0/1] cd /home/apboie/projects/zephyr2/zephyr/tests/ke...ests/kernel/mem_protect/mem_protect/build/ram.json ra
Path                                                                                Size    %
==============================================================================================================
root                                                                                4620 17.60%
├── _kernel                                                                                48 0.18%
├── _memory_protection_test_suite.9302                                                            760 2.90%
├── _sw_isr_table                                                                                688 2.62%
├── arch                                                                                1 0.00%
│   └── arm                                                                                1 0.00%
│       └── core                                                                                1 0.00%
│           └── aarch32                                                                             1 0.00%
│               └── cortex_m                                                                        1 0.00%
│                   └── mpu                                                                         1 0.00%
│                       └── nxp_mpu.c                                                               1 0.00%
│                           └── static_regions_num                                                  1 0.00%
├── drivers                                                                                100 0.38%
│   ├── console                                                                                4 0.02%
│   │   └── uart_console.c                                                                          4 0.02%
│   │       └── uart_console_dev                                                                    4 0.02%
│   ├── gpio                                                                                60 0.23%
│   │   └── gpio_mcux.c                                                                            60 0.23%
│   │       ├── gpio_mcux_port0_data                                                               12 0.05%
│   │       ├── gpio_mcux_port1_data                                                               12 0.05%
│   │       ├── gpio_mcux_port2_data                                                               12 0.05%
│   │       ├── gpio_mcux_port3_data                                                               12 0.05%
│   │       └── gpio_mcux_port4_data                                                               12 0.05%
│   ├── serial                                                                                16 0.06%
│   │   └── uart_mcux.c                                                                            16 0.06%
│   │       ├── uart_mcux_0_data                                                                    8 0.03%
│   │       └── uart_mcux_1_data                                                                    8 0.03%
│   └── timer                                                                                20 0.08%
│       └── cortex_m_systick.c                                                                     20 0.08%
│           ├── announced_cycles                                                                    4 0.02%
│           ├── cycle_count                                                                         4 0.02%
│           ├── last_load                                                                           4 0.02%
│           ├── lock                                                                                4 0.02%
│           └── overflow_cyc                                                                        4 0.02%
├── dynamic_regions.9535                                                                          216 0.82%
├── g_xtal0Freq                                                                                4 0.02%
├── g_xtal32Freq                                                                                4 0.02%
├── k_mem_domain_default                                                                          204 0.78%
├── kernel                                                                                922 3.51%
│   ├── init.c                                                                                865 3.30%
│   │   ├── z_idle_stacks                                                                         352 1.34%
│   │   ├── z_main_stack                                                                          512 1.95%
│   │   └── z_sys_post_kernel                                                                       1 0.00%
│   ├── mem_domain.c                                                                                1 0.00%
│   │   └── max_partitions                                                                          1 0.00%
│   ├── mutex.c                                                                                4 0.02%
│   │   └── lock                                                                                4 0.02%
│   ├── sched.c                                                                                16 0.06%
│   │   ├── pending_current                                                                         4 0.02%
│   │   ├── sched_spinlock                                                                          4 0.02%
│   │   ├── slice_max_prio                                                                          4 0.02%
│   │   └── slice_time                                                                              4 0.02%
│   ├── sem.c                                                                                4 0.02%
│   │   └── lock                                                                                4 0.02%
│   ├── timeout.c                                                                                24 0.09%
│   │   ├── announce_remaining                                                                      4 0.02%
│   │   ├── curr_tick                                                                               8 0.03%
│   │   ├── timeout_list                                                                            8 0.03%
│   │   └── timeout_lock                                                                            4 0.02%
│   ├── timer.c                                                                                4 0.02%
│   │   └── lock                                                                                4 0.02%
│   └── userspace.c                                                                                4 0.02%
│       └── obj_lock                                                                                4 0.02%
├── lib                                                                                8 0.03%
│   ├── libc                                                                                4 0.02%
│   │   └── minimal                                                                                4 0.02%
│   │       └── source                                                                              4 0.02%
│   │           └── stdout                                                                          4 0.02%
│   │               └── stdout_console.c                                                            4 0.02%
│   │                   └── _stdout_hook                                                            4 0.02%
│   └── os                                                                                4 0.02%
│       └── printk.c                                                                                4 0.02%
│           └── _char_out                                                                           4 0.02%
├── modules                                                                                8 0.03%
│   └── hal                                                                                8 0.03%
│       └── nxp                                                                                8 0.03%
│           └── mcux                                                                                8 0.03%
│               └── devices                                                                         8 0.03%
│                   └── MK64F12                                                                     8 0.03%
│                       └── fsl_clock.c                                                             8 0.03%
│                           ├── s_fastIrcFreq                                                       4 0.02%
│                           └── s_slowIrcFreq                                                       4 0.02%
├── subsys                                                                                2277 8.68%
│   └── testsuite                                                                                2277 8.68%
│       └── ztest                                                                                2277 8.68%
│           └── src                                                                              2277 8.68%
│               └── ztest.c                                                                      2277 8.68%
│                   ├── cpuhold_active                                                              4 0.02%
│                   ├── cpuhold_sem                                                                16 0.06%
│                   ├── phase                                                                       1 0.00%
│                   ├── test_result                                                                 4 0.02%
│                   ├── test_status                                                                 4 0.02%
│                   ├── ztest_thread                                                              200 0.76%
│                   └── ztest_thread_stack                                                       2048 7.80%
├── tests                                                                                18266 69.60%
│   └── kernel                                                                                18266 69.60%
│       └── mem_protect                                                                         18266 69.60%
│           └── mem_protect                                                                     18266 69.60%
│               ├── build                                                                       11512 43.87%
│               │   └── kobject_hash.gperf                                                      11512 43.87%
│               │       ├── priv_stacks                                                          9504 36.22%
│               │       ├── stack_data                                                             72 0.27%
│               │       └── wordlist                                                             1936 7.38%
│               └── src                                                                          6754 25.74%
│                   ├── common.c                                                                    1 0.00%
│                   │   └── valid_fault                                                             1 0.00%
│                   ├── inherit.c                                                                2808 10.70%
│                   │   ├── _k_fifo_buf_inherit_msgq                                              100 0.38%
│                   │   ├── child_res_pool_ptr                                                      4 0.02%
│                   │   ├── child_thr                                                             200 0.76%
│                   │   ├── child_thr_stack                                                       512 1.95%
│                   │   ├── inherit_buf                                                            32 0.12%
│                   │   ├── inherit_mem_domain                                                    204 0.78%
│                   │   ├── inherit_memory_partition                                               12 0.05%
│                   │   ├── inherit_memory_partition_array                                          8 0.03%
│                   │   ├── inherit_msgq                                                           44 0.17%
│                   │   ├── inherit_mutex                                                          20 0.08%
│                   │   ├── inherit_sem                                                            16 0.06%
│                   │   ├── inherit_timer                                                          56 0.21%
│                   │   ├── kheap_res_pool                                                        128 0.49%
│                   │   ├── parent_res_pool_ptr                                                     4 0.02%
│                   │   ├── parent_thr                                                            200 0.76%
│                   │   ├── parent_thr_stack                                                      512 1.95%
│                   │   ├── parent_tid                                                              4 0.02%
│                   │   ├── res_pool                                                               24 0.09%
│                   │   ├── sync_sem                                                               16 0.06%
│                   │   ├── test_1_stack                                                          512 1.95%
│                   │   └── test_1_tid                                                            200 0.76%
│                   ├── kobject.c                                                                1528 5.82%
│                   │   ├── child_stack                                                           512 1.95%
│                   │   ├── child_thread                                                          200 0.76%
│                   │   ├── extra_stack                                                           512 1.95%
│                   │   ├── extra_thread                                                          200 0.76%
│                   │   ├── kobject_mutex                                                          20 0.08%
│                   │   ├── kobject_public_sem                                                     16 0.06%
│                   │   ├── kobject_sem                                                            16 0.06%
│                   │   ├── kobject_sem_no_init_access                                             16 0.06%
│                   │   ├── kobject_sem_no_init_no_access                                          16 0.06%
│                   │   ├── kobject_sem_not_hash_table                                             16 0.06%
│                   │   └── random_sem_type                                                         4 0.02%
│                   ├── mem_domain.c                                                             2361 9.00%
│                   │   ├── _k_thread_data_zzz_thread                                              48 0.18%
│                   │   ├── _k_thread_obj_zzz_thread                                              200 0.76%
│                   │   ├── _k_thread_stack_zzz_thread                                            256 0.98%
│                   │   ├── child_stack                                                           512 1.95%
│                   │   ├── child_thread                                                          200 0.76%
│                   │   ├── no_access_buf                                                          32 0.12%
│                   │   ├── no_access_domain                                                      204 0.78%
│                   │   ├── no_access_part                                                         12 0.05%
│                   │   ├── num_rw_parts                                                            4 0.02%
│                   │   ├── overlap_part                                                           12 0.05%
│                   │   ├── ro_buf                                                                 32 0.12%
│                   │   ├── ro_part                                                                12 0.05%
│                   │   ├── rw_bufs                                                               448 1.71%
│                   │   ├── rw_parts                                                              168 0.64%
│                   │   ├── spin_done                                                               1 0.00%
│                   │   ├── spin_sem                                                               16 0.06%
│                   │   └── test_domain                                                           204 0.78%
│                   └── mem_partition.c                                                            56 0.21%
│                       ├── bss_var                                                                 4 0.02%
│                       ├── buf_arc                                                                32 0.12%
│                       ├── part_arch                                                              12 0.05%
│                       ├── var                                                                     4 0.02%
│                       └── zeroed_var                                                              4 0.02%
├── uninit_thread.9876                                                                            200 0.76%
├── z_idle_threads                                                                                200 0.76%
├── z_interrupt_stacks                                                                           2080 7.93%
├── z_main_thread                                                                                200 0.76%
├── z_mem_domain_lock                                                                               4 0.02%
└── ztest_mem_partition                                                                            12 0.05%
==============================================================================================================
                                                                                26243

I opened https://github.com/zephyrproject-rtos/zephyr/issues/30591
The extra memory comes from generating privilege mode stacks.

This is 10K overflow, not sure how we are going to get this into 16k of RAM. This board just needs to be excluded from this test IMO.

No, we need Risc V coverage, this is not an appropriate resolution.
There is more simply some more work to do in this test case not to generate so many separate stacks, there are currently 9 in total. CONFIG_PRIVILEGED_STACK_SIZE=1024 so if we don't use so many stacks I think we can shave off 10K.

No, we need Risc V coverage, this is not an appropriate resolution.

sure, but this is not going to be with this board with only 16k of RAM. We have RISCv coverage in emulation on both renode and qemu. For userspace we probably need to pick another board with more RAM and resources, maybe the VEGA board.

@andrewboie which ARM board with 16K works with this test?

frdm_k64f:

frdm_k64f has way more RAM than 16K.

@nashif : I don't have a VEGA board .. can i reproduce it any other way ?

@nashif : I don't have a VEGA board .. can i reproduce it any other way ?

this board might not be right for testing this feature, I was just thinking loud.
TBH, not sure what the bug is. This architecture needs boards both hardware and emulation that would allow testing features that require resources. Right now we do not have many boards support in riscv and those we have either do not support MMU or are low on RAM/Flash.
so I am inclined to just close it and ask for someone to submit a new board configuration that can be used for regression testing or change the configuration of the board or tests to make them fit on the boards we have.

For now, this test is manually ran and succeed on a similar board with more RAM.

which board is that?

It's a FPGA (arty 100t) simulating RISC-V core E34 (looks like hifive1_revb) with 32k (or 64k) RAM and Floating Point Unit support.
I think add a new board to test RISC-V's userspace feature isn't the best solution, it look more like a workaround.
I admit rework the test or RISC-V specific code to fit in 16k RAM could be huge, then do what you want, I just giving my opinion.

Based on the discussion above closing this issue.


[WFCORE-5595][WFCORE-5596][WFLY-15350] Upgrading to JBoss Modules 2.0.0.Final and JAXP refactoring from WFCORE to WF

This pull request upgrades JBoss Modules to 2.0.0.Final version (eliminates JAXP hack that was there for years) and moves
Woodstox, Xerces & Xalan dependencies from WildFly Core to WildFly.
https://issues.redhat.com/browse/WFLY-15350
https://issues.redhat.com/browse/WFCORE-5595
https://issues.redhat.com/browse/WFCORE-5596
This pull request is following up on:
https://github.com/wildfly/wildfly/pull/14768
https://github.com/wildfly/wildfly/pull/14711

Core - Full Integration Build 10962 outcome was FAILURE using a merge of 2aa6d05e2aa42479b01f4f4e2c9d2f32dcfa7c7e
Summary: Tests failed: 1 (1 new), passed: 4072, ignored: 44 Build time: 01:36:57
Failed tests
org.jboss.as.test.layers.LayersTestCase.testServlet: java.lang.Exception: Some unreferenced modules are un-expected [org.apache.xerces, org.codehaus.woodstox]
	at org.jboss.as.test.layers.LayersTest.test(LayersTest.java:109)
	at org.jboss.as.test.layers.LayersTestCase.testServlet(LayersTestCase.java:142)


[CI] add if_no_artifact_found

SSIA

JaCoCo Code Coverage 76.92% :white_check_mark:

Class
Covered
Meta
Status

  Generated by :no_entry_sign: Danger


cmd+n raises "document treated as folder" with no file selected

...on macOS
Sometimes I enter a state where cmd+n no longer works, instead raising this error every time:

When I click the 'new folder' button that workspace shows when there are no open tabs, the 'parent folder' field is set to a document:

However, that document isn't visibly selected, nor is any other file:

Deleting the file fixes the issue

it seems I enter this state whenever I click a file in the file tree that's already open/selected


Scrolling doesn't work properly in latest insider beta

From @warpdesign on April 22, 2017 10:22
This bug-tracker is monitored by developers and other technical types.  We like detail!  So please use this form and tell us, concisely but precisely, what's up.  Please fill out ALL THE FIELDS!
If you have a feature request, please post to the UserVoice.  If you're reporting a BSOD, don't post here!  Instead, e-mail<EMAIL_ADDRESS>and if possible attach the minidump from "C:\Windows\minidump".

Your Windows build number:  (Type ver at a Windows Command Prompt)
10.0.16179

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)
I ran npm installed which produced lots of output text and wanted to scroll up to read the text I missed.

What's wrong / what should be happening instead:
Instead of seeing the output from the command I just typed, I saw output from a command I ran hours ago.

Strace of the failing command, if applicable:  (If <cmd> is failing, then run strace -o strace.txt -ff <cmd>, and post the strace.txt output here)

Copied from original issue: Microsoft/WSL#1984

From @zadjii-msft on April 24, 2017 15:39
Gonna go out on a limb and say this has to do with the scroll margins, again.
MSFT:11647773 currently tracks what I think is this issue, though I'll add this to that bug to make sure they're the same.
@warpdesign any chance that before you ran npm install ..., you had run apt install ...? I'm pretty sure that apt is a reliable repro for this behavior, but I don't know if npm is yet.

From @zadjii-msft on May 30, 2017 22:31
Wadda ya know, I fixed this issue this morning. On it's way out to Insider's now :)

From @Po-wei on May 12, 2017 5:52
I have the same scrolling problem, too. What's more, when I encounter this issue, typing "clear" would let me cannot scroll up(The scrolling bar was fixed on the top, and the previous information was gone.)

From @Po-wei on June 3, 2017 8:11
@zadjii-msft When can i get this update from regular Windows Update?

From @zadjii-msft on June 5, 2017 16:16
If you're not on Insiders, then I think the best I can tell you is SoonTM. It'll  come out with the Fall Creator's Update, but I don't know when that will officially be released.

From @MerkaST on December 6, 2017 23:17
This appears to still happen with the Fall Creator's Update. I'm on build 16299.64 and running an apt install (or remove or autoremove, I'd assume all commands that use the progress bar) command that produces output longer than one window right after opening WSL will exhibit this behaviour, ie. have missing scrollback content.

From @zadjii-msft on December 8, 2017 17:32
Hmmm. Okay so i think I get what's happening. Basically, the "scroll margins" that apt sets are at a fixed point in the buffer. So anything that would scrollback off of it, is just lost instead.
The right way to do this is to probably instead shift the whole viewport down a line (including the buffer-relative margin settings), then scroll the contents of the margins up a line, so that the top line is off of the viewport, in the "scrollback".
Filing a new bug to take a look at this later this release cycle.

I just submitted a bug fix that should fix the issue of apt install output not getting moved into scrollback when it scrolls off the top of the viewport.
Should be in whatever the next official Windows release is called (2Fall2CreatorsUpdate)


ci: Add travis.yml to run flake8

Pending activation of the project by @j0057
See https://travis-ci.org/j0057/github-release

Thanks for integrating


Fix DiscordLogger link

Today I moved DiscordLogger to it's own repository. This PR fixes the DiscordLogger link as well as improving the description of the package.

@swift-server-bot test this please

@swift-server-bot add to allowlist


Prop on  context provider to completely disable TinaCMS

Summary
The TinaCMS Context Provider should have a prop to completely disable all functionality (eg all network requests), not just hide the sidebar. While hiding the sidebar does stop editing of TinaCMS, it still sends unnessary network requests for data.
Basic example
In this example UserProvider is a custom context provider which let me knows if a user is authenicated to provide edits to the website.
    return (
      <UserProvider>
        {({ isAuthenicated }) => (
          <Tina cms={this.cms} disabled={!isAuthenicated}>
            <Component {...pageProps} />
          </Tina>
        )}
      </UserProvider>
    );

Motivation
My use case
I understand that disabling network requests will cause the website not to display the latest changes until the website is rebuild either via Gatsby or NextJS.  This is the exact functionality I want.
For my use-case:
Non-authenicated users should always only see a controlled compiled version of the website and never have access to Tina editing functionality or see edits applied by other users
When an authenicated user makes an edit, my backend automatically creates a branch where all edits are applied and that user will see their own version of the website.
Since 99.99% of site visitors users are unauthenicated, TinaCMS sending these network requests (which will always error) creates unnessarry network overhead.

Implemented via #1170


Icon control

Button control is used to show icons because it has support to colorize the image. Button is packed with more stuff like states, event handling, label... eventually a light component should be used instead. For now, abstract the usage of Button in the new Icon control and use it in trivial places. There are more places where Icon can be used but require more changes, so I'm leaving them for follow-ups.

Forgot to mention that this is a small step in fixing focus navigation since the previous Button instances had by default enabled: true and so were in the focus chain.


Added Shift Click to Abort Offers in the Grand Exchange

Added Shift Click to Abort Offers in the Grand Exchange.
Closes #9102

This should rather maybe be a MenuEntrySwapper option?

This should rather maybe be a MenuEntrySwapper option?

I feel it fits better under the GE plugin, but we'll see what other think. Thanks for the thumbs up!

Yep, you're right. I've made the change. @RALEx147

You also have to hook to the focus lost event since keypresses/releases won't fire when it is out of focus. Look at some of the other plugins which listen for shift.

added in 61a72d5a54798b606e12bb76deaa9ef2c12fb981


adding page transitions

I'm trying to add page transitions to your wonderful template, but they simply don't work. I'm using https://joshcollinsworth.com/blog/build-static-sveltekit-markdown-blog as a guide, and I have no issues getting them to work in that code. Any hints? Thanks

Nevermind i figured it out sorry mate


Avoid unnecessarily importing ctypes

This only really impacts Windows, as I believe most other platforms are going to have getdlopenflags and follow the same path as before, but it allows us to use pyzmq on builds that don't include ctypes.
I think the rest of the logic for those flags can be simplified, but not significantly, and presumably it's working fine.
FWIW, the actual patch I'm using (given I have a known platform) is just import .libzmq as _libzmq instead of the entire function. But if this much is upstream then I don't need to patch pyzmq at all ;)

OK! How do you get Python without ctypes?

@minrk Create your own distribution and don't include _ctypes.pyd ;)
And I know that seems unreasonable for a widespread public distribution, but for within a business, and particularly for production deployments, it's pretty trivial. Most large companies aren't using a publicly available build of Python already, but haven't quite migrated to private builds/forks of all their dependencies. (And you just saved me from having to maintain a pyzmq fork :) Thanks!)


Obstace_avoid  node can not avoid obstacles in a real car.

Bug

Ubuntu version:14.04&16.04
ROS version:indigo&kinetic
Autoware branch:develop

1.Using the Obstace_avoid node and opening the Avoidance option, it is impossible to avoid obstacles in the test of a real car and can only stop before an obstacle.
2.I used the following nodes：
lane_rule;
lane_stop;
lane_select;
obstace_avoid;
velocity_set;
pure_suit;
euclidean_cluster;
points2costmap;
grid_map_filiter;
I can get  /real_cost_map and send it to grid_map,but it's still parked in front of the barrier, not avoiding it.

Hi @Mor-harry,
I'm in a similar situation, did you get a solution?
Thanks

@javcursor Thanks for using Autoware and for your question. However the issue tracker is for posting confirmed bugs and feature requests.
We ask that you please ask questions on the Autoware Discourse category following our support guidelines: https://github.com/CPFL/Autoware/wiki/Support-guidelines. Please pay particular attention to the information we ask you to provide.

Hi @gbiggs I am facing this harsh issue https://github.com/Autoware-AI/autoware.ai/issues/2387 for a Long time.
I have tried a lot off code combination/configuration, joined related nodes and  launch files, modified the planners parameters, checkbox...
However I still was not able to solve this alone, the car does not avoid the obstacle anyway. I am sure you can give me some good advice to find a solution. I have followed your comments on git, slash, ROS answers, etc and I believe you can help, you have a solid knowledge about Autoware modules. Could you assist me on this regard please?


Standardize Git Branches and Tags

It is very common practice, on GitHub and at almost all Azure/Microsoft repositories to use master branch as the upstream (latest working/released version) as well the default branch of the GitHub repository.
Tags are good to use to point to previous released versions.
For tags, something that points to the source code of the specific released artifact and version.
Would be good to standardize it this way.

@brunoborges Thanks for the suggestion.
Just want to double confirm, the action we should take is rename the tags from azure-functions-archetype-v1.11 -> azure-functions-archetype-1.11.
Am I right?

That is the minor suggestion, yes.
Most importantly is to have master being the default branch and the upstream, latest released version.

I see. So we will have two branches:

the default master is the latest released version.
new feature code goes to develop.

Right?

Correct. We could also use feature branch practice for major features.
On Thu, Jul 12, 2018, 19:03 Sheng Chen<EMAIL_ADDRESS>wrote:

I see. So we will have two branches:

the default master is the latest released version.
new feature code goes to develop.

Right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/azure-maven-archetypes/issues/35#issuecomment-404703349,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH6z1adPB2NExL905kwf5INwdso18qDks5uGAAJgaJpZM4VNtNe
.

I see. Will start this pattern from 1.12

@brunoborges Done.


Update grid collapse documentation

Missed removing float: left from docs.

@kgcreative can you rebase this off master. Then it's good to merge

@whmii  👍


chore(feat-multi-module-components): release 0.82.1

:robot: I have created a release beep boop
0.82.1 (2023-08-02)
BugFixes

tflint v0.47.0 fixes (#154) (565466e)

Misc

bump github.com/aws/aws-sdk-go from 1.44.312 to 1.44.314 (#153) (7393a7c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/vincenthsh/fogg/releases/tag/v0.82.1 :sunflower:


[staging] [security] perl524: 5.24.3 -> 5.24.4; perl526: 5.26.1 -> 5.26.2

Motivation for this change
minor update
bugfixes including 3 CVE
https://metacpan.org/pod/distribution/perl/pod/perl5244delta.pod
https://metacpan.org/pod/distribution/perl/pod/perl5262delta.pod

Failure on x86_64-linux (full log)
Attempted: perl526
Partial log (click to expand)
cannot build derivation '/nix/store/dvh690mp30mdp45pj0q94q3y6m6vqzrc-lzip-1.20.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/dwvhgi1pb4009cgz8xdh0ravpfw7qcks-binutils-wrapper-2.30.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/rpxz6pirp0491bsnn5spr7dz1l8vha0k-diffutils-3.6.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/cwx8qk6y4fv3cg0r5clz5fyjk7yfl1la-ed-1.14.2.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/hx5bwhqnpjaq7bcjah4yyz9amnnxq2lr-findutils-4.6.0.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/h7jsanry5wx07bdil3v7hyx48456nnmm-gcc-wrapper-7.3.0.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/35hn510bg7xs8ayy7irych7qkccinhpj-patch-2.7.6.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/99px50wk8abqsb5ncxmlh13shwwhf177-stdenv-linux.drv': 24 dependencies couldn't be built
cannot build derivation '/nix/store/qxb27qqjm8zxv9wfv3gfy06m9bgjfcfl-perl-5.26.2.drv': 3 dependencies couldn't be built
error: build of '/nix/store/qxb27qqjm8zxv9wfv3gfy06m9bgjfcfl-perl-5.26.2.drv' failed

Success on aarch64-linux (full log)
Attempted: perl526
Partial log (click to expand)
gzipping man pages under /nix/store/z8nhfa6rr5vbnjm04ag7cvrlvbd2a2xj-perl-5.26.2-man/share/man/
strip is /nix/store/mv5fc7rnc7pyhckssxzi8qh059j1ch3a-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/z8nhfa6rr5vbnjm04ag7cvrlvbd2a2xj-perl-5.26.2-man
checking for references to /build in /nix/store/z8nhfa6rr5vbnjm04ag7cvrlvbd2a2xj-perl-5.26.2-man...
shrinking RPATHs of ELF executables and libraries in /nix/store/as16h39hlaqkm2h9clhvnzzbvv4cydgb-perl-5.26.2-devdoc
gzipping man pages under /nix/store/as16h39hlaqkm2h9clhvnzzbvv4cydgb-perl-5.26.2-devdoc/share/man/
strip is /nix/store/mv5fc7rnc7pyhckssxzi8qh059j1ch3a-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/as16h39hlaqkm2h9clhvnzzbvv4cydgb-perl-5.26.2-devdoc
checking for references to /build in /nix/store/as16h39hlaqkm2h9clhvnzzbvv4cydgb-perl-5.26.2-devdoc...
/nix/store/hif77l61ws893hr2bgd9k6p8yc7b54xf-perl-5.26.2

@GrahamcOfBorg build perl524 perl526

Failure on x86_64-linux (full log)
Attempted: perl524, perl526
Partial log (click to expand)
cannot build derivation '/nix/store/dwvhgi1pb4009cgz8xdh0ravpfw7qcks-binutils-wrapper-2.30.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/rpxz6pirp0491bsnn5spr7dz1l8vha0k-diffutils-3.6.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/cwx8qk6y4fv3cg0r5clz5fyjk7yfl1la-ed-1.14.2.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/hx5bwhqnpjaq7bcjah4yyz9amnnxq2lr-findutils-4.6.0.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/h7jsanry5wx07bdil3v7hyx48456nnmm-gcc-wrapper-7.3.0.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/35hn510bg7xs8ayy7irych7qkccinhpj-patch-2.7.6.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/99px50wk8abqsb5ncxmlh13shwwhf177-stdenv-linux.drv': 24 dependencies couldn't be built
cannot build derivation '/nix/store/qsyn0bvgkdnsspms84j03z9yp54rc9w2-perl-5.24.4.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/qxb27qqjm8zxv9wfv3gfy06m9bgjfcfl-perl-5.26.2.drv': 3 dependencies couldn't be built
error: build of '/nix/store/qsyn0bvgkdnsspms84j03z9yp54rc9w2-perl-5.24.4.drv', '/nix/store/qxb27qqjm8zxv9wfv3gfy06m9bgjfcfl-perl-5.26.2.drv' failed

Failure on x86_64-darwin (full log)
Attempted: perl524, perl526
Partial log (click to expand)
cannot build derivation '/nix/store/8243zcw7c9p266bpbspqw38kzlvvjv6a-ICU-osx-10.10.5.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/c267805ycdbwdhxc97knhknb1fw2x2gx-cctools-binutils-darwin.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/qvdwwmydr4rf2184p2q9hfk82d79zf7x-gnutar-1.30.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/fy0i4zl1c26i1k5v4ki8ajp77fbr3mz5-CF-osx-10.10.5.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/vb6vfxn0fs5div4i00krpzg4666lajaq-cctools-binutils-darwin-wrapper.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/4p914bh5qhfq212isc5zdz28a7zlbmy4-clang-wrapper-5.0.2.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/1108d2bdrx2a9zdryxicn8z9rxgcxwb1-stdenv-darwin.drv': 36 dependencies couldn't be built
cannot build derivation '/nix/store/3gkphc3m2q3mmi44qwdamywv7kan445y-perl-5.24.4.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/xpm2s2gww5p08n3fp57x1fn3mi9xmiqd-perl-5.26.2.drv': 4 dependencies couldn't be built
error: build of '/nix/store/3gkphc3m2q3mmi44qwdamywv7kan445y-perl-5.24.4.drv', '/nix/store/xpm2s2gww5p08n3fp57x1fn3mi9xmiqd-perl-5.26.2.drv' failed

Success on aarch64-linux (full log)
Attempted: perl524, perl526
Partial log (click to expand)
strip is /nix/store/mv5fc7rnc7pyhckssxzi8qh059j1ch3a-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/z8nhfa6rr5vbnjm04ag7cvrlvbd2a2xj-perl-5.26.2-man
checking for references to /build in /nix/store/z8nhfa6rr5vbnjm04ag7cvrlvbd2a2xj-perl-5.26.2-man...
shrinking RPATHs of ELF executables and libraries in /nix/store/as16h39hlaqkm2h9clhvnzzbvv4cydgb-perl-5.26.2-devdoc
gzipping man pages under /nix/store/as16h39hlaqkm2h9clhvnzzbvv4cydgb-perl-5.26.2-devdoc/share/man/
strip is /nix/store/mv5fc7rnc7pyhckssxzi8qh059j1ch3a-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/as16h39hlaqkm2h9clhvnzzbvv4cydgb-perl-5.26.2-devdoc
checking for references to /build in /nix/store/as16h39hlaqkm2h9clhvnzzbvv4cydgb-perl-5.26.2-devdoc...
/nix/store/fxw38cf7r3jrqsp61xsdn1l3iddyzjsi-perl-5.24.4
/nix/store/hif77l61ws893hr2bgd9k6p8yc7b54xf-perl-5.26.2

Interesting that it timed out on more powerful x86_64 while succeeded on aarch64

Yes, I would have thought rebuilding gcc would time out on aarch64.

Since this contains several CVE fixes I'm going to merge it now.
BTW, should this be backported to 18.03?

Let's see if there will be some regressions first (I built everything in pkgs.perlPackages but there are other perl packages (hydra, ...) and packages which have perl programs as build dependencies)
Anyway, these versions are 2+ months old so there is no ugrency


analyzer: Run package managers in parallel

This is an experiment to execute different package managers in parallel
to check how it influences the analyzer performance.

This change is

Just FYI, in relation to this PR, see this article about Working with Kotlin Coroutines.

A short update: Test show that this change can significantly improve analyzer performance if multiple package managers are used in one project. The downside is that the logs become less readable.
However, as I'm currently focusing on other topics like the PostgreSQL backend it will take some weeks before I find time to continue work on this, so if anyone wants to take over just let me know.

The downside is that the logs become less readable.

That situation probably could be improved by using different loggers per package manager and adjusting our logger pattern to include the logger name.

@mnonnenmacher, you've removed the "WIP" from the title, but the PR is still marked as a draft. I guess it's ready for review now?

@mnonnenmacher, you've removed the "WIP" from the title, but the PR is still marked as a draft. I guess it's ready for review now?

Yes it is, also see: https://github.com/heremaps/oss-review-toolkit/pull/1825


TITLE

Title
Maintainer Month 2023: Behind the scenes with Rushmore Mushambi
Author or authors
Rushmore Mushambi
Description
At SurrealDB, we're keen on celebrating the efforts made by our maintainers. Rushmore Mushambi is a senior software engineer at SurrealDB and is focused on building out and  maintaining our Rust API layer and WebAssembly library. He shares his journey as an engineer, how he got interested n rust, cool projects he's worked on in the past and everything in between.
Resource link
https://surrealdb.com/blog/maintainer-month-2023-behind-the-scenes-with-rushmore-mushambi
Conent type
Blog Post
Related topics
Open source, database, rust

Huge thanks @feranmiokafor1 -- this is live on the website! So glad to see SurrealDB participating this year :)
Here's our asset kit to make it easy for you to share: https://gist.github.com/abbycabs/39f8f8577f2a7dae3a9b1c88b9ff6aeb

@LadyKerr testing notifications!


Resolve syncing conflicts from repo_sync_working_branch to master

Pull request opened by Docs to resolve syncing conflicts from repo_sync_working_branch to master.

Resolve merge conflict.


Add demo/mvp.sh.

This script demonstrates full end-to-end:

Modeling.
a. Collecting training data from NoisePage and TScout.
b. Building models from training data.
c. (demo hack) Inference as a microservice over a REST endpoint.
Forecasting.
a. Collecting workload trace from NoisePage.
b. Extracting query templates, clustering, and building models for said trace.
c. Generating a workload forecast for a given interval.
(unfortunately, the interval is hardcoded and must be manually fixed)
Action planning.
a. Setting up the DBMS with necessary databases, tables, extensions, etc.
b. Loading the same schema as the forecast.
c. Generating TPC-C CREATE INDEX actions.
d. Selecting good candidate actions with an OpenSpiel CFR solver.
e. Applying recommended actions with a Python script.

TODO(WAN):

Need to think about logging and killing nohup'd processes.
Will nap on whether the pipeline can be simplified any further (if step A and step B must always be run together, combine them into one step).
Will re-review and probably merge #21 first, which may come with quick fixups to e.g., database_game.
Probably won't merge this one just yet.

After discussion with @mkpjnx, will wait for forecast default params PR to land before merging. This is so that people do not need to fiddle with parameters to get the MVP script to work.


Pull hardware info from proxmox or Prometheus

Currently machine information is hardcoded, but we want it to be pulled from proxmox which is more maintainable.

This has been implemented on the website: https://cloud.watonomous.ca/machines


Yandex engine not working

$ trans -debug -e yandex  :fr hello
[ERROR] Oops! Something went wrong and I can't translate it for you :(
This is <IP_ADDRESS>-release on Linux with gawk 4.2.1 and fribidi 1.0.5. Translation with google and bing is OK.
$ w3m -dump http://translate.yandex.net/api/v1/tr.json/translate
{"code":410,"message":"Yandex.Translate API v1 is no longer active. Please migrate to API v1.5: https://tech.yandex.com/translate/."}

SID now contains 4 parts instead of 3. I just tuned parsing a bit in my project.

the same issue

Yandex is not working for me too. I get the following message:
[ERROR] Session is invalid
when running this command:
./trans -b -4 -e "yandex" ar:en "اشتريت سيارة جديدة"

Has there been any progress on this issue ?

Has there been any progress on this issue ?

I'm waiting too

trans -e yandex привет
[ERROR] Oops! Something went wrong and I can't translate it for you :(
NOT WORKING ET


Getting a standard pytorch checkpoint from the model zoo .pkl files

I'm interested in loading the pretrained swin on ADE20K into the standard swin transformer implementation. The current file is a pickle file and not in pytorch .pth files format, do you have a script to convert it back to a standard checkpoint file?

Not coming with a handy script like you describe. But I guess you could also try run an inference with a trained mask2former model and insert some where in the codes a line like "torch.save(model.state_dict(), 'checkpoint.pth')" to convert the .pkl file to a .pth file? And taking out the swin weights part should be straight forward. I think mask2former's swin implementation is taken from the official swin repo so the parameter names and sizes should match naturally.

@YellowPig-zp
What is the intended usage of the .pkl files in the model zoo? For instance I am interested in loading the weights of the pre-trained
Mask2Former trained for SWIN Base with IN-22K, i.e. something like:
def build_model(args):
    cfg = get_cfg()
    # for poly lr schedule
    add_deeplab_config(cfg)
    add_maskformer2_config(cfg)
    cfg.merge_from_file(args.config_file)
    cfg.merge_from_list(args.opts)
    cfg.freeze()
    default_setup(cfg, args)
    model_params = mfm.MaskFormer.from_config(cfg)
    model = mfm.MaskFormer(**model_params)
    pre_trained_weights = torch.load(args.opts[-1]) # 'training/model_checkpoints/model_final_54b88a.pkl'
    model.load_state_dict(pre_trained_weights)

But when I do things this way I get a "magic number" error in the torch.load call, I guess it shouldn't be a .pkl file as the OP points out. Any thoughts on how to address this?

Could you please try to use this script? It is the inverse of convert-torchvision-to-d2.py.
if __name__ == "__main__":
    input = sys.argv[1]

    d2_obj = pkl.load(open(input, 'rb'))
    d2_model = d2_obj["model"]

    torchvision_obj = {}
    for k in list(d2_model.keys()):
        old_k = k

        k = k.replace("shortcut.norm", "downsample.1")
        k = k.replace("shortcut", "downsample.0")
        for t in [1, 2, 3]:
            k = k.replace("conv{}.norm".format(t), "bn{}".format(t))
        for t in [1, 2, 3, 4]:
            k = k.replace("res{}".format(t + 1), "layer{}".format(t))
        if k.startswith("stem."):
            k = k[5:]

        print(old_k, "->", k)
        torchvision_obj[k] = torch.tensor(d2_model.pop(old_k), dtype=torch.float32)

    with open(sys.argv[2], "wb") as f:
        obj = torch.save(torchvision_obj, f)
    if obj:
        print("Unconverted keys:", obj.keys())

Usage:
python3 convert-d2-to-torchvision.py model.pkl model.pth

Could you please try to use this script (convert-d2-to-torchvision.py)? It is roughly the inverse of convert-torchvision-to-d2.py (although there are edge cases).
if __name__ == "__main__":
    input = sys.argv[1]

    d2_obj = pkl.load(open(input, 'rb'))
    d2_model = d2_obj["model"]

    torchvision_obj = {}
    for k in list(d2_model.keys()):
        old_k = k

        k = k.replace("shortcut.norm", "downsample.1")
        k = k.replace("shortcut", "downsample.0")
        for t in [1, 2, 3]:
            k = k.replace("conv{}.norm".format(t), "bn{}".format(t))
        for t in [1, 2, 3, 4]:
            k = k.replace("res{}".format(t + 1), "layer{}".format(t))
        if k.startswith("stem."):
            k = k[5:]

        print(old_k, "->", k)
        torchvision_obj[k] = torch.tensor(d2_model.pop(old_k), dtype=torch.float32)

    with open(sys.argv[2], "wb") as f:
        obj = torch.save(torchvision_obj, f)
    if obj:
        print("Unconverted keys:", obj.keys())

Usage
python3 convert-d2-to-torchvision.py model.pkl model.pth
Main edge case / bug discovered
In the original detectron2 module, convert-torchvision-to-d2.py, there is imprecise logic applied:
        if "layer" not in k:
            k = "stem." + k

When I converted a model from pkl to pth and then back to pkl again using these two scripts, all the values were consistent between the files, however some keys in the original models pkl file don't start with stem. and don't have layer in them.
So when you convert backbone.norm1.weight to pth and back again, it becomes stem.backbone.norm1.weight.
I have not done sufficient analysis of detectron2 code to determine the impact of this. My converted-then-inverted model seems to behave fine when training, however.
Will check out in the next week or so, thanks for your help!

No problem, I'm interested in hearing the results of your experiment.


WindowsForm Titlebar and Borders shrink

Hello,
I merge my assamblies using the nuget package.
Since I do that, all Windows Forms with BorderStyle-Property "FixedToolWindow" or "FixedSingle" or "FixedDialog" have a smaller Title Bar and a bit smaller Border Size then normal.
This is how it looks before merge with ILMerge (BorderStyle = FixedDialog):
https://i.imgur.com/2jZ11yh.png
And this is how it looks after ILMerge (BorderStyle = FixedDialog):
https://i.imgur.com/WhB6vVn.png
I am using Visual Studio 2017 on Windows 10. My projects using .Net Framework 4.5.
Do you have any ID how to solve the problem easlily?
Thanks

I've never heard of it causing this kind of problem. As a first step, if you can send me the log file generated when using the /log option, then I can look at that.

Could a manifest or app config be involved?

This is caused by the unexpected change of subsystem version in PE header.

Okay, if you can give me more details then I can look into it.

Here is the log file:
ilmergelog.log
Hope, that you can find the problem.


registration

@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/78970
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" cffa691d5e1c18b1d98ffe354f4c3623d77daec1
git push origin v0.1.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/78970
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 5e5df198311b89e27ab9ca7edb6834c1f8768e31
git push origin v0.1.0


Sfast optimization for T2I , I2I and Upscale models

Implementation was straight forward from the already written code. But the testing took most of the time. Maybe its because my A5000 was slow or something, it would take forever to load and compile the model for sfast.
for T2I most of the models worked.
Best was ByteDance/SDXL_Lightning with total iteration time of 441s, 1st warmup was 386s and second was only 55s. Inference time of 5.10s/it for first image and it sped it up 4.65it/s for subsequent images.
Worst was SG161222/RealVisXL_V4.0_Lightning with total iteration time of unknows, 1st warmup was 1600s and second was was incomplete even after 55minutes. Inference time of unknown for first image and it sped it up unknown for subsequent images.
for I2I I couldnot get SDXL or SD_turbo to work. Neither did timbrooks/instruct-pix2pix.
for upscale the only model available was stabilityai/stable-diffusion-x4-upscaler but that didnt compile with sfast, even single iteration of compile would take forever. I left it for an hour but it only moved couple of steps. So I will need to make more tests to see if the issue is with models or hardware.
Conclusion: some models took insanely long to pre trace so I dont think that would be a good for anyone. Maybe if there was a way to precompile and save to memory so that you could instantly switch between precompiled models instead of compiling it each time you load the models.

This is the testing result for the sfast uptimised models vs normal.


feat: podman support

Proposed changes
This change introduces an ability to use podman container management tool in addition to docker, which remains the default. Podman provides daemonless architecture and allows to run containers in unprivileged mode natively on Linux.
On systems with both docker and podman installed, the CONTAINER_CLITOOL environment variable can be used to choose a desired option.
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[x] I have read the CONTRIBUTING document
[ ] If applicable, I have added tests that prove my fix is effective or that my feature works
[x] If applicable, I have checked that any relevant tests pass after adding my changes
[ ] I have updated any relevant documentation (README.md)

Details on performed tests
Platform / versions, Docker:
Host - MacOS on M1 pro

% sw_vers
ProductName:	macOS
ProductVersion:	12.6.1
BuildVersion:	21G217

% docker version
Client:
 Cloud integration: v1.0.29
 Version:           20.10.21
 API version:       1.41
 Go version:        go1.18.7
 Git commit:        baeda1f
 Built:             Tue Oct 25 18:01:18 2022
 OS/Arch:           darwin/arm64
 Context:           default
 Experimental:      true

Server: Docker Desktop 4.15.0 (93002)
 Engine:
  Version:          20.10.21
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.18.7
  Git commit:       3056208
  Built:            Tue Oct 25 17:59:41 2022
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.10
  GitCommit:        770bd0108c32f3fb5c73ae1264f7e503fe7b2661
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Platform / versions, podman:
Host - Fedora Linux (x86_64)

$ cat /etc/os-release
NAME="Fedora Linux"
VERSION="36 (Cloud Edition)"
ID=fedora
VERSION_ID=36
VERSION_CODENAME=""
PLATFORM_ID="platform:f36"
PRETTY_NAME="Fedora Linux 36 (Cloud Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:36"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f36/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=36
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=36
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
SUPPORT_END=2023-05-16
VARIANT="Cloud Edition"
VARIANT_ID=cloud

$ podman version
Client:       Podman Engine
Version:      4.3.1
API Version:  4.3.1
Go Version:   go1.18.7
Built:        Fri Nov 11 15:24:13 2022
OS/Arch:      linux/amd64

Targets tested with both docker and podman (rootless):

make build-docker
make build-benchmark-docker
make build-txz-packager-docker
make local-txz-package

Targets tested with podman (rootless) only:

make performance-test (fails with docker on M1)

Untested targets:

make test-docker-component (it's unclear from Makefile how to create proper environment)

Additional findings
https://github.com/containers/podman/issues/16969

@PrabhatDixit and @mtbChef do we want to support other container runtimes in make besides docker (devtools)? I think by doing what is in this PR we would need to adjust the naming of make targets that @defanator modified to not use the word docker in them. If we want to do this in a separate effort, should we consider more than Podman? e.g. LXC, ContainerD/runc ?

TWIMC, tested container targets on Fedora 37 host with docker-ce:
$ docker version
Client: Docker Engine - Community
 Version:           20.10.22
 API version:       1.41
 Go version:        go1.18.9
 Git commit:        3a2c30b
 Built:             Thu Dec 15 22:28:45 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.22
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.18.9
  Git commit:       42c8b31
  Built:            Thu Dec 15 22:26:25 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.14
  GitCommit:        9ba4b250366a5ddde94bb7c9d1def331423aa323
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

$ cat /etc/os-release
NAME="Fedora Linux"
VERSION="37 (Workstation Edition)"
ID=fedora
VERSION_ID=37
VERSION_CODENAME=""
PLATFORM_ID="platform:f37"
PRETTY_NAME="Fedora Linux 37 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:37"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f37/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=37
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=37
SUPPORT_END=2023-11-14
VARIANT="Workstation Edition"
VARIANT_ID=workstation

$ uname -a
Linux t480.lan 6.0.16-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Dec 31 16:47:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Everything works just fine when docker is running without selinux support (default mode). If selinux is enabled (daemon.json contains {"selinux-enabled": true}), things are getting worse:
$ make build-txz-packager-docker
Building Local Packager
#1 [internal] load build definition from Dockerfile
#1 sha256:18a33db6857f6a9d9e6d74ceb29822e5ce145bde77f9cca5d64b09e64a28c40a
#1 transferring dockerfile: 98B done
#1 DONE 0.0s
[..]
#5 [base 2/3] RUN apt-get update &&     apt-get install -y make jq gnupg gnupg1 gpgv1 git aptly debsig-verify createrepo-c dnf rpm                        curl gettext-base make monkeysphere libtool unzip libssl-dev libbz2-dev libbsd-dev libarchive-dev liblzma-dev zlib1g-dev
#5 sha256:a99880e9b9825b6cc4c42366a491abb7c6f2ef08d27f5670c0672534455ea1d1
#5 0.244 Reading package lists...
#5 0.254 E: List directory /var/lib/apt/lists/partial is missing. - Acquire (13: Permission denied)
#5 ERROR: executor failed running [/bin/sh -c apt-get update &&     apt-get install -y make jq gnupg gnupg1 gpgv1 git aptly debsig-verify createrepo-c dnf rpm                        curl gettext-base make monkeysphere libtool unzip libssl-dev libbz2-dev libbsd-dev libarchive-dev liblzma-dev zlib1g-dev]: exit code: 100
------
 > [base 2/3] RUN apt-get update &&     apt-get install -y make jq gnupg gnupg1 gpgv1 git aptly debsig-verify createrepo-c dnf rpm                        curl gettext-base make monkeysphere libtool unzip libssl-dev libbz2-dev libbsd-dev libarchive-dev liblzma-dev zlib1g-dev:
------
executor failed running [/bin/sh -c apt-get update &&     apt-get install -y make jq gnupg gnupg1 gpgv1 git aptly debsig-verify createrepo-c dnf rpm                        curl gettext-base make monkeysphere libtool unzip libssl-dev libbz2-dev libbsd-dev libarchive-dev liblzma-dev zlib1g-dev]: exit code: 100
make: *** [Makefile:118: build-txz-packager-docker] Error 1

$ make build-docker
Building Docker
#1 [internal] load build definition from Dockerfile
#1 sha256:2b3a200ebd205cef64500bfdc0351cbc02b2e40d334aeffd6586bf56bfed64e6
#1 transferring dockerfile: 3.18kB done
#1 DONE 0.0s
[..]
#10 [install 6/6] RUN --mount=type=secret,id=nginx-crt,dst=/nginx-repo.crt     --mount=type=secret,id=nginx-key,dst=/nginx-repo.key     set -x     && addgroup --system --gid 101 nginx     && adduser --system --disabled-login --ingroup nginx --no-create-home --home /nonexistent --gecos "nginx user" --shell /bin/false --uid 101 nginx     && apt-get update     && apt-get install --no-install-recommends --no-install-suggests -y                         ca-certificates                         gnupg1                         lsb-release                         git                         wget                         make     &&     NGINX_GPGKEY=573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62;     found='';     for server in         hkp://keyserver.ubuntu.com:80         pgp.mit.edu     ; do         echo "Fetching GPG key $NGINX_GPGKEY from $server";         apt-key adv --keyserver "$server" --keyserver-options timeout=10 --recv-keys "$NGINX_GPGKEY" && found=yes && break;     done;     test -z "$found" && echo >&2 "error: failed to fetch GPG key $NGINX_GPGKEY" && exit 1;     apt-get remove --purge --auto-remove -y gnupg1 && rm -rf /var/lib/apt/lists/*     && nginxPackages="         nginx-plus         nginx-agent     "     && echo "Acquire::https::pkgs.nginx.com::Verify-Peer "true";" > /etc/apt/apt.conf.d/90nginx     && echo "Acquire::https::pkgs.nginx.com::Verify-Host "true";" >> /etc/apt/apt.conf.d/90nginx     && echo "Acquire::https::pkgs.nginx.com::SslCert     "/etc/ssl/nginx/nginx-repo.crt";" >> /etc/apt/apt.conf.d/90nginx     && echo "Acquire::https::pkgs.nginx.com::SslKey      "/etc/ssl/nginx/nginx-repo.key";" >> /etc/apt/apt.conf.d/90nginx     && apt-get install apt-transport-https lsb-release ca-certificates     && apt-cache policy | awk '{print $2" "$3}' | sort -u     && printf "deb https://pkgs.nginx.com/plus/ubuntu/ `lsb_release -cs` nginx-plus\n" > /etc/apt/sources.list.d/nginx-plus.list     && printf "deb https://pkgs.nginx.com/nginx-agent/ubuntu/ `lsb_release -cs` nginx-plus\n" > /etc/apt/sources.list.d/nginx-agent.list     && mkdir -p /etc/ssl/nginx     && cat /nginx-repo.crt > /etc/ssl/nginx/nginx-repo.crt     && cat /nginx-repo.key > /etc/ssl/nginx/nginx-repo.key     && apt-get update     && apt-get install $nginxPackages -y      && rm /etc/ssl/nginx/nginx-repo.crt /etc/ssl/nginx/nginx-repo.key
#10 sha256:56558e156042b9bc3fc02523e328965d15598ec56553420acf40ec61dc88f426
#10 0.246 + addgroup --system --gid 101 nginx
#10 0.269 Adding group `nginx' (GID 101) ...
#10 0.270 groupadd: cannot lock /etc/group; try again later.
#10 0.270 addgroup: `/sbin/groupadd -g 101 nginx' returned error code 10. Exiting.
#10 0.272 Fetching GPG key  from hkp://keyserver.ubuntu.com:80
#10 0.272 + found=
#10 0.272 + echo Fetching GPG key  from hkp://keyserver.ubuntu.com:80
#10 0.272 + apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --keyserver-options timeout=10 --recv-keys
#10 0.304 E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
#10 0.304 Fetching GPG key  from pgp.mit.edu
#10 0.304 + echo Fetching GPG key  from pgp.mit.edu
#10 0.304 + apt-key adv --keyserver pgp.mit.edu --keyserver-options timeout=10 --recv-keys
#10 0.336 E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
#10 0.336 + test -z
#10 0.336 + echo error: failed to fetch GPG key
#10 0.337 error: failed to fetch GPG key
#10 0.337 + exit 1

The failures seem to be related to https://github.com/moby/buildkit/issues/2320. With buildkit disabled, some targets are working (like make build-txz-packager-docker), some are failing with specific features missing, e.g.:
$ make build-docker
Building Docker
Sending build context to Docker daemon  116.4MB
Step 1/16 : ARG DOCKER_IMAGE
[..]
Step 9/16 : RUN --mount=type=secret,id=nginx-crt,dst=/nginx-repo.crt     --mount=type=secret,id=nginx-key,dst=/nginx-repo.key     set -x     && addgroup --system --gid 101 nginx     && adduser --system --disabled-login --ingroup nginx --no-create-home --home /nonexistent --gecos "nginx user" --shell /bin/false --uid 101 nginx     && apt-get update     && apt-get install --no-install-recommends --no-install-suggests -y                         ca-certificates                         gnupg1                         lsb-release                         git                         wget                         make     &&     NGINX_GPGKEY=573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62;     found='';     for server in         hkp://keyserver.ubuntu.com:80         pgp.mit.edu     ; do         echo "Fetching GPG key $NGINX_GPGKEY from $server";         apt-key adv --keyserver "$server" --keyserver-options timeout=10 --recv-keys "$NGINX_GPGKEY" && found=yes && break;     done;     test -z "$found" && echo >&2 "error: failed to fetch GPG key $NGINX_GPGKEY" && exit 1;     apt-get remove --purge --auto-remove -y gnupg1 && rm -rf /var/lib/apt/lists/*     && nginxPackages="         nginx-plus         nginx-agent     "     && echo "Acquire::https::$PACKAGES_REPO::Verify-Peer \"true\";" > /etc/apt/apt.conf.d/90nginx     && echo "Acquire::https::$PACKAGES_REPO::Verify-Host \"true\";" >> /etc/apt/apt.conf.d/90nginx     && echo "Acquire::https::$PACKAGES_REPO::SslCert     \"/etc/ssl/nginx/nginx-repo.crt\";" >> /etc/apt/apt.conf.d/90nginx     && echo "Acquire::https::$PACKAGES_REPO::SslKey      \"/etc/ssl/nginx/nginx-repo.key\";" >> /etc/apt/apt.conf.d/90nginx     && apt-get install apt-transport-https lsb-release ca-certificates     && apt-cache policy | awk '{print $2" "$3}' | sort -u     && printf "deb https://$PACKAGES_REPO/plus/ubuntu/ `lsb_release -cs` nginx-plus\n" > /etc/apt/sources.list.d/nginx-plus.list     && printf "deb https://$PACKAGES_REPO/nginx-agent/ubuntu/ `lsb_release -cs` nginx-plus\n" > /etc/apt/sources.list.d/nginx-agent.list     && mkdir -p /etc/ssl/nginx     && cat /nginx-repo.crt > /etc/ssl/nginx/nginx-repo.crt     && cat /nginx-repo.key > /etc/ssl/nginx/nginx-repo.key     && apt-get update     && apt-get install $nginxPackages -y      && rm /etc/ssl/nginx/nginx-repo.crt /etc/ssl/nginx/nginx-repo.key
the --mount option requires BuildKit. Refer to https://docs.docker.com/go/buildkit/ to learn how to build images with BuildKit enabled
make: *** [Makefile:218: build-docker] Error 1

Since we will now have the option of using docker or podman for running containers, I think it might make sense to rename some of the make targets to make them a bit more generic.
Like for example maybe change make build-docker to make build-container-image and run-docker to run-container. There are some other make targets as well to do with docker that should be renamed as well.
Other than that the PR looks good.

Since we will now have the option of using docker or podman for running containers, I think it might make sense to rename some of the make targets to make them a bit more generic.

@dhurley - addressed this in https://github.com/nginx/agent/pull/158/commits/76db8ae408096a4632b37b113976f7454017574d:
% make | egrep -i "container|image"
  txz-packager-image        Builds txz packager container image
  test-container-component  Run integration tests in container
  benchmark-image           Build benchmark test container image for NGINX Plus, need nginx-repo.crt and nginx-repo.key in build directory
  image                     Build agent container image for NGINX Plus, need nginx-repo.crt and nginx-repo.key in build directory
  run-container             Run container from specified IMAGE_TAG

I think you just need to resolve some merge conflicts.

@dhurley should be done now, just rebased on updated main.

Looks like the integration tests are failing as its looking for a DOCKER_IMAGE environment variable. I think you need to merge the latest from main into your branch and update the integration tests to use the new environment variable BASE_IMAGE.
Here are the relative places where the changes needs to be made.
https://github.com/nginx/agent/blob/main/scripts/docker/nginx-oss/ubuntu/Dockerfile#L1
https://github.com/nginx/agent/blob/main/test/integration/api/docker-compose.yml#L14
https://github.com/nginx/agent/blob/main/test/integration/api/api_test.go#L37
https://github.com/nginx/agent/blob/main/Makefile#L171

@dhurley addressed in https://github.com/nginx/agent/pull/158/commits/ca9c86b54a5e0d5a9e590f0feccfeabb61aaa76f
Probably it would be nice to add a short instruction on mandatory testing steps that must pass before submitting a PR.


Hiding Spellbook tab with active spells [FoundryVTT Magic Items]

If spell is added to a character sheet by FoundryVTT Magic Items module Spellbook tab will be hidden even if there are spells on it. Tested on with default character sheet and Compact DnDBeyond-like 5e Character Sheet. I believe intended behavior would be to have the tab visible if there is any spell present.

As a temporary workaround, you can add an "Ignore this spell" cantrip (or something similar) to characters who have no spells but have magic items that contain spells.
The Magic Items module does some weird things and isn't actually giving the character spells (from a technical, code standpoint), so it may take a while before I have enough time to put in a reasonable fix for this that doesn't break things for people who don't use the Magic Items module.


Remaking CarlaDataProvider and CarlaActorPool into a non-singleton.

Is your feature request related to a problem? Please describe.
Me and my team are working with reinforcement learning and we use CARLA in our training environment. We would like to use carla-simulator/scenario_runner to specify and run scenarios that our agents learn.
In our pipeline, one trainer node connects to many worker nodes - each running CARLA simulator. It means that within one trainer node python process we have multiple carla.Client objects and multiple carla.World objects at once.
Current design of having a static singleton that holds references to carla.World and carla.Actors makes it impossible/hard to use scenario_runner in our project.
Describe the solution you'd like
We could make ScenarioManager accept instances of CarlaDataProvider and CarlaActorPool in the constructor. Those objects could encapsulate world/actors on a class instance level instead of static level.
Those instances could be passed down to Scenario/AtomicBehaviour objects too when necessary.
Describe alternatives you've considered
Currently we have our own code for specifying and running CARLA scenarios.
Additional context
I could implement this feature and submit a PR if you are willing to accept it. Please let me know if you are interested.

Hello @Ajk4 and sorry for the late reply. I was planning on giving you a yes or no answer regarding our interest in this change but at the end, it doesn't make sense, as I haven't even seen your code.
Truth is that we are taking a look at CarlaDataProvider and CarlaActorPool, as they are relatively old and we don't like how they are currently implemented so this comes just at the right time.
For us, PRs don't have to be fully fleshed additions with no flaws whatsoever so I'd suggest to open a PR and we'll discuss in detail whether or not it is a feature we can incorporate. I can't tell you now if it's gonna be merged but we don't have to decide that right now.
In any case, regardless of whether or not the PR is accepted, thank you very much for wanting to contribute with us, I can tell you right now that it is for sure really appreciated.

Well have that in mind. For know we probably will stick to our custom scenario codes. If necessary we'll open a PR!
Thanks

@Ajk4 Hello, I have a similar problem, do you have any good solutions?


Bug paginator with zoom in css

Bug, feature request, or proposal:
Bug
What is the expected behavior?
pop-up when i click on "items per page" should be re-sized and well positionned
What is the current behavior?
pop-up insn't well positionned and not re-sized
What are the steps to reproduce?
https://stackblitz.com/edit/angular-v87lkq
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
See on stackblitz
Is there anything else we should know?
Is there alternatives to re-size all my app to get a zoom of 80%?

Closing as a duplicate of https://github.com/angular/material2/issues/10924.