text:
Add support for edition 2021.

This adds initial support for Rust 2021, by making it behave the same as Rust 2018. It simply changes == Edition2018 to >= Edition2018. (And adds a PartialOrd implementation to Edition to make that possible.)

Thanks for this, we've triggered an early publish of the rustc-ap* crates so v697 is now available, and we should be able to proceed a bit earlier than Tue

Thanks for this, we've triggered an early publish of the rustc-ap* crates so v697 is now available, and we should be able to proceed a bit earlier than Tue

Updated.
This now fails on a change in how rustfmt formats macro arguments:
-macro foo($type_name: ident, $docs: expr) {
+macro foo($type_name:ident, $docs:expr) {

Trying to find out which rustc change caused this.

Updated.
This now fails on a change in how rustfmt formats macro arguments:
-macro foo($type_name: ident, $docs: expr) {
+macro foo($type_name:ident, $docs:expr) {

Trying to find out which rustc change caused this.

Looks like this is a bug that is now fixed by that change.
Before that change, format_snippet inside MacroBranch::rewrite would return None for that test case. After that change, it returns Some(..) with the newly formatted macro definition with the two spaces removed.

Looks like this is a bug that is now fixed by that change.
Before that change, format_snippet inside MacroBranch::rewrite would return None for that test case. After that change, it returns Some(..) with the newly formatted macro definition with the two spaces removed.

Ah, the problem was that rustfmt skipped formatting of the entire macro definition because of #[doc=$docs] inside the body, which was solved by that change in rustc_parse. See https://github.com/rust-lang/rust/pull/78837#issuecomment-753400518
I'll update the expected test output, as this seems simply a bug that is now fixed.

Ah, the problem was that rustfmt skipped formatting of the entire macro definition because of #[doc=$docs] inside the body, which was solved by that change in rustc_parse. See https://github.com/rust-lang/rust/pull/78837#issuecomment-753400518
I'll update the expected test output, as this seems simply a bug that is now fixed.

Done!

Done!

authors: calebcartwright m-ou-se

repo: rust-lang/rustfmt


text:
Prevent rustfmt from adding impl Trait definitions to types

Fixes #5086

Please let me know what additional test cases I should include!

Thanks so @ytmimi for the quick fix! This would indeed have addressed the immediate issue, but I'm going to close in favor of #5093. I'd been doing some cleanup on aliases recently so I'd started looking at this yesterday evening and want to go that direction since that addresses some things more holistically.
I'd really like to address the underlying indentation issue with ImplTrait kinds when using version Two of formatting, but have opted to continue leveraging the existing hack to avoid running into that issue on type aliases.
I suspect that issue could be a fairly tricky fix, but if you wanted to take a look at it I suspect it's either due to the usage of a suboptimal shape and/or a bug in join_bounds_inner that attempts to determine whether or not to block indent
https://github.com/rust-lang/rustfmt/blob/eee8f0419dca910187350ac38fe9694b8b7919b9/src/types.rs#L812-L825

source: gharchive/pull-request

authors: calebcartwright ytmimi

license_type: permissive

license_source: github-api


text:
implement OpAssign for Complex

Use a crate feature ("opassign")
Design choice: Use by-value forms of OpAssign and use Clone to forward the reference arguments. That matches what the other traits do (for example Add).
Design choice: The complex += complex operation needs Add, not just AddAssign. The complex += real operation can use just AddAssign. You could just use Add for both, not sure which way is preferable.

OpAssign is possibly a big break inducer higher up in num as well.
You could consider adding an extra trait like this: trait NumOpAssign: Num + AddAssign + SubAssign + .., and then use that in impl AddAssign in complex, the same way Num is used for impl Add.
That alone didn't seem like a great motivation to introduce "NumOpAssign."

Instead of a manual feature, perhaps we could use rustc_version in a build script to add --cfg opassign when supported. (version_matches(">= 1.8.0"))
Implementing these by value is acceptable to me.  Most of the time I expect Complex<T> is used with simple primitives anyway, especially floats.
The trait requirements are the tricky question, because we can never expand them without a breaking change.  For instance, in AddAssign I probably would have used += on the real and imaginary parts, ditto SubAssign, but we can never switch to that unless we include those requirements now.  Maybe we should just add those particular cases now.
I also think it will be confusing to users if opassign is allowed with a complex RHS, but not a real.  e.g. if complex_a *= real_b fails but complex_a *= Complex::from(real_b) would succeed.  It's clear why the implementation happened that way, and it would be more restrictive if we forced MulAssign in all cases, but that at least that would be consistent.  What do you think?

I would love to enable these by default with rustc-version. Not sure if it's proportionate to compile that crate too and call rustc another time. I think it's relatively lightweight, but still.
It's unfortunate to have to choose in that manner between Add and AddAssign, but I'll happily use AddAssign when it's possible.

Hmm, sorry this lingered.  We really should do a server bump already and be done with it...
Maybe I should open a devel or next branch to work on that?  With some basic expectations, like we're not rewriting the world, just making incremental changes we couldn't do without breaking API.

I was just closing all kinds of PRs in different projects that had been inactive. In general I think num must develop and evolve from version to version instead of being stagnant. Don't you think it would be permissible with some version friction in exchange for a library that gets better from version to version?

We need to figure something out, yes.  The reason I'm so conservative with it is that num was already so widely used at the time we took maintainership that I don't want to rock that boat.  With the traits especially, these are things that are more likely to show up in the public interface of other crates, which makes version bumps more painful than simple internal dependencies.
Even now num is # 12 most downloaded on crates.io, and for a little fresher info after we split crates, num-traits is # 27.  It's hard to make a clean ranking though -- it would be most useful to limit all crates to a time period for comparing most downloaded.  Anyway, I don't mention these numbers to brag, merely to gauge the potentially broad reach of breaking changes.
We should evolve, but I want to minimize the actual churn.  I hope that in most cases, folks will be able to just bump their dependency and carry on.

authors: bluss cuviper

repo: rust-num/num

license_source: bigquery


text:
ensure copied Cargo.lock is writable

If the path pointed to by XARGO_RUST_SRC contains read-only Cargo lockfiles, then xbuild fails because the copies it makes and attempts to modify are also read-only·
The patch below fixes this bug.
diff --git a/src/sysroot.rs b/src/sysroot.rs
index 1f3c8d1..422d3d0 100644
--- a/src/sysroot.rs
+++ b/src/sysroot.rs
@@ -85,10 +85,20 @@ fn build_crate(
     }

     util::write(&td.join("Cargo.toml"), &stoml)?;
-    fs::copy(lockfile, &td.join("Cargo.lock")).chain_err(||
+    let dst_file = td.join("Cargo.lock");
+    fs::copy(lockfile, &dst_file).chain_err(||
         format!("failed to copy Cargo.lock from `{}` to `{}`",
-            lockfile.display(), &td.join("Cargo.lock").display())
+            lockfile.display(), &dst_file.display())
     )?;
+    let mut perms = fs::metadata(&dst_file).chain_err(||
+        format!("failed to retrieve permissions for `{}`",
+            dst_file.display())
+    )?.permissions();
+    perms.set_readonly(false);
+    fs::set_permissions(&dst_file, perms).chain_err(||
+        format!("failed to update permissions for `{}`",
+            dst_file.display())
+    );
     util::mkdir(&td.join("src"))?;
     util::write(&td.join("src/lib.rs"), "")?;

Thanks for reporting! Could you open a pull request with this patch?

source: gharchive/issue

authors: phil-opp sbourdeauducq

repo: rust-osdev/cargo-xbuild


text:
Use new assembly syntax

This pull request updates x86_64 to use the new asm! macro. This will break older nightlies, but makes the syntax easier to read.
Fixes #164

This PR should be ready to merge. I have tested it with Blog OS and it works fine, but this does not mean that it will always work
We really need to write a full test suite for this crate. Also can I please be added to the x86_64 team phil?
cc @phil-opp

We really need to write a full test suite for this crate.

Absolutely! This would be very useful for changes like this.

Also can I please be added to the x86_64 team phil?

Done!

All of those have been fixed, feel free to merge when you want

Sorry for the late reply! The code looks good to me overall, but the double_fault_stack_overflow test seems to fail on CI:

Running: qemu-system-x86_64 -drive format=raw,file=/home/runner/work/x86_64/x86_64/testing/target/x86_64-bare-metal/debug/deps/bootimage-double_fault_stack_overflow-0254781a0bba0dab.bin -device isa-debug-exit,iobase=0xf4,iosize=0x04 -serial stdio -display none
qemu-system-x86_64: warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
qemu-system-x86_64: Trying to execute code outside RAM or ROM at 0x0000000108234489

I'm not sure what's the cause of this, but it seems like something goes wrong with the IDT or TSS loading.

I believe that's caused by the code that reloads cs, but I can't identify why. I'll do some testing today and then merge this when CI passes

@rybot666 Any updates on this?

Sorry I totally forgot about this! I'll take another look

No worries, thanks!

For some reason cargo xtest doesn't run on my machine (it can't find rust-src despite me having rust-src installed on nightly)

For some reason cargo xtest doesn't run on my machine (it can't find rust-src despite me having rust-src installed on nightly)

There was a breaking change in the Rust repository lately (change of the directory layout), so you might need to update your nightly version and/or cargo-xbuild. See the note from the cargo-xbuild readme:

Note: The latest version of cargo-xbuild supports all nightlies after 2020-07-30. If you are on an older nightly, you need to install version 0.5.35: cargo install cargo-xbuild --version 0.5.35.

If you're on a newer nightly, you need cargo-xbuild version 0.6.0.

@phil-opp @rybot666 I rebased this, implemented the missing commands, and fixed the set_cs issue.
PTAL

The updates look reasonable to me, but I didn't look at the set_cs assembly in detail. The fact that the tests pass again is a good sign though.

I disassembled the double_fault_stack_overflow test, and the code that sets cs is identical before and after this change:
movzx  ecx,WORD PTR [rax+0x48]
push   rcx
lea    rax,[rip+0x3]
push   rax
rex.W  retf
mov    rdi,rbx

So this PR (at least) didn't mess things up.

Great, thanks a lot for checking!

authors: josephlr phil-opp rybot666


text:
CI: Set -Crelocation-model=static in RUSTFLAGS for bootloader test job

In d3b9c0573800b2e888486037e09d43ffd3ffcb97, we switched our test framework to the built-in x86_64-unknown-none target. This required a -Crelocation-model=static flag to work with bootloader v0.9, which we set using a build.rustflags config key.
In 2eb838d101cdd179d6395f79f87916a48e8c1935, we set a RUSTFLAGS env variable on CI to deny warnings.
Unfortunately, the above two commits conflict because the RUSTFLAGS env variable takes precedence over the build.rustflags key. This commit fixes this by setting an explicit RUSTFLAGS value for the bootloader test job that contains both flags.
This should fix the CI build errors.

Enabling merge queues is a good idea! However, the "Bootloader Integration Test" job is not marked as required, so merge queues wouldn't have helped here.
The reason for keeping the bootloader integration test jobs optional is to avoid deadlock situations on nightly breakage. There is a circular dependency because the bootloader crate depends on x86_64, which uses bootloader again for testing. So in case of nightly breakage we need to be able to fix x86_64 first.

Ah, that makes sense. :)

authors: mkroening phil-opp


text:
Document how to link against a local, static/dynamic libpcap

Would be nice to have a vendored feature that statically link the pcaplib. Like openssl crate for example https://docs.rs/openssl/0.10.36/openssl/#vendored

Sounds convenient. PRs are welcome :)

See my latest comment on the PR:https://github.com/rust-pcap/pcap/pull/195#issuecomment-1100212171

See https://github.com/rust-pcap/pcap/pull/195#issuecomment-1100223874

Would be nice to have a vendored feature that statically link the pcaplib. Like openssl crate for example https://docs.rs/openssl/0.10.36/openssl/#vendored

I looked into what openssl does and when it's "vendored" it compiles openssl using the openssl-src crate. We won't do that. But, having thought about it, better support/documentation on how to compile against a locally compiled libpcap is worthwhile. Therefore, this issue is actually broader than #195.

As per the discussion in #195, pcap can be compiled against a static libpcap without modifying any pcap code. Therefore, there is no need to expose a new feature as we won't compile libpcap from scratch like openssl does (too much work, too little gain for a small project like this).
However, there should be some documentation in the README as to how static compiling can be achieved so this issue is getting renamed t reflect this.

Do you think we should use something like https://crates.io/crates/pcap-sys ? we make binding by manually in pcap, but don't use a more "raw" level lib.

With https://github.com/rust-pcap/pcap/pull/253, the README was sufficiently updated to provide enough information to anybody who wants to build statically. Ultimately, it's a rust compilation issue, not a pcap issue so it's up to the user to consult https://doc.rust-lang.org/cargo/reference/build-scripts.html for static linking. From pcap's point of view, they may have to set LIBPCAP_VER if the static library is not the latest version (which is assumed by default).

Having said that. If somebody is willing to put the effort into it, PRs along the line of https://doc.rust-lang.org/cargo/reference/build-scripts.html#-sys-packages are welcome.

it's impossible to statically link for windows, cause the .lib is a fake thing that just say to windows to find a dll.

here's a build.rs:
fn main() {
    #[cfg(all(unix, feature = "static"))]
    {
        let linux_kernel_headers = std::env::var("LINUX_KERNEL_HEADERS").ok();

        let mut cmake_config = cmake::Config::new("libpcap");

        if let Some(linux_kernel_headers) = linux_kernel_headers {
            cmake_config.define("DISABLE_USB", "ON");
            cmake_config.define("DISABLE_DBUS", "ON");
            cmake_config.define("DISABLE_BLUETOOTH", "ON");
            cmake_config.define("DISABLE_RDMA", "ON");
            cmake_config.define("ENABLE_REMOTE", "OFF");
            cmake_config.define("USE_STATIC_RT", "ON");
            cmake_config.define("BUILD_SHARED_LIBS", "OFF");
            cmake_config.cflag(format!("-I{}", linux_kernel_headers));
        }

        let mut dst = cmake_config.build();
        dst.push("lib");

        println!("cargo:rustc-link-search=native={}", dst.display());
        println!("cargo:rustc-link-lib=static=pcap");
    }
}

Cargo.toml:
[build-dependencies]
pkg-config = { version = "0.3", optional = true }
cc = { version = "1.0", optional = true }
cmake = { version = "0.1", optional = true }

[features]
static = ["pkg-config", "cc", "cmake"]

here's a build.rs:
fn main() {
    #[cfg(all(unix, feature = "static"))]
    {
        let linux_kernel_headers = std::env::var("LINUX_KERNEL_HEADERS").ok();
     ....
        println!("cargo:rustc-link-search=native={}", dst.display());
        println!("cargo:rustc-link-lib=static=pcap");
    }
 }

Cargo.toml:
    ....

also git submodule add https://github.com/the-tcpdump-group/libpcap.git
to put libpcap source in the root as build.rs expects this.

And what the idea about it?   What is the why?
Please consider to put the answer in a merge request.
Regards
Geert Stappers
P.S.
For those who want to click on https://github.com/the-tcpdump-group/libpcap,
here is the link https://github.com/the-tcpdump-group/libpcap  :smiley:

Hello, i'm trying to statically link against 1.5.3 (CentOS 7) version of pcap.
Libraries are present in /usr/lib64

ls /usr/lib64 | grep pcap
libpcap.so
libpcap.so.1
libpcap.so.1.5.3

My build.rs:

fn main()
{
println!("cargo:rustc-link-lib=static=pcap");
}

I'm getting /usr/bin/ld: cannot find -lpcap error every time. Tried setting both LIBPCAP_LIBDIR and LIBPCAP_VER with no effect.
Any ideas @Wojtek242 ?
Thanks

    #[cfg(all(unix, feature = "static"))]

cfg options that determine target system like cfg(unix), cfg(target_os="windows") are not supposed to be used with build scripts since it will present problems with cross compilation:

It is a mistake to use #[cfg(target_os = …)] in build.rs. This is because #[cfg] refers to the environment in which the build.rs's executable will run, which will be the host (compiler) operating system. It is not the actual compilation target system.
Build scripts have to use Cargo's environmental variables, like CARGO_CFG_TARGET_OS to get actual OS the program is being compiled for.

The alternative would be:
    #[cfg(feature = "static")]
    if std::env::var_os("CARGO_CFG_UNIX").is_some() {
        let linux_kernel_headers = std::env::var("LINUX_KERNEL_HEADERS").ok();
        // ...
    }

authors: Payn Stargateur Wojtek242 ilya-epifanov stappersg sudormrfbin

repo: rust-pcap/pcap


text:
⚠ Mitsubishi has degraded performance

In 3473f7f, Mitsubishi (https://mitsubishimotorsid-mobileapp.com/app/login) experienced degraded performance:

HTTP code: 200
Response time: 17485 ms

Resolved: Mitsubishi performance has improved in b51153d after 7 minutes.

license: MIT


text:
Add proc_key/1 function match for literals

Supports Cargo.toml configurations such as:
[target.'cfg(windows)'.dependencies]

which are matched by the lexer as {:literal, _} but fail to parse with a function missing error.

@erik-nymi looks like this PR was based on the vendor-erl-nif-sys branch?
Can you please close this and base your changes on master instead?

authors: erik-nymi scrogson

repo: rusterlium/rustler


text:
Exercise 1 in Node Classification notebook

❓ Questions & Help
I'm trying to do the exercise 1 in Node Classification notebook and I'm not sure whether my code is correct:
model = GCN(hidden_channels=16)
optimizer = torch.optim.Adam(model.parameters(), lr=0.01, weight_decay=5e-4)
criterion = torch.nn.CrossEntropyLoss()

best_val = -1.0
best_model = GCN(hidden_channels=16)

def train():
    model.train()
    out = model(data.x, data.edge_index)  # Perform a single forward pass.
    loss = criterion(out[data.train_mask], data.y[data.train_mask])  # Compute the loss solely based on the training nodes.
    loss.backward()  # Derive gradients.
    optimizer.step()  # Update parameters based on gradients.
    optimizer.zero_grad()  # Clear gradients.
    return loss

def test():
    best_model.eval()
    out = best_model(data.x, data.edge_index)
    pred = out.argmax(dim=1)  # Use the class with highest probability.
    test_correct = pred[data.test_mask] == data.y[data.test_mask]  # Check against ground-truth labels.
    test_acc = int(test_correct.sum()) / int(data.test_mask.sum())  # Derive ratio of correct predictions.
    return test_acc

def val():
    model.eval()
    out = model(data.x, data.edge_index)
    pred = out.argmax(dim=1)  # Use the class with highest probability.
    val_correct = pred[data.val_mask] == data.y[data.val_mask]  # Check against ground-truth labels.
    val_acc = int(val_correct.sum()) / int(data.val_mask.sum())  # Derive ratio of correct predictions.
    return val_acc

for epoch in range(1, 201):
    loss = train()
    if best_val < val():
        best_val = val()
        best_model.load_state_dict(model.state_dict())

    _val = val()
    print(f'Epoch: {epoch:03d}, Loss: {loss:.4f}, Val: {_val:.4f}, Best Val: {best_val:.4f}')

test_acc = test()
print(f'Test Accuracy: {test_acc:.4f}')

After running the code, I got Test Accuracy: 0.7940, which is a bit lower than Test Accuracy: 0.7970 when running without validation. Is this normal for this exercise? Also, if you have done the exercise, could I ask what is your final result?

Hi and thanks for this issue :) It's great to see you are already looking at the brand-new colab notebooks.
Your code is absolutely correct, which made me aware that I was missing a crucial step to achieve better performance for GCN on Planetoid datasets: I have forgotten to normalize input node features via:
dataset = Planetoid(root='data/Planetoid', name='Cora', transform=NormalizeFeatures())

This is now fixed, and leads to 81.4% test accuracy without validation, and 82% test accuracy with validation.


text:
Implement functions from position/game_math for RoomXY

RoomXY should have equivalent functionality to Position for in-room stuff that we can do fully within native math. All of the functions from the game_math module would make sense on the RoomXY type.
Potentially as an enhancement, both types could use a manhattan range function in addition to the current chebyshev range function. Maybe we should even go as far as providing a euclidean range function?

Should add some of these to RoomName too

Resolved by #521

repo: rustyscreeps/screeps-game-api


text:
Packed, typed object ids

Resolves #51, resolve #192.
This is based on an initial implementation @Dessix made, but I removed some of the optimizations in favor of simpler code, and created a separate untyped version.
This implements the binary/packed 12-byte storage described in #192 for object ids, and implements fairly efficient transfers of these 12-byte values between rust and JS. All of the translations, formatting and parsing are unit tested for reliability (since there's no reliance on a screeps server for that)
This also implements a typed version of the id, ObjectId<T>. The type is purely for type inference and optional safety - it has a into_type() method to change the inner type arbitrarily, and can be freely transformed into and from untyped object ids. My thought was that allowing this kind of "free" transmutation would mean we can have serialization and deserialization which just works, and doesn't have to do anything like calling into JS and checking Game.getObjectById() to ensure it's the right type. It means we need that one technically uneccessary check if you get an ID from a thing and then immediately use get_object_typed during the same tick, but I think the advantages are worth it.

With the other conversions - I'm happy to add  Into<ArrayString<[u8; 24]>>, Into<String> and From<[u32; 3]> - those seem natural.
I think From<String> would be a bit of a stretch though - conversion into ObjectId could definitely fail if it isn't in the right format, and we do have a FromStr implementation which allows using string.parse()??

You're right. Maybe an expensive TryFrom<String>, but that, I'd definitely leave for later.

Sounds good!
I forgot you mentioned Into<T> too, and I didn't address that. What would you think of adding that as a method, like try_resolve(&self) -> Result<Option<T>, ConversionError> - maybe with a counterpart resolve(&self) -> Option<T> which panics on incorrect type?

I think a combination of try_resolve and resolve sounds good, but I may be biased, as- indeed- I did have that functionality in my own implementation.
There is also potential room for a threadlocal LRU which is per-tick reset caching objects by ID to references, reducing calls out to JS.

Why not TryInto? I don't get why we don't rely on those here (except for the unsafe stuff) as it seems to be the most natural given the rest of the codebase.
Otherwise, I'm certainly not against resolve and try_resolve.

I'd argue against it mostly because it doesn't feel like an into operation - an ID is a fairly separate bit of information from the object it names, and "into" conversions usually mean turning the same bit of data into another form? Like we're getting a lot more than another form of the information contained in ObjectId.
The other reason would be ease of use, since we would be implementing TryInto<Option<T>>.  id.resolve() seems like it would be nicer to use (and read) than let x: Option<_> = id.try_into(); or Option::try_from(id).

Alright, you make a good case, I agree with you!

authors: ASalvail Dessix daboross


text:
does not start from a directory called non-latin characters

OS Windows 10 64 bit
lite crash on start from a directory called non-latin characters
put lite exe to
c:\Проба
ant start lite

There are two ways to solve this on Windows:

You could try (after Windows 10 v1803 update) the "Use Unicode UTF-8 for worldwide language support" checkbox in control panel > Region > Administrative> Change system locale (not tested). This enables the possibility to use ANSI functions like fopen or LoadLibrary with UTF-8 strings.
The other solution would be to modify all the code calls using the ANSI version of Win32 API to the Unicode version (...W) and defining -DUNICODE and  -D_UNICODE when compiling on Windows and fixing all places where fopen is used (and Lua must be patched, to use something like this instead).

Note that this would also need accounting for in system.list_dir() and system.get_file_info() for this to be fixed in lite. I believe #33 and this are the same issue

authors: boris-741 dacap rxi

repo: rxi/lite


text:
确认事项

[ ] 我愿意实现它

您运行的是我们软件的哪个版本？
joplin-blog
您的功能请求是否与问题有关？请描述。
能不能出一个docker版本？想在群晖上部署这套系统
描述您想要的解决方案
如上
描述您考虑过的替代方案
如上
其他上下文
No response

你应该可以使用 nodejs docker 镜像，然后在 dockerfile 中使用 npm i joplin-blog 来安装并运行它，不需要专门的 docker 镜像

这么快就回复了，太感谢了，我试试，主要是非程序员，这这些配置不太熟

authors: jameslcjq rxliuli

repo: rxliuli/joplin-utils


text:
Colors next to code prevents user from setting/removing a breakpoint

When you try to set a breakpoint on a given line that is showing coverage report (green or red) it does not let you set/remove a breakpoint.
Anyone else experiencing this?

Hey carlos, current the vscode api only allows one gutter element at a time sadly ☹ so if you use the gutter coverage you need to switch it off to interact with the breakpoints ref. The other option I was going to suggest was to use the line coverage option with gutters off which would have given you something like

"coverage-gutters.showGutterCoverage": false,
"coverage-gutters.showLineCoverage": true

but there appears to be an issue where simply having gutter coverage false does not enable the breakpoints again. After a quick look in the code I could get the above screenshot to work by tinkering with the rendering options here: https://github.com/ryanluker/vscode-coverage-gutters/blob/master/src/config.ts#L95 so it shouldnt be too hard to fix this. I will add this to the next release, thanks for submitting the issue!

Thanks for replying. I think the solution suggested would work great for now that VSCode doesnt allow multiple gutters elements. Ideally if it did allow it, you could layer the coverage underneath the "breakpoint layer".
Thanks for looking into this. I'll he happy to test things out in your next release 👍

@pintocarlos this issue will be fixed in 1.1.2 which will go out shortly. here is the commit if you are interested in the fix https://github.com/ryanluker/vscode-coverage-gutters/pull/91/commits/2ec3050b0da616e86bbed087417cafb52fb37d02

Thank you @ryanluker

I just experienced the same issue. Thanks @ryanluker for explaining the workaround!
Nowadays (VS Code 1.44.2) one can also change the settings from the UI:

So, this still pending and we are in 2020. Any news?

@JoseFMP based on my reading of the vscode api and the conversation history here https://github.com/microsoft/vscode/issues/73784 I assume that microsoft wants you to create decorators for this in the line itself instead of using the gutter icon sadly.

authors: JoseFMP eddex pintocarlos ryanluker

repo: ryanluker/vscode-coverage-gutters

license: mit


text:
Refactor for nextjs

This was one of the hardest things I've done yet since picking up an interest in react apps. It was also entirely avoidable. Notes to file:

When i created the nextjs project originally, I assumed the project stucture should be similar to a standard react app. I made a src file under app, and under app as the root. Huge mistake. While this worked fine locally, as soon as i tried to deploy it I realized netlify would never be able to figure out my project strucutre. I tried half a day of workarounds before deciding I would need to refactor to a more typical nextjs project structure.
I moved pages, components, contexts, package, and anything else that should be in the root level from the app directory to a new root outside of app.

Oh and I never got the history page to work again, SSR is tough. Will need to start here in next pr.

repo: ryanmio/DecodeMe-


text:
collision with single-document-mode (cmd + shift + D)

@ryantam626 how can I solve the mentioned collision. It appeared in one of the latest JL versions, I'm experiencing it on v 2.2.2.
The same keybinding is in sublime - duplicate line
any help is highly apprichiated
thx

Sorry I completely missed this, I just tried it on JupyterLab 3.0.0, it doesn't seem to happen anymore, is this still an issue for you?

Sorry I completely missed this, I just tried it on JupyterLab 3.0.0, it doesn't seem to happen anymore, is this still an issue for you?

Hi @ryantam626 ,
I have changed shortcut to ctrl + shift + D for duplicating lines with your extension, so cmd + shift + D  remained as it was designed for in JLab. I'm not yet using v3.0, I'm on 2.9. I tend to wait a month or so - so that all extensions, packages I'm using get updated and upstreamed. I'm planing to jump on v3.0 end of Feb, beginning of Mar.

Hi @ryantam626 ,
I have changed shortcut to ctrl + shift + D for duplicating lines with your extension, so cmd + shift + D  remained as it was designed for in JLab. I'm not yet using v3.0, I'm on 2.9. I tend to wait a month or so - so that all extensions, packages I'm using get updated and upstreamed. I'm planing to jump on v3.0 end of Feb, beginning of Mar.


text:
Sending events sets pages as not set in google analytics -> events -> pages

Sending a regular events is not a problem, but when checking the events in google analytics under pages all events are categorized underneath "not set".
The issue occured when having 2 components (Homescreen with a list and item component), the hit is executed in the homescreen but the event is triggered in/by the item component and for some reason when sending it to ga it loses the page info.
I tried to test this out and move the event to the homescreen which gets called by the item component, but without success.
Screenshot:

I have been using React Native with managed expo and made a singleton for the analytics instance.
import { Analytics, PageHit, ScreenHit, Event } from 'expo-analytics';

export default class ExpoAnalyticsManager {

    static instance = null;

    _analytics = null;

    static getAnalytics() {
        if(ExpoAnalyticsManager.instance ==null){
            ExpoAnalyticsManager.instance = new ExpoAnalyticsManager();
            this.instance._analytics = new Analytics("UA-153309176-1");
        }
        return this.instance;
    }

    pageHit(name){
        this._analytics.hit(new PageHit(name)).then(() => console.log("succes " + name)).catch(e => console.log(e.message));
    }

    screenHit(name){
        this._analytics.hit(new ScreenHit(name)).then(() => console.log("succes " + name)).catch(e => console.log(e.message));
    }

    event(category,action,optReclabel=null,optvalue=null){
        this._analytics.event(new Event(category, action, optReclabel, optvalue)).then(() => console.log("Succes Category: " + category + ". Action: " + action + ". Label: " + optReclabel + ". Value: " + optvalue )).catch(e => console.log(e.message));
    }

    addCustomDimension(id,value){
        this._analytics.addCustomDimension(id,value);
    }

    addCustomMetric(id,value){
        this._analytics.addCustomMetric(id,value);
    }

    removeCustomDimension(id){
        this._analytics.removeCustomDimension(id);
    }

    removeCustomMetric(id){
        this._analytics.removeCustomMetric(id);
    }

}

When the button was clicked the event was triggered through following code:
ExpoAnalyticsManager.getAnalytics().event("Like","Like-" + recipes[recipeIndex].name.replace(/\s+/g, '-'), recipes[recipeIndex].name, 1);

So the events get passed without any issue and prints the event in the console correctly.
Is it possible that i have to send a hit when sending an event so it gets linked or is there a different reason to why the page information isn't known?

Please give a look at Expo Analytics Google with static API

Yes but that's a different library as im using this library for my bachelor thesis which is a comparison study of 3 different analytic tools, so i have to use this library.

I have made changes to the singleton to be able to use this properly. Instead of creating the analytics only once i now create it everytime I use the getAnalytics() method. When I call the method I send the parameters object with it so when sending an event I can send the page information through the param object.
static getAnalytics(params) {
        if(ExpoAnalyticsManager.instance ==null){
            ExpoAnalyticsManager.instance = new ExpoAnalyticsManager();
        }
        this.instance._analytics = new Analytics("UA-153309176-1",params);
        return this.instance;
    }

Example of usage:
ExpoAnalyticsManager.getAnalytics({dt:"Get Ideas"}).event("Like","Like-" + recipes[recipeIndex].name.replace(/\s+/g, '-'), recipes[recipeIndex].name, 1);

authors: BillyCottrell murshudov

repo: ryanvanderpol/expo-analytics


text:
REAME.md

It would be useful if you had a README.md file with the link to the site.
rzorzal.github.io

Hi @edgardleal , i saw your point and I'm glad you to give this advise. This repo is just a test of github pages, but I agree with you, it would be best if I created a README.md file with that link and others informations. Thanks.

authors: edgardleal rzorzal


text:
[BUG] build issue with JDK 1.8.0_172, lombok version 1.6.20

Describe the bug
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project project-common: Fatal error compiling: java.lang.ExceptionInInitializerError: com.sun.tools.javac.code.TypeTags -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project project-common: Fatal error compiling
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:567)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1086)
    at org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:168)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:567)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.codehaus.plexus.compiler.CompilerException: java.lang.ExceptionInInitializerError
    at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess (JavaxToolsCompiler.java:173)
    at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile (JavacCompiler.java:174)
    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1075)
    at org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:168)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:567)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
    at com.sun.tools.javac.api.JavacTaskImpl.handleExceptions (JavacTaskImpl.java:163)
    at com.sun.tools.javac.api.JavacTaskImpl.doCall (JavacTaskImpl.java:100)
    at com.sun.tools.javac.api.JavacTaskImpl.call (JavacTaskImpl.java:94)
    at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess (JavaxToolsCompiler.java:126)
    at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile (JavacCompiler.java:174)
    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1075)
    at org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:168)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:567)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: java.lang.ExceptionInInitializerError

To Reproduce
It is wierd that it is not happening in my colleague's machine.
I had correct configuration in idea intelliJ with jdk and jre set to 1.8.0_172 as my colleagues did.  But it can't work with 1.16.20, which is working fine on my colleague's machines. I tried to install a lombok plugin on idea, but it still failed.
When I changed the lombok version to 1.18, it is perfect.
Expected behavior
Solution to the problem without changing the maven configuration.
Version info (please complete the following information):
The jvm I installed on my machine is as followed:
MacBook-Pro:project leonyu$ /usr/libexec/java_home -V
Matching Java Virtual Machines (2):
    12.0.1, x86_64:	"OpenJDK 12.0.1"	/Library/Java/JavaVirtualMachines/adoptopenjdk-12.0.1.jdk/Contents/Home
    1.8.0_172, x86_64:	"Java SE 8"	/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home

/Library/Java/JavaVirtualMachines/adoptopenjdk-12.0.1.jdk/Contents/Home

the maven dependency is listed as followed:
lombok.version>1.16.20</lombok.version>

<dependency>
                <groupId>org.projectlombok</groupId>
                <artifactId>lombok</artifactId>
                <version>${lombok.version}</version>
                <scope>provided</scope>
</dependency>

system version
[INFO] os.detected.name: osx
[INFO] os.detected.arch: x86_64
[INFO] os.detected.version: 10.14
[INFO] os.detected.version.major: 10
[INFO] os.detected.version.minor: 14
[INFO] os.detected.classifier: osx-x86_64

Additional context

Why do you want to use an outdated Lombok version when more recent versions fixed the issue?
This project does not maintain older branches/releases. You have to switch to the current version if you want a bugfix.

I didn't notice that older version is not maintained and issue to older version is not closed.. Btw, where can i find current supported version list.

There are no supported Lombok versions besides the most recent one.

repo: rzwitserloot/lombok


text:
error during login

im trying to login using my phone number, but its not working. i only get- ERROR: {"statusCode":400,"errorKey":null,"data":null,"fields":null,"timestamp":"2023-07-18T20:47:00.670Z","requestId":"3cd4ba658e9c1f0f277960e63dd8ed00"}
Failed with Vonage login provider, re-trying to login with Firebase...
my region is Latvia

Do you get another error after the blue "Failed with Vonage..." ? Can you check the console?

authors: diankabaranka s-alad

repo: s-alad/toofake


text: New Logo


text:
Bug fix: parsing the css files would put the result in the same entry…

… of sheets var. Solved by using IIFE.

@yoel-zeldes I was only getting viewport units converted and rules added to the head from the last CSS file loaded. This fixed my problem, thanks

@yoel-zeldes & @retallicka How can I merge this commit with my fork please? New to GitHub and would like to merge this commit with my fork instead of copying and pasting the changes from the commit line by line. Thank you.

@saabi is there a reason not to merge this pull request?

I have no time to maintain the repo lately and all merges are held up waiting for #39 but this one is important enough that it should be merged.
If anybody wants to help out just mention it, I'm sure he'll be more than welcome by a lot of people.

authors: monolux retallicka saabi yoel-zeldes

repo: saabi/vminpoly


text:
DNSでのサーバ切断/接続

PreHandle/PostHandleで配下のサーバの切断/接続(レコード削除/追加)を行うためのハンドラーを追加する

現状では対応しないことにする。サーバのスケールアップ/ダウンとの併用にはGSLBやELBの利用を推奨する。
サーバの水平スケールを実装する際に再考する。

repo: sacloud/autoscaler


text:
🛑 PEAKE CW Control is down

In c02f608, PEAKE CW Control (https://help.peakesupport.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PEAKE CW Control is back up in 110487f.


text:
Consider switching to em unit

Awesome work!
After looking at the way you handled icon sizes (which I thought was really clever, btw), I couldn’t help but wonder if you might benefit from employing the same strategy but with fractional ems instead of px. For example, you could set the base font size to say 16px and then set @1 = .0625em,@2 = .125em, etc.
The potential benefit of this is you could then have a .icono-2x class, for example, which would simply apply font-size: 32px and all of the icons would get twice as big. You would only have to add a single line of extra CSS to get sizes in 2x, 4x, etc. and the complexity of the .less code wouldn’t have to change at all, afaict.
I’ll note that I have made some icons like this before and have run into odd browser rounding issues. So this might be a concern. But I think it might be fine if you set a base font size for all icons in px and then use em for the width, height, border-width, ::after and ::before sizes, etc.
I’d be happy to take a stab at a PR if you think this is something icono could benefit from.

+1.
A single class approach also works for that:
.top-menu [class^="icono-"] {
    font-size: 16px;
}

.sidebar [class^="icono-"] {
    font-size: 24px;
}

Not to mention media queries.

@joaocunha Good points. Only thing I’d just caveat is that doing non-integer multiples of the base font size (whatever that ends up as in this em world), could produce non-pixel-fitted icons or other undesirable results due to rounding. So once a base font size is set at say 16px or 32px, you’ll want to only user integer multiples of such size.
This made me just think of a potentially interesting approach in which the base font size is set to 1px, and so you have em units like 1em, 2em, etc. essentially behaving as pixels. Then 2px, 3x, base font size would be your multiples. This may have strange consequences for icons inline with commonly sized text, though. I may take a crack at it though just for fun.

@adamschwartz I don't think non-integer would cause any side effects as long as we're using ems. As a matter of fact, even non-integer pixels may round very nicely, as you can see on vUnit.
The easiest way to convert is to use font-size:10px as a base, and convert the units to em.
FROM:
.icono-check {
    width: 28px;
    height: 28px;
    margin: 3px 0 3px 6px;
    transform: rotate(-45deg);
}

TO:
/* base value for all icons, comes as standard and can be overriden by cascade */
[class^="icono-"] {
    font-size: 10px;
}

.icono-check {
    width: 2.8em;
    height: 2.8em;
    margin: .3em 0 .3em .6em;
    transform: rotate(-45deg);
}

I might not have been clear but I was originally commenting on the 16px and 24px sizes used in your original example. The analogous thing in your latest example would be to have then:
.sidebar [class^="icono-"] {
    font-size: 15px;
}

What I’m saying is 15 * .3 and 15 * .6, etc. will produce either 4-to-9, 5-to-9 (both not maintaing the original 1-to-2 ratio of 3-to-6) or it will show the .3em unit as 4 solid pixels and a fifth half-filled in pixel (not pixel-fitted).

Maybe I was not clear also :)
This is a quick hack I came up with to show a proof-of-concept:
(focus only on the check icon)

And this is with font-size:51px:

My point is, uneven ratios/non-integer values would work just fine with em units.
Are we on the same page? :)

It’s not easy to tell, but in your example, the .3em and .6em margins will not center the icon properly.
Here’s a quick example which exhibits the issue more clearly:

On jsFiddle
In the small icon, the blue right border is twice the width of the left red border. In the large icon, the blue icon is 9/4ths larger, since in a border width, the browser rounds 4.5px to 4px.

Ok, I see what you mean. Can't think of any other solution other than abiding to safe base font-sizes.

Adding to it, this issue is happening already when zooming in/out with cmd + +/-.

I'm very interested in this becoming a thing - it should be easy to use the icons at any scale desired, and em allows that.

The rem is better.

authors: adamschwartz benwiley4000 hemedani joaocunha

repo: saeedalipoor/icono


text:
Single invoice download

Notion card
https://www.notion.so/saeloun/Add-Download-button-to-Invoices-List-page-API-Integration-eda269189b9e437ba2feada30448e86a
Summary

API integration for single invoice download

Preview

https://www.loom.com/share/0fb454d34faf4048b64855f7f1e4f2fa
https://www.loom.com/share/533b48b07fc544d5b022023b31a24c12
Type of change

[ ] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Checklist:

[ ] I have manually tested all workflows
[ ] I have performed a self-review of my own code

@Shruti-Apte We are getting the option to download the draft invoice on the invoice/id page.

repo: saeloun/miru-web


text:
Make TransactionApiModule non-global

Depends on #1365

The TransactionApiModule was made Global to facilitate overriding this module in the tests (with a fake one).
Since NestJS now provides the ability to override modules based on the respective token, we should require the respective dependants to declare the need for it (increasing encapsulation).

Pull Request Test Coverage Report for Build 8557779393
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 93.06%

Totals

Change from base Build 8557377486:
-0.01%

Covered Lines:
6548

Relevant Lines:
6786

💛  - Coveralls

authors: coveralls fmrsabino

repo: safe-global/safe-client-gateway


text:
Cannot read properties of undefined (reading ´map´) when executing a tx

Description
Signing and executing a transaction with a Ledger Nano S through Metamask lead to an error showing in MM and making the owner unable to execute the transaction but only sign it.
Environment

Browser: Chrome, Firefox
Wallet: MetaMask with Ledger Nano S (1.9.17)
Chain: Ethereum

Steps to reproduce

Go to Safe app
Create and execute a transaction
Switch to the data view in MetaMask
Observe error being displayed

Expected result
Obtained result
Data view in MM: "e is undefined"
Screenshots

@usame-algan could you add details on how you reproduced it on Rinkeby?

I think the Cannot read properties of undefined error in MetaMask is not Ledger related but the other one e is undefined might be.

We tracked down to Truffle parsing the decoded data. Needs more investigation.
Try reproducing in isolation (outside of the Safe even).

I debugged my MetaMask extension while this error appeared and got some insights.
The error is caused by this line in Metamask: https://github.com/MetaMask/metamask-extension/blob/66c049bb357155750b772e94faedd8c57ed0e88f/ui/components/app/transaction-decoding/transaction-decoding.util.js#L5
The problem is, that metamask expects the calldata decoding to be a function call.
At least it tries to map over the arguments of the decoded data.
In our case truffle returns a MessageDecoding which does not have a args field.
Some Links

Component which decodes the tx
Line causing exception
Truffle docs

@johannesmoormann closing this issue as it needs to be resolved by metamask.
The decoded data display fails to handle fallback calls which we use with our GnosisSafeProxy contracts.
I found this possible related issue at mm https://github.com/MetaMask/metamask-extension/issues/13425

authors: johannesmoormann katspaugh schmanu usame-algan

repo: safe-global/safe-react


text:
Suggestion

Do you guys have any suggestions??

Do you guys have any suggestions??

Use GUI

Add attractive images in background.

repo: sagarbangade/Calculator-in-C-language


text:
🛑 Evon Stone Ceramics is down

In d2b6594, Evon Stone Ceramics (https://evonceramics.com) was down:

HTTP code: 500
Response time: 214 ms

Resolved: Evon Stone Ceramics is back up in 19dc50a after .

repo: sahajananddigital/status


text:
🛑 Harikrusna International is down

In 5a3fd2e, Harikrusna International (https://shreeharikrushnaintl.com) was down:

HTTP code: 503
Response time: 397 ms

Resolved: Harikrusna International is back up in 14917dc after 13 minutes.


text:
🛑 Rüfenacht Elektro AG is down

In 48d807b, Rüfenacht Elektro AG (https://www.ruefenacht-elektro.ch) was down:

HTTP code: 500
Response time: 266 ms

Resolved: Rüfenacht Elektro AG is back up in b2b4f22 after 12 minutes.


text:
🛑 Forum Sumiswald is down

In d573675, Forum Sumiswald (https://www.forum-sumiswald.ch) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Forum Sumiswald is back up in 082f1c7 after 7 minutes.


text:
False positive error on parameter types

Unfortunately I couldn't come up with a simple repro, this happens at work (VS Code):

This builds successfully from console

You said you cannot come up with a reproducible test case.
Can you share the output when you run bingo with -trace enabled?

I'm seeing some of these as well - I'm looking through the trace output here now and my findings are:
The first occurence of the false posistive happens after a save after editing for a while:
--> notif: textDocument/didSave: {"textDocument":{"uri":"file:///Users/REDACTED/myapp/moderate/service_test.go","version":524}}
<-- notif: textDocument/publishDiagnostics: {"uri":"file:///Users/REDACTED/myapp/moderate/service_test.go","diagnostics":[{"range":{"start":{"line":103,"character":27},"end":{"line":103,"character":27}},"severity":1,"source":"LSP: Go compiler","message":"cannot use (func(topicID myapp.TopicID, postID myapp.PostID) (*myapp.Post, error) literal) (value of type func(topicID gitlab.com/REDACTED/myapp.TopicID, postID gitlab.com/REDACTED/myapp.PostID) (*gitlab.com/REDACTED/myapp.Post, error)) as func(topicID gitlab.com/REDACTED/myapp.TopicID, id gitlab.com/REDACTED/myapp.PostID) (*gitlab.com/REDACTED/myapp.Post, error) value in assignment"},{"range":{"start":{"line":108,"character":29},"end":{"line":108,"character":29}},"severity":1,"source":"LSP: Go compiler","message":"cannot use (func(_ *myapp.Post) error literal) (value of type func(_ *gitlab.com/REDACTED/myapp.Post) error) as func(in1 *gitlab.com/REDACTED/myapp.Post) error value in assignment"},{"range":{"start":{"line":44,"character":34},"end":{"line":44,"character":34}},"severity":1,"source":"LSP: Go compiler","message":"cannot use (func(topicID myapp.TopicID, postID myapp.PostID) error literal) (value of type func(topicID gitlab.com/REDACTED/myapp.TopicID, postID gitlab.com/REDACTED/myapp.PostID) error) as func(topicID gitlab.com/REDACTED/myapp.TopicID, postID gitlab.com/REDACTED/myapp.PostID) error value in assignment"}]}

After this starts occuring I start seeing some panics in my logs - but it happens quite a lot later so I don't know if they are neccessarily related:
--> notif: textDocument/didChange: {"textDocument":{"uri":"file:///Users/REDACTED/myapp/write/service.go","version":4},"contentChanges":[{"range":{"start":{"line":0,"character":2},"end":{"line":0,"character":2}},"rangeLength":0,"text":"c"}]}
invalid position for file
panic serving textDocument/completion: runtime error: invalid memory address or nil pointer dereference
goroutine 6388 [running]:
github.com/saibing/bingo/langserver/internal/util.Panicf(0x451f8e0, 0x49eae00, 0x45b080c, 0x2, 0xc007e1b7f8, 0x1, 0x1, 0xc007e1b808, 0x405ba66)
	/opt/bingo/359e4f9a910dd1949e4419d41d39ba9057fc675c/langserver/internal/util/util.go:116 +0x93
github.com/saibing/bingo/langserver.(*LangHandler).Handle.func1(0xc00a4359a0, 0xc007e1be60)
	/opt/bingo/359e4f9a910dd1949e4419d41d39ba9057fc675c/langserver/handler.go:110 +0xc4
panic(0x451f8e0, 0x49eae00)
	/usr/local/Cellar/go/1.11.5/libexec/src/runtime/panic.go:513 +0x1b9
go/token.(*File).Size(...)
	/usr/local/Cellar/go/1.11.5/libexec/src/go/token/position.go:120
github.com/saibing/bingo/langserver.lineStart(0x0, 0x1, 0xc0165ebce0)
	/opt/bingo/359e4f9a910dd1949e4419d41d39ba9057fc675c/langserver/position.go:76 +0x37
github.com/saibing/bingo/langserver.fromProtocolPosition(0x0, 0x0, 0x2, 0xc01133c4c0)
	/opt/bingo/359e4f9a910dd1949e4419d41d39ba9057fc675c/langserver/position.go:49 +0x38
github.com/saibing/bingo/langserver.(*LangHandler).handleTextDocumentCompletion(0xc0000e2420, 0x4668e20, 0xc0146267c0, 0x4667220, 0xc00012a500, 0xc00a4359a0, 0xc01133c480, 0x39, 0x0, 0x2, ...)
	/opt/bingo/359e4f9a910dd1949e4419d41d39ba9057fc675c/langserver/completion.go:34 +0x10a
github.com/saibing/bingo/langserver.(*LangHandler).Handle(0xc0000e2420, 0x4668e20, 0xc0146267c0, 0x4667220, 0xc00012a500, 0xc00a4359a0, 0x0, 0x0, 0x0, 0x0)
	/opt/bingo/359e4f9a910dd1949e4419d41d39ba9057fc675c/langserver/handler.go:268 +0x267a
github.com/saibing/bingo/langserver.(*LangHandler).handle(0xc0000e2420, 0x4668e60, 0xc0000ac008, 0xc00012a500, 0xc00a4359a0, 0xc013cf2540, 0x3a, 0x0, 0x0)
	/opt/bingo/359e4f9a910dd1949e4419d41d39ba9057fc675c/langserver/handler.go:100 +0x66
github.com/saibing/bingo/langserver.(*LangHandler).handle-fm(0x4668e60, 0xc0000ac008, 0xc00012a500, 0xc00a4359a0, 0x0, 0x0, 0x0, 0x0)
	/opt/bingo/359e4f9a910dd1949e4419d41d39ba9057fc675c/langserver/handler.go:26 +0x52
github.com/sourcegraph/jsonrpc2.(*HandlerWithErrorConfigurer).Handle(0xc0000a33d0, 0x4668e60, 0xc0000ac008, 0xc00012a500, 0xc00a4359a0)
	/Users/REDACTED/go/pkg/mod/github.com/sourcegraph/jsonrpc2@v0.0.0-20180831160525-549eb959f029/handler_with_error.go:21 +0x73
created by github.com/saibing/bingo/langserver.lspHandler.Handle
	/opt/bingo/359e4f9a910dd1949e4419d41d39ba9057fc675c/langserver/handler.go:50 +0xfb
<-- error #420: textDocument/completion: {"code":0,"message":"unexpected panic: runtime error: invalid memory address or nil pointer dereference","data":null}
[Error - 2:59:13 PM] Request textDocument/completion failed.
  Message: unexpected panic: runtime error: invalid memory address or nil pointer dereference
  Code: 0

I've tried anonymizing the output here a little bit, hopefully I haven't done anything that removes any important information from it. As mentiond by @lggomez the project builds successfully and restarting VSCode (and thus Bingo) solves the problem for a little while.
It's quite reproducible for me, happening 5-10 times per day. Is there any info I could provide to help pinpoint the issue?
Thanks.

I just updated to the recent master version and I'm still seeing the same issue. For me it seems to be quite consistently croaking when passing around mocks to functions requiring interfaces; for example:

I have a app.MyInterface interface, and a mocks.MyInterfaceMock mock generated via moq
I have an app.NewMyService func that takes in an instance of app.MyInterface
In my tests I create instances of mocks.MyInterfaceMock and pass it to the app.NewMyService function

This seems to start creating the issue more or less the first time I save a file as it is now.
It, however, does not seem to happen if I run bingo with -cache-style=none; might this be some cache corruption issue of some sort?

@tanordheim yeah, this is pretty much my case

I notice similar issues when working with mocks. I will try to put together a full reproduction test case in a repository to demonstrate the issue.  If anyone has already done so, please share it.
I am using https://github.com/mockery/mockery.

It seems that the latest version from master has fixed this issue!
Can someone confirm this, or am I seeing things? :)

I don't think I've seen it since updating 5 days ago either; however, I've been working on a different project for the last few days with a different code structure (no generated mocks, which have been a source of problems before) so I can't fully say which one is the source of things working better. I'm moving back to that other project that were causing issues multiple times a day for me later this week, I can report back if I see any there.

Yup, I see it in my other project as well with the same problems.

I'm seeing this in some projects here still, after upgrading to the latest commit in master as of 24 hours ago. I'm struggling to reproduce it in a small self contained project I could give as a reproduction, but I'm happy to offer any information you'd need and test any work in progress changes with one of our code bases here where it happens quite regularly.

Still having this problem:

@saibing
I've made a lot of changes in this branch https://github.com/banaio/bingo/tree/fix_issues_with_textDocument/publishDiagnostics but I believe the core fix is in either or both of the below:

https://github.com/banaio/bingo/blob/fix_issues_with_textDocument/publishDiagnostics/langserver/handler.go#L56: Don't spawn a go routine for new requests.
https://github.com/banaio/bingo/blob/fix_issues_with_textDocument/publishDiagnostics/langserver/fs.go#L136: Diagnose when instant or onsave.

The rest of the changes are just refactoring. The entire diff of the branch is https://github.com/saibing/bingo/compare/master...banaio:fix_issues_with_textDocument/publishDiagnostics. I've tried to make the commits atomic so you can see changes incrementally. The tests do not pass hence the commit message saying it is a breaking change, run gotest -count=1 -v -json ./... to see where it gets stuck.
Also, I don't know if this makes a difference but I run a build with race detector enabled:
$ go build -o $GOPATH/bin/bingo_dev -race

If anyone wants to try the branch and report back that'd be great.

@lggomez @mbana @nezorflame @inliquid
Please use the enhanced version of gopls, it has fixed this issue.

authors: inliquid lggomez mbana nezorflame saibing tanordheim

repo: saibing/bingo


text:
feat: update TF wf to include v1.9.x

feat: update TF wf to include v1.9.x

/code pr

repo: saidsef/terraform-aws-github-oidc


text:
feat: added ci

issues and license badges,

/code review

:robot:
No issues or suggestions for enhancements are identified in the modified lines of the README.md file. The addition of CI, issues, and license badges improves the documentation by providing quick access to the build status, current open issues, and licensing information directly from the README.
> gpt-4-turbo-preview

repo: saidsef/terraform-tfe-workspaces


text:
chore: update dep lib

chore: update dep lib

/code pr

repo: saidsef/tracing-node


text:
Make the PWA installable

Complete PWA setup to automatically show an install button on Chrome, instead of requiring users to select "Add to Home" for installation.

Fixed with commit c4e5401c5242381a5121f4e8af8a87522000822b


text:
Patch 1

Patch is to fix the problem setting the proxy from set-configuration (open issue #12 )

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant patrice-adp

repo: sailpoint-oss/powershell-sdk


text:
Loot not showing. SPTarkov AKI 3.0.0

For some reason loot isn't showing for ESP, I put the uni installer 1.9 in my 3.0.0 directory, and ran the .exe which seems to have worked fine, I also had played before running the installer as well.

it is working for both 3.0.0 and 3.1.0. Please read the docs. You have to use track command.

Ah, I didn't realize I needed to use that.

it is working for both 3.0.0 and 3.1.0. Please read the docs. You have to use track command.

Is it possible to clear my console? So there's not a bunch of text etc.

authors: ajdrigs sailro

repo: sailro/EscapeFromTarkov-Trainer


text:
Finding Mean,Median,Mode of a numbers

if a user input numbers and he/she will click on mean button to find mean click on median button to find median and mode button to find mode.
I am a gssoc'21 participant can you please assign me this @sairish2001

Feel free to ask your doubts, if any
Deadline 17 March,2021 (11:59 PM IST)

Thanks for assigning this to me i will do my best

I'm a GSSOC'21 participant kindly assign me this issue. I would love to work in this.


text:
Update axlsx_styler.gemspec

axlsx version is now 3.0.0

I guess this should work, but I'd love to see some integration tests against axlsx 2 and 3 to be confident in a release. For example, axlsx_rails has some tests that ensure the app won't blow up against different dependencies: https://github.com/straydogstudio/axlsx_rails/blob/master/spec/ci.rb
I also wonder if there's a way to automate verification of Excel files produced by the tests. I was doing it manually in the past.

I think if we can guarantee that the files produced with the styler gem are identical to the files produced with the vanilla axlsx gem then we're good to go.
Re: Testing against different versions of axlsx. The little bit of research I've done suggests that the appraisal gem from ThoughtBot is a good candidate for generating the various Gemfiles, which can then be passed to Travis or another CI pipeline for running the tests.

Thanks for bringing up this issue @nfruneau! Fixed by @davefp in https://github.com/sakovias/axlsx_styler/pull/21.

authors: davefp nfruneau sakovias


text:
XO-Dojo

รบกวนด้วยครับ

ฮ่าๆ ปกติผมจะแอดgitผ่าน Visult Studio ซึ่งมัน ignore ไฟล์ที่ไม่เกี่ยวข้องให้
แต่อันนี้ไม่ได้แอดเอง ก็ลืม ignore ไปเลยค้าบ คร่าวหน้าจะระวังครับ
ขอบคุณสำหรับคำแนะนำครับ

repo: saladpuk/Coding-Dojo


text:
POC: Move webhooks from plugin to core

POC of webhook refactoring - move webhook events outside of the webhook plugin into regular core modules. This approach implements the RFC https://github.com/saleor/saleor/issues/12583, where webhook events are represented as classes.
The goal of this POC is to show examples of two webhook implementations - an async one and a sync one. The webhooks were changed:

async product_created
sync shipping_list_methods_for_checkout

Additional SQL queries in the benchmark are caused by fetching webhooks for the event shipping_list_methods_for_checkout, which was not visible before because these benchmarks were not using the webhook plugin.
Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations

Docs

[ ] Link to documentation:

Pull Request Checklist

[ ] Privileged queries and mutations are either absent or guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migrations are either absent or optimized for zero downtime
[ ] The changes are covered by test cases
[ ] All new fields/inputs/mutations have proper labels added (ADDED_IN_X, PREVIEW_FEATURE, etc.)
[ ] All migrations have proper dependencies
[ ] All indexes are added concurrently in migrations
[ ] All RunSql and RunPython migrations have revert option defined

FYI - we decided to pause this work for now, as first we need to deliver webhook circuit breaker.

repo: saleor/saleor


text:
Update install-the-collection.md

It wasn't immediately clear to me what the subdomain consisted of (I got it wrong before checking the page I hyperlinked in this PR.)

merged

repo: salesforce-marketingcloud/sfmc-postman


text:
fix(yarn): update to modern yarn

Updates the project to use to modern yarn.
You may need to take a step to make corepack override Volta's shims locally if you have issues. See the note in the readme below.

Looks like my commit signing broke, I'll fix and re-push everything.

repo: salesforce/utam-js-recipes


text:
Created a CSS Star Pattern

Description
A CSS art with Star pattern
Fixes #166
Insert the image of the art below

Checklist:
To fill the checklists, put x inside the brackets. [x]

[x] My code follows the guidelines of this project
[x] I have tested my code and it works properly
[x] I have added just one folder that includes my Art files (jsx and css)
[x] I have not edited App.js file
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] This is my original code and I have NOT copied the code from anywhere else.

Hi @Tejal18, I cannot accept this PR as the code is plagiarized.

Hi @Tejal18, I'll close this PR. Code your own art and feel free to make a fresh PR.

repo: salil-naik/css-art-gallery


text:
Added Netflix Logo

Description
Please provide a 1 line description of your art
Fixes #issue-number
Insert the image of the art below
Checklist:
To fill the checklists, put x inside the brackets. [x]

[] My code follows the guidelines of this project
[] I have tested my code and it works properly
[] I have added just one folder that includes my Art files (jsx and css)
[] I have not edited App.js file
[] I have commented my code, particularly in hard-to-understand areas
[] My changes generate no new warnings
[] This is my original code and I have NOT copied the code from anywhere else.

Please merge my PR #41

@shahbazalam07, I'm closing this PR. Feel free to open a fresh PR whenever you make the changes.


text:
🛑 Blog is down

In 3a313bc, Blog (https://saltbo.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Blog is back up in 34ade55 after 5 minutes.

repo: saltbo/status


text:
Feature Request: Additional Storage Options for NAS/SAN via SMB, NFS, or iSCSI

Is your feature request related to a problem? Please describe.
While Saltcorn currently offers local and Amazon S3 Bucket options for file storage, there is a need for additional storage settings to cater to different infrastructures. Some users, including myself, operate with Network Attached Storage (NAS) or Storage Area Networks (SAN) and would greatly benefit from being able to store files through SMB, NFS, or iSCSI.
Describe the solution you'd like
I propose that Saltcorn expands its storage settings to include the ability to store files on a NAS or a SAN using SMB, NFS, or iSCSI. This enhancement would allow a wider range of users to effectively manage and store their data in a way that best suits their specific needs and infrastructure.
Describe alternatives you've considered
While it's possible to manually transfer files to a NAS or SAN, this can be a time-consuming process and doesn't take full advantage of the automation capabilities that Saltcorn could provide. By incorporating these storage options directly into Saltcorn, users could benefit from a more streamlined, efficient, and automatic file storage process.
Additional context
Expanding storage settings would increase Saltcorn's flexibility and adaptability to different system infrastructures. By offering more diverse options for file storage, Saltcorn could better meet the needs of a larger user base and improve overall user experience.

It's "already supported". :-)
You can mount them to docker as volume or to some S3 engine like Minio.

Hi @pyhedgehog, can you be a little more descriptive?
Can you give examples of how I would connect this to a NAS? Maybe TrueNAS thought SMB or NFS share?

Sorry, I had no practical experience with this NAS exactly. There are docker volume plugins for iSCSI, for SFTP, for SMB, for S3. At last rclone has operation mode to work as docker volume plugin. But I can't hint what to choose in your situation. :-(

@pyhedgehog I'm not advanced enough of a user to understand how to do those setups. :(
Which is why I'm using Saltcorn. :)
Maybe you could make a guide?
I agree we don't need support for all of them, just SMB or NFS would be great. Because currently Saltcron runs in a VM and with users uploading files, it will balloon the VM's storage. If we could link stored content to a NAS (similar to the S3 option we currently have) it would solve the large storage requirements for VM's.
I understand that I could create a virtual disc for the VM on the NAS, but that it has it's own implications (I/O, speeds) if you don't have a fast network setup.
Additionally, these storage options would allow for multiple Saltcorn VM's to run simultaneously in load balancing configuration. Without the need to sync the data and doubling the storage requirements.

Quite a lot of this is beyond the scope of the project, at least for now. Note that if you know your way around the command line and are able to mount the shared drive to a directory on the server, you can do one out of two things:

change the file_store key of the configuration file to the directory in which the shared drive is mounted. This pretty much does what do you want. In the future we could allow the administrator to change this configuration key using the admin UI, just like they can control whether multi tenancy is enabled or disabled. I don't know about other cloud providers but at least on digital ocean you can create a new volume and mount it to a directory on a vm without the command line

Create a Symlink from your shared drive into a sub directory in your saltcorn file store. symlinked directories are omitted from backups. I use this on one project with a dropbox shared drive and it works well

I propose to make another FR "Allow plugins to provide file storage systems". Then this FR can be implemented as plugin.

@glutamate Hi Tom, I like the sound of option (1.) and I want to try the implementation with my NAS. Are you able to provide any more details on the SALTCORN_FILE_STORE variable?

Can you please give me example of the variable path? (Does it include the whole /home/saltcorn/ or only /home/saltcorn/.local/share/saltcorn/public?) Basically, does it backup all the saltcorn files or only the public folder?

When I do a backup, does it also backup all the files in mounted shared drive? Or are they omitted from backups, similar to Symlink setup you have?

If I am correct this variable goes into the /home/saltcorn/.config/.saltcorn config file?

If I can get this working with a NAS, I will write up a guide about it on the forum.

@pyhedgehog That would be great! I can raise the FR if you like.
Would you be able to implement it?

While in principle the plugin idea sounds good, I think in practice it will be difficult to implement when Saltcorn runs as a non root user. I think you need root access to mount e.g. nfs and SMB drives, unless they are already in /etc/fstab with user option (in which case a root user needs to know about them anyways?)
But I could be wrong. We can investigate if and how users can mount shared drives in e.g. gnome, KDE or xfce file managers without entering root password

We can implement just api access — we needn't mount it to os. Like S3 does.

@glutamate I would like to try mounting the NAS as a drive while the plugin could/maybe be developed.
Are you able to provide some details on the SALTCORN_FILE_STORE variable as per my post above?

authors: glutamate pyhedgehog serge402

repo: saltcorn/saltcorn


text:
Label in search window

Hi,
I define a view where I define a label for a field like this
vatCode -> Code like below

If I open the searh window there are "Anywhere" and "vatCode"

For a user this may be a problem because he don't know the field name but the field label as in the form.
Also labels in the search windows aren't in en.json for i18n ("Search Filter", "Anywhere", "Apply" the button).
Thanks,
Fabio.

Okay, agree this is a problem because the end user sees this. In terms of both translation and user experience, I try to prioritise what the end user sees, so we need to fix this

both aspects (i18n and using header label if present) done in #368

authors: fabiograz glutamate


text:
fix(plasma-ui): Replace useLayoutEffect to useIsomorphicLayoutEffect for Slider and Marquee

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install @salutejs/plasma-b2c@1.87.1-canary.132.2865600299.0
npm install @salutejs/plasma-core@1.65.1-canary.132.2865600299.0
npm install @salutejs/plasma-icons@1.91.1-canary.132.2865600299.0
npm install @salutejs/plasma-temple@1.86.1-canary.132.2865600299.0
npm install @salutejs/plasma-typo@0.12.1-canary.132.2865600299.0
npm install @salutejs/plasma-ui@1.120.1-canary.132.2865600299.0
npm install @salutejs/plasma-web@1.120.1-canary.132.2865600299.0
npm install @salutejs/plasma-cy-utils@0.18.1-canary.132.2865600299.0
npm install @salutejs/plasma-sb-utils@0.64.1-canary.132.2865600299.0
# or
yarn add @salutejs/plasma-b2c@1.87.1-canary.132.2865600299.0
yarn add @salutejs/plasma-core@1.65.1-canary.132.2865600299.0
yarn add @salutejs/plasma-icons@1.91.1-canary.132.2865600299.0
yarn add @salutejs/plasma-temple@1.86.1-canary.132.2865600299.0
yarn add @salutejs/plasma-typo@0.12.1-canary.132.2865600299.0
yarn add @salutejs/plasma-ui@1.120.1-canary.132.2865600299.0
yarn add @salutejs/plasma-web@1.120.1-canary.132.2865600299.0
yarn add @salutejs/plasma-cy-utils@0.18.1-canary.132.2865600299.0
yarn add @salutejs/plasma-sb-utils@0.64.1-canary.132.2865600299.0

Demo canvas app deployed!
http://plasma.sberdevices.ru/demo-canvas-app-pr-132/

Documentation preview deployed!
website: http://plasma.sberdevices.ru/pr-132/
ui storybook: http://plasma.sberdevices.ru/pr-132/ui-storybook/
web storybook: http://plasma.sberdevices.ru/pr-132/web-storybook/
b2c storybook: http://plasma.sberdevices.ru/pr-132/b2c-storybook/
temple storybook: http://plasma.sberdevices.ru/pr-132/temple-storybook/

authors: Salute-Eva neretin-trike

repo: salute-developers/plasma


text:
chore(plasma-b2c): remove unused variable

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

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install @salutejs/plasma-b2c@1.141.2-canary.353.4194499292.0
# or
yarn add @salutejs/plasma-b2c@1.141.2-canary.353.4194499292.0

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

Demo canvas app deployed!
http://plasma.sberdevices.ru/pr/demo-canvas-app-pr-353/

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

Documentation preview deployed!
website: http://plasma.sberdevices.ru/pr/pr-353/
ui storybook: http://plasma.sberdevices.ru/pr/pr-353/ui-storybook/
web storybook: http://plasma.sberdevices.ru/pr/pr-353/web-storybook/
b2c storybook: http://plasma.sberdevices.ru/pr/pr-353/b2c-storybook/
temple storybook: http://plasma.sberdevices.ru/pr/pr-353/temple-storybook/

authors: Salute-Eva Yeti-or


text:
FATAL ERROR: 0x80004005 network path not found

Hello Sam,
When running mame-ao.exe I get the following error:
_
#######################################################################################################################
Welcome to Spludlow MAME-AO Shell V1.57
https://github.com/sam-ludlow/mame-ao
#######################################################################################################################
Give it a moment the first time you run
Usage: type the MAME machine name and press enter e.g. "mrdo"
or a CHD e.g. "gauntleg"
or with MAME arguments e.g. "mrdo -window"
SL usage: type the MAME machine name and the software name and press enter e.g. "a2600 et"
or a CHD e.g. "cdimono1 aidsawar" (Note: Not all CHD SLs are not currently available)
or with MAME arguments e.g. "a2600 et -window"
Use dot to run mame without a machine e.g. ".", or with paramters ". -window"
If you have alreay loaded a machine (in current MAME version) you can use the MAME UI, filter on avaialable.
List saved state: ".list".
You can start a particular version of MAME with the command ".VVVV" where V is the version e.g. ".0252" or pass arguments e.g. ".0252 mrdo -window".
WARNING: Large downloads like CHD will take a while, each dot represents 1 MiB (about a floppy disk) you do the maths.
#######################################################################################################################
Initializing
#######################################################################################################################
Data Directory: D:\MAME
Symbolic Links Enabled: False
!!! You can save a lot of disk space by enabling symbolic links, see the README.
=======================================================================================================================
=                                             Prepare source: MachineRom                                              =
Loading MachineRom metadata JSON D:\MAME_METADATA\MachineRom_mame-merged.json ......done.
Title:  MAME 0.256 ROM Set (Merged)
Version:        0256
=                                             Prepare source: MachineDisk                                             =
Loading MachineDisk metadata JSON D:\MAME_METADATA\MachineDisk_MAME_0.225_CHDs_merged.json ......done.
Title:  MAME 0.255 CHDs (merged)
Version:        0255
!!! MachineDisk on archive.org version mismatch, expected:0256 got:0255. You may have problems.
=                                             Prepare source: SoftwareRom                                             =
Loading SoftwareRom metadata JSON D:\MAME_METADATA\SoftwareRom_mame-sl.json ......done.
Title:  MAME SL 0.256 (Merged) - No CHD
Version:        0256
=                                            Prepare source: SoftwareDisk                                             =
Loading SoftwareDisk metadata JSON D:\MAME_METADATA\SoftwareDisk_mame-sl-chd-cdi.json ......done.
Title:  MAME SL CHD - cdi
Version:        MAME SL CHD - cdi
Loading SoftwareDisk metadata JSON D:\MAME_METADATA\SoftwareDisk_mame-sl-chd-neocd.json ......done.
Title:  MAME SL CHD - neocd
Version:        MAME SL CHD - neocd
Loading SoftwareDisk metadata JSON D:\MAME_METADATA\SoftwareDisk_mame-sl-chd-pcecd.json ......done.
Title:  MAME SL CHD - pcecd
Version:        MAME SL CHD - pcecd
Loading SoftwareDisk metadata JSON D:\MAME_METADATA\SoftwareDisk_mame-software-list-chds-2.json ......done.
Title:  mame-software-list-chds
Version:        mame-software-list-chds
=                                                        MAME                                                         =
=                   https://github.com/mamedev/mame/releases/download/mame0256/mame0256b_64bit.exe                    =
Creating machine performance caches......done
Creating software performance caches......done
Getting all SHA1s......done.
!!! FATAL ERROR: Det går inte att hitta nätverksplatsen. Information om hur nätverksfel kan felsökas finns i Windows Hjälp
System.Net.HttpListenerException (0x80004005): Det går inte att hitta nätverksplatsen. Information om hur nätverksfel kan felsökas finns i Windows Hjälp
vid System.Net.HttpListener.AddAllPrefixes()
vid System.Net.HttpListener.Start()
vid Spludlow.MameAO.WebServer.StartListener()
vid Spludlow.MameAO.MameAOProcessor.Shell()
vid Spludlow.MameAO.MameAOProcessor.Run()
If you want to submit an error report please copy and paste the text from here.
Select All (Ctrl+A) -> Copy (Ctrl+C) -> notepad -> paste (Ctrl+V)
Report issues here https://github.com/sam-ludlow/mame-ao/issues
Press any key to continue, program has crashed and will exit.
_
I have checked that all the prerequisites (correct version of .net and so on) are installed and have tried running both as a normal user and as an administrator. I am unsure of what to try next!
Regards,
Anders

Hello Anders
Thanks for the bug report.
Looks like it had an issue starting the web server. It uses http://127.0.0.1:12380/
So IPv4 localhost and port 12380.
Does your machine use IPv6 only network stack?
Look in network settings-> Adapter (whatever) -> Edit IP settings -> Is IPv4 switched off? Try switching it on, see if that helps.
I should probably use "localhost" this should always resolve. And do some tests with IPv6.
Cheers
Sam

Hello Anders I've changed it in 1.58 to use "localhost".
Did that fix it? (forget about your network settings for now).
If it did then I expect your machine is IPv6 only? Can you confirm this out of interest?
Cheers Sam

Closing, I'm pretty sure localhost will fix this issue.
I didn't test on a IPv6 only box, but it seems to use IPv6 with localhost anyway.

authors: prodev-zz sam-ludlow

repo: sam-ludlow/mame-ao


text:
Corrupted GoogleColab!

Hello,
Would you please modify the GoogleColab link? It's already corrupted.
Thanks!

Also, can you add a step-by-step description to run the code and see the result?
It's not even really clear on the MEdium website.

Thanks for pointing this out! Closing the issue since we have updated the Colab link.

authors: afshinebtia samar-khanna


text:
Provide a way to get rid of jsDocTags prop

Provide a way to get rid of jsDocTags prop
Problem
Some schema validator tools get confused when them encontreed jsDocTag
for example this is the stacktrace of Joi when i pass the output of TSON.application to his compiler
Error: Invalid empty array schema (schema.jsDocTags)
    at new module.exports (/home/gcardamone/Workspace/test/infrastructure/backend/node_modules/@hapi/hoek/lib/error.js:23:19)
    at module.exports (/home/gcardamone/Workspace/test/infrastructure/backend/node_modules/@hapi/hoek/lib/assert.js:21:11)
    at Object.internals.schema (/home/gcardamone/Workspace/test/infrastructure/backend/node_modules/joi/lib/compile.js:36:9)
    at Object.exports.schema (/home/gcardamone/Workspace/test/infrastructure/backend/node_modules/joi/lib/compile.js:17:26)
    at internals.Base.$_compile (/home/gcardamone/Workspace/test/infrastructure/backend/node_modules/joi/lib/base.js:645:24)
    at /home/gcardamone/Workspace/test/infrastructure/backend/node_modules/joi/lib/types/keys.js:260:92
    at Object.exports.tryWithPath (/home/gcardamone/Workspace/test/infrastructure/backend/node_modules/joi/lib/common.js:176:16)
    at internals.Base.method [as keys] (/home/gcardamone/Workspace/test/infrastructure/backend/node_modules/joi/lib/types/keys.js:260:32)
    at Object.internals.schema (/home/gcardamone/Workspace/test/infrastructure/backend/node_modules/joi/lib/compile.js:90:25)
    at Object.exports.schema (/home/gcardamone/Workspace/test/infrastructure/backend/node_modules/joi/lib/compile.js:17:26) {
  path: 'schema.jsDocTags'

Feature Request
Would be nice to have the capability of controlloing generated schema directly from the method
Examples
TSON.application<[
  MyInterface
], "swagger", "#/components/schemas", TSON.OmitJsDocTag | TSON.AnotherFlag>()

Suggestion
A fifth Generic can be use to control the omittable fields in generation
export type OmitJsDocTag = 'omit-json-doc-tag'
export type AnotherFlag = 'another-flag'

export type Flags =
 | OmitJsDocTag
 | AnotherFlag

export interface IJsonApplication {
    schemas: IJsonSchema[];
    components: IJsonComponents;
    purpose: "swagger" | "ajv";
    prefix: string;
    flags: Flags
}

Update to the latest version, then it will be fixed

authors: giovannicardamone-facile samchon

repo: samchon/typescript-json


text:
Chime Shown, Homebase not shown

Describe The Bug:
Doorbell chime is recognised and maps the security states successfully (home, away, etc). But the Homebase itself does not appear.
To Reproduce:
Chime and Homebase hardware installed, run plugin.
Expected behavior:
Make the Homebase the alarm system and ignore the chime
Logs:
[6/11/2021, 9:01:31 AM] [EufySecurity] Adding new accessory: Doorbell
[6/11/2021, 9:01:31 AM] [EufySecurity] Adding new accessory: Chime
[6/11/2021, 9:01:50 AM] [EufySecurity] Eufy Guard Mode:  { value: 1, timestamp: 1613159408000 }
[6/11/2021, 9:01:50 AM] [EufySecurity] Eufy Guard Mode:  { value: 1, timestamp: 1613159408000 }

Plugin Config:
            "username": "email@email.com",
            "password": "myPassword",
            "hkHome": 1,
            "hkAway": 0,
            "hkNight": 3,
            "hkOff": 63,
            "platform": "EufySecurity"

Screenshots:

Environment:

Plugin Version: 0.1.1
Operating System:  macOS >

Update: removing the chime and pairing the doorbell with the HomeBase is a workaround.

Interesting. Didn't know that Chimes were treated as stations in eufy-security-client. The code should support having multiple Stations - but if we only receive either a Chime or Hub then we can only add what was returned. I don't have a Chime so I can't test this.

I have a Homebase, keypad, motions sensors and contacts.  The doorbell I had first and was associated with the chime. So I removed the chime, associated the doorbell to the Homebase and all is working perfectly.

If we introduced "the this.log.debug('Found hub' + hub.getName());" in the hub iteration we would be able to see how many hubs the client return.

Thanks, but I suspect my case is pretty niche and I’ve moved the doorbell over to the Homebase, so I’d say focus on bigger thing. Really appreciate the reply and work you’re doing. Absolutely awesome, thank you.

Added the logging. When it is merged you can retest.

@PeterAlexander75 The logging is merged into master now.

Please re-test if possible.

Closing this issue due to inactivity

authors: PeterAlexander75 samemory schliemann

repo: samemory/homebridge-eufy-security


text:
'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

Fix process >

Install Xcode
$: Run sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

$: Run sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

repo: samleoqh/IssueTracker


text:
Adding license file.

Hi sampalmer,
I noticed your awesome program to set a default browser programmatically; I'm using it with a scheduled task to explicitly set my default browser to Chrome as group policy seems to over ride it to Internet Explorer.
Anyway, I didn't see a license file and am wondering if you'd like to put one in. I went ahead and created an MIT license.

Hi @moros,
I'm glad you find this program useful. I use it for the same thing.
It took me a while to make up my mind about which licence to use for this project, but I have decided on Unlicence and added it in commit c2b5745a1df266a48fe96b781debbbe98e00a54b.
I will close this pull request since I have gone with a different licence to the one you suggested.
Thanks

authors: moros sampalmer

repo: sampalmer/set-default-browser

license: Unlicense


text:
🛑 Jobster-API is down

In 2306dba, Jobster-API (https://jobster-api-vnuk.onrender.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jobster-API is back up in 0438398 after 16 minutes.

repo: sampathsailanka/monitoring-tool


text:
Captions not loaded in Firefox when setting tracks with .source setter

Expected behaviour
Setting caption tracks in the player .source in JavaScript code should work like setting <track> tags in HTML.
Actual behaviour
This works fine with the latest Chrome and Safari but not Firefox.
Looking at the network requests shows Firefox never actually loads the caption file in the first place.
Steps to reproduce
See example at https://codesandbox.io/s/magical-knuth-e6qhq
Environment

Browser: Firefox
Version: 67.0
Operating System: macOS
Version: 10.14.5

Console errors (if any)
No errors but enabling debug: true shows it's setting a TextTrack with no cues in Firefox:
Track added
  > TextTrack { kind: "captions",
    > cues: TextTrackCueList { length: 0 }

while in Chrome it does have some cues
cues: TextTrackCueList {0: VTTCue, 1: VTTCue, 2: VTTCue, 3: VTTCue, 4: VTTCue, 5: VTTCue, 6: VTTCue, length: 7}

Link to where the bug is happening
https://e6qhq.codesandbox.io/

Can also attest to this issue:
Track added  TextTrack  activeCues: TextTrackCueList { length: 0 }  cues: TextTrackCueList { length: 0 }  id: ""  inBandMetadataTrackDispatchType: ""  kind: "captions"  label: ""  language: ""  mode: "hidden"  oncuechange: null  <prototype>: TextTrackPrototype { addCue: addCue(), removeCue: removeCue(), kind: Getter, … } plyr.js:2641:33
Also occurs in IE and Edge. This is a pretty massive bug that breaks the most essential accessibility a video player can provide.

I seem to be experiencing this issue as well on Chrome.
I've tried to debug to the best of my abilities but I'm not sure what's wrong. All I can say, seems like first time I assign tracks and video it works. Then if I assign new video and new tracks, those tracks will not be downloaded and won't be shown :(

Similar issue #1959

authors: Wiggyboy barberousse jackguoAtJogg mirkonasato

repo: sampotts/plyr


text:
Fix z-indexes on Youtube controls

On Youtube videos, the "copy link" and browsing "more videos" don't work due to the wrong z-index.

Link to related issue (if applicable)
Encountered in Glightbox: https://github.com/biati-digital/glightbox/issues/214
Summary of proposed changes
Change z-indexes.

This effectively always hides the poster image. Sorry, not a good solution.

authors: sampotts vyskoczilova