Sending messages from MQTT

Hi just a question since I could not find anything about it in here.
How would I go about sending a message from MQTT to a ROS-topic ? What format is expected ?
I tried something along the lines of
mqtt pub -t command -m "{'data':  'move'}"

The data printed in
mqtt sub -t command --jsonOutput

looked exactly the same as the data received from rostopic pub.
I set up the bridge following the tutorial precisely, so that should not be an issue.
I also tried sending data from python
import paho.mqtt.publish as publish
import json
publish.single("command", json.dumps({"data": "move next"}))
publish.single("command", "move next"}))

and Node-Red
[{"id":"a6fe74db.61f648","type":"inject","z":"ffe42276.7efb1","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"\"move next\"","payloadType":"str","x":790,"y":500,"wires":[["61ab1db.5bc4164"]]}]

but nothing seemed to work.
So how would I do that ?
Regards

I seem to have overlooked a tiny type in the configuration file. Sorry for opening up an issue for that. Have a nice day !


About the input image shape

I get the image shape from dataloader, the image shape is torch.Size([1, 12, 3, 32, 224, 224]).
I know it's [batch_size, ?, RGB, frames, H, W], but I don't know why it has "12" in a video data.
Does anyone know that dimension is?
In ./tools/test.py:
data_loader = build_dataloader(dataset, **dataloader_setting)
for i in data_loader:
print("img shape: ", i['imgs'].size())
Thank you.

Hi, I am also confused about this. Do you have any answers?

Hi, I am also confused about this. Do you have any answers?

Hello, I find the answer in the following path:
SwinTransformer/Video-Swin-Transformer/configs/recognition/swin/swin_tiny_patch244_window877_kinetics400_1k.py
You can see that in "test_pipeline" have two process, one is SampleFrames(num_clips=4), another is ThreeCrop.
So it generates 4x3 clips for testing.


Weird CORS problem with superagent and cloudfront amazon S3 in firefox

I got a very weird error with superagent when making simple request to amazon cloudfront:
There is simple code block:
superagent
.get('https://danesrti8sy2q.cloudfront.net/public/issues/6491/deploy.json')
.set('Accept', 'application/json')
.end(function(error, res){
console.log("res");
});
In firefox, it will throws the errors:
"NetworkError: 403 Forbidden - https://danesrti8sy2q.cloudfront.net/public/issues/6491/deploy.json"
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://danesrti8sy2q.cloudfront.net/public/issues/6491/deploy.json. This can be fixed by moving the resource to the same domain or enabling CORS.
But using jquery is totally fine:
$.getJSON("https://danesrti8sy2q.cloudfront.net/public/issues/6491/deploy.json", function(data){console.log(data);})
Note that, cloudfront has been configured to accept CORS request. I guess there might be some differences in term of headers btw the one using by jquery and superagent. Any one have an idea?

Does it work fine in other browsers?

Yes. From what i test, the error only occur in firefox.

I believe this is the same issue as #484, there is an onprogress callback which is added to the xhr. Doing this on a cross domain request causes a security exception only in firefox.
I've modified this on my own fork and removed the callback to work around the issue 9b1e68e4036f12d01b7172141f0c6a2c44d546bf, it looks like firefox is not going to change this. Instead it needs detect the cross origin and not bind the callback in that case.

Am having the same problem :(

I also ran into this issue. Following the trail @rdy suggested, I found this ominous defect on Bugzilla: Unnecessary CORS preflight when using upload progress.
Mozilla claims it's not a defect at all, specifically referencing the XmlHttpRequest spec which states that it will it will use "CORS-with-forced-preflight if one or more event listeners are registered on the associated XMLHttpRequestUpload object...".
So it appears as though when superagent registers for the onprogress event:
// client.js
if (xhr.upload) {
  xhr.upload.onprogress = function(e){
    e.percent = e.loaded / e.total * 100;
    self.emit('progress', e);
  };
}

This is causing Firefox to do a preflight OPTIONS request, which in our case is getting blocked by cloudfront (not your problem). Chrome, IE and Safari seem to have a different interpretation of the spec, and aren't doing the prelight.
@defunctzombie, is there maybe a way to not register for the onprogress event if it's not needed (e.g. no event listeners have been added)? Because even if we configure cloudfront to allow the OPTIONS requests through, there will still be one for every request we make through superagent (on Firefox), even just simple GET requests that shouldn't require a preflight.

@dlockhart
https://github.com/visionmedia/superagent/blob/master/lib/client.js#L929-L930
New versions of superagent don't register the onprogress handler unless you have progress listeners.

Awesome, you read my mind. :)
Confirmed that this fixes the issue, I vote you can close it.


replaced Array.isArray with isarray package

This PR offers better backwards compatibility for environments that don't support Array.isArray.
The isarray package is the defacto way of performing this type check (46 million monthly downloads) so it makes sense that isobject should use it as part of its check.

The isarray package is the defacto way of performing this type check (46 million monthly downloads)

Yeah, I think a huge portion of those downloads is from a previous version of this package.
How likely is it for this to be used in a browser that doesn't support Array.isArray, without having gone through a build-step with something like webpack or browserify first?
Especially given that Array.isArray is just one of many methods and javascript features that won't be available in browsers that don't support JavaScript 1.8.5. It seems unlikely for modern JavasScript to used in older browsers without also having the necessary polyfills.
Any thoughts on this?

I don't think there's any supported browser or node version that does not have Array.isArray.

Closing, I don't see why this would be needed.


JSON schema validation not allowing "description" to be a propery of an object

VSCode Version: 1.28.2
OS Version: macOS mojave 10.14

Steps to Reproduce:

Create file `test.schema.json
In workspace settings, add:

	"json.schemas": [
		{
			"fileMatch": [
				"test.json"
			],
			"url": "test.schema.json"
		}
	]

In file test.schema.json insert this snippet:

{
	"type": "object",
	"properties": {
		"lines": {
			"description": "",
			"type": "array",
			"items": {
				"description": {
					"description": "description",
					"type": "string",
					"minLength": 1,
					"maxLength": 1000
				}
			}
		}
	}
}

That would provide you with an error like this:

While I am totally aware that the description would usually work as a string as the description of for instance the property, there could be cases like this, where the property of an object is called "description".
Without luck I tried to find this in code, but didn't manage - so if you are capable of pointing me in the right direction, I wouldn't mind to look into this myself.
Let me know if you require any further information.

Does this issue occur when all extensions are disabled?: Yes

I think this is actually cause by the formatting of the lines array. Closing for now. Sorry for the inconvenience.


Proper ICMPv6 handling for enable-endpoint-routes

Proposal / RFE
Is your feature request related to a problem?
Yes, currently neighbor solicitations messages (ICMP6_NS_MSG_TYPE) exiting an endpoint have to have dstIP of router or other endpoint in the ENDPOINTS_MAP.  See https://github.com/cilium/cilium/blob/master/bpf/lib/icmp6.h#L383 or https://github.com/cilium/cilium/blob/master/bpf/lib/icmp6.h#L389.
When enable-endpoint-routes is enabled (which is my case) the endpoint could be sending out NS like:
.---------------------------------------------------------------------.
|  .-----------------.                                                |
|  | cilium_host     |                                                |
|  '-----------------'                   .---------------------------.|
|  .-----------------.                   |         podScope          ||
|  | lxcXXXXXXXXXXXX |                   |                           ||
|  '-----------------'                   |                           ||
|  .-----------------.    .---------.    |   2a02:598:247:3::abb4    ||
|  | lxc86bcaa204b44 |<-->| bpf_lxc |<-->|       link-local          ||
|  '-----------------'    '---------'    | fe80::d01e:84ff:fedf:1794 ||
|       link-local             .         |          MAC              ||
|fe80::d0ff:2aff:fe5f:29f4     |         |    d2:1e:84:df:17:94      ||
|          MAC                 |         '---------------------------'|
|   d2:ff:2a:5f:29:f4          |                                      |
|                              |                                      |
|hostScope                     |                                      |
'------------------------------|--------------------------------------'
                               '
                     handle_xgress()
                     tail_handle_ipv6()
                     handle_ipv6()
                     icmp6_handle()
                     icmp6_handle_ns()
                     tail_icmp6_handle_ns()
                     __icmp6_handle_ns()

xx drop (Unknown L3 target address) flow 0x0 to endpoint 0, identity 0->0: fe80::d01e:84ff:fedf:1794 -> fe80::d0ff:2aff:fe5f:29f4 NeighborSolicitation

which is neither (meaning the dstIP) router nor another endpoint.  This results in the packet being dropped - https://github.com/cilium/cilium/blob/master/bpf/lib/icmp6.h#L397
Describe the solution you'd like
This should either be allowed for enable-endpoint-routes with something like:
#ifdef ENABLE_ENDPOINT_ROUTES
#define SKIP_ICMPV6_NS_HANDLING
#endif

since SKIP_ICMPV6_NS_HANDLING is already present here https://github.com/cilium/cilium/blob/master/bpf/lib/icmp6.h#L400
or this should be handled in a better way since without this fix/feature IPv6 traffic cannot and doesn't work.

:wave: circling back - this is about the logic in https://github.com/cilium/cilium/blob/71646861786bc4cddbbc51d9607149ac5f72c44e/bpf/lib/icmp6.h#L312, correct?
For the case you describe, we should also consider NS messages for another pod's link-local address? And presumably let those pass into the stack, rather than drop them.


Add backend controller to saas-operator

Why?
We need to add more 3scale components to saas-operator as new operator controller (ansible role). One of the main and more complex components (in terms of number of objects involved...) is 3scale backend, so it is the next controller to be implemented, reducing the complexity of application management  to a single and small CR (to handle differences between environements with CR fields...).
How?
Add a new backend controller with operator-sdk binary, extracting all yamls used on staging environment: deployments, services, route, configmap, podmonitors, secretdefinitions, and grafana dashboards (backned main app dashboard, and all dashboards related to storage on EC2, nodes, redis, sentinel, twemproxy...).
By the moment prometheusrules will be out of the operator scope, as they can be very dynamic, still figuring out best alerts, thresholds... (so there is no need to update operator image with a new release to add, finetune, delete alerts or apply small changes).
Requirements

[ ] Add backend controller with all required objects in a single CRD

Acceptance Criteria
N/A
Notes
N/A

Opened issue to operaotr-sdk https://github.com/operator-framework/operator-sdk/issues/3216 :

Default liveness probe config (appears on operator-sdk v0.18.0) fails when there are 2 controllers

Solved by configuring less aggressive liveness probe

On operator-sdk v0.18.0/ v0.18.1 appears some  random weird lines (different apis each pod not related to saas-operator) on operator logs Throttling request took 1.046533228s, request: GET:https://<IP_ADDRESS>:443/apis/apiextensions.k8s.io/v1?timeout=32s
``   - But they are legit, comes from updated k8s client-go modulehttps://github.com/kubernetes/client-go/blob/3d5c80942cce510064da1ab62c579e190a0230fd/rest/request.go#L574-L575 , our clusters may be stressed at API calls level, non important, just info lines


As an admin I want to be able to create custom tax rates for country/region/postal

Testing Instructions:

Start the app and log in with a valid account
Navigate to Settings/Checkout/Taxes

Actually region should never be required since you can set a tax rate for an entire country


Add more information to Google CloudDNS guide

What this PR does / why we need it: This PR adds more information to the Google CloudDNS guide
Which issue this PR fixes: N/A
Special notes for your reviewer:
Release note:

Add more information to Google CloudDNS guide

/lgtm
/approve


Add SciFeeds to Tools

SciFeeds is a nice science aggregator gem that spans many fields of science, not just biology. Biology topics range broadly from microbiology to specifically on G-protein coupled receptors. It even has a section on Bioinformatics and other related informatics 😄
Added some spaces for consistency.

Thank you!


Experiment with Rust CI tool

You're porting the yaml/bash to Rust? This looks great!

You're porting the yaml/bash to Rust? This looks great!

I'm glad it doesn't seem totally crazy to you. Even after having written the tool, I'm not sure how I feel about replacing ~70 lines of Python with ~800 lines of Rust.
I think I could pretty easily replace the "Compare test failures VS reference" step with this, so that would be about -110 lines of Bash, and would help tip the scales a little bit.
The idea was to centralize all of the logic for analyzing test results. Right now we seem to have access to, and consider, the "ignore intermittent tests" list during the "Compare test failures VS reference" step, but not during the "Compare test summary VS reference" that actually determines whether the GnuTests workflow passes or fails.
This issue was the impetus:
https://github.com/uutils/coreutils/issues/6732
It's a very intermittent test, and even though it's listed in "ignore-intermittent.txt", if it fails, the GnuTests workflow fails.
I think having this logic in Rust might make it easier to do some nicer reporting, for instance to print the part of the test log that corresponds to any newly failing tests, rather than just reporting the delta in the count. But again, it's a lot of code, considering what it's replacing, and there's definitely an argument to be made that tasks like this should be done in higher level scripting languages that are less verbose.

Not a fan of the complexity :/

There's some downsides for sure. I think at the very least these steps should be refactored into separate files. Maybe something like Python is a slightly better fit though? On the other hand, we can probably reduce the complexity of this code a fair bit.

Do you see perf wins?

There's no performance benefit, no. If anything, the extra compile step probably makes this slower.
We can probably address https://github.com/uutils/coreutils/issues/6732 pretty easily without major refactoring. I think we just need some of the logic/data from "Compare test failures VS reference", so we can check which tests failed, not just the delta.

There's some downsides for sure. With Rust, I think I'm mostly concerned about the extra compile step. At the very least these steps should be refactored out of the yaml into separate files. Maybe something like Python is a slightly better fit though? On the other hand, we can probably reduce the complexity of this code a fair bit.

Yes, that's probably a more reasonable approach. I was thinking it would be nice to reduce the number of tools/programming languages being used in the CI scripts, but Rust is probably just too low level/verbose for these tasks.
And yes, having dozens of lines of Bash scripts in YAML files isn't too nice, because you don't get editor support/ability to lint with ShellCheck, etc.

I don't think we want to increase the complexity. Python is fine in this case. Sorry :(


bug(dev): Core dump when panic

Is there an existing issue?

[X] I have searched the existing issues

Description of bug
When the node shuts down because of a panic, the node is supposed to stop gracefully
However, when I add a todo!() at a random place in the code, this happens:
[2024-09-13 10:49:15 HTTP] 🌐 starknet_V0_7_1_call 200 102 bytes - 83.436ms
[2024-09-13 10:49:16 HTTP] 🌐 starknet_V0_7_1_getClass 28 77 bytes - 293µs
[2024-09-13 10:49:16 HTTP] 🌐 starknet_V0_7_1_getNonce 200 39 bytes - 363µs
[2024-09-13 10:49:16 HTTP] 🌐 starknet_V0_7_1_getNonce 200 39 bytes - 368µs
thread 'tokio-runtime-worker' panicked at crates/client/rpc/src/providers/mempool.rs:40:54:
not yet implemented
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
run.sh: line 39: 51977 Aborted                 (core dumped) ./target/debug/madara --gateway-key <hidden> --base-path .deoxysdb --no-l1-sync $@

The process is aborted and the core is dumped. I wonder what's happening, but the rocksdb "gracefully closing the db" log is not shown - it might be related..? weird
We do not use unsafe anywhere in the codebase, so I'm guessing this is probably the Drop implementation of rocksdb::DB doing this.  (for those who don't know, the DB graceful close is implemented using the Drop trait, because unwinding the stack runs destructors :) )
This is lower priority as we're not supposed to panic anyway, but in case we panic we're supposed to close the db properly. Also, we are already fault-tolerant, so not closing the db properly is not that big of a deal.
Steps to reproduce
No response

For any contributor wanting to take this: the way you would debug this kind of thing is using gdb or lldb, and opening the core dump (that's what it's for ;) )

Hey, I've been trying to reproduce this bug in the latest version for Madara without any success. Are you still able to get a core dump this way?


Issue today after updating to 2.0

I got this issue today after updating to 2.0. I have soft restarted, and also hard-restarted,

Log
  zigbee2mqtt:info 2018-11-15 17:29:36 Logging to directory: '/share/zigbee2mqtt/log/2018-11-15.17-29-36'
  zigbee2mqtt:info 2018-11-15 17:29:39 Starting zigbee2mqtt version 0.2.0 (commit #unknown)
  zigbee2mqtt:info 2018-11-15 17:29:39 Starting zigbee-shepherd
  zigbee2mqtt:info 2018-11-15 17:29:44 zigbee-shepherd started
  zigbee2mqtt:info 2018-11-15 17:29:44 Coordinator firmware version: 'undefined'
  zigbee2mqtt:info 2018-11-15 17:29:44 Currently 0 devices are joined:
  zigbee2mqtt:warn 2018-11-15 17:29:44 `permit_join` set to  `true` in configuration.yaml.
  zigbee2mqtt:warn 2018-11-15 17:29:44 Allowing new devices to join.
  zigbee2mqtt:warn 2018-11-15 17:29:44 Set `permit_join` to `false` once you joined all devices.
  zigbee2mqtt:info 2018-11-15 17:29:44 Zigbee: allowing new devices to join.
  zigbee2mqtt:info 2018-11-15 17:29:44 Connecting to MQTT server at mqtt://<IP_ADDRESS>:1883
  zigbee2mqtt:info 2018-11-15 17:29:45 zigbee-shepherd ready
events.js:183
      throw er; // Unhandled 'error' event
      ^
Error: Connection refused: Not authorized
    at MqttClient._handleConnack (/zigbee2mqtt-0.2.0/node_modules/mqtt/lib/client.js:920:15)
    at MqttClient._handlePacket (/zigbee2mqtt-0.2.0/node_modules/mqtt/lib/client.js:350:12)
    at work (/zigbee2mqtt-0.2.0/node_modules/mqtt/lib/client.js:292:12)
    at Writable.writable._write (/zigbee2mqtt-0.2.0/node_modules/mqtt/lib/client.js:302:5)
    at doWrite (/zigbee2mqtt-0.2.0/node_modules/readable-stream/lib/_stream_writable.js:428:64)
    at writeOrBuffer (/zigbee2mqtt-0.2.0/node_modules/readable-stream/lib/_stream_writable.js:417:5)
    at Writable.write (/zigbee2mqtt-0.2.0/node_modules/readable-stream/lib/_stream_writable.js:334:11)
    at Socket.ondata (_stream_readable.js:639:20)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
npm
 ERR! code ELIFECYCLE
npm ERR! errno 1
npm
 ERR<EMAIL_ADDRESS>start: `node index.js`
npm ERR!
 Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!
     /root/.npm/_logs/2018-11-15T16_29_45_726Z-debug.log
2018-11-15T17:29:46: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2018-11-15T17:29:46: PM2 log: App [npm:0] starting in -fork mode-
2018-11-15T17:29:46: PM2 log: App [npm:0] online
><EMAIL_ADDRESS>start /zigbee2mqtt-0.2.0
> node index.js
		Zigbee2mqtt requires node version >=8.11 10, you are running v8.11.4!
  zigbee2mqtt:info 2018-11-15 17:29:53 Logging to directory: '/share/zigbee2mqtt/log/2018-11-15.17-29-53'
  zigbee2mqtt:info 2018-11-15 17:29:55 Starting zigbee2mqtt version 0.2.0 (commit #unknown)
  zigbee2mqtt:info 2018-11-15 17:29:55 Starting zigbee-shepherd
  zigbee2mqtt:info 2018-11-15 17:30:00 zigbee-shepherd started
  zigbee2mqtt:info 2018-11-15 17:30:00 Coordinator firmware version: 'undefined'
  zigbee2mqtt:info 2018-11-15 17:30:00 Currently 0 devices are joined:
  zigbee2mqtt:warn 2018-11-15 17:30:00 `permit_join` set to  `true` in configuration.yaml.
  zigbee2mqtt:warn 2018-11-15 17:30:00 Allowing new devices to join.
  zigbee2mqtt:warn 2018-11-15 17:30:00 Set `permit_join` to `false` once you joined all devices.
  zigbee2mqtt:info 2018-11-15 17:30:00 Zigbee: allowing new devices to join.
  zigbee2mqtt:info 2018-11-15 17:30:00 Connecting to MQTT server at mqtt://<IP_ADDRESS>:1883
  zigbee2mqtt:info 2018-11-15 17:30:01 zigbee-shepherd ready
events.js:183
      throw er; // Unhandled 'error' event
      ^
Error: Connection refused: Not authorized
    at MqttClient._handleConnack (/zigbee2mqtt-0.2.0/node_modules/mqtt/lib/client.js:920:15)
    at MqttClient._handlePacket (/zigbee2mqtt-0.2.0/node_modules/mqtt/lib/client.js:350:12)
    at work (/zigbee2mqtt-0.2.0/node_modules/mqtt/lib/client.js:292:12)
    at Writable.writable._write (/zigbee2mqtt-0.2.0/node_modules/mqtt/lib/client.js:302:5)
    at doWrite (/zigbee2mqtt-0.2.0/node_modules/readable-stream/lib/_stream_writable.js:428:64)
    at writeOrBuffer (/zigbee2mqtt-0.2.0/node_modules/readable-stream/lib/_stream_writable.js:417:5)
    at Writable.write (/zigbee2mqtt-0.2.0/node_modules/readable-stream/lib/_stream_writable.js:334:11)
    at Socket.ondata (_stream_readable.js:639:20)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
npm
 ERR!
code ELIFECYCLE
npm ERR! errno 1
npm
 ERR<EMAIL_ADDRESS>start: `node index.js`
npm
ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!
     /root/.npm/_logs/2018-11-15T16_30_01_571Z-debug.log
2018-11-15T17:30:01: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2018-11-15T17:30:01: PM2 log: App [npm:0] starting in -fork mode-
2018-11-15T17:30:01: PM2 log: App [npm:0] online
><EMAIL_ADDRESS>start /zigbee2mqtt-0.2.0
> node index.js
		Zigbee2mqtt requires node version >=8.11 10, you are running v8.11.4!
  zigbee2mqtt:info 2018-11-15 17:30:09 Logging to directory: '/share/zigbee2mqtt/log/2018-11-15.17-30-09'
  zigbee2mqtt:info 2018-11-15 17:30:12 Starting zigbee2mqtt version 0.2.0 (commit #unknown)
  zigbee2mqtt:info 2018-11-15 17:30:12 Starting zigbee-shepherd
  zigbee2mqtt:info 2018-11-15 17:30:15 Error while starting zigbee-shepherd, attemping to fix... (takes 60 seconds)
  zigbee2mqtt:info 2018-11-15 17:31:15 Starting zigbee-shepherd
  zigbee2mqtt:error 2018-11-15 17:31:18 Error while starting zigbee-shepherd!
  zigbee2mqtt:error 2018-11-15 17:31:18 Press the reset button on the stick (the one closest to the USB) and start again
  zigbee2mqtt:error 2018-11-15 17:31:18 Failed to start
	{"message":"request timeout","stack":"Error: request timeout\n    at CcZnp.<anonymous> (/zigbee2mqtt-0.2.0/node_modules/cc-znp/lib/ccznp.js:255:22)\n    at Object.onceWrapper (events.js:315:30)\n    at emitOne (events.js:116:13)\n    at CcZnp.emit (events.js:211:7)\n    at Timeout.<anonymous> (/zigbee2mqtt-0.2.0/node_modules/cc-znp/lib/ccznp.js:234:18)\n    at ontimeout (timers.js:498:11)\n    at tryOnTimeout (timers.js:323:5)\n    at Timer.listOnTimeout (timers.js:290:5)"}

Did you create a corresponding issue in zigbee2mqtt repo? Probably would be a good idea given I think it’s more likely to be an issue there than with the add-on

I have the same issue today, how did you solve this?

I haven't yet
ons. 21. nov. 2018 21.37 skrev 1981nick1982<EMAIL_ADDRESS>
I have the same issue today, how did you solve this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/danielwelch/hassio-zigbee2mqtt/issues/71#issuecomment-440801467,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACe97lGkRq8zLWoK2SlXIT5c4LurYRH2ks5uxbmggaJpZM4YgpOb
.

Same issue. Had a running configuration on HomeAssistant/hassio on a Raspberry Pi 3. Updated to hassio-zigbee2mqtt Version 0.2.0 and lost the complete zigbee functionality. I read several posts (for example https://github.com/Koenkk/zigbee2mqtt/issues/67#issuecomment-393521792) but even after un-plugging and re-plugging the stick, resetting it etc it does not work at all.
I am not sure how "Jessie" or "not-Jessie" translates to hassio (https://github.com/Koenkk/zigbee2mqtt/wiki/Running-the-bridge "NOTE: it is reported that Raspbian Jessie doesn't work.") but as hassio on a Pi3 does not seem to be an exotic configuration, I am wondering how to resolve this issue...

Thanks for the reports, I’ll try to look into it. Again, I’d echo that an issue should be created in zigbee2mqtt and linked here.

This seems to be a zigbee2mqtt issue, lets continue here: https://github.com/Koenkk/zigbee2mqtt/issues/617

For users having this problem, do you have authentication enabled on the MQTT server?

I do
fre. 23. nov. 2018 08.55 skrev Koen Kanters<EMAIL_ADDRESS>
For users having this problem, do you have authentication enabled on the
MQTT server?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/danielwelch/hassio-zigbee2mqtt/issues/71#issuecomment-441173552,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACe97t9aGrSjf8iCrYhK-SCO4hYOafymks5ux6nWgaJpZM4YgpOb
.

Might be worth knowing what backend everyone is using for MQTT in Hassio. I use the community add on, but I think some changes were made recently to the official MQTT add on

@danielwelch that would mean when downgrading the zigbee2mqtt to 0.1.8 it should work again. @martincollignon can you try this?

I also have the community add-on of MQTT.

I am using this one https://www.home-assistant.io/addons/mosquitto/

@jensbri are you using the optional logins config for that add on and, if so, are you using those credentials for this add on?

Okay,
So I have hassio installed with just Zigbee2mqtt addon, connecting to a mqtt server on different machine altogether, upgrading to v2 has completely broken zigbee network
Also tried full restore of v1.8 working snapshot, automatically upgrades to v2.0, during addon boot up resulting with no zigbee network. So down grading does not work
Even tried deleting db, and re-pairing, this just causes the device to constantly crash and reboot
Hope this helps in trying to figure out what’s broken, log also warning node-js needs upgrading (not compatible).

@1981nick1982 mentioned in https://github.com/Koenkk/zigbee2mqtt/issues/617 that setting anonymous setting on true, for the hassio mosquitto broker fixed the problem.
Could it be that the authentication configuration is not used correctly @danielwelch ?

Hi. I followed your recommendation and set anonymous to true in their "Mosquitto broker". Now everything works like a Charme. Thanks!

I’m wondering if the move to authenticating with the homeassistant user in the latest versions of the mosquito official add-on is what’s causing the problem for most. The fact that it works with anonymous access certainly supports this. The latest versions of the add-on (if I recall, version 3 and beyond) require you to set up an “integration” via the front end. If anyone reading this upgraded without doing that, I’d refer to the add on docs and do that.
Allowing anonymous access is, generally speaking, a bad idea. In the example config posted by @1981nick1982, the logins option is blank. You should be able to use that option to define login credentials that you can then use in zigbee2mqtt, allowing zigbee2mqtt to connect without enabling anonymous access.

Spoke too soon,
Now getting sames issue!!!! with v0.81.6

@01kbpatel could you tell us more about your setup? Is your log error identical to the one we are discussing here? What are you using for an MQTT server/broker? Do you have authentication enabled on your MQTT server? Does disabling that fix the problem? Based on the one suggested fix, it seems like a problem with zigbee2mqtt authentication, but I’m not aware of any change that was made relating to that. I suspect changes to the official MQTT add-on are causing the problem for some, but I’d like to hear more about your issue since you’re using a separate MQTT server.

Hi Guys, I made it working for me! I have changed  mosquito to: "anonymous": true,
I have also added in the configuration.yaml file"
mqtt:
broker: (IP of Raspberry)
And I have added the allow to join configuration of zigbee2mqtt. works like a charme.
So install the add ons:
Mosquitto broker - and punt anonymous on true.
zigbee2mqtt
mqtt- and put the IP address in the configuration
add the allow to join configuration. ( you need to remove 2 spaces before every line before it works)

Hi Guys, I made it working for me! I have changed mosquito to: "anonymous": true,
I have also added in the configuration.yaml file"
mqtt:
broker: (IP of Raspberry)
And I have added the allow to join configuration of zigbee2mqtt. works like a charme.
So install the add ons:
Mosquitto broker - and punt anonymous on true.
zigbee2mqtt
mqtt- and put the IP address in the configuration
add the allow to join configuration. ( you need to remove 2 spaces before every line before it works)

@michaeldbr, when you say "allow to join" for zigbee2mqtt do you mean set permit_join to true?

Sorry I made a mistake. I used the the allow to join script from:
https://github.com/danielwelch/hassio-zigbee2mqtt/blob/master/README.md

Hi Guys, I made it working for me! I have changed mosquito to: "anonymous": true,
I have also added in the configuration.yaml file"
mqtt:
broker: (IP of Raspberry)
And I have added the allow to join configuration of zigbee2mqtt. works like a charme.
So install the add ons:
Mosquitto broker - and punt anonymous on true.
zigbee2mqtt
mqtt- and put the IP address in the configuration
add the allow to join configuration. ( you need to remove 2 spaces before every line before it works)

This only works for a short time. After some hours i get this error:
1543758328: Saving in-memory database to /data/mosquitto.db.

I am also having this isssue with HA 0.83.2.
Zigbee2mqtt only works for a short period of time. It was working correctly before updating to this HA latest version.
I have a manual installation of HA on top of raspbian, mosquito in the same RPi with authentication.
I can provide more details if needed to help to solve this issue.
Thanks

Hi everyone,
Just a quick update since I like to answer my own questions :-)
Yesterday I updated my HA to the latest 0.83.3 but this dindn't solve the zigbee2mqtt issue.
After some debugging running zigbee2mqtt manually and analyzing its the logs and also mosquitto's, I fixed the issue I was having by deleting the mosquitto database:
sudo service mosquitto stop
sudo rm /var/lib/mosquitto/mosquitto.db
sudo service mosquitto start
Not sure if this was really needed but since I was having a huge delay only with mqtt messages from/to zigbee2mqtt, I decided to delete mosquitto database.
after that I comented/removed the following line in zigbee2mqtt configuration yaml:
#include_device_information: true
Since then my zigbee2mqtt is working without any issues as before last weekeng HA update.
HTH anyone

Hi,
I had similar issues upon updating to 0.2.0, zigbee2mqtt was logging
Error: Connection refused: Not authorized
and mosquitto was logging
Socket error on client
at the same time.
I followed the steps below, my system seems to be stable for the time being:

Updated mosquitto add-on to version 4
Set a local user on mosquitto config - i.e.

"logins": [
    {
      "username": "mqttuser",
      "password": "password"
    }
  ],

Set this user in zigbee2mqtt config:

"mqtt_user": "mqttuser",
"mqtt_pass": "password"

Restart mosquitto add-on
Restart zigbee2mqtt

I’m pretty certain there are multiple separate issues being discussed in this thread, causing some confusion. @ekinmeroglu and others ran into problems because the official mosquito add-on changed the way it did authorization, so they just needed a configuration update to get things going. Others are having problems while running their own brokers and, obviously, are experiencing a separate issue.

Hi, this is my first time configuring zigbee. I updated the USB firmware, and now I'm trying to configure this great module, but I'm getting a error message when I try to allow permit join from the script:
`[Info] Configuration file found. Will overwrite configurable               fields with values from add-on configuration
[Info] Configuration written to /share/zigbee2mqtt/configuration.yaml
2018-12-13T12:12:51: PM2 log: Launching in no daemon mode
2018-12-13T12:12:53: PM2 log: App [npm:0] starting in -fork mode-
2018-12-13T12:12:53: PM2 log: App [npm:0] online

<EMAIL_ADDRESS>start /zigbee2mqtt-0.2.0
node index.js
Zigbee2mqtt requires node version >=8.11 10, you are running v8.11.4!
zigbee2mqtt:info 2018-12-13 12:13:04 Logging to directory: '/share/zigbee2mqtt/log/2018-12-13.12-13-03'
zigbee2mqtt:info 2018-12-13 12:13:08 Starting zigbee2mqtt version 0.2.0 (commit #unknown)
zigbee2mqtt:info 2018-12-13 12:13:08 Starting zigbee-shepherd
zigbee2mqtt:info 2018-12-13 12:13:10 zigbee-shepherd started
zigbee2mqtt:info 2018-12-13 12:13:10 Coordinator firmware version: '20180815'
zigbee2mqtt:info 2018-12-13 12:13:10 Currently 0 devices are joined:
zigbee2mqtt:info 2018-12-13 12:13:10 Zigbee: disabling joining new devices.
zigbee2mqtt:info 2018-12-13 12:13:10 Connecting to MQTT server at mqtt://<IP_ADDRESS>:1883
zigbee2mqtt:info 2018-12-13 12:13:10 zigbee-shepherd ready
zigbee2mqtt:info 2018-12-13 12:13:10 Connected to MQTT server
zigbee2mqtt:info 2018-12-13 12:13:10 MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'online'
zigbee2mqtt:info 2018-12-13 12:22:33 Zigbee: allowing new devices to join.
zigbee2mqtt:info 2018-12-13 12:22:36
{"message":"request timeout","stack":"Error: request timeout\n    at CcZnp. (/zigbee2mqtt-0.2.0/node_modules/cc-znp/lib/ccznp.js:255:22)\n    at Object.onceWrapper (events.js:315:30)\n    at emitOne (events.js:116:13)\n    at CcZnp.emit (events.js:211:7)\n    at Timeout. (/zigbee2mqtt-0.2.0/node_modules/cc-znp/lib/ccznp.js:234:18)\n    at ontimeout (timers.js:498:11)\n    at tryOnTimeout (timers.js:323:5)\n    at Timer.listOnTimeout (timers.js:290:5)"}
zigbee2mqtt:info 2018-12-13 12:32:34 Zigbee: disabling joining new devices.
zigbee2mqtt:info 2018-12-13 12:32:34 Zigbee: disabling joining new devices.
zigbee2mqtt:info 2018-12-13 12:32:37
{"message":"request timeout","stack":"Error: request timeout\n    at CcZnp. (/zigbee2mqtt-0.2.0/node_modules/cc-znp/lib/ccznp.js:255:22)\n    at Object.onceWrapper (events.js:315:30)\n    at emitOne (events.js:116:13)\n    at CcZnp.emit (events.js:211:7)\n    at Timeout. (/zigbee2mqtt-0.2.0/node_modules/cc-znp/lib/ccznp.js:234:18)\n    at ontimeout (timers.js:498:11)\n    at tryOnTimeout (timers.js:323:5)\n    at Timer.listOnTimeout (timers.js:290:5)"}
zigbee2mqtt:info 2018-12-13 12:32:40
{"message":"request timeout","stack":"Error: request timeout\n    at CcZnp. (/zigbee2mqtt-0.2.0/node_modules/cc-znp/lib/ccznp.js:255:22)\n    at Object.onceWrapper (events.js:315:30)\n    at emitOne (events.js:116:13)\n    at CcZnp.emit (events.js:211:7)\n    at Timeout. (/zigbee2mqtt-0.2.0/node_modules/cc-znp/lib/ccznp.js:234:18)\n    at ontimeout (timers.js:498:11)\n    at tryOnTimeout (timers.js:323:5)\n    at Timer.listOnTimeout (timers.js:290:5)"}`

I don't have problem connecting to broker, but I don't know why I receive this error messages...

I'm pretty sure I've had two separate issues with zigbee2mqtt 0.2.0: There was another one even before updating mosquitto to v4.
I was using a customized devices.js via zigbee_shepherd_devices: true statement, and the custom file in question was from 0.1.8 era - It seems some parts were not compatible with 0.2.0, so the service failed to start with an exception like TypeError: Cannot read property 'key' of undefined
I disabled this custom devices.js usage, and everything got back to normal.
Long story short, I'd try running the add-on with only the default settings / parameters, and if it fails with an exception other than ..Not authorized, I'd go on and open a different issue, as @danielwelch suggested.

In case anyone else has this issue and stumbles across this page, this issue is fixed by creating a Home Assistant user with the same username and password as you put in the zigbeetomqtt configuration.


Chromium docs 4987579

Docs Build status updates of commit a84b26d:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit eeeaacf:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/whats-new/includes/contact-whats-new-note.md
:warning:Warning

Details

microsoft-edge/devtools-guide-chromium/whats-new/2019/12/devtools.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/2020/01/devtools.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/2020/03/devtools.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/2020/05/devtools.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/2020/06/devtools.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/media/2019/12/bing-devtools-send-feedback.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/media/2020/01/bing-devtools-send-feedback.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/media/2020/03/bing-devtools-send-feedback.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/media/2020/05/bing-devtools-send-feedback.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/media/2020/06/bing-devtools-send-feedback.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/media/bing-devtools-send-feedback.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/workspaces/index.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/includes/contact-whats-new-note.md

Line 13, Column 41: [Warning-bookmark-not-found] Cannot find bookmark '#feedback' in 'devtools-guide-chromium/whats-new/includes/contact-whats-new-note.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2a23490:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/whats-new/includes/contact-whats-new-note.md
:warning:Warning

Details

microsoft-edge/devtools-guide-chromium/whats-new/2019/12/devtools.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/2020/01/devtools.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/2020/03/devtools.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/2020/05/devtools.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/2020/06/devtools.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/media/2019/12/bing-devtools-send-feedback.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/media/2020/01/bing-devtools-send-feedback.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/media/2020/03/bing-devtools-send-feedback.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/media/2020/05/bing-devtools-send-feedback.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/media/2020/06/bing-devtools-send-feedback.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/media/bing-devtools-send-feedback.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/workspaces/index.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/whats-new/includes/contact-whats-new-note.md

Line 13, Column 41: [Warning-bookmark-not-found] Cannot find bookmark '#feedback' in 'devtools-guide-chromium/whats-new/includes/contact-whats-new-note.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

#sign-off and merged.


fix startActivity

#7

the code looks good. would you mind to preserve tab- and whitespace style from the original code?

fixed

thanks one more time @Pmant :)

included in release 1.1.5


Completion of walkthroughs/week-3-server/step-3

Thanks Tayyaba! Looks good overall!
(Just a few nitpicks:))


Exactly the same error than in Angular-froala-WYSIWYG html.set is not a function

See
https://github.com/froala/angular-froala-wysiwyg/issues/206
We have exactly the same error in the Angular 1 version.

This commit https://github.com/mthomasson/angular-froala/commit/0930ae307322e8c276a398888c6327c094dc6723
solves it

We're also experiencing this issue

@stefanneculai when you install the package with npm it installs the latest version 2.8.4 with the  issue fixed. But if you install the package with bower you are still getting 2.8.3. Looking at the Release in GitHub, the latest release is flagged as 2.8.3. Maybe this is the issue with bower?

@petarblazevski I believe the problem is bower relies upon the github "release" tags, and there isn't a release tag for 2.8.4, so we have to use the git sha instead.


[feature] limit max connections

hi @manjuraj

allow to set max simultaneous connections
server shouldn't close listen fd when accept function occur error

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Bazel ci

I wanted to take another look at this, because I don't think the Bazel setup that's on master will work well for external projects, because of the way the vendoring works. I think "cargo raze" installation should be faster now. So, I'll just open this PR to take a look on Travis.

Sure thing. I am going to mute this thread while you iterate — please close and open another PR when you need me to take a look.

Looks like this is still slow, because cargo-raze has added new code that should compile faster, but hasn't yet removed the old code: https://github.com/google/cargo-raze/issues/132

This is down to ~4 minutes if cargo-raze is installed in debug mode (which should be fine, since the command takes 2.5 seconds to run when compiled that way). I'll try to get cargo-raze to add a feature that eliminates the cargo dependency next.

It looks like this will be about as fast the other builds if I can get the cargo-raze changes accepted.  Right now, the Bazel CI build is only a little slower than the macOS build, and it's running the cargo-raze stuff as well as the existing Bazel code.

A patch similar to mine eventually got landed in cargo-raze, so it should build much faster now.
I am still making a separate cc_library from the rust_library in my own code, so that both are compiled with the toolchains specified in the Bazel workspace. The only thing I had to add was
a linkstatic=True to the extra rule.


Additive transparency faces aren't always displayed (camera angle)

tomb4:
https://youtu.be/hOtcMvjeRms
TEN:
https://youtu.be/MM_4y7XCyBs
It's hard to tell exactly what's going on here, but depending on the camera angle the faces appear or disappear.
On the water surface below, they seem visible only from below.

Note 1: As shown on the screenshot below, I have a horizontal room portal in the middle of the waterfall (red line represents the portal). Don't know if it's related.
Note 2: Water surface above the waterfall is rendered completely opaque, but never flickers. However I set it as "Lighten" mode in TE (but maybe extra blending modes are just not implemented yet)

This was fixed a long time ago


Create SFTP fetcher / cache.

Done with tests in branch feture/remote. Live testing with active SSH service has been done but not included in the unit testing. asyncssh/asyncio was previously considered, implemented and tested in its own branch, but was dropped in favor of paramiko.


Create FP/FN bar charts (for one epoch)

Bar charts next to the matrix for false-positive (FP) and false-negative (FN) data.

Done.


[Bug Report] Icons don't work

Element UI version
1.4.2
OS/Browsers version
Windows 10, Chrome Version 60.0.3112.101
Vue version
2.4.2
Reproduction Link
https://jsfiddle.net/api/post/library/pure/
Steps to reproduce
Create some icon or button with icon
What is Expected?
Expected to show icon
What is actually happening?
Instead of icon it shows cube

Done

icon is name class  : class="name icon"

What it means? I didn't get.
I'm creating icons like that -
Or buttons with icon like that - Search
this is even on home page of this component - http://element.eleme.io/#/en-US/component/icon
but it doesn't work at all, it doesn't work since yesterday

Just assign the class name to el-icon-iconName.
it is class name in css with font-icon in css file.

like that?
<i class="el-icon-edit"></i>
if not can you provide an example please?

it have. https://jsfiddle.net not found by "f12" not load file css in server.
uri : @import url("//unpkg.com/element-ui@1.4.2/lib/theme-default/index.css"); not load.

https://github.com/ElemeFE/element/issues/6462

@Leopoldthecoder  your can help me. how to using event change in el-select.

@Leopoldthecoder it helps, thank you very much


Differences between the code and the paper

Hello,
Thank you for providing the code. I wonder if there are some differences between the code and the description in the paper? For example, you use a user_short_embedding as the initial state of the interest_evolve GRU and also propose a discrepency loss between the long and short-term user embedding. But these are not mentioned in the paper. Moreover, the short-term query in the paper is the q_s^{u,t} but you use the concatenation of the short_term_intention and the target_item_embedding as the short-term query in the code.
Thank you!

Hello,
Thanks for your attention on our work. There are a few details missing in the paper due to space limit.
First, as introduced in the Remark of Section 3.2.4 in the paper, adding a discrepency loss is a traditional  way to achieve disentanglement, however, it does not fit our case of disentangling long and short-term user interest since the two aspects can also overlap with each other to some extent. In our codes, we implement such discrepancy loss to investigate the effect of this traditional approach. Through experiments with different values of discrepancy_loss_weight, we find that the discrepancy loss brings no benefits. Specifically, the performance of setting discrepancy_loss_weight as a very small value of 0.01 is roughly the same as setting discrepancy_loss_weight as 0. Meanwhile, increasing discrepancy_loss_weight to 0.1 will bring performance drop. You can set discrepancy_loss_weight as other values to further investigate the effect of discrepancy loss.
Second, for the initial state of the interest_evolve GRU and the short-term query, these details are not introduced in the paper since they are not directly related to the main idea of self-supervised disentanglement. Please refer to our provided codes and we may update the paper on arxiv to include these details.
Thank you again!


chore: update distroless-iptables to v0.5.4

fixes https://github.com/Azure/azure-workload-identity/issues/1336

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

Project coverage is 52.55%. Comparing base (3874533) to head (3b3f569).
Report is 12 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1351      +/-   ##
==========================================
+ Coverage   51.66%   52.55%   +0.88%
==========================================
  Files          53       53
  Lines        2938     2445     -493
==========================================
- Hits         1518     1285     -233
+ Misses       1378     1118     -260
  Partials       42       42

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


ManageHHUI hits save errors if NPSP error logging disabled

Many of our save scenarios are hitting record lock issues on the account, as so many pieces of the save hit the account (merging, updating contacts, updating the hh from the LC component, updating the hh from the visualforce page fieldset).  Seems like UpdateNames() is usually the call that fails with the record lock.  With NPSP Error logging enabled, this error isn't treated as fatal, and just gets logged.  But with error logging disabled, this error gets propagated up to the page, and the save fails.

**lurch: add

Tracking W-010888

Included in beta release 3.78 (Beta 5)

Included in production release rel/3.78


[Bug Report]: Gzip is not enabled with noEmitAssets: true for Rspack dev server

System Info
.
Details
.
Reproduce link
No response
Reproduce Steps
See title.

Blocked by https://github.com/web-infra-dev/rspack/discussions/2742


Pokemon service - phase 0

Watch out! No tests yet!

How about now?
I don't raise exception, but return None if no results are found, that should be fine


CHIP-0015: NFT Metadata Extension

Please note that this CHIP proposal is pending the next published release from schema.org (expected by end of May).
Feel free to message on the PR or me directly (bholmes22/@clydewallace22) with any questions/comments/concerns

This CHIP is now a DRAFT. Please leave your reviews here.

We will be holding a public Zoom call to discuss this CHIP:
Time: May 16, 2023 at 4 PM PDT (11 PM UTC / 7 AM on the 17th in China)
Audience: Ecosystem developers and NFT creators
Zoom Link: See Discord
The call will be recorded and posted to Youtube afterward.

Here is the discussion of this CHIP:
https://www.youtube.com/watch?v=gZ9V5GxT0GU

I fully support this additional CHIP. Leveraging schema.org is an obvious choice.

To anyone else that might have the question of where @context and @type may come from, and then stumbling onto the W3C recommendation for JSON-LD (JSON Link Data https://json-ld.org/).
The following is my journey in discovering how @context will be used in the future. AFAICT this CHIP would be forward-compatible:
Here's one example where @context is a string, as it's used as I see CHIP-0015 recommending in some part, if I were to extrapolate a specific schema representing the NFT as a singular, whole:
https://www.w3.org/TR/json-ld11/#advanced-context-usage

Here's one where @context is an object:
https://www.w3.org/TR/json-ld11/#the-context

Another example shows that a @type is used in the 'leaf' node like shown in the CHIP-0015 examples.
https://www.w3.org/TR/json-ld11/#specifying-the-type

I saw JSON-LD gets very abstract, you can even alias keywords within the @context, so going that far can get pretty strange:
https://www.w3.org/TR/json-ld11/#aliasing-keywords

I then wanted to see what would happen if I try to point @context to something like a .jsonld. (I went with the page for VideoObject, which is not a .jsonld
I ran from the example, the following:
{
        "@context": "https://schema.org/VideoObject",
        "@type": "VideoObject",
        "encodingFormat": "video/mp4",
        "thumbnail": {
            "@type": "ImageObject",
            "encodingFormat": "image/png",
            "name": "Pikachu Thumbnail",
            "url": "www.fakeurl.com/example1_thumbnail.png",
            "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
        }
}

The Validator gave this warning:

So coming full-circle it's appropriate to have @context set to https://schema.org. Assuming any schema.org validation would use the "local context of schema.org" this makes sense.
I believe there could be another CHIP in the future which could distill this down more, furthering compatibility with JSON-LD (if desirable). Although as a novice, I'm not well-versed enough to state whether it wouldn't be compatible as-is (pointing @context to a schema.jsonld at some URI). It might already be.
JSON-LD seems to be useful if you have a bunch of custom schemas, that aren't yet introduced the schema.org where they may be slow on the uptake.
With the format, CHIP-0015 being specified at the root of the metadata, it should be easy to iron any quirks out in the differences in the structure of data.

tl;dr:
"I fully support this additional CHIP. Leveraging schema.org is an obvious choice."

This CHIP is now in Review. Brandt has updated it to include the latest spec, as well as many example files. Please leave your reviews here.
This CHIP will remain in Review status for a minimum of two weeks. After that point, if we have consensus from the community, it will be moved to Last Call before being finalized.

Thanks for putting this together, @BrandtH22!
First of all, using schema.org for additional structured data is a great idea.
Why invent something new when there is such a rich standard already defined.
And I like the backwards-compatible way of how it is integrated, leveraging the data field from CHIP-0007.
From the perspective of MintGarden, so an explorer and marketplace, this CHIP results in two things:

More clarity of what NFTs represent and how they want to be displayed
More work to support all the possible use cases

Apart from the thumbnail use case, which is a big improvement no questions asked, we will probably wait and see which types of data want to be used by creators.
The good thing is that we can always go back and upgrade existing NFTs based on the structured data that was originally provided but ignored.
I'm quite skeptical about the creator/collaborator information being part of the NFT metadata, I see that being the job of DIDs.
Also, this CHIP introduces a lot of use cases where links are embedded in the metadata, making them not as permanent as the ones directly added to the NFT, since they can't be upgraded if the hosting provider goes down.

Thanks for putting this together, @BrandtH22!
First of all, using schema.org for additional structured data is a great idea. Why invent something new when there is such a rich standard already defined. And I like the backwards-compatible way of how it is integrated, leveraging the data field from CHIP-0007.
From the perspective of MintGarden, so an explorer and marketplace, this CHIP results in two things:
* More clarity of what NFTs represent and how they want to be displayed

* More work to support all the possible use cases

Apart from the thumbnail use case, which is a big improvement no questions asked, we will probably wait and see which types of data want to be used by creators. The good thing is that we can always go back and upgrade existing NFTs based on the structured data that was originally provided but ignored.
I'm quite skeptical about the creator/collaborator information being part of the NFT metadata, I see that being the job of DIDs.
Also, this CHIP introduces a lot of use cases where links are embedded in the metadata, making them not as permanent as the ones directly added to the NFT, since they can't be upgraded if the hosting provider goes down.

Thank you for the detailed and thorough review!
Completely agreed that if we can start with thumbnails then see what additional fields are used by creators that will help greatly!
I do know a number of projects are already planning to use the isPartOf and hasPart features as well so I would recommend looking at those.
As for the creator/collaborator, you are correct that DIDs cover part of this but the reason to include the information in the extra data object is for all of those cases where the project DID does not include the information.
The main reason for this type of inclusion is that DIDs will innevitably be limited to creators/projects/organizations and will have difficulty bridging the gap to identify multiple different creators for a specific project or identifying creators of individual parts of an NFT. For example, imagine a musician who is releasing tracks; they would use their own creator DID to mint their NFT but what if they want to acknowledge the production company, the drum stem creator, or their videographer? Current DIDs, royalty split puzzles, and other coin contracts could fill this gap but that would lead to a large amount of additional blockchain data processing. Including the data in the NFTs metadata (potentially to include signatures from each individual creators DID that verifies their association with the project) would drastically reduce this parsing time.
While I believe this is another thing that we can wait to see how the creators in the space are using the fields and it is just another bit of data that schema.org can represent, I personally believe that having this data readily available will be beneficial for the long term.

Thanks for the reviews!
This CHIP is now in Last Call. If no changes are required for the next two weeks, it will become Final.

This CHIP is now Final. No further changes are allowed (other than errata).


Adding custom class with yolo

How to add the 81st item that the network can classify without losing all the 80 categories that already have been trained from the original pre-trained model?

@ARNABKUMARPAN Just follow the readme. It includes all the details.

I am only getting boxes for  the custom class that I added but not getting any box for those pretrained classes

@ARNABKUMARPAN Sorry I really have no clues.


Server does not support secure connection

Hi there!
Is it correct in "lib/protocol/sequences/Handshake.js":
var serverSSLSupport = packet.serverCapabilities1 & ClientConstants.CLIENT_SSL;

or it's better to be this instead?:
var serverSSLSupport = packet.serverCapabilities1 && ClientConstants.CLIENT_SSL;

The single & is correct as it it performing a bitmask operation in that line.


5 | Longest Palindromic Substring | Java

5 | Longest Palindromic Substring | Java -
What will change -
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] Java

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

Please. Can you assign this issue to me?

Hey can u please assign this to me?
Peace :)
pleaseeeeeeeeee

can I work on this? @HanningLin

Thanks @Yashica7 for assigning this to me, will be making a pull request shortly.
Peace :)


change stage physh engine 1.0

Describe your problem here.
Hi, can you please help. I want the stage to change to another one during the song, please write the code. it's like the whole stage (the same with the decals from the stage, they also became those in another stage) became another stage right during the song.
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

I need this too because I tried some that already exist but didn't work, I want to be like the change character event

You can use stage as character to background. I making my own mod and without any code now the background is changing. I just made background as character


Cross-compilation for windows from linux

Is it possible to rebuild electron from linux environment and package it then using electron-packager?

This is most likely not easily possible, sorry - I'd love to be wrong though!


Fix syncSecondaryToCommit Update for SQL MIAA

SyncSecondaryToCommit now a part of az sql mi-arc update
Update field for SyncSecondaryToCommit now has a limit of 2

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.001%) to 41.684%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/azcli/src/az.ts
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.001%

Covered Lines:
27832

Relevant Lines:
62205

💛  - Coveralls


Add tests for the DNS Records functionality

Description
This PR adds tests for the DNS Records functionality.
Types of changes
What sort of change does your code introduce/modify?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Adding tests for the existing functionality.

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

small nitpick, otherwise looks good thanks! we can extend this to cover different record types in the future.

I really appreciate you for reviewing the PR. Yeah, right now I'm just intending to add tests for those functionalities that didn't have tests at all.


ValueError: After taking into account object store and redis memory usage, the amount of memory on this node available for tasks and actors (-2.96 GB) is less than -17% of total. You can adjust these settings with ray.init(memory=, object_store_memory=).

python paper_experiment_sdcfr_vs_deepcfr_h2h.py
************************** Initing args for:  EXPERIMENT_SD-CFR_vs_Deep-CFR_FHP   **************************
Running with  20 LearnerActor Workers.
Traceback (most recent call last):
File "paper_experiment_sdcfr_vs_deepcfr_h2h.py", line 75, in
n_iterations=150,
File "/Users/d.saienko/Data Science/Deep-CFR/DeepCFR/workers/driver/Driver.py", line 21, in init
chief_cls=Chief, eval_agent_cls=EvalAgentDeepCFR)
File "/Users/d.saienko/anaconda3/lib/python3.7/site-packages/PokerRL/rl/base_cls/workers/DriverBase.py", line 35, in init
self._ray.init_local()
File "/Users/d.saienko/anaconda3/lib/python3.7/site-packages/PokerRL/rl/MaybeRay.py", line 44, in init_local
object_store_memory=min(2 * (10 ** 10), int(psutil.virtual_memory().total * 0.4)),
File "/Users/d.saienko/anaconda3/lib/python3.7/site-packages/ray/worker.py", line 1323, in init
head=True, shutdown_at_exit=False, ray_params=ray_params)
File "/Users/d.saienko/anaconda3/lib/python3.7/site-packages/ray/node.py", line 149, in init
self.start_head_processes()
File "/Users/d.saienko/anaconda3/lib/python3.7/site-packages/ray/node.py", line 571, in start_head_processes
self.start_redis()
File "/Users/d.saienko/anaconda3/lib/python3.7/site-packages/ray/node.py", line 419, in start_redis
self.get_resource_spec(),
File "/Users/d.saienko/anaconda3/lib/python3.7/site-packages/ray/node.py", line 240, in get_resource_spec
self._ray_params.redis_max_memory).resolve(is_head=self.head)
File "/Users/d.saienko/anaconda3/lib/python3.7/site-packages/ray/resource_spec.py", line 195, in resolve
int(100 * (memory / system_memory))))
ValueError: After taking into account object store and redis memory usage, the amount of memory on this node available for tasks and actors (-2.96 GB) is less than -17% of total. You can adjust these settings with ray.init(memory=, object_store_memory=).

Is there any way to config allocated memory?

It can be fixed due to clone repository of PokerRL and edit file PokerRL/rl/MaybeRay.py


conf-notes.txt

Resin specific images available: multiubivol
Let us discuss the image format name here.

So can we close this as it is not needed?


Can you please specify the license this software is released under

Our company can't use this without a published (and hopefully permissive) license attached to the project.
MIT and apache are grand, if you're looking for suggestions.

distribued under Apache Software License 2. (as noted in pom.xml)

Added https://github.com/logpresso/CVE-2021-44228-Scanner/blob/main/LICENSE

Amazing, thanks!


Basic Schemes for template

Need discussion to have the final schemes on iOS template.

{{Project Name}} Debug: Staging environment with development provisioning profile
{{Project Name}} Staging: Staging environment with Ad-hoc distribution provisioning profile
{{Project Name}} test suite: Configured for both Unit Tests and UI Tests
{{Project Name}} unit tests: Configured for Unit Tests
{{Project Name}} ui tests: Configured for UI Tests
{{Project Name}}: Production level for releasing to App Store

Reference: https://github.com/nimblehq/ios-templates/wiki/Project-configurations
The recommended schemes that we should have in a project:

{{ProjectName}}
{{ProjectName}}Staging
{{ProjectName}}SIT (optional)
{{ProjectName}}UAT


some apis are available on Illumos which are not available on stock S…

…olaris
thus availability evelavated from cflags. discard some sporadically for large pages
support mainly.

Thanks. A bit of a shame we need to do this in both os.c and static.c but I agree it is better than doing it project wide.
It will look a bit shorter if we just  #undef _XOPEN_SOURCE and #undef _POSIC_C_SOURCE always (no matter if defined before) if __sun is defined. I think this gives no warnings?


Added optional percentage rounding

If that works fine for you, with no errors, could you merge to master? :)

Done.
How did you find this project?

I was going to create a function for it, but I was going to use it in several projects, so I decided I'd make a library for it. In my research for that, I found this. Any plans to release on PyPi?

Yeah I was making it for one of my projects because no one else had.
I'm working on preparing it for PyPI. Check out that branch if you have any improvements.

Ooh, you've made quite a few improvements. I'll take a proper look later :)


support error boundaries?

inspired by fiber, dio v5.2.0 might introduce error boundaries, this issue will document possible implementation details.
class Foo extends dio.Component {
    componentDidThrow (err) {
        switch (err.location) {
            case 'componentDidMount': return h('h1', 'something bad happened in did mount');
            case 'render': return h('h1', 'something bad happened in render');
        }
    }
    componentDidMount () {
       throw 'pawned!';
    }
    render () {
        return h('h1', 'Hello World');
    }
}

After componentDidMount throws, it will first render nothing from the Foo component and continue to the end of the stack at which point it will then re-try to render the Foo component, if it still fails it will then capture the error and pass it to componentDidThrow if it exists, if componentDidThrow returns something that can render(element/string/array) dio will render that else continue to render nothing. If componentDidThrow is not defined it fallbacks to the default error handler that prints a console.error of the error and continues to render nothing.
Dio caught an error thrown by "Foo", the error was thrown in "componentDidMount".

The object passed to componentDidThrow will have the shape
{
    from: 'Foo',
    location: 'componentDidMount',
    message: 'pawned!',
    stack: 'js stack trace...'
}

render, lifecycle methods and callbacks passed to setState and forceUpdate will fall within the areas that are supported by error boundaries.

Interesting. Would this be development only?

@lukeed both development and production since it's more useful in production in reducing single points of failure that could take down a whole app.


Adding auto validation, and fixing interception issue

Coverage remained the same at 100.0% when pulling f55202698cf407f12f1a38ea2d5df737e2321ecb on ktutnik:master into 2d47a3ec4b33b67e1612dc871fd92b180afb5cfc on kambojajs:master.


(PUP-8045) Add support for Fedora 26 to the dnf provider

The default package provider should be set to use dnf on Fedora 26.

CLA signed by all contributors.

thanks!


V4 "Self Aggregating" Aggregates

Child of #1610
Tasks:

[ ] Auto-resolve in EventGraph on demand
[ ] Support private constructors

Duplicate issue, nothing to see here....


How to set user display name?

I want to change  user DisplayName
How?
bruh i dont know how to add label "help wanted" to this

I'm not actually sure what you're asking. You mean from the Authentication call? Typically, you'd want them to put in their own display name so they can choose what they want; then, when they are Authenticated, you'd associate their user ID from the Authentication with the name they chose, store that in the Realtime Database, and use it from that point on: when they authenticate, you then go get their appropriate display name. This is not really a question for the plugin though.

I'm not actually sure what you're asking. You mean from the Authentication call? Typically, you'd want them to put in their own display name so they can choose what they want; then, when they are Authenticated, you'd associate their user ID from the Authentication with the name they chose, store that in the Realtime Database, and use it from that point on: when they authenticate, you then go get their appropriate display name. This is not really a question for the plugin though.

This answer doesn't stand out, as you can see there https://firebase.google.com/docs/reference/rest/auth?hl=en#section-update-profile there is a method that indeed does what the user originally asked. I would love to see it implemented, and I will do it for myself if needed.

I'm not actually sure what you're asking. You mean from the Authentication call? Typically, you'd want them to put in their own display name so they can choose what they want; then, when they are Authenticated, you'd associate their user ID from the Authentication with the name they chose, store that in the Realtime Database, and use it from that point on: when they authenticate, you then go get their appropriate display name. This is not really a question for the plugin though.

This answer doesn't stand, as you can see there https://firebase.google.com/docs/reference/rest/auth?hl=en#section-update-profile there is a method that indeed does what the user originally asked. I would love to see it implemented, and I will do it for myself if needed.

If you had just looked at @fenix-hub's PR conveniently linked, it shows it's already been implemented.


Release 0.25

Coverage remained the same at 89.416% when pulling c8977df3e9ad5de2de1dca3bdcd37cbd9959f96c on mirceaulinic:RELEASE0.25 into ccf875019187affa60eea15ca3f82582fc4a7a9d on fooelisa:master.


Feature request

Hey dude,
This is awesome can you add a feature to log buckets it has found please?
if i get time ill see if i can throw a PR request.

Will add something. In the meantime you can just python bucket-stream.py > buckets.txt 2>&1 &

Thanks @Ekultek - how do you feel about creating a csv instead? bucket_url,owner

also want to say how bad ass this tool is - awesome job

I think a csv would kind of defeat the purpose of a log file since there is not always going to be a known owner of the site @eth0izzle

#3


Not able to setup Storage explorer locally on my machine

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.30.0
Regression From
No response
Architecture
x64
Storage Explorer Build Number
No response
Platform
Windows
OS Version
Windows
Bug Description
Unable to retrieve child resources
ProducerError:{
"name": "FetchError",
"message": "request to https://dbstorage22mbvml7pfczo.blob.core.windows.net/?comp=list&include=metadata failed, reason: self signed certificate in certificate chain",
"stack": "FetchError: request to https://dbstorage22mbvml7pfczo.blob.core.windows.net/?comp=list&include=metadata failed, reason: self signed certificate in certificate chain\n    at ClientRequest. (C:\Users\NAIKRAK\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\node_modules\@storage-explorer\blob-extension\dist\src\index.js:2:2834516)\n    at ClientRequest.emit (node:events:513:28)\n    at TLSSocket.socketErrorListener (node:_http_client:502:9)\n    at TLSSocket.emit (node:events:513:28)\n    at emitErrorNT (node:internal/streams/destroy:151:8)\n    at emitErrorCloseNT (node:internal/streams/destroy:116:3)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)",
"type": "system",
"errno": "SELF_SIGNED_CERT_IN_CHAIN",
"code": "SELF_SIGNED_CERT_IN_CHAIN"
}
Steps to Reproduce
Launch explorer and try to setup
Actual Experience
Unable to retrieve child resources
ProducerError:{
"name": "FetchError",
"message": "request to https://dbstorage22mbvml7pfczo.blob.core.windows.net/?comp=list&include=metadata failed, reason: self signed certificate in certificate chain",
"stack": "FetchError: request to https://dbstorage22mbvml7pfczo.blob.core.windows.net/?comp=list&include=metadata failed, reason: self signed certificate in certificate chain\n    at ClientRequest. (C:\Users\NAIKRAK\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\node_modules\@storage-explorer\blob-extension\dist\src\index.js:2:2834516)\n    at ClientRequest.emit (node:events:513:28)\n    at TLSSocket.socketErrorListener (node:_http_client:502:9)\n    at TLSSocket.emit (node:events:513:28)\n    at emitErrorNT (node:internal/streams/destroy:151:8)\n    at emitErrorCloseNT (node:internal/streams/destroy:116:3)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)",
"type": "system",
"errno": "SELF_SIGNED_CERT_IN_CHAIN",
"code": "SELF_SIGNED_CERT_IN_CHAIN"
}
Expected Experience
No response
Additional Context
No response

@zachdialwynnlasvegas can you give using system proxy setting a try? You can read more about it here: https://docs.microsoft.com/en-us/azure/storage/common/storage-explorer-network#use-system-proxy-preview

Closing due to lack of response. This issue will no longer be monitored. If you are still encountering this issue we recommend opening a support ticket from the Azure portal. Alternatively you can open a new issue here.


bottlerocket custom cluster-dns-ip doesn't work in ec2nodeclass userdata

Description
Observed Behavior:
When using the following EC2NodeClass, karpenter should set cluster-dns-ip to <IP_ADDRESS> (that's a random ip address I chose to use with nodelocaldns):
apiVersion: karpenter.k8s.aws/v1beta1
kind: EC2NodeClass
metadata:
  name: karpenter-cpu
spec:
  amiFamily: Bottlerocket
  amiSelectorTerms:
  - name: bottlerocket-aws-k8s-1.27-x86_64-*
  ....
  userData: |
    [settings.kubernetes]
    cluster-name = "infra-dev-1"
    cluster-dns-ip = "<IP_ADDRESS>"

However, after karpenter created a Bottlerocket node based on that EC2NodeClass, here is the resulting UserData (as seen in the EC2 console) :
[settings]
[settings.kubernetes]

cluster-name = 'infra-dev-1'
cluster-dns-ip = '<IP_ADDRESS>'

Expected Behavior:
karpenter should set the cluster-dns-ip to the specified value. I don't think there's a particular issue with my setup, as other values like cluster-name are set correctly based on what was specified in the EC2NodeClass.
Versions:

Chart Version: 0.32.3
Kubernetes Version (kubectl version): 1.27 (EKS)

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

I agree that it's a bit odd that Karpenter will override a field that you specified in your custom UserData with a discovered value. Right now, what's happening is that Karpenter is trying to discover ClusterDNS for the cluster that Karpenter is running on and use that value when launching new nodes (see https://github.com/aws/karpenter-provider-aws/blob/main/pkg/providers/amifamily/resolver.go#L192).
Realistically, I do agree that we should probably respect values in the following order of precedence:

Values specified in your custom userData
Values specified in your kubelet config
Default values discovered by Karpenter.

As a workaround for now, I'd recommend that you set the ClusterDNS through the KubeletConfig in the spec.template.spec.kubelet.clusterDNS field.

I agree that it's a bit odd that Karpenter will override a field that you specified in your custom UserData with a discovered value. Right now, what's happening is that Karpenter is trying to discover ClusterDNS for the cluster that Karpenter is running on and use that value when launching new nodes (see https://github.com/aws/karpenter-provider-aws/blob/main/pkg/providers/amifamily/resolver.go#L192).
Realistically, I do agree that we should probably respect values in the following order of precedence:

Values specified in your custom userData
Values specified in your kubelet config
Default values discovered by Karpenter.

As a workaround for now, I'd recommend that you set the ClusterDNS through the KubeletConfig in the spec.template.spec.kubelet.clusterDNS field.

Thank you for the explanation and the workaround. It works fine by setting the ClusterDNS in the NodePool's kubelet config 👍🏻

@jonathan-innis I have a similar error, but In my case the parameter is in EKS Cluster layer. The documentation say that Karpenter override this field, but In this case is overriding wrong.
I opened a issue for it: https://github.com/aws/karpenter-provider-aws/issues/5702
Can you help me, please?

@nikoul Do you know why the Karpenter discovered value was wrong in your case? It sounds like there was an issue with the service IP that was discovered? Specifically, it sounds like you have the kube-dns service that was running on <IP_ADDRESS> in the cluster and that's what Karpenter passed through, though somehow that's inaccurate with the actual state of your cluster. Do you know why this value isn't accurate for you?

@jonathan-innis given that <IP_ADDRESS> is from link-local unicast cidr, it's most likely @nikoul wants to set up node-local-dns. At least I got similar problem with inability to override cluster-dns-ip via userData, which lead me here.
node-local-dns runs as deamonset, uses kube-dns as upstream and provides dns cache for node. In this configuration kube-dns is needed and present in cluster, but it isn't used by pods directly.

Hi
can someone help me resolve the issue that my nodeclaim not getting initize duo to ec2nodeclass userdata below
userData: |
[settings.kernel.sysctl]
net.ipv4.conf.all.send_redirects = 0
Here i need to change the sysctl variable values using userdata .

In general - I was surprised to find that Karpenter overwrites settings we pass in via UserData. I feel like that anything the user supplies should become the ultimate setting, without exception. Is there room for a discussion on this behavior?


tcmalloc_minimal MinGW-w64 target

https://github.com/Alexpux/MINGW-packages
The mingw-w64 package would make tcmalloc available on Appveyor-CI and Windows.

Hi. Can you please elaborate what this ticket is about? I.e. what exactly needs to be done to close this ticket ?

Hi,
I think PKGBUILD for tcmalloc from gperftools git repo would be enough.
For example I got this one from Arch, (but didn't do much with it):
https://github.com/rakhimov/MINGW-packages/commit/e427ca96ea4f73509dd23a25501f05e8367e17e3

Well, sure, do whatever packaging you want. But how is that something that needs gperftools ticket?


Added Hebrew language to Nutshell.language

Added Hebrew to Nutshell.language in the nutshell.js file.

Just so you know, it says in the README that she is not accepting pull requests.

“That said, I'm accepting two kinds of Pull Requests! 1) Bug fixes, and 2) Translations.”

“That said, I'm accepting two kinds of Pull Requests! 1) Bug fixes, and 2) Translations.”

Ah! My bad. Sorry.

Hi @Adiveler ! Sincerest apologies it took me two months to finally getting around to pulling this (my inbox and schedule has been a mess), I super appreciate you translating this and making Nutshell accessible to more folks. Thank you again so much! 👍

Better late than never.
Thank you very much 😃


Broken Demo!

http://themes.gohugo.io/material-docs --> The demo link is broken!

Hello @onrea,
I know that the current demo of the Material Docs theme is broken. The stylesheets aren't loaded completely - the end is always chomped. I'm searching for the source of this odd behavior but wasn't successful so far.
However, for this reason I hosted a demo myself. The theme itself is not broken and can be used without any issues like in the demo.
PS: This repository doesn't contain the source code for this theme. Look here :wink:


flickr.photos.getRecent NoMethodError

Hello guys, first of all, thanks for this awesome gem abstraction!
I've experiencing a strange behavior with the flickr.photos.getRecent method. Sometimes it pass on my tests, but sometimes it breaks. This is how I'm using it:
flickr.photos.getRecent(page: @page, per_page: 200)

And sometimes I get this error exception/message:
NoMethodError:
       undefined method `split' for #<FlickRaw::Response:0x00000005010f68>
     # /home/gustavo/.rvm/gems/ruby-2.3.3@stock_images/gems/flickraw-0.9.9/lib/flickraw/request.rb:13:in `build_request'
     # /home/gustavo/.rvm/gems/ruby-2.3.3@stock_images/gems/flickraw-0.9.9/lib/flickraw/api.rb:37:in `block in build'
     # /home/gustavo/.rvm/gems/ruby-2.3.3@stock_images/gems/flickraw-0.9.9/lib/flickraw/response.rb:41:in `block in each'
     # /home/gustavo/.rvm/gems/ruby-2.3.3@stock_images/gems/flickraw-0.9.9/lib/flickraw/response.rb:41:in `each'
     # /home/gustavo/.rvm/gems/ruby-2.3.3@stock_images/gems/flickraw-0.9.9/lib/flickraw/response.rb:41:in `each'
     # /home/gustavo/.rvm/gems/ruby-2.3.3@stock_images/gems/flickraw-0.9.9/lib/flickraw/api.rb:37:in `build'
     # /home/gustavo/.rvm/gems/ruby-2.3.3@stock_images/gems/flickraw-0.9.9/lib/flickraw/api.rb:55:in `initialize'
     # /home/gustavo/.rvm/gems/ruby-2.3.3@stock_images/gems/flickraw-0.9.9/lib/flickraw.rb:22:in `new'
     # /home/gustavo/.rvm/gems/ruby-2.3.3@stock_images/gems/flickraw-0.9.9/lib/flickraw.rb:22:in `flickr'

I can't figure out why this method sometimes works and sometimes not. Especially because I'm using VCR for record the API calls, so I believe that if it works one time, should works always.
My application is an sinatra (1.4.8) app with Ruby 2.3.3 and flickraw (0.9.9). For tests, I'm using rspec (3.5.0), airborne (0.2.7) and vcr (3.0.3) gems.

I've figured out and solved this issue, the "problem" it was related with the VCR gem. The Flickr request query is passed on body and by the default the VCR only matches the request by the URI and the verb. So, it was necessarily to match the request by the body too.


Logs flooded with "[warning] accept() failed"

Under certain circumstances when RaSCSI is running with token auth enabled, it gets stuck in a state where it's spitting out hundreds of these messages every second, freezing other processes running on the Pi, until systemd kills it.
Dec 21 11:20:48 rascsi3b RASCSI[5645]: [2021-12-21 11:20:44.354] [warning] accept() failed
I think it happens when a client repeatedly tries to authenticate with either no token, or the wrong token.

@rdmark This error is a socket-related one, I don't think it has anything to do with the authentication, because the authentication is not a low-level (socket-related) feature. It´s part of a message like the device ID etc. and has no special (technical) meaning.

I have yet to reproduce this again, and noone in the community has complained. Closing for now!


Fix issue 7967

This checklist is used to make sure that common guidelines for a pull request are followed.

[X] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[X] I adhere to the Command Guidelines.

@mentat you will need to resolve the conflict for the CI to kick off.

Done, thanks.


Inner styles in SVG are not getting overwritten

This code
circle(1).fill_color(papaya).fill_color(black)

generates a black circle when rendered as PNG and a papaya one when rendered as SVG. The expected behaviour should be the former. The generated SVG code seems correct:
<g style="fill: #000000;"><g style="fill: #ff9700;"><g style=";" transform="scale(1)"><circle cx="0" cy="0" r="1" /></g></g></g>

Should we resolve the styling prior to rendering? Or is there a simpler solution?

I think the best way to handle this is to pass a chalk Style object to render_svg in a similar way as Transform is passed to get_bounding_box. Each subclass can then know the global style state.


Add to README distinctions between this library and hashicorp/golang-lru

This cache is heavily inspired by hashicorp/golang-lru simplelru implementation.

How does it differ?

I've added expirable LRU to hashicorp/golang-lru in https://github.com/hashicorp/golang-lru/pull/116, I'll try to figure out what is the difference and write it to the readme.


124643

Hello dear community
I have now switched to the emulated HUE and Alexa finds all the devices
Unfortunately, Alexa always says the value is outside the device
I already deleted all files.
The port is at 80.
I own 3x Alexa Generation 3
and a generation Alexa 1
I can not find the error to make everything controllable with HUE.
About home Assistant works without problems but with the speech recognition works fine.
In the system I have Osram sockets, Sonoff with Tasmota, Xiaomi sensors, etc.
To start the Emulated Bridge I have the following in my config:
emulated_hue:
listen_port: 80
I have no errors in the log files or in the system.
Maybe I have a thinking mistake?
Thank you very much
Ghostsl

This is the issue tracker for the Home Assistant Documentation.
Please report Home Assistant issues at https://github.com/home-assistant/home-assistant/issues/new or use the forum for questions about installation, setup, configuration and usage.


fix website render issue on < and >

Description
Fixes #12168
Fixes #11438
Comments
I didn't hear back yet from @piiswrong  about the purpose of this particular line. However, removing it fixes two documented render issues, and I don't see any negative effects after removing the line.
Preview
http://<IP_ADDRESS>/versions/tag_render/

@piiswrong - You authored it earlier, can you please suggest if this will not break other expected behavior?

Merging this PR, as it fixes couple of issues and I couldn't hear back from Eric. Verified on the rendered site, did not find any issues.


[Bullet] Wrong physics when accelerating and braking using VehicleWheel

The spring physics of the vehicle wheel or body is wrong. When accelerating and braking, the vehicle tilts forward or backward. However this is done in the opposite direction from what is natural.
Using a simple setup with a vehicle body and 4 wheels and a static ground plane.

When applying an engine force to the vehicle, the vehicle tilts forward. In real life the vehicle would tilt backwards.

When braking the vehicle tilts backwards. In real life the vehicle would tilt forward.

Here is an example of a vehicle braking

Can anyone still reproduce this bug in Godot 3.2.3 or any later release?
If yes, please ensure that an up-to-date Minimal Reproduction Project (MRP) is included in this report (a MRP is a zipped Godot project with the minimal elements necessary to reliably trigger the bug). You can upload ZIP files in an issue comment with a drag and drop.

Couldn't reproduce the issue in 3.2.3. Tilting works well. Recording :
https://user-images.githubusercontent.com/54415525/110321977-7090e500-8038-11eb-8943-bf920f822dd5.mp4

So closing as resolved. If you can still reproduce in Godot 3.2.4 rc3 or never, comment with a reproduction project.

For me, this problem exists in all versions, including 3.3.3. I'm attaching a video. The BastiaanOlij project can be used for a test project, where the horizon changes downwards during acceleration: https://github.com/BastiaanOlij/vehicle-demo/tree/Part-4
https://user-images.githubusercontent.com/63282037/133959509-45662d06-ec57-4566-b424-3800c5135dbe.mp4
If necessary, I could do a separate project, but I use Bastian's code here.

Reopening as per above comment.

Same for me as of now. Version 3.4.4 Steam version.

@mojoyup Please upload a minimal reproduction project to make this easier to troubleshoot.

@mojoyup Please upload a minimal reproduction project to make this easier to troubleshoot.

Interestingly, I created a simplified test project, same version and it seems to work.
I will try to find out in my original what could have caused this and report back, in case anyone has this issue also.
What happened with mine was, when I was changing the VehicleWheel Radius (I scaled everything down, even the models/meshes), then it seems to be "backwards".
The project before scaling and resizing the VehicleWheels worked but Ill try to get more details for it if needed.

VPTest.zip
This is the test file. This works if anyone wants to use this

Rule of thumb for physics bodies/collision shapes is NOT to scale them!

The VehicleWheels have the option for such in the parameters. The others were not scaled in the editor, but in Sketchup.

I think I might be able to ahve this closed. I figured out one thing that affects the physics this way. It is the different in the transforms of the parent node (Vehicle), and the children nodes (most likely and mainly the wheels and main collision). I have always put my origin of the children nodes to where the parent node sits on the ground for better control. If it is too exotic of a difference between the parent node Y pos and the children Y pos', Itll start to behave different. I hope that makes sense.
TL/DR: Try to reset the transforms of the children and the parent node(Vehicle) and test/tweak


Remove dup package ref

Noticed in passing.

How was this a duplicate package ref?
WindowsServiceHelpers and UseWindowsService is clearly defined in Microsoft.Extensions.Hosting.WindowsServices.
If I download and build the project it now fails:
error CS0234: The type or namespace name 'WindowsServices' does not exist in the namespace 'Microsoft.Extensions.Hosting' (are you missing an assembly reference?)
I think you wanted to remove the implicit reference to Microsoft.AspNetCore.Hosting.WindowsServices and wanted to leave the reference to Microsoft.Extensions.Hosting.WindowsServices.

Thanks for the catch, @X-Celcius ... I'll fix this right now.


AI specification config and permissions

I have deno tests but when I use the generate tests feature it assumes jest.
It would be nice to have some config file where you can instruct the AI on certain details about the project and give permissions.
For example that we use deno bdd testing and the test folder can be found at this location of the workspace.
When generating tests it then understands that context.
This can also be used for other scenarios where you want to give access permissions and define parameters.

What version of the extension/vscode are you using? Also do you already have any existing test file? Would it be possible to share you workspace (or a simplified version of that)


Improve documentation for hats.

I am trying to use hats myself, but I am having a hard time understanding the documentation. I I understand that there is supposed to be another file, but not entirely sure how it all ties in. Any insight? I can update the docs once I fully understand.

Sorry for the docs lacking on hats, essentially hats allow a developer to put their own configuration on top of a repo's .sail/Dockerfile environment.
So if you like zsh, you can change your shell to zsh. If you have certain apt packages that you like to include in all of your environments, you can add that to your hat as well. If you store your ~/.gitconfig or ~/.ssh keys at uncommon locations, you can mount those in through share labels using the correct source.
Basically it just allows the developer to personalize every project environment they work on so that they don't have to leave their favorite tooling and configuration behind.

That is totally understandable, but how do I use them? I tried the example on sail.dev (also, in the repo somewhere and it did not seem to work as expected ). I kept getting the error in issue #178 (when it was actually attempting to apply) and sometimes it would simply just not apply. The proper command is -hat, right?

was going to work on this, but my knowledge is still very vague of hats. If someone could pick it up, that would be good.

I'd also like to see an improvement on the documentation here. It's not clear on how to get started or an example of a hat that adds something custom to the existing .sail/Dockerfile

Sorry about the lack of documentation regarding hats. You can check the hat-examples directory in this repository for a couple of simple hats you could use.
Then to install a hat, just put a Dockerfile in an empty folder somewhere on your computer. You can use default_hat in your configuration file or sail run --hat path/to/hat. The path should be the path to the folder holding the Dockerfile.
e.g.:
$ ls ~/sail
Dockerfile

$ sail run --hat ~/sail cdr/sail
...


Add raises matcher

I expect I've missed some edge cases in the tests!

Also - an attempt to cover #5

Also -
    assert_that(lambda: func("arg"), raises(Exception))

vs.
    assert_that(lambda: func("arg"), raises(instance_of(Exception)))

the implementation for catching the expected exception when calling the lambda (first) seemed more obvious than catching the exception then matching the type (second -  matching with instance_of).
Alternatively phrased, would you ever expected raises to be an instance_of something not an exception?
If there is a case where raises(MyException) is less favourable than raises(instance_of(MyException)) could you describe it and I'll update and cover in the tests.

Also cf hamcrest implementation;
assert_that(calling(parse, bad_data), raises(ValueError))


Add new demo based on Designer News

Main endpoint:
https://news.layervault.com/?format=json

[x] Show posts
[x] Show comments for a post

Fixed! https://github.com/hyperoslo/Sync/tree/master/Examples/DesignerNews