text:
gdal crate failing to compile

Crate name
map-engine
Build failure link
https://docs.rs/crate/map-engine/0.1.0/builds/491073
Additional details
Happy new year to everyone and thanks for your amazing work.
I just published my first crate (map-engine) and I'm having problems generating the docs due to a dependency that fails to compile.
The dependency is gdal which has an external dependency (GDAL). I checked if it was possible to make a PR to crates-build-env but the problem is that Ubuntu 18.04 has a very old version of GDAL.
Is there any recommended way of dealing with this?

I can generate my docs locally, is there any way to upload those?
The gdal crate has a custom build.rs that seems to deal with this. Does the build system use that or should I write my own build.rs?

Thanks!

The error comes from this conditional compilation in gdal:
#[cfg(docsrs)]
pub fn gdal_version_info(_key: &str) -> String {
    "GDAL 3.2.0, released 2222/02/22".to_string()
}

#[cfg(not(docsrs))]
pub fn gdal_version_info(key: &str) -> String {
    let c_key = std::ffi::CString::new(key.as_bytes()).unwrap();

    unsafe {
        let res_ptr = gdal_sys::GDALVersionInfo(c_key.as_ptr());
        let c_res = std::ffi::CStr::from_ptr(res_ptr);
        c_res.to_string_lossy().into_owned()
    }
}

They do provide a flag in their Cargo.toml:
[package.metadata.docs.rs]
rustc-args = ["--cfg", "docsrs"]

But the building system seems to ignore it (you can see "--config" "build.rustflags=[\"--cfg\", \"docsrs\"]"  in the build log).

@Nemo157 could you have a look here?

@Nemo157 was this solved with the resolved cargo issue?

I think it should have been, I've queued a rebuild and we'll see what happens.

Rebuild succeeded 🎉

authors: Nemo157 spadarian syphar


text:
Make the GitHub buttons more accessible

The link to a crate's repository is the feature I use the most; we still have space in top bar, so why not moving the button there?

This is a duplicate of https://github.com/rust-lang/docs.rs/issues/61.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
docs.rs does not load in China anymore

This is what I see when debugging this in Firefox - it appears only a few resources are not loading:

I thought it might be related to the recent move of blocking TLS 1.3 and ESNI, but I couldn't verify it for sure.
I am happy to provide further data to help resolving this issue, if at all possible.
Thank you

I guess this is pretty strong motivation for #921. We did switch to fontawesome 5 recently which uses a different CDN, but from your screenshot it looks like even the old files aren't loading.

Is the site completely broken or is it just the css missing? We can move it from <head> to <body> as a short term workaround which would let you at least use the site.

Thanks for taking a look! It's completely broken as one only sees a white screen, due to the CSS not loading. The HTML is present though, it just won't ever be displayed. Firefox would display 'ghosts' of the page while in dev mode for some reason, and Curl can also get anything hosted on docs.rs.
That workaround of moving the CSS sounds great, I would love to give it a try.

I think vendoring all those files is as easy as shuffling things around, I'd avoid messing with the ordering.

If we need to we can vendor our CSS, that's the recommended way to use FA 5

I have no idea if a Chinese Rust community even exist

@Byron you might be interested in https://www.youtube.com/watch?v=j_ha1-1w6sw

authors: Byron Kixiron jyn514 pietroalbini


text:
Switch to grass for sass compilation

Removes our dependency on sass_rs/libsass, which reduces our total # of native dependencies

Helps contributors since it reduces the number of native dependencies as well as fixing the interments issues with libsass randomly breaking
grass supports more features, namely sass modules which are currently unsupported by sass_rs

This PR was made out of anger when libsass suddenly broke

libsass suddenly broke

I didn't hear about this, what went wrong?

Code changes look fine, but have you run a diff on the generated CSS file before and after? I don't want to make changes blind.

I have pretty much no idea, it just suddenly died when linking

The two outputs are very nearly identical, only difference is that grass doesn't minify yet, but I don't think that's a huge deal considering how small our css is anyways

This bit about a complete rewrite really worries me: https://github.com/connorskees/grass/pull/33#issuecomment-673110393
I understand grass is a new project and has a lot of advantages over libsass, but I don't want to switch to a project that's about to be completely redone. Can we come back to this after the proposed rewrite?

If you're still interested in this, grass is at a point where I feel quite confident in its output. For docs.rs, the output only seems to differ from dart-sass in whitespace.

@connorskees I probably won't have time to work on switching myself, but if it reduces our dependencies I'd be willing to take a PR for it :)

source: gharchive/pull-request

authors: Kixiron connorskees jyn514


text:
haiku adding getentropy.

no man page so far but
https://github.com/haiku/haiku/blob/e4a557f372b21b348e0c6a2ae7157c1b73e0d738/src/system/libroot/posix/unistd/getentropy.c#L13

@rustbot label stable-nominated

Looks straightforward enough to me, @nielx could you double check this?

@devnexen No objections to adding getentropy(), however I think the place is incorrect. The commit you cite actually moved this out of libbsd into the general libroot. However, in this change, you place it in the block that links to bsd. While this will not cause any problems in practise, I suggest it is placed outside of this block to match Haiku.

@tgross35 looks good to me!

Thanks for reviewing! I am just holding off on merging anything until FreeBSD comes back (rustc broke, should be fixed in this nightly or the next one)

Thanks for reviewing! I am just holding off on merging anything until FreeBSD comes back (rustc broke, should be fixed in this nightly or the next one)
Seems working now.

authors: devnexen nielx tgross35

repo: rust-lang/libc


text:
[0.2] Backports

Backport https://github.com/rust-lang/libc/pull/4157

The first CI run is me applying only the patch adding tests, that fails as expected without the fix https://github.com/rust-lang/libc/actions/runs/12046642238/job/33587533778?pr=4160.


text:
Review Linux futex implementation for weak memory

This appears to be the smoking gun of std::sync::mpsc https://github.com/matklad/once_cell/pull/182 and crossbeam channel https://github.com/rust-lang/rust/issues/55005#issuecomment-1152732346 deadlocks
https://github.com/rust-lang/miri/blob/32a7580b05b1f34b19d830f4f99cf1d9f58f7a76/src/shims/unix/linux/sync.rs#L129-L148
The deadlock can be seen running this
use std::{sync::mpsc::channel, thread};

fn test() {
    let (tx1, rx1) = channel();
    let (tx2, rx2) = channel();
    let t1 = thread::spawn(move || {
        tx1.send(()).unwrap();
        rx2.recv().unwrap();
    });

    rx1.recv().unwrap();

    tx2.send(()).unwrap();

    assert!(t1.join().is_ok());
}

pub fn main() {
    for i in 0.. {
        dbg!(i);
        test();
    }
}

[src/main.rs:20] i = 0
[src/main.rs:20] i = 1
[2022-06-10T22:00:00Z TRACE miri::concurrency::weak_memory] outdated value read at /home/cbeuw/.rustup/toolchains/miri/lib/rustlib/src/rust/library/std/src/sys/unix/futex.rs:61:21: 69:22 (#0)
error: deadlock: the evaluated program deadlocked
   --> /home/cbeuw/.rustup/toolchains/miri/lib/rustlib/src/rust/library/std/src/sys/unix/thread.rs:250:66
    |
250 |             let ret = libc::pthread_join(self.id, ptr::null_mut());
    |                                                                  ^ the evaluated program deadlocked
    |
    = note: inside `std::sys::unix::thread::Thread::join` at /home/cbeuw/.rustup/toolchains/miri/lib/rustlib/src/rust/library/std/src/sys/unix/thread.rs:250:66
    = note: inside `std::thread::JoinInner::<()>::join` at /home/cbeuw/.rustup/toolchains/miri/lib/rustlib/src/rust/library/std/src/thread/mod.rs:1352:9
    = note: inside `std::thread::JoinHandle::<()>::join` at /home/cbeuw/.rustup/toolchains/miri/lib/rustlib/src/rust/library/std/src/thread/mod.rs:1485:9
note: inside `test` at src/main.rs:15:10
   --> src/main.rs:15:10
    |
15  |     assert!(t1.join().is_ok());
    |             ^^^^^^^^^
note: inside `main` at src/main.rs:21:9
   --> src/main.rs:21:9
    |
21  |         test();
    |         ^^^^^^

note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace

error: aborting due to previous error

(That TRACE line was added locally. I'll make a separate PR to add weak memory logging)

I think that FIXME refers to the fact that we use SeqCst. Is that the right ordering or not? The futex documentation should specify how it interacts with other non-futex atomic accesses to the same location -- what kind of an access does it behave like?

This also seems suspicious to me:
https://github.com/rust-lang/miri/blob/32a7580b05b1f34b19d830f4f99cf1d9f58f7a76/src/shims/unix/linux/sync.rs#L209
When waking up a thread, shouldn't we also tell that thread that it "synchronized with" the thread that triggered the wakeup? Or does futex not guarantee that?
The corresponding calls in sync.rs (the lock implementations) do do something with the data race model. It's a bit non-local unfortunately; maybe unblock_thread should take some kind of parameter (a vclock or so) so that it can do all that work itself so that we cannot possibly forget this?

Ah, there actually is code to inform data_race about the futex happens-before, it is just in a different file:
https://github.com/rust-lang/miri/blob/10d978c180217f09c576822a312bc7353adfc17c/src/sync.rs#L566

What happened here is that an outdated value was read from addr, which happens to be equal to expected and the thread starts waiting even though someone else has already changed *addr and called futex_wake.
This exact issue was mentioned in the Linux kernel implementation:
https://github.com/torvalds/linux/blob/0885eacdc81f920c3e0554d5615e69a66504a28d/kernel/futex/waitwake.c#L27-L95
 * In futex wake up scenarios where no tasks are blocked on a futex, taking
 * the hb spinlock can be avoided and simply return. In order for this
 * optimization to work, ordering guarantees must exist so that the waiter
 * being added to the list is acknowledged when the list is concurrently being
 * checked by the waker, avoiding scenarios like the following:
 *
 * CPU 0                               CPU 1
 * val = *futex;
 * sys_futex(WAIT, futex, val);
 *   futex_wait(futex, val);
 *   uval = *futex;
 *                                     *futex = newval;            // cbeuw: They are assuming interleaving semantics here but with weak memory this assignment can be executed before CPU 0 even ran anything
 *                                     sys_futex(WAKE, futex);
 *                                       futex_wake(futex);
 *                                       if (queue_empty())
 *                                         return;
 *   if (uval == val)
 *      lock(hash_bucket(futex));
 *      queue();
 *     unlock(hash_bucket(futex));
 *     schedule();
 *
 * This would cause the waiter on CPU 0 to wait forever because it
 * missed the transition of the user space value from val to newval
 * and the waker did not find the waiter in the hash bucket queue.
 *
 * The correct serialization ensures that a waiter either observes
 * the changed user space value before blocking or is woken by a
 * concurrent waker:
 *
 * CPU 0                                 CPU 1
 * val = *futex;
 * sys_futex(WAIT, futex, val);
 *   futex_wait(futex, val);
 *
 *   waiters++; (a)
 *   smp_mb(); (A) <-- paired with -.
 *                                  |
 *   lock(hash_bucket(futex));      |
 *                                  |
 *   uval = *futex;                 |
 *                                  |        *futex = newval;
 *                                  |        sys_futex(WAKE, futex);
 *                                  |          futex_wake(futex);
 *                                  |
 *                                  `--------> smp_mb(); (B)
 *   if (uval == val)
 *     queue();
 *     unlock(hash_bucket(futex));
 *     schedule();                         if (waiters)
 *                                           lock(hash_bucket(futex));
 *   else                                    wake_waiters(futex);
 *     waiters--; (b)                        unlock(hash_bucket(futex));
 *
 * Where (A) orders the waiters increment and the futex value read through
 * atomic operations (see futex_hb_waiters_inc) and where (B) orders the write
 * to futex and the waiters read (see futex_hb_waiters_pending()).
 *
 * This yields the following case (where X:=waiters, Y:=futex):
 *
 *	X = Y = 0
 *
 *	w[X]=1		w[Y]=1
 *	MB		MB
 *	r[Y]=y		r[X]=x
 *
 * Which guarantees that x==0 && y==0 is impossible; which translates back into
 * the guarantee that we cannot both miss the futex variable change and the
 * enqueue.

But our futex_wake doesn't handle a concurrent wait call:
https://github.com/rust-lang/miri/blob/31da2d9f610ea7fc4d0ce8e5e7988b037055ca1a/src/sync.rs#L550-L577
We could use addr.fetch_add(0) to read and ensure "waiter observes the changed user space value before blocking" in this case, and this will work because Miri will never yield to a concurrent waker before our futex_wait call is finished - but it's still incorrect and will deadlock again once we add pre-emptive scheduling (my recent attempt to add a very simple time-quanta based preemption failed due to deadlocks in tests. I didn't figure out why but I think this is it)

(FWIW the Miri scheduler is preemptive now, though it doesn't use time quanta -- it uses a simple "probability to yield at the end of each basic block".)
So is this a bug in how stdlib uses the futex API, or in how Miri implements it?

but it's still incorrect and will deadlock again once we add pre-emptive scheduling (my recent attempt to add a very simple time-quanta based preemption failed due to deadlocks in tests. I didn't figure out why but I think this is it)

Further thoughts: actually we won't be pre-empting inside Miri shims, so this is
 * CPU 0                               CPU 1
 * // the following two accesses are in MIR and preemptable - though if they are reordered the wait call will return immediately
 * val = *futex;
 *                                     *futex = newval;
 *                                     // cannot preempt
 *                                     sys_futex(WAKE, futex);
 *                                       futex_wake(futex);
 *                                       if (queue_empty())
 *                                         return;
 * // cannot preempt
 * sys_futex(WAIT, futex, val);
 *   futex_wait(futex, val);
 *   uval = *futex;           // guaranteed to read newval and not val if we use RMW
 *
 *   if (uval == val)
 *      lock(hash_bucket(futex));
 *      queue();
 *     unlock(hash_bucket(futex));
 *     schedule();

So is this a bug in how stdlib uses the futex API, or in how Miri implements it?

How Miri implemented it. I think changing the atomic read to a fetch_add(0) will do the trick

Yes, Miri shims are atomic.
Thanks for the detailed analysis! I cannot say I have fully understood it yet; I'll need more time to carefully re-read everything you said. But if you know what the fix is, then if you could create a PR (with a testcase, of course), that would be great. :)

authors: RalfJung cbeuw

repo: rust-lang/miri

license_source: bigquery


text:
Change helper fn 'write_os_str_to_wide_str'

Helper fn write_os_str_to_wide_str now works on Scalar<Tag>, just like other read/write os_str helper functions.
The 2nd commit contains some changes made to src/shims/env.rs in PR #1225, in order to keep it from bloating too much.

Looking good, thanks. :)
@bors r+

:pushpin: Commit 07f7083409c3cdb112249bc4f5930c3713d1bbb4 has been approved by RalfJung

:hourglass: Testing commit 07f7083409c3cdb112249bc4f5930c3713d1bbb4 with merge e2a9c7baed31d29c02d62acfcf49e61af1c37f12...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing e2a9c7baed31d29c02d62acfcf49e61af1c37f12 to master...

authors: JOE1994 RalfJung bors


text:
Fix #151

When looking for a where in
rust-rewind-to-beginning-of-current-level-expr, check that it is not
part of a string or comment.

r? @huonw
(rust_highfive has picked a reviewer for you, use r? to override)

r? @MicahChalmer

Even with this patch, there are still places in the code that look for where clauses and don't check for comments, so there are still edge cases in which the word "where" in a comment can affect the indentation.  For instance, with or without this PR, rust-mode will indent the following code as follows:
fn foo<F,G>(f:F, g:G)
    where F:Send,
// where
    G:Sized
{

}

but if you change the "where" in the comment to another word, the G:Sized is aligned with the F:Send (which I believe is correct.)  If you make the comment a a where clause with a type annotation in it, rust-mode starts to align the actual code with the comment:
fn foo<F,G>(f:F, g:G)
    where F:Send,
// where      F:ThisIsNotActualCode,
              G:Sized
{

}

You're right. I'll update all places where we're looking for "where" to use (the existing) rust-in-str-or-cmnt.

authors: MicahChalmer mrBliss rust-highfive

repo: rust-lang/rust-mode


text:
matches!(x, | A | B | ...) produces strange output

When using a leading | in the matches! macro, this leads to some weird formatting looking like closure syntax:
enum Bla {
    A,
    B,
}

impl Bla {
    // before processing by `rustfmt`
    pub fn weird_unformatted(self) -> bool {
        matches!(self, | Self::A | Self::B)
    }

    // output of `rustfmt` --- looks like closure syntax!
    pub fn weird_formatted(self) -> bool {
        matches!(self, |Self::A| Self::B)
    }

    // what if we use just plain `match`?
    pub fn match_unformatted(self) -> bool {
        match self {
            | Self::A | Self::B => true,
        }
    }

    // that looks better!
    pub fn match_formatted(self) -> bool {
        match self {
            Self::A | Self::B => true,
        }
    }
}

Thanks for reaching out, but closing as a duplicate of #4462
Formatting of macro calls is still a bit limited and rudimentary as rustfmt is a formatter of known/valid rust syntax, and args to calls aren't always such. As such, rustfmt will attempt to format calls that use paren or bracket delims, but not calls with brace delims. For paren/bracket delimited calls, rustfmt will only format if each arg can be parsed as a valid syntactical construct, with the first attempt being to parse as an expression. Using a leading pipe does result in that second arg getting parsed as a closure, so it's formatted according to the corresponding closure rules instead.
I'm sure at some point we'll get around to special case handling of matches! calls, but in the interim, would encourage skipping the leading pipe or using brace delims (though that'll require you to format the call contents entirely by hand)

Ok, thanks for your detailed explanation!

repo: rust-lang/rustfmt


text:
rustfmt adding unnecessary parenthesis and commas.

When I am run cargo fmt or rustfmt it adds unnecessary parenthesis and commas randomly somewhere.
Here is the output of rustfmt --check ran on a file,
❯ rustfmt --check src/sample_hive/gui/panels/side_panel.rs
Diff in /home/apoorv/repos/sample-hive-rs/src/sample_hive/gui/panels/side_panel.rs at line 67:
                 if path.is_dir() {
                     let header = egui::CollapsingHeader::new(format!(
                         "📁 {}",
-                       entry.file_name().to_string_lossy())
-                    )
+                        entry.file_name().to_string_lossy()
+                    ))
                     .default_open(false)
                     .show(ui, |ui| {
                         self.nested_collapsible_directory_structure(ui, &path);
Diff in /home/apoorv/repos/sample-hive-rs/src/sample_hive/gui/panels/side_panel.rs at line 77:
                     if ui
                         .selectable_label(
                             false,
-                            format!("📄 {}", &entry.file_name().to_string_lossy())
+                            format!("📄 {}", &entry.file_name().to_string_lossy()),
                         )
                         .drag_started()
                     {

as you can see it is trying to add extra parenthesis in the first section and a comma in the second section.
I am not sure but I think this mostly happens around lines with unicode or emoji  in the text or something as I did notice this in another place where I had emoji.
Also I only started noticing this issue today only, it was fine yesterday.

Thanks for reaching out but I'm going to close.
In the first case, rustfmt isn't adding a parenthesis, but is simply moving the closing paren from the end of one line (after the to_string_lossy call) to the next.
In the second case, rustfmt is adding a trailing comma
Both of these are the expected and correct behavior as dictated by the Rust Style Guide which rustfmt implements.
You can utilize the trailing_comma config option if you'd like to modify the behavior of the latter; the former is not controllable.

I am not sure but I think this mostly happens around lines with unicode or emoji in the text or something as I did notice this in another place where I had emoji.
Also I only started noticing this issue today only, it was fine yesterday.

No, any string contents or unicode vs ascii aspects are unrelated and orthogonal to the behavior. This is long standing rustfmt behavior, and there's been no changes to rustfmt for quite some time so I can't speak to why you've not seen this before. It's possible the associated files weren't being formatted, or they were nested within some module/block/etc. that rustfmt wasn't touching for other reasons (e.g. not-yet-supported syntax like let else, bug in comment handling, etc.) but that some recent code changes have resulted in rustfmt finally getting to these portions of your code

Thanks for reaching out but I'm going to close.
In the first case, rustfmt isn't adding a parenthesis, but is simply moving the closing paren from the end of one line (after the to_string_lossy call) to the next.
In the second case, rustfmt is adding a trailing comma
Both of these are the expected and correct behavior as dictated by the Rust Style Guide which rustfmt implements.
You can utilize the trailing_comma config option if you'd like to modify the behavior of the latter; the former is not controllable.

I am not sure but I think this mostly happens around lines with unicode or emoji in the text or something as I did notice this in another place where I had emoji.
Also I only started noticing this issue today only, it was fine yesterday.

No, any string contents or unicode vs ascii aspects are unrelated and orthogonal to the behavior. This is long standing rustfmt behavior, and there's been no changes to rustfmt for quite some time so I can't speak to why you've not seen this before. It's possible the associated files weren't being formatted, or they were nested within some module/block/etc. that rustfmt wasn't touching for other reasons (e.g. not-yet-supported syntax like let else, bug in comment handling, etc.) but that some recent code changes have resulted in rustfmt finally getting to these portions of your code

I see.
But what about this,
https://user-images.githubusercontent.com/53279454/214372109-6806518a-cf2c-4604-8f5a-0769fa80d7fe.mp4

But what about this,

You are attempting to make an invalid comparison between two things that are very differently syntactically. A trailing comma after the last argument in a call is optional, but valid, Rust syntax. A comma token in some other arbitrary position (i.e. after the closing paren of a call and before the statement ending semicolon) is a completely different story, and is not valid syntactically.

But what about this,

You are attempting to make an invalid comparison between two things that are very differently syntactically. A trailing comma after the last argument in a call is optional, but valid, Rust syntax. A comma token in some other arbitrary position (i.e. after the closing paren of a call and before the statement ending semicolon) is a completely different story, and is not valid syntactically.

This compiles fine,
                ui.horizontal(|ui| {
                    ui.selectable_value(
                        &mut self.side_panel_section,
                        SidePanelSection::Browser,
                        "💻 Browser");
                    ui.selectable_value(
                        &mut self.side_panel_section,
                        SidePanelSection::Favorites,
                        "🖤 Favorites");
                });

But rustfmt does this to the section,
                ui.horizontal(|ui| {
                    ui.selectable_value(
                        &mut self.side_panel_section,
                        SidePanelSection::Browser,
                        "💻 Browser"),
                    ;
                    ui.selectable_value(
                        &mut self.side_panel_section,
                        SidePanelSection::Favorites,
                        "🖤 Favorites"),
                    ;
                });

and this doesn't compile.

Sorry but I don't follow what you're saying. You've been bouncing around between a few items, as well as inline snippets and videos on a thread that's gotten long.
It sounds like you are now claiming that there is a case where rustfmt is turning valid input into an invalid output. While that would indeed be a problem we'd need to address, there's a lack of clarity around the specifics.
If that's indeed what you're claiming, then I'll need you to provide a minimal and complete snippet (not a diff nor a screen video of an editor/IDE) that can be used to reproduce the claimed issue by running rustfmt directly against the snippet. If you're able to construct such a snippet then please feel free to post a comment here or open a new issue and we'll be happy to take a look.
Otherwise in the absence of such a reproducible example I don't think there's much more to be said on this thread.

Sorry but I don't follow what you're saying. You've been bouncing around between a few items, as well as inline snippets and videos on a thread that's gotten long.
It sounds like you are now claiming that there is a case where rustfmt is turning valid input into an invalid output. While that would indeed be a problem we'd need to address, there's a lack of clarity around the specifics.
If that's indeed what you're claiming, then I'll need you to provide a minimal and complete snippet (not a diff nor a screen video of an editor/IDE) that can be used to reproduce the claimed issue by running rustfmt directly against the snippet. If you're able to construct such a snippet then please feel free to post a comment here or open a new issue and we'll be happy to take a look.
Otherwise in the absence of such a reproducible example I don't think there's much more to be said on this thread.

I have been saying the same thing from start, that rustfmt was adding unnecessary stuff, it is what it did in my last response before this as well. Its just you told me for the problem I mentioned that, that was valid syntax.
Isn't my last response before this is a minimal snippet enough?


text:
update macro rewrite functions to return RewriteResult

Tracked by #6206
Description

update both rewrite_macro and rewrite_macro_def to return RewriteResult
add a new enum variant that represents macro rewrite failure

TODO
There are multiple reasons for macro formatting failure, and I have to make decisions on how to express them.

Looks like some of the self_tests are failing because of a long comment. In general its probably better to place comments directly above the code that you're trying to explain given the max_width constraints that rustfmt has.
---- test::self_tests stdout ----
error[internal]: line formatted, but exceeded maximum width (maximum: 100 (see `max_width` option), found: 105)
    --> src/macros.rs:1043:1043:101
     |
1043 |     let parsed_args = MacroArgParser::new().parse(token_stream).macro_error()?; // TODO macro parse error
     |                                                                                ^^^^^
     |
     = note: set `error_on_unformatted = false` to suppress the warning against comments or string literals

Thank you for the review! I’ve made the requested changes.

Running the Diff-Check

authors: ding-young ytmimi


text:
Link compiler major change proposal zulip threads

Right now, the triagebot will create a zulip thread when a compiler-team MCP is opened, but it doesn't link to that zulip thread from the compiler-team issue. It would be great for it to leave a comment like

Zulip thread
Archive

where the archive points to https://zulip-archive.rust-lang.org/

I think can be closed

Archive is no longer relevant, and the GitHub issue now links to the Zulip topic.

authors: Kobzol apiraino nikomatsakis

repo: rust-lang/triagebot


text:
Investigate web server integration

Find out how a possible web server integration could look like. Which crate could we use? What are possible implementations. Maybe add a prototype implementation to the current feature set.

For the start it mostly comes down to two implementation options.
CGI
CGI's are simply executables that are run by the webservers and print the html output to stdio. Parameters of the HTTP request are passed to the executable via environment variables (i.e user-agent, request url).
The following link shows a simple example implementation which doesn't require crates:
https://newspaint.wordpress.com/2016/06/16/creating-a-basic-cgi-executable-using-rust/
One or two crates seem to exist for this purpose as well. However i couldn't read into them yet since the domain that the documentation is hosted on seems to have fallen to a domain grabber.
Pro

Standardized interface that can be used with pretty much any webserver
Allows full use of features provided by the external webserver (authentication, caching, ...)

Con

Performance overhead (starting up the executable on every single request)

Embedded Webserver
This essentially means just writing our own webserver and embedding it into our executable.
Integration with existing webservers only would be possible via proxy passes.
Pro

Allows for best performance (primarily depending on our code)
Easy and fast to use, just fire up the executable.

Con

Requires socket handling, http parsing and so on to be handled by us.
Lacks advanced features found in webservers (or we have to code all of it ourselves)

Thank you very much for the feedback. I would like to go with the embedded variant. For this we could evaluate hyper and iron, two popular http libraries for rust. We could check which one of them will fit our needs best.

iron is the high level crate which allows pretty easy implementation of a webserver and would seem to be the one of choice here. hyper is lower level and is used within iron.
This iron example listens on port 3000 and returns "Hello World!" as response content while printing the requested url to stdio. In the simplest form we could just parse the request url and return the corresponding html page for a start.
extern crate iron;

use iron::prelude::*;
use iron::status;

fn httpd(req: &mut Request) -> IronResult<Response>
{
    println!("{}", req.url);
    Ok(Response::with((status::Ok, "Hello World!")))
}

fn main() {
    Iron::new(httpd).http("localhost:3000").unwrap();
}

Sounds pretty good. I think the usage of iron is straight forward and we could start implementing a first server for our generated files. Let's take this evaluation point to our next meeting.

Closed during the meeting decision that we want to go forward with embedded servers (iron crate).

authors: saschagrunert sschroe

repo: rust-leipzig/wiki

license: mit


text:
Add rsqrt method to Float trait

rsqrt is a widely used math function in game development, and is faster than combining the two functions: recip(sqrt(x)) thanks to x86 SSE instructions RSQRTSS, RSQRTPS, RSQRTSD, and RSQRTPD. Should we consider add rsqrt to Float trait?

x86/x86_64 SSE: _mm_rsqrt_ps (note that RSQRT instruction is approximate, less accurate than SQRT)
ARM Neon VRSQRTE
PowerPC Altivec: vec_rsqrte

This should probably be proposed for the standard library first.  So far we don't have any arch-specific code -- I'd rather just have num's impl Float for f64 forward to an optimized/intrinsic call in std.

I agree; it makes sense to offer this in libstd.

Reasonable, I'll propose it in rust-lang/rust.
I'll keep the issue open as reminder.

This issue was moved to rust-num/num-traits#1

authors: clarcharr cuviper davll

repo: rust-num/num


text:
Remove #![cfg_attr(feature = "const_fn", feature(const_in_array_repeat_expressions))]

As of (approximately) rust 1.52.0-nightly (a143517d4 2021-02-16), the const_in_array_repeat_expressions feature has been "removed due to causing promotable bugs." This therefore prevents the compilation of all uses of the x86_64 crate until this line is removed. I'm not sure if removing this line will impact compilation of the crate or not, or if any uses of the crate depends on it.

Update: so apparently a cargo update solved this problem. I thought it was an issue with the latest build but apparently its already been resolved. Apologies!


text:
Can it build on Linux to windows

I want to build on Linux to Windows, can it supports?

Yes, please see the README for instructions

Oh sorry, misunderstood your question. I thought you asked if it builds on Windows.
Building from Linux to Windows should work since we support Windows builds, but we don't have it documented.

😁Thank you very much for your reply. I would be very grateful if there are documents or construction guidelines.

I used the build tool: cargo-xwin  , and tried to run:
cargo xwin build --target x86_64-pc-windows-msvc

then, I got the failed info:
  = note: lld-link: error: could not open 'wpcap.lib': No such file or directory
          lld-link: error: could not open 'pcap.lib': No such file or directory

I have downloaded the SDK of WinPcap and copied wpcap.lib and packet.lib in the x64 directory to Linux. But I can't find pcap.lib

I'm no expert on cross-compiling so I can't help you here. However, I'll reopen the issue so that somebody else perhaps will see this and answer.

tks🌹

have you try use LIB env variable to pin point the location of wpcap.lib ?

have you try use LIB env variable to pin point the location of wpcap.lib ? also try to just put the file at the root of the project. Should work.

Yes, I tried it, it didn't work. I also tried to copy and rename wpcap.lib to pcap.lib, but it still failed with the error: lld-link: error: could not open 'pcap.lib': No such file or directory. I can't find pcap.lib.

You might try building with a build.rs (which puts the build information into the build process) instead of the manual environmental variable.  The following build.rs works for me on a "built for windows, on windows" build which I haven't tried from Linux, but should be a reasonable starting point.  It assumes the same directory structure as what comes out of the npcap dev libs, e.g., that if you want a x64 bit build, you want to use the "lib/x64" subdir.
robsh@LAPTOP-O7RS71IJ MINGW64 ~/git/go3x (main)
$ find lib/
lib/
lib/x64
lib/x64/Packet.lib
lib/x64/wpcap.lib

robsh@LAPTOP-O7RS71IJ MINGW64 ~/git/go3x (main)
$ ls build.rs
build.rs

$ cat build.rs
use std::env;
use std::path::Path;

fn main() {
    let dir = env::var("CARGO_MANIFEST_DIR").unwrap();
    println!(
        "cargo:rustc-link-search=native={}",
        Path::new(&dir).join("lib/x64").display()
    );
}

You might try building with a build.rs (which puts the build information into the build process) instead of the manual environmental variable. The following build.rs works for me on a "built for windows, on windows" build which I haven't tried from Linux, but should be a reasonable starting point. It assumes the same directory structure as what comes out of the npcap dev libs, e.g., that if you want a x64 bit build, you want to use the "lib/x64" subdir.
robsh@LAPTOP-O7RS71IJ MINGW64 ~/git/myproj (main)
$ find lib/
lib/
lib/x64
lib/x64/Packet.lib
lib/x64/wpcap.lib

robsh@LAPTOP-O7RS71IJ MINGW64 ~/git/myproj (main)
$ ls build.rs
build.rs

$ cat build.rs
use std::env;
use std::path::Path;

fn main() {
    let dir = env::var("CARGO_MANIFEST_DIR").unwrap();
    println!(
        "cargo:rustc-link-search=native={}",
        Path::new(&dir).join("lib/x64").display()
    );
}

@robs-zeynet thank you, i had tried it, but it not worked

authors: Stargateur TomatoMr Wojtek242 robs-zeynet

repo: rust-pcap/pcap


text:
Don't call cargo when skip_compilation? is true

This fixes a regression from #386 which made rustler_mix call cargo metadata even when skip_compilation? is set to true,
breaking setups in which the rust library is built separately, e.g. in separate docker stage with proper rust versioning and in which the elixir compilation stage doesn't have cargo.
This fix assumes that the external_resources attribute is irrelevant when skip_compilation? is set to true.

I wonder if we should instead skip calling into Rustler.Compiler.compile_crate/2 altogether if skip_compilation? is set.

@evnu makes sense to me.

I think we should go ahead with this PR as is and release a patch version, and refactor later.

@karolsluszniak I released v0.22.2 with this fix. Thanks again!

authors: evnu karolsluszniak

repo: rusterlium/rustler


text:
[Feature Request] support v-blur

like https://shopify.github.io/react-native-skia/docs/image-filters/blur/

:blur :grayscale :brighten :invert will be support in v-image!
https://github.com/rustq/vue-skia/pull/29

repo: rustq/vue-skia


text:
implements bindings for Object.is

I've been quite busy lately, but doing my best to keep up with the latest changes :)

Awesome, thanks!

authors: alexcrichton belfz

repo: rustwasm/wasm-bindgen


text:
Might want to change PointConv name in the framework

There is a quite recent paper which cam out at cvpr 2019 : https://arxiv.org/abs/1811.07246, called PointConv. Just to avoid confusion, it could be helpful to rename the PointConv operation in the framework.

Good point. Thank you!

I would like to up the topic as I got confused too

Any alternative naming proposals? PointNetConv?

PnConv or PointNetConv could be cool !

I renamed the PointConv to PointNetConv, see https://github.com/rusty1s/pytorch_geometric/commit/a675ef9750d034908f52d9a5fe7687b06dec3ecc.
I will deprecate PointConv in the next release and will remove it afterwards.

authors: QuanticDisaster lelouedec rusty1s


text:
fix ruyisdk/pmd#11 : 多语言支持

多语言支持：当前只要求支持English
需要提前预留位置和确定技术方案以防改造过于高难度。

目前准备使用 Project Fluent 实现本地化。重构待进行

repo: ruyisdk/ruyi


text:
keyd doesn't capture the power button

I'm trying to left behind the ubuntu keyboard shortcuts and the only one I can't replace is the control+power to reboot my machine.
When I run sudo keyd -m and then press the power button, I have nothing in capture screen.

@herrsimon is correct. Most power buttons emit ACPI events which never propagate to userspace in form of input events.

authors: crimuvi rvaiya

repo: rvaiya/keyd


text:
Fix no .git commondir in submodule repos

Hi, there.
I found v0.13.0 breaks in a submodule repo.
same as https://github.com/rwjblue/git-repo-info/issues/27
and https://github.com/TryGhost/Ghost/issues/7614
Recently, I installed Ghost with a developer install,
When I run grunt init, it returns
>> Ran "grunt init" in "core/client".

Running "clean:tmp" (clean) task
>> 0 paths cleaned.

Running "subgrunt:dev" (subgrunt) task
Running "shell:ember:dev" (shell) task

> ghost-admin@1.0.0-alpha.5 build /Users/zhangbinliu/my_web_dev/Cool4zbl.com/myDevGhost/core/client
> ember build

ENOENT: no such file or directory, open '../../.git/modules/core/client/commondir'
Error: ENOENT: no such file or directory, open '../../.git/modules/core/client/commondir'
    at Error (native)
    at Object.fs.openSync (fs.js:549:18)
    at Object.fs.readFileSync (fs.js:397:15)
    at findRepoHandleLinkedWorktree (/Users/zhangbinliu/my_web_dev/Cool4zbl.com/myDevGhost/core/client/node_modules/git-repo-info/index.js:27:32)
    at findRepo (/Users/zhangbinliu/my_web_dev/Cool4zbl.com/myDevGhost/core/client/node_modules/git-repo-info/index.js:47:14)
    at module.exports (/Users/zhangbinliu/my_web_dev/Cool4zbl.com/myDevGhost/core/client/node_modules/git-repo-info/index.js:145:21)
    at version (/Users/zhangbinliu/my_web_dev/Cool4zbl.com/myDevGhost/core/client/node_modules/git-repo-version/index.js:11:14)
    at CoreObject.module.exports.config (/Users/zhangbinliu/my_web_dev/Cool4zbl.com/myDevGhost/core/client/node_modules/ember-cli-app-version/index.js:10:46)
    at CoreObject.superWrapper [as config] (/Users/zhangbinliu/my_web_dev/Cool4zbl.com/myDevGhost/core/client/node_modules/core-object/lib/assign-properties.js:32:18)
    at /Users/zhangbinliu/my_web_dev/Cool4zbl.com/myDevGhost/core/client/node_modules/ember-cli/lib/models/project.js:224:29

npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/bin/node" "/Users/zhangbinliu/my_web_dev/Cool4zbl.com/myDevGhost/core/client/node_modules/.bin/npm" "run" "build"
npm ERR! node v4.2.1
npm ERR! npm  v2.15.5
npm ERR! code ELIFECYCLE
npm ERR! ghost-admin@1.0.0-alpha.5 build: `ember build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ghost-admin@1.0.0-alpha.5 build script 'ember build'.
npm ERR! This is most likely a problem with the ghost-admin package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ember build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ghost-admin
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls ghost-admin
npm ERR! There is likely additional logging output above.

That sounds strange, so I dug in and found
https://github.com/ember-cli/ember-cli/blob/master/lib/utilities/version-utils.js#L5
Ghost requires Ghost-Admin, Ghost-Admin requires ember-cli,
and finally, ember-cli  requires this repo.
If there is a submodule repo,  in this PR commondir may not exists.
So I just added some conditions and fix the problem.
>> Ran "grunt init" in "core/client".

Running "clean:tmp" (clean) task
>> 0 paths cleaned.

Running "subgrunt:dev" (subgrunt) task
Running "shell:ember:dev" (shell) task

> ghost-admin@1.0.0-alpha.5 build /Users/zhangbinliu/my_web_dev/Cool4zbl.com/myDevGhost/core/client
> ember build

Built project successfully. Stored in "dist/".

Done.
>> Ran "grunt shell:ember:dev" in "core/client".

Done.

However, there's already a PR for SHA of a submodule (also a better solution),
the condition that if the file exists should be considered.
@rwjblue
Please review, thanks.

@cool4zbl This should be fixed in v1.3.1.  Can you please confirm that ghost is working for you in v1.3.1?

@hjdivad
Of course.
I did this hack core and run ghost init again,
then it worked fine and returned done info just like I posted above.
😃
So, please review, thanks.

closed by https://github.com/rwjblue/git-repo-info/pull/29 and released in v0.13.1

authors: cool4zbl hjdivad rwjblue

repo: rwjblue/git-repo-info


text:
Add Support for 'checkItemStates' in GetCardOptions

https://developer.atlassian.com/cloud/trello/rest/api-group-cards/#api-cards-id-get

It seems this setting does not do anything, so closed until someone can explain what it actually does

repo: rwjdk/TrelloDotNet


text:
CardCover Color Not added for new card

Using AddCardAsync example, card cover is not added.
newAdvancedCard.Cover = new CardCover(CardCoverColor.Blue, CardCoverSize.Normal);
Card created but the cover is not added.

Hi @accjon . Thank you for reporting this bug... It is indeed not adding the Cover, but I've just fixed this in the code so NuGet Package 1.10.0 will resolve the issue (available in a few minutes).

Thanks @rwjdk! That was quick!!

authors: accjon rwjdk


text:
Update German Locale

The german Multiplayer.xml was adapted to the newest changes. New translations added.

Thanks a lot!

authors: Maxsiom Zetrith

repo: rwmt/Multiplayer-Locale


text:
Create 0000-01-02-rwsandstrom.md

comment for "Create ...rwsandstrom.md"

comment when confirming merge of PR3

repo: rwsandstrom/github-slideshow


text:
how to go to the next occurrence of the desired pattern?

Once you find a match, press Ctrl+D to jump to the next occurrence if there's any. This works also without having to use Find Text specifically by just highlighting some piece of code.
Note that in other code editors the same shortcut Ctrl+D will not only jump but also select (it creates a new cursor) the next occurrence. I still haven't found a way to do that in Lite, though I hope it's enabled soon.

Once you find a match, press Ctrl+D to jump to the next occurrence if there's any. This works also without having to use Find Text specifically by just highlighting some piece of code.
Note that in other code editors the same shortcut Ctrl+D will not only jump but also select (it creates a new cursor) the next occurrence. I still haven't found a way to do that in Lite, though I hope it's enabled soon.

To do that with find text I just press Ctrl+F and enter multiple times

To do that with find text I just press Ctrl+F and enter multiple times

Thx!

Thx!

authors: drmargarido herokunt peach-lasagna

repo: rxi/lite


text:
[VictoriaMetrics] vmagent remote write - duplicate sample for timestamp xxx; overrides not allowed

Logs:
2024-08-26T09:32:47.346Z    error    VictoriaMetrics/app/vmagent/remotewrite/client.go:446    sending a block with size 398970 bytes to "1:secret-url" was rejected (
skipping the block): status code 400; response body: duplicate sample for timestamp 1724664766445; overrides not allowed: existing 1379, new value 3342
2024-08-26T09:32:52.747Z    error    VictoriaMetrics/app/vmagent/remotewrite/client.go:446    sending a block with size 392222 bytes to "1:secret-url" was rejected (
skipping the block): status code 400; response body: duplicate sample for timestamp 1724664766445; overrides not allowed: existing 11394, new value 34
2024-08-26T09:33:00.962Z    error    VictoriaMetrics/app/vmagent/remotewrite/client.go:446    sending a block with size 390841 bytes to "1:secret-url" was rejected (
skipping the block): status code 400; response body: duplicate sample for timestamp 1724664772645; overrides not allowed: existing 1, new value 0
2024-08-26T09:33:03.446Z    error    VictoriaMetrics/app/vmagent/remotewrite/client.go:446    sending a block with size 393029 bytes to "1:secret-url" was rejected (
skipping the block): status code 400; response body: duplicate sample for timestamp 1724664782607; overrides not allowed: existing 0.3810720109998354, new value 0.40
62051349998865

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."


text:
Python 3.6 (nightly) problem

Only my Python 3.6 build fails (here: https://travis-ci.org/jayvdb/csl-data/jobs/108199025 ) with
$ pip install tox-travis
Collecting tox-travis
  Downloading tox_travis-0.3-py2.py3-none-any.whl
Collecting tox>=2.0 (from tox-travis)
  Downloading tox-2.3.1-py2.py3-none-any.whl (40kB)
    100% |████████████████████████████████| 40kB 7.8MB/s
Collecting virtualenv>=1.11.2 (from tox>=2.0->tox-travis)
  Downloading virtualenv-14.0.6-py2.py3-none-any.whl (1.8MB)
    100% |████████████████████████████████| 1.8MB 368kB/s
Requirement already satisfied (use --upgrade to upgrade): py>=1.4.17 in /home/travis/virtualenv/python3.6-dev/lib/python3.6/site-packages (from tox>=2.0->tox-travis)
Collecting pluggy<0.4.0,>=0.3.0 (from tox>=2.0->tox-travis)
  Downloading pluggy-0.3.1-py2.py3-none-any.whl
Installing collected packages: virtualenv, pluggy, tox, tox-travis
Successfully installed pluggy-0.3.1 tox-2.3.1 tox-travis-0.3 virtualenv-14.0.6
$ tox

Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.6-dev/bin/tox", line 11, in <module>
    sys.exit(cmdline())
  File "/home/travis/virtualenv/python3.6-dev/lib/python3.6/site-packages/tox/session.py", line 38, in main
    config = prepare(args)
  File "/home/travis/virtualenv/python3.6-dev/lib/python3.6/site-packages/tox/session.py", line 26, in prepare
    config = parseconfig(args)
  File "/home/travis/virtualenv/python3.6-dev/lib/python3.6/site-packages/tox/config.py", line 208, in parseconfig
    pm.hook.tox_addoption(parser=parser)
  File "/home/travis/virtualenv/python3.6-dev/lib/python3.6/site-packages/pluggy.py", line 724, in __call__
    return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
  File "/home/travis/virtualenv/python3.6-dev/lib/python3.6/site-packages/pluggy.py", line 338, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/home/travis/virtualenv/python3.6-dev/lib/python3.6/site-packages/pluggy.py", line 333, in <lambda>
    _MultiCall(methods, kwargs, hook.spec_opts).execute()
  File "/home/travis/virtualenv/python3.6-dev/lib/python3.6/site-packages/pluggy.py", line 596, in execute
    res = hook_impl.function(*args)
  File "/home/travis/virtualenv/python3.6-dev/lib/python3.6/site-packages/tox_travis.py", line 32, in tox_addoption
    desired_envs = get_desired_envs(config, version)
  File "/home/travis/virtualenv/python3.6-dev/lib/python3.6/site-packages/tox_travis.py", line 62, in get_desired_envs
    return split_env(travis_section.get(version, TOX_DEFAULTS.get(version)))
  File "/home/travis/virtualenv/python3.6-dev/lib/python3.6/site-packages/tox/config.py", line 801, in _split_env
    if '\n' in env:
TypeError: argument of type 'NoneType' is not iterable

It might be a tox bug, but if it is then I hope tox-travis can work around it.

Can you also post the tox section of your tox.ini?

It is as boring as it gets.
https://github.com/jayvdb/csl-data/blob/767bc9d2cc3608d9a23932e0ae28ba0df9ec7b5c/.travis.yml
language: python

python:
  - "2.7"
  - "3.3"
  - "3.4"
  - "3.5"
  - "nightly"

install:
  - pip install tox-travis

script:
  - tox

notifications:
  email: false

Do I need to include py36 in tox.ini ?

I don't think that you'll need to do that, though you may decide that you should. Do you want 3.6 to run on your local tox runs?
My main question is what the value of the TRAVIS_PYTHON_VERSION environment variable is during this run. If it's 3.6, then I can (and should) add that to the default configuration, so that it just works.
Unfortunately, I suspect that it will simply be nightly, and there's no good way for me keep nightly in sync with what's actually nightly at any given time.
Try adding this section to your tox.ini, and please let me know if it works:
[tox:travis]
nightly = py36

And I'm going to see about adding a better error message if/when this gets hit in the future.

Having everyone add
[tox:travis]
nightly = py36

multiplies the problem of keep "nightly" in sync.  We expect that tox-travis understands tox and Travis CI for us. ;-)
#11 is brilliant.

authors: jayvdb ryanhiebert

repo: ryanhiebert/tox-travis


text:
xsession: add numlock module

Resolves #651
Not sure how to support Darwin for this, if that's an issue.
The only other concern I have is how well it might play with other DEs or WMs, aside from what I'm currently using (verified working on xmonad + gdm).
Please let me know if there's anything else I'm missing.

Thanks! Rebased to master in e59b8b0c37f08f6b6a9399b24e9b67d90c9b8436.

authors: evanjs rycee

repo: rycee/home-manager


text:
Open AI Activity Summaries

Is your feature request related to a problem? Please describe.
I wanted to generate a text summary of my recent activity using GPT-3 / Open AI, and have my profile automatically updated.
Describe the solution you'd like
I built this kinda hacky solution here: https://github.com/OR13/OR13/blob/main/.github/workflows/weekly.yml
Here is an example of the revisions it publishes weekly: https://github.com/OR13/OR13/commit/bbc7674e401f640f6099cadfbd5dc018fd6f96f1
I would welcome any feedback on it / for it to be supported by a team /  group with more time.
Describe alternatives you've considered
I think many of the examples in this repo are good alternatives, especially the ones summarizing activity.
Additional context
This is kinda just an FYI that this is possible, I'm happy to collaborate on it if folks are interested, but I'm also happy to just have it closed.

Hello my friend
You made a very good tool, whenever you like, tell me to add it to the list of this repository for everyone to use 👌

Is your feature request related to a problem? Please describe.
I wanted to generate a text summary of my recent activity using GPT-3 / Open AI, and have my profile automatically updated.
Describe the solution you'd like
I built this kinda hacky solution here: https://github.com/OR13/OR13/blob/main/.github/workflows/weekly.yml
Here is an example of the revisions it publishes weekly: OR13/OR13@bbc7674
I would welcome any feedback on it / for it to be supported by a team / group with more time.
Describe alternatives you've considered
I think many of the examples in this repo are good alternatives, especially the ones summarizing activity.
Additional context
This is kinda just an FYI that this is possible, I'm happy to collaborate on it if folks are interested, but I'm also happy to just have it closed.

Hello my friend
You made a very good tool, whenever you like, tell me to add it to the list of this repository for everyone to use 👌

repo: rzashakeri/beautify-github-profile


text:
Release an artifact without the ShadowClassLoader for compiling custom handlers

This was suggested by David Nelson on and mailing list and I believe it would provide a much more consistent environment for developing extensions.  His rationale is pretty extensive and can be found at https://groups.google.com/forum/#!searchin/project-lombok/shadowclassloader/project-lombok/LK975m4cGig/qdeTq3ZkoBYJ.
As an aside, Reinier Zwitserloot asked that this issue be created in that thread - I couldn't find it but hope I'm not somehow overstepping my bounds.
Thanks!

I really like the idea. Is there any plan for that?

I believe we added this now, otherwise, see issue 1927.

@rzwitserloot Can you provide an example of how Lombok is now easier to extend?  I've been playing around with the technique used by the Maven plugin but that's really opaque.  Is there documentation?  Or even just a couple bullet points to start in the right direction?

authors: RomainPiel rzwitserloot smoyer64

repo: rzwitserloot/lombok


text:
@Jacksonized: modify generated @(Super)Builders such that they will be used by Jackson's deserialization

This PR implements the proposal discussed here.
Adding @Jacksonized to a context where there is also a @Builder or @SuperBuilder annotation does the following:

Configure Jackson to use the builder for deserialization using @JsonDeserialize(builder=MyClass.MyClassBuilder[Impl].class)) on the class. (An error is emitted if such an annotation already exists.)
Copy Jackson-related configuration annotations (like @JsonIgnoreProperties) from the class to the builder class. This is necessary so that Jackson recognizes them when using the builder.
Insert @JsonPOJOBuilder(withPrefix="") on the generated builder class to override Jackson's default prefix "with". If you configured a different prefix in lombok using setterPrefix, this value is used. If you changed the name of the build() method using using buildMethodName, this is also made known to Jackson.
For @SuperBuilder, make the builder implementation class package-private.

There is one minor difference to the proposal (with regard to step 1.): If there is already a @JsonDeserialize annotation on the class, it will give an error. The reason is that all other parameters of @JsonDeserialize are only useful when not using a builder; often they will even contradict the usage of a builder. So I though it is reasonable to error out then and let the user decide what to do.
I did not yet write documentation for the website, because I didn't where to place it (there is no "external" section in the site). I propose adding it as "experimental".

I pushed two new commits to the branch/PR:

add flag usage configuration key (I just noticed I forgot this)
add documentation and changelog entry

This is amazing work, @janrieke – all I really had to do was think of a funny byline :)

authors: janrieke rzwitserloot


text:
Added ability to handle named anchors

I noticed that in recursive scraping, it didn't correctly add the named anchor links, it just changed the link to the page name.
i.e. all links with www.example.com/page.html#id would become path/to/file/page.html, not  path/to/file/page.html#id
I fixed this by concatenating the source attribute to the relative path in html.js

Hi, @Sporks.
Thank you for your PR.
I'll review changes when I'll have some free time, possibly next week.

Thanks a bunch.  I noticed it wasn't working on expressjs.com/api for
example.
On Tue, Feb 9, 2016 at 8:59 AM, Sophia Nepochataya <notifications@github.com

wrote:

Hi, @Sporks https://github.com/Sporks.
Thank you for your PR.
I'll review changes when I'll have some free time, possibly next week.
—
Reply to this email directly or view it on GitHub
https://github.com/s0ph1e/node-website-scraper/pull/17#issuecomment-181956335
.

Hi again
I have few comments regarding your changes:

need to add unit tests
your implementation handles only case when # is a first char. But # can be in the middle of the string, for example:

link

I suggest to add method getHashFromUrl to utils which will use node core module url and return url.parse(string).hash

no need to keep # for all resources. It makes sense only for html resources. To check resource type you can use method getType

In the result I'd like to see something like this:

var hash = utils.getHashFromUrl(attr);
if (hash && loadedResource.getType() == types.html) {
  relativePath = relativePath.concat(hash);
}
el.attr(source.attr, relativePath);

@Sporks can you please update your PR according to comments above? If you can't I'll fix this bug later. Thanks.

Thanks for the feedback, I will see what I can do.  I am knees deep in
another project at the moment though!
On Wed, Feb 17, 2016 at 12:01 PM, Sophia Nepochataya <
notifications@github.com> wrote:

Hi again
I have few comments regarding your changes:

need to add unit tests
your implementation handles only case when # is a first char. But #
can be in the middle of the string, for example:

link
I suggest to add method getHashFromUrl to utils
https://github.com/s0ph1e/node-website-scraper/blob/master/lib/utils.js
which will use node core module url and return url.parse(string).hash

no need to keep # for all resources. It makes sense only for html
resources. To check resource type you can use method getType
https://github.com/s0ph1e/node-website-scraper/blob/master/lib/resource.js#L75
In the result I'd like to see something like this:
var hash = utils.getHashFromUrl(attr);if (hash && loadedResource.getType() == types.html) {
relativePath = relativePath.concat(hash);
}el.attr(source.attr, relativePath);
@Sporks https://github.com/Sporks can you please update your PR
according to comments above? If you can't I'll fix this bug later. Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/s0ph1e/node-website-scraper/pull/17#issuecomment-185379148
.

fixed in 448514fe61f9c48a5f8df2d165852979567bb09c
released in version 0.3.2


text:
There are tasks that ESPNET does with S3PRL that fail

File "/media/shiyanshi/E/espnet/espnet2/asr/frontend/s3prl.py", line 26, in init
import s3prl.nn
ModuleNotFoundError: No module named 's3prl.nn'
Error: S3PRL is not properly installed.
Please install S3PRL: cd ${MAIN_ROOT}/tools && make s3prl.done
But S3PRL is successfully installed and can also be imported successfully in the terminal，How do I fix it?

Hi, can you try to pip show s3prl to see its version?
Please upgrade to the latest version v0.4.4

Already the latest version 0.4.4：

Are you sure the environment the ESPNET recipe evokes is the same as the one you use when trying in the terminal?
Like, they are the same conda environment right? I remember ESPNET is using activate_python.sh to assign the conda env.

Yes, I've tried it, but it still doesn't work.

Oh, I guess I know the reason.
You are using older version of ESPNet.
Could you try to upgrade ESPNet repo to be newer than this commit?
https://github.com/espnet/espnet/commit/0a62508814792bc4afb7991f152fa0ea75c7c863

Okay, the power in the laboratory has been cut off... I'll get back to you when I try tomorrow morning. Thank you.

espnet was updated, but new issues appeared in stage10 in espnet2
Traceback (most recent call last):
File "/home/shiyanshi/anaconda3/envs/espnet1/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/shiyanshi/anaconda3/envs/espnet1/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/media/shiyanshi/F/2021_s/espnet/espnet2/bin/asr_train.py", line 23, in
main()
File "/media/shiyanshi/F/2021_s/espnet/espnet2/bin/asr_train.py", line 19, in main
ASRTask.main(cmd=cmd)
File "/media/shiyanshi/F/2021_s/espnet/espnet2/tasks/abs_task.py", line 1019, in main
cls.main_worker(args)
File "/media/shiyanshi/F/2021_s/espnet/espnet2/tasks/abs_task.py", line 1121, in main_worker
model = cls.build_model(args=args)
File "/media/shiyanshi/F/2021_s/espnet/espnet2/tasks/asr.py", line 417, in build_model
frontend = frontend_class(**args.frontend_conf)
File "/media/shiyanshi/F/2021_s/espnet/espnet2/asr/frontend/s3prl.py", line 46, in init
upstream = S3PRLUpstream(
File "/home/shiyanshi/anaconda3/envs/espnet1/lib/python3.9/site-packages/s3prl/nn/upstream.py", line 96, in init
self.upstream = getattr(hub, name)(
File "/home/shiyanshi/anaconda3/envs/espnet1/lib/python3.9/site-packages/s3prl/upstream/hubert/hubconf.py", line 33, in hubert_local
return hubert_custom(*args, **kwargs)
File "/home/shiyanshi/anaconda3/envs/espnet1/lib/python3.9/site-packages/s3prl/upstream/hubert/hubconf.py", line 22, in hubert_custom
if ckpt.startswith("http"):
AttributeError: 'NoneType' object has no attribute 'startswith'
Accounting: time=6 threads=1
Ended (code 1) at Fri Sep 30 22:05:12 CST 2022, elapsed time 6 seconds

espnet was updated, but new issues appeared in stage10 in espnet2：
Traceback (most recent call last):
File "/home/shiyanshi/anaconda3/envs/espnet1/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/shiyanshi/anaconda3/envs/espnet1/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/media/shiyanshi/F/2021_s/espnet/espnet2/bin/asr_train.py", line 23, in
main()
File "/media/shiyanshi/F/2021_s/espnet/espnet2/bin/asr_train.py", line 19, in main
ASRTask.main(cmd=cmd)
File "/media/shiyanshi/F/2021_s/espnet/espnet2/tasks/abs_task.py", line 1019, in main
cls.main_worker(args)
File "/media/shiyanshi/F/2021_s/espnet/espnet2/tasks/abs_task.py", line 1121, in main_worker
model = cls.build_model(args=args)
File "/media/shiyanshi/F/2021_s/espnet/espnet2/tasks/asr.py", line 417, in build_model
frontend = frontend_class(**args.frontend_conf)
File "/media/shiyanshi/F/2021_s/espnet/espnet2/asr/frontend/s3prl.py", line 46, in init
upstream = S3PRLUpstream(
File "/home/shiyanshi/anaconda3/envs/espnet1/lib/python3.9/site-packages/s3prl/nn/upstream.py", line 96, in init
self.upstream = getattr(hub, name)(
File "/home/shiyanshi/anaconda3/envs/espnet1/lib/python3.9/site-packages/s3prl/upstream/hubert/hubconf.py", line 33, in hubert_local
return hubert_custom(*args, **kwargs)
File "/home/shiyanshi/anaconda3/envs/espnet1/lib/python3.9/site-packages/s3prl/upstream/hubert/hubconf.py", line 22, in hubert_custom
if ckpt.startswith("http"):
AttributeError: 'NoneType' object has no attribute 'startswith'

Do you set the config like this?
https://github.com/espnet/espnet/blob/14fcb2d42b2609f766ffaa7a79e9c921cd8398d9/egs2/librispeech/asr1/conf/tuning/train_asr_conformer7_hubert_ll60k_large.yaml#L18-L23
It seems the name you pass into the s3prl frontend is None

My configuration is as follows:
network architecture
pretrained model related
freeze_param: [
"frontend.upstream"
]
frontend: s3prl
frontend_conf:
frontend_conf:
upstream: hubert_local
upstream_model_config:
upstream_ckpt: /media/shiyanshi/F/2021_s/chinese-hubert-base/chinese-hubert-base.pt
download_dir: ./hub
multilayer_feature: true
preencoder: linear
preencoder_conf:
input_size: 768  # Note: If the upstream is changed, please change this value accordingly.
output_size: 80
encoder related
encoder: conformer
encoder_conf:
output_size: 256    # dimension of attention
attention_heads: 4
linear_units: 2048  # the number of units of position-wise feed forward
num_blocks: 12      # the number of encoder blocks
dropout_rate: 0.1
positional_dropout_rate: 0.1
attention_dropout_rate: 0.0
input_layer: conv2d2 # encoder architecture type
normalize_before: true
rel_pos_type: latest
pos_enc_layer_type: rel_pos
selfattention_layer_type: rel_selfattn
activation_type: swish
cnn_module_kernel: 15

Oh... I think usually we do not expect to use custom pre-trained model with this frontend. I expect that this checkpoint is pre-trained from fairseq right? Currently we do not support hubert_local to load checkpoint from fairseq since this will require to install fairseq, which is a dependency we are trying to remove. We will support to directly load the fairseq-pretrained checkpoint in the upcoming release. However, this is not supported right now.

However, if you want, you can try to convert your checkpoint with this script:
https://github.com/s3prl/s3prl/blob/main/s3prl/upstream/hubert/convert.py
and the converted checkpoint can be loaded with hubert_local

thank you!

I'm sorry, but since I'm just getting started, I have to disturb you, the converted output path is empty, and how to set the configuration file~    /qaq

Hi @leo19941227, could we still load custom pretrained models from huggingface? In the old versions, I could easily do this by add entries in wav2vec2_hug/hubconf.py :). Thanks in advance!

Hi, oh I removed that entry since previously it is kind of a duplicate function to the fairseq version and the fairseq version is somehow faster. But I will consider adding it back, since I also notice that there are many new pre-trained wav2vec2/hubert weights released in the huggingface format, and adding this entry back is not just duplication of the fairseq version, but enabling much more pre-trained models. Thanks for brining this up!

但是，如果您愿意，您可以尝试使用以下脚本转换您的检查点：
https://github.com/s3prl/s3prl/blob/main/s3prl/upstream/hubert/convert.py
并且可以加载转换后的检查点hubert_local

Hi, I had the same problem, I was using converted checkpoints and the problem was not resolved.

However, if you want, you can try to convert your checkpoint with this script:
https://github.com/s3prl/s3prl/blob/main/s3prl/upstream/hubert/convert.py
and the converted checkpoint can be loaded with hubert_local

Hi, I had the same problem, I was using converted checkpoints and the problem was not resolved.

I believe this issue is improved in #443, so I am closing it for now.
Feel free to re-open it if it does not fit your need. Thanks!

authors: abcdbosh bofenghuang leo19941227 sendream


text:
fix: Replace link to docs

This PR will replace wrong link in index.html.
Closes #993

Great thank you!
@all-contributors please add @redpfire for code and bug

authors: redpfire shahednasser

repo: sButtons/sbuttons


text:
bug: (feature request) I'd like to be able to disable themes on the fly using data-theme="disabled".

What version of daisyUI are you using?
latest npm package
Describe your issue
I'd like to be able to disable the theme dynamically using an html flag so that I can embed apps in transparent iFrames more easily.
Currently when the default themes are present, the entire page is styled according to the chosen theme and I can't seem to be able to override any styles. I tried using
* {
    background-color: white !important;
}

or
* {
    background-color: transparent !important;
}

but the styles remain untouched. This affects how the app is shown inside an iframe.
If I were to disable all themes using
  daisyui: {
    themes: []
  }

then the iFrame is transparent and it blends in well with the parent page. This affects how the app looks like when it is not inside an iFrame.
If I could set the data-theme="disabled" on  the html element, then I could use some JS to detect whether or not the app is inside an iFrame and change themes accordingly.

Could I have my cake and eat it too, please?
What browsers are you seeing the problem on?
All browsers
Reproduction URL (optional)
No response

So the problem is not the theme, you just want the background of the page (iframe) to be transparent?

I think you should use some JS to detect if it's iframe or not. I don't think that's possible with CSS.
but to make the background transparent, you can add bg-transparent to the <html> tag.

repo: saadeghi/daisyui


text:
fix: pin packages and replace nightly adapter

This pull request does two things:
First, it adds resolutions for the version of various @ledgerhq/* packages being used to fix this issue.
Second, replaces the nightlylabs custom wallet adapter with the solana standard nightlylabs adapter. This fixes another issue I was getting with testing and makes the adapters more consistent.

@michaelhly Anything I can do to help with the review?

@michaelhly would it be possible to get a release?

repo: saber-hq/saber-common


text:
Run saber server on 3001 port if 3000 is being used

Feature request

What problem does this feature solve?
Running saber server whiteout passing a port argument while the port 3000 is being used break the app
What does the proposed API look like?
Run the server on the port 3001 automatically
How should this be implemented in your opinion?
N/A
Are you willing to work on this yourself?
YES

We already have --port option, this looks unnecessary somewhat.

@kidonng but it's much more elegant if Saber just binds itself to an available port instead of crashing whenever 3000 is already used.

Running multiple dev server is rare, it's common to show a message notifying the port is taken. Though I agree Saber shouldn't crash 😂

authors: MarchWorks kidonng krmax44

repo: saberland/saber


text:
feat: add support for typescript pages and components

Summary

Closes #128
You can now write .ts and .tsx pages in ./pages folder, <script lang="ts"> is also supported in .vue pages and normal .vue components.
This is implemented with @babel/preset-typescript, so it does transformation without type checking.

Following features will be introduced in the future.
TODOs:

[ ] Detect tsconfig.json and if it exists:

[ ] Use fork-ts-checker-webpack-plugin for type-checking
[ ] Automatically generate saber-env.d.ts to include types for saber/config etc

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Build-related changes
[ ] Other, please describe:

If changing the UI/CSS related code, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] Briefly describing what this PR does in the title in Angular Commit Message Conventions, e.g. fix: rebuild when a page is added

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:

Any ETA on when we could expect this to get merged?

authors: egoist lahdekorpi


text:
Question about default standard style rules in iOS

Thanks for the package. Shall we include default standard style rules for iOS written in css (e.g. default colors, font sizes)? I think it'll be very helpful.

@menway can you explain it more? if you feel something should be added, please fork and I would be happy to accept pull requests.
glad you like it, please tell me if you require more requires. I am thinking of making this use sass, so we can have variables etc.

authors: menway sabeurthabti

repo: sabeurthabti/react-native-css


text:
Can I download file with album cover

Which tool
Can I download file with album cover
Describe your question
Can I download file with album cover
Add screenshots
Can I download file with album cover

Any example URL ?

No that's not I need when I download original track it's download with cover when I play on music player it's showing with song name and cover

Use this https://github.com/yaronzz/Tidal-Media-Downloader


text:
accept finalized param in signPsbt for unisat

Context:
Unisat support signPsbt with optional option to finalize or not. https://docs.unisat.io/dev/unisat-wallet-api#signpsbt
we should support that option as well.

Added support for finalize option in ordit.unisat.signPsbt fn; https://github.com/sadoprotocol/ordit-sdk/commit/7e7d9ca86447f15880678ad805f8202b20954732 in #30

authors: iamcrazycoder kevzzsk

repo: sadoprotocol/ordit-sdk


text:
feat(polymer): make the element hybrid

Before this commit the element was only usable inside projects using
Polymer 1. Now, the element is turned hybrid so it also can be used
inside Polymer 2 projects.

Unit test are not passing I agree, but it drives me crazy because they were never not really executed (see #35) and I need this web component in a Polymer 2 app asap.

@masonlouchart Thank you for efforts. But I we should not break the master branch. I can't merge it into the master branch unless all tests pass.

@masonlouchart I fixed running unit tests. Please do reverse merge from the master branch (or
do rebase) to make sure all tests passed.

Damn, I worked on unit tests the all night. 😕
I took a look at your fix and I think we can just execute the content of the callback defined in all listeners instead of fire the event manually.
Please see below my proposal and comment on it:
Change setup
setup(function(done) {
	myEl = fixture('moment-js-fixture');
    if (myEl.isMomentReady) {
    	done();
    } else {
    	myEl.addEventListener('moment-is-ready', function () {
        	// Wait the element is ready before perform unit test.
        	done();
    	});
    }
});

Remove listener from unit test
test('ISO Date is valid', function() {
	myEl.set('date', '2011-10-10T10:20:30');
    assert.equal('2011-10-10T10:20:30', myEl.date);
    assert.isTrue(myEl.isValid);
});

test('ISO Date is not valid', function() {
	myEl.set('date', '2011-10-10T10:20:90');
    assert.isFalse(myEl.isValid);
});

// ...

The difference is in your solution, because of the event, the element recomputes its date. Not in mine. That introduces "interesting" issues like changing the format does not automatically recompute the formatted date.
I think observers are not working because to fix my new issues I had to call them manually inside the good functions (dateChanged, formatChanged, etc...). But it's another topic.

I rebased my branch but still have an issue with unit test on shared locale setting. I'll push soon.

Polymer 2 and Firefox 57 seem not be friends... 😕 .
Anyone see what I missed?

Polymer v2 is not loaded in Firefox (hybrid element is working with Polymer v1).

NB: when you run unit test suite with polymer test -l firefox -p it can happens that there is no logs in the console. Just refresh Firefox page to see them...

I guess it's related to https://github.com/webcomponents/webcomponentsjs/issues/699

🆘 Help wanted to make the element work with Polymer 2 on Firefox 57+.

@masonlouchart We could ship a new major version of this element which only supports Polymer 2 instead of hybrid support. Is it helpful?

It could help. I think using the web-components-loader will solve the issue with Firefox 57.
Do you prefer a new PR or just a commit (on this branch) that turns the element into class?

@masonlouchart Please keep working on this branch. I will release it as a new major version which only supports Polymer 2.x. Please also remove unnecessary codes of Polymer 1.x.
Thanks a lot.

Hi @saeidzebardast ,
I didn't have yet migrated the element but I tested Polymer 2 with webcomponentsjs-loader on Firefox 57 and it didn't work. 😕
I don't like the idea of lose hour(s) to migrate the element and get the same result...
I'll push a commit to improve locales file loading and language setting sharing. Expect Travis complain about the UT because, you know... FFF... (the first F is for "Fucking").

Hi @saeidzebardast,
It's been a while!
Now the element is using class-style syntax and is not hybrid anymore.
Unit tests have been fixed.
See this Travis CI build.

Hi @masonlouchart,
Thanks for the migration. I am going to merge this and release a new major version.

authors: masonlouchart saeidzebardast

repo: saeidzebardast/moment-js


text:
Custom app warning pop up visible for a short time when internal app is opened

Description
When opening an internal safe app like Drain Account or Tx-builder the custom app pop up is visible for a split second.
Note: At the time of opening this ticket this is only reproducible on rc 1.2.0 from the web team but should reach prod this week.
Steps to reproduce
On the browser developer tools, set network speed to slow 3G or fast 3G to easier catch the pop up and open tx-builder safe app.
Expected result
App is opened as usual.
Obtained result
A warning pop up is shown for a split second.
https://user-images.githubusercontent.com/92332710/207391189-e107a437-eac3-45c6-893b-6710b297183e.mp4

Whoever gets to work on it - please check the discussion in the linked PR

I've made a small adjustment as per that thread and resolved it. Ready for QA.

Closing this señor ticket as the linked PR was merged 😄

authors: JagoFigueroa katspaugh mikhailxyz

repo: safe-global/safe-react-apps


text:
Unable to get FB info with access token

I have two parts on my client side:
Web - using satellizer
Mobile - using ng-cordova-oauth
Server - Providing rest data after authenticating with the backend (python). Everything works with satellizer client, both on client and server.
With ng-cordova-oauth, for Google+ it works, if I just use the token, but fails with FB. Have taken the python code from the example folder of this project and did FB and Google+ login starting step2. FB fails.
I opened a ticket for ng-cordova-oauth to provide code token, but the author refused. Can you please help me resolve this issue ?
https://github.com/nraboy/ng-cordova-oauth/issues/26
If you need additional info from my side, let me know.

My bad usage of API, fixed the problem at my end now. Thanks for your time.

repo: sahat/satellizer


text:
[Bug] Requesting changes to 'Requestable Objects List' (list-requestable-objects)

Describe the bug
ENTITLEMENT is not supported by this API
To Reproduce
curl  GET '{{tenant}}/beta/requestable-objects?types=ENTITLEMENT'
Expected behavior
Get All Requestable Entitlements
Actual behavior
Error by API
Screenshots
{
    "detailCode": "400.1 Bad request content",
    "trackingId": "xx",
    "messages": [
        {
            "locale": "en-US",
            "localeOrigin": "DEFAULT",
            "text": "The request was syntactically correct but its content is semantically invalid."
        },
        {
            "locale": "und",
            "localeOrigin": "REQUEST",
            "text": "The request was syntactically correct but its content is semantically invalid."
        }
    ],
    "causes": [
        {
            "locale": "en-US",
            "localeOrigin": "DEFAULT",
            "text": "ATTRIBUTE and ENTITLEMENT request object types are not supported!"
        }
    ]
}

This is a product issue and not a documentation issue.  I created a ticket for the product team to look into supporting entitlements in this API. IDNWAIMEA-11950

authors: colin-mckibben-sp piyush-khandelwal-sp


text:
Add sum of Nth term of Geometric Progression under General Maths

Is your feature request related to a problem? Please describe.
There is a calculator to find sum of nth term of a AP but no such for GP.I want to add that.
Describe the solution you'd like

A clear and concise description of what you want to happen.

issue is already opened for the same

/assign

#270


text:
add existence of polygon calculator

With reference to issue #1605
Added calculator to check existence of polygon calculator

@sairish2001 Pls help me idk why these merge conflicts cant be solved


text:
Need to support entity proxies

Currently we can map entities to other entities (e.g. proxies). They can also have extended information. Not sure if we should make that part of this pkg? @dhowden thoughts?
Example:
"Bay Area" proxies to:
{
    "Bay Area": {
        "name": "San Francisco, CA, USA",
        "lat": 37.7833,
        "lng": 122.4167
    }
}

I think that this is very useful, and could apply to any chunk of data or string in the system?  In which case I think it should be in a separate layer.

Not sure how it would fit in here, especially as the output returned from FindAll is quite "flat" at the moment.  Feels like it is an extra layer on top, and so should probably be somewhere else.

yep agreed.
On Mon, Sep 21, 2015 at 10:45 PM, David Howden notifications@github.com
wrote:

Not sure how it would fit in here, especially as the output returned from
FindAll is quite "flat" at the moment. Feels like it is an extra layer on
top, and so should probably be somewhere else.
—
Reply to this email directly or view it on GitHub
https://github.com/sajari/fastentity/issues/1#issuecomment-141963247.

--
Hamish Ogilvy
Sajari Pty Ltd
*t:  +61 (*0) 414 658 353  |  *e: *hogilvy@sajari.com
w: www.sajari.com

repo: sajari/fastentity


text:
SAK-49588 gradebookng use a mock ResourceLoader when running tests

https://sakaiproject.atlassian.net/browse/SAK-49588

LGTM thanks

authors: ern mpellicer

repo: sakaiproject/sakai


text:
SAK-32543 joda-time 2.9.9

https://jira.sakaiproject.org/browse/SAK-32543

@ern cheers!


text:
SAM-1074 Adding Delete test submission attempt feature for samigo, we…

… used this feature at Texas State Univ  from 2006 till now for sakai10.4
Tested over sakai's trunk, works well. For history of this feature merge request and also related feature demo video link, please see SAM-1074.

Can you amend the last commit to prefix it with SAM-1074 please?

Code comments provided in-line

This feature should have a property to control whether it can be turned on, and should be off by default.

This jira has merge conflict and without it, the feature on SAM-2587 doesn't work and in turn https://jira.sakaiproject.org/browse/SAM-2712 results.
Are @yuanhuaqu able to resolve the conflicts here so this can be merged? The property is probably a good idea but would need to involve both this workflow and another and I think should be a separate issue.

This looks good, can you run a "git rebase master" to clean up all the commits on this?

I did a merge with master on Mar 22 and resolved the conflicts.  I tried to do "git rebase master" , it somehow didn't pull all the commit on this branch and allow me to squash.  I guess, having a merge in the middle of the process won't allow me to rebase? Any guide I can follow for this case?

Hi @yuanhuaqu
Having a merge in there does complicate things a little..
Basically you need to get rid of the merge, you can do this a few ways perform a rebase and drop the commit with the merge.You can also squash your commits in the same rebase.
So you need to figure out how many commits to include in the rebase, in the example below I use 5 but you should adjust according to the number of commits you have on this branch. (Remember the one of those commits is the merge)
git rebase HEAD~5
Select which commits to squash and select the merge commit to drop.
Once this is complete you will then just have 1 commit and the merge will be gone.
Now in order to update your branch from master you perform from your branch:
git rebase master
This will then bring your branch up to date with master (you may need to fix if there are conflicts).
At this point you should have just 1 commit being the last one, now just need to update this PR by force pushing your changes.
Hope this helps!
BTW there are others to do this like performing a SOFT reset on your branch but the way I described above would be the most direct.

It took me a while figuring out the complexity caused by using merge instead of rebase for updating  my feature branch with master, resolve conflicts and eventually squash all the commits (8) into a cleaner one.
@ern
Thanks  for the guide.  It helped me a great deal!!!!    May I suggest you to put this guide in somewhere like Git+Setup ?  And surely, case like mine with this branch which almost stretch out about a year,   to keep feature branch updated before it finally get into the master base , doing a   git rebase master will be much simpler than git merge master (which I learned it the hard way :=))

I have some internal documentation explaining most if not all of this, which I plan to move into the Sakai Confluence page you mentioned in the near future.

Thanks all for following up on this, I'll merge and test this after Travis passes.

Thanks.

authors: bjones86 ern jonespm yuanhuaqu


text:
SAK-40645 - gradebook, accessibility: Set Score for Empty Cells inval…

…id score error message prevents other actions

@adrianfish It looks like there were a few issues from your first PR on #6414.

The javascript call had the parenthesis at the wrong location so "true" was actually never passed in
The form inputs were disabled by the submit but something needed to re-enable them, I think this was more of the issue than "dontDisable". I removed the code from the performRealSubmit since I don't think we can know at that point whether or not to disable.
IF there was a NumberFormatException this wasn't called either so I added to that catch

Re-opened as #8319 SAK-43847


text:
conference-site to 0.0.8

Promote conference-site to version 0.0.8

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

repo: salaboy/environment-racerhorse-staging


text:
Change stack for ios-bundle

We were building with older stack with Xcode 13.2 and Intel machines in Bitrise. These have been deprecated by them, and it was causing issues in sending the SDK to Cocoapods.

!merge

repo: salemove/ios-bundle


text:
Add kpro_connection:sasl_reauthenticate_after/2

Allows authentication callback adapters to re-authenticate the
connection before session lifetime expires. An example use case is given
under function documentation.
This change requires adding the connection config, which contains SASL
options to the state record.
In theory, the connection process could read session_lifetime_ms out
of the SASL authentication response and set a timer itself, but this
would require quite a few changes to existing interfaces as the sasl
authentication functions return just ok and such an addition would
probably need to be behind a feature flag.

I will make a PR to the upstream when we have moved some of our services over.


text:
Use prop-types package

React.propTypes is deprecated in version 15.5 and this causes warnings
when using react-intl-tel-input.

bump the version?

https://github.com/salemove/react-intl-tel-input/pull/2

!merge

!check

!check

authors: SteamRiC deiwin ostap0207 willmore

repo: salemove/react-intl-tel-input


text:
Add benchmarks for fetching checkout available shipping methods

Add benchmarks for fetching checkout availableShippingMethods.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Closing. New PR: https://github.com/saleor/saleor/pull/8636

repo: saleor/saleor


text:
how to eval VizWiz?

Thanks for your released model, But when I used instructBLIP vicuna7B model to eval VizWiz, the acc result is 26%, while the result in paper is 34.5%, is there any special setting? such as for "unanswerable" answer.
With same experiment setting, I can get right result in okvqa、gqa, except VizWiz.
Here is my setting:

model: https://storage.googleapis.com/sfr-vision-language-research/LAVIS/models/InstructBLIP/instruct_blip_vicuna7b_trimmed.pth
data: "testdev" and "val" in VizWiz, around 8k test and 4k val images in official website.
eval setting

run:
  task: vqa
  # optimization-specific
  batch_size_train: 16
  batch_size_eval: 64
  num_workers: 4

  # inference-specific
  max_len: 10
  min_len: 1
  num_beams: 5
  inference_method: "generate"
  prompt: "{}"

  seed: 42
  output_dir: "output/BLIP2/VizWiz"

  evaluate: True
  test_splits: ["test"]

  # distribution-specific
  device: "cuda"
  world_size: 1
  dist_url: "env://"
  distributed: True

Hi @jorie-peng,
Do you have any update on this? Have you been able to reproduce the results for VizWiz?

Hi @jorie-peng and @lavoiems . Have you guys figured out how to reproduce the results for VizWiz yet? Thanks!

Hi @jorie-peng and @lavoiems . Have you guys figured out how to reproduce the results for VizWiz yet? Thanks!
haven't, maybe @LiJunnan1992  knows.

hello, I also want to test the instructblip model with coco dataset ,but I don't know how to do ? I have the A100 GPU with centos, could you tell me how to config the according file?

authors: DoggyLu jorie-peng lavoiems weiyueli7

repo: salesforce/LAVIS


text:
🛑 RAÄ Kringla is down

In 62efabe, RAÄ Kringla (https://www.kringla.nu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RAÄ Kringla is back up in c2e59cb after 8 minutes.


text:
Drop direct dependencies for config and dotenv

Description
Currently, when we have NODE_ENV=production set, attempting to run node-pg-migrate will throw warnings with no way to silence them.
Reproduction
$> NODE_ENV=production node-pg-migrate up
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode

Additional Context
The always-throwing-warning was introduced with 1.9.0 of config as part of their Strict Mode release. While you can tell node-config to warn instead of throw, the errors cannot be shut off, even when you are not using config in your app. This happens because we have a direct dependency on config (and dotenv) meaning that we'll always require and run them even if our consuming code doesn't use them.
As a proposed fix, I suggest we leave our require + try/catch intact, and just move config and dotenv into peerDependencies just like we do with pg.
💥 This will introduce a breaking change A change to peerDependencies means that anyone who was assuming a .env or a config/default-<environment>.json file would "just work" will have migrations that do not run without adding the peer dependency.
Workaround
In the meantime, if you're in a CI environment and don't require NODE_ENV for the migration operation, this comment indicates that you can explicitly remove the NODE_ENV value by running NODE_ENV= node-pg-migrate up. It's not an ideal workaround, but it is something in case you're running into weird CI issues.
References

https://github.com/salsita/node-pg-migrate/blob/master/bin/node-pg-migrate#L237 - example of the existing try/catch
https://github.com/lorenwest/node-config/wiki/Strict-Mode - strict mode docs stating a warning will always be issued
https://github.com/lorenwest/node-config/issues/386 - stating that they refuse to fix this and prefer folks "Just create the file."

But they are currently optionalDependencies?
https://github.com/salsita/node-pg-migrate/blob/e883e5bb9f4f863f8a0e328dd34f39223ccc6ebf/package.json#L83-L86

Unfortunately, optionalDependencies still install, they just don't fail thenpm install. https://docs.npmjs.com/files/package.json#optionaldependencies (think chokidar's fsevents as an example)
As a result, pg-node-migrate installs both dotenv and config. 😕
It's pretty poorly named.

That would be my recommendation, to move them into peerDependencies. The code is already try/catching the requires responsibily.
The only reason it's a breaking change is someone could be depending on .env files or the config/ directory and not realize it was node-pg-migrate adding things to process.env. It's an undocumented "feature" we'd be removing.

Problem is, that dotenv and config are really optional dependencies, it is not necessary to use them, bad is that npm installs them regardless. Moving them to peerDependencies would result in a warning during installation for people who do not use them.
There is no way how to tell that dependency is optional and it is up to the user to have it installed if he wants to use it.
The correct solution would be probably to remove them from package.json completely.

@dolezel I'd be okay with dropping them completely. The try/catch does its job properly. Happy to put together a PR for it.
What are your thoughts everyone RE that being a breaking change?

💥 It's a breaking change, because anyone who didn't install their own version of dotenv or config but had a .env or config/ will suddenly lose access to DATABASE_URL
🔕 It's a patch change, because as far as the code is concerned, because end-developers were never intended to consumenode-pg-migrate's copies of these dependencies.

authors: Jakobo Shinigami92 dolezel

repo: salsita/node-pg-migrate


text:
Provide directions for air-gapped environments / repository syncing with the new packages.broadcom.com repos

Page to update:

https://docs.saltproject.io/salt/install-guide/en/latest/topics/other-install-types/air-gap-install.html

Previously, Salt Project provided directions for tools like rsync and aws cli for pulling down Salt repositories for use within local/private infra. With the new repository locations, new guidance can be given.
Repository locations:

Artifactory view

Salt Project RPM Repo
Salt Project DEB Repo
Salt Project Generic Repo (Windows, MacOS, etc.)

General repository navigation

Salt Project RPM Repo
Salt Project DEB Repo
Salt Project Generic Repo (Windows, MacOS, etc.)

Something like this should work:
RCLONE_WEBDAV_URL=https://packages.broadcom.com/artifactory/ RCLONE_WEBDAV_VENDOR=other rclone sync :webdav:saltproject-generic/ ./saltproject-generic/

@max-arnold  wget could be a simple option too:
wget --mirror -nH --cut-dirs=1 https://packages.broadcom.com/artifactory/saltproject-rpm/
wget --mirror -nH --cut-dirs=1 https://packages.broadcom.com/artifactory/saltproject-deb/
wget --mirror -nH --cut-dirs=1 https://packages.broadcom.com/artifactory/saltproject-generic/

authors: ScriptAutomate max-arnold

repo: saltstack/salt-install-guide


text:
Fix #757 - Swagger Controller file path error

Cause
The issue arises because the input file paths are URL-encoded. Even after Nestia SDK URL encodes the file paths, the problem should not occur.
Solution
Changes Made:
I have made modifications in the ReflectAnalyzer.analyze method. I replaced the import paths with decodeURIComponent(file) to decode the file paths using URL decoding. This change ensures that file paths containing Korean characters or spaces are handled correctly.

It appears that additional test cases are needed. However, I'm unsure about how to add these test cases. The additional test cases should include folder names that contain Korean characters or characters subject to URL encoding. Such test cases are crucial to verify whether the fix correctly handles folder names with special characters. Additionally, it seems that the 'input' property in the 'nestia.config.ts' file should be defined as a function rather than a string array.
import { INestiaConfig } from '@nestia/sdk';
import { NestFactory } from '@nestjs/core';
import { AppModule } from '@src/app.module';

const NESTIA_CONFIG: INestiaConfig = {
  input: () => NestFactory.create(AppModule),
  // input: async () => {
  //   const app = await NestFactory.create(AppModule);
  //   app.setGlobalPrefix('api');
  //   app.enableVersioning({
  //     type: VersioningType.URI,
  //     prefix: 'v',
  //   });
  //   return app;
  // },
  // input: ['src/controllers'],
  output: 'src/api',

  swagger: {
    output: 'packages/api/swagger.json',
    beautify: true,
    security: {
      bearer: {
        type: 'apiKey',
        name: 'Authorization',
        in: 'header',
      },
    },

    servers: [
      {
        url: 'http://localhost:8000',
        description: 'Local Server',
      },
    ],
  },
  distribute: 'packages/api',
  simulate: true,
};
export default NESTIA_CONFIG;

Just copy and paste some of test/features belonged project as you want, and rename it to the Korean language.

In the previous commit, there was no Swagger build error, but there was an issue with Swagger's route list being empty. To address this problem, I applied decodeURIComponent to the analyze_application part of the ConfigAnalyzer.input logic.

authors: de-novo samchon

repo: samchon/nestia