getting redux-form to update state when DOM fields are updated

Hi,
This is a redux-form question and I apologise if it should be on stackoverflow but I've tried there and found little help as yet.
I've started using redux-form to validate a user details form. The form includes an address-lookup service provider that populates DOM input text fields after selecting an address.
When the service providers script populates the DOM with the selected address, is there a way to get redux-form to automatically respond and update the state or would it be better to have these fields separate from redux-form and updated in the state via a separate action/reducer.
Guidance on this greatly appreciated.

I have the exact same issue. Postcode Anywhere have created an Angular directive but after speaking to their customer support there is no React/Redux equivalent.

In case this helps anyone I've got it working by using the API version of the address lookup. This creates a control object that provides a listener that can detect when a user selects and populates their address. I just hooked this up to the Redux form change action within my component's componentDidMount method:
componentDidMount() {

    let { dispatch } = this.props;

    window.control.load();

    window.control.listen('populate', function(address, variations) {
      dispatch(change('Form', 'address_line_1', address.Line1));
      dispatch(change('Form', 'address_line_2', address.Line2));
      dispatch(change('Form', 'address_line_3', address.Line3));
      dispatch(change('Form', 'address_line_4', address.Line4));
      dispatch(change('Form', 'city', address.City));
      dispatch(change('Form', 'post_code', address.PostalCode));
    });

  }

Great to see a good example provided here - thanks, @djvern!
This question is strongly related to React itself, and not to Redux Form.
So another way you could do it is to use a MutationObserver.
But this seems a lot more complex than simply using an API.


Chip8 from scratch

Reminder to do chip 8 system from scratch. It is designed terribly.

Ya. I need to definitely tear this down.


formatted code with "black" formatter and default settings

I just ran find -iname '*.py' -exec black {} \; from the code subdirectory...

Thank you for your contribution 👍

Thank you for your contribution :+1:

Thanks for merging so fast! :+1:  Not every maintainer does that.


ref(tests): remove calls to NewMockMeshCatalog from tests

Description:

Replaces calls to NewMockMeshCataloger with NewMockInterface to phase out the mesh cataloger interface.
Removes unused mock interfaces mock_catalog_generated.go, mock_endpoint_provider_generated.go and mock_service_provider_generated.go
Part of #5156

Testing done: Changes to test suite -- ensured existing test scenarios still pass

Affected area:

Functional Area

Tests
[x]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Did you notify the maintainers and provide attribution? no

Is this a breaking change? no

Has documentation corresponding to this change been updated in the osm-docs repo (if applicable)? n/a

lgtm, pending resolving the conflicts!

Codecov Report

Merging #5233 (0bcf3b2) into main (0f8e70b) will increase coverage by 2.58%.
The diff coverage is n/a.

:exclamation: Current head 0bcf3b2 differs from pull request most recent head a73a7f6. Consider uploading reports for the commit a73a7f6 to get more accurate results

@@            Coverage Diff             @@
##             main    #5233      +/-   ##
==========================================
+ Coverage   67.09%   69.67%   +2.58%
==========================================
  Files         198      195       -3
  Lines       16407    15791     -616
==========================================
- Hits        11008    11003       -5
+ Misses       5345     4733     -612
- Partials       54       55       +1

Flag
Coverage Δ

unittests
69.67% <ø> (+2.58%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/messaging/workqueue.go
89.28% <0.00%> (-10.72%)
:arrow_down:

pkg/envoy/generator/cds.go
86.84% <0.00%> (-5.27%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Have opened a follow-up issue #5239 for design doc changes as there will be multiple other changes to the design docs required after all the refactoring work is complete


rotation angle and number of output control

Hi Yuta,
I implemented on a sample dataset and I got images as the attached picture. I have two additional questions:

I don't need the middle image, how can I stop producing the middle image?
My rotations are not what I wanted, How can I control the image rotations? For example I want first upside down, the third image as vertical position.

Thanks in advance
Best

You can control the rotation by changing the extrinsic parameters.
In the example, line 82 defines the external parameters, in which one posture is represented by 6 degrees of freedom, translation and rotation angles (Euler angles).
If you want to remove the image in the middle,
Please change as follows.
Before:
extrinsic_R = utils.convertTransRotTo4x4([[0,0,0,90,0,0],
                                            [0,0,0,0,90,0],
                                            [0,0,0,0,0,90]])

After:
extrinsic_R = utils.convertTransRotTo4x4([[0,0,0,90,0,0],
                                            [0,0,0,0,0,90]])

Thanks a lot for your response :)
Have a nice day


Scala 3.0.0-RC1 in, Scala 3.0.0-M3 out

I prpoose we go ahead tag this as 1.2.0. @lorandszakacs called it 1.2.0-RC3 when preparing the release notes, but binary compatibility isn't promised in Dotty releases by most projects.

Had a bad rename of the macros. Trying again.


Template Assestion Error

I tried to set up the cookiecutter template and I get the folowing error after entering the Project Name.
cookiecutter https://github.com/at-gmbh/at-python-template
full_name [Jane Doe]: xyz
company_name []: Test Company
email<EMAIL_ADDRESS><EMAIL_ADDRESS>project_name [My Project]: Test Project
Traceback (most recent call last):
  File "/usr/bin/cookiecutter", line 11, in <module>
    load_entry_point('cookiecutter==1.6.0', 'console_scripts', 'cookiecutter')()
  File "/usr/lib/python2.7/dist-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python2.7/dist-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python2.7/dist-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/cookiecutter/cli.py", line 120, in main
    password=os.environ.get('COOKIECUTTER_REPO_PASSWORD')
  File "/usr/lib/python2.7/dist-packages/cookiecutter/main.py", line 82, in cookiecutter
    context['cookiecutter'] = prompt_for_config(context, no_input)
  File "/usr/lib/python2.7/dist-packages/cookiecutter/prompt.py", line 216, in prompt_for_config
    val = render_variable(env, raw, cookiecutter_dict)
  File "/usr/lib/python2.7/dist-packages/cookiecutter/prompt.py", line 170, in render_variable
    template = env.from_string(raw)
  File "/usr/lib/python2.7/dist-packages/jinja2/environment.py", line 880, in from_string
    return cls.from_code(self, self.compile(source), globals, None)
  File "/usr/lib/python2.7/dist-packages/jinja2/environment.py", line 591, in compile
    self.handle_exception(exc_info, source_hint=source_hint)
  File "/usr/lib/python2.7/dist-packages/jinja2/environment.py", line 780, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "<unknown>", line 1, in template
jinja2.exceptions.TemplateAssertionError: no filter named 'slugify'

Hi Nagmeh. Could you show me which version of cookiecutter you have installed (cookiecutter --version)? It looks like slugify was added to cookiecutter in version 1.7.1, so I
think this problem will be solved by upgrading cookiecutter to the latest version (pip install -U cookiecutter).
Although slugify is included in cookiecutter, it's not yet documented so it might be worth adding slugify as an explicit extension in cookiecutter.json. What do you think, @klamann ?

@naghmehfazeli yes, this should be solved with a cookiecutter upgrade. Please upgrade with conda update -c conda-forge cookiecutter or pip install -U cookiecutter
@Arrrlex I remember that there was a reason why I didn't add the extension to cookiecutter.json when we started using slugify, but I could be mistaken. We can look into this again, if you think it may be helpful.
We most definitely should add a troubleshooting section to the readme, because the issue of an outdated cookiecutter version has come up before.

@naghmehfazeli, the template also requires Python >= 3.6, it seems like you are currently using 2.7.

That doesn't seem right. I am inside a conda environment with python 3.7.6! Shouldn't the cookiecutter use that?

I had some problems in my setup.
The last version of cookiecutter was not installed inside my conda environment. I fixed that and now everything is working fine.
thanks

Cool, thanks for reporting back, @naghmehfazeli!

@Arrrlex I remember that there was a reason why I didn't add the extension to cookiecutter.json when we started using slugify, but I could be mistaken. We can look into this again, if you think it may be helpful.

A troubleshooting section sounds like the right thing to do to me :)


[SliderStyled] Add sx prop

This PR adds the sx prop on the SliderStyled component.
Example usage:
<Slider
  defaultValue={30}
  aria-labelledby="disabled-slider"
  sx={{
    m: 2,
    color: 'secondary.main',
    bgcolor: 'primary.light',
  }}
/>

I'm not really following how this prop is useful for complex components. Could you share a real-world use case?

Could you share a real-world use case?

https://material-ui.com/system/basics/#real-world-use-case (allow to remove the Boxes with clone). Basically allow closing #13100 with a demo.

I wouldn't recommend adding examples for this per component. Next step will be to introduce a documentation for the sx prop. We will need to re-think the whole system guide, I plan to work on that next week.

Could somebody summarize for me what the real-world use case is now? The PR body still has the styling that I wouldn't expect to find anywhere.

I wonder, did we drop the SliderProps type?


how to integerate swipe event to tab?

how i can integreate swipe touch event to tab component ?

Only with custom solution (for example using Hammer.js library) or use Swiper instead of tabs

ok.i will try thanks


ardour: 6.5 -> 6.7

Motivation for this change
Fixes:
https://github.com/NixOS/nixpkgs/issues/123295
https://github.com/NixOS/nixpkgs/issues/120705
Supersedes:
https://github.com/NixOS/nixpkgs/pull/119983
Please also backport to the next release version.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

Sorry for the bad commit, I totally missed #115121


CLOUD-828 stack - cluster relation change

@akanto @martonsereg

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1310/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1320/

LGTM


command failed: dotnet build myfirstbot.csproj

Describe the bug
while creating the bot by using bot framework composer ..its giving error after few steps.

Version

Version:  2.1.2
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0
Browser

Mozilla firefox

[ ] Electron distribution
[ ] Chrome
[ ] Safari
[] Firefox
[ ] Edge

OS

[ ] macOS
[] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to 'bot framework composer '
Click on 'create new'
Scroll down to 'under C# empty bot' then next then bot name, location, runtime type'
See error: command failed: dotnet build xyz.csproj

Expected behavior

empty  bot need to be created.
Screenshots

Command failed: dotnet build myemptybot.csproj
Additional context

I installed everything as mentioned in this document: https://learn.microsoft.com/en-us/composer/install-composer?tabs=windows
all are installed fine

@dmvtech ,
Thank you for the quick reply.
I resolved this issue with the help of my colleague. The problem was I only installed .NET code SDK 3.1.426 as mentioned in the document. I didn't having installed the .NET SDK 6.0.5 version. so I installed it and the created by using BFC. hope this helps someone who facing this problem.
The combination was Node 14xxx, .NET core SDK v3.1.426 , .NET SDK v6.0.5 and Bot Framework Composer v2.1.2

closing this issue as it resolved.


Add mkalias

mkalias
An alias management tool that creates/removes aliases and preserves them across shells/boots.

Has no interest.


Delete GPU dummy mempool

Original issue: https://charm.cs.illinois.edu/redmine/issues/1489

The dummy mempool inside GPUManager has not been used in a while, and should be removed.

Original date: 2017-11-27 20:39:03

Gerrit patch: ~~https://charm.cs.illinois.edu/gerrit/#/c/3329/~~ https://github.com/UIUC-PPL/charm/commit/38a875b1463cb7d37e73b484252efce4b377479e


AttributeError: 'function' object has no attribute 'Variable'

AttributeError                            Traceback (most recent call last)
 in ()
3 import torch.nn as nn
4 from torch.autograd import Variable
----> 5 from grid.clients.torch import TorchClient
6 import numpy as np
7 import re
~/OpenMined/Grid/grid/init.py in ()
----> 1 from . import clients
2 from .channels import torch_listen_for_obj_callback
~/OpenMined/Grid/grid/clients/init.py in ()
----> 1 from . import base
2 from . import keras
3 from . import torch
~/OpenMined/Grid/grid/clients/base.py in ()
----> 1 from ..workers import base_worker
2 from .. import channels
3 from grid.lib import utils
4 from .pretty_printer import PrettyPrinter
5
~/OpenMined/Grid/grid/workers/init.py in ()
1 from . import *
----> 2 from . import compute
3 from . import tree
4 from . import anchor
~/OpenMined/Grid/grid/workers/compute.py in ()
----> 1 from . import base_worker
2 from ..lib import strings, utils, output_pipe
3 from .. import channels
4 from ..services.fit_worker import FitWorkerService
5 from ..services.listen_for_openmined_nodes import ListenForOpenMinedNodesService
~/OpenMined/Grid/grid/workers/base_worker.py in ()
9 from ..lib import utils
10 from ..services.broadcast_known_workers import BroadcastKnownWorkersService
---> 11 from ..services.whoami import WhoamiService
12
13
~/OpenMined/Grid/grid/services/init.py in ()
4 from . import listen_for_openmined_nodes
5 from . import broadcast_known_workers
----> 6 from . import torch
~/OpenMined/Grid/grid/services/torch/init.py in ()
----> 1 from . import torch_service
~/OpenMined/Grid/grid/services/torch/torch_service.py in ()
1 from ..base import BaseService
----> 2 from .hook_service import HookService
3 from ... import channels
4 from ...lib import utils,torch_utils as tu
5
~/OpenMined/Grid/grid/services/torch/hook_service.py in ()
2 from ..base import BaseService
3 from ... import channels
----> 4 from ...lib import utils, torch_utils as tu
5
6 from collections import OrderedDict
~/OpenMined/Grid/grid/lib/torch_utils.py in ()
95 }
96 map_var_type = {
---> 97     'torch.autograd.variable.Variable':torch.autograd.variable.Variable,
98     'torch.nn.parameter.Parameter':torch.nn.parameter.Parameter
99 }

Hi, this is a copy of OpenMined/PySyft#1336.  You can check out the response there, and feel free to reach out with any further questions here!


Support for forcing driver in read_dataframe

I have some CSV data that uses a file extension that is not .csv. It appears that the OGR CSV driver only auto-detects CSV data if the extension is .csv. Is there a way to force the use of a specific driver when not auto-detected? It appears there is not already. This would be akin to driver in fiona.open.

It looks like Fiona uses the enabled_drivers to restrict the drivers that are checked by GDAL when opening a file for reading (not driver, which is used for writing).  It is unclear from the example in the docstring if it actually allows overriding the driver used to open the file, or if it simply constraints the set of drivers checked - which would still depend on file extension.
In pyogrio we have it enable all drivers at startup; I'm not sure we want to selectively enable some of them.
The GDAL Python bindings let you first obtain a driver instance and then use that to open a path, so it may provide a better example to check.

Have you tried this, from the GDAL CSV driver documentation?

For files structured as CSV, but not ending with .CSV extension, the 'CSV:' prefix can be added before the filename to force loading by the CSV driver.

Ooo... the driver documentation page is very long and I missed that. But yes that does work!
I'm happy to close this or keep it open in case forcing a driver is useful in other cases

We can close until there is an urgent need to add that capability for other drivers.

This works for all drivers already... the prefix to use is defined with the GDAL_DMD_CONNECTION_PREFIX metadata item of each driver, e.g.:
poDriver->SetMetadataItem(GDAL_DMD_CONNECTION_PREFIX, "MSSQL:");


[CI] Update rust-static-lib workflow

In this PR, the rust-static-lib workflow is updated to match the latest codebase and fix #92.

@hydai Please help review this PR. Thanks a lot!

@hydai The review issue has been fixed. Please help review the updated. Thanks!

@hydai Thanks for the review!


Include credentials when fetching audio urls.

Short description of changes:
Add options to set withCredentials to true on outgoing requests. This allows accessing audio resources hosted on a different domain.
Breaking in the external API:
None
Breaking changes in the internal API:
None
Todos/Notes:
Related Issues and other PRs:

#1310 fixed this.


need instructions added to load data/UCMerced_LandUse/Images/ from machine learning example

I remember a comment made during the presentation that the UC Mercred was to large to include in the instructional data.  That said it would be nice to include a note that the data can be downloded from the site, or possibly add a commented out download using intake.   Also, since the data is so large, maybe include a  small set that will get the examples working even if they will produce bad results.

thanks!


lxd/storage/zfs: Fix error reporting

Closes #6123
Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

Testsuite passed


tendermint: 0.32.10 -> 0.32.11

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tendermint/tendermint/releases.
meta.description for tendermint is: "Byzantine-Fault Tolerant State Machines. Or Blockchain, for short."
meta.homepage for tendermint is: "https://tendermint.com/"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.32.11 with grep in /nix/store/xngcpfl7gb7ik1554v582xns2sg9vxnh-tendermint-0.32.11

directory tree listing: https://gist.github.com/8facc48a1e6062cecc9aa00e442e0ec0

du listing: https://gist.github.com/81ce294006252f3614c3465de4c711aa

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
tendermint

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xngcpfl7gb7ik1554v582xns2sg9vxnh-tendermint-0.32.11 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A tendermint https://github.com/r-ryantm/nixpkgs/archive/683e7634980ce646617d34b2ad1257de67babf4d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xngcpfl7gb7ik1554v582xns2sg9vxnh-tendermint-0.32.11
ls -la /nix/store/xngcpfl7gb7ik1554v582xns2sg9vxnh-tendermint-0.32.11/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:
- tendermint

Maintainer pings
cc @alexfmpe @kalbasit for testing.

Builds and runs on my nixos


Kestrel connection limits on Windows?

I'd like to test drive a .NET 4.6 application on Kestrel (so Linux doesn't work afaik) including some load testing.
I was able to grab a potent enough machine but no server OS and am now worried if Kestrel suffers from the same "10 concurrent requests" disease IIS has on client Windows?
If necessary I could install a Server 2012 trial just for the test, but it would be good to know in general.

Please log this in https://github.com/aspnet/KestrelHttpServer/issues/.


Feature/ofdt 199 prepare tfs cli for deployment

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Integrate with reactive-grpc

Reactive gRPC is a suite of libraries for using gRPC with Reactive Streams programming libraries. Using a protocol buffers compiler plugin, Reactive gRPC generates alternative gRPC bindings for each reactive technology. The reactive bindings support unary and streaming operations in both directions. Reactive gRPC also builds on top of gRPC's back-pressure support, to deliver end-to-end back-pressure-based flow control in line with Reactive Streams back-pressure model.
Reactive gRPC supports the following reactive programming models:
RxJava 2
Spring Reactor
here is the link : https://github.com/salesforce/reactive-grpc

@qqeasonchen , I like to involve this feature , let me come up with analysis for further discussion.

@msdhinesh-geek sure ok.

Any update for this issue?

Hi @qqeasonchen @ruanwenjun
Thanks for your support. I am adding a gRPC design doc and protobuf data model. and generated java codes. Please review the following PR.  Let me know if you have any comments.
PR - https://github.com/apache/incubator-eventmesh/pull/593
Next step, I will write the code to support gRPC in Java-SDK and eventmesh-runtime

Due to code conflicts, I create a new PR - https://github.com/apache/incubator-eventmesh/pull/594


Is there a way to download older compiler version?

Description
I'm having some problems with compiler version 16.0 (described in #453), and was wondering if it's possible to grab previous version of edgetpu-compiler. Running
curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -
echo "deb https://packages.cloud.google.com/apt coral-edgetpu-stable main" | sudo tee /etc/apt/sources.list.d/coral-edgetpu.list
sudo apt-get update
apt-cache madison edgetpu-compiler

shows that no other version is available, but maybe I'm just looking in the wrong place.
Click to expand!
Issue Type
Build/Install
Operating System
No response
Coral Device
No response
Other Devices
No response
Programming Language
No response
Relevant Log Output
No response

Here  is the edgetpu_compiler version 15.0.340273435.

Thank you! Is it hosted anywhere public? I would need it to run as part of my CI job, but quick glance at the license tells me that I'm not really allowed to keep it in the public repo.

Curretly we are not maintaing legacy compiler versions. However, We have Edge TPU Compiler version 14.1.317412892 hosted public here. I will pass this to the internal team as feature request.
Thanks

Sounds great, thanks!

Here is the edgetpu_compiler version 15.0.340273435.

How is this supposed to be inatalled. It has no .sh file

Hi @Lagree007 no need of any installation. Just extract the zip folder and run the edgetpu_compiler command.
Please make sure your system has these requirements: https://coral.ai/docs/edgetpu/compiler/#system-requirements
hemanth@hemanth-glaptop:~$ ./Downloads/compiler/edgetpu_compiler -s test_data/mobilenet_v1_0.5_160_quant.tflite
Edge TPU Compiler version 15.0.340273435

Model compiled successfully in 405 ms.

Input model: test_data/mobilenet_v1_0.5_160_quant.tflite
Input size: 1.33MiB
Output model: mobilenet_v1_0.5_160_quant_edgetpu.tflite
Output size: 1.54MiB
On-chip memory used for caching model parameters: 1.48MiB
On-chip memory remaining for caching model parameters: 6.22MiB
Off-chip memory used for streaming uncached model parameters: 0.00B
Number of Edge TPU subgraphs: 1
Total number of operations: 31
Operation log: mobilenet_v1_0.5_160_quant_edgetpu.log

Operator                       Count      Status

CONV_2D                        15         Mapped to Edge TPU
SOFTMAX                        1          Mapped to Edge TPU
DEPTHWISE_CONV_2D              13         Mapped to Edge TPU
AVERAGE_POOL_2D                1          Mapped to Edge TPU
RESHAPE                        1          Mapped to Edge TPU


Make the library accessible through a Maven repository

The library should be accessible via Maven Central or JCenter (bintray) in order to make it usable in other projects.

It is possible to use any GitHub project via JitPack.io which can build the project just in time (hence the name). No additional configuration is necessary to publish it - just add jitpack.io as a repository

Nice. Then you should create a GitHub release and provide a hint for the users to show them how to include it into their build.


Remove ArrayBufferView from globals

ArrayBufferView doesn't seem to exist in any environment, and it looks to be succeeded by DataView.

Updated to also remove it from tests.

Coverage remained the same at 96.56% when pulling e3b7c2826668b48161d7046141d2c3bc10063198 on silverwind:remove-arraybufferview into e6611af2d180bd2317d5762e85807a481de99ccb on jshint:master.

Updated commit and PR title.

Coverage remained the same at 96.56% when pulling 40000d809fbccf1a1076557e4adb6091c6994a71 on silverwind:remove-arraybufferview into e6611af2d180bd2317d5762e85807a481de99ccb on jshint:master.

Your correct it is not present in the browser.
https://html.spec.whatwg.org/multipage/infrastructure.html#arraybufferview
https://developer.mozilla.org/en-US/docs/Web/API/ArrayBufferView
It is a type created for the spec, it does not exist as an interface or object in the browser.

@jugglinmike I don't think this is breaking because it was never actually defined.. am I ok to rebase and push it?
Just checking because technically it is a breaking change.

It's definitely low-risk, but I also don't think there's any urgency here, so I'm happy to defer this for 3.0.


what is new for 2.0 ?

Docs http://docs.spring.io/spring-android/docs/2.0.x/reference/pdf/spring-android-reference.pdf
do not explain why there is major version increase.

@royclarkson when do you plan to release 2.0? There was no activity on this repo since December. :cry:

@paulvi 2.0 was started in response to some changes in Spring Framework's RestTemplate. Spring for Android's RestTemplate had made some different API choices, and the initial goal of 2.0 was to bring those two close to parity. The major version number update was because of some of these minor, but breaking changes.
@WonderCsabo Unfortunately, we've had changes in priorities which mean this project is not receiving much attention right now. I'm happy to facilitate merging PRs, triaging issues, and pushing out releases.

Thanks! I was just asking so we can communicate  this correctly in the downstream AndroidAnnotations project.

@royclarkson BTW what is stopping you from release 2.0 as the current HEAD? Are there any blocking issues or missing features?

There's not anything critical, IIRC. I had gone through and merged in many of the improvements and updates from Spring Framework already. The main outstanding issue is the OkHttp support as mentioned in #24, and of course doc updates.

Alright, OkHttp (#24) support is in a better place now. Here are a few other outstanding items that would be nice to have addressed prior to pushing a GA.

remove Jackson 1.x support
update dependencies and fix resulting issues
https://jira.spring.io/browse/ANDROID-168
https://jira.spring.io/browse/ANDROID-163
https://jira.spring.io/browse/ANDROID-143

Went ahead and knocked out those first two items on the list.

What is the ETA of final release of 2.0?

2.0.0.M3 is now available for testing. It includes the latest OkHttp improvements. @jaredsburrows unfortunately, I don't have a specific ETA for the GA. I'm juggling some priorities, but working on getting those last few issues cleaned up. Thanks.

Hi, Roy. Will there be support for PATCH or should I like for another solution?
If anyone has a good reference in solving this usecase, I'm all eyes.
Thanks.

We have PATCH support in the latest 2.0 milestone. You can see the usage in code via a search. Most versions (or all?) of the native Android HTTP clients do not support PATCH, however. You'll need to include the dependency for either the Android port of Apache HttpClient 4.3, or OkHttp to make use of it. Hope that helps.


The AWS device module does not allow you to retrieve the device region

Describe the bug
According to the documentation I can retrieve the regions of a device via the Braket SDK. This doesnt appear to be supported in the code.
The Amazon Braket SDK the docs state that you can access the device region as a property of your declared device: https://amazon-braket-sdk-python.readthedocs.io/en/stable/_apidoc/braket.aws.aws_device.html#braket.aws.aws_device.AwsDevice. Here's the doc string: https://github.com/aws/amazon-braket-sdk-python/blob/main/src/braket/aws/aws_device.py#L70.
To reproduce
Open https://amazon-braket-testnbiex.notebook.us-east-1.sagemaker.aws/notebooks/Braket examples/braket_features/Getting_Devices_and_Checking_Device_Properties.ipynb and modify cell 20 to
# the managed simulator SV1
device = AwsDevice("arn:aws:braket:::device/quantum-simulator/amazon/sv1")

print(device.DEVICE_REGIONS)

You will get an attribute error AttributeError: 'AwsDevice' object has no attribute 'DEVICE_REGIONS'
Expected behavior
The statement returns the device regions. In this case: ('us-east-1', 'us-west-1', 'us-west-2', 'eu-west-2')
Additional context
This bug is the inconsistency between the documentation and what's supported. Function and docs need to be reconciled.

Calling device.DEVICE_REGIONS does not return anything by design.
Pushed: https://github.com/aws/amazon-braket-sdk-python/pull/321
A follow up fix is needed for including a device.regions property. This is being discussed to align on the implementation details.

Resolving since this has been fixed by #321


Fix 'secrets.GITHUB_TOKEN' reference

Why:
This is doesn't match the rest of the document:

Closes: N/A

What's being changed (if available, include any code snippets, screenshots, or gifs):
{{secrets.GITHUB_TOKEN}} changes to ${{ secrets.GITHUB_TOKEN }} to match other references/usage in the document.

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

[!WARNING]
The token wraps over two lines, not sure what the call is for scenarios like this: a) The inline code has to be formatted correctly regardless of how it looks or b) it can change to make the presentation better.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
[x] For content changes, I have completed the self-review checklist.

@itecompro Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏


h2o for kv cache compression

Type of Change
feature
Description
H2O: Heavy-Hitter Oracle for Efficient Generative Inference of Large Language Models
paper
NTD

[x] example
[x] refactor code to same style
[x] add seq len api
[x] support for more models, both sim and real
[x] mean accumulate score function

Expected Behavior & Potential Risk
None
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
any library dependency introduced or removed

pre-commit.ci autofix

Could we add a document introducing what h2o is?

format scan will improve by https://github.com/intel/intel-extension-for-transformers/pull/1647.

Could we add a document introducing what h2o is?

add in the example/readme


JSON Schemas for v3.0 Encoding object missing pattern properties for extensions

The schema for the Encoding object is missing patternProperties for extension properties.
patternProperties:
  '^x-': {}

https://github.com/OAI/OpenAPI-Specification/blob/9764b45c8f824a83b441674ff0872f72b8e5f332/schemas/v3.0/schema.yaml#L1001-L1024
I will open a PR if the maintainers agree this should be added.

Agree with your assertion, a PR would be great against the main branch.


Exposes the Charges piece of Nuclei to Python

Is this pull request associated with an issue(s)?
No
Description
Right now in Python we can't call gradient modules correctly because Nuclei didn't expose the Charges piece. This PR fixes that.
TODOs
None if CI passes.

Also, add #include <sstream> to src/python/chemical_system/point_charge/export_charges_view.cpp to appease Clang.

🚀 [bumpr] Bumped! New version:v1.2.8 Changes:v1.2.7...v1.2.8


Connect the codecoverage to scrutinizer

I have configured the code coverage report from scrutinizer and add the badge to the readme file.
It has 3 steps

Add scrutinizer/ocular
Allow remote code coverage in .scrutinizer.yml
Add the badge to the readme

Cool, thanks!


[landing] schema for path-manager vs scheduler

The idea would be to have a dedicated schema for each concept:

PM: path (subflows) creation and deletion (typically on the client side), and addresses announcements (typically on the server side, to tell it can be reached via another address, or one address of the client/server got removed).
Scheduler: where to send data on the available paths. (note: its goal might not be to use all the available bandwidth, it can also pick only one path (faster, less lossy, etc.), or duplicate data over multiple subflows)

You can get some inspirations from https://lpc.events/event/16/contributions/1354/attachments/999/1927/LPC2022 - MPTCP - eBPF + Netlink.pdf (pages: 9 and 13)
While at it, it is important to mention that a "subflow" == "path" in the "Here is how it works" paragraph.

@mux99 I don't remember which ones you wanted to do: these 2 and the main one?


PPO Linen example

Reinforcement learning (proximal policy optimization) example ported to Linen API.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #508   +/-   ##
=======================================
  Coverage   80.05%   80.05%
=======================================
  Files          55       55
  Lines        4002     4002
=======================================
  Hits         3204     3204
  Misses        798      798

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 45937af...ae576bd. Read the comment docs.

What are the remaining issues on this example for it to be merged? /cc @wrzadkow @jheek

@googlebot I signed it!

Hi Avital, from my perspective there are no major issues to fix here but of course I'm open to suggestions from code review. In the meantime, I committed the same changes that were introduced for non-Linen example in PR #541 . Thanks for following up!


[BEAM-6145] Revert "Merge pull request #7051 from markflyhigh/py-move-off-apitools-1"

R: @markflyhigh @chamikaramj

Run Python PostCommit

LGTM

LGTM. Thanks.

Run Python PostCommit


Is it possible to add jest tests to sample app?

Is it possible to add jest tests to sample app? I'm trying to add tests in my application, but i can't mock properly this library.
Thanks.

Hummm, I dont I'm not sure about that, but you would have to mock the component's callback events.

Does anyone have any clue regarding this. I have failed also trying to mock if anyone succeeded (any help with be appreciated)

Did you try to mock the module?
https://jestjs.io/docs/tutorial-react-native#tips

anyone was able to get the tests or mock the package
@ergenekonyigit @Khalilw1


[ast] Add inline wavejson for waveform images

@zi-v our documentation tools can render the wavejson format directly, so there is no need to paste the code and a screenshot in the docs.
This cleans up the related sections and replaced the image with inline code snippets.
Here are the resulting images when processed:

Signed-off-by: Michael Schaffner<EMAIL_ADDRESS>

Thanks @msfschaffner
Note that we auto generate the hjason from the google doc every revision and we sometimes look directly at the google doc source. If it is not of a problem for you, I prefer to keep it as is.


To be non-blocking

This library should not block application logic, so simply specify non-blocking flag to sendto(2) and if the operation which about to doing will block, just give up to send the message and pass the error to error handlers.

Coverage increased (+0.002%) to 99.787% when pulling 0c9eb4b4b508fdea6032e79226ade9ce0f97f66d on non-blocking into 3d6539b6cc24fa02b8ca9f2e9a268b0c05d5a3ad on master.


Parameters setting for indoor navigation tasks

I am preparing a indoor uav navigation task, in order to achieve collision-free flight i use avoidance. When I set the start position is (0,0,1.5), then drone can take off and hover at 1.5m and wait for next destination, next I choose a point free on octomap whose altitude is 1.5m, it always shows that the goal is occupied. My parameter is set as cell_scale=0.5, octomap resolution=0.5, goal_altitude=1.5, min_altitude=0, max_altitude=3, ground_obstacles_filter=0.
In addition, for indoor navigation, our drone is not very large, so above parameters may be rough. Could I set the cell_scale less than 0.5. and decrease the octomap's resolution, or some other suggestions for narrow obstacles avoidance?
Thanks,
Joey

@JoeyLeeNPU The current global_planner is not usable for indoor navigation, as it uses priors of the occupancy probability of altitude (it is less probable to be occupied as the altitude increases). Therefore, it is likely that you will have a collision with the ceiling.
A more robust planner is being developed on #453

hah! I see #453 and it may be a better solution for indoor navigation, but I also want to have a try on traditional global planner in avoidance.
In a room, I try to set cell_scale in source file as 0.5 and set the octomap resolution as 0.25 in debug window, changing parameter cell_scale  may not work, so I met that no matter how I change it, I can't get the desired value. Finally, I change it in the source code file.
For altitude priors, I set the altitude below 3m equal, and increase the cost of rising.
If OMPL added into avoidance, i will try it as soon as possible.
Thanks for help,
Joey

@JoeyLeeNPU Awesome. I have seen some implementations working indoors with the changed priors, and seems to work with some modifications.
It would be cool if you can contribute the changes so that everyone else can also use it indoors

@Jaeyoung-Lim Okay, I will make some changes to meet both indoor and outdoor obstacle avoidance flights. If a lot of tests are successful, I will share my experience.
Cheers,
Joey


kbfs doesn't work on linode headless server

[write something useful and descriptive here]
my log id: 0f979c7bc8410eda7a02c01c

Try keybase unlock --stdin?  Normally the problem is that you haven't unlocked your device private key, and there's no GUI to prompt you for that.  But @cjb has more experience than I do with this.

The very bottom of the KBFS log eventually shows logged in progress followed by a hang.

@cjb: that's not progress.  Looks like the user canceled an operation that was waiting on the exponential backoff algorithm to try again.  I don't see any successful authentication.

Oops.  Thanks, I agree.

I've had a similar issue on my Chromebook, trying to view files in /keybase/public/jamgregory after running run_keybase. I'm guessing it hadn't unlocked, and so hung at that point. After I ran keybase unlock, it seemed to work OK.


Keda prometheus trigger keeps returning empty results though present

Report
keda-operator:
Image:      ghcr.io/kedacore/keda:2.12.0
API Version:  keda.sh/v1alpha1
PrometheusQuery:         kaka_query{topic="event.x-y.v1"} offset 2m
The prometheus query keeps returning Zero (0) though query is valid and data is present  But a curl returns data fine for the same.
"s0-prometheus" (target average value):                 0 / 3900m
$ kubectl describe hpa -n <>
Metrics:                                                  ( current / target )
  "s0-prometheus" (target average value):                 0 / 3900m
  resource memory on pods  (as a percentage of request):  23%<PHONE_NUMBER>0m) / 10%
  resource cpu on pods  (as a percentage of request):     6% (19m) / 10%
Min replicas:                                             3
Max replicas:                                             10
Rollout pods:                                             10 current / 10 desired
Conditions:
  Type            Status  Reason            Message
  ----            ------  ------            -------
  AbleToScale     True    ReadyForNewScale  recommended size matches current size
  ScalingActive   True    ValidMetricFound  the HPA was able to successfully calculate a replica count from memory resource utilization (percentage of request)
  ScalingLimited  True    TooManyReplicas   the desired replica count is more than the maximum replica count
Events:           <none>```

$ kubectl describe scaledobject -n <>
```yaml
API Version:  keda.sh/v1alpha1
Kind:         ScaledObject
  Scale Target Ref:
    API Version:  argoproj.io/v1alpha1
    Kind:         Rollout
    Name:         ltb-golang-microservice
  Triggers:
    Metadata:
      Aws Region:          us-east-1
      Identity Owner:      operator
      Ignore Null Values:  true
      Query:               kaka_query{topic="event.x-y.v1"} offset 2m
      Server Address:      ServerAddress
      Threshold:           3.9
      Unsafe Ssl:          true
    Type:                  prometheus
    Metadata:
      Value:      10
    Metric Type:  Utilization
    Type:         cpu
    Metadata:
      Value:      10
    Metric Type:  Utilization
    Type:         memory
Status:
  Conditions:
    Message:  ScaledObject is defined correctly and is ready for scaling
    Reason:   ScaledObjectReady
    Status:   True
    Type:     Ready
    Message:  Scaling is not performed because triggers are not active
    Reason:   ScalerNotActive
    Status:   False
    Type:     Active
    Message:  No fallbacks are active on this scaled object
    Reason:   NoFallbackFound
    Status:   False
    Type:     Fallback
    Status:   Unknown
    Type:     Paused

Expected Behavior
successful query should return:
value: 4
{"status":"success","data":{"resultType":"vector","result":[{"metric":{"name":"kafka_server_received_records","topic":"event.x-y.v1"},"value":[1705616102.962,"4"]}]}}
curl query had returned the above successful result.
but keda scaled Object keeps reporting zero.
Actual Behavior
keda-operator:
Image:      ghcr.io/kedacore/keda:2.12.0
API Version:  keda.sh/v1alpha1
PrometheusQuery:         kaka_query{topic="event.x-y.v1"} offset 2m
The prometheus query keeps returning Zero (0) though query is valid and data is present  But a curl returns data fine for the same.
"s0-prometheus" (target average value):                 0 / 3900m
Steps to Reproduce the Problem

do a curl against the prometheus endpoint.

Logs from KEDA operator
No response
KEDA Version
2.12.0
Kubernetes Version
1.25
Platform
Amazon Web Services
Scaler Details
No response
Anything else?
No response

Could you share your Scaledobject?


Invoke-WebRequest and Invoke-RestMethod: broken tab completion with respect to common parameters

Note: I haven't looked into what pattern underlies the behavior: the two cmdlets definitely exhibit the broken behavior, while spot-checking others suggests that they're not affected.
Steps to reproduce
Invoke-WebRequest -out<tab>  # press <tab> repeatedly
Invoke-RestMethod -out<tab>  # press <tab> repeatedly

Expected behavior
-out should expand to -OutFile (cmdlet-specific parameter), then to common parameters -OutBuffer and -OutVariable
Actual behavior
-out expands to -OutFile, but nothing else.
If you type -outb or -outv before pressing TAB  - i.e. if you type an unambiguous prefix - the common parameters are found.
Environment data
PowerShell Core 7.0.0-preview.4

This seems to be broken for any parameter name that could potentially conflict with a common parameter name from a given tab completion.
function test {
    [cmdletbinding()]
    param($Pipecleaner)
}

test -pipe<tab>

Tab completion is unable to pickup -PipelineVariable

Dupe of https://github.com/PowerShell/PowerShell/issues/1265


Measure max shooter range and precision with mechanical limiters and stops removed

We have achieved at least 50/50 shots at 16 feet.  18, 20, and 22 ft shots are more risky.  Issue is that precision suffers 1ft error in either direction when at 18ft+.  Partial correction is software:  switch off the in-house pid commanding volatage to using internal Flex Position PID control, but also hardware: the following are mechanical issues:

Note is clipping white board.  Change the board material and ensure it's not too high at the center and clipping note.
Distance between transfer and Flywheels needs to be increased such that note is never touching both flywheels and transfer at same time.
Would like to remeasure after these are fixed.

Also a dead issue.  Closing.


Cannot download ModelNet40 dataset

Hello @vinits5,
Thank you for this amazing work.
I would love to try out your package but i can't manage to download the ModelNet 40 data used in the examples.
Both your download class (dataloaders.py) and direct download link (https://shapenet.cs.stanford.edu/media/modelnet40_ply_hdf5_2048.zip) in a browser are not working, the connection is timing out .
Do you know another link to access the dataset ?
Thanks,
Barnabe

Hey @barnabe-perspectives ,
I think the link still works. Please try the following link from browser:
https://shapenet.cs.stanford.edu/media/modelnet40_ply_hdf5_2048.zip
(It's working in my web browser. If it fails then do send me you email, I will share the data with you.)

Hey @vinits5 ,
I can't download this dataset , can you share with me ?.


IStringLocalizer support in Blazor

Does the statement that "IStringLocalizer<> is supported in Blazor apps" mean that I may to inject and use it in my own code or is it used also internally (e.g. for localizing error messages)?

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

ID: 15e7c51d-1839-1849-813a-23c4d21c64ae
Version Independent ID: d6f07538-228e-9f96-680f-6c324caf11d6
Content: ASP.NET Core Blazor globalization and localization
Content Source: aspnetcore/blazor/globalization-localization.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @TPIvan ... Yes, that's right. Here's how the JsonStringLocalizer example (one of the example projects listed at https://docs.microsoft.com/aspnet/core/fundamentals/localization-extensibility#localization-resources) demos it (injected into Configure) ...
https://github.com/hishamco/My.Extensions.Localization.Json/blob/master/samples/LocalizationSample/Startup.cs#L20

So it is not used by Blazor framework internally.

Sorry ... I missed the 2nd part of your question. It seems yes ... it is used internally. However, the setup might not be as devs expect. I noticed various discussions on the subject that lead to me to believe that either cross-links or an outright example would be helpful. For example ...

https://stackoverflow.com/questions/59659489/how-to-localize-validation-message-dataannotationsvalidator-in-blazor-server-s
https://stackoverflow.com/questions/59033230/how-to-add-viewmodel-localization-to-blazor

I'd like to take a closer look at this. However, we're crazy busy these days, so I'll need to backlog this for a while until I get some free time to take a closer look.
If you need help, devs apparently have been working with localization in Blazor, including localization of error messages. Reach out on the usual support channels if you don't find what you need in blog resources and the ASP.NET Core docs in the main doc set ...

Stack Overflow
ASP.NET Core Slack
ASP.NET Gitter

Note to self: https://github.com/dotnet/aspnetcore/issues/12158.

Ok ... I took a closer look. Loc issues are being addressed by engineering. They don't have a "loc" label, but searching blazor-labeled issues with "localization" turned up ...
https://github.com/dotnet/aspnetcore/issues?q=is%3Aopen+is%3Aissue+label%3Aarea-blazor+localization
I think what we call out in the topic as "supported" is correct today. Other loc features should be covered in the engineering issues or requested on the engineering repo. When data annotations are available, then we'll open an issue to cover it when the time comes.
I don't think we'll have time to add a dedicated loc sample. I'm having this little break for a few months to get caught up on issues, then :boom: 5.0 preview issues are going to start appearing here.


Get-NavContainers.ps1 : Adding a parameter: ContainerName to filter on the container name

Update Get-NavContainers.ps1
Adding a parameter: ContainerName
to filter on the container name

@microsoft-github-policy-service agree

Why not just use:
Get-BcContainers | Where-Object { $_ -like 'bc*' }

With -includeLabels - it would be
Get-BcContainers -includeLabels | Where-Object { $_.name -like 'bc*' }

But I guess you found out.


win8  get_adapter_index  err Unable to find matching

Do you have any extra context here that would help us to fix?

Fixed by https://github.com/nulldotblack/wintun/pull/26


Document new checkboxes feature :book:

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

Project coverage is 81.74%. Comparing base (824aa5f) to head (12f2455).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #343   +/-   ##
=======================================
  Coverage   81.74%   81.74%
=======================================
  Files           8        8
  Lines         378      378
  Branches       55       55
=======================================
  Hits          309      309
  Misses         67       67
  Partials        2        2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add gemm and simd src code

We migrated the chisel code in the separate repos in this PR.
The test for these two accelerators will be added later, including

sw test in C (next PR)
scala test (in the longer term)

chisel_acc is a temporal name. Please let me know if there is a better name.

Hi @jorendumoulin

Wait, we cannot just copy and paste the code from gemm right?

It is not a just copy and paste. I updated the gemm a bit.

The code should not live in two places at the same time, either we move it here, or only the external repository. Otherwise we return to the problem if one thing needs to change we need to change it in two spots!

Yes, we will remove the old gemm repo from snax_cluster  in the next pr.

If you need help on how to make this happen with mill or sbt, let me know!

What do you mean make this happen with mill or sbt,? :)

Could you maybe just take a look at this if it is possible like this?
https://github.com/jackkoenig/mill-multi-project
Or for sbt  (seems more difficult)
https://www.scala-sbt.org/1.x/docs/Multi-Project.htm

Could you maybe just take a look at this if it is possible like this? (Jack Koenig is the lead developer of chisel, so he must know what he's doing 😆 ) https://github.com/jackkoenig/mill-multi-project
Or for sbt (seems more difficult) https://www.scala-sbt.org/1.x/docs/Multi-Project.html

Nice finding! It seems doable to manage several projects and share the code between them. But we can also view the accelerators as one big Scala project? In that sense, is it ok to maintain the file structure as we have now?
How about leaving this file structure for now but if we indeed need improvement then we discuss it later?

Hi, wait, not yet! Actually, the goal I put it together is to make the gemm and rescaling simd together. We would like to view it as a big accelerator because they are so interdependent.
I just realized later they need to be combined that is why I want them together.
It just so happens we can also separate them but it makes much more sense that they are combined to reduce having to load/store into memory many times!
It's funny because the latest reviewer from the MICRO paper also said to combine them together!

Hi,
I like this PR, because now it seems we are going for a more monolithic repo after all :D
I think doing a multi-project build for each and every accelerator is a bit against the purpose of going monolithic, so I'm not sure I agree with @jorendumoulin? For sure we would need it later if people want to include their own accelerator as an external dependency.
Note that we are already shipping two distinct packages inside this repo (the accelerators and the streamers) and if we'd like to keep them seperate (should we really though?), a correct setup for a multi-project build might be beneficial here after all.?
I don't like

I updated the gemm and cleaned a bit. :)

Can you make an overview of what you changed (just for us for future reference!)? We can not see the diff here, because all these files are new changes in this repository! Without knowing what you did, I think It would have been better if you did the changes there first and later migrated them here?
Is there any reason why we are still using sbt and mill together? Can we not just move to a single build system?
@xiaoling-yi there is no CI change in this PR. Since you are adding sbt build files it seems like you are doing a local build anyway. I think it still makes sense to add a simple scala build here, even if it is to change it in the next pr. You never know what is setup wrong; the devil is in the details here.
Overall this is a really nice progression in my opinion.


Geocoding using Google Maps API

Adding scripts use to geocode a given sheet.

@NirantK updated the branch with proposed changes. Requesting another review.


migrate existing areas directly under a space to the child of the root area

closed in https://github.com/almighty/almighty-core/pull/913


adding custom worker demo

adds a customer worker demo

I deleted my comment about html-sanitizer since that's a bug and it will be reported on the respective repo.


 But Master Discovery continue to wkorking.   Maybe you can write a subscribe to discovery node or when it restart to take any message from discovery it can restart master synchronization again. We use your project at our project. İf ı know phyton well i would do it myself.

Do you have still problems with synchronization?


Adds jsdocs

Adds some missing jsdocs. Still a few outstanding.
Additions

Adds missing jsdocs to methods that were missing them.

Review

@sebworks
@KimberlyMunoz
@jimmynotjim

:

It's not everything, but it's a start.


live_stats removed to fix memory leak

Live stats removed to avoid memory leak

Event source removed from stats to prevent client to start listening to live_stats api

I also recommend to disable keep-alive param on the load balancer side.

Forgot to include from api,
That should mitigate the resources a open on that channel

Also you can try to increase the update interval, ideal every minute. It will give some time to finish all processes.
    "stats": {
        "updateInterval": 60,
        "historicalRetention": 14400,
        "hashrateWindow": 300
    },

@michaelotis thoughts?

We’ve already removed live_stats completely. It didn’t fix the mem leak issue

It is clear that code is not the problem, every znomp implementation runs the same code, how did you sort things out?
Do you keep front end separated from stratum and daemon running on different box?
Do you have at least 8gm of ram and 4gb of swapping, are you using p2p for block notify or blockRefreshInterval=0,

We have more than enough to run z-nomp on the server. We thought last month it was created by us messing with the code, but this is a fresh install.
Also, how many z-nomp instances do you know of running more than 1000 workers? It appears most do not and this explains why it is not an issue for them.

@BlueSilver22 1000 workers should be nothing, and number of workers is more related to cpu rather than mem (miningspeed, nanopool does among others). NodeJs is backed up on Cluster module which spawn multiple threads to handle multiple processes. Unless you are getting getting DDoS attacked you will experience only cpu. Memory leak should be related to objects not being cleared from memory nor eligible for garbage collectors, and this z-nomp impl is not pilling up objects on stack, the only variable that keeps that many data in memory is statHistory which can be controlled by retentionTime from config.
I recommend to implement newrelic to do introspection on the instance you are running, it will tell you exactly where is it happening.


Add a QR Code to the Port forwarding tab

Local Port Forwarding is one of my favorite features as we work a lot with NFC devices and phone browsers. It would be fantastic if the forwarded address would not just be shown as a URL but also as a QR code so that it can be easily scanned on the phone. The expo.dev React Native guys do this and it makes it such a pleasure to work with.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Add wlr_touch frame signal

I was wondering why wlr_touch does not have a  frame event like wlr_pointer has.
In the libinput backend the corresponding event LIBINPUT_EVENT_TOUCH_FRAME is declared as noop, and that according to git blame already for longer
In the wlr_seat implementation a frame event is currently directly sent after each touch event.
Would it make sense to implement a touch signal that relays the libinput event?

Yup, seems like on oversight. We should definitely add it.

Done in https://github.com/swaywm/wlroots/pull/3001.


unable to actuate number of people in a zone

Hi. I have been trying to simulate varying the number of people in a zone, but I keep getting the following error

Exception ignored on calling ctypes callback function: <function EmsPy._enclosing_callback.._callback_function at 0x11cb99ee0>
Traceback (most recent call last):
File "/Users/yash/Documents/Zodhya/RL-EmsPy/emspy/emspy.py", line 543, in _callback_function
self.set_ems_handles()
File "/Users/yash/Documents/Zodhya/RL-EmsPy/emspy/emspy.py", line 276, in set_ems_handles
setattr(self, 'handle' + ems_type + '' + name, self._get_handle(ems_type, handle_inputs))
File "/Users/yash/Documents/Zodhya/RL-EmsPy/emspy/emspy.py", line 308, in _get_handle
raise Exception(f'ERROR: [{str(ems_obj_details)}]: The EMS sensor/actuator handle could not be '
Exception: ERROR: [('People', 'Number of People', 'People_1')]: The EMS sensor/actuator handle could not be found. Please consult the .idf and/or your ToC for accuracy

This is the People object in my IDF file
`
People,
People_1,                               !- Name
Ergo Office 1,                          !- Zone or ZoneList Name
Ergo Schedule,                          !- Number of People Schedule Name
People,                                 !- Number of People Calculation Method
1,                                      !- Number of People
,                                       !- People per Zone Floor Area {person/m2}
,                                       !- Zone Floor Area per Person {m2/person}
0.3,                                    !- Fraction Radiant
,                                       !- Sensible Heat Fraction
Ergo Activity;                          !- Activity Level Schedule Name
`
And this is my tc_actuator dictionary
tc_actuators = {     'zn0_people': ('People', 'Number of People', 'People_1'),  # deg C }

Dear @asrjy
Do you have fixed the problem above?  Could tell me the detail?
Best Regards;


v0.4.0 state fixes

The post with id 143 has parent id 170 but I think it should be 136 instead as I recall it being a response to that question. Also 170 is surely invalid. We should fix it

This needs to be taken into consideration after exporting the state for the new version


Set the tombstone response type as text/plain

Resolves: https://jira.duraspace.org/browse/FCREPO-2123

This does not change the serialization of tombstone resources, but it does change the content-type to reflect the actual response body.


vscode-client: make LanguageClient platform-independent

Platform-specific routines remain in main.ts, but consumers can now import client.ts without requiring any Node or Electron dependencies. This makes it possible to use LanguageClient in platforms other than Node+Electron.
Consumers of client.ts merely need to provide a () => Thenable<{reader: StreamMessageReader, writer: StreamMessageWriter}>.
The main.ts API remains unchanged and should be 100% backward-compatible. The client.tests tests pass.
The large size of this diff is misleading. The changes were in 2 steps:

Move the LanguageClient from main.ts to a new file client.ts
Create a LanguageClient in main.ts that extends the "base" LanguageClient in client.ts, and move Node/Electron stuff from client.ts to overrided methods in main.ts's LanguageClient

No new "real" code was added.
I would love to get feedback on this diff early, so I created this PR. Happy to go back to the drawing board if this is not something you are willing to merge.

Btw, allowing to pass Promises/Thenables as parameters is considered an antipattern. It just makes code more complicated, the callee should let the promise resolve before calling the function.

@sqs nice work. Could you look into signing the CLA ?

@dbaeumer Done, thanks!

Hi, I am closing and re-opening this PR to bump the CLA bot. Sorry for the inconvenience!

@dbaeumer The only outstanding thing I'm aware of is the InitializeParams processId. This PR contains this change:
-                       processId: process.pid,
+                       processId: typeof process !== 'undefined' ? process.pid : 0,

I can either change the TypeScript definition of InitializeParams to allow processId: null (which conforms to the LSP spec), or leave this at 0. I have no preference.
Otherwise, let me know if you'd like to see any changes. Thanks! :+1:

@sqs I would change the protocol.ts to have | null for the processId. A couple of other comments:

I would name streamOpener streamProvider. This is more in line with the naming we have in VS Code.
I would name LanguageClient BaseLanguageClient in client.ts and make it abstract
I would add a file browser.ts (I am open for a different name. Agree that browser is not optimal) which exports a LanguageClient extending BaseLanguageClient.

This better ensures that we can further develop that design/
And again thanks for the work you are doing here.

@sqs: there seems to be another bigger thing to do here. The json-rpc library currently used by the client.ts file heavily depends on node as well. So we also need to restructure the json-rpc library to ensure that the client part is not relying on any node specific code through the json-rpc library.

@dbaeumer I implemented the first three changes. I am not to sure what benefit a browser.ts would provide if it is just this?
export class BrowserLanguageClient extends LanguageClient {}

Let me know if you still want me to add it.
I would look at jsonrpc next and do a separate PR for that if that is okay.

@felixfbecker thanks for continuing on this.
I would still introduce a second file browser.ts (as said I am open for a different name). Otherwise non npm clients need to instantiate BaseLanguageClients which looks strange IMO.

@dbaeumer done

@felixfbecker browser.ts imports main.ts, which depends on the child_process module. You'll need to rework that.

is webpack less strict than requirejs?
with requirejs it traverses the entire import tree. if something tries to import something it doesn't know about it complains - child_process.
globals, need to be treated differently.
do you have a special build config? would be nice to take a look.

Sorry, this was a typo. browser.ts was supposed to reexport client.ts, not main.ts. Fixed now.

@dbaeumer anything else?

@felixfbecker sorry, I was busy with some emergency fixes and will be out on vacation next week. Will comment on the PR when I am back. I you don't hear anything please ping.

ping @dbaeumer

@felixfbecker thanks for the ping. The thing I am not sure about yet is if there is work needed on jsonrpc as well. vscode-languageclient depends on vscode-jsonrpc which is highly node dependent. When you will use vscode-languageclient outside of node how do you guys consume this. Will the dependency be ignored? I just want to make sure we do something and it will have ripples down to vscode-jsonrpc which we then need to ripple in the client again.

One additional thing I stumbled over. The Language Client heavily depends on VS Code API as well. How would the client be used outside an Node / Electron app. VS Code API fully requires Node / Electron.

@dbaeumer vscode-jsonrpc only pulls in types from node afaik, not values. This PR makes it significantly easier to use in a non-node environment and works for our needs (we have this branch working in the browser with VS Code without Electron/Node). Other use cases might require even more decoupling but we can address that when it comes

I am still a little puzzled here: the client always supported to pass in a function as a server to create the server process. In this case no child_process code was executed. Would there have been an easier solution then to make it work in your environment. Looks like you only want to avoid executing node code.

@dbaeumer It would not execute child_process code, but the child_process module was still imported and used (eg the value was imported and referenced in the code, not only the type).

@felixfbecker as mentioned that's what ends up happening. a bit confusing at first - i agree.
what i ended up doing is stubbing all the imports and their functions.
i wonder if there is a tool that would actually do this automatically, now that i come to think of it.
it seems mechincal: look all the import and find the browser based version, if not, stub all the functions of the module.
irc, one needs to be double-check, even if the import fails the script (in the browser) might still work. however, i guess its better to fix this...

@mbana Browserify will automatically give you browser shims for all kinds of Node modules like url, events, http, buffer - maybe even child_process with WebWorkers. But these shims are often huge, and it is much better to actually provide platform-independent modules

@felixfbecker but there is a lot of other code that imports node code and references it. In addition there is all the VS Code specific code that it executed (all the type conversion code). What if VS Code decides to reference child process in its code which I reference through the converters.
Don't get me wrong I am all in for making the library more useful in other contexts but I am not sure I understand the goal right now. Can you give me an example where the client/src/client.ts is used given all the VS Code and other node dependencies this file drags in.

@dbaeumer you can go to https://sourcegraph.com/github.com/Microsoft/vscode-languageserver-node/-/blob/client/src/main.ts right now and it is using this branch :)
If you open the dev tools and search for lsp in the network tab you will find a WebSocket connection that speaks LSP to a TypeScript language server on the backend.
The goal of this PR is not to remove the dependency on VS Code, it is just to make it easier to run it in a browser.
If VS Code decides to reference child_process somewhere we modify it to use WebWorkers instead :)

Hi @dbaeumer, what can we do to improve this PR? This patch is working well in production and makes it much easier to use the library in other contexts. Is @felixfbecker's example sufficient? Thanks!

We had endgame the last week and I needed to implement features for VS Code tasks. This is why the PR is on hold right now.
Here is what I think should be done since this is not really making the library platform independent:

have a client file with basically the code as proposed with an abstract LanguageClient
have a main file to not break anything

DO NOT include a browser.ts file since this gives the impression that the library actually supports running in the browser and we would need to fix things if this is broken.
The current PR has merge conflicts. If one of you can make the changes then I will merge them in. Otherwise I will have a look in the next 1 - 2 weeks.

@dbaeumer Thanks for the pointers. I just updated the PR.

Tried to merge but I already changed the code (again :-). So I went down the path of doing the change myself on master. It is basically what you guys suggested with some tweaks:

in client the class is called BaseLanguageClient and is abstract.
since we need subclasses anyways I made the creation of the reader/writer a method to implement instead of a function passed to the BaseLanguageClient.
main.js behaves as before.

I pushed the change to master. @sqs can you please have a look if this satisfies your needs. Please open separate issues if not


pull request for e2e test at 01/06/2017 16:45:08

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Create a Section SFC

🚀 Feature Request
Is your feature request related to a problem? Please describe.

Enhancement

Describe the solution you'd like

Outsource the  into a single file component. Filename: OptionSection.vue

Describe alternatives you've considered

Additional context

I can take this one!

assigned @taramatt93


Update setup scripts to disable console on ttyAMA0

See #400.
This updates two setup scripts (mkimg.sh and update_footer.sh) to look for and remove any console=ttyAMA0 references in /boot/cmdline.txt, resolving a serial connection issue that caused USB receivers to be unable to connect if installed after boot, and for intermittent disconnects of GPS receivers connected over serial GPIO.
This also removes an outdated reference to /etc/inittab in mkimg.sh.

Outstanding, AvSquirrel!  This allowed my serial GPS to connect almost immediately instead of the former 8 to 10 minutes.  Woohoo!


widthForPagingItem delegate method causes leak with new PagingViewControllerSizeDelegate

Hello.
I have just migrated the project to 2.0.1 and started to use the new delegate and noticed it causes leaks. When I dismiss the view controller that has PagingViewController, the view controller is removed from memory but the child view controllers that belong to PagingViewController are stayed in the memory.
I have just created and simple code showing what I did:
https://gist.github.com/rocxteady/3f562c2b2bd2262ff1c6f40a7bd11052
I took a screenshot that shows the memory graph.

See the child view controllers called PirtViewController which should have been released from the memory.
Thank you.

I have just sent a pull request which solves this issue: #433

This should be fixed now and will be included in the next release. Thanks again for the PR!


Introduce new config options in setup.cfg for PyScaffold and templates

We should set the following (copied over from setuptools github):

long_description_content_type='text/x-rst; charset=UTF-8',

   "Documentation": "https://setuptools.readthedocs.io/",

},```

and set the url to github and the documentation to our homepage. This way we should also see the nice Github statistics on PyPI as with setuptools.

I just activated these settings for configupdater and it works great. Check it out on PyPI. One important thing though, one must use twine to upload to PyPI for this to work!

Done in 499fcd1b41f7c2043f9026fb3d2251c2ceb4e16c. I guess these settings are not important enough to define them in the update procedure.


maskElement cannot be animated on Android

In MaskedElementIOS, maskElement can be nicely animated, however it doesn't seem to work on Android with this component.

This is the kind of example that would be supported if the maskElement can be animated on Android the same way to works on iOS: https://www.youtube.com/watch?v=gLopy2MCAqM. Source code: https://github.com/wcandillon/can-it-be-done-in-react-native/tree/master/season3/src/LiquidSwipe

I have same issue, any updates?

It tool me two days trying to figure out the issue with android and my conclusion is that the bitmap which drawn by native code is apply the mask perfectly, however it is not animatable

Has there been any progress on solving this?
I can't display an image inside the mask view with another image as the maskElement.
<MaskedView         maskElement={(           <Image             source={require('../assets/image_mask.png')}           />               )}       >         <image           source={image}         />       </MaskedView>
It does not render anything. If I set a backgroundcolor on maskelement it render the image (expected).
Reloading the code using fast reload render the image until the next reread of the view.
Unfortunately I know too little about android development to attempt solving this myself

I have another use case for an animated maskElement that doesn't work on Android, let me know if this is helpful to provide it.
Right now, the best workaround to this is to use ClipPath from RN SVG but this has serious limitations.

I'm in need of this functionality as well for Android

@wcandillon I think the recently merged pull request fixed the visualization issue in your tutorial. But the performance is not so good, I tried on Android devices and the FPS is so low.

#52 seems to have resolved this issue for me in a performant manor.

Limit the draw circle it's possible ? the current solution renders so much more than necessary

If anyone has a workaround for this 👍

As @JustinFemh mentioned this seems to be have been fixed. @heroic what did you think about the performance?

@wcandillon for my usage, the performance has been impeccable. You can see in the package I've built that the animations are fluid, even with a somewhat complex animation:
https://github.com/crutchcorn/react-native-button-toggle-group

Thks @crutchcorn !

@wcandillon if there were some performance issues we will work on it. Waiting for a new episode from you ;)

Hi @wcandillon, still not able to make your liquid-swipe example working with the latest react-native-masked-view version. Any suggestion?

@wcandillon none noticeable!

Damn this is really slow though it works!

hehe indeed, it's because on every frame, it takes a snapshot of the view and then applies the mask. It's all done on the CPU. I'm not sure what is the best practice on Android for such use case.

I don't get it. MaskedElement is still not animate-able on android using the latest version of this library on android. Is it just me or everyone else too?

I see that this PR tries to add the animation support back by giving us the opportunity to set the rendering mode to software manually. However, even when doing this, I can't run animations on the MaskElement on android

animatable element in maskedElement not working here.

Animated maskElement still doesn't work on Android here. Any updates or suggestions on a workaround?

Hardware Accelerated MaskView Animations in React Native Android
This is a workaround for the performance issues with MaskView animations on Android devices in React Native. While the MaskView animations work well on iOS, they pose some performance issues on Android.
The Issue:
When androidRenderingMode is set to software, the animations work but the performance is poor with barely 10 fps. However, with androidRenderingMode set to hardware, the animations work as long as the MaskView element is in motion at initialization. Once the element stops, it freezes and cannot be animated anymore. The performance, however, is far better with 45 - 60 fps.
The Workaround:
The workaround involves keeping the MaskView element always in motion. Trying this from the JavaScript code results in performance issues, with the framerate dropping to around 15-30 fps.
A more efficient solution is to modify the native code to keep the UI thread constantly moving the element. This results in a performance increase of up to 60 fps.
Here's the patch for the changes that you can use with patch-package:
@react-native-masked-view+masked-view+0.2.9.patch
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 4615d21..dfa80a8 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -7,6 +7,7 @@ import android.graphics.Paint;
 import android.graphics.PorterDuff;
 import android.graphics.PorterDuffXfermode;
 import android.view.View;
+import android.animation.ValueAnimator;

 import com.facebook.react.views.view.ReactViewGroup;

@@ -17,6 +18,7 @@ public class RNCMaskedView extends ReactViewGroup {
   private boolean mBitmapMaskInvalidated = false;
   private Paint mPaint;
   private PorterDuffXfermode mPorterDuffXferMode;
+  private ValueAnimator animator;

   public RNCMaskedView(Context context) {
     super(context);
@@ -26,6 +28,18 @@ public class RNCMaskedView extends ReactViewGroup {

     mPaint = new Paint(Paint.ANTI_ALIAS_FLAG);
     mPorterDuffXferMode = new PorterDuffXfermode(PorterDuff.Mode.DST_IN);
+
+    animator = ValueAnimator.ofFloat(0, 1);
+    animator.setDuration(60000); // Change duration as needed
+    animator.setRepeatCount(ValueAnimator.INFINITE);
+    animator.addUpdateListener(new ValueAnimator.AnimatorUpdateListener() {
+        @Override
+        public void onAnimationUpdate(ValueAnimator animation) {
+    // Force a refresh on each animation frame
+    invalidate();
+        }
+    });
+    animator.start();
   }

   @Override
@@ -112,4 +126,13 @@ public class RNCMaskedView extends ReactViewGroup {
       setLayerType(LAYER_TYPE_HARDWARE, null);
     }
   }
+
+  @Override
+    protected void onDetachedFromWindow() {
+        super.onDetachedFromWindow();
+        // Stop the animator when view is detached
+        if (animator != null) {
+            animator.end();
+        }
+    }
 }

This may not be the most elegant solution, but it works and hopefully can inspire a more efficient solution from a more experienced Android engineer.
Thanks to @wcandillon for the Liquid Swipe example that inspired this workaround.
And here's a video showing how the Liquid Swipe example looks on my Android 10 device with androidRenderingMode="hardware":
https://github.com/react-native-masked-view/masked-view/assets/7797467/d1cf2faa-4079-453a-9515-7d72511013bb

Hardware Accelerated MaskView Animations in React Native Android
This is a workaround for the performance issues with MaskView animations on Android devices in React Native. While the MaskView animations work well on iOS, they pose some performance issues on Android.
The Issue:
When androidRenderingMode is set to software, the animations work but the performance is poor with barely 10 fps. However, with androidRenderingMode set to hardware, the animations work as long as the MaskView element is in motion at initialization. Once the element stops, it freezes and cannot be animated anymore. The performance, however, is far better with 45 - 60 fps.
The Workaround:
The workaround involves keeping the MaskView element always in motion. Trying this from the JavaScript code results in performance issues, with the framerate dropping to around 15-30 fps.
A more efficient solution is to modify the native code to keep the UI thread constantly moving the element. This results in a performance increase of up to 60 fps.
Here's the patch for the changes that you can use with patch-package:
@react-native-masked-view+masked-view+0.2.9.patch
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 4615d21..dfa80a8 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -7,6 +7,7 @@ import android.graphics.Paint;
 import android.graphics.PorterDuff;
 import android.graphics.PorterDuffXfermode;
 import android.view.View;
+import android.animation.ValueAnimator;

 import com.facebook.react.views.view.ReactViewGroup;

@@ -17,6 +18,7 @@ public class RNCMaskedView extends ReactViewGroup {
   private boolean mBitmapMaskInvalidated = false;
   private Paint mPaint;
   private PorterDuffXfermode mPorterDuffXferMode;
+  private ValueAnimator animator;

   public RNCMaskedView(Context context) {
     super(context);
@@ -26,6 +28,18 @@ public class RNCMaskedView extends ReactViewGroup {

     mPaint = new Paint(Paint.ANTI_ALIAS_FLAG);
     mPorterDuffXferMode = new PorterDuffXfermode(PorterDuff.Mode.DST_IN);
+
+    animator = ValueAnimator.ofFloat(0, 1);
+    animator.setDuration(60000); // Change duration as needed
+    animator.setRepeatCount(ValueAnimator.INFINITE);
+    animator.addUpdateListener(new ValueAnimator.AnimatorUpdateListener() {
+        @Override
+        public void onAnimationUpdate(ValueAnimator animation) {
+    // Force a refresh on each animation frame
+    invalidate();
+        }
+    });
+    animator.start();
   }

   @Override
@@ -112,4 +126,13 @@ public class RNCMaskedView extends ReactViewGroup {
       setLayerType(LAYER_TYPE_HARDWARE, null);
     }
   }
+
+  @Override
+    protected void onDetachedFromWindow() {
+        super.onDetachedFromWindow();
+        // Stop the animator when view is detached
+        if (animator != null) {
+            animator.end();
+        }
+    }
 }

This may not be the most elegant solution, but it works and hopefully can inspire a more efficient solution from a more experienced Android engineer.
Thanks to @wcandillon for the Liquid Swipe example that inspired this workaround.
And here's a video showing how the Liquid Swipe example looks on my Android 10 device with androidRenderingMode="hardware":
2023_06_13_16_16_05_1_resized.mp4

This really works for me!
THANKS!!!!


Cant find stacking docs

I am looking for the docs for stacking at https://github.com/phonegap/phonegap-plugin-push#stacking
but I am not finding.  Could someone point me in the right direction!
Thanks,
Rodney

https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/PAYLOAD.md#stacking


Gem5 to Mcpat

Hi,
I have used the parser given by you, but it gives me the following error
Traceback (most recent call last):
File "Gem5ToMcPAT-Parser.py", line 301, in
main()
File "Gem5ToMcPAT-Parser.py", line 298, in main
dumpMcpatOut(args.output)
File "Gem5ToMcPAT-Parser.py", line 267, in dumpMcpatOut
param.attrib['value'] = str(eval(str(value)))
File "", line 1, in
TypeError: unsupported operand type(s) for /: 'float' and 'list'
Please can anyone help me to rectify it.
Thanks and best regards.

This error is mostly due to your template.xml file. The stats in your template.xml file do not match the stats in your stats.txt file from gem5. Print 'value' before line 267 and check the last parameter printed. This last parameter would be the statistic your parser is looking for in stats.txt


feat: DISA Kubernetes STIG compliance

Reason for Change:
Update cluster configuration to enforce the DISA Kubernetes STIG.
The following set of configuration changes will be applied by default moving forward:
API Server config changes:

STIG Rule SV-242438r879806_rule: --request-timeout set to "1m"
STIG Rule SV-242468r879889_rule: --tls-cipher-suites set to "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384"
STIG Rule SV-242468r879889_rule: --tls-min-version set to "VersionTLS12"
STIG Rule SV-254801r879719_rule: add feature gate "PodSecurity=true" (+v1.25)

Controller Manager config changes:

STIG Rule SV-242385r879530_rule: --bind-address set to "<IP_ADDRESS>"
STIG Rule SV-242376r879519_rule: --tls-min-version set to "VersionTLS12"
STIG Rule SV-254801r879719_rule: add feature gate "PodSecurity=true" (+v1.25)

Kubelet config changes:

STIG Rule SV-245541r879622_rule: --streaming-connection-idle-timeout set to "5m"
STIG Rule SV-254801r879719_rule: add feature gate "PodSecurity=true" (+v1.25)

Scheduler config changes:

STIG Rule SV-242384r879530_rule: --bind-address set to "<IP_ADDRESS>"
STIG Rule SV-242377r879519_rule: --tls-min-version set to "VersionTLS12"
STIG Rule SV-254801r879719_rule: add feature gate "PodSecurity=true" (+v1.25)

etcd config changes:

STIG Rule SV-242380r879519_rule: added --peer-auto-tls
STIG Rule SV-242379r879519_rule: added --auto-tls

The following changes will be enabled only if the new enforceKubernetesDisaStig feature flag is set:

Stop and disable sshd from all Linux nodes
Audit Policy captures everything

No changes are applied to Windows nodes.
Issue Fixed:

Credit Where Due:
Does this change contain code from or inspired by another project?

[ ] No
[ ] Yes

If "Yes," did you notify that project's maintainers and provide attribution?

[ ] No
[ ] Yes

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Notes:

/az run

/azp run

/azp run

/azp run

/azp run

/azp run


validation rule on a textarea

Hi,
may be this trouble was allready reported, sorry, i didn't take time to search.
I've past the last 4 hours to find why a rule defined on a textarea was not working at all. I've realized the rule was applied using the attribute name of this textarea and not his attribute id.
In all forms, i use both attributes id and name, but sometimes, i use array for the name, for example id="section_name" and name="section[name]". But if i add rules in the usual « $('#form')validate(rules) » using the id, this won't work.
I had to add a rule specificly after this part using $('#section_name').rules('add',{});
May be some improvment could be appreciated.
Thanks.

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.
To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!


Kinesis-sink consider topic-name as partition-key if record key empty

Motivation
#2116 refactored to pass record-key as partition-key to the configured sink. However, old pulsar-client (< 2.0) are not sending partitioned-key in the message which makes this key empty all the time. So, in that case, we should consider topic-name as partitioned-key to manage ordering for that partition.
Modifications
Consider topic-name as partitioned-key if record-key is not available.

actually this change is related bunch of other changes. so not going to merge it to branch-2.1


Blocks fail when tested as boolean

This fails :
if { mut x = 3; x } == 3:
    print <- "hello"

Fixed. Good catch!


build service job for eeitt microservice

@konradwudkowski  we should really start again with EEITT in lowercase as it even goes against naming guidelines: https://confluence.tools.tax.service.gov.uk/display/AR/Microservice+Naming+Guidelines

Agreed. Now the question if this will cause some sort of clash... But we can solve if it happens

@konradwudkowski EEITT repo has been renamed to eeitt, we are safe to merge this now


robot.errors.DataError: Reading XML source failed: ParseError: no element found

Traceback (most recent call last):
File "C:\Python27\lib\runpy.py", line 174, in _run_module_as_main
PabotLib process stopped
"main", fname, loader, pkg_name)
File "C:\Python27\lib\runpy.py", line 72, in _run_code
exec code in run_globals
File "C:\Python27\lib\site-packages\pabot\pabot.py", line 643, in
main(sys.argv[1:])
File "C:\Python27\lib\site-packages\pabot\pabot.py", line 630, in main
_get_suite_root_name(suite_names)))
File "C:\Python27\lib\site-packages\pabot\pabot.py", line 505, in _report_results
return _report_results_for_one_run(outs_dir, options, start_time_string, tests_root_name)
File "C:\Python27\lib\site-packages\pabot\pabot.py", line 509, in _report_results_for_one_run
output_path = _merge_one_run(outs_dir, options, tests_root_name)
File "C:\Python27\lib\site-packages\pabot\pabot.py", line 532, in _merge_one_run
merge(files, options, tests_root_name).save(output_path)
File "C:\Python27\lib\site-packages\pabot\result_merger.py", line 131, in merge
settings.non_critical_tags, tests_root_name)
File "C:\Python27\lib\site-packages\pabot\result_merger.py", line 118, in merge_groups
non_critical_tags).values():
File "C:\Python27\lib\site-packages\pabot\result_merger.py", line 109, in group_by_root
res = ExecutionResult(src)
File "C:\Python27\lib\site-packages\robot\result\resultbuilder.py", line 46, in ExecutionResult
return _single_result(sources[0], options)
File "C:\Python27\lib\site-packages\robot\result\resultbuilder.py", line 70, in _single_result
raise DataError("Reading XML source '%s' failed: %s" % (unic(ets), error))
robot.errors.DataError: Reading XML source 'E:\autotest\autotest2.0\output\20170216_120910_test_std_5GAPMode.ini_10__5GAPMode_11an\pabot_results\autotest.3 Wireless.4 5G APMode.6 1 11Na Connectivity.6 1 11Na Connectivity Open Long Wep Index2 A2C\output.xml' failed: ParseError: no element found: line 195320, column 47

Seems to happen when using Pabot. If you report the issue there, please provide more information about how you used the tool. Just giving a traceback isn't typically enough for others to understand what's going on. If you are certain the problem is in Robot, not Pabot, please provide more information about it here.


Versions for builders and internal package 📦

Changes

This adds versions for the builder: v1alpha1 and v1beta1.
This also migrate the builder to internal/builder while keeping an
alias on test/builder for user of this package (marking it as
deprecated).
Those are in the internal package so only this project can refer them (making it easier to remove later on as nobody from the outside will depend on them).
This is in preparation of #2410  as… well… builders are gonna be needed for v1beta1 (or… it will take ages to do :joy_cat: ).
This feels big but there is not much net new code:

It's moving files around (test/builder -> internal/builder/v1alpha1)
It's adding a whole new builder package (internal/builder/v1beta1) based on internal/builder/v1alpha1 but with the v1beta1 API

Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>/cc @afrittoli @dibyom @bobcatfish @ImJasonH
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

@vdemeester i think you tried to explain this to me in chat but I don't quite understand why we need 2 versions of the builders? esp. if we're going to be able to rely on having only 1 type to interact with in the tekton controller, which is my understanding of the finished state of updating the storage types.

builders are gonna be needed for v1beta1 (or… it will take ages to do 😹 ).

Or is the idea that the next step would be to delete the v1alpha1 builders?

I would like to take this opportunity to commit to a goal of phasing out test builders entirely, after these changes are in place. Phasing out test builders shouldn't block "real" work like updating the storage version, but since this will move them to internal packages, we should just commit to removing them, with a reasonable deadline.
If this seems reasonable I can write a real issue to track it, with justifications and timelines, and assign it to myself. If not, I'd like to convince you that it is reasonable and still do it. 😄

I would like to take this opportunity to commit to a goal of phasing out test builders entirely, after these changes are in place. Phasing out test builders shouldn't block "real" work like updating the storage version, but since this will move them to internal packages, we should just commit to removing them, with a reasonable deadline.
If this seems reasonable I can write a real issue to track it, with justifications and timelines, and assign it to myself. If not, I'd like to convince you that it is reasonable and still do it. 😄

I think test code will be more transparent without the builders. It may be non-obvious in some cases how to build an object, but a good reference example should be enough to cover that.

@vdemeester i think you tried to explain this to me in chat but I don't quite understand why we need 2 versions of the builders? esp. if we're going to be able to rely on having only 1 type to interact with in the tekton controller, which is my understanding of the finished state of updating the storage types.

builders are gonna be needed for v1beta1 (or… it will take ages to do joy_cat ).

Or is the idea that the next step would be to delete the v1alpha1 builders?

@bobcatfish There is multiple answer to the "2 versions". There is 2 versions of the APIs, if we do builder for the api it make sense to have 2 version of the builder — I mean, why not, especially if we use them in tests (we are testing v1alpha1 and v1beta1 in e2e for example). But, yes the idea is the "next" step (after #2410) will be to remove the v1alpha1  builders (and in general most likely all).

I would like to take this opportunity to commit to a goal of phasing out test builders entirely, after these changes are in place. Phasing out test builders shouldn't block "real" work like updating the storage version, but since this will move them to internal packages, we should just commit to removing them, with a reasonable deadline.
If this seems reasonable I can write a real issue to track it, with justifications and timelines, and assign it to myself. If not, I'd like to convince you that it is reasonable and still do it. smile

@ImJasonH Yes :+1: We may need alternative for verbose cases (a fromYaml methods or whatever), but in a gist I am fine with that.
The main goal here is:

make it so that people don't depend on it (hence the internal) — we need to put a deprecation notice on test/builder so that we can remove it in a few releases.
make it more easy to do #2410 – and more quick ; and also more easy to review.
Once #2410 is done, the v1alpha1 builder should be only used in a few places (most likely only in test/v1alpha1)
From there on we can phase out the builder

I think test code will be more transparent without the builders. It may be non-obvious in some cases how to build an object, but a good reference example should be enough to cover that.

So the goal is to have test readable and with the least "noise". That said, builders didn't really achieve what I had in mind initially… :sweat:

The linting should be fixed :crossed_fingers:

Hard to review the full thing but from what I understand it is just a migration between alpha to beta until we get rid of the builders
so that sounds good to me,
/lgtm

/kind misc

/test pull-tekton-pipeline-integration-tests