microK8S's dns does not work

Hello,
I've just a fresh install of microK8S following the official doc do not get the dns pods to start.
Following the troubleshooting section there I double checked my fw rules.
but a

microk8s.kubectl logs coredns-588fd544bf-dt8jz -n kube-system

0407 16:07:10.623229       1 reflector.go:125] pkg/mod/k8s.io/client-go@v0.0.0-20190620085101-78d2af792bab/tools/cache/reflector.go:98: Failed to list *v1.Service: Get https://<IP_ADDRESS>:443/api/v1/services?limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:443: i/o timeout
E0407 16:07:10.623229       1 reflector.go:125] pkg/mod/k8s.io/client-go@v0.0.0-20190620085101-78d2af792bab/tools/cache/reflector.go:98: Failed to list *v1.Service: Get https://<IP_ADDRESS>:443/api/v1/services?limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:443: i/o timeout
E0407 16:07:10.623229       1 reflector.go:125] pkg/mod/k8s.io/client-go@v0.0.0-20190620085101-78d2af792bab/tools/cache/reflector.go:98: Failed to list *v1.Service: Get https://<IP_ADDRESS>:443/api/v1/services?limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:443: i/o timeout

My ufw status looks like:
xxxxxx@master-node:~$ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
443/tcp                    ALLOW       Anywhere
Anywhere on cni0           ALLOW       Anywhere

Anywhere                   ALLOW OUT   Anywhere on cni0

So the dns pod does not have access to the cluster ip
xxxxx@pinfo3:~$ microk8s kubectl -n kube-system get services
NAME       TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE
kube-dns   ClusterIP   <IP_ADDRESS>   <none>        53/UDP,53/TCP,9153/TCP   2m32s

I tried the same with a busy box and it has also not access to the cluster-ip but it has access to the other pods.
Thanks a lot in advance
inspection-report-20200407_213505.tar.gz

Following #1034, I checked my proxy logs and I have the same issue:
7224   32034 server.go:621] starting metrics server failed: listen tcp <IP_ADDRESS>:10249: bind: address already in use

But the problem is that when microK8S runs I have
xxxx@master-node:~$  sudo lsof -i :10256
COMMAND     PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
kube-prox 32157 root    9u  IPv4 690097      0t0  TCP localhost:10256 (LISTEN)

But when I stop microk8s I do not have any more port running
xxxx@master-node:~$ sudo microk8s stop
Stopped.
xxxx@master-node:~$  sudo lsof -i :10256
xxxx@master-node:~$

Hi @hostettler there is something not right with the network setup in this system. The 10.152.183.X network is where kubernetes gets its cluster ips from. It seems that traffic is dropped to this network. It is not only DNS that is affected by this. This needs a bit of research on your side. One thing I would check first is the default input policy that is set to DROP. Could you try to change that to ACCEPT or at least ACCEPT the traffic to/from the 10.152.183.X network?

Thanks a lot for looking into it. So I did
sudo ufw allow to <IP_ADDRESS>/24
sudo ufw allow from <IP_ADDRESS>/24

But it does not solve the problem

So I temperately set the default policy to accept and it does solve the problem but obviously I do not want to have to set that policy to accept.

The second network you want to allow traffic to/from is <IP_ADDRESS>. This network if where pods are.

So adding
 sudo iptables -A INPUT-p tcp -s <IP_ADDRESS>/24 -j ACCEPT
 sudo iptables -A OUTPUT -p tcp -d <IP_ADDRESS>/24 -j ACCEPT

Does not solve the problem

I made some progress. So the problem is apparently that the traffic from cni0 get dropped despite the fact that microk8s seems to put the right rules in place.
I did the following
sudo iptables -P INPUT ACCEPT
sudo iptables -L LOGGING
sudo iptables -A LOGGING -m limit --limit 10/min -j LOG --log-prefix "IPTables-Dropped: " --log-level 6
sudo iptables -A LOGGING -j DROP

to capture the dropped packets and simulate the drop policy as it sweep the rest of the traffic and I can reproduce the problem. Now if I add accept to all cni0 traffic before logging/dropping
sudo iptables -P INPUT ACCEPT
sudo iptables -D  LOGGING -m limit --limit 10/min -j LOG --log-prefix "IPTables-Dropped: " --log-level 6
sudo iptables -D  LOGGING -j DROP
sudo iptables -A LOGGING -i cni0
sudo iptables -A LOGGING -m limit --limit 10/min -j LOG --log-prefix "IPTables-Dropped: " --log-level 6
sudo iptables -A LOGGING -j DROP

Then it works.


Small Incremental changes with PDD

Bug Description
A clear and concise description of what the bug is and how to reproduce it.
Screenshots
If applicable, add screenshots to help explain your problem.


Only Console version

Hi, I want to start the app in a Ubuntu Server. (No gui)
I start with:
qlcplus --nowm --nogui --web
but I get:
qlcplus: cannot connect to X server

Hey, have a look at this thread
Please search the forum and post your questions there in the future.

Yes, thanks. I solved with xvfb :)


Web - Search - Group expense box is not highlighted evenly when selected by keyboard

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.56-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:

Go to staging.new.expensify.com
Submit two expenses to any user
Go to Search
Go to Outstanding
Navigate to the group expenses in Step 2 using keyboard
Click on the empty area to remove the blue border

Expected Result:
The group expense box will be highlighted evenly
Actual Result:
The top and bottom of the group expense box have different shade than the middle of the box
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/b1075f94-6178-4c98-8e77-2f6d226a75ca
View all open jobs on GitHub

@nkdengineer Can you take a look?

I don't think this is a blocker, but it seems the change created a bunch of other issues and is being reverted already.

Reverted in https://github.com/Expensify/App/pull/51795 & that was checked off by applause, so seems to be fixed!

Fix was submitted in https://github.com/Expensify/App/pull/51937

The PR above was deployed


Update npu doc

Mainly changes in this PR:

update npu doc
update requirements.txt
add Contribution description in README.md

@codemayq cc

LGTM


Update npm module

The version of this SDK on npm is out of date.  It does not reflect the changes made in most recent commit (e945f250f1d4b416fd5ff0793196f64cbb22c111) .

@Jalepeno112 thanks for pointing this out! Npm now has the latest version available.
Cheers!


is there any way to resize image ?

Please see issues #35 and #88.

Thanks.. cracked it ..

I solved it this way.
 $.when(readFileIntoDataUrl(fileInfo)).done(function (dataUrl) {
	 var randomID = "I_"+ Math.floor(Math.random() * 20);
	 var imgHTMLstr ='';
          // replaced the original code with insertHTML so we could get an ID on this image
	 execCommand('insertHTML', imgHTMLstr);
		//now that we have the ID we can invoke  jquery  resizeable api
              $(function () {
		            $("#"+randomID).resizable();
		 });
	//just replace the code below with the code above.
      //execCommand('insertimage', dataUrl);//original code

@icandothat2 Elegant. Does this actually resize the image though, or simply modify the way it is displayed? IE: If I am sending the editor content to a server via POST for storage, the image will be stored as its original size, correct?

Thank you,
You are Correct. It does not "resize" the image in the sense that the image
data is not changed, it just looks smaller on screen. To actually resize
the image would take a canvas element. I actually may still put it into a
canvas to enable on screen drawing etc. but for now resizing was a good
first step.
On Wed, May 30, 2018 at 2:45 PM, kaptainkommie<EMAIL_ADDRESS>wrote:

@icandothat2 https://github.com/icandothat2 Elegant. Does this actually
resize the image though, or simply modify the way it is displayed? IE: If I
am sending the editor content to a server via POST for storage, the image
will be stored as its original size, correct?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/steveathon/bootstrap-wysiwyg/issues/124#issuecomment-393329928,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APcqjCrqS53aDtfE6a93EJiXDkBiIhBLks5t3xLngaJpZM4NUNnZ
.

Thanks, I had implemented resizing using canvas for my use case, but I was curious if this worked similarly.


chore: fix incorrect merge conflict resolution

Motivation
https://github.com/ChainSafe/lodestar/pull/5463 merge conflict was incorrectly resolved
See https://discord.com/channels/593655374469660673/1092670111237799978/1104056821146198096

:tada: This PR is included in v1.9.0 :tada:


Add git package

Issue: N/A
Description of changes:

Add git package
Add RepositoryService interface to pkg/github

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Note to reviewers: the reason behind adding the RespositoryService, Opener, Cloner, OpenCloner is to make testing easier - without having to make real Gihub API requets or calling "git clone". ALso the next PR will introduce pkg/repository with basic unit tests.


Documentation is very sparse

Can you add in documentation that we can have signature value using sig.signatureValue after loading signature? Is this intended to be exposed, can I use this in my project?

You can use any of the public API in your project. If you find the documentation lacking, please consider contributing to the Wiki to improve it.


[Snyk] Upgrade metavm from 1.2.6 to 1.4.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade metavm from 1.2.6 to 1.4.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 3 versions ahead of your current version.
The recommended version was released 4 months ago, on 2023-12-10.

Release notes

Package name: metavm

1.4.1 - 2023-12-10Version 1.4.1
PR-URL: #120

1.4.0 - 2023-10-25Version 1.4.0
PR-URL: #118

1.3.0 - 2023-10-08Version 1.3.0
PR-URL: #113

1.2.6 - 2023-07-31Version 1.2.6
PR-URL: #110

    from metavm GitHub release notes

Commit messages

Package name: metavm

02db246 Version 1.4.1
de64893 Update dependencies
641f466 Add "es2020" to eslint configuration
bbeb204 Update Guthub actions CI config
fc359ca Fix package file format
b395b70 Version 1.4.0
7b0236d Support node.js 21.x
f2e0a2a Add stub for ESM
c530668 Add fetch to default global
02efc2d Improve tests: get error line and position
30d533a Move to native node.js test runner
374cec1 Version 1.3.0
682b291 Support new globals for node.js 18 and 20
c1a70b4 Drop node.js 16 and 19
a321ba1 Update dependencies
2c4eff4 Convert lockfileVersion 2 to 3

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Close in favour of https://github.com/metarhia/metasql/pull/290


rabbitmq-server: 3.9.1 -> 3.9.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/rabbitmq/rabbitmq-server/releases.
meta.description for rabbitmq-server is: "An implementation of the AMQP messaging protocol"
meta.homepage for rabbitmq-server is: "https://www.rabbitmq.com/"
meta.changelog for rabbitmq-server is: ""
Updates performed

Version 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

/nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3/bin/rabbitmq-defaults passed the binary check.

/nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3/bin/rabbitmq-diagnostics passed the binary check.

/nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3/bin/rabbitmq-env passed the binary check.

Warning: no invocation of /nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3/bin/rabbitmq-plugins had a zero exit code or showed the expected version

Warning: no invocation of /nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3/bin/rabbitmq-queues had a zero exit code or showed the expected version

/nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3/bin/rabbitmq-server passed the binary check.

/nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3/bin/rabbitmq-streams passed the binary check.

/nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3/bin/rabbitmq-upgrade passed the binary check.

/nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3/bin/rabbitmqctl passed the binary check.

6 of 9 passed binary check by having a zero exit code.

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

found 3.9.3 with grep in /nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3

found 3.9.3 in filename of file in /nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3

directory tree listing: https://gist.github.com/1f1a6b0bfd886d59f88b116df1f03d7a

du listing: https://gist.github.com/ad50e306af61e97fc037b785fc2f8c11

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
rabbitmq-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The 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 rabbitmq-server https://github.com/r-ryantm/nixpkgs/archive/6ca6cc20447e2094bd8e5427e28eb3ccbf418d2c.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/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3
ls -la /nix/store/pldyvwf1lzi1ga2nf1gss0mhx9ihp93j-rabbitmq-server-3.9.3/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 run on x86_64-linux 1

1 package built:

rabbitmq-server

Maintainer pings

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/rabbitmq-needs-a-new-maintainer/14545/6


Question to use number_entity for park and start

Hello,
I have a question regarding the new usage of the number_entity for park and start. Could you give an example how to use this or update the usage section?
I use the current service for manually start the mower:
service: husqvarna_automower.park_and_start
data:
command: Start
duration: 60
target:
entity_id: vacuum.husky
Thank you!

Command would look like that:
service: number.set_value
data:
  value: '60'
target:
  entity_id: number.husky_mow_for

Thank you very much!

This is excellent.
If used as number.husky_park_for, does the mower then resume schedule?
If not, how can resume schedule be called?


Page content not shown

Environment
Host

item
version

OS
CentOS 7.6

GROWI
3.5.0-RC (7b5d741)

node.js
10.16.0

npm
6.9.0

Using Docker
yes (Kubernetes)

Using growi-docker-compose
no

Client

item
version

OS
macOS 10.14.5

browser
Chrome 74.0.3729.169

How to reproduce? (再現手順)

npm run server:prod
Login to GROWI

What happens? (症状)

Page content was not loaded.
Not able to switch to edit tab.

JS Console:

What is the expected result? (期待される動作)

Page content is displayed.

@shield-9 Thank you for your report. I have confirmed it was reproduced. I'll fix it soon.


Missing dependencies

I am trying to compile this project. It seems the following two dependencies cannot be downloaded. Could you please re-upload these files? Thanks!
        "eigen"      : "eigen:eigen:${eigen}@zip",
        "opencl"     : "csarron:OpenCLHeaders:${opencl}@zip",

I couldn't find the dependency files, but you may find https://gitlab.com/libeigen/eigen/-/archive/3.3.3/eigen-3.3.3.zip and https://github.com/KhronosGroup/OpenCL-Headers useful. Sorry about the inconvenience.

Thanks for the reply. I am able to compile and run the code.
I find, in your renderscript, you actually didn't use the RS_KERNEL scripts. I modified your .rs file and used rsForEach function to run the RS_KERNEL scripts, but it is significant slower than what you have implemented. I think you have already tried similar method, but do you know why using RS_KERNEL is much slower?


Successible should be Serializable

Most of our type classes are Serializable, including Predecessible. Same should apply to Successible.

closed by: https://github.com/twitter/algebird/commit/3b78165ca3f0a6cb6ba3de6467f4fe1fce5c4b75
which I accidentally pushed to master. It is so trivial, I don't want to bother with the revert unless someone is really concerned.


validator: missing kafka output

Missing kafka output from schema https://docs.fluentbit.io/manual/pipeline/outputs/kafka

See https://github.com/calyptia/core-fluent-bit/pull/17. Be good to resolve but probably in upstream - we would not be enabling experimental inputs for LTS.

We don't need the input support... sorry about that.
@nicolasparada are we using this file for the schema? It seems the kafka output stuff is right there.
https://github.com/calyptia/core-images-index/blob/main/schemas/23.1.2/core-fluent-bit-pretty.json#L5914

Great, then we just need to update this repo and use the schema from the index then 👍


need help using maestro in windows. ERROR: The input line is too long. The syntax of the command is incorrect

I have been trying to setup maestro in windows but there are some issues which i am facing while executing ".\maestro test flow.yaml" command.
The error is as follows:
The input line is too long.
The syntax of the command is incorrect.
kindly anyone help me with the same.

Same here. None of the command options work.
Always the same error:

The input line is too long.
The syntax of the command is incorrect.

I moved maestro to c:\maestro and it worked
it tries to set an env variable set CLASSPATH= which is just way too long

i tried that still same error is occuring.

Reopening as I believe we should investigate if we can fix this in Meastro itself

We recommend using WSL to avoid having issues like that one (and generally have a better developer experience with a lot of other tooling on the market). The instructions can be found here: https://maestro.mobile.dev/getting-started/installing-maestro/windows


RFP - tachidesk

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://github.com/Suwayomi/TachideskJUI
Direct download URL for the software / installer : https://github.com/Suwayomi/TachideskJUI/releases/download/v1.1.1/TachideskJUI-windows-x64-1.1.1.msi
Software summary / short description: Comic online UX client

I pick up this package :slightly_smiling_face:
I actually already have created a Chocolatey package which is currently waiting for the review of Moderators :wink:

This package has been reviewed and approved by @TheCakeIsNaOH :slightly_smiling_face:


no-unbound-method: Fix description typo

PR checklist

[ ] Addresses an existing issue: #0000
[ ] New feature, bugfix, or enhancement

[ ] Includes tests

[ ] Documentation update

Overview of change:
Fixes typo in description of no-unbound-method rule. Extra word "as".
Is there anything you'd like reviewers to focus on?
No.
CHANGELOG.md entry:

Thanks for your interest in palantir/tslint, @sehrope! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.


[Feature Request] Default to suggesting threaded activities (and other async helper docs)

Describe the solution you'd like

Let people know that if they block an async def call in Python it stops all async code
Document set_debug(True) which also warns about tasks taking longer than 0.1 seconds
Encourage more use of threaded activities unless the user is sure their calls are non-thread-blocking

Encourage more use of threaded activities unless the user is sure their calls are non-thread-blocking

To add to this, we're going to change the quickstart and maybe samples to use threaded activities


Added Gate extension and can function to README.md

Added missing info about TwigBridge\Extension\Laravel\Gate extension in README.md, also added can function to the function list.

Coverage increased (+0.8%) to 55.252% when pulling 8844bd8e407c82ad34ecca3d812f3a8dc31d78c3 on silverqx:silverqx-patch-readmemd-update into fd856b37d605ff215450dca347523eb3a332f6f0 on rcrowe:master.


Azure AD plugin for client auth adding spn: prefix to apiserver-id indefinelty when unauthorized

I'm using kubectl Windows version v1.18.0 with the Azure AD plugin for client authentication.
The first time it works fine.
After 1 or 2 hours or inactivity, it fails. Remark the spn:spn:spn:spn string.
E0611 15:21:07.898016   28816 azure.go:154] Failed to acquire a token: refreshing the expired token: refreshing token: adal: Refresh request failed. Status Code = '400'. Response body: {"error":"invalid_resource","error_description":"AADSTS500011: The resource principal named spn:spn:spn:spn:spn:spn:spn:35XXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX was not found in the tenant named XXXX. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant.\r\n .... "error_uri":"https://login.microsoftonline.com/error?code=500011"}

Following google recommendations, i deleted access-token and refresh-token in the kube's config file. I also removed all the spn: prefixes that were present on the apiserver-id line.
apiserver-id: spn:spn:spn:spn:spn:spn:spn:35XXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX

to
apiserver-id: 35XXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX

After succesfully relogin to azure, the connection to the cluster still fails. But this is not the problem here. Each time the following command is issued and fails, the kube's config file is modified:
PS C:\> kubectl get pods
error: You must be logged in to the server (Unauthorized)

modified kube's config file:
apiserver-id: spn:35XXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX

After a second fail:
apiserver-id: spn:spn:35XXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX

etc...
So i suppose this is the issue everyone is reporting since 2 years. Each time the command fails, it adds the spn: prefix to the apiserver-id.
Note that config-mode is set to 0. Setting it to 1 (or removing the line) triggers the issue.
Client version info:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"windows/amd64"}

This was fixed in 1.18.1 in https://github.com/kubernetes/kubernetes/pull/89783


[MB-2615] domestic crating uncrating pricers

Description
I added pricers for Domestic Crating (DCRT) and Domestic Uncrating (DUCRT).
I also updated the Acceptance Testing Payment Requests wiki page with details about the new service items.
Reviewer Notes
Is there anything you would like reviewers to give additional scrutiny?
Setup
make db_dev_e2e_populate

Go to the TIO view and look for the move with the locator PARAMS.
This move should have crating and uncrating service items. If you go through the "review service items" flow you should see the service items for crating and uncrating and the calculation details.
Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
this article explains more about the approach used.

Screenshots
If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

Messages

:book:
:link: MB-2615

  Generated by :no_entry_sign: dangerJS against ee7edf471a02b7329b40a092253e5d2cd02caf9b


Activate SNI

Might be a good idea to add the activation of SNI to the manual.
http://directadmin.com/features.php?id=1100
Caused me some time to figure that out.

Development of this plugin is suspended because of native Let's Encrypt support in DirectAdmin since version 1.49.2.

If this features isn't being released or very limited, we'll continue development.


[BUG]

Prerequisites

[X] I have read the documentation.
[X] I have checked other issues for similar problems.

UI Screenshots & Parameters

Error Logs
Well, this might not be direct issue with auto-train seeing the above error on HF and TypeError: BFloat16 is not supported on MPS on M1 even after a model.to("cpu")
Additional Information
No response

its not an autotrain issue. you can try the code in readme and use it locally or deploy using inferencce endpoints. you can send this issue to<EMAIL_ADDRESS>as it looks like problem with api inference.

Thank you @abhishekkrthakur but TypeError: BFloat16 is not supported on MPS can be fixed via autotrain flags?
https://huggingface.co/gnumanth/phi3guanaco is the model I have published using the scripts suggested here

could you please add full logs of error? and code to reproduce it? :)

Indeed!

from transformers import AutoModelForCausalLM, AutoTokenizer

model_path = "gnumanth/phi3guanaco"

tokenizer = AutoTokenizer.from_pretrained(model_path)
model = AutoModelForCausalLM.from_pretrained(
    model_path,
    device_map="auto",
    torch_dtype='auto'
).eval()

model.to("cpu")

# Prompt content: "hi"
messages = [
    {"role": "user", "content": "hi"}
]

input_ids = tokenizer.apply_chat_template(conversation=messages, tokenize=True, add_generation_prompt=True, return_tensors='pt')
output_ids = model.generate(input_ids.to('cuda'))
response = tokenizer.decode(output_ids[0][input_ids.shape[1]:], skip_special_tokens=True)

# Model response: "Hello! How can I assist you today?"
print(response)

Stack trace:
Traceback (most recent call last):
  File "/private/tmp/k.py", line 7, in <module>
    model = AutoModelForCausalLM.from_pretrained(
  File "/Users/hemanth/.pyenv/versions/3.10.12/lib/python3.10/site-packages/transformers/models/auto/auto_factory.py", line 556, in from_pretrained
    return model_class.from_pretrained(
  File "/Users/hemanth/.pyenv/versions/3.10.12/lib/python3.10/site-packages/transformers/modeling_utils.py", line 3502, in from_pretrained
    ) = cls._load_pretrained_model(
  File "/Users/hemanth/.pyenv/versions/3.10.12/lib/python3.10/site-packages/transformers/modeling_utils.py", line 3926, in _load_pretrained_model
    new_error_msgs, offload_index, state_dict_index = _load_state_dict_into_meta_model(
  File "/Users/hemanth/.pyenv/versions/3.10.12/lib/python3.10/site-packages/transformers/modeling_utils.py", line 805, in _load_state_dict_into_meta_model
    set_module_tensor_to_device(model, param_name, param_device, **set_module_kwargs)
  File "/Users/hemanth/.pyenv/versions/3.10.12/lib/python3.10/site-packages/accelerate/utils/modeling.py", line 384, in set_module_tensor_to_device
    new_value = value.to(device)
TypeError: BFloat16 is not supported on MPS

torch dtype = torch.float16 should work no? ill give it a try myself.

@abhishekkrthakur I thought so to, maybe I am missing something obvious?

@abhishekkrthakur any luck on your end?


fix: RND-101: Fix ML backend compatibility with sdk>=1

https://github.com/HumanSignal/label-studio-ml-backend/issues/566

https://github.com/HumanSignal/label-studio-ml-backend/pull/557


C++ build doesn't include pthread?

For instance every time I try to submit stage 3 for Redis for C++, I keep getting "undefined reference to pthread_create". I have the header files and all of the dependencies installed, so I am just confused why this keeps happening when I try to push to origin master. Is there something completely obvious I am missing?

Thanks for @SamirOsAbdalla for reporting!

Applying this change to CMakeLists.txt seems to fix the issue:

Let's figure out why this builds locally but not on our build machines - maybe different C++ distributions include different libs by default?

This is now fixed with the move to vcpkg!


Resume Position Not Working

Describe the bug
Newest version (<IP_ADDRESS>) fixes the hangs / crashes described in my previous issue. However, I'm having some difficulty with resuming videos from both "Continue" and the episode listings themselves. The information is being stored in the Bookmarks correctly, and in some but not all cases, correctly displayed within the episode listing, however attempting to resume a video does not actually go to the resume point, it starts at the beginning.
No errors are being logged and debug logging is on. Will try and dig in later and see if I can find at what point it's going wrong or not being passed so I can maybe provide you some more information. There's also a slight inconsistency with Continue, occasionally after the 'first' item is added, a channel restart is needed for subsequent items to be visible. This is not a major issue I guess.
Is this an issue you've observed in the latest version?
To Reproduce
Steps to reproduce the behavior:

Play content
If content resume position was saved, try to resume the content
Content will play from the beginning.

Expected behavior
Content should resume where saved.
Manifest if that helps.
title=XXX
major_version=40
minor_version=1
build_version=1
FEED_URL=XXX
splash_color=#000000
BACKGROUND_COLOR=#000000
ui_resolutions=hd
USE_RAF=0
OFFER_SUBSCRIPTIONS=0
ENABLE_ROKU_VOICE=0
FAST_FORWARD=0
REWIND_BACK=0
supports_voice_roinput=0
supports_etc_next=0
supports_etc_seek=0
supports_input_launch=1
mm_icon_focus_hd=pkg:/images/channel.jpg
splash_screen_hd=pkg:/images/splash_HD.jpg
splash_screen_fhd=pkg:/images/splash_FHD.jpg

USE_THUMBNAIL_BACKGROUND=false
HIDE_GRID_THUMBNAIL=false
OVERHANG_CLOCK=false
OVERHANG_OPTIONS=false
CONTINUE_WATCHING=true
WATCHED_INDICATOR=true
CONTENT_VOTING=false
ALLOW_CHANNEL_SEARCH=false
SHOW_DETAILS_THUMBNAIL=false
DEBUG_PRINT=1 ```

Can you provide the steps needed to recreate your issue?

Can you provide the steps needed to recreate your issue?

It's in the first post
1.Play content
2.If content resume position was saved, try to resume the content
3.Content will play from the beginning.

Is the Debug zip on here any different than the <IP_ADDRESS> release?

No

Is the issue related to episodes only?

Is the issue related to episodes only?
Seems to not affect "movie" types in the same manner, having said that on one attempt, the movie didn't get added to the "continue row"  nor had any "resume progress" visible. On exiting the channel fully, coming back and playing the same movie (which began from the beginning) navigating a while in, and then going 'back' , the resume progress was saved and clicking resume did indeed resume at the correct position. In the "continue row" clicking that same movie which had resume progress, did also resume from the correct position. The episodes still do not.

To sum up
Sometimes no progress is saved, or at least visible within the channel. Yes I am skipping in a while and letting it play.
Items which are 'episodes' that eventually show up in Continue, do not play from the stored position, and similarly, those items when played from the episode grid, do not resume, they start from the beginning.
Printing the contents of the bookmarks on startup shows correct content ids and saved positions.
>>> DEBUG: key is xyz123
>>>> DEBUG: value is {"creationDate":"1732138983","position":"4.619"}
>>> DEBUG: key is def123
>>>> DEBUG: value is {"creationDate":"1732144234","position":"1.034"}
>>> DEBUG: key is abc123
>>>> DEBUG: value is {"creationDate":"1732138855","position":"126.159"}`

This appears to be a regression bug.

I have a fix for the non-Episodes.  Please try this and let me know if it resolves this part of the issue.  If it does, I'll roll it into a quick update.
In VideoPlayer.brs, in the ShowVideoScreen() function, please replace:
m.videoPlayer.addFields( { "playbackId" : playbackId } )
with:
if m.videoPlayer.hasField("playbackId")
     m.videoPlayer.setFields( { "playbackId": playbackId } )
else
     m.videoPlayer.addFields( { "playbackId" : playbackId } )
end if

I'm still working on the Episodes part of this issue.

Will try this in an hour or so and let you know.
Thanks again :)

Yeah the change works. Of note, I only have 1 movie item in the channel feed (I can add some dummy items if needed) but the behavior (saving, displaying, and resuming) playback position on movie items appears to be consistent.

Fixed in version <IP_ADDRESS>

Seems to work, sorry for the late reply :)
I'll test it more on a larger feed to verify.
Thanks again.


Incorrect link for Deploy via ansible

This is a Bug Report
Problem: The link for deploy via ansible under Network modes in Networking on windows is incorrect. It is redirecting to https://github.com/ovn-org/ovn-kubernetes/tree/master/contrib instead of that it should redirect to https://github.com/ansible/ansible.
Proposed Solution: Deploy via ansible should redirect to https://github.com/ansible/ansible instead of https://github.com/ovn-org/ovn-kubernetes/tree/master/contrib.

Page related to the issue: https://kubernetes.io/docs/concepts/services-networking/windows-networking/

/language en
/sig docs

I would to link to work on this issue, if triage gets accepted.

Really, the whole page could use an overhaul, and the mention of Ansible might actually disappear.

/sig windows

Since, the issue is already addressed in the PR so, i am closing this issue.


AvionDB Logo

I've added AvionDB to my encyclopedia of databases:
https://dbdb.io/db/aviondb
Do you have a SVG logo for this system? Thanks.
-- Andy

SVG available here
Also country of origin is India and United States.

Hi @apavlo
We have updated the logo for AvionDB. Here are some samples. Feel free to update the logo on dbdb.io.
Thanks :)

Do you have a SVG file of this?

@apavlo yup. Here you go! aviondb.svg

I need the first one with the words "AvionDB" in it.

@vaultec81 can you help us out here?

@apavlo Sorry for the delay. The full size SVG logo is available here


Low-Medium and Medium-High fan speeds not supported

My indoor unit supports the Low-Medium and Medium-High fan speeds (via the physical remote), but not via esphome-lg-controller. Surprisingly, changing to these fan modes is also not supported in the LG ThinQ Android app, although the "SmartThinQ LGE Sensors" Home Assistant integration does support them. (I think my indoor unit may also support fan mode 7 "power", although I'm not certain.)
(I see that lg-controller.h already has some support for these fan modes. I also see that the Climate component of ESPHome supports custom fan modes, which I assume are the relevant thing to use to implement this. I haven't dug through all the code to ensure that everything works the way I think it does, though.)

The protocol does have support for Low-Medium and Medium-High fan modes, but my units don't recognize these values if I send them manually. You could try this with your indoor unit (see protocol.md) but I expect it won't work, if your unit is similar to mine.
When using these fan modes with the wireless remote or ThinQ, the wired controller will just receive Medium, IIRC. At least the AC unit is smart enough to not reset it to the actual Medium fan mode later if the controller doesn't change it.
It's really unfortunate that the Wifi controller and wired controller have a different set of features.

Some devices support customizable fan speeds through Installer Setting 3.
I played around with that a little and it was really nice, however the setting is persisting power cycles.
So every change will likely wear the controller's EEPROM / Flash.
Anyway, if Installer Setting 3 is supported, you might find a speed configuration that satisfies your needs even with just 3 fan speeds available.

I finally got around to testing this, and can confirm what you said. It appears that when I set the fan speed to 5 or 6, the change is ignored. In addition, it looks like the capabilities message also does not report supporting low-medium or medium-high.
I noticed that the capabilities message does report that my unit supports fan speed 7. While performing this testing, I had my unit on fan only mode, but when I set the fan speed to power, the unit automatically set itself to cooling mode and 64 F, so it appears that power is not a normal fan speed, so we probably wouldn't want it as one. (I've seen power mode in heat mode before using either the physical remote or the LG app, but similarly, I don't think it would be desirable as a normal fan option.)

I noticed that the capabilities message does report that my unit supports fan speed 7. While performing this testing, I had my unit on fan only mode, but when I set the fan speed to power, the unit automatically set itself to cooling mode and 64 F, so it appears that power is not a normal fan speed, so we probably wouldn't want it as one. (I've seen power mode in heat mode before using either the physical remote or the LG app, but similarly, I don't think it would be desirable as a normal fan option.)

That's good to know, I haven't tried this option yet. On the PREMTB100, 'Power Cooling' and 'Power Heating' are separate operation modes with fixed setpoint associated with it (30C / 86F for heating).
The ThinQ app has a Jet Mode switch. That would probably be the easiest way to implement this.

I did some testing and my units only support the Power Fan option in Cooling mode. I can turn on the Jet option in the ThinQ app in heating mode, but the unit just resets it after a few seconds and also sends 'medium' to the wired controller. It looks like having a wired controller connected prevents my units from using this in heating mode.
Maybe I'll get back to this in the summer. I also want to add a toggle for the 'auto dry' / 'auto clean' option but that's also easier to test when the units are in cooling mode.

It looks like having a wired controller connected prevents my units from using this in heating mode.

Hi, thanks for all the work. I just started using this project and noticed that with the wired controller connected I can't set the Jet mode (at least while heating) on my AC (LG Standard plus, PC12SK). I would understand if it is not implemented in the code but how is it possible that I can't set this even with IR remote or LG ThinQ app? AC completely ignores the button press on IR remote or ThinQ app...
Do you think this can be fixed somehow? I used the Jet mode quite frequently as the high fan speed nicely mixes air around the whole room when nobody is home (so the noise is not an issue)
Thanks!


add navigation to index.html

Add navigation to index.html

think this was already fixed in another pull request but good job and thanks anyway ;)


Feature/dac node register

Description

Types of Changes

[ ] Tech Debt (Code improvements)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Dependency upgrade (A change in substrate or any 3rd party crate version)

Migrations and Hooks

[ ] This change requires a runtime migration.
[ ] Modifies on_initialize
[ ] Modifies on_finalize

Checklist

[ ] Change has been tested locally.
[ ] Change adds / updates tests.
[X] Changelog doc updated.

https://github.com/Cerebellum-Network/blockchain-node/pull/341


Update provider-tls.md

adding the required validator and delegate-limit flags to the Stake the Provider on Chain section

@KokosP  :) Thanks !!


⚠ Mobitopup has degraded performance

In 24cc1da, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 14663 ms

Resolved: Mobitopup performance has improved in 737363c.


feat: Extends the ProgressBar to potentially be also used as a meter.

The ProgressBar can now have a minimum and maximum value - not necessarily starting at 0. The value can be set to a value between the minimum and maximum value. The progress bar will then be filled up to the percentage of the value between the minimum and maximum value.
Before submitting the PR:

[ ] Does your PR reference an issue? If not, please chat to the team on Discord or GitHub before submission.
[ X] Did you update and run tests before submission using npm run test?
[ X ] Does your branch follow our naming convention? If not, please amend the branch name using branch -m new-branch-name
[ X ] Did you update documentation related to your new feature or changes? <<< Happened automatically 🤯

What does your PR address?
This extends the progress bar with a new property min so that it does not have to start at 0 necessarily.

This is a nice quality of life improvement @delight. Great job!


use data source for obtaining thumbprint

Instead of using variable for setting the certificate thumbprint, we can use data source to obtain the same.

Hey @skesarkar-schubergphilis – thanks for this! I didn't know about that data source! This has been released in v1.1.0.


*..dll has no meta file, but it's in an immutable folder. The asset will be ignored.

XRTK - Mixed Reality Toolkit Bug Report
Describe the bug
When installing the Lumin package (rather than submoduling) Unity will not load the dll's copied in from the SDK, as they do not have accompanying *.meta files.
To Reproduce
Add Lumin via package manager
Make sure the dll shim copy happens (ie, that https://github.com/XRTK/Lumin/blob/dbd3a908bf250af59b7d4d275457ccc09e309251/XRTK.Lumin/Packages/com.xrtk.lumin/Editor/LuminRemote.cs#L80) executes).
See the errors in the console:
Asset Packages/com.xrtk.lumin/Runtime/Plugins/Editor/x64/TouchpadGestureStateMixer.dll has no meta file, but it's in an immutable folder. The asset will be ignored.

Expected behavior
?  I'm not sure actually, hence this bug report.  Definitely no errors though.
Actual behavior
Your Setup
Upgrading older XRTK system to latest ML & XRTK packages.  Including moving from submodules to package install.
Additional context
The copy happens successfully (after a wee fix on LabDriver - PR incoming).  My guess is that in the developer environment, Unity creates the necessary meta files and this issue is only visible on installed systems.
Perhaps Lumen package could include meta files, or perhaps the copy could happen to the assets folder?  What do you think?

What version were you trying to install?

XRTK Lumin 0.20.0-preview.12/Core preview.108

@FrozenKiwi I sent you an invitation to the XRTK org. You shouldn't need to fork to make the changes and open a PR.
Good think I know you IRL huh? haha

That makes things considerably simpler :-)  Thanks a bunch Stephen!


Implement tick_timer() for lptimers

Ref https://github.com/stm32-rs/stm32h7xx-hal/pull/114
The tick_timer method is not implemented for LPTIM[1-5]
Is there some limitation of the LPTIMs that makes it difficult?
The LPTIMs require a specific initialisation sequence (for example, CFGR must be set before enabling the timer, ARR must be set after), so it's not difficult but rather a little tedious to check against the RM that it's correct.

@richardeoin
I needed the tick_timer method, so I have a push available with this code.   There are a couple of differences in how LPTIM'ers work relative to the other TIM'ers, but nothing super complex.
My code includes a couple of (proposed) fixes such as

fn counter() sometimes gave incomprehensible results, so I changed the
self.tim.cnt.read()bits()
to
self.tim.cnt.read().cnt().bits().into()

Hi @noppej That's great, proposed improvements and fixes are very welcome! Normally we do this by Pull Requests, so if you make a Pull Request with your code I would review it.

Hi @richardeoin ... I will gladly create a pull request. Before I do, I'd like to get your view on something, so that I can fix that at the same time.
Currently, for regular (non low power) timers, the fn set_tick_freq<T>(&mut self, frequency: T), sets a reload value in the ARR register. This function, is also called from fn tick_timer<T>(self, frequency: T, prec: Self::Rec, clocks: &CoreClocks) .
Is it just me, or should the tick_timer set the frequency (PSC) ONLY, and NOT set the ARR?

I think set_tick_freq does set the ARR to 0xFFFF for 16-bit timers, and 0xFFFF_FFFF for 32-bit timers. That's those two lines https://github.com/stm32-rs/stm32h7xx-hal/blob/master/src/timer.rs#L376-L377
The documentation on the tick_timer method in its trait definition says that it "Counts from 0 to the counter's maximum value". That sentence could be made more precise (does it include the maximum value or not?), but setting ARR to the maximum value seem reasonable based on that.


Rancher generates wrong docker command therefore taints are not applied on nodes.

Rancher Server Setup

Rancher version: 2.6.3

Information about the Cluster

Kubernetes version:
Cluster Type (Local/Downstream):

Downstream, provider AWS

User Information

What is the role of the user logged in?

Admin/Cluster

Describe the bug
Rancher generates wrong docker command when a cluster is created using Provision new nodes and create a cluster using RKE  option(AWS Auto scalling groups) therefore taints are not applied on nodes.

To Reproduce

got to rancher homepage
Click on create new
choose AWS EC2

Result
Expected Result
With this command generated by rancher when new cluster is created:
Wrong Generated command: docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run  rancher/rancher-agent:v2.6.3 --server https://vpn.dev.rancher.snetlabs.com --token pg6pffzxnpwcgsdfsfhj2zmh669v5dp8fs48dwdk2pc4bzczw8d8svzv --ca-checksum 4c69a1f4c4efeb3f079f20e10sdfsfjkbwea98bc02ef1db00e7 --worker --taint softhermember=true:NoSchedule
Expectation was that taints will be added on nodes created but it did not.
SURE-4481

Did anyone faced similar issue?

I have also run in to this on Rancher 2.6.4, with the Registration UI for RKE nodes on a custom cluster outputting --taint. However, I can confirm that this doesn't result in the node being tainted on join and --taints must be used instead. --taints is also the flag listed in the documentation, so this seems to be a UI bug?

I've also opened up a support case referencing this ticket - 00343946.

Bumping to prevent closure, as this is still an issue. I've been told the internal bug ticket for this is SURE-4481.

Bumping to prevent closure, as this is still an issue.

@KingJ  @vishal563 is the downstream a windows cluster?

@KingJ @vishal563 is the downstream a windows cluster?

In my case, no - Linux-based.
I opened up a support case with Rancher a few months back, and they've acknowledged this bug. Not seen a fix released yet.

I would agree that this seems to be a UI bug. From what I can tell the registration command is generated in this file, and the taints are added to the command here. In that file that the flag --taint is being pushed to the UI, as opposed to the proper --taints flag.
Curiously, this issue does not reproduce when registering custom RKE1 clusters which utilize windows worker nodes. In this case, the registration command will include the proper --taints flag both when generating the linux registration command as well as when generating the windows registration command.

I just tried to reproduce this issue in three ways, but in all three ways it seemed to work in the latest version of v2.6-head.
1. Node Template
I created an RKE1 node template with taints:

That resulted in the taint appearing correctly in the cluster:

2. Node Pools
In the EC2 cluster's node pool section, I added a taint during cluster creation:

The taint showed up successfully:

3. RKE1 Custom Cluster Creation
When I went to create a custom RKE1 cluster, the --taints was pluralized in the Docker command:

I had a question about the steps to reproduce in the issue description. I don't see how one gets from the EC2 node pool cluster creation page to the docker command. When I create a node pool cluster on EC2, the form takes me straight to cluster management with no registration command shown. The registration command is only visible in the UI for custom clusters. So I'm wondering if the original issue meant to say it was a custom RKE1 cluster? And if not, how was the command obtained?
I believe the code that is being used for generating the docker commands for creating RKE1 clusters is being taken from an iFramed Ember page from the old UI. And the old UI seems to use the correct pluralization:
taints.forEach((taint) => {
      out += ` --taints ${ get(taint, 'key') }=${ get(taint, 'value') }:${ get(taint, 'effect') }`;
    });

At first I assumed this issue was about RKE1 due to the Docker command being used, but now it looks like the broken code is only in the dashboard, which isn't used for RKE1 provisioning. So I'd like to confirm the cluster type - node pool vs. custom - and the K8s distro to be able to reproduce it.

@catherineluse I was able to reproduce the issue only when creating a custom RKE2 cluster. I followed the following steps

Create custom RKE  2 cluster
On the cluster registration screen click Show Advanced

Add in some taints and observe the registration command below update


[web] using hooks_riverpod app stuck at Waiting for connection from debug service on Chrome...

Describe the bug
using hooks_riverpod 1.0.0 on web cause the app to be stack at
"Waiting for connection from debug service on Chrome..."
To Reproduce

code sample
import 'package:flutter/material.dart';
import 'package:hooks_riverpod/hooks_riverpod.dart';
import 'pod.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(primarySwatch: Colors.blue),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends HookConsumerWidget {
  final String title;
  const MyHomePage({Key? key, required this.title}) : super(key: key);

  @override
  Widget build(context, ref) {
    final counter = ref.watch(counterPod);
    return Scaffold(
      appBar: AppBar(title: Text(title)),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text('You have pushed the button this many times:'),
            Text(
              '${counter.value}',
              style: Theme.of(context).textTheme.headline4,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: () => counter.value = counter.value++,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ),
    );
  }
}

pubspec.yaml
name: counter_app
description: A new Flutter project.
version: 1.0.0+1

environment:
  sdk: ">=2.14.4 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  flutter_hooks: ^0.18.0
  hooks_riverpod: ^1.0.0

dev_dependencies:
  flutter_lints: ^1.0.4

flutter:
  uses-material-design: true

likely a duplicate of https://github.com/rrousselGit/river_pod/issues/889. @aoatmon please take a look and if it's the same, please close this one and comment there to make it easier for the maintainers :-)

likely a duplicate of #889. @aoatmon please take a look and if it's the same, please close this one and comment there to make it easier for the maintainers :-)

seems that the underlying issue is actually from dart itself


Bump dep versions to latest

The new versions highlighted a bug in the stackdriverSender definition, which this change also fixes.

@artembilan I'm also planning to merge this bump of versions into 1.0.x. Is that OK, or should we stay on the older RC1 versions there?


Zqs 920 loss function wrapper

I have accidentally commited other things on this branch, closing it and opened #34

I wanted to closed #33 , not this one, sorry for the mess 😅


Updated James' contact information

Sorry, could've looked that up by myself (>.<)

No problem, also practising pull requests ;)


#59: Removed TurretTurnAngle and TurrentManualAim State

Removed the use cases of the mentioned states but the classes still exist.

Sorry, this is a high school robotics team repository and we're not taking pull requests from outside contributors.


Set protobuf to <4.25.0

TL;DR
Set protobuf to <4.25.0.
Some of unit tests are failing due to the changes in the latest protobuf. https://github.com/flyteorg/flytekit/actions/runs/6741354377/job/18325816188?pr=1918
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
^^^
Tracking Issue
NA
Follow-up issue
NA

If you find an issue in the protobuf github, can you link it here?


Module 1.1 Assignment

Given what you have learned about Git, why would you want to use Git in your classroom?

To better manage demands and codes, generating versioning.


Streaming ASR support

Can we do streaming ASR as a downstream task ?
If not directly any high level steps and starting point  to finetune something like Streaming Convnets

Hello,
Sorry, we don't support streaming ASR currently.


UX improvements to Settings

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)

I always thought, shouldn't the Pin Sidebar toggle also be a switch like the ones used for feature flags? I don't think it needs its own iconography.

@freben thanks -- fixed both things.

@freben any suggestions how to make the test work?

Maybe some help in here: https://github.com/mui-org/material-ui/issues/17697

@stefanalund it's data-testid, not data-test-id

@stefanalund Maybe it could be interesting to also try to use userEvent.click instead of fireEvent. It really works a lot more like an actual user and browser does, by emitting the entire series of events that may or may not be relevant. Like mouse enters the thing, mouse moves a bit, button is pressed down, button is released ..." instead of just the low level "click" and nothing else. This sometimes works a lot better. We don't use it a lot yet but it feels like the future :)
https://github.com/testing-library/user-event

Thanks for the help @abhishekjakhar — much appreciated!

Thanks for the help @abhishekjakhar — much appreciated!

Glad to help.


Update README.md

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.284%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1540

Relevant Lines:
1583

💛  - Coveralls


fixed heading issue for smaller screens

Fixes #44
I have declared variables and assigned your values for rotate animation and for smaller screens I have assigned values which fixes the actual issue. I have also written font-weight: bold for that you don't have to use <b> </b> again and again.
Here I attached the differences before and after :

Also this :

Thanks 🙏


Allow Twitter notifications to include media

Allow Twitter notifications to include media.
The notifier uses the Twitter-recommended async chunked media/upload approach and tries to convey the correct mime type of the media. The implementation is based on https://github.com/geduldig/TwitterAPI/blob/master/examples/upload_video.py.
notify:
  - name: twitter
    platform: twitter
    consumer_key: …
    consumer_secret: …
    access_token: …
    access_token_secret: …

automation twitter:
  alias: Send a test message
  initial_state: False
  hide_entity: False
  trigger:
    platform: time
    seconds: 00
  action:
    - service: notify.twitter
      data:
        message: "Test at {{ now().strftime('%I:%M:%S %p') }}."
        data:
          media: /tmp/my-awesome-video.mp4
    - service: homeassistant.turn_off
      entity_id: automation.send_a_test_message

Hi @MikeChristianson,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

@balloob Please have another look, thanks.

Awesome! 🐬  🎉

Thanks, @balloob! 🎊 Glad I could help the community, too.

Can you please update the component page to include the correct formatting for images, can send txt tweet no problems, yet with the above example using both a local path and http:// I can not get the notify to work once I add the include media code.


Add comment about combined _.defaults and _.extend

@jridgewell it's done. Is it okay that I made this revert commit? I mean if you do squash merge at the end it won't matter.

No, we can squash merge it. Still need the link to #3842. And someone else should look over the wording. @captbaritone? 😉

@jridgewell
Still need the link to #3842

Do you mean I should add #3842 to the commit message?

To the comment, not the commit message.

@jrburke how about now?

Rather than "makes sense" can you explain the behavior that it actually avoids?

@captbaritone I added line about it helps to avoid conflicts with Object.prototype properties.

I'm not familiar with this issue, and those who are reading this comment probably won't be either. In what way does it "make sense"? Does it preserve attributes which have been explicitly set to undefined? Does it overwrite them?

It has two steps.

We have to create an object that contains all properties, attrs taking precedence over defaults. We clobber prototype inheritance here on purpose.

_.extend({}, defaults, attrs)

Anything in Step 1 that is undefined should be overridden with its defaults value. Since we clobbered prototype inheritance, we know for certain that if something is undefined, it was set specifically to undefined in attrs. (Or, if it was set in defaults, it will still be undefined after this step)

_.defaults(_, defaults)

Superseded by #4267.


act_dr6_lesing likelihood as a  Python package, with data automatically downloaded by the setup.py

Dear ACTCollaboration people,
First, thanks for such amazing data. I have a request/suggestion, if I may. Could you please make the act_dr6_lesing likelihood a Python Package, with data automatically downloaded by the setup.py?, or have the data installed by Cobaya as, e.g., for the Planck likelihood?
With regards,
Uendert

See #4 for the first part of this! Automated data download is for sure the next thing to do.

Just for my education... is there a preferred way of doing (or not doing) getting package data from a URL you are aware of?
From what I can read maybe the best way is for the package to include a command line script which goes and gets the data and installs it which the user can run when they want.

use install_options class attribute, e.g. as
https://github.com/CobayaSampler/cobaya/blob/master/cobaya/likelihoods/planck_2018_lowl/EE.py
Then you can just do cobaya-install packagename.LikeName


Warning on react-native 0.49.x

I get this warning:
Module RNFetchBlob requires main queue setup since it overrides `constantsToExport` but doesn't implement `requiresMainQueueSetup. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.

can be fixed similar to this: https://github.com/wix/react-native-navigation/pull/1983/files

same here +1

You can also check https://github.com/Microsoft/react-native-code-push/pull/1035/files

PR created, see #674

Also seeing this warning.

Hi Guys, you can ignore this type of warning using the YellowBox module:
import { YellowBox } from 'react-native';

// React native 0.55.4 is currently migrating to a new React API.
// Some warnings are expected in this version.
YellowBox.ignoreWarnings([
    'Warning: isMounted(...) is deprecated',
    'Module RCTImageLoader requires main queue setup',
    'Module RNFetchBlob requires main queue setup',
]);

And? What about fix this issue?

@Dictory we already have a fix to this on master: https://github.com/facebook/react-native/issues/17504

@francaracuel Hello. Hm, i use rn v 0.54 and catch this  warning

"react-native": "0.56.0" and I keep seeing the warning but with module RNGoogleSignin

Having this warning also...

just started getting this warning on upgrade to 0.56.0

solution: https://stackoverflow.com/a/51352132
and now I have no any issues


Increase zookeeper sync/init timeouts, add max client connections

Git commit hash or branch: master
Cloud Environment: openstack

On larger zookeeper data sets, followers can fail to synchronize with the master if the sync limit is too low. Also allow maxClientConnections to be set via ansible.
Increase initLimit and syncLimit on zookeeper to the following default values.
initLimit=20
syncLimit=10
maxClientCnxns=200

Closing this, there are already vars to do this in the main zookeeper role.


treewide: remove jonringer as package maintainer and code owner

Description of changes
Jon was permanently banned from the nixos community.
I've noticed that this caused the codeowners file to be invalid, so here is a follow up to the ban, removing Jon as maintainer.
If possible, we should find new code owners for

[ ] /pkgs/development/interpreters/python/hooks
[ ] /pkgs/applications/editors/vscode/extensions

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

We should remove him from maintainers/maintainers-list.nix as well


Note authentication draft

This is functional draft PR for note authentication.  This is a work in progress and some refactoring is required and additional documentation will be supplemented. This PR introduces a NoteOrigin struct which is responsible for holding the information related to the origin of a note - specifically the block header of the block it was created in and in the index of the note in the note tree for that block.  We modify note Felt serialization to include origin information such that the masm code can authenticate the notes origin. We modify the testing patterns such that we can include a MerkleStore when constructing the advice provider.

I've made changes are suggested.  I wonder if instead of merging NOTE_META and NOTE_HASH to produce AUTH_DIGEST it may be more efficient to authenticate the leafs directly using mtree_verify.  I'm not certain of this but it may be worth considering - shall I create an issue for this or shall we explore this for this PR?

I don't think this would be needed. While it may reduce the number of cycles on the stack, it will basically double the number of rows in the hasher chiplet as we'd be verifying nearly the same path twice.

Makes sense, thanks!


use conda libs and includes.  add zip/unzip deps.

Eventually it might be good to hack all of the BUILD files that we already have libraries for.  This only fixes the ones that are broken (only look for system zlib).
zip and unzip are proposed at https://github.com/conda-forge/staged-recipes/pull/1533 - might want to wait for them to be available before doing much with this PR.

Sorry, this does not actually work yet.  False alarm.  I think I'm on the right track, but getting mixed results.

Bazel does seem to be quite unforgiving about customizing certain search paths.  If you figure this one out @msarahan let me know, I would be very interested.

It's actually already fixed in master.  I thought it was really weird, because they were building zlib themselves - why wasn't this finding it?
Here's the missing link: https://github.com/tensorflow/tensorflow/blob/master/grpc.BUILD#L540-L541
I'm planning on just patching that in until the next release.  Actually using conda's libs would be nicer, but I need to get this out sooner rather than later.


Ken/did merge

Fragment passing, COSE_Sign1 and DID:x509 support.
When a fragment arrives at gcs its signature is checked and the issuer DID:x509 is checked. If both are good the issuer/feed are offered to the policy and if itis accepted by the policy it will be consumed.

Replaced by https://github.com/microsoft/hcsshim/pull/1575


"1 shared_informer.go:401] The sharedIndexInformer has started, run more than once is not allowed" in logs

Hello! I see this line repeated in logs of Policy Reporter every five seconds or so:

1 shared_informer.go:401] The sharedIndexInformer has started, run more than once is not allowed

I have metrics server enabled with "--metrics-enabled", it seems to be somehow related. I can troubleshoot more if need be. Thank you!
Maxim

Hey, which version do you running? I released this morning the helm chart version v2.9.5 which the newest policy-reporter version 2.6.2. This version should fix this issue.

It helped! Thank you!


Does this really require go 1.12?

The go.mod file is set to work only with go 1.12.  When building with go 1.11 I get errors around which version of Go is required.  Is go 1.12 required?  Can this limitation be removed from the go.mod?

what is the benefit of using go 1.11 and not use go 1.12? (with coming 1.13 release)

There is none.  I'm trying to compare libraries and want to be accurate or not on stating that sony/gobreaker requires go 1.12. (which it currently appears to since it does not build as a dependency on 1.11)

IMHO i think that gobreaker requirement need to still the go 1.12. most of the projects move to go 1.12 now as hard dep.

I have confirmed that gobreaker works well in Go 1.10, 1.11 and 1.12.
https://github.com/sony/gobreaker/blob/master/.travis.yml#L3-L5


Bypasses validate functions

Using optionOrPrompt bypasses validate functions specified on inputs. Is there a way to trigger them?

Unfortunately I don't have any time to look at this right now - if you're able to fork the project and make a fix, I'll look at a pull request when I get some time.

With the patch at https://github.com/artefact-group/yeoman-option-or-prompt/pull/15, it should be "straight-forward" to implement it. I personally do not use "validate" in my setup. Thus, I just comment instead of going straight ahead and implementing it 😇.


Custom icon doesn't appear

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
6.0.4
Electron version
22.0.2
Operating system
macOS 10.13.4
Last known working Electron Forge version
No response
Expected behavior
When running yarn start, the electron app works fine. But the custom icon I've added to the app doesn't appear. I still have the default Electron icon.
I have carefully followed the documentation. I created 16x16, 32x32, 128x128, 256x256 and 512x512 png icons, generated an icon.icns set with iconutil, an icon.ico for Window and an icon.png for Linux. I've added all of them at the project root in an icon folder, and added their path to my forge.config:
import type { ForgeConfig } from "@electron-forge/shared-types";
import { MakerSquirrel } from "@electron-forge/maker-squirrel";
import { MakerZIP } from "@electron-forge/maker-zip";
import { MakerDeb } from "@electron-forge/maker-deb";
import { MakerRpm } from "@electron-forge/maker-rpm";
import { MakerDMG } from "@electron-forge/maker-dmg";
import { MakerWix } from "@electron-forge/maker-wix";
import { WebpackPlugin } from "@electron-forge/plugin-webpack";
import { mainConfig } from "./webpack.main.config";
import { rendererConfig } from "./webpack.renderer.config";

const config: ForgeConfig = {
  packagerConfig: {
    icon: "./icon",
  },
  rebuildConfig: {},
  makers: [
    new MakerSquirrel({
      setupIcon: "./icon/icon.ico",
    }),
    new MakerZIP({}, ["darwin"]),
    new MakerRpm({
      options: {
        icon: "./icon/icon.png",
      },
    }),
    new MakerDeb({
      options: {
        icon: "./icon/icon.png",
      },
    }),
    new MakerDMG({
      icon: "./icon/icon.icns",
      iconSize: 256,
    }),
    new MakerWix({
      icon: "./icon/icon.ico",
    }),
  ],
  plugins: [
    new WebpackPlugin({
      mainConfig,
      renderer: {
        config: rendererConfig,
        entryPoints: [
          {
            html: "./src/index.html",
            js: "./src/renderer.ts",
            name: "main_window",
            preload: {
              js: "./src/preload.ts",
            },
          },
        ],
      },
    }),
  ],
};

export default config;

I have also added the path to main.ts:
const createWindow = (): void => {
  // Create the browser window.
  const mainWindow = new BrowserWindow({
    width: 1200,
    height: 800,
    icon: "./icon/icon.png",
    webPreferences: {
      preload: MAIN_WINDOW_PRELOAD_WEBPACK_ENTRY,
      nodeIntegration: true,
      contextIsolation: false,
    },
  });

The app compiles without any problem, but I don't see my custom icon.
Actual behavior
I don't see the custom icon.
Steps to reproduce
I should see the custom icon.
Additional information
No response

Thanks for submitting this issue!
Can you check whether the packaged application in your /out/ folder has the expected icons?
The icons are set in the package step, meaning that we don't expect the icons to be present in the yarn start dev mode of the application. However, on macOS, you can set the icon in the dock with app.dock.setIcon (docs) if you want to make sure the icon is there in dev mode.

same issue.

Can you check whether the packaged application in your /out/ folder has the expected icons?

yes the icon seems to be there, but when i try to install it it shows nothing..

The icons are set in the package step, meaning that we don't expect the icons to be present in the yarn start dev mode of the application.

on my dev mode its fine the icon is showing perfectly fine.

Hi @georgexu99 ,
All my apologies for my late answer, I didn't see your post before receiving @0xearl 's notification.
Indeed, I can display the icon during development thanks to the line app.dock.setIcon(path.join(process.cwd(), "icon", "icon.png")); in main.ts. However, I don't have the icon in the out folder.
out has 4 files:
- MyApp.app (the app icon is Electron's)
- LICENSE
- LICENSES.chromium.html
- version

If I right-click on MyApp.app to show the package's content,I have:
- Contents
  - Frameworks
    - Electron Framework.framework
      - Electron Framework
      - Helpers
        - chrome_crashpad_handler
      - Librairies
        - libEGL.dylib
        - libffmpeg.dylib
        - libGLESv2.dylib
        - libvk_swifthshader.dylib
        - vk_swiftshader.icf.json
      - Resources
        - many .lproj folder with locale.apk files
      - Versions
        - many other folders
    - MyApp Helper
    - MyApp Helper (GPU)
    - MyApp Helper (Plugin)
    - MyApp Helper (Renderer)
    - Mantle.framework
    - ReactiveObjC.framework
    - Squirrel.framework
  - Info.plist
  - MacOS
    - MyApp (unix executable)
  - PkgInfo
  - Resources
    - af.lproj
    - am.lproj
    - app
      - node_modules
      - package.json
    - ar.lproj
    - bg.lproj
    - ... many other .lproj empty folders
    - de.lproj
    - electron.icns (looks like electron's default icon)
    - en_GB.lproj
    - ... many other .lproj empty folders
    -

Anyways, I don't see my icon anywhere here.

I've made another attempt today with the New York Time's icns (you can get it here). It doesn't work either. The installer looks like this:

As you can see, the icns is correctly detected since the icon appears on the top navbar and on the footer. But the main logo is still Electron's default. When I install and launch the app, all the logo are also Electron's default.
There is clearly an issue with MakerDMG and/or the icns process.

Another note: if I inspect the package content in /out/myapp-darwin-x64, the info.plist file contains the lines:
    <key>CFBundleIconFile</key>
    <string>electron.icns</string>

So, it seems my icon.icns is not properly called.
Any update @georgexu99 , @erickzhao ?

same issue.

Can you check whether the packaged application in your /out/ folder has the expected icons?

yes the icon seems to be there, but when i try to install it it shows nothing..

The icons are set in the package step, meaning that we don't expect the icons to be present in the yarn start dev mode of the application.

on my dev mode its fine the icon is showing perfectly fine.

@AndreevAndrey sadly, no. The icon issue persist, and no one cares about it :(.

@DoneDeal0 , thanks for the quick response!

I was running into the same issue and it looks like we are setting the icon wrong.
You'll need to set the icon in the packagerConfig's icon. https://www.electronforge.io/guides/create-and-add-icons#windows-and-macos
Additionally, I think file format may be an issue. I ended up converting my png into ico and icns to support other platforms.
Do these things and you will solve this issue. I don't think its completely needed to switch build methods all together.
Hope this helps!

Still stuck after all these months...
@itstristanb : if I remove the MakerDMG:
const config: ForgeConfig = {
  packagerConfig: {
    icon: path.join(process.cwd(), "icon"),
  },
  rebuildConfig: {},
  // makers: [
  //   new MakerDMG({
  //     icon: path.join(process.cwd(), "icon", "icon.icns"),
  //     background: path.join(process.cwd(), "icon", "icon.png"),
  //     format: "ULFO",
  //   }),
  // ],
  plugins: [
    new WebpackPlugin({
      mainConfig,
      renderer: {
        config: rendererConfig,
        entryPoints: [
          {
            html: "./src/index.html",
            js: "./src/renderer.ts",
            name: "main_window",
            preload: {
              js: "./src/preload.ts",
            },
          },
        ],
      },
    }),
  ],
};

I get the following error:

An unhandled rejection has occurred inside Forge:
Error: Could not find any make targets configured for the "darwin" platform.

So I need the MakerDMG. The build works fine, but the installer still doesn't have any main icon (only in the nav and footer of the installation window). When launching the app, all's good... except I still have the default Electron icon!!!
@erickzhao , @georgexu99 any idea? I can't believe this superb project is ruin at the build step for something as silly as an icon.

@DoneDeal0 a little late to the party here, but that final working code was still working on macOS? I'm having a lot of trouble getting it to recognize any icons at all.
I can get the dock icon showing in dev mode with app.dock.setIcon(path.join(process.cwd(), "icons", "icon.png"));, but not with the .icns

@DoneDeal0  Create icons name folder after use app.dock.setIcon(path.join(process.cwd(), "icons", "icon.png")) for Mac


v1.2 edited formatting in Implementations

Coverage remained the same at 89.9% when pulling 636e8c3958dca31ff490c074e64dbd9971cef7fc on aziziazfar:v1.2_updateUGDG into 98bec4c1a079796a3edd09fe04c3ac6376d0bb72 on CS2103AUG2017-T15-B4:master.


⚠ ClamAV has degraded performance

In 7b4a9c7, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 566 ms

Resolved: ClamAV performance has improved in 7cc55f9.


the meaning of prior frame and canonical frame

Hi, Davis,
You really did a wonderful job for both your paper and your codebase! Thanks for sharing the code, which is well-organized and well-annotated. I love it and I have learned a lot.
I have some trouble understanding the transformation of coordinate systems, eg. compute_world2aligned_mat and compute_cam2prior. Could you explain a little bit about the default setup of each coordinate system, and why we need to transform?
Besides, what is the meaning of "prior frame" and "canonical frame"? Do they all refer to reconstructing motions in the world coordinate system? If not, what's the relationship or connection between the prior frame and the canonical frame?
Looking forward to your reply.

Hello, I'm glad you're finding the codebase useful.
There are 3 coordinate systems that are relevant here:

The coordinate system of the processed AMASS mocap data. The origin of this system is on the floor with +z pointing "up" orthogonal to the floor (i.e. the floor is the xy plane). This coordinate system is fixed (i.e. it doesn't change throughout a motion sequence). I sometimes refer to this as the "world" frame in the code.
The "canonical frame" and "prior frame" are used interchangeably and usually mean the same thing. In particular, this is the coordinate system that the motion model (HuMoR) directly operates in. The origin of this coordinate system changes over time throughout a motion sequence (wrt the "world" frame). This coordinate system is described in the paper and supplementary material: in short it's set up so that +z is up (same as the world frame), +x axis is parallel to the floor plane but pointing in the same direction as the body right vector (defined by the SMPL root orientation), and so +y will point forward. The xy position of the origin is at the body root position. The reason we need this coordinate system is so that the network can easily generalize no matter where the human is in the "world" frame -- the network can always assume the inputs are transformed in this canonical coordinate frame. This makes the network input invariant to the arbitrary position or facing direction of the human in the "world" frame.
The camera coordinate frame. This is only relevant when we are fitting to RGB or RGB-D video. Its origin is defined by the camera pose and fixed over time (assuming the camera is static).

So compute_world2aligned_mat computes the rotation that goes from the "world" frame to the "canonical" frame. This is used to transform the data inputs to the neural network before passing them in (and to transform outputs back to the "world" frame after making a prediction). This is used while training and testing the model with AMASS data, and during pose estimation fitting from RGB video.
On the other hand, compute_cam2prior is only used during fitting to video. This computes the transformation from the camera coordinate frame to the canonical one. This is needed because the poses we predict from a video are in the camera coordinate frame, but HuMoR is only trained in the "canonical" frame. So we have to first transform the current pose to this canonical frame before using HuMoR to roll out the motion. We can figure out the transformation from camera to canonical frame by using the floor plane (which defines the xy plane of the canonical frame at z=0) and the person's current 3D pose (which gives the xy position of the origin the body right vector).
Note: when I say "canonical" or "prior frame" in the code base, it's not always precise... e.g. in viz_fitting_rgb the "prior" frame is actually the coordinate system defined by the "canonical" frame of first timestep of the motion sequence only.
Hope this helps clear things up a bit, all the coordinate systems here can definitely be confusing!

I found the root orient is init with x_axis*pi.
https://github.com/davrempe/humor/blob/fc6ef84f0baa153be15427402e0147ed1a63a11a/humor/fitting/motion_optimizer.py#L82
And I showed the vertices and joints.

It seems the canonical frame is left-down-back.
Could you have a look at this result?


Feature Request: Ability to refresh navigationOptions

There are a number of issues related to the lifecycle around navigationOptions, which does not update after the initial render:
https://github.com/react-community/react-navigation/issues/2309
https://github.com/react-community/react-navigation/issues/2203
https://github.com/react-community/react-navigation/issues/940
https://github.com/react-community/react-navigation/issues/413
The common prescribed fix is to use "setParams" or put any state that controls the header configuration into the router parameters. This feels like a forced workaround when the header state is not necessarily part of a router parameter, but some other state.
Could navigationOptions take a property that controls whether it should re-render more aggressively? Or even a function like "shouldHeaderUpdate"?

👍

👍

@Antoine38660
so is it fixed in this merge? Any example out there how to use it?
Thanks a lot

@MarcelBlockchain we used the "setParams fix" but we are still looking for a better way to do! You can see how we did it in this commit : https://github.com/gitpoint/git-point/pull/193/commits/a10e9c9df8cffb6297b79ad8e1023e40b6c0a77c 😃
Sorry for the late answer, I miss the notification...


Few POSIX API implementations checks for negative error codes

cond_wait() and sem_trywait() implementation checks for error codes with negative sign. This is not expected as per documentation.
static int cond_wait(pthread_cond_t *cv, pthread_mutex_t *mut, int timeout)
{
   ...
   ...
    return ret == -EAGAIN ? ETIMEDOUT : ret;
}

int sem_trywait(sem_t *semaphore)
{
    if (k_sem_take(semaphore, K_NO_WAIT) == -EBUSY) {
     ...
     ...
}

Figured out that this isn't a bug. The implementation both checks for error codes updated from zephyr APIs and not POSIX implementation.
-EAGAIN in cond_wait() is updated by _pend_current_thread() function.
-EBUSY in sem_trywait() is updated by k_sem_take() implementation.
Hence both POSIX API implementations are checking for negative error codes.


Change floats to NSNumbers

This should also allow us to not have to set 0 for the value in structured events.


crypto-random-string breaking webpage

I'm trying to put together a simple todo app with Deno and am running into an issue where calling crytpoRandomString causes the page to crash without outputting any meaningful error.
The code:
// ..
import { cryptoRandomString } from<EMAIL_ADDRESS>
type Props = React.ComponentProps<typeof useDeno>;

type Task = {
  id: string;
  data: string;
};

export default function Home<Props>() {
  const [tasks, setTasks] = useState([] as Task[]);
  const [task, setTask] = useState("");

  const handleAddTask = (e: any) => {
    const newTask: Task = {
      id: cryptoRandomString({
        length: 16,
        type: "abc",
      }),
      data: task,
    };
    setTasks([...tasks, newTask]);
    setTask("");
  };

  // ..

  return (
   // ..
   <button onClick={handleAddTask}>Add Task</button>
   // ..
  );
}

I'm not quite sure why this is happening, but aleph isn't erroring out at the commandline, so this must be some issue with the crypto-random-string lib.

Update:
This works:
import { cryptoRandomString } from "https://github.com/piyush-bhatt/crypto-random-string/raw/main/mod.ts";

This doesn't:
import { cryptoRandomString } from<EMAIL_ADDRESS>


425-bulk workflow manager - auto-resume enhancements

Enhancement to auto-resume feature;

Keeps backwards compatible behavior of auto-resuming.
Uses a tree-traversal to walk the Pages under /etc/acs-commons/bulk-workflow-manager to find resumable BWM pages (it does NOT visit the potentially very large batch structure under each page); This traversal is very fast as its walk of a isolated Page tree (which should never get large enough to be problematic).

@justinedelson sure; thats a problem - fixed


CLI tool -- "Repo not found" when trying to create a repo that already exists

When trying to create a repo that already exists, bit returns a Repo not found message. E.g.
bit -k $BITIO_KEY repo create -r bls_work_stoppage -d 'Bureau of Labor Statistics Work Stoppage Data from https://www.bls.gov/wsp/' -p False
Repo not found.

A more helpful message would tell the user that the repo already exists. Alternatively, an option could be added to overwrite an existing repository.

With the deprecation of repos and the v2 API, this is no longer relevant.


suspend users with api

Hi, I am wondering if it's possible to suspend users with API here? We just want to disable rather than delete the user. Thanks.

Hey there! Unfortunately the API only supports removing a user. If you want to "reactivate" a user you can recreate the user, their Authy ID will remain the same. Let me know if that doesn't suit your use case, happy to take the feedback to the rest of the team.
More detail: https://www.twilio.com/docs/authy/api/users

Thanks! It would be very useful to add this disable functionality. Actually, recreation could not solve my problem. After recreation, we need to add the user again. Otherwise, we will have an error "There was an error processing the transaction."

Can you give me an example of the code that's causing that problem? I'll make sure that's the intended functionality. I'm also not sure what you mean by "After recreation, we need to add the user again."

Several other suggestions:

It would be convenient to have the push notification showing automatically on top of Android authy app, just like what Duo has.
Is there any function to enumerate all the users in an app? With that, we could deploy the app and then add new users later on.
Could it also be possible to have many sub-users under a user? By doing so, we could deploy the app with a number of sub-users and the app users only need to scan a barcode to get access. This would be ownderful for my project.

In my project, I just want to deploy an app to many users, each with a authy push notification. Right now, I have to create many users with many emails, which is impossible, for deployment. The ideal case would be having user accounts managed outside of the deployed app so that they are modular and independent.
Please let me know what you think. Thanks.

I attached python code. You probably need to change some settings. Please try this to see the two messages on the Authy app.
import subprocess

# Check if it's working
cmd = 'curl "https://api.authy.com/protected/json/app/details" ' \
      + '-H "X-Authy-API-Key: zA56lWvPLYj2g5EEN9RGDDmnc2TyIV9b"'
subprocess.check_call(cmd)

# Disable an user from an app
cmd = 'curl -X POST https://api.authy.com/protected/json/users/90351534/remove ' \
      + '-H "X-Authy-API-Key: zA56lWvPLYj2g5EEN9RGDDmnc2TyIV9b"'
subprocess.check_call(cmd)

# Enable an user from an app
cmd = 'curl -XPOST "http://api.authy.com/protected/json/users/new" ' \
      + '-H "X-Authy-API-Key: zA56lWvPLYj2g5EEN9RGDDmnc2TyIV9b" ' \
      + '-d<EMAIL_ADDRESS>' \
      + '-d user[cellphone]="6172300695" ' \
      + '-d user[country_code]="1"'
subprocess.check_call(cmd)

# Push again, with errors after recreation of users
cmd = 'curl "https://api.authy.com/onetouch/json/users/90351534/approval_requests" ' \
      + '-H "X-Authy-API-Key: zA56lWvPLYj2g5EEN9RGDDmnc2TyIV9b" ' \
      + '-d message="Login requested for a CapTrade Bank account."  Please make sure you rotate the keys on your application anyway, you can do that from the application settings page:

I'll take a look at the code/your suggestions!

Thanks!


statemachine detection fails if nbsp; or special chars in statemachine title

this prevents certain features like our smarter grouping and renaming from working

can't reproduce anymore. Maybe something else was going on. Will re-open if needed.


Expose Fabio metrics via Prometheus

Fabio looks like a really impressive proxy for hashicorp related systems.
However I have seen that the metrics exposed by fabio do no include prometheus. The reason for this issue is to request whether anyone would like to work on adding Prometheus metrics to the program.
We will need to perform some instrumentation. I am looking for someone with go expertise. Please let me know if anyone would like to work on this.

Closing this as a duplicate of #211 ... please feel free to  comment on that issue.


fix dlwp_healpix constant coupler batch inference

Modulus Pull Request
Description

Fix the bug where dlwp_healpix constant coupler did not support batch coupled inputs for inference
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The CHANGELOG.md is up to date with these changes.
[ ] An issue is linked to this pull request.

Dependencies

What test covers this change?

@ivanauyeung
I tested successfully the inference of ensemble forecast with this PR.
However, do we know this works in training? have you tested that?

The function set_coupled_fields in the coupler.py is only used in the inference stage. So these changes will not affect the training. Also, tests are added to cover this function.

/blossom-ci


CUDA out of memory with the latest update

Describe the bug
after updating to the latest version i get a CUDA out of memory. Ubuntu, i5 11400, 32gb ram, rtx3080 10gb vram.
both llm were working fine without Cuda oom error before with same settings. Any Idea what changed what could cause this error? Does Devin take more memory now?

My config.toml and environment vars (be sure to redact API keys):
LLM_API_KEY="na"
LLM_BASE_URL="http://<IP_ADDRESS>:5000/v1"
LLM_MODEL="openai/Mistral"
LLM_EMBEDDING_MODEL="lokal"
WORKSPACE_DIR="./workspace"
MAX_ITERATIONS=20000
My model and agent (you can see these settings in the UI):

Oobabooga Web UI
Model:
deepseek-ai_deepseek-coder-1.3b-instruct
https://huggingface.co/deepseek-ai/deepseek-coder-1.3b-instruct

TheBloke_Mistral-7B-Instruct-v0.2-code-ft-AWQ
https://huggingface.co/TheBloke/Mistral-7B-Instruct-v0.2-code-ft-AWQ
this one works although its way bigger in size than the other
Unblocked_Finetuned-Mistral-7B-v0.2-code-full
https://huggingface.co/Unblocked/Finetuned-Mistral-7B-v0.2-code-full
only problem with this one is, that it stops prompting in the frontend only prompting in the make start-backend terminal without writing any actual code

Agent: Monologue

Logs, error messages, and screenshots:
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 644.00 MiB. GPU 0 has a total capacity of 9.54 GiB of which 490.75 MiB is free. Process 1583 has 0 bytes memory in use. Process 4681 has 414.00 MiB memory in use. Including non-PyTorch memory, this process has 7.90 GiB memory in use. Of the allocated memory 7.36 GiB is allocated by PyTorch, and 282.50 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True to avoid fragmentation.  See documentation for Memory Management  (https://pytorch.org/docs/stable/notes/cuda.html#environment-variables)
Output generated in 1.79 seconds (0.00 tokens/s, 0 tokens, context 5222, seed<PHONE_NUMBER>)

@stratte89 is that error message coming from the OpenDevin backend? Or is it coming from the LLM?
We shouldn't be using much more memory, but 644MiB is not a lot. Looks like pytorch is hogging memory on your GPU...

@stratte89 is that error message coming from the OpenDevin backend? Or is it coming from the LLM?
We shouldn't be using much more memory, but 644MiB is not a lot. Looks like pytorch is hogging memory on your GPU...

hey, it's comming from the oobabooga log. do you have an idea how i could stop pytorch from doing that?

That's an oobabooga bug then 😄 nothing we can do about it here


put license file at module root

The Go package discovery service, https://pkg.go.dev, looks for a redistributable license at the root of a module to determine whether it can display the README and documentation for the module.
Although there is an acceptable license file at the repo root, there isn't one at the module root, in the go/arrow directory.
Please copy the LICENSE.txt file from the repo root to the go/arrow directory.

Would a symlink work?

It doesn't work at present. I filed the issue linked above.
Whatever the resolution of that issue, nothing will happen soon (Go is just beginning a 6-month release cycle), so maybe you could copy temporarily.

golang/go#39417 was closed with an explanation of why symlinks can never happen. It suggests one alternative to making the copy, which is renaming the file at root to LICENSE.


Rancher 2.0 Bind ip explicitly of ingress dosen't work

Since the ingress, could not find the source you are using in the repos here, seems to be a fork of the original ingress-nginx, I would like to request the following feature from the main ingress:
https://github.com/kubernetes/ingress-nginx/blob/a118a780361bd4b50b56df7c9deb39b4fd24b5c9/docs/user-guide/nginx-configuration/configmap.md#bind-address
This is important for bare metal setups where you have an host that for some reason is not only running kubernetes service but some other things on a separate ip.
Is it maybe also possible to just use the official ingress-nginx or is there something special with the version you deploy?

probably it's connected with my issue https://github.com/rancher/rancher/issues/14550

I think it might be a bug.
I tried to circumvent this issue by using port 8080 and 8443 in order to redirect my port 80 on my second ip address to port 8080 on all ip addresses. Whenever I change the port mappings, upgrade the workload and remove the pod, it binds to port 80 and 433, it somehow ignores the settings.

Hi @wzrdtales
Can you try the following, please?

Go to the system project.
Go to the config map page.
Edit the nginx-configuration config map
Add the bind-address value to it (https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#configuration-options)

I have encountered the same problem, and the workaround of @loganhz doesn't change anything, I still have Port 80 is already in use when restarting the ingress controller after specifying the bind address. It seems that rancher is bypassing the k8s configuration

@grobert63 https://github.com/rancher/rancher/issues/15163 not sure if this issue helps

I tried updating to the latest ingress version (0.20.0) from k8s repository and I still get the same error. I'm suspecting that it uses the node private IP instead of the bind-address set in the config map as the pod ip advertised in Rancher UI is my node private IP

Specifying the bind-address to a local ip is working for me.
Setup:
ingress version: rancher/nginx-ingress-controller:0.21.0-rancher3
kubernetes version: rancher/hyperkube:v1.13.5-rancher1