redox-os issueshttps://gitlab.redox-os.org/groups/redox-os/-/issues2020-10-20T18:05:59Zhttps://gitlab.redox-os.org/redox-os/rusttype/-/issues/157Querying horizontal glyph metrics in pt2020-10-20T18:05:59ZRobin KrahlQuerying horizontal glyph metrics in ptfreetype allows me to access the glyph metrics in pt by querying the metrics for the unscaled glyph and then scaling it using the `units_per_em` value. As far as I see, I can only access the glyph metrics scaled to a pixel size in rustt...freetype allows me to access the glyph metrics in pt by querying the metrics for the unscaled glyph and then scaling it using the `units_per_em` value. As far as I see, I can only access the glyph metrics scaled to a pixel size in rusttype 0.9. Is this intentional? Or am I missing something?https://gitlab.redox-os.org/redox-os/redox/-/issues/1319panicked at 'unexpected -vV format' with compiling2023-06-13T02:55:49ZYi Chengpanicked at 'unexpected -vV format' with compiling# Description
On WSL ubuntu 18.04, compile fail and output info:
```
thread 'main' panicked at 'unexpected -vV format', ~/.cargo/registry/src/github.com-1ecc6299db9ec823/rustc_version-0.1.7/src/lib.rs:126:5
```
# Environment info
* Oper...# Description
On WSL ubuntu 18.04, compile fail and output info:
```
thread 'main' panicked at 'unexpected -vV format', ~/.cargo/registry/src/github.com-1ecc6299db9ec823/rustc_version-0.1.7/src/lib.rs:126:5
```
# Environment info
* Operating system: WSL Ubuntu 18.04
* uname -a: Linux DESKTOP-GSOK8JJ 4.4.0-17763-Microsoft #864-Microsoft Thu Nov 07 15:22:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux
* `rustc -V`: rustc 1.47.0-nightly (6c8927b0c 2020-07-26)
* git rev-parse HEAD: d7e52b5238e69df764adbf9f2a0b3bd3b056d322
# Steps to reproduce
1. `cd path/to/your/projects/folder/`
2. `curl -sf https://gitlab.redox-os.org/redox-os/redox/raw/master/bootstrap.sh -o bootstrap.sh && bash -e bootstrap.sh`
3. `cd redox`
4. `make all`
## Behavior
* **Expected behavior**: Successful build.
* **Actual behavior**: Build fail and output panicked.
## Self Analysis
compile panicked with info `unexpected -vV format`, related to source code `.cargo/registry/src/github.com-1ecc6299db9ec823/rustc_version-0.1.7/src/lib.rs:126`.
```
// lib.rs
/// Parses a "rustc -vV" output string and returns
/// the SemVer version and additional metadata
/// like the git short hash and build date.
pub fn version_meta_for(verbose_version_string: &str) -> VersionMeta {
let out: Vec<_> = verbose_version_string.lines().collect();
const ERR_MSG: &'static str = "unexpected -vV format";
assert!(out.len() == 6 || out.len() == 7, ERR_MSG);
...
```
This function is used to parse `rustc -vV`,and I execute this command manually.
```
% rustc -vV
rustc 1.47.0-nightly (6c8927b0c 2020-07-26)
binary: rustc
commit-hash: 6c8927b0cf80ceee19386026cf9d7fd4fd9d486f
commit-date: 2020-07-26
host: x86_64-unknown-linux-gnu
release: 1.47.0-nightly
LLVM version: 10.0
```
According to the `rustc -vV` message, I write a testcase.
```
24 #[test]
23 fn parse_nightly_cy() {
22 let version = version_meta_for(
21 "rustc 1.47.0-nightly (6c8927b0c 2020-07-26)
20 binary: rustc
19 commit-hash: 6c8927b0cf80ceee19386026cf9d7fd4fd9d486f
18 commit-date: 2020-07-26
17 host: x86_64-unknown-linux-gnu
16 release: 1.47.0-nightly
15 LLVM version: 10.0",
14 );
13
12 assert_eq!(version.semver, Version::parse("1.47.0-nightly").unwrap());
11 assert_eq!(
10 version.commit_hash,
9 Some("6c8927b0cf80ceee19386026cf9d7fd4fd9d486f".into())
8 );
7 assert_eq!(version.commit_date, Some("2020-07-26".into()));
6 assert_eq!(version.channel, Channel::Nightly);
5 assert_eq!(version.host, "x86_64-unknown-linux-gnu");
4 assert_eq!(
3 version.short_version_string,
2 "rustc 1.47.0-nightly (6c8927b0c 2020-07-26)"
1 );
313 }
```
and everything is fine,when I ran `cargo test`.this means `version_meta_for` is correct.so why compile fail?https://gitlab.redox-os.org/redox-os/book/-/issues/140Update the Getting Started chapter2023-06-13T04:52:39ZToby WebbUpdate the Getting Started chapterI followed the `compiling Redox` chapter and came across issues about missing commands.
As well as updating the instructions, I can see great benefit in adding a "Troubleshooting" section, in case something gets broken later.
(I might ...I followed the `compiling Redox` chapter and came across issues about missing commands.
As well as updating the instructions, I can see great benefit in adding a "Troubleshooting" section, in case something gets broken later.
(I might get round to compiling a MR for this issue if I have time.)https://gitlab.redox-os.org/redox-os/redox/-/issues/1318po4a required for clean build on Ubuntu 20.042023-06-13T02:54:48Zjeannekamikazepo4a required for clean build on Ubuntu 20.04<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report....<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report. You can also preview this report before submitting it. Feel free to modify/remove sections to fit the nature of your issue. -->
<!-- Please search to check that your issue has not been created already. By preventing duplicate issues, you can help keep the repository organized. If your current issue has already been created and is still unresolved, you can contribute by commenting there. -->
<!-- Replace the empty checkbox [ ] below with a checked one [x] if you have already searched for your issue. -->
- [X] I agree that I have searched opened and closed issues to prevent duplicates.
--------------------
## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
On Ubuntu 20.04, `po4a` seems to be required for a successful clean install.
## Environment info
<!-- To understand where your issue originates, please include some relevant information about your environment. -->
<!-- If you have built Redox OS yourself, please provide the following information: -->
- Operating system:
Ubuntu 20.04
- `uname -a`:
`Linux sha490 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux`
- `rustc -V`:
`rustc 1.48.0-nightly (f68e08933 2020-09-19)`
- `git rev-parse HEAD`:
`d7e52b5238e69df764adbf9f2a0b3bd3b056d322`
<!-- Depending on your issue, additional information about your environment (network config, package versions, dependencies, etc.) can also help. You can list that below. -->
## Steps to reproduce
<!-- If possible, please list the steps to reproduce ("trigger") your issue below. Being detailed definitely helps speed up bug fixes. -->
1. `cd path/to/your/projects/folder/`
2. `curl -sf https://gitlab.redox-os.org/redox-os/redox/raw/master/bootstrap.sh -o bootstrap.sh && bash -e bootstrap.sh`
3. `cd redox`
4. `make all`
## Behavior
<!-- It may seem obvious to know what to expect, but isolating the behavior from everything else simplifies the development process. Remember to provide a single issue in this report. You can use the References section below to link your issues together. -->
<!-- Describe the behavior you expect your steps should yield (i.e., correct behavior). -->
- **Expected behavior**:
Successful build.
<!-- Describe the behavior you observed when running your steps (i.e., buggy behavior). -->
- **Actual behavior**:
Build fails saying `po4a` was not found.
<!-- **Logs?** Posting a log can help developers find your particular issue more easily. Please wrap your code in code blocks using triple back-ticks ``` to increase readability. -->
<!-- **Solution?** Have a solution in mind? Propose your solution below. -->
- **Proposed solution**:
`sudo apt install po4a`
<!-- **Screenshots?** Make it easier to get your point across with screenshots. You can drag & drop or paste your images below. -->
<!-- **Code?** Awesome! You can also create a pull request with a reference to this issue. -->
<!-- **Files?** Attach your relevant files by dragging & dropping or pasting them below. -->
<!-- You also can preview your report before submitting it. Thanks for contributing to Redox! -->https://gitlab.redox-os.org/redox-os/redox/-/issues/1317Issue with compiling for the first time.2023-06-13T03:00:00ZEvan HooseIssue with compiling for the first time.<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report....<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report. You can also preview this report before submitting it. Feel free to modify/remove sections to fit the nature of your issue. -->
<!-- Please search to check that your issue has not been created already. By preventing duplicate issues, you can help keep the repository organized. If your current issue has already been created and is still unresolved, you can contribute by commenting there. -->
<!-- Replace the empty checkbox [ ] below with a checked one [x] if you have already searched for your issue. -->
- [x] I agree that I have searched opened and closed issues to prevent duplicates.
--------------------
## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
`make all` Failing to compile.
## Environment info
<!-- To understand where your issue originates, please include some relevant information about your environment. -->
<!-- If you have built Redox OS yourself, please provide the following information: -->
- `uname -a`:
Linux laptop 5.4.0-7642-generic #46~1598628707~20.04~040157c-Ubuntu SMP [REDACT] x86_64 x86_64 x86_64 GNU/Linux
NOTE: I am currently running Pop!_OS, not vanilla Ubuntu.
- `rustc -V`:
rustc 1.48.0-nightly (6af1bdda5 2020-09-15)
- `git rev-parse HEAD`:
d7e52b5238e69df764adbf9f2a0b3bd3b056d322
## Steps to reproduce
<!-- If possible, please list the steps to reproduce ("trigger") your issue below. Being detailed definitely helps speed up bug fixes. -->
1. Follow Manual Setup in https://doc.redox-os.org/book/ch02-04-preparing-the-build.html
2. Run make all as stated in https://doc.redox-os.org/book/ch02-05-compiling-redox.html
## Behavior
<!-- It may seem obvious to know what to expect, but isolating the behavior from everything else simplifies the development process. Remember to provide a single issue in this report. You can use the References section below to link your issues together. -->
<!-- Describe the behavior you expect your steps should yield (i.e., correct behavior). -->
- **Expected behavior**:
Compile finishes without error.
<!-- Describe the behavior you observed when running your steps (i.e., buggy behavior). -->
- **Actual behavior**:
Receive error:
```
mk/depends.mk:13: *** cargo-config 0.1.1 not found, run "cargo install --force --version 0.1.1 cargo-config". Stop.
```
<!-- **Logs?** Posting a log can help developers find your particular issue more easily. Please wrap your code in code blocks using triple back-ticks ``` to increase readability. -->
I don't know where to find logs, but would be happy to provide them if someone can point me to the right place
Related to:
- #1310 Possibly same bug? I'm not familiar with the build systems involved, so I can't say for sure.https://gitlab.redox-os.org/redox-os/ion/-/issues/978cd $variable has an unexpected behaviour2020-11-29T21:45:40ZDario Goedtkindtcd $variable has an unexpected behaviourbug: When cd'ing to a variable of the form ```~/path/to/dir```, ion evaluates this as ```cd $HOME/~/path/to/dir```
code:
```
let awesomeconf = '~/.config/awesome'
echo $awesomeconf
cd $awesomeconf
pwd
```
expect:
```
~/.config/awesome
...bug: When cd'ing to a variable of the form ```~/path/to/dir```, ion evaluates this as ```cd $HOME/~/path/to/dir```
code:
```
let awesomeconf = '~/.config/awesome'
echo $awesomeconf
cd $awesomeconf
pwd
```
expect:
```
~/.config/awesome
/home/name/.config/awesome
```
got:
```
~/.config/awesome
failed to set current dir to /home/name/~/.config/awesome: No such file or directory (os error 2)
```
kernel: linux5.4
version: 63d1bf76b6dc27ec9fab80274926738688b6d03ehttps://gitlab.redox-os.org/redox-os/ion/-/issues/977Parameter Expansion?2020-09-11T05:42:09ZunmellowParameter Expansion?I'm trying to do what I believe is called parameter expansion
eg: `old_name=run_fix.bash
new_name=${old_name%.bash}.in_hold.txt`
in bash
i'm trying to automaticly convert files to thier current name but replacing eg .png with .avif
i he...I'm trying to do what I believe is called parameter expansion
eg: `old_name=run_fix.bash
new_name=${old_name%.bash}.in_hold.txt`
in bash
i'm trying to automaticly convert files to thier current name but replacing eg .png with .avif
i heard the best way to do this is to use parameter expansion
i have this shell script "name file2.ion"
```sh
#!/bin/ion
let old_name=@args[1]
#$HOME/go/bin/avif -e @args[1] -o $(echo @args[1] |sed 's/.png&/.avif/')
let new_name=${old_name%.*}.avif
$HOME/go/bin/avif -e @args[1] -o $new_name
```
and would execute
./file2.ion ./picture.png
and get
ion: syntax error: syntax error: '%' at position 25 is out of place
and i don't understand whyhttps://gitlab.redox-os.org/redox-os/redox/-/issues/1316Unsupported OS in bootstrap: Alpine Linux2023-06-13T03:06:41ZMelody HornUnsupported OS in bootstrap: Alpine Linux<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report....<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report. You can also preview this report before submitting it. Feel free to modify/remove sections to fit the nature of your issue. -->
<!-- Please search to check that your issue has not been created already. By preventing duplicate issues, you can help keep the repository organized. If your current issue has already been created and is still unresolved, you can contribute by commenting there. -->
<!-- Replace the empty checkbox [ ] below with a checked one [x] if you have already searched for your issue. -->
- [x] I agree that I have searched opened and closed issues to prevent duplicates.
--------------------
## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
I'm trying to build Redox from Alpine Linux, and the bootstrap script is incorrectly detecting it as FreeBSD.
## Environment info
<!-- To understand where your issue originates, please include some relevant information about your environment. -->
<!-- If you have built Redox OS yourself, please provide the following information: -->
- Operating system:
Alpine Linux
- `uname -a`:
Linux UberPC-V3 4.19.128-microsoft-standard #1 SMP Tue Jun 23 12:58:10 UTC 2020 x86_64 Linux
## Steps to reproduce
<!-- If possible, please list the steps to reproduce ("trigger") your issue below. Being detailed definitely helps speed up bug fixes. -->
1. Run the bootstrap script on Alpine Linux with some dependencies missing.
## Behavior
<!-- It may seem obvious to know what to expect, but isolating the behavior from everything else simplifies the development process. Remember to provide a single issue in this report. You can use the References section below to link your issues together. -->
<!-- Describe the behavior you expect your steps should yield (i.e., correct behavior). -->
- **Expected behavior**:
Dependencies are installed automatically.
<!-- Describe the behavior you observed when running your steps (i.e., buggy behavior). -->
- **Actual behavior**:
<!-- **Logs?** Posting a log can help developers find your particular issue more easily. Please wrap your code in code blocks using triple back-ticks ``` to increase readability. -->
```
|------------------------------------------|
|----- Welcome to the redox bootstrap -----|
|------------------------------------------|
+ echo 'FreeBSD detected!'
FreeBSD detected!
+ echo 'Installing missing packages...'
Installing missing packages...
+ install_freebsd_pkg git
+ install_bsd_pkg 'sudo pkg' git
+ PKG_MANAGER='sudo pkg'
+ PKG_NAME=git
+ BIN_NAME=
+ '[' -z ]
+ BIN_NAME=git
+ which git
+ true
+ BIN_LOCATION=
+ '[' -z ]
+ echo 'sudo pkg install git'
sudo pkg install git
+ sudo pkg install git
> pkg@4.4.4
> Error! Not more than one entry file/directory is expected
```
<!-- **Solution?** Have a solution in mind? Propose your solution below. -->
- **Proposed solution**:
Add support for Alpine Linux in the bootstrap script. Its package manager is `apk` and its package repository can be browsed at https://pkgs.alpinelinux.org/packages; an example of its usage would be `apk add git`.
<!-- **Screenshots?** Make it easier to get your point across with screenshots. You can drag & drop or paste your images below. -->
<!-- **Code?** Awesome! You can also create a pull request with a reference to this issue. -->
<!-- **Files?** Attach your relevant files by dragging & dropping or pasting them below. -->
<!-- You also can preview your report before submitting it. Thanks for contributing to Redox! -->https://gitlab.redox-os.org/redox-os/rusttype/-/issues/156Unexpected panic when rasterizing specific font at specific size2020-09-06T09:13:54ZCobrandUnexpected panic when rasterizing specific font at specific sizeHello there,
as written in the title, when trying to rasterize a very specific text at scale 24.0 with the font Bitter-Regular.otf, I get a panic when rendering the word "Gauntl".
I created a repository that you can clone and `cargo ru...Hello there,
as written in the title, when trying to rasterize a very specific text at scale 24.0 with the font Bitter-Regular.otf, I get a panic when rendering the word "Gauntl".
I created a repository that you can clone and `cargo run` for a minimal example with the problematic font included (I copied the `ascii` example and modified the font size, the font and the word, nothing else).
You can have a look at the repository here: https://github.com/Cobrand/rusttype-bug-example
The panic output with RUST_BACKTRACE=1 :
```
thread 'main' panicked at 'index out of bounds: the len is 100 but the index is 18446744073709551615', /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/ab_glyph_rasterizer-0.1.2/src/raster.rs:85:17
stack backtrace:
...
13: core::panicking::panic_bounds_check
at src/libcore/panicking.rs:62
14: <usize as core::slice::SliceIndex<[T]>>::index_mut
at /home/cobrand/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/libcore/slice/mod.rs:3109
15: core::slice::<impl core::ops::index::IndexMut<I> for [T]>::index_mut
at /home/cobrand/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/libcore/slice/mod.rs:2966
16: <alloc::vec::Vec<T> as core::ops::index::IndexMut<I>>::index_mut
at /home/cobrand/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/liballoc/vec.rs:1987
17: ab_glyph_rasterizer::raster::Rasterizer::draw_line
at /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/ab_glyph_rasterizer-0.1.2/src/raster.rs:85
18: <rusttype::outliner::OutlineRasterizer as ttf_parser::OutlineBuilder>::line_to
at /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/rusttype-0.9.2/src/outliner.rs:122
19: <rusttype::outliner::OutlineTranslator<T> as ttf_parser::OutlineBuilder>::line_to
at /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/rusttype-0.9.2/src/outliner.rs:68
20: <rusttype::outliner::OutlineScaler<T> as ttf_parser::OutlineBuilder>::line_to
at /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/rusttype-0.9.2/src/outliner.rs:22
21: ttf_parser::tables::cff::Builder::line_to
at /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/ttf-parser-0.6.2/src/tables/cff.rs:297
22: ttf_parser::tables::cff::_parse_char_string
at /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/ttf-parser-0.6.2/src/tables/cff.rs:392
23: ttf_parser::tables::cff::parse_char_string
at /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/ttf-parser-0.6.2/src/tables/cff.rs:265
24: ttf_parser::tables::cff::outline
at /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/ttf-parser-0.6.2/src/tables/cff.rs:168
25: ttf_parser::Font::outline_glyph
at /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/ttf-parser-0.6.2/src/lib.rs:1256
26: rusttype::ScaledGlyph::build_outline
at /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/rusttype-0.9.2/src/lib.rs:253
27: rusttype::PositionedGlyph::build_outline
at /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/rusttype-0.9.2/src/lib.rs:416
28: rusttype::PositionedGlyph::draw
at /home/cobrand/.cargo/registry/src/github.com-1ecc6299db9ec823/rusttype-0.9.2/src/lib.rs:451
29: rusttype_bug::main
at src/main.rs:58
```
Note that the bug seems to trigger very specificly with that word and no other for some reason. "Gauntlxxxx" will panic as well, but "Gaunt" for instance, will not. Likewise, "Gaunlt" will not panic.https://gitlab.redox-os.org/redox-os/ion/-/issues/976Panic on unterminated array expression2020-08-31T15:40:55ZMichel Le BihanPanic on unterminated array expressionHello,
On latest master (63d1bf76b6dc27ec9fab80274926738688b6d03e) I accidentally didn't close an array expression that cause a panic. Here is a minimal example that will cause a panic:
```
michel:~/git/ion# target/debug/ion
michel:~/gi...Hello,
On latest master (63d1bf76b6dc27ec9fab80274926738688b6d03e) I accidentally didn't close an array expression that cause a panic. Here is a minimal example that will cause a panic:
```
michel:~/git/ion# target/debug/ion
michel:~/git/ion# let a = [
thread 'main' panicked at 'ion: fatal error with syntax validation: unterminated array expression', src/lib/expansion/words/mod.rs:241:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```https://gitlab.redox-os.org/redox-os/redox/-/issues/1315Red Hat Enterprise Linux 7.8 VM2023-06-13T03:09:13ZAdrian LewisRed Hat Enterprise Linux 7.8 VMOS
```
Virtualization: vmware
Operating System: Red Hat Enterprise Linux
CPE OS Name: cpe:/o:redhat:enterprise_linux:7.8:GA:server
Kernel: Linux 3.10.0-1127.el7.x86_64
Architecture: x86-64
```
I run the bootstrap, which (nearly) immediat...OS
```
Virtualization: vmware
Operating System: Red Hat Enterprise Linux
CPE OS Name: cpe:/o:redhat:enterprise_linux:7.8:GA:server
Kernel: Linux 3.10.0-1127.el7.x86_64
Architecture: x86-64
```
I run the bootstrap, which (nearly) immediately tells me it is an usupported platform and then continues to clone.
```
$ curl -sf https://gitlab.redox-os.org/redox-os/redox/raw/master/bootstrap.sh -o bootstrap.sh && bash -e bootstrap.sh
|------------------------------------------|
|----- Welcome to the redox bootstrap -----|
|------------------------------------------|
Fatal error: Unsupported platform, please open an issue\[0mCloning gitlab repo...
Cloning into 'redox'...
```https://gitlab.redox-os.org/redox-os/termion/-/issues/183Handle alt+<arrow key> on libvte derived terminals2022-10-21T07:07:27ZPaul FarielloHandle alt+<arrow key> on libvte derived terminalsalt+up can generate either `\033\033[A` on rxvt and derivative terminals or `\033[1;3A` on vte based terminal such as gnome-terminal and termite. The later isn't handle by termion as far as I could test.
Numbered escape code seems to be...alt+up can generate either `\033\033[A` on rxvt and derivative terminals or `\033[1;3A` on vte based terminal such as gnome-terminal and termite. The later isn't handle by termion as far as I could test.
Numbered escape code seems to be handled in [event.rs](src/event.rs#L240) but only `M` and `~` not `A` `B` `C` or `D`.https://gitlab.redox-os.org/redox-os/seahash/-/issues/9unaligned u64 reads2020-12-03T10:27:33ZJoonas Koivunenunaligned u64 readsNot sure if this could be related to the ARM performance #7 but I was just thinking of the unsafe code, for example [in `buffer.rs`](https://gitlab.redox-os.org/redox-os/seahash/-/blob/master/src/buffer.rs#L50-53) or [in `stream.rs`](htt...Not sure if this could be related to the ARM performance #7 but I was just thinking of the unsafe code, for example [in `buffer.rs`](https://gitlab.redox-os.org/redox-os/seahash/-/blob/master/src/buffer.rs#L50-53) or [in `stream.rs`](https://gitlab.redox-os.org/redox-os/seahash/-/blob/master/src/stream.rs#L73-81). I think there's no guarantee that a pointer to `&[u8]` is good for reading u64.
Might be that we'd need to do a loop of smaller to align to `align_of::<u64>()` and read the non-aligned suffix in similar slower way.
Apologies if this has already been discussed to death or if I am misreading and missing some alignment enforcing part.https://gitlab.redox-os.org/redox-os/redox/-/issues/1314Package 'bison' not installed, linux build2023-06-13T03:11:09ZMatt MillerPackage 'bison' not installed, linux buildFollowing the installation instructions compilation bombed because bison was missing. Indeed after re-checking this URL 'https://doc.redox-os.org/book/ch02-04-preparing-the-build.html' for the 'Linux Users:' portion it is indeed missing ...Following the installation instructions compilation bombed because bison was missing. Indeed after re-checking this URL 'https://doc.redox-os.org/book/ch02-04-preparing-the-build.html' for the 'Linux Users:' portion it is indeed missing 'bison' in the install line.https://gitlab.redox-os.org/redox-os/redox/-/issues/1313Compilation of "xz" recipe in cookbook fails for linux build2023-06-13T03:07:48ZMatt MillerCompilation of "xz" recipe in cookbook fails for linux buildDuring the compilation process on an x86_64 machine it fails to find the 'configure' script during the building of 'redox/cookbook/recipes/xz'. I changed into the folder to look around and noticed an 'autogen.sh' file after running this ...During the compilation process on an x86_64 machine it fails to find the 'configure' script during the building of 'redox/cookbook/recipes/xz'. I changed into the folder to look around and noticed an 'autogen.sh' file after running this the 'configure' file was available and all was well.https://gitlab.redox-os.org/redox-os/kernel/-/issues/101Use sysretq in the syscall handler2021-02-15T19:11:09ZJacob Lorentzon4ldo2@protonmail.comUse sysretq in the syscall handlerCurrently, `IRETQ` is invoked when returning from the syscall handler, rather than `SYSRETQ`. This may probably be somewhat slower.
To properly use `SYSRETQ`, we would need to set bits 63:48 of the `IA32_STAR` MSR, to the user segments ...Currently, `IRETQ` is invoked when returning from the syscall handler, rather than `SYSRETQ`. This may probably be somewhat slower.
To properly use `SYSRETQ`, we would need to set bits 63:48 of the `IA32_STAR` MSR, to the user segments in the GDT, and change some assembly (may be harder that it seems).https://gitlab.redox-os.org/redox-os/ion/-/issues/975Manual: super and global namespaces example doesn't demonstrate the feature2021-06-02T19:24:13ZbakaManual: super and global namespaces example doesn't demonstrate the featureThe [Scopes (super and global namespaces)](https://doc.redox-os.org/ion-manual/html/variables/07-namespaces.html#scopes-super-and-global-namespaces) example is as follows:
```
let a = 1
fn demo
let b = 2
fn nested
echo ${super...The [Scopes (super and global namespaces)](https://doc.redox-os.org/ion-manual/html/variables/07-namespaces.html#scopes-super-and-global-namespaces) example is as follows:
```
let a = 1
fn demo
let b = 2
fn nested
echo ${super::b}
echo ${global::a}
end
nested
end
demo
```
This code is functionally equivalent to:
```
let a = 1
fn demo
let b = 2
fn nested
echo $b
echo $a
end
nested
end
demo
```
This doesn't demonstrate the super and global namespace feature since $a and $b can be accessed just fine without using them.
In fact, I could not find any situation where this feature would apply. The [Scopes chapter](https://doc.redox-os.org/ion-manual/html/variables/06-scopes.html) says `Functions have the scope they were defined in.` which from my understanding implies a function always has access to the "super" scope (and if applied recursively, the global scope).
One guess was that this feature was meant to a situation like this where the variable is defined in the scope the function was called from:
```
fn print_vars
echo ${super::y}
end
if test 1 == 1
let y = 3
print_vars
end
```
However that doesn't work (and I guess is unnecessary since you can pass variables to functions as a parameter).Ion Shell v1.0.0betahttps://gitlab.redox-os.org/redox-os/ion/-/issues/974Manual: confusing example in Process Expansions chapter2020-12-11T20:56:00ZbakaManual: confusing example in Process Expansions chapterIn the [Process Expansions chapter](https://doc.redox-os.org/ion-manual/html/expansions/02-process.html) the following code is given:
```
let array = @(cmd args...)
```
I expected this to produce an array that I could access using `@ar...In the [Process Expansions chapter](https://doc.redox-os.org/ion-manual/html/expansions/02-process.html) the following code is given:
```
let array = @(cmd args...)
```
I expected this to produce an array that I could access using `@array`. It instead produces a string `$array`. I eventually figured out that I need to use `let array = [ @(cmd args...) ]` to perform a [deep copy](https://doc.redox-os.org/ion-manual/html/variables/02-arrays.html#copy-array-into-a-new-array).
The example should be changed to `let array = [ @(cmd args...) ]` and include a link to https://doc.redox-os.org/ion-manual/html/variables/02-arrays.html#copy-array-into-a-new-array as a reminder of the reason for the square brackets.https://gitlab.redox-os.org/redox-os/redox/-/issues/1312Tracking issue for io_uring2023-07-02T14:55:25ZJacob Lorentzon4ldo2@protonmail.comTracking issue for io_uringThis is the tracking issue for the [io_uring](https://gitlab.redox-os.org/redox-os/rfcs/-/merge_requests/15) feature.This is the tracking issue for the [io_uring](https://gitlab.redox-os.org/redox-os/rfcs/-/merge_requests/15) feature.https://gitlab.redox-os.org/redox-os/redox/-/issues/1311https://www.redox-os.org/ SSL certificate has expired2022-11-30T12:35:37Zsamuelahttps://www.redox-os.org/ SSL certificate has expiredLooks like the SSL cert has expired. Firefox makes a big fuss about it.Looks like the SSL cert has expired. Firefox makes a big fuss about it.