[ENHANCEMENT] time series conformal prediction

As described in this paper :
https://arxiv.org/abs/1802.06300
Or the EnbPI method proposed by Xu & Xie (2021) :
http://proceedings.mlr.press/v139/xu21h.html
https://arxiv.org/pdf/2010.09107.pdf

Hi, I recommend taking a look at our ICML 2021 Oral Paper: Conformal Prediction Interval for Dynamic Time-series. It builds upon the ideas of the Jackknife+ algorithm (e.g. Jackknife+-after-bootstrap, my collaboration with Prof. Rina Barber) and is easy to implement/use.
Moreover, I have established a GitHub repository for this paper, and I look forward to discussing with you if you are interested in incorporating this in the module.

Hi Chen,
Thanks for sharing your paper and your github repo ! I just read it and found it really exciting. It's a really smart adaptation of the Jackknife+ to sequential data. As this method seems to model-agnostic, it could definitely be included in MAPIE, also because adapting MAPIE to time-series is key for us.
I have one little question regarding the bootstrap: does a B value of 20-30 as suggested in the paper assures you to have at least one "leave-one-out" model for every training point (in order to be able to compute $\hat{f}_i^{\phi}$, line 7 of algorithm 1) ?
My colleagues are currently on vacation but we'll get back to you by the end of August regarding your great method.

Hi Vianney,
Thanks for your message and I am very glad that you found my work possible to be included in MAPIE; this is really a great tool and I look forward to its growth over the coming years.
Regarding your question: Yes, having B = 20-30 is sufficient. More precisely, if we build B bootstrap models, then the LOO ensemble model for the i-th training datum aggregates a random B_i ~ Binomial(B, (1-1/T)^T) number of bootstrap models. The binomial distribution has an expected value roughly around B*e^{-1} and by the concentration of binomial distributions, it is unlikely that any B_i is zero.
Meanwhile, I am refining some parts of the method so that the intervals are shorter without losing coverage guarantee. Therefore, it will be great to collaborate near the end of August, by which I will likely have more refinements on my end as well.
获取 Outlook for iOShttps://aka.ms/o0ukef

发件人: Vianney Taquet @.>
发送时间: Monday, August 2, 2021 8:23:48 PM
收件人: scikit-learn-contrib/MAPIE @.>
抄送: hamrel-cxu @.>; Comment @.>
主题: Re: [scikit-learn-contrib/MAPIE] [ENHANCEMENT] time series conformal prediction (#74)
Hi Chen,
Thanks for sharing your paper and your github repo ! I just read it and found it really exciting. It's a really smart adaptation of the Jackknife+ to sequential data. As this method seems to model-agnostic, it could definitely be included in MAPIE, also because adapting MAPIE to time-series is key for us.
I have one little question regarding the bootstrap: does a B value of 20-30 as suggested in the paper assures you to have at least one "leave-one-out" model for every training point (in order to be able to compute $\hat{f}_i^{\phi}$, line 7 of algorithm 1) ?
My colleagues are currently on vacation but we'll get back to you by the end of August regarding your great method.
―
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fscikit-learn-contrib%2FMAPIE%2Fissues%2F74%23issuecomment-890982883&data=04|01||a1c379c41423407e245708d955b061ad|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637635038304038650|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=CFB3HptvOnIKNZleMvraZEt%2BBZYbsSZF0nPDN3tLgmA%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAI6PAUIC7K5MQXN53RJL5TLT22E5JANCNFSM5ANAKKTA&data=04|01||a1c379c41423407e245708d955b061ad|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637635038304048642|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=VjvUti955lK72IhCYj3MSDtGxBpID80cpFSU42EFHyw%3D&reserved=0.

Hi Chen,
Thanks for your reply and your explanation regarding the B parameter, that makes sense. I look forward to seeing your update on this method.

Hey there! Any update on this? I am using MAPIE for some time series prediction intervals of panel data and this seems ideal! If not I may give it a go at extending the package with an implementation of the above.
Cheers!

Hi Ethan, thanks for your message. We have been implementing the Jackknife+-after-Bootstrap, the method at the basis of the EnbPI proposed by Chen, and it should be merged into the main branch in the next coming days. We plan to start implementing the EnbPI method into MAPIE in the next coming weeks. We'll let you know when the implementation is ready, hopefully before the end of the year.

Amazing! Thanks a bunch and big thanks as well for putting such a great package together!

Folks, any news on EnbPI by chance? Would be great to play with it.
please also note link to Awesome Conformal Prediction - the most comprehensive resource list on the subject
https://github.com/valeman/awesome-conformal-prediction

https://github.com/valeman/awesome-conformal-prediction
Conformal Prediction is #1 uncertainty quantification method in 2021, has been implemented in several, libraries including MAPIE.


Make registers mutable

As suggested by @ThaumicMekanism, we should make it possible to change a register value in the register view. Probably as text that changes to a text field when clicked, maybe best adopted from other debug views. Loosely relates to #2

I added this feature for the int registers. Just double click the value in the variables/registers panel on the left of the debugger. Then you can enter your value as decimal or hexadecimal (maybe add binary support?).
I'm unsure however how to overwrite float registers, or better said in what format the float registers values are saved. Would it even be usable for a user to change the values of fregisters directly?

This now also works for float registers.
The current solution seems stable.


Why does the nested field have to be a string?

I noticed the following:
https://docs.rs/serde_with/1.9.4/serde_with/json/nested/index.html
#[derive(Deserialize, Serialize)]
struct A {
    #[serde(with = "serde_with::json::nested")]
    other_struct: B,
}
#[derive(Deserialize, Serialize)]
struct B {
    value: usize,
}

let v: A = serde_json::from_str(r#"{"other_struct":"{\"value\":5}"}"#).unwrap();  // This is a string not a truly nested object

The "other_struct" there is given as a string value which is itself a JSON object.
However, in practice, you'd normally receive the nested field as a JSON object not as a string.
In other words, you are deserialising this:
{"other_struct":"{\"value\":5}"}
But I want to deserialise this:
{"other_struct":{"value":5}}
Is it possible?

It seems like you are looking for RawValue from serde_json. This crate has nothing similar.

Not sure what you mean? I managed to achieve what I want by simply not having an attribute. 'serde' is able to deserialise nested JSON just fine

Sorry, the RawValue suggestion is not useful. I didn't read the code snippet too careful.
From time to time, I see that people want to use serde_with::json::nested when they want no attribute at all. I never had the chance to ask: Is there something in the documentation which makes you believe you need the attribute? serde does the right thing be default, so I'm not sure how people end up finding this crate and json::nested.

In my particular case, I tried first without the attribute and it didn't
work but it was for a different reason and because it was failing inside an
async function, it did not panic and print the error so I could see what
went wrong so I wrongly assumed it's because of nesting since that was the
more likely cause (turned out that it was a u8 field that was too small and
should be u64).
This is a beginner mistake because I'm still learning Rust. Altho I should
have known from experience with other platforms that if an error is thrown
inside a Task/Future, it doesn't always propagate back to the caller
(depending on the platform, I think).
On Thu, 28 Apr 2022, 08:07 Jonas Bushart, @.***> wrote:

Sorry, the RawValue suggestion is not useful. I didn't read the code
snippet too careful.
From time to time, I see that people want to use serde_with::json::nested
when they want no attribute at all. I never had the chance to ask: Is there
something in the documentation which makes you believe you need the
attribute? serde does the right thing be default, so I'm not sure how
people end up finding this crate and json::nested.
—
Reply to this email directly, view it on GitHub
https://github.com/jonasbb/serde_with/issues/441#issuecomment-1111826969,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFONGIQEZMTTQ2TYIB2DS73VHI2K3ANCNFSM5UPYIE2Q
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


small fixes

I fixed the TODO.
Also vite build did not work in dev, but it was easy to solve it by using path.resolve instead of path.relative, and it seems to work fine

Awesome template!

Awesome, thanks!


SCSB Korean records from Columbia have ascii u0027 or u0027 instead of apostrophe

example https://catalog.princeton.edu/catalog/SCSB-13610491/raw
I checked the same record in Columbia

The files I checked were last indexed 2022-04-05. The event from that day is https://bibdata.princeton.edu/dumps/1215.json. I looked for this scsb id 15154980 with no results. I also searched for scsb id  https://catalog.princeton.edu/catalog/SCSB-13610993/raw in the file with no results.


Prepare PR to the graph-node tooling repository to merge fuel support

To allow for subgraphs to be developed using Fuel networks, the AssemblyScript library (graph-ts) must add support for Fuel types and the CLI (graph-cli) must add the names of Graph networks.
Information and examples are included at the bottom of the “Add Chain” document:
https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md#user-content-what-else

https://github.com/graphprotocol/graph-node/pull/5340#issuecomment-2052125879


[PB-2153] feat: do not request the user's password in security endpoints

Ticket

https://inxt.atlassian.net/browse/PB-2153

Updates

Do not request the user's password to update their password or their TFA (Two Factor Authentication)

PR related

wip: https://github.com/internxt/drive-server-wip/pull/423
server: https://github.com/internxt/drive-server/pull/460
web: https://github.com/internxt/drive-web/pull/1341

Not necessary task


[Discussion]: Referencing existing resources that we have drawn influence from

Summary
Citing how we have formulated the spec from literature
Source
Convo with stakeholders
Detail
On a call with a stakeholder today, a good point was raised - if this is heading the way of a TRE standard (or even if it just remains TRE guidance), are we being clear with how it aligns with pre-existing standards TRE teams are getting (DSPT, ISO27001 etc.).
Either this goes the way of becoming a standard, in which case it will need buy-in from e.g. ICO, NHS etc, and these orgs will want to see how it builds of currently accepted standards
OR
It isn't a standard, but e.g. best practice or guidance, in which case it needs to clearly align with pre-existing standards to be useful for teams.
@machintim I know you did a big literature review of this stuff, do we want to make this explicit somewhere?
Intended Output

[ ] A reference on the spec of what currently existing resources we have built on
[ ] A more in-depth evaluation by the SATRE team (WP3?) on current standards, ensuring the spec aligns with them

Who can help

@machintim
@jemrobinson
@JimMadge
@manics

I don't think it makes any sense for this to be a standard at the level of ISO27001. It's a lot closer to DSPT in that it's a self-certification, but we're certainly not going to be doing any of:

maintaining an up-to-date database of certifications
evaluating/auditing TREs
providing a formal certification award

so I don't think it's a standard at all.
It's much closer to being best-practice/guidelines, but with a lot more actual recommendations about what to do than eg. Five Safes.
Our brief is to produce a "specification/reference architecture" which I interpret as being more like a blueprint/suggestion for others to follow if they choose.

I think it's showing how we have considered what is already available through e.g. DSPT, ISO27001, other accepted resources about effective IS management, to show that we are creating something aligned with, and not in competition with, them.

Is this suggested change to add something to the main page of https://satre-specification.readthedocs.io/en/latest/ ?

I think it's showing how we have considered what is already available through e.g. DSPT, ISO27001, other accepted resources about effective IS management, to show that we are creating something aligned with, and not in competition with, them.

This makes sense. If we're going to write this up as an academic publication this will be needed anyway, so there's no reason not to add it to the spec website as background information.

This is lifted directly from ISO in terms of requirements (inputs into how the capabilities are implemented) this should mean pretty good alignment at that very high level. Suggest we add sections in the spec to link to specific external standards and requirements. That list could be very long but if we start with open standards ISO27001, 9001 etc. DSP and others could be added later.

Following on from the meeting today, are there updates to log here? @machintim @manics were you going to reach out to ppl at your orgs to go through this for us?
I'm wondering if it would be worth compiling a list of other standards/certs we'd want to cross reference against. Off the top of my head:

CE+
ISO2700X
DSPT
DEA

What others are there?

I thought we agreed we'd talk with IG in our orgs to provide feedback on SATRE spec when it's ready, and to help with evaluating our TREs? This issue is just about how the other certifications fit in with SATRE, I don't think that's relevant- or did you mean you want validation that these aren't incompatible? If so then yes, that'll come automatically as part of the IG assessment of SATRE.

Feels risky to leave incompatibility checks for too long - I thought we were saying we'd do these checks, amend and release as a v. 0.3?

I don't think we can do compatibility checks before we have a stable version of SATRE to evaluate against. It's probably OK for us (SATRE team members) to re-do the evaluation for every minor version change, but if we're going to be asking external IG people to do it (or look at our self-evaluations) we can probably only do so once or twice before the end of the project.


#87 Unread Message Count on Sidebar

Added unread message count to the Messages sidebar menu item, #87

Great! Could you get rid of the console.log statements? Then I'll merge it ASAP

Completely forgot I had those in there, they have been removed.  Thanks for pointing that out.

:+1: Thanks!


Local first tasks are synced in the wrong task list after sign-in

Describe the bug
There is an issue with remote parent id link when syncing local only task list with remote.
To Reproduce
Steps to reproduce the behavior:

fresh install
create a task list A
create a task B within A
sign-in to an account with already some data (at least default task list "My tasks")
go to https://tasks.google.com
Task list A is visible at the end but task B is displayed within the default list "My tasks"

Expected behavior
Task list A should be displayed at the end with task B within it

Fixed by PR #76


Issue on mac

When I run with java -jar MercuryTrade.jar
WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.gson.internal.reflect.UnsafeReflectionAccessor (file:MercuryTrade.jar) to field java.awt.Color.value
WARNING: Please consider reporting this to the maintainers of com.google.gson.internal.reflect.UnsafeReflectionAccessor
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
It runs, I can select where the logs are, it does see the messages because it plays the notification sound but it does not create the notification window and pc freezes for few minutes.
Tried several times, now while I was writing this I got a new error and the main windows does not appear anymore
13:47:41.103 [main] ERROR ErrorHandler - java.lang.NoClassDefFoundError: com/sun/awt/AWTUtilities
at com.mercury.platform.ui.adr.components.AbstractAdrFrame.(AbstractAdrFrame.java:31)
at com.mercury.platform.ui.adr.components.AbstractAdrComponentFrame.(AbstractAdrComponentFrame.java:23)
at com.mercury.platform.ui.adr.components.AdrTrackerGroupFrame.(AdrTrackerGroupFrame.java:18)
at com.mercury.platform.ui.adr.components.factory.frame.TrackerGroupFrameProvider.getFrame(TrackerGroupFrameProvider.java:24)
at com.mercury.platform.ui.adr.AdrManager.lambda$initComponents$11(AdrManager.java:297)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at com.mercury.platform.ui.adr.AdrManager.initComponents(AdrManager.java:283)
at com.mercury.platform.ui.adr.AdrManager.load(AdrManager.java:63)
at com.mercury.platform.ui.manager.FramesManager.start(FramesManager.java:147)
at com.mercury.platform.AppMain.main(AppMain.java:65)
Caused by: java.lang.ClassNotFoundException: com.sun.awt.AWTUtilities
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:606)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:168)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
... 10 more
This is the version of java I have
openjdk version "15.0.1" 2020-10-20
OpenJDK Runtime Environment AdoptOpenJDK (build 15.0.1+9)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 15.0.1+9, mixed mode, sharing)

Can you try running it with oracle java installed from here? https://java.com/download/

Can you try running it with oracle java installed from here? https://java.com/download/

Same thing, withouth the errors in terminal

Same thing, withouth the errors in terminal

You can try the newest version: https://github.com/Morph21/MercuryTrade-Community-Fork/releases/tag/<IP_ADDRESS>
And im not happy to say that but linux/macOS version won't be continued besides some critical bug fixes. You can read more about it here: https://github.com/Morph21/MercuryTrade-Community-Fork/wiki/Linux-macOS-not-working-manifest

You can try the newest version: https://github.com/Morph21/MercuryTrade-Community-Fork/releases/tag/<IP_ADDRESS>
And im not happy to say that but linux/macOS version won't be continued besides some critical bug fixes. You can read more about it here: https://github.com/Morph21/MercuryTrade-Community-Fork/wiki/Linux-macOS-not-working-manifest


Other configs of dotfiles

I want to share not only Neovim configs but also zsh ones, dotfiles setup scripts, or Brewfile.
That's because the project name is dotfyle.

Thanks for making the issue!
I do plan to add this, as you could tell by the name. 👍
But likely not for a while. I want to focus on making the app really good for Neovim before working on generalizing it for more configs I think.

Wow! Thank you for your reply.
I’m looking forward to it.


Intern types for instrumentation analysis

@bot-gradle test APT

I've triggered the following builds for you. Click here to see all build failures.

All Performance Tests (Trigger)


Feature/source filetypes option

Codecov Report

Merging #15 into master will decrease coverage by 0.32%.
The diff coverage is 13.33%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
- Coverage   51.91%   51.59%   -0.33%
==========================================
  Files          26       26
  Lines         495      502       +7
  Branches       38       40       +2
==========================================
+ Hits          257      259       +2
- Misses        236      241       +5
  Partials        2        2

Impacted Files
Coverage Δ

rplugin/python3/curstr/info.py
54.28% <ø> (+4.93%)
:arrow_up:

rplugin/python3/curstr/action/facade.py
46.15% <0%> (-3.85%)
:arrow_down:

rplugin/python3/curstr/action/source/base.py
46.15% <15.38%> (-13.11%)
:arrow_down:

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 f2736c6...cf2a1ce. Read the comment docs.


Nested Where clauses don't handle mixed conditions

When trying to write nested conditions in the Where clauses, it seems that the results are off.
Syntax which I think should work (from reading the documentation) is
// (A && B) || (C && D)
const users = store.getters['entities/users/query']()
      .where((_user, query) => {
        query.where('age', 20).where('active', true);
      })
      .orWhere((_user, query) => {
        query.where('age', 24).where('active', false);
      })
      .get()

I set up 2 different test cases, one for a (A || B) && (C || D) condition and one for (A && B) || (C && D) condition on a fork there: https://github.com/tvillaren/vuex-orm/commit/dfaae4c5ba6c535d05c258c45ede53c0223b1945
I did a bit of digging & debugging: it looks like the where clauses are pushed to the same where array without respect for the "priority" / nested-ness.

Pushed a fix on a branch https://github.com/vuex-orm/vuex-orm/compare/master...tvillaren:bugfix-nested-where
There were 2 issues:

the nested queries were added to the root query where array (and not the newQuery one)
grouping AND & OR predicates at the same level on one query led to an issue when trying to check emptyness of results in case of closure

Will check coverage and perf tomorrow before opening a PR

Thank you so much @tvillaren !


No support for  changeDetection: ChangeDetectionStrategy.OnPush,

I'm submitting a ...
[ X ] bug report
[ X ] feature request
[ ] question about the decisions made in the repository

Do you want to request a feature or report a bug?
This is both a feature request and a bug report.

What is the current behavior?
In order to avoid pointless view refreshes, I use changeDetection: ChangeDetectionStrategy.OnPush for most of my components. However, when you have a "dnd-sortable-container" with OnPush detection, the view isn't updated as changing the order of items within an array isn't an event.

EDIT:
Upon further investigation it would appear that markForCheck is being called, but not in the main _onDragEnterCallback method, making it so that the changeDetector isn't being notified.
Without OnPush, the view and ordering of items is updated just fine.

** Reproduction:

Simply import     ChangeDetectionStrategy from @angular/core and add "changeDetection: ChangeDetectionStrategy.OnPush" to a component declaration that has a sortable container within.

What is the expected behavior?

It would be nice that what changes the array contents would call ChangeDetectorRef.markForCheck() whenever the contents are change.

What is the motivation / use case for changing the behavior?
Right now I have to create an interval that calls ChangeDetectorRef.markForCheck() whenever the drag starts and kill it when it ends

Please tell us about your environment:

Angular version: 4.2.X
Browser: all

@chpoit I do have the same problem. Due to performance reasons I switched my change dection strategy to OnPush for my components. Now, as you mentioned, the sortable behavior seems to be broken. Can you post an example (snippet/plunkr) how you solved the issue on your end?

@mawo87 I didn't. I created a quick pull request (#168)  that adds a call to markforcheck, but only for sortables a while ago, but it hasn't been merged yet. Ideally I should go and completely convert ng2-dnd to OnPush, but I don't have the time while I'm at work to do so.
If I don't want a clunky movement I create an interval on a 100-300ms using the onDragStart event and dismiss the interval with the onDragEnd event. This feels gross, but it works and is simpler than creating a forked npm package.

Thanks for the note - sounds like a solid workaround.


Doc Feedback:

Location : https://is.docs.wso2.com/en/latest/setup/adding-logs-for-tokens/
<IS_HOME>/repository/conf/security/identity_log_tokens.properties
Isn't there a way to configure this in deployment.toml

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


example templatesConfig using decorators

from #136
dunno if that's better or worse. it works (tm)

@Jerskouille here it is

So basically we are preparing a <Template> prop for the Component, with some default configuration

LGTM :)

closing and handling it in #136


some changes

https://github.com/CommandString/php-bot/pull/1/commits/387caa2fe2eec06d1a8ddf2d7cff52133c4212b7, https://github.com/CommandString/php-bot/pull/1/commits/21087cf2e1e9fb47636f1b2c23c0a42bc76eee5b, https://github.com/CommandString/php-bot/pull/1/commits/61898d4fe83926c318c8545e36d30f89e65874f2, and https://github.com/CommandString/php-bot/pull/1/commits/62d6dca04e2bbc61a4bb8da05a56eabb41815633 should technically be applied to DiscordPHP Bot Template.
There also seems to be some indenting issues in many of these commits. Will probably open a counter PR in a bit.


implement loop kustomize

added kustomize_deploy role
Converge usage of the architecture repository
Implement flexible step loop for EDPM deployment

As a pull request owner and reviewers, I checked that:

[ ] Appropriate testing is done and actually running
[ ] Appropriate documentation exists and/or is up-to-date:

[ ] README in the role
[ ] Content of the docs/source is reflecting the changes

recheck


reactjs example

I search an example with vivus and react (jxs or not)
do you know some sites ?
Thanks
ami44

Hallo,
I'm sorry, I don't know any :-$ Not really a massive user of React and I haven't check what the community has built from Vivus with React.
What kind of usage you expect? Maybe I can help

i would luke add svg animation in spectacle sides https://github.com/FormidableLabs/spectacle

Although this is an old post, and closed a very long time ago... I thought I'd share my implementation of a complete React solution...
import React from 'react';
import PropTypes from 'prop-types';
import Vivus from 'vivus';

import FLLogo from 'images/FLLogoAnimate.svg';
import Wrapper from './Wrapper';

class FLLoadingIndicator extends React.Component {
  constructor(props) {
    super(props);

    this.state = {
      vivus: null,
    };
  }

  componentDidMount() {
    this.setState({
      vivus: new Vivus('flsvg', { duration: 100, file: FLLogo }, () =>
        this.resetAnimation(),
      ),
    });
  }

  startAnimation() {
    this.state.vivus.play(() => {
      this.resetAnimation();
    });
  }

  resetAnimation() {
    this.state.vivus.reset();
    this.startAnimation();
  }

  render() {
    return (
      <Wrapper>
        <object aria-label="" id="flsvg" loop={this.props.loop} />
      </Wrapper>
    );
  }
}

FLLoadingIndicator.propTypes = {
  loop: PropTypes.bool,
};

export default FLLoadingIndicator;


Test Issue created at Mon, 29 Nov 2021 02:21:02 GMT

Test issue body  Mon, 29 Nov 2021 02:21:02 GMT

Comment on issue at Mon, 29 Nov 2021 02:21:04 GMT


[not an issue] 2 delivery carriers but 3 sensors in HA ?

Hi,
Thanks for your work ! I've submitted a separate PR to add a french translation just in case it could be useful for some others :).
Anyway besides that, i have a question, i see 3 sensors in HA despite there are 2 carriers so far (Postnord and Citymail).
Since the integration is still very recent and documentation is clear but short, i'm wondering the purpose of the 3rd sensor.

Is it correct that it simply aggregates both carriers and indicates the next scheduled delivery, independantly of which carrier it is ?

Cheers,
Matthieu

Hi! Will merge it into dev and it will be released very soon! Thanks for the translation!
Regarding the third sensor; it is just as you say a combined sensor with the next delivery regardless of operator (it is actually prepared to handle even more operators if needed)

All clear, thanks !


Export BytesMut::from_vec(vec)

Hi, can we expose BytesMut::from_vec? Which can help avoid copying when building a BytesMut from Vec<u8>

The comments on from_vec call out the fact that the allocation strategy may change at some point, making this a more expensive operation because it would then involve a copy. I'm not sure how likely that is and I don't have any opinions about exposing it, but I wanted to call it out here since this would be a departure from that stance.
https://github.com/tokio-rs/bytes/blob/327615e5d4ba27e9647734d83ef9ad88d7dd8a38/src/bytes_mut.rs#L824-L829

Yes, good point, thanks.

While it's true that the allocation behind Bytes could change in the future and suddenly make the conversion slower, as a regular user who just needs to work with libraries using Bytes, I don't think it's a good decision to not have a From<Vec<u8>> implementation.
Some libraries use Bytes, others use Vec<u8>, and right now the easiest way I found to convert from a Vec<u8> into Bytes is to deref it into &[u8], and then use From<&[u8]>, which calls to_vec() internally and makes a clone/copy anyway. Given that there is no real other choice (at least to my knowledge, feel free to tell me if there's a better way), I suspect this is what most users also end up doing.
I don't see how that's any better than letting us have a From<Vec<u8>> which would be faster at least today, even in the future where this operation ends up slow. Sometimes we just have no choice to convert back and forth between the types to use foreign libraries. If the sudden performance hit really a concern, then perhaps let from_vec public instead of making a From, and document its behavior publicly (and not privately).

+1 for From<Vec<u8>> and maybe From<String>.
But I'm curious why From<Vec<u8>> is explicitly called out but the documentation for From<Bytes> says it avoids a copy if the Bytes is unique.
https://github.com/tokio-rs/bytes/blob/2d996a2b419ad1a29d65ba6c7e82cfe9c733595c/src/bytes.rs#L1030-L1050
And, there is a From<Vec<u8>> (and From<String>) on the Bytes. The From<Vec<u8>> for Bytes impl makes no such promise, but the API exists and performs a zero-copy instantiation of Bytes thus the contract has been set.
https://github.com/tokio-rs/bytes/blob/2d996a2b419ad1a29d65ba6c7e82cfe9c733595c/src/bytes.rs#L964-L997
So, transitively, From<Vec<u8>> for BytesMut should be simply BytesMut::from(Bytes::from(vec)) and ultimately zero-copy.


(#12404) Reduce redundant code in lib/puppet/application

Reduce redundant code by defining Puppet::Application.logdest_option,
which can then be called from applications that need a log destination
instead of copying the 9 lines of code specific to creating a log
destination.
Reduce redundant code by defining Puppet::Application.setup_logs
to ease (and standardize) the log setup across the applications.
Reduce redundant code by moving setup_host into Puppet::Application.
Encapsulate logic for exiting if Puppet.settings.print_config?
Encapsulate logic for sorting type providers in Puppet::Application::Describe.
Modify tests to use standard option :setdest.
Modify tests to mock options :setdest, :debug, and :verbose to
handle standardized checked against each option in consolidated
setup_logs method.

@jeffweiss - I am looking at this, but it is a bigger change than I can immediately merge.  I like the idea; most complexity is around "should we retain this choice", rather than anything in the code, so takes bigger thinking to answer.


Bug in day selection by click (only in master)

After merge PR https://github.com/flatpickr/flatpickr/pull/2127 (related with issue https://github.com/flatpickr/flatpickr/issues/2126) is bug in day selection by mouse click if is enabled allowInput: true. A second click is required now.
Example with master flatpickr:
https://jsfiddle.net/6uL3sh08/
Steps to reproduce:

click to input for open flatpickr
click to some day number - day is not selected
Day is selected after second click.

 New example: https://jsfiddle.net/kp8czbfo/


Adds enums for cli package syncing of cookies, data flows and attributes

Related Issues

links https://github.com/transcend-io/cli/pull/118

Adds the following enums in order to support syncing attributes, cookies and data flows between transcend instances. These enum are used in the codec for validation.

@anotherminh im going to put up a PR to import these in the monorepo

Oh, awesome!


OLS-974: RHOAI VLLM as provider for OLS

Description
RHOAI VLLM as provider for OLS
Type of change

[ ] Refactor
[x] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[x] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)
[x] Unit tests

Related Tickets & Documents

Related Issue #OLS-974

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] PR has passed all pre-merge test jobs.
[x] If it is a core feature, I have added thorough tests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.74%. Comparing base (617d32f) to head (c371b92).
Report is 18 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1484      +/-   ##
==========================================
+ Coverage   94.66%   94.74%   +0.07%
==========================================
  Files          58       59       +1
  Lines        2531     2569      +38
==========================================
+ Hits         2396     2434      +38
  Misses        135      135

Files
Coverage Δ

ols/src/llms/providers/provider.py
100.00% <100.00%> (ø)

ols/src/llms/providers/rhoai_vllm.py
100.00% <100.00%> (ø)

ols/src/prompts/prompt_generator.py
100.00% <ø> (ø)

/lgtm

/approve

/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"


No midi support on Ubuntu 18.04

Description
Ubuntu 18.04 does not have an up to date version of libfluidsynth, only supporting up to version 1.1.9-1 as of this time. The game does not seem to support this version of libfluidsynth, and will show the regular error of fluidsynth not being installed even though it is.
Maybe this could be fixed by bundling a newer version of libfluidsynth with the client.
Screenshots

Additional context
$ dpkg -l | grep libfluidsy
ii  libfluidsynth-dev:amd64                       1.1.9-1                                           amd64        Real-time MIDI software synthesizer (development files)
ii  libfluidsynth1:amd64                          1.1.9-1                                           amd64        Real-time MIDI software synthesizer (runtime library)
$ apt search libfluidsynth
Sorting... Done
Full Text Search... Done
libfluidsynth-dev/bionic,now 1.1.9-1 amd64 [installed]
  Real-time MIDI software synthesizer (development files)

libfluidsynth1/bionic,now 1.1.9-1 amd64 [installed,automatic]
  Real-time MIDI software synthesizer (runtime library)

$ cat /etc/issue
Ubuntu 18.04.6 LTS \n \l

all I can really say in this regard is "oof"
there's a build script to solve this I PR'd to the native libraries thing... um...
@PJB3005 pls

If it is still relevant for anyone: there is a workaround (haven't tested on Ubuntu, but it worked on Fedora).
The game tries to load fluidsynth library from the /path/to/space-station-14/bin/loader/libfluidsynth.so.2. So all you need to do is just to put the library there. In my case, I just symlinked it:
cd /path/to/space-station-14/bin/loader
ln -s /usr/lib64/libfluidsynth.so libfluidsynth.so.2

By the way, Space Station 14 looks for libfluidsynth.so.2, but at least on Fedora (though it is 37 which is still in beta) it is already libfluidsynth.so.3

That last note is a bit of a complicated mess. Dropping support for libfluidsynth.so.2 will break things for some users and not having support for libfluidsynth.so.3 will be messy for others. Blame Fluidsynth - they appear to have decided to make a major ABI change because they couldn't just keep around the 32-bit soundfont access API for some unknown reason (source: https://github.com/FluidSynth/fluidsynth/blob/master/doc/recent_changes.txt What's new in 2.2.0?). I'm not sure if that will cause a problem or not, but it's worth mentioning why that happened.

Also for the record, the current plan is to make our nfluidsynth fork target libfluidsynth.so.3 and ship it ourselves, although I can't give an estimate of when this will happen sadly.

I see... Good to know, thanks. For now the workaround seems to work anyways. Though it is funny to see it working in that case

Also bit of an issue on NixOS, where  fluidsynth.so.2 was removed a year ago by https://github.com/NixOS/nixpkgs/pull/141918.
For NixOS it's easies to run SS14 using Steam, so to add Fluidsynth to it's environment I added an override:
  nixpkgs.config.packageOverrides = pkgs: {
    steam = pkgs.steam.override {
      extraPkgs = pkgs: [ pkgs.fluidsynth ];
    };
  };

And linked the file:
ln -s /lib64/libfluidsynth.so ~/.local/share/Steam/steamapps/common/Space\ Station\ 14\ Playtest/bin/loader/libfluidsynth.so.2


Feature/formatting tests

Can we please merge this? I know, the tests do not pass, but it would majorly simplify the process if we did the changes to make tests green directly on the develop to prevent merge conflicts.


Docker image old version of code

Am I right that in the docker container old version of the code?
Try to pass images to train the model, but the result is different. Model does not use images to train.

And of course different results between the google collab model and the docker model.
COLLAB

DOCKER

Same parameters.

Which docker are you using? The one from replicate, or the one from our own docker repo?

The second one. Use the command docker-compose up in the StyleGan directory for creating an image.

Just an update that I haven't forgotten you, but it's a rather busy week due to conference deadlines. I'll probably be freer around the weekend and I'll try to look into things.

Thank you. I am waiting. If I can help you, I am at your disposal.

Okay, so the docker does make use of older code. It should still have support for image directory targeting, but the notebook inside the docker doesn't support this option.
The quickest solution to get things up-to-date is to just git pull/clone inside the docker.
It has the correct environment set up (and you've been able to run the code inside it), so the new code should work fine as well.
A second alternative is to use the docker from replicate.com which is more up-to-date. You can grab it with:
docker pull r8.im/rinongal/stylegan-nada@sha256:5295deb56da56f890f123e1bb0ede34d63896adf42d6c4856defdca2b187552a
This version is slightly bigger since it also has some pre-trained models inside for inference. It doesn't have all the initial models from other domains though.
Finally, I can update the docker, but that's going to take me a bit of time since I've got a few other things on my table atm.
We can start by seeing if option 1 works for you. If it doesn't then we can try the other two.

Finally, I can update the docker, but that's going to take me a bit of time since I've got a few other things on my table atm.

Thank you for your answer. Yeah of cause. I will try the first two options and let you know.

Tried first case, install a new version of the stylegan_naga repository
I have been stuck on saving the model.
torch.save(model, path)

Traceback (most recent call last):
  File "train.py", line 55, in <module>
    train()
  File "train.py", line 36, in train
    model.save(model_name)
  File "/workspace/style-transfer/model_gan.py", line 45, in save
    torch.save(model_wrapper, path)
  File "/opt/conda/lib/python3.7/site-packages/torch/serialization.py", line 379, in save
    _save(obj, opened_zipfile, pickle_module, pickle_protocol)
  File "/opt/conda/lib/python3.7/site-packages/torch/serialization.py", line 484, in _save
    pickler.dump(obj)
AttributeError: Can't pickle local object '_transform.<locals>.<lambda>'

type(model)
# <class 'ZSSGAN.model.ZSSGAN.ZSSGAN'>

Try to figure out the reason for the problem but unsuccessfully.
Also in the docker instant from replica, I saw that you saved the model in a different way than I do.
The next step try to use docker instant.

Also, one more example of training the model with parameters:

source class "Photo"
target class "Monet portrait"
iteration 200

That was in your paper:

In docker container:

But I had very good results with:

sketch

Ukiyo

White walker

Werewolf

An immediate guess is that there's some difference between the parameters you're using and the ones in the Colab.
Your ukiyo-e / white walker / werewolf results also look nothing like I'd expect. Mostly the color scheme.
Can you check what the training outputs look like? Are they similar to your own editing results, or closer to mine?
If it's the later, then you're probably not loading the model correctly.
About saving - just see what I'm doing in my code. You want to save the generator itself. You don't need the rest of the ZSSGAN module.

I tried running the prompts again the colab and I'm not encountering your issue. In some of the other issues / in our paper, we list the parameters used for specific prompts. You can try reproducing the results with those parameters and this might give us a better idea of whether parameter differences are at fault or not.

Thanks so much. I refreshed the Style-Gan repository and saved the model in your way (saved only generator) and everything works fine. Also start to investigate your paper to understand which parameters are related to the results.


sail should report its usage for -v option.

MacOS: 11.2.3
Bash Version:3.2
Sail Version: 1.0.1
Laravel Version: 8.12
PHP Version: 8.0.2
Description:
I would like to see more options for the sail command.
Steps To Reproduce:
・Reproduction Procedure
sail -v
・Expected results
There is a description of the sail command
・Actual result
The description of the docker compose command is printed.
docker-compose version 1.29.0, build 07737305

Feel free to PR something if you can 👍


UOW for command processing

When processing a command, its possible that the domain might raise several events.  We should encapsulate all events raised from a single command in an event store transaction

fixed


Bump typescript-eslint monorepo to 5.47.1 to deal with typescript-eslint warning

I found that @typescript-eslint/typescript-estree displays a warning when running eslint like the following.
$ npm run lint

><EMAIL_ADDRESS>lint
> eslint src --ext ts

=============

WARNING: You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree.

You may find that it works just fine, or you may not.

SUPPORTED TYPESCRIPT VERSIONS: >=3.3.1 <4.5.0

YOUR TYPESCRIPT VERSION: 4.6.3

Please only submit bug reports when using the officially supported version.

=============

This is because @typescript-eslint/typescript-estree used in the repository is old.  @typescript-eslint/typescript-estree is dependancy of @typescript-eslint/eslint-plugin.
So in this PullRequest, I update @typescript-eslint/* to deal with the above warnings.

I confirmed that the result of npm run lint is not changed.
$ npm run lint

><EMAIL_ADDRESS>lint
> eslint src --ext ts

See Also:

https://github.com/typescript-eslint/typescript-eslint/issues/4614
https://github.com/facebook/jest/pull/12557

a similar PullRequest to deal with the same warning

Thank you! We need some time to review because it's hard to check package-lock.json. Sorry for waiting for you.

@shibayu36
Sorry, could you revert the change in package-lock.json? It's hard to review package-lock.json because of security.

OK, do you mean I should change only package.json and after that you are going to update package-lock.json by yourself?

@ono-max
I fixed to only update package.json.  Please feel free if you have anything to want me to do 😄

That's exactly what I said! Thank you for your patience!

Thanks to merge!


NBC Multiprocessing Enhancements

Currently multiprocessing is rudimentary.  Need to optimize.

Closing as I will not be adding anything more to multiprocessing at this time.


[BUG] Custom version is not downloaded - latest is downloaded instead

Describe the bug
I'm using auto typings in combination with @monaco-editor/react, and my AutoTypings create config is following:
await AutoTypings.create(editor, { sourceCache: new LocalStorageCache(), monaco, versions: { apify: '2.3.2' }, preloadPackages: true });

So I would expect<EMAIL_ADDRESS>is downloaded, but instead, latest<EMAIL_ADDRESS>is downloaded (and cached).
To Reproduce
Set different major version for any package, try to fetch its types
Expected behavior
Different version types is fetched
Environment (please complete the following information):
React 17.0.2 /w CRA

OS: macOS
Browser Version: Chromium 103
monaco-editor-auto-typings Version: 0.4.2

Thank you for your contribution!


Ngnix: log rotate  by default and in a volumes

It would be great to have log roate enbale by default in the ngnix conf and to store the log outside the containers.

Could be a good idea to allow this as an option, if you have an idea for this, feel free to submit PR ;)


Refactor fastlane CommanderGenerator usage

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Description

Remove --env option from fastlane global_options.
Now fastlane help shows correct options.
  fastlane

  CLI for 'fastlane' - The easiest way to automate beta deployments and releases for your iOS and
Android apps

        Run using `fastlane [platform] [lane_name]`
        To pass values to the lanes use `fastlane [platform] [lane_name] key:value key2:value2`

  Commands: (* default)
    action                 Shows more information for a specific command
    actions                Lists all available fastlane actions
    add_plugin             Add a new plugin to your fastlane setup
    docs                   Generate a markdown based documentation based on the Fastfile
    enable_auto_complete   Enable tab auto completion
    env                    Print your fastlane environment, use this when you submit an issue on
GitHub
    help                   Display global or [command] help documentation
    init                   Helps you with your initial fastlane setup
    install_plugins        Install all plugins for this project
    lanes                  Lists all available lanes and shows their description
    list                   Lists all available lanes without description
    new_action             Create a new custom action for fastlane.
    new_plugin             Create a new plugin that can be used with fastlane
    run                    Run a fastlane one-off action without a full lane
    search_plugins         Search for plugins, search query is optional
    trigger              * Run a specific lane. Pass the lane name and optionally the platform first.
    update_fastlane        Update fastlane to the latest release
    update_plugins         Update all plugin dependencies

  Global Options:
    --verbose
    --capture_output     Captures the output of the current run, and generates a markdown issue
template
    --troubleshoot       Enables extended verbose mode. Use with caution, as this even includes ALL
sensitive data. Cannot be used on CI.
    -h, --help           Display help documentation
    -v, --version        Display version information

  Options for trigger:
    --env STRING[,STRING2] Add environment(s) to use with `dotenv`

  Author:
    Felix Krause<EMAIL_ADDRESS>
  Website:
    https://fastlane.tools

  GitHub:
    https://github.com/fastlane/fastlane

Motivation and Context

Because --env option is not actually global_option, it's option for 'fastlane trigger'.

@mfurtak Thanks 👍

Thanks for bringing help back 👍

Yeah 🚀


Adding new Q# language repo to the contribution guide.

Fixes #1077

Docs Build status updates of commit 8d312db:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/contributing/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit ecf2960:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/contributing/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Templating variables miss dependencies

Continuing https://github.com/grafana/grafana/issues/13291
It seems like the variable is not populated when query is sent to Clickhouse, resulting in an error:
My templating variable:

Turns into this query:
SELECT arrayJoin(range()) AS cpus FORMAT JSON

Dashboard JSON if you want to reproduce:

https://gist.github.com/bobrik/4d011d4c28f4729207fc2b933a02ede5

Hi @bobrik
My config is following:

plugin Version 1.7.0
Grafana v5.2.5 (commit: 6f9b734)
dashboard (I've changed queries to match my metrics) - https://gist.github.com/hagen1778/f448f5202d76c82ab9953b2382417a5a

In my case I see the same behavior for both: clickhouse and prometheus variables. Both requests were sent without variable value, got errors and automatically repeated successfully:

I reproduced the same behavior at Grafana playground:

The gist for Grafana playground - https://gist.github.com/hagen1778/0bd00b0555cf8f4090a9b6195148f6b8
Unfortunately, it's "floating" bug and can't be reproduced with 100% probability.
Thank you!

Can you update the Grafana issue and ask them to reopen if this can be reproduced in playground?

Yes, I will

Looks like this was fixed with https://github.com/grafana/grafana/issues/11890.


Windows 11 Context Menu support

This I would like to get an integration for open in VS Code in the Windows 11 Context Menu (IExplorerCommand) because:

it's better visually
it's more clear in terms of design
it's new
it's easier to access

/duplicate of #127365

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


About the script that used in VOC2012 dataset

I'm trying to reproduce your marvelous work as my baseline, but it really confuses me a lot that the uploaded script seems just like a draft.
Could your plz offer me the script that you used in the experiments on VOC 2012 dataset?
Thank you so much.

Do you have any problem reproducing our results?


reana.yaml: load parameters from an external file

Parameters of a workflow are specified in the inputs.parameters section of reana.yaml, like this:
inputs:
  parameters:
    myparam1: myvalue1
    myparam2: myvalue2

However, in case of a CWL or Snakemake workflow, it is also possible to load parameters from an external file by providing a special input parameter (source code)
inputs:
  parameters:
    input: my-parameters.yaml

We should introduce a new property in reana.yaml to support loading parameters from a file also for serial or Yadage workflows. One possible name for this property can be parameter_file (or parameterfile):
inputs:
  parameter_file: my-parameters.yaml

If we want to support multiple parameter files at the same time, then we should use parameter_files (or parameterfiles) instead:
inputs:
  parameter_files:
    - my-parameters-first-stage.yaml
    - my-parameters-second-stage.yaml

In this second case, we also need to decide how to handle parameters defined in different files but having the same name.

Making this "parameter input file" clearer and better structured is definitely a nice and needed improvement.
In the rest of reana.yaml it looks to me like we often go for snakecase (see kubernetes_memory_limit, compute_backends, ...), so I would prefer parameter_files.
I also think that being able to support multiple parameter files at the same time is better; in this case, I think that parameters that are defined later should simply override the ones that were defined previously, and issue a warning about this. This is a very commonly followed approach when dealing with duplicate keys (see Oracle DB for example), and users seem to complain about the absence of warnings rather than about being allowed to put duplicate keys (see helm lint, prometheus). Note that this is something we have to address anyway, as right now the current code does not complain for duplicated keys in the same parameter file, but just overrides the first one with the value of the second (because this is how yaml.load behaves).


Add Classname to Default enum value. Fix #25

Default enums only had the value and not the class name.
This was causing compile error.
Now it will be ClassName.EnumName

Can you please merge these changes ?


sos status -s VALUE does not yield error for unacceptable status

If just ignores and return nothing. We should limit the selection to running, pending etc.

fixed.

fixed.


Add ws281x driver parameter for PWM channel

1. Tell us something about your changes.
The RPi 2 and 3 have two PWM channels and 3 PWM pins available to the
gpio header.  BCM18 and BCM12 run on PWM channel 0.  BCM13 runs on PWM
channel 1.  This change allows BCM13 to be used by allowing the PWM
channel to be specified.
2. If this changes affect the .conf file. Please provide the changed section
Adds optional "pwmchannel" parameter to the "device" section.  If unspecified, has the default of 0 which was used before this change.  So, all old .conf files should work the same as they did before.
3. Reference a issue (optional)

Damn ! You beat me.
I've added the invert option today and was about to create a PR.
I'll redo it after this is merged

If someone adds a "dtoverlay=pwm" or the default one to config.txt, your settings here will be overwritten and it won´t work?

Ah one more thing, @penfold42  @markwal
Wiki :)

The ws281x driver doesn't make use of the pwm kernel module, so it will conflict if used. That was true before this pull request. Also with the ws2812b driver.
I didn't do the invert option because Hyperion already had color order.

The invert option doesn't change the RGB order, it changes the logic of the output.
It changes the logic sense of the output wire on the gpio.
Merge this PR and I'll redo my invert PR.

@penfold42 Ah, cool, I didn't realize.


Backport #209

Verified that it is pulling the correct branches
Working with ref: refs/heads/releases/9.0
Working with a branch: releases/9.0
Triggered by change in APPS


CI: move Linux testing to Ubuntu 20.04

When Travis images are available.

As of 915a4c0f4624bd86dc4c4f41d72b2a995eb9adf0 this is done.


Do you plan on implementing error handling?

Hi just wondering if you plan on implementing the error handling part of the JSON API spec? Where you would render all exceptions to the JSON errors dictionary and a suitable http code.
Apologies if you already do I just didn't see it mentioned in the Readme or when I briefly looked over the code.

@malhal Actually it's implemented... I got to admit it requires better documentation.


Can Flexget add or subtract a number from a series ID?

I want to download TV series through RSS. The TV series titles provided by RSS are similar to ‘XXXX - 25’. I can use the manipulate plugin to format it as ‘XXXX S02E25’. However, 25 is actually the first episode of the second season. I hope to subtract 24 from 25. I have tried everything I can think of, but nothing works. It’s driving me crazy. If Flexget has this feature, please give me some hints.

yes you can set a custom series id
in your series config, set a custom variable with the offset. then on the rename when moving, use the new id instead of the default accepted one if it exists.
series:
  - 'SERIES':
      alternate_name: SERIES_ALT
      set:
        custom_series_id: "{{(series_id)|int - 24)|string|pad(2)}}"
...
move:
  to: /blah/{{series_name}}/
  rename: "{{series_name}} {% if custom_series_id is defined %}S02E{{custom_series_id}}{% else %}{{series_id|pad(2)}}{% endif %}"


Daily build with lerna

Proposed Changes
Fix the issue related to the daily builds that are not being published due to changes in the directory structure.

@JuanAr Build still failing. Also looks like it needs to be rebased.

Pull Request Test Coverage Report for Build 445

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

Files with Coverage Reduction
New Missed Lines
%

packages/QnAMaker/bin/qnamaker.js
1
67.54%

Totals

Change from base Build 429:
-0.08%

Covered Lines:
2698

Relevant Lines:
3471

💛  - Coveralls

Build is passing. Code coverage is reporting decreased but this changes are not related to code coverage.


Type hints

Hello.
We are currently using aioredis with a ton of internal type stubs for it, but aioredis is kind of in a transitional/crisis period right now. So we would like to switch to aredis/coredis. If I submitted PRs with type annotations for a bunch of methods, would you consider merging them in?

Hi @Tinche - I'd strongly recommend holding off on spending any time on adding type hints  (or any non bug fix changes) on the state of the code that is in master branch right now (which is approximately == 2.x branch). The 2.x series that I've sort of frozen is backward compatible with aredis and contains some of the pending pull requests/fixes + python 3.10 support.
I'm currently (~85% done) in the midst of a significant refactor which involves some breaking changes, but also has proper type hinting support as a required goal. I hope to  get something in master and have atleast a beta release out in the next couple of days, and hopefully wrap up documentation cleanup next weekend.
The TL;DR of the breaking changes are:

Better consistency with redis docs in terms of method argument names & types (and default values)
Use of  enums for pure tokens
Stricter return types and  eventually, overloads for methods that can return different types
Removal of non essential extras such as cache
[Most probably] drop support for python 3.7
[Most probably] drop support using both bytes and strings and just defaulting to strings in and out with always decoded responses

In most simple cases the apis will not be significantly different from either redis-py or aredis so you should be able to drop it in to your code base with trivial effort.
Given what I've described above regarding breaking changes - if that would be manageable for your code base, I'd love to get some eyes (other than mine :grin:) on the 3.x candidate.
An example showing a combination of some of these changes:
Before:
   async def georadius(
        self,
        key,
        longitude,
        latitude,
        radius,
        unit=None,
        withdist=False,
        withcoord=False,
        withhash=False,
        count=None,
        sort=None,
        store=None,
        store_dist=None,
        any=False,
    ):

After:
    async def georadius(
        self,
        key: str,
        longitude: Union[int, float],
        latitude: Union[int, float],
        radius: Union[int, float],
        unit: Literal[PureToken.M, PureToken.KM, PureToken.FT, PureToken.MI],
        withcoord: Optional[bool] = None,
        withdist: Optional[bool] = None,
        withhash: Optional[bool] = None,
        count: Optional[int] = None,
        any_: Optional[bool] = None,
        order: Optional[Literal[PureToken.ASC, PureToken.DESC]] = None,
        store: Optional[str] = None,
        storedist: Optional[str] = None,
    ) -> Union[int, Tuple[Union[str, GeoSearchResult], ...]]:

Where GeoSearchResult and GeoCoordinates are still tuples but named.:
class GeoCoordinates(NamedTuple):
    latitude: float
    longitude: float

class GeoSearchResult(NamedTuple):
    name: str
    distance: float
    geohash: int
    coordinates: GeoCoordinates

Thanks - that is exactly the kind of feedback I'd love to get. I was toying with making Redis use generics for the return type - and you're absolutely right about not needing the union :+1:

Sorry for the delay but I've unfortunately not had much time in the last few weeks to work on this. Having said that I just noticed a major addition in redis-py itself to start adding async support (https://github.com/redis/redis-py/pull/1899) which is making me seriously rethink the usefulness of this project.

Good to know, however if this is just bringing aioredis 2.0 into redis-py (which is what it looked like the last time I looked), this project can still be useful. aioredis 2.0 was/(probably still) is much slower than aioredis 1.3 or aredis.

As maintainer of aioredis and also the person who did the redis py migration, having another option in the meantime is great, especially a maintained one. I would simply be careful around adding features; it gets very hectic very fast. Additionally, one of the other aioredis maintainers is refactoring the asyncio portion to improve performance back to original status, but until then this library is quite useful :)

This is an interesting and difficult point in the life of redis python, especially for asyncio.
I've not been able to manage even really getting half way done with the refactoring of aredis to a point that I can reason around the code enough to quickly iterate on adding features (since it was written by someone else).
I will probably have some time the next few weeks to see the type hinting support through. The half baked version so far is in https://github.com/alisaifee/coredis/commit/6ba867549e5f5a70a020b8d65a3d14ee03f2341d but I'm indeed starting to feel that this will quickly get out of hand for a single maintainer

My design goals for the refactoring are:

Stay as close to the redis command definition (both for command parameters and return types)
Minimal runtime overhead
Runtime type safety as an optional opt-in using beartype
Departure from the implicit response destructuring using global mapping and try to "inline" how a command is parsed and transformed in to a python equivalent
Full support for RESP3 to minimize the guess work around parsing response types.

@Tinche perhaps you can look at #20 which includes type hints. From my local testing the performance doesn't diverge from the 2.x branch but a second opinion wouldn't hurt.

I've merged the current state of type hints / updates to master and made an initial 3.0.0rc1 release.
Specifically related to the type hints you can see the WIP docs and the API documentation

@alisaifee Sorry, I was super busy but I might be able to review soon.

FYI I tagged / released3.0.0rc2 which contains the breaking api changes that I was referring to.


Add openshift as bundle suffix for ocp bundles

As of now each bundle have preset as part of it's name but that is not true for OpenShift bundles, we should add openshift preset for openshift bundles so that on the crc side we can use same logic for each type of bundles.

so that on the crc side we can use same logic for each type of bundles.

In CRC, this logic is centralized in a single method to go from preset to bundle name, and ideally the rest of CRC should treat this bundle name as something opaque. Apart from this method, CRC should not really care what the bundle name is/looks like.
I agree it would be nicer for consistency, but not having a direct preset <-> bundle name association allows us to indirectly test that we do not make wrong assumptions about bundle names :) Maybe we can name the openshift bundles crc_ocp_libvirt_4.11.1_arm64.crcbundle to keep that level of indirection while having some consistency?


Clarify rs2 values for scmode

One other improvement could be to clear the tag on an invalid scmode (i.e. no x/invalid perms and maybe rs2 > 1)? But regardless of that change in semantics this LGTM.

I created another ticket for that suggestion: https://github.com/riscv/riscv-cheri/issues/384


Forking a private repo from one private organization to another leaks the source

Description
I am running gitea 1.17.0 and I have two separate groups that are using the same server.
I wanted to share a project from one group to the other, to provide access to the code pre-release - but did not intend to share the source organisation, as they are separate.
When I forked from organisation1 to organisation2, I get a repository visible to organisation2 with the following message:
  organistion2 / uvc-gadget  [Private]
forked from organistion1/uvc-gadget

This seems like a leak of private information between the two groups, so I would consider this a 'bug', however it could also simply be a feature request to ask
"Please ensure that information such as the organisation/customer name is not leaked when forking a project between private organisations."
Gitea Version
1.17.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
provided by docker : gitea/gitea:1.17.0
Operating System
Linux
How are you running Gitea?
Docker compose.
version: '2.4'
services:
  web:
    image: gitea/gitea:1.17.0
    volumes:
      - /srv/gitea/data:/data
    expose:
      - 3000
    ports:
      - "4444:22"
    restart: unless-stopped

Database
SQLite

So proposed solution is to have option to hide fork information but keep it as forked repository?

Yes, I still believe it's useful to fork from one organisation to another, even if both are private (after all, I just had that need/requirement) - but the issue is that there was information leaked that was private.
In this instance, the code could be shared, but the fact that two organisations were working on the same thing was not supposed to be leaked. Of course I could have manually created the repository in both places, or had a base fork from a non-private or generic named private organisation maybe...
Otherwise, it could only be visible to members which are in both organisations perhaps? I'm not sure what the correct implementation is - but the result of identifying the hidden/private organisation to another hidden/private organisation was the bug/fault in my view.

But as a fork repository, he should always contribute code back to parent repository. I think it's difficult to hide all these information and keep it as a fork repository.

Who mandates that they should contribute back? (in this instance, as a member of both groups, I'd be in control of that anyway) - but the point is that the previously private organisation A (lets call them Microsoft) are now exposed to private organisation B (again for example sake lets call them Apple) ... This code in question belongs to 'me' in both cases, but I wanted to take work done for A/Microsoft, and share it in advance of making everything public with B/Apple - but now I have leaked the fact that I am working with Microsoft to Apple, which maybe they might not like - or might not have been in my interests to acknowledge at the time.
It's the distinction that a repository was forked from a private organisation to a separate private organisation that I'm querying here.
Now - I acknowledge, that the repository was 'forked' to be able to duplicate/replicate the repository from one private group to another. Perhaps that is considered a shortcut - and simply not an acceptable way to take an existing repository from one private group to another, but gitea allowed me to do so - and keep the repository private - but did so at the cost of leaking this originator information.
*All company names are examples only here, I don't work with/for either Apple or Microsoft.

Updated title to clarify that it's the name of the private organisation that is leaked, not any code, (which is obviously explicitly shared by the nature of the forking action)

I think maybe you need a repository copy feature but not fork? Even though the source can be hidden, since it's a fork repository, others will always ask you where the repository forked from.


Add a sleep to work around coarse time resolution in CI systems

rdar://problem/41383808

@swift-ci please smoke test

👍


feat(api): update routes to prepare for sws pocket app

:tada: This PR is included in version 3.0.0-alpha.46 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Force guava version to avoid conflict

We need to force guava version to 30.1-jre because with grpc upgrade in https://github.com/pravega/pravega/commit/572aae50332da36d81b8ee8e9c366b203b81d840 the guava version will be bumped to 31.0.1-android.

Closed via #153


just removed the extra blank gap .

@Himanshu2107 is correct here. Please stick to the style guide wherever possible.


Update 60-steam-input.rules to include rules for DualSense Edge

This should make the DualSense Edge fully functional. These rules have been taken from the Steam Deck's files and reformatted to better fit the rest of the rules in this file.
File From the Steam Deck: 71-sony-controllers.rules
If implemented, the DualSense Edge should function exactly as it does on the Steam Deck.

I have now tested the change on ChimeraOS, where it's already been accepted into main, and it's working perfectly. I have yet to run into any issues with these rules. I hope they can be incorporated here as well, so that everyone can enjoy using the Edge.

Any news about merging this PR?


Merge in updated left forearms

The first pass at the left forearm was missing the version number and handedness indicators debossed in the wrist.  This is now fixed.

Updating left forearm lookup table, no big changes otherwise


FFUF v1.5.0 Kali Exclusive - Bug on time-based matcher and not correct working on output

Hello,
we are aware of an issue on FFUF tool related to the -mt option. When we use -mt "<6000", on the FFUF header we see "Filter" word and not "Matcher" word. We are testing it on a Portswigger Lab about Time-based SQL Injection.
Furthermore, could you please fix the help output on -mt and -ft section because on the example are reported: >100 and <100 but should be correct to change them as ">100" and "<100" (with double quotes) because without double quotes the argument does not recognize the input.

Thanks for opening the issue. I'll look into these details shortly!


Front end layout

As discussed in #6, incorporate tailwindcss and setup a dashboard style structure for the app.

Good day @wliao008. I love this project.
I would love to be assigned this as I can handle this, but I would need a template.
Please could you point me to a webpage that suits what you desire for the dashboard, or maybe a low-fidelity design of what you want?
With that, I can be assigned and would start working on it

@Aahil13 that is awesome! I don't have permission to assign issue, but @Shivansh-yadav13 can.
The style that I think we're looking for is this: https://tailwindui.com/components/application-ui/application-shells/sidebar, where the left panel would be navigation menus (in this case it'd contain list of db tables etc).

@Aahil13 you can create a basic dashboard rn, I'll work on to create a figma design for future pages and features we will have and, then we will update the frontend.

@Shivansh-yadav13 I have just added tailwindcss and revamped the home page. Submitted the pull request here: #36.


ReactNativeBlobUtil.fs does not work on iOS

react-native-blob-util: 0.19.0
react-native: 0.69.12 (not New Architecture, not Expo)
Hello! I am having a lot of trouble getting any information to show up when I called ReactNativeBlobUtil.fs.stat on a URI from React Native Image Picker. After struggling with this for a bit and looking through all the troubleshooting tips, I decided to see if it worked on Android. It did.
Here's the example code, complete with all my desperate console.logs.
    const [imageSize, setImageSize] = useState<number | undefined>(undefined);

    {/* ...omitted... */}

    const scanPhoto = async () => {
        const photo = await launchImageLibrary({
          mediaType: 'photo',
          quality: 0.8,
        });

        if (photo.assets === undefined || photo.assets[0] === undefined) {
          // IRL we probably want to handle this in a way that doesn't suck. But for the demo page I'm too lazy.
          throw photo.errorMessage;
        }
        console.log('photo', photo.assets[0].uri as string);

        const decodedPath = decodeURIComponent(photo.assets[0].uri as string);
        console.log('decodedPath', decodedPath);

        let stats = await ReactNativeBlobUtil.fs.stat(decodedPath);
        console.log('stats', stats);
        setImageSize(stats.size);
    };

The decodedPath bit wasn't there originally and didn't seem to make a difference.
No error is thrown in the console. It prints out the 'photo' and 'decodedPath' debug statements, but then it never prints the "stats" out or changes the imageSize state.
I eventually rearranged the stat call to hopefully print out some helpful error information:
    ReactNativeBlobUtil.fs
      .stat(decodedPath)
      .then(stats => {
        console.log('stats', stats);
        setImageSize(stats.size);
      })
      .catch(err => {
        console.error(err);
      });

...and here's what I got:
Error: failed to stat path `file:///Users/kimtho/Library/Developer/CoreSimulator/Devices/987BB6D2-BF08-419E-89F4-BE467D42859F/data/Containers/Data/Application/C0915CC0-FBAA-4AA6-9E28-4CA2D9A083DD/tmp/3B8C7F15-4409-4C29-964C-D94157C92D74.jpg` because it does not exist or it is not a folder
    at fs.js:270:24
    at MessageQueue.__invokeCallback (MessageQueue.js:463:13)
    at MessageQueue.js:125:12
    at MessageQueue.__guard (MessageQueue.js:368:9)
    at MessageQueue.invokeCallbackAndReturnFlushedQueue (MessageQueue.js:124:10)
    at RNDebuggerWorker.js:2:384123

A similar message occurs if I try it on a physical iOS device as well (an iPhone mini 12). On an Android simulator or device, this works fine.
Thanks for your help!

Same thing with me and it's also returning false for fs.exists(), but I've confirmed the image is there by opening up the folder manually in finder

https://github.com/RonRadtke/react-native-blob-util/blob/master/ios/ReactNativeBlobUtil/ReactNativeBlobUtil.mm#L524
This is the failing line:
exist = [fm fileExistsAtPath:path isDirectory:&isDir];
NSFileManager doesn't seem to work with file-urls like file:///Users/.... If you strip away file:// from the decocedPath it works.

I'll see if I can adjust the code to automatically strip the file:// part


:focus and .active styles indistinguishable on toggle buttons

PoC: http://getbootstrap.com/javascript/#buttons-single-toggle
In Firefox 33.0 Ubuntu 14.06 LTS and Chrome 38 Ubuntu 14.06 LTS, the active button stays active until it is unfocused.

yes, this is a shortcoming of the current styles - :focus and .active are indistinguishable, and since even when clicking with the mouse (rather than just moving to the button with the keyboard) the button receives :focus, it's hard to tell the difference between a toggled button and one that's just been switched off... may have a look at this when I get a chance /cc @cvrebert

Duplicate of #13971?

Yup - sorry, should have checked for dupes. Closing this, but rest assured we'll be working on this, as it's something that bugged me recently as well :)


Feature request: compatibility with velero 1.2.0

Hi!
I'd like to ask if that would require a lot of effort to update the plugin to work properly with version 1.2.0 of Velero?
Thanks!

Hi @UncleIS,
I wrote a good portion of this and I do not believe it is being consumed or maintained by Cisco any longer, and I am no longer an employee there.  I also informed the Velero team that this is not being maintained.  I would recommend you check out the velero channel in the Kubernetes slack and see if someone has picked this support up and where that repo might be.


Docker image not building as part of CI

@LanderU, Docker image isn't building anymore. Can you please help me with that?

I'll have a look.

Something was cached on the dockerHub web page. I've removed the build and I've generated a new one. Hope this fix the problem.

Fixed!


Updated "configure" signature for TS completion

Once #71  gets fixed, this will be really helpful when working with TS - no more need to specify callback parameter type explicitly

Just noticed there's already open PR for that, sorry


Plugins - Add documentation for plugins

What
Add documentation for Plugins
Plugin notes:
https://docs.google.com/document/d/11yuUfSLT47yunW5HHTraBV1KBxbE5cYxO-NNb935Iq0/edit#
Create a plugin guide draft:
https://docs.google.com/document/d/1xLETvJApivoUiBw4enajmEKYp-07ItAQW0O7cBuesws/edit#
PR:
https://github.com/alphagov/govuk-prototype-kit-docs/pull/231
Why
So people can write and use them
Who

Developer (initially for first draft)
Content designer (for review and refinement)

Done when

[ ] documentation for plugin authors
[ ] review existing documentation for plugin end users
[ ] research next steps have been agreed

@ruthhammond @joelanman I've separated out the previous plugin assurance doc and the Create a plugin draft, as it was getting a little confusing.
@nataliecarey we've put together a structure for the create a plugin guide, which includes a tutorial aspect (create your first plugin) and more technical parts for the package.json and config file.
Are you able to build on the draft with the technical elements and the example plugin you walked me through before? It would be great to take the user through that process. Thanks!

plugin guidance is now online:
https://prototype-kit.service.gov.uk/docs/create-plugin


[vcpkg_build_qmake]Switch qmake build system to nmake in Windows.

Building system jom is very inefficient, try to switch to nmake.
Related: #4692.

install_qt.cmake in qt5-base still uses jom

also we should pass some parallel build argumenet because else building qt takes forever.

Building system jom is very inefficient, try to switch to nmake.

Could you elaborate please?
https://wiki.qt.io/Jom

jom is a clone of nmake to support the execution of multiple independent commands in parallel.

As far as others are aware jom is the tool you use to build Qt.

@heydojo  Take it easy, it's just a draft. If using nmake takes longer than jom, I will turn off this PR.

@Neumann-A  flag /mp parallel build
nmake can't parallelize, but the compiler itself is doing a good job

From the issue:

I have one PC (out of 3) where Jom consistently deadlocks (4 Jom process running without any progress for hours) within bigger builds of qt (e.g. qt5-base)

So the issue is not inefficiency (nmake will definitely be less efficient), but it appears there is a correctness issue in Jom on certain machines.

why closed?
code that works with the /MP flag
    if(CMAKE_HOST_WIN32)
        #vcpkg_find_acquire_program(JOM)
		find_program(NMAKE nmake)
        set(ENV{CL} /MP)
        set(INVOKE "nmake")
    else()
        find_program(MAKE make)
        set(INVOKE "${MAKE}")
    endif()

@Voskrese

After testing, the time to use nmake is greater than the time to use jom.
According to @ras0219-msft said, we need to solve the jam problem of jom instead of replacing it with nmake.

@Jackboosy.
maybe a solution like the PREFER_NINJA solution in the CMake generator selection?
Let the user set e.g. VCPKG_AVOID_JOM in a triplet to force nmake instead of JOM

@JackBoosY
from JOM the known problem for a long time, at multithreading, it begins to compile the new file, without having compiled dependence, and as a result there is a conflict, dependence is not present, and compilation went, an error