EXPERIMENTAL: Explore the finite magma refutation data and see how the number of variables in the law play a role

Discussed in https://leanprover.zulipchat.com/#narrow/stream/458659-Equational/topic/visualization.20of.20graph.20closure .  Let k denote the number of variables in a law.  As discussed above, the k=1 laws should be underdetermined and obeyed by a large number of finite magmas; k=2 laws should be determined and obeyed by a few number of finite magmas; and k>2 laws should be overdetermined and obeyed by mostly just the trivial magma.  Now that we have data sets of what laws are obeyed by which finite magmas of order up to 4, plus some selected larger magmas, some data analysis should be able to see whether this heuristic holds up, and whether there are anomalous laws that exhibit a different number of solutions than the heuristic predicts.
When done, report on the outcome of the experiment in a new chapter of the blueprint.

One can also explore the statistics of the implication graph stratified by k.  For instance, the above heuristic predicts that the k=1 laws should have many laws implying them, but few consequences, whereas the k>2 laws should have the opposite.  It should in particular be quite rare for a low k law to imply a high k law, though this is not an absolute prediction (e.g. one can artificially introduce more variables via substitutions).


Removed disableSslCertValidation

pyVim/connect.py
doesn't have disableSslCertValidation argument for SmartConnect.
So instead of this already a method is there SmartConnectNoSSL which can be used instead.

disableSslCertValidation is available in SmartConnect since https://github.com/vmware/pyvmomi/commit/4f3294d0b32bf54bd04b468a523a5d539d13f7d2


Add deployment guide.

Implements most of #88, but monitoring and backup/restore are still not done.
Would like to decide if we are implementing #66 before completing the backup/restore docs.
For monitoring, we may want to add some http endpoint for pinging the front end. @dajohi do you still have monit configurations for dcrstakepool? Could be adapted for vspd?

@vctt94 could you confirm if this deployment guide covers everything you encountered when setting up vspd?


not all files are being archived in a single run

successive archive results were 30K, 1K, 0 for 3 runs, maybe individual folders have max limits?

todays runs:
5947 of 6476
226 of 784
0 of 558


Support BTCC

Interesting project. I could see that you have made some bitcoins from these trades but the Poloniex fee rates are high. Why not support BTCC? It doesn't charge fees for trading. :-)

Thanks for the comment.  There's been some discussion of strategies to manage fees@ https://github.com/owocki/pytrader/issues/5 -- integrating with a low-fee or no-fee exchange is certainly an attractive option.

Good to know! Moving the suggestion to #5 and closing this one.

Thanks.  its a good suggestion!  Feel free to sign up to the slack -- We are organizing contributions in a more immediate way there https://github.com/owocki/pytrader/issues/23


Converted Strings to Unicode

Solution for #36 by converting python string literals to unicode usage.

Sorry to hear, I will check it.

Try out functionalities like copy/ paste. @stefanseibert

Sorry, I will not have the time to finish this up, came too much other stuff up at work :(


Updates to NamelessMatchSpec to allow deserializing

While working on this issue:

https://github.com/prefix-dev/pixi/issues/76

I realized that I was going to need to be able to deserialize the NamelessMatchSpec struct from a mapping. I believe the easiest way to allow this is by adding Deserialize to derive in the correct places.
On NamelessMatchSpec I also chose to use DisplayFromStr for version and build because I believe that's the easiest way to do it. I would be happy to change it if that's not right though.
Below is my simplified use case:
use std::fs;
use std::path::PathBuf;

use indexmap::IndexMap;
use clap::{Parser};
use serde::Deserialize;
use serde_with::{serde_as, DisplayFromStr, PickFirst};
use rattler_conda_types::NamelessMatchSpec;

#[derive(Parser)]
#[command(name = "tt - TOML test")]
#[command(author = "Travis Hathaway")]
#[command(version = "0.1.0")]
#[command(about = "Tests with TOML parsing")]
struct Cli {
    /// TOML File
    toml_file: PathBuf,
}

/// Describes the contents of a test project manifest.
#[serde_as]
#[derive(Debug, Clone, Deserialize)]
pub struct MyManifest {
    #[serde_as(as = "IndexMap<_, PickFirst<(_, DisplayFromStr)>>")]
    dependencies: IndexMap<String, NamelessMatchSpec>
}

fn main() -> Result<(), Box<dyn std::error::Error>>{
    let cli = Cli::parse();

    println!("{:?}\n", cli.toml_file);

    if cli.toml_file.exists() {
        let contents = fs::read_to_string(cli.toml_file)?;
        let manifest = toml_edit::de::from_str::<MyManifest>(&contents)?;

        println!("Dependencies:");
        println!("{:?}", manifest.dependencies);

    } else {
        println!("File does not exist");
    }

    Ok(())
}

Thanks @travishathaway!


Please bump firebase_auth version to ^0.6.2

Having firebase_auth at version ^0.5.7 in my project as requested by the flutter_firebase_ui causes the following error to be thrown:
FAILURE: Build failed with an exception.

* What went wrong:
Failed to capture fingerprint of input files for task ':app:checkDebugClasspath' property 'compileClasspath' during up-to-date check.
> The library com.google.android.gms:play-services-base is being requested by various other libraries at [[15.0.1,15.0.1]], but resolves to 16.0.1. Disable the plugin and check your dependencies tree using ./gradlew :app:dependencies.

Please bump the version to ^0.6.2

bump. Is anyone working on this?

Apparently the master branch's pubspec.yaml was updated 15 days ago by @ypelud
When should we expect an update to the central pub repo?

done today


feat: add no_std support

Some of the changes are taken from the another deim/bcs fork:
https://github.com/zefchain/bcs

We could probably divide this commit into smaller, single feature-related ones (even within one PR) as there are some groups of changes made.

I do agree, but that would take a lot of our time.


CB-13208: (windows) Fix readAsBinaryString to only read the requested range

Platforms affected
Windows
What does this PR do?
Change readAsBinaryString on FileReader for Windows to use a stream which seeks to the start position and only reads until the requested end instead of reading the entire file to a buffer then slicing the requested fragment.
What testing has been done on this change?
Plugin change has been tested on Windows as that's the only platform affected.
Checklist

[X] Reported an issue in the JIRA database
[X] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform affected.
[X] Added automated test coverage as appropriate for this change.

Did I get this right that this basically adds an additional step in between where only the requested part is read into buffer?
There seems to be a conflict now, can you fix that by rebasing your changes?

That is correct, I am using the other read methods as a template.
The merge conflicts should be resolved now.
Thanks!

Any status on this PR?

Hey, I just fixed the problem that caused Android tests to fail in master. Could you rebase this PR please? This should get rid of the Android failures and possibly fix all test failures for this PR.

Rerun tests with current config.

CI: Once more please.

@janpio Sorry for the delay but just noticed your request. I merged apache/master into my fork which has updated this PR. Let me know if there is anything else I can do to help with.
Thanks!

Oh sorry, this wasn't even a request - I just have to close, then reopen the PR to trigger a CI rebuild ;) So I was talking to myself or CI (which doesn't listen of course, but rebuilds becaus of the open/close dance I was doing) ;)

Is this PR abandoned or fixed in another PR?

I take this PR will never be merged. Going to close it to remove it from my list of open PRs. This is an issue but I assume the platform has been abandoned.


Dictionary is Russian and not Bulgarian?

It seems the dictionary has many Russian words that are not Bulgarian. Are you sure about the dictionary that is used?

The dictionary is Bulgarian. The Bulgarian and Russian languages have many common words

Yeah, I know some words are the same. But there are some words in the list that were not recognized by some native speakers, like "ТРЕФА". Could be of course that either they are just not acquainted with the word, but wondered if there are maybe not some loan or imported words from e.g. dialects or other languages in the list.

"ТРЕФА" means "clubs" in game of cards. I think it is a slang, so that is why most people don't know it.

Ok thanks for your clarification!


Fix Range's "changed" signal emitting with a value even if binded to emit none

Fixes #29817.

For the reference, this issue seems to exist since the first open source commit of Godot. I had a quick look at rg 'connect.*"changed"' and I don't see any class actually connecting to this (bogus) signal, so I think this change is safe.

Thanks!


we need some feedback that the observatory is up and available to connect to

From https://github.com/flutter/tools/issues/110
The CLI VM prints out Observatory listening on http://<IP_ADDRESS>:8989 when run w/ the observatory enabled. Perhaps the flutter runtime should to the same?
It looks like the VM doesn't print on startup if you use the default port of 8181. And parsing stdout for a token isn't the most reliable way of doing things.
We could change the flutter start command to not return until the process is up and running on android. Then we'd know, when that completes, that the observatory is ready to connect to.

cc @devoncarew still needed?

Yup -

We print this now.


Introducing Farm Guru on Gurubase.io

Hello team,
I'm the maintainer of Anteon. We have created Gurubase.io with the mission of building a centralized, open-source tool-focused knowledge base. Essentially, each "guru" is equipped with custom knowledge to answer user questions based on collected data related to that tool.
I wanted to update you that I've manually added the Farm Guru to Gurubase. Farm Guru uses the data from this repo and data from the docs to answer questions by leveraging the LLM.
In this PR, I showcased the "Farm Guru", which highlights that Farm now has an AI assistant available to help users with their questions. Please let me know your thoughts on this contribution.
Additionally, if you want me to disable Farm Guru in Gurubase, just let me know that's totally fine.

Seems nice! I'll merge this PR

Hi @wre232114,
I’d like to update you on the release of the Maintainer Panel feature on Gurubase. With this panel, you can add, remove, or update data sources, as well as change the logo and more. You can find the details here.
In the near future, I’m planning to include analytics insights in this panel, such as the number of questions asked, the most frequently asked ones, and more. I’ll be sure to update this thread once it’s available. However, in case I miss it, I highly recommend joining our Discord channel to stay updated.
If you’d prefer that I don’t update this thread anymore, please let me know.

it's awesome! you can update this thread


How to draw a single path with different coloring on different segments?

Is there a way to do this? The current behavior is that whenever you set color, the lines are connected based on the color group.  I would like to connect the lines based on the order in which the data appears, but coloring the segments based on another variable.

Related to this, I'd like the ability to change other properties of individual line segments as well, such as width or line_style.  It's certainly possible within Compose... what would it take to open this up to Gadfly.Geom as well?  (I'm happy to submit a PR if you can point me in the right direction)

You can change them post-hoc in Immerse with setproperties!. See https://github.com/JuliaGraphics/Immerse.jl/blob/master/test/properties.jl
That doesn't directly address the original question, however.

I spent some time inside Gadfly and Compose looking into this, and I think this is going to be tricky without a big rewrite of some core parts of both packages.  Sorry to say, no matter how much time I spend staring at those internals, they are never as intuitive as I want them to be.
It seems that around here the properties (stroke color, for example) are pushed onto the stack before the loop drawing all the children.  This means that all children get the same properties, even if you pass an array of colors into the stroke method within Compose.  In fact, there's a place with a hardcoded 1-index in which I think guarantees that it won't access the color vector when setting cairo properties.
@dcjones please correct me if I'm wrong about any of this!

@zywind There's not a built in way to do per-segment coloring per se, but you can fake it without too much effort by just making a separate line for each segment. Here's an example:

@tbreloff The hard-coded 1-index is applying scalar properties, for which there only is one element, so it's not discarding properties. If you want to draw line segments differently, you just have to split them into separate lines. That's how it works on most graphics backends (cairo, svg, etc), compose isn't peculiar in this regard. So coloring segments differently could just be implemented in Geom.line rather easily, by just automating what I did above.

Ok thanks @dcjones. I'll use this example to dig through the code a little more.
Also a side point... I've started implementing real time updating through Plots, and the basics are working. I was pleasantly surprised at the performance of Immerse/Gadfly... See https://github.com/tbreloff/Plots.jl/issues/30#issuecomment-143004624. Have you pushed performance improvements recently?

On Sep 25, 2015, at 3:10 AM, Daniel C. Jones<EMAIL_ADDRESS>wrote:
@zywind There's not a built in way to do per-segment coloring per se, but you can fake it without too much effort by just making a separate line for each segment. Here's an example:
@tbreloff The hard-coded 1-index is applying scalar properties, for which there only is one element, so it's not discarding properties. If you want to draw line segments differently, you just have to split them into separate lines. That's how it works on most graphics backends (cairo, svg, etc), compose isn't peculiar in this regard. So coloring segments differently could just be implemented in Geom.line rather easily, by just automating what I did above.
—
Reply to this email directly or view it on GitHub.

@tbreloff,
keep in mind that you update (in your example) something below 1000 points. Speed degradation in rendering with Cairo shows up in higher regions. In all my experiments using Gadfly rendering into a window, i was also successful drawing ~10-20ms.

Thanks @dcjones. I'll use your method for my code. It would be very nice if this is automated.

@lobingera I started to worry that there was some underlying explosion in drawing time with additional points, so I threw together a test to time the time-to-update after adding 500 new points to each series repeatedly.  The results are linear, which is good (and expected), although a highly optimized library might be able to go sub-linear by not drawing overlapping items.  Results:

For comparisons sake, though... here's the same test with Qwt as the backend.   For this test, Qwt is about 4x faster (and the current implementation uses PyCall to access a python library PyQwt which then re-wraps a C++ library Qwt, which eventually draws to a QPainter object...)

Back to the original question.  This is not an easy thing to do with Gadfly, and there are limitations.  You'll have to call it through Plots.jl (I haven't pushed the changes to master yet, but there's a great hack to do something like what Daniel did above), and here's how:
If you pass in the same number of colors as data points, it works as expected IF there are no duplicate colors:

This should work for paths too, which probably wouldn't work with Daniel's example:

But things start to break if you don't have enough colors:

Or if there are not enough unique colors:

I don't think these issues can be fixed easily, but maybe Daniel knows how.

I just pushed up my changes to Plots... give it a try and see if it meets your needs.

You can fix this using the group aesthetic:

I'm not totally sure why it works but it does! :+1:


send diffs of numpy arrays when syncing changes

It would be great if we didn't have to sync an entire array every time any element changed. Some ideas:

Compute a sparse difference between old and new values and send just that. If the data type changed, probably send the entire array. If the size changed (e.g., data was appended), send the new size information.

Use a binary diffing algorithm, such as xdelta or simply python difflib

#150 I believe was moving towards this


Added int_frac function for configuring PWM

It's a bit late, but finally got around to raising a PR for issue https://github.com/raspberrypi/pico-sdk/issues/734.
I've done some testing, but perhaps worth your team testing too before merging.
Also, I don't know whether its worth mirroring the pwm_config_set_clkdiv_int with a pwm_set_clkdiv_int too? As mentioned in the issue, it seems somewhat redundant, since PIO only has the int_frac version.

I agree that pwm_set_clkdiv_int would be redundant - if the user wants that they can just pass in a 0 for the fractional part :slightly_smiling_face:

...although whilst we're here, I wonder if it might make sense to change the implementation of pwm_config_set_clkdiv to more closely look like https://github.com/raspberrypi/pico-sdk/blob/develop/src/rp2_common/hardware_pwm/include/hardware/pwm.h#L391 ? :shrug:
(and perhaps it makes sense to change pwm_config_set_clkdiv_int to just call pwm_config_set_clkdiv_int_frac(c, div, 0); ? )

@lurch so change them to be like?
static inline void pwm_config_set_clkdiv(pwm_config *c, float div) {
    valid_params_if(PWM, div >= 1.f && div < 256.f);
    uint8_t i = (uint8_t)div;
    uint8_t f = (uint8_t)((div - i) * (0x01 << 4));
    pwm_config_set_clkdiv_int_frac(c, i, f);
}

static inline void pwm_config_set_clkdiv_int(pwm_config *c, uint div) {
     pwm_config_set_clkdiv_int_frac(c, (uint8_t)div, 0);
}

so change them to be like?

Yup, as long as @kilograham is okay with that suggestion? :slightly_smiling_face:


Optimize full res display

Currently, our gallery lib attempts to load all the full res images in a given thread at once. For local images, this is pretty quick. But for remote images, this can be quite slow, leading to a less optimal UX. We should consider doing something like:

show thumb for all
when on a photo
load full, and replace

Since the images are only displayed one to a 'page', this shouldn't mess up things for tiling or gallery building.

This is actually incorrect. The lib is pretty smart about only loading as many images as it needs.


chore(readme): update wording

Update with more natural wording

lgrm

@wesleycho can you rebase the PR against the current master changes?

Done


Implement DotTranslator getFromStore results translation

Requires #91
Child of #46
Given a QueryContext and REST data from the DotDelegator, convert the rest data into the proper witsml POJO serialized string for the object type and version.

Do this for WELLs only

After the DoT delegator performs the querying to populate a query context JSON object, do the following:

use WitsmlObjects library to convert that json to a <IP_ADDRESS> object POJO (Chris is providing a GIST example on how to do this)
Convert the POJO to <IP_ADDRESS> using the witsml object library conversion support if qc.VERSION is <IP_ADDRESS>
serialize the POJO to an xml string and return it from the translator -> valve -> addToStore method -> client


MissingInputException for Valid Downloadable URL

I am encountering an unexpected error when using the storage plugin. I have the following link which downloads a xlsx file from the destatis data base (https://www.destatis.de/DE/Home/_inhalt.html):
"https://www.destatis.de/EN/Themes/Economy/Prices/Publications/Downloads-Energy-Price-Trends/energy-price-trends-xlsx-5619002.xlsx?__blob=publicationFile"
The link has no redirects and works properly when running it in the browser or in requests.get. However, when using it within the storage function, like in
rule retrieve_irena:
    input:
        storage(
            "https://www.destatis.de/EN/Themes/Economy/Prices/Publications/Downloads-Energy-Price-Trends/energy-price-trends-xlsx-5619002.xlsx?__blob=publicationFile",
        ),

the workflow throws the following error:
Assuming unrestricted shared filesystem usage.
Building DAG of jobs...
MissingInputException in rule retrieve_irena in file /home/fabian/playground/snakemake-storage/Snakefile, line 1:
Missing input files for rule retrieve_irena:
    affected files:
        https://www.destatis.de/EN/Themes/Economy/Prices/Publications/Downloads-Energy-Price-Trends/energy-price-trends-xlsx-5619002.xlsx (storage)

I tried to understand what is going on, but could not resolve it. It seems to me like a bug, but perhaps I am missing a required setting.

It appears that there can be several causes that all result in the same MissingInputException, it could be an authentication issue (that happened to me today), but I suspect that in this case it is the ?__blob=publicationFile at the end that causes the issue. This URL for example seems to work just fine: http://wettelijkerente.net/wettelijkerente2.csv

ah no, I found the issue for your URL. snakemake uses requests.head to get some initial data from the file without downloading it in its entirety, but that returns an HTTP 303 status, which tells you to redirect elsewhere, but even following that redirect returns an HTTP 400 'Bad request'. So the assumption of snakemake is that every HTTP server supports both the HEAD and GET HTTP verbs, but that is not the case on this server.
I think the best way to fix this would be to add a configuration flag on the storage provider supports_http_head, which defaults to True, but can be set to False to use GET also to query the metadata.
Alternatively, a allow_http_get_fallback flag could be created instead, which defaults to False, but when set to True would fall back to GET on certain HTTP status codes. However, it might be quite tricky to get the correct set of status codes, because I think the error 400 would actually be a code on which you would not retry with GET. Therefore the supports_http_head flag would seem to me to be a better approach. I will create a pull request to implement this shortly.
@johanneskoester is there a way to make the MissingInputException give more feedback for remote files, because once a network is involved there are a lot of reasons for the file to (temporarily) not be found, even for a valid resource.


Add documentation for EnvironmentPlugin

Includes new API from https://github.com/webpack/webpack/pull/3161 which is not yet merged.

I did not see content/plugins folder until now. It seems incomplete and not yet published to the site.
Should this be moved to a separate file in that folder?

I've moved the documentation to content/plugins/environment-plugin.md and adopted the writing style used in the other plugin documentations.

I did not see content/plugins folder until now. It seems incomplete and not yet published to the site.

The setup is partially dynamic. Any files placed there will be picked up by the build (it's aggregate of plugin readmes + this kind of data).

Beware that this documents a feature which isn't available before<EMAIL_ADDRESS>I'm not sure how long until it's released, so if you want this documentation merged before it arrives, we can add a notice about when that feature becomes/became available.

Maybe it would work if you documented the old behavior first (there's EnvironmentPlugin in webpack 1 even) and added a big fat warning (W>) to the section about the new work. Or we can just merge the docs when a new version of webpack goes out. Either is fine by me.

I gave it a try, but since the example is also based on the new feature, I would be a large rewrite. Suggest we wait for<EMAIL_ADDRESS>instead.

Yeah, let's do that. One more option would be to push EnvironmentPlugin out of the core to webpack-contrib (pair with DefinePlugin?), but that would take a bigger decision as it might have other implications (uglify etc.). 👍

This should be good to go according to https://github.com/webpack/webpack/releases/tag/v2.2.1 .
Can you fix the conflict so we can merge?

Fixed

I merged it as a version of webpack with the functionality has been released. Thanks again.


Replace scandir() with glob("*.php")

This way we prevent a lot of code smell and confusing bugs

been there done that

naffan pls


[BUG] Oven Rempte

Describe the bug
This integration does not seem to work with LG Wall oven.  I do not see the expected values.
Expected behavior
I know this is a new integration.  Just trying to provide some feedback on how its working with my oven.
In HA sensor.oven_oven_lower_target_temperature shows the value of "Unknown" while I see in the log that 350 is reported.
Also would like to see the current temperature as a sensor.  This is also reported in the log as 'lowerCurrentTemperatureValue': 185.0.
The lower oven has a remote start capability so that would be nice to see as a service.  The upper oven is a combo convection/microwave.  I cannot see a way to start that one from the iOS app so I think that may not be possible.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment details:

Environment (HASSIO, Raspbian, etc):
Home Assistant version installed: core-2021.6.3
Component version installed: 0.8.8
Last know working version: None
LG device type and model with issue: LSWC307ST
LG devices connected (list):

Output of HA logs
Paste the relavant output of the HA log here.
I have debug turned on for this integration and see the following Oven related output that might be of use.
'deviceState': 'E', 'snapshot': {'ovenState': {'upperControlLock': 'DISABLE', 'cooktop1CooktopState': 'INIT', 'cooktop2CooktopState': 'INIT', 'cooktop5PowerLevel': 0.0, 'lowerEasyCleanEnable': 'DISABLE', 'cooktop1OperationTimeHour': 0.0, 'upperAutoCookName': 'NONE', 'cooktop5CooktopState': 'INIT', 'lowerRemainTimeSecond': 59.0, 'lowerRemoteStartUsing': 'ENABLE', 'cooktop2OperationTimeSecond': 0.0, 'upperEasyCleanEnable': 'DISABLE', 'upperTargetTemperatureUnit': 'FAHRENHEIT', 'cooktop3CooktopState': 'INIT', 'cooktop4OperationTimeSecond': 0.0, 'cooktop2OperationTimeHour': 0.0, 'lowerDoorLock': 'DISABLE', 'cooktop4CooktopState': 'INIT', 'upperTimerSecond': 0.0, 'upperSabbath': 'DISABLE', 'upperState': 'INITIAL', 'upperDoorLock': 'DISABLE', 'lowerMyRecipeCookNumber': 0.0, 'cooktop4PowerLevel': 0.0, 'cooktop3OperationTimeHour': 0.0, 'upperTimerSet': 'ENABLE', 'cooktop5OperationTimeHour': 0.0, 'lowerDoorOpen': 'DISALBE', 'lowerDemoMode': 'DISABLE', 'lowerCurrentTemperatureUnit': 'FAHRENHEIT', 'lowerRemainTimeMinute': 11.0, 'lowerTimerHour': 0.0, 'upperTimerHour': 0.0, 'cooktop1PowerLevel': 0.0, 'lowerEasyCleanCount': 0.0, 'upperRemainTimeMinute': 0.0, 'upperTimerMinute': 0.0, 'cooktop3PowerLevel': 0.0, 'lowerManualCookName': 'LOWER_BAKE', 'lowerSabbath': 'DISABLE', 'lowerTimerSecond': 0.0, 'drawerPowerLevel': 0.0, 'lowerCurrentProveTemperatureF': 0.0, 'upperTargetTemperatureValue': 0.0, 'upperRemoteStart': 'DISABLE', 'upperRemainTimeHour': 0.0, 'upperFotaEnable': 'DISABLE', 'lowerTargetTemperatureUnit': 'FAHRENHEIT', 'upperDoorOpen': 'DISALBE', 'cooktop1OperationTimeSecond': 0.0, 'cooktop3OperationTimeSecond': 0.0, 'lowerRemainTimeHour': 0.0, 'upperCurrentTemperatureValue': 94.0, 'lowerIsError': 'DISABLE', 'lowerTargetProveTemperatureF': 0.0, 'lowerTargetTemperatureValue': 350.0, 'cooktop5OperationTimeSecond': 0.0, 'lowerTimerSet': 'ENABLE', 'upperRemainTimeSecond': 0.0, 'lowerControlLock': 'DISABLE', 'lowerCurrentTemperatureValue': 185.0, 'upperRemoteStartUsing': 'DISABLE', 'upperOptionSet': 'ENABLE', 'cooktop2PowerLevel': 0.0, 'upperMWOPowerLevel': 0.0, 'lowerTimerMinute': 0.0, 'lowerState': 'PREHEATING', 'upperDemoMode': 'DISABLE', 'lowerFotaEnable': 'DISABLE', 'cooktop1OperationTimeMinute': 0.0, 'upperIsError': 'DISABLE', 'upperEasyCleanCount': 0.0, 'upperCurrentTemperatureUnit': 'FAHRENHEIT', 'cooktop2OperationTimeMinute': 0.0, 'cooktop4OperationTimeMinute': 0.0, 'lowerOptionSet': 'DISABLE', 'upperManualCookName': 'NONE', 'cooktop3OperationTimeMinute': 0.0, 'cooktop5OperationTimeMinute': 0.0, 'lowerRemoteStart': 'ENABLE', 'cooktop4OperationTimeHour': 0.0}, 'mid': 75980518.0, 'online': True, 'static': {'deviceType': '301', 'countryCode': 'US'}, 'meta': {'allDeviceInfoUpdate': False, 'messageId': 'AAy8qkEDRu-JmwyZyXT5WA'}, 'timestamp':<PHONE_NUMBER>580.0}, 'online': True, 'platformType': 'thinq2', 'area': 334505, 'regDt':<PHONE_NUMBER>3229.0, 'blackboxYn': 'Y', 'order': 0, 'drServiceYn': 'N', 'fwInfoList': [{'checksum': '0000E145', 'partNumber': 'SAA41423501', 'order': 1.0}], 'modemInfo': {'modelName': 'WLC389PC', 'appVersion': 'clip_hna_v1.9.080', 'modemType': 'QCOM_QCA4010', 'ruleEngine': 'y'}, 'guideTypeYn': 'Y', 'guideType': 'TYPE4', 'regDtUtc': '20201203003229', 'regIndex': 0, 'groupableYn': 'N', 'controllableYn': 'N', 'combinedProductYn': 'N', 'masterYn': 'Y', 'pccModelYn': 'Y', 'autoOrderYn': 'N', 'initDevice': False, 'existsEntryPopup': 'N', 'tclcount': 0}, {'appType': 'NUTS', 'modelCountryCode': 'WW', 'countryCode': 'US', 'modelName': 'F3P2CYUBE__', 'deviceType': 201, 'deviceCode': 'LA02', 'alias': 'Washer', 'deviceId': '035700b2-63e3-1879-a419-402f86f14cb5', 'fwVer': '', 'imageFileName': 'home_appliances_img_wmdrum.png', 'imageUrl': 'https://objectstore.lgthinq.com/3120cb69-4c7c-48d5-9d..............

Additional context
Add any other context about the problem here.

Thanks for the feedback and information, could you also provide JSON device information file?
I will try to fix as soon as I will have some additional free time.

When I call the service as shown below I receive and error in the lower left
"Failed to call service ......: Unknown Error"
Then in the log the below appears:
021-06-09 20:23:10 ERROR (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Error executing script. Unexpected error for call_service at pos 1:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 368, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 568, in _async_call_service_step
await service_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1491, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1526, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 666, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 658, in entity_service_call
future.result()  # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 760, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 695, in _handle_entity_call
await result
File "/config/custom_components/smartthinq_sensors/sensor.py", line 680, in async_remote_start
raise NotImplementedError()
NotImplementedError
2021-06-09 20:23:10 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140170557413216] Error handling message: Unknown error
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 25, in _handle_async_response
await func(hass, connection, msg)
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 525, in handle_execute_script
await script_obj.async_run(msg.get("variables"), context=context)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1216, in async_run
await asyncio.shield(run.async_run())
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 350, in async_run
await self._async_step(log_exceptions=False)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 368, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 568, in _async_call_service_step
await service_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1491, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1526, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 666, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 658, in entity_service_call
future.result()  # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 760, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 695, in _handle_entity_call
await result
File "/config/custom_components/smartthinq_sensors/sensor.py", line 680, in async_remote_start
raise NotImplementedError()

It seems no JSON file is present.
Am I submitting the correct service?

Remote start is only for DRYER and WASHER, not for Oven. You correctly receive "NotImplementedError".

Is this what you need?
98156830.txt

No, this is the translation, I need the definition.

OvenJSON.txt

Could you check if with last release target and current temperatures are properly detected?

I updated and checked the target and current temperatures and the on/off sensors and they all seem to work.  The lower oven current temperature reads zero until the temperature exceeds 130degF.  The upper over current temperature always seems to work.  Its a cool feature to be able to see the current temperatures using this automation as this is not otherwise available on the oven display or the LG App.
Many sensors, not appropriate to this double wall oven, show "unavailable".  For others who read this in the future the below screen shot shows the sensors that work.  At the time of this writing there are no services available to control the wall oven.  A note for future developments is that it is not possible to start the upper over from the LG App so it may not be possible to do it from HA either.

Thanks again to #ollo69 for making all this work.

I will review this in the future to not create sensor not appropriate. The reason is this part is implemented to manage both Oven and CookTop, but i think that is possible to determinate what is availble and what not
Probably binary_sensor "Oven" should be renamed something like "Oven State".

Seems that is not possible to avoid creation of all sensors because all info are always provides and available in the JSON info file. There is something available in the config section of the JSON Info, but I don't have enough information to base a filter on this.
For the moment with last release I changed some name and icons of the sensors.

Can we close this issue? Additional feature request can be opened in new threads.

Yes I think so.  Thanks for sorting this out.  Its not a big deal to have to decide the appropriate sensors for the appliance you have.
Would rather dedicate and resource you have to creating services.

Ok, I close this, pls open a new feature request for Range control so that we can keep track for this.


Error installing with python3.6.9

Hello there!
root@scan:/leveldb-1.20/include# pip3 install coincurve
Collecting coincurve
Using cached https://files.pythonhosted.org/packages/65/31/9f13921cc7ca27059af4def1a9d1277a6a252dea967b62f9ea05cc2a4115/coincurve-15.0.0.tar.gz
Requirement already satisfied: asn1crypto in /usr/lib/python3/dist-packages (from coincurve)
Requirement already satisfied: cffi>=1.3.0 in /usr/local/lib/python3.6/dist-packages (from coincurve)
Requirement already satisfied: pycparser in /usr/local/lib/python3.6/dist-packages (from cffi>=1.3.0->coincurve)
Building wheels for collected packages: coincurve
Running setup.py bdist_wheel for coincurve ... error
Complete output from command /usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-qgvqo9t3/coincurve/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" bdist_wheel -d /tmp/tmpz0lxusq_pip-wheel- --python-tag cp36:
/usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
warnings.warn(msg)
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.6
creating build/lib.linux-x86_64-3.6/coincurve
copying coincurve/context.py -> build/lib.linux-x86_64-3.6/coincurve
copying coincurve/utils.py -> build/lib.linux-x86_64-3.6/coincurve
copying coincurve/_windows_libsecp256k1.py -> build/lib.linux-x86_64-3.6/coincurve
copying coincurve/ecdsa.py -> build/lib.linux-x86_64-3.6/coincurve
copying coincurve/init.py -> build/lib.linux-x86_64-3.6/coincurve
copying coincurve/flags.py -> build/lib.linux-x86_64-3.6/coincurve
copying coincurve/keys.py -> build/lib.linux-x86_64-3.6/coincurve
copying coincurve/types.py -> build/lib.linux-x86_64-3.6/coincurve
copying coincurve/py.typed -> build/lib.linux-x86_64-3.6/coincurve
running build_clib
/tmp/pip-build-qgvqo9t3/coincurve/libsecp256k1/autogen.sh: 3: /tmp/pip-build-qgvqo9t3/coincurve/libsecp256k1/autogen.sh: autoreconf: not found
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-build-qgvqo9t3/coincurve/setup.py", line 309, in
**setup_kwargs
File "/usr/lib/python3/dist-packages/setuptools/init.py", line 129, in setup
return distutils.core.setup(**attrs)
File "/usr/lib/python3.6/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/lib/python3.6/distutils/dist.py", line 955, in run_commands
self.run_command(cmd)
File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/tmp/pip-build-qgvqo9t3/coincurve/setup.py", line 95, in run
_bdist_wheel.run(self)
File "/usr/lib/python3/dist-packages/wheel/bdist_wheel.py", line 204, in run
self.run_command('build')
File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/usr/lib/python3.6/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/tmp/pip-build-qgvqo9t3/coincurve/setup.py", line 152, in run
subprocess.check_call([autogen], cwd=absolute('libsecp256k1'))
File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/tmp/pip-build-qgvqo9t3/coincurve/libsecp256k1/autogen.sh']' returned non-zero exit status 127.

Failed building wheel for coincurve

Done. I've tried in fresh ubuntu 18.xx VPS and i found i didn't have the requirements:
https://pypi.org/project/coincurve/5.0.0/#installation
build-essential
automake
pkg-config
libtool
libffi-dev
libgmp-dev

after install them, i tried again and works OK.


Getting and setting Cookies

Hey, I just started using C# and I was looking into this PCL. I got it working after looking at examples and everything. I was wondering if it was possible to get the Cookies from the connection and using storing and sending those Cookies when a new connection is made.
If that can be done, could you please post an example? Thanks for this lib. anyways :)

By default, HttpClient disposes it's handler after the first use, even if you make multiple requests. You can make use of the InnerHandler property of the ClearanceHandler, set this to be an HttpClientHandler which you can define to store cookies, and then set up the HttpClient to not dispose the handler. Something like this should work:
var cookieContainer = new CookieContainer();
using (var cfHandler = new ClearanceHandler()) {
    cfHandler.InnerHandler = new HttpClientHandler() {
        UseCookies = true,
        CookieContainer = cookieContainer
    };
    using (var client = new HttpClient(cfHandler, false)) {
        // do stuff here..
    }
}

Sorry, but I didn't get the code. Care to explain a little?
I wanted to connect to a site and grab all the cookies that the website makes for this particular connection and then pass these cookies to another instance of the client to use those cookies and connect to that website. How should I approach this in c#?
I've been writing in Python and it being Python, it was pretty easy. This is still confusing for me.

Here is another example:
// Shared CookieContainer, that will contain all cookies
var cookies = new CookieContainer();

// First client instance
var client1 = new HttpClient(new ClearanceHandler(new HttpClientHandler
{
    UseCookies = true,
    CookieContainer = cookies // setting the shared CookieContainer
}));

client1.GetStringAsync("http://target.site");

// Second client instance
var client2 = new HttpClient(new ClearanceHandler(new HttpClientHandler
{
    UseCookies = true,
    CookieContainer = cookies // setting the shared CookieContainer
}));

client2.GetStringAsync("http://target.site");

Thanks :+1:


Search results no longer update if you put in a new navbar search while already on the search results page

Seems to be fixed in the interim.


glog static lib on_test link error with  -- undefined reference to symbol 'pthread_rwlock_destroy@@GLIBC_2.2.5'

Xmake Version
2.7.7
Operating System Version and Architecture
WSL Ubuntu20.04
Describe Bug
after package glog build down as static library, it will test on:
on_test(function (package)
        assert(package:has_cxxfuncs("google::InitGoogleLogging(\"glog\")", {includes = "glog/logging.h"}))
    end)

and get link error for like this:
libglog.a(logging.cc.o): undefined reference to symbol 'pthread_rwlock_destroy@@GLIBC_2.2.5'
/usr/bin/ld: /lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO missing from command line

this lead package build failed.
actually test program need add link with -lpthread on my platform
Expected Behavior
package build succeed
Project Configuration
No response
Additional Information and Error Logs
No response

try it again.
xrepo update-repo
xmake remove --all glogs
xmake f -c
xmake


testing preview

This pull request is being automatically deployed to Netlify.
✅ Preview:

This pull request is being automatically deployed to Netlify.
✅ Preview:

This pull request is being automatically deployed to Netlify.
✅ Preview:

This pull request is being automatically deployed to Netlify.
✅ Preview:

This pull request is being automatically deployed to Netlify.
✅ Preview:

This pull request is being automatically deployed to Netlify.
✅ Preview:

Possible bug on preview URL

🎉 Published on https://preview.nibmcs.org as production
🚀 Deployed on https://6519de4b58a2270a05a472a9--stirring-maamoul-21e9ba.netlify.app


Fix empty label checkbox

What is the context of this PR?
We now enforce validation of non empty string values as a result of this  validator PR. As we no longer accept empty label values, I have updated the logic for checkbox question pages so that we display an empty label if there is only one answer option.
How to review
Use test_checkbox.json to check the changes.
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

 Review the use of empty string values in schemas (S)


Update rate limited key and update description

Fixes #2
It appears that the key might not be working any more, so I just created a new rate limited key. I also added a config description to let the users know they should create a new one for themselves.

gifs => GIFs


Should The Constant Version Be Bumped to 8?

Now that v8 is released, shouldn't this constant be also updated to ensure that generated code and library code are compatible?
Thanks!

No, it should not be updated because the twirp runtime library was not updated; v7 and v8 are the same. The major version release is for the generator. See the new doc we added with a version compatibility matrix: https://twitchtv.github.io/twirp/docs/version_matrix.html
But, to your point, we should probably update the comment on that constant. Thanks for reporting!

ah, love that matrix. thanks!


Sign in with google is broken

Visit https://usevolition.com/users/new
Click on 'Sign in with Google'

Ah, the reason for this is that Google sign in is only mapped to www.usevolition.com and not usevolition.com. I'll go make sure both urls are supported.

It should be working now. Thanks for pointing this out @rohitpaulk


pkg: propagate units via files

This changes the propagation logic for packaged systemd units, by copying
runtime units instead of symlinking them.
Reference: https://github.com/coreos/bugs/issues/2079

/cc @squeed @euank @dm0-

As an FYI, @lucab, we would like to include this fix in our release Wednesday, so if you want to go ahead and tag a patch release too that would be appreciated!

Changes look good to me.

@euank https://github.com/coreos/torcx/releases/tag/v0.1.0


A preference for the number of threads used by local SF

Threads and Hash implemented as preferences in v2.3.130


Add GxE column to studies download

All v2 and v3 studies downloads should have an additional column indicating GxE yes or no.
Background info: GxE status is entered in the studies tab of the submission template.

The column header definitions will need updating @ljwh2

@ala-ebi  I can only see 5 studies (from 1 publication) with GxE = yes. That doesn't seem right. Is the data up to date?

ugh sorry, I'm commenting before reading all the information - I see this was intentional, so this looks good for the current test!

should be fixed in next DR


PYT-1807 Bump pyyaml dependency to latest

Bumped pyyaml to the latest released version.

Done, I placed a todo in the code as well.
https://contrast.atlassian.net/browse/PYT-1971


Custom Inflector Rules not respected

I've encountered (in parallel only) my custom inflector rules not being respected. I am following this pattern: https://guides.emberjs.com/v2.13.0/models/customizing-adapters/#toc_pluralization-customization
I have a model 'bars' that is uncountable that is referenced through a hasMany on 'foo'. When running the model and serializer tests for 'foo' the test fails saying:
No model was found for for 'bar'
The tests both specify needs: [ 'model:bars']
These tests do not fail when running without parallelization.
I am on:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Do the failing tests run in isolation, i.e. when you run just that single test? If not, it might be that the failing tests need a dependency that happens to be supplied by another test file. When the tests run in parallel, if the failing and "supplier" test are run in different partitions, the dependency is no longer supplied.

Can you provide a reproduction of your issue? In general, I highly doubt that this addon is the root cause here. All Ember Exam does during tests is change which test modules get required by the TestLoader.
The route @YoranBrondsema mentions is also worth investigating.

@YoranBrondsema spot on. It appears my Acceptance tests were the only way the import of my custom-inflector-rules.js was happening because I was doing it in app.js
I just needed to import my rules in test-helper.js
Maybe the guide @ https://guides.emberjs.com/v2.13.0/models/customizing-adapters/#toc_pluralization-customization should mention this?

@scottkidder might be worth opening an issue on the guides repo for that: https://github.com/emberjs/guides


Custom script (Mods for WAU)

Proposed Changes
Mods for WAU allows you to craft a script to do whatever you like via _WAU-mods.ps1 in the mods folder.
This script executes if the network is active/any version of Winget is installed/WAU is running as SYSTEM.
If ExitCode is 1 from _WAU-mods.ps1 then Re-run WAU.
Related Issues
#377

An example of a crafted Mod (_WAU-mods.ps1 in the mods folder) to accomplish what I want:
#Mods for WAU if Network is active/any Winget is installed/running as SYSTEM
#Exit 1 to Re-run WAU from this script!

#Function to get the latest WAU available version on Github
Function Get-WingetAvailableVersion {

	#Get latest winget info
	$Wingeturl = 'https://api.github.com/repos/microsoft/winget-cli/releases/latest'

    try {

        #Return version
        return ((Invoke-WebRequest $Wingeturl -UseBasicParsing | ConvertFrom-Json)[0].tag_name).Replace("v", "")

    }
    catch {

        return $false

    }

}

#Function to get the installed winget version
Function Get-InstalledWingetVersion {

    #Get WinGet Path (if admin context)
    # Includes Workaround for ARM64 (removed X64 and replaces it with a wildcard)
    $ResolveWingetPath = Resolve-Path "$env:ProgramFiles\WindowsApps\Microsoft.DesktopAppInstaller_*_*__8wekyb3d8bbwe" | Sort-Object { [version]($_.Path -replace '^[^\d]+_((\d+\.)*\d+)_.*', '$1') }

    if ($ResolveWingetPath) {
        #If multiple version, pick last one
        $WingetPath = $ResolveWingetPath[-1].Path
    }

    #Get Winget Location in User context
    $WingetCmd = Get-Command winget.exe -ErrorAction SilentlyContinue
    if ($WingetCmd) {
        $Script:Winget = $WingetCmd.Source
    }
    #Get Winget Location in System context
    elseif (Test-Path "$WingetPath\winget.exe") {
        $Script:Winget = "$WingetPath\winget.exe"
    }
    else {
        Write-ToLog "Winget not installed or detected !" "Red"
        return $false
    }

    #Set Winget installed version
    $WingetVer = & $Winget --version

    return $WingetVer.Replace("v", "")

}

#Function to download and update winget
Function Update-Winget ($LatestVersion) {

    #Download WinGet MSIXBundle
    Write-ToLog "Downloading Winget MSIXBundle for App Installer..."
    $WinGetURL = "https://github.com/microsoft/winget-cli/releases/download/v$LatestVersion/Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle"
    $WebClient = New-Object System.Net.WebClient
    $WebClient.DownloadFile($WinGetURL, "$WorkingDir\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle")

    #Install WinGet MSIXBundle
    try {
        Write-ToLog "Installing Winget MSIXBundle for App Installer..."
        Add-AppxProvisionedPackage -Online -PackagePath "$WorkingDir\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle" -SkipLicense | Out-Null
        Write-ToLog "Installed Winget MSIXBundle for App Installer"  "Green"
    }
    catch {
        Write-ToLog "Failed to intall Winget MSIXBundle for App Installer..."  "Red"
    }

    #Remove WinGet MSIXBundle
    Remove-Item -Path "$WorkingDir\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle" -Force -ErrorAction Continue

}

$WingetAvailableVersion = Get-WingetAvailableVersion
$InstalledWingetVersion = Get-InstalledWingetVersion

If (!($WingetAvailableVersion -match "-pre") -and ($WingetAvailableVersion -gt $InstalledWingetVersion)) {

    Write-ToLog "Winget is not up to date: v$InstalledWingetVersion (v$WingetAvailableVersion is available)" "Red"
    Write-ToLog "Forcing a full upgrade of all Store Apps (this can take a minute)..." "Yellow"
    $namespaceName = "root\cimv2\mdm\dmmap"
    $className = "MDM_EnterpriseModernAppManagement_AppManagement01"
    $wmiObj = Get-WmiObject -Namespace $namespaceName -Class $className
    $result = $wmiObj.UpdateScanMethod()
    Start-Sleep 15
    $InstalledWingetVersion = Get-InstalledWingetVersion
    if ($WingetAvailableVersion -gt $InstalledWingetVersion) {
        Write-ToLog "Winget is still not up to date!" "Red"
        Write-ToLog "Forcing a download and upgrade to the latest Winget: v$WingetAvailableVersion" "Yellow"
        Update-Winget $WingetAvailableVersion
    }
    #Exit and Re-run WAU
    Exit 1

}

Write-ToLog "...nothing to change." "Green"
Exit 0


Mac Error

#![feature] may not be used on the stable release channel
--> /Users/jacob/.cargo/registry/src/github.com-1ecc6299db9ec823/rifgen-0.1.51/src/lib.rs:1:12
|
1 | #![feature(drain_filter)]
|            ^^^^^^^^^^^^
For more information about this error, try rustc --explain E0554.
error: could not compile rifgen due to previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile rifgen due to previous error

Hii there
You need to use nightly to compile the create
It seems you currently have the stable in use

Thanks! I installed nightly, and it built it smoothly!


[Testing Confirmation] Confirm current testing requirements

As part of the discussion around implementing an organization-wide testing policy, I am visiting each repo to see what tests they currently perform. I am conducting this work on GitHub so that it is easy to reference.
Looking at the Dashboards Notifications repository, it appears there is

Repository
Unit Tests
Integration Tests
Backwards Compatibility Tests
Additional Tests
Link

Dashboards Notifications
- [ ]
- [x]
- [ ]
Lint Checker, Documentation Auto-cut
https://github.com/opensearch-project/dashboards-notifications/issues/17

I don't see any requirements for code coverage in the testing documentation. If there are any specific requirements could you respond to this issue to let me know?
If there are any tests I missed or anything you think all repositories in OpenSearch should have for testing please respond to this issue with details.

I believe we have unit tests as well for this repo? For example:
https://github.com/opensearch-project/dashboards-notifications/tree/main/public/pages/Emails/__tests__


Button missing on all paints.

Correction its shows on sell orders but not on the bo section.

Looks like they were being ignored due to the paint on them, its fixed in the latest version.
Thanks for reporting!


Step 6 malformed content

Parts c - f are enclosed in code block.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 85cbe739-d436-c414-8ad0-1197ff2af011
Version Independent ID: b0d675ef-1efd-eec6-cf82-a39b07472b98
Content: Tutorial: Azure Active Directory single sign-on (SSO) integration with Jamf Pro
Content Source: articles/active-directory/saas-apps/jamfprosamlconnector-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@MarcLaf Thanks for your feedback! We will investigate and update as appropriate.

@chetansriv Please fix the article.

@MarcLaf We have updated the article, please review
#please-close


Add Remix/ESBuild support by checking the _debugOwner._debugSource

As Remix/ESBuild _debugSource filepaths are relative I had to also add GaitanK's code in order to make path absolute in my Remix app.
ESBuild has added _debugSource for a long time now https://github.com/evanw/esbuild/issues/2318 but looks like at least in React 18 we need to read it from somewhere else.
@ericclemmons, happy to have your feedback on this.

Will remix support be accepted? PR is already half a year old, are there any problems with this?

Will remix support be accepted? PR is already half a year old, are there any problems with this?
Also in the latest remix version (2.1.0) I get:
/node_modules/cliui/build/index.cjs:291
const stringWidth = require('string-width');
                    ^

Error [ERR_REQUIRE_ESM]: require() of ES Module /node_modules/string-width/index.js from /node_modules/cliui/build/index.cjs not supported.
Instead change the require of index.js in /node_modules/cliui/build/index.cjs to a dynamic import() which is available in all CommonJS modules.

oops, I added click-to-react-component to serverDependenciesToBundle in remix.config.js and everything worked.


[1.0][rc][BE]update 4 POM GET templates

add 2 fields in response template:
GET add uni
GET delete uni
GET add eline
GET delete eline
@{{productOrderItem[0].stateChange[*].state}}
description: state in state change history
required: No
Extended Property: No
state value mapping is required
@{{productOrderItem[0].stateChange[*].changeDate}}
description: change date in state change history
required: No
Extended Property: No

pass


Fix #17

https://github.com/pkmnct/robinhood-mint-sync-chrome/issues/17#issuecomment-761906397
Currently if the user is in a "Zero State" (They have 0 properties on the account) the Add Property Button can not be clicked.
This adds some functionality to waitForElement to check for fail states, and allows a failure callback.
Also fixes some buttons being incorrectly clicked on create. (prefers to now use the element returned from waitForElement, and filters down a bit more)
Adds some more debug logs to the various steps.

@superpowered I made a new issue to track this: #31. I have some additional bug fixes in #24 that I'd like to release at the same time, so I'm going to update your PR to target that branch.

@superpowered I made a new issue to track this: #31. I have some additional bug fixes in #24 that I'd like to release at the same time, so I'm going to update your PR to target that branch.

@superpowered I've fixed the merge issues and done some small cleanup, but I'll do a more in-depth review soon.

@superpowered I've fixed the merge issues and done some small cleanup, but I'll do a more in-depth review soon.


Project status

Project status.
Description
Hey,
Is this package still maintained ?
Are the features mentioned in the project tab still under work, since the last activity is from December 2018 ?
@akazorg

Hello @walidbagh!
I've been quite busy, but the project tab / roadmap are still up to date.
On the next weeks I plan to commit some work.
Thanks

@akazorg hey,
Hope you are doing well...
I just wanted to ask if there's any chance on getting this package running again.
I really like the effort put into this, it's very promising package that solves a very complex problem, it's very well coded and have an amazing road map and planned features.
It hurts me that it's kind of abandoned :/

@akazorg hey,
Hope you are doing well...
I just wanted to ask if there's any chance on getting this package running again.
I really like the effort put into this, it's very promising package that solves a very complex problem, it's very well coded and have an amazing road map and planned features.
It hurts me that it's kind of abandoned :/

Hey @walidbagh , it's been a long journey with my life and job, but I do plan to commit some work on this, at least make it compatible with the latest versions of Laravel.
Thanks for your message reminding about 💪🏼

Hey @walidbagh , it's been a long journey with my life and job, but I do plan to commit some work on this, at least make it compatible with the latest versions of Laravel.
Thanks for your message reminding about 💪🏼


docker scan does not detect dependencies included in a fat jar

Using docker scan (3.4.1) on the image datadog/agent:6.21.1-jmx does not detect the dependency log4j 2.12 included in jmxfetch.jar
scan results:
datadog-jmx_scan.log
contents of unzipped jar:
jmxfetch_jar_contents.log
jmxfetch pom depending on log4j 2.12:
jmxfetch_pom_xml.log

This is a wrong repo for this issue. This repo is dedicated to Docker registry implementation donated to CNCF.


Two set-cookie, one overwriting the other

Package version
4.1.1
Node.js and npm version
Node: v16.13.2, npm: 8.3.2, yarn: 1.22.15
Sample Code (to reproduce the issue)
### Controller code

public async Redirect({ ally } : HttpContextContract) {
  return ally.use('github').redirect()
}

public async callback({ ally, auth, response } : HttpContextContract) {
  const gith = ally.use('github')

  if (gith.accessDenied()) {
    return 'Access was denied'
  }

  /**
   * Unable to verify the CSRF state
   */
  if (gith.stateMisMatch()) {
    return 'Request expired. Retry again'
  }

 if (gith.hasError()) {
   return suap.getError()
 }
 //continues...
}

When redirecting, Ally sends two set-cookies, one of which is encrypted (as expected) and the second one without any encryption. Debugging the code, I realized that the encrypted set-cookie stores the correct state and the decrypted one stores a second state completely different from the first.
Below are the HTTP headers, the state passed by the URL is OKAb_ICu0VGAzaHA6H39JGla_K-XYF55. I checked this state, it's the same one that arrives at the Oauth2Driver.persistState method.
set-cookie: gh_oauth_state=eyJtZXNzYWdlIjoiIn0; Max-Age=-1; Path=/; Expires=Thu, 01 Jan 1970 00:00:00 GMT; HttpOnly
set-cookie: gh_oauth_state=e%3ADN_HCjMSzCNnSlB_NSzEMRTX15GL8Rn8mAqD3ktLHkmFkDJYnh6xHhzgI3oqREznyDYuhQJZm3HyHjYZSK0eWHGp5WmQIbDKIplBYmAJyas.akJWMTVYYmxtU2FjT0tmRA.d8dUoYeyNmJir7CgpvusTrQQeEE0t_IPjQEr7l9UR28; Max-Age=7200; Path=/; HttpOnly

On return to the callback, the encrypted cookie no longer exists, it has been overwritten by the decrypted cookie, causing an error 'Request expired. Retry again'.
//config/app.ts
export const http: ServerConfig = {
//...
  cookie: {
    domain: '',
    path: '/',
    maxAge: '2h',
    httpOnly: true,
    secure: false,
    sameSite: false,
  },
//...
}

//config/session.ts
const sessionConfig: SessionConfig = {
//...
  cookie: {
    path: '/',
    httpOnly: true,
    sameSite: false,
  },
//...
}

The application is configured to use the AdonisJS web version, using sessions to keep the user authenticated.

what was the solution?


Begin working on basic single-address wallet functionality for paying tx fees

Closing as this is now very outdated.


Hide status bar

Please support for hiding status bar

I've added a showsStatusBar property to NYAlertViewController, and released a new version through CocoaPods. If the value of showsStatusBar is set to NO, the view controller will indicate that it prefers the status bar to be hidden.

Nice, thank you !


Remove references to legacy TFMs

Summary
Legacy TFMs refer to binaries produced by pre-released versions of .NET Core.  These versions are no longer supported,  Remove related docs from Update third-party-deps.md

@cartermp FYI


MM-17550 Added support for search term in get marketplace plugins

Summary

Added search param for getMarketplacePlugins api endpoint.
Added missing test for failure case of getMarketplacePlugins

Ticket Link
MM-17550
Related PR

Webapp PR

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit tests passed
[x] Ran make flow to ensure type checking passed
[x] Added or updated unit tests (required for all new features)
[x] All new/modified APIs include changes to the JavaScript driver

@prapti Do you want to do QA for this PR pre or post merge?

Merging - this would be tested in the feature branch as discussed with @prapti


How to get broker and consumer metadata outside the context

How can I access all metadata about broker, topics and consumer listener details. Topics are created and consumers are listening from multiple applications( multiple docker apps).
I want to stop, start, status of the every consumer in the consumer group across the organization. So I am writing one app that can display all topics and query all consumers per topic and control the status from UI.
I tried with KafkaListenerEndpointRegistry, but this is giving the consumer details within the context of the app.
org.apache.kafka.clients.admin.AdminClinet is not giving me access to individual consumer in the consumer group.
Is there any other solution to get these datails?

GitHub issues are not for asking questions; they are for reporting bugs and asking for new features.
Furthermore, this question has nothing to do with Spring; you should ask the wider Kafka community, either on Stack Overflow, or on one of their mailing lists. https://kafka.apache.org/contact

You might also want to take a look at Kafdrop: https://github.com/obsidiandynamics/kafdrop


[WIP] Revert centralite battery map, add new 3.1v map

To open discussion...
Reverts centralite battery map to last know working map. Uses 2.8-1.5v battery logic for centralite/smartthings.
Incorporates logic from: Smartthings Zigbee Button for #176.
Reverts: 6cba0ff
Fixes: #199
Potential fix: #176

IMO we just should have a linear volts to % function and each manufacturer/model just need to define the min/Max volts.

@Adminiuga i started the logic found in st for battery logic. #205 But, i would imagine there was a reason ST used the map for some devices... possibly the way they report voltage? I am not stuck on using a map, i honestly just wanted something to get my battery values back as the previous commit made like the bottom 50% of my batteries None.
Both of these PRs are mostly about opening discussion and us getting to a solid fix.

IMO we just should have a linear volts to % function and each manufacturer/model just need to define the min/Max volts.

I like this idea the more that I think about it.

If I can get some ideas how to pass values from the quirks to init I'll get it done.

I just would define a child class overriding parent class attributes for
min/max
On Sat, Nov 30, 2019, 22:27 roblandry<EMAIL_ADDRESS>wrote:

If I can get some ideas how to pass values from the quirks to init I'll
get it done.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dmulcahey/zha-device-handlers/pull/204?email_source=notifications&email_token=ABMOM4DPSHVM5QHWLRKNPLDQWMVIPA5CNFSM4JTGYWHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFQ2NMI#issuecomment-560047793,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMOM4AT66M5EFGADUJRQILQWMVIPANCNFSM4JTGYWHA
.

Closing in favor of #208


About reproduing experiment results

Hi Bahare,
I have read your papers of HypE and ReAlE, which are quite valuable to me, and thanks for your open source codes.
However, similar to Finnhh's issue in https://github.com/baharefatemi/ReAlE/issues/5,
I have also tried running the provided codes on JF17K with lr=0.2/0.08/0.1/0.05, emb_dim=200, hidden_dropout=input_dropout=0.0, nr=10, w=2, but the model achieves MRR of 0.23 after 400 epochs.
I am wondering if you could provide best hyper-parameters for ReAlE on JF17K, FB-AUTO and M-FB15K.
Besides, could you give some suggestions on hyper-parameter settings for ReAlE? I am quite curious why ReAlE is heavily affected by hyper-parameter setting (like from 0.2 to 0.5 on JF17K)

Thanks for your timely reply.
Unfortunately, I tried the provided hyper-parameters on JF17, which achieves MRR of 0.248 after 1000 epoch training. I am not sure if there is some details I missed. I may try this again after you provide more details about settings on all datasets.
Anyway, thanks for your reply. Hope you can provide details as soon as possible.
BTW, in paper the nr is said to be 10, which may be a typo (100 here).

You may want to pull again as I have a new commit with a slight modification. I will provide the complete set of hyperparameters in about 10 days.
The nr is set to 10 for the results in the arxiv version of the paper. Furthur tuning (e.g., nr = 100) gives much better results. The setup I mentioned for JF17K gives better results compared to the results in the paper.

Thanks!


Add unique ID for fellow data

Currently there is no unique ID field in the fellow data. This makes referring to specific fellows difficult in code. It will be good practice to have an ID field for our data.

I am adding this in my next PR.


Use --force-with-lease instead of --force after rebasing

Using --force in git push can be destructive as it does not take into account the state of the remote. With --force-with-lease the push will fail if the remote is in a unexpected state. It is better to exit early during the push that to carry on and cause trouble on the remote.

Using --force-with-lease is only part of the solution though, we should then handle the case where the push fails. In this case, I suppose the appropriate response should be to treat the PR as modified, which should clear the approval status.

Using --force-with-lease is only part of the solution though, we should then handle the case where the push fails

Agreed, but I do think we should split the two into separate pull requests. This is a almost trivial which provides more safety with regards to the remote, a quick win. The other requires a bit more work and makes the bot itself more robust. Note that this PR does not close https://github.com/channable/hoff/issues/63

The window where this can make a difference is small though, because we already abort when we receive a push webhook. So only when you already approved a PR, Hoff tested it, and CI just passed, if you force-push at that point, and webhook delivery is delayed, Hoff may overwrite your push. But that’s a race anyway, and if Hoff wins the race, it will merge the PR before your push gets in, regardless of whether we force push with lease or not.
So there is this small window of time where currently Hoff would unconditionally conclude the merge, and if we change it to --force-with-lease, it would either conclude the merge, or fail silently, depending on who won the race. I don’t think that’s an improvement.

@ruuda I did some work on this trying to ensure we post comments when a push failed, had some trouble with the test failing and traced it back to the --force-with-lease change. It seems that with lease we get [rejected]  (stale info) while this is not the case with --force. This was behaviour I did not anticipate so I reverted the initial change again.
While I was able to add tests for the new parsing function I did not add tests for the comment on push fail yet. This is still a TODO.

The actual output of this hook check is send to std_err and can differ per remote hosting service (github / gitlab). Maybe we want to post the entire output in case of a push failure?

That makes sense, it sounds more useful to capture stderr than stdout then, indeed.


Install on RHEL 7.3

luaposix 33.4.0 (or a number of other versions) would not install via Luarocks using Lua 5.3.4 and Luarocks 2.4.2 on a system running RHEL 7.3.  The issue is an incompatibility with gcc versions that reserve the directory name "specs" for use by the compiler.  Here is my work around for manual install, which could be easily updated in the code.
Download a luaposix tar file from github
untar it
module load automake
mv specs yaml_specs
export LUA_INCLUDE=-I/opt/asn/apps/lua_5.3.4/include
./configure --prefix=/opt/asn/apps/lua_5.3.4
edit Makefile to change /specs/ to /yaml_specs/
make >&make.log1
make test
make install

This looks very much like a misconfigured gcc install to me.  Having gcc look for a specs file in the current directory is almost as much of a security problem as having '.' in your PATH - a malicious person could easily put something in repository you are going to check out, and then you end up running it accidentally, with permissions to access all your files.  Imagine that I left an actual gcc specs file in the top of the luaposix tree that injected an additional library into your link line that you then installed into /usr/local as root...
I don't plan to rename the specs directory in all my Lua projects, but especially not if it helps a few people find a security issue with their installation that needs fixing.


Link to source, not reddit thread

Hey,
Really grateful that you included my writeup! Thanks! Could you please point to the source directly? That way your users will get the up to date version (I keep adding new examples).

Of course! Thank you Michal!


Support SystemJS module output.

I do realize that the SystemJS loader can be used with AMD and CommonJS modules. Is there any interest in outputting directly to the system module format?

+1. would like to see System loader implemented

I've seen in the contributing guidelines that features need to be marked as "approved" before being accepted. Just out of boredom I did fork and begin implementing SystemJS module output. You can check it out at https://github.com/mikehaas763/TypeScript/tree/systemjs
Please do leave me comments and suggestions on it.
There are several similarities to how AMD modules are created so I'm thinking I should find an abstraction for those similarities and use it from both module types.

The actual function that emits the module format is mostly just a copy of the amd one at this point. I'm currently using https://github.com/ModuleLoader/es6-module-loader/wiki/System.register-Explained as a specification of sort for how I need to actually create the module format.

@mikehaas763 We are currently considering adding UMD (#2605) module support. so would be looking into systemjs as well.
@vladima has a change along the same lines as yours. it would be great if you can collaborate on getting systemjs PR ready.

@vladima what change is it that you're working on?
@mhegazy It'd be nice if the current UMD spec had support for system modules!

In my branch https://github.com/Microsoft/TypeScript/tree/systemRegister I've added initial support for system emit, hoisting of variable\function declarations. Pending work: rewriting exports, adding tests

@mikehaas763 you can send PRs against @vladima's branch; i think this would be a good way to collaborate on this. we need to discuss the proposal in the language design meeting (which we usually have weekly). it would be great if we have a PR ready as well.

+1

Looks like vladima has submitted his PR for this. So System.register modules should be coming soon! :smile:

here is the PR: https://github.com/Microsoft/TypeScript/pull/2840

Is this the only way to handle circular references in TypeScript at the moment? I understand that SystemJS supports circular references, but at the moment I often get errors in the class code if the base class comes from another module involved in a circular reference.
At the moment I'm using SystemJS and TypeScript together by using the CommonJS module output format.
Hopefully we get to see this in TS1.5 :)

@jamiewinder with the new ES6 module syntax supported by TypeScript 1.5 you can get most of your circular references issues done.
e.g.
import { two } from "./module2";

export function one(counter: number) {
    two(counter);
    console.log(`in one ${counter}.`);
}

import { one } from "./module1";

export function two(counter: number) {
    if (counter) {
        one(--counter);
    }
    console.log(`in two ${counter}.`);
}

two(3);

running

tsc --m commonjs module2.ts

and

node module2.js

results in:
in two 0.
in one 0.
in two 0.
in one 1.
in two 1.
in one 2.
in two 2.

The reason is these module aliases will be rewrite by the TypeScript compiler, so my module1.js looks like:
var module2_1 = require("./module2");
function one(counter) {
    module2_1.two(counter);
    console.log("in one " + counter + ".");
}
exports.one = one;

where all references to two is rewritten as module2_1.two.
The cases where you need systemJs support is cyclical references in the main module body (i.e. not wrapped in function and classes) and in practice these are really limited scenarios.

I'm using the TypeScript 1.5 Alpha with the ES6 module format. This is an example from an issue I raised on the SystemJS repo (though I'm not sure it's a SystemJS issue):
mod-a.ts
import { ClassB } from './mod-b';

export class ClassA
{
  constructor()
  {
  }

  public isB(): boolean
  {
    return this instanceof ClassB;
  }
}

mod-b.ts:
import { ClassA } from './mod-a';

export class ClassB extends ClassA
{
  constructor()
  {
    super();
  }
}

index.ts
import { ClassA } from './mod-a';
import { ClassB } from './mod-b';

var a = new ClassA();
var b = new ClassB();

window.alert(a.isB());
window.alert(b.isB());

The result is an error in the TypeScript __extends function (for ClassB) where the prototype is being set to that of the base constructor function. This because the base constructor wasn't imported (was undefined).
To clarify, this is ES6 modules, using TypeScript 1.5-alpha to output them as CommonJS format modules, to then be imported with SystemJS. So it's difficult to say where the issue is!

I think the issue here is order of imports.. so modifying your index.ts, to:
import { ClassB } from './mod-a';
import { ClassA } from './mod-b';

var a = new ClassA();
var b = new ClassB();

console.log(a.isB());
console.log(b.isB());

node index.js

i get:

false
true

And for completeness, systemjs module output should handle this correctly.

Covered by https://github.com/Microsoft/TypeScript/pull/2840

@mhegazy need help with compiler options, don't see System.register at top of generated .js files...
here's the gulp task (using @ivogabe gulp-typescript)
gulp.task('build-ts-system', function () {
  var tsResult =  gulp.src([
        './aurelia-dts/**/*.d.ts'
        ,'./animator-css/*.ts'
        ],
        {base: "."})// tsProject.src() // instead of gulp.src(...)
    .pipe(ts({
         typescript: require('typescript'),
         declarationFiles: false,
         noExternalResolve: true,
         target: "es6",
         module: "system",
         emitDecoratorMetadata: true
    }));

    return tsResult.js.pipe(gulp.dest('../dist/system'));
});

@cmichaelgraham
That works for me (except I use require('typescript').ModuleKind.System. Using "system" should work too though because I believe it automatically maps strings to the underlying ModuleKind type. How did you install your local typescript in to node_modules? Are you using the latest master branch?

@cmichaelgraham Support for systems was added in gulp-typescript v2.7.0. It now reads all the options from the ModuleKind & ScriptTarget enums at runtime, so all module kinds are now supported.

Is it possible to get one bundled JS file with 'es5' as target and 'system' as module output using the out parameter? The only thing we need are System.register statements creating named modules.

@Lenne231 currently --out does not support combining --module; in 1.6 this should be supported though.

+1. I'm also interested in this.
Just out of curiosity, are you guys waiting for the stable 1.5 to release it?

yes. we usually lock down on the release a few weeks before it is out publicly. so stay tuned.

Alright, thanks!

+1 for being able to generate a bundle containing n system modules, that'll be sweet!


Store CC backups under /var/lib/docker/aufs

/var/lib/docker/aufs is mounted as its own volume on our instances, so
moving things over to /var/lib/docker/.captain-comeback-backup means
we have to copy them, which is not ideal because:

It can fail if we run out of disk space or if we hit things that
shutil.move doesn't know how to handle (e.g. named pipes).
It can be slow if there's a lot of data to copy.
It's not transactional so we can't tell the difference between a
backup that's being moved and a backup that's been moved.

There's no fundamental reason to put these backups under
/var/lib/docker anyway, so let's just put them under
/var/lib/docker/aufs, and use a simple os.rename to move data over,
which is much less likely to fail, instant, and transactional.
Note that this will fail if /var/lib/docker/aufs/diff and
/var/lib/docker/aufs/captain-comeback-backup are on different devices,
but that's not something we need / want to support.

cc @fancyremarker - this will change a couple things regarding our storage structure and strategy when freeing up disk space:

/var/lib/docker/.captain-comeback-backup will always be safe to delete since we won't use it anymore.
Any directory under /var/lib/aufs/captain-comeback-backup is safe to delete (because moves will be transactional), but try to avoid deleting /var/lib/aufs/captain-comeback-backup itself (doing so wouldn't be a major issue, but if there are any containers being restarted then their backup may end up being left around in /var/lib/aufs/diff).

Note that I've opted not to move the container data directly to the backup directory so that we fail gracefully in the event that /var/lib/docker/aufs/diff is its own device, but as I noted in the commit above, that shouldn't be the case on our own infrastructure.

Thanks for the clear summary of the safety of possible disk freeing operations!


meta-dts-distro/recipes-dts/dts/dasharo-deploy: fix downloading Dell …

…BIOS Update packages

@miczyg1 Picked here on top of the latest changes and rebuilding locally: https://github.com/Dasharo/meta-dts/pull/34
@TomaszAIR Didn't we have CI for DTS? Couldn't we build PRs and upload artifacts?

@macpijan we have a weekly CI for checking cache, but we did not create one for pushed PR, I started an issue for this https://github.com/Dasharo/dasharo-issues/issues/476
@miczyg1 changes from here are already integrated in #36 so I am closing this one.

@TomaszAIR the problem is the change didn't work as expected. I must have messed up the bash syntax because wget doesn't detect the URL after the change.


Update Dockerfiles

Status
Ready/In Progress/In Hold (Reason for hold)
Related Content Pull Request
Related PR: link to the PR at demisto/content
Related Issues
Related: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/python-deb:<IP_ADDRESS>278
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/python-deb/tags
Get started by pulling the image:
docker pull devdemisto/python-deb:<IP_ADDRESS>278

Docker Metadata

Image Size: 58.99 MB

Image ID: sha256:1e2c1078e679f43d3f11dcbc44e68c497bd61e58c355eaa6000d66e705a857d0

Created: 2022-12-06T12:01:09.798719421Z

Arch: linux/amd64

Command: ["python2"]

Environment:

PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=C.UTF-8
PYTHONIOENCODING=UTF-8
GPG_KEY=C01E1CAD5EA2C4F0B8E3571504C367C218ADD4FF
PYTHON_VERSION=2.7.18
PYTHON_PIP_VERSION=20.3.4
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/831b5dd0bec03caf24aa6d736a28dc2ba80f91cc/public/2.7/get-pip.py
PYTHON_GET_PIP_SHA256=40ee07eac6674b8d60fce2bbabc148cf0e2f1408c167683f110fd608b8d6f416
DOCKER_IMAGE=devdemisto/python-deb:<IP_ADDRESS>278

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:10f15552e187a968920d41b59502607fbc911229
org.opencontainers.image.version:<IP_ADDRESS>278


cmd/compile: ppc64le broken by encourage inlining of functions with single-call bodies

https://go-review.googlesource.com/c/go/+/147361 broke ppc64le.
https://build.golang.org/log/cee992f2c28faffaa1c9526349f4923f9cb16c83
##### GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
--- FAIL: TestGdbPython (0.58s)
    runtime-gdb_test.go:66: gdb version 7.7
    runtime-gdb_test.go:213: gdb output: Loading Go Runtime support.
        Loaded  Script
        Yes     /tmp/workdir-host-linux-ppc64le-osu/go/src/runtime/runtime-gdb.py
        Breakpoint 1 at 0x92cac: file /tmp/go-build132537636/main.go, line 15.
        hi

        Breakpoint 1, main.main () at /tmp/go-build132537636/main.go:17
        17		gslice = slicevar
        BEGIN info goroutines
        * 1 running  syscall.Syscall
          2 runnable runtime.forcegchelper
          17 waiting  runtime.gopark
          18 runnable runtime.runfinq
        END
        BEGIN print mapvar
        $1 = map[string]string = {["abc"] = "def", ["ghi"] = "jkl"}
        END
        BEGIN print strvar
        $2 = "abc"
        END
        BEGIN info locals
        mapvar = map[string]string = {["abc"] = "def", ["ghi"] = "jkl"}
        strvar = "abc"
        slicevar =  []string
        END
        BEGIN goroutine 1 bt
        #0  main.main () at /tmp/go-build132537636/main.go:17
        END
        BEGIN goroutine 2 bt
        #0  runtime.forcegchelper () at /tmp/workdir-host-linux-ppc64le-osu/go/src/runtime/proc.go:242
        #1  0x0000000000092cac in fmt.Println (a=..., n=<optimized out>, err=...) at /tmp/workdir-host-linux-ppc64le-osu/go/src/fmt/print.go:275
        #2  main.main () at /tmp/go-build132537636/main.go:14
        Traceback (most recent call last):
          File "/tmp/workdir-host-linux-ppc64le-osu/go/src/runtime/runtime-gdb.py", line 536, in invoke
            gdb.parse_and_eval('$sp = $save_sp')
        gdb.error: Attempt to assign to an unmodifiable value.
        Error occurred in Python command: Attempt to assign to an unmodifiable value.
        END
        Breakpoint 2 at 0x92ce0: file /tmp/go-build132537636/main.go, line 18.
        runtime: newstack sp=0xc000032fc0 stack=[0xc000064000, 0xc000065000]
        	morebuf={pc:0x92cac sp:0xc000032fc0 lr:0x0}
        	sched={pc:0x38bb4 sp:0xc000032fc0 lr:0x92cac ctxt:0x0}
        runtime: gp=0xc000000180, goid=1, gp->status=0x2
         runtime: split stack overflow: 0xc000032fc0 < 0xc000064000
        fatal error: runtime: split stack overflow

        runtime stack:
        runtime.throw(0xd4b34, 0x1d)
        	/tmp/workdir-host-linux-ppc64le-osu/go/src/runtime/panic.go:608 +0x5c
        runtime.newstack()
        	/tmp/workdir-host-linux-ppc64le-osu/go/src/runtime/stack.go:995 +0x7a4
        runtime.morestack()
        	/tmp/workdir-host-linux-ppc64le-osu/go/src/runtime/asm_ppc64x.s:333 +0x60

        goroutine 1 [running]:
        runtime.forcegchelper()
        	/tmp/workdir-host-linux-ppc64le-osu/go/src/runtime/proc.go:242 +0x14 fp=0xc000032fc0 sp=0xc000032fc0 pc=0x38bb4
        runtime: unexpected return pc for main.main called from 0x0
        stack: frame={sp:0xc000032fc0, fp:0xc000033080} stack=[0xc000064000,0xc000065000)

        fmt.Println(...)
        	/tmp/workdir-host-linux-ppc64le-osu/go/src/fmt/print.go:275
        main.main()
        	/tmp/go-build132537636/main.go:14 +0x1ec fp=0xc000033080 sp=0xc000032fc0 pc=0x92cac
        [Inferior 1 (process 11715) exited with code 02]
        BEGIN goroutine 1 bt at the end
        No such goroutine:  1
        END

    runtime-gdb_test.go:286: goroutine 1 bt at the end failed: No such goroutine:  1
FAIL
FAIL	runtime	36.282s

Odd.
The backtrace for the background GC thread is all wrong:
BEGIN goroutine 2 bt
        #0  runtime.forcegchelper () at /tmp/workdir-host-linux-ppc64le-osu/go/src/runtime/proc.go:242
        #1  0x0000000000092cac in fmt.Println (a=..., n=<optimized out>, err=...) at /tmp/workdir-host-linux-ppc64le-osu/go/src/fmt/print.go:275
        #2  main.main () at /tmp/go-build132537636/main.go:14

The backtrace starts at a GC helper thread, then somehow jumps to the user's thread, at a nonsensical location.
Here's goroutine 2's stack trace from a correct run (on linux):
        BEGIN goroutine 2 bt
        #0  runtime.gopark (unlockf=<optimized out>, lock=0x752d20 <runtime.forcegc>, reason=16 '\020', traceEv=20 '\024', traceskip=1) at /usr/local/google/home/khr/sandbox/inl/src/runtime/proc.go:302
        #1  0x0000000000429766 in runtime.goparkunlock (lock=<optimized out>, reason=<optimized out>, traceEv=<optimized out>, traceskip=<optimized out>) at /usr/local/google/home/khr/sandbox/inl/src/runtime/proc.go:307
        #2  runtime.forcegchelper () at /usr/local/google/home/khr/sandbox/inl/src/runtime/proc.go:250
        #3  0x0000000000450671 in runtime.goexit () at /usr/local/google/home/khr/sandbox/inl/src/runtime/asm_amd64.s:1340
        #4  0x0000000000000000 in ?? ()
        END

The error isn't deterministic; sometimes it happens and sometimes it doesn't.
I think this issue is probably a bug in the underlying mid-stack inlining, not anything to do with my inlining change directly.
I will investigate further.
@davidlazar @aclements

I haven't been able to reproduce this error on any of our systems, using various distros.
Is there something different about the way this run or the builder system?
I tried the full all.bash or just by doing this:
go tool dist test runtime:cpu124

Our ppc64le builders run Debian jessie with kernel:
Linux go-le-1 3.16.0-4-powerpc64le #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) ppc64le GNU/Linux

Check gdb versions as well, that is likely to be part of the issue.

$ gdb --version
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1

Could we get a newer distro and kernel on the ppc64le builder. This is the second time we've seen failures in the builder that don't happen on other distros. Debian 8 seems pretty old.
I don't work with OSU much so I don't know who your contact is for this system or how to make this request.

Could we get a newer distro and kernel on the ppc64le builder.

Sorry, but that won't happen anytime soon. We have a backlog of builder work and this wouldn't be near the top of the priority list. I recommend just skipping GDB tests if the GDB or kernel is too old.
/cc @dmitshur

It would be good if we could upgrade at some point. It's not a certainty that's the problem in this case, just a guess since it seems to work right so many places.
I built the programs for main.go, the program being run by gdb when it fails, before and after the bad commit. One thing I saw that looks suspicious is that starting in the commit where it started failing, Fprintln is now inlined from Println, so main doesn't directly call Println anymore. And fmt.Println is what shows up in the backtrace in the output when it fails. So I'm wondering if that is significant? I don't know what has to happen to the dwarf or whatever information gdb has to look at to figure out the backtrace in the case where inlining happened to get it right, but maybe there is something that causes gdb to look at uninitalized data causing random behavior? I also see that Println and Fprintln have variable argument lists, not common.

I'm not sure what's happening on the ppc64le builder, but I can reproduce the exact same error output on any machine by doing this:
GOMAXPROCS=1 ./runtime.test -test.run=GdbPython$
I can also use gdb with the source for the program being run in the testcase and step through and see what's wrong. I don't think the problem is not related to the compiler doing something wrong but because the testcase is different and behaves differently. I can try this test with an older compiler and get the same failure.
The problem occurs if forcegchelper is at the top of the stack for one of the goroutines and the goroutine's pc is at the start of the function. At this point the value for sp has not been set yet for forcegchelper, and since this is the initial function for a goroutine I'm not sure what sp would be at that point.
// start forcegc helper goroutine
func init() {
        go forcegchelper()
}

So when we have this situation, and 'goroutine 2 bt' is invoked for a goroutine with this at the top of its stack, things go wrong after that, probably because the sp does not make sense at this point. If I break at the end and do goroutine 2 bt no errors occur.

To see the reason for the above change, here is a reference in the gdb documentation. https://sourceware.org/gdb/onlinedocs/gdb/Registers.html.
See the footnote where it is providing information on another way to set $sp.
This is a way of removing one word from the stack, on machines where stacks grow downward in memory (most machines, nowadays). This assumes that the innermost stack frame is selected; setting $sp is not allowed when other stack frames are selected.

This is still failing freebsd-arm-paulzhol builds.
Latest failure: https://build.golang.org/log/d9278491818714d74a9190557d6107f737d48612
Is it feasible to disable this test, as @bradfitz suggested earlier? Or is there something else that can be tried?

@katiehockman, done, in https://golang.org/cl/155932 and tracked in new bug #29508

@laboger, is this still a problem or can this be closed?

I haven't seen this problem in a while on ppc64x. I think it was left open due to similar issues on other platforms. I think it can be closed.

Thanks. Closing.


Update requirement link in update.md

Description of the change:
Added link of requirements

Required:

Git
RVM
Homebrew
npm
yarn
Gatsby

Reason for the change:
Ease for users to navidate
Link to original source:
https://github.com/sendgrid/docs/blob/develop/readme.md

Closes #4319

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

Hello @jindalAnuj,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

Hello @jindalAnuj,Thanks again for the PR!                                         We noticed that you have earned 1 out of the 5 points needed to receive glorious SendGrid Hacktoberfest swag.                                         Please take a moment to checkout this link to find more issues to get you past the required threshold.                                         Also, please be sure that you have officially registered here.                                         Thank you and Happy Hacktobering!                                         Team SendGrid DX

Hello @jindalAnuj,Thanks again for the PR!                                         You have earned 1 out of the 5 points needed to receive glorious SendGrid Hacktoberfest swag.                                         Please take a moment to checkout this link to find more issues to get you past the required threshold or to simply continue the celebration.                                         Also, please be sure you have officially registered with us here by November 1, 2018 to qualify.                                         If you have any questions you can email us at<EMAIL_ADDRESS>                                        Thank you and Happy Hacktobering!                                         Team SendGrid


Is the thinResNet34 with angular-prototypical the state-of-the-art neural network you know?

Thank you for this open source and your paper "In defence of metric learning for speaker recognition".
In this paper, your "proposed metric learning objective outperform state-of-the-art methods."
The best network in the paper is thin ResNet34 with angular-prototypical loss.
Is the best network you know?
Is there any update?
If my question is not rude, please teach me which network is the best you know...
Thank you.

This paper has better results than ours, but also using a much larger network.
We have some minor updates (e.g. change of input dimensions, etc.) that makes small improvement to performance -- we will release this soon.

Thank you so much~

Thank you for your answer,  but this paper you mentioned above(Jhu-HLTCOE System for the Voxsrc Speaker Recognition Challenge)  was 2nd ranked in VOXSRC 2019.
In Voxsrc2019, BUT system showed its superiority to Jhu-HLTCOE System, doesn't it?
BUT system was the winner of VOXSRC 2019.
I am confused with the State of the Art....please let me know....thank you...
BUT system:  https://arxiv.org/pdf/1910.12592.pdf

I know that there are several works that has lower EER than our baseline, but don't have an exhaustive list of them. For example, this paper claims an EER as low as 0.5% but we cannot validate the claim.

Thank you very much!!
the paper which claims to achieve EER 0.55% made me surprised!
Actually I cannot accept the claim even though the paper in on InterSpeech...but it was so impressive, thank you.


Add Popcorn Time 0.2.9

Adds Popcorn Time 0.2.9.
Official repo is here: https://github.com/popcorn-official/popcorn-app

I wish Github would allow adding some kind of popup/warning based on entered title which would prevent people from even sending the same issue again and again.

Perhaps we should add a “refused casks”1 section to CONTRIBUTING.md, right at the top. It would be populated only by Popcorn Time, at the moment, but it’d come in handy occasionally, like with FirefoxDevelopEdition (it’s available on caskroom/versions but was being submitted to the main repo repeatedly.

I think #7489 suggested a good idea for precluding this. This solution would in turn be a duplicate of #5779.


MM-35074: short circuit slash command hooks

Summary
When the Confluence plugin consumes a slash command for client-side processing (i.e. /confluence subscribe), it signals this by returning an empty object as per the required interface.
However, the webapp passes this empty object through all other registered slash command hooks. When the Confluence and Incident Collaboration plugins are installed (and Incident Collaboration "registers last"), Incident Collaboration receives this empty object and mistakenly initializes the undefined args parameter in testing whether it should process the slash command. The final result consumed by the webapp is now partially initialized, leading to a JavaScript exception and a create post component that won't process slash commands until it mounts afresh.
While we can address this in Incident Collaboration, it's unexpected that the webapp would notify plugins at all in this case, given there is literally no metadata on which to try to do anything meaningful. Short-circuit in this case, avoiding the original report altogether.
Ticket Link
Fixes: https://mattermost.atlassian.net/browse/MM-35074
Release Note
Short-circuit slash command hooks when a plugin consumes one for client-side processing.

This was a ... fascinating confluence of the three hats I'm wearing this week as SET Lead, Web Platform Lead, and Incident Collaboration Lead. I imagine it would have been hard to find had I not had the Incident Collaboration plugin installed by default :)

Filed a bug for the Incident Collaboration plugin: https://mattermost.atlassian.net/browse/MM-35096

cc @DHaussermann

@lieut-data can you please clarify the scope for this?

It's unclear to me what type of webapp regression testing may be needed here.
It seems possible to test this by installing both plugins and using them without an actual working confluence instance. This would make testing much easier. Is that correct?

@DHaussermann,

The scope should entail any kind of slash command interaction, with an emphasis on plugins that handle some slash commands on the frontend (vs. the default behaviour of routing to the backend). I think Jira would be an excellent additional test case.
Yes, you can reproduce without an actual working Confluence instance: that's exactly how I tested.


feat: Add 'About The App' section

Fixes #1882
Screenshot for the change:

Add OSS license section

What about F-Droid build

Change OSS Licenses to 3rd Party Libraries Used

What about F-Droid build

Updated, now 3rd Party Libraries Used will show only in the Play Store build.

Change OSS Licenses to 3rd Party Libraries Used

Done.

Huge duplication for not showing a single button

Updated.


add service pipelines-email

@svanharmelen I rebased on top of master, everything seems working fine

Cool, thanks @itscaro!