Unable to enumerate monero based apps

Recently, I updated my copy of the repo with the latest code and attempted to retrieve the address from my monero app as a test and I keep receiving the following message.

I have confirmed that the app is working normally using the monero gui and cli wallet. This happens with other apps that are based on monero as well.

Monero is not supported by this project.

If it is not supported, why was I able to use it with previous version of the monero app and monero based apps?

If it is not supported, why was I able to use it with previous version of the monero app and monero based apps?

I don't know. HWI was not and is not tested with nor designed for anything other than the Bitcoin app. Any other app working with it is a coincidence and you should not rely on it working for anything else.


install failure

libraries/haste-lib/src/Haste/Compiler.hs:37:20:
Not in scope: ‘genericRun’
rhel 7

was caused by incompatible deps versions


Guide for hekate

can you add a guide to use hbl on 5.0.x via the hekate method

I won't be supporting half-finishes CFW options. Be patient and wait for Atmosphère.


Chinook Pass (and maybe others) crashing

I think this may be related to the accumulated snowfall column but I need to dig in a bit

This is actually related to one of the 2 weather stations at Chinook Pass not having data points for each time 😬

The root cause of this issue (and the thing that's still broken) is that TimeSeriesTable assumes that the date_time arrays will be the same when fetching observations for multiple weather stations at once. That's not the case! 🤮
This is a url that demonstrates the issue: curl 'https://api.snowobs.com/wx/v1/station/data/timeseries/?stid=32%2C33&source=nwac&start_date=202303080200&end_date=202303090200&units=default&output=mesowest&calc_diff=false&raw_data=false&token=71ad26d7aaf410e39efe91bd414d32e1db5d'. The "Chinook Pass Summit" station has 24 entries but the "Chinook Pass Base" station is missing 12 entries in the middle.
I guess one solution is to build a complete list of date_time entries in advance, set up the rows and then start iterating over the observations for each station. Maybe there's a more elegant way though.


Rename layer_geometry_type to geometry_type

Resolves #114
As discussed on 6/2/2022 GeoPandas dev team call; renaming for consistency throughout (layer_geometry_type was used only in geopandas I/O functions; geometry_type is used on other places).
Includes minor formatting cleanup of test file, sorry!

@jorisvandenbossche ping for review; would like to get this merged relatively soon (provided we want this change) so I can cut an 0.4.0b1 release today or tomorrow


Gif preview in AnimateDiff Combine -node

Hacked this together using mtb node's gif preview in their "Save Gif" -node. Javascript seems necessary for the functionality.
All the necessary js (and probably lot of unnecessary) is in one file and  "init.py" is modified to load the .js.
Some modifications in the nodes.py to add pingpong generation option and to match the .js requirements.
So far everything seems to work, node resizing is not perfect, but it wasn't in the original code either. To me this works better than the Save Gif node as it keeps the node size as it should between generations, unlike the original.
https://github.com/Kosinkadink/ComfyUI-AnimateDiff-Evolved/assets/40791699/26a0d4ed-8b0d-49b8-828e-39b76331d3cd

Thanks! I'll take a look at this tonight.

The current pingpong code duplicates the first and last frame. While this may be a matter of preference, you'll get a smoother loop with
frames += frames[-2:0:-1]

The current pingpong code duplicates the first and last frame. While this may be a matter of preference, you'll get a smoother loop with
frames += frames[-2:0:-1]

Oh indeed, good catch, that's preferable.

I've finshed the code for video format configuration, but I'll likely hold off on opening a pull request until this one is merged for clarity.

Attempting to add lossless version of Webp failed

Would you mind providing more insight on what you had difficulty with, @arilss?
Visual quality is configured with the -crf flag in ffmpeg. The video format code I've written (available here, but not included in the current pull request)  has -crf values for each of its formats that should be visually lossless,
The default vp9 encoder for webm is the least well defined, but -crf 19 is my safe guess for lossless quality. My personal recommendation is to use the av1-webm format , which in my limited testing, is providing visually lossless webm animations for 1/4 the size of a single constituent png frame.

        # save webm
        ffmpeg_path = shutil.which("ffmpeg")
        if ffmpeg_path is None:
            raise ProcessLookupError("Could not find ffmpeg")
        file_webm = f"{filename}_{counter:05}_.webm"
        file_path = os.path.join(full_output_folder, file_webm)
        dimensions = f"{first_image.width}x{first_image.height}"
        args = [ffmpeg_path, "-v", "panic", "-n", "-f", "rawvideo", "-pix_fmt", "rgb24", "-s",
                dimensions, "-r", str(frame_rate), "-i", "-", "-pix_fmt", "yuv420p", file_path]

Rewrite the file directly on the server
Replaced webm with webp
I tried changing the compression command but it failed so I deleted the file.
--
“sd-webui-animatediff” also appears to have mp4 and webp video format extensions in the pull request.
I think we need to decide whether to split up or create a similar program.
The video compression program also appeared to be a compression program that did not use ffmpeg.
I'm planning to try out Austin Mroz's new video compression style starting today.

Apologies, I had misread that you were wanting a webp and not a webm
Now that I've tested it, I seem to be running into the same issue you are with using ffmpeg to generate an animated webp. As you mentioned, the upstream repository, "sd-webui-animatediff" uses Pillow (a python image library already in the requirements) to generate animated webp outputs, and I think this is a better solution as it allows users to get higher quality outputs even if they don't have ffmpeg installed, but it still uses the ffmpeg code from here for webm support.
Since the upstream repo has merged the features of this pull request, I'll open a pull request there to merge the video format changes I've made (which are unrelated to webp support)
It seems the maintainer of this repo, kosinkadink, is working on some backend changes, so I'm willing to wait patiently on merging the changes in this request until he is ready.

Hey, sorry for the delay, tonight I am finally finishing up the sliding context window functionality - once I have that merged into main, I will work with you guys to get this merged in here! I've got a lot of nodes planned for AnimateDiff and Advanced-ControlNet, so this week a lot of functionality will be added here.

The develop branch is almost in a state where I'll be merging it into main soon - if you can check if this PR is compatible with it, that should help with the merge! Right now I just need a few hours of sleep so I can finish the rest of what needs to be done. I appreciate the work you guys did here 👍

Alrighty, my sliding context windows changes have been pushed into main. Gifs are too big to include in the README,, so I will merge this in so I can finish the README examples haha. Does this require any dependencies if not using the video nodes? I want to make sure I don't brick the nodes for 95% of the users

Imma ball instead, I'm merging 😎

There's no additional python requirements. Video outputs require that ffmpeg is installed and in the system PATH.
If ffmpeg isn't available, an error is raised on execution if the selected format (video/webm) requires it, but the code could easily be changed to instead hide the formats that require ffmpeg if it's not detected.
I'll also open the pull request for the video formatting configs as the safe defaults that this pull request used are probably defaulting to a high crf (35).


doc: Helm guide instructions for installing cilium on AKS

Update helm instructions for installing cilium with byocni on AKS and remove instructions for installing with azure-ipam.
Depends on this PR: #28933
Related: #27289
Please ensure your pull request adheres to the following guidelines:

[ ] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[ ] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[ ] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Are you a user of Cilium? Please add yourself to the Users doc
[ ] Thanks for contributing!

Fixes: #issue-number
<!-- Enter the release note text here if needed or remove this section! -->

this PR #28933 has these changes.. so closing it


Support mjs files as entrypoints

The node-start buildpack at the moment looks just for js files as start scripts, https://github.com/paketo-buildpacks/node-start/blob/v0.8.1/node_application_finder.go#L32. If I use ECMAScript modules and therefore import statements and name my file with mjs as extension, then it won't work.
A sample code repository that today cannot be built is https://github.com/SaschaSchwarze0/dump-headers.
Describe the Enhancement
Extend node-start to also look at mjs files.
Possible Solution
This must be extended at those places:

https://github.com/paketo-buildpacks/node-start/blob/v0.8.1/node_application_finder.go#L32
https://github.com/paketo-buildpacks/paketo-website/blob/main/content/docs/howto/nodejs.md

Motivation
Adoption of ECMAScript modules is growing.

I can take a look at this as a follow on to https://github.com/paketo-buildpacks/libnodejs/pull/8
@SaschaSchwarze0 is your suggestion just that it looks for the same files with an mjs extension in addition to the .js ones ?
One question is also how it should affect the ordering.  My first take would be same ordering in terms of server, app etc. but look for both .js and .mjs for each before moving to the next.  Does that make sense to you?

One question is also how it should affect the ordering. My first take would be same ordering in terms of server, app etc. but look for both .js and .mjs for each before moving to the next. Does that make sense to you?

Makes sense, yes. Thank you.

@nodejs/maintainers does what I outlined in https://github.com/paketo-buildpacks/node-start/issues/225#issuecomment-1532024712 sound good to you? If so I'll submit a PR once some of the existing ones I have open land.

opps wrong mention
@paketo-buildpacks/nodejs-maintainers does what I outlined in https://github.com/paketo-buildpacks/node-start/issues/225#issuecomment-1532024712 sound good to you? If so I'll submit a PR once some of the existing ones I have open land.

A sample code repository that today cannot be built is https://github.com/SaschaSchwarze0/dump-headers.

But can't you simple add the environment variable BP_LAUNCHPOINT=server.mjs. Works for me.

A sample code repository that today cannot be built is https://github.com/SaschaSchwarze0/dump-headers.

But can't you simple add the environment variable BP_LAUNCHPOINT=server.mjs. Works for me.

Yep, this is more about what works ootb without that you must customize something. Is imo hard to explain that you evolve your app to modules, by that use mjs as extension and suddenly the build does not work anymore (without env customization).

This dropped off my radar, will try to get back to it.

Submitted - https://github.com/paketo-buildpacks/libnodejs/pull/31 as the first step. Once that lands we can add some additional testing into this buildpack to validate the .mjs cases.


About the predict.py

Hello, when I run the predict.py, there is something wrong with the code. It seems like the input size is not matching.

Hi, Cong Zhang
The problem may be in the wrong version of the torchvision library. I used version v0.4.1. Please see the Dockerfile for the exact environment.


When connecting with Remote-SSH and using "Download" of the file, the file name field becomes blank

VSCode Version:  1.50.1
OS Version: Client: Windows10 2004 (19041.508), Server: Ubuntu18.04.5

Steps to Reproduce:

Connect to the server using Remote-SSH
In Explorer on the side menu, right-click the file and select "Download".
The file name in the server is not retained, and you need to enter a new file name in the save dialog.

Does this issue occur when all extensions are disabled?: Yes/No
Yes (Remote-SSH is enabled because this bug is due to Remote-SSH. No other extensions are installed.)

Dup of https://github.com/microsoft/vscode/issues/83433


Add compat-libstdc++-33-3.2.3-61.i386

It is required for some older HLDS addons (.so files) that need this library to work.
http://www.rpm-find.net/linux/RPM/www.startcom.org/AS-5.0.0/updates/i386/compat-libstdc++-33-3.2.3-61.i386.html
Egg: https://github.com/parkervcp/eggs/tree/master/steamcmd_servers/hlds_server
Image: quay.io/parkervcp/pterodactyl-images:ubuntu_source

Uhh I don't think you did that correctly


NUMBERS-143: Added specialised hypot function to Complex.

The new implementation is faster and has lower maximum error than using
Math.hypot.
This is a port of the "Freely Distributable Math Library" hypot
function. The original source notice is included in the project LICENSE.
The functionality of Complex.abs should match Math.hypot for infinity
edge case handling and scaling of the intermediate sum. Tests have
been added to the CStandardTest to check the returned value on random
numbers.
Update Complex performance test for Complex.abs().
Add tests for Math.sqrt(Complex.norm()) and use of Math.hypot().
Increase size to 10000 to prevent branch prediction memorising the test
data.
Exclude PMD rule ExcessiveMethodLength for Complex.

Coverage increased (+0.02%) to 98.411% when pulling f39fbe9e438dcea7df4f28f7c9c3e00921bc572f on aherbert:numbers-143-feature into 81c2fd3d763afdae3cadc711b220e6ded9f7fd36 on apache:master.


Where to host Release Agent? On Dedicated or Target Server

In case I have high available load balanced production environment, which one is better to install release agent on each production server or to have dedicated release agent which deploy to all servers?
[Enter feedback here]

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

ID: 47625b86-abd5-ee15-6d61-8bcf81861b96
Version Independent ID: be9a6174-a69b-7aed-d584-5f602fcc5eb4
Content: Azure Pipelines Agents - Azure Pipelines
Content Source: docs/pipelines/agents/agents.md
Product: devops
Technology: devops-cicd-agents
GitHub Login: @steved0x
Microsoft Alias: sdanie

@RiadKatby Thank you for the question.
This issue really becomes measuring the time it takes to process a build versus that combined with the network latency in transferring the job.  Any added complexities in build steps, server count, etc. becomes a matter of a preference.
In general, increase server load before the server count so to avoid unnecessary complexity.
For more advice on specific build configurations, please refer to Azure DevOps support.


[Port dspace-7_x] DS-7936: remove optimize option (-o) from oai import

References

Backport of https://github.com/DSpace/DSpace/pull/9081
Fixes #7936

Checklist

[X] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
[X] My PR passes Checkstyle validation based on the Code Style Guide.
[X] My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
[X] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
[X] If my PR includes new libraries/dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[X] If my PR modifies REST API endpoints, I've opened a separate REST Contract PR related to this change.
[X] If my PR includes new configurations, I've provided basic technical documentation in the PR itself.
[X] If my PR fixes an issue ticket, I've linked them together.

@nwoodward : Just a brief note.  We have mostly "automated" the backport process these days via a GitHub action & port to [branch-name] labels.  So, small PRs can often be ported automatically... we only require these (manual) port PRs for larger work where needed.
I just want to make sure you were aware that these manual ports are optional now.  You are welcome to still create them if you wish, but you often don't need to (unless we ask for your help on one).

@tdonohue Thanks for letting me know. I thought I'd read something about that, but I couldn't tell if it was happening. Do I need to do something particular with the PR to kick off that process, or does it happen automatically with all of them?

Thanks @nwoodward! I tested the patch and it removes the -o option. The import function still works as expected.

Do I need to do something particular with the PR to kick off that process, or does it happen automatically with all of them?

@nwoodward if you add the port to main or port to dspace-7_x label (before merging), the bot will attempt to port the pull request by cherry picking the commits.


Added 2 small fixes that were mentioned after my previews PRs got already merged.  (First is about adding Guard.NotNull, mentioned by bokobza here https://github.com/stratisproject/StratisBitcoinFullNode/pull/732, second is about accidentally deleting '<' mentioned by aprogiena in slack's pm)

Let me check this one

Looks good to me lets wait for @Aprogiena to review.

@dangershony rather than readme file, i'd suggest having an external knowledge base
but i'd not be happy to duplicate the information from class comment into that or readme file, you will find the comment will change in one source and won't in other source, then you have a mess

Fixed everything but this

empty comment is not a good one ;)
Because I'm not sure yet what this one actually does. Will add comment when I'll be doing comments for this class.

Also new names for the variables and functions might be considered a bit long, but at least they represent the purpose much better.
So let me know what you think =)

ok, you have a conflict here, can you resolve?
i know you don't know what that one is, that was the point :) look at BlockAssembler class and how GenerateBlock is called, it might help:
                    this.powLoop = this.powMining.Mine(BitcoinAddress.Create(minto, this.network).ScriptPubKey);

->

                BlockTemplate pblockTemplate = this.blockAssemblerFactory.Create(chainTip).CreateNewBlock(reserveScript.reserveSfullNodecript);

->

        public abstract BlockTemplate CreateNewBlock(Script scriptPubKeyIn, bool fMineWitnessTx = true);

->

        protected virtual void CreateCoinbase()
        {
            // Create coinbase transaction.
            // Set the coin base with zero money.
            // Once we have the fee we can update the amount.
            this.coinbase = new Transaction();
            this.coinbase.AddInput(TxIn.CreateCoinbase(this.ChainTip.Height + 1));
            this.coinbase.AddOutput(new TxOut(Money.Zero, this.scriptPubKeyIn));


Make reasonable bootstrap logging

Codecov Report

Merging #1 (d66e774) into master (2197636) will decrease coverage by 0.96%.
The diff coverage is 48.71%.

@@            Coverage Diff             @@
##           master       #1      +/-   ##
==========================================
- Coverage   82.73%   81.76%   -0.97%
==========================================
  Files          36       36
  Lines        3017     2879     -138
==========================================
- Hits         2496     2354     -142
- Misses        419      421       +2
- Partials      102      104       +2

Impacted Files
Coverage Δ

boot/prom_entry.go
90.24% <ø> (+2.10%)
:arrow_up:

boot/static_file_handler_entry.go
75.00% <ø> (-3.19%)
:arrow_down:

boot/sw_entry.go
72.43% <ø> (-4.45%)
:arrow_down:

interceptor/context/context.go
86.13% <ø> (ø)

interceptor/jwt/options.go
79.41% <ø> (ø)

boot/echo_entry.go
62.11% <44.44%> (-3.14%)
:arrow_down:

boot/common_service_entry.go
83.78% <100.00%> (+0.45%)
:arrow_up:

boot/tv_entry.go
59.71% <100.00%> (-5.97%)
:arrow_down:

Continue to review full report at Codecov.

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


Missing stuff in Adobe XD UI kit (progress ring and title bar)

In earlier versions we could see the App Titlebar with minimise, restore and close buttons, it is absent.
Also missing is the ProgressRing control.
There is no taskbar either.

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

ID: d9fc7b1d-8b97-598a-f059-093d94972931
Version Independent ID: 943e9c97-f223-4d3c-730c-a7f20cb04560
Content: Design toolkits and samples for UWP apps - UWP app developer
Content Source: windows-apps-src/design/downloads/index.md
Product: windows
GitHub Login: @mijacobs
Microsoft Alias: mijacobs

Thanks for the feedback--I've passed it on to the folks who create the toolkits. I'll let you know when an update is ready.

The .PDF included with the XD download lists<EMAIL_ADDRESS>as the email address to use for feedback like this.

I'm also looking for the Windows 10 title bar in the Adobe XD toolkit

@sguergachi : By Windows 10 title bar, do you mean the app title bar?

Yes

Sammy Guergachi

From: Mike Jacobs<EMAIL_ADDRESS>Sent: Tuesday, August 28, 2018 5:13:47 PM
To: MicrosoftDocs/windows-uwp
Cc: Sammy Guergachi; Mention
Subject: Re: [MicrosoftDocs/windows-uwp] Missing stuff in Adobe XD UI kit (progress ring and title bar) (#737)
@sguergachihttps://github.com/sguergachi : By Windows 10 title bar, do you mean the app title bar?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windows-uwp/issues/737#issuecomment-416742635, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAlj2hnj_IS93to0qxFRJX0WdFZ2xoXZks5uVbKLgaJpZM4U-QgM.

The virtual keyboards are also missing from the xd file.

The latest updates should fix these issues, please re-open if that's not the case.
https://docs.microsoft.com/en-us/windows/uwp/design/downloads/


Small editorial change to the Feature Extension spec text.

Signed-off-by: David Bosschaert<EMAIL_ADDRESS>

how could it be handled to use the same extension multiple times with different configurations?
like with the config.factory.pattern~here?

Hi @stbischof it should depend on the actual extension whether multiple instances of it make sense.
I can see that it would make sense if you for example have an extension that defines validation rules for configuration to have multiple instances of those. However the extension mechanism itself already supports multiple values (in this case you could use a JSON extension that is an array of JSON objects, one for each validation rule), so registering the extension itself multiple times would not be needed.
On the other hand having multiple instances doesn't make sense for some other extensions. For example an extension that specifies the framework launcher properties to be set only makes sense to be there once.
An extension already defines how it interprets its provided definition. By letting the extension itself define whether it can handle multiple values in its content you basically already ensure that only multiple values can be specified for the extension when it makes sense, and you won't end up with situations where multiple values are specified in cases where it doesn't make sense.
At least this is my experience.
On the other hand if there is a strong use-case for this, we could quite easily add this in a future version. Given that we are so close to the deadline I would suggest not to add this new concept right now.

Fully agree to not handle it in this release. Just want so speak it out to be sure we have the options to do more later.


Further attribute set copy constructor fixes for non constant strides

Copy of  #406

Creating a new PR hasn't fixed it. I found this https://circleci.com/docs/2.0/workflows-waiting-status/ but as others aren't having this issue I assume it's unrelated? I'm going to try setting up Circle on my fork, but it's pretty ridiculous that I have to give circle read and write access to all organisations and private repositories I'm a member of (travis is the same) and, from what it looks like, set up circle jobs specifically on forks of repositories I want it to run on. Seems to only like running on local branches https://circleci.com/gh/AcademySoftwareFoundation.
Doesn't look Appveyor needs any of this? Are we expecting other users to have to go through this process too?

Creating a new PR hasn't fixed it. I found this https://circleci.com/docs/2.0/workflows-waiting-status/ but as others aren't having this issue I assume it's unrelated?

I don't think this is related.

I'm going to try setting up Circle on my fork, but it's pretty ridiculous that I have to give circle read and write access to all organisations and private repositories I'm a member of (travis is the same) and, from what it looks like, set up circle jobs specifically on forks of repositories I want it to run on. Seems to only like running on local branches https://circleci.com/gh/AcademySoftwareFoundation.
Doesn't look Appveyor needs any of this? Are we expecting other users to have to go through this process too?

No, I expect that any PR will use the ASWF Circle account (and allowance) for builds and not require you to need to sign up to Circle. That does appear to be the case from what I can tell. It seems like this issue is specific to you for some reason, I only suggested signing up to Circle in case it helped us understand what was going on, I don't think it's the solution.
Appveyor and Circle work quite differently. Appveyor has it's own limitations in that it doesn't understand GitHub organizations so you have to have it tied to a specific GitHub user account.

It seems like this issue is specific to you for some reason, I only suggested signing up to Circle in case it helped us understand what was going on, I don't think it's the solution.

Signing up for circle seems to have fixed it but I'm still not sure why. Lets get this in for 6.1 then take another look at this.

It seems like this issue is specific to you for some reason, I only suggested signing up to Circle in case it helped us understand what was going on, I don't think it's the solution.

Signing up for circle seems to have fixed it but I'm still not sure why. Lets get this in for 6.1 then take another look at this.

I encountered this issue myself (https://github.com/AcademySoftwareFoundation/openvdb/pull/418) despite having circle installed on my own fork, so it's probably just coincidence that re-submitting the PR after signing up for circle resolved the issue for you.
On investigation, I think it might be related to us using the old GitHub Commits API for the ASWF rather than the new GitHub Checks API, so I've mailed Andrew/ASWF HelpDesk to ask about enabling it.


Refactor the Code

Created a class to refactor all the code...
The code looks good now

Will take a look deeply! thank you very much : )

Saw your merged, what next for the package


Publish 7.6-20221105002636+0000

Publish 7.6-20221105002636+0000

@bot-gradle test and merge

OK, I've already triggered a build for you.


Extension crashes with indicator.get_parent() is null

Hello Andia89,
Within the last two weeks the extension has been crashing. It seems to happen after I unlock my screen. The error in Extension Manager is "indicator.get_parent() is null"
I am using Ubuntu 22.04lts.
Thanks for creating this extension. And, thank you for looking into this issue.

It happens to me too on Fedora 40 with Gnome 46.
Some log from journalctl of it can help.
gnome-shell[6145]: Object St.Bin (0x561357ff5810), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
                                             == Stack trace for context 0x56135795b900 ==
                                             #0   7ffef1331330 b   file:///home/<user>/.local/share/gnome-shell/extensions/order-extensions@wa4557.github.com/extension.js:94 (3e037e4d4e20 @ 219)
                                             #1   561357a22008 i   resource:///org/gnome/shell/ui/init.js:21 (37d074570bf0 @ 48)
audit[6145]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=6145 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=11 res=1
kernel: show_signal_msg: 47 callbacks suppressed
kernel: gnome-shell[6145]: segfault at 8 ip 00007f2d454b3af0 sp 00007ffef1330c70 error 6 in libmutter-clutter-14.so.0.0.0[3baf0,7f2d4549d000+8f000] likely on CPU 4 (core 8, socket 0)

I tried the following patch.
In extension.js, replace:
        let box = indicator.get_parent().get_parent();
        if (box == undefined) continue
        this._addToPanelBox(role, indicator, 0, box)

With:
        {
            let box = indicator.get_parent().get_parent();
            if (box == undefined) continue
            this._addToPanelBox(role, indicator, 0, box)
        }

I got no crash since.


Enhance Traditional Chinese translation

Correct some machine translation mistakes, and convert Mainland China's regional expression to Taiwan.
Pull Request Checklist

[x] Description: Briefly describe the changes in this pull request.
[ ] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?

Description
[Insert a brief description of the changes made in this pull request]

Changelog Entry
Added

[List any new features or additions]

Fixed

[List any fixes or corrections]

Changed

[List any changes or updates]

Removed

[List any removed features or files]

Thanks!


@2.7.34 no select2

from some reason select2 did not published to npm via setassets commands?

fixed in 2.8.2


Migrated from npm to pnpm

Description
Please explain the changes this PR addresses here.
Checklist

[ ] If this requires a documentation change, I have created a PR that updates the mkdocs/docs directory
[ ] If this requires it, I have updated the Readme
[ ] If necessary, I have updated the examples
[ ] I have verified if I need to create/update unit tests
[ ] I have verified if I need to create/update acceptance tests
[ ] If necessary, I have run acceptance tests on this branch in CI

I have a problem when trying to link
@moonbeam-network/mrl:link: @moonbeam-network/mrl:link: ><EMAIL_ADDRESS>link /home/mmaurello/gitData/xcm-sdk/packages/mrl @moonbeam-network/mrl:link: > pnpm ln @moonbeam-network/mrl:link: @moonbeam-network/xcm-config:link:  ERR_PNPM_LINK_BAD_PARAMS  You must provide a parameter @moonbeam-network/xcm-builder:link:  ERR_PNPM_LINK_BAD_PARAMS  You must provide a parameter @moonbeam-network/xcm-config:link:  ELIFECYCLE  Command failed with exit code 1. @moonbeam-network/xcm-config:link: ERROR: command finished with error: command (/home/mmaurello/gitData/xcm-sdk/packages/config) /home/mmaurello/.nvm/versions/node/v20.12.2/bin/pnpm run link exited (1) @moonbeam-network/xcm-builder:link:  ELIFECYCLE  Command failed with exit code 1. @moonbeam-network/xcm-config#link: command (/home/mmaurello/gitData/xcm-sdk/packages/config) /home/mmaurello/.nvm/versions/node/v20.12.2/bin/pnpm run link exited (1)

You are right, it works a bit differently then in NPM https://pnpm.io/cli/link#use-cases. It might be that to use it in our other projects we need to migrate to pnpm them too. But I will check this later. I will find a solution later. For now is important that we can build.


167: Added filtering for Networks

PR for #167

@lumimul Looks good, thanks!

@rultor merge it please

@rultor merge it please

@amihaiemil OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge it please

@amihaiemil Done! FYI, the full log is here (took me 2min)

Job gh:amihaiemil/docker-java-api#336 is not assigned, can't get performer


 and

Hey gusy, I finally got some spare time to look into this now. Thanks a lot for putting this together!
I'm looking at the symbol tables fro words and characters. I noticed that 0 was reserved for  in words.txt, but was used for  in characters.txt. As a results, in the resulting SG.fst graph, on the output side you have separate  and  symbols, while on the input side, you have a mixed  and  symbol. This is because OpenFST treat 0 as epsilon in all algorithms by default.
Shall we reserve 0 for  as long as OpenFST is involved? This requires changes to both Athena and Athena-decoder. Correct me if I'm wrong though. @tjadamlee @godjealous

Hey gusy, I finally got some spare time to look into this now. Thanks a lot for putting this together!
I'm looking at the symbol tables fro words and characters. I noticed that 0 was reserved for in words.txt, but was used for in characters.txt. As a results, in the resulting SG.fst graph, on the output side you have separate and symbols, while on the input side, you have a mixed and symbol. This is because OpenFST treat 0 as epsilon in all algorithms by default.
Shall we reserve 0 for as long as OpenFST is involved? This requires changes to both Athena and Athena-decoder. Correct me if I'm wrong though. @tjadamlee @godjealous

Thanks for your interest in athena-decoder project.
Actually, we always reserve 0 for epsilon on the input side and output side in WFST.  As you have mentioned, symbol 0 is reserved in file words.txt. Symbol 0 is also reserved in file characters_disambig.txt.
The input symbol table for SG.fst graph is file  "characters_disambig.txt" rather than the file "characters.txt". The output symbol table for SG.fst graph is file "words.txt".
Compared with file "characters.txt", file "characters_disambig.txt" contains some extra information including epsilon symbol and some disambiguate symbols.


File transfer in base64 over metacom

Landed in https://github.com/metarhia/Example/commit/66a74e1e7ab2eda2e5c0b30d21cd0c2f4c390538


IIS Sysprep Compatibility Needs More Details

Issue Details
Fix "Applies To:" in http://technet.microsoft.com/en-us/library/dd744581(v=ws.10).aspx
The article says Sysprepping is not supported if there are "encrypted credentials", but there's no reference about how to identify this scenario.  Can this detail be added to the document?  Thanks

@TaraMeyer Is there anything you can help here?

@TaraMeyer Can you response if you are the right person to contact? @themar-msft @joshhbax-msft for awareness.

@Powerhelmsman - I'm sorry for my late response, thank you for sending me an email and bringing to my attention.  I'm forwarding you the contact information of the content owner.  You'll need to work with her as to how to get this content updated.  Thanks!

Hi @BGaudreault-EDR , thanks for the comment. You can learn about IIS encrypted accounts here - that article includes some ways to validate that passwords are encrypted. Other than that, we'd recommend checking out the IIS library as a whole. Thanks!

Thanks @lizap! Closing this issue, as the information was provided above.


fix: nonfunctional alteration submission and misc. oversights in date overlap detection

Description :sparkles:
It looks like I broke the submit button in the last PR by accident at the last minute while fixing a code quality violation reported by sonarcloud.
I basically went from handleAlteration: formik.submitForm to handleAlteration: () => void formik.submitForm which actually doesn't call the function anymore.

API branch is deployed to platta: https://helsinkilisa-pr3068.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://helsinkilisa-ui-handler-pr3068.dev.hel.ninja :rocket::rocket::rocket:

APPLICANT branch is deployed to platta: https://helsinkilisa-ui-pr3068.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://helsinkilisa-ui-handler-pr3068.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://helsinkilisa-ui-pr3068.dev.hel.ninja :laughing::tada::tada::tada:

API branch is deployed to platta: https://helsinkilisa-pr3068.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

APPLICANT branch is deployed to platta: https://helsinkilisa-ui-pr3068.dev.hel.ninja :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://helsinkilisa-ui-handler-pr3068.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://helsinkilisa-ui-pr3068.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://helsinkilisa-ui-handler-pr3068.dev.hel.ninja :laughing::tada::tada::tada:

HANDLER branch is deployed to platta: https://helsinkilisa-ui-handler-pr3068.dev.hel.ninja :rocket::rocket::rocket:

APPLICANT branch is deployed to platta: https://helsinkilisa-ui-pr3068.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://helsinkilisa-ui-handler-pr3068.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://helsinkilisa-ui-pr3068.dev.hel.ninja :laughing::tada::tada::tada:


Workaround for render-lifecycle performance issues?

Hi all,
My team has implemented a very thin wrapper around the FixedDataTable in which we track an "active" row and use the Table's rowClassNameGetter prop to supply the proper active class to the correct row.  We have noticed that on tables with ~8 columns and 100 rows we cannot quickly change the active row this way as it starts to be laggy.  After checking out some CPU profiles in Chrome, we've ruled out our end of things (no multiple event handlings, no multiple renders, we're using PureRenderMixin), and we've seen the vast majority of time is spent in what looks like the render lifecycle of the Table (with a vast majority of that being stuff that looks like ReactDOMComponent.Mixin.receiveComponent).
This performance is improved in a production node environment, however still not performant enough to ship in our opinion.
We would like to handle 3 separate but similar tracked states like this – hovered row, active row, and selected rows.  We understand that we can see performance improvements with using css :hover effects for the hovered state (although that would preclude us from some other fancier things), but the perf issues still exist for active row and selected rows.
Has anybody else tried / noticed something like this?  Is there another methodology we should be attempting?  Thanks!

I also noticed a similar issue, any feedback would be much appreciated!

I noticed a performance problem in FixedDataTable's api-v0.5 branch which was later converted to version 0.6. See https://github.com/facebook/fixed-data-table/pull/221#issuecomment-145412983
I am not sure if it is fixed or not in 0.6.


explode clones element with differing position value

.lm-container is position: fixed, but gets cloned with a hardcoded value of position: absolute.
This causes the clone to jump upwards in our application, since it's position is now relative to a different, positioned parent.

Going to position: absolute is part of the point, so that it's easily animatable. The real bug here is probably that we aren't adjusting the top and left correctly so that the visual position remains constant.

Seconding. I'm animating spans in a label on my personal site ( ⚠ WIP) joedaniels29.github.io and I found that I had to set top:0 !important because it would jump up otherwise. Is this something a newbie can help fix?

@joedaniels29 if you want to take a stab at it, try breaking here to figure out why the top and left are incorrect in your app.


AT => AP: Quote post of not-bridged guest-visible adult content results in adult content in embed without CW

It's definitely an edge case, but if on Bluesky

A isn't bridged,
A's posts are web-visible without login,
B is bridged,
A posts adult content with self-applied label,
B quotes that post, then

in Mastodon this can result in a link preview showing adult content in a post that doesn't have a content warning. It would be helpful if, if the quote doesn't have its own label, it inherited the quotee's CW with prefixed "Re: ".

Great idea!

This is probably true both directions, right?

Technically labels and sensitive can apply to text too, right? Unusual, but possible?
Re the behavior, yes, if a bridged fediverse account quotes a bridged fediverse post, Bridgy Fed should translate it into a native Bluesky quote post, including embed of the quoted post.

(Oh and unrelated, but I guess I/we should tighten up terminology. I've generally used the terms "native" and "bridged" accounts, but I saw you mention recently that you've used "bridged" and "bridge" accounts. I don't feel strongly, I get both, and I don't have a good feel for what the broader community is settling on. Maybe no clear consensus yet, this stuff isn't really obvious or intuitive 😁)

Technically labels and sensitive can apply to text too, right? Unusual, but possible?

For sensitive it depends on the Fediverse software. Pixelfed: yes, Mastodon: no.
I think applying the label for link preview text does make sense, even if it's unexpected, if the native post had a CW/summary(?) 🤔
I wish Bluesky allowed labels to warn about text pure posts too, anway.

(Oh and unrelated, but I guess I/we should tighten up terminology. I've generally used the terms "native" and "bridged" accounts, but I saw you mention recently that you've used "bridged" and "bridge" accounts. I don't feel strongly, I get both, and I don't have a good feel for what the broader community is settling on. Maybe no clear consensus yet, this stuff isn't really obvious or intuitive 😁)

I tend to say bridged account to specifically mean a native account with bridging enabled. I'm not sure that isn't less easy to understand, though.

Re the behavior, yes, if a bridged fediverse account quotes a bridged fediverse post, Bridgy Fed should translate it into a native Bluesky quote post, including embed of the quoted post.

For native quotes on Bluesky there's no issue, as the nested label warning is effective there.

For sensitive it depends on the Fediverse software. Pixelfed: yes, Mastodon: no.

Hmm, the Mastodon docs seem to imply yes...?  https://docs.joinmastodon.org/spec/activitypub/#properties-used :

sensitive
Used to determine whether status media or text should be hidden by default. See the Sensitive content extension section for more information about as:sensitive

and https://docs.joinmastodon.org/spec/activitypub/#sensitive :

Mastodon uses the as:sensitive extension property to mark certain posts as sensitive. When a post is marked as sensitive, any media attached to it will be hidden by default, and if a summary is present, the status content will be collapsed behind this summary.

Mastodon doesn't allow you to set the sensitive flag independently of summary,  but for incoming posts that only have the former, it definitely doesn't hide the text but blurs the images. (I just checked.)
I'm not sure how sensitive alone would behave on a text-only post, though.

I just noticed this on my own account bridged from Bluesky into Fediverse - I'm not sure it'll be particularly rare. I think this will be very common for artists that are occasionally quote-boosting their own art. What's particularly worrying about it is that I can't think of a user-side fix right now.
Bluesky doesn't allow applying adult labels to text-only posts or quote posts, so there's no way to by-paw fix the problem; and since the account is automated I can't log-in and apply the labels myself. In the meantime it's making me hesitant to quote-boost any adult content on Bluesky.
I think it'll be rare for non-artist users, but a relatively common problem for adult artists.


materialbox doesn't work Ubuntu 14.04 firefox 40.

Using meteor package:
<img class="materialboxed" width="600px" data-caption="{{metadata.description}}" src="{{this.url store="thumbs"}}"/>

Works under Chrome, Microsoft Edge.
10 different magnify glasses appear when you click on image.

It's ok with latest materialize on  FF35 and 49.


Camera-PointCloud Fusion

How to enable the function of camera-point cloud fusion?

No fusion is done at the bridge level.
You can a ROS node to achieve that in Autoware.

No fusion is done at the bridge level. You can a ROS node to achieve that in Autoware.

In roi-cluster-node, the transform between base_link and camera_link is required. But the sensors are not calibrated yet. How to calibrate the sensors in carla?


fix: splitFileAndPostfix works as cleanUrl

Description
cleanUrl and splitFileAndPostfix where working in different ways.
cleanUrl('/hello#hash?query') -> '/hello'
splitFileAndPostfix('/hello#hash?query') -> '/hello#hash'

This PR makes cleanUrl make them both work in the same way, possibly fixing issues with dependencies having # in their path. The new cleanUrl also avoids the second regex if it isn't needed.

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Looks like cleanUrl is right, first the hash needs to be removed, and then the query. If not new URL calls we do later on won't work correctly (like in injectQuery).
new URL('https://bar.com#foo?hello').hash === '#foo?hello'
new URL('https://bar.com#foo?hello').search === ''

I think the original splitFileAndPostfix having these inverted may not have been intentional . Probably the intention at that point was to remove both the query and the hash.
Later on, this ended up helping with paths like es5-ext/array/#/concat.

The PR now makes splitFileAndPostfix work as cleanUrl instead. And modifies cleanUrl to better reflect the way new URL works (before, it would only remove the latest part ?bar#foo?bar)
new URL('https://hello.world/#foo?bar#foo?bar').hash
'#foo?bar#foo?bar'

/ecosystem-ci run

/ecosystem-ci run astro iles

/ecosystem-ci run iles

Marking this as a fix. I think we should do it, but I'm not sure if in 4.3.

It looks like the Iles fail isn't related to this PR, it was failing in others too (cc @ElMassimo in case you have some time to check with the current Vite main).
@bluwy if the Astro fail is because of flakiness, I think we could merge this PR in 4.3.

/ecosystem-ci astro
I'm not sure if it's a fluke since it's a new error I haven't seen before. re-running again

/ecosystem-ci run astro

So I believe this is how the behaviour had changed:

fsPath
original
fs refactor
pr

foo?bar#baz
foo?bar#baz
-
foo?bar#baz

foo#bar?baz
foo#bar?baz
-
foo#bar + ?baz

foo?bar
-
-
-

foo#bar
foo#bar
foo#bar
foo#bar

The fs refactor PR might've caused a regression, so this PR seems to be on the right track, but with only one change for the second case. I think this PR should be fine then 👍

I think you are right, looks like the logic the fs refactor wasn't right. I now updated this PR to ignore foo?bar#baz, we don't need to check that one.

fsPath
original
fs refactor
pr

foo?bar#baz
foo?bar#baz
-
-

foo#bar?baz
foo#bar?baz
-
foo#bar + ?baz

foo?bar
-
-
-

foo#bar
foo#bar
foo#bar
foo#bar


revert: "fix(meta): Temporary remove these platforms as of #16 (#17)"

This reverts commit 907a86f40249ed2addd4792ea4319d34e624cf84.

Merge this if any requirements on #16 are set


perf(semantic): improve logic

Even though there is no noticeable performance improvement, this change makes sense and I think we can merge the

Current dependencies on/for this PR:

main

PR #2088   👈

This stack of pull requests is managed by Graphite.

I know why. Our current benchmark is missing the .d.ts file.


[BULK] DocuTune - Rebranding

Global effort for the Microsoft Learn platform rebrand
The Microsoft team is applying changes to content for the Microsoft Learn platform rebrand. Changes include modifications to current Microsoft Learn and Microsoft Docs terminology as well as associated domain name and content URL path changes.
Please review this draft PR and provide any necessary comments as soon as possible. Because these fixes are tightly scoped, we have approval to automatically merge these changes to the default branch for publication.
This PR was generated via DocuTune. It includes only targeted fixes and minor formatting adjustments.
CorrelationId: d8c4c3ac-d49a-4c95-9ddc-9822ca297907
InitiativeId: docutune-rebranding-2022-09
PointOfContact: Alex Buck

#docutune-draft

Docs Build status updates of commit 8d68113:
:bulb: Validation status: suggestions

File
Status
Preview URL
Details

Docs/Features/secure-stop-pk.md
:bulb:Suggestion

Details

CONTRIBUTING.md
:white_check_mark:Succeeded

Docs/Overview/additional-information.md
:white_check_mark:Succeeded

Docs/Overview/output-protection-levels.md
:white_check_mark:Succeeded

Docs/Features/secure-stop-pk.md

Line 39, Column 2: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'style' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 71, Column 74: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'span' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 76, Column 200: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'span' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Links containing percent-encoded character trigger URIError in react-router

Version
"react-router-dom": "4.2.2",
"react-dom": "16.0.0",
"react": "16.0.0"

Test Case
https://codesandbox.io/s/zj7ok3l5x (WARNING: codesandbox has some problems with this test case, this link is just here to ease the test case bundle download)
Steps to reproduce

Create a router with path equal to "/:id", and with a component being a simple display component displaying the id.
Create a Link  with a "to" parameter equal to something containing a percent-encoded percent sign: (e.g.  to = {`/${encodeURI("%foobar")}`} )
Click on the link
Refresh

Expected Behavior
When refreshing, you get the same page as when you click on the link (so, after step 4 you get the same display as before step 4).
Actual Behavior
When refreshing, you get an error:
URIError: Failed to decode param '/%foobar'
After the click on the link, the url bar in the browser contains "/%foobar", and not "/%25foobar", which is nonetheless the actual destination of the Link.
Sample video showing the problem (notice that the "%netflix" link is correctly percent-encoded by looking at the bottom left of the video when hovering the link):  https://ptpb.pw/UBJc.mkv
Mirror of the codesandbox:  https://ptpb.pw/tOIr.zip

This is caused by the history library. There is a bug being tracked there: ReactTraining/history#505


added  lib/domains/com/onmicrosoft/zs10zabrze.txt

added Technikum Nr 7 Zabrze im. prof. Janusza Groszkowskiego w Zabrzu

@wikadii Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


checkpoints: Properly report missing permissions

Signed-off-by: Till Maas<EMAIL_ADDRESS>

Coverage increased (+0.02%) to 69.005% when pulling 741e0bb6c58c4d0c4657a980f6906a9173a21919 on tyll:checkpoint_permissions into fd6f944ec3017a9b8e6c51b9f590a0d342033a1a on nmstate:master.

@EdDev ready for re-review


Add search toolbar on editors

search toolbar allows user to find text from DocxToSource app

That's not a bad idea.  I think the control names are a bit generic though. Something like xXmlSource and xCodeSource, that way it is easier to keep track of while coding.

xName changes was updated. Where should I log feature requests? like a file comparer between 2 files.

I like it.  Once I check it out on a Windows machine, I'll make the pull.
As far as feature requests are concerned, just open an issue and put an enhancement label on it.  A file comparison feature would be nice, I definitely see a benefit for it based on past experience.  There would be some obstacles that would need to be worked out, and they could be discussed in further detail in the issue, but I think it would be worth the time.

Works ok.  Only thing left is to make sure that you update the MainWindow.xaml.cs file to use the new names that were put in the corrisponding xaml file.  Once that is done, I'll pull it in.  Thanks

its updated now. Sorry for missing this.

No problem.  Thanks for taking the time.

This is a nice addition.  It should probably be brought to the fore front more but that can be done later.  Thanks again.


The forge project uses hardhat to verify bytecode inconsistencies

verify error, I have a project, first use forge to build the project, and then use hardhat to deploy the verification contract.
After verification many times, it keeps prompting that the contract bytecode is inconsistent.
Later I found out that it was added,
preprocess: {
     eachLine: (hre) => ({
       transform: (line: string) => {
         if (line.match(/^\s*import /i)) {
           for (const [from, to] of getRemappings()) {
             if (line. includes(from)) {
               line = line. replace(from, to);
               break;
             }
           }
         }
         return line;
       },
     })
   },

caused by.

If you intend to compile contracts and deploy them on the zkSync network, using forge build is not suitable as it relies on the solc binary for compilation instead of zksolc. Instead, please use the hardhat-zksync-compile plugin to compile your project.

This is used, but it is added, preprocessed into the configuration, and the verification cannot be successful.


Fixed for mobile platforms

There's no "click" event to "" on touchscreen-based mobile platforms. It's "touchstart" there.
I'm not familiar with the Grunt, so edited files manually. Sorry for that… =\

Sorry, I will not merge this as all mobile browsers trigger a click event.
If you notice any problems when using jstree on mobile - please let me know. All plugins that need special attention for mobile (like dnd) are taken care of.
Best regards,
Ivan

Well. Yes, there's a problem. I cannot unfold a node on mobile "Xperia" (cannot tell the certain model right now, it's not my phone).
Configuration:
$.jstree.defaults.core.themes.icons           = false;
$.jstree.defaults.core.multiple               = false;
$.jstree.defaults.search.show_only_matches    = true;
$('.jstree').jstree({"plugins" : [ "search" ]});

Unfortunately, I don't have enough time right now to prepare the example page.


Smol tweaks

Motivation

Solution

PR Checklist

[ ] Added Tests
[ ] Added Documentation
[ ] Updated the changelog

Codecov Report

Merging #58 (6fffb4a) into main (17b81c5) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #58   +/-   ##
=======================================
  Coverage   43.00%   43.00%
=======================================
  Files          18       18
  Lines        5495     5495
=======================================
  Hits         2363     2363
  Misses       3132     3132

Flag
Coverage Δ

test
43.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/app.rs
91.02% <100.00%> (ø)

tests/integration-tests.rs
97.18% <100.00%> (ø)

Continue to review full report at Codecov.

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


feat: added a sliver app bar to preferences when with illustration

Impacted file:

user_preferences_page.dart: added a sliver app bar when we have an illustration

What

As discussed in #2074, the illustration in preferences' header blocked the top of the page.
A SliverAppBar seemed appropriate, and is coded in this PR.

Screenshot
https://user-images.githubusercontent.com/11576431/171156398-c39658ac-a04b-48ff-9104-5187d7dfc6ee.mp4
Part of

#2057

Thank you @M123-dev!

LGTM. this is something we can probably apply to all pages with illustration

Including product page?...


resolved_ts: fix online changing resolved-ts.advance-ts-interval can't take effect immediately

What problem does this PR solve?
Issue Number: close #10426
Problem Summary:
Online changing resolved-ts.advance-ts-interval can't take effect immediately
What is changed and how it works?
What's Changed:
Register new advance ts event right after config change and add cfg_version to reject advance ts event that previous registered.
Check List
Tests

Integration test

Release note
Fix online changing `resolved-ts.advance-ts-interval` can't take effect immediately

/merge

/rebuild

/merge


Handle undefined/null child in registerInputs

I find myself often writing code like:
render: function() {
  if (condition) {
    var heading =
Heading
;
  }

  return

    { heading }
    <MyInput ... />

}

Unfortunately I get the error message Uncaught TypeError: Cannot read property 'props' of null when the condition evaluates to false.

Does the same happen when you declare your var outside the condition as an empty object?

No but a lot of the react examples have render functions which return null.  I just submitted a PR #26 for this issue.

And it has been accepted, awesome stuff, thanks :-)


Hitman: add gamespeed control through keyboard via timestop variable

Timestop is done with a float, and it's doable to make that control the gamespeed. This is useful for people who want to use the camera tools for creating videos.

Implemented in v1.0.6


Bump cloudposse/tfstate-backend/aws

what

Update to latest module to support AWS provider V5
Enable SuperAdmin to assume tfstate access roles

why

Support AWS provider V5
Enable SuperAdmin to use Terraform without requiring var.privileged = true

Not actual anymore


Make spamassassin work for multiple users

Hi,
in my installation I have multiple domains and it seems that spamassassin does not scan all the domains. In https://github.com/tomav/docker-mailserver/issues/496 it should be fixed.
Do I need to add some config to make it work?
Thx in advance!

Hi @thiesschneider, could you check that you have /etc/amavis/conf.d/60-dms_default_config in your image?

Hi @tomav,
yes, I have this file and it looks fine:
use strict;

@local_domains_maps = (
   read_hash('/etc/postfix/vhost')
);

1;  # ensure a defined return

inside vhost there are also the correct domains.
Any ideas how to check if it really works?

With that configuration, I have spassassin headers on all my domains:
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-5 required=4.9
	tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
	HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
	RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001]
	autolearn=ham autolearn_force=no

I do not know hot to test this and I am also confused with this part in the wiki:

Why are Spamassassin x-headers not inserted into my sample.domain.com subdomain emails?
In the default setup, amavis only applies Spamassassin x-headers into domains matching the template listed in the config file 05-domain_id (in the amavis defaults). The default setup @local_domains_acl = ( ".$mydomain" ); does not match subdomains. To match subdomains, you can override the @local_domains_acl directive in the amavis user config file 50-user with @local_domains_maps = ("."); to match any sort of domain template.

Is it possible to clearify this section in the wiki?

With the improvement made, this part is outdated I suppose.
Regarding "how to test it", send an email from an external account to 2 different domains hosted on your mail-server. In the logs (and in the headers regarding your configuration), you should see what I pasted above.

@radicand Have you investigated in this? I would like to close this issue, but it seems like it is still not solved.

@aendeavor I haven't come back to this since my original comment - the edits are built into my K8s deployment and work with the changes I noted (even if onerous).

Alright. I'll label this properly and leave it open. I can't fix this, so someone else must do it.

I will now close this off as (and we talked about that in another issue) this issue has become stale, there is no activity and it's 3 years old.
If, in the future, something is done here, feel free to re-open or ask me to re-open.


fix: return engine_getPayload error response

Previously, we would return Poll(Err(error)) when on_get_payload returns an error. Instead, we should be returning that error back to the client if it corresponds to one of the errors from the engine API spec.
Previously:
>> (c2356d73) {"jsonrpc":"2.0","id":2,"method":"engine_getPayloadV1","params":["0xdb5a075c19eee601"]}
<< (c2356d73) {"jsonrpc":"2.0","error":{"code":-32001,"message":"Custom error: channel closed"},"id":2}
CLMocker: Could not getPayload (c2356d73, 0xdb5a075c19eee601): Custom error: channel closed

Now:
>> (effe3338) {"jsonrpc":"2.0","id":2,"method":"engine_getPayloadV1","params":["0xf98c6886602604e5"]}
<< (effe3338) {"jsonrpc":"2.0","error":{"code":-32603,"message":"Payload does not exist / is not available"},"id":2}

Codecov Report

Merging #2175 (e7960c8) into main (2df1602) will decrease coverage by 55.15%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #2175       +/-   ##
===========================================
- Coverage   72.06%   16.92%   -55.15%
===========================================
  Files         447      448        +1
  Lines       54326    54487      +161
===========================================
- Hits        39152     9222    -29930
- Misses      15174    45265    +30091

Flag
Coverage Δ

integration-tests
16.92% <0.00%> (-2.34%)
:arrow_down:

unit-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/consensus/beacon/src/engine/error.rs
0.00% <ø> (-57.15%)
:arrow_down:

crates/consensus/beacon/src/engine/mod.rs
0.00% <0.00%> (-89.22%)
:arrow_down:

... and 320 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


preallocate loaded series map size

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Before this change, PreloadSeries took 41.77% CPU time while mapassign function took about 6.49% CPU time. 3.3% CPU time was spent on growing the map.

After this change, PreloadSeries took 17.89% of CPU time while mapassign function took only 1.2%. And no need to grow and reallocate map due to growing.

Changes
For each batch of series fetch, since we know the batch size beforhand, we can preallocate the size of loadedSeries map.
Verification

I am also wondering if we should rework the index cache FetchMultiXXX interface. Having a map seems a little bit expensive. A slice of cached items should also work, sharing the same idx of the input keys.


Add certificate pinning

Add certificate pinning to the app

Certificate pinning for web apps appears to have been deprecated from browsers.
Need to identify if there is any new functionality needed in order to meet security requirements.

This is not valid for the web app. We are awaiting the report from the web app security testing and will open tickets as necessary for that.


Add Sourcify CLI plugin

Description
Adding a Sourcify CLI plugin to fetch contracts from it's repository.
Additional Information

[x] I read the contributing docs (if this is your first contribution)

Your ENS/address:
wslyvh.eth

Not sure what happened with public/assets. Only noticed it just now..

Thanks for adding this! Made some updates and created https://github.com/wagmi-dev/wagmi/pull/1841 since I couldn't push to this branch.


Set S3 file expire time after compaction.

So S3 storage will not keep growing.

Minio doesn't support a tag-based expiration filter, so we will implement delayed deletion to reduce the storage size.


formatting to 'p' because removeFormat cannot deal with headers

https://stackoverflow.com/a/52137754/4514671
https://stackoverflow.com/questions/14028773/javascript-execcommandremoveformat-doesnt-strip-h2-tag
I'm not a js dev (iOS) so here are the references

duplicate


Feat/ability to use custom index definition

Adding ability to add custom index definitions. It allows to set custom ScoringProfiles, Suggesters, Analzers etc.

Checklist:

[x] My PR has a descriptive title (not a vague title like Needed this)
[x] Title and all the commits follow commitlint guidelines
[x] My PR targets the develop branch or appropriate release branch
[x] My PR provides test coverage for my change (where applicable)
[ ] I've placed the link to the corresponding Trello card or issue which this PR fixes/address below ⤵

Fixes: ### ISSUE_OR_TRELLO_LINK ###

@trt left some comments, lets pair on this on FF.


[Slider] Remove style-propable mixin and react-dom

This PR removes the style-propable mixin and react-dom from the slider source.
It, also, fixes the line:
const calcDisabledSpacing = this.props.disabled ? ` -${disabledGutter}px` : '';

There should be a space between '-' and '${disabledGutter}px', otherwise it will not be valid CSS.
Just to point it out, the following statement changed from:
style={prepareStyles(this.props.style)}

to:
style={prepareStyles(Object.assign({}, this.props.style))}

Since, the reference to this.props.style is kept outside the render() method would start to produce the warning from callOnce everytime we call the render method for styles that use this.props.style

Good job @felipethome!

Just to point it out, the following statement changed from:
style={prepareStyles(this.props.style)}
to:
style={prepareStyles(Object.assign({}, this.props.style))}

Good catch, yes we've been careful to make sure to not prepareStyles directly from passed in props but to compute a new object from it. :+1:
I left some comments that were unrelated to your changes that might improve code quality in other areas but so far this looks good.
I forget to ask before, can you also move the getStyles() outside of the class definition like this. We're trying to move away from imperative methods and trying to makes these getStyles() functions purely a result from props and state.  Doing so you'll have to remove the getTheme() calls from the getStyles() method (after which you can also delete that method).

Thanks @newoga . And I will gladly remove the getTheme() function. I want to do it for a long time now :smile: .
I have a question, the slider has a lot of styles, some of them can be removed and I will do it soon, but most of them can't. A lot of these styles will me merged depending of state and prop variables. Right now, most of this merge computations are made in the render method, but two of these merges are made in the getStyles(). I would like to have all these merge computations that depend of state or props ideally in one place. What do you think? (Note: right now it is easier if a make getStyles() free of state and props)

I just realize that what I asked is not a good thing for the code. So, we don't need to change that. I will do the changes we talked about and remove getStyles to outside the class as you said, thanks!

@felipethome Yeah give it a shot. The general patter we've been following is construct the style object in getStyles(), merge with custom style provided by props in render. Eventually many of these components can be written as functional components (which is pretty much what getStyles() is, except that it's not returning JSX).

@newoga can you give a look? I am sorry I removed the clearValue function, I thought it was dead code since it is not being used inside the component and it doesn't seem to be in the docs, but maybe is some legacy code so I put the declaration back to its place.

 I am sorry I removed the clearValue function, I thought it was dead code since it is not being used inside the component and it doesn't seem to be in the docs, but maybe is some legacy code so I put the declaration back to its place.'

Yeah, it's probably better to leave it in for now. That being said, we should consider deprecating those methods for the next release since this component is controlled with value and onChange.

Should I fix that to spread only the ones left? I mean, the ones the component doesn't explicitly use.

Yeah I think that's a good idea, let's add description, disabled, style etc. to the destructure. Though moving the {...other} destructure within the JSX to the left was a good idea too. :+1:

Another thought, we call of "handle" the element that we drag, but it is really common to use the word handle in functions that are manipulating events, what do you think about change the name "handle" to "knob" or "thumb"?

Yeah I wondered the same thing, that's a good idea. Thumb seems like a good name based on the slider spec.

Unfortunately, I think we will need to accept the name "handle", because there are variables in the muiTheme that use this name like: handleSize or handleFillColor, so if I change in the end we would end up with two names ("handle" and "thumb").

because there are variables in the muiTheme that use this name like: handleSize or handleFillColor

Yikes, yes you're right. That makes me said :disappointed:. @alitaheri @oliviertassinari thoughts on this?

It makes me said too!  I really would like to fix that. Let me think about options...

@newoga do you think this is too difficult to read:
handle: {
    boxSizing: props.disabled ? 'content-box' : 'border-box',
    position: 'absolute',
    cursor: props.disabled ? 'not-allowed' : 'pointer',
    pointerEvents: 'inherit',
    top: '0%',
    left: state.percent === 0 ? '0%' : `${(state.percent * 100)}%`,
    zIndex: 1,
    margin: `${(slider.trackSize / 2)}px 0 0 0`,
    width: props.disabled ? slider.handleSizeDisabled :
      state.active ? slider.handleSizeActive : slider.handleSize,
    height: props.disabled ? slider.handleSizeDisabled :
      state.active ? slider.handleSizeActive : slider.handleSize,
    backgroundColor: props.disabled ? slider.trackColor :
      state.percent === 0 ? slider.handleFillColor : slider.selectionColor,
    backgroundClip: 'padding-box',
    borderRadius: '50%',
    borderStyle: 'solid',
    borderColor: (state.focused || state.hovered) ? slider.trackColorSelected : slider.handleColorZero,
    borderWidth: state.percent === 0 && !props.disabled ? `${slider.trackSize}px` : 0,
    transform: 'translate(-50%, -50%)',
    transition:
      `${Transitions.easeOut('450ms', 'background')}, ${
      Transitions.easeOut('450ms', 'border-color')}, ${
      Transitions.easeOut('450ms', 'width')}, ${
      Transitions.easeOut('450ms', 'height')}`,
    overflow: 'visible',
    outline: 'none',
},

The slider can have a lot of different states: active, hovered, focused, disabled, percent zero. That is why I am thinking about ternaries instead of if-else generalizing all the states. Maybe the original way is more readable?

Wow, you're not kidding :laughing: Yeah maybe there's just too much state here to use ternarys for. Alright, let's leave it alone for now. I think there might be away to break it up a bit still but let's see if we can get this merged now since we got style-prop and reactdom out.

@oliviertassinari @alitaheri Can you take a look at this when you get a chance?

That is a pity, but yes..would be too much for this PR. Can I at least move this piece of code:
{
    left: `${(percent * 100)}%`,
}

To inside of the getStyles method()?
Also, just something to point:
const sliderStyles = Object.assign({}, styles.root, this.props.style);
...

    {this.props.description}
    {this.props.error}
    <div
      style={prepareStyles(sliderStyles)}
      ...

The this.props.styles are being applied two times, and should be just in the root element, right? But we probably would break some pages out there changing that right now.

Can I at least move this piece of code:

Yeah definitely, that makes sense

The this.props.styles are being applied two times, and should be just in the root element, right? But we probably would break some pages out there changing that right now.

I didn't even catch that, that's a bug in my opinion. We ran into that with the AutoComplete component recently too. The style prop should really only be used for the root element. I want to fix this too...
Looking at the code more closely, I wonder if the sliderStyles div should really be the root, and managing the error text and description should be handled outside of this component. This component doesn't really offer much flexibility in customizing the style for the description and error and I wonder if it's could be moved to a wrapper component. That way this component could simplify too. (Don't do this now, just brainstorming)

It doesn't offer anything at all for error and description. I think the slider component is more complex than what it seems when you just think about it. The material design specification also doesn't help us here because it has a lot of details about the design of this component.

That way this component could simplify too and really be just the slider (not the slider control including label, etc.)

I agree and If we had a directory just for the slider component, we would be able to break the implementation into pieces like: handle/thumb, track, errors, root. And that would simplify a lot..
Another awesome thing, would be a test case. Unfortunately, this test case isn't simple to write because of the amount of properties the user can set (that is the price we pay for customization).

I agree and If we had a directory just for the slider component, we would be able to break the implementation into pieces like: handle/thumb, track, errors, root. And that would simplify a lot..

I agree, I think splitting this up is a good idea (and agree there is a lot more complexity to this than it seems, including functionality in the spec that we haven't implemented yet). Soon all the components will be put in directories (#3212) and we should be able to split it up. :sweat: I wouldn't be totally opposed to starting to split of the thumb into a SliderThumb component from now.

Soon all the components will be put in directories (#3212)

Awesome!

I wouldn't be totally opposed to starting to split of the thumb into a SliderThumb component from now.

I would gladly be part of the discussion of how to split it, once you decide is time to do it.
I added the last changes we talked about, now I think it is done.

Okay awesome @felipethome, let's get some feedback from the other guys and we'll see what next steps are. Thanks so much, this is a huge help :+1:

@felipethome That looks good :+1:.
Side note: I have noticed that autoPrefix.set(body.style, 'userSelect', value, this.state.muiTheme);
doesn't work property. That's kind of expected, the autoPrefix.set method is broken.

Thanks @oliviertassinari ! The PR #3237 will solve this problem if you accept it.

@felipethome Could you squash when you get a chance?
@alitaheri If all is green for you, feel free to merge. We'll get the autoPrefix and other related improvements in future PRs.

Actually only squash f39258575b42a2b94f3154f1d1a2434648f78508 The rest of the commits are good for the history :+1: I'll review in a moment :+1:

Side note: I have noticed that autoPrefix.set(body.style, 'userSelect', value, this.state.muiTheme);
doesn't work correctly. That's kind of expected, the autoPrefix.set method is broken.

Let's continue this on the other PR.
@oliviertassinari Feel free to merge, this looks good to me :+1:

@felipethome Thanks! :tada:

Awesome, thanks a lot @felipethome :+1: :+1: :+1:

Great job! @felipethome :smile:

Thank all of you too! :smile:


DM/mariadb: sync the binlog executed in slave during master-slave replication

What problem does this PR solve?

Issue Number: close https://github.com/pingcap/tiflow/issues/10741
What is changed and how it works?

add test case
update go-mysql version https://github.com/go-mysql-org/go-mysql/pull/852

Check List
Tests

Unit test
Integration test

~~https://github.com/okJiang/tiflow/actions/runs/8243030893~~
https://github.com/okJiang/tiflow/actions/runs/8290808978
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`

/retest

/cc @lance6716 @GMHDBJD

/retest

/retest

/retest

/retest


Add the Windows build environment to Travis builds

Explore and implement how the Windows build environment can be added to Travis CI for this project.

Get ideas from sourced-ce bat file

On hold until Windows-Travis support is out of beta and protects secure env vars: https://docs.travis-ci.com/user/best-practices-security#steps-travis-ci-takes-to-secure-your-data

The beta Windows support does not obfuscate secure environment variables leaked into the build log. Please keep reading the next section, on how to avoid leaking secrets to build logs


[ODPR-1605] - Address warnings in: Digital Platform Reporting Register Frontend

Description
Fix codecoverage by upgrading to scala version 3.5.1
Add a link to the relevant story in Jira
https://jira.tools.tax.service.gov.uk/browse/ODPR-1605
Checklist PR Raiser
Before creating PR

[x] Have you run the tests?

[x] Have you rebased against the current version of main?
[x] Have you checked code coverage isn’t lower than previously?
[x] Have you checked to ensure all dependencies are up-to-date?

After PRs been raised

[ ] Have you checked the PR Builder passes?

Checklist PR Reviewer
Before Reviewing

[ ] Have you pulled the branch down?
[ ] Have you assigned yourself to the PR?
[ ] Have you moved the task to “in review” on JIRA?
[ ] Have you checked to ensure all dependencies are up-to-date?
[ ] Have you checked to ensure branch has been rebased against the current version of main?

Whilst Reviewing

[ ] Have you run the tests?
[ ] Have you run the journey tests?
[ ] Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[ ] Have you checked for merge conflicts or any changes in the current main that may affect the current pull request?
i.e. does it need another rebase?
[ ] Have you checked to make sure there are no builds in the pipeline before you merge?
[ ] Have you moved the task to “in pipeline” on Jira?

Looking good to me. There are lot of file changed. But this registration frontend and very less activity is going on. So it should less or no merge conflict with the current work. Therefore I am approving this PR.


Front end/ga virtual page views

Needs a review by @Demwunz and @TrentDSD

Redone this and will create new PR.


Difference disableEviction and skipWaitForDeleteTimeout

Hello,
Is it possible to get example/explanation of the difference between the two ?
Regards,

From the README:
  # If left unspecified, no drain will be performed.
  # See:
  # - https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/
  # - https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#drain
  drain:
    # deleteLocalData: true  # default
    # ignoreDaemonSets: true # default
    force: true
    # Use `disableEviction == true` and/or `skipWaitForDeleteTimeout > 0` to prevent upgrades from hanging on small clusters.
    # disableEviction: false # default, only available with kubectl >= 1.18
    # skipWaitForDeleteTimeout: 0 # default, only available with kubectl >= 1.18

From https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#drain:

Name
Shorthand
Default
Usage

disable-eviction

false
Force drain to use delete, even if eviction is supported. This will bypass checking PodDisruptionBudgets, use with caution.

skip-wait-for-delete-timeout

0
If pod DeletionTimestamp older than N seconds, skip waiting for the pod. Seconds must be greater than 0 to skip.

What this means is that prior to 1.18 kubectl drain did not honor Pod Disruption Budgets when draining a node. If you want to replicate this behavior (aka just deleting pods on the draining node) on a 1.18+ cluster with a 1.18+ kubectl you should set your plan .spec.drain.disableEviction to true. If you would prefer to honor PDB up to a maximum-ish number of seconds, then you should set your plan .spec.drain.skipWaitForDeleteTimeout.
If you do not set either of these values for draining nodes in a 1.18+ cluster then, with PDB honored via the Eviction API, your drain operations can hang indefinitely while waiting for an appropriate node to reschedule your pod(s) to. An example of this would be attempting to upgrade a 3-server HA cluster with Rancher 2.x and Longhorn installed: by default Rancher deploys a 3 member ReplicaSet and Longhorn requires 3 members DaemonSets for quorum which means that attempting to perform an upgrade on any of these nodes for a plan with .spec.drain configured that neither disables use of the Eviction API nor sets a deletion timeout will fail to complete successfully.

@adi90x if you have suggestion(s) for how this can be made more clear in the README I would welcome a pull request!


How do I apply a band-pass filter?

How do I apply a bandpass filter? I would like to apply a bandpass filter from 8 to 30 Hz to the EEG sent by emotiv pro.

@YuminosukeSato
So, you can use EmotivPro-LSL feature to receive data stream from EmotivPro. Then apply your filter to the data stream.

ok.Thank you.


Trying to query a HA entity but getting "sorry thats not supported yet"

Home assistant entity is called sensor.battery_state_of_charge this is a percentage from 0%-100%
I created this nodered flow which I think is correct but I don't know what to set up the entity on the skills bridge (or the exact phrase to ask alexa) I'm just looking to get a response from something like:
Alexa tell me the battery state
"Your battery is at xx percent" as a response.
I have read all the documentation and I have also posted in the nodered group for at least a couple of months and got no-where with it. I know this will be something simple, might not even be supported? hence why I raised this issue in the hope that either you can point me in the right direction or that an enhancement can be made to support this.
[{"id":"e9fc7c35.44ca4","type":"api-current-state","z":"de7d428686d4597d","name":"Get entity state","server":"e7c1f572.ea52d8","version":3,"outputs":1,"halt_if":"","halt_if_type":"str","halt_if_compare":"is","entity_id":"sensor.battery_state_of_charge","state_type":"str","blockInputOverrides":false,"outputProperties":[{"property":"payload","propertyType":"msg","value":"","valueType":"entityState"},{"property":"","propertyType":"msg","value":"","valueType":"entity"}],"for":0,"forType":"num","forUnits":"minutes","x":620,"y":200,"wires":[["b7fa0d45.4a4a"]]},{"id":"e7c1f572.ea52d8","type":"server","name":"Home Assistant","version":5,"addon":true,"rejectUnauthorizedCerts":true,"ha_boolean":"y|yes|true|on|home|open","connectionDelay":true,"cacheJson":true,"heartbeat":false,"heartbeatInterval":"30","areaSelector":"friendlyName","deviceSelector":"friendlyName","entitySelector":"friendlyName","statusSeparator":"at: ","statusYear":"hidden","statusMonth":"short","statusDay":"numeric","statusHourCycle":"h23","statusTimeFormat":"h:m","enableGlobalContextStore":true}]

This is not possible and there is no ongoing development for this skill (it is based on an old API that cannot support this)

Thanks I am working around this by just creating a switch in the skills bridge which will change the state of a HA entity, when that entity changes I will use the Alexa Media Player to report the entity value instead.

VSH (Virtual Smart Home) can do this (and more)


Minor DOC.md modifications for panvimdoc lists

Pandoc fails to parse markdown lists unless they come after an empty line. Thus the panvimdoc generated lists are crammed in a single paragraph.

Ah nice, thank you!!


GridFieldPaginator() not switching pages

Within ModelAdmin:
public function getEditForm($id = null, $fields = null)
{
    /** @var Form $form */
    $form = parent::getEditForm($id, $fields);

    /** @var GridField $gridField */
    $gridField = $form->Fields()->fieldByName($this->sanitiseClassName($this->modelClass));

    $config = GridFieldConfig_RecordEditor::create();
    $config->addComponent(new GridFieldPaginator());
    $gridField->setConfig($config);

    return $form;
}

This adds the Pagination controls to the bottom however attempting to navigate through the pages will always refresh the first page and never actually change the page
The POST invoked by the GridField if it's helpful:
action_gridFieldAlterAction?StateID=gf_e7311087:Next
filter[-Zanderwar-Scraplands-Models-Player][PlayerName]:

I can replicate this by adding the paginator component to a GridField. Some notes:

I had 79 records, and the default page size (without pagination) was 30
When GridFieldPaginator was added, the pagination controls showed 3 pages (correct)
It would switch to page 2, but not page 3 (would jump back to page 1 again)
When I specified 30 as the constructor argument (same as default) it wouldn't leave the first page

Which version of SS?

SS4 Alpha 4

could it be a regression from my PR: https://github.com/silverstripe/silverstripe-framework/pull/6263?

Is this:
$lastShownRecord = $state->currentPage * $itemsPerPage;`

meant to be the first record of the current page? otherwise shouldn't it be
$lastShownRecord = ($state->currentPage * $itemsPerPage) - 1;

For example if you're on page 3 of 5, showing 10 items per page, wouldn't the last record shown be 29 on page 2?
However wouldn't explain how that PR would break it since it does the same thing previously

I can confirm this. I just pulled in the latest version of SS4 framework, and my model admins are not able to paginate (they were't able to do so before either, which is why I updated framework).
In order to enable pagination I added the following lines to my model admin (taken from this pull request):
public function getEditForm($id = null, $fields = null)
{
    $form = parent::getEditForm($id, $fields);
    $gridField = $form->Fields()->fieldByName($this->getGridFieldName());
    $config = $gridField->getConfig();
    $config->addComponent(new GridFieldPaginator);
    return $form;
}
public function getGridFieldName()
{
    return $this->sanitiseClassName($this->modelClass);
}

Now, when I press the pagination it loads the second page, and on top I'm getting the CMS spinner which won't go away. If I remove it by inspecting it in the browser and press the next page, I'm being sent back to the first page.

@dhensy this doesn't appear to be caused by #6263 - I've reverted those changes and the bug persists.

Ok - I've done some debugging, and there's actually no problem with the paginator at all.
The Paginator is added by default (GridFieldConfig_Base::__construct), but it's not visible at the bottom of the page because it's hanging out off canvas. I tested by adding margin-bottom: 60px to the .field__paginator__controls element, and the paginator controls are working fine (Chrome/OSX) This CSS doesn't work in IE10 though - it's still off the bottom of the canvas by about half of the element height. I didn't test in any other browsers.
The problem of jumping between pages is caused by having two paginators in the GridFieldConfig. Oddly enough, adding the paginator (because you can't see one to start with, so assume there isn't one) makes it show up in the perfect place, it just doesn't work because the list gets paginated twice and confuses the states.

I can confirm @robbieaverill's findings. I just did the same, and brought the paginator back with some css hacking, I can now paginate. I'm still having the overlay not disappearing though.
See screenshot.

Requirements::customCSS("table.table.grid-field__table {
        margin-bottom: 55px;
}");

Fixes it perfectly for me, thanks @robbieaverill

@zanderwar cross browser?

I can confirm that by reverting to 4.0.0-alpha4 and implementing that css hack, pagination now works - without the spinner issue. That must be something having been introduced post 4.0.0-alpha4.

The spinner issue is logged at #5685

See https://github.com/silverstripe/silverstripe-framework/issues/6585#issuecomment-282595526; I'm having trouble replicating this issue on dev-master. I see the spinner appear as normal, and disappear after loading completes.
Regarding @robbieaverill 's issue:

The Paginator is added by default (GridFieldConfig_Base::__construct - or GridFieldConfig_RecordEditor for model admins), but it's not visible at the bottom of the page because it's hanging out off canvas.

I've fixed this with https://github.com/silverstripe/silverstripe-framework/pull/6653. Possibly that's all that was necessary?

Immediately after I posted this, I managed to run into the bug. Oh dear...

@tractorcow yeah, there wasn't much to the pagination bug. I hadn't PR'd because I haven't had a chance to work out the best fix for it and didn't want to PR a CSS hack.

It seems that it works MOST of the time; Trying to figure out what I did that made the bug appear.

According to @robbieaverill the issue was probably just the addition of the second paginator breaking navigation. Hope that the template CSS class fixes that then. ;)

Yep - I'll summarise:
Initial problem
Not seeing pagination controls in a custom ModelAdmin, I (and others) added a GridFieldPaginator component. Doing so shows pagination controls, but there is already a paginator component, so you end up with two of them.
This causes a bunch of weird stuff to happen, but it is solely caused by having two paginator components applied.
Actual problem
The default paginator component for model admin GridFields is not visible in the viewport.
Changing the position of it with CSS and testing it, it works fine. It's just initially invisible.

@tractorcow's fix at #6653 works to fix this issue.


device_plugins: Updated Readme.md

Signed-off-by: chaitanya1731<EMAIL_ADDRESS>

It looks good to me!


fix(widget-add-modal): add preview image of widgets

To Reviewers

[ ] Skip (style, chore ONLY)
[x] Not that difficult

Type of Change

[ ] New feature
[ ] Bug fixes
[x] Feature improvement
[ ] Refactor
[ ] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[x] Error / Warning / Lint / Type

Description

Things to Talk About
There's style bug! I'll fix it later.

@h22y25n would give me an error image later :)


Adding queue data structure on Array and Linked List

Hi
I want to add the Queue Data Structure implementation using Array and Linked List
Please assign me if i can do that.
Thanks

Hi @TawfikYasser,
It's assigned to you.

Thanks @ming-tsai


Control Award Submission

https://www.firstinspires.org/sites/default/files/uploads/resource_library/ftc/control-award-instructions.pdf

reopening, need to get closer to states before doing


SAMPLEIJ: what should it do?

Reported by Ansley B Manke on 4 May 2005 20:59 UTC
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1229

Comment by<EMAIL_ADDRESS>on 4 May 2005 21:07 UTC
As currently written, the following two commands give the same result:
yes? LIST/x=161/y=35 sst[LSIT SAMPLEIJ(sst[L=1](l=1]
yes?), 161, 35)
(If x,y is a location on the grid. else sampleij returns missing).
I would have thought that it would be equivalent to
yes? LIST/i=161/j=35 sst[l=1]
The documentation made it seem that the 2nd and 3rd arguments are indices,
rather than coordinates.  The documentation has been changed to reflect the way
the code actually works, but would a function that returns the data at a set of
index values be more useful?  It's what I would expect from a function called
SAMPLEIJ. As I recall, SAMPLEIJ was developed as a first step to SAMPLEXY. In
its present form is it of any use, or just a possible source of confusion?


Research of fundamentals

User story

As a developer
I want / need to grasp the fundamental objectives and technologies behind the project idea
So that I can organize better my work and duties, and ask relevant information from the partner

Acceptance criteria

Perform initial research of the project idea
Get an overall understanding of the technologies required

Definition of done (DoD)

All developers have acquired enough preliminary knowledge to decide the higher-level features they would like to work on and the technologies they will use to do so
The partner agrees with the assessments provided by the developers and with the suggested technologies

I believe the Definition of Done could be written as a more universal guideline, which can always be reused for all other issues 🙂
For instance, "All Acceptance Criteria are met" or "All tests ran successfully".


View border does not clip sub components

Description
Creating a View with borderWidth and overflow:'hidden', the border is nevertheless overwritten by the embedded components if it is too large to fit into the View.
Reproduction
class SquareButton extends Component {
  render() {
    const _size=50
    const _borderWidth=3
    const _lineHeight=_size-(_borderWidth*2)
    return (
    <TouchableHighlight onPress={this.props.onPress}>
      <View style={{width:_size,height:_size,backgroundColor:'green',justifyContent:'center',
    alignItems:'center',borderRightColor:'black',borderBottomColor:'black',
    borderTopColor:'grey',borderLeftColor:'grey',borderWidth:_borderWidth,
    overflow:'hidden'}}>
        <Text style={{lineHeight:_lineHeight+20,fontSize:_lineHeight,color:'yellow'}}>1</Text>
      </View>
    </TouchableHighlight>
  )}
}

Solution
Border of View should clip embedded components.
Additional Information

React Native version: 0.41.2
Platform: iOS
Operating System: MacOS

We're cutting down on the number of outstanding issues, in order to allow us to focus. I'm closing this issue because it has been open for over 60 days with no activity. If you think it should still be opened let us know why. PRs are always welcome.