Improve settings documentation to include possible values for enum types

For example https://beta.ruff.rs/docs/settings/#pydocstyle doesn't say what's the possible values for the type Convention.

Definitely! I wonder if we can autogenerate these.

I think it's a little tricky to autogenerate there, #[option(possible_values = "x,y,z")] certainly will work but it feels tedious, and we don't have access to the actual value type in the proc-macro.
https://github.com/charliermarsh/ruff/blob/ad8693e3deddbd8e178546dad7be5759ebf1a095/ruff_macros/src/config.rs#L119-L159

Yeah. I guess there are few enough values that we can just update them manually as a first pass.

I can do it, don't mind.


Point pip to this repository instead of proxypoke's old repo

I do not have the time. Maybe in a few years.

what should be done to point pip to this repository?

I have no idea :tada:

You may use github repo directly, i.e. pip install git+https//github.com/OliverUv/quickswitch-for-i3


HDFS-10753.Method invocation in log can be replaced by variable becau…

…se the variable's toString method contains more info

https://issues.apache.org/jira/browse/HDFS-10753 is superceded by HDFS-10752. Closing.


s3 bucket policy question

** Question : **
I'm trying to block deployment of s3 buckets with a bucket policy of Allowing s3:*
Below is my Feature file, based very much on the documentation for overpermissive roles:
Feature: Terraform-BDD
  Scenario: Ensure s3 buckets deployed privately
    Given I have aws_s3_bucket_policy defined
    When it contains policy
    And it contains Statement
    And its Effect is Allow
    And its Action contains s3
    Then its value must not match the "\*" regex

The output shows problems in the And/Action line:
Scenario: Ensure s3 buckets deployed privately
        Given I have aws_s3_bucket_policy defined
        When it contains policy
        And it contains Statement
        And its Effect is Allow
	💡 SKIPPING: Can not find s3 Action in .
        And its Action contains s3
        Then its value must not match the "\*" regex

Please note that I've tried this with s3, s3:*, s3:ANY, *, ANY, and a few others in that spot.
Could you please let me know what I'm doing wrong here?
Thank you.

Hi @DolpheusLabs ,
Thanks for the issue :tada:. Multiple reasons your test is failing.

And its Action contains s3 will fail on anything that is s3:* or something. Since it is searching for s3 not s3*..
Normally And its Action is s3:* should work, but just found out that * character is not allowed for a property. Just added * to the match list within the code in my local, and it works. Will release a new version with that.

After having the new release, this test scenario will work ;
Feature: Terraform-BDD
  Scenario: Ensure s3 buckets deployed privately
    Given I have aws_s3_bucket_policy defined
    When it contains policy
    And it contains Statement
    And its Effect is Allow
    And its Action contains s3:*
    And it contains resource
    Then its value must not match the "\*" regex

till that, as a work around, this should work without And its Action contains ... step ;
Feature: Terraform-BDD
  Scenario: Ensure s3 buckets deployed privately
    Given I have aws_s3_bucket_policy defined
    When it contains policy
    And it contains Statement
    And its Effect is Allow
    And it contains resource
    Then its value must not match the "\*" regex

Right on, thank you! I've got the workaround in place and working, will update to that commit later on.


EACCES: permission denied, doesn't open modal asking for user/pass

VSCode Version: Code 1.13.1 (379d2efb5539b09112c793d3d9a413017d736f89, 2017-06-14T18:13:05.928Z)
OS Version: Darwin x64 16.6.0
Extensions:

Extension
Author
Version

vscode-docker
PeterJausovec
0.0.16

vscode-multi-line-tricks
bigous
0.0.3

vscode-eslint
dbaeumer
1.2.11

githistory
donjayamanne
0.2.0

python
donjayamanne
0.6.5

vscode-babel-coloring
dzannotti
0.0.4

diff-tool
jinsihou
0.0.1

Go
lukehoban
0.6.62

terraform
mauve
0.0.16

debugger-for-chrome
msjsdiag
3.1.4

shellcheck
timonwong
0.1.0

vscode-proto3
zxh404
0.1.1

Steps to Reproduce:

Run command to edit a file not owned by the current user, like code /etc/hosts
Save the file
See error

Failed to save 'hosts': A system error occured (EACCES: permission denied, open '/private/etc/hosts')

Previously, VS Code seemed to handle this scenario properly by opening a window asking for admin user/password to escalate the save command. If I'm incorrect, apologies. The only other issues I see on this have proposed solutions that involve changing the owner of the files, which is not a correct fix, particularly in this scenario.

No, we never asked for user level elevation, but this is a valid request that has been reported in duplicates already.

My mistake, then - I totally thought this was a regression. Sorry about the noise!


Add: India Daily Live

Channel Name
India Daily Live
Alternative Names (optional)
No response
Network (optional)
No response
Owners (optional)
No response
Country
IN
Subdivision (optional)
No response
City (optional)
Noida
Broadcast Area
c/IN
Languages
hin
Categories (optional)
news
NSFW
FALSE
Launched (optional)
2023-07-03
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://www.theindiadaily.com/
Logo
https://www.indiantelevision.com/sites/default/files/images/tv-images/2014/09/02/live.jpg
Notes
No response

Fixed


Internal error while sending eth_getStorageAt

Instructions
Please fill out the template below to the best of your ability and include a label indicating which tool/service you were working with when you encountered the problem.
Problem
When sending this  {"jsonrpc": "2.0", "method": "eth_getStorageAt", "id": 659307, "params": ["0x2a03a891add2dc6d0f7b94419086630ba5cb65b6", "0x0", "latest"]}  payload to evm-gw paired with the public AN endpoint, it works, but when we send the request to evm-gw connected to our own local AN, the req fails with internal error. This seems to be an isolated case, since many other tested methods work fine in the latter setup.
Using default access node running configs (provided in the setup instructions) and similar for evm-gateway with the exception of the following parameter: --init-cadence-height=211176670
Steps to Reproduce
Send curl req with the above payload to a node running with that specific cadence height when spinned up.

Hey @AntonieDavid, thanks for reporting 🙏
For this to work with a local AN, the execution data API should be enabled, as far as I know.
For the public ANs, this is already enabled, that's why it works.
In the near future, couple of weeks, we will roll out some changes, and the eth_getStorageAt will be powered by the EVM Gateway's local state index, without the need to get the necessary data from an AN.

hey @m-Peter - @AntonieDavid has enabled execution data API on the Access node but still runs into the same issue.
Anything else he could check?


[PE-D][Tester D] Error in description of edit in UG

edit 3 m/ t/Borrowed $10 Edit the tags of the 2nd person to be Borrowed $10 plus the existing tag of that person.
edit 3 m/ g/CS2103T Edit the groups of the 2nd person to be CS2103T plus the existing groups of that person.

From the UG, the tags and groups of the 3rd person is edited instead.

Labels: severity.Low type.DocumentationBug
original: joellow88/ped#1

Completed. PR #162


Handle subscriptions with deleted products

When a product is soft-deleted, it should also be removed from all active subscriptions, or perhaps we shouldn't allow deleting a product that has active subscriptions associated.

Since we can't assume the subscribable class will always be a subclass of Spree::Variant, it may be harder to fix subscriptions on subscribable deletion.
If we want to allow products deletion when they're still included in an active subscriptions, I see two main ways:

handle the case while processing the subscription, checking for subscribables existence and removing them before processing, if needed
handle the case in a cleaner way through decoration of the subscribable class.

in that case we could apply the decoration only if the class is a Spree::Variant, or maybe the restriction could be that it needs to be an ActiveRecord model and then hook up the fix on its after_deletion or after_discard callbacks.

I would rather go for the second option, any opinion?

@luca-landa thanks for the analysis here! I think removing the variant from any associated subscriptions is the right way to go here. I also think we should only do this when we're dealing with Spree::Variant, and just delegate the logic to the user in case they're using a custom subscribable class (which is unlikely, anyway).

does it make sense to delete the Spree::Variant from every subscription? Or should it be removed from active subscriptions only? (what about soft-deleting it from every subscription?)


Suggestions Wout

Starting from Robbin's changes.

Add figure on licenses used in JPR.
Box on how to get started with OSS.
Paragraph on funding agency mandates.
Small edits and comments throughout.

That's not actually what I wanted to do, silly Github.


[feature] ability to re-run an exited pod (with new --exec and app args)

It would be great if after a pod exited, there was the ability to start that same pod back up, and potentially change the exec/args provided to the pod apps.
However this is done or is implemented is a detail. I know that pods are designed such that they're 'run once', which is fine, another way this could work is just creating a full copy of the existing, exited pod and spawning a new container with that as the base, rather than an ACI directly.
Use cases:

Faster iteration speed when testing containers (don't have to rebuild an ACI for every single change, not to mention rkt/acbuild are both fairly minimal in regards to caching, so this really sucks).
Debugging. I want to take an exited container, and then later --exec /bin/bash into it later so I can introspect the container and figure out what might be wrong with my container.
Interactive container building (non automated ACI building). I want to start with a base OS, do some stuff. Come back to it, do more stuff. Eventually when I'm done experimenting, I'd like to export the pod as an ACI (another feature which would be nice).

https://github.com/coreos/rkt/issues/551

I was looking everywhere for an existing issue, didn't see that one. I can add my use-cases to the other issue if you like.

Yes please.


Many-To-Many associations are NOT versioned

Hi everybody,
i'm wondering why this TODO is left, i'm currently diving deeper in to Doctrine and Symfony2 and have currently the problem to solve the audit of all my entities which includes also the n to m relations.
Could anybody give me an advise how to solve this within this Bunde  ?
Thx in Advance

I would like to see this feature too.

Is this bundle alive @DavidBadura? Have there been discussions about adding this?

@peschee we do not have any active maintainers with good knowledge of the codebase, unfortunately. This extension was created for one small project of ours which is still alive and well. But since that project is a simple use case and we haven't had use for the extension in other projects, knowledge isn't what it could be. Since the creator of the extension is no longer involved in the development, all knowledge is second hand anyways.
I have been meaning to give a heads up in the README about this, but haven't gotten around to it yet. Anyone around who has experience in transitioning a project to a new maintainer or any suggestions on finding new maintainers are very welcome.

I see, thanks for the writeup. We are currently considering using this audit bundle for a project instead of writing the audit functionality from scratch.
As of now, we don't have Many-To-Many relationships. I just wanted to know while evaluating, if that feature is available or not. The {{README}} states Many-To-Many is unsupported. However, looking at #99 it seems implemented.
Should we miss something during our implementation, we'll try to add it back to the bundle. As for the project transition.

I have the README updated


Reorganize files so they are named like their primary provide

This organizes files in the library so they are named like their (primary) provide.  This serves as the foundation for having one provide per file (see #5679).
This also adds a new set of tests that are run in Node.  Currently, the only new tests make assertions about their being only one provide per file and having the file named like the provide.  These tests fail, so they are not run as part of npm test.  You can run the tests manually with npm run test-node.  When these tests are passing, we can include them as part of the existing test target.

I've added a few more commits with patterns that I think we can follow.
In the case of ol/color/color.js, there is no reason for the color directory, so I've renamed this to ol/color.js.
In the case of ol/control/controldefaults.js, this provides ol.control, so the file should be named either ol/control.js or ol/control/index.js.  Since we have other provides under ol.control.*, I've moved this to ol/control/index.js (and people will be able to require('ol/control').defaults).
Note that this new pattern for naming files will result in multiple files with the same name (but with different paths).  E.g. there may be many index.js files in the library.  This requires that developers are comfortable quickly opening files based on path, not just the filename alone.

Ok, this is ready for review.
There are multiple parts of addressing #5679.  This pull request is mainly about the first part: naming files like their primary provide.  In most cases this involved renaming files.  In some cases this involved renaming provides/types.  I've documented the latter in the upgrade notes (and this will not be relevant to people who only use the @api symbols).
There are two tests in the new one-provide.js file.  With the changes here, the "has a path that maps to the provide" test passes.
The next part of the work will be to rework files with multiple provides.  There are two alternatives for addressing this.  The first is to create new files for the provides (breaking ol/webgl/shader.js into three files in bdc998af5517af6b02ef37c097d5473405f16673 is an example of this).  The second is to add properties to things already provided (7d3d675c5d11c2e2468768fb0d67b4d2865975da is an example of this type of change).
When this next part of work is done, both tests in one-provide.js will pass and we can run it as part of the normal test target.  I'll leave that next part of work to be done elsewhere.

Hats off for this awesome work, Tim.

Yes, please merge. I think this is huge step in the right direction. Thanks again
!

Ok, rebased.  Will merge when green.

To make sure that other changes conform with the same, I've added the 'has a path that maps to the provide' test to our ci target.
So, make test-node runs this one test, asserting that files are named like their "default export" (in future terms).  After we get the other part working (one provide per file), we can run all of the one-provide tests.  All Node tests can be run with npm run test-node.

👍 I much prefer the new names, simpler and IMHO cleaner than the old ol/control/attributioncontrol.js pattern

In the case of ol/control/controldefaults.js, this provides ol.control, so the file should be named either ol/control.js or ol/control/index.js. Since we have other provides under ol.control.*, I've moved this to ol/control/index.js (and people will be able to require('ol/control').defaults).

@tschaub are you sure using index.js is standard? According to this thread it is specific to node and some transpilers.
The closure documentation, states that import foo from './folder/source' will be interpreted as "load the folder/source.js" (not "folder/source/index.js`).
Based on the two links above, it looks like we should avoid using index.js for now.

and I was just about to comment that this can be a bit confusing. I was just looking at ol/has.js which requires ol.dom and ol.webgl; ol.dom is in ol/dom.js whereas ol.webgl is in ol/webgl/index.js. There's no way of telling from the require which pattern this follows.
Also, with this pattern, shouldn't source.jsdoc be in source/index.jsdoc and style.jsdoc in style/index.jsdoc?

in ES6, the whole question of module specifiers is still to be decided. Initial browser implementations (using <script type="module">) follow script tag rules: absolute and relative urls only


Is it possible to pre-record in go2rtc?

Is it possible to pre-record in go2rtc?
&pre-record=5&
http://localhost:1984/api/stream.mp4?src=camera1&mp4=flac&pre-record=5&duration=5&filename=record.mp4
Thank you.
Record from H264 or H265 camera
Record from service call to the future. Doesn't support loopback.
mp4=flac - adds support PCM audio family
filename=record.mp4 - set name for downloaded file
service: telegram_bot.send_video
data:
url: http://localhost:1984/api/stream.mp4?src=camera1&mp4=flac&duration=5&filename=record.mp4  # duration in seconds
target: 123456789

Yes i would be interested in this as well ! I would love to use go2rtc to get a clip from a camera for example if someone rings the doorbell or a motion sensor is being triggered.

It's a shame that few people are interested in this feature.


Add more context to ErrUnderestimatedFee error

[x] Return candidateTx and estimated witnessCount in API 500 error ErrUnderestimatedFee

This is useful for debugging in case of errors

Comments

Byron part of KeyWitnessCount will be used in #3765

Issue Number

ADP-2268 / ADP-2613

Thanks @jonathanknowles!
bors r+

bors r+


Input for super-indexes doesn't work well

I might be doing something wrong but when I try to introduce
a super-index I just can't.
I type \ + ˆ  or \ + ˆ+ SPC then I just can't get the super intex.
If I just type \ and use in the bottom panel that appears with the symbols I can.
Then I can put whaevert I want by choosing ^ followed by the number or whatever BUT clicking
with the mouse, which is so annoying.
Any clue?

It's working fine on my laptop, could it be input-method or keyboard-layout-related stuff?

You're right.  It's working fine with "US"  instead of the US international option. weirdo.


"application.has is not a function" booting up 0.6.0-beta.5

Having trouble booting up Torii 0.6.0-beta.5 on Ember 1.13.10. App won't boot with an application.has is not a function TypeError in torii.js on line 26. Looks like the error maps to line 37 of lib/torii/bootstrap/torii.js.

also present in 2.0.2

+1

also see #225; this is occuring in the ESA tests for 2.0.1, 2.0.0, 1.12.1, #beta and #canary

Made a pull request that should fix this, #234

Please check 0.6.0-beta.7 :-) Thank you!

Fwiw getting beta.7 checked out is the last hurdle for a 0.6.0 release :grin:

Ember Simple Auth build is green again: https://travis-ci.org/simplabs/ember-simple-auth
👍

sessionServiceName works great with the authenticatedRoute DSL and this error no longer appears on bootup! Thank you all! :+1:


Gettin Started Full fails on Ubuntu

Hi,
Following the steps of https://github.com/black-parrot/black-parrot/blob/master/docs/getting_started.md,  namely:
Prereq:
sudo apt-get install autoconf automake autotools-dev curl libmpc-dev libmpfr-dev libgmp-dev gawk build-essential bison flex texinfo gperf libtool patchutils bc zlib1g-dev libexpat-dev wget byacc device-tree-compiler python gtkwave
Download/build:
# Clone the latest repo
git clone https://github.com/black-parrot/black-parrot.git
cd black-parrot
# make prep is a meta-target which will build the RISC-V toolchains, programs and microcode
#   needed for a full BlackParrot evaluation setup.
# Users who are changing code can use the 'libs' 'progs' or 'ucode' targets as appropriate
# For faster builds, make prep -j is parallelizable!
make prep
On Ubuntu 18.04.5v LTS fails after ~1H of build time fails with these messages:
riscv64-unknown-linux-gnu-g++  links-dso-program.cc -c -I/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/ -isystem /home/glenn/work/chipyard/riscv-tools-install/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/include/c++/9.2.0 -isystem /home/glenn/work/chipyard/riscv-tools-install/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/include/c++/9.2.0/riscv64-unknown-linux-gnu -isystem /home/glenn/work/chipyard/riscv-tools-install/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/include/c++/9.2.0/backward -mcmodel=medany -g -O2 -Wall -Wwrite-strings -Wundef -fmerge-all-constants -frounding-math -fno-stack-protector          -I../include -I/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support  -I/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64  -I../sysdeps/unix/sysv/linux/riscv/rv64  -I../sysdeps/unix/sysv/linux/riscv  -I../sysdeps/riscv/nptl  -I../sysdeps/unix/sysv/linux/generic  -I../sysdeps/unix/sysv/linux/wordsize-64  -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux  -I../sysdeps/nptl  -I../sysdeps/pthread  -I../sysdeps/gnu  -I../sysdeps/unix/inet  -I../sysdeps/unix/sysv  -I../sysdeps/unix  -I../sysdeps/posix  -I../sysdeps/riscv/rv64/rvd  -I../sysdeps/riscv/rv64/rvf  -I../sysdeps/riscv/rvf  -I../sysdeps/riscv/rvd  -I../sysdeps/riscv/rv64  -I../sysdeps/riscv  -I../sysdeps/init_array  -I../sysdeps/ieee754/ldbl-128  -I../sysdeps/ieee754/dbl-64  -I../sysdeps/ieee754/flt-32  -I../sysdeps/wordsize-64  -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. -I../libio -I. -nostdinc -isystem /home/glenn/work/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/include -isystem /home/glenn/work/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/include-fixed -isystem /home/glenn/work/black-parrot/external/riscv-gnu-toolchain/linux-headers/include  -D_LIBC_REENTRANT -include /home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/libc-modules.h -DMODULE_NAME=nonlib -include ../include/libc-symbols.h       -DTOP_NAMESPACE=glibc -o /home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program.o -MD -MP -MF /home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program.o.dt -MT /home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program.o riscv64-unknown-linux-gnu-gcc  -nostdlib -nostartfiles -o /home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program    -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both /home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/csu/crt1.o /home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/csu/crti.o riscv64-unknown-linux-gnu-gcc   --print-file-name=crtbegin.o/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program.o -lstdc++ -lgcc -lgcc_s  -Wl,-dynamic-linker=/lib/ld-linux-riscv64-lp64.so.1 -Wl,-rpath-link=/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/math:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/dlfcn:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/nss:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/nis:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/rt:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/resolv:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/mathvec:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/crypt:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/nptl /home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/libc.so.6 /home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/libc_nonshared.a -Wl,--as-needed /home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/ld.so -Wl,--no-as-needed -lgcc riscv64-unknown-linux-gnu-gcc   --print-file-name=crtend.o/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/csu/crtn.o /home/glenn/work/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: cannot find -lstdc++ /home/glenn/work/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: cannot find -lgcc_s collect2: error: ld returned 1 exit status ../Rules:193: recipe for target '/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program' failed make[7]: *** [/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program] Error 1 make[7]: Leaving directory '/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/support' Makefile:258: recipe for target 'support/others' failed make[6]: *** [support/others] Error 2 make[6]: Leaving directory '/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/riscv-glibc' Makefile:9: recipe for target 'all' failed make[5]: *** [all] Error 2 make[5]: Leaving directory '/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64' Makefile:234: recipe for target 'stamps/build-glibc-linux-rv64imafd-lp64' failed make[4]: *** [stamps/build-glibc-linux-rv64imafd-lp64] Error 2 make[4]: Leaving directory '/home/glenn/work/black-parrot/external/riscv-gnu-toolchain' /home/glenn/work/black-parrot/external/Makefile.tools:46: recipe for target 'gnu_build' failed make[3]: *** [gnu_build] Error 2 make[3]: Leaving directory '/home/glenn/work/black-parrot' /home/glenn/work/black-parrot/external/Makefile.tools:82: recipe for target '/home/glenn/work/black-parrot/external/touchfiles/gnu.70063d751135fb22e754ff14bc969ffe9e905fbd' failed make[2]: *** [/home/glenn/work/black-parrot/external/touchfiles/gnu.70063d751135fb22e754ff14bc969ffe9e905fbd] Error 2 make[2]: Leaving directory '/home/glenn/work/black-parrot' Makefile:62: recipe for target 'tools' failed make[1]: *** [tools] Error 2 make[1]: Leaving directory '/home/glenn/work/black-parrot' Makefile:24: recipe for target 'prep' failed make: *** [prep] Error 2
If someone can help figure out this issue, I will be happy to test and verify.  I am totally new too BP so I do not even know were to start looking.   It looks like an error in a ENV Var.
Thank you!

Maybe this will help:
https://askubuntu.com/questions/346377/cannot-find-lgcc-s
On Thu, Feb 11, 2021 at 10:16 AM gabaxter<EMAIL_ADDRESS>wrote:

Hi,
Following the steps of
https://github.com/black-parrot/black-parrot/blob/master/docs/getting_started.md,
namely:
Prereq:
sudo apt-get install autoconf automake autotools-dev curl libmpc-dev
libmpfr-dev libgmp-dev gawk build-essential bison flex texinfo gperf
libtool patchutils bc zlib1g-dev libexpat-dev wget byacc
device-tree-compiler python gtkwave
Download/build:
Clone the latest repo
git clone https://github.com/black-parrot/black-parrot.git
cd black-parrot
make prep is a meta-target which will build the RISC-V toolchains,
programs and microcode
needed for a full BlackParrot evaluation setup.
Users who are changing code can use the 'libs' 'progs' or 'ucode'
targets as appropriate
For faster builds, make prep -j is parallelizable!
make prep
On Ubuntu 18.04.5v LTS fails after ~1H of build time fails with these
messages:
riscv64-unknown-linux-gnu-g++ links-dso-program.cc -c
-I/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/
-isystem
/home/glenn/work/chipyard/riscv-tools-install/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/include/c++/9.2.0
-isystem
/home/glenn/work/chipyard/riscv-tools-install/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/include/c++/9.2.0/riscv64-unknown-linux-gnu
-isystem
/home/glenn/work/chipyard/riscv-tools-install/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/include/c++/9.2.0/backward
-mcmodel=medany -g -O2 -Wall -Wwrite-strings -Wundef -fmerge-all-constants
-frounding-math -fno-stack-protector -I../include
-I/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support
-I/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64
-I../sysdeps/unix/sysv/linux/riscv/rv64 -I../sysdeps/unix/sysv/linux/riscv
-I../sysdeps/riscv/nptl -I../sysdeps/unix/sysv/linux/generic
-I../sysdeps/unix/sysv/linux/wordsize-64
-I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux
-I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu
-I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix
-I../sysdeps/posix -I../sysdeps/riscv/rv64/rvd -I../sysdeps/riscv/rv64/rvf
-I../sysdeps/riscv/rvf -I../sysdeps/riscv/rvd -I../sysdeps/riscv/rv64
-I../sysdeps/riscv -I../sysdeps/init_array -I../sysdeps/ieee754/ldbl-128
-I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32
-I../sysdeps/wordsize-64 -I../sysdeps/ieee754 -I../sysdeps/generic -I..
-I../libio -I. -nostdinc -isystem
/home/glenn/work/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/include
-isystem
/home/glenn/work/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/include-fixed
-isystem
/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/linux-headers/include
-D_LIBC_REENTRANT -include
/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/libc-modules.h
-DMODULE_NAME=nonlib -include ../include/libc-symbols.h
-DTOP_NAMESPACE=glibc -o
/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program.o
-MD -MP -MF
/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program.o.dt
-MT
/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program.o
riscv64-unknown-linux-gnu-gcc -nostdlib -nostartfiles -o
/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program
-Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both
/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/csu/crt1.o
/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/csu/crti.o
riscv64-unknown-linux-gnu-gcc --print-file-name=crtbegin.o/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program.o
-lstdc++ -lgcc -lgcc_s -Wl,-dynamic-linker=/lib/ld-linux-riscv64-lp64.so.1
-Wl,-rpath-link=/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/math:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/dlfcn:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/nss:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/nis:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/rt:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/resolv:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/mathvec:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/crypt:/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/nptl
/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/libc.so.6
/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/libc_nonshared.a
-Wl,--as-needed
/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/ld.so
-Wl,--no-as-needed -lgcc riscv64-unknown-linux-gnu-gcc
--print-file-name=crtend.o/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/csu/crtn.o
/home/glenn/work/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld:
cannot find -lstdc++
/home/glenn/work/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld:
cannot find -lgcc_s collect2: error: ld returned 1 exit status
../Rules:193: recipe for target
'/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program'
failed make[7]: ***
[/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/support/links-dso-program]
Error 1 make[7]: Leaving directory
'/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/support'
Makefile:258: recipe for target 'support/others' failed make[6]: ***
[support/others] Error 2 make[6]: Leaving directory
'/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/riscv-glibc'
Makefile:9: recipe for target 'all' failed make[5]: *** [all] Error 2
make[5]: Leaving directory
'/home/glenn/work/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64'
Makefile:234: recipe for target 'stamps/build-glibc-linux-rv64imafd-lp64'
failed make[4]: *** [stamps/build-glibc-linux-rv64imafd-lp64] Error 2
make[4]: Leaving directory
'/home/glenn/work/black-parrot/external/riscv-gnu-toolchain'
/home/glenn/work/black-parrot/external/Makefile.tools:46: recipe for target
'gnu_build' failed make[3]: *** [gnu_build] Error 2 make[3]: Leaving
directory '/home/glenn/work/black-parrot'
/home/glenn/work/black-parrot/external/Makefile.tools:82: recipe for target
'/home/glenn/work/black-parrot/external/touchfiles/gnu.70063d751135fb22e754ff14bc969ffe9e905fbd'
failed make[2]: ***
[/home/glenn/work/black-parrot/external/touchfiles/gnu.70063d751135fb22e754ff14bc969ffe9e905fbd]
Error 2 make[2]: Leaving directory '/home/glenn/work/black-parrot'
Makefile:62: recipe for target 'tools' failed make[1]: *** [tools] Error 2
make[1]: Leaving directory '/home/glenn/work/black-parrot' Makefile:24:
recipe for target 'prep' failed make: *** [prep] Error 2
If someone can help figure out this issue, I will be happy to test and
verify. I am totally new too BP so I do not even know were to start
looking. It looks like an error in a ENV Var.
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/black-parrot/black-parrot/issues/757, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFG5AAPISFMXNI77FJOEYLS6QNGBANCNFSM4XPJVFRQ
.

It seems odd that running the prereq step would leave the system in a state that it doesn't know about libgcc. That post is helpful for determining if ldconfig knows about the path, but I'm not sure it gives a user-friendly solution.
Perhaps explicitly installing a relatively recent version of gcc and g++ and making those the default versions would resolve?

Thank you for the quick response!
glenn@xxxx:~/work/black-parrot/external(master)$ cd /home/glenn/work/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/
glenn@xxxx:~/work/black-parrot/external/riscv64-unknown-linux-gnu/bin(master)$ ls
ar  as  ld  ld.bfd  nm  objcopy  objdump  ranlib  readelf  strip
Those are the tools installed at the location.  The repo is designed to self get everything, so it is not referring to prerequisite tools since those will be in /usr/bin or /usr/local/bin.
I was concerned it generated correct paths, but in looking at it, it seems to have done so.   Not sure what else I can offer.  Let me know if you want to see any particular system path.

Check out the apt-get install command in the Dockerfile we provide (which launches an Ubuntu 18.04 image). https://github.com/black-parrot/black-parrot/blob/master/Dockerfile
From a brief scan, it looks like it installs a couple extra things than are listed in the getting started guide. To me it looks like the error is occurring while building the RISC-V gcc toolchain submodule, so my best guess is a missing dependency for the gcc build. You could also try running the prereq installs listed on the toolchain repo (https://github.com/riscv/riscv-gnu-toolchain) then rebuilding.
If you have multiple cores to spare you can use make prep -jN where N is some number of cores to do the BP make in parallel (this can significantly speed up build time).

I took the docker apt, and it is different from what is in readme.  It looks like python-yaml is missing.  Here is the complete output of running the docker apt:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libexpat1-dev' instead of 'libexpat-dev'
autoconf is already the newest version (2.69-11).
automake is already the newest version (1:1.15.1-3ubuntu2).
autotools-dev is already the newest version (20180224.1).
bc is already the newest version (1.07.1-2).
bison is already the newest version (2:3.0.4.dfsg-1build1).
build-essential is already the newest version (12.4ubuntu1).
device-tree-compiler is already the newest version (1.4.5-3).
flex is already the newest version (2.6.4-6).
gawk is already the newest version (1:4.1.4+dfsg-1build1).
libgmp-dev is already the newest version (2:6.1.2+dfsg-2).
libmpc-dev is already the newest version (1.1.0-1).
libmpfr-dev is already the newest version (4.0.1-1).
libtool is already the newest version (2.4.6-2).
patchutils is already the newest version (0.3.4-2).
pkg-config is already the newest version (0.29.1-0ubuntu2).
python is already the newest version (2.7.15~rc1-1).
zlib1g-dev is already the newest version (1:1.2.11.dfsg-0ubuntu2).
byacc is already the newest version (20140715-1build1).
gperf is already the newest version (3.1-1).
gtkwave is already the newest version (3.3.86-1).
swig is already the newest version (3.0.12-1).
texinfo is already the newest version (6.5.0.dfsg.1-2).
apt-utils is already the newest version (1.6.12ubuntu0.2).
bash is already the newest version (4.4.18-2ubuntu1.2).
curl is already the newest version (7.58.0-2ubuntu3.12).
gettext-base is already the newest version (<IP_ADDRESS>-6ubuntu0.3).
git is already the newest version (1:2.17.1-1ubuntu0.7).
libexpat1-dev is already the newest version (2.2.5-3ubuntu0.2).
python3-dev is already the newest version (3.6.7-1~18.04).
python3-dev set to manually installed.
tzdata is already the newest version (2021a-0ubuntu0.18.04).
vim is already the newest version (2:8.0.1453-1ubuntu1.4).
wget is already the newest version (1.19.4-1ubuntu2.2).
The following package was automatically installed and is no longer required:
  libllvm9
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
  python-yaml
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 115 kB of archives.
After this operation, 479 kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 python-yaml amd64 3.12-1build2 [115 kB]
Fetched 115 kB in 0s (520 kB/s)
Selecting previously unselected package python-yaml.
(Reading database ... 246021 files and directories currently installed.)
Preparing to unpack .../python-yaml_3.12-1build2_amd64.deb ...
Unpacking python-yaml (3.12-1build2) ...
Setting up python-yaml (3.12-1build2) ...
I then ran
make prep -j 8
After about 20 minutes it made is much farther, but still failed:
...
pypy3.6-v7.3.2-linux64/lib-python/3/antigravity.py
cd /home/glenn/work/black-parrot/external/bsg_sv2v/tools/pypy3; mv pypy3.6-v7.3.2-linux64/* .
cd /home/glenn/work/black-parrot/external/bsg_sv2v/tools/pypy3; rmdir pypy3.6-v7.3.2-linux64/
mkdir -p /home/glenn/work/black-parrot/external/bsg_sv2v/tools
virtualenv -p /home/glenn/work/black-parrot/external/bsg_sv2v/tools/pypy3/bin/pypy3 /home/glenn/work/black-parrot/external/bsg_sv2v/tools/virtual_env
/bin/bash: virtualenv: command not found
Makefile:144: recipe for target '/home/glenn/work/black-parrot/external/bsg_sv2v/tools/virtual_env' failed
make[4]: *** [/home/glenn/work/black-parrot/external/bsg_sv2v/tools/virtual_env] Error 127
make[4]: Leaving directory '/home/glenn/work/black-parrot/external/bsg_sv2v'
/home/glenn/work/black-parrot/external/Makefile.tools:77: recipe for target 'bsg_sv2v_build' failed
make[3]: *** [bsg_sv2v_build] Error 2
make[3]: Leaving directory '/home/glenn/work/black-parrot'
/home/glenn/work/black-parrot/external/Makefile.tools:86: recipe for target '/home/glenn/work/black-parrot/external/touchfiles/bsg_sv2v.03f1e921ef9319218798a5a8826b79dcc8b19056' failed
make[2]: *** [/home/glenn/work/black-parrot/external/touchfiles/bsg_sv2v.03f1e921ef9319218798a5a8826b79dcc8b19056] Error 2
make[2]: Leaving directory '/home/glenn/work/black-parrot'
Makefile:62: recipe for target 'tools' failed
make[1]: *** [tools] Error 2
make[1]: Leaving directory '/home/glenn/work/black-parrot'
Makefile:24: recipe for target 'prep' failed
make: *** [prep] Error 2
This in turn looks like another dependency?
/bin/bash: virtualenv: command not found
Thoughts?

On a different but related topic, the docker flow just finally failed as well (after ~8H of run on high end MacBook Pro).  Here is what I believe are the initial location of the error. This is using Docker Desktop on Mac, starting Docker Desktop and then running the docker install commands from the local MacOS shell.  AFAIK, this should work.  If not, please let me know how the docker portion is to run.
riscv64-unknown-linux-gnu-gcc    -nostdlib -nostartfiles -r -o /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os '-Wl,-(' /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/dl-allobjs.os /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/rtld-libc.a -lgcc '-Wl,-)'
-Wl,-Map,/home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os.map
riscv64-unknown-linux-gnu-gcc    -nostdlib -nostartfiles -shared -o /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/ld.so.new
-Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both -Wl,-z,defs
/home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os -Wl,--version-script=/home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/ld.map
-Wl,-soname=ld-linux-riscv64-lp64.so.1
-Wl,-defsym=_begin=0
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function process_envvars': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/rtld.c:2493: undefined reference to __GI___open64_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function dl_main': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/rtld.c:1333: undefined reference to __access'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/rtld.c:2194: undefined reference to __access' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function is_dst':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:211: undefined reference to __GI___close_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function is_trusted_path_normalize':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:128: undefined reference to __GI___fxstat64' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:166: undefined reference to __GI___close_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_map_segments': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/./dl-map-segments.h:56: undefined reference to __lseek'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/./dl-map-segments.h:60: undefined reference to __GI___read_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/./dl-map-segments.h:73: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_map_object_from_fd': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:995: undefined reference to __GI___close_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1198: undefined reference to __GI___close_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function elf_get_dynamic_info':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/get-dynamic-info.h:48: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/get-dynamic-info.h:131: undefined reference to __GI___close_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_map_object_from_fd': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:981: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1291: undefined reference to __GI___open64_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1304: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1374: undefined reference to __GI___read_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1342: undefined reference to __lseek'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1349: undefined reference to __GI___read_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:998: undefined reference to __GI___close_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:998: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function add_path':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:2264: undefined reference to __lseek' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function open_verify':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1455: undefined reference to __GI___read_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1546: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function elf_machine_matches_host': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/../sysdeps/riscv/dl-machine.h:71: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function open_verify': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1667: undefined reference to __GI___fxstat64'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1668: undefined reference to __GI___close_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1668: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1582: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1657: undefined reference to __GI___xstat64'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function open_path': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:1821: undefined reference to __GI___close_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_map_object': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-load.c:2171: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function add_dependency': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-lookup.c:647: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_setup_hash': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-lookup.c:944: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function elf_machine_rela': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/../sysdeps/riscv/dl-machine.h:214: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/../sysdeps/riscv/dl-machine.h:191: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os:/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/../sysdeps/riscv/dl-machine.h:194: more undefined references to rtld_errno' follow
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_fini': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-fini.c:73: undefined reference to __GI___open64_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-fini.c:87: undefined reference to __GI___fxstat64' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-fini.c:94: undefined reference to __GI___close_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function match_symbol': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-version.c:100: undefined reference to __GI___open64_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _itoa_word': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/../sysdeps/generic/_itoa.h:76: undefined reference to __GI___fxstat64'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_check_map_versions': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-version.c:225: undefined reference to __GI___close_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function match_symbol': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-version.c:134: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_check_map_versions': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-version.c:218: undefined reference to __GI___close_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function match_symbol': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-version.c:66: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-version.c:80: undefined reference to __GI___close_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_check_map_versions':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-version.c:357: undefined reference to __lseek' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function match_symbol':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-version.c:144: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-version.c:143: undefined reference to __GI___write_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-version.c:143: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_check_map_versions':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-version.c:290: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function __GI__dl_allocate_tls_init':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-tls.c:437: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_load_cache_lookup':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-cache.c:295: undefined reference to __libc_check_standard_fds' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function tunable_initialize':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-tunables.c:149: undefined reference to __GI___open64_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-tunables.c:158: undefined reference to __GI___read_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function __tunable_set_val': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-tunables.c:163: undefined reference to __GI___close_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_discover_osversion': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/../sysdeps/unix/sysv/linux/dl-sysdep.c:107: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/../sysdeps/unix/sysv/linux/dl-sysdep.c:121: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/../sysdeps/unix/sysv/linux/dl-sysdep.c:93: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_next_ld_env_entry': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-environ.c:45: undefined reference to __GI___lxstat64'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-environ.c:40: undefined reference to __GI___lxstat64' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function unsetenv':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-environ.c:75: undefined reference to __GI___openat64_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function malloc':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:50: undefined reference to __GI___fxstat64' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:69: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function free': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:118: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function __strerror_r': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:165: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:168: undefined reference to __GI___close_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function realloc':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:123: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function __GI___assert_perror_fail':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:224: undefined reference to __GI___fcntl64_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:224: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _itoa': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:241: undefined reference to __GI___close_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:245: undefined reference to __GI___open_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:241: undefined reference to __GI___fxstat64'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function __strsep': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:272: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:272: undefined reference to __GI___close_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-minimal.c:265: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function fatal_error': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-error-skeleton.c:78: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-error-skeleton.c:78: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-error-skeleton.c:78: undefined reference to __GI___close_nocancel'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-error-skeleton.c:78: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-error-skeleton.c:78: undefined reference to __lseek'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_signal_exception': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-error-skeleton.c:92: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_signal_cexception': /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-error-skeleton.c:149: undefined reference to __GI___fxstat64'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-error-skeleton.c:136: undefined reference to __GI___fcntl64_nocancel' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_signal_cerror':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-error-skeleton.c:155: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-error-skeleton.c:155: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-error-skeleton.c:157: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os: in function _dl_resolve_conflicts':
/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-conflict.c:33: undefined reference to rtld_errno' /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-conflict.c:69: undefined reference to rtld_errno'
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/librtld.os:/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf/dl-conflict.c:36: more undefined references to rtld_errno' follow /home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/ld.so.new: hidden symbol __libc_check_standard_fds' isn't defined
/home/build/black-parrot/external/lib/gcc/riscv64-unknown-linux-gnu/9.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
Makefile:496: recipe for target '/home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/ld.so' failed
make[7]: *** [/home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64/elf/ld.so] Error 1
make[7]: Leaving directory '/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc/elf'
Makefile:258: recipe for target 'elf/subdir_lib' failed
make[6]: *** [elf/subdir_lib] Error 2
make[6]: Leaving directory '/home/build/black-parrot/external/riscv-gnu-toolchain/riscv-glibc'
Makefile:9: recipe for target 'all' failed
make[5]: *** [all] Error 2
make[5]: Leaving directory '/home/build/black-parrot/external/riscv-gnu-toolchain/build-glibc-linux-rv64imafd-lp64'
Makefile:234: recipe for target 'stamps/build-glibc-linux-rv64imafd-lp64' failed
make[4]: *** [stamps/build-glibc-linux-rv64imafd-lp64] Error 2
make[4]: Leaving directory '/home/build/black-parrot/external/riscv-gnu-toolchain'
/home/build/black-parrot/external/Makefile.tools:46: recipe for target 'gnu_build' failed
make[3]: *** [gnu_build] Error 2
make[3]: Leaving directory '/home/build/black-parrot'
/home/build/black-parrot/external/Makefile.tools:82: recipe for target '/home/build/black-parrot/external/touchfiles/gnu.70063d751135fb22e754ff14bc969ffe9e905fbd' failed
make[2]: *** [/home/build/black-parrot/external/touchfiles/gnu.70063d751135fb22e754ff14bc969ffe9e905fbd] Error 2
make[2]: Leaving directory '/home/build/black-parrot'
Makefile:62: recipe for target 'tools' failed
make[1]: *** [tools] Error 2
make[1]: Leaving directory '/home/build/black-parrot'
Makefile:24: recipe for target 'prep' failed
make: *** [prep] Error 2
build@a5569f5593e2:~/black-parrot$

I did virtualenv apt install and reran make prep -j 8.
This seemed to now finish without error (last 2 lines):
make[2]: Leaving directory '/home/glenn/work/black-parrot/bp_me/src/asm'
make[1]: Leaving directory '/home/glenn/work/black-parrot'
So I tried doing:
make build_cov.sc sim.sc SUITE=riscv_tests PROG=rsort
Which returned
make: *** No rule to make target 'build_cov.sc'.  Stop.
This might be operator error at this point?  Would not surprise me!  Is there some kind of script to run to set the env up before that works?  I did not see that in readme, but well could have missed it.

Hi, thanks for the reports.  Regarding virtualenv, it's been added in the prereqs for Ubuntu in dev. Just hasn't percolated to master yet.  It's needed for bsg_sv2v, but nothing else if you need to comment out that build from the Makefile.
https://github.com/black-parrot/black-parrot/blob/dev/docs/getting_started.md#ubuntu

This might be operator error at this point? Would not surprise me! Is there some kind of script to run to set the env up before that works? I did not see that in readme, but well could have missed it.

Are you running from bp_top/syn ?

As I said operator error....
It built a bunch of g++ files and then
The correction for the main readme seems to be prerequisite:
apt-get install -y apt-utils tzdata git vim gettext-base
bash autoconf automake autotools-dev curl libmpc-dev libmpfr-dev libgmp-dev gawk
build-essential bison flex texinfo gperf libtool patchutils bc zlib1g-dev libexpat-dev
wget byacc device-tree-compiler python gtkwave python-yaml pkg-config swig python3-dev
python-yaml virtualenv

Thanks, glad it's working!

Thank you guys for all the very quick help.  I hope that my minors setup issues help others avoid these same issues.

Hi Dan,
Can you provide any additional guidance on getting a quad core machine to work through the FPGA flow?  I’ve not been able to find why it does not work for me.  So you know here are the specific repo’s I am currently using:
glenn@xxxx:~/work/black-parrot((HEAD detached at 82e69828))$
glenn@xxxx:~/work/black-parrot/bsg_fpga/vu37p((HEAD detached at 9a1985c))$
Thoughts?
Cheers,
Glenn
--
Glenn Baxter | CacheQ Systems | glenn<EMAIL_ADDRESS>|<PHONE_NUMBER>
On Feb 11, 2021, at 9:49 PM, Dan Petrisko <notifications<EMAIL_ADDRESS>wrote:
Thanks, glad it's working!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/black-parrot/black-parrot/issues/757#issuecomment-777968617, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKTKOUFDFFEECHCW2MFP7TDS6SXORANCNFSM4XPJVFRQ.

Hi Glenn,
https://github.com/black-parrot-examples/bsg_fpga/blob/master/vu37p/v/design_1_wrapper.v#L27
I modified this line to e_bp_multicore_4_cfg and it synthesized a quad core BP for me. Can you double check that this isn't working for you? Maybe clean the directory to make sure there are no cached build files


how do you generate audio?

im so confused, the instructions are ASS, i somehow figured out how to load a model, but how do i type some text, with the model i have, to then generate audio? or is this something the tool can't do?
i hope im not the only one who finds this whole audio stuff a nightmare, i didnt struggle this much when i had to find a gui for stable diffusion, but trying to find a text to audio ai tool makes me want to die inside
i want something like elven labs or whatever it was called

This is not a audio synthesis tool, it is an audio conversion tool. It takes audio in and converts it to the model you provided. So no, the instructions are not ASS, you just don't understand the difference between synthesis and conversion.

This and the original RVC repo is not a TTS conversion tool. It is an audio->audio conversion software. Not text->audio.


ERRORS

Has anyone successfully configured the environment? I have installed all current versions of openpcdet and trained normally. But after the environment of PDV code is installed, the training reports errors, and I have tried many times and failed. The code is based on openpcdet, why is it so difficult to install.

Has anyone successfully configured the environment? I have installed all current versions of openpcdet and trained normally. But after the environment of PDV code is installed, the training reports errors, and I have tried many times and failed. The code is based on openpcdet, why is it so difficult to install.


Rebuilding Async Projection Does Not Wait for Batch to Complete Before Moving to Next Batch

Marten Version: 4.1.0
Target Framework: net5.0
I have a projection I am rebuilding using the async daemon and when I am rebuilding it, it produces incorrect results. I've been debugging and it appears when I am using a custom grouper it doesn't wait for a previous batch's result to be saved prior to grouping the next batch. This results in getting incorrect documents from my query, so events are not applied to the documents correctly. Using breakpoints, I'm seeing the Group being called before the Apply on the previous groupings. I've attached a reproducible example project that is similar to what I'm doing in my real app.
When I run this app the first time, it generally succeeds (not all the time), but if I run it more than once, it always fails on subsequent runs.
Note that the example is extremely arbitrary, and I realize that in this example app it could be modeled differently, but I promise in my real app I have to load the documents the way I do here.
Minimal Reproducible Example

Step 1 is just making sure the relevant ActionBlock is set to single file, ensured ordering. Not sure about this though, because nothing should be working well without that.

Okay, nevermind, duh. The design of the action blocks in the aggregation was built with the assumption that the "grouping" could be done in parallel to the application of the projection itself, so the grouping is in a separate action block from the application and update of a single event batch. Works wonderfully for aggregation by stream, and not so much for custom grouping where you use the data store in order to do the grouping.
It's going to take some significant design changes to the async daemon internals to accommodate what you're trying to do here w/o losing the throughput optimizations we did for "not crazy" aggregations.

@jeremydmiller Thanks for the response, I can understand the throughput optimization. I do want to note I think this is a use case that would arise somewhat frequently for anybody using projections to create denormalized, performant read side models, not just in my weird case here. For example, if you had a denormalized Issue model that contained the name of the assignee, if the assignees name changed, you would need to look up all the issues assigned to that employee to know which ones to apply the name change ever to. That would be impossible to do accurately if you cannot depend on the projections being up to date prior to the grouping.
In the mean time, is there any documentation you could point me to for writing a custom IProjection? I'm not really sure what that entails but would love to read anything that points to a better long term solution than the current workaround I have.
Thanks again for your response and work on this

Specifically, it's using the aggregate build product itself within the grouping. That's just not gonna work as it is. The IProjection interface is pretty simple at least. Here's a batch of events organized by stream, go do whatever you want. In your case, you want to use a full identity map session I think so you can avoid doing unnecessary lookups.
I don't think there's anything to change on the Marten side other than documentation and maybe building a documented example.


Estimate of false positive rate of Corona-Warn-App?

There have been recent press reports about local health authorities in Germany complaining about their work not being supported by the App (which technically is true) and expecting an increased workload through the adoption of the App by the public (cf. eg. https://rp-online.de/panorama/coronavirus/gesundheitsaemter-kritisieren-fehlende-einbindung-bei-corona-app_aid-51583559 or other similar press reports).
In this context it would be interesting to know whether there any estimates about the expected false positive rate of the Corona-Warn-App, in particular with regards to establishing the parameters for the risk score calculation?
Have there been any considerations/estimates how many encounters the average user of the App might have a day which, if the respective contact later reported COVID-19 positive, would constitute a "risky encounter"?
If that figure times the average number of days it takes before a contagious person has been tested positive is large compared to the reproduction number R (i.e. the number of further persons one contagious person infects over the course of the illness) we could directly use it as an estimate for the number of false positives inflicted by the app per uploaded positive test result (this is an upper bound since it assumes that each risky encounter of a given person is with a different individual; more refined calculations and modeling are surely possible).
It would be helpful to get to know about such estimates and considerations as a basis for a fact-based public discussion.

This issue should also be considered in relation to the attack described in #228.

We are all aware of challenges regarding the limitations of the used technology, i.e. mobile devices with built-in Bluetooth to trace encounters. Some limitations were already outlined in our solution architecture document.
The development of the application is accompanied by extensive scientific research how the individual parameters need to be tweaked in order to lower the amount of false warnings. Also after the release of the application, the respective parameters will be updated continuously - as outlined in the scoping document. You will probably see some additional documentation from our side about this research and how the parameters are determined in detail, but that may still take some time...
Robust numbers can be expected once the application is out and running for quite a while - and of course we will use these numbers for further improvements. Until then, we unfortunately can't provide such details.
Mit freundlichen Grüßen/Best regards,
SW
Corona Warn-App Open Source Team


Process title displays custodian plus subcommand name

Added setproctitle to requirements, but it isn't required in Lambda environments
Process will now rename itself before it executes the subcommand

Refs #506

merge conflict on requirements.txt

does setproctitle install on windows? just wondering if it should be in setup.py vs an optional

definitely don't want to have this in setup.py, it does look like it has some support in windows, but the lack of wheels means folks will need compilers. looks like we need a custom drone image as well for the extension.

so i think just dropping it from requirements.txt, and opportunistically doing the behavior if present is the right thing given the lack of wheels for the pkg. its primarily an operational thing for systems monitoring to give better disambiguation.


Add fugitive support

Can you consider adding fugitive support?

No, I think.  But you (or anyone else) could fork this repo and make it works with fugitive.
The reason I create vim-easygit is that I find fugitive's API is hard to use, and it's bad performance for vim startup time.

I tried but find out fugitive not providing some api I need (like show the diff content in a split buffer).
vim-easygit could works with fugitive, just not enable the commands.

Mmm but can you consider adding minimal support? Even though the api does't provide everything you need.


Subtitle / caption support

As I understand it there is some work planned to look at subtitles, TTML and subtitle playlists. Dash itself has the concept of an adaption set for subtitles.
I was looking to add subtitles and potentially captions as well. While the implementation for each is essentially the same there is a semantic difference that I would like to capture.
I currently pass something like html5 tracks structure to our player and then inturn pass that to the shakaplayer.
tracks: [
          {
            kind: 'subtitles',
            src: '/subtitles-en.vtt',
            srclang: 'en'
          },
          {
            kind: 'captions',
            src: '/captions-en.vtt',
            srclang: 'en'
          }
        ]

The shakaplayer accepts a call like this
addExternalCaptions('/subtitles-en.vtt', 'en', 'text/vtt');
addExternalCaptions('/captions-en.vtt', 'en', 'text/vtt');

But once these are added there is no easy way to distinguish between them. As calling getTextTracks() will return
0: {
active: true,
enabled: false,
id: 2,
lang: "en"
},
1: {
active: false,
enabled: false,
id: 3,
lang: "en"
}

There is no information that indicates that one is a subtitle and the other is a caption. Even if I call addExternalCaptions with a mime type extension like 'text/vtt+caption' that information is not available.
Ultimately I would like to create a UI to allow the user to select a subtitle or a caption in their language.
I could manage the association between my tracks structure and the getTextTracks but there a couple of assumptions I need to make. Either I assume that the call to getTextTracks will return the results in the same order that I called addExternalCaptions which is probably a safe thing to do, or I take the index of my tracks list and add +2 before calling selectTextTrack(index + 2); which seems a little mysterious (I'm experienced in off by one errors but off by two are less common:)).
Perhaps the cleanest way would be to return the TextTrack object from the call to addExternalCaptions so I know which text track this refers to. Currently addExternalCaptions returns undefined.
An alternative would be to enrich the current text track model with a friendly name and perhaps even the kind into the call addExternalCaptions('/subtitles-en.vtt', 'en', 'text/vtt', 'English'); which can be queried via getTextTracks(). This better aligns with the HTML5 specification.
I hope that made sense

Thanks, Mark.  In the short term (v1.6.0), we could return the track object from addExternalCaptions.  Would this work for now?
Long term, I'd like to make sure that a future redesign of Shaka Player provides some more elegant way to represent the semantics you're looking for.  Can you help me understand the difference between captions and subtitles?

Sure that will work.
Captions are targeted at the hearing impaired. For example if you are hearing impaired, and an English speaker the captions will contain English dialogue but also environmental noises that might influence the actors. [bang!] to indicate a loud noise, [creaking floorboards] to add suspense, etc...
Subtitles are dialog translated to a different language, potentially you could have captions in different languages.
The rendering of each is identical, captions may use the location features of WebVTT to indicate a noise came from the left or right of the screen.
Not everyone will be interested in the distinction. But if you have ever watched a movie with closed captions when you wanted subtitles it can be very distracting. An example I watched recently was Deadlands in which the dialog is in Maori, which I don't speak but it included captions which wasn't ideal.

Thanks for the explanation.  We'll try to support that distinction better in v2.0.
I've taken another look at the code, and it actually will be difficult to return TextTrack the way it is currently implemented.  Let me see if there is something else we can do short-term.

@sarge, Shaka v2 should now distinguish between caption and subtitle tracks.  Thanks for the report!

Thanks Joey!
On 22 Mar 2016 06:03, "Joey Parrish"<EMAIL_ADDRESS>wrote:

@sarge https://github.com/sarge, Shaka v2 should now distinguish
between caption and subtitle tracks. Thanks for the report!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/google/shaka-player/issues/206#issuecomment-199381787


Added delete multiple contacts functionality into DeleteCommand

Delete command now dynamically identifies whether the user gave a single or multiple index.
Correct input command for deleting multiple contacts would be only 1 whitespace between non-zero positive integers, leading and trailing whitespaces are OK.
DeleteCommandParserTest all ok.
DeleteCommandTest currently still WIP.

Codecov Report

Merging #34 (e0a0669) into master (31e52ea) will increase coverage by 0.18%.
The diff coverage is 77.77%.

@@             Coverage Diff              @@
##             master      #34      +/-   ##
============================================
+ Coverage     70.81%   71.00%   +0.18%
- Complexity      385      406      +21
============================================
  Files            70       70
  Lines          1196     1245      +49
  Branches        117      131      +14
============================================
+ Hits            847      884      +37
- Misses          318      325       +7
- Partials         31       36       +5

Impacted Files
Coverage Δ

...n/java/seedu/address/commons/core/index/Index.java
83.33% <0.00%> (-16.67%)
:arrow_down:

...va/seedu/address/logic/commands/DeleteCommand.java
72.97% <65.51%> (-27.03%)
:arrow_down:

...in/java/seedu/address/commons/util/StringUtil.java
96.42% <100.00%> (+1.69%)
:arrow_up:

...eedu/address/logic/parser/DeleteCommandParser.java
100.00% <100.00%> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
97.95% <100.00%> (+0.73%)
:arrow_up:

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 31e52ea...e0a0669. Read the comment docs.


cue/errors: error list does not work with %w verb

cuelang.org/go v0.4.1-beta.6.0.20211206112628-28b42576ce83

The errors.list type does not work well with the %w verb used by printf:
https://go.dev/play/p/jfz6YylA_af
I'd expect the two fmt.Printf lines to print the same thing. Instead I see this:
config validation failed: foo: conflicting values "goodbye" and "hello" (and 1 more errors)
config validation failed: %!w(errors.list=[0xc0002a61c0 0xc0002a6230])

I'm talking rubbish here. %w should not work with Printf, only Errorf.


Port McCLIM Gopher Browser to Mezzano

I am interested in leveling my LISP up a little, I was wondering: could someone describe to me the process through which I should port this McCLIM gopher browser to Mezzano?
https://github.com/knusbaum/clim-gopher
A rough outline is sufficient: as I understand it, this software only runs on UNIX, and bases on X. But I can't help but remember that McCLIM had been ported to Mezzano: would it be possible to get this gopher browser on Mezzano by running it on our McCLIM?
Getting some sort of hypertext support is crucial for me to consider using Mezzano as a daily driver. Much like a lot of folks use plan9 for aesthetic reasons, I would seriously consider ditching Linux for Mezzano if I could somehow get gopher going.
Thanks in advance (:

We tend to use  #mezzano on irc.freenode.net to talk about Mezzano.
Froggey has a version of McClim that works with Mezzano, so you need to load that. It should be in the MBuild/home directory.  And, I would install gopher in that directory (MBuild/home) as well. Then load it and see what happens?
The development environment I use for working on Mezzano is running Mezzano in VirtualBox, connect using slime from emacs on the host machine (where I'm running Linux)
Does that help any? Feel free to ask more questions either in email or on #mezzano.
fittestbits

We tend to use  #mezzano on irc.freenode.net to talk about Mezzano.
Froggey has a version of McClim that works with Mezzano, so you need to load that. It should be in the MBuild/home directory.  And, I would install gopher in that directory (MBuild/home) as well. Then load it and see what happens?
The development environment I use for working on Mezzano is running Mezzano in VirtualBox, connect using slime from emacs on the host machine (where I'm running Linux)
Does that help any? Feel free to ask more questions either in email or on #mezzano.
fittestbits

that's a huge help (:
thanks so much (:

that's a huge help (:
thanks so much (:

Just wanted to add here that it'd be great to get the closure web browser in Mezzano for at least some basic html website surfing. Should I follow the same steps above to get that going?


Function that Sets, Updates and Removes

I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[x] Support request
[ ] Other... Please describe:

Current behavior
I have a simple entity store in which I store team members. When a user enters the app I fetch it's data (via the team-members store, as the user also is a team member). When the user goes to /team I want to fetch all the team members, but for performance reason I only fetch fewer properties, compared to fetching the individual user. I need all the user's data at any time, in order to display links in the navbar properly.
Expected behavior
So the desired behaviour would be to add any team members, that weren't fetched before, to update the ones that were already fetched and to remove the ones that aren't part of the newly fetched team members. I know the function upsert handles the first two points, but is there any other built-in function that can perform my desired task?
What is the motivation / use case for changing the behavior?
If there is no built-in function, a function like 'upset' (Removing any entities, that are not part of the new entities, and updating the old ones), implementing such a function would provide one further functionality for the community.

Hi @Tobjoern 🙂
Sounds to me like you can get the functionality you describe as 'upset' by using the remove method and giving it a function as a parameter, which returns true if the entity in the store isn't one of the newly fetched team members, e.g. store.remove((entity) => !newTeamMembers.some((newMember) => newMember.id === entity.id));

@Tobjoern as @theblushingcrow suggested you can do it by using upsert and remove with predicate function:
@transaction
updateStore() {
  store.upsert(...);
  store.remove((entity) => ...);
}

Sounds good?

Thanks for the quick help! This is exactly what I was looking for :)


Add v1.16.5-1.1 images

Do not remove runtime packages
Closes: #1492
related: https://github.com/fluent/fluentd-docker-image/pull/383

Revised again.

Created v1.16.5-1.1 tag.


C++ to WebAssembly in a browser

I would like to make small chunks of my JS code faster (short functions, which perform heavy computation). I was thinking about writing them in WebAssembly manually, but writing them in C would be much more comfortable.
Would you like to extend your tool, so it can compile the C code into WebAssembly? I don't want to make a mess in my computer by installing heavy native compilers, just to translate several lines of C code into WebAssembly.

Maybe you can rewrite your JS code in asm.js?

Would you like to extend your tool, so it can compile the C code into WebAssembly?

The project was built to be an interpreter. If you are looking for a compiler, it's better to start from the emscripten+LLVM approach. The main advantage of a JS-written package is that it can be run on client side, thus reducing server traffic/CPU time. And I don't see much gain from a JS-written compiler.

I am a web developer and I am not used to many native apps. The only two native apps I use is a web browser and a text editor. I think that the compiler inside a browser would be much more friendly to web developers, than some special apps controlled from a command line.
BTW. I think I found an online C++ to WASM compiler.

Cool. Do you mind sharing the online compiler? I'm interested.

Oh, sorry, I forgot to paste the URL :D  here it is https://wasdk.github.io/WasmFiddle/

I read its code and it is just a web client calling an endpoint server for compilation.