Improve Report UI

The report UI doesn't look super great and could be better. Let's improve it.
To-Do

[ ] Improve Report UI

Hi @nprail,
I have a suggestions for you:

Would be good to have an option for CLI to enable/disable showing unique vulnerabilities. For example if you have installed<EMAIL_ADDRESS>then you will have 6 vulnerabilities, because of<EMAIL_ADDRESS>but they are same vulnerabilities.
Also as you can see here I have added collapsable for "Reasons" section (which makes sense if point 1 is a case). Note that it is CSS only solution, mainly because these kind of reports are used in CI-s where you don't want to (or can't) have JS.

@AdrianoCahete Sure, giving the option to add any sortable columns to the table would be best. I just meant, what should the default columns be.
The trouble with CVE is that it is an array of CVEs. There can be more than one. Would it make sense to group them all into one column?
Example:

Name
Severity
Module
CVEs

Arbitrary File Overwrite
High
fstream
CWE-59, CVE-2019-13173

I've started to work on the new design!
What do you think about a dark theme?

DARK MODE!
🎉🎉🎉
Feedback is much appreciated.

Is the palette easy to change? On my screen the green colors don't seem to have enough contrast.
Maybe you could try the color palette from https://material.io/design/color/dark-theme.html#anatomy

Yep, totally. I think I'll add a CLI option for dark or light mode.
I'll definitely be making adjustments to the color palette too.

Hope this will roll out soon. I have a small suggestion, It would be great if a breakdown of total no of issues based on the severity also.

@nikhilgeo I'll be working on finishing this up and hopefully releasing a new version with it tomorrow!
I'm probably going to make dark mode an option but not the default.

I've improved the dark theme a lot (borrowed some styles from VS Code) and also added code highlighting with highlight.js.
If you want dark mode, you will have to add --theme dark as a CLI option. 2.0 will probably switch to dark mode by default.
Dark mode

Light mode

Awesome, thank you for the new looks.  Looking forward for the new release.

:tada: This issue has been resolved in version 1.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[graphicsmagick] Linux/MacOS support

Added support to build GraphicsMagick on Linux and MacOS

It closes #6399


visual alignment (purely aesthetic)

The armor prefix BEGIN SLATEPACK. is a single character too long to wrap nicely with the 15 char blocks.
BEGIN SLATEPACK. 2A4ijPMavuaBrAX EqsdWEtB5dy5ZN6
H9md6GTf7GbsrPf c4i9i1atSdCknwQ 6nCcmJKmuUgkiu9
KU5wFwUMYrZKXvV Z2TUVBbDwRYrS2L mA3ppP7o5EQ7yqR

BEGIN SLATEPACK SIGNED MESSAGE. fits nicely relative to a pair of 15 char blocks -
BEGIN SLATEPACK SIGNED MESSAGE. 2A4ijPMavuaBrAX
EqsdWEtB5dy5ZN6 H9md6GTf7GbsrPf c4i9i1atSdCknwQ
6nCcmJKmuUgkiu9 KU5wFwUMYrZKXvV Z2TUVBbDwRYrS2L

BEGIN SLATPACK. would also work but maybe a little too close to SALTPACK and looks weird...

Thanks, @antiochp it would have been much nicer if the message framing was the same length as words.
One aspect worth considering is if we want to encode any more human readable data in these messages to help distinguish them. I've been considering BEGIN SLATEPACK INITIAL, BEGIN SLATEPACK RESPONSE, BEGIN SLATEPACK 1/2 (for extremely long edge case slates), BEGIN ENCRYPTED SLATEPACK. All of these could be encoded underneath the human readable armor but it might be nice to have that data visible. Do you have any thoughts on this approach? Or does it seem cleaner to leave that data as machine readable only? This is where the armoring and serialization overlap a bit.
I do think it can make sense to do some optimizing here for human readability here because a few bytes won't make a major difference and are worth an improved user experience.

+1 for this, I coincidentally noticed/thought about this mis-alignment just a few hours ago!

What about something like
BEGINSLATEPACK. 2xfX9bS82gxJ6jN
D6X4X843wrT84DT FkstYawTtacDqeU
MyGqBauGHxEFZNg FeEbVFsqXaKkKwK
tDvEwUBsuhb9GRf 1MK3jegnbKG5JJr
pbY4nbeZgPtRaZj QZL61Wj7iGqKBuJ
axfussSBrZq7xMQ P1rbw3GpebXkMeY
eXHDN9iascu. ENDSLATEPACK.

From my testing on mobile it looks like the words get split up into pairs to be displayed. I don't think we want to go larger than 15 character words or this gets jumbled a bit.
We also don't do any padding so the last word could be one or fifteen characters.
If we don't touch it, things look a little better on mobile as the framing header gets its own line:
BEGIN SLATEPACK.
2xfX9bS82gxJ6jN D6X4X843wrT84DT
FkstYawTtacDqeU MyGqBauGHxEFZNg
FeEbVFsqXaKkKwK tDvEwUBsuhb9GRf
1MK3jegnbKG5JJr pbY4nbeZgPtRaZj
QZL61Wj7iGqKBuJ axfussSBrZq7xMQ
P1rbw3GpebXkMeY eXHDN9iascu.
END SLATEPACK.

I went ahead and merged https://github.com/j01tz/slatepack/pull/3 to try a more aligned framing based on feedback. Will keep this issue open in case we want to revisit other options here.

Yes. Thanks! I like this -
BEGINSLATEPACK. 2xfX9bS82gxJ6jN
D6X4X843wrT84DT FkstYawTtacDqeU
MyGqBauGHxEFZNg FeEbVFsqXaKkKwK
tDvEwUBsuhb9GRf 1MK3jegnbKG5JJr
pbY4nbeZgPtRaZj QZL61Wj7iGqKBuJ
axfussSBrZq7xMQ P1rbw3GpebXkMeY
eXHDN9iascu. ENDSLATEPACK.

I think we should only have a single kind of armor as well, and not a specific version for each round of communication. I suspect that will blur the purpose of this.

I think we should only have a single kind of armor as well, and not a specific version for each round of communication.

I think this is where I am too after seeking more feedback. Going to close this now, thanks!


overhaul mpl backend; fix coordinate flip argument

coord_flip did not work for the matplotlib backend [e.g. replacing all figs here with MPL backends made everything unreadable].
I overhauled it to use ax.errorbar. Fixed(L) v old (R)

Also added an optional ax argument so that plots can be faceted mpl style

also the fact that the Inf interaction in the event study appears all the way to the right is quite disconcerting. Could we convert it into -inf @s3alfisc ?

Also was thinking about how to pair joint confints with iplot.
Here's something I made with an annoying amount of manual work
# interact treatment indicator with time dummies omitting the last period before treatment
m2 = pf.feols(
    """
              Y_it ~ i(time_id, ever_treated,  ref = 14) |
                unit_id + time_id
              """,
    df,
    vcov={"CRV1": "unit_id"},
)
# confidence regions
restable = m2.tidy()
timestamps = restable.index.str.extract(r'\[T\.(\d+)\]', expand=False).astype(int)
# create confidence envelopes for all pre-treat and all post-treat coefs
kv = [f"C(time_id, contr.treatment(base=14))[T.{t}]:ever_treated" for t in range(15)]
uniform_confint_pre = m2.confint(keep=kv, joint=True, exact_match=True)
kv = [f"C(time_id, contr.treatment(base=14))[T.{t}]:ever_treated" for t in range(15,30)]
uniform_confint_post = m2.confint(keep=kv, joint=True, exact_match=True)
uniform_res = pd.concat([uniform_confint_pre, uniform_confint_post])
uniform_res.columns = ['unif_25', 'unif_975']

f, ax = plt.subplots(1, 1, figsize=(12, 6))
ax.plot(
    np.arange(30),
    np.r_[np.repeat(0, 30 - 15), treat_effect_vector],
    marker=".",
    label="True ATE",
)
ax.errorbar(
    timestamps + .5,
    restable["Estimate"],
    yerr=restable["Std. Error"] * 1.96,
    fmt="o",
    label="pointwise 95% CI",
)
ax.errorbar(
    timestamps + .75,
    restable["Estimate"],
    yerr= [restable["Estimate"] - uniform_res["unif_25"], uniform_res["unif_975"] - restable["Estimate"]],
    fmt="o",
    label = "Joint 95% CI (pre/post)",
)
ax.axvline(x=14.5, color="k", linestyle="--")
ax.legend()

where the joint intervals are for all the pre-treatment coefficients at once (which is basically a test for parallel trends) and all the post-treatment coefficients at once (which is a test for the treatment effect function)

On the joint CIs: likely best to do a small code refactoring and move the core joint CI logic from the confint to the vcov method. This way, we can update the variance covariance matrix via .vcov().
If the used vcov matrix is not yet of type "simultaneous", we can then propagate it to iplot() by updating the .tidy() method with a joint = True argument, which is called by all plotting functions to get the coefficients, which in turn calls .vcov(), which calls .get_inference().
We can also have a flexible input argument joint = "both", which would return a Feols instance with standard inference and a copy of the instance with simultaneous inference.

Hi, I have opened a PR that adds an argument to iplot() for joint CIs over at #587. Does not seem to work yet with matplotlib (I am really not an mlp expert).

Could we convert it into -inf @s3alfisc ?

Yes, happy to do that =D

Hi, generally happy to accept these changes!
At the moment, the PR breaks multiple estimation functionality. Quick example:
import pyfixest as pf
from lets_plot import *
LetsPlot.setup_html()

data = pf.get_data()
fit = pf.feols("Y + Y2~ i(f1)", data = data)

fit.iplot(coord_flip = False, plot_backend="matplotlib", figsize=[4, 3])
fit.iplot(coord_flip = False)

The mlp version returns

but it should look as

I like the option of being able to define subplots. Would this work with seaborn too?

Maybe not the most elegant, but we could simply to everything manually in seaborn? I did not manage to get any of the seaborn default args for flipping x- and y axis to work.
    if flip_coord:
        # Flip the x and y axes
        plot = (
            so.Plot(df, y="Estimate", x="Coefficient", color="fml")  # Swap x and y
            .add(so.Dot(), so.Dodge(empty="drop"))
            .add(
                so.Range(),
                so.Dodge(empty="drop"),
                ymin=str(round(lb * 100, 1)) + "%",  # Swap xmin with ymin
                ymax=str(round(ub * 100, 1)) + "%",  # Swap xmax with ymax
            )
            .label(
                title=title,
                y=rf"Estimate and {round((1-alpha)*100, 1)}% Confidence Interval",  # Swap x and y labels
                x="Coefficient",
                color="Model",
            )
            .on(ax)
        )
    else:
        plot = (
            so.Plot(df, x="Estimate", y="Coefficient", color="fml")
            .add(so.Dot(), so.Dodge(empty="drop"))
            .add(
                so.Range(),
                so.Dodge(empty="drop"),
                xmin=str(round(lb * 100, 1)) + "%",
                xmax=str(round(ub * 100, 1)) + "%",
            )
            .label(
                title=title,
                x=rf"Estimate and {round((1-alpha)*100, 1)}% Confidence Interval",
                y="Coefficient",
                color="Model",
            )
            .on(ax)
        )

I'm actually strongly in favour of getting rid of seaborn use entirely.
MPL and letsplot(or other ggplot-likes, eg altair or plotnine) are two corner solutions: either roll your own plot with matrices and have very fine control over things (MPL: my preference) or have a user-friendly API that gets you 90% of the way there at the cost of finer control (eg letsplot). Seaborn is not very good at either, as illustrated here. Keeping the mpl backend as pure mpl for weirdos like me while most people use the default letsplot backend seems like a reasonable choice

Sounds good to me, let's switch to pure matplotlib then. I think the last PR I merged might need a slight refactor as we'll need the critical values for the joint cis, which is not available atm - though I think it could be easily added to the model_df frame that stores the coefficient and cis. Obviously some other larger refactors might also work =)

Btw I opted for letsplot back when because it's usually much faster than plotnine and looks prettier out of the box. I also like its  dynamic / html features. Have never used Altair though, just seen some nice plots produced by a colleague

fixed multiple estimation

Pushed a small update to allow for joint CIs (& fixed a mypy complaint). Looks good to merge for me, though let me know if you'd prefer another solution for enabling joint= True, than the one I have now implemented.

We also need to remove the seaborn dependency and replace it with matplotlib. Can be done via "poetry remove seaborn" and "poetry add matplotlib". I tried to do it myself but I'm in a train in the middle of nowhere in Germany and there is no WiFi around here 🤦♂

Around Berlin now so wifi is back - updated the dependencies & created a new lock file. Ready to be merged from my end!

Oh yeah thx; I'll also update the mpl function to plot joint intervals.
Also running into some issues with the buildfile (e.g. hardcodes powershell lol) so I'm glad you handled it.

Yeah the power shell is hard coded because I'm a windows guy 😀 I've implemented support for joint ci's btw! I can also give you a quick intro to the build tools one of these days, it's mostly very simple poetry + the just file commands (minus the power shell req)

I ended up reverting the seaborn dependency drop commit since it produced a bunch of unit test failures (in corners of the package i know less well) btw. Will need a new patch to fully un-seaborn the package but I'm not in a hurry to do it since it is a fairly stable package that auto-installs matplotlib. You should go ahead with changes if you have strong opinions on the matter.


Pushing to segments_mut creates unrecoverable segment

Here is some code illustrating the problem:
use std::env::args;
use img_parts::jpeg::{self, JpegSegment, Jpeg};

const OUR_MARKER: u8 = jpeg::markers::COM;

fn main() {

    // Get path of JPEG from CLI
    let mut args = args();
    let _executable = args.next();
    let path = args.next().unwrap();

    // Read JPEG from file and report number of segments
    let bytes = std::fs::read(path).unwrap();
    let mut jpeg = Jpeg::from_bytes(bytes.into()).unwrap();
    println!("Initial number of segments:                  {}", jpeg.segments().len());

    // Add segment to end, and report number of segments
    let segments = jpeg.segments_mut();
    segments.push(                        // BROKEN
    //segments.insert(segments.len() - 1, // WORKS
        JpegSegment::new_with_contents(
            OUR_MARKER,
            img_parts::Bytes::from("OUR SEGMENT CONTENT")
        )
    );
    println!("Number of segments after adding new segment: {}", jpeg.segments().len());

    // Roundtrip JPEG via bytes and report number of segments
    let new_bytes = {
        let mut bytes = vec![];
        jpeg.encoder().write_to(&mut bytes).unwrap();
        bytes
    };
    let new_jpeg = Jpeg::from_bytes(new_bytes.into()).unwrap();
    println!("Number of segments after roundtrip:          {}", new_jpeg.segments().len());
}

which demonstrates that pushing a new segment to .segments_mut() creates a segment which is accessible from the original JPEG instance, but disappears when the JPEG is serialized and deserialized again.
When push ing the new segment to jpeg.segments_mut(), the serialized representation of the JPEG contains the new segment after EOI and
https://github.com/paolobarbolini/img-parts/blob/main/src/jpeg/image.rs#L53-L55
ignores everything after EOI.
If you replace push(... with insert(<somewhere before last element>, then the new segment is placed before EOI and is recovered when the JPEG is deserialized.

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


Css and animations

Added animation to the toggle-mode button and whole body ease-in-out animation, adjusted CSS of date in Events Calender section.

Bug is still there.
In light mode:


Trivialize unit test environment variables

I believe unit test environment variables should not be associated with their deployment values. Organizationally, this makes it clearer that these values don't need to be updated when the real values change, however, they still need to be set.

Force push to rebase master ^


Docs for apiLogging options in Configuration CRD

The documentation for the Configuration CRD needs to be extended to include docs for apiLogging, as added in https://github.com/dapr/dapr/pull/5462

/assign

Closed as completed by #3034


overworld trees in nether

Describe the bug
overworld trees dont grow properly in the nether, even when bonemealed 1.19.2 forge ver 1.2.2
To Reproduce
place a overworld tree in the neter (i used oak) and than bone meal it once, starts off fine, second time leaves disapear, 3rd time the rest of what is left
Screenshots

Rendering Glitches
nope no shaders
Crashes

Are you running the latest version of Dynamic Trees? yes
What addons are you using?
Are you on the latest version for each addon?

Mods List
crash-2024-10-11_17.23.48-server.txt

This is because there is no natural light in the nether


Incorrect exercise: [courseId=grammar-intro_eng][lessonNumber=9][exerciseId=4133]

Description
If possible, please provide a brief description of what is wrong with this exercise.
ke'a being marked as incorrect
Diagnostics information (do not remove)

Exercise identifier: [courseId=grammar-intro_eng][lessonNumber=9][exerciseId=4133]
Exercise payload: {"sentences":[{"text":"The instructor, who is Lojbanic, is happy that you sold me the tool.","lojbanic":false}],"title":"Translate this sentence","type":"typing"}
Attempted solution: {"text":"la ctuca noi ke'a lojbo cu gleki lo nu do vecnu lo se pilno mi"}
Attempted solution was classified as correct: no
Validation payload: {"canonicalAnswer":"lo ctuca noi lojbo cu gleki lo nu do vecnu lo se pilno mi","correct":false}

Thanks for reporting!
It seems that the issue in this case was the use of "la ctuca" instead of "lo ctuca".
For this exercise, an optional "ke'a" is already accepted.

(["lo ctuca noi {ke'a} lojbo cu gleki lo nu do dunda lo se pilno mi"], ["The instructor, who is Lojbanic, is happy that you gave me the tool."])

https://github.com/jqueiroz/lojban.io/blob/a2e5efe40d82cd848135f6574b37fdbe0995fe40/haskell/src/Study/Courses/English/Grammar/Introduction/Translations.hs#L1098


File drag / drop bug

Operation System: Ubuntu with i3wm
Beaker version: prerelease.1
Dragging a file onto a page most of the time works, but when dragging it out or moving it crazy on the page, the page crashes. It goes black and the console says "DevTools was disconnected from the page". It only happens on dat:// sites and never on http://.
Does this only happen to me?

Sounds like an electron bug. It might be fixed in the latest builds because we upgraded electron (and thus chromium).

Allright, thanks! Waiting for a Linux build then :smile: lol

Haha yeah, I'll jump on my linux box in a bit to fix some bugs and I'll cut a build then

Linux build is out now

Thanks @pfrazee, you're the best! :smile:


Are anchor links to a specific brick possible?

First of all: I'm impressed how flexible and easy hugobricks is! It makes me capable of creating websites I never dreamed of creating in hugo (since i'm just a hobbyist with no formal training what so ever in this field). So: thank you for open sourcing this!!
My question: Is it possible to create a link to a specific brick on a page? Like https://www.hugobricks.preview.usecue.com/#cta to scroll to the call to action on the index page? If so, (where) can I specify the anchor name?

found my own answer: yes, it's possible
when inspecting page, i found the ID of the H2 header i wanted to link to; this can be used to make the anchor link
Like this:
https://www.hugobricks.preview.usecue.com#what-users-say-about-hugobricks
Only thing is a sticky header doesn't play nice with this, it overlaps the title...

Ah... there is a solution for that... I will take a look. Thank you for reporting this.


2021.3 Compatibility

This issue just for notify of compatibility done.
We are all patiently waiting for...

I couldn't find any incompatible API usages via the GitHub search.
Updating sinceBuild and untilBuild in build.gradle might be enough.
Great work on the plugin by the way. I use it on a daily basis 🙂

Here is already a pull request for that reason
#343

Note, I put a .jar for download in this PR comment if anyone is really needing this now.

https://youtrack.jetbrains.com/issue/IDEA-284041
Sorry, guys, I've done my best to try to avoid continuous plugins version bumping.

@SantjagoCorkez it is jetbrains’ choice to deal with this or other issues related to plugins.
there is a different issue in handling .env files that should be built into the IDE but the company has thus far refused to address.
Plugins, particularly community provided ones and how they are incorporated into IDE cores will probably going to be the single most important point of competition between IntelliJ and its children and vscode.

Here is already a pull request for that reason #343

@homburgs you've seen @OpherV's PR comments presumably?

It seems like this comment from the YouTrack issue would be particularly apt for this:
"Alternatively, they may even decide to specify no until-build so the plugin will be available in any later released IDE version(s) - until incompatibilities are detected and the until-build is limited manually on JetBrains Marketplace to prevent further problems for users."

Any good news or workaround, please?

Any good news or workaround, please?

I put a workaround jar Here .

2021.3.1 is now out as well, so prob want to take that into account when releasing the next version.

Will it be resovled?

Any update?

Please specify whether this plugin is out of maintenance.

This feels like something that is core enough to the git workflow that I feel like IntelliJ should adopt and update this plugin, just like they did with the Lombok plugin in 2020.3

How to push Jetbrain to adopt this excellent plugin to be the native bundled? Let's do it.

I like the idea, but from my experience, feature requests around incorporating plugins into the IDE are very challenging to get traction on.
A good example is PY-5543 , which has over 170 votes, 5 duplicates and goes back to 2014.
PY-5543 is arguably far less complicated feature, requiring a check box and perhaps a file path widget.
But it still is not being acted on by JB.
It is okay if the maintainer of this library is unable to keep up given the reasonable standards they have.
However, perhaps this project should be forked and maintained using lower standards. What I mean is, it presumes IDE changes are not breaking the plug-in’s behavior.
The main reason the maintainer insists on updating this with each release is to reduce the likelihood that this plug-in causes accidental loss of work.
That said, Pycharm and afaik, all of the Jetbrains IDEs have Local History, which is like a temporary cache of file changes independent of Git. So it is reasonable to consider if this is enough of a safety net in of itself.
I wouldn’t want to bet a full day of work on Local History, but the convenience of this macro is very high.

In the meantime you can use Git Flow Integration Plus which is a fork of this plugin.

In the meantime you can use Git Flow Integration Plus which is a fork of this plugin.

I don't know Java well. Has anyone looked this repo through? Non-latin letters in public repo, rare commits...

The mere presence of non-latin letters in a public repo should not create suspicion but that this is a concern at all draws attention to why JetBrains should make an effort to bring this and other popular plugins (that have maintenance problems due to versioning) into the core product suite.
It is a security issue, and this and PY-5543 deserve to be controlled and validated by the company's internal security auditing.
Separately, it is not very challenging to build this plugin using IntelliJ IDEA CE. If you are concerned at all, just make the version changes and build. See info / links I provided here.

Checking the repo. Found:

create CI scripts/yaml configs
delete CI scripts/yaml configs
repeat
repeat
...
repeat
enough
https://github.com/RubinCarter/gitflow4idea-plus/commit/938473700fc304374edd4d734fbfc6b154e8d7e6
https://github.com/RubinCarter/gitflow4idea-plus/commit/1af85a0b641dbb3eacc49d2d36af8afa57d4af10
GitFlow-Fix <-> GitFlow-Plus multiple transitions in naming and meta information
https://github.com/RubinCarter/gitflow4idea-plus/commit/550a4980c2ff8d4a1563155e232b8fb728bccbf3 (which was added in a series of commits)

So far: there's no a single feature implemented (though stated in README). The only difference to current project: minVersions/maxVersions bumping up and dropping down here and there, some cosmetic fixes in IDEA's interfaces which do not seem critical. And 2 binary uploads of gradle JAR.
Meh...

Hi @OpherV, it would be really helpful if you could write at least a short comment to give us an update of the current status of this project.
Many people rely on your great plugin, and it would be sad to see this project becoming a zombie, without any clear notice.

I hope that they weren't a victim of the pandemic.

https://github.com/EkoLabs/react-native-background-downloader/commits?author=OpherV&since=2022-02-01&until=2022-02-16
No, the owner is still alive and active. Seems he just got tired of Intellij'es versioning and lost interest to this project.

Added PR #345 fixing the indentation from @homburgs PR and updating the version number

Maybe someone should make a fork of this project and develop it?
It would be nice if the current author wrote what is the current status of this project

Any solution?

For now I think the solution is migrate to https://github.com/RubinCarter/gitflow4idea-plus


nuxt3: Cannot read property 'hooks' of undefined

Version
@nuxtjs/strapi: v0.3.1
nuxt: v3.0.0-27235451.ece0e01
Reproduction Link

Steps to reproduce
Fresh nuxt3 install. Added nuxt/strapi. Run 'yarn dev -o'
What is Expected?
nuxt running
What is actually happening?
Cannot start nuxt:  Cannot read property 'hooks' of undefined 15:36:55
at Object.wrappedModule (node_modules/@nuxt/kit/dist/index.mjs:1092:13)
at Object.installModule (node_modules/@nuxt/kit/dist/index.mjs:1196:17)
at Object.strapiModule (node_modules/@nuxtjs/strapi/lib/module.js:39:14)
at installModule (node_modules/@nuxt/kit/dist/index.mjs:1196:17)
at initNuxt (node_modules/nuxt3/dist/index.mjs:817:11)
at async load (node_modules/nuxi/dist/chunks/dev.mjs:6763:9)
at async Object.invoke (node_modules/nuxi/dist/chunks/dev.mjs:6794:5)
at async _main (node_modules/nuxi/dist/chunks/index.mjs:417:7)
✔ Generated nuxt.d.ts

Any updates on this?

The new dev version works for me. See https://github.com/nuxt-community/strapi-module/blob/dev/docs/pages/2.setup.md#edge-channel
Thanks @benjamincanac for the great work!!!


Motif finding in protein sequences.

Hello! What a wonderful program you have here.
I was writing to ask if lightmotif is capable of searching for motifs in protein sequences.  It looks like functionality is partially in place but I couldn't get it to run with some simple code tweaks. It kept crashing as it was trying to reverse compliment a protein sequence. Maybe I'm doing something wrong?
I'm looking to use motif searching techniques to find short, but conserved exons in genomes. Similarity approaches such as Blast, Diamond, HMMER aren't able to find these. We
When mining a genome, we know roughly where an exon is because it is nestled between or adjacent to longer exons. Thus we only have to search a miniscule fraction of the actual genome. We've done a basic proof of concept which shows the idea works.  Unfortunately, all the references sequences are only available in amino acids. The nucleotide format is not available for the references. However, we are able to pass nucleotides or translations for the genome we are mining if that would help.
We were hoping to use your software so we didn't have to reinvent the wheel so to say.
Is this protein motif searching possible in lightmotif? If not, is it something you can add?

Hi @Thernn88,
The Rust library is capable of running on protein sequences, although the implementation is slower than for DNA (because of DNA having only 5 symbols vs the 20 proteinogenic amino acids, some optimizmations don't work for larger alphabets).
If you tried using the Python library, I have not added support yet because I need to hardcode the protein alphabets -- the alphabets must be defined at compile-time in LightMotif (this allows some loop unrolling based on the dimension of the alphabet, $K$); I can try adding support if that's something you need.

Hi Althonos,
Yes! This would be very useful. We would greatly appreciate you adding this.
We aren't terribly worried about speed. The search space is so small for these (capped at 20000bp) that it shouldn't be noticable. I/O is probably a larger concern.

In that case, to be honest, I think you can use the Bio.motifs module from Biopython -- it is functionally equivalent (same algorithm but implemented naively), and supports proteins for sure (with a little bit of configuration options).

Protein sequences are now supported in v0.9.0, just use lightmotif.create(..., protein=True) and lightmotif.stripe(..., protein=True) to treat the input as protein sequences.


Cannot deploy bitnami helm chart

What happened?
I am working with the kubernetes cluster available through Docker for desktop under windows. I am using helm v2, as I am currently evaluating devspace and my current deployment tool is skaffold, which does not cope well with helm v3. Therefore, I performed the following actions:
helm init
helm repo add stable https://kubernetes-charts.storage.googleapis.com
helm repo add bitnami https://charts.bitnami.com/bitnami

Then, I created a special namespace for my deployments with devspace:
kubectl create namespace devspace
devspace use namespace devspace

After that, I wrote the following devspace configuration:
version: v1beta6
deployments:
- name: minio
  helm:
    componentChart: false
    chart:
      repo: https://charts.bitnami.com/bitnami
      name: minio
    values:
      ingress:
        enabled: true
        annotations:
          kubernetes.io/ingress.class: nginx
        hosts:
        - name: assets.shopozor
          path: /
      mode: standalone
      clusterDomain: localhost
      persistence:
        enabled: false
        size: 10Gi
      disableWebUI: false
      accessKey:
        password: minio
      secretKey:
        password: minio123
      service:
        port: 9000

I tried to deploy it like this:
devspace dev

as well as
devspace deploy

I get the following error:
[fatal]  Error deploying: Error deploying minio: Unable to deploy helm chart: failed to download "https://charts.bitnami.com/bitnami/minio-3.0.7.tgz" (hint: running `helm repo update` may help)
Run `devspace purge -d minio` and `devspace deploy` to recreate the chart

Performing a
helm install -n minio bitnami/minio

works perfectly. Clicking the above provided link
https://charts.bitnami.com/bitnami/minio-3.0.7.tgz
in my favorite browser successfully downloads the tgz archive. Running the corresponding skaffold configuration works perfectly too:
apiVersion: skaffold/v2alpha2
kind: Config
deploy:
  helm:
    releases:
      - name: minio
        chartPath: bitnami/minio
        remote: true
        namespace: dev
        overrides:
          ingress:
            enabled: true
            annotations:
              kubernetes.io/ingress.class: nginx
            hosts:
            - name: assets.shopozor
              path: /
          mode: standalone
          clusterDomain: localhost
          persistence:
            enabled: false
            size: 10Gi
          disableWebUI: false
          accessKey:
            password: minio
          secretKey:
            password: minio123
          service:
            port: 9000

What did you expect to happen instead?
I expected the helm chart to be successfully deployed.
How can we reproduce the bug? (as minimally and precisely as possible)
The steps are described in the above first section.
Local Environment:

DevSpace Version: 4.5.4
Operating System: windows
Deployment method: helm v2

Kubernetes Cluster:

Cloud Provider: Docker for Desktop under Windows 10
Kubernetes Version:

Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:16:51Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:07:57Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}

Anything else we need to know?

/kind bug

@zadigus thanks for reporting this issue! I suspect this is caused by the helm repo caching between versions (there are sometimes issues when using v2 and v3 together) and should be fixed by deleting the ~/.helm folder, alternatively you can tell devspace to just use helm v2. The config you provided will use helm v3, so if you want to test devspace with helm v2 you can enable that via the v2 property in the deployments section. The above devspace config works for me without having to run any previous helm command.

It works fine if I use
deployments:
- name: minio
  helm:
    v2: true
    [...]

Thanks for the hint.


Deal with executable file command

Still working on it. Do not merge it :smile:
./bin/second_handler fb --token 'our_token' --id '817620721658179'

:arrow_up:  to move to previous page
:arrow_down: to move to next page
Ctrl + C to leave

@qoo392 @katy12032001 @yiweihuang
Please fetch this PR
$ git fetch origin pull/3/head:lockys-fb-feature
$ git checkout locks-fb-feature
$ ./bin/second_handler fb --token 'our_token' --id '817620721658179'
# our token is in our hackpad

I have merge #2 by @qoo392 into this patch.
Please check that, @katy12032001


Grey vertical lines with addon output

First off, thanks for the great addon to Screenly!  Your effort is much appreciated.  It works flawlessly with the exception of the video/HDMI addon.  Instead of showing the expected screen, it shows 2/3rds of the screen, but with an overlay of vertical grey lines.
I am running screenly on a Pi4 using screenly version 0.18.2.

Hello @moridin1138
sorry for the late answer, but I'm on vacation :D
This is very interesting. I haven't been able to test the whole thing on a Raspberry Pi 4 yet because I don't have these devices in my test environment or productive system.
Which version of the Raspbian system are you using? -> 86bit / 64bit -- Buster?
If you reinstall the add-on, the error remains?
Best
didiatworkz

Hola didiatworkz,
We are using 32-bit Buster to get this going.  It was a bit of a hack because I got it working using a pre-Pi4 version of Screenly.  Will try a reinstall on a spare Pi and see if the issue persists.
Thanks,
-brian

Hello @moridin1138
now that I have bought a Raspberry Pi 4 and installed screenly (docker version).
Afterwards the ose-monitiring and the add-on.
Everything worked without problems.
After no feedback and no problem I will close this issue.
Best didiatworkz


Assembling Everything

Assembling everything both hardware and software. Test our machine. Finding bugs.

The project is done


Add multi threading to r-address generation

Hey, nice :) I believe I did a relatively neat (quick and dirty but neat) implementation over here:
https://github.com/WietseWind/XRPL-Vanity-to-BigQuery
I had some instances running generating almost 10k accounts per second on decent machines (64 cores). It would be easy to strip out the BigQuery insertion and do matching + console.logging


ModuleNotFoundError: No module named 'tensorflow.python.training.device_util'

I got an error "ModuleNotFoundError: No module named 'tensorflow.python.training.device_util'" when I run train.py, my cuda version is 10.0, so I have to use tensorflow-gpu>=1.13.0, do you know how to slove it? I would appreciate it if you could answer my question.

Hi @suyouooooo ,
You must use the tensorflow version 1.12 to use this code.


Automate release creation

Creating a release should be less manual effort:

Can be triggered from GitHub
Version is automatically incremented (even if still with manual input major/minor/patch)
Major/minor/patch is automatically determined

Look into https://github.com/semantic-release/semantic-release/tree/master

Related #228


Could not locate that visualization

The dashboard works for Kibana 7? I imported the json files and I see the following message:
Could not locate that visualization (id: 618e79d0-78ae-11e8-a41e-1930b01c3fee)
Any ideas?

Which specific version of ELK stack are you using? Can you please share the JSON files for testing?


ISPN-5602 Create timeout scheduler executor

https://issues.jboss.org/browse/ISPN-5602
Notes for reviewer:

I didn't add any configuration for the timeout since the only thing configurable is the thread name.
In UnitTestTestNGListener, I changed to print the threads names only when trace is not enabled. (so no stack trace)
In JGroupsTransport, findbugs reported Collection<URL> confs as a possible source of NPE so I changed it.

Pushed, thanks


Fix outline pane text falls out container when user expand or collapse

Fix: #209757
Before:

After:

Hey 👋 @jrieken would you mind taking some time to review this PR?

Fix for #209757

It seems still repro in insider. Could you please take a time to review it? @jrieken
Version: 1.90.0-insider
Commit: 5f78b58b57b7cf84d28d801fed6bb4a48f908601
Date: 2024-05-09T05:51:12.471Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Code-Insiders/1.90.0-insider Chrome/120.0.6099.291 Electron/28.2.8 Safari/537.36

@bpasero @mjbvz It seems to still reproduce in the latest code-insiders. Anyone can help to review the changes?
Version: 1.92.0-insider
Commit: 06f8ef165cc37104bc78b7f36209d95333474348
Date: 2024-07-16T05:03:41.928Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Code-Insiders/1.92.0-insider Chrome/124.0.6367.243 Electron/30.1.2 Safari/537.36

Version: 1.93.0-insider
Commit: 336db9ece67f682159078ea1b54212de7636d88a
Date: 2024-08-30T18:47:32.318Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Code-Insiders/1.93.0-insider Chrome/124.0.6367.243 Electron/30.4.0 Safari/537.36
Seems still repo in the latest insider.


[CLI]: RuntimeError: "histogram_cpu" not implemented for 'BFloat16'

Describe the bug

When using BFloat16 floating point format, I get the following runtime error:
It seems that "histogram_cpu" is not implemented for 'BFloat16' in PyTorch.

Offending line:
https://github.com/wandb/client/blob/48b740a930648ce0a7c0f789a4e11042cb24d60b/wandb/wandb_torch.py#L215

Traceback:
Traceback (most recent call last):
  File "./examples/pytorch/language-modeling/run_clm.py", line 545, in <module>
    main()
  File "./examples/pytorch/language-modeling/run_clm.py", line 493, in main
    train_result = trainer.train(resume_from_checkpoint=checkpoint)
  File "/cluster/home/andstorh/transformers/.venv/lib/python3.8/site-packages/transformers/trainer.py", line 1400, in train
    tr_loss_step = self.training_step(model, inputs)
  File "/cluster/home/andstorh/transformers/.venv/lib/python3.8/site-packages/transformers/trainer.py", line 1984, in training_step
    loss = self.compute_loss(model, inputs)
  File "/cluster/home/andstorh/transformers/.venv/lib/python3.8/site-packages/transformers/trainer.py", line 2016, in compute_loss
    outputs = model(**inputs)
  File "/cluster/home/andstorh/transformers/.venv/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
    return forward_call(*input, **kwargs)
  File "/cluster/home/andstorh/transformers/.venv/lib/python3.8/site-packages/deepspeed/runtime/engine.py", line 1588, in forward
    loss = self.module(*inputs, **kwargs)
  File "/cluster/home/andstorh/transformers/.venv/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1123, in _call_impl
    hook_result = hook(self, input, result)
  File "/cluster/home/andstorh/transformers/.venv/lib/python3.8/site-packages/wandb/wandb_torch.py", line 113, in <lambda>
    lambda mod, inp, outp: parameter_log_hook(
  File "/cluster/home/andstorh/transformers/.venv/lib/python3.8/site-packages/wandb/wandb_torch.py", line 109, in parameter_log_hook
    self.log_tensor_stats(data.cpu(), "parameters/" + prefix + name)
  File "/cluster/home/andstorh/transformers/.venv/lib/python3.8/site-packages/wandb/wandb_torch.py", line 215, in log_tensor_stats
    tensor = flat.histc(bins=self._num_bins, min=tmin, max=tmax)
RuntimeError: "histogram_cpu" not implemented for 'BFloat16'

Additional Files
No response
Environment
WandB version: 0.12.11
OS: Linux-4.18.0-193.el8.x86_64-x86_64-with-glibc2.10
Python version: 3.8.3
Versions of relevant libraries: torch 1.10.2+cu113, transformers: 4.18.0.dev0, and deepspeed: 0.5.10
Additional Context
No response

Hi @andstor,
Thanks for writing in! Would it be possible for you to share a minimal reproduction of this bug? I'll pass it on to our engineering team to have this resolved.
Thanks,
Ramit
Weights and Biases Support

Hi @ramit-wandb,
following is a minimal reproduction of the bug.
Information
Model: GPT-2
Running on GPU cluster with 2 x NVIDIA A100 40G
To reproduce
Run causal language modeling example training script from Hugging Face: transformers/examples/pytorch/language-modeling/run_clm.py.
Hugging Face launch script:
export WANDB_LOG_MODEL=true
export WANDB_WATCH=true

deepspeed examples/pytorch/language-modeling/run_clm.py \
    --deepspeed ./zero2_min.json \
    --model_name_or_path gpt2 \
    --dataset_name wikitext \
    --dataset_config_name wikitext-2-raw-v1 \
    --overwrite_output_dir \
    --per_device_train_batch_size 8 \
    --logging_steps 1 \
    --do_train \
    --bf16 \
    --output_dir /tmp/test-clm

DeepSpeed config:
{
    "fp16": {
        "enabled": false
    },
    "bfloat16": {
        "enabled": true
    },
    "zero_optimization": {
        "stage": 2,
        "offload_optimizer": {
            "device": "cpu",
            "pin_memory": true
        },
        "allgather_partitions": true,
        "allgather_bucket_size": 2e8,
        "reduce_scatter": true,
        "reduce_bucket_size": 2e8,
        "overlap_comm": true,
        "contiguous_gradients": true
    },
    "gradient_accumulation_steps": "auto",
    "gradient_clipping": "auto",
    "steps_per_print": 100,
    "train_batch_size": "auto",
    "train_micro_batch_size_per_gpu": "auto",
    "wall_clock_breakdown": false
}

After 100 steps, it fails with the following error:
RuntimeError: "histogram_cpu" not implemented for 'BFloat16'

Debug logs
debug.log
debug-internal.log

Hi @andstor,
Thanks for the information! I looked into this further, and it looks like histogram_cpu is actually a function belonging to PyTorch, not wandb:
https://github.com/pytorch/pytorch/blob/bc03c1d000dcb8417fc771a49165c2b963278092/aten/src/ATen/native/Histogram.cpp#L345-L350
This is something that would have to be resolved by the PyTorch team. I recommend contacting the PyTorch team to resolve this.
Thanks,
Ramit

Closing this ticket since there is nothing to be done here.
Thanks,
Ramit

This seems to be fixed with the release of pytorch 1.12


Labels with Chinese characters are not shown on Android 12

A user of our app reported that on Android 12 labels with Chinese characters are not shown on the map. I have checked it and unfortunately, it is the case that on Android 12 (Pixel 3a device) labels with Chinese characters are not shown. On Android 11 and older it is working properly. I have also tried to target Android 12 in our app and it did not helped. I have not digged into Tangram-ES what could be the case yet, I am just reporting it now. I am also attaching screenshots from our app (Walkabout style) and I have also noticed that it is not working in StreetComplete app too (@westnordost). Screenshots are showing Taiwan.

If I remember correctly we access system font files for part of our label rendering pipeline. Since it's working on android 11 but not on android 12, it would be good to verify if font file (fallback) exists and at the correct location on android 12. Maybe comparing font.xml on 11 and 12 should provide some hint.

@tallytalwar thank you a lot. I have checked fonts.xml on Android 11 (Samsung Galaxy Tab A) and on Android 12 (Google Pixel 3a) and there is a difference. It seems that parser cannot parse fonts.xml on Android 12 because it contains text and also inner tags:
<familyset version="23">

    <family name="sans-serif">
    Roboto-Regular.ttf
      <axis tag="ital" stylevalue="0" />
      <axis tag="wdth" stylevalue="100" />
      <axis tag="wght" stylevalue="100" />

    ...

this is from Android 11:
<familyset version="23">

    <family name="sans-serif">
      Roboto-Thin.ttf
      ...

I am attaching these fonts.xml files:
Google Pixel 3a (Android 12) fonts.xml:
https://gist.github.com/rwrx/a1e16c0ce834b27d3855df40eab32f7d
Samsung Galaxy Tab A (Android 11) fonts.xml:
https://gist.github.com/rwrx/c6000e5187641fbb5d5fbf529e97190c
I am not sure what do to with this, as I have discovered that FontConfig.java file which is parsing this fonts.xml file is using XmlPullParser and it throws exception due to this (incorrect?) fonts.xml file.

Our approach for locating system fonts has been unfortunately limited by the fact that the font XML files are both un-documented and non-standardized. App developers are not supposed to parse them. Our code is able to handle many font XML files, but it often breaks when new Android versions are released.
Fortunately, in API level 29 Android added an interface for accessing system fonts programmatically: https://developer.android.com/reference/android/graphics/fonts/SystemFonts We still want to support older versions of Android, but when Tangram ES is running on a new enough version we could use this API to locate the available system fonts (including CJK fonts) without parsing XML at all.
This change will require some time to implement and test. In the meantime, you can work around these font errors by bundling your own font with support for Chinese scripts and referencing it in your Tangram scene: https://tangrams.readthedocs.io/en/main/Syntax-Reference/fonts/

Thank you. Now I can see that this is not that easy to implement. I have tried to make use of SystemFonts, but unfortunately I cannot find a way to get importance of font fallbacks. It is only returning system fonts.
At least I have tried to modify getFontFallback method:
public static synchronized String getFontFallback(final int importance, final int weightHint) {
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.S) {
        String fallback = "";

        if (importance == 0) {
            Set fonts = SystemFonts.getAvailableFonts();

            for (Font font : fonts) {
                File file = font.getFile();
                String filePath = file.getAbsolutePath();

                if (filePath.toLowerCase().contains("cjk") && filePath.toLowerCase().contains("sans") && font.getStyle().getWeight() == weightHint) {
                    fallback = file.getAbsolutePath();
                    break;
                }
            }
        }

        return fallback;
    }
    else {
        if (!initialized) {
            init();
        }

        int diffWeight = Integer.MAX_VALUE;
        String fallback = "";

        for (int i = 0; i < fallbackFontDict.size(); ++i) {
            int diff = Math.abs(fallbackFontDict.keyAt(i) - weightHint);

            if (diff < diffWeight) {
                final List<String> fallbacks = fallbackFontDict.valueAt(i);

                if (importance < fallbacks.size()) {
                    fallback = fallbacks.get(importance);
                    diffWeight = diff;
                }
            }
        }

        return fallback;
    }
}

But it is really a "hack" and I assume that it will work only on my device model Google Pixel 3a or in better case on all models from Google or Android One. @matteblair do you have some hints on how to improve this "hack"?

Users of StreetComplete report that no text is displayed at all on Android 12. I use a style which sets the font family of every label to a custom font ("Roboto", Android's default font). If this is indeed the same bug, I'd propose to change the title.

Yes, to me it seems that it is the same bug. Maybe changing title to something like "No system fonts fallback on Android 12"?

Sorry I've been slow to follow up on this - my job has been keeping me busy!
Since the current approach to locating fonts is clearly causing problems on Android 12, I think the Android font loading logic should add a completely new code path for API level 29 or newer that builds both fontDict and fallbackFontDict using the new Font APIs instead of parsing XML.
I don't expect this to be terribly complicated but it will require a bit of time to implement and test.

@matteblair thank you for your answer. Is there some way I can help with this to be implemented sooner?

I've started working on this. Unfortunately there is more to the problem than I initially understood. I've run into two issues:

The SystemFonts API doesn't have an obvious way to determine which fonts should be treated as "fallbacks" and what order they should be checked. This information was previously determined by the fonts.xml structure. For some fonts it's possible to look for strings like "CJK" in the file name, but this is incomplete and not robust.
In Android 12 the system fonts no longer use separate files for weight variations like "light" and "bold". Instead, these variations are encoded in a single font file using "variation axes". Tangram's font code doesn't currently handle font variation axes, and until it does we won't be able to load "light" or "bold" versions of any system fonts. This is less important than getting basic text rendering working for all languages, but still needs to be addressed.

I'm still researching answers to these problems - just wanted to give a status update.

@rwrx @westnordost This issue was auto-closed because I believe #2306 resolves it, but please give this latest change a try and let me know what you see!


Replace torchaudio.load_wav with common_utils.load_wav

This PR replaces torchaudio.load_wav with common_utils.load_wav, which is a wrapper around scipy.io.wavfile.read.
This allows each test to not depend on torchaudio's I/O implementation.

thanks


[Feature]: when will publish a new version

🚀 The feature, motivation and pitch
Vllm add some exciting features like guiding json  and tokenization more faster, I'm looking forward to see these feature in the next version.
I wounder that when will bump a new version of vllm?
Alternatives
No response
Additional context
No response
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

You can always run the latest nightly with:
pip install https://vllm-wheels.s3.us-west-2.amazonaws.com/nightly/vllm-1.0.0.dev-cp38-abi3-manylinux1_x86_64.whl

See here for more pre-install pathways: https://docs.vllm.ai/en/latest/getting_started/installation.html#build-from-source


scoped packages

Type of Issue
[x] Bug Report
[ ] Feature Request

Description
running npm run packagr for a scoped package (e.g. @test/test will produce a folder called @test under dist.
Running npm pack or npm publish then throw errors, no such file or directory.
How To Reproduce
In package.json name your package "name": "@test/test"
Then run npm run packagr.
Under dist a folder called @test is created.
Expected Behaviour
The folder should probably just be called test, without @.
Version Information
ng-packagr: v1.5.0-rc.1
node: v8.8.1
@angular: v5.0.0
rxjs: v5.5.2
zone.js: v0.8.14

This is a duplicate of #218

As described in #218, npm v5.3.0 works fine.
The bug should be fixed as documented in https://github.com/npm/npm/pull/19033


determining on the client side if the failed request will be queued or not

Library Affected:
"workbox-background-sync": "^6.5.3",
"workbox-core": "^6.5.3",
"workbox-precaching": "^6.5.3",
"workbox-window": "^6.5.3"
Browser & Platform:
all browsers
Issue or Feature Request Description:
TLTR
On the client side - how to tell if the failed request will be queued or not?
Else
sw.js
import {
  precacheAndRoute,
  cleanupOutdatedCaches,
  createHandlerBoundToURL,
} from "workbox-precaching";
import { NavigationRoute, registerRoute } from "workbox-routing";
import { Queue } from "workbox-background-sync";
import { NetworkOnly } from "workbox-strategies";

const queue = new Queue("myQueueName", {
  onSync: async ({ queue }) => {
    let entry;
    while ((entry = await queue.shiftRequest())) {
      try {
        await fetch(entry.request.clone());
      } catch (error) {
        await queue.unshiftRequest(entry);
        throw error;
      }
    }
  },
});

precacheAndRoute(self.__WB_MANIFEST);
cleanupOutdatedCaches();
registerRoute(new NavigationRoute(createHandlerBoundToURL("index.html")));

const statusPlugin = {
  fetchDidFail: async ({ originalRequest, request, error, event }) => {
    console.log("fetchDidFail");
    queue.pushRequest({ request: originalRequest });
  },
  fetchDidSucceed: ({ response }) => {
    console.log("fetchDidSucceed");
    return response;
  },
};

registerRoute(
  new RegExp(".*/Exercises/.*"),
  new NetworkOnly({
    plugins: [statusPlugin],
  }),
  "POST"
);

On the client using axios:
    const add = async () => {
      try {
        var response = await axiosInstance.post("Exercises/Create", { name: 'test' });
      } catch (error) {
        console.log(error);
       // Error, but what kind of error?? Will the request be queued or not??
       // 400, 401, 5xx, etc, or network unavailable
      }
    };

The flows are following:

case: no connection (ERR_NETWORK), or service unavailable (ECONNABORTED)

send post request from UI
client catches exception in add method
(with delay) in sw.js  - fetchDidFail is invoked, request added to queue

case: bad request 400 (ERR_BAD_REQUEST)

send post request from UI
client catches exception in add method
(with delay) in sw.js  - fetchDidSucceed is invoked, request NOT added to queue

So in all 3 cases the client catches an exception while making a request. But the request will be queued only in some cases.
I would like to know in advance on the client side if the request will go through the fetchDidFail or the fetchDidSucceed chain! This is so that I could warn the user that the request execution failed, but will be retried later! The item should then be added to a indexeddb storage.  In case when the request is not queued - user just gets the error message and nothing gets stored.
So how to accomplish this?
Notes

I don't want to check for hardcoded error codes (ERR_NETWORK/ECONNABORTED/ERR_BAD_REQUEST). They come and go with new specifications, so I can't account for all situations using this method. Need a more robust solution. Unless??
If possible, I don't want to rely on a missing http status code (0) in response. Because I have noticed that in some cases this value is set to 0 when backend dotnet server throws the internal error (5xx http status code). When the CORS headers are not properly set for response then axios reads all codes as 0 (feature, not a bug). So this code is not reliable in my case.

I have looked into the "second note" more and decided to check if the fetch API is any different than the axios.. and it's not!
Meaning, if there is CORS problem - the service worker will always treat all responses with fetchDidFail!
so

case 1: 500 error thrown by the server, valid CORS in response - fetchDidSucceed, not added to queue
case 2: 500 error thrown by the server, invalid CORS in response - fetchDidFail, added to queue

I am surprised that this scenario is not properly addressed by the community. Maybe it is I am just not aware of it?
So, I think I actually have 2 problems:

how to distinguish to-be-queued requests
distinguish false-positive failed requests where status code is read as 0

Am I correct to assume that if 2. is fixed then we can use the status code to fix the 1.?
My proposed solution - on the server side it is possible to set the custom header such as x-status-code that will always have the exact value as the real status code. Now we just need to tell the fetch logic of the worker service to use this header as a reference to making decisions!
So the question is - is it possible to override the fetch event of the service worker and tell him to use the custom header to decide whether the request failed or not?
I am guessing default logic is something like
try {
    fetch(request)
    fetchDidSucceed(request)
}
catch (error) {
    fetchDidFail(request, error)
}

but we need to change it to
var response;
try {
    response = await fetch(request)
    fetchDidSucceed(request)
}
catch (error) {
    if (response.hasHeader("x-status-code")) {
        fetchDidSucceed(request)
    }
    else {
        fetchDidFail(request, error)
    }
}

Then, when it's done, I should be able to use the x-status-code header on the client side to determine if the fetchDidSucceed or fetchDidFail is going to be executed - or even better - maybe axios will treat responses as success because I can force-override the response and set the correct/actual status code. Is this correct?
I will continue to dig to this direction while there is no answer to this topic. Please let me know if this is a wrong lead. Or maybe this problem has already been solved by smart minds :)

Does this information from the docs help explain what's going on?

BackgroundSyncPlugin hooks into the fetchDidFail plugin callback, and fetchDidFail is only invoked if there's an exception thrown, most likely due to a network failure. This means that requests won't be retried if there's a response received with a 4xx or 5xx error status. If you would like to retry all requests that result in, e.g., a 5xx status, you can do so by adding a fetchDidSucceed plugin to your strategy:

const statusPlugin = {
  fetchDidSucceed: ({response}) => {
    if (response.status >= 500) {
      // Throwing anything here will trigger fetchDidFail.
      throw new Error('Server error.');
    }
    // If it's not 5xx, use the response as-is.
    return response;
  },
};

// Add statusPlugin to the plugins array in your strategy.

I know that talks specifically about the BackgroundSyncPlugin, but all that plugin does is set up a fetchDidFailcallback, which you're already doing manually.

If I understood this correctly - any non-0 status code is threaded as failure.
According to my observations - fetch will return a 0 status code/failure when there is a CORS issue with the response. Even if the service itself has processed the request correctly. My question was how to override the fetch response or the logic for fetching so I could handle the false-positive responses..
I have made a discovery that when axios is used with the custom timeout value - this timeout value essentially cancel's out all of the logic executed by workbox handler.
So if the client makes a request and it fails because of the axios timeout - the client will see the error message before the fetchWillFail callback is executed. This raises all kinds of problems, such as - you are not able to modify the response in the services worker, because user has already gotten this response.. The solution to this problem is to ditch the timeout property of the axios and start using the networkTimeoutSeconds which is global for all requests. This seems to the downside to this approach that you can't override this value per-request since it's private and is per-strategy.
But this will allow me to move forward at least.


metricsbp: Add total counter to span hooks

We only need 2 of fail, success, and total. Before this change we use
fail and success, and eventually I think we would want to use fail and
total instead, but keep success for now for backward compatibility.
The reason success and total won't work is that there's no way to
guarantee that the success and total counter gets reported atomically,
so it would lead to situations that success reported a slightly higher
rate than total, which screws up the rate calculating. Although
theoretically this is also an issue with fail+total (or fail+success),
they are much more tolerable than success+total.

cc @spladug

Yea the main concern is around sampling. The experience is that we usually do need to sample on timers/histograms, and do not need to sample on counters.


MachVibes sound not working on Dev C++

I have to use dev c++ as my IDE so i installed it but when i type in the editor the machvibes stop generating sound even its not on mute. Unlike other editors it does not produce sound

Try running mechvibes as admin. If that doesn't work, unfortunately, the app may be blocking other apps from listening to your keypresses. We can't fix that at this time.


hide the filterable list + request focus to open keyboard

For the most part of it, this library is great. However, I've been pulling my hair over simple issues.

How do I hide the filterable list manually? Once it's open, there's no way to close it other than clicking an item. I've tried

mChipsInput.setFilterableList(new ArrayList<ChipInterface>());
mChipsInput.getEditText().getFilterableListView().fadeOut();
mChipsInput.getEditText().getFilterableListView().fadeOut();
mChipsInput.getFilterableList().clear(), and called mChipsInput.invalidate() afterwards

The view logic is just so poorly designed, none of these seem to work. I've been digging into the source code and see that fadeOut() is to hide it from within the library. Why doesn't it work when used as an api?

Open the soft-keyboard automatically when the mChipsInput is clicked.
I've tried the following:
 mChipsInput.requestFocus();
 mChipsInput.getEditText().requestFocus();
 openKeyboard(mChipsInput.getEditText());  // this uses the InputManager to open the keyboard on this view.
 mChipsInput.getEditText().performClick();

Again, none of these work!

Turns out it was a really silly line in the code that was causing the issue as for 1.
I've sent a PR #99
It creates the edittext only once, instead of creating a new one each time getEditText is called.


Refresh (watch) labels

is it possible refresh the model when i add new items to labels ?

Current version is not watch labels, so is'nt refresh or change labels attribute


Redis Vector Sentinel Support

Expected Behavior

Need support to connect to multiple Redis sentinel nodes
Current Behavior

Currently, only one redis node connection is supported.
Context

As the Redis support builds upon Spring Data and Spring Boot support for Redis, you can configure this using application configuration properties.  See https://dzone.com/articles/redis-sentinel-with-spring as a start.


Release azure-cli-feedback 2.0.1

Reviewers, please verify the following for this PR:

[ ] The PR title has format Release <component-name> <version>.
[ ] setup.py has been modified with the same version as in the PR title.
[ ] HISTORY.rst has been modified with appropriate release notes.
[ ] If releasing azure-cli or azure-cli-core, __version__ defined in __init__.py should also be modified to match.

Started releasing azure-cli-feedback 2.0.1...

Release of 'azure-cli-feedback' with version '2.0.1' successful. View at https://pypi.python.org/pypi/azure-cli-feedback/2.0.1.

GitHub release created. https://github.com/Azure/azure-cli/releases.

Codecov Report

Merging #2887 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2887   +/-   ##
=======================================
  Coverage   63.17%   63.17%
=======================================
  Files         466      466
  Lines       26139    26139
  Branches     3997     3997
=======================================
  Hits        16514    16514
- Misses       8544     8547    +3
+ Partials     1081     1078    -3

Impacted Files
Coverage Δ

...dback/azure/cli/command_modules/feedback/custom.py
34.69% <0%> (ø)
:arrow_up:

...-cli-role/azure/cli/command_modules/role/custom.py
31.95% <0%> (ø)
:arrow_up:

src/azure-cli-core/azure/cli/core/util.py
68.99% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 923dfa6...302559b. Read the comment docs.


update css to remove extra padding

This PR fixes #13375

Pull Request Test Coverage Report for Build 373116772

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 41.221%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/jupyter/serverInstance.ts
4
73.81%

Totals

Change from base Build 372769611:
-0.01%

Covered Lines:
21770

Relevant Lines:
48454

💛  - Coveralls


TimePicker data-minutes-step="15" always selects 0 minutes

Hi,
i'm not sure if this feature is fully developed because it is not documented, but if it is there is a bug! 😄
Besides not selecting correct value, it seems scroll doesnt center.

Vedran

At the moment I am left without a computer, so it will be difficult for me to help. Details on https://www.facebook.com/metrouicss

What is your browser?

Hi Olton,
tnx for getting back at me! I tested in Edge, FF and Chrome.. After some more testing, it seems that returns initial value (not only 0), and sometimes i can switch value only to 0 if it set for example to 15 and thats it..
Vedran

Here's code pen if it helps:
https://codepen.io/dugi007/pen/VwjJZYg

Thank you, fixed in 4.4.3, check it.

Tnx! Works like a charm!


filter out invalid k-v events when applying kv-file on PiTR

Signed-off-by: joccau<EMAIL_ADDRESS>
What is changed and how it works?

Issue Number:
Close https://github.com/tikv/tikv/issues/13853
Ref https://github.com/pingcap/tidb/issues/39398
What's Changed:

filter out invalid k-v events when applying kv-file on PiTR

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

[x] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
Filter out invalid k-v events when applying kv-file on PiTR

/run-test

/merge


Initial draft of a release process for the cellxgene-schema PyPI package

This is a first draft of a release process to release new versions of the cellxgene-schema PyPI package. The process is very similar to the release process of cellxgene Desktop but with one notable exception. I have simplified the release process to exclude rc versions for now. Until burning of version numbers becomes a problem, I figured we can stick to just releasing to Test PyPI first and if we burn a version number there, we should note it and just use the next.
Note: I have not tested this process myself so please double check my work. Or if it's conveniently, please trial it on a new release and make changes accordingly.

Just to clarify, if we burn a version number on testpypi and we bump to the next, then when we release in pypi there will be "skipped" versions?

Just to clarify, if we burn a version number on testpypi and we bump to the next, then when we release in pypi there will be "skipped" versions?

Yep. The alternative is that we use the rc suffix to first push out the trial release candidates. So for example, if we want to release 0.2.1, then first we release 0.2.1rc0 to verify that the release looks good. If it looks bad, then you can bump up to 0.2.1rc1 and so on until you're satisfied and then finalize the release into 0.2.1. It adds an addition step in the release process but does avoid burning version numbers.
On cellxgene Desktop we used to do it with burned numbers (you can see the old burned numbers here) but switched to rc after we (ahem, I) burned quite a few. But until we burn a bunch, I opted for the simpler process.

Just to clarify, if we burn a version number on testpypi and we bump to the next, then when we release in pypi there will be "skipped" versions?

Yep. The alternative is that we use the rc suffix to first push out the trial release candidates. So for example, if we want to release 0.2.1, then first we release 0.2.1rc0 to verify that the release looks good. If it looks bad, then you can bump up to 0.2.1rc1 and so on until you're satisfied and then finalize the release into 0.2.1. It adds an addition step in the release process but does avoid burning version numbers.
On cellxgene Desktop we used to do it with burned numbers (you can see the old burned numbers here) but switched to rc after we (ahem, I) burned quite a few. But until we burn a bunch, I opted for the simpler process.

Gotcha! I like the cleanness of the RC nomenclature, and it's not a big extra effort. I'd be inclined to keep it.

Done! I've updated the process to include the rc tag so that we don't burn any version numbers moving forward. There is one additional sibling PR to review now that includes new commands to manage the rc versioning.


wont let me paste images onto the canvas

One day it just stopped working, but copying an image and pasting it onto the canvas with ctrl+c and ctrl+v no longer works, as well as with inserting pictures as files. The problem is only with pasting images as layers, not as just an image. This makes it extremely hard to use references. It only happens on my chromebook, not my mac.
Screen recording 2023-11-07 5.52.12 PM.webm

It failed sometime between October 15th and October 21st.
When I try to edit > transform, it gives me the popup that the layer is empty.

No, it is not.  I'll try it on a different chromebook when i get the chance

It says it is HP and Qualcomm, I'm not sure which one you're looking for. I am unsure of what the model name is. I believe my friend's was a different model because it had a different design and a few keys that were different as well.  My Chrome OS version is 117.0.5938.157
I believe it does always happen, I just tried with a fresh Kleki tab. Disabling extensions did not work, and I am up to date on the Chrome OS updates.

I'm sorry, my chromebook has a different label on the bottom and I'm unable to locate the model. If there is anything I can try to do on the Kleki tab that may aid in locating the issue, I would be happy to help.

hey, just wanted to drop in since I saw this and know how to find the model name without the labels.

Go to chrome://system/
Do ctrl+F and enter "model_name" (without the quotes)
You should see something like the below image, but you'll likely see a different model name after the = sign.

Hope this helps!

When I go there and ctrl+F model_name it doesn't give me any results. Thank you for trying to help though!


Configures the test image with a custom DNS server.

This change allows users to set a custom DNS server in the config.json of the test device. The
DNS server is only set if the environment variable DNS_SERVER is set to a non-zero value.
This is needed to test with a balenaCloud instance whose address can only be resolved using a custom
name server. This is a common setup for balenaMachine deployments in air-gapped networks.
Change-type: patch

LGTM


GCC 6.3, need to remove parameters

When I try to install this on debian stretch with GCC 6.3, the node-gyp rebuild step fails with the following error:
><EMAIL_ADDRESS>install /home/barco/test/node_modules/v4l2camera
> node-gyp rebuild

make: Entering directory '/home/barco/test/node_modules/v4l2camera/build'
  CC(target) Release/obj.target/v4l2camera/capture.o
In file included from ../capture.h:7:0,
                 from ../capture.c:1:
/usr/include/linux/videodev2.h:2126:20: error: field ‘timestamp’ has incomplete type
  struct timespec   timestamp;
                    ^~~~~~~~~
v4l2camera.target.mk:112: recipe for target 'Release/obj.target/v4l2camera/capture.o' failed
make: *** [Release/obj.target/v4l2camera/capture.o] Error 1
make: Leaving directory '/home/barco/test/node_modules/v4l2camera/build'
...

If I manually clone this repo to node_modules and remove the -std=c11 and -std=c++14 flags from the binding file, everything seems to build and work.

#30


Help!!  "Too many requests, please try again later"

Hi, I just bought and setup the Govee Wi-Fi Water Sensors Alarm, which includes 1 Gateway (H5040) and 3 Leak Sensors (H5054).
After the initial setup, everything was working fine with the senors and the Govee app (the alarms sounded and the app sent notifications when testing the leak sensors with water).  Then, I installed and setup the Govee homebridge plugin.  At this point, everything also seemed fine within the Apple Home app—all of the leak senors were showing.
Then, after setting up the Govee homebridge plugin, tested one of the leak senors (with water) and the alarm sounded.  However, no nonfiction was received from the Govee app or the Apple Home app.
Note: this is my first Govee product, and my first time installing and using the Govee homebridge plugin.
At this point, I opened the Govee app to check the devices... and when attempting to view any of the sensor devices, I get the following messing...

Too many requests, please try again later

As a result, the Govee app is currently useless and I do not receive any notifications, and I am not able to check any of the devices within the app.
Any ideas for resolving this issue?  Also, any ideas what happened and how to ensure I can use both the Govee app and the Govee homebridge plugin?  Btw, I disabled the plugin and am still experiencing this issue.
Any help would be greatly appreciated.  I would love to use this plugin, but being able to use the Govee app is important—I need it to function properly again.

Update:
After a few days, the "too many requests" message stopped and the app functions properly with the water leak sensors.
That said, I am nervous about trying the Homebridge plugin again, as this is what started the problem.
Is there any way to adjust any settings for the plugin to ensure this does not happen again?
Also, does this plugin allow for HomeKit (Home app) notifications, when water is detected, or is it only for viewing the status and battery level of the water leak devices?

I eventually re-installed and re-setup this plugin and didn't have any issues the second time around.


<rh-navigation-secondary>:  aria-label on the nav in the shadowroot should be customizable

For other elements we've used accessible-label property to set and customize labels such as this, this would also be an improvement for translations.

navigation-secondary has two shadow children: a <nav> and an overlay
why not change the nav to a div, make the host a role: navigation

At the point of applying aria-label on the host for backwards compatibility does it even make sense to add accessible-label property now?  Given we are applying that right back to the host element now that it becomes role=navigation through internals.


restrict geocoder with max bounds

is it possible to restrict search results to max bounds?

Hi @chiho13, you can use the bbox prop. Here's an example https://codesandbox.io/s/reactmapglgeocoder-bbox-example-zzlf1.


stop logging host and instead use pubkey

This PR makes changes to log messages in createChannel where we are logging the host, however the host may not be available at all times. Instead we should log the pubkey

did you miss https://github.com/sparkswap/lnd-engine/pull/191/files#diff-b7e454eb5526d0778b8abb6f047c155dR81

@martineehrlich yess good catch

 Prevent LND-Engine from logging the host


V2: Make ZIO microsite look really nice scalaz#220

@Vilkina Could you post a screenshot of what this looks like, so people won't have to build the PR? :)

@NeQuissimus , you can see the screenshot by following this link https://pbs.twimg.com/media/DracK4AWkAEhDjH.jpg:large

@NeQuissimus , how can I restart Travis?

Only project members can.
I have no idea why the build consistently times out now...
It happens on master as well.
@jdegoes ?

@NeQuissimus Does it time out at the end, or during tests?

Right after the tests, there is no output for > 10 minutes and then Travis considers the build stalled.

I need to do PR to another issue. Should I create another branch or I have to merge this PR, and than create PR for another issue?


[Backport 4.8.x] Fix for RestOpenApiProcessor for parsing path variables from the http…

… request uri succesfully.  (#16220)

Update RestOpenApiProcessor.java

if uri is not starting with slash then remove the slash in the consumerPath from the openApi spec, because if there is any path variables (/../{id}) in the consumerPath and the uri does not start with "/" then  HttpHelper.evalPlaceholders method throws an ArrayIndexOutOfBoundsException.

code style fixes and added null check the uri.

Description

Target

[ ] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[ ] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

There are tests failure in Camel JBang plugins which are not related to this PR. @oscerd is it fine to merge anyway given the problems are not within this PR? not sure the policy we're adapting here in the core. Thanks.


Suppress errors in anomoly detector for now.

Python pipelines are broken due to a bad README.md file, this suppresses that issue for now.

@lmazuel ... when you get a chance can you take a look at the Anomaly Detector README?


v2.63.3 control-iq incremental data uploads fail

Briefly: uploading control-IQ data throws an error when the v2.63.3 uploader is in incremental mode, but no error is thrown if one switches the uploader to 'all' mode.  I can confirm that control-iq data has made it into the web app, but I can't confirm if that occurred before or after I switched to 'all' mode; specifically, I don't know if the incremental uploader actually worked, but just threw a noisy error.  My suspicion is 'all' is what got the data in there.
Either way, from the UI, this is all I get:
 .
Forcing drivermanager debug mode, this is what I find in the console:

Note that stack trace is taken from commit tag v2.63.3.  That's pretty much it; there isn't anything else I can find in the console logs.
The pump in question is firmware_version: 105900, deviceModel: "1002717" .  If you need more identifiable information please ping me and I can privately share whatever logs/ID's you may need to trace this.
If you need me to retry something, or pull a trace ID out of the session- just let me know how.  I've verified this failure for both windows and linux versions, but I'm fine w/ mangling my local linux version (or trying branches) as needed if it helps.
Thanks for the integration either way; this is observability of control-iq I've been doing by hand, and this feature is greatly appreciated.

As the error message says, there's not enough Control-IQ data in your incremental data for an upload. In short, we require there to be at least one change from automated to manual (or vice versa), to be able to correctly classify automated basals. You can manually trigger an automated->manual change by suspending and resuming, or perform an "all data" upload (as you already discovered).
I'm open to suggestions for making the error message clearer :wink:

So... just confirming what you said via testing; I triggered an upload today, which went through fine.  Since yesterday and today I've had a suspension (cartridge change).  That worked w/out error; running the upload immediately again, that however triggered the error.  TL;DR: what you describe is exactly what I'm seeing.
As to a suggestion: I kind of strongly argue you shouldn't present this as an error to the user.  It's not an error if the user manages to stay in control-iq automation; that's actually the desired state.  :)
Better question; why does the code view this as an error?  Is it treated as an error because the 'fetch data range' function doesn't get results for control-iq, and is unable to discern if that's a failed fetch, or lack of data?  Is that a limitation of the protocol spec for tandem?
If it is a limitation- inability to tell if the fetch failed, or if there was no data- tidepool knows the last control-iq data point.  It's a blood fricking hack, and presumably annoying for your API/PII models, but the uploader could ask for the last control-iq timestamp, and then ask the pump for -1...current.

It's a limitation of the protocol spec for Tandem. You're right that we could retrieve the last Control-IQ mode change from the backend, and that's likely what we'll have to do if we can't identify another solution with Tandem. In the meanwhile we're monitoring how often this happens, to be able to prioritise a workaround/fix. Our current assumption is that most people don't upload every day, so would have a cartridge change (or some other suspension) happening between uploads.

For my particular case, I don't have any suggestion beyond what you already know.  It might be worth putting out a minor version release that tweaks the error message to clarify "this isn't an error if there is no fresh data"- I would've skipped reporting it if I saw that message, but I may not be representative of your userbase.
Either way, I appreciate the clarifications, but I don't really have a suggestion beyond the above.  You're in a rock/hard place if the firmware isn't giving you the necessary clarity.  The best I can think of is doing a "try incremental, get an error, fetch the timestamp from tidepool services, then retry w/ that timestamp to confirm error vs no data"... which is painful.
If you've got anything you want tested in regards to above, give a yell; I don't upload data daily, but I try to.

This issue was fixed in v2.49.0, released 21 February 2023.


uv run --no-project excludes virtual environments that are not in projects

e.g. when a virtual environment is active or discovered with a pyproject.toml alongside:
❯ tree .
.

0 directories, 0 files

❯ uv venv
Using Python 3.12.3 interpreter at<EMAIL_ADDRESS>Creating virtualenv at: .venv
Activate with: source .venv/bin/activate

❯ uv run  python -c "import sys; print(sys.executable)"
/Users/zb/workspace/example/.venv/bin/python

❯ uv run --no-project python -c "import sys; print(sys.executable)"
/Users/zb/Library/Caches/uv/builds-v0/.tmphJIdvS/bin/python

❯ source .venv/bin/activate
❯ uv run --no-project python -c "import sys; print(sys.executable)"
/Users/zb/Library/Caches/uv/builds-v0/.tmpxmAgQo/bin/python

Should --no-project apply here? I'd expect this to require a separate flag.

Hmm yeah.

Basically, it should have no effect when you're not in a project (whereas right now, it does).

What would you use to avoid .venv detection? --isolated?

I think so?


Date conversion failes

This is a really cool project but when I try to run it I only get a "Unexpected character encountered while parsing value: {. Path 'Alerts[0].Activation', line 1, position 6576."
Which points to ""Activation":{"$date":{"$numberLong":"1543679128601"}}" in the json.
So there is some error with the date conversion here or Im missing something.

Hey! I'll check it out, but this project is currently under rewrite. You can check the rewrite branch for more details. The current implementation lacks a lot of things and is generally bad.

@niklasCarstensen can you send the full stacktrace?

@niklasCartensen you need to use api.warframestat.us not the base worldstate from DE

Ohh I didn't expect DE to have multiple worldstate jsons
Also thanks for answering so fast, I didn't expect that either. ^^
Im using your library here if you wanna look over it.
I hope Im using the license correctly.

The banner was still there from the fork but I removed it now and I also added the license to this project into the readme now

Looks good, however, I do think that the copyright has to be included? I'm bad with licenses so don't quote me on this ^^'

oh, i see now. you're writing an update for an existing C# app one of ours had made some time ago.

If you just wanna write a PR on it, we can probably rope you in and let you just help maintain it


chore(main): release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2024-01-27)
Features

fix (#8) (aa829d3)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ryanhanks-bestow/__a_test/releases/tag/v1.1.0 :sunflower:


Could not load bitsandbytes native library: 'NoneType' object has no attribute 'split'

System Info
System Info
bitsandbytes 0.43.1
Python 3.10.12
"CUDA" library: rocm-libs Version: <IP_ADDRESS>000-91~22.04
Ubuntu 22.04.1
Getting the following error after Mistral safetensors are downloaded:
Could not load bitsandbytes native library: 'NoneType' object has no attribute 'split'
Traceback (most recent call last):
File "/home/user/Documents/python-env/jupyter-default/jupyter-default/lib/python3.10/site-packages/bitsandbytes/cextension.py", line 109, in
lib = get_native_library()
File "/home/user/Documents/python-env/jupyter-default/jupyter-default/lib/python3.10/site-packages/bitsandbytes/cextension.py", line 88, in get_native_library
cuda_specs = get_cuda_specs()
File "/home/user/Documents/python-env/jupyter-default/jupyter-default/lib/python3.10/site-packages/bitsandbytes/cuda_specs.py", line 39, in get_cuda_specs
cuda_version_string=(get_cuda_version_string()),
File "/home/user/Documents/python-env/jupyter-default/jupyter-default/lib/python3.10/site-packages/bitsandbytes/cuda_specs.py", line 29, in get_cuda_version_string
major, minor = get_cuda_version_tuple()
File "/home/user/Documents/python-env/jupyter-default/jupyter-default/lib/python3.10/site-packages/bitsandbytes/cuda_specs.py", line 24, in get_cuda_version_tuple
major, minor = map(int, torch.version.cuda.split("."))
AttributeError: 'NoneType' object has no attribute 'split'
CUDA Setup failed despite CUDA being available. Please run the following command to get more information:
python -m bitsandbytes
Inspect the output of the command and see if you can locate CUDA libraries. You might need to add them
to your LD_LIBRARY_PATH. If you suspect a bug, please take the information from python -m bitsandbytes
and open an issue at: https://github.com/TimDettmers/bitsandbytes/issues
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++ BUG REPORT INFORMATION ++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++ OTHER +++++++++++++++++++++++++++
Traceback (most recent call last):
File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/home/user/Documents/python-env/jupyter-default/jupyter-default/lib/python3.10/site-packages/bitsandbytes/main.py", line 4, in
main()
File "/home/user/Documents/python-env/jupyter-default/jupyter-default/lib/python3.10/site-packages/bitsandbytes/diagnostics/main.py", line 51, in main
cuda_specs = get_cuda_specs()
File "/home/user/Documents/python-env/jupyter-default/jupyter-default/lib/python3.10/site-packages/bitsandbytes/cuda_specs.py", line 39, in get_cuda_specs
cuda_version_string=(get_cuda_version_string()),
File "/home/user/Documents/python-env/jupyter-default/jupyter-default/lib/python3.10/site-packages/bitsandbytes/cuda_specs.py", line 29, in get_cuda_version_string
major, minor = get_cuda_version_tuple()
File "/home/user/Documents/python-env/jupyter-default/jupyter-default/lib/python3.10/site-packages/bitsandbytes/cuda_specs.py", line 24, in get_cuda_version_tuple
major, minor = map(int, torch.version.cuda.split("."))
AttributeError: 'NoneType' object has no attribute 'split'
Reproduction
It always replicates with this code:
from transformers import BitsAndBytesConfig, AutoModelForCausalLM, AutoTokenizer, GenerationConfig
MODEL_NAME = "mistralai/Mistral-7B-Instruct-v0.1"
quantization_config = BitsAndBytesConfig(
load_in_4bit=True,
bnb_4bit_compute_dtype=torch.float16,
bnb_4bit_quant_type="nf4",
bnb_4bit_use_double_quant=True,
)
tokenizer = AutoTokenizer.from_pretrained(MODEL_NAME, use_fast=True)
tokenizer.pad_token = tokenizer.eos_token
model = AutoModelForCausalLM.from_pretrained(
MODEL_NAME, torch_dtype=torch.float16,
trust_remote_code=True,
device_map="auto",
quantization_config=quantization_config
)
generation_config = GenerationConfig.from_pretrained(MODEL_NAME)
generation_config.max_new_tokens = 1024 # maximum number of new tokens that can be generated by the model
generation_config.temperature = 0.7 # randomness of the generated tex
generation_config.top_p = 0.95 # diversity of the generated text
generation_config.do_sample = True # sampling during the generation process
generation_config.repetition_penalty = 1.15 # the degree to which the model should avoid repeating tokens in the generated text
pipe = pipeline(
"text-generation",
model=model,
tokenizer=tokenizer,
return_full_text=True,
generation_config=generation_config,
)
Expected behavior
To be able to load the model and initialize pipeline.

This is most likely due to I am using an AMD GPU. Sorry for the unnecessary issue.


Tests don't run in subdirectories

The README says that tests should be able to run in subdirectories, but when I tried it I got "ReferenceError: describe is not defined". It doesn't look like any of the regex's (eg. '^tests/jasmine/server/integration/.+\.(js|coffee|litcoffee|coffee\.md)$') in any of the TestFramework files (eg. ServerIntegrationTestFramework.js) look for nesting. I'd like to be able to do tests/jasmine/server/integration/packages/package-name/testSpec.js.
Seems like the best approach is just to make the regexes look for more subdirectories.

Actually it looks like the regex does work and the files do get picked up, so now I have no idea why describe is not defined. It seems to work if I don't put it in a subdirectory.

I was missing Jasmine.onTest. I'm running into other issues now, but subdirectories don't seem to be the issue so I'm closing this.

Sorry for that. I will soon add a better error message for this error. It's already on my list.


Update nf-cryptxml-cryptxmlsign.md

Adding additional information regarding CryptXmlSign creating a UI window for certificate selection.

@WAftring : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


chore: add gov.light.so

Hi! What is your PR about?

[ ] Add or edit a skin
[x] Add a custom domain for your space
[ ] Add an alias to migrate your space

I've completed adding the custom domains here:

Working now


Beta versions should not be pushed to npm as latest

Bug report
Description / Observed Behavior
Currently beta versions are pushed as latest to npm:

This makes them show up in npm outdated:
Package           Current        Wanted        Latest  Location                  Depended by  Package Type     Homepage
swr                 1.1.1         1.1.1  1.1.2-beta.0  node_modules/swr          nasa-web     dependencies     https://swr.vercel.app

Expected Behavior
Only stable versions should be pushed as latest.

Thank you! The tags were re-added and it should be good now.


redirectToChild

Specify a redirect to an immediate child when specifying a focus path:
useFocusPath('profile', {
  redirectToChild: 0
});

This way, if something places focus directly on the profile, it will result in profile.0 being focused in that same update. This would also work for deeply nested children.
This prevents a situation where the focus path causes n renders as all of the children are focused, while also still allowing controllers of focus to be unaware of what the default focus of a component subtree should be.

This is unnecessary with the new implementation. Leaf nodes are always focused.


Update user guide to reflect add meeting entry format

Related issues

Closes #69, partially for #58
Description

Updated the user guide to reflect the current state of the add meeting entry command.
Briefly mentioned module code in the user guide as add meeting entry requires it.
Changed all instances of LINK using l/ as the prefix to u/ as the prefix.

Codecov Report

Merging #70 (b61132f) into master (e148456) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #70   +/-   ##
=========================================
  Coverage     65.61%   65.61%
  Complexity      485      485
=========================================
  Files            95       95
  Lines          1655     1655
  Branches        177      177
=========================================
  Hits           1086     1086
  Misses          504      504
  Partials         65       65

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e148456...b61132f. Read the comment docs.

Our code base uses URL as to indicate the link to the zoom meeting, should we use URL in the user guide instead of LINK? Cause our app is called LinkyTime. @AY2122S2-CS2103T-T13-3/developers

Our code base uses URL to indicate the link to the zoom meeting, should we use URL in the user guide instead of LINK?

I think URL is a clearer way of naming the meeting URL link. I can't remember how the exact font used looks like currently, but the lowercase "L" may look like a capital "i", hence I think prefixing it with "u" and using "URL" may also remove any ambiguity for the user.


views: decorators

Add support for adding decorators to views. Most importantly, we need to be able to add access restrictions.

Solved in a different way for now - see #15


Module compiled with Swift 3.0 cannot be imported in Swift 3.0.1

time to updata please

Just starting out with swift this week, and I am getting this error:

No such module 'Alamofire'

is it because of Swift 3.0.1?

@CompassCanJV no ,it is because you have no build it ,make sure you Installation the module in the right way ,and try shift+command +B

Same problem here. Any updates?

pod 'Alamofire', :git => 'https://github.com/Alamofire/Alamofire.git', :tag => '4.0.0'
This worked for me

I got it working with Carthage using $carthage update --platform iOS --no-use-binaries

I tried
$carthage update --platform iOS --no-use-binaries
but it was not good for me, I updated carthage and Alamofire, I still had this problem.

@CompassCanJV You shouldn't need to point to a specific tag, pod 'Alamofire' should work just fine.
In general, we use our GitHub project for bug reports and feature requests. In the future, you should open questions like this on Stack Overflow and tag alamofire.
Cheers. 🍻

From our Contribution Guidelines
Asking Questions
We don't use GitHub as a support forum. For any usage questions that are not specific to the project itself, please ask on Stack Overflow instead. By doing so, you'll be more likely to quickly solve your problem, and you'll allow anyone else with the same question to find the answer. This also allows maintainers to focus on improving the project for others.

I found what helped is that after updating is deleting your derived data (Preferences > Locations > Derived Data).

@nassarofficial That did the trick for me too. Thanks much!


Contacts

It will be much simpler.
First title and contact type will be removed.
There will be 3 contact types as default.These are;
Primary Contact (Email, phone) -editor
Secretary (email, phone)
Technical Contact
If journal manager wants to add a new contact, there will be just these fields;
Contact type* (text, string )
Name*,
email*,
phone,
instution,
address

There will be 3 contact types as default
contact type have all crud processes you can design easily how you want.


Cannot delete the initial value with normal delete button keyboard

I just use this package with v.2.0. I cannot delete the initial value with the standard method but when I long-press the delete button for around 2-3 sec. so, it can be deleted. but it was so strange. Can anybody help?
Device used to debug: Samsung S20+ with Android11

@pondkiller  Actually its issue in package you have to edit package for this. Add following  line in init method after that you can delete initial value using backspace
_updateTextInputState(replaceText: true);


Mod Usage

Is there any way I can display images I have on my computer, that have not been uploaded anywhere else?

I even made a DeviantArt account to make it work, and the file is a PNG, but the mod won't convert it into a map, for some reason.

Solution found.


feat: Portfolio to have a get_weights() function or something similar

Idea
I am interested in measuring the performance of a variety of rebalance strategies (threshold / interval). For the threshold rebalances you rebalance if weights deviate from some target weight. It would be nice to maybe at a field to the portfolio to have a target weight for each position and an actual weight for each position. perhapses something like this
pub struct Portfolio {
    // other fields
    pub actual_weight: HashMap<Positions, f32>,
    pub target_weight: HashMap<Positions, f32>
}

Let me know what you think! I am happy to work on this

Great idea, thank you. Go ahead :)
Probably need to impl Hash, Eq, and PartialEq for Position if you wanna use it for the keys.


Fixes ignored --file-download-options

This fixes #1275 by assigning camel cased options in parsed arguments in the parseArgs function.

@TheCleric please review this and let me know if there are any changes.

@abhi12299 thanks! Merged, will ship in the next release, which I'll release in a couple days/weeks.

Now there is a new problem. When opening a new window to save the downloaded file through window.open, the window will not be automatically closed after selecting the save path.

Now there is a new problem. When opening a new window to save the downloaded file through window.open, the window will not be automatically closed after selecting the save path.

Can you provide a minimal example?