text:
Instructions in Readme.md assume rustup without mentioning it

I was just following through the instructions in the Readme.md and noticed that the setup scripts require rustup to be present without ever mentioning how to install rustup. rustup is an upstream tool that is usually not available in Linux distributions due security implications.
Thus, the build instructions should be extended to include the installation of rustup. Alternatively, it would be preferable not to use rustup at all but rather rely on the tools supplied by the distribution repositories.

Sure, I'll update the README.
rustc_codegen_gcc uses the unstable flag -Zcodegen-backend, so it requires rust nightly. Do some distributions provide packages for specific Rust nightly?

My understanding is that it's always disabled for stable releases. Any -Z flag is and an attempt to use one on stable would result in:
error: the option `Z` is only accepted on the nightly compiler

And I bet this codegen-backend will remain unstable for a long time since its API keep changing. But I could be wrong about this.

OK. I would have assumed that you would build Rust from source yourself anyway. And I'm not sure why you would need rustup for that.

Since I don't have to build rustc (as I only build a .so that is loaded by rustc), I avoid it.
I pick a nightly version and pin to it in this file.

If the concern is the distribution of the gcc-based rustc to Linux distros, perhaps the best would be to build rustc with codegen-backends = ["gcc"] in the config.toml.
That would not require rustup.

And I bet this codegen-backend will remain unstable for a long time since its API keep changing. But I could be wrong about this.

-Zcodegen-backend may end up getting stabilized as -Ccodegen-backend in the future, but in that case it will only allow switching between codegen backends distributed with rustc itself (which cg_gcc may become in the future), not external backends. For external backends it will likely remain unstable for a long time if not permanently.

If the concern is the distribution of the gcc-based rustc to Linux distros, perhaps the best would be to build rustc with codegen-backends = ["gcc"] in the config.toml.

It isn't wired up to ./x.py dist yet unfortunately. Part of https://github.com/rust-lang/rust/pull/81746 is wiring this up.

If the concern is the distribution of the gcc-based rustc to Linux distros, perhaps the best would be to build rustc with codegen-backends = ["gcc"] in the config.toml. That would not require rustup.

Ah, that sounds like a good idea. If it's actually possible to build Rust with both backends enabled without running into any build failures, I will look into enabling that for Debian's rustc package. Then it should be much easier to test the GCC backend on Debian and Ubuntu.

I think it is a bit premature for that. Building with multiple backends has been supported for several years, but producing dist packages containing backends other than llvm is not yet possible. In addition switching backends is not yet possible on stable.

I'm aware of the fact that alternative backends are not mature yet. I'm more interested in making it easier to test alternative backends so that more developers and users can provide feedback and fixes.
But I guess we will have to wait at least until all GCC patches have  been merged upstream so that a standard distribution GCC package can be used.

PR is up, i don't know if still necessary to assign this issue to me.

Not necessary but assigned you anyway.


text:
Inline comments in declarations get deleted

Rustfmt converts
pub /*const*/ fn cant_be_const_yet() {}

pub fn cant_be_const_yet() {}

I'd really like to keep that comment. =(

$ rustfmt --version
rustfmt 1.4.37-stable (2a3635d 2021-05-04)

Thank you for reaching out. There's probably open issues somewhere in the issue tracker for this but I can't recall them offhand and don't feel like doing a detailed search so will leave this open for now.
For a little context as to why the comments are lost, rustfmt is an AST driven formatter which means that rustfmt doesn't directly see things like inline comments while iterating over the AST nodes to generate the target formatting. Instead, rustfmt has to peek back into the source in places to see if there are comments between those elements which are explicitly represented in the AST.
Sometimes there's just bugs in rustfmt where we're missing checks for comments in those "between" places, but in other cases the comment-check is skipped intentionally, typically a result of weighing the tradeoffs between complexity/impact (both on the rustfmt source as well as the rustfmt runtime) and how common comments are to appear in those locations in practice.
Your snippet with comments in between parts of the function signature header is more the latter type, where it's a known case that hasn't yet warranted the effort to change. That doesn't mean that we want comments within the signature to be dropped, just some background on why they are and why it's not particularly likely to change in the immediate future. It's a very unusual place for long-lived comments, so for now you may just want to consider doing something different with your comments to move them outside the fn sig, e.g.
/* pub const fn cant_be_const_yet() {} */
pub fn cant_be_const_yet() {}

// or

/*const*/
pub fn cant_be_const_yet() {}

For anyone interested in taking a look at this, a good place to start would probably be rewrite_fn_base which handles the corresponding formatting. However, beware that there's likely to be several frustrating cases to be handled, including multiline block style comments, inner line style comments, around wrapping/width limits, etc.
https://github.com/rust-lang/rustfmt/blob/541aeba5b2c6063f73ee6ce7aa050a4df4bccce9/src/items.rs#L2180-L2187

For a little context as to why the comments are lost, rustfmt is an AST driven formatter which means that rustfmt doesn't directly see things like inline comments while iterating over the AST nodes to generate the target formatting. Instead, rustfmt has to peek back into the source in places to see if there are comments between those elements which are explicitly represented in the AST.

I'm actually surprised. I would have expected rustfmt's AST to aggressively attach comments to tokens, so that /* const */ would be part of the fn or pub token (this is how I've seen other formatters do it; I think the Bazel/Starlark formatter does it?). I don't think it's a big deal to delete these comments. Makes sense to deprioritize something minor like this. Thanks!

I would have expected rustfmt's AST to aggressively attach comments to tokens

There is no "rustfmt AST". rustfmt uses the rust compiler's internals, and the rustc parser and AST do not explicitly represent comments, whitespace, etc.

source: gharchive/issue

authors: calebcartwright mcy

repo: rust-lang/rustfmt

license_type: permissive

license_source: github-api


text:
max_width makes short lines longer

If I have some code that is formatted perfectly correctly for a max_width = 50:
fn example() {
    let x = [1, 2, 3]
        .iter()
        .rev()
        .enumerate()
        .count();
}

then the same code formatted with a longer maximum length (max_width = 100) always gets reformatted to stretch as widely as possible. It gets changed despite already being formatted cleanly, and not exceeding the maximum width:
fn example() {
    let x = [1, 2, 3].iter().rev().enumerate().count();
}

This makes rustfmt's formatting especially detrimental when max_width is set to a high value (like max_width = 150 or max_width = 200), because expressions that had reasonable line breaks previously are forced to become very long lines.
I don't mind having occasional long lines in the code, and I would like to be able to set higher allowable maximum line width, without it also becoming a target width for making all code maximally wide.
Example use-cases:

In if conditions, wrapping has a relatively high cost. Indentation of the wrapped conditions is the same as indentation of a usual "then" block, so the reader has to pay close attention to the unusual position of {. In such cases a line that is a bit longer is IMHO a lesser evil. But I don't want rustfmt to undo already wrapped if conditions where I've already decided the line was too long.

I have match statements with similar but not identical content (e.g. when mapping types in an enum to invocations of a generic function, the calls may be very similar, but variant names and variable names differ in lengths). It's possible for some, but not all, of the match arms to exceed the usual limit of 80-100 chars. This makes rustfmt format the arms inconsistently in regards to each other: some will have multi-line formatting, some will have single-line formatting. This makes it harder to compare the match arms. A value of max_width that makes one match consistent will break consistency of another that has different range of widths.

I have expressions that implement standard-defined mathematical formulas defined in external documents. I want those expressions to have line breaks in the same places as in the source document, for them to be easy to compare to the original for review.

I want to avoid trivial code changes from looking more complex in code reviews. Code is more often read more than written, and code that is developed via pull requests is also often read as a diff. For me as a maintainer, readability of diffs of the code is most important. When a PR renames a function or a variable, I want that PR to have minimal single-word diffs. Unfortunately, if the new name has a different length, it often makes lines cross the (un)wrapping threshold, and changes start to look like a complete rewrite of entire blocks/statements. Same thing happens when a line is deleted from a multi-line expression (e.g. a struct field is deleted). Instead of keeping it as an obvious 1-line-delete diff, rustfmt can decide to unwrap the whole multi-line block into one long line, making the diff much bigger, and obscuring what has really changed.

Why not #[rustfmt::skip]?

It's an all-or-nothing mark, rather than control over line length. I still want all the short and long lines to be correctly formatted in all other aspects, like spaces around punctuation. When a long line ends with a block, I still want the indentation of the following code in the block to be formatted well.

#[rustfmt::skip] attribute by itself adds visual clutter. It becomes a point of contention whether an improvement in readability of one line is worth adding an eyesore in another. Usually it isn't, which makes me feel forced to live with an undesirable max_width behavior that always makes some code worse regardless of what value I set it to.

Notably, go fmt does not have this problem. In Golang, lines that exceed the maximum limit are wrapped to become multi-line expressions, but expressions that already fit below the maximum line length are not forced to become one-liner spaghetti. All lines are still formatted correctly according to gofmt's rules, and this behavior is entirely deterministic and idempotent.

@kornelski I'm not sure if it'll help in all cases, but maybe some of rustfmt's more granular width configurations could help you out here:
I'm linking to use_small_heuristics, which links to the other width options.

No, these don't help at all. I've reviewed and tested these carefully. The problem is not in choosing the right widths for various items, the the general principle that rustfmt will always unwrap shorter lines up to the maximum setting. If set short widths, I'll have much more wrapping than I want. If I set long widths, I'll have unwanted spaghettification.
I can only move the thresholds, but I can't disable the domino effect of code crossing a threshold.
To be clear, I'm not asking to change max_width specifically, but some option to change the behavior to be like go fmt would be great.

Thanks for clarifying. That might be easier said than done. As you've noted, rustfmt doesn't take the source layout into account when rewriting AST nodes.

rustfmt somehow preserves empty lines, even though they're whitespace and not part of a usual AST. Perhaps in a similar way it could keep information about the original line lengths, and format AST nodes for a max_width set to maximum line length of any of the child nodes?

The way rustfmt preserves newlines between AST nodes is actually fairly simple and doesn't require keeping track of any layout information from the source code. It does however peek back into the source to count newlines and recover comments.
It's maybe possible to provide an option that would infer the layout of nodes in certain contexts based on the source code, for example forcing a vertical layout, but I don't think we'd be able to format code exactly like go fmt would.

There's a lot of good discussion on this thread but there's a few things I want to add.
I know this is somewhat tangential to the underlying behavior being requested, but I think important to note rustfmt has some config options (including max_width) that by default change the values of other options unless those options are set explicitly by the user. So changing the value of max_width is also changing the value of chain_width which is what triggers the specific formatting change here.
Ultimately, I think the difference between the requested behavior and the current behavior is that the Style Guide currently has very explicit prescriptions based on column widths, and if an element is less than that threshold (e.g. chain_width) then it must be single line, else it must be multiline, regardless of whatever choice the developer made about linebreaks in the input.
As a result, you'll never see something like this with rustfmt
fn example() {
    let x = [1, 2, 3]
        .iter()
        .rev()
        .enumerate()
        .count();

    let x = [1, 2, 3].iter().rev().enumerate().count();
}

two identical constructs will be formatted exactly the same way, every time. that's an intentional decision, and one that comes with tradeoffs that reasonable people may weigh differently.
i'll share that the Style team already has plans to review the default rules for 2027 to try to devise something that produces more consistently "better" results as we believe that column width is simpler to grok mentally and implement in tools but too often produces subpar results.
In the meantime, something the rustfmt team has been actively exploring are config-driven solutions that would add options that support devs/teams that want more manual control over when line breaks are added or removed, and which would enable the the outcome requested here.
Given the current (and unlikely to change) model, I do not envision the default formatting behavior will ever change and be gofmt, but I do completely agree that the whitespace information is available in the input and we can support non-default formatting options that utilize it.
Due to the AST-centric nature of the formatting rules and behavior, it is something we would have to do very incrementally (chains, arrays, etc.), but it is doable. We successfully implemented a POC with this for chains, but had to temporarily put it on the backburner due to the focus on the 2024 edition. It's something we'll pick back up once 2024 ships

two identical constructs will be formatted exactly the same way, every time.

This is only true in a narrow case. It's not every time. In practice, the opposite happens, and rustfmt can force identical AST nodes to look completely different:
let x = [1, 2, 3].iter().rev().enumerate().count();

if true {
    let x = [1, 2, 3]
        .iter()
        .rev()
        .enumerate()
        .count();
}

rustfmt formatting identical expressions in different ways is one of the issues I have with it. If the longest line happens to cross a threshold:
match val {
    Enum::One(one) => take(one).and().process().it(),
    Enum::Two(two) => take(two).and().process().it(),
    Enum::Three(three) => take(three).and().process().it(),
    Enum::Four(four) => take(four).and().process().it(),
}

Then rustfmt makes identical match arms formatted differently:
match val {
    Enum::One(one) => take(one).and().process().it(),
    Enum::Two(two) => take(two).and().process().it(),
    Enum::Three(three) => take(three)
        .and()
        .process()
        .it(),
    Enum::Four(four) => take(four).and().process().it(),
}

This is only true in a narrow case. It's not every time. In practice, the opposite happens, and rustfmt can force identical AST nodes to look completely different:
let x = [1, 2, 3].iter().rev().enumerate().count();

if true {
    let x = [1, 2, 3]
        .iter()
        .rev()
        .enumerate()
        .count();
}

The indentation level of a node is an important factor when determining the layout since that impacts how much room rustfmt has before it needs to break lines. It might be better to say that "two identical nodes will be formatted exactly the same way, every time if they appear in the same context".

rustfmt formatting identical expressions in different ways is one of the issues I have with it. If the longest line happens to cross a threshold:
match val {
    Enum::One(one) => take(one).and().process().it(),
    Enum::Two(two) => take(two).and().process().it(),
    Enum::Three(three) => take(three).and().process().it(),
    Enum::Four(four) => take(four).and().process().it(),
}

Then rustfmt makes identical match arms formatted differently:
match val {
    Enum::One(one) => take(one).and().process().it(),
    Enum::Two(two) => take(two).and().process().it(),
    Enum::Three(three) => take(three)
        .and()
        .process()
        .it(),
    Enum::Four(four) => take(four).and().process().it(),
}

Having more consistent match arm formatting has been brought up before (https://github.com/rust-lang/rustfmt/issues/3995). Probably best to keep the discussion here focused on how increasing the max_width makes short lines longer.

authors: calebcartwright kornelski ytmimi


text:
any() and all() methods for mask types

It appears that mask types don't currently have any() and all() methods that packed_simd and simd had.
Filing this to keep track of adding those methods.

Related to #36

authors: calebzulawski hsivonen

repo: rust-lang/stdsimd


text:
Roundoff error when doing scalar division of Complex64

From @fkjogu on August 9, 2016 14:54
Transforming all scalar operations to complex arithmetics leads to numerical roundoff errors when doing scalar division of a Complex64, compared to a direct floating point division.
Consider this minimal arbitrary example
extern crate num;

use num::complex::Complex64;

fn main() {
    let r = 98.29372511785971;
    let c = Complex64::new(0., r);
    let s = 25.;
    assert_eq!(c / s, Complex64::new(0., r / s));
}

I'd expect it to be exactly the same, which is not the case. This is due to the much more complicated calculation dividing to Complex64.
This might be a philosophical issue, but I find it unnecessary to convert a scalar to a complex number first. Not only it introduces some additional error, but also adds to runtime.
In my opinion we should use specialized scalar arithmetic, which should be easily doable, thanks to macros.
Shall I turn this into an pull request?
Copied from original issue: rust-num/num#217

I'd expect it to be exactly the same, which is not the case.

Even direct floating point division like assert_eq!(a/b, a/b) can't be assured in general.  Some architectures, especially x86, may store values in registers with more precision than they would have stored in memory.
But we can probably do better here, regardless.

In my opinion we should use specialized scalar arithmetic, which should be easily doable, thanks to macros.

Right, they're already converted naively with the real_arithmetic! macro.  If you'd to implement each op more directly, that would be great.

Shall I turn this into an pull request?

Sure!

I forgot that rust-num/num#320 already made these ops more direct, although that missed Rem -- I'll post a new PR for that.
The remaining consideration is that assert_eq is unreliable with floats, but that's just how it is -- nothing we can fix here.

repo: rust-num/num-complex


text:
Wrapper types?

Taking inspiration from NonZero<T> and Type-driven parsing, what if this crate (or a separate one, for organizing) provided wrappers for specific numeric properties?
Strawman examples (not tested as compilable):
#[derive(Deref)]
struct Even<T: Integer>(T);

impl<T: Integer> even for Even{
    fn new(x: T) -> Option<Self> {
        if x.is_even() {Some(Self(x))} else {None}
    }
}
// assume `Odd` is defined similarly...

impl<T> Add for Even<T> {
    // even + even = even
    fn add(self, &Self) -> Self
    // even + odd = odd
    fn add(self, &Odd) -> Odd
}
// etc... assume Odd also has similar methods which follow the theorems of math

New fns could be defined that take advantage of such types. If a fn requires a Prime to work properly and safely, it'll no longer have to check primality by itself!
The compiler can optimize code using Even or Odd to have the same size and alignment as Option<Even | Odd> (because LSB is unused).
Existing fns could use these types to guarantee stuff such as
fn sqrt(n: Square<u64>) -> u32

// this equality will be satisfied for all `Square`s!
assert_eq!(sqrt(Square::new(4).unwrap()).pow(2), 4)

If num provided such types, there would be less crates implementing their own wrappers, or worse, doing redundant expensive checks:
use crate1::Prime1;
use crate2::Prime2;
use crate3::CheckedPrime;

crate1::some_fn(Prime1::new(5).unwrap())
crate2::another_fn(Prime2::new(5).unwrap())
crate1::some_fn(CheckedPrime::build(5).unwrap())

If there was 1:
use num_integer::Prime;

let p = Prime::new(5).unwrap();

// assuming all crates have chosen `num` as standard
crate1::new_fn(p)
crate2::yet_another_fn(p)
crate1::foobar_fn(p)

I've been considering that, perhaps, this would be more appropriate to something like ranged-ints?

If multiple other crates have a shared need for some wrapper, they can collaborate on a common crate, but I definitely don't want to get into implementing all possible number categories here. :)

they can collaborate on a common crate

good point 👍

definitely don't want to get into implementing all possible number categories here. :)

I totally agree! haha. There's literally infinite of them. Even niche ones such as Fib, and AFAIK, it's extremely rare to find an algorithm that requires Fibonacci numbers (maybe Fib Trees?).
I propose we only focus on simple, everyday stuff, such as Even & Odd. There's no need to impl operator traits, as Deref can be used to implicitly operate on them as regular ints

Honestly, I'd rather see even the simple stuff developed in their own crate. If it needs small additions in num-integer (not breaking changes), that might be accommodated, but this isn't a good place for big new experiments.

this isn't a good place for big new experiments

I agree, especially considering rust-num/num#421

authors: Rudxain cuviper

repo: rust-num/num-integer

license_source: bigquery


text:
Transitioning from bootimage to the new system

So, my kernel still uses the old bootimage building system, but that's now deprecated. However, I don't know how to (safely) transition from the old to the new system. So how do I go about doing this?

Bootimage is not deprecated yet, it's just that the newest bootloader version uses a different build approach (documented here. I'm currently working on updating the Writing an OS in Rust blog for the new version and I plan to create a migration guide too. The fundamental differences are:

New build system instead of bootimage.
Pixel-based framebuffer instead of VGA text buffer.
When using the new UEFI support, you need to use the APIC since the legacy PIC is no longer supported.

Update: so I just re-read the documentation and it makes a bit more sense, but it still raises some questions, e.g.: where do I get "cargo-builder"? How do you go about writing one if that's necessary? (I was thinking of using something like cargo-make to automate that process a bit as well.)

cargo builder is an alias command defined in the .cargo/config.toml of the bootloader, so it is automatically available in the bootloader dir without installing anything.

@ethindp Maybe this is what you want: https://gist.github.com/JonahHenriksson/f037c778881918ac57ee131e0a045735
Tried automating this with cargo make, but it was really nasty. I wanted to separate the builder command into its own task, but working with environment variables didn't work. Finally got something that works, but requires you to set some of your own project specific variables. The bootimage tool was definitely easier to automate, but I'm happy to see UEFI support.

@phil-opp Hey, how do we use the framebuffer? I tried writing to it, but get nothing. Is there something I need to enable or set before using it? Where would I go to learn more? The UEFI spec?

@JonahHenriksson Writing to the memory area reported by the boot info should work. If it doesn't, that would be a bug.
I also wanted to say sorry about the missing documentation around the new build system. I thought I would get to this earlier, but the latst few weeks have been busy for me. I try to create a small example for the build crate in the next few days.

I actually have a question about this. Do I use standard characters
when I write to the GOP framebuffer, or can I use something more
elaborate like a TTF to render individual glyphs and then just write
the raw glyph renderings to the FB?
On 5/16/21, Philipp Oppermann @.***> wrote:

@JonahHenriksson Writing to the memory area reported by the boot info should
work. If it doesn't, that would be a bug.
I also wanted to say sorry about the missing documentation around the new
build system. I thought I would get to this earlier, but the latst few weeks
have been busy for me. I try to create a small example for the build crate
in the next few days.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/rust-osdev/bootloader/issues/150#issuecomment-841825059

--
Signed,
Ethin D. Probst

The framebuffers that bootloader v0.10 sets up are pixel-based (on both UEFI and BIOS systems). This means that you can (and need to) control each individual pixel, there is no such thing as the ASCII-aware VGA text buffer anymore. So to display text, you need to render it to pixels first. You can do that using full TTF rendering, or you can use some simpler bitmap font such as font8x8.

I didn't notice this until now -- thanks for that information! So, say I want to render the string "Hello!" using fontdue. So, would I do the following?

I create a layout and append text to it.
I get the glyphs from the font
I loop through each glyph and... write what exactly to the framebuffer? Relevant information is over here.

I've never done font rendering before so I've no idea what to do.

@ethindp I haven't worked with fontdue yet, so I don't know any specifics. However, there are typically two high-level steps in font rendering: determining where the glyphs should be placed (e.g. dependent on the spacing between glyphs) and rendering each glyph. The GlyphPosition struct you linked looks like it's related to the first step. For the second step, you probably need something like the rasterize method. This outputs a bitmap, which is a two-dimensional array that contains the alpha value (0-255) for each pixel. By combining this alpha with the color of your choice, you can calculate the pixel values that you need to set in the framebuffer.
Hope this helps!

Lol, came back to work on my OS project after finishing up my school work, and now I see what I did. I iterated though the range of the buffer, instead of the buffer itself, setting those values instead... 🤦♂

@JonahHenriksson Your makefile is (sort-of) working. Its just not building the script properly -- cargo apparently still has that bug where it builds everything with the target specified in .cargo/config.toml. Removing that (sort-of) fixes the problem (though you then need to annotate each cargo command with --target) but then it fails to build the script because of -Z build-std.

So I got it to work and its booting (sort-of).
@phil-opp You mentioned 8x8 bitmap fonts. If I use font8x8 (I was looking at the docs a few minutes ago at time of writing) what is the process for rendering a character via the framebuffer? I've done a lot of thinking and think that 8-bit fonts might be easier for now.

Are there plans for a definitive migration guide from bootloader 0.9 to 0.10?

We now have migration guides available at https://github.com/rust-osdev/bootloader/tree/main/docs/migration.

authors: JonahHenriksson PatchMixolydic ethindp phil-opp

repo: rust-osdev/bootloader


text:
Fix the broken doc

Also, applied rustfmt.

Thanks!

source: gharchive/pull-request

authors: IsaacWoods toku-sa-n


text:
add clean_up and clean_up_with_filter

This pr adds support for deallocating unused page tables.
Closes #238

I just noticed PageRange in the docs. I'll change my pr to use this later

Right now this is only implemented for the MappedPageTable type (and the derived OffsetPageTable), but not for the RecursivePageTable. If possible, I think it would be a good idea to make the method generic on the Mapper trait and implement it for the recursive page table type too.

I don't think it's possible to make this generic on Mapper alone because it's very high-level and doesn't support walking the page tables. It would be possible to do this with PageTableFrameMapping but there are no public implementations and RecursivePageTable doesn't implement it either.
I'm not entirely comfortable with recursive page tables just yet, so that's why I haven't implemented anything for them.
So I think there are three options:

just implement this for certain types like I already did
make it generic on PageTableFrameMapping, implement PageTableFrameMapping for RecursivePageTable and make those implementations public (don't implement them only on internal types)
Do something entirely different

What are the use cases for clean_up_with_filter method? Its interface is quite complex with the filter function, so I wonder if a simpler interface based on an address range would be better (e.g. clean_up_addr_range). Or would it be too restricting? (Internally, we could of course still keep the filter-based function, so no change of the implementation would be necessary for this).

In your comment on the initial issue (#238) you mention that the user should be able to integrate their own logic, so I tried to make it as customizable as possible. In hindsight I agree that this was perhaps needlessly over engineered. I like the idea of replacing clean_up_with_filter with clean_up_addr_range especially because it would also probably make the implementation much more readable. clean_up can also be implemented with clean_up_addr_range so there wouldn't be a need for an internal clean_up_with_filter.

Right now this is only implemented for the MappedPageTable type (and the derived OffsetPageTable), but not for the RecursivePageTable. If possible, I think it would be a good idea to make the method generic on the Mapper trait and implement it for the recursive page table type too.

RecursivePageTables need their own implementation: They will never be completely empty because they always have an entry pointing to themselves.

I guess they still need some custom logic though because a clean up in a certain region should probably also clean up the corresponding recursive page table entries.

Or maybe not? Still struggling to wrap my head around this

I'm not sure why CI is failing, but I'm pretty sure it's unrelated to this pr.

Thanks a lot for the quick changes!
The CI failure was fixed on master already, so updating your PR to the latest master should fix it. Given that this PR is quite old already, I would recommend to just merge master into your branch instead of attempting a rebase.

I saw that you no longer use the next branch, so I changed the base branch to master.

Yeah, I just noticed that as well. We normally only use it for PRs with breaking changes, other changes can be merged directly into master. I don't think that this contains any breaking changes, so I just wanted to propose changing the base branch. Thanks!


text:
fix: read upto EOF in uncompress

btw this wasn't an assigned task, i was curious on the uncompress and it seems it didn't read upto EOF with those dynamic code size(i.e n_bits), So this fixes it and i also added some comments, there were a lot of bitwise operation, so i thought it needed some comments

Very nice!   This is helpful, thanks.  merged.
Protip:  It might be possible to use an existing crate for the Read-N-Bits and Write-N-Bits operations.  Other file formats such as audio and video codecs have "stream of 10-bit codes" type of patterns.  I meant to research this.  "bitstream" might be a good search word.

@jgarzik, i did have the thought of looking up, but the "zero dependency goal" thing hit my head and had to go with it

authors: jgarzik rishadbaniya

repo: rustcoreutils/posixutils-rs

license: MIT


text:
KEY_VOICECOMMAND missing

This is a minor problem I guess but it would be nice if KEY_VOICECOMMAND was included in the keyd. Now with the --monitor option keyd gives "unsupported evdev code" (keyd v2.4.3).
The rationale is that the Voicecommand button is included in some remote control style keyboards (for controlling HTPCs, PCs) and some people might not have any use for remote voice control. On the other hand, there are very few buttons on such controls, so remapping this would greatly expand their capabilities. (Example: (https://www.umax.cz/galerie/9_47415/name-original.jpg) id 1915:1025, the button is the blue microphone in the middle)
I was able to remap the voicecommand key by choosing a random key in the code (BTN_FORWARD - KEYD_MOUSE_FORWARD) and swapping it with (KEY_VOICECOMMAND - KEYD_VOICECOMMAND) and it works perfectly. But of course a "native" solution would be much better.
Thanks!

Support for this should be added to the latest commit. Confirmation would be appreciated.

It works a treat! Thanks a lot!

authors: rvaiya samozrejmost

repo: rvaiya/keyd


text:
Warpd hangs after some time with 100% CPU

Hello, as you asked, creating a new issue. So I use the latest warpd commit (built from source) and latest macos.
So I use it like this: enter hint mode, chose location, maybe small movement with hjkl and click.
After 3-4-5-6 times of doing it, I click my keybinding for enter hint mode and warpd hangs and no keyboard events passed to system. Also I don't see any hints, for example. In process monitor I see that warpd consumes 100% cpu.
buttons: n , m
oneshot_buttons: space - /
hint_border_radius: 10
hint_font: Iosevka
use_system_cursor: 1

Please post the output of warpd -v.

warpd v1.3.5-osx (built from: 6d43797)

I can't seem to reproduce this. Does this happen with a blank config? Also try running make clean to ensure there are no artifacts from previous builds.

Same for me, but i am also use Karabiner-Elements 14.10.0.

I'ts possible karabiner is interfering with the event tap used by warpd. @max-frai Are you using any other remapping software (e.g karabiner)? @funvit Can you see if disabling karabiner solves the problem?

No, I don't have any remapping software. Pure latest mac os.
Also I just tried again. After reboot I long time didn't use warpd and now decided to call the hint mode and right after keybinding was clicked, warpd process started eating 100cpu and 300gb virtual ram.

@max-frai I still can't reproduce this. Does this happen after clicking on a secure input field? (e.g web password field, sudo prompt, etc). Can you do a clean install using the latest commit? (git pull origin master && make clean && make && sudo make install).

Also, are you using a multi screen setup?

I tried clean make install and default config and it works okay all day. So I will try to add back my config file and test further everything.

Okay, no luck :( After reboot I tried to run it again and the problem appeared. With default config.

Okay, I found the issue. It works okay until system input language is english. But when you enter keybinding in other language, it hangs.
So when my input language is ukrainian, I press Command + Option + X and warpd starts consuming 100% cpu

Greetings,
I have similar issue, if language is different from English (Bulgarian) warpd just takes the keyboard input and there is no way to recover, except killing the process (which is impossible without keyboard :) ).
Running on OSX:
Version:
warpd v1.3.5-osx (built from: 01650ea)
Is there any workaround around this?
This tool seems what I always wanted, and thank you for making it !

when you enter keybinding in other language, it hangs.

Have the same issue

I have the same issue with Hebrew. Only way around it is killing warpd with only the mouse since the keyboard no longer responds until warpd is terminated.

authors: B1T3X askazakov funvit max-frai rvaiya tzkoshi

repo: rvaiya/warpd


text:
Set up Travis and add badge

I'll make a PR, but I don't have permission to flip the switch on Travis. In develop we can now do:
rebar3 do proper, ct

[![Travis](https://img.shields.io/travis/rvirding/lfe.svg?maxAge=2592000)]()

repo: rvirding/lfe


text:
circular reference

alert.hasCancelButton = cancelButtonTitle != nil;
alert.hasDestructiveButton = destructiveButtonTitle != nil;
alert.hasOtherButtons = otherButtonTitles.count > 0;
if ([UIAlertController class]) {
alert.alertController = [UIAlertController showAlertInViewController:viewController
withTitle:title message:message
cancelButtonTitle:cancelButtonTitle
destructiveButtonTitle:destructiveButtonTitle
otherButtonTitles:otherButtonTitles
tapBlock:^(UIAlertController *controller, UIAlertAction *action, NSInteger buttonIndex){
if (tapBlock) {
tapBlock(alert, buttonIndex);
}
}];
}
alert->alertController->tapBlock->alert

should be fixed in 0.8

authors: FlyBigBird ryanmaxwell

repo: ryanmaxwell/RMUniversalAlert

license: mit


text:
Web hackaton. Added features

Smirnov Sergey
Mogilevskiy Alexander
Beskrovnyj Konstantin

login() - нет проверки на пустой логин

//команда pr №353

logout() - logined.remove(name) удаляет только последнего пользователя. Как вариант, можно заменить Queue на ArrayList.

+2 за ревью
Просил написать список фичей - напишете?

authors: Akazantseva Al-p-i SergSmirn

repo: rybalkinsd/atom


text:
Convex Hull

One defining feature of this software is that we need to be able to take a group of features and produce a convex hull which defines the boundary of the thing.
This can be accomplished in a lot of ways, but I think that Graham scan is probably the most suited?

We can load GeoJSON via the geojson crate, and perform the convex hull operation via the QuickHull implementation at geo::algorithm::convexhull.

So, while a "convex hull" is a good thing to have, when it comes to grouping features together into one outline, it's a bit more difficult.
The "convex hull" of the collection of shapes

is actually a pentagon, not the crown shape that actually represents the outline.
What I think we're more looking for is a way to dissolve boundaries between polygons. In other words, see if there's a set of overlapping points. I'm not sure if the datasets we get have exact point-to-point intersections, which makes things a bit difficult.

repo: rye/distringo


text:
Causing CTD from Stack Overflow

The past few days I have been plagued with random CTD's caused by JContainers for SE/AE. Both the version currently up on Nexus and the pre-release here on Github have been giving the same result. According to the Crash Logger, JContainers suffers a repeating stack overflow error immediately before the crash. JContainers log included.
JContainers64.log

This is from some mod using the optional JC's Lua scripts. Frankly, it looks like installation / usage problem and not something related to a specific version of JC.

repo: ryobg/JContainers


text:
All tests throw "Error: No active group"

Describe the bug
All my tests throw 2 errors at a time, 1 is actual error of a test and the other is "No active group"
To Reproduce

I added jest setup files as per your instructions
I changed jest config by adding ./jest.setup.js to setupFilesAfterEnv
I run tests as before using jest --runInBand --verbose=true ./test/e2e command
I generate report using node_modules/.bin/allure generate ./allure-results -c && allure open

Actual result
Tests are run correctly. Each tests has 2 results: 1 for the tests and 1 for the reporter. Results for the reporter are shown in Allure after report generation. That's not the information I want to see.
Expected result
No errors from reporter upon run AND if there're reporter's errors they should be omitted for the reporter.
Desktop (please complete the following information):

OS: iOS 10.15.7
jest-allure2 Version 1.2.3
jest version 25.2.1 (also tried with 26.6.0)
node version 14.13.1 (also tried with v12)

Additional context
Full error:

at JasmineAllureReporter.get currentGroup [as currentGroup] (path/node_modules/jest-allure2/src/reporter.ts:76:10)
at path/node_modules/jest-allure2/src/reporter.ts:434:9
at Object. (path/node_modules/jest-allure2/src/reporter.ts:399:31)
at path/node_modules/jest-jasmine2/build/queueRunner.js:45:12
at new Promise ()
at mapper (path/node_modules/jest-jasmine2/build/queueRunner.js:28:19)
at path/node_modules/jest-jasmine2/build/queueRunner.js:75:41

Jest has this settings:

{
"testEnvironment": "node",
"setupFilesAfterEnv": [
"/test/expect.js",
"./jest.setup.js"
],
"collectCoverage": true,
"coverageReporters": [
"text",
"text-summary"
],
"collectCoverageFrom": [
"src//*.js",
"!/node_modules/",
"!/config/.js",
"!**/.mock.js",
"!**/*.json"
],
"reporters": [
"default",
[
"jest-junit",
{
"outputDirectory": "reports",
"outputName": "unit.xml"
}
]
]
}

I had the same issue and bumped back to previous version (1.2.2) and it is ok now


text:
Compatibility issues with error-prone

Lombok currently does not work with error-prone.
See issue in error-prone project: https://github.com/google/error-prone/issues/347

This isn't really our bug. The best resolution would be for lombok to support javac 9.

I created issue #985 to handle jdk9 related issues.

repo: rzwitserloot/lombok


text:
django.template.exceptions .TemplateDoesNotExlst: admin/edit inline/stack -nested.html

我已经解决 ,忘记在steeings 添加app  抱歉. 可以删帖了

repo: s-block/django-nested-inline


text:
🛑 Motheo Koffiefontein is down

In b4c4680, Motheo Koffiefontein ($KOFFIEFONTEIN) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Motheo Koffiefontein is back up in 49c1185 after 25 minutes.


text:
Moved pull implementation from stream.hpp to new file pull.hpp

This is a more major refactoring of stream.hpp, which is why I'm doing it on it's own branch, and initiating a pull request. This branch splits the implementation of stream and pull into separate files. It also removes the function pull.toStream(), which just invoked stream's constructor. This created an unnecessary cyclic dependency between the two classes. All instances of pull.toStream() were replaced with a direct call to streams constructor.
Questions:

What is bot (declared as an empty union), and how does it differ from top (declared as using top = std::monostate)?
Can we remove eff.hpp? It doesn't seem to do anything. It contained the definitions for bot and top, but I moved those into stream.hpp and pull.hpp respectively.

top = top type, meaning it has only one inhabitant. An example of top is a struct with no fields. The only inhabitant is the single empty struct.
bot = bottom type, meaning it has zero inhabitants. An example of bot is a union with no entries. There's no way to initialize this union. (So, a task<bot> is a task that never completes. A vector<bot> can only ever be an empty vector. Etc.)

Regardless, pull should not be exposed as a primary type. I will explain why in tidy/stream.docs.


text:
Connect error

masterthermconnect --api-ver v2, result = Connection Failed {"error":"invalid_grant","error_description":"Invalid user credentials"}
Version of the custom_component
 tryed all versions
Describe the bug
A clear and concise description of what the bug is.
Can not connect into server  , username and password is correct
Debug log
do not know were is debug
masterthermconnect --api-ver v2
Connection Failed {"error":"invalid_grant","error_description":"Invalid user credentials"}

Add your logs here.
none

Are you sure you need api version 2?
Op do 22 dec. 2022 12:00 schreef valentapat @.***>:

masterthermconnect --api-ver v2, result = Connection Failed
{"error":"invalid_grant","error_description":"Invalid user credentials"} Version
of the custom_component tryed all versions Describe the bug
A clear and concise description of what the bug is.
Can not connect into server , username and password is correct
Debug log
do not know were is debug
masterthermconnect --api-ver v2
Connection Failed {"error":"invalid_grant","error_description":"Invalid
user credentials"}
Add your logs here.
none
—
Reply to this email directly, view it on GitHub
https://github.com/sHedC/python-masterthermconnect/issues/41, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJUM62NYYDKMTUVG5AALO3WOQYFRANCNFSM6AAAAAATGS3KUM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

its the same
Im try      masterthermconnect --user val***** --password ********
Connection Failed Invalid user name or password

If you login using https://mastertherm.vip-it.cz/webui.php same credentials however if you are using the parameters for the user and password and have a space in the username please replace the space with a + and retry.
Old interface some usernames have spaces but those get converted to + but seems to fail if doing from the parameters.

v1 - mastertherm.vip-it.cz is pre 2021 installs.

I have new version,  mastertherm.online, username  conntains   "_" (underline),
Is this problem ?

No idea would have to debug to see what it sends, we will check it out, it is possible though.

I just tried running
masterthermconnect --api-ver v2 --list-device-data --user myemail@gmail.com --password mypassword

and this works perfectly. But, my email and password doesn't contain any underline

username I cannot change,  password contains    %
for more info:   homeassistant on synology in docker,  HASS also cannot connect, all I try . in docker terminal

Its the %, it has to be encoded for URL,s I will do that please don't change it :)

bash-5.1# masterthermconnect --api-ver v2 --list-device-data --user my_username --password mypass%x
Connection Failed {"error":"invalid_grant","error_description":"Invalid user credentials"}
Traceback (most recent call last):
File "/usr/local/bin/masterthermconnect", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.10/site-packages/masterthermconnect/main.py", line 128, in main
devices = controller.get_devices()
AttributeError: 'NoneType' object has no attribute 'get_devices'

sorry - how correctly replace all files ?
pip install masterthermconnect==1.1.0rc2 ??   rc8 ???
or any command for update?

Sorry not yet deployed just doing some other updates then will implement an rc9 so install would be pip install masterthermconnect==1.1.0rc9

Just published rc9, fingers crossed, the user and password transfer correctly so hopfully works.

Its next on the list if I get a chance tonight I will, ignore the version on HASS until I do an official release all pre-releases are ignored.
HACS should just take the latest commit.  If I can do it before christmas I will do it tonight.

I have not HACS, need only folder /custom_components/mastertherm/

OT:

is it possible to execute commands? e.g. change temperature, on/off hot watter and save it.
how can send this data into mqtt or run this script from node-red
sorry and thanks

Not yet that going to start looking at once I have a stable read.  Then was going to only allow changes that we can fully confirm :)
Build it up as its all guess work

authors: SeBsZ sHedC valentapat

repo: sHedC/python-masterthermconnect


text:
2DSE: Cross-Platform Rendering and Mac Retina display fixes.

It should be like this video.
Windows and Linux now render properly. Mac should be a lot better but I require feedback from someone with a Retina display. Does it work like in the video?

I wish someone could provide me with some video footage so I could actually see how the alignment behaves now and have them test a couple trial & error iterations with me. The fixes in this PR should at least guarantee nothing is up-side down like loaded background images. Every time I ask around they are like "sure I will help" and stop replying. I wonder if I really have to purchase a MacBook Pro just to fix this PR...

I'm working on this issue

@Henry00IS
This is not a perfect fix, I've spent quite a few hours trying to fix this issue properly and I've not come across an easy consistent way to do this across Metal,DirectX/OpenGL and Retina/Non-Retina. It's hard to tell if the root cause is a Unity bug or a misunderstanding on our part, but given how inconsistent the behaviour is I wouldn't be surprised if this is a Unity bug.
I've updated this pull request with improvements that now make it reasonably consistent across those platforms, there are still some minor off by one pixel issues in certain configurations but it's significantly better than what's in master currently.
I have tested this in Unity 2017.3.1 on:

MacBook Pro - Retina - Metal
MacBook Pro - Retina - OpenGL
MacBook Pro - Low Res (Non-Retina) - Metal
MacBook Pro - Low Res (Non-Retina) - OpenGL
Windows - DirectX
Windows - OpenGL

As mentioned above it functions acceptably on all these platforms. If this pull request looks okay to you I'd suggest merging it to stabilise master, then creating a new issue to represent multi-platform improvements to the 2DSE grid rendering.

@sabresaurus
I can't possibly find the right words to thank you enough. I am currently on a vacation to my mom and this good news made it even better! Truly, thank you so much! 🙇
It's so nice to see you back in action! The rendering is fine under Windows and I trust your judgement for the other platforms. If the bottom half of the grid is off by one pixel that even happens on Windows sometimes, depends on the window size and scroll position, lines tend to get twice as thick, nothing too serious, because I switch from positive modulo into negative modulo calculations, there's a small hack that shifts things by one pixel. But again that's only the bottom half of the grid.

repo: sabresaurus/SabreCSG


text:
Sub second timing

Would love to have sub-second (millisecond precision is fine) for Viddy!
I run go test ./... through viddy a lot to ensure I don't introduce any intermittent test failures and every second just isn't fast enough for me!
Would you be open to me submitting a PR for sub-second precision on the -n flag?

@SophisticaSean viddy is supporting sub-second.
You can specify the value like following.
watch style
viddy -n 0.5 ls

Go style
viddy -n 500ms ls

I would like to close this issue.
If the above response was not suit for your requirements.
Feel free to reopen this.

thanks a ton! love viddy so thank you for your work on this

authors: SophisticaSean sachaos

repo: sachaos/viddy


text:
Exception when iOS app running on M1 Mac

2021-04-15 17:51:36.250058+0500 KickSharing[41952:669837] MagicTimer: initialized
2021-04-15 17:51:36.253818+0500 KickSharing[41952:669837] *** Assertion failure in -[MagicTimer.MGStandardTimerFormatter setAllowedUnits:], NSDateComponentsFormatter.m:806
2021-04-15 17:51:36.260599+0500 KickSharing[41952:669837] [General] Invalid parameter not satisfying: allowedUnits == 0 || !(allowedUnits & ~(NSCalendarUnitYear | NSCalendarUnitMonth | NSCalendarUnitWeekOfMonth | NSCalendarUnitDay | NSCalendarUnitHour | NSCalendarUnitMinute | NSCalendarUnitSecond))

I faced this crash too.
The problem is in MGStandardTimerFormatter class and converToValidFormat(ti:) func
the .nanoSecond is not acceptable for converting to string
So it should be this:
func converToValidFormat(ti: TimeInterval) -> String? {         switch ti {         case let x where Int(x) >= MGTimeUnit.hour.rawValue:             allowedUnits = [.hour, .minute, .second]         case let x where Int(x) <= MGTimeUnit.hour.rawValue:             allowedUnits = [.minute, .second]         default:             break         }         return super.string(from: ti)     }

Fixed in 1.0.3 version.

authors: SlonGL abspr sadeghgoo

repo: sadeghgoo/MagicTimer


text:
New feature banner is stretched incorrectly

Description
There is a bug with the banner on the Wallet page, around 1700px breakpoint it stretches across the page, and then it is shown correctly again with the margins on the sides.
See screenshots below.
Expected result
The banner should preserve margins on all breakpoints.

Replaced by #404

authors: DiogoSoaress TanyaEfremova

repo: safe-global/safe-homepage


text:
Set up automatic deployment of documentation with each push to main.

title.

I needed to change several workflow files before merging to main, because I worried things would break if trying to merge each change individually. Should be good to go now, fingers crossed.

silly me...

repo: safeliquids/cap


text:
🛑 x-crx-prod is down

In 3e9e751, x-crx-prod ($SECRET_SITE_CPS_PROD) was down:

HTTP code: 404
Response time: 803 ms

updated monitoring URL https://cps-prod.sage-iq.com/api/system/operations-check

repo: sage-iq/upptime


text:
Use Electron Forge for Packaging

Use Electron Force for packaging the electron app.

git fetch origin
git checkout 12-use-electron-forge-for-packaging


text:
🛑 Advance Dye Chem is down

In 16ce030, Advance Dye Chem (https://advancedyechem.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Advance Dye Chem is back up in 666b4f3 after 2 minutes.

repo: sahajananddigital/status


text:
Theorem Environments across multiple pages

Does the package currently support having theorems span across a page?
Currently whenever this happens it just moves the entire theorem box to the next page leaving a huge blank space on the current page.

Add breakable: true to thmbox. thmplain is already breakable.

If you're using Typst 0.12, you may be affected by a recent change to figure show rules, so you may have to use my PR's branch in the meantime: https://github.com/sahasatvik/typst-theorems/pull/39

I'm using the online app. Setting breakable: true didn't resolve the issue. I assume this is because of @PgBiel comment?
Is there a way to use "PR's branch" through the web app version?

Is there a way to use "PR's branch" through the web app version?

Copy the following file to your project, and replace #import "@preview/ctheorems:version" with #import "theorems.typ" (adjusted to the path where you save the file): https://raw.githubusercontent.com/sahasatvik/typst-theorems/2e506e3ae25e79d4931da79f1a979022ee860e72/theorems.typ

@PgBiel that did the trick. Thanks! Hopefully that branch gets merged soon!

authors: FlandiaYingman PgBiel balltar

repo: sahasatvik/typst-theorems


text:
🛑 Philosophie.ch is down

In 533a54f, Philosophie.ch (https://www.philosophie.ch) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Philosophie.ch is back up in 66b5fcf.


text:
🛑 FAIRMED Schweiz is down

In 479c3a4, FAIRMED Schweiz (https://www.fairmed.ch) was down:

HTTP code: 521
Response time: 159 ms

Resolved: FAIRMED Schweiz is back up in 12c3dd0.


text:
🛑 Philosophie.ch is down

In 6611151, Philosophie.ch (https://www.philosophie.ch) was down:

HTTP code: 500
Response time: 2104 ms

Resolved: Philosophie.ch is back up in b420ca1 after 1 hour, 2 minutes.


text:
Metadata: parse new names

Implements parsing new tags

PackageName  || Title
PackagerName || PackagedBy
Icon         || PackageIcon
Url          || Links

See https://github.com/sailfishos-chum/main/issues/100
As the implementor I have taken the liberty of supporting PackagedBy as well, because I like it.

Thank you very much, LGTM

@nephros, unfortunately this change fails to compile:
chum-gui-0.6.0_compiling-fails.txt
Can you please take a look at it.

Damn, missing closing bracket.

… which I failed to see (despite being trivial) due to being overly tired when I detected that building fails.

Sorry about that.

Never mind.  It uncovered another issues: The CI runs at GitHub show success, even though compiling fails!  I have to improve the workflow definition(s).

Fixes coming up!

Thank you for PR #185.  Merged and compiling, as expected.

authors: Olf0 nephros rinigus

repo: sailfishos-chum/sailfishos-chum-gui


text:
Adding trigonometric calculator

I would like to add a calculator for finding sin, cos, tan, cosec, sec, cot value when angle in degree is given.
Please assign this issue to me @sairish2001

it's already there in Calculator


text:
Dark mode in contact section

I want to add dark/light mode in contact section.
[GSSOC'21]
Please assign me this issue @sairish2001

@sairish2001 Please assign me this issue

Go ahead
Deadline 10 May,2021


text:
Geting error using Cysco Anyconnet

Hi, I'm taking this errors on log, when I connect to my corporate VPN using Cysco AnyConnect. Does anyone already faced the same problem?
check: ❌ nslookup fail for example.com AAAA using 8.8.8.8
ping: bad address 'example.com'
check: ➖ ping fail to IPv6 external host (example.com)
ssl_client: example.com: certificate verification failed: unable to get local issuer certificate
wget: error getting response: Connection reset by peer
check: ❌ wget fail for https://example.com

When wsl-vpn-kit is activated:
instantly...

When wsl-vpn-kit is deactivated:
a few seconds without nothing and then...

I already deactivated the auto-generated resolv.conf. Now, its hard coded, with dns from google and the corporate dns I need for work.
WSL2 - Using Arch linux
Cysco Anyconnect  4.10.05095

Have you tried using the wsl-vpnkit with the auto-generated resolv.conf or 192.168.67.1?

@sakai135 with or without wsl-vpnkit running?

VPN - ON
wsl-vpnkit - OFF

With wsl-vpnkit running. VPN on, wsl-vpnkit on.

@sakai135 however, I can't ping www.uol.com.br for instance.

@sakai135 however, I can't ping www.uol.com.br for instance.

did you ping www.uol.com.br or ping 200.147.3.157
Also, is ICMP (reply) allowed from that host? does the ping work from the host using Powershell for example?

Closing due to inactivity


text:
S2U-42 SAK-49271 Card Game: Do not require an answer

This addresses SAK-49271 for S2U-42

Thanks a lot @stetsche

authors: mpellicer stetsche

repo: sakaiproject/sakai


text:
Add Basic Testing to use with CircleCI

Add some basic flask testing modules to ensure that at the very least the latest build boots up.

Added, circle cml also added. Closing.

repo: sakshaat/noclick


text:
Support Default Values

Some of the types might provide default values and hence should be automatically initialized. The point here is to provide user controllable facilities to define default values. Maybe use Mixins?
Default values may take two forms:

fixed values - just a compile time specified value that will be used to initialize
dependent values - when another object of same underlying type is present it can be used to default initialize

Or maybe something more generic like value mapping?

repo: sal-vage/d-domain


text:
[WIP] AI custom cards

Added interface for custom card renderer
Added MessageRenderer implementation for messages with HTML-based metadata
Added logic for handling messages with metadata as regular operator message in case when metadata can't be handled

@EgorovEI please check if the SDK is building well before the merge.

authors: EgorovEI dukhovnyi

repo: salemove/ios-sdk-widgets


text:
Use secure download endpoint for secure messaging

Use dedicated endpoint for downloading files in secure messaging instead of the one that is currently used for engagement.
MOB-1994

!squash

!merge


text:
Update exportApi.ts

What does this PR do?
Removes the string mutation that is changing the case of any IDs that may be in a query filter.
It then uses regex to see if the query starts with "select" (ignoring case).
What issues does this PR fix or reference?
Should resolve bug related to W-8827929 - https://github.com/forcedotcom/cli/issues/828

@amphro this is the first time I've tried to test Javascript. Please review this accordingly. I'm always looking to improve so any feedback at all will be happily accepted.

@robertStrunk Appears the check failures are lint errors.
From the repository root directory run yarn test to see the errors locally.

@peternhale  Thanks! I have worked through the errors with the exception of one. In the data\packages\plugin-data\test\queryFields.test.ts file it is trying to import a module from a non-existent directory data\packages\plugin-data\lib\commands\force\data\soql\query. since this is existing code I feel like there was some local command I failed to run to generate that directory. Any ideas?

@robert-strunk, I tried this branch locally and did not see the error regarding a missing file.
Try running yarn run prepack and then yarn run test to see if that resolves the issue.

That command just gives me a slew of errors. Unfortunately I don't have time to figure all this out so delete this pull request if you like.

@robert-strunk, I took your changes and cleaned up the issues. PR #35 is up for review.
Thank you for the contribution and I will be closing this PR.

Very much appreciated! New to this model of development, a bit overwhelmed with it all.
From: peternhale notifications@github.com
Sent: Thursday, February 4, 2021 3:35 PM
To: salesforcecli/data data@noreply.github.com
Cc: Strunk, Robert robert.strunk@atginfo.com; Mention mention@noreply.github.com
Subject: Re: [salesforcecli/data] Update exportApi.ts (#23)
@robert-strunkhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frobert-strunk&data=04|01|robert.strunk%40atginfo.com|189b49789b1843ddbc8008d8c94c4cde|c4b35b1471064585bac4d5031acd598f|0|0|637480676873084924|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=O7TZGjGoVsARenxVD0XpjYsRw%2Be9feTv9mxZTIGUwKk%3D&reserved=0, I took your changes and cleaned up the issues. PR #35https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsalesforcecli%2Fdata%2Fpull%2F35&data=04|01|robert.strunk%40atginfo.com|189b49789b1843ddbc8008d8c94c4cde|c4b35b1471064585bac4d5031acd598f|0|0|637480676873084924|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=THqui2CkYC9g2hJyGplQGOr%2BpFTMhY3b8agJ7UBeXHI%3D&reserved=0 is up for review.
Thank you for the contribution and I will be closing this PR.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsalesforcecli%2Fdata%2Fpull%2F23%23issuecomment-773587256&data=04|01|robert.strunk%40atginfo.com|189b49789b1843ddbc8008d8c94c4cde|c4b35b1471064585bac4d5031acd598f|0|0|637480676873094914|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Ag3hbEo9y7H7EQul933s9DqYbdL%2BZNG4nsDn7uq06qk%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALLPXWR2RREDTAQV7ZOPFXTS5MAGDANCNFSM4WZ4GPTA&data=04|01|robert.strunk%40atginfo.com|189b49789b1843ddbc8008d8c94c4cde|c4b35b1471064585bac4d5031acd598f|0|0|637480676873094914|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=H2yXkTWeN%2Bvdbfiq182H2U%2BcM3CWMbxKBiipGmQxgKU%3D&reserved=0.

@robert-strunk when you have a free moment it would be nice to hear about your struggles in this new model of development. If possible list the tools that you are using and any documentation/readme, etc that you found useful or found not so useful.

authors: peternhale robert-strunk robertStrunk

repo: salesforcecli/data


text:
Only one (main) LWC folder is being watched

We have split up our codebase into several separate directories:

src/main/default/lwc
src/main/core/lwc
src/main/customer360/lwc
src/main/cpq/lwc
etc.

However, only when modifying LWC's in the first of these directories (src/main/default/lwc), I get a message like:
[LWC Dev Server] File 'c/accountIcons/accountIcons.html' modified - updating.

Any changes to LWCs in the other directories are being ignored.

@jverelst Please attach the contents of your sfdx-project.json to the issue description.

authors: jverelst ravijayaramappa

repo: salesforcecli/plugin-lightning-dev


text:
Improve exception handling for amazon errors

Which API - Endpoint is your request about: any endpoints
Traceback:
  File "/opt/venv/lib/python3.9/site-packages/sp_api/api/orders/orders.py", line 204, in get_order_buyer_info
    return self._request(fill_query_params(kwargs.pop('path'), order_id), params={**kwargs})
  File "/opt/venv/lib/python3.9/site-packages/sp_api/base/client.py", line 125, in _request
    return self._check_response(res)
  File "/opt/venv/lib/python3.9/site-packages/sp_api/base/client.py", line 134, in _check_response
    js = res.json() or {}
  File "/opt/venv/lib/python3.9/site-packages/requests/models.py", line 917, in json
    raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: [Errno Expecting value] : 0

The exception message is not helpful. It would be nice to see the the response and/or the response code.
Additional context
It is reproduceable if amazon doesn't response with the expected json. For example if amazon responses with <html>\r\n<head><title>502 Bad Gateway</title></head>

Sounds good! I think it's pretty hard to give more output here, since the error usually is a result of an illegal request. Do you have a good idea how to improve the message?

Maybe this updates at sp_api/base/client.py:_check_response() will be enough:
    def _check_response(self, res) -> ApiResponse:
        try:
            if self.method == 'DELETE' and 200 <= res.status_code < 300:
                try:
                    js = res.json() or {}
                except JSONDecodeError:
                    js = {'status_code': res.status_code}
            else:
                js = res.json() or {}
            if isinstance(js, list):
                js = js[0]
            error = js.get('errors', None)
        except Exception as exc:
            error = [{'message': '%s: %s: %s' % (type(exc).__name__, str(exc),
                                                 str(res.content))}]

        if error:
            exception = get_exception_for_code(res.status_code)
            raise exception(error, headers=res.headers)
        return ApiResponse(**js, headers=res.headers)

?

authors: braeutigamj saleweaver

repo: saleweaver/python-amazon-sp-api


text:
Add feed types

Adding similar thing as reportTypes.py but for feedTypes
List pulled from here
https://github.com/amzn/selling-partner-api-docs/blob/main/references/feeds-api/feedtype-values.md

Nice, thanks!

authors: abrihter saleweaver


text:
🛑 SCB - svensk-utbildningsnomenklatur-sun is down

In 0a386cd, SCB - svensk-utbildningsnomenklatur-sun (https://www.scb.se/dokumentation/klassifikationer-och-standarder/svensk-utbildningsnomenklatur-sun/) was down:

HTTP code: 503
Response time: 1397 ms

Resolved: SCB - svensk-utbildningsnomenklatur-sun is back up in a8166ac after 1 hour, 46 minutes.


text:
Clicking on links should use user's default browser

Currently any links will open in a new window under the Soundcleod app, except for soundcloud links which just use the open window (which should be the case).
Previous behaviour was that links would open in the default browser which is handy for links like youtube/facebook where the user may already be logged in.

+1 🙏

Fixed in 1.1.0

authors: salomvary sammarcus sunmockyang

repo: salomvary/soundcleod


text:
🛑 Blog is down

In 4bc59bf, Blog (https://saltbo.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Blog is back up in bfdc6b0 after 5 minutes.

repo: saltbo/status


text:
🛑 Blog is down

In 5b3ac57, Blog (https://saltbo.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Blog is back up in 8478b26 after 8 minutes.


text:
feat(plasma-temple): update getImageProps slider args

Исправил getImageProps

:baby_chick: Download canary assets:
colors--canary.450.4543778101.xml
color_metro_ios-swift--canary.450.4543778101.swift
color_metro_kotlin--canary.450.4543778101.kt
color_metro_react-native--canary.450.4543778101.ts
color_sberHealth_ios-swift--canary.450.4543778101.swift
color_sberHealth_kotlin--canary.450.4543778101.kt
color_sberHealth_react-native--canary.450.4543778101.ts
color_sbermarket_ios-swift--canary.450.4543778101.swift
color_sbermarket_kotlin--canary.450.4543778101.kt
color_sbermarket_react-native--canary.450.4543778101.ts
color_sberprime_ios-swift--canary.450.4543778101.swift
color_sberprime_kotlin--canary.450.4543778101.kt
color_sberprime_react-native--canary.450.4543778101.ts
color_selgros_ios-swift--canary.450.4543778101.swift
color_selgros_kotlin--canary.450.4543778101.kt
color_selgros_react-native--canary.450.4543778101.ts
color_smbusiness_ios-swift--canary.450.4543778101.swift
color_smbusiness_kotlin--canary.450.4543778101.kt
color_smbusiness_react-native--canary.450.4543778101.ts
PlasmaTokensColor--canary.450.4543778101.swift
shadow_sbermarket_react-native--canary.450.4543778101.ts
typo_mage_ios-swift--canary.450.4543778101.swift
typo_mage_kotlin--canary.450.4543778101.kt
typo_mage_react-native--canary.450.4543778101.ts
typo_plasma_ios-swift--canary.450.4543778101.swift
typo_plasma_kotlin--canary.450.4543778101.kt
typo_plasma_react-native--canary.450.4543778101.ts
typo_ruler_ios-swift--canary.450.4543778101.swift
typo_ruler_kotlin--canary.450.4543778101.kt
typo_ruler_react-native--canary.450.4543778101.ts
typo_sage_ios-swift--canary.450.4543778101.swift
typo_sage_kotlin--canary.450.4543778101.kt
typo_sage_react-native--canary.450.4543778101.ts
typo_sbermarket_ios-swift--canary.450.4543778101.swift
typo_sbermarket_kotlin--canary.450.4543778101.kt
typo_sbermarket_react-native--canary.450.4543778101.ts
typo_soulmate_ios-swift--canary.450.4543778101.swift
typo_soulmate_kotlin--canary.450.4543778101.kt
typo_soulmate_react-native--canary.450.4543778101.ts

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install @salutejs/plasma-temple@1.146.0-canary.450.4543778101.0
# or
yarn add @salutejs/plasma-temple@1.146.0-canary.450.4543778101.0

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-450/

Component performance testing
Result: 🟢 Success
Check out report in job artifacts!

authors: Salute-Eva shirinovIldar

repo: salute-developers/plasma


text:
Separate FMX from VCL code

Separated the FMX from the VCL run-time package so VCL deployment does not require FMX.  Unfortunately the same is not true in reverse.

GitHub is asking to resolve conflicts so I downloaded your branch and merged the changes manually.
Thank you very much Larry!

authors: lhengen salvadordf


text:
Test Cases Failing : 2 suites resolved

Two suites of test cases which check header and body of homepage, resolved. While the rest are still failing

2 Test cases resolved which were failing due to no id associated with the HTML components. Added IDs to the respective components being checked


text:
Fix prepend logic in Logger's static methods

Hello,
This PR fix a bug in Logger's static methods that result in the messages being printed twice:

With the following changes:

Thank you :)

authors: HeavenVolkoff JumpLink

repo: sammydre/ts-for-gir


text:
Support for collections

Hi there,
Does this plugin supports collections?

It doesn't sorry. You can see the code, it's very simple: https://github.com/samrayner/jekyll-asset-path-plugin/blob/master/asset_path_tag.rb

authors: iloveip samrayner

repo: samrayner/jekyll-asset-path-plugin


text:
Merge pull request #1 from samshadwell/master

Merge

Ooops, sorry!

repo: samshadwell/TrumpScript


text:
Dryrun tags bug fixing

Should merge after #492 merged into master.
Changing 'dryrun' -> 'config_dryrun' will cause conflicts and bugs

I re-change 'config_dryrun' to 'dryrun'. Let's discuss about it then go!

Well, it does look good, but dryrun does not work, so somehow the logic is failing.

@joejulian there is some error on here which is very weird to me. I'm working on it.
- name: Wait for api server
  wait_for:
    host: "{{ item | regex_replace('https://','') }}"
    port: 443
    timeout: 600
  with_items: "{{ api_servers }}"
  vars:
    kubefn: "{{ config_base | expanduser }}/{{ cluster.name }}/admin.kubeconfig"
    kubeconfig: "{{ kubefn | is_file | ternary( kubefn, '/dev/null' ) }}"
    api_servers: "{{ lookup('file', kubeconfig) | from_yaml | json_query('clusters[*].cluster.server') }}"
  when: not ( dryrun | bool )

when we run this with dryrun admin.kubeconfig file is not generated for intention.
However, even if dryrun tag is set, they check the existency of admin.kubeconfig file


text:
Android: Add 'share' as action on notifications

Actions for Button1/2/3

Mark Read
Save
Share
none/disable

screenshots source: QKSMS

Currently we've only SAVE & MARK READ options which are fixed buttons.
This Feature will give users bit more freedom/control through notifications.

I'm not entirely sure what you're asking for here. Can you offer a bit of clarity? I'd be happy to think about adding controls somewhere.

Currently we've only SAVE & MARK READ options which are fixed buttons.

check screenshot. (no1 & no2)

FR for controlling what these buttons should do.
Add this feature to Settings > Notifications > Actions
Options for action buttons:
Button 1

Mark Read
Save
Share
none/disable

Button 2

Mark Read
Save
Share
none/disable

Button 3

Mark Read
Save
Share
none/disable

We can add Share, but I see no reason to add configuration for order.

Launching as v12.1.0.

repo: samuelclay/NewsBlur


text:
Improve generic subclass support

Change Summary

Add parameterised subclasses to __bases__ when constructing new parameterised classes, so that A <: B => A[int] <: B[int].
This helps to facilitate a use case based on abstract classes, and leads to less unexpected behaviour when comparing between concrete versions of classes.
Related issue number

fix #2007
Checklist

[x] Unit tests for the changes exist
[ ] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

test fastAPI is failling with:
ImportError: cannot import name 'RowProxy' from 'sqlalchemy.engine.result' (/opt/hostedtoolcache/Python/3.7.10/x64/lib/python3.7/site-packages/sqlalchemy/engine/result.py
As far as I can tell that's not anything I could've incidentally broken.  I'm not sure what the best way to proceed with it would be?

@diabolo-dan Don't worry you can have a rest for the CI! ;)
It's due to fastapi tests that uses databases without pinning sqlalchemy dependency.
I already submitted a fix https://github.com/encode/databases/pull/299 for that

I notice that there was significant generic implementation done by @dmontagu , including the line:
    assert concrete_model.__name__ == 'Model[int, BT][str]'

Which is I believe the only concrete claim about the behaviour of reapplication of partially parameterised generic models. (namely extending from the former).
This behaviour adds complexity to establishing parameterised bases, and makes for less  (because a concrete type could be constructed through arbitrary many type variables).  I also think it's less intuitive than always building from the base, (so that Model[int, BT][str] is Model[int, str]).  The alternative isn't perfect, because there's still the issue of checking issubclass(Model[int, BT][str], Model[int, AT]) which for various assumptions on the TypeVars, should ideally hold, but I don't think it's possible to achieve that (at least through setting __bases__).
I'm just wondering if there was a particular reason for implementing it this way, or if it was just the simplest thing that met the requirements at the time.

please update.

please review.

great, thank you.

Just a note for anyone watching this PR, this changes here I think have caused a memory build up, see #3829.
To mitigate this, I've implemented (and will soon merge) #4083 which limits the size of _generic_types_cache and _assigned_parameters_limit to 1000. These configured by settings generics._generic_types_cache_limit and generics._assigned_parameters_limit.
Feedback on the PR welcome, but in order to include this fix in v1.9.1 I won't being waiting for feedback before merging - any further changes would need to be in another PR.

authors: PrettyWood diabolo-dan samuelcolvin

repo: samuelcolvin/pydantic


text:
chore(main): release 0.23.0

:robot: I have created a release beep boop
0.23.0 (2023-03-04)
Features

. (a246c3a)
enhance github action (9dede25)
enhance github action (2353b84)
enhance release action (83c2163)
enhance release action (93e3312)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/samuele-cozzi/obsidian-marp-slides/releases/tag/0.23.0 :sunflower:

repo: samuele-cozzi/obsidian-marp-slides


text:
Atom for All

Everything should have an atom feed.

Site wide
Board wide
Thread wide

Everything except site-wide atom feed has been created in this commit: 6ea028d08af7aec4151323a94a9fa84af666af4d
I'm not sure if a site-wide feed is a great idea, doesn't seem that useful.


text:
Custom Domain Question

I'm setting the CacheDomainName parameter when deploying the CloudFront-Enabled version of 4.1.1.  DNS CNAME records are set to the same custom domain.  This all works as expected.  The service can be invoked with the custom domain the data in the info.json responses look great, with the exception of the @id field which includes the lambda domain rather than my custom domain.  I had expected that to be replaced with the value entered for CacheDomainName.  Is it possible to configure the service to include the custom domain in @id field?

Thank you for reporting this. I think this has come up before, but I can't remember exactly how it played out. We're using a cloudfront-enabled instance and the @ids are looking like they should, so I think there must be some kind of configuration glitch. (It's not necessarily on your end – we use a customized deploy script and may have done something somewhere alone the line that the SAR click-to-deploy version doesn't.) Can you give me some details about your configuration and what you're seeing?

Thanks for the quick reply.  What would be helpful to know about my setup?
I'm using the CloudFront-Enabled deploy script from an unmodified version of serverless-iiif repo that I forked earlier today.  I'm just setting 2 parameters, the CacheDomainName and the SourceBucket.  For the CacheDomainName I'm setting the value to iiif-image.juncture-digital.org.
After the deploy completed I updated the CloudFront distribution config with the same custom domain name (using the Alternate domain name (CNAME)) field and pointed to the associated custom SSL certificate.  I'm using the Google Domains for DNS hosting, so I also needed to add the generated CloudFront ID to a CNAME record there.

@rsnyder I think I understand now. Open up the lambda function in the AWS console and check its environment variables (under the Configuration tab). There should be a forceHost variable set to the custom domain that you want your IDs to use. This is usually set during deploy, but if you updated the CloudFront distribution's CNAME after the fact, that wouldn't have happened.

Thanks for this update.  After looking at the code (and some trial-and-error) that is what I arrived at too.  Thanks for confirming this was the correct resolution.  And, thanks for developing/supporting this great package.  It really simplifies the deployment of an IIIF image service.
Ron
From: Michael B. Klein @.>
Date: Tuesday, December 13, 2022 at 2:49 PM
To: samvera/serverless-iiif @.>
Cc: Ronald Snyder @.>, Mention @.>
Subject: Re: [samvera/serverless-iiif] Custom Domain Question (Issue #89)
Caution: This message did not originate from within ITHAKA's email system. Please use caution when opening attachments and following links within this message.
@rsnyderhttps://github.com/rsnyder I think I understand now. Open up the lambda function in the AWS console and check its environment variables (under the Configuration tab). There should be a forceHost variable set to the custom domain that you want your IDs to use. This is usually set during deploy, but if you updated the CloudFront distribution's CNAME after the fact, that wouldn't have happened.
—
Reply to this email directly, view it on GitHubhttps://github.com/samvera/serverless-iiif/issues/89#issuecomment-1349602091, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAEFEYCOENPADA4ZQEHTZYLWNDHNHANCNFSM6AAAAAASE5R36U.
You are receiving this because you were mentioned.Message ID: @.***>

authors: mbklein rsnyder

repo: samvera/serverless-iiif


text:
[bugfix] Prevent is-rfc268-test to be treated as a test

From Slack:

is-rfc268-test.js:4 Uncaught TypeError: Object.defineProperty called on non-object

so this happens with 1.15 betas only when trying to import useNativeEvents from the ember-cli-page-object/extend.
I don't fully understand the root cause of the issue, but here are my observations:

extend/index.js depends on -private/execution_context
which depends on -private/is-rfc268-test which causes an issue acording to error message
Somehow when -private/is-rfc268-test is referenced via this depency chain out of the test execution context(for example in the tests/test-helper.js) we get an error above. if I rename the -private/is-rfc268-test to avoid the "-test.js" suffix an error dissapears.

It could possible fix the other imports issues I have heard about earlier..
I think there are pretty low chances to test it on CI cause we need an external app/addon to include ember-cli-page-object for that.

Coverage remained the same at 98.763% when pulling 3b872fba1ad3c710389c9d223dd180fac5c58b81 on is-rfc268--test into aaec068aa9a8c4faba810af04d8644ea968c5669 on master.

Any chance of getting a new release? Would be great :)

@mydea thanks for heads up! Going to make new beta release early this week.

authors: coveralls mydea ro0gr


text:
MicroBitLightSensor

This is not really an issue... but I am just curious...
I know that the microbit doesn't have a default light sensor, but it uses a trick to get that value:
https://lancaster-university.github.io/microbit-docs/extras/light-sensing/
Is it possible with node.js?

It is if you're prepared to do some coding on the micro:bit itself using its C/C++ APIs. Per the page you linked to, you could read the light sensor periodically and each time you obtain a value, package it in a MicroBitEvent object with a ID of your choosing and the light sensor reading in the event' value part. Then have your node.js code subscribe to your chosen event ID and the "ANY" value wildcard and you should receive events in your node.js code, with the light sensor reading packaged in it.

@smartyw thanks for answering!
@MatthijsKamstra the answer above be @smartyw looks good to me, so closing this.

authors: MatthijsKamstra sandeepmistry smartyw

repo: sandeepmistry/node-bbc-microbit


text:
Is this compatble?

Hey sandeep,
Would this module based on SX1276 chip work with your library?
https://www.aliexpress.com/item/1005002115974180.html?spm=a2g0o.store_pc_groupList.8148356.61.1b0d6ccfcQ9oPl
Thanks.

Hi @happytm,
I haven't tried that module myself, but from the link you shared it should be compatible with this library.
Feel free to close this issue if your questions is answered.

Thank you Sandeep.

authors: happytm sandeepmistry

repo: sandeepmistry/pico-lorawan


text:
Installation Failed: Expected double-quoted property name in JSON at position 768

Can't install 0.7.
0.6.2 install works fine but can't update.
Foundry v10.291

Fixed. Please try again.

authors: niuserre sanguaire

repo: sanguaire/fast-dice-box


text:
学园交流和悬赏通缉有点问题

学园交流和悬赏通缉有点问题..我配置的时每个区域刷5次,但是脚本执行了第一个5次后,就提示没有票了,跳过了后两个.想了一下可能是把10识别成了0,我开了大小月卡有15张票

已于 df3f911 修复，如还有问题请再次反馈，谢谢

新版本还在测试中，请到群内下载测试版

版本已发布，issue关闭


text:
OutOfMemoryError on nexus 6 video

Hello.
I added mp4parser 1.9.27 as gradle dependency.
I'm trying to build a movie
MovieCreator.build(filePath)
OOM occurs only on videos, which were captured on device.
I debugged method parse of AbstractBoxParser.
size/type:

24/ftyp
1527/moov
108/mhvd
121/meta
1751411826/��������

This is video.
Do you have any suggestions? Maybe, I can help with something else?
Thank you.
Stack trace:
java.lang.OutOfMemoryError: Failed to allocate a 1751411837 byte allocation with 16766280 free bytes and 484MB until OOM
at dalvik.system.VMRuntime.newNonMovableArray(Native Method)
at java.nio.DirectByteBuffer$MemoryRef.(DirectByteBuffer.java:58)
at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:240)
at org.mp4parser.support.AbstractBox.parse(AbstractBox.java:95)
at org.mp4parser.AbstractBoxParser.parseBox(AbstractBoxParser.java:107)
at org.mp4parser.BasicContainer.initContainer(BasicContainer.java:107)
at org.mp4parser.boxes.iso14496.part12.MetaBox.parse(MetaBox.java:82)
at org.mp4parser.AbstractBoxParser.parseBox(AbstractBoxParser.java:107)
at org.mp4parser.BasicContainer.initContainer(BasicContainer.java:107)
at org.mp4parser.support.AbstractContainerBox.parse(AbstractContainerBox.java:75)
at org.mp4parser.AbstractBoxParser.parseBox(AbstractBoxParser.java:107)
at org.mp4parser.BasicContainer.initContainer(BasicContainer.java:107)
at org.mp4parser.IsoFile.(IsoFile.java:55)
at org.mp4parser.IsoFile.(IsoFile.java:50)
at org.mp4parser.muxer.container.mp4.MovieCreator.build(MovieCreator.java:54)
at org.mp4parser.muxer.container.mp4.MovieCreator.build(MovieCreator.java:39)

With help of debugging, if I rewind header before parsing type - it displays that type is 'hdlr'

Same problem here!

Same. Version 1.1.7 works

Thank you @whiteLT your comment save my time

authors: Artem-dsi OrangeDynamic Pretorian1 whiteLT


text:
NoSuchElementException

I followed your code, but get this error and have no idea with it.
    File mFile = new File(FILE_PATH);

    /**TODO
     * Define Orientation of image in here,
     * if in portrait mode, use value = 90,
     * if in landscape mode, use value = 0
     */
    IsoFile isoFile = null;
    try {
        Movie movie = new Movie();

        isoFile = new IsoFile(mFile.getAbsolutePath());

        Log.i("", "isoFile " + isoFile);
        Log.i("", "movie " + movie);

        // ERROR IN THIS LINE
        Container out = new DefaultMp4Builder().build(movie);
        isoFile.getMovieBox().getMovieHeaderBox().setMatrix(com.googlecode.mp4parser.util.Matrix.ROTATE_180);

        FileChannel fc = new FileOutputStream(new File(FILE_PATH)).getChannel();
        out.writeContainer(fc);
        fc.close();
    } catch (IOException e) {
        e.printStackTrace();
    }

Please take a look and tell me how to fix.
Thank you.

What version are you using? Would you please try to use the latest release 1.0.6? It's here: https://oss.sonatype.org/content/repositories/comgooglecodemp4parser-1060
This version will also be on maven central in a day or two.
1.) I don't debug old versions - that just doesn't make any sense for me.
2.) without knowing the version I cannot find the code that's failing at all.

authors: huytower sannies


text:
Mantaray Install Issues - Ubuntu 16.04.2

Any updates that allow Mantaray to run on Ubuntu 16.04.2?
I Installed SIFT no problem by doing the following:
Go to the Latest Releases
Download all the release files
sift-cli-linux
sift-cli-linux.sha256.asc
Import the PGP Key - gpg --keyserver pgp.mit.edu --recv-keys 22598A94
Validate the signature gpg --verify sift-cli-linux.sha256.asc
Validate SHA256 signature sha -a 256 -c sift-cli-linux.sha256.asc
You'll see an error about improperly formatted lines, it can be ignored so long as you see sift-cli linux: OK before it
Move the file to mv sift-cli-linux /usr/local/bin/sift
Run chmod 755 /usr/local/bin/sift
Type sift --help to see its usage
I then followed the MantaRay Install Instructions and had the following errors:
sudo add-apt-repository ppa:mantaray/stable
sudo apt-get update
PPA:
$ sudo apt-add-repository ppa:mantaray/stable
$ sudo apt-add-repository ppa:sift/stable
$ sudo apt-get update && sudo apt-get upgrade -y
Error:
W: The repository 'https://apt.dockerproject.org/repo ubuntu-xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://ppa.launchpad.net/mantaray/stable/ubuntu xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://repo.saltstack.com/apt/ubuntu/16.04/amd64/latest/dists/xenial/main/dists/xenial/main/binary-amd64/Packages 404 Not Found [IP: ]
E: Failed to fetch https://apt.dockerproject.org/repo/dists/ubuntu-xenial/main/binary-i386/Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
E: Failed to fetch http://ppa.launchpad.net/mantaray/stable/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found [IP: ]
E: Some index files failed to download. They have been ignored, or old ones used instead.
$ sudo apt-get install mantaray
Error:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package mantaray
Source from PPA:
$ sudo apt-add-repository ppa:mantaray/stable
$ apt-get source mantaray
Error:
$ apt-get source mantaray
Reading package lists... Done
E: You must put some 'source' URIs in your sources.list
$
GitHub:
$ git clone https://github.com/mantarayforensics/mantaray.git
$ cd mantaray
$ git clone https://github.com/mantarayforensics/mantaray.git
fatal: destination path 'mantaray' already exists and is not an empty directory.
$ cd mantaray
bash: cd: mantaray: Not a directory
$ sudo mantaray
sudo: mantaray: command not found
Thank you

Mantaray has not been updated to support Ubuntu 16.04 xenial, therefore it will not install.
I believe Mantaray is no longer being actively maintained

authors: ekristen mformal

repo: sans-dfir/sift


text:
remove package.json

we dont use (need or want!) this.

Haha. Love this!

authors: Mikcl sansyrox

repo: sansyrox/starfyre


text:
switch use of FORMATTER_DICT to PROMPT_FIELDS

the use of PROMPT_FIELDS prints a DeprecationWarning to the shell each time the user hits .
Example:
~   master *  repos  xonsh                                                                                2.2m  Sun  8 Jan 13:41:06 2017
PendingDeprecationWarning: FORMATTER_DICT is an alias of PROMPT_FIELDS and will be removed in the next release
PendingDeprecationWarning: FORMATTER_DICT is an alias of PROMPT_FIELDS and will be removed in the next release

This is a duplicate of https://github.com/santagada/xontrib-powerline/pull/2

Thanks for helping but the fix was already waiting to be merged in PR #2

authors: dcwild moigagoo santagada

repo: santagada/xontrib-powerline


text:
"items" can be a bool in 2020

see the Closed tuple example in the 2020 release notes https://json-schema.org/draft/2020-12/release-notes.html
{
  "prefixItems": [
    { "$ref": "#/$defs/foo" },
    { "$ref": "#/$defs/bar" }
  ],
  "items": false
}

Also, thanks for the awesome package.
In addition to the functionality your package provides, I need to be able to simply marshal/unmarshal into json/yaml. That alone has been a nontrivial lift. My point is, much respect for getting compilation/validation working!

yes. in 2020 release, items can take boolean value.
but in 2020 release, boolean value is a valid schema.
so in 2020 release, items is compiled into boolean schema if it is boolean.
to be precise:
{ "items": false }

compiles into:
&Schema{
    Items2020: &Schema{ Always: &false },
}

similarly:
{ "items": true }

compiles into:
&Schema{
    Items2020: &Schema{ Always: &true },
}

Aaaahh, thank you! Sorry for the erroneous ticket!

It's fine. Not an issue

authors: chanced santhosh-tekuri

repo: santhosh-tekuri/jsonschema


text:
🛑 KEYCLOAK_URL is down

In 819e943, KEYCLOAK_URL ($KEYCLOAK_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KEYCLOAK_URL is back up in f4c36dd after 20 minutes.

repo: santomaharaj/upp


text:
Shapes & schemas

work in progress @ shapes and schemas

wip

authors: arnoweiss simantvermasap


text:
Bad things happen when there are multiple components with the same name

Basically, the page breaks because of keys here:
renderComponents() {
	let { highlightTheme, components } = this.props;

	return components.map((component) => {
		return (
			<ReactComponent highlightTheme={highlightTheme} component={component} key={component.name}/>
		);
	});
}

I think we could detect it in styleguide.loader.js and then either fix it (component #1, component #2, etc) or throw an error with some friendly message.

Or we can just append component path to key.

And later, when we add ids like I did in https://github.com/lovelybooks/react-styleguidist/commit/bb024de001526dcbd7c8befa82ab42d54357152d, shall we also use them for the navigation? (I mean relativePath)

Yeah, I think so.

repo: sapegin/react-styleguidist


text:
Implement Continuous Integration (CI) for the project

Let's try to follow the tutorial Continuous Integration (CI) Best Practices with SAP: Introduction and Navigator and implement Continuous Integration (CI) for the project.

Hi Gregor,
I will overtake this issue and we can see how far we can get here. Have some time next week to push this.
BR and nice weekend,
Alex

Build script added 713308771a5fdae96443de1071497a35de413027

Status: Build & test, creation of a DU and deploy to QA system is automated. Server side tests have to be migrated from browser based tests. For realistic QA test the production DB should be exported and imported into QA before importing the DU. That would test for any issues regarding changes in the DB schema.

authors: aloeffel gregorwolf

repo: sapmentors/SITreg


text:
Add "direction" in degrees

Hello!
It would be awesome, if you could extend the "direction" option with something like 130deg.
Thank you! :)

It may be quite complicated to implement because there is no way to to it with the native canvas API.
I keep this as a feature to add if possible because it's a good idea.

Custom directions are now available in V2.0.0 (#46), you can't express them in degrees but you have full control of the gradient direction.

authors: SebaGnich sarcadass


text:
Ionic Package Cloud Service - Error: Variable(s) missing

Ionic package cloud service
does not work with the plugin for android builds.
The error returned is :
Error: Variable(s) missing (use: --variable FABRIC_API_KEY=value --variable FABRIC_API_SECRET=value).
It may be linked to the fact that custom hooks are not run during ionic cloud builds.
But after looking at the content of the hooks it does not look like it.
Could you please confirm that the hooks only remove things from the plugin installation phase and adds the dSym and such ?
Thanks !

Hi,
same problem here (only for Android):
:compileReleaseJavaWithJavac/home/package/workspace/apps-20175d24-98/cordova/platforms/android/src/com/sarriaroman/fabric/FabricPlugin.java:142: error: cannot find symbol
						JavaScriptException ex = new JavaScriptException(data.getString(0));
						^
  symbol: class JavaScriptException
/home/package/workspace/apps-20175d24-98/cordova/platforms/android/src/com/sarriaroman/fabric/FabricPlugin.java:142: error: cannot find symbol
						JavaScriptException ex = new JavaScriptException(data.getString(0));
						                             ^
  symbol: class JavaScriptException
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
2 errors
 FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileReleaseJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Any idea ?

Related to issue #75

Solved in version 1.1.3

authors: Nightbr pvdyck sarriaroman

repo: sarriaroman/FabricPlugin


text:
Using @each directive for color array

I have a file util.scss
// 72 line below, very similar with the official documentation http://sass-lang.com/documentation/file.SASS_REFERENCE.html#each-directive
@each $color in red, blue, green, gray, white, black {
  .#{"" + $color} {
    color: $color;
  }

  .bg-#{"" + $color} {
    background-color: $color;
  }
}
...

I use node-sass(3.7.0) through gulp-sass. Print these error when compile.

events.js:141
      throw er; // Unhandled 'error' event
      ^
Error: util.scss
Error: Base-level rules cannot contain the parent-selector-referencing character '&'.

       Backtrace:
       	util.scss:72
        on line 72 of util.scss
>>   .#{"" + $color} {
   --^

    at options.error (/Users/basten/dev/web-projects/util.css/node_modules/gulp-sass/node_modules/node-sass/lib/index.js:271:32)

Sounds like you have a bug some where in your code. The error is likely due to incorrectly using & somewhere above this @each. Please confirm your code works with the offical Sass compiler. You can do this online with sassmeister.com.
You have not supplied enough working code us to reproduce this issue.

@xzyfer I try using sassmeister.com to compile my sass code, see http://www.sassmeister.com/gist/c98d2dec48b7c49d4b9343295b5e5475. It's ok.

It also works fine when using LibSass 3.3.6 as you can see sassmeister.com.
As I said earlier. The error your seeing is caused by the loop, from incorrectly using & some where that calls this this loop.

authors: bastengao xzyfer

repo: sass/node-sass