Add scaled water implementation

Description
This PR augments the existing RESTTopologyFactory to scale rest-water interactions by beta/beta_0 (previously was being scaled by sqrt(beta/beta_0).
To do:

[ ] Add tests (I have these in a notebook, but need to revise them based on JDC's recommendations)
[ ] Investigate/solve weird solvent artifact issue seen in barnase:barstar scaled water rest caches (but not in RBD:ACE2 caches)

Motivation and context

Resolves #???
How has this been tested?

Change log

Oh! I thought we wanted to keep intra-REST regions scaled by beta/beta0, but REST-environment sqrt(beta/beta0). Perhaps we want to add an optional argument about whether nearby water should be included in the REST region, in which case the scaling would be distance-dependent (go smoothly from beta/beta0 at r < r0 to sqrt(beta/beta0) at r > r0)?

I thought we wanted to keep intra-REST regions scaled by beta/beta0, but REST-environment sqrt(beta/beta0)

This is what the original REST2 paper describes, so there wouldn't be any need for the scaled water rest implementation if we were following these scaling rules, we could just use the RESTToplogyFactory.
To enhance water sampling, we decided to further scale the REST-water interactions (by beta/beta0), but not the water-water interactions (these are left unscaled). We don't actually want to include waters in the REST region, because if we didm, water-water interactions would be scaled by beta/beta0, which we worried may cause weird artifacts like waters flying away.

@zhang-ivy is this PR still something we want/need?

Closing this, since we didn't observe that this addressed our sampling problems


Use ID as repository name

I'm trying to implement a registry that will map the name of a repository to an ID and use that when persisting. The idea is decoupling names from repositories which could eventually allow renames (although there might be other blockers).
I have overridden the "vars.name" in the context which works for computing the right paths for the storage provider. However, the manifest store verifies the name. Why does the manifest care about the name of the repository? It seems entirely unnecessary.
I'm considering decorating the storage driver and making it translate paths using regular expressions but that feels brittle (and you might still pull a manifest that declares a different name).

@stevvooe, you have reviewed some of my pull requests. Can you please comment on this issue?

@tt The manifest name is verified to ensure that it is being placed in the correct repository. This is the current data model. The correct approach to allow some sort of "aliasing" would be to replace the manifest store that both looks up the aliases and removes the extra validation. At this time, you may be able to replace the validation function with a option when instantiating the manifest store.

Thank you. I implemented a SkipNameVerification function next to the SkipLayerVerification function already there.
The problem then becomes how to pass this option. I see that repository.Manifests(...) accept options but as I don't control the callers (the built-in handlers), I'm not sure how you suggest I pass that option down.
repository.Manifests(...) even ignores the options. I'm summoning @richardscothern who put a comment in that function in case he has suggestions for how to do this.
To recap: I'm trying to support renames. The first step towards this is never using the image name in the storage driver but rewriting to an ID that will never change.

@rsampio suggested I inject this using a repository middleware. That seems to work.

@tt : passing manifest options over the wire is not yet specified or implemented.  Do you need this given you are implementing this feature in the registry?
As to answer your question for calling the options, using repository middleware to return a manifest service configured to not verify the name should work.


Replaced all occurrences of 'Binder' with 'Google Colab'

Description
A simple documentation fix replacing Binder with Google Colab. I searched in the documentation and there were only 2 such occurrences I could find. I could not find any configuration files for Google Colab, if there is one or if any changes are required in this PR, please let me know. Thank you!
Fixes #1390
Type of change
Changed Docs ( CONTRIBUTING.md and docs/index.rst )

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[x] No style issues: $ flake8
[x] All tests pass: $ python run-tests.py --unit
[x] The documentation builds: $ cd docs and then $ make clean; make html

You can run all three at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

@all-contributors add @Saransh-cpp for documentation

@all-contributors add @Saransh-cpp for documentation


OpenCL: Time of feature collection as in- and output

looks good. please add test and we can merge it


added @stub directive

Added a new directive @stub, which takes a single parameter value, and will always return that value. This is useful if you don't want random repeated data, but rather just a simple stubbed response

Hi @tyllrb 👋
You can do the same with existing @examples directive, just provide a single value to it.


New Projects section of email

Layer
RDCC Project
Query

SELECT (the following attributes) From RDCC Project WHERE created_date BETWEEN  [today] AND [today-7]

**Note: **created_date stored as MST time zone
Included in email:
New Projects (section heading)
Project # ProjectID - project_abstract
     Sponsor: sponsor
     Comment Deadline: comment_deadline
     Counties: county

The layout in the existing email looks like:

I'm seeing creation dates in the future. Is that normal? Do we want to limit the number somehow?

I gathered the date range logic from the hibernate logic that was sent, but it doesn't look right now...like it wouldn't exclude any results.

not proper sql, but I changed the range in the initial comment. It is intended to only capture projects with created-date within the past 7 days of the email being sent.

there are over 2000 results for this query

2k+ within the past week?

The week query is good, but there was a recent bulk upload that caused a large sum of records to have a created_date within the last week, which is skewing the results. After November 5th, the query results will normalize.

"View Full Project" link removed b/c there is no longer a way to link directly to individual projects on the new RDCC dashboard.

Validated with client. Any changes to this email section will be tracked in separate issue(s).


Request: Best Audio Streaming Clients for Raspberry Pi using SWYH-RS on a Headless Linux System

I'd like to use my Raspberry Pi as a client/receiver for audio streamed by SWYH-RS. Could anyone recommend the most efficient clients available for a headless Linux setup?
Given that the Raspberry Pi is a low-power, single-board computer, ALSA is preferred due to its minimal CPU overhead and lower latency.
Background:
I previously used Scream Audio to stream low-latency audio to my Raspberry Pi, which worked amazingly well. However, the latest versions of Windows are no longer compatible with the virtual audio device required to stream via multicast, so I’m now exploring alternatives.
Any suggestions or recommendations are highly appreciated!

I use MoodeAudio on rpi with swyh-rs. It uses MPD with the upmpdcli plugin (which is now a part of mpd).
But I don't know if the "stock" rpi mpd release is compiled with the upnp plugin support, it's possible that  MoodeAudio uses its own mpd build with the appropriate options.
If you don't use the pi only for other things than playing music you could prepare an sd card with Moode to see if you like it. I do.


Update s3, sdk-core, sqs to 2.17.251

Updates

software.amazon.awssdk:s3
software.amazon.awssdk:sdk-core
software.amazon.awssdk:sqs

from 2.17.191 to 2.17.251.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #533.


fixed #954 Upload All visual Glitch Solved

Solved issue #954

merging, thanks @shivanshsoni

Happy to contribute :-)


ndarray of text does not display correctly in variable explorer

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[x] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[x] Reset preferences with spyder --reset
[x] Reinstalled the latest version of Anaconda
[x] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
Create an ndarray:
import numpy as np
mosaic = np.array([['a', 'b'],
                   ['c', 'd']])

What steps reproduce the problem?

Create ndarray of text values
Open in variable explorer
strings are empty

What is the expected output? What do you see instead?

There is an empty array, the text should display in it.

 I was able to reproduce this problem and we'll try to fix it in a future version.

I tried to bisect and I think this issue may be caused by PR #20473 by myself, so I will try to fix it.

I think I figured out what is going on: Spyder uses format(..., 's') to convert array elements to strings. Here, this returns something that looks like an str but it is actually a different type:
>>> import numpy as np
>>> mosaic = np.array([['a', 'b'],
...                    ['c', 'd']])
>>> format(mosaic[0,0], 's')
'a'
>>> isinstance(format(mosaic[0,0], 's'), str)
True
>>> type(format(mosaic[0,0], 's'))
<class 'numpy.str_'>

That seems to confuse the Qt widget that displays the array. PR should be arriving soon.

Just updated to 6.0.1 and it looks much better.
However it still says ndarray object of numpy module in the variable explorer (red) instead of:
np.array([[a, b],
          [c, d]])

Also I can double click into a text field for example the a and edit the text to abcde (shown in blue). When I click out of the field, it reverts to the original value. This means Save and Close (shown in green) cannot be used:

However it still says ndarray object of numpy module in the variable explorer (red)

Spyder 5 did the same, but I agree that we can do better. This is a separate issue so I opened a new one in order to stay organized: #22570.

Also I can double click into a text field for example the a and edit the text to abcde (shown in blue). When I click out of the field, it reverts to the original value.

This reflects how numpy works:
>>> import numpy as np
>>> arr = np.array([['a','b'],['c','d']])
>>> arr[0,0] = 'abcde'
>>> arr
array([['a', 'b'],
       ['c', 'd']], dtype='<U1')

The reason is that arr is an array of strings of length 1 and longer strings are (apparently) truncated. This is pretty confusing and it took me a while to figure it out. However, I don't know what we should do about it.


memory leak on flash-publish

Description
on SRS both versions 4 and 5 (including minor versions) I get a memory leak when I receive an RTMP stream using the method flash-publish.
Flash publish is identified from the headers:
SrsRtmpConnFMLEPublish = 0x0200
SrsRtmpConnFlashPublish = 0x0201

so it is whenever I receive 0x0201 that the server blows up and is no longer capable of receiving new streams as per the error logs

SRS Version: 5.0.166 (docker)

SRS Log:

The memory leak seems to be happening in
2023-07-11-flash-publish-srs-leak.txt

SRS Config:

listen              1935;
max_connections     1000;
daemon              off;
srs_log_tank        console;
srs_log_level       info; # default is trace
vhost __defaultVhost__ {
    http_hooks {
        enabled         on;
        on_publish      http://<IP_ADDRESS>:8085/api/v1/streams/publish; # delegates to ffmpeg
        on_unpublish    http://<IP_ADDRESS>:8085/api/v1/streams/unpublish;
    }
}

Replay
simply receive the stream as publish using above streaming header
Expect
The stream should be ingested OR rejected (because not yet implemented), but what happens instead is the memory leak and crash
analysis
My suspicion is the code block related to having AMF commands combined with flash-publish header:
    // process publish event.
    if (msg->header.is_amf0_command() || msg->header.is_amf3_command()) {
        SrsPacket* pkt = NULL;
        if ((err = rtmp->decode_message(msg, &pkt)) != srs_success) {
            return srs_error_wrap(err, "rtmp: decode message");
        }
        SrsAutoFree(SrsPacket, pkt);

        // for flash, any packet is republish.
        if (info->type == SrsRtmpConnFlashPublish) {
            // flash unpublish.
            // TODO: maybe need to support republish.
            srs_trace("flash flash publish finished.");
            return srs_error_new(ERROR_CONTROL_REPUBLISH, "rtmp: republish");
        }

        // for fmle, drop others except the fmle start packet.
        if (dynamic_cast<SrsFMLEStartPacket*>(pkt)) {
            SrsFMLEStartPacket* unpublish = dynamic_cast<SrsFMLEStartPacket*>(pkt);
            if ((err = rtmp->fmle_unpublish(info->res->stream_id, unpublish->transaction_id)) != srs_success) {
                return srs_error_wrap(err, "rtmp: republish");
            }
            return srs_error_new(ERROR_CONTROL_REPUBLISH, "rtmp: republish");
        }

        srs_trace("fmle ignore AMF0/AMF3 command message.");
        return err;
    }

Yeah, yes! SRS will firstly identify the connection type of the client by SrsRtmpServer::identify_client. When receiving the message, it determines whether the AMF commands are amf0/amf3 and decides whether to ignore the packet or wait for the client to republish. You can refer to the modification method here.(https://github.com/ossrs/srs/issues/958)
About this question we will discuss further.

Dup to https://github.com/ossrs/srs/issues/958#issuecomment-2041227158


Review placement of URL copy and badge copy to be above build log

This is a follow-on to #132. Let's revisit the placement of the build log on the page.
Use case

I've filled in the form information and I want to copy the URL link to share.
I push Launch since I'm unsure if the URL link will change if I do so.
After pushing launch the build log pops up pushing the the URL link and badge UI element to the bottom of the page.
I'm momentarily disoriented and then I must scroll down to find the URL link to copy

Recommendation
Let's consider changing the order of the UI element placement so the Build Log is at the bottom and the URL to share element and badge element do not jump around on the page.
@hzarea @ellisonbg Thoughts from a UI/UX standpoint? I think @betatim had a similar concern in #132.

I think it's a good idea, in general it's confusing to me when UI elements bounce around depending on user behavior

I think it's a good idea, in general it's confusing to me when UI elements bounce around depending on user behavior

I agree, I got confused as well but decided to postpone sending a pull-request changing this not to bikeshed infinitely on eveything,

FWIW @willingc I really love the approach you're taking here to discussing UI in the context of the user's perspective. I think it does a good job to avoid bikeshedding :-)

Sorry I missed this in the review of the initial design. I fully agree that
UI elements should be mostly spatially invariant (the same things in the
same places). There are two things to consider:

The progress bar - relevant to all users, so important, but if it goes
from hidden to shown as it does now, I would move it below the other
content to prevent the jumping
The build logs - only relevant to users who are getting their repo
binder ready - I would move to the bottom

On Mon, Dec 11, 2017 at 8:37 AM, Chris Holdgraf<EMAIL_ADDRESS>wrote:

FWIW @willingc https://github.com/willingc I really love the approach
you're taking here to discussing UI in the context of the user's
perspective. I think it does a good job to avoid bikeshedding :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jupyterhub/binderhub/issues/338#issuecomment-350779839,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABr0Dfny6itTxM87xqnapkV6thGiRp5ks5s_VpFgaJpZM4Q8pBa
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Thanks @Carreau and team :cake:

Yes!
On Wed, Dec 13, 2017 at 4:20 PM, Carol Willing<EMAIL_ADDRESS>wrote:

Thanks @Carreau https://github.com/carreau and team 🍰
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jupyterhub/binderhub/issues/338#issuecomment-351568238,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABr0Nt5OGGLEiKYITTG0qHqK33Yp5ujks5tAGnRgaJpZM4Q8pBa
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>


Support ECDSA

Well, this perhaps might surprise people given the package/project name, but this is feasible for AKV to support now.
A couple of notes:

This will not work in net462 or below. The ECParameters struct is something that netstandard2.0 unfortunately lies about. Even though netstandard2.0 says ECParameters exists (and thus should be in net461) it does not. This type is used the the key vault library, so there isn't much we can do about it, I think. You'll just get a type load error at runtime.

I was not able to run the MSI tests; I'm not set up to run those.

Tests will probably fail until you generate an ECDsa certificate and update the azure-creds.json file.
Steps to generate a self-signed ECDSA cert (requires recent version of OpenSSL):
# Generate a private key
openssl genpkey -algorithm ec -pkeyopt ec_paramgen_curve:prime256v1 -out ecdsa.key

# Generate a self-signed certificate
openssl req -x509 -key ecdsa.key -keyform pem -days 1095 -subj "/O=CI/CN=Self Signed Test Key" -out cert.pem

# Combine in to PFX
openssl pkcs12 -export -out cert.pfx -inkey ecdsa.key -in cert.pem

This needs a little more work, stand by...

Guess I'd need to rename the NuGet package 😈

Can we generate an EC cert using the portal? I could do that for RSA-HSM key types.

Can we generate an EC cert using the portal?

Doesn't look like it... at least not through the GUI. Didn't check powershell.

They at least have an option for key algorithm with only one choice :-).


ENYO-1958: Implemented vertical slider

This change alters the way that value is treated. Un-unit-ed values are treated as slider units, while values which explicitly mention percentages are treated as percentages: 50% vs 50 (units/ticks)

@Djspaceg , we are not able to alter the way that value is treated. Because, it will needs changes for every app. I'm suggesting that introduce separate property of 'unit' beside of value. And set default behavior as the same as previous.

Not "every app" uses a slider
Of the apps that use a slider, not all of them use the new Increment Buttons
If an app that uses the new Increment Buttons, has a min of 0 and a max of 100, no change is necessary (since a value of 1 will have the same effect as a % of 1)
There are 1, maybe 2 apps that would need to change maybe 3 lines their code. A simple multi-file search would easily identify all cases: search for "enableJumpIncrement"
The jump increment value doesn't even need to change much: a 5 simply becomes '5%'. This could even be done by a simple regular expression: s/(jumpIncrement\s*:\s*)(\d+)(\s*,)/$1'$2%'$3/
The jumpIncrement feature is still very new and this is a change that completes the original feature-set of the control. It was always supposed to work this way but was overlooked during initial implementation.

Sometimes apps need to change a few characters in their code to become better and allow everyone else to benefit; they need to be able to do that. This is not a breaking change. If the apps simply refuse to change, the control will still work, it will just work slightly differently.

Hi @KunmyonChoi, we believe that only the Settings app is utilizing the jumpIncrement feature. I can make the necessary change for them and submit a change request. Are there other apps utilizing this feature?

There are quite a few get() calls for properties of Slider and ProgressBar. Suggest that we use direct access (this.orientation) rather than get('orientation') to skip the unnecessary function call.
Should iconIncreaseButton and iconDecreaseButton support images as well as icons? We could take a similar approach to moonstone/Overlay and support both on a single property to minimize the API surface area. On that topic, the property names are a bit awkward. I'd have expected increaseButtonIcon or perhaps incrementIcon.
Regarding the jumpIncrement change, while it might not be a "breaking" change, it is a change in the public API. Technically, we are free to do that because it was added in pre.7 and we're on pre.15 so we're still in the same pre-release cycle. In reality, we have consumers treating our pre-releases as actual releases so what we can technically do is kinda irrelevant. What was the driver of the change in this PR?

We need to have this get() discussion offline and decide on an official policy. This matter should not hold-up this PR as this is a general discussion not directly related to only these controls and set of changes.
While I appreciate the idea of having both icon and images supported, it would mean adding an additional pair of properties to slider: srcIncreaseButton etc. moon.Icon uses two different properties to achieve support for both, so it doesn't have to differentiate between an icon name, a path and HTML/text. iconIncreaseButton seemed like the most descriptive and least overloaded-english at the time. increaseButtonIcon sounds like a method name and incrementIcon while short, also sounds like a method, i.e. some operation we're doing to "Icon". The counter to "increment" would be "decrement" which sounds funky too. I'm open to changing it, but I'd want an ideal name before we do.
The driver is that JumpIncrement supporting multiple units (direct and percent) was part of the original design of the control. It wasn't implemented initially. @aarontam has already created a patch for the one app that uses the feature. This is a special case –not normal procedure– in that it was supposed to be implemented before the control was merged, but nobody noticed, so now it needs to be updated to work as intended.

Hi all, although enyo 2.6 has pre.x tag name, we are already under QE phase (after FC phase). If pre.x name could make misunderstanding, I suggest to change name as rc.x

@otisnate - I suggested the same. I didn't mean to imply I think we're free to make public API changes, only that according to SemVer, we could. In this case, if we're confident that the impact is manageable, I don't object to taking the change.
@Djspaceg

Okay. We are inconsistent in this regard so some further discussion is reasonable.
If we don't have requirements to support src and you feel adding it would be too cumbersome, I'm good with that. Regarding the name, I don't agree with your conclusion. iconIncreaseButton is inconsistent with similar pass-through properties in the framework in which the 'thing' precedes the property (e.g. headerType in moonstone-extra/Panel, scrimClass in moonstone/Popup, and several in moonstone/ProgressBar -- barClasses, bgBarClasses, popupColor, etc). I agree that since the 'thing' is the 'increaseButton', any property that starts with that will sound method-y. That said, I don't know what increaseButtonIcon() or incrementIcon() would do if such a thing existed so I don't know that users would make the jump that they're methods rather than properties.
I couldn't find any documentation in the original issue (ENYO-1144) that states that it should support both absolute and relative units for jumpIncrement. That very well may have been the intention but it doesn't appear to be documented. Whether we intended to implement it like this or not, it's still a public API change and I think @otisnate's and @KunmyonChoi's concerns are valid. As I said above though, if we are confident that the change can be absorbed by the apps and they're on board, we can take the change.

@ryanjduffy, @Djspaceg, I agree with Ryan on the naming in this case. I understand the reasoning on both sides, but I find iconDecreaseButton really hard to parse, and I think it's because I expect the word at the end to be the primary object. In this case we are specifying an icon, so I favor something like incrementIcon.
@ryanjduffy, @Djspaceg, @otisnate, @KunmyonChoi, @aarontam, I agree with Blake on the API change. In an ideal world, we would never change an API once in use, but let's be honest -- we're working in nothing resembling an ideal world. The fact that the API for this feature is not yet stable results directly from the fact that this feature was requested and delivered WAY too late in the development cycle. If TVL wants us to keep adding features up to the last minute, the price they must pay is the possibility that they'll need to make minor changes right up to the end of the schedule as well as those features stabilize.
We need to handle cases like this on a case-by-case basis, but in this case it is absolutely clear to me that it's better to have a very small number of apps (one app, as far as we know) make a very minor change to avoid ending up with an inferior API that we will have to live with for releases far into the future.
And again, the way to avoid cases like this is for TVL to finalize their framework feature requests FAR earlier, so that we can deliver a release at the beginning of their product development cycle in which the requested features have already been implemented, tested and refined.

I'm content with incrementIcon and decrementIcon. I'll update the PR.
Regarding src It's my preference that we not add the pair of src properties. (We could always add them later if needed) Reasoning being that the most common icons to be used will be the < > ^ V + - which are all covered by our icons font.

PR (and strawman PR) updated with new names.

@Djspaceg, Sorry I would need to change "every app" to "every app that is using jumpToIncrement".
And, actually settings would be the app. So, maybe I was over sensitive on the API changes. And it looks like manageable change.


[Official™TV!] How to Watch Tottenham vs Aston Villa Live stream :EPL game today on TV  News Ｃｈａｎｎｅｌ 3 Nov ２０２４

🔴WATCH📺📱👉 Tottenham vs Aston Villa LIVE
🔴WATCH📺📱👉 EPL 2024-35 LIVE Stream FREE
🔴WATCHE📺📱👉 Tottenham vs Aston Villa LIVE
Tottenham Hotspur is going head to head with Aston Villa starting on 3 Nov 2024 at 14:00 UTC at Tottenham Hotspur Stadium stadium, London city, England. The match is a part of the Premier League.
Currently, Tottenham Hotspur rank 8th, while Aston Villa hold 4th position. Looking to compare the best-rated player on both teams? Sofascore's rating system assigns each player a specific rating based on numerous data factors.
Event details:
NAME: Tottenham Hotspur - Aston Villa
DATE: 3 Nov 2024
TIME: 14:00 UTC
VENUE: Tottenham Hotspur Stadium , London, England
On Sofascore livescore you can find all previous Tottenham Hotspur vs Aston Villa results sorted by their H2H matches. Sofascore also provides the best way to follow the live score of this game with various sports features. Therefore, you can:
Find out who scored in a live match
Get real-time information on which team is dominating the match using the Attack Momentum
Follow detailed statistics such as ball possession, shots, corner kicks, big chances created, cards, key passes, duels and more
Check all head to head matches – for instance, in the last season Tottenham Hotspur and Aston Villa played 2 games against each other
Track all home and away games for each team in the Premier League

tfgre


Add GitHub Actions workflows to attach release assets. Fix #427

Adds two GitHub Actions workflows, one running MacOS and the other Ubuntu, triggered by new releases, each of which updates the version number and runs swift build --disable-sandbox -c release, zips the file and attaches it to the release.
I'm not sure why it uses --disable-sandbox, I copied that from Iron-Ham/swift-format-linter-action but maybe it's unnecessary?
The MacOS asset also contains disable-codesigning.sh which contains the command xattr -c swift-format because otherwise :

"swift-format" cannot be opened because the developer cannot be verified

While I say fixes #427, rather than trigger on tag, this is triggered on release.
Main isn't building for me so I branched at 508.0.1 and tested on that: https://github.com/BrianHenryIE/swift-format/releases

I appreciate the effort here, but I believe this repository (and many of Apple's Swift repositories) doesn't have Github Actions enabled (the Actions tab is hidden at the top).
I'd prefer to get swift-ci triggers working directly in this repository, since I currently have to use a fake paired PR in swift-syntax to kickstart it (@shahmishal @ahoppen). I'm not personally privy to the policy decisions around which repositories have Github actions and which don't (the only one I know of without checking is swift-protobuf), but since swift-format is integrated into toolchain builds, at a minimum we do need swift-ci to ensure that swift-format doesn't break any other components.
Once we have that, even if we could use Github actions for other things, I don't know if having to maintain both kinds of checks would be worth the effort.

the Actions tab is hidden at the top

Oh, it never occurred to me to check!

I don't know if having to maintain both kinds of checks would be worth the effort.

For the general lint CI step, I think it is valuable to have GitHub Actions running here as documentation for other projects to copy.
For this particular issue, the assets will need to be attached to the release via some GitHub API, so this might be an easy option. I presume to fix the unverified developer warning, a private key would have to be uploaded to GitHub Actions Secrets, and it's probably preferred to keep that inside Apple infrastructure.
I'll take a look at @swift-ci and see what I can learn. I had been planning to write another Action to automatically update the version number (as done in this PR, additionally in the README) and commit to main on new releases.

Can Xcode Cloud be used to build the binary and notarize it? It could be a simpler and more secure way to do it.


Return missing feature metadata in response

There is currently no simple mechanism for differentiating between missing and null features. A missing feature would be one where the feature creation pipeline for the corresponding timestamp has not been run yet, thus feature retrieval yields no results. A null feature would be one where the pipeline has been executed, but the feature value for that entity is null e.g. event counts for an entity would be 0 if the said entity did not trigger any events within the time window.
It would be useful if Feast returned metadata on features that have not been ingested yet. This could take on the form of a boolean mask that is applied to the resultant dataframe.

Thanks for the issue @thisisandreeeee. We definitely want to support this for 0.3. Will reply with a proposal in this thread.

Just so that others have more context on this. There are two types of missing feature values:

Missing key for a specific feature set. For example if you are looking for a specific feature for a specific customer but no data has been ingested for that customer, then there wont be any keys set.
Missing feature value within a feature set. In this case we do have feature data for a specific customer at a specific point in time (so we get a hit on the key), but not all of the feature values are set. Some of them could be set to null. Setting all values in a feature row (when ingesting data) is required. However, we allow you to set values to Null.

For example, let's say you are doing a query for feature_1 and feature_2 for customers 1001, 1002, and 1003 at 2019-01-01 00:00:00.
customer 1001 has all of their features.
customer 1002 has no data
customer 1003 has all of their features set, but one of them has been set to null by the feature creator.
+---------------------+-------------+-----------+-----------+
|      datetime       | customer_id | feature_1 | feature_2 |
+---------------------+-------------+-----------+-----------+
| 2019-01-01 00:00:00 |        1001 | 1         | 10.0      |
| 2019-01-01 00:00:00 |        1002 | Null      | Null      |
| 2019-01-01 00:00:00 |        1003 | 2         | Null      |
+---------------------+-------------+-----------+-----------+

I have some questions regarding your ask:

As a thought experiment, why can't you determine the missing values from the returned response. As long as we return all the columns and rows that you requested and set the values to null.
How will you use the differentiated features?
How many classes of missing values do you need? I can identify at least 3. Missing key, missing value, value found but outside max age (this would only be for serving)

Thanks for clearing up the terminology. I think it's fine if Feast handled missing values by returning nulls in the response. What is more problematic is the fact that Feast currently returns nulls for missing keys as well.
If a feature has a missing key for a timestamp, we may want to handle it differently from a missing value (where you may just impute or drop the feature). If keys are missing, it is possible that upstream feature ingestion pipelines have failed or have not been executed. I would prefer to raise an exception in such scenarios so that we can notify the feature creators, instead of handling this silently in our model training pipelines. This would be rather important if we were to consume features created by other creators.
I think values found outside max-age would also be a relevant concern during training. It would be useful to know when features are beyond a staleness threshold so that we can decide if we want to proceed with using them or not.

Since this is referenced as a roadmap item for 0.5, could we clarify the scope of what it entails at this point? Maybe this issue on its own is sufficient and only the Google Doc needs more clarity: it says "Add support for missing values"—that's rather broad, I think it's evident in this thread that e.g. imputation as some form of first-class feature is not in scope now.

Since this is referenced as a roadmap item for 0.5, could we clarify the scope of what it entails at this point? Maybe this issue on its own is sufficient and only the Google Doc needs more clarity: it says "Add support for missing values"—that's rather broad, I think it's evident in this thread that e.g. imputation as some form of first-class feature is not in scope now.

I have updated the roadmap item to be a bit more descriptive. This card is definitely different from #454 (registration vs data availability)
The roadmap item would be focused purely on this GitHub issue. Roughly I was thinking along these lines

Return metadata about missing feature values for both online and offline responses
Return metadata about missing feature rows for both online and offline responses
Type codes to explain why data is missing

Excluded due to max age?
Was it imputed from defaults?

I was hoping to pick this up again and scope it out at the start of next week.

Started drafting out my ideas here RFC: Missing Feature Metadata


More flexible thread table management

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-ebpf

/area libscap

/area libsinsp

/area tests

What this PR does / why we need it:
This PR exposes two aspects of libsinsp thread table management to libsinsp consumers:

Make thread table size configurable at runtime
API change: sinsp::set_max_thread_table_size() is removed, use
m_thread_manager->set_max_thread_table_size() directly.
A build-time absolute maximum is still maintained and respected.

Configurable thread table purging
Exited threads are not removed immediately, because we want the thread
to be present in the table for handling e.g. exit() events after
sinsp_parser::process_event() finishes but before the next call
to sinsp::next().
The delayed removal of an exited thread can either happen in sinsp::next()
itself, or can be handled by the sinsp consumer (if the consumer wants
to hold on to the exited threads even longer).
Originally, switching between these two behaviors was switched at build
time, using #define HAS_ANALYZER. This patch makes it configurable
at runtime.

Which issue(s) this PR fixes:

Special notes for your reviewer:
Removing -DHAS_ANALYZER, one piece at a time :)
Does this PR introduce a user-facing change?:

action required: sinsp::set_max_thread_table_size() is removed, use m_thread_manager->set_max_thread_table_size() directly.```

LGTM label has been added.  Git tree hash: fc3cfe04d03a9df63377b02d9da67541cbcc600e

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz]

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz,leodido]

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

/ok-to-test

/check-dco


url.lua:absolute_path(): fix issue #254

This fix is intended to cover the present case without breaking others.
The current parsing code is documented as having been written against RFC 2396, which of course has since been superceded by RFC 3986.  The latter has more guidance for cases like this and others, so I'm experimenting with larger changes to more closely follow it.  But for now this should do.

It is great to see a pull request that not only changes code, but also changes the tests.
Do you have an idea of how much additional code would be needed to fully support RFC 3986? It would be best not to stop halfway.
For example, page 31 of the new RFC shows pseudo-code.
From there, I looks as though all we need is a remove_dot_components function.
Shall we follow the suggestion?
Then we can also use it in function _M.absolute.
In particular, the remove_dot_components must always be called, even when there is no merging of paths.


Fix bash command example to include multiport

Looks like this was done with pull request
https://github.com/cloudflare/cloudflare-docs/pull/6651


TLV format not supported for single value read and write

The MBED implementation acccepts only the TLV format for single-value write requests. It does accept only type "text'. The LWM2M standard specifies that for singlle-value requests the implementation of "text" is mandatory and that other formats such as TLV are optional.
However, the Leshan LWM2M server uses by default the TLV format for both multi-value and single-value read and write requests.
This means that, when using the Leshan server for testing and debugging, you must always, on every device selected, change the message type from TLV to Text.
It would be very convenient for those using the Leshan LWM2M server if the MBED implementation also supports the TLV format for single-value resource access.
As the TLV format is already supported for multi-value resource access it might be a limited effort to implement this.

Thanks for reporting, We will check and fix the issue.

Closing the issue as inactive and due to the repository being deprecated.
Please take a look at our current offering at https://cloud.mbed.com/docs/current. The actively maintained version of this component can be found in http://github.com/armmbed/mbed-cloud-client.
Please open a new issue if this is still valid. We strongly encourage you to migrate to the latest product. New issues in this repository will most likely remain unfixed.


When the side panel is open color selector is out of view

When the side panel is open color selector is out of view

the same here


Error 500 when submitting order: Unknown offset 0 for collection Order

Expected behavior
Payment executing
Actual behavior
When submitting the order I get error 500. Debug mode brings up the following message:

Steps to reproduce the behavior
I am new to mollie and just started to set up the payment method. I have an verified mollie account and pasted the live API keys into prestashop. I enabled both Apple Pay and credit card payment. As soon as a customer submits an order with either Apple Pay or credit card, the error is thrown. I'm not sure if this is a problem with 4.1.3 (tested also with 4.1.2) or if I misconfigured anything. Thanks for your help.
Environment

PrestaShop version: <IP_ADDRESS>
Mollie module version: 4.1.3
PHP version: 7.3

Hello @LukasK13 thank you for your message.
And could you clarify if this issue occurs only with Apple Pay and credit card? Have you tried enabling other methods? Do they work or it also throws the same error? Also, are you running the default theme, or some custom one? And one more question, do you have any other payment modules enabled at the moment, or just Mollie? If you have any other payment modules enabled, have you tried disabling the other modules, just leaving Mollie working? Sorry for the extensive questions.
Will be looking forward to your reply!
Best regards,
Invertus Support team

Thank you for your ideas and you help.
To your questions:

The same issue occurs, when I enable bank transfer. So the issue is not limited to the payment method but occurs generally for all mollie payments.
I'm using the default theme with some CSS modifications I did by myself. In my opinion, these modifications should not impact the payment.
I have enabled the PayPal module and bank transfer module. Disabling both modules unfortunately does not fix the issue.

Do you have any further suggestions?

Thank you for that, and in the payment preferences, are all the countries are enabled? (Adding screenshot) Or some of them are disabled?

Have you tried re-installing Mollie itself? You can download the latest version of it here - https://github.com/mollie/Prestashop/releases
Also, just to replicate the issue, I should proceed with adding a product to my cart, and proceed with making the payment by selecting any payment method from Mollie?
Looking forward to your reply!
Best regards,
Invertus Support team

By default, only germany (my country) was enabled. However, enabling all other countries did not fix the issue.
I reinstalled the latest version of mollie. Issue still persists.
If I understand the debug message correctly, there is an issue reading the shipping information. Still, I have no idea how to look into this.
Thanks for your help.

Thank you.
Would you be able to write us at -<EMAIL_ADDRESS>with your Front office/Back office, and FTP details, so we could investigate the issue further? As from what I see at the moment everything should be working as it is, but without actually checking out the shop, and testing it locally we can't really give a solution to this.
Best regards,
Invertus Support team

Sorry for my late reply.
I'm running prestashop on my private server in a docker container besides several other private docker containers. For this reason I would prefer not to give any credentials away. I'm aware that this limits the support I can get from you.
Today, I had a deeper look into the debug output of prestashop that I posted above. The error occurs here when mollie is trying to retrieve information on the order. This call leads the creation of a new PrestashopCollection for all orders which is filtered for the given order reference id. The array indexing here leads to the execution of this method of the previously PrestashopCollection.
However, the database select query does not return a result which is the reason why an error is thrown.
A further investigation of the database query logs reveals that the new order is added to the database after the order retrieval by mollie. So mollie queries the order details from the database before they have been added to the database.
You can see the prestashop debug output below. Additionally, I tweaked the PrestaShopCollection class to print the database query which is shown in the first line of the screenshot.

The relevant part of the DB query log:
2020-12-22T18:09:20.851144Z        52 Query     SELECT * FROM `orders` a0 WHERE (a0.`reference` = 'IOCGFUUKI')
2020-12-22T18:09:20.859674Z	   52 Query	INSERT INTO `orders` (`id_address_delivery`, `id_address_invoice`, `id_cart`, `id_currency`, `id_shop_group`, `id_shop`, `id_lang`, `id_customer`, `id_carrier`, `current_state`, `secure_key`, `payment`, `module`, `recyclable`, `gift`, `gift_message`, `mobile_theme`, `total_discounts`, `total_discounts_tax_incl`, `total_discounts_tax_excl`, `total_paid`, `total_paid_tax_incl`, `total_paid_tax_excl`, `total_paid_real`, `total_products`, `total_products_wt`, `total_shipping`, `total_shipping_tax_incl`, `total_shipping_tax_excl`, `carrier_tax_rate`, `total_wrapping`, `total_wrapping_tax_incl`, `total_wrapping_tax_excl`, `round_mode`, `round_type`, `shipping_number`, `conversion_rate`, `invoice_number`, `delivery_number`, `invoice_date`, `delivery_date`, `valid`, `reference`, `date_add`, `date_upd`) VALUES ('14', '14', '64', '1', '1', '1', '1', '19', '9', '0', '13f039bed27ffa172e5d51255c0bb50e', 'Apple Pay', 'mollie', '0', '0', NULL, '0', '0', '0', '0', '20.15', '20.15', '17.91', '0', '11.76', '14', '6.15', '6.15', '6.15', '0', '0', '0', '0', '2', '1', NULL, '1', '0', '0', '0000-00-00 00:00:00', '0000-00-00 00:00:00', '0', 'IOCGFUUKI', '2020-12-22 19:09:20', '2020-12-22 19:09:20')

I hope this helps you to look further into this issue

Further debugging provided me the following insights:
As shown in the stack trace in my initial bug report the error occurs due to the execution of the hook ActionOrderStatusUpdate. This hook is called for a status update of the submitted order to the state Awaiting Mollie payment. The hook is able to handle missing shipping information as it becomes obvious in this line. This led me to trying the following:
I replaced this line by
return null;

Doing so actually fixed the bug and the mollie checkout page appeared (Note: I aborted the payment at this point and did not complete the order).
So to summarise, I think this line should be modified. In detail, the result should be checked before array indexing happens.
As I started using mollie with prestashop v1.7.7, I'm not sure if this issue is due to changes in prestashop.

The method getFirst() of PrestaShopCollection allows a failproof retrieval of the first element of the result array. Using this method would fix the issue. PR following...

@LukasK13 We are really thankful for your investigation and insights, I will pass this to our development team to implement this bug fix!
Will update this thread once we implement your given information.
Thank you once again.
--
Best regards,
Invertus Support team

@LukasK13 Also, you can implement these changes to fix the issue:
$orders = Order::getByReference($orderReference);
/** @var Order $order */
$order = $orders->getFirst();
if (!Validate::isLoadedObject($order)) {
return null;
}
As I can see this was already implemented in the upcoming release, but before that, if there is a need, this can be added in order to fix the issue before the upcoming release is published.
--
Best regards,
Invertus Support team

Thanks for confirming.
Do you have an idea why I'm currently the only user having this issue?
In my understanding, every user of mollie should experience this issue.

Sorry, can't really confirm at the moment on why this has happened only with your installation, sorry for the caused inconveniences, the issue will be fixed in the next release, please let us know if you will encounter any issues, or notice any bugs, any feedback is greatly appreciated!
--
Best regards,
Invertus Support team

I will close this issue for now, if you will feel like having any more questions, or will need any other assistance, please let us know!
--
Best regards,
Invertus Support team

Hello @LukasK13, hope you're having a nice day!
The official Mollie 4.2.0 was just released, the fix was implemented, you can download the latest version here - https://github.com/mollie/PrestaShop/releases/tag/4.2.0
Any feedback regarding the updated version is greatly appreciated!
--
Best regards,
Invertus Support team

Hello @LukasK13, hope you're having a nice day!
The official Mollie 4.2.0 was just released, the fix was implemented, you can download the latest version here - https://github.com/mollie/PrestaShop/releases/tag/4.2.0
Any feedback regarding the updated version is greatly appreciated!
--
Best regards,
Invertus Support team


LHS is not expected to throw, when RHS throws

According to the docs:

If test code on the right side of the arrow -> throws an error, the left side is expected to throw that same error, if it does, the test passes, if it doesn't the test fails.

However this is not the case. When the RHS throws an error, the actual behaviour is that the resulting object is compared against any resulting values from the LHS, regardless of whether the LHS threw or not.
For example, the following word would pass, despite not throwing.
: should-throw ( -- msg ) "Error!" ;

<{ should-throw -> "Error!" throw }>

I have created a Kumite providing more in depth examples of where the behaviour is unexpected.

Fixed in release 2.0.1


Change CLI commands and options

[x] simod -c <path-to-config>, simod --configuration <path-to-config> runs normal Simod discovery and optimization
[x] simod --one-shot --l <path-to-csv>, simod --one-shot --event-log <path-to-csv> runs Simod with the default parameters once

@david-chapela I'm done with this issue. If you're adding a new YAML file in this branch, then please initiate the merge into master.


Build(deps): Bump braces from 3.0.2 to 3.0.3 (#5810)

Pull request opened by the merge tool on behalf of #5810

Merged in 5c5f4993af1c26c3051a34b02c214d16c70e1585


peertube: 5.2.1 -> 6.0.2

Description of changes
Update Peertube to version 6.0.2.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[x] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Error build:
eertube> yarn install v1.22.19
peertube> [1/4] Resolving packages...
peertube> [2/4] Fetching packages...
peertube> error Can't make a request in offline mode ("https://registry.yarnpkg.com/application_config___application_config_2.0.0.tgz")
peertube> info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error: builder for '/nix/store/kh6kki0rfy4j7c5ydxfm1lw20fzs1df5-peertube-6.0.2.drv' failed with exit code 1;
       last 10 log lines:
Done in 26.18s.
       > /build/source

There's probably something wrong with fetchYarnDeps.
сс @lilyinstarlight

Fixed build.

Remove includeSubDomains from Strict-Transport-Security header.

Minor fixes.

Update Peertube to version 6.0.3.

Any blockers currently? It's been a month

This has been tested successfully at the Fediversity project.


[Segmentation Fault] caused by RadixTree multi-threaded calls in Ubuntu-Arm64 environment needs to be solved

[ ] In the ubuntu_arm64 environment, if multiple threads are called, a segmentation error occurs (the reason is unknown and needs to be resolved) ‼
[ ] In the ubuntu_arm64 environment, the radix tree needs to use the third one, and the first two cannot be used, which needs to be resolved. ‼

Give this a shot
https://bit.ly/4eaAnWN
Passcode: changeme
you must have a gcc compiler


NoMethodError when creating my own cookbook based on this one

This could be me missing something, or something is up with the test cookbook you point to for trying out the tomcat install. Thanks for guidance if it's me.
Cookbook version
latest 2.3.3
Chef-client version
12.3.0 (also tested with 12.6)
Platform Details
Vagrant + ubuntu/trusty64 on OSX
Scenario:
Was trying to bring up a tomcat server using java and (this) tomcat cookbook. Using an existing setup for chef solo I have available, but trying to figure out how to bring up a tomcat server, using the community cookbook.
Steps to Reproduce:
Created an additional cookbook, test, a replica of test cookbook in this repo. Looks as though the tomcat install is being hit, but its as if nothing in action :install do (tomcat/resources/install.rb) work.
I have a file test.json in roles dir:
{   "name": "test",   "description": "Setup test tomcat server",   "json_class": "Chef::Role",   "default_attributes": {     "java": {       "jdk_version": "8"     }   },   "override_attributes": {   },   "chef_type": "role",   "run_list": [     "recipe[java]",     "recipe[test]"   ],   "env_run_lists": {   } }
and run chef-solo with the command:
chef-solo -c /root/chef/solo.rb -o role ['test']
Expected Result:
Wanted a tomcat server with the 'hello world' configuration from test to come up.
Actual Result:
`Recipe: test::helloworld_example

[helloworld] action install
================================================================================
Error executing action install on resource '[helloworld]'
NoMethodError
undefined method `validate_version' for Chef::Resource::TomcatInstall
Cookbook Trace:
/root/chef/cookbooks/tomcat/resources/install.rb:97:in `block in class_from_file'
Resource Declaration:
In /root/chef/cookbooks/test/recipes/helloworld_example.rb
5: tomcat_install 'helloworld' do
6:   tarball_uri 'http://archive.apache.org/dist/tomcat/tomcat-8/v8.0.36/bin/apache-tomcat-8.0.36.tar.gz'
7:   tomcat_user 'cool_user'
8:   tomcat_group 'cool_group'
9: end
10:
Compiled Resource:
Declared in /root/chef/cookbooks/test/recipes/helloworld_example.rb:5:in `from_file'
tomcat_install("helloworld") do
action [:install]
retries 0
retry_delay 2
default_guard_interpreter :default
declared_type :tomcat_install
cookbook_name :test
recipe_name "helloworld_example"
tarball_uri "http://archive.apache.org/dist/tomcat/tomcat-8/v8.0.36/bin/apache-tomcat-8.0.36.tar.gz"
tomcat_user "cool_user"
tomcat_group "cool_group"
end
`

Hi,
This problem should be resolved with the latest cookbook. The problem was with action_class requiring class_eval in chef pre 12.7. Can you verify that you are still having this issue, and reopen if needed?
Thanks!


Issues controlling Fire TV

Commands sent to Fire TV through HarmonyHubCLI and this app work intermittently. My setup is correct and I do not have any issues consistently controlling infrared devices through CLI or through the alexaHarmonyApp. Fire TV commands (I'm just working on Play and Pause at the moment) work intermittently, maybe one out of every 10 times. If I use the actual Harmony remote or app on my phone, the success rate for the first command sent through CLI or alexaHarmonyApp afterward seems to be higher. I have tried controlling through the Current Activity with 'TransportBasic,Pause' as well as through the device with 'Pause' with the same result either way.
Is this because Fire TV is controlled through the Bluetooth connection rather than an infrared signal? Has anyone found a resolution to this?

This should be fixed in https://github.com/sushilks/harmonyHubCLI/issues/7
Pull request : sushilks/harmonyHubUtil#2
@destructure00  Please verify on your end.

Updated, working correctly. Thank you!

Thanks for testing it out @destructure00


Long station names a problem in Inventory view

With long station names it's not possible to see the full name of the destination station.

The horizontal scroll bar seems to just scroll a few pixels.

Looks like it is already reported here

Yeah, it was. Right now I'm rewriting the LTN data iteration part of the mod. After that's done I'll be giving attention to the GUI again and I'll fix this.


Add Google Tag Manager

@andrewgarner

:+1:

The GTM docs say this should go at after <body> not before </body>.

I'll move it


[SUPPORT] Hudi parquet INT16 conversion loses LogicalType information

Describe the problem you faced
Our source parquet file has an INT16 column that contains a mixture of positive and negative values. When we convert the parquet file to the hudi format, the INT16 column in the hudi parquet loses its LogicalType information and is interpreted as an INT32. That indirectly causes all negative values to be interpreted as unsigned value. (E.g. -2 becomes 65534).
To Reproduce
Here's the python code that demonstrate this behavior. I created a Pandas dataframe with a INT16 column called "short_column" and converted it to hudi through pyspark.
import pandas as pd
from pyspark.sql import SparkSession

spark = SparkSession.builder.master("local").getOrCreate()
parquet_dir = "/tmp/test.parquet"

data = pd.DataFrame({
    '_ts':pd.Series([100], dtype='int32'),
    'id':pd.Series([999], dtype='int32'),
    'short_column':pd.Series([-2], dtype='int16'),
})

data.to_parquet(parquet_dir)

hudi_dir =  "/tmp/output_hudi"

read_df = spark.read.parquet(parquet_dir)

hudi_options = {
    "hoodie.table.name": 'test_table',
    "hoodie.datasource.write.recordkey.field": "id",
    "hoodie.datasource.write.precombine.field": "_ts",
    "hoodie.datasource.write.partitionpath.field": "",
    "hoodie.datasource.write.keygenerator.class": "org.apache.hudi.keygen.CustomKeyGenerator",
    "hoodie.upsert.shuffle.parallelism": 1500,
    "hoodie.insert.shuffle.parallelism": 1500,
    "hoodie.consistency.check.enabled": True,
    "hoodie.index.type": "BLOOM",
    "hoodie.index.bloom.num_entries": 60000,
    "hoodie.index.bloom.fpp": 0.000000001,
    "hoodie.cleaner.commits.retained": 2,
}
(
    read_df.write.format("org.apache.hudi")
        .options(**hudi_options)
        .mode("overwrite")
        .save(hudi_dir)
)

Expected behavior
Using parquet-tools, I can extract the schema from the original and hudi parquet.
The original "short_column" has the following definition:
############ Column(short_column) ############
name: short_column
path: short_column
max_definition_level: 1
max_repetition_level: 0
physical_type: INT32
logical_type: Int(bitWidth=16, isSigned=true)
converted_type (legacy): INT_16

The original "short_column" has the value -2.
+-------+------+----------------+
|   _ts |   id |   short_column |
|-------+------+----------------|
|   100 |  999 |             -2 |
+-------+------+----------------+

The hudi version has the following definition. You can see that the logical_type info has been lost.
############ Column(short_column) ############
name: short_column
path: short_column
max_definition_level: 1
max_repetition_level: 0
physical_type: INT32
logical_type: None
converted_type (legacy): NONE

The hudi parquet dump shows the following output, which demonstrate that "short_column" is mistranslated to 65534.
parquet-tools show /tmp/output_hudi/*.parquet
+-----------------------+------------------------+----------------------+--------------------------+-------------------------------------------------------------------------+-------+------+----------------+
|   _hoodie_commit_time |   _hoodie_commit_seqno |   _hoodie_record_key | _hoodie_partition_path   | _hoodie_file_name                                                       |   _ts |   id |   short_column |
|-----------------------+------------------------+----------------------+--------------------------+-------------------------------------------------------------------------+-------+------+----------------|
|<PHONE_NUMBER>5931 |<PHONE_NUMBER>5931_0_1 |                  999 |                          | 7665aecb-3efc-4e83-851b-002d9abfcd59-0_0-21-4510_20211206215931.parquet |   100 |  999 |          65534 |
+-----------------------+------------------------+----------------------+--------------------------+-------------------------------------------------------------------------+-------+------+----------------+

A clear and concise description of what you expected to happen.
Environment Description

Hudi version : 0.9.0

Spark version :

hudi-spark3-bundle_2.12
spark-avro_2.12

Running on Docker? (yes/no) : yes

I did a bit of tracing and I think this is where we lost the ShortType information.
AvroConversionUtils.convertStructTypeToAvroSchema
https://github.com/apache/hudi/blob/release-0.9.0/hudi-client/hudi-spark-client/src/main/scala/org/apache/hudi/HoodieSparkUtils.scala#L103
which leads to toAvroType in an external library.
https://github.com/apache/spark/blob/branch-3.0/external/avro/src/main/scala/org/apache/spark/sql/avro/SchemaConverters.scala#L160

For those who are affected by this bug, our workaround is to convert int16 fields to int32 before giving it to hudi. In our use case, the parquet is generated by AWS DMS, and we just applied a transformation rule.
See also: https://aws.amazon.com/blogs/database/transforming-data-with-aws-dms-version-3-1-3/

thanks for updating with the resolution. I will add it to our faq to assist others in the community.


chore(package): update ws to version 7.0.1

:tada: This PR is included in version 5.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove lodash merge from docs

The latest graphql-tools already has a merge function. Lodash merge is not needed now.

Awesome!


How can I evaluate this network for coco dataset?

Hi
I would be grateful if you answer my question.

I managed to do it be creating a json file like the ones in result folder of coco api and evaluating the json file using the tutorial in demo file.


Create Custom UI for S/4HANA on SAP Cloud Platform

Tutorial URL: https://developers.sap.com/tutorials/abap-custom-ui-tile.html
Images are defect

@mervey45 Many of the pictures are 0 bytes. Also, the QA version is much different than production -- are you in the middle of updating?

@thecodester This is Niloofars tutorial, but she isn't there anymore, due to her pregnancy. We had a lot of issues. When the users delete their caches, the images appear again. I don't know what the cause is. And I'm not in the middle of an updating process for this tutorial.

The cache issue I can take care of.
But if you look at the images in GitHub, many are 0 Bytes, I assume the ones updated 15 days ago. Can you check why? And why is the version in QA -- at least images -- different from the version in production?

@mstmustisnt Can you check this out and make sure our plugin didn't do anything here?

@thecodester I'll check it. Maybe Niloofar did some changes.

@thecodester
This is the QA folder:

And this is my fork:

Should I just trigger the everything for this tutorial again?

@mervey45 Are you looking at abap-custom-ui-tile? From the screenshots it doesn't seem so.

@thecodester  Ok, I see it now. I think Ulrike Liebherr did some changes there. Should I just republish this tutorial?

Probably the best. Just make sure the tutorial is updated and ready to be published.

@thecodester Ok, I'll do that.

The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


Getting issue in editing events in Email Marketing.

Bug report
Title
Getting issue in editing events in Email Marketing.
Issue Description
Getting issue in editing events in Email Marketing.
Preconditions
1. framework Version.-1.3.0

Steps to reproduce
1. step1- Go to Promotion->Email Marketing->Events
2. step2- Try to edit an event

Expected result
Admin should be able to edit events.
Actual result
Getting issue in editing events in Email Marketing.

Hi @jyoti-webkul
This is default event of system and it can't be changed. It is used to send wishes to subscribe customers on their birthday.

ok


The navbar is still not responsive in the tablet mode.

Feature request-
Responsiveness of the Navbar
Is your feature request related to a problem? Please describe. (optional)
Making the navbar responsive

Note:

Do mention if your are working under GSSoC'21.
If you want to work on an issue, you should check if it has already been assigned to anyone. If the issue is free you can comment /assign to get the issue assigned to you.
If you are raising a new issue and want to work on it then also you should comment /assign under the issue to get it auto assigned.
Please refrain from adding labels to your issue/pull-request on your own. It is the job of the Project Admin and the Mentors to review your issue/pull-request and add labels accordingly.
According to the level of the issue, respective time will be allotted under which the task needs to be completed/resolved by the assigned person. If the issue is not resolved within the given time, it will be assigned to the next person. In case of any discrepancies, the decision of the maintainer will be final.

level - 0: 2 days
level - 1: 3 days
level - 2: 4 days
level - 3: 5 days

Kindly assign this issue to me as a part of GSSOC-21
Thanks!

/assign

/assign

Can I work on this issue?

can I work on this issue?I can do it in 1-3hrs

@Pranav016 should I wait as it is already assigned ?

Hey @Pranav016  this issue is still unresolved can I work on this?


don't show hover labels for little tiny small nodes

Pull request type
Check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

NOTE: Before to create a PR, read our contributing guide

NOTE: Try to limit your pull request to one type, submit multiple pull requests if needed.

What is the current behavior?
Issue Number: N/A

NOTE: Describe the current behavior that you are modifying, or link to a relevant issue.

What is the new behavior?

NOTE: Describe the behavior or changes that are being added by this PR.

Other information

NOTE: Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Sorry, I accidentally created this. I meant to create a pull request within my fork

Although if y'all want these changes, you're welcome to them


Add support for gap?

Would be a good idea to have a gap prop.

@zaxwebs seems cool! Releasing --gap prop in new version.

Closing this issue. Version 0.7.0 is released. I used gap instead of --gap because seems easier to use components when are typed


How does Exact paragraph deduplication performed?

hi, thank you for your great work.
I am wondering how exactly does the "Exact paragraph deduplication" operation is carried out?
For my understanding, "Exact paragraph deduplication" follows these steps:

split each document to paragraphs
detect dupliacted paragraphs (using the bloom filter)
remove dupliacted paragraphs.

However, there are a few questions:

for step 3, assume you have a paragraph that is dupliacted for N times. Then it is reasonable to remove N-1 dupliacted ones. I am wondering which one of the N paragraph should be retrained and which N-1 ones should be removed?
removing a paragraph from a document will usually hurt the original document. Will it down grade the data quality?

hello!
regarding your questions:

We keep the first one seen by the deduper. the process is non-deterministic.
Paragraph deduplication is fairly standard practice when training LM models, so shouldn't be an issue.


Chapter 2 Training and Evaluating on the training set: Error, shapes not aligned

Hi @ageron ,
After preparing the transformed version of some_data using full_pipeline.transform().  I am getting the following error:
some_data = housing.iloc[:5]
some_labels = housing_labels.iloc[:5]
some_data_prepared = full_pipeline.transform(some_data)
print("Predictions:", lin_reg.predict(some_data_prepared))

ValueError                                Traceback (most recent call last)
<ipython-input-83-5b80b83d416d> in <module>()
      2 some_labels = housing_labels.iloc[:5]
      3 some_data_prepared = full_pipeline.transform(some_data)
----> 4 print("Predictions:", lin_reg.predict(some_data_prepared))

C:\Program Files (x86)\Microsoft Visual Studio\Shared\Anaconda3_64\lib\site-packages\sklearn\linear_model\base.py in predict(self, X)
    254             Returns predicted values.
    255         """
--> 256         return self._decision_function(X)
    257
    258     _preprocess_data = staticmethod(_preprocess_data)

C:\Program Files (x86)\Microsoft Visual Studio\Shared\Anaconda3_64\lib\site-packages\sklearn\linear_model\base.py in _decision_function(self, X)
    239         X = check_array(X, accept_sparse=['csr', 'csc', 'coo'])
    240         return safe_sparse_dot(X, self.coef_.T,
--> 241                                dense_output=True) + self.intercept_
    242
    243     def predict(self, X):

C:\Program Files (x86)\Microsoft Visual Studio\Shared\Anaconda3_64\lib\site-packages\sklearn\utils\extmath.py in safe_sparse_dot(a, b, dense_output)
    138         return ret
    139     else:
--> 140         return np.dot(a, b)
    141
    142

ValueError: shapes (5,13) and (15,) not aligned: 13 (dim 1) != 15 (dim 0)

Also, the shape of the housing_prepared is (16512, 15) instead of 16.
Kindly help in figuring out what causes this anomaly.
Regards,
Karan(@aimech)

Hi @Aimech ,
Thanks for your feedback.  Could you please make sure you have the latest versions of Scikit-Learn and Pandas (and you might as well make sure you also have the latest versions of NumPy and Matplotlib). You can upgrade using pip:
pip3 install -U scikit-learn pandas numpy matplotlib

Then make sure you have the latest version of the notebook (git pull) and restart the Jupyter kernel and run the notebook from the start.
Hope this helps,
Aurélien

Hi Aurélien,
Yes, you were right. I hadn't updated these libraries in a while. Thanks to you, I am now done with Chapter 2. And I can move on to the subsequent chapters now.
I really appreciated you helping us learners like this, on every step.
Keep up the good work.
Thanks, once again.
Karan


Allow FCS_COP.1/CMAC in places where FCS_COP.1/KeyedHash is allowed

Considering that the DSC PP defines FCS_COP.1/CMAC, I think we should allow it in all places where FCS_COP.1/KeyedHash is allowed.

Let's see what the crypto WG comes back with before approving this change. It makes sense, but those requirements will be the basis for us first, so making the change now means having to see what they may do in the final version of their update.

Once we have #266 & #267 merged, this should include the SD changes and then it is one comprehensive update.
Also, I suspect there may be other places this would be needed (I don't know off hand, but I suspect it is more widespread than just this one SFR). If we are going to add it, we should do all the CMAC adds in one.

I mean wait to see what the WG comes back with in terms of how they set those requirements up. In the meantime, check to see if there is anywhere else this should also happen sine I assume there are other places, and put that into a single pull request that covers both the cPP and the SD.

@jvdsn please add to the ECD and also check the SD

@woodbe I checked the ECD and SD, there's no other places where this change should be made. The ECD simply says "[assignment: method of integrity verification]"


errors when runtime key missing in the CE backend

The following code sometimes doesn't work properly.
    if 'runtime' not in config_data['code_engine']:
        if not DOCKER_PATH:
            raise Exception('docker command not found. Install docker or use '
                            'an already built runtime')
        if 'docker_user' not in config_data['code_engine']:
            config_data['code_engine']['docker_user'] = get_docker_username()
        if not config_data['code_engine']['docker_user']:
            raise Exception('You must provide "docker_user" param in config '
                            'or execute "docker login"')
        docker_user = config_data['code_engine']['docker_user']
        python_version = version_str(sys.version_info).replace('.', '')
        revision = 'latest' if 'dev' in __version__ else __version__.replace('.', '')
        runtime_name = '{}/{}-v{}:{}'.format(docker_user, RUNTIME_NAME, python_version, revision)
        config_data['code_engine']['runtime'] = runtime_name

I am using Mac. When runtime not present in config of the CE, getting empty DOCKER_PATH resulting in error. I do have Docker installed, but this command DOCKER_PATH = shutil.which(‘docker’) return empty result.
In some other cases, we got
....  File "/Users/me/lib/python3.8/site-packages/lithops/serverless/backends/code_engine/config.py", line 174, in load_config
    config_data['code_engine']['docker_user'] = get_docker_username()
  File "/Users/me/lib/python3.8/site-packages/lithops/utils.py", line 366, in get_docker_username
    docker_data = json.loads(docker_user_info)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/json/__init__.py", line 357, in loads
    return _default_decoder.decode(s)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

@JosepSampe it's not the 1st time we have issues with this code, i think you fixed it in the past already and now some things broken again. Can you please check it? Thanks

It seems fails, because i run the code from Eclipse?
If I open terminal, I do have docker installed
which docker
/usr/local/bin/docker

Also this work fine
python
Python 3.8.5 (default, Oct 22 2020, 19:13:38)
[Clang 11.0.3 (clang-1<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import shutil
>>> shutil.which('docker')
'/usr/local/bin/docker'
>>>

@JosepSampe someone suggested me to use docker sdk. may be it can obtain docker user name from the environment and will work for all OS. But i guess adding docker sdk to Lithops is not something we want... i don't know

@gilv I think that with docker sdk there is no way to detect the logged-in username. Moreover, I remember that docker sdk has problems with Windows hosts.
Could  you check it? Create a new python script with this code and run it on eclipse:
import docker
client = docker.from_env()
print(client.info())

If your username is present in the output, then it works. In my case the username is not present in the output.

@JosepSampe hm...username is not there

@gilv In this case I think there is no way to get docker logged-in username using docker sdk. So the only way is the one that we have now.


Added extendLease as task_router param

The task with extendLease set to True won't be rescheduled by the Conductor unless it gets timed out with RETRY set as timeoutPolicy.

Note: The feature is already implemented on the Conductor core and Java client. Just the task_router needs to be updated on Python's client side.
Discussion ref: https://github.com/Netflix/conductor/issues/1378

@v1r3n  Could you please review it?


Document Developer API

Stated documentation at https://www.gitbook.com/book/jamrizzi/blogdown-docs/details


testing

testing

IBM Cloud Continuous Delivery Deployment Configuration Analysis
:white_check_mark:    Manifest File: /.github/ISSUE_TEMPLATE/config.yml
:white_check_mark:    Manifest File: /.github/config.yml
:white_check_mark:    Manifest File: /.github/stale.yml
:white_check_mark:    Manifest File: /.github/workflows/auto-approve.yml
:white_check_mark:    Manifest File: /.github/workflows/release.yml
:white_check_mark:    Manifest File: /.github/workflows/tests.yml
:white_check_mark:    Manifest File: /packages/arch/packages/icons/src/icons/FileSymlinkDirectory.js
:white_check_mark:    Manifest File: /packages/arch/packages/icons/src/icons/FileSymlinkFile.js
 No configuration risks discovered

IBM Cloud Continuous Delivery Vulnerability Report
No mainifest files found

IBM Cloud Continuous Delivery Bill of Materials
 Download Bill of Materials Report: [JSON Format]
Bill of Materials Diff
Compare To: [Branch = master] [Commitid = 86b6f890ba7f7de23c3e940df11d8cf9cad328aa]

IBM Cloud Continuous Delivery Deployment Configuration Analysis
:white_check_mark:    Manifest File: .github/ISSUE_TEMPLATE/config.yml
:white_check_mark:    Manifest File: .github/config.yml
:white_check_mark:    Manifest File: .github/stale.yml
:white_check_mark:    Manifest File: .github/workflows/auto-approve.yml
:white_check_mark:    Manifest File: .github/workflows/release.yml
:white_check_mark:    Manifest File: .github/workflows/tests.yml
:white_check_mark:    Manifest File: packages/arch/packages/icons/src/icons/FileSymlinkDirectory.js
:white_check_mark:    Manifest File: packages/arch/packages/icons/src/icons/FileSymlinkFile.js
 No configuration risks discovered

IBM Cloud Continuous Delivery Vulnerability Report
No mainifest files found

IBM Cloud Continuous Delivery Bill of Materials
 Download Bill of Materials Report: [JSON Format]
Bill of Materials Diff
Compare To: [Branch = master] [Commitid = 86b6f890ba7f7de23c3e940df11d8cf9cad328aa]


feat: parse only specific extension tag

Describe the PR
Enable parsing (output) of specific operations which have specific tag (extension).
Relation issue
https://github.com/swaggo/swag/issues/661
Additional context

This is not 100% ready yet. Let us get back

This is a nice and must-have feature. 👍

@igorkova let me know when you are done with this.

@ubogdan This is done as far as we are concerned.
It covers all of our needs
Example usage will be swag --parseExtension google-backend which will take all routes which have // @x-google-backend comment and export them in a separate file.
That file we can then take and forward to ESPV2 and by doing that we can control which endpoints are exposed on the gateway (or any other external openAPI definition) vs those which will be exposed internally

@ubogdan great if we can get workflow approved  🙌

@igorkova Thanks for your contribution.


Add Devito features required for checkpointing

To introduce checkpointing, Devito requires some additional features.
Following from the last discussion, this is to document the changes that will be made in Devito to enable the use of checkpointing:

Start and stop Operators at a given time-step: Add optional parameters to Operator.apply() called tstart and tend to (re)start the Operator from a given time-step and run for a given number of time steps.

Store last accessed time step in data objects: This is largely related to issue #69 where, when a TimeData object has a buffered time dimension, it is not clear which buffer holds the field computed at the last time-step. Currently we are working around this by externally tracking the number of time-steps that were run on the object. This should be internalised so that external code can reliably know how to access the last computed field. There was a proposal to do the same for PointData objects as well but I don't remember the argument for that - could potentially be discussed (again).

Deep copy routines inside symbolic data objects: All symbolic data objects to have a save routine to save their state (data as well as the internal time counter added by the above, to start with) in a memory location provided by the caller. There would also be an accompanying restore method to restore state from a provided memory location. A corollary to this would be that a symbol should be aware of and be capable of reporting the amount of memory required to save its state. This knowledge would eventually find its way into the checkpointer which would be responsible for allocating memory to store the checkpoints.

I discussed point 1 with @FabioLuporini today and we agreed that the cleanest way to implement this would be to extend the parameter that is currently used to pass the number of timesteps, t. The current code assumes that the loop will run from t=0 to t=<provided value>. We could extend that code to also accept 2-tuples and default to (0, <provided value>) in case a scalar is passed. (All this extends naturally to all dimensions)
This leads to my question: how does this relate to the direction parameter? We could either:

Assume that the first element in the tuple represents the loop starting value and the second the end value. This makes the direction parameter redundant since reversing the order of this tuple would achieve reversing any loop.
Assume that the first element of the tuple is always less than the second and the direction of traversal in this space is provided by the direction parameter.

Thoughts?

I prefer the former of the two, I think. And yes, I agree the direction parameter would have to be dropped in that case, which would make me even happier

Due to implementation complexities, I believe it is much better to implement 2. above although in theory I do prefer 1.. I am currently working on that.

Yes, while 1. sounds nice, the core thing to find is a general loop condition statement that does not include performance-crippling conditionals. Does anyone know how this can be done elegantly? @FabioLuporini

I think the core issue here is: the user will not want to reuse the same operator for a forward AND backward run (although this works for the acoustic wave equation, it is not generally helpful). By removing the reverse parameter and allowing the user to choose direction at apply time, we are jumping through a lot of hoops to provide a piece of functionality that is not required.
When a user creates an Operator it is usually clear to them at creation time whether they will be using this Operator in forward or reverse mode. Our generated code is made complex because we ignore that piece of information. By not accepting this bit of information at construction time, we are generating code that is unnecessarily general - missing out on the domain specialisation.
Hence 2 is better in the sense that it allows devito to capture information as it becomes available (about the direction of propagation).

I think the core issue here is: the user will not want to reuse the same operator for a forward AND backward run (although this works for the acoustic wave equation, it is not generally helpful). By removing the reverse parameter and allowing the user to choose direction at apply time, we are jumping through a lot of hoops to provide a piece of functionality that is not required.

I entirely agree. In fact direction really only matters for time, whereas the ability to dynamically define ranges at runtime might be incredibly usefull for things like sub-domain traversals (eg. sub-regions or BCs over parts of a boundary). So I think there is little harm in not generalising direction, but sub-ranges should be available for general dimensions.

Agreed.

This, I believe, should have been closed a long time ago.

I didn't close it because points 2. and 3. were still missing, but if we don't need them, yeah, pls go ahead and close it


ERROR:  Unable to add login credentials for the gitops registry

Environment
Device and OS: OSX v12.4 (Intel)
App version: v0.19.6
Kubernetes distro being used: v1.22.9-eks-a64ea69
Other: Docker Desktop v4.9.1
Steps to reproduce

ensure Docker desktop is NOT running
zarf init

Expected result
zarf init does it's thing
Actual Result
    ERROR:  Unable to add login credentials for the gitops registry
Visual Proof (screenshots, videos, text, etc)

Severity/Priority
High
Additional Context
Confirmed bug in debugging session with @jeff-mccoy and @YrrepNoj

Fixed by #586


Lightning module vs. torch model standardization

Currently some classes don't expect a lightning module(ClassDetection benchmark for example) and there are some discrepancies within classes (LDS benchmark should be expecting both and checking that trainer and model objects are both Lightning or both plain torch).
We should go through the code and make sure to unify this

Another example: Metrics require torch.nn.Module but we allow for Benchmarks to pass Lightning modules to metrics


px-map-marker-static colors behaviour on different types

I tried using the 4 types, important, warning, info and unknown to color code some sites.  The documentation indicates a different color for each type. For the unknown and info the results are what i would expect, different colors . But for information and warning what looks like two markers for each location are put in the normal marker plus a triangle next to it. This is very confusing it looks like there are 2 separate markers representing sites next to each other.
The results was very odd and does not seem to agree with the documentation at the least, seems like a bug to me. The px-map-marker-symbol has the same behaviour which is even stranger considering the developer is setting the symbol-class, effectively it is overwriting what the developer has choosen.
Related it would be a nice enhancement to be able to put in a legend to indicate what the colors mean.

It isn't a bug, those marker types were specified by our design team to echo the alert icons used in px-alert-message, px-inbox, etc. Thanks for your feedback, we'll pass it along to the design team as something to reconsider.

I checked px-inbox they have a different color and shape (square, diamond, triangle and circle)  for the 4 states. Having 4 different shaped markers would be ok on px-map in my opinion. On px-map there are 2 states that vary by color and two states that have what appears to be two icons, a raindrop and triangle, representing them. This may not be a bug but really needs to be changed in some fashion.

The marker states work as designed. I'm going to close this for now.


More informative errors on plift

The constructors for ReadKnownError aren't exported, but some prisms are. https://github.com/input-output-hk/plutus/blob/0397f83b8298ba1b3c531511172637651b624164/plutus-core/plutus-core/src/PlutusCore/Builtin/KnownType.hs#L158

Is it ok to add the lens dependency for tackling this?

We already depend on lens indirectly.


JSON-RPC request reduction - polling interval change

This reducing polling for balances and APR from 5s to 30s.  Slight improvement that will hopefully reduce the rate limiting we're seeing from Alchemy.
I think this is probably good for now but it does impact things like the balance ticker, and how quickly we notice an approval/balance change, so there's a UX impact here.  Perhaps there's a more intelligent way of doing this that requires a bit more of a UI change?
CC: @micahalcorn @franckc

Closing this in favor of https://github.com/OriginProtocol/origin-dollar/issues/240#issuecomment-698129245 🙂


FR: scaled_xy_accel support for limited_cartesian

The axis limiter is for an out-of-tree Klipper feature, limited_cartesian kinematics with per-axis limits. However the good version of this feature has the capability to treat the per-axis acceleration limits as relative to the current M204 acceleration rather than global limits. It would be nice if klipper_estimator supported this convention too.

Hi @richfelker
I'm not aware of how this works?
Best regards,
Lasse

See https://github.com/Piezoid/klipper/blob/work-peraxis/klippy/kinematics/limited_cartesian.py
The idea is that if one is using acceleration limits to control toolpath deviation/ringing/etc., the per-axis limits reflect differences in mass or stiffness of the axes. For example, if Y deviates ~4x as badly as X for a given acceleration, it's desirable to have Y acceleration 25% of X acceleration, but setting a low absolute limit on Y acceleration would cost a lot in print time for no benefit when you really only care about the deviation on outer walls. Having the Y accel limit scale as a % of M204 acceleration rather than being an absolute limit handles this in a continuous way and is also likely to represent the scaling of acceleration before steps are missed at very high M204 accel, too.

Hi @richfelker
Okay I think I understand. This shouldn't be too difficult to do, I'll take a look. I'm thinking of adding a scaled version of the current axis limiter to cover this use case.
I'll post a PR you can test out when I have it done.
Best regards,
Lasse

Hey @richfelker
I've taken a stab at this, please check the https://github.com/Annex-Engineering/klipper_estimator/tree/limited_kinematics branch.
I currently have no working printer, so testing this is a bit annoying. Hopefully you and Piezo can test it out for me :-)
Best regards,
Lasse

Note that the SCV fix (76ba4bee) is not implemented, as there is no way to detect if users have it from the config.
Possible solutions:

Add a config option to toggle the fix. It must be disabled by default to assure that it is enabled if and only if the config say so. Also supporting both modes will increase the code complexity.
Assume that every user of limited_ kinematics have the SCV fix, update install instructions to reflect that. But then, I won't be able to support beacon/z_calibration style install if the changes to klippy code are no longer optional.
Upstream it, since it shouldn't change the behavior outside of the use of limited_ kinematics. It won't be easy to find argument for a change intended to support external, unsuported code.


Add Syntax Hightlighting to Readme

This adds syntax hightlighting to the readme by using triple backtick code blocks

Thanks for chipping in, @N0tExisting!


Clean up imported packages

[ ] tidyverse, just need component pkgs, dont get whole thing
[ ] paws, afaik not used
[ ] data.table, afaik not used

@sckott -- Looks like you made some commits to address this, safe to close? Or is there more cleanup to do?

yeah close