Skewed bounding boxes

Hello,
When supplying the bounding boxes, I noticed that the degraded bounding boxes are not what I really imagined them to be.

The red text and the bounding boxes are what I pulled out of the original pdf, before degrading using Augraphy.
Shouldn't the degraded boxes be the ones I outlined in blue, so the whole original object is outlined?
This is even more obvious when you look at it at the larger scale:

The larger bounding box around the table is supposed to encompass the table, but here we can see that some of the textual boxes are now outside of the actual area of interest.
Is this a feature or a bug?

Hi, so as in the documentation, only the start point and end point of the box are affected:
https://augraphy.readthedocs.io/en/latest/doc/source/augmentations/folding.html
So this should be consistent with your observation?

Yes, this is exactly what is stated in the docs, so I guess this is a feature, not a bug :).
Hovewer the second image I uploaded is a mix of Geometric and Folding, and with the larger bounding box, this is mostly an "issue" with the rotation. I would say that the correct way would be rotating the bounding box, then getting the bottom left and the top right coordinate and using that as the new bounding box.
If you were to label the table in the second image, where would you put the rectangle? I think you want to encompass the whole object.
I am not a computer vision specialist, so I'm not sure what the correct way is, so this issue is maybe just opening a debate how the bounding box computation should be approached

Right, there should be a better solution to this problem. For example, for clockwise rotation, it should take top-left and bottom-right of the box, while for anticlockwise rotation (your example), it should take top-right and bottom-left of the box.
Thanks for pointing this out. So probably you can submit a pull request too if you are able to create a better alternative to address on this problem.

Yeah, the bounding box should just be the (min(all_x), min(all_y), max(all_x), max(all_y)) in my opinion.
Im currently very low on time, but I might give it a crack in a few months!
Feel free to close this, thanks :)


GUI flashing/blinking

hello,
I have issues with the GUI that keeps on blinking and flashing, with or without moving the mouse and whether in full screen or not.
see attached screenshots.
I just installed the Windows version 1.2.0, and the PC is running Windows 10 Prod 22H2.
The dependencies have been checked (NPCAP  1.75 installed as advised and environment variables added to the NPCAP SDK folder)
I will try to find another computer, running a different version of Windows OS to check.
anyone has/had the issue?

This is a known issue which happens on some system not supporting the default wgpu renderer.
I've created a version of the app which uses another renderer (glow) which usually solves the problem.
Check https://github.com/GyulyVGC/sniffnet/issues/218 to know more about this issue. There you will find a file to download which contains the same version of the app but using the alternative renderer.
Let me know if this solves the problem.

Thank you very much, it's working great now.
Sorry for the duplicate

Thank you very much, it's working great now.
Sorry for the duplicate

I'm happy it's working!
Don't worry 🙌


Move off jenkins

I've had it with jenkins. it's so painful to work with. I want to move off. It's currently broken-- it isn't building go-ipfs properly.
I really like golang's build system: http://build.golang.org -- it is just https://github.com/golang/build -- ideally we could run our own version of that, equipped with ipfs to avoid re-downloading things multiple times (i.e. so tests get even faster). This sounds non-trivial to setup...
So perhaps in the meantime we could try to use travis for everything we do in jenkins. This may not work, particularly:

race tests will crawl or may just fail on travis
not sure if container tests (3nodetest) will work.

The jenkins tests in question are:

test_sharness_expensive ideally with fuse
build_docker_image to check it works
build_all_commits to check all commits build (probably redundant given test_all_commits)
test_go
test_3node requires containers
test_go_race likely to be very slow
test_all_commits runs make test on all commits.
test_go_integration runs some integration tests

I think that -- instead of only testing make test on all commits, we should instead:

for every commit:

go test
go test race
sharness (expensive)
build docker image
integration tests

This might be as simple as making the repo test all these pieces and using travis.

@whyrusleeping @chriscool thoughts?

First, yeah it is a good idea to test every commit as much as possible, at least as long as it doesn't take too much time.
If Travis works well, it looks like a good idea to do as much as possible using it.
Can FUSE tests be done on Travis too?
As some tests cannot be done on Travis, maybe we can keep Jenkins only for these tests or use something else like http://buildbot.net/.

could take a look at teamcity: https://www.jetbrains.com/teamcity/

i'd prefer a service (that we don't have to manage) and something very
tightly integrated with the open source workflow.
On Wed, Apr 1, 2015 at 1:53 PM, Jeromy Johnson<EMAIL_ADDRESS>wrote:

could take a look at teamcity: https://www.jetbrains.com/teamcity/
—
Reply to this email directly or view it on GitHub
https://github.com/ipfs/infrastructure/issues/9#issuecomment-88628084.

I think we should:

try to do it all on travis first, have that as something to fallback to always.
from there, we can see about circleci and codeship, which both claim to integrate with github + open source well.

closing in favor of https://github.com/ipfs/infrastructure/issues/20


City with county code not found by OpenWeatherMap API

This is due to a bug in openweather-apis. I will submit a PR for the dependency.

https://github.com/CICCIOSGAMINO/openweather-apis/pull/34

Nevermind, I will replace the dependency completely in the next release to support a lot of new condition values.


Transform response body

Hi there,
first of all, I'd like to thank you for offering this awesome method of scripting for the krakenD gateway. I am a complete novice considering go and lua, but I got some nice things working with only small effort.
Sadly I got stuck now and struggle to find appropriate documentation. I hope it is ok to open an issue here even if it is mainly a question on how to do things.
For context, this is what I am trying to achieve. I get a json response from a ruby backend with snake case keys like this:
{
  "items": [
    {"id": 1, "name": "foo", "funny_property": true, "long_name": "foo bar"},
    {"id": 2, "name": "foo2", "funny_property": false, "long_name": "foo2 bar2"},
    ...
  ]
}

And I want to prepare it for the javascript frontend which likes to have it's json with camelCase like this:
{
  "items": [
    {"id": 1, "name": "foo", "funnyProperty": true, "longName": "foo bar"},
    {"id": 2, "name": "foo2", "funnyProperty": false, "longName": "foo2 bar2"},
    ...
  ]
}

While I think the main algorithm isn't that hard to write (even for a lua novice), I struggle with what data types I really get from methods like: response.load():data():get('items') and what I can do with it. For example while I managed to iterate over this list of items I couldn't figure out how to iterate over every key, value pair of the item itself.
Any hints on tackling this are highly appreciated :)
Thanks for reading so far and have a nice day

I'm not a LUA expert, but I think it could be done using the stdlib. For example, this pair of lines
result, _ = string.gsub("some_var", "(%w)_(%w)", function(w,x) return w..string.upper(x) end)

print(result)

will return
someVar

Ah yes, I see, I should've added more details, sorry about that.
Yes I got that already but what I struggle with is how to reflect about every key from the backend response to even make that tranformation.
So for example I tried iterating over every pair in the items array I mentioned above and got an error, that items is not the right data type table but that it is userdata.
Maybe I just clarify what my question really is: How do I reflect on every key in a backend response without knowing the explicit response? I think this is not really a lua question but more a question on the lua intepreter you guys wrote here.
Please guide me to the right place, if this is wrong here to ask.

you don't need Lua here, just use flatmap_filter:
          "extra_config": {
              "github.com/devopsfaith/krakend/proxy": {
                "flatmap_filter": [
                    {
                        "type": "move",
                        "args": ["items.*.funny_property", "items.*.funnyProperty"]
                    },
                    {
                        "type": "move",
                        "args": ["items.*.long_name", "items.*.longName"]
                    }
                ]
            }
          }

you don't need Lua here, just use flatmap_filter:
          "extra_config": {
              "github.com/devopsfaith/krakend/proxy": {
                "flatmap_filter": [
                    {
                        "type": "move",
                        "args": ["items.*.funny_property", "items.*.funnyProperty"]
                    },
                    {
                        "type": "move",
                        "args": ["items.*.long_name", "items.*.longName"]
                    }
                ]
            }
          }

Thanks for pointing that out, flatmap is indeed helpful for smaller objects. But if I read the docs correctly, there is no way to transform all the properties by reflection, right?


[Release-1.27] - k3s-server creates improper etcd member name

Backport fix for k3s-server creates improper etcd member name

#9521

Issue is not reproducible in k3s. Reproduced it in rke2 here https://github.com/k3s-io/k3s/issues/9521#issuecomment-2018913907
Validated the etcd member name is displayed correctly on k3s version v1.27.12-rc1+k3s1 and rancher version v2.7.12-rc2
ubuntu@shyk3s27-pool1-bef584fb-928lq:~$ k3s -v
k3s version v1.27.12-rc1+k3s1 (78ad5756)
go version go1.21.8
ubuntu@shyk3s27-pool1-bef584fb-928lq:~$ sudo ETCDCTL_API=3 etcdctl --cert /var/lib/rancher/k3s/server/tls/etcd/server-client.crt --key /var/lib/rancher/k3s/server/tls/etcd/server-client.key --endpoints https://<IP_ADDRESS>:2379 --cacert /var/lib/rancher/k3s/server/tls/etcd/server-ca.crt member list -w table
+------------------+---------+----------------------------------------+----------------------------+----------------------------+
|        ID        | STATUS  |                  NAME                  |         PEER ADDRS         |        CLIENT ADDRS        |
+------------------+---------+----------------------------------------+----------------------------+----------------------------+
| 4039854d3de5adf2 | started | shyk3s27-pool1-bef584fb-q4td9-306d2998 | https://<IP_ADDRESS>:2380 | https://<IP_ADDRESS>:2379 |
| a23a6aa1439b4994 | started | shyk3s27-pool1-bef584fb-928lq-092581e5 |  https://<IP_ADDRESS>:2380 |  https://<IP_ADDRESS>:2379 |
| fc56a40a9a3164cd | started | shyk3s27-pool1-bef584fb-skjr9-e0d136ab |    https://<IP_ADDRESS>:2380 |    https://<IP_ADDRESS>:2379 |
+------------------+---------+----------------------------------------+----------------------------+----------------------------+
ubuntu@shyk3s27-pool1-bef584fb-928lq:~$


bump build target to support biginteger and add package-lock back

the main branch stopped building because the package-lock.json wasn't committed.
most likely, someone in some dependency bumped a minor version which introduced BigInteger usage.
this broke vite build because its transpile targets didnt support BigInteger
this bumps vite to a version that has BigInteger since electron has it.
i also added a package-lock.json so this no longer happens in the future.

Was able to get this working anyway by specifying a new ES target, but thanks for taking a look!
We do probably need to get a package-lock.json going at some point


in XCode 7.3 and 8.0 you need to define the ddLogLevel as DDLogLevel

Don't know what has changed, but in XCode 7.3 and 8.0 you need to define the ddLogLevel as DDLogLevel, complier will not accept int .

Thanks for catching this!


v1 branch

Hi, thanks for the package 👍
Could you create a branch from v1.0.40 tag so we could open PRs for fixes in v1 ? :) I see there are a lot of unreleased commits in main with significant refactoring, so we need a way to improve the existing version until that is ready to be released.

Hi
I am curious about your problem and why you do not use the dev-main branch.

dev-main is untagged, unstable and not recommended. That is why we have tags and semantic versioning. We're currently at v1.0.40 which is the latest stable version of this package. There have been many commits made after this tag, but no release and I suspect it is not coming soon 🤔
This package (or at least the version of it tagged at 1.0.40) is built with the assumption of auto-incrementing IDs. This fails in certain cases when UUIDs are used. Would like to try to implement a "fix" so it could be released as v1.0.41 but that now is not possible because main branch has breaking changes and would need to be v2.x. If we have v1 branch we can push fixes to it and tag v1.0.41 on that branch. Thus main branch can continue to evolve and v1 support can continue independently until v2 is released.

Anyways I recommend using dev-main version. I thought no one will use this until make it was ready.
Ok, I will release version 1.x in a few days.

The speed gains are too good not to use 😃 But 1x (1.0.40) is already released? 🤔 Is that by mistake or you mean you will create V1 branch? 🙂

I do not remember anything along the 1.x
all of them should be 0.1.x
If you see 1.x or something, it is by mistype.  😃

Ok that explains it 😃 So yeah there is a 1.0.40 tag by mistake then 🙂

I removed that release on packagist.org, I think should not see it anymore.
Thanks for the report.
This package basically should support migrations so that the fake DB should gain some insights about the default values of columns and type of IDs and etc.

I suspect this will break some people's installs once the cache is gone from packagist as it was the default version install when you run composer require imanghafoori/eloquent-mockery 😄 I'll update our project 🙂

This package basically should support migrations so that the fake DB should gain some insights about the default values of columns and type of IDs and etc.

Maybe, but I still saw places where it does ($lastInsertId ?? 0) + 1 which does not work when that ID is not int :)

I have a lot of changes and features in mind but this heavy project makes me no money and I am also involved with the laravel-micoscope as well. Anyways it was exciting to see that my work is getting used without getting fully ready or advertised.
Makes me motivated to finish it.


C source files not allowed when not using cgo: sqlite3-binding.c

I create an application using this driver and works very well in OSX. Now i want to cross-compile for windows and after type GOOS=windows GOARCH=386 go build i get the following error C source files not allowed when not using cgo: sqlite3-binding.c
I installed all the necessary dependencies through goxc and i cross-compile almost every day to windows. The mentioned issues happens when i use this driver.
Any help appreciated.

See http://www.limitlessfx.com/cross-compile-golang-app-for-windows-from-linux.html

I read it (is in the README) after post this question but im not sure what exactly do on OSX. I already have the native Windows toolchain (it was installed with goxc) but i'm kinda loss in the step 4.
Is there any tutorial or tips of how to do the equivalent thing on OSX without re-install the hole thing ?
Thanks in advance.

Am also seeing this error when running GOOS=linux GOARCH=amd64 go build.

Same. Although, in my case I was trying to use the goose tool on an ec2 box. When I cross compiled on my mac, I got the above error. When I compiled it directly on the linux box, I just got a no buildable Go source files error, because goose depends on this project.
I manually removed all reference to go-sqlite3 (I'm using mysql) and was able to get goose working right away. So this is definitely an issue with this repo if you want to use it on linux amd64.

This binding uses CGO and according to https://golang.org/cmd/cgo/ CGO is disabled by default when cross-compiling. You need to enable it explicitly by setting CGO_ENABLED=1 environment variable.

:+1: @kikht, I just had this issue and it's solved thanks to you ! :gift_heart:

@kikht +1 Tnx

Hi, i have the same problem.
If i set CGO_ENABLED=1 on compile for linux64 or win32 from my windows10, i have the following error:
C:\Users\xxxx\AppData\Local\Temp\go-build414971746\runtime\cgo\_obj\_cgo_main.c:1:0: error: -fPIC ignored for target (all code is position independent) [-Werror]  int main() { return 0; }  ^ cc1.exe: all warnings being treated as errors Error: Process ended with return value 2
Help :)

@Fruchtgummi are you trying cross compiling?

Yes!

Then, you need to use cross compiler not host compiler.

My cross-linux64.env
`# cross-compiler linux amd64
GOROOT=c:\go
GOBIN=%GOROOT%\bin
GOARCH=amd64
GOOS=linux
CGO_ENABLED=1
GO15VENDOREXPERIMENT=1
PATH=C:\mingw-w64\x86_64-5.3.0-posix-seh-rt_v4-rev0\mingw64\bin;%PATH%
LITEIDE_GDB=gdb
LITEIDE_MAKE=mingw32-make
LITEIDE_TERM=%COMSPEC%
LITEIDE_TERMARGS=
LITEIDE_EXEC=%COMSPEC%
LITEIDE_EXECOPT=/C`
It that wrong -> LITEIDE_MAKE=mingw32-make

you need to use C-compiler that can generate ELF binary. Not go compiler.

What?
I use mingw-w64 and also provides ELF binary, I complie other GO programm with C-components -everything goes?? I only have trouble with sqlite3.

Ah, I found this. So currently, you can do this on Windows.
https://github.com/golang/go/blob/master/src/cmd/go/build.go#L3015-L3019

export CC=arm-linux-gnueabihf-gcc-5; \
CGO_ENABLED=1 go build -ldflags "-linkmode external -extldflags -static" \
  -o "./bin/${GOOS}_${GOARCH}/the_app"


Classes/Naming page has a typo in the example code

What convention is being referenced?
Classes/Naming.md
How do you propose this convention could be improved? Please provide rationale and examples if possible.
Current code has a typo of @nd instead of @end, it should be fixed.
@interface XYZObject : NSObject // good: XYZ three letter prefix
@nd

Fixed by #11


Deep sleep issues

If you are using the Xiao ESP32S3 Sense with OV2640 camera you may be experiencing short battery life when in deep sleep mode.  It seems the OV2640 does not go to sleep with the CPU and continues to consume 20mA which would give you 5 hours battery life with a 100mA LIPO.  However, the OV3660 camera can be put into software standby mode before deep sleep which reduces current consumption to about 1.5mA.
You might find the discussion here of interest:
https://forum.seeedstudio.com/t/xiao-esp32s3-sense-camera-sleep-current/271258

I implemented the esp_camera_deinit() in the code  #4, but I don't have the tools to test and measure it.
As far as I can read, the camera is now deinitialized before the CPU.

The consensus view is that esp_camera_deinit does not work, doesn't stop the Ov2640 camera drawing high current and stops the camera working again until power to it is cycled. See my earlier link. Suggest you check how long your battery lasts as I don't know of anybody else who has managed to get low current consumption during deep sleep using a Ov2640 on esp32s3.


Simplify some constructors by delegating to other constructors

For the copy/alloc+copy/alloc+move constructors specify the effects in terms of other constructors as a way of simplifying the specification.
NOTE: That this PR also makes the indirect(std::allocator_arg_t, const Allocator& alloc, indirect&& other) now conditionally noexcept. This is required because the case where alloc != other.get_allocator() may require allocating a new object and move-constructing the new object from *other.
The main question here is whether the post-condition that other is valueless is required to hold.
If it allocates a new object rather than taking ownership of other's object, do we want to force other to become valueless, or just leave it having a value that is in a moved-from state?

I don't think we should force a moved from object to be valueless if allocator mismatch means it can be just moved from.
It's extra work for no benefit. The standard gives us few guarantees about the state of the moves from object but we know it's non-null so valueless_after_move should return false.


question: using Cluster ctor and specifying non-cluster enabled node

Lets assume opts are like this:
    "redisCluster": {
        "hosts": [
            { "host": "localhost", "port": 6379 }
        ],
        "options": {

        }
    },

Then I create cluster connection:
var clusterClient = new Redis.Cluster(config.redisCluster.hosts, config.redisCluster.options);

Redis is 3.x, but cluster mode is disabled for this instances on my local machine. The behaviour in the result is the following:
22:09:53 ng.ark.com: Connected to AMQP
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
  at Cluster.addListener (events.js:160:15)
  at Cluster.once (events.js:185:8)
  at Cluster.<anonymous> (/Users/vitaly/projects/api_v2/node_modules/ioredis/lib/cluster.js:87:10)
  at tryCatcher (/Users/vitaly/projects/api_v2/node_modules/bluebird/js/main/util.js:24:31)
  at Promise._resolveFromResolver (/Users/vitaly/projects/api_v2/node_modules/bluebird/js/main/promise.js:427:31)
  at new Promise (/Users/vitaly/projects/api_v2/node_modules/bluebird/js/main/promise.js:53:37)
  at Cluster.connect (/Users/vitaly/projects/api_v2/node_modules/ioredis/lib/cluster.js:65:10)
  at Cluster.<anonymous> (/Users/vitaly/projects/api_v2/node_modules/ioredis/lib/cluster.js:99:16)
  at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)

(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
  at Cluster.addListener (events.js:160:15)
  at Cluster.once (events.js:185:8)
  at Cluster.<anonymous> (/Users/vitaly/projects/api_v2/node_modules/ioredis/lib/cluster.js:88:10)
  at tryCatcher (/Users/vitaly/projects/api_v2/node_modules/bluebird/js/main/util.js:24:31)
  at Promise._resolveFromResolver (/Users/vitaly/projects/api_v2/node_modules/bluebird/js/main/promise.js:427:31)
  at new Promise (/Users/vitaly/projects/api_v2/node_modules/bluebird/js/main/promise.js:53:37)
  at Cluster.connect (/Users/vitaly/projects/api_v2/node_modules/ioredis/lib/cluster.js:65:10)
  at Cluster.<anonymous> (/Users/vitaly/projects/api_v2/node_modules/ioredis/lib/cluster.js:99:16)
  at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)

I havent really dug into the code, but it seems like .connect is called multiple times and previous event listeners are not removed. Maybe this is specific to the wrong configuration (using cluster ctor on non-cluster node), but maybe not. Should probably look at the error handling here

Looks like to be the same problem as https://github.com/luin/ioredis/commit/f663fe236d4b83d3f836e61748906eb9952a6211. I'm looking into it.


Deprecation warnings - bump cloudposse/s3-log-storage/aws to 0.28.2

I'm getting deprecation warnings:
│ Warning: Argument is deprecated
│
│   with module.alb-logs.module.s3_bucket.module.aws_s3_bucket.aws_s3_bucket.default,
│   on .terraform/modules/alb-logs.s3_bucket.aws_s3_bucket/main.tf line 30, in resource "aws_s3_bucket" "default":
│   30: resource "aws_s3_bucket" "default" {
│
│ Use the top-level parameter object_lock_enabled and the aws_s3_bucket_object_lock_configuration resource instead

~Related to downstream: https://github.com/cloudposse/terraform-aws-s3-log-storage/issues/74
The above has to be done first, then this: https://github.com/cloudposse/terraform-aws-lb-s3-bucket/blob/master/main.tf#L63
has to be bumped after aws-s3-log-storage is released.~
New cloudposse/s3-log-storage/aws is already released under 0.28.2
Versions
terraform 1.0.7
aws provider 4.27.0
cloudposse/lb-s3-bucket/aws 0.16.0

There is a new release cloudposse/s3-log-storage/aws, version should be bumped here from 0.28.0 to 0.28.2


use pro features for nfdi

 use pro in nfdi

bors merge

bors merge

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
30246

Relevant Lines:
35533

💛  - Coveralls


Allow users to update more things directly from the collective page instead of having to go to settings

User story
As a user, I want to be able to edit my social links, short description, team members, etc, directly from the home page. So, I don't have to navigate to the settings page.
Best solution for this problem
Add a button near links that will show a form/modal to update the respective fields.

MVP
Something similar to GitHub.
https://user-images.githubusercontent.com/46647141/144568436-0ffc3b8f-01ae-45fe-afe5-4927ffde0bde.mov
P1 high frequency, high impact

Can I work on this one? @snitin315

I think we will need some input from the design team on this before starting implementation.

Ok

Adding this related comment from @carolineawoolard

As a collective admin I tried for weeks to double click on the text about my group only to give up and think "I guess I can't change it." I want to be able to edit the text about my group directly, as I can edit the logo and image on my page, in addition to going into the settings panel. See this Loom about it

Due to the establishment of the Dashboard it is unlikely that we would enable this functionality. We have been actively moving all functions to the Dashboard. Due to this I will close this issue.


Yale smart alarm .084 fails error

Home Assistant release with the issue: 0.84.1
Operating environment (Hass.io/Docker/Windows/etc.):
hass.io
Component/platform:
https://www.home-assistant.io/components/alarm_control_panel.yale_smart_alarm/
Description of problem:
works fine on first reboot yet then becomes unresponsive and fills the log with the below error
2018-12-13 08:18:16 ERROR (MainThread) [homeassistant.helpers.entity] Update for alarm_control_panel.yale_smart_alarm fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 221, in async_update_ha_state
    await self.async_device_update()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 349, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/alarm_control_panel/yale_smart_alarm.py", line 84, in update
    armed_status = self._client.get_armed_status()
  File "/usr/local/lib/python3.6/site-packages/yalesmartalarmclient/client.py", line 49, in get_armed_status
    alarm_state = self._get_authenticated(self._ENDPOINT_GET_MODE)
  File "/usr/local/lib/python3.6/site-packages/yalesmartalarmclient/client.py", line 92, in _get_authenticated
    data = response.json()
  File "/usr/local/lib/python3.6/site-packages/requests/models.py", line 897, in json
    return complexjson.loads(self.text, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/simplejson/__init__.py", line 518, in loads
    return _default_decoder.decode(s)
  File "/usr/local/lib/python3.6/site-packages/simplejson/decoder.py", line 370, in decode
    obj, end = self.raw_decode(s)
  File "/usr/local/lib/python3.6/site-packages/simplejson/decoder.py", line 400, in raw_decode
    return self.scan_once(s, idx=_w(s, idx).end())
simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Same here. If I restart HA then it seems to work for a while then error continues to repeat as though it's timed out.

Yeah, I believe this is the issue with the refresh token @charlesastaylor solved. I'll double check and get a new version into HA as soon as I can.

All day it's been logging errors at random times. Yet it seem the token last about 12hrs before it expires.
Restarted my HA at 7.30am this morning stoped working now 8.00pm then errors appear in the log every minute

Hi. Yep this looks like a result of the bug I fixed here.
Access tokens expire after 10 hours and due to changes to the Yale API the check to test if this had happened no longer worked so the client never updates it's token and all requests fail. The error itself is a result of calling the requests json() method on an empty response.
The change I made to make use of refresh tokens was actually separate and probably shouldn't have been in the same PR.
@domwillcode Having just checked, I believe a new release needs to be put on PyPI and the HA requirements updated to reflect that.
In the meantime you can manually replace the yalesmartalarmclient/client.py that HA uses to the latest code and it'll work as expected.

Ah, didn't notice your environment. I've never used hass.io so don't know the answer to your question I'm afraid.
Looking at your stack trace though, if you can access the file system (with ssh maybe) the file you're looking to edit is /usr/local/lib/python3.6/site-packages/yalesmartalarmclient/client.py. No idea if this would mess up anything up in hass.io. Also, having looked into it a bit, I'm not sure it's really advised to manually edit files in site-packages anyway...

Thanks for investigating @charlesastaylor, will hopefully have a few spare minutes in the next couple of days to get this up.

@domwillcode
Is The latest version 100% working and if so would it be possible to see it in the next HA update.
Merry Christmas


Update Elasticsearch chart dependency to 8.5.1

The old version uses an outdated apiVersion for kind: PodDisruptionBudget, which breaks this chart for Kubernetes 1.21 and ongoing.
The following error emerges when using the old Elastic Helm chart:
Error: UPGRADE FAILED: resource mapping not found for name: "elasticsearch-master-pdb" namespace: "" from "": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"

As you can see, the newer version of the Elastic Helm chart uses some logic to pass the correct apiVersion: https://github.com/elastic/helm-charts/blob/v8.5.1/elasticsearch/templates/poddisruptionbudget.yaml
Kind regards
Franz

Hi, ElasticSearch 8.5.1 is not licensed by the Apache 2.0 anymore. That is why we hold the upgrade.
We expose to connect existing ElasticSearch as you could use any installed version.

It also breaks the CI

Hi, ElasticSearch 8.5.1 is not licensed by the Apache 2.0 anymore. That is why we hold the upgrade.
We expose to connect existing ElasticSearch as you could use any installed version.

Hi. We don't ship ES server/client codes here, we don't directly depends on the ES server (8.5.1 is the Helm Chart version), and, ES is not mandatory required (because we now support using a demo postgresql storage too). Is this still a problem?

If it is an optional config, we should be fine.

As the older Elasticsearch Helm template does not run on Kubernetes <= 1.21, I could not deploy Skywalking in our cluster at all. If the postgres backend is not recommended for production, I cannot use that either.
The update to chart version 8.5.1 was a tryout of mine to get Skywalking running. I would appreciate it very much if you could provide a Skywalking version that can be installed on Kubernetes 1.25.

At least, you could use ElasticSearch official helm to deploy it first, then use our helm to connect the existence ElasticSearch.

@kezhenxu94 Could you take a look at the ElasticSearch deployment in our helm to upgrade?

At least, you could use ElasticSearch official helm to deploy it first, then use our helm to connect the existence ElasticSearch.

Thank you for the hint, I will give this a try.

Closing in favor of https://github.com/apache/skywalking-kubernetes/pull/98


Move CI to GitHub Actions

Our sister project has transitioned from GCB to GitHub Actions. There are currently advantages to this (most prominent being public logs) so we should do the same.

The initial work was done in #691


error: cannot access function2

I cant use request code . it raises cannot access function 2 error..Any solution sir?

Looks like a duplicate of #40

Please use the Default Method over Inline Result:

Do check the README for more info

I'm using default method...but cant use request code with this

What do you mean by  cant use request code. Can you please post error here?

its now resolved sir, thank you very much for this wonderful product..i just removed the inline support implementation...:)


Requirements for Release

https://github.com/open-feature/openfeature-ruby/issues/7#tasklist-block-f1d814c4-40b3-4844-8737-35cd0b2ed007

We've done a few releases so far, and are listed on the OF website now. Closing this as I believe we've fulfilled the scope here


NYX - ensure governor reaches correct position

@RobertSchaffer1 and I found that interrupting the governor transitions can result in the governor being forced to state M, yet will report a successful status.
This can result in hardware being in a dangerous position.
Add code, either to the LSDC governor transition function itself or into the data collection side of things, to check final position. If not correct, throw an exception.

@JunAishima I'm a little bit confused as to how this is happening to be honest, the set function looks like this:
def setGovRobot(state):
if state == "DI":
return setGovRobotDI()
else:
logger.info('setGovRob%s' % state)
setRobotGovState(state)
altName = state.lower().capitalize()
waitGov()
robotGovState = (getPvDesc("robot%sActive" % altName) or getPvDesc("human%sActive" % altName))
logger.info("robot gov state = " + str(robotGovState))
if (robotGovState != 0):
if state in ["SA", "DA"]:
toggleLowMagCameraSettings(state)
return 1
else:
logger.info("Governor did not reach %s" % state)
gui_message("Governor did not reach %s." % state)
return 0
So the LSDC does check the governor state after the move. My best guess is that when the waitGov() finished it was in the correct state, but that after that it moved enough to drop to M - annoying, but can't really be caught with this type of checking. Are we monitoring the governor state PV?

Labelled as high, as problems with the governor status will decrease reliability of LSDC in production.

this was done in pull request #173, which has been merged. closing.


Allow update service instances with empty tags

Tracker story: https://www.pivotaltracker.com/story/show/96329216

Thanks, everything looks good, merged!


CONTRIBUTING.md

Issue Description
The CONTRIBUTING.md file has some grammatical issues.
Screenshots or Examples (if applicable)
No response
Proposed Solution (optional)
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[X] I am participating in Hacktoberfest 2023

You've been assigned @RS-labhub! :) I'll open your PR now


Add special Heroku instructions

Relates to #528
Not great with wording (or rst).. will update to whatever you all prefer, just want to help the next person with this problem not overlook this :)

I added some generic reverse proxy security notes as well. Upstreaming now, thanks for the contribution!


Optimize Catalog Item Retrieval

Previously, each catalog item kept track of it's own associated categories & sub-categories.  This PR removes categories/sub-categories from catalog items and instead  categorizes each item into an items array under each sub-category in the main Catalog object (similar to console's buildersByCategory object).   Categorization also dynamically adds 'All' and 'Other' main and sub-categories when needed.
This allows quicker processing as we only have to cycle through the category items once to categorize them whereas previously each catalog item ran through each category/sub-category, and then a second pass to remove those categories/sub-categories which weren't associated with any items.
This also allows for cleaner filtering code in the <service-view> component.
All unit tests passed include service-view.spec which tests many of the categorization rules.
Fixes #215

Hi @jwforres, I believe I have addressed your last review issues. -thanks!


Fix observed generation release note

This will need to go into the 1.8 release notes. This is pointing at the wrong issue.

In response to a cherrypick label: new pull request created: #28762


[Bug]: Unable to write dbt_artifacts results to different dataset in Bigquery

Overview
After following the guide and trying several different things, I am not really able to get the dbt_artifacts output to wind up anywhere other than the dataset specified in profiles.yaml.
How to reproduce
dbt-core 1.3.1
dbt-bigquery 1.3.0
dbt_artifacts 2.6.3
Following the guide and adding the necessary:
models:
  ...
  dbt_artifacts:
    +database: your_destination_database # optional, default is your target database
    +schema: your_destination_schema # optional, default is your target schema
    staging:
      +database: your_destination_database # optional, default is your target database
      +schema: your_destination_schema # optional, default is your target schema
    sources:
      +database: your_sources_database # optional, default is your target database
      +schema: your sources_database # optional, default is your target schema

to dbt_project.yml (also trying to replace +database with +project and +schema with +dataset) the views are still being added to the default dataset.
Expected behaviour
Regular models should be written to the default project + dataset as specified in profiles.yml and dbt_artifacts models should be written to the specified project + dataset.
Environment
Results of running dbt --version:
Core:
  - installed: 1.3.1
  - latest:    1.8.3 - Update available!

  Your version of dbt-core is out of date!
  You can find instructions for upgrading here:
  https://docs.getdbt.com/docs/installation

Plugins:
  - bigquery: 1.3.0 - Update available!

  At least one plugin is out of date or incompatible with dbt-core.
  You can find instructions for upgrading here:
  https://docs.getdbt.com/docs/installation

Please paste the contents of your packages.yml file here:
packages:
  - package: dbt-labs/dbt_utils
    version: "1.0.0-b2"
  - package: calogica/dbt_expectations
    version: [">=0.8.0"]
  - package: brooklyn-data/dbt_artifacts
    version: 2.6.3
  ...

Not sure if it could be due to the outdated version of dbt we are using.

@kabam-blambert I'm seeing the same issue as well on snowflake on latest in cloud.  I am looking to force the database and schema, and for me, while the database part works, the specified schema is getting appended to the target schema.
i.e.:
My project is building to dev_sandbox.mde_poc_prod
And I want artifacts to populate:
dev_dbt_artifacts.dbt_mde_poc
But instead it's trying to build to: DEV_DBT_ARTIFACTS.MDE_POC_PROD_DBT_MDE_POC
So the schema I am calling out in artifacts is getting appended instead of replaced.
Seems like a problem with or missing a custom generate_schema_name macro in the dbt_artifacts package.
And for me, this isn't a CI build either (full job).

Follow on:
Looks like this might be "predicted" behaviour according to the readme:
That's because the raw tables are now managed as dbt models. Be aware of any impact that [generate_database_name](https://docs.getdbt.com/docs/building-a-dbt-project/building-models/using-custom-databases#generate_database_name) and [generate_schema_name](https://docs.getdbt.com/docs/building-a-dbt-project/building-models/using-custom-schemas#how-does-dbt-generate-a-models-schema-name) macros may have on the final database/schema```

Here's the fix: You need to create an override generate_schema_name macro, and edit the else to remove the prefix behaviour.
Keep in mind this affects all schemas in the project, so there might be some more sophisticated logic to be had here.  I tried some things, but the on-run-end hook seemed to be a bit quirky.
this fix is courtesy:
This medium article
{% macro generate_schema_name(custom_schema_name, node) -%}

    {%- set default_schema = target.schema -%}

    {%- if custom_schema_name is none -%}

        {{ default_schema }}

    {%- else -%}
        {{ custom_schema_name | trim }}

    {%- endif -%}

{%- endmacro %}

@wsargent-emcins hey thanks a ton for all your help with this!

You bet @kabam-blambert! One more unlock: If you want to add logic to detect the special database, you need to use node.database instead of target.database:
(I added some logging here, that is optional)
{% macro generate_schema_name(custom_schema_name, node) -%}

    {%- set default_schema = target.schema -%}
    {%- set debug_message = '[GSN] Node: ' ~ node.name ~ ' Node Database: ' ~ node.database ~ ' Target Database: ' ~ target.database ~ ' Default Schema: ' ~ default_schema ~ ' Custom Schema: ' ~ custom_schema_name%}

    {# If the target database is the dev_dbt_artifacts database, don't appent the default schema #}
    {%- if node.database == 'dev_dbt_artifacts' -%}
        {{ log(debug_message, info=True) }}
        {{ log('[GSN] Detected Artifacts Database Detected. Using custom_schema_name', info=True) }}
        {{ custom_schema_name | trim }}

    {# If the custom_schema_name is empty, use the default schema from the job or environment #}
    {%- elif custom_schema_name is none -%}
        {{ default_schema }}

    {# If there is a specific schema called out in the model YAML or model config block, then append the default schema and use that schema (default dbt behaviour) #}
    {%- else -%}
        {{default_schema}}_{{ custom_schema_name | trim }}

    {%- endif -%}

{%- endmacro %}


Permanent notification for Brevent?

Hi.
Android may unload Brevent on wish. As I know many applications show constant notifcation to prevent that. Is there any chance Brevent will implement this too?

@liudongmiao Strange. If Brevent app is not running it doesn't work for me. I.e. brevented apps in Android task manager doesn't get killed. And I seen Android killed Brevent app after few days.

Oh, you're right. Looks like things just don't work 100% reliable in the rom I use


chore(release): cut v1.2.0

[X] I have cherry-picked any changes labelled needs-cherry-pick-vX.Y.Z

[X] I have made all of the following version and patch updates:

Updated the container image tag in charts/osm/values.yaml
Updated the chart and app version in charts/osm/Chart.yaml
Updated the image tags used in the automated demo
Regenerated the Helm chart README.md

[X] I have checked that the base branch for this PR is correct as defined by the release guide

Is this a release candidate? No

Codecov Report

Merging #4927 (e70a0dd) into release-v1.2 (14d457b) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           release-v1.2    #4927      +/-   ##
================================================
- Coverage         68.63%   68.62%   -0.02%
================================================
  Files               220      220
  Lines             15918    15918
================================================
- Hits              10925    10923       -2
- Misses             4941     4943       +2
  Partials             52       52

Flag
Coverage Δ

unittests
68.62% <ø> (-0.02%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/certificate/manager.go
76.70% <0.00%> (-0.81%)
:arrow_down:

Continue to review full report at Codecov.

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


Ability to reload configuration files without restarting server

I believe this is made possible/a lot easier with version 4.1.0 of the Sponge API. Not sure if it will work but I will give it a shot.

Sounds good, would help you if needed

The plan here is to allow everything BUT features to be reloaded. Making it so features can be reloaded might cause quite the headache as well as performance issues the way things are currently setup. Might work on changing this later, but at the moment it makes sense to require the server to be restarted to enable/disable features. I am going to change the config files around a bit to make it clear as to what can/can't be reloaded. So everything within the main, totaleconomy.conf, config file will not be able to be reloaded. Other then that I am hoping everything else can be changed and reloaded with ease.
And just so I remember, sponge has a command built in the will run the GameReloadEvent which is "/sponge plugins reload".


it does not work anymore

everything was going very well until tonight.  I checked Home Assistant and everything is unavailable.  after a reboot of my Raspberry, nothing works.  Has there been a major change from Renault?

Duplicate of #120


Upgrade ruby 3.1.3

closes #29

I'll hold off on merging this until after the RMD cycle, so I'll merge it in March.


Update just-wait and use npm bins

This should work the exact same, but much cleaner.
https://docs.npmjs.com/files/folders#executables

The reason those paths are relative, is to avoid having to install npm binaries globally.

Hey @RickWong,
When you NPM install a project with code like I have, the dependencies which have a bin object in their package.json will auto-install their binaries via symlink.
Are you worries my changes will cause you to need to -g install those packages? If so, give it a shot, you don't need to.

When in local mode, executables are linked into ./node_modules/.bin so that they can be made available to scripts run through npm. (For example, so that a test runner will be in the path when you run npm test.).

Thanks @lostthetrail


Grabber doesn't apply download intervals

Bug description
Sankaku complex is an annoying one... So i tried to set some delay and less download at a time. And, grabber seems to still make a lot of request at the same time.
Steps to reproduce

Go to "source"
Click on option form idol.sankakucomplex.com
Go to "Download" then apply a delay, like 10s for me.
Look at the log on any requestion (for exemple : cosplay)

[13:06:13.120][Info] Loading image from https://is.sankakucomplex.com/data/7d/6b/7d6bc85a7d76aefa6ef002637bef2981.webm?e=1545739452&m=iYi5w2dihhSMc0tSowEYYg 10
[13:06:13.125][Info] File already exists: E:\Avatars\photo\idol.sankakucomplex.com\public\anon\misc\unknown\anon - explicit - 664136 - 8b98256eb92b8595bb6c195ed1ad98c8.webm
[13:06:13.139][Info] Loading image from https://is.sankakucomplex.com/data/63/4b/634b334c68bbb93605d3164f89809bbf.webm?e=1545739462&m=MEAtC43VHnIGnGSdKiMWsg 10
[13:06:13.144][Info] File already exists: E:\Avatars\photo\idol.sankakucomplex.com\public\anon\misc\unknown\anon - explicit - 666737 - 575918f72cee1a0b2ce3d90266d852c3.webm
[13:06:13.157][Info] Loading image from https://is.sankakucomplex.com/data/04/7f/047f511866b118de4ee9e358f523736f.webm?e=1545739462&m=0CcBK5Y9AEbEXt93ZbB3Ew 10
[13:06:13.195][Info] Details limit reached (429). New try.
[13:06:13.227][Info] Details limit reached (429). New try.

Expected behavior
Since I tell grabber to wait 10s between "image", it should only try one image, then wait "10s" before try the next on.
Context

Provide your main.log file to see if any obvious error occured.
main.log
Providing your settings.ini file will greatly help maintainers reproduce your problem if it may be caused by your configuration.
settings.ini.txt

Screenshots
main window : https://i.imgur.com/hSww3CT.jpg
Site options : https://i.imgur.com/Fg3MFB0.jpg
System information

OS: Windows 10
Grabber version: 6.0.6

Set global max downloads to 1. The individual site one doesn't work at all for me.

Seems fixed in the lastest release !


Release new version

I appreciate that #161 was merged, but unfortunately we cannot depend on it as it's not released yet. Is there a roadmap for when releases are created?

We tend to schedule our releases around when the upstream makes a major change (unless of course we fix some critical bug on our side).  They haven't released in quite a while but it looks like they're in the somewhat-final stages of the 3.4.0 release: https://github.com/sass/libsass/issues/2174

upstream 3.3.6 is now available as 0.11.2! :sparkles:


Fix Image reflection issue and proguard rules

What does this PR do?

Changes some proguard rules in order to make the code work in release build.
Changes some reflection logic for image mapper in order to make it work in higher version of Coil
Change the bitmap copy config in order to make it work for Bitmap ALPHA config.
Update the sample app image showcase screen.

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report
Attention: Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.

Project coverage is 69.43%. Comparing base (71c250b) to head (bcc5f79).

Files with missing lines
Patch %
Lines

...rnal/mappers/semantics/ImageSemanticsNodeMapper.kt
0.00%
9 Missing :warning:

Additional details and impacted files
@@                  Coverage Diff                   @@
##           feature/sr_compose    #2337      +/-   ##
======================================================
- Coverage               69.45%   69.43%   -0.02%
======================================================
  Files                     753      753
  Lines                   27945    27950       +5
  Branches                 4779     4783       +4
======================================================
- Hits                    19409    19406       -3
- Misses                   7175     7195      +20
+ Partials                 1361     1349      -12

Files with missing lines
Coverage Δ

...rnal/mappers/semantics/ImageSemanticsNodeMapper.kt
1.79% <0.00%> (-0.18%)
:arrow_down:

... and 23 files with indirect coverage changes


Expiring a live object won't expire those fields that are distirbuted objects

I define a live object like this:
@REntity
public class ExampleLiveObject {
    @RId(generator = LongGenerator.class)
    private Long id;
    @RCascade(RCascadeType.ALL)
    private Map<Integer, Integer> map;
}

Then try to expire a live object:
RLiveObjectSerivce service;
ExampleLiveObject liveObject;

service.asRExpirable(liveObject).expire(1, TimeUnit.SECONDS);

The live object will be removed after one second, but the map in the object won't. Is this behavior expected?
My current workaround is to expire each distributed object field in a live object explicitly.

At the moment, expiring is only associated to the underlying RMap. I guess this can be added as a new feature that expiration also cascades down too.

If I delete a live object having the following class structure using service.delete(Session.class, "sessionid"), won't the fields inside the object get deleted? Do I have to delete each field explicitly?
@REntity
public class Session {
@RId
private String id;
private String api_key;
private String userid;
private String ip;
private Long expirytime;
}

@elitalobo those fields will be deleted and cascading is working fine for persisting and deleting, only expiring is not yet supported.

@jackygurui, thanks for the fast reply!. I am saving sessions in redis using redission so I also need to set expiry for the Session live object. Since I don't have any distributed objects in my session class, expiring a live object of the same shouldn't be a problem right?

@jackygurui, thanks for the fast reply!. I am saving sessions in redis using redission so I also need to set expiry for the Session live object. Since I don't have any distributed objects in my session class, expiring a live object of the same shouldn't be a problem right?

@jackygurui, thanks for the fast reply :). I am storing session in redis and hence need to expire live Session objects. Since I do not have any distributed objects in my session class, expiring a Session live object shouldn't be a problem right?

@elitalobo you should be fine with expiring of the object if you don't have any nested expirables

Why Is closed? The issue Is still presente! Maps and List inside a live object never expires. Also there are no referente into live_object_fileds to the patent love object, so actually Is not possible use a listner to clean up

Redisson still doesn't seem to clean up Redis/Valkey child objects of Live Objects fields in the latest version, but the following example demonstrates a simple, but manual, approach to expiring child objects. Just thought I'd shared this for future reference.
@REntity
@SuppressWarnings("LombokSetterMayBeUsed") // Can't use Lombok with Redisson Live Object
public class SomeData {

    private @RId String id;
    private Set<String> someSet;

    /**
     * Sets the expiration of this {@link SomeData} live object and cascades the expiration to the
     * child object references.
     *
     * @param dataCache the {@link RedissonClient}
     * @param duration  the expiration {@link Duration}
     */
    public void expire(RedissonClient dataCache, Duration duration) {
        dataCache.getLiveObjectService().asLiveObject(this).expire(duration);
        ((RSet<String>) getSomeSet()).expire(duration);
    }

    public String getId() {
        return id;
    }

    public void setId(String id) {
        this.id = id;
    }

    public Set<String> getSomeSet() {
        return someSet;
    }

    public void setSomeSet(Set<String> someSet) {
        this.someSet = someSet;
    }
}


Error messages still too noisy

I get complaints from a lot of users that the error message like:
REQUEST [error] Error (error) while connecting to http://<IP_ADDRESS>:38987/completions.
REQUEST [error] Error (error) while connecting to http://<IP_ADDRESS>:38987/event_notification. [26 times]
Are too noisy. Can we do something about this?
@Valloric just fyi

Depending on the errors involved, this could be a client-side issue.
For event notification especially, ycmd will send back an error if the file is already being compiled. That error is completely ignorable though and shouldn't be presented to the user.
That's off the top of my head without more information about the errors.

Besides, ycmd will display"contacting host <IP_ADDRESS>:xxxx" in the mode line every several seconds, which is noisy too...

Yes, we can probably do something about these. I just need to find some time to look into it.

@r4nt It looks like you can squash a lot of these messages by setting ycmd-request-msg-level to -1. Try that out and let me know if it works for you. This is a bit suboptimal, of course, because it might hide real errors, but that doesn't seem too likely, and it's far less of an issue than the noise problem.
@zhuzhongshu Setting the msg-level probably won't address the "contact host" messages. That seems to be buried down in the guts of the emacs http stack, but I'll see if I can figure it out.

@zhuzhongshu Try setting url-show-status to nil. It looks like this prevents the "Contacting host" messages. Note that the documentation string for url-show-status seems incomplete or misleading on 24.4. See url-lazy-message if you want to see how it's really used.

It works! Many thanks @abingham .

I've added a section to the README for this issue. I'll update it if it turns out that the advice is bad, and feel free to suggest any other additions you come up with.

@r4nt Have you had a chance to try the ycmd-request-msg-level trick I mentioned above? If that works to your satisfaction then I'll close this out.

Yep, works. Thanks!

Thanks :)


feat(acns): Add advanced networking observability tls management for az aks create and update commands

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
Creates commands for
az aks create --advanced-networking-observability-tls-management None
az aks create --advanced-networking-observability-tls-management Managed
az aks update --advanced-networking-observability-tls-management None
az aks update --advanced-networking-observability-tls-management Managed
General Guidelines

[x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[x] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[x] My extension version conforms to the Extension version schema

For new extensions:

[x] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

Waiting for tlsMangement property of advanced networking observability profile to be vendored before merging this pr

Requeued the live test pipeline to validate the updates

@rayaisaiah Could you please resolve this conflict?

@rayaisaiah Could you please resolve this conflict?

updated and running live test for test_aks_create_advanced_networking_observability_tls_management and
test_aks_update_advanced_network_observability

@rayaisaiah Could you please resolve this conflict?

@rayaisaiah Could you please resolve this conflict?

updated and running live test for test_aks_create_advanced_networking_observability_tls_management and
test_aks_update_advanced_network_observability

@rayaisaiah Could you please resolve this conflict?

updated and live test has passed for

test_aks_create_advanced_networking_observability_tls_management
test_aks_update_advanced_network_observability
test_aks_update_enable_acns
test_aks_create_with_enable_acns
test_aks_create_with_enable_acns_complex


template: add notes on CC footer (fix for #878)

Copy the description from the website explaining how the CC footer works.
And explain that /preview doesn't email the reviewers, which fixes #878.

Thank you so much @rcoup!


Inherit Parent class type instead of Childs when return this in parent class

TypeScript Version:  3.1.0

Search Terms: inherit this parent class
Code
interface DepsA {
  a: string
}

class Parent {
  constructor(protected deps: DepsA) {}

  public static factory() {
    return new this({a: 'This is a nice Dependency'})
  }
}

class Child1 extends Parent {
  public testFnc(){
    return this.deps.a
  }
}

const child1 = Child1.factory()
console.log(child1.testFnc())

Expected behavior:
console logs "This is a nice Dependency"
Actual behavior:
Typescript error: [ts] Property 'testFnc' does not exist on type 'Parent'.
Playground Link: here
Related Issues: Didn't find any

A work around for this would be the following:
interface DepsA {
  a: string
}

class Parent {
  constructor(protected deps: DepsA) {}

  public static factory<T extends Parent>() {
    return new this({a: 'This is a nice Dependency'}) as T
  }
}

class Child1 extends Parent {
  public testFnc() {
    return this.deps.a
  }
}

const child1 = Child1.factory<Child1>()

console.log(child1.testFnc())

But when I implement this I run in other issues as described in this stack overflow post

See #5863


Histogram support

AS A [user],
I WANT TO [create query],
SO THAT [I can get histogram as an output]

8c945265add9acdcfcf419ebada54e34c708c590
Few TODO's remain. Basic functionality provided.


Fix target type validation

Allow TargetType to be Ref items, such as Ref('AWS::NoValue'), as well as parameters.
This will not allow using None, but one would argue Ref('AWS::NoValue') would be a better choice.
Also today, when trying to use None (at least in python 2.7), you would get the error:
TargetType is <type 'NoneType'>, expected <type 'basestring'>
Fixes #1539

Thanks!


Make it possible for users to validate POST requests

This is kind of a requirement for any real-world application on using dash-uploader in the public internet. Currently, the README states:
⚠Security note: The Upload component allows POST requests and uploads of arbitrary files to the server harddisk and one should take this into account (with user token checking etc.) if used as part of a public website!

This could be tackled with a bit of python code. There could be a subclassable class that has the logic for checking POST requests. Default would be to accept everything, but user could write a validate_post_request method that would override this and give more possibilities on how the uploading would generally work. This could also be done with functions as arguments to the du.configure_upload, but classes are a bit nicer in sense that there could be other customizable things, too. For example, server could decide what to do with which type or size of file, etc.

Implemented functionality in  v.0.5.0 of dash-uploader. Now it is possible to configure handling of POST and GET requests with the http_request_handler argument given to du.configure_upload. The argument should be a subclass of du.HttpRequestHandler.


Conv3DBackpropInputOpV2 only supports NDHWC on the CPU.

Bugs_log:
InvalidArgumentError (see above for traceback): Conv3DBackpropInputOpV2 only supports NDHWC on the CPU.
[[node synthesis/layer_0/conv3d_transpose/conv3d_transpose (defined at /home/chenghao/pcc_geo_cnn/src/compression_model.py:70) ]]

Hi, I follow the steps on the README to prepare the ModelNet40 dataset but face the problem above when I want to train your model.
Environments:
Ubuntu 16.04
Python 3.6.5
Tensorflow 1.13
I have tried to modify the code to train the model on GPU.
It seems all right when I compress/decompress the testing dataset of ModelNet40.
But the decompressed point cloud went wrong when I test the model on the MVUB dataset.
The decompressed point cloud is a cube full of points with 512512512 shape.
Maybe you can point out where did I do something wrong.
Thanks in advance!

Hi,
Thank you for your interest in our work.
Have you installed tensorflow using the tensorflow-gpu package ?
In your error message, tensorflow mentions that it is using the CPU.
The code is using data layouts optimized for the GPU (channels first).
You can double check your installation here:
https://www.tensorflow.org/install/gpu
You can also check that a GPU is available using the following code:
from tensorflow.python.client import device_lib
print(device_lib.list_local_devices())

Yes. I have installed tensorflow-gpu and use it on other projects to train models.
I am confusing with the input_fn() in both compression_models.py and decompression.py
You specify tensorflow to use cpu, other than gpu.
Also, I don't find the code to specify gpu for tensorflow.
The code below is what I mean.
'''Set GPU'''
gpus = [GPU_INDEX] # Here I set CUDA to only see one GPU
os.environ['CUDA_VISIBLE_DEVICES']=','.join([str(i) for i in gpus])
def train():
    with tf.Graph().as_default():
        with tf.device('/gpu:'+str(GPU_INDEX)):

Does I dig into wrong direction?

To answer your questions, in input_fn() the dataset operations are placed on the CPU as this preprocesses the data (on the CPU) prior to loading it on the GPU.
In decompression.py, there is a performance issue at high resolutions which is documented here https://github.com/tensorflow/tensorflow/issues/25760 .
If I understand correctly,  you are encountering this error when decompressing point clouds.
This is probably be cause of this line in decompress.py:
os.environ['CUDA_VISIBLE_DEVICES'] = ''
On my configuration, I compiled tensorflow from source with Intel MKL support (https://www.tensorflow.org/install/source#configure_the_build) which enables channels first on the CPU.
You could try one of these two:

Compile Tensorflow with MKL support
Remove the line mentioned previously. However, this will slow down the decompression process significantly.

Thanks for your explanation about input_fn().
I have tried to comment out the line in decompress.py: os.environ['CUDA_VISIBLE_DEVICES'] = ''
It indeed slows down the process significantly.
But I will try other datasets with less resolution instead, so the influence seems okay to my project.
Thank you again for helping me find the solutions. :)

InvalidArgumentError:  Conv3DBackpropFilterOpV2 only supports NDHWC on the CPU.
[[node gradient_tape/sequential_6/conv3d_16/Conv3D/Conv3DBackpropFilterV2 (defined at :23) ]] [Op:__inference_train_function_4107]
i was running the code of 3dcnn and got this error
model.add(Dense(nb_classes,init='normal'))
model.add(Activation('softmax'))
opt=adam(lr=0.0001)
Compile the model
model.compile(optimizer=opt, loss='categorical_crossentropy', metrics=['accuracy'])
Spliting the dataset for testing and training
X_train_new, X_val_new, y_train_new,y_val_new =  train_test_split(train_set, Y_train, test_size=0.2, random_state=4)
Training  the model along with creating callbacks to tensorboard for graphical visualization of training process
tbcallback = keras.callbacks.TensorBoard(log_dir='/workspace/dgx1/keras/40g', histogram_freq=0, write_graph=True, write_images=True)
hist = model.fit(X_train_new, y_train_new, validation_data=(X_val_new,y_val_new),
batch_size=batch_size,nb_epoch = nb_epoch,shuffle=True,verbose=1,callbacks=[tbcallback])


Message Queue Handling

Is your feature request related to a problem? Please describe.
This is related to create metering point.
Related to ingestion part.
Talk to @Korgath
Describe the solution you'd like.

[x] Add Message Queue Envelope (MessageQueueItem), that contains:

[x] UserIdentity (add via context)
[x] CreateMeteringPointCommand
[ ] CommandType (won't implement directly, using protobuf contract instead)

[ ] Add interface: IMessageQueueService (won't implement directly, using messaging transport "framework")
[x] Create concrete implementation with ServiceBus: MessageQueueService
[x] Add to DI
[x] Retry handling - Polly

Definition of done

[ ] Demonstrate that item can be added to underlying queue (ServiceBus)
[ ] Demonstrate that retry handling works
[x] Manual test

@erduna Does this issue need more testing?

Haven't explicitly demonstrated retry handling, but I think we can close this anyways :)


Update headpose_forwarddirection.md

Add a note explaining planned behavior change to head forward direction on HoloLens 2.
@thetuvix

@dfields-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Implement TRAPI 1.3 updates for workflow runner

Ticket created based on discussion in Aragorn 8/5 team meeting (agenda)

This would be better on the workflow runner repository.   But it has now been completed.


Trying to cross compile 3.1.3 against Python

When trying to cross-compile Python 3.12 which includes OpenSSL 3.1.3, The below errors occur when building for 32 bit (64bit and X86_64 are fine).
OpenSSL 3.0.11 does not have these same issues.
I'm not really sure what else to include to help understand this.  The OpenSSL library itself does build, but the errors below are when I'm trying to build Python for Android.  If you would like to see the project, it is here (https://github.com/GRRedWings/python3-android/tree/DWE-3790)
ld.lld: error: relocation R_ARM_REL32 cannot be used against symbol 'OPENSSL_armcap_P'; recompile with -fPIC
>>> defined in /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a(libcrypto-lib-armcap.o)
>>> referenced by libcrypto-lib-sha256-armv4.o:(.text+0x104) in archive /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a
ld.lld: error: relocation R_ARM_REL32 cannot be used against symbol 'OPENSSL_armcap_P'; recompile with -fPIC
>>> defined in /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a(libcrypto-lib-armcap.o)
>>> referenced by libcrypto-lib-sha512-armv4.o:(.text+0x280) in archive /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a
ld.lld: error: relocation R_ARM_REL32 cannot be used against symbol 'OPENSSL_armcap_P'; recompile with -fPIC
>>> defined in /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a(libcrypto-lib-armcap.o)
>>> referenced by libcrypto-lib-sha1-armv4-large.o:(.text+0x530) in archive /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a
ld.lld: error: relocation R_ARM_REL32 cannot be used against symbol 'OPENSSL_armcap_P'; recompile with -fPIC
>>> defined in /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a(libcrypto-lib-armcap.o)
>>> referenced by libcrypto-lib-poly1305-armv4.o:(.text+0xB40) in archive /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a
ld.lld: error: relocation R_ARM_REL32 cannot be used against symbol 'OPENSSL_armcap_P'; recompile with -fPIC
>>> defined in /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a(libcrypto-lib-armcap.o)
>>> referenced by libcrypto-lib-chacha-armv4.o:(.text+0x20) in archive /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a
ld.lld: error: relocation R_ARM_REL32 cannot be used against symbol 'OPENSSL_armcap_P'; recompile with -fPIC
>>> defined in /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a(libcrypto-lib-armcap.o)
>>> referenced by libcrypto-lib-armv4cpuid.o:(.text+0x160) in archive /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a
ld.lld: error: relocation R_ARM_REL32 cannot be used against symbol 'OPENSSL_armcap_P'; recompile with -fPIC
>>> defined in /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a(libcrypto-lib-armcap.o)
>>> referenced by libcrypto-lib-armv4-gf2m.o:(.text+0x2A0) in archive /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a
ld.lld: error: relocation R_ARM_REL32 cannot be used against symbol 'OPENSSL_armcap_P'; recompile with -fPIC
>>> defined in /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a(libcrypto-lib-armcap.o)
>>> referenced by libcrypto-lib-armv4-mont.o:(.text+0x0) in archive /python3-android/src/Python-3.12.0/Android/sysroot/usr/lib/libcrypto.a
clang-17: error: linker command failed with exit code 1 (use -v to see invocation)

Hello,
I have the same issue, I compiled OpenSSL 3.1.3 with android ndk to use in an Android application. But I got this error when compiling my Android application:
ld.lld: error: relocation R_ARM_REL32 cannot be used against symbol 'OPENSSL_armcap_P'; recompile with -fPIC

No issue with OpenSSL 3.1.2

Hello,
the bug is still present in the new verion 3.1.4. Is there any workaround to fix it?
Thanks.

Is there any workaround to fix it?

FWIW: There is some discussion going on about the issue in #22181.

What solution did you guys find? I'm trying to compile openSSL 1.1.2 for Android and facing the same error. The comments on #22181 are pure giberish to me


Refactor dotnet code gen

🤔 What's changed?
Rewrote the Dotnet code generation script to adopt the ruby erb gem approach used for other languages.
Modified the target .NET Framework settings by eliminating the use of .NET45 - targeting .NETStandard2.0 only.
Used a DevContainer so you'll see a devcontainer.json in the file set.
⚡ What's your motivation?
To bring the .NET implementation to parity with the java version.
🏷 What kind of change is this?

:bank: Refactoring/debt/DX (improvement to code design, tooling, etc. without changing behaviour)

♻ Anything particular you want feedback on?
Per the question I posted on issue #230, does the ordering of properties of a entity matter when serialized? The serialization I have does not match the sequence of properties shown in the CCK examples.
I've used a Microsoft provided devcontainer image. Do you mind? Or should that be changed to the github image?
📋 Checklist:

[x] I agree to respect and uphold the Cucumber Community Code of Conduct
[ ] I've changed the behaviour of the code

[X ] I have added/updated tests to cover my changes.

[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[X ] Users should know about my change

[X ] I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

This text was originally generated from a template, then edited by hand. You can modify the template here.

Per the question I posted on issue https://github.com/cucumber/messages/issues/230, does the ordering of properties of a entity matter when serialized? The serialization I have does not match the sequence of properties shown in the CCK examples.

Answered: https://github.com/cucumber/messages/issues/230#issuecomment-2197433270. The order does not matter.

I've used a Microsoft provided devcontainer image. Do you mind? Or should that be changed to the github image?

As long as that choice falls within the common practices in the .Net ecosystem that is okay. The goal is to make sure the next contributor familiar with .Net understands what is going on.
I also don't think the Github provided containers are available on Dockerhub.

Updated the PR to include a ChangeLog entry.
Revised the code gen script to house all the generated C# classes in a /generated folder.
Added support classes in alignment with what the Java implementation has (for serialization support and TimeStamp conversions).
Added tests for the support classes (again, similar in nature to what the Java implementation does)
Dropped target framework support for .NET Framework 4.x (leaving .NET Standard 2.0 as the target).

@mpkorstanje please add @gasparnagy as a reviewer of this PR. Thanks

Dependent on the timeframes involved this will maybe require a large conflict resolution as I'm in the process of refactoring the codegen (Only a small refactor, but lots of moving of files around), here: https://github.com/cucumber/messages/pull/228
I'm currently at a bit of an impasse in terms of contributing for the coming weeks, so if this is merged in in the next 1-2 weeks you'll have no issues and I'll fix up conflicts my end. But just letting you know :+1:

@luke-hill cheers.
@clrudolphi @gasparnagy take your time, I won't be looking at opensource this week until the end of the weekend.

I've also added a line to MessagetoNdjsonReader and Writer classes to Close their internally held streamwriter upon Dispose().

Thanks for your review comments so far.
I think the only outstanding item is the comment from @luke-hill about the dotnet generation script and the complexity required when declaring Nullable properties/fields.

@mpkorstanje @luke-hill Any chance to close this out today or tomorrow? I'm going on holiday until the 1st of August and would be good to finish this so that @luke-hill can proceed with his other refactoring.

@clrudolphi consider all my comments that have not been addressed to be "deferable" I don't want to hold anything up.
Just consider the actual dotnet stuff from Gaspar / Rien now. I can do some more fine tuning after your stuff is merged in a separate PR entirely to both this one and my companion one. Which would probably make things easier for you to review also.

Shit it 😀!

Funniest merge approval comment ever!

😀 Autocorrect... But you know what I meant.

@gasparnagy have you made a release before?

No, I don't think so.

Just posting here. Let's hold off releasing until I get my codegen stuff in also. As then it's a chunky enough release for a major.

No problem.


chore: update os

Want to take a quick look at this one @ShaunSHamilton - I just ran the install command as you suggested.
Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

Would you mind making your fork public as well? I cannot push to your PRs if it is private.


Gitea UI trimming white space

Gitea Version
1.15.2
Operating System
Ubuntu 20.04
Browser Version
Chrome 93.0.4577.63
Can you reproduce the bug on the Gitea demo site?
No
Description
I'm not entirely sure what the issue is or if it is an interface bug. But all the repositories on my self hosted Gitea are missing spaces. I've attached a screenshot of the issue.
Screenshots
Here's a screenshot from the Gitea UI

and here is a screenshot from my IDE. Looks like Gitea has trimmed the whitespace for some reason

It's not Gitea.
It's Cloudfare.
You're using Cloudfare and you've got whitespace minimization on.

It's not Gitea.
It's Cloudfare.
You're using Cloudfare and you've got whitespace minimization on.

Thanks for getting back to me so quickly. This was the issue. I would have never thought of it


Fail to overwrite a blob by one blob with tags after retrying 'Enable overwrite' option

Storage Explorer Version: 1.20.1
Build Number: 20210720.10
Branch: hotfix\1.20.1
**Platform/OS:**Windows 10/ Linux Ubuntu 18.04/ MacOS Big Sur 11.4
Architecture: ia32/x64
How Found: From running test case
Regression From: Not a regression
Steps to Reproduce

Create a storage account -> Create a blob container -> Upload one blob.
Click 'Upload' -> Choose a file which has the same name with the uploaded blob.
Add a tag on 'Upload Files' dialog -> Click 'Upload'.
Click 'Do not upload' -> Click 'Apply to All Conflicts' -> Click 'Retry...' action next to the activity log.
Make sure the 'Overwrite' option is 'Enable overwrite' in the popped up 'Retry Azcopy' dialog-> Click 'Retry Selected'.
Check whether the blob uploads successfully.

Expected Experience
The blob uploads successfully.
Actual Experience
The blob doesn't upload successfully, and an error message appears on activity log.

Additional Context

This issue also reproduces when choosing 'Prompt for overwrite' option in the popped up 'Retry Azcopy' dialog.
This issue doesn't reproduce when choosing 'Replace' on the firstly popped up 'Conflict' dialog.

Looks like we are probably missing the tag permission when we regenerate the SAS for retry.

Fix merged into main.


Update configure_github_repo.md

Added Subsection about documentation configuration
I have given it a try for my Issue #22

Oh I see the issue but not in love with the solution. I think it'd be better to be specific that the issue is having to add the Page Tree at the end of the mkdocs.yml file. Let me know what you think of it being,
Setting up the Navigation system
Because the docs only start with an index.md file, there's no need / way to setup a more complete navigation system (otherwise known as the page tree). To set this up, reference the nav section of this cookiecutter's mkdocs.yml file. Note that each highest level list item becomes part of the top nav and then all nested items are shown within each section.

Your solution is perfect. Actually after reading the nav section on your repo helped me to understand where to setup this.


Changing File Type

Description of the new feature / enhancement
I request a new feature for PowerToys that would allow users to easily change the file type of any file. As someone who works with a variety of file types on a daily basis, I often find myself needing to convert files from one type to another. While there are a variety of third-party tools that can do this, it would be incredibly convenient to have this functionality built directly into PowerToys.
Here's how I envision this feature working: when I right-click on a file in Windows Explorer, I would like to see a new option called "Change File Type" in the context menu. When I select this option, a small window would appear that allows me to choose the new file type from a list of options. PowerToys would then automatically convert the file and save it in the new format, while preserving any metadata or other relevant information.
I believe that this feature would be incredibly useful for a wide range of users, including professionals who work with different file types on a regular basis, as well as casual users who just want to quickly convert a file without having to install additional software. It would also make PowerToys an even more powerful and versatile tool for Windows users.
Scenario when this would be used?
Imagine you're a graphic designer who often receives image files from clients in various formats, such as JPEG, PNG, or TIFF. You typically work with Adobe Photoshop, which has a file format that it prefers to work with, such as PSD or AI. However, occasionally you receive a file from a client in a format that is not compatible with Photoshop, such as a JPEG or PNG.
In this situation, you would normally need to find a separate file conversion tool to convert the file to a compatible format before you can work with it in Photoshop. However, with the new file type conversion feature in PowerToys, you can simply right-click on the file in Windows Explorer and choose "Change File Type". You can then select the desired file format, such as PSD or AI, and PowerToys will automatically convert the file to that format, preserving any metadata or other relevant information. Another example is for students like me. We are always downloading the PPTX slides that our instructors provide. However, it is not useful to take notes in PowerPoint app. We need to convert this file to a PDF version to open in our note taking applications. Converting these files sometimes take time. So, it would be great to see a feature allowing us to convert these documents easily with Microsoft PowerToys.
Supporting information
No response

It's not that simple. You can't change any random filetype into any other random filetype. For the types that are similar, the conversion still needs some kind of app/codec/logic to convert between them. That's exactly what those famous programs are made for.
A PSD file totally different from an image file.

neat idea, but no plans do do this. A lot of apps have built in converts that let you save it as a different format.


bring lownodeutilization and highnodeutilization to plugin

as title

/unhold

/assign @ingvagabund

@ingvagabund  coding finish for bring two nodeutilization to plugins, please kindly reivew if you at rest :)

@pravarag for awareness

@pravarag for awareness

Hi @ingvagabund @JaneLiuL does this PR covers what's mentioned here: https://github.com/kubernetes-sigs/descheduler/issues/837#issuecomment-1164511878 ?
I was already in works for bringing LowNodeUtilization and HighNodeUtilization strategies, let me know otherwise. I'll pick something else to work upon.

hi @pravarag since i check already two months and still not seem your pr, so i just raise pr for that.

/retest

@JaneLiuL please let us know when the PR is ready for review :) This is the last strategy in the list.

@ingvagabund  ok for review now, would you please kindly review this pr ? :)


gru_ops.py trying to load a .so file on windows

gru_ops.py is attempting to load an .so library on windows when using CPU version (vs GPU), is this the correct behavior? It fails in my case.
LINE 33
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/rnn/python/ops/gru_ops.py

Please provide details about what platform you are using  (operating system, architecture). Also include your TensorFlow version. Also, did you compile from source or install a binary?  Make sure you also include the exact command if possible to produce  the output included in your test case. If you are unclear what to include  see the issue template displayed in  the Github new issue template.
We ask for this in the issue submission template, because    it is really difficult to help without that information. Thanks!

The error was my setup, fixed, no issue.
Platform Windows 10/64. Install was from a .whl.
This item can be closed.
Thank you.
On Wed, Sep 27, 2017 at 1:12 PM, Paul Tucker<EMAIL_ADDRESS>wrote:

Please provide details about what platform you are using (operating
system, architecture). Also include your TensorFlow version. Also, did you
compile from source or install a binary? Make sure you also include the
exact command if possible to produce the output included in your test case.
If you are unclear what to include see the issue template displayed in the
Github new issue template
https://github.com/tensorflow/tensorflow/issues/new.
We ask for this in the issue submission template, because it is really
difficult to help without that information. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/13311#issuecomment-332589083,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXVTXUSTlM_T17rvzVioshVg41pN0Qbks5smoHsgaJpZM4PkKEa
.


feat(workers): Adds a new command worker

This adds a worker that actually translates commands into lattice ctl operations. It also starts the work of creating a control client per lattice as needed
Closes #50

This looks good but I'd like to see integration tests for when unmanaged instances of an actor are on the same host as managed instances to verify that the unmanaged ones remain unaffected and reconciliation done by wadm doesn't affect unmanaged actors or providers.

I did test this 🙂. It is the last test done in the integration test


⚠ Bofrost.at has degraded performance

In b57c839, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1061 ms

Resolved: Bofrost.at performance has improved in aa5f28e.


Improve heatmap documentation.

This also removes a utility function that is also handled in a proper utils method.

Yes.  Documenting things is a powerful way to find and fix issues.


Add a No-Op DataProvider

Some consumers don't want to (or can't) reach to external resources for entity resolution. Provide a permissive DataProvider implementation for those use cases.

Fixed in https://github.com/symphonyoss/messageml-utils/issues/95.


Interfaces not visualizing on child devices

Issue type
[ ] Feature request
[ x] Bug report
[ ] Documentation

Environment

Python version:  3.4.5
NetBox version:  2.2.6
on CentOS 7

Description
I have a device which is a server chassis(added to a rack) and several blade servers which are children of said chassis. I have added interfaces to all child devices. After binding an interface to an IP address, the interface stops visualizing in the device page. The interface DOES exist and is bind to the device, but it doesn't render/visualize.

DB info:
select * from dcim_device where name = 'c1s01';
-[ RECORD 1 ]--+------------------------------
id             | 201
created        | 2017-12-07
last_updated   | 2017-12-07 17:14:26.515451+00
name           | c1s01
serial         |
position       |
face           |
status         | 1
comments       |
device_role_id | 12
device_type_id | 6
platform_id    | 10
rack_id        | 7
primary_ip4_id | 6145
primary_ip6_id |
tenant_id      | 5
asset_tag      |
site_id        | 1
cluster_id     |
select * from dcim_interface where device_id = 201;
-[ RECORD 1 ]------+------------------
id                 | 682
name               | p49p1
form_factor        | 1000
mgmt_only          | f
description        |
device_id          | 201
mac_address        | 00:23:ae:fe:4e:fc
lag_id             |
enabled            | t
mtu                |
virtual_machine_id |
-[ RECORD 1 ]-+------------------------------
id            | 6145
created       | 2017-11-30
last_updated  | 2017-12-07 17:14:26.326756+00
family        | 4
address       | <IP_ADDRESS>
description   | c1s01
interface_id  | 682
nat_inside_id |
vrf_id        |
tenant_id     | 1
status        | 1
role          | 51
As soon as I unlink the interface/IP the interface starts visualizing.
This isn't a problem with the data, as the interface is being fetched and passed to be rendered by the Jinja logic.
Steps to reproduce:

Add a device type (parent) and a device type(child). See my types for reference:

Create an IP address which to use for the child device
Add a device with the type of the parent and one with the type of the child. I just tried and the child doesn't even have to be in the bay.
Add an interface
Bind the created IP to the created interface.

Please provide the steps needed to reproduce this bug, using specific values.

@jeremystretch - done, edited the description of the issue.

I'm not able to reproduce this. I can assign IPs to interfaces belonging to a child device and they show normally. I'm not sure what would prevent them from showing up.
@atkozhuharov Can you post a more detailed set of steps to reproduce this please? Be sure to specify exactly what you're doing at each step, what values you're using, etc.

The steps I took are as in the description. Here are the concrete values:
Site: Testing
Rack: fl5.rack, group: floor5, width 19 inces, height 42U descending units
Device Type:
M1000E Dell Height - 10U, Fulldepth, Net device, Parent role
M1000E Dell Height - 0U, Fulldepth, Net device, Child role
Devices:
name: dell-chassis, device-role: chassis, Dell M1000E
name: c1s01, device role: Openstack node, Dell M610, serial: ABCD, site: Testing, rack: fl5.rack, Status: Active, Platform: Ubuntu, Primary IPv4 <IP_ADDRESS>/32
Interface:
c1s01:
IP:
<IP_ADDRESS>/32, VRF global, family ipv4, tenant: test, status:active, role: blade server, description c1s01

"blade server" isn't a valid IP address role.

Why is it not valid ? Attached screenshot.

IPAddress role choices are hard-coded. You're probably looking at Prefix/VLAN roles.
IPADDRESS_ROLE_LOOPBACK = 10
IPADDRESS_ROLE_SECONDARY = 20
IPADDRESS_ROLE_ANYCAST = 30
IPADDRESS_ROLE_VIP = 40
IPADDRESS_ROLE_VRRP = 41
IPADDRESS_ROLE_HSRP = 42
IPADDRESS_ROLE_GLBP = 43
IPADDRESS_ROLE_CARP = 44
IPADDRESS_ROLE_CHOICES = (
    (IPADDRESS_ROLE_LOOPBACK, 'Loopback'),
    (IPADDRESS_ROLE_SECONDARY, 'Secondary'),
    (IPADDRESS_ROLE_ANYCAST, 'Anycast'),
    (IPADDRESS_ROLE_VIP, 'VIP'),
    (IPADDRESS_ROLE_VRRP, 'VRRP'),
    (IPADDRESS_ROLE_HSRP, 'HSRP'),
    (IPADDRESS_ROLE_GLBP, 'GLBP'),
    (IPADDRESS_ROLE_CARP, 'CARP'),
)```

Yes the prefix role is blade-server.

Prefixes are not involved in this workflow at all.
I'm sorry, but I'm not able to reproduce this issue with the information provided, and thus am closing this issue. If someone can provide detailed instructions for reproducing the reported issue on a stock NetBox installation, I'll re-open it.


Feature Request: Star icon should be stateful based on whether article is starred or not

Have the star icon be an empty fill when an article is not starred, and use existing icon if the article is already starred

We don't have any plans to change this for the current toolbar, but the new toolbar for NetNewsWire 6.0 will use a stateful star when used in Big Sur.


Settings Icon in Now Playing Widget Should Display Aria Label on Hover

Describe the bug
Settings Icon in Now Playing Widget Should Display Aria Label on Hover. Other icons display an tooltip with their element's aria label and we should follow the lead.
Expected behavior
Hovering over the Settings Icon should display a tooltip displaying a 'Edit Snip' aria label. This is quite similar to the implementation on the track list.
Screenshots
If applicable, add screenshots to help explain your problem.
CURRENT

EXPECTED (based on tracklist implementation)

IMPLEMENTATION
Based on the tracklist implementation, it should be as simple as adding the role and aria-label attributes to the Icon component? Reference https://github.com/cdrani/chorus/blob/ef998b9e084bf8174d94359ffe5f8f7474113ade/models/snip-icon.js#L23-L25

Hey there, can you please tell in which file the Settings Icon is present ?

@Piyush-Deshmukh: https://github.com/cdrani/chorus/blob/5c88d09d3f4608712fe861e66435e8f3fbac49eb/models/icon.js#L14


ECDSA verification failure on webhook call when updating provisioner

Version

Karpenter Version: v0.27.1

Kubernetes Version: v1.23
Expected Behavior
Updating the provisioner
Actual Behavior
Internal error occurred: failed calling webhook "defaulting.webhook.karpenter.sh": failed to call webhook: Post "https://karpenter.karpenter.svc:443/default/karpenter.sh?timeout=10s": x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "karpenter.karpenter.svc")
Steps to Reproduce the Problem
Modify an existing provisioner
Resource Specs and Logs
"https://karpenter.karpenter.svc:443/default/karpenter.sh?timeout=10s\": x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "karpenter.karpenter.svc")"}2023-03-30T15:14:36.574Z	ERROR	controller	Reconciler error	{"commit": "7131be2-dirty", "controller": "counter", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "Provisioner": {"name":"default"}, "namespace": "", "name": "default", "reconcileID": "14460c1e-6391-47d9-b444-632489e8b134", "error": "Internal error occurred: failed calling webhook "defaulting.webhook.karpenter.sh": failed to call webhook: Post "https://karpenter.karpenter.svc:443/default/karpenter.sh?timeout=10s\": x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "karpenter.karpenter.svc")"}2023-03-30T15:14:36.628Z	ERROR	controller	Reconciler error	{"commit": "7131be2-dirty", "controller": "counter", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "Provisioner": {"name":"default"}, "namespace": "", "name": "default", "reconcileID": "2ea08894-19a8-49e0-ae26-1407a7d35c85", "error": "Internal error occurred: failed calling webhook "defaulting.webhook.karpenter.sh": failed to call webhook: Post "https://karpenter.karpenter.svc:443/default/karpenter.sh?timeout=10s\": x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "karpenter.karpenter.svc")"}2023-03-30T15:14:36.731Z	ERROR	controller	Reconciler error	{"commit": "7131be2-dirty", "controller": "counter", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "Provisioner": {"name":"default"}, "namespace": "", "name": "default", "reconcileID": "cdfc29dd-2033-47cb-ba50-887680014f21", "error": "Internal error occurred: failed calling webhook "defaulting.webhook.karpenter.sh": failed to call webhook: Post "https://karpenter.karpenter.svc:443/default/karpenter.sh?timeout=10s\": x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "karpenter.karpenter.svc")"}2023-03-30T15:14:36.910Z	ERROR	controller	Reconciler error	{"commit": "7131be2-dirty", "controller": "counter", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "Provisioner": {"name":"default"}, "namespace": "", "name": "default", "reconcileID": "fa32a757-b3e4-478e-a1ac-56c8af5fc476", "error": "Internal error occurred: failed calling webhook "defaulting.webhook.karpenter.sh": failed to call webhook: Post "https://karpenter.karpenter.svc:443/default/karpenter.sh?timeout=10s\": x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "karpenter.karpenter.svc")"}
Community Note

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

Can you provide the Karpenter logs?
Are you using ArgoCD or Flux to install Karpenter? We've seen issues where Argo fights the webhook reconciler within the Karpenter controller and can cause these cert verficiation errors.

@bwagner5 yes, I'm using argocd. Is there anything I can do here? I already tried replace, deleting individual resources, etc.
The Karpenter logs are the provided ones, is there anything additional I should look for in the logs which could be helpful for you?

Can you try adding a block like this?
      ignoreDifferences:
      - kind: ValidatingWebhookConfiguration
        group: admissionregistration.k8s.io
        name: validation.webhook.karpenter.k8s.aws
        jqPathExpressions:
        - .webhooks[].clientConfig.caBundle
      - kind: MutatingWebhookConfiguration
        group: admissionregistration.k8s.io
        name: defaulting.webhook.karpenter.k8s.aws
        jqPathExpressions:
        - .webhooks[].clientConfig.caBundle

@bwagner5 I already had those ignoreDifferences in place, including that one:
ignoreDifferences:
  - kind: Secret
    name: karpenter-cert
    jsonPointers:
      - /data

But removing those, also, don't make a difference.

Alright, I could find the issue, there was a duplicate webhook with a different name which wasn't deleted, during an upgrade:
defaulting.webhook.karpenter.sh
The new one is defaulting.webhook.karpenter.k8s.aws
I had to delete the old webhook, then everything worked again.

In 0.27.2, ClusterRole karpenter-core retains this
  - apiGroups: ["admissionregistration.k8s.io"]
    resources: ["mutatingwebhookconfigurations"]
    verbs: ["update"]
    resourceNames: ["defaulting.webhook.karpenter.sh"]

Should it be changed to the new MutatingWebhookConfiguration defaulting.webhook.karpenter.k8s.aws?