battery errors

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I have started to see these errors lately, anyone know why? I don't have LFP battery. Teslamate is installed in docker on Synology NAS
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output
n/a

Screenshots

Additional data
No response
Type of installation
Docker
Version
v1.28.1

Thanks for reporting.
Please update TeslaMate to latest version (1.30.1 as of writing). It seems like you only updated the grafana docker and not the TeslaMate. See https://docs.teslamate.org/docs/upgrading

I have tried many ways to update it on Sinology NAS but not successful.
I hav tried from Container Manager, I hav tried from Poratiner, system just says I have latest update.
any tips?

Use a supported installation method (portainer is not).

Post your docker-compose.yml (without secrets)

version: "3.9"
services:
teslamate:
image: ghcr.io/teslamate-org/teslamate:pr-3630
container_name: TeslaMate
restart: on-failure:5
environment:
- ENCRYPTION_KEY=xxxxxxxx
- DATABASE_USER=xxxxxx
- DATABASE_PASS=xxxxxxx
- DATABASE_NAME=teslamate
- DATABASE_HOST=database
- MQTT_HOST=mosquitto
ports:
- 20002:4000
cap_drop:
- all
database:
image: postgres:14
container_name: TeslaMate-DB
restart: on-failure:5
environment:
- POSTGRES_USER=xxxxxxx
- POSTGRES_PASSWORD=xxxxxx
- POSTGRES_DB=teslamate
volumes:
- /volume1/docker/teslamate/db:/var/lib/postgresql/data:rw
grafana:
image: teslamate/grafana:latest
container_name: TeslaMate-GRAFANA
restart: on-failure:5
environment:
- DATABASE_USER=xxxxxxx
- DATABASE_PASS=xxxxxx
- DATABASE_NAME=teslamate
- DATABASE_HOST=database
ports:
- 20003:3000
volumes:
- /volume1/docker/teslamate/datagrafana:/var/lib/grafana:rw
mosquitto:
image: eclipse-mosquitto:2
container_name: TeslaMate-MOSQUITTO
restart: on-failure:5
command: mosquitto -c /mosquitto-no-auth.conf
# ports:
#   - 1883:1883
volumes:
- /volume1/docker/teslamate/mosqconf:/mosquitto/config:rw
- /volume1/docker/teslamate/mosqdata:/mosquitto/data:rw
- /volume1/docker/teslamate/mosqlogs:/mosquitto/log:rw

Is there a reason you are running a specific PR? Instead of a released version?

image: ghcr.io/teslamate-org/teslamate:pr-3630

As @cwanja already pointed out, you are not using TeslaMate:latest (1.30.1 as of writing) but a testing version from February 2024.
Please see instructions here: https://docs.teslamate.org/docs/installation/docker/

Is there a reason you are running a specific PR? Instead of a released version?

I don’t know why/ how I downloaded a specific version (maybe was following instructions to download it on NAS)
now I am trying to follow proper instructions and running this command from the folder where docker-compose.yml us and it’s saying the image is up to date. If I have the latest version then how do I switch to using that in grafana and keep my data (then delete this old version)
sudo docker pull teslamate/teslamate
Using default tag: latest
latest: Pulling from teslamate/teslamate
Digest: sha256:21b53b2490f88805a48c03998a1a307edfc908dec6323f5221097639bcb846bf
Status: Image is up to date for teslamate/teslamate:latest
docker.io/teslamate/teslamate:latest

YOu must change your docker-compose.yml file,
At minimum you must change image: ghcr.io/teslamate-org/teslamate:pr-3630 to image: teslamate/teslamate:latest. Save it.
Run ´docker compose pullanddocker compose up -d`

You must change your docker-compose.yml file,
At minimum, you must

change image: ghcr.io/teslamate-org/teslamate:pr-3630 to image: teslamate/teslamate:latest. Save it.
Run docker compose pull
docker compose up -d

But it is advised to review your docker-compose file in whole

I am just getting to many issues trying to upgrade Testalate on Synology NAS.
$ sudo docker-compose up
[+] Running 0/0
⠋ Container TeslaMate            Creating                                 0.0s
⠋ Container TeslaMate-DB         Creating                                 0.0s
⠋ Container TeslaMate-GRAFANA    Creatin...                               0.0s
⠋ Container TeslaMate-MOSQUITTO  Creat...                                 0.0s
Error response from daemon: Conflict. The container name "/TeslaMate-GRAFANA" is already in use by container "b6a46ecc6be1a2ebf088f0de073590e5544ccb04a8c5e60233732b044708dc33". You have to remove (or rename) that container to be able to reuse that name.
I followed and online guide that involved installing portioner to get teslamate to work on Synology NAS, is that really needed?
What do I need to backup by data (gathered from the car) and restore it? I like to start from scratch.

was the only purpose of portainer to create the docker-compose.yml file?

Portainer adds another level of abstraction above it which results in more complexity and is therefor not supported.
You are running an outdated, unsupported docker version (docker-compose is deprecated, docker compose is right.

I exported container TestamateDB from the UI, is that all I need to restore vehicle date after?

Nope, just follow https://docs.teslamate.org/docs/maintenance/backup_restore

issue resolved
backed up DB
deleted all images/containers
pulled them from YML folder and restored DB, all is working now including historical data.
Deleted portainer and not using the test image of test version anymore.
Thank you @JakobLichterfeld for helping out a noob (Now have a saved, backup and restore scripts and the backup file of the db.

issue resolved
backed up DB
deleted all images/containers
pulled them from YML folder and restored DB, all is working now including historical data.
Deleted portainer and not using the test image of test version anymore.
Thank you @JakobLichterfeld for helping out a noob (Now have a saved, backup and restore scripts and the backup file of the db.

Great, I'm glad to hear that. I hope you continue to enjoy TeslaMate.


Use --selectProjects option with Jest

Using Craco I am attempting to utilize the Jest's selectProjects cli option to invoke a specific defined project within the configuration.
Using this as the craco.config.js
module.exports = {
  jest: {
    configure: {
      projects: [
        {
          name: "unit",
          displayName: "unit",
          testMatch: ["<rootDir>/**/*.test.*"],
        },
        {
          name: "playwright",
          displayName: "playwright",
          testMatch: ["<rootDir>/**/*.uitest.*"],
        },
      ],
      globals: {
        CONFIG: true,
      },
    },
  },
};

And then in my package.json I am defining the following scripts:
{
  ...
    "test": "craco test --watchAll=false --coverage --json --selectProjects unit",
    "test:ui": "craco test --watchAll=false --coverage --json --selectProjects playwright --showConfig"
  ...
}

But it appears it cannot find a configuration as it throws the following error:

Error: Jest: Cannot use configuration as an object without a file path.
at readConfig (/Users/mstelze/Git/react-example/node_modules/jest-config/build/index.js:188:13)
at /Users/mstelze/Git/react-example/node_modules/jest-config/build/index.js:447:18
at Array.map ()
at readConfigs (/Users/mstelze/Git/react-example/node_modules/jest-config/build/index.js:441:10)
at async runCLI (/Users/mstelze/Git/react-example/node_modules/@jest/core/build/cli/index.js:230:59)
at async Object.run (/Users/mstelze/Git/react-example/node_modules/jest-cli/build/cli/index.js:163:37)

Any thoughts? Am I missing something in the configuration or is this function not supported?

Any thoughts on this?


Feature request: Dynamic Capabilities checked before each run

The only supported way to provide capabilities is to add ".capabilities" file(?)
We need to have a capabilites check that runs before a job is assigned to an agent.
This could be a powershell script that runs when a specific capability is requested.
It could be that a service needs to be running to be able to run a job, but we can't control the service, so before agent is determined we want said powershellscript to run to get this capability value.
Specific examples is to check that docker is running, or that if a local database exists. local user is logged in and so forth.
Values that is runtime and can change several times after startup of the agent.

@caspChristian Thanks for reporting! We are working on more prioritized issues now but will get back to this one soon

These kind of bots is just rude, remove and start maintain this repo properly instead!

WTF!? These kind of bots is just rude, remove and start maintain this repo properly instead!
Should it really be up to reporters to ping issues to "keep them alive" ??? If that what is needed then I might need to create a bot that does just that to counter.
Now please tell me how the original reported issue was dealt with if you are closing this issue, if not make sure to reopen!


Github workflows for at_onboarding_cli

- What I did
adding git workflows to test at_onboarding_cli
- How I did it
- How to verify it
- Description for the changelog

Both the 'check_docker_readiness' and 'check_test_env' seem to be failing. They are retrying a couple of times and then timing out after 5mins.

@srieteja I'm looking at this now.
One of the tests used by at_client_sdk depends on running a script against the virtual environment to load data. So I'd expect that to fail.
Do you have things working locally?


feature request * implement getURL like OpenLayer

hi
i really like your library... nice and elegant. i found a feature in OpenLayer which was very easy to implement in leaflet 0.7.3...
sometimes it is needed to modify the tileUrl on the fly based on the x,y,z coords
an example : http://trac.osgeo.org/openlayers/wiki/UsingCustomTiles
	getTileUrl: function (tilePoint) {

		var tileurl = this._url;
		if (typeof this.options.getURL === 'function') {
			tileurl = this.options.getURL(tileurl, tilePoint, this.options);
		}

		return L.Util.template(tileurl, L.extend({
			s: this._getSubdomain(tilePoint),
			z: tilePoint.z,
			x: tilePoint.x,
			y: tilePoint.y
		}, this.options));
	},

in leaflet-master the code would look like
	getTileUrl: function (coords) {

		var tileurl = this._url;
		if (typeof this.options.getURL === 'function') {
			tileurl = this.options.getURL(tileurl, coords, this.options);
		}

		return L.Util.template(tileurl, L.extend({
			r: this.options.detectRetina && L.Browser.retina && this.options.maxZoom > 0 ? '@2x' : '',
			s: this._getSubdomain(coords),
			x: coords.x,
			y: this.options.tms ? this._globalTileRange.max.y - coords.y : coords.y,
			z: this._getZoomForUrl()
		}, this.options));
	},

Does this have any benefit over https://github.com/ismyrnow/Leaflet.functionaltilelayer ?

less code.. no additional plugin to get the functionality
i think it much simpler to do it this way... you can also use similar existing code from OpenLayer
eg.
    var mylayer = new L.TileLayer('http://server/internal/tiles/style/{z}/{x}/{y}.png', { attribution: '© Any Attribution', minZoom: 10, maxZoom: 15,
            getURL: function(tileurl, tilePoint, options) {
                var z = tilePoint.z;
                var y = tilePoint.y;
                tileurl = tileurl.replace('{y}', ((2 << z) - y - 2) );
                return tileurl;
            }
        }
    );

less code.. no additional plugin to get the functionality

You miss the point of Leaflet design. If a feature is not needed by a majority of users and can be put in a plugin, it will be put in a plugin.

I think it's much simpler to do it this way

It's even simpler to write a plugin for this:
L.TileLayer.Microfunctional = L.TileLayer.extend({
	initialize: function(options) {	// No need for url anymore when instantiating
		return L.TileLayer.prototype.initialize.call(this, null, options);
	},

	getTileUrl: function(tilePoint) {
		this._url = this.options.getUrl(tileUrl, tilePoint, this.options);

		return L.TileLayer.prototype.getTileUrl.call(this, tilePoint);
	}
});

L.tileLayer.microfunctional = function(opts) {return new L.TileLayer.Microfunctional(opts);}

Or, if you want the plugin to modify the behaviour of all tilelayers instead:
(function(previousMethods){
if (typeof previousMethods === 'undefined') {
	previousMethods = {getTileUrl: L.TileLayer.getUrl}
}

L.TileLayer.include({
	getTileUrl: function(tilePoint) {
		if (typeof this.options.getUrl === 'function') {
			this._url = this.options.getUrl(tileUrl, tilePoint, this.options);
		}
		return previousMethods.getTileUrl.call(this, tilePoint));
	}
})

})(window.leafletMicroFunctionalTileLayerMethods);

I still don't see any need to include this in the core library code.

i don't think i miss the point. less code, easier handling... additional feature...
but no problem... it's just a proposal... i'm not unhappy if it is not included...

@emergence75 thanks for the suggestion! Let me think about this for a while...

You miss the point of Leaflet design.

Take it easy Ivan, we don't want to loose awesome potential contributors by being unfriendly upfront. :)

Take it easy Ivan, we don't want to lose awesome potential contributors by being unfriendly upfront. :)

Sorry about that. You know I'm a bit hot-headed sometimes :sweat_smile:


Add downsampling to fallback function

Partly addresses #150 . The value for the downsampling is still taken from [od_reading.config] samples_per_second but that needs more thought!

Other than the one comment - lgtm! Not sure why I didn't do this originally.


Colony vanishes (Could not resolve reference to object)

Describe the bug
all colonists stopped working and were unable to interact with anything they. They all just went on their normal wonder when there is nothing to do and I got an alert for every colonist that there was nothing to do. When I reloaded save I was booted to the world screen and got a nice solid error log
It seems that only my colony vanished, save data still seems to have the rest of the world's data.
Here are the save files(one being the last autosave before it broke and one being the save I took after all my colonists stopped working)
savefiles.zip
To Reproduce
No known way
Error Logs
when loading the broken save file
https://gist.github.com/f8bae3026b881a349295a3f319482caa
Logfile of when colonists stopped working before reloading the map
https://gist.github.com/thefriendlycacti/a1287d97b594132494b13d2736a232a3
Mod List
https://gist.github.com/thefriendlycacti/100a1eff20f09a80a4a5988b407fabf9
Screenshots

https://gist.github.com/HugsLibRecordKeeper/7f407fd2674329c562f2d7d0ddd803d4
Same issue . happend same way . Sadly cannot replicate

I did do some patches around "Verse.AI.RegionCostCalculatorWrapper" so this may be fixed... Please make another post if this reoccurs. Otherwise this will probably be closed in the next week or so, since its sounds like this is not reproducible.

unable to reproduce the issue on 1.3.1

https://gist.github.com/d17dd2e352dd23e2d335a0101be1e0db
happened to me in a modded game. log is linked.
re opening with new tags

Empire3 (Permadeath).zip
save file is attached

Also happening on RT 2.4.2 on loading previously fine save.
https://pastebin.com/WyaCp2FM

Please retest with RT>=2.5.12 and include steps to reproduce. Closing until then.


[TRI-945] Add a manual project setup guide to the docs

We have a quickstart which uses the CLI init command. But we don't have a manual installation guide anywhere.

The manual installation guide should live in the guides sidebar.
It would have steps to install packages
It would have steps to add/modify the correct files and folders (everything the init command does).

For inspiration, create-next-app have good manual installation steps here: https://nextjs.org/docs/getting-started/installation#manual-installation
From SyncLinear.com | TRI-945

/bounty $50

/attempt #277

/attempt #277

/attempt #277

/tip $20 @Chigala


-mode=server ERROR

I can't run the next syntax: sudo cast install teamdfir/sift --mode=server, because appear a error:
dfir@scilabs:~/Downloads$ sudo cast install teamdfir/sift --mode=server
FATA[0000] please provide a distro alias to install
What's the problem?

Sorry. I changed my syntax to: sudo cast install --mode=server teamdfir/sift, and solved.
Thanks

Yeah arguments are positional unfortunately. Glad you got it worked out.


http.post handler not routing - 404 not found

Hi,
This spec is working fine as expected; but when I go to run the code for a real call then it doesn't work; it's like is not loading the handler in the app.
Calls:
get localhost:8080/lita/info -> got response
post localhost:8080/lita/whatsapp -> 404 not found
require "spec_helper"

describe Lita::Handlers::WhatsAppHandler, lita_handler: true do
  it { is_expected.to route_http(:post, "/whatsapp") }

    describe "#whatsapp_messages" do
        it "writes 'OK' as a reply" do
            response = http.post("/whatsapp")
            expect(response.body).to eq("Hello, Faraday v0.17.1!")
        end
    end
end

What could I be missing that the handler doesn't load?
class handler
module Lita
  module Handlers

    class WhatsAppHandler < Handler
        http.post("/whatsapp", :process_whatsapp_messages)

        def process_whatsapp_messages(request, response)
            Lita.logger.info("whatsapp message: #{request.user_agent}")
            response.body << "Hello, #{request.user_agent}!"
        end
        Lita.register_handler(self)
    end

    class EchoHandler < Handler
      route(/^echo\s+(.+)/, :echo, command: true, help: {
              "echo TEXT" => "Replies back with TEXT."
      })

      def echo(response)
        response.reply(response.matches)
      end
    end

    #Lita.register_handler(WhatsAppHandler)
    Lita.register_handler(EchoHandler)
  end
end

Base on the documentation of http_router; it should be used add method to create a map to the route: https://github.com/joshbuddy/http_router#addname-options
(or the method #url instead which take a route as argument)
instead the code is using add_route method, but as the doc said:
Routes will not be recognized unless #to has been called on it.
the #to method is like the callback
  r = HttpRouter.new
  r.add('/test/:variable(.:format)').name(:my_test_path).to {|env| [200, {}, "Hey dude #{env['router.params'][:variable]}"]}

Line with potential issue:
https://github.com/litaio/lita/blob/c1a1f85f791b74e40ee6a1e2d53f19b5f7cbe0ba/lib/lita/rack_app.rb#L74
I recomend the use of the #url method to avoid a big refactor and fix the issue.

@jimmycuadra any idea about this issue?

Your code works as expected to me. Can you provide more info about how you're testing it with a real HTTP request outside of the test suite?
The "route.to" call that you thought might be missing can be found here: https://github.com/litaio/lita/blob/964a827c0b99f742ddbcd143b178e79c59aed56a/lib/lita/http_route.rb#L68

@jimmycuadra Thanks for you answer,

Lita does not automatically mount your HTTP routes at the path /lita. That's just where the routes that are provided with Lita itself are defined. You should get the response you expect if you POST to /whatsapp rather than /lita/whatsapp.

Yes that's the problem
to test just use any test client in you browser like this one:
https://chrome.google.com/webstore/detail/advanced-rest-client/hgmloofddffdnphfgcellkdfbfbjeloo
prepare 2 calls:
get localhost:8080/lita/info -> you should get a response
post localhost:8080/lita/whatsapp -> you should get 404 not found

Still getting the 404 when I try:
post localhost:8080/whatsapp

It works for me:
$ curl -X POST http://localhost:8080/whatsapp
Hello, curl/7.64.1!

The issue might be with the program you're using to test, as Lita is behaving as expected when using the code from top of the issue.

It seems a problem in the project; because now I was able to run it but in another new project, thanks


Expose SES API as globals

Currently we export lockdown. Compartment gets introduced as a side-effect of lockdown, but should exist before. We arrived at a consensus that harden should be exposed as a global. The current notion is that harden should only exist after lockdown, or maybe exist but throw before lockdown, to avoid the hastle that anything hardened before lockdown would need to
somehow be promoted to actually-hard after lockdown.

I hadn't considered before the possibility that harden before lockdown() exists but throws. I like it.


feat: adding dark-theme support for input

Closes #20

https://github.com/SDC-USAR/ArtiGenius-AI/assets/5417662/14ff75ca-6992-40a1-b3d2-143e40ac2b23

LGTM 👍Thanks for your contribution.


No "find & replace" for bad formatted XML?

I have a XML like this
<?xml version="1.0" encoding="utf-8"?>
<DataChecks>
<DataCheck ID="1" ParentDataCheckID="-1" Name="Test ---------------------------------------------------------------" Description="" DataCheckSqlStatement="" WithoutRLS="false" Active="true" ModuleName="" />
  .... 80 lines more
</DataChecks>

XML Notepad tells me "The DataChecks-Element is not declared", and "find" and "replace" are doing nothing: no search, no error, no report, ...
Is this intended?

This is what I see.  Perhaps you have a "Schema" loaded in the "View/Schemas..." dialog that is defining a schema for any XML document that uses no namespace and that is mistakenly being applied to this document.  Try deleting any schemas you see in the  "View/Schemas..." dialog and see if that helps.

here is a screencast: https://autode.sk/3sqBaux
Maybe a user problem?

Oh, thanks for the video, it seems that "find" is broken in some cases, thanks for he video.  I'll check it out.

thanks for the great bug!!
fixed in <IP_ADDRESS>.
See commit 4aeae9b1621969fd97c7d392eab2da2ec7755ab3.

Thanks for fixing 👍


Send event to DD on merged PR

What does this PR do?
Send event to DD on merged PR, including context from the QA description and qa labels
Motivation
Allow monitoring QA practices adoption
Describe how to test/QA your changes
You can try it locally with:

a merged PR with no qa labels nor description

inv -e github.pr-merge-dd-event-sender -d -p 30194

a not yet merged PR (this one)

inv -e github.pr-merge-dd-event-sender -d -p 30627

a merged PR with qa label and qa description

inv -e github.pr-merge-dd-event-sender -d -p 30208

Possible Drawbacks / Trade-offs
Additional Notes

Will merge on Monday to avoid bad surprises during the long weekend

/merge


openjdk8: 8u122-04 -> 8u121-13

Motivation for this change
OK, so this is an odd one in terms of versioning :)

8u121-13 is newer code than 8u122-04
8u122 does not exist anymore
8u122-04 was a preview tag, I am unsure we should use those in the first place
This build is now on par with the release Oracle published for Java SE 8 this week

Things done

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

[X] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

O.o

Should we backport this too?

Probably, yes.


mqtt listener crashes after many 600 byte messages

this is a regression from 0.14.2
environment

ubuntu 16.04, smp
erlang/otp 18.3 and erlang/otp 19

scenario

a python (paho) script attempts to publish 1000s of mqtt messages with body length of 500 bytes to unique topics over a single connection
after a thousand or so messages, vernemq generates a crash log and closes the connection. the script detects the close, reconnects, and continues sending
this happens with retained and not-retained messages

sample crash log
2016-12-06 15:29:05 =CRASH REPORT====
  crasher:
    initial call: vmq_ranch:init/4
    pid: <0.463.0>
    registered_name: []
    exception error: {{badmatch,<<0,79,99,47,49,53,56,98,54,51,55,53,45,100,51,52,48,45,53,98,54,52,45,57,48,55,55,45,99,55,48,55,54,51,50,100,54,57,99,52,47,108,111,99,47,54,101,53,54,102,49,100,56,45,57,98,102,102,45,53,97,97,55,45,97,51,54,51,45,56,98,52,51,51,48,51,52,55,99,57,49,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46>>},[{vmq_parser,parse,4,[{file,"/home/walrus/src/vernemq/_build/default/lib/vmq_commons/src/vmq_parser.erl"},{line,68}]},{vmq_mqtt_fsm,data_in,3,[{file,"/home/walrus/src/vernemq/_build/default/lib/vmq_server/src/vmq_mqtt_fsm.erl"},{line,129}]},{vmq_ranch,handle_message,2,[{file,"/home/walrus/src/vernemq/_build/default/lib/vmq_server/src/vmq_ranch.erl"},{line,161}]},{vmq_ranch,loop_,1,[{file,"/home/walrus/src/vernemq/_build/default/lib/vmq_server/src/vmq_ranch.erl"},{line,104}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]}
    ancestors: [<0.314.0>,<0.313.0>,ranch_sup,<0.182.0>]
    messages: []
    links: [<0.314.0>,#Port<0.4683>]
    dictionary: [{socket_open,<<>>},{max_msg_size,0},{rand_seed,{#{max =><PHONE_NUMBER>51711743,next => #Fun<rand.8.41921595>,type => exsplus,uniform => #Fun<rand.9.41921595>,uniform_n => #Fun<rand.10.41921595>},[71743633123403324|144425778866035504]}},{bytes_received,<<>>},{mqtt_connect_received,<<>>},{mqtt_publish_received,<<>>},{bytes_sent,<<>>},{guid,{{'VerneMQ@<IP_ADDRESS>',<0.463.0>,{1481,66945,24809}},4}}]
    trap_exit: true
    status: running
    heap_size: 1598
    stack_size: 27
    reductions: 2786
  neighbours:
2016-12-06 15:29:05 =ERROR REPORT====
Ranch listener {{127,0,0,1},1883} had connection process started with vmq_ranch:start_link/4 at <0.463.0> exit with reason: {badmatch,<<0,79,99,47,49,53,56,98,54,51,55,53,45,100,51,52,48,45,53,98,54,52,45,57,48,55,55,45,99,55,48,55,54,51,50,100,54,57,99,52,47,108,111,99,47,54,101,53,54,102,49,100,56,45,57,98,102,102,45,53,97,97,55,45,97,51,54,51,45,56,98,52,51,51,48,51,52,55,99,57,49,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46,46>>}```

Thanks for reporting this @waliferus!
We'll try to see what happens here. The parser seems to be confused and expect 'more' input from a binary.

Hi @waliferus, @ioolkos ' analysis is spot on - we are working on a fix.

Hi guys,
We are having the same issue with big files.
pwgen 200000 test
mosquitto_pub -u username -P password -h <IP_ADDRESS> -p 1883 -t test/test -f test

then most of the time we get this crash on vmq_parser
2016-12-07 14:33:42.174 [debug] <0.19691.0>@vmq_queue:state_change:847 [<0.19691.0>] transition from offline --> online because of add_session
2016-12-07 14:33:42.177 [error] <0.19688.0> CRASH REPORT Process <0.19688.0> with 0 neighbours crashed with reason: no match of right hand value <<0,12,47,100,101,118,105,99,101,47,116,111,116,111,117,101,116,51,110,101,101,112,51,67,111,104,48,72,117,67,104,105,101,120,55,112,104,111,98,111,104,104,105,101,104,101,117,106,101,99,104,105,111,115,52,108,111,104,53,118,111,104,99,104,97,105,52,106,111,117,103,97,105,55,105,101,90,101,105,52,98,105,105,116,111,111,48,78,97,101,55,97,101,80,101,53,102,97,112,104,97,104,68,97,116,104,111,111,51,116,101,105,107,101,101,75,97,104,99,97,105,109,53,103,97,101,103,104,97,101,56,111,111,106,111,...>> in vmq_parser:parse/4 line 68
2016-12-07 14:33:42.179 [error] <0.19688.0> Ranch listener {{0,0,0,0},1883} terminated with reason: {badmatch,<<0,12,47,100,101,118,105,99,101,47,116,111,116,111,117,101,116,51,110,101,101,112,51,67,111,104,48,72,117,67,104,105,101,120,55,112,104,111,98,111,104,104,105,101,104,101,117,106,101,99,104,105,111,115,52,108,111,104,53,118,111,104,99,104,97,105,52,106,111,117,103,97,105,55,105,101,90,101,105,52,98,105,105,116,111,111,48,78,97,101,55,97,101,80,101,53,102,97,112,104,97,104,68,97,116,104,111,111,51,116,101,105,107,101,101,75,97,104,99,97,105,109,53,103,97,101,103,104,97,101,56,111,...>>}
2016-12-07 14:33:43.239 [debug] <0.19695.0>@vmq_queue:state_change:847 [<0.19695.0>] transition from offline --> online because of add_session

Please let me know if I can help you!

Thanks @wayglem, looking at the data and place the crash occurs, it seems safe to say it's the same edge case as the one @waliferus is running into. Hopefully we'll have the fixed merged later today.

The's a new nightly build available with the fix over on our download page: http://vernemq.com/downloads/.
Also, don't hesitate to get in touch with us over Slack http://slack-invite.vernemq.com/ or IRC! :)


docs(zh): Update translation of core-concepts/index

packages/docs/zh/core-concepts/index.md
更新翻译同步英文文档现版本，个人经验不足，72行需要一些review
Update the docs/zh translation to latest. May need review at line 72 due to my experience.
packages/docs/core-concepts/index.md
In the process of translating I found a bug, the line 71 was added after line 73 while the SSR link is remained. Has moved it forward and cancelled the latter one on line 73.

packages/docs/core-concepts/index.md
In the process of translating I found a bug, the line 71 was added after line 73 while the SSR link is remained. Has moved it >forward and cancelled the latter one on line 73.
This is now causing conflict, should I submit it in a seperate PR as it's issue of EN docs?


ZONNSmart TRV fix and improvements

This PR does the following :

FIx OnOff clusters when you have multiple TRV (only the last one added was working)
Use updates() for the ZONNSMARTManufCluster attributes
Fix local_temperature_calibration read back from the TRV
Implement the holiday_start_stop attribute
Implement scheduling support in the ZONNSMARTManufCluster
Enable time setting on the TRV

Scheduling details :
Schedules can be read from the schedule_ attributes. They cannot be queried from the TRV directly, you must first use the Online button to force the TRV to send the values or set the schedule using the schedule_set attribute. Until you do so, the schedules will appear empty.
The default schedule for a day on my TRV is the following :
06:00/17.0 12:00/21.0 14:00/17.0 17:00/21.0 24:00/17.0
The temperature will vary in the following way :

00:00 -> 06:00 : 17C
06:00 -> 12:00 : 21C
12:00 -> 14:00 : 17C
14:00 -> 17:00 : 21C
17:00 -> 24:00 : 17C

You can set the schedule for a single day or multiple day with the following syntax :
<day> <period> <period> ...
For example, writing the value mon 09:00/17 21:00/21.5 24:00/17 to the schedule_set attribute will set the temperature in the morning and evening to 17C and 21.5C between 9AM and 9PM.
day can be any off mon, tue, wed, thu, fri, sat, sun, mon-fri, sat-sun, mon-sun. The last 3 will set the schedule for multiple days at once.
Holiday start - stop :
The holiday_start_stop will not be populated until you use the Online button.
The syntax is the following : 2022/12/01 01:01 | 2022/12/31 12:00.
In the above example the whole month of December 2022 will be set as holiday and the TRV will switch automatically to the holiday temperature set in the holiday_temperature attribute.
Once the end date is reached, it will switch back to the scheduled/auto mode.

Codecov Report
Base: 82.68% // Head: 82.38% // Decreases project coverage by -0.29% :warning:

Coverage data is based on head (bf7439f) compared to base (59c098d).
Patch coverage: 26.78% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##              dev    #1961      +/-   ##
==========================================
- Coverage   82.68%   82.38%   -0.30%
==========================================
  Files         245      248       +3
  Lines        7647     7921     +274
==========================================
+ Hits         6323     6526     +203
- Misses       1324     1395      +71

Impacted Files
Coverage Δ

zhaquirks/tuya/ts004f.py
80.64% <ø> (ø)

zhaquirks/tuya/ts0601_trv.py
73.00% <26.78%> (-8.68%)
:arrow_down:

zhaquirks/xiaomi/__init__.py
82.92% <0.00%> (-0.87%)
:arrow_down:

zhaquirks/xbee/xbee3_io.py
100.00% <0.00%> (ø)

zhaquirks/legrand/dimmer.py
100.00% <0.00%> (ø)

zhaquirks/tuya/ts0601_motion.py
100.00% <0.00%> (ø)

zhaquirks/tuya/ts0601_sensor.py
100.00% <0.00%> (ø)

zhaquirks/xiaomi/aqara/motion_agl04.py
67.74% <0.00%> (ø)

zhaquirks/xiaomi/aqara/feeder_acn001.py
96.52% <0.00%> (ø)

zhaquirks/xbee/types.py
91.48% <0.00%> (ø)

... and 5 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-82 of 112 (26.79%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.8%) to 82.389%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

zhaquirks/tuya/ts0601_trv.py
30
112
26.79%

Totals

Change from base Build<PHONE_NUMBER>:
-0.8%

Covered Lines:
6526

Relevant Lines:
7921

💛  - Coveralls

tuya TRV schedule is one large mess and i think all different types is using different implementing of it so its not possible making one nice GUI in ZHA for all TRV.
Great work done !!

Can you help me understand how this works? I do understand how the shedule is formated, but I don't understand where to write it. I found the ZONNSMARTManufCluster but there's no schedule attribute there.

Have you applied this PR to your installation ?  If so you should have "shedule_set" attribute in the ZONNSMARTManufCluster.

I don't know how to do this (sorry, I'm a newbe). Can you please explain?

https://community.home-assistant.io/t/how-to-setup-local-zha-quirks/341226
Copy the patched ts0601_trv.py  in zustom_zha_quirks and restart.

Would someone be able to review this please ?
@dmulcahey or @Adminiuga maybe ?

@javicalle this look good to you?

The whole implementation of TRVs is not familiar to me, and to me it's a huge monster that I hope I don't have to deal with.
I was going to argue against the implementation of the OnOff clusters but I see that it is consistent with the rest of the code so it would be fine to me.
As for the rest, it seems to me that the general 'disorder' of the TRVs is increasing, but I don't have a better proposal (or time available).

@dmulcahey please ?

Can you rebase this? (So newer tests run)

Hmm, the OnOff stuff is definitely hacky, but that's already in at the moment and I guess it's one of the few ways of doing it with the current quirks/ZHA implementation.
Fixing it so that it actually works with multiple TRVs is a needed improvement.
This PR looks like it will conflict with:

https://github.com/zigpy/zha-device-handlers/pull/1192

but that PR seems somewhat stale anyways and it seems like @jacekk015 made a custom repo for TRV quirks: https://github.com/jacekk015/zha_quirks
These already seem to contain some fixes (i. e. the OnOff stuff for multiple devices if I'm not mistaken).
Obviously, it would be best to also get these in officially eventually.
@jacekk015 If you have a minute, do you have any opinions on this PR?
Nothing overly wrong sticks out to me in the added schedule stuff, but it's quite a bit of code. In general, the TRV implementation seems to be quite cluttered and should probably be split up eventually.
@gmsoft-tuxicoman I assume these changes still work correctly?

@TheJulianJES Yes, it still works. I have 14 of those TRVs and I have no issue at all.

Keep so many different TRVs under one file is madness - in my opinion.
Since my quirks didn't complete tests I've abandoned any hope for any official PR.
I've taken quirks code in the state they were and extended/corrected them to users need.
Newest quirks were written according to my simplest approach, but older ones weren't rewritten since they just work.
For quirk rewrite you need to have a user that will test it - otherwise that's just a waste of time.
When user gets a working quirk he is loosing any free time to spare, mostly.
So you will end up with you quirk rewritten on the disk or Github cloud... waiting.
Don't have so much spare time to waste.
I've started to check if TuyaNewManufCluster is usable for TRV's but that's a switch from Attributes to DP's
For now I didn't touch it.
OnOff is a hack, but you can't even set a name/description for OnOff, so when user get two switches without a proper name they are lost already.
So again, it is like it is.
Looking at the latest quirk created
https://github.com/jacekk015/zha_quirks/blob/main/ts0601_trv_etop.py
you have to write over 300 lines of code to make it supported somehow.
I didn't find any TRV quirk example created form top to bottom using newest, proper, approach.
Most of them are glued together pieces of code found in different places.
Will that change? I don't think so - latest 2 years[winters] showed me that the code 'disorder' exist till today.

@javicalle is trying getting one better way getting ZHA climate being matched from device class and attribute so not updating climate component then adding one new device is the quirk. If its working its easy making tuyaTRV1 tuyaTRV2 and yo in and in ZHA climate and the quirk is setting the name and attribute and ZHA is loading the right patches for the device.
I have the first PRed TRV and its badly working at all with ZHAs quirk and with the extended its have all in but is being broken 2 time in the year then its not on the master.
Rewriting all TRV to good working code is possible but its need time from devs and users that can doing all the testing and in the long run is very needed.
I think we need work being done in ZHA for making its easier and better integrating this devices in ZHA like functions for temperature calibrating and switches with fix function like open window and valve detect but it can being possible doing but its needs more testing and help from the "ZHA" side and not only saying its not possible.
So if the ZHA climate can matching functions we can doing it with all other 2 in one clean easy way.
Knowledge i knowing have but not the interest fixing it in some places is not there.
Pleas dont do one "deCONZ" (self killing) of ZHA by doing it worse, try doing it best and we can doing it (we have nearly all tuya TRVs working with extended functions and its bad for many users must installing code they cant maintaining).

If I understand correctly what @MattWestb is saying, we probably need ZHA to have better API for TRVs.
I do agree with that, right now there is no proper way to implement a TRV unless you use those hacks.
The way forward is probably to get a better API for the TRVs and then migrate each model to this new API.
Until then, I don't see a better solution than using the hacky code as it is.

@javicalle After looking some more at this code and how it's handled in HA, I've found the proper way to deal with all those OnOff clusters.
I've removed all that cruft and created a corresponding HA PR : https://github.com/home-assistant/core/pull/87546
I guess those should be merged at around the same time or at least the HA one first so that users have some time to update their code.

If possible, it would be nice if you could implement some (basic) tests

I'm working on unit tests. It appears that recent changes in tuya clusters broke this PR so I need to fix it too.

Codecov seems broken or disabled. I've added unit test but it didn't catch those :(
Can someone please do a manual review (or fix codecov) ?

Hi, is it possible to test this by using only the zha quirk? I'm asking since you've made some changes to home assistant core as well, and I'm wondering if it works alone now?

Hey @puddly can you rerunning the test then it was not working after last fixes and its being great if we can getting this working on ZHA so we can using the same principes for other devices.
Thanks in advance !!

I rebased, it should help for the tests.

From looking at this we need to add more negative tests, since those code branches are not covered in codecov.

There is another issue, you cannot set temperature greater than 25.5, because you multiply them by 10, and then treat them as uint8_t, so you can fit 255 value as max.
Here is what happens if I try to set 26 degress in schedule:
2023-05-07 13:35:39.088 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139659890865680] 260 is not an unsigned 8 bit integer
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 199, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1849, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1889, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 874, in admin_handler
    await result
  File "/usr/src/homeassistant/homeassistant/components/zha/websocket_api.py", line 1297, in set_zigbee_cluster_attributes
    response = await zha_device.write_zigbee_attribute(
  File "/usr/src/homeassistant/homeassistant/components/zha/core/device.py", line 748, in write_zigbee_attribute
    response = await cluster.write_attributes(
  File "/usr/local/lib/python3.10/site-packages/zhaquirks/tuya/__init__.py", line 519, in write_attributes
    await super().command(
  File "/usr/local/lib/python3.10/site-packages/zigpy/quirks/__init__.py", line 200, in command
    return await self.request(
  File "/usr/local/lib/python3.10/site-packages/zigpy/zcl/__init__.py", line 311, in request
    hdr, request = self._create_request(
  File "/usr/local/lib/python3.10/site-packages/zigpy/zcl/__init__.py", line 273, in _create_request
    request.serialize()  # Throw an error before generating a new TSN
  File "/usr/local/lib/python3.10/site-packages/zigpy/types/struct.py", line 257, in serialize
    chunks.append(value.serialize())
  File "/usr/local/lib/python3.10/site-packages/zigpy/types/struct.py", line 257, in serialize
    chunks.append(value.serialize())
  File "/usr/local/lib/python3.10/site-packages/zhaquirks/tuya/__init__.py", line 271, in serialize
    return b"".join([self._item_type(i).serialize() for i in self[:]])
  File "/usr/local/lib/python3.10/site-packages/zhaquirks/tuya/__init__.py", line 271, in <listcomp>
    return b"".join([self._item_type(i).serialize() for i in self[:]])
  File "/usr/local/lib/python3.10/site-packages/zigpy/types/basic.py", line 94, in __new__
    raise ValueError(
ValueError: 260 is not an unsigned 8 bit integer

@Mikaka27 thanks for the patch and reporting the 26C issue. I think I know how to fix it. I'll update the PR shortly.

I looked at this PR and the HA PR and they mostly seem to be fine.  I've added some comments in the HA PR.
For this PR, it would be nice (although not required I guess) if tests would cover the cases where a ValueError is thrown.
The complete PR is a bit hard to fully review, as I don't completely understand Tuya's protocol. But again, it seems to be fine.
IMO, if the last comments are addressed, we could try to move this forward for HA 2023.11.0. (2023.10.0b0 is out already and since this is a breaking change, we can't and shouldn't add this in the beta phase.)
We need to make sure to list this as a breaking change for the zha-quirks dependency bump at some point then.

Since the quirk ID stuff for the ZHA PR hasn't made it into HA yet, I don't see how this can make 2023.11.0. (2023.11.0 beta already releases tomorrow)
Hopefully, the "quirk ID" implementation is ready before 2023.12.0, so we can get it into that release.

Btw., these two review comments are still valid IMO:

https://github.com/zigpy/zha-device-handlers/pull/1961#discussion_r1342130757
https://github.com/zigpy/zha-device-handlers/pull/1961#issuecomment-1737942490 (cover last remaining lines in tests)

This should be good to go again. I've added the quirk ID for the zonnsmart TRV and also fixed state_change function when no value is cached.

@TheJulianJES could you please review this ? it should fairly quick, not much changed since your last review :)
Thanks !

We'll try to target this for HA 2024.3.0. Merge this soon, do the quirks bump in the next few weeks and then the corresponding HA PR can be rebased.

Also, it might be worth rebasing this once more (or merging changes from the current branch) to re-trigger CI with the latest zigpy version, as TSN handling changed there slightly, so the tests might need to be slightly adjusted.
Similar to:

https://github.com/zigpy/zha-device-handlers/pull/2885

Also linking this comment regarding quirks v2 and "exposing entities in quirks" here:
https://github.com/home-assistant/core/pull/87546#issuecomment-1955688910

https://github.com/zigpy/zigpy/pull/1353 was merged, hopefully the tests will work once current head will be used in this repo.


Use record to get with keyword.

This PR modifies the SubmissionOptions class to be a record class, allowing other code to use the with keyword to modify instances of the class on a field-by-field basis. The existing With method can then be refactored to use the with keyword.

Any updates on this?


No card component

I just noticed that there is not card component. Are there existing components you would recommend in its place? Do you think a card component should be added? I'm just now trying things out. Please close this issue if you don't think its relevant. Thanks

I see now. I should use the box component. I'll close this.

Yes, for example Blank Slate is just content inside a box: https://primer-live.org/blankslate#combined-in-a-box

Great stuff, Arthur. I'll be using PrimerLive for the GUI's I develop for my BPM project. Thanks!


neomutt: add patch for CVE-2021-32055

Motivation for this change
https://nvd.nist.gov/vuln/detail/CVE-2021-32055
#124656
No upstream release for this issue yet, though they have merged the fix.
Things done

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

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

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

Fetchpatch is missing from inputs.

Result of nixpkgs-review pr 124960 at edcde75b run on x86_64-linux 1

1 package built successfully:

neomutt

1 suggestion:

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/applications/networking/mailreaders/neomutt/default.nix:18:5:
   |
18 |     (fetchpatch {
   |     ^

Ported to 20.09 as 7f3a9bf6ddc5d13f758287652a6e74b984a31df6.


UI Experiment & Prototype

Howdy 👋🏻,
As what we've discussed on #1, there could be many different UIs approach to display the resulting repos. Here I make this issue to discuss specifically on every experiment that we'll make, and decide which one is best.
So @dberget, do you want to start with the mockup that @markerikson has made, and evolve from that? Also, the card-like UI.. 😀
But if anyone has any idea and has some chance to make it through code, don't be hesitant to send PR and reference the PR here.
Thank you! 🙏🏻

Sounds good @wilbertliu, I'll mockup some different things to get us started!

I'll submit a proper PR tonight but wanted to post a screenshot to get any initial feedback on the card layout.
A few "designers" caveats:

I didn't do anything really with the left hand navbar yet so ignore that.

I could probably spend 8 hours bumping the top sort bar stuff around if i'm not careful so i'm just going to post it. I feel like it has too many icons and the spacing is a little weird at the moment.

Generally speaking it would probably be good to add some color?

Any other thoughts? All feedback welcome, i'm not a professional at this. :)

Hey @dberget 👋🏻😀,
Thank you for the early screenshot. I really encourage anyone to share often (and you've demonstrated it in a good way 👍🏻), so we could have a nice feedback-loop that will benefit ourselves in the long run (e.g not getting burnout, not feeling lonely, and any other mental health things).
So let me start by answering your thoughts and questions.

I feel like it has too many icons and the spacing is a little weird at the moment.

In short yes. I've just discussed few things about this as well on #1.

Generally speaking it would probably be good to add some color?

I feel the same! But first of all, I think it's good to put the purple color of Redux as our primary color. Of course this one is a good reference if you want to take a look. Based on our primary color, there are many ways to create a color palette. One of them is to see the catalog of design based on the hex color. When we found something that sticks to us, you can download its color palette on the detail page. For example this one, there's a color palette that can be downloaded on the right side. Hope that helps. 😀
Last but not least, let me shoot some thoughts :

Please see #1 because I highlighted some of our features that might be added or removed.
I think there shouldn't be a Submit link for now because there's no discussion about it on #1 yet. At least not at the moment. But About is okay though, just a minor addition that could be linked to our GitHub repo if we want to.
I think the grey colored box in the middle should expand until the rightmost side, unless you have planned something to be put on the right side.
I assume you hear me on number 3, I think it's better to widen the space between cards, so people could digest the information in a better way. Because then, too tight in spacing is disturbing, that's why we should design the whitespace as well.
The date inside the card is quite confusing I think. People don't know what's the intention of that date. Whether it's a creation date, update date, etc. I suggest to add some label or something if possible.

Alright, I think that's all.
Let me know what you think! 😀🙏🏻

Appreciate the feedback @wilbertliu, it also sounds very reasonable to me, I will update accordingly in #4!

Couple of things about the main/index page. I currently haven't done much with it from a design standpoint and I think we should discuss some things on it first.

In my opinion the categories seem to be better suited for a straightforward list layout. Quicker to skim down the list this way to get to a category. For the sake of consistency though it might be worth to just use the same card layout, so open to everybody's thoughts.
Beyond showing the sub-topics i'm not sure what else would else be useful to display. The subtopics could link directly to its location.
Since we're displaying the entire list, and also the search bar, it seems unnecessary to have the left-nav dropdown's on this page, also the sort options don't do anything on this page so i'm thinking we should not have the sort-by options here.

Here is a very early mockup of the items with the subtopics, on one hand it feels like a lot of info but it also seems nice to have the direct navigation to a subtopic available like that. Maybe could do a hover state to display sub topics if we want.
Anyway, open to thoughts! 😄

Hello @dberget 👋🏻,
More or less I thought similarly to what you did above, but my main consideration was the design on #4  will make people do more steps when they want to switch to another subcategory that's not inside the current selected category. Do you know what I mean? 😀 Now the problem with design above is also similar. Though people could choose subcategory directly because the category is listed, people will go back and forth from the result page to this All Categories page just for the sake of changing category / subcategory or seeing the result of repositories.
Being that said, what if we modify the design on #4 to move the sort to the bottom, and put the list of categories at the top by using this pattern? Yes, it's like folder, but you don't have to make it so. Just a clickable list that will expand the subcategories once it's clicked by people. Got some idea? 😉 So no dropdown anymore. Also for Go To Subtopic, I don't think there's benefits on showing that to people. So, that could be removed as well I think?
P.S : Note that the sort options should be checked at the initial state, because we do sort by both of those GitHub stars & NPM downloads. See #1 specifically my latest comment.

Being that said, what if we modify the design on #4 to move the sort to the bottom, and put the list of categories at the top by using this pattern? Yes, it's like folder, but you don't have to make it so. Just a clickable list that will expand the subcategories once it's clicked by people. Got some idea? 😉 So no dropdown anymore. Also for Go To Subtopic, I don't think there's benefits on showing that to people. So, that could be removed as well I think?

I like that pattern a lot and think it makes a lot of sense with this situation, and if we're using that then it makes sense to remove the Go To Subtopic section. i'll get to work on it! :)

Closing this issue for now because we just have the working prototype! 🎉


Does this script run with the hybrid-filled method by default?Thanks!

@madlag

I had the same question. I understand I need to set "attention_pruning_method" : pruning_method and "dense_pruning_method" : pruning_method:1d_alt  for hybrid pruning.  What are the parameters I need to set to do hybrid-filled pruning? @madlag @echarlaix


Port to Android

You know you want it.

Probably gonna do it

Being worked on, got some good ideas on how to make it look

What was done for it to this day : Every actions such as "play", "credits", "exit", "restart" or "sound/music enable" were put on HUD so this is already a great step  for Android port. in-game HUD was also reworked a bit, which might permit to have player's buttons in good positions.
Stay tuned :)


Resize Dax logo in new tab page

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#4608  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nalcalag and the rest of your teammates on  Graphite


Unrecognized field 'pluginDownloadURL' on 'provider.Config'

What happened?
A user is reporting an issue over the runpod/pulumi-runpod-native provider built with pulumi-go-provider, something is failing with 'Unrecognized field pluginDownloadURL'.
Example
(runpod) ➜ pulumi up
Enter your passphrase to unlock config/secrets
    (set PULUMI_CONFIG_PASSPHRASE or PULUMI_CONFIG_PASSPHRASE_FILE to remember):
Enter your passphrase to unlock config/secrets
Previewing update (tmpp):

Downloading plugin: 14.31 MiB / 14.31 MiB [=========================] 100.00% 0s

[resource plugin runpod-0.0.654] installing

     Type                        Name                                                                Plan       Info
 +   pulumi:pulumi:Stack         provider-runpod-native-tmpp                                         create
     └─ pulumi:providers:runpod  default_0_0_654_github_/api.github.com/runpod/pulumi-runpod-native             2 errors

Diagnostics:
  pulumi:providers:runpod (default_0_0_654_github_/api.github.com/runpod/pulumi-runpod-native):
    error: pulumi:providers:runpod resource 'default_0_0_654_github_/api.github.com/runpod/pulumi-runpod-native': property version value {0.0.654} has a problem: Unrecognized field 'version' on 'provider.Config'
    error: pulumi:providers:runpod resource 'default_0_0_654_github_/api.github.com/runpod/pulumi-runpod-native': property pluginDownloadURL value {github://api.github.com/runpod/pulumi-runpod-native} has a problem: Unrecognized field 'pluginDownloadURL' on 'provider.Config'

Output of pulumi about
N/A
Additional context
In the bridged provider we have some special treatment for ignoring pluginDownloadURL and version fields passed two CheckConfig, see the "tolerate pluginDownloadURL":
https://github.com/pulumi/pulumi-terraform-bridge/blob/master/pf/tests/provider_checkconfig_test.go#L448
These fields may be sent by Pulumi CLI even though they are not part of the provider schema, so they're exceptional in some way.
I could not find a pluginDownloadURL reference in this repo so perhaps something is not being handled quite right; cannot exclude the possibility that this is handled in pulumi/pulumi and linked here but the provider maintainers reporting the issue are using an outdated version.
CC @usrbinkat
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Output of pulumi about:
CLI
Version      3.109.0
Go Version   go1.22.0
Go Compiler  gc
Plugins
NAME    VERSION
nodejs  unknown
runpod  0.0.655
Host
OS       darwin
Version  13.4
Arch     arm64
This project is written in nodejs: executable='/Users/pierre_at_runpod/.nvm/versions/node/v18.19.0/bin/node' version='v18.19.0'
Backend
Name           Prabuddhas-Laptop.local
URL            file://~
User           pierre_at_runpod
Organizations
Token type     personal
Dependencies:
NAME                 VERSION
@pierre78181/runpod  0.0.655
@pulumi/pulumi       3.110.0
typescript           4.9.5
@types/node          14.18.63
Pulumi locates its logs in /var/folders/85/25qrq5xd04z8l7gvh_90t6740000gq/T/ by default
warning: Failed to get information about the current stack: No current snapshot

What ended up fixing the issue is one of:

bumping up to the latest version of the pulumi/pulumi-go-provider
adding a version trimmer in the main.go.

trimmedVersion := strings.TrimPrefix(runpod.Version, "v")

Hope pulumi incorporates the version trimmer by default because seems like a general use case.

Ah thanks for following up @pierre818181 , possibly this is fixed in the latest then.

Yea we should definitely revisit the version trimmer.


Fix #6632 support alternative dtype string spellings

As title. Support for alternative ways of spelling dtypes
with strings.
Fixes #6632

@stuartarchibald, in the current state, it would allow the spelling of structured dtype as a str but it will lead to a internal error. Consider this patch (https://github.com/sklam/numba/commit/50ec513442d5bab33500bd662f5b81cc9ee60020) to fix it.

@stuartarchibald, in the current state, it would allow the spelling of structured dtype as a str but it will lead to a internal error. Consider this patch (https://github.com/sklam/numba/commit/50ec513442d5bab33500bd662f5b81cc9ee60020) to fix it.

@stuartarchibald, in the current state, it would allow the spelling of structured dtype as a str but it will lead to a internal error. Consider this patch (sklam@50ec513) to fix it.

Good point, thanks for the patch, I've merged it in.


Updates Generator Model Table composite primary check to check null

I have noticed an issue in propel/propel/src/Propel/Generator/Model/Table.php - involving hasCompositeKey and when a table is missing it, it never makes it to its exception (foreignTable is null).
if ($foreignTable->hasCompositePrimaryKey()) is the check that is the issue in the scenario. I am going to try and send a MR in for it, but its pretty edge - but debugging it required diving as the exception / error was useless to indicate where it happens.
With the notNull assertion check this ensures this does not fail, and allows propel to proceed to the needed exception which results in:
[Propel\Generator\Exception\BuildException] Table "my_table" contains a foreign key to nonexistent table "non_existant_table"
To reproduce create a table with a foreign key to a table that does not exist. The resulting Exception is the failure in the code, not the failure of processing the schema or what the cause may be.

Reviewing deeper I am closing this PR - however a major problem still exists, what happens is that in a large system, with many tables, if a table is removed but its foreign key is not, what you will result with is a debug output that begins at where the problem as occurued.
What this means is when I have the following:
A - Foreign key to C
B
C - foreign key to B
Then:
A - Foreign key to C
B  - {Deleted}
C - foreign key to B
In the debug output, just table C will show - having 'reset the list of tables to process' starting with the table after the issue.
How this is fixed I have not figured out yet, but once you are in a very large database setup it can be difficult to isolate what happened.
(I am moving a large schema over to a new iteration of an application and removed what I thought was an orphaned table - I was wrong, and it caused 2 hours of debugging or more lol)

Fatal error: Uncaught Error: Call to a member function hasCompositePrimaryKey() on null in /var/www/html/vendor/propel/propel/src/Propel/Generator/Model/Table.php on line 791
Is there error that you will receive and it will be ambiguous as to the cause and my solution does not resolve it.

This issue is very strange as it seems to only be affected in WSL2 + Docker on Windows 10.
What I did to verify was build the same project by deleting, pulling, rebuilding.

WSL2 + Ubuntu 18 via /mnt/ - Builds Pass
WSL2 + Docker on Alpine - Build Fail
MacOS + Docker on Alpine - Build Pass

Always complains about hasCompositePrimaryKey and unable to locate the cause 😢

Well this one is insane, but here it is:
https://github.com/docker/for-win/issues/4824
Essentially when crossing the WSL2 bridge you must be mindful of directory permissions as you will receive an exit code 255 as windows will expose the filesystem as 777 permissions, but once WSL2 actually accesses the files on the windows file system the permissions are different and will reject and not provide any reason to you the console.

Thank you for the findings.
Your code change might still be valid in terms of pure PHP.
Since the value can be null we shouldnt blindly check on it causing a fatal error.
Better to throw a meaningful exception for example in that case.


v.1.2.1 not shown

When installing your plugin v.1.2.1 isn't pulled. Latest version is shown as 1.2.0

It was not yet released on NPM. Is out now.

PS: I'm still trying to get the CHANGELOG into Homebridge. Hope to have it at some point. Please note the breaking changes of v1.2.1!

Thank you! I do see the changelogs AFTER installing in CONFIG UI X
On 18 May 2020, 14:44 +0200, Johann Richard<EMAIL_ADDRESS>wrote:

PS: I'm still trying to get the CHANGELOG into Homebridge. Hope to have it at some point. Please note the breaking changes of v1.2.1!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


enhance connector helper notebook to support 2.9

Description
enhance connector helper notebook to support 2.9
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

And model name is mostly unique so it ends up with unique model name with a dedicated model group.

Model group name is unique, but model name not. One model group can have multiple models with same model name.

@ylwu-amzn why do we need to have this when we have Flow framework which exactly does this right now?

@ylwu-amzn why do we need to have this when we have Flow framework which exactly does this right now?

But we don't have flow framework on AWS now, right ? This is to help current AWS cx


Refactor: Identify items using URIs, not itemKeys

For v2 at least, stop using itemKeys to identify items, and use URIs instead.
It might seem that we are already using URIs, and just mapping those to itemKeys after the request comes in as a URI. But this applies only to the top level requests coming into the controller; it doesn't apply to links inside a request body. We have to have some way to resolve those as well.
If it's possible to do this with v1 as well, great. Mostly this will depend on the extent to which existing clients submit request bodies that they originally grabbed from the server, as opposed to constructing the request bodies themselves. If existing clients are grabbing data from the server, modifying it and then resubmitting, then we can get away with applying this to v1 as well. That will require a little research.

No longer relevant now that we have the SDR-based API.


Add config files for models

Allows to provide models in 2 ways:

with the CLI, for very basic parameters, using --model_args only (will allow people to give a quick try to the lib, and the test suite to still work)
with individual model files.

Todos:

[x] Update README
[x] Test the 3 new config files (base/adapters/peft, TGI)

Fix #128

I think it comes from the merge I did this morning, will investigate, ty

Should be good :D


Replace express with native node calls

I updated the old express calls to use the ones provided by the base node framework.
There are two other changes I wanted to suggest as well. If a module is not found an error is thrown which results in a non-graceful shutdown of the process. This in turn results in a generic exception in .NET which does not give any indication of the error that actually occurred within the node process.
throw new Error('The module "' + resolvedPath + '" has no export named "' + bodyJson.exportedFunctionName + '"');

This also applies to the logic used in react-rendering.js. I would propose ensuring that all errors bubble up to the client without causing the process to end unexpectedly i.e. wrapping the logic inside of a try/catch block and sending the error via the http pipeline before ending the process.
I can submit an additional PR if needed.

Hi @gregbty, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

Thanks for this! It's merged.
Regarding your other suggestion about error handling, I just added commit 80575a that hopefully addresses this. Let me know if you think anything further is needed.

That should work. Thanks!


bug: script result limited to 8191 symbols

When I run this script in dev tools,
window.webui.executeDeno(`
              async function saveScene() {
const bit = await firstWindow.script("return 'x'.repeat(10000);");
console.log(bit.length);
} `)

I am expecting to see 10000 in console but unfortunately it shows 8191

Sorry just noticed the solution to pass bufferSize in options
https://github.com/webui-dev/deno-webui/blob/d48f8a3df0ce2185885c778f3d84489b44f84e2b/src/webui.ts#L235
Perhaps its possible to increase or remove default limit?

The default limit is 8 KiB. Custom sizes to reduce or increase the default value can be passed via the options arg.
https://github.com/webui-dev/deno-webui/blob/d48f8a3df0ce2185885c778f3d84489b44f84e2b/src/webui.ts#L225-L230

I think better solution would be to automatically calculate buffer length, currently I have to do manually in two steps:
            const bufferSize = await firstWindow.script('return window.ea.getFiles()["' + fileId + '"].dataURL.length;');
      var fileDataURL = await firstWindow.script('return window.ea.getFiles()["' + fileId + '"].dataURL;', {
              bufferSize: bufferSize + 1,
            });

The issue that I have to re-executed same code twice, it would be better if it can automatically cache first result and then return with correct bufferSize

Enough memory needs to be allocated to hold the response. How should it be calculated before there is a response? The only way would be raising it but it comes with a trade off. 8KiB is enough to hold most responses but it was kept configurable. If a higher limit is needed why not just passing the buffersize arg right away?

I mean something like this
const bufferSize = await firstWindow.script('const result = expensiveComputation(); window.cache = result; return result.length; ');
const result = await firstWindow.script('return cache;', {
              bufferSize: bufferSize + 1,
            });

Though it's not important issue, just an idea

It would be stored in the cache field of the window object. JS has a GC and doesn't need to allocate memory manually like we need in C with the buffer. While this is possible, I think it's not worth the tradeoff in performance to make it the default behavior. Maybe there can be some api that provides this behaviour to spare the boilerplate for users who run into cases like @7flash does.

Or, because webui runs on PCs, why not make the default buffer 1MB or even more?

@ttytm what's the proper way to calculate buffer size of string? just .length might not be right?

@ttytm what's the proper way to calculate buffer size of string? just .length might not be right?

currently doing like this but on other hand it might be over head:
bufferSize *= 4;
bufferSize += 4;

I'm not fully sure. @hassandraga can you tell the correct way for WebUI?

what's the proper way to calculate buffer size of string?

const bufferSize = Buffer.byteLength(str, 'utf-8'); is the right one to get the size of a buffer in bytes, while .length gives the string len. To see the difference, use a Unicode text.
const str = "السلام عليكم"; // Hello in Arabic
console.log(str.length); // 12
console.log(Buffer.byteLength(str, 'utf-8')); // 23

what's the proper way to calculate buffer size of string?

const bufferSize = Buffer.byteLength(str, 'utf-8'); is the right one to get the size of a buffer in bytes, while .length gives the string len. To see the difference, use a Unicode text.
const str = "السلام عليكم"; // Hello in Arabic
console.log(str.length); // 12
console.log(Buffer.byteLength(str, 'utf-8')); // 23

Uhm but Buffer is not available in browser and that's whole point to measure it in browser

That's true. But the example was just to show the difference between characters length, and bytes length. However  in the browser you can encode the string, then get length, which will give the bytes length, and that what we used in WebUI Bridge.
new TextEncoder().encode(str).length

That's true. But the example was just to show the difference between characters length, and bytes length. However in the browser you can encode the string, then get length, which will give the bytes length, and that what we used in WebUI Bridge.
new TextEncoder().encode(str).length

Unfortunately that's expensive operation which does not work with long strings as shown in https://github.com/webui-dev/webui/issues/270 and later fixed with chunking in https://github.com/webui-dev/webui/pull/271 but it would be too expensive I think just to calculate bytes length, and rather I will just reserve a bit more bytes, do you think it will always work just to multiple str len by two?


Deploy a single Camunda Form (without the bpmn diagram)

Is your feature request related to a problem? Please describe.
As a developer I want to test my form. In the user task I use reference binding latest for my form.
After some change in the modeler I want to check the form in the task list. To get the form deployed, I either have to use a different tool like curl, postman or Camunda Cockpit (EE) or deploy the process diagram and include the form in the deployment.
Describe the solution you'd like
The Camunda Form can be deployed directly from the modeler. Same as to deploy process diagrams or decision diagrams.
Describe alternatives you've considered
Deploying with another tool, but this is poor developer experience.
Additional context
See https://jira.camunda.com/browse/CAM-14004.

This will only be possible for Platform forms, at the moment. To my knowledge, Cloud isn't prepared to deploy forms - it doesn't allow so in the web modeler


HTTP 503 should be dispatched in case the circuit is broken

I'm using Spring Cloud Gateway 2.1.2.RELEASE ( Greenwich.SR2 ) along with a Hystrix Filter and I'm running a series of unit tests in order to verify the behavior of the circuit breaker mechanism.
In case the back-end system does not respond in time (see the property: execution.isolation.thread.timeoutInMilliseconds), then the HTTP status dispatched by the Gateway is 504 (as expected).
In case multiple errors of this kind occur, then the circuit is broken (also as expected) but the HTTP status dispatched by the Gateway is 500 (while one would expect 503).
Is there any configuration we are missing here?

I think this is a tricky situation as to what the right status code should be.  I can see a 503 indicating that the downstream service being unavailable, however I could see it also meaning the gateway itself if unavailable.

Thank you @ryanjbaxter for the prompt response!
Let me also add to the discussion that there is nothing wrong with the Gateway itself; it's just one route (out of dozen registered ones) which received multiple timeout errors from a single back-end service.
A response with HTTP 500 should prevent the original service consumer from retrying, while a response with HTTP 503 should indicate that a retry is feasible after a while.
On a side note, are you aware whether HTTP 500 is coming straight from Hystrix or is that how the Gateway interprets the com.netflix.hystrix.exception.HystrixRuntimeException ?

I understand, my gut says we should return a 503 but I want to hear what my teammates think as well.

On a side note, are you aware whether HTTP 500 is coming straight from Hystrix or is that how the Gateway interprets the com.netflix.hystrix.exception.HystrixRuntimeException ?

Not off the top of my head

If it helps, below you may find the stacktrace:
Daemon Thread [HystrixTimer-1] (Suspended (breakpoint at line 39 in HystrixRuntimeException))
	HystrixRuntimeException.<init>(FailureType, Class<HystrixInvokable>, String, Exception, Throwable) line: 39
	HystrixGatewayFilterFactory$RouteHystrixCommand(AbstractCommand<R>).handleFallbackDisabledByEmittingError(Exception, FailureType, String) line: 1052
	HystrixGatewayFilterFactory$RouteHystrixCommand(AbstractCommand<R>).getFallbackOrThrowException(AbstractCommand<R>, HystrixEventType, FailureType, String, Exception) line: 878
	HystrixGatewayFilterFactory$RouteHystrixCommand(AbstractCommand<R>).handleTimeoutViaFallback() line: 997
	AbstractCommand<R>.access$500(AbstractCommand) line: 60
	AbstractCommand$12.call(Throwable) line: 609
	AbstractCommand$12.call(Object) line: 601
	OperatorOnErrorResumeNextViaFunction$4.onError(Throwable) line: 140
	OnSubscribeDoOnEach$DoOnEachSubscriber<T>.onError(Throwable) line: 87
	OnSubscribeDoOnEach$DoOnEachSubscriber<T>.onError(Throwable) line: 87
	AbstractCommand$HystrixObservableTimeoutOperator$1.run() line: 1142
	HystrixContextRunnable$1.call() line: 41
	HystrixContextRunnable$1.call() line: 37
	HystrixContextRunnable.run() line: 57
	AbstractCommand$HystrixObservableTimeoutOperator$2.tick() line: 1159
	HystrixTimer$1.run() line: 99
	Executors$RunnableAdapter<T>.call() line: 511
	ScheduledThreadPoolExecutor$ScheduledFutureTask<V>(FutureTask<V>).runAndReset() line: 308
	ScheduledThreadPoolExecutor$ScheduledFutureTask<V>.access$301(ScheduledThreadPoolExecutor$ScheduledFutureTask) line: 180
	ScheduledThreadPoolExecutor$ScheduledFutureTask<V>.run() line: 294
	ScheduledThreadPoolExecutor(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1149
	ThreadPoolExecutor$Worker.run() line: 624
	Thread.run() line: 748

Note: I'm using the latest version of Hystrix (i.e. 1.5.18).

Thanks, first I want others to chime in on whether returning a 503 is right.
@spencergibb @TYsewyn @OlgaMaciaszek any thoughts?

IMO it does make sense to return 503 in such cases, and AFAIK we have the failure type SHORT_CIRCUITED for that.
That new exception would indeed look like the TimeoutException.
Thumbs up from me! 👍

There's already a switch to determine if it is short-circuited where a 503 could be returned.

PRs welcome

@spencergibb, @ryanjbaxter : PR created ( https://github.com/spring-cloud/spring-cloud-gateway/pull/1230 )


Provide an ordering to transaction visitors

Pass a monotonically-increasing sequence number to each transaction
visitor.  This will provide a way to sequence read-write ExecuteSql()
calls.  See ExecuteSqlRequest.seqno for more details.
Fixes #279.

This change is

I'm not clear on whether 0 is a valid sequence number or if they should start at 1. The java implementation starts at 1.

FWIW, I originally started at 1, and then went to INT64_MIN, and then to 0.  But I'm happy with 1.
Done.


build(docker): upgrade base ubi image to latest

build(docker): upgrade base ubi image to latest version (ubi9/ubi:9.4-947).
build(cmvfs): upgrade cvmfs binaries to latest version (2.11.3).

Combined with upgrading to latest version of go + library dependencies this reduces the number of vulnerabilities reported from trivy by 95 (195 total remaining). To tackle this further would require likely require running in a distroless image which feels like a large piece of work to plan for.

LGTM.


kill container on network config error

Closes #192.

With this change, should the proxy still kill the container if weave attach fails? Seems a bit belt-and-braces, but could catch other errors.

should the proxy still kill the container if weave attach fails?

You may want to read the code and/or commit message ;)

Ah _or_die is not used in attach.


unable to create Ingress on RKE2

Rancher Server Setup

Rancher version: 2.6.3
Installation option (Docker install/Helm Chart): docker
Proxy/Cert Details: self signed certificate and self signed CA certificate

Information about the Cluster

Kubernetes version: v1.21.8+rke2r2
Cluster Type (Local/Downstream): local

User Information

What is the role of the user logged in? Admin

Describe the bug
Unable to create a simple ingress
To Reproduce
install rancher in docker (image: rancher/rancher:latest).
Create RKE2 cluster and add nodes.
Install e.g. kubernetes dashboard with
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.4.0/aio/deploy/recommended.yaml
create a simple ingress in the kubernetes-dashboard namespace for the kubernetes-dashboard service
Result
error message:
Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://rke2-ingress-nginx-controller-admission.kube-system.svc:443/networking/v1/ingresses?timeout=10s": x509: certificate is valid for dockervm.mshome.net, not rke2-ingress-nginx-controller-admission.kube-system.svc
Expected Result
no error message and a new ingress being created
Screenshots

confirmed that this is an issue on v2.6.5-rc5.
you can also reproduce this by:

deploy a load balancer with a workload on a rke2 cluster

this was incorrectly reopened by myself -- we are able to create ingress using v2.6.5-rc5 on both rke1 and rke2 clusters.

hi @Torkolis, your issue is likely caused by the misconfiguration of the Niginx Ingress Controller. I do not have a solution right now, but recommend you to check both RKE2 documentation  and Nginx upstream repo for more information:

https://docs.rke2.io/networking/#nginx-ingress-controller
https://github.com/kubernetes/ingress-nginx/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc

I didn't change any configurations, everything was installed as default. Why is it misconfigured? Who is responsible for the default configuration? I thought because it is a rancher image it would be fitting to open the issue here so the default configuration can be fixed.


Failed Fetches with an ok of false still creates a file but corrupted

react-native: 0.74.5
react-native-file-access: 3.1.0
Platform:  both
Bug
When I fetch an asset with FileSystem.fetch and the request fails for some reason, such as 403, 404, then the asset is still downloaded and saved
To reproduce
Try out this sample that download an image with unanavailable url:
import * as RNFA from 'react-native-file-access';
import {Button, StyleSheet, View} from 'react-native';

const url =
  'https://buffer.com/library/content/images/size/w1200/2023/10/freimages.jpg';

function App(): React.JSX.Element {
  return (
    <View style={styles.screen}>
      <Button
        title="press me"
        onPress={async () => {
          const path = `${RNFA.Dirs.DocumentDir}/test.png`;
          console.log('path', path);
          const res = await RNFA.FileSystem.fetch(url, {path: path});
          console.log('res', res);
          const exists = await RNFA.FileSystem.exists(path);
          console.log('exists', exists);
        }}
      />
    </View>
  );
}

const styles = StyleSheet.create({
  screen: {
    flex: 1,
    backgroundColor: '#fff',
    alignItems: 'center',
    justifyContent: 'center',
  },
});

export default App;

You will notice that the response is 404 not found but the file is still created with the path. Why would a failed fetch create a file?

The reason for still creating the file is with, for example, a JSON api, the returned blob on 404 (or other 4xx and 5xx errors) may still have relevant information (like an error message to display in app).  I cannot think of a way to automatically determine if this library should discard completed server responses, even when not 2xx OK replies.

doesnt it make more sense to return the response as an error if it fails or some other way?

oh alright got it


information about how to enable dev mode

I think it would be rather helpful for lots of people to add a line to the docs how to enable dev mode when they start from the default svelte or sapper templates. Otherwise they would install this extension an it wouldn't work just because dev: false by default.

Yeah, it took me finding this issue to be aware of dev: true, and then it's barely mentioned in the svelte-loader docs - so I had to scratch my head a bit before understanding that you need to specify it in that loader's options in your Webpack config.
Thanks for this tool!

Why is this issue closed? I don't know where to set dev:true. Where to add dev:true?  That is the question of this issue, and it is not completed @RedHatter

Why is this issue closed? I don't know where to set dev:true. Where to add dev:true? That is the question of this issue, and it is not completed @RedHatter

in compiler options. either in a vite plugin or in svelte.config file


Provide failure notifications on gated BinaryDataNotifications

One of the issues IDA struggles with (in regard to events) is that some of their 'gated' event notifications may fail without notification. BN also seems to suffer from this.
By 'gated' events mean an event callback that happens before a certain piece of information is modified in the database, and an event callback that happens after it is modified.
For example, in BinaryDataNotifications we have:
BEFORE - function_update_requested
AFTER  - function_updated

As a plugin developer, I may want to hook function_update_requested to capture some information prior to this object being modified. My hooks then may change their logic to wait for a function_updated event to come through.
But in failure cases, the function_updated event may never get fired off. As a result, my logic is now stuck in a state waiting for an event that may never come (or recieve a completely different one later).
If these gated events cannot complete, you should send out a notification as such:
FAILURE - function_update_canceled

In slack, rss noted that `this might be worth a ticket, my recollection of that path makes that seem like it wouldn't be hard to add'. Filing this so it doesn't get lost.

We believe this would be best implemented as an analysis pass, #471 which we plan but is not done yet. I'm going to close as a dupe.


Allow to hide instances from the list.

A user reported that it would be nice to remove instances from a group. The motivation is that during an initial setup, maybe there are instances that were used just temporarily to make sure that things are working. And if they requested an update but then don't report back (because they've been deleted), they may show up with an error status.
To avoid that, and other possible use-cases, we should allow a way to hide instances from being considered. Maybe this could be done using a criteria (machine ID, IP, etc.).

Hide Instances UI:
https://www.figma.com/proto/Sz5ZchrZJS0rtTz2KULzii/Nebraska-V4?node-id=1331%3A0&viewport=1490%2C718%2C0.6123372316360474&scaling=min-zoom&page-id=176%3A8

Update the action button location:
https://www.figma.com/proto/Sz5ZchrZJS0rtTz2KULzii/Nebraska-V4?node-id=1350%3A0&viewport=6272%2C560%2C0.6400880217552185&scaling=min-zoom&page-id=176%3A8


More AUR support suggestions

Can provide richer functions for AUR workspace.
1.Provides file type association for .SRCINFO files
2.Provides convenient operation functions, such as updpkgsums command, and graphical buttons for executing makepkg --printsrcinfo > .SRCINFO command to generate .SRCINFO file
3.Provides run options, such as makepkg -si installation, clean workspace, etc.
4.Quickly create an empty AUR package repository with a sample PKGBUILD file
This extension is an excellent idea and needs to be continuously improved.

Thanks @witt-bit for the suggestions.

1.Provides file type association for .SRCINFO files

Opened as separate issue #39.

2.Provides convenient operation functions, such as updpkgsums command, and graphical buttons for executing makepkg --printsrcinfo > .SRCINFO command to generate .SRCINFO file

Opened as separate issue #40.

3.Provides run options, such as makepkg -si installation, clean workspace, etc.

Opened as separate issue #41.

4.Quickly create an empty AUR package repository with a sample PKGBUILD file

I’m already maintaining a Cookiecutter template for that, cookiecutter-pkgbuild.
If you think it makes sense to integrate the Cookiecutter template with the VS Code extension, feel free to open a separate issue. I don’t think it’s a good fit, because VS Code is workspace-/folder oriented, and scaffolding templates generally work best if the workspace root doesn’t exist yet.
A simpler variant of this may be for the extension to contribute a snippet, which can be inserted into an empty PKGBUILD via the Snippets: Insert snippet command.

This extension is an excellent idea and needs to be continuously improved.

Thank you for your honest feedback.
Contributions are always welcome.


Deprecated typings components in quickstart example

We get the following warnings while running the quickstart example at npm install step. [https://angular.io/docs/ts/latest/quickstart.html]
typings WARN deprecated 10/14/2016: "registry:dt/node#6.0.0+20160909174046" is deprecated (updated, replaced or removed)
typings WARN deprecated 10/3/2016: "registry:dt/jasmine#2.2.0+20160621224255" is deprecated (updated, replaced or removed)
typings WARN deprecated 9/14/2016: "registry:dt/core-js#0.0.0+20160725163759" is deprecated (updated, replaced or removed)

In my humble opinion, the typings.json file needs to be updated
{
  "globalDependencies": {
    "core-js": "registry:dt/core-js#0.0.0+20160725163759",
    "jasmine": "registry:dt/jasmine#2.2.0+20160621224255",
    "node": "registry:dt/node#6.0.0+20160909174046"
  }
}

Worry not, they are going away really soon.


RFC: Don't include underline in default toolbar

Underlined text for non-links has been an anti-pattern for more than a decade. The CMS editor is set up to help authors avoid making bad choices (e.g. we don't have font/colour pickers).
In this light, should we remove the underline option from the default toolbar? Sites with a specific need for it can add it back in with config.

Repeating what I had said:
Normally, it's been accepted as bold (html <strong>) to bring to attention and italics (html <em>) for emphasis.
Although having said that, italics have been in contention due to readability and custom font sheets.
Underline has been understood for active links on webpages for a long time

Yes. I've manually removed the option on every site I'm come across, but it would be good for the default tinyMCE config to not include it.

Pointer: Update the properties in TinyMCEConfig I think it's quite straight forward.

@silverstripeux Do you have views on this?
For the record, I agree with disabling the underline option by default. I think it would be safer to remove it in SS5 however as we're technically removing a feature.

Yup, happy to disable the underline option by default.
Related to SS5 TinyMCE improvements: https://github.com/silverstripe/silverstripe-admin/issues/653
Designs:


Creating app with Meteor 1.3 and Angular2 gives 'reflect-metadata shim is required when using class decorators'

I was trying to create a project using Meteor 1.3 and Angular, but I can't get it to work.
The documentation isn't ready for this new stack, I used the descriptions from the README.md from this repo and the angular2-meteor-auto-bootstrap repo.
It's tested with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>This are the steps I followed:
Creating the project
meteor create meteor-1.3-test-2 --release 1.3-rc.2
cd meteor-1.3-test-2/

npm install angular2 --save
npm install https://github.com/Urigo/angular2-meteor --save
npm install https://github.com/Urigo/angular2-meteor-auto-bootstrap --save
npm install<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>--save

meteor remove blaze-html-templates
meteor add angular2-compilers

client/app.ts
import {Component} from 'angular2/core';
//import {bootstrap} from 'angular2/bootstrap';
import {bootstrap} from 'angular2-meteor-auto-bootstrap/bootstrap';

@Component({
    selector: 'socially',
    template: "
Hello World!
"
})
export class Socially {}

bootstrap(Socially);

client/index.html:

        <meta charset="UTF-8">
        <title>meteor 1.3 test</title>

    <socially>Doesn't work jet</socially>

Running the app:
meteor

Console log :
Uncaught reflect-metadata shim is required when using class decorators    -->   modules.js?hash=74bb7a2…:9809

yes, you'll need to import 'reflect-metadata' yourself.
Also change to import {bootstrap} from 'angular2-meteor-auto-bootstrap'.

meteor create meteor-angular2-test --release 1.3-rc.4
cd meteor-angular2-test
npm install https://github.com/Urigo/angular2-meteor --save
npm install https://github.com/Urigo/angular2-meteor-auto-bootstrap --save
meteor remove blaze-html-templates
meteor add angular2-compilers
npm install<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>\
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

  <meta charset="UTF-8">
  <title>meteor 1.3 test</title>

  <socially>Doesn't work jet</socially>

import 'reflect-metadata';
import {bootstrap} from 'angular2-meteor-auto-bootstrap'
import {Component} from 'angular2/core';

@Component({
  selector: 'socially',
  template: `<p>Hello World!</p>`
})
class Socially { }

bootstrap(Socially);

now its Uncaught ReferenceError: Zone is not defined for me :-/

Hi sciausen,
I think you need to install Angular2.
npm install angular2 --save

@masterdude That's the first module I stated in npm install.

@sciausan You are right I missed that.
When I follow your steps on a new project I get the zone error too.
When I upgrade my project using the same dependency versions I stil get the reflect-metadata shim error.
When I changed the order of the imports from this:
import {Component} from 'angular2/core';
import 'reflect-metadata';
import {bootstrap} from 'angular2-meteor-auto-bootstrap';

to this:
import 'reflect-metadata';
import {Component} from 'angular2/core';
import {bootstrap} from 'angular2-meteor-auto-bootstrap';

Then I get the zone error to on my old project too.

To fix that I have an import file in a lib directory with that
import 'moment';
import 'zone.js';
import 'reflect-metadata';
import 'rxjs';

It have to be loaded before any call to angular

@hlehmann But then you are importing the modules on the server too. Which crashes the server. Besides you get this during compilation:

Exported external package typings file 'node_modules/zone.js/dist/zone.js.d.ts' is not a module.

I tried a lib/dependencies.js with
if (Meteor.isClient) {
    require('zone.js');
    require('reflect-metadata');
    require('rxjs');
}

But then I'm stuck with: compiler.ts:8 Uncaught Error: ZoneSpec required!

try the imports in client/lib/dependencies.js
make sure you have the modules package installed

@hlehmann
Still the same results.
I have added the client/lib/dependencies.js with the content from @rbaradari .
Modules package is part of the angular2-meteor package and was already present in ./.meteor/local/build/programs/web.browser/packages
I have also tried it after installing modules package via npm myself, but still the same result.

I added all dependencies and polyfills required by Angular2 in a separate package called angular2-runtime that goes as part of angular2-compilers now. Just update angular2-compilers (when new version is published), and it should free you from requiring dependencies like reflect-metadata etc directly.

How does one force meteor to update a package when running meteor update angular2-compilers responds with The specified packages are at their latest compatible versions. and yet running meteor update yields
Not updating the release, because this app is at a newer release<EMAIL_ADDRESS>than the latest recommended release (METEOR@1.2.1).
Your top-level dependencies are at their latest compatible versions.

The following top-level dependencies were not updated to the very latest version available:
 * angular2-compilers 0.5.0 (0.5.4 is available)

Newer versions of the following indirect dependencies are available:
 * barbatus:typescript 0.2.0-beta.8 (0.2.0 is available)
 * barbatus:typescript-compiler 0.5.0-beta.14 (0.5.0-beta.15 is available)
To update one or more of these packages, pass their names to `meteor update`.

?

@u0m3 can you try doing meteor update<EMAIL_ADDRESS>or maybe even just meteor update barbatus:typescript should work?

@Urigo unfortunately no
C:\git\meteor1.3-angular2.0-socially [master +7 ~0 -0 !]> meteor update barbatus:typescript
The specified packages are at their latest compatible versions.
C:\git\meteor1.3-angular2.0-socially [master +7 ~0 -0 !]> meteor update<EMAIL_ADDRESS>=> Errors while upgrading packages:

While selecting package versions:
error: Package names can only contain lowercase ASCII alphanumerics, dash, dot, or colon, not "@".