Simple alarm-panel card

Hi I want to use alarm-panel card with 2 buttons, Schedule and Disarm. I do not understand what needs to be done to have it.
There are some custom stuff that can be configured but not sure how and where, it is very confusing and not a single example how someone did it with custom service or what ever is needed. So far I only see how to do it with arm home and arm away and night, vacation and bypass that throw error.

Do I need to create custom script to have Schedule in alarm-panel?

when adding alarm-panel card, there is only options for home, and away (arm-home, arm-away).
if we need to add another option for geofencing, or schedule

I've the same issue when adding alarm-panel card, there is only options for home, and away (arm-home, arm-away). if we need to add another option for geofencing, or schedule

I guess there is some configuration missing from our side and documentation is not that detailed. Maybe someone reply with some detailed description.

Geofencing or schedule are nor actually a valid mode, they are conditions to switch between modes.
When you set geofencing, the mode is either armed, home or disarmed but geofencing is responsible to switch between them. It is similar using automations in home assistant

So it is not possible to have it as a card for schedule or geofencing?

Let's ask the question other way around, how would you represent geofencing mode in home assistant?

I just want to have 2 buttons that I can use to switch from disarmed to schedule mode and vice versa.

Thennn, just setup 2 buttons on front end and call respective services :-)
eufy_security.alarm_guard_schedule
eufy_security.alarm_guard_geo

But as i described earlier, scheduled is not an actual state, it is a rule config to set the state automatically, so you won't see it here. You can only see real states as disarmed, armed away, armed home and 3 more custom states.

I will create a new sensor to expose the rule state as None, Schedule or Geofencing

I will create a new sensor to expose the rule state as None, Schedule or Geofencing

Hi, any news?


reqwest website

👷 Deploy Preview for aquamarine-gaufre-967570 processing.

Name
Link

🔨 Latest commit
98c3ff07529133c70d0a5e2d2f6a7da72a4f155a

🔍 Latest deploy log
https://app.netlify.com/sites/aquamarine-gaufre-967570/deploys/650ee4ab0cf65e0008c149ec


Missing support for *_proxy environment variables

Guzzle is missing lowercased version of proxy variables. According to https://unix.stackexchange.com/a/212972, the *_proxy variables used to be named in lowercase.
Is this intentional from guzzle?
If no, I will submit a PR to add support for lowercased *_proxy variables.

Good question, I have no idea if it's intentional. I will have to check, but currently I am more focused on releasing 6.3.


Move Radmin.VPN 1.1.4394 to Famatech.RadminVPN 1.1.4394

Microsoft Reviewers: Open in CodeFlow

Possible duplicate package entry.
Similar installer SHA256 hash found in manifest:

InstallerSha256: a4b32eb102f693c37fba3aaafa262560648408a345936124a2af751ab0bf182e

manifests\r\Radmin\VPN\1.1.4394

Verify by hash.


Cadence VSCode extension conflicts with VSCode bracket colorization

Problem
Bracket colorization is not respected when editing Cadence files.
i.e.
   "editor.guides.bracketPairs": true,
   "editor.bracketPairColorization.enabled": true,

Steps to Reproduce
Open any .cdc file:

You'll notice brackets are not highlighted, nor colored.
Expected result (taken from a non-cdc file):

Acceptance Criteria
Brackets should be colorized.
Context
VSCode extension version: v1.0.4
Other system info:
  System:
    OS: macOS 12.0.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 105.42 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.13.2/bin/yarn
    npm: 8.15.1 - ~/.nvm/versions/node/v16.13.2/bin/npm
  Managers:
    Homebrew: 3.6.1 - /opt/homebrew/bin/brew
    pip3: 22.2.2 - /opt/homebrew/bin/pip3
    RubyGems: <IP_ADDRESS> - /usr/bin/gem
  Utilities:
    Make: 3.81 - /usr/bin/make
    GCC: 13.1.6 - /usr/bin/gcc
    Git: 2.34.0 - /opt/homebrew/bin/git
    Clang: 13.1.6 - /usr/bin/clang
    FFmpeg: 5.1 - /opt/homebrew/bin/ffmpeg
  Servers:
    Apache: 2.4.48 - /usr/sbin/apachectl
  Virtualization:
    Docker: 20.10.11 - /usr/local/bin/docker
  IDEs:
    Nano: 2.0.6 - /usr/bin/nano
    VSCode: 1.71.2 - /usr/local/bin/code
    Vim: 8.2 - /usr/bin/vim
    Xcode: /undefined - /usr/bin/xcodebuild

We probably need to tokenize the braces as special tokens. Maybe use the scope inspector (https://code.visualstudio.com/api/language-extensions/syntax-highlight-guide#textmate-tokens-and-scopes) to look at a file (JS?) where it works and see how it differs.
This seems like a very low priority issue though.


Add more LLMs as judges

Add judges for metrics to assess conversation quality on (1) Grounded: Every substantial claim in the response of the model is derivable from the content of the document. (2) IDK: Does the model response say I don't know?

It seems like your example is crashing the tests for some reason so, just exclude it from the examples tests in the tests/test_examples.py

ok, I have fixed this. I am not sure how to resolve the DCO check now?

Thanks @eladven I just updated the examples.rst. Pls lmk if it is sufficient.


Support User Defined Table Function

Which issue does this PR close?
Closes #7926
Rationale for this change
This is a draft PR to show how to implement User-Defined-Table Function.
It remains a lot of things to do, but maybe it's a good start.
Such as:

Internal Table Defined Function
More input functions types
More friendly register
...

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

@alamb  PTAL, a draft implementation of user-defined-table-function  : )

Thank you @Veeupup  -- I am very excited to check this out. I plan to do so tomorrow if possible (though it is a holiday in the US so it may not be until Friday or the weekend)

Happy Thanksgiving!! Enjoy your holiday!
I'll checkout your constructive comments later today when I'm free : )

cc @yukkit  hi, this PR is almost ready for review, comments are welcome!

Should we start a new issue to support table function inputs with Expr::Column and more complicated Expr?  @alamb
I can make some trials later.

I took the liberty of merging this branch up from main. If the tests pass I'll plan to merge it. While waiting I will likely file follow on tickets

I filed https://github.com/apache/arrow-datafusion/issues/8383 to track follow on work. Is there any other specific improvement that we discussed that isn't covered?

🚀


[AutoComplete] with  gives error about disableFocusRipple prop

Problem description
Using an AutoComplete whose datasource has an item as follows...
{ text: '', value: <MenuItem disabled={true} primaryText='No results found.'/> }
...the item is correctly displayed, and not selectable, but the following is thrown:
Warning: Unknown prop `disableFocusRipple` on <div> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
    in div (created by ListItem)
    in div (created by ListItem)
    in ListItem (created by MenuItem)
    in MenuItem (created by MyThingyHere)
    in div (created by List)
    in List (created by Menu)
    in div (created by Menu)
    in ClickAwayListener (created by Menu)
    in Menu (created by AutoComplete)

Note, the filter is disabled and dataSource is filtered based on the search text, via API call.
I believe the error is caused by a combination of the cloning happening here, where disableFocusRipple is passed to the MenuItem: https://github.com/callemall/material-ui/blob/master/src/AutoComplete/AutoComplete.js#L431
...it's then passed to the ListItem: https://github.com/callemall/material-ui/blob/master/src/MenuItem/MenuItem.js#L292
...before finally being passed to the <div/> in the case of disabled==true here: https://github.com/callemall/material-ui/blob/master/src/List/ListItem.js#L364
I believe the fix is to:

"Grab" the disableFocusRipple prop here: https://github.com/callemall/material-ui/blob/master/src/List/ListItem.js#L496
Add disableFocusRipple to the docs for ListItem (with a note about only applying if not disabled)
Pass the prop through to the EnhancedButton here: https://github.com/callemall/material-ui/blob/master/src/List/ListItem.js#L652

If that all sounds correct and complete, let me know and I'll try my hand at a PR. Thanks :)
Steps to reproduce
As above
Versions

Material-UI: 0.15.4
React: 15.3.0
Browser:  Google Chrome 52.0.2743.116

Just encountered exactly the same issue with AutoComplete and disabled MenuItem.

My offer to fix this is still there, just looking for some confirmation of approach from a developer on the project..

any update on this?

Still happy to help fix if my outlined approach was good..

Closed by #4783


fscache: enable log-level settings

Log-level settings not work for fscache so add "--log-level" in fscache args to fix it.

Codecov Report

Merging #64 (c16b2f4) into main (c9cb582) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #64   +/-   ##
=======================================
  Coverage   32.00%   32.00%
=======================================
  Files          19       19
  Lines        1484     1484
=======================================
  Hits          475      475
  Misses        934      934
  Partials       75       75

Continue to review full report at Codecov.

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


fix: ConnOpenTry handshake from cosmos to sovereign

Closes: #331
Description

PR author checklist:

[ ] Added changelog entry, using unclog.
[ ] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[ ] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).
[ ] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

Now, the test fails at proof verification. Need to debug this by comparing the ConsensusState stored at Sovereign and the Header queried at the height corresponding to the ConsensusState.

Currently this requires correct state root hash update from sovereign to cosmos.
This is fixed at informalsystems/hermes-sdk#359.

Currently, it fails, as the consensus state doesn't match at counterparty chain - as we're using dummy header.
https://github.com/informalsystems/hermes-sdk/blob/f4111975fafba7a280f840eeaa02eb44b7c35425/crates/sovereign/sovereign-chain-components/src/cosmos/impls/sovereign_to_cosmos/client/update_client_message.rs#L50-L55
We have to build the header with proper AggregatedProofConfig.

My above explanation is wrong. The problem is actually in sovereign-ibc. Only commitment root is stored at ConsensusState - so other fields don't matter.
Currently, sov-ibc creates Sovereign rollup commitment root from Celestia header hash - this is incorrect and probably done before as dummy value.
We need to find how we retrieve this value. The begin_slot_hook comes with a pre_state_root: Root which can be converted to [0; 32]. Currently, we are updating the wasm client with user_hash as commitment root. We need to verify what value we get at [u8; 32]::from(pre_state_root).

I had to bring back -1/+1 in chain status query and proof fetching for sovereigh rollup - as we have to be consistent with the host consensus state storage at sovereign-ibc.
For now, this works with current sovereign-ibc implementation with sovereign-sdk-wip. Although, I am still not sure, if we are missing anything because we don't validate the aggregated proof at sovereign-ibc.


bug: ERROR importing cache manifest from docker.io/tensorchord/python-cache:envd-v0.3.43                                                                          1.8s

Are you use the envd server?

[ ] Yes, I am using the envd server.
[X] No, I am not using the envd server.

Describe the bug
envd cannot use the cache as expected.
To Reproduce
Any config and run envd up
Expected behavior
No response
The docker info output
Not related to docker
The envd version output
envd: v0.3.43
BuildDate: 2023-12-28T03:24:08Z
GitCommit: 3394589f9b57fd12d87661692c73564ba9f10eee
GitTreeState: clean
GitTag: v0.3.43
GoVersion: go1.19.10
Compiler: gc
Platform: linux/amd64
Additional context
No response

Not sure why the release action failed to download the artifacts. Will create a new release after #1837 is merged.

fixed in #1837


fix(package.json): support react > 16.8

:tada: This PR is included in version 3.12.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Grid - "Page indicator box" partially hiding the "page number" (three digit case)

Hi, Mr. Atanasov.
This is just another secondary issue (...as always, from my cases...).
Issue subject and the attached picture tell the most.
Is there any chanche to enlarge the page indicator box (e.g.: by some supplementary .css) / is it auto resizing / what else?
Note I am using Gijgo ver. 1.9.6.
I don't remember i had same issue using previous versions of Your framework.
Still, I can verify if needed.
Thanks for Your attention. Regards,
Francesco.

Thanks a lot, Mr. Atanasov!!!

p.s.: of course, I'd have analogue request for "total number of pages" indicator box....))))
Thanks a lot for Your huge patience...


'morph_stats' output: just one output for morphology files equally named but with different extensions

Recent versions of NeuroM do not include the extension of the original morphology files in their morph-stats output . Example:
When running morph_stats on a directory with 2 files C230300D1-rep-cor.h5 and C230300D1-rep-cor.swc:

the output file contains information about just one instead of two cells
the extension of the source file is not included

{
"C230300D1-rep-cor": {
"axon": {
"max_section_branch_order": 15,
"total_neurite_length": 14302.22999937718,
"total_number_of_neurite": 1
},
"basal_dendrite": {
"max_section_branch_order": 3,
"total_neurite_length": 2398.5855940959173,
"total_number_of_neurite": 7
},
"total_soma_radius": 12.9966
}
}

Done via #909


Upgrade dependencies for v4 release

This issue is to document the status of dependencies of Ontop for the v4 release.
The following have been achieved:

[x] Most of the direct dependencies have been upgraded to the latest versions.
[x] All the Maven build plugins have been upgraded to the latest versions.
[x] Maven wrapper (mvnw) has been upgraded to v3.6.3.
[x] All the security alerts by Github have been cleaned up.
[x] The dependencyConvergence rule is now configured in maven-enforcer-plugin to enforce unique version for each dependency (https://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html)

The following dependencies have to be locked to old versions:

jdk is locked to v8.0 due to Protégé
owlapi is locked to v4.5.9 due to Protégé
guava is locked to v18.0 due to Protégé
jsqlparser is locked to v3.1. Some JUnit test cases fail for v3.2
h2 is locked to v1.4.196 (the latest version has a number of issues for unit testing)

v1.4.200 and v1.4.199 caused issues in tests in ontop-cli:
org.h2.jdbc.JdbcSQLNonTransientException: The database is read only; SQL statement: ALTER TABLE PUBLIC."tb_bk_gen" ADD CONSTRAINT PUBLIC."fk_bk_gen" FOREIGN KEY("id_bk") REFERENCES PUBLIC."tb_books"("bk_code") NOCHECK [90097-200]
v1.4.196 has an issue for supporting GROUP_CONCAT:
org.h2.jdbc.JdbcSQLException: Function "LISTAGG" not found.
These tests have been temporarily ignored.

Closed by d88fc9f5fc8cb93de0190cfbf61932c0fab9d46b


this is not preserved when extracted to function in module scope

TypeScript Version:  3.9.6

Search Terms: extract to function, this
Code
function test(this: any, foo: string) {
  console.log(this.name);
  console.log(foo);
}

Select these two console.log and extract them to function in module scope.
Expected behavior:
this should be passed to newFunction
function test(this: any, foo: string) {
    newFunction(this, foo);
}

function newFunction(context: any, foo: string) {
    console.log(context.name);
    console.log(foo);
}

Actual behavior:
this in newFunction is undefined now.
function test(this: any, foo: string) {
    newFunction(foo);
}

function newFunction(foo: string) {
    console.log(this.name);
    console.log(foo);
}

Playground Link:
Seems Refactoring is not supported on TypeScript Playground.
Related Issues:

webstorm is working as expected.


nuitka is detected as PUA.Python.Nuitka/Trojan.Nuitka.Script.24 in virustotal even if py file is fud

i used nuitka 1.4.8 including 1.2.7 but i got 12 detections in virustotal on every version of nuitka other modules for nuitka are ccache 4.7.4  zstandard 1.5.4 and i used py -m nuitka --onefile --windows-icon-from-ico=  main.py command with python 3.10.10

This is a duplicate, if you do things correctly, it will work. The information how to do it, is behind the Nuitka commercial paywall though. If you want, you can get in touch with virus vendors and have them explain to you what your options are as well.

but i didnt use no console command so how does it get more detections than pyinstaller


data/make_data_loader.py not included in repo

I'm trying to train the baseline model on dukeMTMC-reid and when I follow the README.md instructions I see the error:
$ python3 tools/train.py --config_file='configs/softmax_triplet_with_center.yml' MODEL.DEVICE_ID "('0')" DATASETS.NAMES "('dukemtmc')" OUTPUT_DIR "('dukemtmc-reid_0')"

Traceback (most recent call last):
  File "tools/train.py", line 15, in <module>
    from data import make_data_loader
ImportError: cannot import name 'make_data_loader'

It seems like make_data_loader.py was not included in the github repo, both tools/train.py and tools/test.py reference make_data_loader.

@Oewyn I am sorry! I forgot to upload it. Please 'git pull' and try again.
I recommend that you save the dataset in another folder and input the file path into the configure file.


Not able to validate the elements of policy json with TC v 1.2.x

Description :
Not able to drill down to each element in a policy JSON
To Reproduce

<Either a sample terraform code, or your terraform plan file if it doesn't have any confidential information>

resource "aws_sns_topic" "test" {
  name = "my-topic-with-policy"
}

resource "" "default" {
  arn = aws_sns_topic.test.arn

  policy =<<POLICY

  {
  "Statement": [{
    "Sid": "Statement1",
    "Effect": "Allow",
    "Principal": {
      "AWS": "111122223333"
    },
    "Action": ["sns:Subscribe"],
    "Resource": "arn:aws:sns:us-east-2:444455556666:MyTopic",
    "Condition": {
      "StringEquals": {
        "sns:Protocol": "https"
      }
    }
  }]
}
POLICY
}

<Used terraform-compliance parameters>

terraform-compliance -t C:\Terraform\0.12.26\terraform.exe -f C:\TC_Rules -p C:\TF_Templates\plan.json
3.
Python
4.

<Your feature/scenario/steps>

Scenario: sns topic policy should not allow * principal - test1
       Given I have aws_sns_topic_policy defined
	When it contains policy
	And it contains Statement
	And its Effect is Allow
	Then it must contain Principal
	And its value must not match the "\*$" regex

Scenario: sns topic policy should not allow * principal - test2
       Given I have aws_sns_topic_policy defined
	When it has policy
	And it has Statement
	And its Effect is Allow
	Then it must contain Principal
	And its value must not match the "\*$" regex

Scenario Outline: sns topic policy should not allow * principal - test3
       Given I have aws_sns_topic_policy defined
	When it has policy
	Then it must contain policy
	Then it must contain Statement
	Then it must contain <key>
	And its value <condition> match the "<value>" regex

Examples:
| key        | condition    | value    |
| Effect     | must         | Allow    |
| Principal  | must not     |  ^\*$    |

Expected behavior :

I expect that the Scenario2 would PASS
Tested versions :

<terraform-compliance version (terraform-compliance -v)>
terraform-compliance v1.2.7 initiated
<terraform version (terraform -v)>
Terraform v0.12.26

provider.aws v2.67.0

<python runtime version, if running as a python package (python --version)>
Python 3.8.2
Additional context

I may be missing something, but not quite sure how to validate elements of a policy, especially the elements inside Statement?
ex: I would want to check if Principal is * only when Effect is Allow, but right now, I dont see a way to do that check
any help is greatly appreciated.

please see the attached plan json
plan.json.txt

Hi @vrbcntrl,
This issue revealed a number of bugs, hence the messy activity log.
With 1.2.10, all scenarios seem to be working on my machine.
Scenario Outline: sns topic policy should not allow * principal - test3
       Given I have aws_sns_topic_policy defined
	When it has policy
	Then it must contain policy
	Then it must contain Statement
	Then it must contain <key>
	And its value <condition> match the "<value>" regex

Examples:
| key        | condition    | value    |
| Principal  | must not     |  ^\*$    |

Will not pass because Scenario outline examples are escaped an additional time before interpreted as regexes.
| Principal  | must not     |  ^\\*$    |

Would check for the regex ^\*$ as intended.
Could you give these a try?

Hi @Kudbettin ,
Sorry for the delay in my reply.
Thank you for the input, as per your suggestion, I actually ended up using the below Scenario
Scenario: sns topic policy should not allow * principal - test4
        Given I have aws_sns_topic_policy defined
	When it has policy
	Then it must contain policy
	Then it must contain Statement
	When its Effect is Allow
	Then it must contain Principal
	And its value must not match the "\*$" regex


Modelbinding with JSON data

Having problems getting model binding to work with an API endpoint that's receiving JSON data. Looking at the MusicStore SPA example code I can see that there's a no parameter API endpoint and then simply using TryUpdateModel().
Tried this in my own example, but I'm unable to make this work.
        public async Task<Album> Album()
        //public async Task<Album> Album([FromBody] Album postedAlbum)
        {
            int id = 3;// postedAlbum.Id;

            Album album = null;
            if (id < 1)
                album = context.Albums.Add(new Album());
            else
            {
                album = await context.Albums
                    .Include(ctx => ctx.Tracks)
                    .Include(ctx => ctx.Artist)
                    .FirstOrDefaultAsync(alb => alb.Id == id);

                if (album == null)
                    throw new ApiException("Invalid album id", 404);
            }

            // ModelBinding doesn't work right at the moment
            if (!await TryUpdateModelAsync(album, null))
                throw new ApiException("Model binding failed.", 500);

            int result = await context.SaveChangesAsync();

            return album;
        }

TryUpdateModelAsync() doesn't fail but it also doesn't update anything. Modelstate is empty.
I've also tried updating by using the parameter - that works - the parameter gets set, but then ModelState still contains no data at which point I can manually update.
I would expect model state to be set in either scenario but currently I don't see ModelState set from JSON data.

We are planning to resolve this with #1776, the actual work is tracked by #1654 and #1642, we don't plan to build a mapper in the system, we verified our scenarios with AutoMapper on the desktop framework. When AutoMapper becomes available to CoreCLR it will enable the scenario there as well


inline-block mixin defined above linear gradient breaks linear gradient

http://cl.ly/3j0714181h121x192V1E
Chrome and Firefox won't acknowledge linear-gradient when inline-block is defined first. Difficult for the programmer to debug.

I have looked at this a lot this morning and I think it was an issue with the browser and not the mixins, It has yet to show it's face so I think we can close this out. Appreciate you looking into this Dan.

I assume this was on a non-rails project? When you used the sass --watch command you may have forgotten to pass in the required flag to make bourbon's mixins work properly. Based on the screenshot, it appears as if the compact() function didn't get properly executed when sass compiled the linear-gradient mixin. See here: http://cl.ly/EJCt
I cannot reproduce this issue therefore I am closing it. Please let me know if this reoccurs.


Friend enc failure

Re-encrypts single-segment application messages when the network seqnum has changed, to avoid encrypting messages with different seqnums in network and transport. This operation is only required for unsegmented messages, as segmented messages don't need to use the same seqnum in network.
Fixes #19265.

@menglingao1997 FYI

I'll pull out the all-nodes commit and make a separate PR if we decide we want to do it.


messense/rust-musl-cross:x86_64-musl is not x86_64-unknown-linux-musl target.

Thanks for your work on this. A very usefull docker image to build musl target.
But recently, I find that messense/rust-musl-cross:x86_64-musl is not x86_64-unknown-linux-musl target. It shows x86_64-unknown-linux-gun in my wsl2 kali  roling linux.

It shows x86_64-unknown-linux-gun in my wsl2 kali roling linux.

What do you mean by this? What show that? Can you give a list of steps to reproduce?

@messense
It can reproduce by following steps:

create command aliasalias rust-musl-builder='mkdir -p .cargo/registry && mkdir -p .cargo/git  && podman run -it -v "$(pwd)/.cargo/registry":/root/.cargo/registry -v "$(pwd)/.cargo/git":/root/.cargo/git -v "$(pwd)":/home/rust/src messense/rust-musl-cross:x86_64-musl'

run  command rust-musl-builder
list toolchains

I think you misunderstood the difference between toolchain and target.

https://rust-lang.github.io/rustup/concepts/toolchains.html
https://rust-lang.github.io/rustup/cross-compilation.html

Thanks!


A11y - Cell toolbar & Markdown toolbar - Enter after selecting Delete or Hide/Show Preview does nothing

Azure Data Studio Version: 1.23.0

Steps to Reproduce:
Test using Narrator in Windows:

Add a new cell.

Navigate via keyboard through the cell toolbar icons to the Delete icon.

Hit Enter.
Result: Nothing happens

Navigate from there to the Move cell up and hit Enter.
Result: Cell is deleted. (Cell should have moved up)

Add a new cell.

Navigate via keyboard through the cell toolbar icons to the Move cell down icon.

Hit Enter.
Result: Cell is moved up. (Cell should have moved down)

FAILURE

Test using VoiceOver in MacOS X:

Add a new cell.
Navigate via keyboard through the cell toolbar icons to the Delete icon.
Follow screen reader prompt to use Ctrl-Option-Space
Result: Success
Navigate via keyboard through the markdown toolbar icons to the Hide/Show Preview icon.
Follow screen reader prompt to use Ctrl-Option-Space
Result: Success

SUCCESS

Test on Win or Mac without screen reader:

Add a new code or text cell.
Navigate via keyboard through the cell toolbar icons to the Delete icon.
Hit Enter.
Result: Nothing happens
Navigate via keyboard through the markdown toolbar icons to the Hide/Show Preview icon.
Hit Enter.
Result: Nothing happens

The above are results on Mac or PC when NOT using the screen reader. This may be acceptable; we should check with the a11y team on this.

@chlafreniere I'm moving this into the June milestone as part of our cleanup of a11y issues, could you see if this is still relevant and whether it meets the bar for fixing?

bulk closing the usability level issues since we are not planning to work on it anytime soon.


[Bug (Maybe)] Kill Increase When a Criminal Kills

In the past, +kill was not earned when a criminal was killed.
eg fix;
old:
	else if ( NotoThem != NOTO_GUILD_SAME )
	{
		// I'm a murderer !

new:
	else if ( NotoThem < NOTO_NEUTRAL && NotoThem != NOTO_GUILD_SAME )
	{
		// I'm a murderer !

The codes here are purely examples. Although many have been tested, some may need to be rewritten.

Maybe a ini setting would be good here to edit default behavior, and an override in a trigger could be useful

is the request to add a kill to a player who kills a criminal? that's not typically how UO works, since a kill is a murder, and you cannot 'murder' someone who is committing criminal actions. this sort of custom behavior could be achieved in the scripts as well.

Here i think we have a "little problem"
In the original UO content. Kills are only earned if the killed mark the murder count
https://uo.com/wiki/ultima-online-wiki/player/the-murder-system/
but in the website say
If the victim dies before the criminal flag timer ends, the attacker is guilty of murder, regardless of whether he actually administered the killing blow. This includes damage inflicted by pets or summons.
so criminal kills dont earn kills

Closed, this work fine. Maybe implement the feature of Report murder system


Hello , no error , just a question

I was wondering if it was possible to disable the chat message upon joining
Thanks in advance !

Buy the ad free version

Buy the ad free version

or just remove the lines including it 💀


Option to remove a notification?

Is there a way to remove/hide a notification? (or if not, could it be added)
i.e. alerter/terminal-notifier (https://github.com/vjeantet/alerter) has a "-remove" option which allows the code to clear/hide a notification(s) that it had previously issued.
This would be super handy if the application is reporting a transient issue which it could then recover from, etc.

Extending this request -- would also be useful to be able to re-issue a notification, that replaced the a previous one issued.
This would mirror the functionality offered by the -groupid option in Alerter/Terminal-Notifier.


feat: Add typescript definitions

As suggested in https://github.com/domoritz/leaflet-locatecontrol/pull/357#issuecomment-2514216228. After this project was made ESM-ready (very nice!) the suggested way of importing this project is not supported in TypeScript because the TS definitions don't exist in this repo, and the ones from DefinitelyTyped still assume the L.Control.Locate global.
Considering the L.Control.Locate global only exists in the UMD bundle but not in the ESM bundle, i chose the approach to default to ESM structure in the TS definitions in this repo. @types/leaflet.locatecontrol will still exist for the possibility to use the L.Control.Locate global in the UMD bundle. This might not be acceptable, so i'm looking for feedback on this. Maybe it is better to support both.

Merged manually. Thanks!


Try to resolve module before checking imports

Fixes #20576
Use-case 1:
import "./foo";

No importClause.name nor importClause.namedBindings, no branch is reached that tries to resolve the module.
Use-case 2:
import {} from "./foo";

No importClause.name, has importClause.namedBindings but it's empty, no branch is reached that tries to resolve the module.
Notes:

The only test changed is what seems to have been a false positive.
Other tests have their baseline updated, as all new errors thrown are valid and correct, without impairing the underlying test cases as far as I can tell
Although the in the issue it is stated use-case 1 is handled correctly by emitting an error, I confirmed in both 2.6.2 and 2.7.0-dev.20171213 that it is not the case.

I missed the other PR opened for this issue. I'll leave this open for now because of the additional use-case fix.


New sample for microprofile-config-api usage

This is a new sample for microprofile-config-api usage.
Please review and give me a feedback, if this sample is properly implemented and can be used as a sample for eclipse/microprofile-samples repository.
How to build: mvn clean install -Phammock
How to run:     java -DallowedUsers="het:mypass" -DlistAllConfigAllowed="true"  -jar .\config-1.0.0-SNAPSHOT-hammock.jar
How to access:

http://localhost:8080/list/all
Returns all config sources along with their set configurations, if listAllConfigAllowed configuration property is set to true
http://localhost:8080/list/users
Returns all users provided by allowedUsers configuration property
http://localhost:8080/list/source/<name>
Returns all configurations of the given config source

This is the first draft of the microprofile-sample-config project.
Changes:

Initial check in of new microprofile-sample-config
Update hammock version to 2.1
Had to add additional dependencies to new sample because ClassNotFoundExceptions occurred during startup
Added capsule-maven-plugin (commented out) which could replace maven-shade-plugin

Thanks for your contribution! Can you please fix the ip-validation? You need to sign off Eclipse Contribution Agreement. When you commit, you need to specify -s to sign off your contribution.


Documentation: Extend html-formatter and CustomRendering

Documentation request:
Please add some examples on how to implement our own html-formatter based on the existing one.
It is difficult to understand how to properly use the "CustomRendering" to change the way different parts are rendered.
Describe the solution you'd like
A complete step-by-step guide that explains how to extend the html-formatter and how to override different elements' rendering.
Thank you for your help.

I would like to see some examples too please!
Should I write my own version of CucumberHtmlStream and somehow inject a CucumberReact component there so I can set the suggested customRendering attribute? I found this in cucumber/react-components:
<CucumberReact customRendering={{
  DocString: (props) => (
    <>

I am going to render this doc string in a textarea:

      <textarea>{props.docString.content}</textarea>
    </>
  )
}}>
  <GherkinDocument />
</CucumberReact>

I am not a react developer and I don't really know what to do with this information (especially how is this going to get into my report).
Any help?
(by the way @aurelien-reeves your links are pointing to nowhere now)

Hey @sashokbg @zbirizdo, sorry for the late reply.
To give a little background, the motivation for making the components customisable was to layer on some extra functionality in the Reports service https://reports.cucumber.io/. We wanted to do this with a nice pattern that would Pitt finally be useful to other consumers, but I’d say it’s somewhat incomplete - as you’ve noted, currently you’d need to essentially reimplement the html-formatter module.
Would you mind elaborating a bit in the use cases you have and how you want to change/extend the output? Depending on what they are we may be able to support them in other ways eg configurability.

Hi @davidjgoss, sorry for the late reply on my part too. I managed to solve my problem with a somewhat different approach.
About my problem... I am doing visual regression tests and I was able to insert multiple images into my report (so I can compare the reference image of the test with the current screenshot and the one containing the differences). It is really a pain in the a** to keep the reference images up to date manually so my idea was to further extend the report with an "Approve" button so I can just click through the changes.
In the end I realized that I can write a custom formatter based on the built in html formatter to generate the report as it is now, then tap into the finished method to insert some js into the report's html file. With that js I can manipulate the dom to make my changes without diving into react too deep or rewriting anything.
It is not a nice solution and I wouldn't recommend doing this with more complex functionality, but for just an extra button I'm fine with it.


Syntax error on php 7.1

When using deptrac on php 7.1 we get the following error:
.
Syntax Error on File Domain/Functions/CategoryRepositoryInterface.php
Syntax error, unexpected '?' on line 20

This is probably due to the nullable return type:
20 public function findOneByTitle(string $title): ?Category;

thanks for reporting, i've to update the phpparser.
https://github.com/nikic/PHP-Parser/issues/260

the problem is that the phpparser 3 isn't stable right now.
deptrac runs well with phpparser3 but for now i think we should wait until it's stable deptrac/tree/feature_phpparser3
if you need php7.1 and want to use deptrac you can use a special deptrac beta build.

I think that this is a current issue, because PHP-Parser 3.x is stable and 7.1 is being adopted more and more every day.

i am a bit busy at the moment but i try to update the phpparser soon.

should be fixed =)

The issue hasn't been resolved, see: https://github.com/sensiolabs-de/deptrac/pull/122
There was 1 error:

1) SensioLabs\Deptrac\Tests\DependencyEmitter\BasicDependencyEmitterTest::testApplyDependencies
Error: Call to a member function toString() on string

The previously working beta build also has been removed (Access Denied S3 error) which now leaves us with no solution.

I updated my PR with a fix, I am however not very familiar with the inner workings of deptrac so I am not sure if it has any side affects / covers all edge cases.

thanks a lot, i merged the PR and updated the phar file :)


Update client-go to 0.25.6 and bump go to 1.20

Using kubebuilder v3.8.0 scaffolding and client-go 0.25.6 and controller-runtime v0.13.1
Additionally, copied clientset impl from #29 to use dynamic clients

Hi @marcushines
I re-created the scaffolding using the kubebuilder v3.8.0 which works with client-go 0.25 and controller-runtime 0.13.
Now the infra errors are gone, and only clientset tests are failing...
Since I am not familiar with dynamic-based clientsets, maybe you know a way out from these errors?

@marcushines i will create a draft PR against kne project to have a discussion around this approach. It looks promising and removes the need for clientset using the dynamic client while still working with structured types.
If all goes well I will open a PR today


How to get client id?

Sorry for newbie question. I try to get from session or cookie not work. Can you advice me to get it, please.

Please refer: https://developers.google.com/analytics/devguides/collection/protocol/v1/parameters#cid
Not sure from where you're trying to access the client ID but that can be set using a random generated UUID. Refer the docs above.

for this "setClientId()" Where can I get it?
Now I get from javascript
var clientId = tracker.get('clientId');
I don't know. please example to get it, please.

You don't get that. You need to set a random generated ID. Even the JS version of Google Analytics simply generates a random number for that browser session and stores that in a cookie to send hits later.
Go through the above link i sent you and this one to understand:
https://developers.google.com/analytics/devguides/collection/analyticsjs/cookies-user-id
So the example would be:
$gamp = GAMP::setClientId( '<randomly generated id>' );
$gamp->setDocumentPath( '/page' );
$gamp->sendPageview();


Stage1 failing to deploy external snapshotter on AWS

Looks like a missing CRD:
E0123 21:51:18.888122       1 main.go:86] Failed to list v1 volumesnapshots with error=the server could not find the requested resource (get volumesnapshots.snapshot.storage.k8s.io)

This is on a cluster created using bootstrap for aws... stage0/aws-terraform

Closes with #53


Bug: Two status lines appear when using nvim -p[x] and switching tabs

Self Checks

[x] I'm using the latest lualine.
[X] I didn't find the issue in existing issues or PRs.

i found this problem with other plugin too   but i like lualine so ... i am saying the issue here  excuse me XD

I have this exact same issue. Just switched to Lazy Vim since Lunar Vim maintainer vanished. Thought it was an issue with LazyVim default config but it doesn’t appear that’s the case

@lioil987 are you using LazyVim by any chance? If you are, are you using the Noice plugin?

@ParisTheProgrammer I don't use LazyVim, but I do have noice installed. I tried disabling noice and the problem went away. I also tried disabling lualine and re-enabling noice and the problem came back. So it seems like the problem is with noice and not lualine.

Thank you for your attention. It seems the issue lies in the noice, i removed that for preventing me from fully reading the message. However, I've retained this page. but I'm grateful for your assistance.

sorry i am new in git , if i close or open or...   something is not intentional

and please see my projects and say your opinion


TestPeerConnectionTrickle failure on CI

--- FAIL: TestPeerConnectionTrickle (1.21s)
    peerconnection_go_test.go:717:
        	Error Trace:	peerconnection_go_test.go:717
        	            				icegatherer.go:162
        	            				asm_386.s:1325
        	Error:      	Received unexpected error:
        	            	InvalidStateError: remote description is not set
        	Test:       	TestPeerConnectionTrickle

Infrequently happens on CI.
It seems like a race condition.

I will take this!
I think we are calling AddICECandidate before we have a remote description. You have this same issue in the browser :( I just need to cache the candidates.


Support structure rendering on various missing axis & props

Hi
We have identified that various viewer axises and props do still not render SMILES/molfiles as structure images.
It would be nice if the following list could be completed:

Scatterplot color-by (highest priority)
Histogram split
Bar chart stack
Line chart split
Pie chart category
Treemap split

Thanks
Nico

Let's discuss it tomorrow. For most of the viewers referenced above, rendering a molecule is somewhat challenging since the space is limited - but we'll see what we can do

And Boxplot category (from user) as well

The following viewers already render SMILES/molfiles as structure images:

Scatterplot color-by
Histogram split
Bar chart stack
Line chart split
Pie chart category

For the box plot, there is a separate task 2057

thanks!

From: Olena Ahadzhanian @.>
Sent: Thursday, June 22, 2023 18:11
To: datagrok-ai/public @.>
Cc: Pulver, Nico @.>; Author @.>
Subject: Re: [datagrok-ai/public] Support structure rendering on various missing axis & props (Issue #938)
This Message is from an External Sender. Do not click links or open attachments unless you trust the sender.
The following viewers already render SMILES/molfiles as structure images:

Scatterplot color-by
Histogram split
Bar chart stack
Line chart split
Pie chart category

For the box plot, there is a separate task 2057https://urldefense.com/v3/__https://github.com/datagrok-ai/public/issues/2057__;!!N3hqHg43uw!vcTWWneq2K_5Se2gkzqP7YluGPHloY47L8-4mIMmI_t3la3n6gE7xbq4wCyym-r80tgcJVNawyL7zD33wotnOyfFumz3$
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/datagrok-ai/public/issues/938*issuecomment-1602946111__;Iw!!N3hqHg43uw!vcTWWneq2K_5Se2gkzqP7YluGPHloY47L8-4mIMmI_t3la3n6gE7xbq4wCyym-r80tgcJVNawyL7zD33wotnOy8i651l$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ACG2R64ZOF3RUFEVR4ZX27TXMRVDLANCNFSM56HQZPXA__;!!N3hqHg43uw!vcTWWneq2K_5Se2gkzqP7YluGPHloY47L8-4mIMmI_t3la3n6gE7xbq4wCyym-r80tgcJVNawyL7zD33wotnOzbtc7Mm$.
You are receiving this because you authored the thread.Message ID: @.***>


why no data normlization in data pre-processing？when I use data normlization in data pre-processing， rate of convergence of the network  is slow

What ??
Write properly, with intro, and full description of your problem\question


Update Software refs page

[x] Clarify that if there are RRIDs we don't need to add AQ, and if authors have added a software ref this is fine to leave.

Definition of done

[ ] Updates completed
[ ] Team reviewed and approved page?

@Melissa37 @bcollins14 @FAtherden-eLife @JGilbert-eLife
In light of recent discussions about what we want for software references, can I ask for a re-review of the following sections?:

The What needs to be added? section
The When to add software references section
The action of github-web-test. Do we want to query authors who have cited github repos and not provided version numbers? They probably won't know what we mean if we use the query as it stands - should we specifically ask for which commit they used or not bother?

For 'What needs to be added?', can we change the Mandatory cells for Source and Publisher from 'No' to 'Yes (or Publisher must be entered instead)' and 'Yes (or Source must be entered instead)'?

The action for github-web-test is fine I think.
Although, the Author fields in that specific example are not correct, (should be O'Toole A and McCrone JT, based on the repo), but I don't know if the expectation is that Exeter would find out that information, or just leave the author details as they are in this scenario (given that the query has been added).

On the point about host versus publisher - maybe an '(if applicable)' in the bullet pointed list descriptions?

The screenshot with the caption "All the software here needs to be added as software references and cited properly" is probably not terribly useful to a new starter without some highlighting to make clear where the software is in that paragraph.

Agree that the github-web-test action is OK. However, not sure how wide-covering the examples are with regards to distinguishing repos from blog posts.


Meta fixes

Putting the full ref qualifier git push HEAD:refs/heads/testing-branch makes it work.

No I don’t think that's the issue, the current code works on push events but not on pull_request events due to a permission issue. This sounds like GitHub is giving a token with reduced permissions to PRs, as expected.

https://github.com/fregante/setup-git-user/blob/5ede2be584625f0c1f2a2ef6f6e4a8aa7665eb4c/.github/workflows/test.yml#L25
Putting the full ref qualifier git push origin HEAD:refs/heads/testing-branch makes it work.

This works as tested here: https://github.com/sitiom/setup-git-user/pull/1

Can you send this PR from your fork? https://github.com/fregante/setup-git-user/pull/3/files
It's weird that they'd allow a fork to push to either repo

Can you send this PR from your fork? https://github.com/fregante/setup-git-user/pull/3/files
It's weird that they'd allow a fork to push to either repo

Yeah fails to work: https://github.com/sitiom/setup-git-user/pull/1.

Yeah, so it defeats the purpose of being included for PRs.
Thanks for working with me on this


[bug]: Syntax error with every component

Describe the bug
I'm sure this is a silly configuration issue on my end - but I've tried loads of things and cannot figure it out.
I've got a basic SolidJS application, with Firebase too, meaning I've got an index.html file in the root directory.
It has Tailwind installed too.
So far I've tried to import the Button and ComboBox components, but with both of them, I get issues, meaning that they cannot be used.
With the Button I get an issue with CVA:

And also the Button primitive:

And then on every instance of the ComboBox primitive, I get a similar issue:

Not really sure where to start with this - there are still some aspects of web dev I don't fully grasp, but I would expect this to work based on my setup.
I've followed the manual installation steps, so I have updated my tsconfig.json to have the @ directory.
My tailwind.config.cjs is configured correctly.
My app.css file is actually my index.css file, but that also has the same syntax as the installation instructions.
I also have a cn helper.
I'm using NPM rather than PNPM to install single components (npx shadcn-solid@latest add button VS pnpm dlx degit...), as the PNPM variant doesn't seem to work.
I'm kindof at a dead end with this. I could probably fix these individual components, but I don't want to have to fix a component every time I import it, so I'm hoping some configuration issue!
Error below from Vite:
Error: The following dependencies are imported but could not be resolved:

  @/components/ui/button (imported by C:/Source/Non/solid-chess/src/App.tsx)

Are they installed?
    at file:///C:/Source/Non/solid-chess/node_modules/vite/dist/node/chunks/dep-NjL7WTE1.js:50534:15
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///C:/Source/Non/solid-chess/node_modules/vite/dist/node/chunks/dep-NjL7WTE1.js:50039:26
16:29:54 [vite] Pre-transform error: Failed to resolve import "@/components/ui/button" from "src/App.tsx". Does the file exist?
16:29:54 [vite] Internal server error: Failed to resolve import "@/components/ui/button" from "src/App.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Source/Non/solid-chess/src/App.tsx:2:21
  5  |  const _REGISTRY = _$$registry();
  6  |  var _tmpl$ = /* @__PURE__ */ _$template(`<div class="flex h-screen"><div class=w-80></div><div class=flex-grow>`);
  7  |  import { Button } from "@/components/ui/button";
     |                          ^
  8  |  const App = _$$component(_REGISTRY, "App", () => {
  9  |    return (() => {
      at TransformPluginContext._formatError (file:///C:/Source/Non/solid-chess/node_modules/vite/dist/node/chunks/dep-NjL7WTE1.js:49133:41)
      at TransformPluginContext.error (file:///C:/Source/Non/solid-chess/node_modules/vite/dist/node/chunks/dep-NjL7WTE1.js:49128:16)
      at normalizeUrl (file:///C:/Source/Non/solid-chess/node_modules/vite/dist/node/chunks/dep-NjL7WTE1.js:63910:23)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async file:///C:/Source/Non/solid-chess/node_modules/vite/dist/node/chunks/dep-NjL7WTE1.js:64042:39
      at async Promise.all (index 4)
      at async TransformPluginContext.transform (file:///C:/Source/Non/solid-chess/node_modules/vite/dist/node/chunks/dep-NjL7WTE1.js:63969:7)
      at async PluginContainer.transform (file:///C:/Source/Non/solid-chess/node_modules/vite/dist/node/chunks/dep-NjL7WTE1.js:48974:18)
      at async loadAndTransform (file:///C:/Source/Non/solid-chess/node_modules/vite/dist/node/chunks/dep-NjL7WTE1.js:51796:27)
      at async viteTransformMiddleware (file:///C:/Source/Non/solid-chess/node_modules/vite/dist/node/chunks/dep-NjL7WTE1.js:61750:24)

Affected component/components
Button, Combobox, potentially more.
How to reproduce
Create a SolidJS TS app from the template.
Install Firebase & init.
Setup ShadCN prerequisites.
Install a component (such as a Button or Combobox).
Use the component. Build fails.
Codesandbox/StackBlitz link
No response
Logs
No response
System Info
FireFox.
Typescript 5.5.4
Vite 5.4.0

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

Turns out, having this in my vite.config.ts is absolutely critical, and resolves this issue. Can't see it in the documentation so might be worth adding:

Feel free to close.

Noted, thanks!

Seems like this is fixed in the docs now: https://shadcn-solid.com/docs/installation/solid-start
@hngngn should this issue be closed?

I think he's following this https://shadcn-solid.com/docs/installation/manual, and it doesn't have the resolve.alias. That's why I left this open until I or someone updates the docs.


Add @bolt/core dependencies to the few packages that lacked such.

When Bolt undergoes an update (eg recently to 1.3), there's consistently a few packages that get left behind due to lacking a @bolt/core dependency. For instance, here's the current version of all packages:
@bolt/components-placeholder       v1.3.0
@bolt/components-action-blocks     v1.3.0
@bolt/components-background-shapes v1.3.0
@bolt/components-background        v1.3.0
@bolt/components-band              v1.3.0
@bolt/components-block-list        v1.3.0
@bolt/components-blockquote        v1.3.0
@bolt/components-breadcrumb        v1.3.0
@bolt/components-button-group      v1.3.0
@bolt/components-button            v1.3.0
@bolt/components-card              v1.3.0
@bolt/components-dropdown          v1.3.0
@bolt/components-chip-list         v1.3.0
@bolt/components-chip              v1.3.0
@bolt/components-copy-to-clipboard v1.3.0
@bolt/components-critical-fonts    v1.3.0
@bolt/components-device-viewer     v1.3.0
@bolt/components-figure            v1.3.0
@bolt/components-form              v1.3.0
@bolt/components-headline          v1.3.0
@bolt/components-icon              v1.3.0
@bolt/components-icons             v1.3.0
@bolt/components-image             v1.3.0
@bolt/components-link              v1.1.2
@bolt/components-logo              v1.3.0
@bolt/components-navbar            v1.3.0
@bolt/components-nav               v1.3.0
@bolt/components-navlink           v1.3.0
@bolt/components-ordered-list      v1.3.0
@bolt/components-page-header       v1.3.0
@bolt/components-share             v1.3.0
@bolt/components-site              v1.1.2
@bolt/components-smooth-scroll     v1.2.4
@bolt/components-sticky            v1.2.0
@bolt/components-teaser            v1.3.0
@bolt/components-tooltip           v1.3.0
@bolt/components-unordered-list    v1.3.0
@bolt/components-video             v1.3.0
@bolt/core                         v1.3.0
@bolt/global                       v1.3.0

You can spot the outliers. This PR gets the stragglers back in the fold.

My main issue that this resolves is the inconsistency. Almost every component has a dependency on @bolt/core:
$ grep -r \@bolt/core packages/components/ | grep package.json
packages/components//bolt-action-blocks/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-background/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-background-shapes/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-band/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-block-list/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-blockquote/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-breadcrumb/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-button/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-button-group/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-card/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-chip/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-copy-to-clipboard/package.json:    "@bolt/core": "^1.3.0",
packages/components//bolt-critical-fonts/package.json:    "@bolt/core": "^1.3.0",
packages/components//bolt-device-viewer/package.json:    "@bolt/core": "^1.3.0",
packages/components//bolt-dropdown/package.json:    "@bolt/core": "^1.3.0",
packages/components//bolt-figure/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-form/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-headline/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-icon/package.json:    "@bolt/core": "^1.3.0",
packages/components//bolt-icons/package.json:    "@bolt/core": "^1.3.0",
packages/components//bolt-image/package.json:    "@bolt/core": "^1.3.0",
packages/components//bolt-link/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-logo/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-nav/package.json:    "@bolt/core": "^1.3.0",
packages/components//bolt-navbar/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-navlink/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-ordered-list/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-page-header/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-placeholder/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-share/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-site/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-smooth-scroll/package.json:    "@bolt/core": "^1.3.0",
packages/components//bolt-sticky/package.json:    "@bolt/core": "^1.3.0",
packages/components//bolt-teaser/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-tooltip/package.json:    "@bolt/core": "^1.3.0",
packages/components//bolt-unordered-list/package.json:    "@bolt/core": "^1.3.0"
packages/components//bolt-video/package.json:		"@bolt/core": "^1.3.0",

Except for these few, presumably due to an oversight:
$ grep -L \@bolt/core packages/components/*/package.json
packages/components/bolt-chip-list/package.json
packages/components/bolt-link/package.json
packages/components/bolt-page-footer/package.json
packages/components/bolt-site/package.json
packages/components/bolt-smooth-scroll/package.json
packages/components/bolt-sticky/package.json

I suppose I should change bolt-page-footer and bolt-chip-list as well.

I'm good with this 👍 The whole idea is that @bolt/core is used by everything, so if it bumps a version then I see no reason to not bump the version of all the components. I also noticed that the chip list was importing @bolt/global which it's not supposed to, so I changed that in this PR on d0d460e - those are global styles etc and creates extra styles. That'd only be an issue if you were trying to compile just the chip list via components.individual, so it probably wasn't happening but I wanted to change it nonetheless. This is good to merge after CI passes.


Remove ?Send option of async-trait

Not every async_trait we implement requires ?Send.
Modify it accordingly:

[x] Remove ?Send of Store, StoreMut, IndexMut
[x] Remove ?Send of AlterTable, but Self is Send
[x] Remove ?Send of Index, but Self is Sync
[x] Remove ?Send of Tester. but Self is Sized

caution) The trait bounds requirements of AtlerTable and Index are still not well understood.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.518%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
37949

Relevant Lines:
38520

💛  - Coveralls

https://docs.rs/async-trait/latest/async_trait/#dyn-traits
I understood with that document.
It looks like we can remove this constraint by replacing the default implementation with declare_macro.

depends on #1078

Close, because it's deprecated code


Ruby 2.4.0 has deprecated the Fixnum class

This has now been replaced with the Integer class

Changes Unknown when pulling e70bf4a957ec766f0cfe1400f82840c90516e5b1 on thechrisoshow:fix-2-4-0 into ** on fog:master**.

Changes Unknown when pulling e70bf4a957ec766f0cfe1400f82840c90516e5b1 on thechrisoshow:fix-2-4-0 into ** on fog:master**.

Changes Unknown when pulling fe48dbc4170ed472d959b7c8210243a730bad06c on thechrisoshow:fix-2-4-0 into ** on fog:master**.

Closing in favor of #65

Thanks for your interest and contribution here. I did merge this same change from another PR to speed up the process. I don't have time to code myself nowadays so i heavily depend on contributions. Sorry for the trouble.


Several changes for smoother results and more control over the NN.

Changed mutation to also check if it should mutate at all based on the rate. Changed the mutation rate because of the mentioned mutation-changes. Doubled vehicle.maxforce so it has more control over itself. Changed the border-inputs according to the entire canvas instead of the 50px wide stroke. Lastly I've added a fallback for when all vehicles are about to die, which would probably never happen in the current reproduction-rate.
The mutation-changes are mainly so not every reproduced vehicle is mutated (which pretty much was the case). The vehicle.maxforce seems to have quite some impact on the results over time, setting this to an insane amount will get some 100k+ vehicles (framecount score) quite easily. The border changes were made so the vehicles don't get stuck in a corner. The fallback is quite useless now, but it would be nice if you want to change the reproduction-rate.

I love these ideas! Thank you so so much!
I think these suggestions might be best implemented as a demo by you that I would link to? For the purposes of an example that people can build on I think it's simpler with just one set of sensors?
Also, I love the idea of making it more "biological" and reducing health while accelerating! But again I think this is more something that a viewer would add as an exercise rather than part of the example? I'm using a lot of questions marks b/c I am not sure!
Let me know your thoughts and how it might work best to link to and credit your work here!
I am also curious for @meiamsome's thoughts as they suggested many of the original improvements.

@shiffman I think you were ment to post the comment about adding more sensors and making it more biological here: https://github.com/CodingTrain/Toy-Neural-Network-JS/pull/115


add arktype and tanstack router to ecosystem in readme

I will add your changes by hand and add you as a co-author


Same code and QCs, but updated format

Updated the format a bit - added PASS if QC passes. I also hard coded rt_dataset as this parameter does not change

@ksdkalluri when you have time, please approve this. I just updated the format but it is the same code.


Prevent pkg-config from being removed in image

Currently, installing the toolchain for arm-unknown-linux-gnueabihf
uses xz-utils which gets pruned. This also removes pkg-config, so
remove the prune altogether to keep both packages. curl is also kept
as that was originally installed in common.sh as well.
Fixes #422

bors r+

Thanks, @jmagnuson!


How to enter the docker offline / with no network

Could someone explain the steps I would need to take to be able to launch and enter the apollo docker offline. I would like to be able to enter the docker and perform tests without having an internet connection. Thanks very much!

you could reference following command:
sudo /docker/scripts/dev_start.sh -l .
Hope this could help you:)

Yeah, @muleisheng is right, there is an -l option to start docker locally. This may work well for early version,  for the latest version, the new added docker images are not handle the -l option, so some additional work need to be done to achieve this.
Simply, you may need to find all the 'docker pull' command(except the main docker, handled already) and comment it out in dev_start.sh and restart_map_volume.sh .
Hope it helps.

Thank you, the steps @zhxt  mentioned on commenting out the 'docker pull' commands in both dev_start.sh and restart_map_volume.sh has done the trick!

I think you can use -l option but you have to fix /docker/scripts/dev_start.sh. You need to change name "local_dev" to existing docker image like dev-x86_64-20180702_1140


[Bug]: SBB-Toggle-Option Selector switch is output with misleading info

Preflight Checklist

[X] I have read the Contributing Guidelines for this project.
[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Bug type
Accessibility
It affects the following packages
Components
Which version of Lyne Components are you using
0.40.14
Operating system
No response
Browser / Browser version
No response
Input mode
None
Additional settings
No response
What happened?
Tooltip-Handling // Radio button is output with misleading information (submenu) because the element is marked with aria-haspopup="dialog" attribute although there is no submenu.

Steps to reproduce the issue

Step one
Step two
...

Relevant log output
No response

Will probably be addressed when we refactor the tooltip in general way.

hey @jeripeierSBB, "aria-expanded, aria-controls, aria-haspopup" can be removed in sbb-toggle-option because it's not necessary for screenreader users.

Hi @Ckauczor, these properties are coming from the tooltip, not from the toggle-option itself. The "problem" is that you bound the tooltip to the toggle option (?).
As said, we will completely refactor the sbb-tooltip and therefore hopefully get around this. Maybe it's not best practice to use tooltip on toggle itself, or how do you provide solutions to mobile users?

Hi, i could confirm that you are right :) we remove the tooltips and the aria-labels are gone


Scope of the project

By looking at the sources of this repo, it seems that the project is to generate artifacts for a wide range of platforms (both OSs and architectures). That's nice! However, I'm lacking some explanation in the README for understanding how does this fit with other similar projects in the ecosystem. I'd like to gather some information for listing it in hdl/packages and forwarding people for which this is the best solution.
Precisely, YosysHQ/fpga-toolchain is based on prior work by Miodrag, who did also contribute to apio. See https://github.com/YosysHQ/fpga-toolchain#credits and https://github.com/FPGAwars/toolchain-ecp5. Moreover, builds in fpga-toolchain are nightly/daily too. The main feature of fpga-toolchain is that tools are built statically.
In this repo:

Python is used for the plumbing, instead of bash.
The tools are cross-compiled on containers, instead of using the CI environments (typically Ubuntu).
At the same time, there is a Windows job in CI, which builds tools on MSYS2 "natively".

On the one hand, I'm not sure about the motivation for having a container for Windows cross-compilation and an MSYS2 CI job at the same time. I would expect one or the other to be used.
On the other hand, it seems that most of the tools are still built statically. Hence, is this a drop-in replacement for fpga-toolchain (with a different codebase and build environments)?
Furthermore, are you expecting to provide containers to end users? Or are those only for using a custom and portable build environment?

With regard to MSYS2, similarly to fpga-toolchain, you seem to have a significant number of tweaks for trying to use the same plumbing as for other platforms. However, IMHO, building a distribution of tools for/through MSYS2 is better done using the built-in package manager (pacman), PKGBUILD recipes and makepkg-mingw. In fact, the following works already:
# Extract https://github.com/msys2/msys2-installer/releases/download/2021-02-28/msys2-base-x86_64-20210228.tar.xz and open a MINGW64 shell
# NOTE: https://github.com/msys2/setup-msys2/blob/master/main.js#L12

# pacman -Syu
...

# pacman -S mingw-w64-x86_64-eda
:: There are 21 members in group mingw-w64-x86_64-eda:
:: Repository mingw64
   1) mingw-w64-x86_64-dfu-util
   2) mingw-w64-x86_64-ecpprog
   3) mingw-w64-x86_64-fritzing
   4) mingw-w64-x86_64-ghdl-llvm
   5) mingw-w64-x86_64-gtkwave
   6) mingw-w64-x86_64-icesprog
   7) mingw-w64-x86_64-icestorm
   8) mingw-w64-x86_64-iverilog
   9) mingw-w64-x86_64-kicad
   10) mingw-w64-x86_64-kicad-footprints
   11) mingw-w64-x86_64-kicad-meta
   12) mingw-w64-x86_64-kicad-packages3D
   13) mingw-w64-x86_64-kicad-symbols
   14) mingw-w64-x86_64-kicad-templates
   15) mingw-w64-x86_64-nextpnr
   16) mingw-w64-x86_64-ngspice
   17) mingw-w64-x86_64-openFPGALoader
   18) mingw-w64-x86_64-prjtrellis
   19) mingw-w64-x86_64-serial-studio
   20) mingw-w64-x86_64-verilator
   21) mingw-w64-x86_64-yosys

Enter a selection (default=all):

Find links to each of the recipes in https://hdl.github.io/MINGW-packages/#_packagestools and https://packages.msys2.org/group/mingw-w64-x86_64-eda. Recipes are located in https://github.com/msys2/MINGW-packages/.
The official recipes use fixed commits/tags. There are two workflows in hdl/MINGW-packages for keeping track of breaking changes and/or outdated packages:

https://github.com/hdl/MINGW-packages/blob/main/.github/workflows/build.yml builds the recipes. Since MSYS2 is a rolling environment, builds might break and/or the tools might need to be rebuilt.
https://github.com/hdl/MINGW-packages/blob/main/.github/workflows/test.yml tests the latest available packages with main/master/head test suites. This allows knowing when packages are outdated because some new feature was added.

On the one hand, you might use those workflows as a reference for working around the timeout issues you have in CI. On the other hand, you might want to customise those recipes for building main/master/head of the projects, instead of fixed versions. That would make your build procedure on/for Windows different from others. Yet, supporting cross-compilation for arm, arm64, riscv64 and amd64 is a huge task already. Hence, reducing the complexity of the Windows infrastructure would allow you to focus on the foreign linux builds.
Personally, I like contributing workflows for building main/master/head to the projects, instead of doing it in orgs MSYS2 or HDL. See: iverilog, verilator, gtkwave, GHDL, Serial-Studio, etc. There is a reference workflow in https://hdl.github.io/MINGW-packages/#_testing_pkgbuild_recipes_downstream, together with some brief guidelines.
Note that MSYS2 packages are tarballs. Therefore, YosysHQ could potentially have a mirror/repository with custom builds/versions, should you want to. Alternatively, you can publish assets in a 'nightly' release:

https://github.com/gtkwave/gtkwave/releases/tag/nightly
https://github.com/ghdl/ghdl/releases/tag/nightly

A similar strategy is used in MSYS2 for staging packages: https://github.com/msys2/msys2-autobuild/releases. See also https://packages.msys2.org/queue.
Nevertheless, MSYS2 maintainers are really fast. For instance: https://github.com/msys2/MINGW-packages/pull/8180. Therefore, I don't think it's worth maintaining an independent set of nightly packages, unless you want to have very specific build options and/or combine tools with non-free software. Typically, any update will be available for everyone in 1-3 days after opening a PR.
No matter which strategy you follow, let me know if you need any hint about MSYS2/MINGW packages (hdl/MINGW-packages), QEMU and Docker (dbhi/qus) and/or MSYS2 on GitHub Actions (msys2/setup-msys2). I'm not an expert in either of them, but I do have experience with all and I'd be glad to help you make the best of your time.
Cheers

Hi Unai,
Thank you for your feedback and useful tips.
As you have noticed this is not something that is quite finished, and I do
work on solving the rest of the issues and cleaning up scripts to a
maintainable level, and that is the major reason why proper README content
is missing. We published it a bit earlier then foreseen to be able to test
GitHub actions and check if we can use it.
Anyway this project started as my effort of making a build system for our
commercial package, but in mind of greater OS support. Since it was modular
I have started from beginning to make it ready for public build as well,
since we have a lot of people interested in using open source stack but
have problems setting all solvers and can't keep up with updating all tools
they need to update. So this was made as a self-contained system to build
binary non-static releases but still able to execute on various
distributions without a change. Containers are there just for building
projects and all things you need to run software is packaged (check
default.sh for how it is done, note that for Windows I rely on setting PATH
for now for DLL loading, but looking into better solution).
Note that static build is easier to make portable, but this is not possible
for GUI tools, those that integrate python or others that rely on dynamic
loading of plugins.
Since there are a lot of possible supported platforms, but not sure we are
going to be able to make releases for all (at least not from start) it is
easy to set up the build environment and do the checks. Also this allows
adding new packages for any external contributor much easier. First I have
added Windows support for msys2 since that seems natural, but makes things
complicated for CI and testing (if you have linux based machines only) so I
made docker based one, but still have some limitations there (missing ADA
compiler, so no GHDL build possible for now).
We are still not announcing this project until there are working builds
available to download, but it is good to have more people testing and
giving their suggestions. Will see to improve preview of build status of
packages per platform, so it is known what users can expect to have in the
final build ( there are certain solvers that are linux only, or just can
work on windows for example). In time I also plan to upstream some of the
changes to projects used to make scripts easier to maintain but also those
projects more compatible with certain OS-es.
For now I would concentrate on FPGA based EDA software that is already in
and make that building nice before attempting to add something else.
On Wed, Mar 24, 2021 at 3:32 AM Unai Martinez-Corral <
@.***> wrote:

By looking at the sources of this repo, it seems that the project is to
generate artifacts for a wide range of platforms (both OSs and
architectures). That's nice! However, I'm lacking some explanation in the
README for understanding how does this fit with other similar projects in
the ecosystem. I'd like to gather some information for listing it in
hdl/packages https://github.com/hdl/packages and forwarding people for
which this is the best solution.
Precisely, YosysHQ/fpga-toolchain
https://github.com/YosysHQ/fpga-toolchain is based on prior work by
Miodrag, who did also contribute to apio. See
https://github.com/YosysHQ/fpga-toolchain#credits and
https://github.com/FPGAwars/toolchain-ecp5. Moreover, builds in
fpga-toolchain are nightly/daily too. The main feature of fpga-toolchain is
that tools are built statically.
In this repo:

Python is used for the plumbing, instead of bash.
The tools are cross-compiled on containers, instead of using the CI
environments (typically Ubuntu).
At the same time, there is a Windows job in CI, which builds tools
on MSYS2 "natively".

On the one hand, I'm not sure about the motivation for having a container
for Windows cross-compilation and an MSYS2 CI job at the same time. I would
expect one or the other to be used.
On the other hand, it seems that most of the tools are still built
statically. Hence, is this a drop-in replacement for fpga-toolchain (with a
different codebase and build environments)?
Furthermore, are you expecting to provide containers to end users? Or are
those only for using a custom and portable build environment?
With regard to MSYS2, similarly to fpga-toolchain, you seem to have a
significant number of tweaks for trying to use the same plumbing as for
other platforms. However, IMHO, building a distribution of tools
for/through MSYS2 is better done using the built-in package manager
(pacman), PKGBUILD recipes and makepkg-mingw. In fact, the following works
already:
Extract https://github.com/msys2/msys2-installer/releases/download/2021-02-28/msys2-base-x86_64-20210228.tar.xz and open a MINGW64 shell# NOTE: https://github.com/msys2/setup-msys2/blob/master/main.js#L12
pacman -Syu
...
pacman -S mingw-w64-x86_64-eda
:: There are 21 members in group mingw-w64-x86_64-eda:
:: Repository mingw64

mingw-w64-x86_64-dfu-util
mingw-w64-x86_64-ecpprog
mingw-w64-x86_64-fritzing
mingw-w64-x86_64-ghdl-llvm
mingw-w64-x86_64-gtkwave
mingw-w64-x86_64-icesprog
mingw-w64-x86_64-icestorm
mingw-w64-x86_64-iverilog
mingw-w64-x86_64-kicad
mingw-w64-x86_64-kicad-footprints
mingw-w64-x86_64-kicad-meta
mingw-w64-x86_64-kicad-packages3D
mingw-w64-x86_64-kicad-symbols
mingw-w64-x86_64-kicad-templates
mingw-w64-x86_64-nextpnr
mingw-w64-x86_64-ngspice
mingw-w64-x86_64-openFPGALoader
mingw-w64-x86_64-prjtrellis
mingw-w64-x86_64-serial-studio
mingw-w64-x86_64-verilator
mingw-w64-x86_64-yosys

Enter a selection (default=all):
Find links to each of the recipes in
https://hdl.github.io/MINGW-packages/#_packagestools and
https://packages.msys2.org/group/mingw-w64-x86_64-eda. Recipes are
located in https://github.com/msys2/MINGW-packages/.
The official recipes use fixed commits/tags. There are two workflows in
hdl/MINGW-packages for keeping track of breaking changes and/or outdated
packages:

https://github.com/hdl/MINGW-packages/blob/main/.github/workflows/build.yml
builds the recipes. Since MSYS2 is a rolling environment, builds might
break and/or the tools might need to be rebuilt.
https://github.com/hdl/MINGW-packages/blob/main/.github/workflows/test.yml
tests the latest available packages with main/master/head test suites. This
allows knowing when packages are outdated because some new feature was
added.
On the one hand, you might use those workflows as a reference for working
around the timeout issues you have in CI. On the other hand, you might want
to customise those recipes for building main/master/head of the projects,
instead of fixed versions. That would make your build procedure on/for
Windows different from others. Yet, supporting cross-compilation for arm,
arm64, riscv64 and amd64 is a huge task already. Hence, reducing the
complexity of the Windows infrastructure would allow you to focus on the
foreign linux builds.
Personally, I like contributing workflows for building main/master/head to
the projects, instead of doing it in orgs MSYS2 or HDL. See: iverilog
https://github.com/steveicarus/iverilog/blob/master/.github/workflows/test.yml?rgh-link-date=2021-03-23T04%3A42%3A39Z,
verilator https://github.com/verilator/verilator/pull/2681, gtkwave
https://github.com/gtkwave/gtkwave/blob/master/.github/workflows/build.yml?rgh-link-date=2021-03-23T04%3A42%3A39Z,
GHDL https://github.com/ghdl, Serial-Studio
https://github.com/Serial-Studio/Serial-Studio/tree/master/msys2, etc.
There is a reference workflow in
https://hdl.github.io/MINGW-packages/#_testing_pkgbuild_recipes_downstream,
together with some brief guidelines.
Note that MSYS2 packages are tarballs. Therefore, YosysHQ could
potentially have a mirror/repository with custom builds/versions, should
you want to. Alternatively, you can publish assets in a 'nightly' release:

https://github.com/gtkwave/gtkwave/releases/tag/nightly
https://github.com/ghdl/ghdl/releases/tag/nightly

A similar strategy is used in MSYS2 for staging packages:
https://github.com/msys2/msys2-autobuild/releases. See also
https://packages.msys2.org/queue.
Nevertheless, MSYS2 maintainers are really fast. For instance:
msys2/MINGW-packages#8180
https://github.com/msys2/MINGW-packages/pull/8180. Therefore, I don't
think it's worth maintaining an independent set of nightly packages, unless
you want to have very specific build options and/or combine tools with
non-free software. Typically, any update will be available for everyone in
1-3 days after opening a PR.
No matter which strategy you follow, let me know if you need any hint
about MSYS2/MINGW packages (hdl/MINGW-packages
https://github.com/hdl/MINGW-packages), QEMU and Docker (dbhi/qus
https://github.com/dbhi/qus) and/or MSYS2 on GitHub Actions (
msys2/setup-msys2 https://github.com/msys2/setup-msys2). I'm not an
expert in either of them, but I do have experience with all and I'd be glad
to help you make the best of your time.
Cheers
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/YosysHQ/fpga-nightly/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA3UUSDXJ3STE4FXGHA7IG3TFFFLVANCNFSM4ZWLLVEA
.

Anyway this project started as my effort of making a build system for our commercial package, but in mind of greater OS support.

Is "your commercial package" Tabby CAD? Is there any non-open tool in the bundle apart from Verific's parser/frontend? I only found lists of the open source tools included.

we have a lot of people interested in using open source stack but have problems setting all solvers and can't keep up with updating all tools they need to update.

I would very strongly suggest you to distribute one container, at least, even if temporarily. In general, I don't like large monolithic containers, because of technical and conceptual reasons. However, that is the fastest solution for making any custom set of tools available to any user. That is because you need to care about a single Linux environment (pick the base image that you wish). The same image can then be used in CI, on Linux, Windows or MacOS. Once you have that first problem solved, you can focus on more granular build and distribution solutions. In a sense, I'm proposing you to focus on a subset of what you already have, since all the tools are already built/tested on some Debian/Ubuntu, you avoid all that custom copying of shared libs.
For formal verification, @tmeissner contributed multiple solvers to https://hdl.github.io/containers/#_tools_and_images. Precisely, image formal contains boolector, cvc4, superprove, yices2 and z3, apart from GHDL, Yosys and SymbiYosys. You can use it as a base and add the Verific frontend as a plugin on top of it. Also, whichever additional solvers you provide in Tabby CAD. Alternatively, you can clone/fork the repo and customise the dockerfiles to your needs; or you can have a look at it and use it for inspiration. If you want to share some effort, I'd be glad to discuss how can I/we reshape hdl/containers for making it more appealing to your needs.
NOTE: unlike MINGW-packages, in the containers ghdl-yosys-plugin is a library. Therefore, there should be no conflict for your clients to have both GHDL and Verific in the same environment.

for Windows I rely on setting PATH for now for DLL loading, but looking into better solution

I don't know whether any better solution exists. The canonical approach on MSYS2 is to install all DLLs to /bin, precisely for having all of them automatically available in the PATH without dealing with additional locations.

Note that static build is easier to make portable, but this is not possible for GUI tools, those that integrate python or others that rely on dynamic loading of plugins.

Indeed... Yet, my very personal opinion is that maintaining a custom build procedure needs to pay off due to some specific feature or use case which is not supported by upstream solutions. In the case of fpga-toolchain or apio, that added value was/is the portability and ease of installation, at the cost of certain features. At the same time, when those projects were created, many EDA tools were not upstreamed to official repositories yet.
Conversely, nowadays most of the tools are already packaged as DEB, RPM and/or PKGBUILD recipes. Therefore, I think that salsa, copr, aur, homebrew, nixos, etc. are a better fit for maintaining a complex multi-arch set of tools. In fact, this is not just a comment. I expect to replace the build procedures in hdl/containers with proper DEB and/or RPM recipes. That's because the added value of containers is the containerization itself. The recipes can and should be shared with "native" users.
IMVHO, your strong point is that you are the developers or relevant contributors of most of the tools in Tabby CAD. Therefore, you have very first hand information about upcoming challenges and potentially conflicting changes. You can foresee the work that packagers will need to do in the following update. You are also in a unique position for adding the features that your clients need, and having them published ASAP. Hence, I would like to very politely ask you to reconsider whether supporting recipes, CI and distribution of 12+ tools on 4+ archs is something that 1-2 people can develop and maintain on their own. It is my very honest believe that you would be more valuable for the open source EDA community if you balanced towards focusing on communication skills; on closing any existing gap between the development of that tools and the packagers in the major distributions. I'm pretty sure you'd get good help if you asked the community "we want help for having nightly DEBs and RPMs of all YosysHQ projects". Then, you could maintain this repository (the Python part) as a wrapper around those DEB, RPM, PKGBUILD and brew recipes. You would focus on your expertise: the integration of the tools in a bundle (not actually building and cross-compiling). At the same time, contributors would not need to learn your custom plumbing, but they'd contribute with their specific knowledge.
Please, note that I'm suggesting this because I know the effort it takes to maintain all these tools on two different environments for amd64 only (and very few multiarch). That is less than half of the work you explained in your scope! In those cases, allowing contributors not to understand the plumbing and allowing myself not to know the usage details of each tool did help all of us move forward. Of course, you might have additional constraints, demands and requirements which I'm not aware of. Hence, please, accept my apologies, should you consider it intrusive.

I have added Windows support for msys2 since that seems natural, but makes things complicated for CI and testing (if you have linux based machines only) so I made docker based one, but still have some limitations there (missing ADA compiler, so no GHDL build possible for now).

Honestly, I'm not sure that will work. Naturally, I suggest you to confirm with some expert (https://gitter.im/msys2/msys2), but my understanding is that MSYS2 cannot be used on Linux. Some users have tried using Wine, but I don't think it works. This is because the MSYS2 project itself would greatly benefit from building all their packages on Linux machines, but they don't/can't. On Linux you get mingw, not MSYS2. Both projects are similar, but not the same since long time ago. You might still be able to build all the tools using mingw/linux, but I would be careful about naming them MSYS2 or mixing them with actual MSYS2 packages.

Will see to improve preview of build status of packages per platform, so it is known what users can expect to have in the final build ( there are certain solvers that are linux only, or just can work on windows for example).

When the different packaging solutions are slightly more mature (in a few months), I'd like to make a table similar to https://hdl.github.io/MINGW-packages/#_packagestools in hdl/packages, showing the tools and versions available in each packaging solution. That will hopefully allow users to pick the one that fits their needs: FPGA/EDA, Verilog/VHDL/SV, sim/synth/formal, CI/embedded/workstation, etc. For a reference, in MSYS2 they compare themselves to Arch and Cygwin: https://packages.msys2.org/outofdate.

In time I also plan to upstream some of the changes to projects used to make scripts easier to maintain but also those projects more compatible with certain OS-es.

That is really nice to hear. In fact, most (if not all) YosysHQ projects do support MSYS2 already, which really helps maintenance of packages. Must be grateful to the people that did it.

Sorry for a bit of a late answer.
First, thank you for your input and suggestions, sorry if I do not address
all your questions, but had a lot of obligations today.
Right TabbyCAD is our product, and regarding software used it is mostly
Verific integration that differentiate it from the open source version.
Regarding DEB, RPM, brew, ... it is something I have already played with,
the issue is that there would be even more combinations (due to the number
of distribution versions you need to support to make sense) and at the end
we still need to deliver something to each customer as binary blob. Also
note that a number of distributions have their own packages for some of the
software we use and we will have conflicts with those (possible to override
in most cases, but still an additional burden).
In this case having one binary distribution for one architecture makes less
effort of maintaining it then writing 5 different recipes and building it
for various distribution versions.
For sure there are pros and cons for each approach, and it is hard to say
something is better until it is late :)
On Wed, Mar 24, 2021 at 1:10 PM Unai Martinez-Corral <
@.***> wrote:

Anyway this project started as my effort of making a build system for our
commercial package, but in mind of greater OS support.
Is "your commercial package" Tabby CAD
https://www.yosyshq.com/tabby-cad-datasheet? Is there any non-open tool
in the bundle apart from Verific's parser/frontend? I only found lists of
the open source tools included.
we have a lot of people interested in using open source stack but have
problems setting all solvers and can't keep up with updating all tools they
need to update.
I would very strongly suggest you to distribute one container, at least,
even if temporarily. In general, I don't like large monolithic containers,
because of technical and conceptual reasons. However, that is the fastest
solution for making any custom set of tools available to any user. That is
because you need to care about a single Linux environment (pick the base
image that you wish). The same image can then be used in CI, on Linux,
Windows or MacOS. Once you have that first problem solved, you can focus on
more granular build and distribution solutions. In a sense, I'm proposing
you to focus on a subset of what you already have, since all the tools are
already built/tested on some Debian/Ubuntu, you avoid all that custom
copying of shared libs.
For formal verification, @tmeissner https://github.com/tmeissner
contributed multiple solvers to
https://hdl.github.io/containers/#_tools_and_images. Precisely, image
formal contains boolector, cvc4, superprove, yices2 and z3, apart from
GHDL, Yosys and SymbiYosys. You can use it as a base and add the Verific
frontend as a plugin on top of it. Also, whichever additional solvers you
provide in Tabby CAD. Alternatively, you can clone/fork the repo and
customise the dockerfiles to your needs; or you can have a look at it and
use it for inspiration. If you want to share some effort, I'd be glad to
discuss how can I/we reshape hdl/containers for making it more appealing to
your needs.
NOTE: unlike MINGW-packages, in the containers ghdl-yosys-plugin is a
library. Therefore, there should be no conflict for your clients to have
both GHDL and Verific in the same environment.
for Windows I rely on setting PATH for now for DLL loading, but looking
into better solution
I don't know whether any better solution exists. The canonical approach on
MSYS2 is to install all DLLs to /bin, precisely for having all of them
automatically available in the PATH without dealing with additional
locations.
Note that static build is easier to make portable, but this is not
possible for GUI tools, those that integrate python or others that rely on
dynamic loading of plugins.
Indeed... Yet, my very personal opinion is that maintaining a custom build
procedure needs to pay off due to some specific feature or use case which
is not supported by upstream solutions. In the case of fpga-toolchain or
apio, that added value was/is the portability and ease of installation, at
the cost of certain features. At the same time, when those projects were
created, many EDA tools were not upstreamed to official repositories yet.
Conversely, nowadays most of the tools are already packaged as DEB, RPM
and/or PKGBUILD recipes. Therefore, I think that salsa, copr, aur,
homebrew, nixos, etc. are a better fit for maintaining a complex multi-arch
set of tools. In fact, this is not just a comment. I expect to replace the
build procedures in hdl/containers with proper DEB and/or RPM recipes.
That's because the added value of containers is the containerization
itself. The recipes can and should be shared with "native" users.
IMVHO, your strong point is that you are the developers or relevant
contributors of most of the tools in Tabby CAD. Therefore, you have very
first hand information about upcoming challenges and potentially
conflicting changes. You can foresee the work that packagers will need to
do in the following update. You are also in a unique position for adding
the features that your clients need, and having them published ASAP. Hence,
I would like to very politely ask you to reconsider whether supporting
recipes, CI and distribution of 12+ tools on 4+ archs is something that 1-2
people can develop and maintain on their own. It is my very honest believe
that you would be more valuable for the open source EDA community if you
balanced towards focusing on communication skills; on closing any existing
gap between the development of that tools and the packagers in the major
distributions. I'm pretty sure you'd get good help if you asked the
community "we want help for having nightly DEBs and RPMs of all YosysHQ
projects". Then, you could maintain this repository (the Python part) as a
wrapper around those DEB, RPM, PKGBUILD and brew recipes. You would focus
on your expertise: the integration of the tools in a bundle (not actually
building and cross-compiling). At the same time, contributors would not
need to learn your custom plumbing, but they'd contribute with their
specific knowledge.
Please, note that I'm suggesting this because I know the effort it takes
to maintain all these tools on two different environments for amd64 only
(and very few multiarch). That is less than half of the work you explained
in your scope! In those cases, allowing contributors not to understand the
plumbing and allowing myself not to know the usage details of each tool did
help all of us move forward. Of course, you might have additional
constraints, demands and requirements which I'm not aware of. Hence,
please, accept my apologies, should you consider it intrusive.
I have added Windows support for msys2 since that seems natural, but makes
things complicated for CI and testing (if you have linux based machines
only) so I made docker based one, but still have some limitations there
(missing ADA compiler, so no GHDL build possible for now).
Honestly, I'm not sure that will work. Naturally, I suggest you to confirm
with some expert (https://gitter.im/msys2/msys2), but my understanding is
that MSYS2 cannot be used on Linux. Some users have tried using Wine, but I
don't think it works. This is because the MSYS2 project itself would
greatly benefit from building all their packages on Linux machines, but
they don't/can't. On Linux you get mingw, not MSYS2. Both projects are
similar, but not the same since long time ago. You might still be able to
build all the tools using mingw/linux, but I would be careful about naming
them MSYS2 or mixing them with actual MSYS2 packages.
Will see to improve preview of build status of packages per platform, so
it is known what users can expect to have in the final build ( there are
certain solvers that are linux only, or just can work on windows for
example).
When the different packaging solutions are slightly more mature (in a few
months), I'd like to make a table similar to
https://hdl.github.io/MINGW-packages/#_packagestools in hdl/packages,
showing the tools and versions available in each packaging solution. That
will hopefully allow users to pick the one that fits their needs: FPGA/EDA,
Verilog/VHDL/SV, sim/synth/formal, CI/embedded/workstation, etc. For a
reference, in MSYS2 they compare themselves to Arch and Cygwin:
https://packages.msys2.org/outofdate.
In time I also plan to upstream some of the changes to projects used to
make scripts easier to maintain but also those projects more compatible
with certain OS-es.
That is really nice to hear. In fact, most (if not all) YosysHQ projects
do support MSYS2 already, which really helps maintenance of packages. Must
be grateful to the people that did it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/YosysHQ/fpga-nightly/issues/1#issuecomment-805770015,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA3UUSEL2LU46PMVI2R34G3TFHJDTANCNFSM4ZWLLVEA
.


How to open .bvh format files?

Thank you very much for your work.
I want to know how to use .bvh file to generate animation,as demonstrated in your video.

You can import the bvh file to Blender to the see same visualization like what we show.
In addition,  if you want to drive a mesh model with this bvh data, it requires a little Animation acknowledge like skining and rigging.


Why are some constants like MPI_REQUEST_NULL statics ?

I've noticed that some constants like MPI_REQUEST_NULL, MPI_COMM_WORLD, etc. are static muts instead of consts. Why is this ? In particular, when can I not read their values because it is undefined behavior to do so ? (e.g. before initializing MPI ?)
static mut is almost impossible to use correctly - https://github.com/rust-lang/rust/issues/53639

E.g. MPI_REQUEST_NULL in:

mpich: https://github.com/pmodels/mpich/blob/45fc41144de975f5bf938c87c036e2231166f269/src/include/mpi.h.in#L93
 #define MPI_REQUEST_NULL   ((MPI_Request)0x2c000000)

openmpi: https://github.com/open-mpi/ompi/blob/c79a4c55a24fba10edfbfa2d5a75ac11e950021e/ompi/include/mpi.h.in#L754
#define MPI_REQUEST_NULL OMPI_PREDEFINED_GLOBAL(MPI_Request, ompi_request_null)

is always a const.

Actually, in this example you showed, OpenMPI's MPI_REQUEST_NULL is NOT a const. It's an extern. Here's the precise define for ompi_request_null, which is what MPI_REQUEST_NULL evaluates to after some casts:
OMPI_DECLSPEC extern struct ompi_predefined_request_t ompi_request_null;

So unfortunately we can't make them const since the MPI standard does not require that they evaluate to constant expressions.

Damn. Does this mean that the value of these is allowed to change during a program?

I think they're defined once the program has been linked, but OpenMPI especially supports dynamic linking, so you don't necessarily know that value until runtime.

Shouldn't then static (as opposed to static mut) be enough ? Or am I allowed to mutate these values ?

Not sure - you'd have to ask the OpenMPI guys. Anything under ffi is a pedantic translation from bindgen. I think we generally treat usage of ffi as "at your own caution" (it DOES require unsafe everywhere).

The MPI specification 3.1 goes into details in section 2.5.4. Most MPI constants are link-time constants. I agree, that they should be static mut. In rsmpi.h, I have made them extern const which the version of bindgen that we have to use translates into static mut. More recent versions of bindgen use static (immutable) instead. Once again, I have to point to #44.

Fixed in a3adac0499e273b407c0040f0da5d30c1fb223c8? What used to be static muts now seem to be static.


rdma-core: 48.0 -> 49.0

Description of changes
https://github.com/linux-rdma/rdma-core/releases/tag/v49.0
Things done

Built on platform(s)

[x] 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

[x] 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/)
23.11 Release Notes (or backporting 23.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

[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test slurm