x64: lower iabs.i64x2 using a single AVX512 instruction when possible

This introduces the mechanism for encoding EVEX instructions to the new backend (ported with slight changes from the old) and then uses it to improve the lowering of iabs.i64x2 from 5 instructions to 1 instruction (i.e. VPABSQ).

I'm introducing this PR as a draft to solicit opinions about how best to integrate this:

any preference to switch to a builder pattern (e.g. Evex::new().v128().prefix(...).map(...).reg(...).rm(...).w(true).opcode(0x1F).encode() matching the manual's syntax, EVEX.128.66.0F38.W1 1F /r) over the current encode_evex(...)`?
a better integration with Inst than XmmUnaryRmREvex { op: Avx512Opcode, ...}? I cannot just add a boolean evex field to XmmUnaryRmR because some AVX512 instructions (e.g. VPABSQ) don't exist so they should not be included in SseOpcode. But the XmmUnaryRmREvex approach is not going to scale to a bunch of other instructions well.

any preference to switch to a builder pattern (e.g. Evex::new().v128().prefix(...).map(...).reg(...).rm(...).w(true).opcode(0x1F).encode() matching the manual's syntax, EVEX.128.66.0F38.W1 1F /r) over the current encode_evex(...)?

Yeah, this could be nice! If the flags don't have any relationship with each other, it might be possible to pass a &sink to the new() function and encode it as we call the builder functions. Alternatively, deferring it all and building in encode(&sink) sounds good too! And if this works out well, we could refactor a bit the previous encode functions; their API really looks a bit too C-ish.

a better integration with Inst than XmmUnaryRmREvex { op: Avx512Opcode, ...}? I cannot just add a boolean evex field to XmmUnaryRmR because some AVX512 instructions (e.g. VPABSQ) don't exist so they should not be included in SseOpcode. But the XmmUnaryRmREvex approach is not going to scale to a bunch of other instructions well.

Why wouldn't this scale well, out of curiosity? In general I think we should tend to APIs that make it impossible to create invalid instructions. It might not be the case for existing APIs, which should be refactored ideally...

@bnjbvr, the latest commit moves to the builder pattern. It's a hybrid of your idea: the EVEX 4-byte prefix is built up as the builder methods are called but we still need to call .encode(sink) to emit later because some methods, e.g. .reg(...), modify both the prefix and the ModR/M byte, which are emitted at completely different times.
Being a bit paranoid about performance, I benchmarked the encode_evex function approach and the current EvexInstruction builder approach by encoding the same instruction repeatedly inside bencher. For some reason, the builder approach turns out to be faster:
test isa::x64::inst::encoding::evex::tests::encode_with_function ... bench:          17 ns/iter (+/- 0
test isa::x64::inst::encoding::evex::tests::encode_with_builder  ... bench:           6 ns/iter (+/- 0)

I didn't dig too deep into this since @cfallin mentioned that emission is hardly the long pole in the tent. I was happy enough that this builder approach was not slower and left it at that. I think this is ok to review and merge understanding that there are still pieces coming (e.g. this only supports reg-reg addressing).

Why wouldn't this scale well, out of curiosity?

 Finding the right Inst variant when adding a new instruction can be tricky: "so this is unary, right, so I'm going to use that... no wait, I need to use the Xmm form... no, hold on, this is AVX512 so I need to find the Evex form of that." It's a developer experience thing more than anything. I agree that we should restrict the inputs somehow to only generate valid instructions but this "which Inst variant?" question seems a bit different.

@bnjbvr, can you take another look at this when you get a chance?

@bnjbvr, can you take another look at this when you get a chance?

Yep, happy to take a look in the next few days!


MovierulzHD

Source name
MovierulzHD
Source link
https://1movierulzhd.bar/movierulz-2024-watch-free-movies-online-hindi-telugu-tamil-english/
Source language
English ,Hindi , Telugu , Tamil , Kannada
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist on the website extensions list or the app.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

Due to a DMCA takedown notice, we will not add any more piracy streaming sites


(kubernetes) Unable to ping pod from a pod inside different node.

Hi guys,  could you help me on this problem?
Expected Behavior

Current Behavior

I'm currently running a kubernetes with 1 master and 3 followers, using the latest flannel cni.
[root@cu05 ~]# kubectl get no
NAME   STATUS   ROLES    AGE     VERSION
cu01   Ready    <none>   2d12h   v1.19.2
cu03   Ready    <none>   2d12h   v1.19.2
cu04   Ready    <none>   2d12h   v1.19.2
cu05   Ready    master   2d12h   v1.19.2

pods:
kube-system   coredns-6d56c8448f-jqwk9             1/1     Running   1          2d12h
kube-system   coredns-6d56c8448f-nhzdx             1/1     Running   1          2d12h
kube-system   etcd-cu05                            1/1     Running   1          2d12h
kube-system   kube-apiserver-cu05                  1/1     Running   0          39h
kube-system   kube-controller-manager-cu05         1/1     Running   1          2d12h
kube-system   kube-flannel-ds-bffst                1/1     Running   0          15h
kube-system   kube-flannel-ds-hbgp5                1/1     Running   0          15h
kube-system   kube-flannel-ds-nwr7x                1/1     Running   0          15h
kube-system   kube-flannel-ds-xdgdf                1/1     Running   0          15h
kube-system   kube-proxy-5rfrg                     1/1     Running   0          14h
kube-system   kube-proxy-b9kmw                     1/1     Running   0          14h
kube-system   kube-proxy-cl4hf                     1/1     Running   0          14h
kube-system   kube-proxy-khx5p                     1/1     Running   0          14h
kube-system   kube-scheduler-cu05                  1/1     Running   2          2d12h

It doesn't seem anything wrong to me. Here are the services:
[root@cu05 ~]# kubectl get svc
NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)       AGE
kubernetes             ClusterIP   <IP_ADDRESS>       <none>        443/TCP       2d12h
mysql-service          ClusterIP   <IP_ADDRESS>    <none>        3306/TCP      40h

Endpoints:
[root@cu05 ~]# kubectl get ep -A
NAMESPACE     NAME                      ENDPOINTS                                                 AGE
default       kubernetes                <IP_ADDRESS>:6443                                        2d12h
default       mysql-service             <IP_ADDRESS>:3306                                        40h
kube-system   kube-controller-manager   <none>                                                    2d12h
kube-system   kube-dns                  <IP_ADDRESS>:53,<IP_ADDRESS>:53,<IP_ADDRESS>:9153 + 3 more...   2d12h
kube-system   kube-scheduler            <none>                                                    2d12h

As you can see, I have a mysql-5.7 pod running in the cluster node cu03, which has pod clusterip <IP_ADDRESS>.
A mysql service that has an ep points to that pod.
On a pod scheduled on node cu03, I'm able to log on to mysql server, using
(base) root@CU03:~# docker exec -it 0b1adfd5abae /bin/bash
root@mysql-rc-hb8gv:/# mysql -u root -h <IP_ADDRESS> -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 128
Server version: 5.7.31 MySQL Community Server (GPL)

Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql>

But it isn't working when I try to login mysql to that service on other nodes.
Try to connect to pod ip:
[root@cu05 ~]# docker exec -it dfb2ff149a62 /bin/bash
root@mysql-testbox-cu05:/# mysql -u root -h <IP_ADDRESS> -p
Enter password:

Then no reply.
[root@cu05 ~]# docker exec -it dfb2ff149a62 /bin/bash
root@mysql-testbox-cu05:/# mysql -u root -h <IP_ADDRESS> -p
Enter password:

No reply either.
What's the possible problem? I checked the logs of flannel and found nothing wrong. They're using correct ifaces. And when I try to schedule pods from master(cu05) nothing went wrong. But in a pod running in cu05 or cu01, I can't even ping the running pod on cu03. I do able to ping the service IP <IP_ADDRESS> on  cu05 or cu01, but not able to use it. Only when I deliberately schedule the mysql pod to cu05, like adding nodeName: cu05, the pod starts to run on cu05, and I'm able to use that service on the same node, different pod inside kubernetes.
Possible Solution

Steps to Reproduce (for bugs)

Install kubernetes with kubeadm
Install flannel with flannel.yml
Deploy mysql-rc with only one replica, app:mysql.
Create a service that exposes container port 3306 with clusterIp <IP_ADDRESS>:3306
Create mysql-client pod on same node with the mysql pod, able to login with mysql -h  <IP_ADDRESS>
Create mysql-client pod on different node with the mysql pod, not able to login.

Context

Your Environment

Flannel version:
Backend used (e.g. vxlan or udp):
Etcd version:
Kubernetes version (if used):
Operating System and version:
Link to your project (optional):

It turns out that the iptable is poisoned. When I flushed the iptables using iptable --flush, the connectivity gets back again. Closing the issue here.


🕵♀ Investigate My Detail - INC1619899 - Slow performance and create a ⚡report on findings

User Story
As a Cloud Ops team member
I want to improve the incident process
So that incidents are not bounced unnecessarily around teams.
Value / Purpose

INC1619899 has highlighted the fact that the current incident process struggles with the rate of change in the business.
Neil mentioned in SU that not every alert is an incident.
Dan mentioned we can use the slackbot as a trigger to the API to raise incidents when it's been declared.
Simplify comms by keeping it in channel

Useful Contacts
Rich B, any ServiceNow user.
Additional Information
Definition of Done

[ ] Discussion on findings
[ ] issues raised from discussion.

Perform a retro on this to understand why this has been passed around / look for improvement actions in the process.
Caroline Jones - Incident management (Useful Contact for bouncing incidents)


Fix code highlighting / formatting in README

We actually need this to stay as is. We consume this .md file on developers.google.com/web and adding the gh flavored syntax highlighting messes that up. See https://github.com/GoogleChrome/puppeteer/commit/9b06ed28ae72ee3aa6de1f8b534f51347320b4a6#diff-04c6e90faac2675aa89e2176d2eec7d8


Ignore torches if ENB Light.esp is active - else the patcher will divide them for the second time

Reported by Fuzzles

already fixed


Build and test on ESP32, ESP8266 and mbed based webservers

For the first release, I'll target being able to deploy a full web-based embed control on ESP and mbed hardware.

We've got the most basic functions working on an ESP32, new issues will be raised as needed.

We've got the most basic functions working on an ESP32, new issues will be raised as needed.


Highlights / Top Usage

https://www.figma.com/design/MxA95ZHK5NqGX4ptFQljRJ/⭐-Design-System-3.0?node-id=6816-102697&t=2NDU1npQJhizQlPo-11  - Design Mockup


padding fixes

On medium screens there was no padding around the content.

I hope this time there's not much to debate... @bonustrack :P

Thank you that's great. Can you just make the end of search input aligned to the feed?

done

Well... I don't feel very comfortable doing a report for every few lines of code I changed... :/
But there will be a report from me today about something else... I'll post it as soon as @heimindanger posted his update on dtube. ;)

Works for me :)


Updated storage engine doc

Fixes #479 #581
cc @rkuchan @beckettsean

@jwilder awesome, thanks! Presumably we could back-port this to the 0.13 docs if we wanted?
@rkuchan  I want to make some structural changes, so I'm gonna accept this PR and then submit my own for the macro edits.

Yes.  Should be relevant for 0.13 as well.  Feel free to edit as needed.


Electron

I was thinking that maybe migrating the project to http://electron.atom.io/ would be very cool. So it could be used as a desktop demo player as well. After my exams I will gladly help with it.

Great idea, but I would create a new project that uses this one as a library. Let me know when you're done with your exams and we'll do it.


Log rotation

See #1964
In addition to shipping logs we also need to rotate them so they don't get too huge

See https://github.com/uber-go/zap/blob/master/FAQ.md#does-zap-support-log-rotation


Add alias for EnumNaming and EnumEntryNameCase

Fixes #7491
We didn't have the alias for these two rules

Warnings

:warning:
It looks like this PR contains functional changes without a corresponding test.

  Generated by :no_entry_sign: dangerJS against a0b03dfd39f57fca3f48cc81a80c697db94ae973


Bump external-snapshotter and aws-iam-authenticator versions

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


 I asked a generic question on http://stackoverflow.com/questions/30176068/how-to-repair-a-corrupted-collection-in-arangodb but just noticed something interesting in the arangod.log that might be too specific for StackOverflow:
2015-05-11T05:16:07Z [15927] INFO ArangoDB (version 2.5.3 [linux]) is ready for business. Have fun!
2015-05-11T05:17:02Z [15927] INFO control-c received, beginning shut down sequence
2015-05-11T05:17:09Z [16007] INFO ArangoDB 2.5.3 64bit -- ICU 52.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1f 6 Jan 2014
2015-05-11T05:17:09Z [16007] INFO using default language 'en'
2015-05-11T05:17:10Z [16007] INFO loaded database '_system' from '/var/lib/arangodb/databases/database-115750'
2015-05-11T05:17:10Z [16007] INFO JavaScript using startup '/usr/share/arangodb/js', application '/var/lib/arangodb-apps'
2015-05-11T05:17:10Z [16007] INFO using V8 options '--harmony --harmony_arrow_functions'
2015-05-11T05:17:12Z [16017] INFO ArangoDB 2.5.3 64bit -- ICU 52.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1f 6 Jan 2014
2015-05-11T05:17:12Z [16017] INFO using default language 'en'
2015-05-11T05:17:12Z [16017] INFO starting up in supervisor mode
2015-05-11T05:17:12Z [16019] INFO loaded database '_system' from '/var/lib/arangodb/databases/database-115750'
2015-05-11T05:17:12Z [16019] INFO running WAL recovery (1 logfiles)
2015-05-11T05:17:12Z [16019] INFO replaying WAL logfile '/var/lib/arangodb/journals/logfile-991553616778.db' (1 of 1)
2015-05-11T05:17:12Z [16019] INFO WAL recovery finished successfully
2015-05-11T05:17:12Z [16019] INFO using endpoint 'tcp://<IP_ADDRESS>:8529' for non-encrypted requests
2015-05-11T05:17:12Z [16019] INFO using endpoint 'tcp://<IP_ADDRESS>:8529' for non-encrypted requests
2015-05-11T05:17:12Z [16019] INFO using default API compatibility: 20500
2015-05-11T05:17:12Z [16019] INFO JavaScript using startup '/usr/share/arangodb/js', application '/var/lib/arangodb-apps'
2015-05-11T05:17:12Z [16019] INFO using V8 options '--harmony --harmony_arrow_functions'
2015-05-11T05:17:14Z [16019] INFO In database '_system': Database is up-to-date (20503/prod/standalone/existing)
2015-05-11T05:17:14Z [16019] WARNING collection 'wdt_packs' already exists. Leaving it untouched.
2015-05-11T05:17:14Z [16019] WARNING collection 'wdt_timers' already exists. Leaving it untouched.
2015-05-11T05:17:14Z [16019] WARNING collection 'wdt_timerLogs' already exists. Leaving it untouched.
2015-05-11T05:17:15Z [16019] INFO permanently changing the gid to 999
2015-05-11T05:17:15Z [16019] INFO permanently changing the uid to 999
2015-05-11T05:17:15Z [16019] INFO ArangoDB (version 2.5.3 [linux]) is ready for business. Have fun!
2015-05-11T16:22:09Z [16019] WARNING collection 'wdt_packs' already exists. Leaving it untouched.
2015-05-11T16:22:09Z [16019] WARNING collection 'wdt_timers' already exists. Leaving it untouched.
2015-05-11T16:22:09Z [16019] WARNING collection 'wdt_timerLogs' already exists. Leaving it untouched.
2015-05-11T16:22:31Z [16019] WARNING accept failed with 24 (Too many open files)
2015-05-11T16:22:31Z [16019] WARNING accept failed with 24 (Too many open files)
2015-05-11T16:22:31Z [16019] WARNING accept failed with 24 (Too many open files)

lot's of these and then
2015-05-11T16:22:31Z [16019] WARNING accept failed with 24 (Too many open files)
2015-05-11T16:22:31Z [16019] ERROR too many accept failures, stopping logging
2015-05-11T16:22:31Z [16019] WARNING accept failed with 24 (Too many open files)

...
2015-05-11T16:22:31Z [16019] WARNING accept failed with 24 (Too many open files)
2015-05-11T16:22:31Z [16019] ERROR too many accept failures, stopping logging
2015-05-11T16:22:31Z [16019] ERROR cannot open datafile '/var/lib/arangodb/databases/database-115750/collection-400775147359/datafile-400830197599.db': 'Too many open files'
2015-05-11T16:22:31Z [16019] ERROR cannot open datafile '/var/lib/arangodb/databases/database-115750/collection-400775147359/datafile-400830197599.db': Too many open files
2015-05-11T16:22:31Z [16019] ERROR cannot open document collection from path '/var/lib/arangodb/databases/database-115750/collection-400775147359'
2015-05-11T16:22:31Z [16019] WARNING accept failed with 24 (Too many open files)
2015-05-11T17:24:28Z [16019] ERROR Error in foxx route '{ "match" : "/timers/timers", "methods" : [ "post" ] }': 'corrupted collection', Stacktrace: Error: corrupted collection
2015-05-11T17:24:28Z [16019] ERROR   at Error (native)
2015-05-11T17:24:28Z [16019] ERROR   at /var/lib/arangodb-apps/_db/_system/wdt/APP/controllers/timers.js:113:22
2015-05-11T17:24:28Z [16019] ERROR   at Object.res.action.callback (/usr/share/arangodb/js/server/modules/org/arangodb/foxx/internals.js:108:5)
2015-05-11T17:24:28Z [16019] ERROR   at /usr/share/arangodb/js/server/modules/org/arangodb/foxx/routing.js:323:19
2015-05-11T17:24:28Z [16019] ERROR   at execute (/usr/share/arangodb/js/server/modules/org/arangodb/actions.js:1304:7)
2015-05-11T17:24:28Z [16019] ERROR   at next (/usr/share/arangodb/js/server/modules/org/arangodb/actions.js:1321:7)
2015-05-11T17:24:28Z [16019] ERROR   at routingInfo.middleware.push.action.callback (/usr/share/arangodb/js/server/modules/org/arangodb/foxx/controller.js:416:53)
2015-05-11T17:24:28Z [16019] ERROR   at execute (/usr/share/arangodb/js/server/modules/org/arangodb/actions.js:1304:7)
2015-05-11T17:24:28Z [16019] ERROR   at next (/usr/share/arangodb/js/server/modules/org/arangodb/actions.js:1321:7)
2015-05-11T17:24:28Z [16019] ERROR   at routingInfo.middleware.push.action.callback (/usr/share/arangodb/js/server/modules/org/arangodb/foxx/controller.js:379:13)
2015-05-11T17:24:28Z [16019] ERROR   at execute (/usr/share/arangodb/js/server/modules/org/arangodb/actions.js:1304:7)
2015-05-11T17:24:28Z [16019] ERROR   at next (/usr/share/arangodb/js/server/modules/org/arangodb/actions.js:1321:7)
2015-05-11T17:24:28Z [16019] ERROR   at [object Object]:386:5
2015-05-11T17:24:28Z [16019] ERROR   at execute (/usr/share/arangodb/js/server/modules/org/arangodb/actions.js:1304:7)
2015-05-11T17:24:28Z [16019] ERROR   at routeRequest (/usr/share/arangodb/js/server/modules/org/arangodb/actions.js:1325:3)
2015-05-11T17:24:28Z [16019] ERROR   at foxxRouting (/usr/share/arangodb/js/server/modules/org/arangodb/actions.js:1095:7)
2015-05-11T17:24:28Z [16019] ERROR   at execute (/usr/share/arangodb/js/server/modules/org/arangodb/actions.js:1304:7)
2015-05-11T17:24:28Z [16019] ERROR   at Object.routeRequest (/usr/share/arangodb/js/server/modules/org/arangodb/actions.js:1325:3)
2015-05-11T17:24:28Z [16019] ERROR   at Function.actions.defineHttp.callback (/usr/share/arangodb/js/actions/api-system.js:51:15)
2015-05-11T17:24:28Z [16019] ERROR

I just restarted arangod and it seems to be working again
2015-05-11T19:29:49Z [16019] INFO control-c received, beginning shut down sequence
2015-05-11T19:44:29Z [19847] INFO ArangoDB 2.5.3 64bit -- ICU 52.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1f 6 Jan 2014
2015-05-11T19:44:29Z [19847] INFO using default language 'en'
2015-05-11T19:44:30Z [19847] INFO loaded database '_system' from '/var/lib/arangodb/databases/database-115750'
2015-05-11T19:44:30Z [19847] INFO JavaScript using startup '/usr/share/arangodb/js', application '/var/lib/arangodb-apps'
2015-05-11T19:44:30Z [19847] INFO using V8 options '--harmony --harmony_arrow_functions'
2015-05-11T19:44:33Z [19857] INFO ArangoDB 2.5.3 64bit -- ICU 52.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1f 6 Jan 2014
2015-05-11T19:44:33Z [19857] INFO using default language 'en'
2015-05-11T19:44:33Z [19857] INFO starting up in supervisor mode
2015-05-11T19:44:34Z [19859] INFO loaded database '_system' from '/var/lib/arangodb/databases/database-115750'
2015-05-11T19:44:34Z [19859] INFO running WAL recovery (1 logfiles)
2015-05-11T19:44:34Z [19859] INFO replaying WAL logfile '/var/lib/arangodb/journals/logfile-991566571963.db' (1 of 1)
2015-05-11T19:44:34Z [19859] INFO WAL recovery finished successfully
2015-05-11T19:44:34Z [19859] INFO using endpoint 'tcp://<IP_ADDRESS>:8529' for non-encrypted requests
2015-05-11T19:44:34Z [19859] INFO using endpoint 'tcp://<IP_ADDRESS>:8529' for non-encrypted requests
2015-05-11T19:44:34Z [19859] INFO using default API compatibility: 20500
2015-05-11T19:44:34Z [19859] INFO JavaScript using startup '/usr/share/arangodb/js', application '/var/lib/arangodb-apps'
2015-05-11T19:44:34Z [19859] INFO using V8 options '--harmony --harmony_arrow_functions'
2015-05-11T19:44:37Z [19859] INFO In database '_system': Database is up-to-date (20503/prod/standalone/existing)
2015-05-11T19:44:37Z [19859] WARNING collection 'wdt_packs' already exists. Leaving it untouched.
2015-05-11T19:44:37Z [19859] WARNING collection 'wdt_timers' already exists. Leaving it untouched.
2015-05-11T19:44:37Z [19859] WARNING collection 'wdt_timerLogs' already exists. Leaving it untouched.
2015-05-11T19:44:37Z [19859] INFO permanently changing the gid to 999
2015-05-11T19:44:37Z [19859] INFO permanently changing the uid to 999
2015-05-11T19:44:37Z [19859] INFO ArangoDB (version 2.5.3 [linux]) is ready for business. Have fun!

I'll close that StackOverflow question again.

Basically it means that you ran out of file descriptors. You should raise the number of open files to something like 2000 or 4000. You could add
server.descriptors-minimum
to the arangod.conf to ensure that the number is available.

It normally happens if you open a lot of connections to the server. Each connections needs one file descriptor. If you eat up all allowed file descriptors, there is no way for ArangoDB to open its datafiles.
Therefore you need to raise the limit. ArangoDB can handle 10K or more connections.

I don't think I did open a lot of connections. My app is still private and I'm the only user. According to my nginx log file, there was no unusual activity against my Foxx app. I'm also accessing the DB via arangojs from another server with only about 3 roundtrips per minute.
Also interesting, using aardvark I was still able to use the other 2 collections.

You could check the number of connections using netstat. Which OS are you using?

Ubuntu 14.04.2 LTS
3.13.0-43-generic x86_64

And which node.js version? There seems to be some weird thing going on with node.js & connections. Can you try to issue a
netstat -anpt

after a while? This should show how many connections are open. On my ubuntu the defaut limit is 1024.

I'm using iojs v1.8.1
netstat | grep ":8529" | wc -l has been hovering between 8 and 18 since I've restarted 40 minutes ago. I'll keep an eye on it.

For info: it's not only the number of connections, but also the number of files opened by arangod that matter. That includes WAL logfiles (usually just a handful) but also collection datafiles. If there are many collections available with lots of files, then it might be sensible to raise the ulimit value for max open files.

Can you also check the open files? "lsof" should list them.

lsof | grep "arangodb" | wc -l: 1570
Is that high or normal?

Can you post the output without the wc? Or send it to hackers (at) arangodb.com if it contains sensitive information.

https://gist.github.com/pekeler/b2c657dde30d707ec20f

How many collections / database do you have?

I have 3 collections in _system, no extra DB.

I thinks lsof is displaying each thread separately. Therefore the high numbers. So it is unclear why the file descriptors where used up. If the situation arises again, can you do the netstat and lsof?

Perhaps I've structured one of my collections in a suboptimal way. The documents look like:
{
  "someFK": "123456789",
  "log": [
    [1,<PHONE_NUMBER>000, "foo", "bar"],
    [8,<PHONE_NUMBER>000, "baz", "uh"],
...
  ]
}

The "log" array is limited to 1000 elements. Every minute I slice and unshift the array with AQL:
'FOR tl IN myLogs FILTER tl.someFK == @aKey UPDATE tl WITH {log: SLICE(UNSHIFT(tl.log, @logEntry), 0, 1000)} IN myLogs

Any chance this structure contributed to the problem?

No, that should not cause such problems.

OK, thanks. I'll make sure to netstat and lsof and report back when I see the problem again.

Couldn't you use a cap collection constraint instead to limit the number of entries? If there are plenty of such documents with their own doc key, then probably not...

@CoDEmanX I have plenty of such documents, and will get more over time, so I don't think I should create a collection for each.


Getting started instructions to install python should probably be consistent with tutorial docs

Currently we have the getting started experience, which for example in windows, points users to the windows store python. However our tutorial https://code.visualstudio.com/docs/python/python-tutorial#_install-a-python-interpreter is a little different. https://code.visualstudio.com/docs/python/python-tutorial#_install-a-python-interpreter is also linked to in some of our prompts the extension uses, to recommend users from where to install python.
cc/ @luabud

Note Windows store may not be available for Windows 8, so it's probably best to point to python.org.


Exporting Layer Groups as separate images ontop of set background

Hi,
I'm wondering if this is the same plugin that I used here:
http://magoarcade.org/docs/doku.php?id=software:gameexthemeeditor:start
Pic of the 'old' settings:
http://magoarcade.org/docs/lib/exe/fetch.php?media=mediaexport.png
I'm back to this now for a new gimp project, but if it is the same plugin, the settings have changed a lot! I'm trying to achieve the same thing. Have a single Background image and then export a separate image for each Layer Group (i.e. a composite of the layer group and the background) - should be able to do in  a batch run. Here's my layout:

And my settings:

BaseWheel is tagged "Background" and the upper two layer groups as "foreground"
However, this just produces 3 identical images, each named after the Layer Group name:

Whereas, I'm aiming for it to have separate images, which consist of the background layer and then each of the separate foreground layer groups (not a composite of both)
Hope that makes sense! Any suggestions on how I could achieve this?
thanks

Nemmind. Figured it. I took "Foreground" tags off the layer groups to be transposed:

Issue sorted. Thanks for a great plugin!

Glad you got it working.

I'm wondering if this is the same plugin that I used here:

It indeed is, but a very old version (2.5 I think).


Add detainee and move information pages

Introduces:
A detainee information form page
A move information form page, capable of adding multiple destinations
It adds the following gems:
GovukElementsFormBuilder
Reform
Virtus

Looks good but where are the specs?

The commit history is kind of weird. In affc7a7 we've introduced the Detainee controller, view & associated form but the actual model & table in the DB don't exist yet. 😕

The detainee model has already been introduced on master

@cesidio my bad i misread Destination

Closing.. GitHub seems to not be able to see latest changes..


Flower and apple at same time counts as NoTouch

There seems to be an issue that if you touch flower and then pick last apple it counts the run as not finished (NoTouch).
From debugging the code it looks like the apple take event is last and the code checks only the last event. May have to check if there's other events also at the same time. Check this level and rec:
https://up.elma.online/u/eo497yn1xi/foodtest.lev
https://up.elma.online/u/9cyonu0cc3/foodtest.rec
Last four events in rec looks like this:
{ "time": 1.700025599992275, "touchInfo": 2, "type": 0, "groundInfo": 0 },
{ "time": 1.700025599992275, "touchInfo": 4, "type": 0, "groundInfo": 0 },
{ "time": 1.700025599992275, "touchInfo": 4, "type": 0, "groundInfo": 0 },
{ "time": 1.700025599992275, "touchInfo": -1, "type": 4, "groundInfo": 0.9900000095367432 }

To add to this, if you touch flower early in replay with apples left and then take apples it counts as 0 apples regardless of how many you take.
https://up.elma.online/u/937e1rbwci/lc408one.rec
https://up.elma.online/u/bgmaph64jr/lc408oneNoFlowe.rec
https://up.elma.online/u/oylqjksigd/lc408finish.rec
https://up.elma.online/u/6jnf83rbtd/lc408finNoFlowe.rec
lc408one.rec touch flower, one apple, death: { finished: false, time: 22433, reason: 'NoTouch', apples: 0 }
lc408oneNoFlowe.rec one apple, death: { finished: false, time: 18566, reason: 'NoTouch', apples: 1 }
lc408finish.rec touch flower, five apples, finish: { finished: true, time: 66807, reason: 'Touch', apples: 0 }
lc408finNoFlowe.rec five apples, finish: { finished: true, time: 86896, reason: 'Touch', apples: 5 }

I found some more cases with DNF misdetection, hope it's okay to add them in here:

dying to killer is not marked as DNF - https://elma.online/r/hztfiebqdn/03fuck
touching the flower without taking all apples and then escing the run is not marked as DNF - https://elma.online/r/ibqzhjexgd/28chal30Tigro


Android build fails because of ''when' expression must be exhaustive' error

When running the android build, I get the following error:
> Task :amazon-ivs-react-native-player:compileReleaseKotlin FAILED
e: /Users/.../app/node_modules/amazon-ivs-react-native-player/android/src/main/java/com/amazonaws/ivs/reactnative/player/AmazonIvsView.kt: (289, 5): 'when' expression must be exhaustive, add necessary 'BUFFERING', 'IDLE', 'ENDED' branches or 'else' branch instead

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':amazon-ivs-react-native-player:compileReleaseKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
   > Compilation error. See log for more details

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
java.lang.StackOverflowError (no error message)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 7s
59 actionable tasks: 3 executed, 56 up-to-date

React native version 0.70.6
amazon-ivs-react-native-player version 1.2.0

Any idea on how to solve this?

We are looking into this and will get back to you. Thanks for reporting it.

@anatoleblanc Yes, for now it's necessary to downgrade Kotlin in build.gradle to a version lower than 1.7.0, since from that version on Kotlin checks for 'Exhaustiveness of When Statements' - see here.
This should be a temporal fix until amazon-ivs-react-native-player refactors this and checks all status branches or implements some other solution in the onPlayerStateChange method.


Max-height restriction

Max-height only works if the style is inlined. if applying a class to the textarea element it will not work!

I can't recreate this, max-height works for me wherever I apply it. Could be CSS specificity issue perhaps? Able to show a test case? Thanks.

In addition I would recommend to remove resize: none when max height has been reached.

Moving max-height from inline to class breaks my scroll (it doesn't show), however the textarea still honors the max-height value set in class.

Closed due to inactivity


Converted Inkscape SVGs into plain SVGs

I converted all of the inkscape svgs into plain svgs which saved some kilobytes of storage.

resolves #75

Cherry picked commit cca5924 in favour of merging an unfinished feature.
Additionally removed metadata with the regex >[\W]*<metadata[.\s\S]*</metadata> --> >


Explicitly Use GPU

How do I explicitly tell a session to use my computer's GPU rather than CPU? The python binding seems to do that by default:
python
Python 2.7.13 (default, Dec 28 2016, 13:21:25)
[GCC 5.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcurand.so.8.0 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcufft.so.8.0 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcudnn.so.5 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcublas.so.8.0 locally
>>> session = tf.Session(config=tf.ConfigProto(log_device_placement=True))
E tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:896] could not open file to read NUMA node: /sys/bus/pci/devices/0000:01:00.0/numa_node
Your kernel may have been built without NUMA support.
I tensorflow/core/common_runtime/gpu/gpu_device.cc:885] Found device 0 with properties:
name: GeForce GTX 1080
major: 6 minor: 1 memoryClockRate (GHz) 1.7715
pciBusID 0000:01:00.0
Total memory: 7.92GiB
Free memory: 7.81GiB
I tensorflow/core/common_runtime/gpu/gpu_device.cc:906] DMA: 0
I tensorflow/core/common_runtime/gpu/gpu_device.cc:916] 0:   Y
I tensorflow/core/common_runtime/gpu/gpu_device.cc:975] Creating TensorFlow device (/gpu:0) -> (device: 0, name: GeForce GTX 1080, pci bus id: 0000:01:00.0)
I tensorflow/core/common_runtime/gpu/gpu_device.cc:586] Could not identify NUMA node of /job:localhost/replica:0/task:0/gpu:0, defaulting to 0.  Your kernel may not have been built with NUMA support.
Device mapping:
/job:localhost/replica:0/task:0/gpu:0 -> device: 0, name: GeForce GTX 1080, pci bus id: 0000:01:00.0
I tensorflow/core/common_runtime/direct_session.cc:257] Device mapping:
/job:localhost/replica:0/task:0/gpu:0 -> device: 0, name: GeForce GTX 1080, pci bus id: 0000:01:00.0

>>>

When I call Session.run with the ocaml bindings however, I get the following log messages:
$ _build/default/main.exe
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE3 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.1 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.2 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX2 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use FMA instructions, but these are available on your machine and could speed up CPU computations.

which seems to imply that it's using CPU rather than GPU.

Indeed it seems that you're using the cpu rather than your gpu here.
Are you using the gpu or cpu version of libtensorflow.so ? If you don't remember I would suggest you try again with the gpu version of release 1.2 if you're using the current github tip or the gpu version of release 1.0 if you're using the opam package.

ah - it turns out that building the shared libraries by default build only the CPU libraries. I used the one you provided and it works as expected. Thanks!


CSI External Attacher CVE fix: Address GHSA-xr7q-jx4m-x55m

Issue #, if available:
Address GHSA-xr7q-jx4m-x55m
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


RPM not available after BIG-IP upgrade

The cloud failover extension disaappears after you upgrade the BIG-IP.
Workaround
You must re-install the cloud failover RPM in order for the failover to work properly. The failover declaration JSON is still intact. However, without the RPM/extension installed then you will receive a 404 error due to endpoint missing.

Thanks for reporting this. This has been added to the backlog, internal ID AUTOSDK-398.

This is a duplicate of https://github.com/F5Networks/f5-cloud-failover-extension/issues/48.
Internal tracking ID AUTOSDK-448.
Closing this now.


test - 1600 estimate gas with precompiles more tests added

Added more tests for estimate gas with precompiles
Added tests for ERC contract functions
added tests for Redirect functions
added tests for read functions

Note: More tests related to create token functions should be added

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (cf011f6) 77.83% compared to head (a6ae5b0) 77.83%.
 Consider uploading reports for the commit ee15b2e to get more accurate results

Files
Patch %
Lines

packages/relay/src/lib/eth.ts
50.00%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2026   +/-   ##
=======================================
  Coverage   77.83%   77.83%
=======================================
  Files          40       40
  Lines        3086     3086
  Branches      625      626    +1
=======================================
  Hits         2402     2402
  Misses        479      479
  Partials      205      205

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


Update cosmo claw

launch jenkins<EMAIL_ADDRESS>

@elsagermann I have some dependency on cosmo I want to check before merging this

launch jenkins --test=root cosmo<EMAIL_ADDRESS>


running prophet4j

I followed the steps to build the project. However, I couldn't make the tool produce prophet4J features for repogit4testv0. Actually, I couldn't find instructions to produce p4j features. Could you please guide me regarding this problem?

hi @mainjar1
which mode do you use? Prophet4J features are only available in mode files
FYI WIP in https://github.com/SpoonLabs/coming/pull/262

potential fix in branch fixfeature. Could you give it a try?

Hi @mainjar1 this is fixed in master, see #263


I want to delete an SBOM (maybe other stuff too)

I just uploaded and SBOM and want to get rid of it from the system.

[x] Provide an API for deleting the document
[ ] Amend the UI to support this

belated observation: what is the rbac/acl mechanism for authorising a user to mutate ?

belated observation: what is the rbac/acl mechanism for authorising a user to mutate ?

At present, we have this, used like so.


Export Distribution clarifications

Can you please document what works in Export Distribution and what doesn't? Is there an export channel that is functional?
Thanks a lot

@rtmaster I have added mqtts, and https was already supported

Thanks @chenchix


ownerscheck with labels

Signed-off-by: Itay Donanhirsh<EMAIL_ADDRESS>Description:
Configure ownerscheck to work with labels.
Risk Level:
Low.
Testing:
In this PR.
Docs Changes:
None
Release Notes:
None

/rk-bless

/checkowners!

api shepherds, please ignore.

/assign @htuch
/rk-unbless

/retest

/rk-bless

/rk-unbless


Upon startup with web components, hooks error shows up

When using web components (at least thats what I'm using), when starting up with this addon included all stories show up like this:

Error: "Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:"
version: 0.0.5
storybook version: 6.4.19
node: 14.18.0
Really excited about this addon because I think it could be really helpful! just cant get it up and running

Thanks for the report @CodeByAlex! I was able to reproduce this issue with a @storybook/web-components setup.
This is fixed in 0.0.6 version!

Wow -This was really fast! Thanks!


Redeploy lambda edge function via cli

Solution is to redeploy the whole upload package for correct memory and timeout to take effect.


Bundler: CSS variables are not compiled

Just realized that CSS variables are not compiled anymore for some reason. E.g. in Substance make file:
b.css('substance.css', DIST+'substance.css', { variables: true })

When looking at dist/substance.css there's still the variable block.
@oliver---- is this a bundler regression? Or some misconfiguration?
We should fix and make another patch release.

Wait.. I'm totally wrong. Everything is fine. Just got confused that the variable block is still in the CSS and the comments:
:root {
  /* Layout */

  /* Normalized heights (used by buttons and inputs) */

  /* Colors */

  /* Used by Button component */ /* #f8f8f8; */

  /* Depending on a base-color */

  /* We disable this for now, as accessibility needs more discussion */ /* #1795CD;/* #5BE3FF;

  /* Font colors */

  /* Default padding */

  /* Prose font sizes */
  /* Title font sizes */
  /* Heading font sizes */

  /* code-font */

  /* RGB #A3CDFD = HSB 209,29,80 */

  /* Collaborator colors */
}

While this works as expected in Substance it does not in forms, there I still see the variables. :/ No idea what the difference is. The make file looks ok.

Mhhh with a fresh clone and npm install now it worked.

fresh clone does not sound reasonable. Maybe rm -rf of node_modules would have been enough.

Yeah that's what I actually did. Thx ;)


trying to install the tool give error

go: github.com/projectdiscovery/dnsprobe upgrade => v1.0.1
go: github.com/projectdiscovery/retryabledns upgrade => v1.0.4
go: golang.org/x/sys upgrade => v0.0.0-20200420163511-1957bb5e6d1f
go: golang.org/x/crypto upgrade => v0.0.0-20200423211502-4bdfaf469ed5
go: golang.org/x/net upgrade => v0.0.0-20200425230154-ff2c4b7c35a0
github.com/projectdiscovery/dnsprobe/lib
github.com/projectdiscovery/dnsprobe/lib
/home/cypher/Desktop/githubTools/go/pkg/mod/github.com/projectdiscovery/dnsprobe@v1.0.1/lib/dnsprobe.go:41:17: assignment mismatch: 2 variables but "github.com/projectdiscovery/retryabledns".New returns 1 values

yep, latest commit in retryabledns see here changes signature of .New and thatÄs the reason.

So on my end Can I do something to fix this? @schniggie

@cYph3r1337 - Thanks for the issue! The go modules dependencies have been updated, they were still pointing to the previous version of retryabledns. Could you confirm if now it works for you?
@schniggie Thanks a lot for the PR! I've added a correction for the signature to the same PR that updated the modules, so I'm closing yours if this is solved.

Closing as a result of #19


As a Kperf developer, I want to refine service generate/measure flags, code comments and etc.

Refine service generate and measure

[x] CLI flags

Per offline discussion with @qibobo who is working on refining, this Issue will also cover

[ ] Add more code comment

As suggested https://github.com/knative-sandbox/kperf/pull/3#discussion_r509885265

[ ] Variable definition
As commented https://github.com/knative-sandbox/kperf/pull/3/files#r509885363
https://github.com/knative-sandbox/kperf/pull/3/files#r509885434, good to add a common function.

/assign @qibobo
Yang is helping with this. Thanks!

PR merged. Close it.


Plugin still not working

I refer here to this issue:
https://github.com/badsgahhl/pihole-browser-extension/issues/54
Since unfortunately no reaction was to be noted in the last days, I open hereby a new one.
I can gladly provide any log to analyze the problem.
I have the problem on two independent PiHole instances.

Please try the following to get some debug information:

open the settings page
enter your PiHole data
press F12 to open the dev console
press F5 to refresh the page
make a screenshot of the "console" and "network" tab in the dev console

do you mean like this?

Now I am embarrassed. Problem found. For some reason one of the piholes had the APIKey wrong.....
Corrected the second one and it works!
I am sorry!

😄 no problem.


Error when using the gem with ruby prior to 2.1

I'm having trouble using this gem with ruby prior to 2.1 in spite of the fact that there's no required minimum ruby version on the gem definition.
The problem is caused by this line

I'll take care of that in a few minutes.

Hey @weshatheleopard I created a PR for it already: https://github.com/weshatheleopard/rubyXL/pull/314 please take a look 😊


Add model: multilayer perceptrons.

Add multilayer perceptrons, which is the imnet model employed by LIIF.

On the locaiton of the file: is it a kind of refiner?

On the locaiton of the file: is it a kind of refiner?

I am not sure where should the file locate.
Can you give me a suggest? Thank you.


App crashes when updating Avatar

here's the crash report from my simulator
https://fabric.io/we-are-set-inc/android/apps/com.textile.dev/issues/7b593f85de3ef15f4dd087ddaceb83ff?time=last-seven-days
this is from an already onboarded account.

go to settings, change avatar
pick a new image from android camera roll
submit.
2-3 seconds the ui will seem locked up
followed by a full crash

Looks like a pretty common issue. Here's one popular answer: https://stackoverflow.com/a/50691494/641834

This looks like a more useful and recent bit of info: https://issuetracker.google.com/issues/76112072#comment122

I'm now seeing this when dropping and rejoining a cafe on Android (when i already have a group + some photos to upload). will check it out


Refactor Section::UpdateService

I don't think these single line methods were adding anything.

Thanks @floehopper. I've rebased and force pushed in preparation for merging.


JS DOM beforeunload events stop links from working

Microsoft Teams Desktop version <IP_ADDRESS>72
User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Teams/<IP_ADDRESS>72 Chrome/80.0.3987.163 Electron/8.5.5 Safari/537.36
My application is a website that has been added as a tab to a team.
Dependencies:

Bootstrap version 4.6.0
Popper.js version 1.16.1
JQuery version 3.6.0

Relevant code from my website:
    window.addEventListener("beforeunload", (e) => {         e.preventDefault();         e.returnValue = "";     });
After the event listener is added, all links that navigate to another page stop functioning. I think this might be due to Teams not displaying a confirmation box like Chrome does when there is a beforeunload event present.

@iComputer7 - Thank you for the insights. will repro at our end and will let you know.

I noticed that Teams updated recently, and the bug is still present. Version is Teams/<IP_ADDRESS>61

@iComputer7 - I have reproduced the same code that has been provided and able to repro the issue. Will be raising the same as bug if it's get confirmed from internal team and will inform you as soon as possible.

@iComputer7 -Microsoft Team SDK have  microsoftTeams.registerBeforeUnloadHandler() method to use it in their tab content pages.

I'm not sure what you mean

@iComputer7 - Teams won't support many JS events. So, you can use microsoftTeams.registerBeforeUnloadHandler() event in your teams tab instead of beforeunload event.


[mythx] e.loginWithToken is not a function

I'm currently getting authentication errors when using the MythX extension. The first analysis works fine, but when clicking "Analyze" the second time the report tab shows: "e.loginWithToken is not a function". It works again after reloading the page.

Browser is Chrome 79.0.3945.88 on Mac.

fixed https://github.com/aquiladev/remix-mythx-plugin/commit/a42e5aa9e41b08f943e18c3f681b1769acf61612

Awesome, can we get this merged into Remix prod ASAP plz 🙏

@b-mueller I asked guys to deploy the latest version 21 of Dec, still waiting for a response. I think it is holidays

finally, it is deployed. the issue can be closed


failed to call webhook  when deploy milvus2.x cluster

error infomation
Error from server (InternalError): error when creating "milvus_cluster_default.yaml": Internal error occurred: failed calling webhook "mmilvus.kb.io": failed to call webhook: the server could not find the requested resource
deploy by milvus-operator
yaml file:（https://github.com/milvus-io/milvus-operator/blob/main/config/samples/milvus_cluster_default.yaml）
apiVersion: milvus.io/v1beta1
kind: Milvus
metadata:
name: my-release
labels:
app: milvus
spec:
mode: cluster
dependencies: {}
components: {}
config: {}

Hi, which version of milvus-operator are you using?

I follow the steps of the official documentation to deploy， as follow：
kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.5.3/cert-manager.yaml
kubectl apply -f https://raw.githubusercontent.com/milvus-io/milvus-operator/main/deploy/manifests/deployment.yaml

I don't know how to find its version.

plz check if cert-manager started successfully by kubectl get pods -n cert-manager
Then check the pods of milvus-operator kubectl get pods -n milvus-operator
and paste the result here if you don't know whether thery're good.

It seems very close to this issue #129

They are all OK。
cert-manager-86b6c9bf4b-6g4qm              1/1     Running   0          3h32m
cert-manager-cainjector-7d4868cf69-zs4r5   1/1     Running   0          3h32m
cert-manager-webhook-6cb6fbfc58-z4kjp      1/1     Running   0          3h32m
milvus-operator-controller-manager-86f57c8f48-29rtw   1/1     Running   0          3h33m

Hi, the manifest is not using the latest image.
Try update the image. and wait for the new pod ready.  And it should be working.
kubectl -n milvus-operator \
  set image deploy/milvus-operator-controller-manager \
  manager=milvusdb/milvus-operator:main-latest

We'll fix this soon, and update the docs, thank you for report it. ❤

Hi, is mc of the command "kubectl delete mc my-release" a tool?
https://github.com/jonnylangefeld/kubectl-mc/tree/v1.0.1#speed-comparison
When I run that command, it comes out a error message as below:
Error from server (NotFound): milvusclusters.milvus.io "my-release" not found

Hi, is mc of the command "kubectl delete mc my-release" a tool? https://github.com/jonnylangefeld/kubectl-mc/tree/v1.0.1#speed-comparison When I run that command, it comes out a error message as below: Error from server (NotFound): milvusclusters.milvus.io "my-release" not found

No, the mc is old abbriviation of MilvusCluster crd. But in new version we use milvus for both standalone milvus & milvuscluster.
Maybe you're following some document, we should update them soon.
You can delete your milvus by kubectl delete milvus my-release.


zappi API enums for 'sta' and 'pst' properties

Apologies if these are already included in the repository/integration and I failed to find them through GitHub search.
Perhaps this is a feature request for the https://github.com/cjne/pymyenergi rather than ha-myenergi.
[API - pst] [HA entity - myenergi_zappi_XXXXXXXX_plug_status] :
A = EV Disconnected
B1 = EV Connected
B2 = Waiting for EV
C1 = EV ready to charge
C2 = Charging
F = Fault
[API - sta]  [HA entity - myenergi_zappi_XXXXXXX_status] :
1 = Paused
2 ??
3 = Diverting/Charging
4 = Waiting for surplus
5 = Complete
I am keen to work out how these two correlate with myenergi's RGB icon on the front of the zappi.
I would like to replicate the RGB colours on my entity card.
Has anyone observed the 'sta' value indicating whether the EV is diverting or boosting?

I will try and test what values are shown for the two entities over the next few days.

Currently have a scheduled boost charging the car. The zappi is set to Eco+ mode.
pst = C2
sta = 4  - which I understood to be "waiting for surplus" !??
myenergi_zappi_XXXXXXX_status state is "Boosting", so that's good 👍
myenergi_zappi_XXXXXXXX_plug_status state is "Charging" which matches the C2 👍
I have seen myenergi_zappi_XXXXXXX_status show "Diverting" when it's charging using excess PV generation. 👍


Add own bells to dataset

Add option to make Wheatley add his own bells to the regression dataset (which is on by default).  This will hopefully prevent Wheatley overfitting to the users' bells when Wheatley is ringing the majority of the bells.
Resolves #97

I guess the linter either hasn't managed to track the type hint from the constructor parameter to the field, or for some reason isn't using it to filter?
https://github.com/kneasle/wheatley/blob/ca0f47622e705ee10fdd932b0f6af800271e9b5a/wheatley/bot.py#L26-L29
I'm not surprised we don't have a unit test covering these method paths at the moment - one day we might get round to it.

I don't think the linter deals with type checking.  In my eyes the lack of typing is a major flaw in Python as a language, though I understand that many people see it as a strength.

Right I've fixed the merge conflicts so this should be ready to go

An issue with this is that Wheatley doesn't anticipate the Network Lag, so always thinks it's own bells are rung late.
You can hear / see (with RegressionRhythm logging on DEBUG) this by just setting Wheatley ringing all the bells to rounds and it quickly slows down and keeps slowing down.
Maybe a different approach of adding the time Wheatley wanted to ring at to the dataset instead?

Alternatively we could experiment with estimating and removing the network latency from user rung bells as well. But that seems a much more difficult problem to solve reliably even. I'm also not sure if it would help or hinder a band ringing on good connections with humans slightly anticipating where to ring.

Oh I hadn't thought of the effect of network latency on this - it doesn't make sense to add the return time to the dataset anyway.
I think in the interests of getting a fixed version out to the people wanting it, we should release 4.0 with current master branch.

I think in the interests of getting a fixed version out to the people wanting it, we should release 4.0 with current master branch.

I agree.

OK this is well and truly stale now.  At any rate, this feels like patching a problem rather than fixing it.


debug_scan: Result is not a Dictionary

Describe the bug
Starting the debug_scan throws the following error:
2022-09-19 04:05:43.651 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [22770838962432] Error handling message: Error rendering data template: Result is not a Dictionary (unknown_error)

To Reproduce
Steps to reproduce the behavior:

Developer Tools -> Services -> debug_scan -> fillout uuid with token (from bosch) -> start

Expected behavior
Successful ddbug scan
Screenshots
If applicable, add screenshots to help explain your problem.
Version

HA version? 2022.9.5
HA Bosch component version? 0.18.3
Python Bosch HTTP client version?

** Debug SCAN **
😎 nope
Additional context

Do you have www directory?

Yes, there is a www directory.

I tried several times and can't reproduce. Always end up:
2022-09-28 07:59:12.321 INFO (MainThread) [custom_components.bosch] Starting rawscan of Bosch component
2022-09-28 07:59:50.280 INFO (MainThread) [custom_components.bosch] Rawscan success. Your URL: https://URL/local/bosch_scan.json?v1436

Enable debug logs of bosch component to find out what's going on

Let's reopen if author can provide more details.


Copy most recent IOB implementation and tests over from oref0. 'make …

…test' now works, tests IOB. You can import dcalc, do dcalc.iob.generate(history) call.

Looks good to me, I see the recent IOB fixes from oref0


Updated Mail.ru logo one more time

Codecov Report

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

@@           Coverage Diff           @@
##           master     #443   +/-   ##
=======================================
  Coverage   78.53%   78.53%
=======================================
  Files           9        9
  Lines        1118     1118
=======================================
  Hits          878      878
  Misses        188      188
  Partials       52       52

Flag
Coverage Δ

#unittests
78.53% <ø> (ø)
:arrow_up:

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 ed1d2bf...b267696. Read the comment docs.


Isy994 x10 flag

Description:
This PR adds two things that I would like feedback on.

A new flag that adds X10 devices from the ISY994 as switches. I was not satisfied with having to write 20+ programs for all the X10 devices I have at my place. I think adding all X10 devices as switches is a decent middle ground instead of adding full support for them.
A warning message to help users debug why their ISY994 devices aren't being added as entities. I spent a lot of time trying to figure out why my X10 devices weren't being added and the current logging didn't provide enough detail. I had to dig into the component code to figure out why it wasn't being added. Having a logging message like this would have helped.

Pull request with documentation for home-assistant.io: home-assistant/home-assistant.io#10271
Example entry for configuration.yaml (if applicable):
isy994:
  host: ISY_ADDRESS
  username: ISY_USERNAME
  password: ISY_PASSWORD
  enable_x10: true

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

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

@OverloadUT can you review?

As per @MartinHjelmare's comment, I got rid of the usage of global by doing a little refactoring. node_filters is now a dict that gets passed around between functions instead of something accessed globally.
Let me know what you think! @MartinHjelmare @OverloadUT

I think we should remove the config option and just have X10 devices be supported as switches always. There's not a lot of reason to treat X10 devices as any different than everything else, which means we include them, and the user can use the ignore feature if they want to remove any.
When I wrote the current method of translating ISY nodes in to Hass entities I did not exclude X10 on purpose; I simply don't have any and so I didn't think of it. :)

@OverloadUT I figured that was the case with X10's not being there lol
Well I had fun hacking away at this, but I'll shrink this PR down to just directly adding X10's to the switches filter

Even if a lot of that work gets tossed away, you've still managed to get a pretty solid understanding of why that complicated code is all there and how it works, so you'll be able to contribute potential ISY changes in the future!

Updated the PR so it adds X10 devices as switches.
I also added a logging message that that lets a user know why their device wasn't added to HA. Not sure if this is the best place to put it, let me know what you think. This would've helped me figure out why my X10 devices weren't being added.

@OverloadUT ok?

@MartinHjelmare Good to go


Add nucleo h745zi

Support for NUCLEO-H745ZI-Q with Cortex-M7 and Cortex-M4 added
Fixes #24301
Fixes #21399

^^@ABOSTM

HI @Nukersson,
Thanks for this PullRequest.
Don't commit both '.DS_Store' files.

done

Thanks for this work, this is overall good.
To ease the review:
* Can you squash your commits so all changes appear once ? (no fix commit). Ideally you need 2 commits. First commit introducing soc/dts part. Second commit introducing the board

* Can you fix errors reported by zephyr bot?

Thanks

checks are passing.

Thanks for this work, this is overall good.
To ease the review:
* Can you squash your commits so all changes appear once ? (no fix commit). Ideally you need 2 commits. First commit introducing soc/dts part. Second commit introducing the board

* Can you fix errors reported by zephyr bot?

Thanks

@erwango Splitter into two commits only as desired. Checks are passing.

@Nukersson please rebase against the latest master

@Nukersson can you get rid of the commits that aren't yours.
Also, can you rework your commits titles to fit the usual form:

soc: stm32: Add support for .....
boards: Add support for ...

Txs

@Nukersson please rebase against the latest master

done

@Nukersson can you get rid of the commits that aren't yours?
Also, can you rework your commits titles to fit the usual form:

soc: stm32: Add support for .....
boards: Add support for ...

Txs

done

Looks like support for SoC commit comes after the board support commit, it should be the other way around.

Maybe the date is wrong, but in my git log the commits comes in right order boards after soc:

commit 68ac40836f314c8735b5acdbaa2f48d0f1ed8d89 (HEAD -> add_nucleo_h745zi#21399, > origin/add_nucleo_h745zi#21399)
Author: Alexander Kozhinov<EMAIL_ADDRESS>Date:   Sun Apr 26 12:30:43 2020 +0200
boards: Add support for NUCLEO-H745ZI-Q

Added new supported board

Signed-off-by: Alexander Kozhinov<EMAIL_ADDRESS>
commit 85b29178d45cf715d644ca8496f12e19104c8f59
Author: Alexander Kozhinov<EMAIL_ADDRESS>Date:   Tue May 19 12:38:25 2020 +0200
soc: stm32: Add support for stm32h745xx SoC

Add stm32h745xx SoC and corresponding device tree

Signed-off-by: Alexander Kozhinov<EMAIL_ADDRESS>

Looks like support for SoC commit comes after the board support commit, it should be the other way around.

Maybe the date is wrong, but in my git log the commits comes in right order boards after soc:

commit 68ac408 (HEAD -> add_nucleo_h745zi#21399, > origin/add_nucleo_h745zi#21399)
Author: Alexander Kozhinov<EMAIL_ADDRESS>Date:   Sun Apr 26 12:30:43 2020 +0200
boards: Add support for NUCLEO-H745ZI-Q

Added new supported board

Signed-off-by: Alexander Kozhinov<EMAIL_ADDRESS>
commit 85b2917
Author: Alexander Kozhinov<EMAIL_ADDRESS>Date:   Tue May 19 12:38:25 2020 +0200
soc: stm32: Add support for stm32h745xx SoC

Add stm32h745xx SoC and corresponding device tree

Signed-off-by: Alexander Kozhinov<EMAIL_ADDRESS>

I think that adjusting dates would better reflect the changes.

Looks like support for SoC commit comes after the board support commit, it should be the other way around.

Maybe the date is wrong, but in my git log the commits comes in right order boards after soc:

commit 68ac408 (HEAD -> add_nucleo_h745zi#21399, > origin/add_nucleo_h745zi#21399)
Author: Alexander Kozhinov<EMAIL_ADDRESS>Date:   Sun Apr 26 12:30:43 2020 +0200
boards: Add support for NUCLEO-H745ZI-Q

Added new supported board

Signed-off-by: Alexander Kozhinov<EMAIL_ADDRESS>
commit 85b2917
Author: Alexander Kozhinov<EMAIL_ADDRESS>Date:   Tue May 19 12:38:25 2020 +0200
soc: stm32: Add support for stm32h745xx SoC

Add stm32h745xx SoC and corresponding device tree

Signed-off-by: Alexander Kozhinov<EMAIL_ADDRESS>

I think that adjusting dates would better reflect the changes.

Okay. Will be done.

Looks like support for SoC commit comes after the board support commit, it should be the other way around.

Maybe the date is wrong, but in my git log the commits comes in right order boards after soc:

commit 68ac408 (HEAD -> add_nucleo_h745zi#21399, > origin/add_nucleo_h745zi#21399)
Author: Alexander Kozhinov<EMAIL_ADDRESS>Date:   Sun Apr 26 12:30:43 2020 +0200
boards: Add support for NUCLEO-H745ZI-Q

Added new supported board

Signed-off-by: Alexander Kozhinov<EMAIL_ADDRESS>
commit 85b2917
Author: Alexander Kozhinov<EMAIL_ADDRESS>Date:   Tue May 19 12:38:25 2020 +0200
soc: stm32: Add support for stm32h745xx SoC

Add stm32h745xx SoC and corresponding device tree

Signed-off-by: Alexander Kozhinov<EMAIL_ADDRESS>

I think that adjusting dates would better reflect the changes.

done

HI @Nukersson,
Thanks for this PullRequest.
Don't commit both '.DS_Store' files.

@ABOSTM All requested changes were made. Please provide a review.

Needed for #26226

Looks like commits content got messed up, e.g. 8fcbb423bd7f406da7009fcb5c4dea9c92a20a42 deletes DMA entries.

Looks like commits content got messed up, e.g. 8fcbb42 deletes DMA entries.

Yes. And this one 9a44f13d2382987a11acf2eb7054e3d6cfc57de6 adds them, since I needed to separate rig/dma support addition.

You need to first delete these entries from initial commits and create a fixup commit for them. After that just do the changes and you should end up with a clean commit sequence.

You need to first delete these entries from initial commits and create a fixup commit for them. After that just do the changes and you should end up with a clean commit sequence.

The changes were made. Please provide review again! Thnx.

Approved, thanks for the efforts!

@gmarull Yeaaah! Thank you too :)


Systray?

Are there any plans for systray support? Would it be possible to have a systray?

No, not right now. For now I am just trying to replicate the look, feel, and functionality of my prior dwm setup.


Is Layotto doesn't support Windows?

Your question
I didn't find the configuration about building on Windows in Github Action workflows. So, Is Layotto doesn't support Windows? Also future? And why? As far as I know, many developers are still working on Windows and not using WSL2. By the way, I work on macOS.

Unfortunately, no.
It's because MOSN doesn't support Windows.
But developers can run Layotto with docker
docker pull layotto/layotto:latest

Similar issue: https://github.com/mosn/layotto/issues/620

OK, got it. I will close the issue now.


KDE plasma5 does not work in 19.03-release

Issue description
When logging in, krunner works, but nothing else (e.g. desktop with background, menu bar, etc.) does.
Steps to reproduce
Unknown, but I'd expect that anyone using KDE in its default configuration would experience this.
Technical details

system: "x86_64-linux"
host os: Linux 5.1.3, NixOS, 19.03.git.606306e (Koi)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.2.2
channels(root): "nixos-18.09.1571.7795a7ad5f0"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

A reboot fixed the issue, but I'd expect that after a suspend to RAM and logging back in the system would work.

Unless it's not encountered more often it's not worth investigating so closing.


Crypto Deposit, Database table design for Cryptocurrencies

Design and write SQL for Table to handle available Cryptocurrencies
create table "AvailableCryptocurrency" (
  id bigint generated always as identity,
  name varchar NOT NULL
);

Write seed for a table - write inserts for available Cryptocurrencies
insert into "AvailableCryptocurrency"
( "name" )
values
('BTC'),
('USDT);

https://github.com/a3ka/cryptoexchange/pull/4


recipes-openamp: get rpmsg apps from new repo

remove rpmsg-echo-test, rpmsg-mat-mul and rpmsg-proxy-app source files and modify relative recipe to sync code from openamp-system-reference repo
Refactored rpmsg-example.inc by Bill Mills

set a real and useful SHA1 hash by default so no AUTOREV
Allow SRCREV to be overridden in mass in the local.conf file
(:pn-xxx override is also possible)
removed sha256sum, not used for git

Signed-off-by: Tanmay Shah<EMAIL_ADDRESS>Signed-off-by: Bill Mills<EMAIL_ADDRESS>

I have refactored Tanmay's PR#22.
I will close that one.
The needed SW is in the corresponding repo now.
HOWEVER: we should make sure that the change that was in Mark's initial version of PR26 is included
Xilinx needs to test these new utilities to ensure that are still compatible with Petalinux 5.15/2022.x.
They were modified to work with 6.0+ kernels but SHOULD still work with older kernels.

@TanmayShah-xilinx Can you please take a look.  I left your signed-off-by on it as you had done most of the work.

@TanmayShah-xilinx Can you please take a look. I left your signed-off-by on it as you had done most of the work.

This looks good to me.

Is this ready to be merged, or is there still work pending?

@wmamills, @mhatle I believe this is ready to be merged. If no further concerns then, can we merge it?

@mhatle @bentheredonethat Please merge this at your convenience.  I don't want to mess up your nightly when you are not around.  I will be away from home until the 10th and my first (official) work day is the 17th


nixos/nginx: add systemd-tmpfiles exclusion of temporary directories

Directories used by nginx in the tmp path are only created upon startup and must not be deleted while nginx is running.
cc @dasJ @ajs124 @SuperSandro2000
Description of changes
Added a systemd-tmpfiles rule to prevent deletion directories created in tmp by nginx. The content of the paths is not excluded from cleaning.
Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

How does that even happen? I've never seen this before.

How does that even happen? I've never seen this before.

Nginx is used as a proxy and sits there not used for more than 10 days. After that period the nginx_client_body directory is deleted and nginx is unable to store client bodies. Strange use case, but this just happened.

Could you add a NixOS test that fails before that PR and passes with that PR?

Could you add a NixOS test that fails before that PR and passes with that PR?

I will try that in the second half of next week.

@ofborg test nginx-tmpdir

Awesome, thank you for the test!

How does that even happen? I've never seen this before.

I know this is long ago, but I've experienced this multiple times on my 3d printer setup w/ Klipper.
So Klipper is managing my 3d printer, w/ a webinterface for uploading 3d prints, which I may not use in 2-3 weeks, and then suddenly when I needed it, I just got weird error messages. But never made this connection (to systemd-tmpfiles).
Thanks for this PR, I really appreciate not having to restart my RPi each time I want to print (every other week or so) :)


Add possibility to set a request and connection timeout

Hi there would be really nice to have a possibility to set a connection and request timeouts values. Not sure whats are the default ones?

`    HttpClient client = httpClientConfig.HttpClientObject();
HttpConfig newConfig = HttpConfig.builder()
  .apiBaseUri(axwayUrl) //Set Your Base API Url here
  .restBaseUri(axwayUrl) //Set your Base Rest Url here
  .build();`

My HttpClient looks like this and .getParams is depricated. How to you propose to make this change in the HttpConfig? @judy2k

Hi! Any updates on this?

Available in v7.8.0 (added in #478).


refactor: rewrite Typesystem without context propagation

Description
Refactors the way the Typesystem is resolved and passed around. Instead of passing through context we explicitly propagate it via a TypesystemResolverFunc that resolves it in a memoized way.
References
https://github.com/openfga/openfga/issues/616
Review Checklist

[x] I have clicked on "allow edits by maintainers".
[x] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

Looks like something broke in the tests. I'll investigate next week 👍

Closing until we can get around to this at a later time.


Update _user.py

While this does reduce the number of lines of code, I'm not convinced of the merit of these changes. They seem to just move things around but don't provide much value beyond personal preference. I'm happy to discuss further if you disagree.


Target profile page rewrite: Implement the Known drugs widget

Duplicate of https://github.com/opentargets/platform/issues/242


Typeof should use proxy

There is no need to have a reified value here. We could use just a Proxy.

Sorry for missing this. Assigning so I can track it.

Thansk!


New card :  Tezotopia memberShip card

New credential type
Wainting for design and json-ld specs

associated to MembershipCard_1

@HugoNDO is it the expected design


BUG: Add Hover text in Social media

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

Add a hover text so that the user will have an idea where he or she is clicking (on which icon).
Also increase the size of the icons, the cursor is blocking the icons.
Kindly assign me this issue.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Assigned!
Make sure to attach before & after screenshots in your PR and include the issue number.
Also, please star the repo before working on it. Happy open-source contributing!


[FEATURE] Add hugepage support to Harvester

Is your feature request related to a problem? Please describe.
The Harvester host OS should provide a convenient way to configure hugepages support
Describe the solution you'd like
User can enable hugepage support and specify size at installation time, and have this configuration choice preserved across OS upgrades.
Describe alternatives you've considered
hugepages can be manually configured via SLE micro but it is inconvenient
Additional context
N/A

See https://github.com/harvester/harvester/issues/5062 for a follow-on extension of this.


Enable installing apm using the ci command

There's been a few dependency changes (notably: the dropping of node-gyp), so let's give this another try. Seems to work on my machine™.

That didn't work! All right then. I'll try again after atom/apm#845.

Actually...let me try ci with global-style.


Get-DbaService

Adds a new command to dbatools:

Get-DbaService

Allows scanning for services using the connection management.
Example usage:
Get-DbaService -Name LanmanServer
Get-ADComputer -Filter * | Get-DbaService -Name Browser
Get-DbaService -ComputerName "server1","server2","server3" -Name Lanman%

hey fred - i'm happy to overlap with some of the SqlServer module functions, but I'm concerned about overlapping with Windows itself. Would this command be better as an internal function? I was actually wondering that about a few of the other Cm commands - we love them, but would end-users want them exposed? I'll ask in the #dbatools-style channel too for feedback

Heya Chrissy,
I totally don't mind putting it in internal instead. Wasn't too sure about this one and just went with intuition ('Hey, this might be cool ...').
The other -Cm commands however are firmly in the public sector:
Get-DbaCmObject (and the upcoming Invoke-DbaCmCommand) are plain too useful, so I'd keep them exposed. The rest is all about configuring the way dbatools connects to computers, so I'd keep them public.
For the meta commands - such as this one, as well as the pending Stop-DbaService, Start-DbaService and Restart-DbaService - I can totally live with making them internal.

Another point though:
This does only partially overlap with the windows cmdlets: Get-/Start-/Stop-/Restart-Service use the service control manager's own remoting options. This means, that service management using those depends on the firewall and service allowing remote management over this old interface.
This set of commands however achieves this over Cim/Wmi/PowerShell Remoting. So while it does provide the same functionality, it takes a radically different path to do so. It can be very legitimately argued that this command is out-of-scope for dbatools to publish . On the other hand, how often do dbas have no control over the firewall settings they are stuck with?

I could see these of use for say discovery purposes. If say I get some support ticket for a client (or user) on a server, one that I don't recognize, then I'd want to ensure SQL Server is running on it. We could expand these as internal functions or public ones and say build one that is wrapper to use various methods to say SQL Server is on this machine or it isn't.
Just thinking out loud.

Well ... we have Get-DbaSqlServer for that I think.

There is one for Get-DbaSqlService but that is just basic services.

Well ... I suppose this is as ready as it's going to be, merging.


#3367

PR Summary
- Resolves #3367
- Resolves #3365

PR Checklist

[x] Descriptive Title: This PR's title is a synopsis of the changes it proposes.
[x] Summary: This PR's summary describes the scope and intent of the change.
[x] Contributor's Guide: I have read the contributors guide.
[x] Style: This PR adheres to the style guide.

I mixed up the commits. This PR includes it for two issues.


sprockets 3 doesn't work without CoffeeScript?

I have a Rails project in which I disabled CoffeeScript by commenting it out in the generated Gemfile (I'm not using CS, only plain JS).
I removed Gemfile.lock and run bundle to get new versions of all the gems today. Sprocket has been upgraded to 3.0.3 from 2.12.3. Unfortunately the application doesn't work anymore. This is the error I get when trying to load the home page.
LoadError in HomeController#index
cannot load such file -- coffee_script
Extracted source (around line #274):

272 def require(file)
273   result = false
274   load_dependency(file) { result = super }
275   result
276   end
277 end

Rails.root: /home/me/project
Application Trace | Framework Trace | Full Trace

activesupport (4.2.1) lib/active_support/dependencies.rb:274:in `require'
activesupport (4.2.1) lib/active_support/dependencies.rb:274:in `block in require'
activesupport (4.2.1) lib/active_support/dependencies.rb:240:in `load_dependency'
activesupport (4.2.1) lib/active_support/dependencies.rb:274:in `require'
sprockets (3.0.3) lib/sprockets/autoload/coffee_script.rb:1:in `<top (required)>'
sprockets (3.0.3) lib/sprockets/coffee_script_processor.rb:15:in `cache_key'
sprockets (3.0.3) lib/sprockets/coffee_script_processor.rb:20:in `call'
sprockets (3.0.3) lib/sprockets/processor_utils.rb:75:in `call_processor'
sprockets (3.0.3) lib/sprockets/processor_utils.rb:57:in `block in call_processors'
sprockets (3.0.3) lib/sprockets/processor_utils.rb:56:in `reverse_each'
sprockets (3.0.3) lib/sprockets/processor_utils.rb:56:in `call_processors'
sprockets (3.0.3) lib/sprockets/loader.rb:87:in `load_asset_by_uri'
sprockets (3.0.3) lib/sprockets/loader.rb:45:in `block in load'
sprockets (3.0.3) lib/sprockets/loader.rb:157:in `fetch_asset_from_dependency_cache'
sprockets (3.0.3) lib/sprockets/loader.rb:38:in `load'
sprockets (3.0.3) lib/sprockets/cached_environment.rb:20:in `block in initialize'
sprockets (3.0.3) lib/sprockets/cached_environment.rb:47:in `yield'
sprockets (3.0.3) lib/sprockets/cached_environment.rb:47:in `load'
sprockets (3.0.3) lib/sprockets/bundle.rb:23:in `block in call'
sprockets (3.0.3) lib/sprockets/utils.rb:183:in `dfs'
sprockets (3.0.3) lib/sprockets/bundle.rb:24:in `call'
sprockets (3.0.3) lib/sprockets/processor_utils.rb:75:in `call_processor'
sprockets (3.0.3) lib/sprockets/processor_utils.rb:57:in `block in call_processors'
sprockets (3.0.3) lib/sprockets/processor_utils.rb:56:in `reverse_each'
sprockets (3.0.3) lib/sprockets/processor_utils.rb:56:in `call_processors'
sprockets (3.0.3) lib/sprockets/loader.rb:87:in `load_asset_by_uri'
sprockets (3.0.3) lib/sprockets/loader.rb:45:in `block in load'
sprockets (3.0.3) lib/sprockets/loader.rb:157:in `fetch_asset_from_dependency_cache'
sprockets (3.0.3) lib/sprockets/loader.rb:38:in `load'
sprockets (3.0.3) lib/sprockets/cached_environment.rb:20:in `block in initialize'
sprockets (3.0.3) lib/sprockets/cached_environment.rb:47:in `yield'
sprockets (3.0.3) lib/sprockets/cached_environment.rb:47:in `load'
sprockets (3.0.3) lib/sprockets/base.rb:63:in `find_asset'
sprockets (3.0.3) lib/sprockets/environment.rb:30:in `find_asset'
sprockets (3.0.3) lib/sprockets/base.rb:89:in `[]'
sprockets-rails (2.2.4) lib/sprockets/rails/helper.rb:230:in `lookup_asset_for_path'
sprockets-rails (2.2.4) lib/sprockets/rails/helper.rb:138:in `block in javascript_include_tag'
sprockets-rails (2.2.4) lib/sprockets/rails/helper.rb:136:in `map'
sprockets-rails (2.2.4) lib/sprockets/rails/helper.rb:136:in `javascript_include_tag'
actionview (4.2.1) lib/action_view/template.rb:145:in `block in render'
activesupport (4.2.1) lib/active_support/notifications.rb:166:in `instrument'
actionview (4.2.1) lib/action_view/template.rb:333:in `instrument'
actionview (4.2.1) lib/action_view/template.rb:143:in `render'
actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:66:in `render_with_layout'
actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:52:in `render_template'
actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:14:in `render'
actionview (4.2.1) lib/action_view/renderer/renderer.rb:42:in `render_template'
actionview (4.2.1) lib/action_view/renderer/renderer.rb:23:in `render'
actionview (4.2.1) lib/action_view/rendering.rb:100:in `_render_template'
actionpack (4.2.1) lib/action_controller/metal/streaming.rb:217:in `_render_template'
actionview (4.2.1) lib/action_view/rendering.rb:83:in `render_to_body'
actionpack (4.2.1) lib/action_controller/metal/rendering.rb:32:in `render_to_body'
actionpack (4.2.1) lib/action_controller/metal/renderers.rb:37:in `render_to_body'
actionpack (4.2.1) lib/abstract_controller/rendering.rb:25:in `render'
actionpack (4.2.1) lib/action_controller/metal/rendering.rb:16:in `render'
actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:44:in `block (2 levels) in render'
activesupport (4.2.1) lib/active_support/core_ext/benchmark.rb:12:in `block in ms'
/home/me/.rvm/rubies/ruby-2.2.2/lib/ruby/2.2.0/benchmark.rb:303:in `realtime'
activesupport (4.2.1) lib/active_support/core_ext/benchmark.rb:12:in `ms'
actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:44:in `block in render'
actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:87:in `cleanup_view_runtime'
activerecord (4.2.1) lib/active_record/railties/controller_runtime.rb:25:in `cleanup_view_runtime'
actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:43:in `render'
actionpack (4.2.1) lib/action_controller/metal/implicit_render.rb:10:in `default_render'
actionpack (4.2.1) lib/action_controller/metal/implicit_render.rb:5:in `send_action'
actionpack (4.2.1) lib/abstract_controller/base.rb:198:in `process_action'
actionpack (4.2.1) lib/action_controller/metal/rendering.rb:10:in `process_action'
actionpack (4.2.1) lib/abstract_controller/callbacks.rb:20:in `block in process_action'
activesupport (4.2.1) lib/active_support/callbacks.rb:117:in `call'
activesupport (4.2.1) lib/active_support/callbacks.rb:117:in `call'
activesupport (4.2.1) lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
activesupport (4.2.1) lib/active_support/callbacks.rb:505:in `call'
activesupport (4.2.1) lib/active_support/callbacks.rb:505:in `call'
activesupport (4.2.1) lib/active_support/callbacks.rb:498:in `block (2 levels) in around'
activesupport (4.2.1) lib/active_support/callbacks.rb:313:in `call'
activesupport (4.2.1) lib/active_support/callbacks.rb:313:in `block (2 levels) in halting'
route_translator (4.0.0) lib/route_translator/extensions/action_controller.rb:20:in `set_locale_from_url'
activesupport (4.2.1) lib/active_support/callbacks.rb:432:in `block in make_lambda'
activesupport (4.2.1) lib/active_support/callbacks.rb:312:in `call'
activesupport (4.2.1) lib/active_support/callbacks.rb:312:in `block in halting'
activesupport (4.2.1) lib/active_support/callbacks.rb:497:in `call'
activesupport (4.2.1) lib/active_support/callbacks.rb:497:in `block in around'
activesupport (4.2.1) lib/active_support/callbacks.rb:505:in `call'
activesupport (4.2.1) lib/active_support/callbacks.rb:505:in `call'
activesupport (4.2.1) lib/active_support/callbacks.rb:92:in `_run_callbacks'
activesupport (4.2.1) lib/active_support/callbacks.rb:776:in `_run_process_action_callbacks'
activesupport (4.2.1) lib/active_support/callbacks.rb:81:in `run_callbacks'
actionpack (4.2.1) lib/abstract_controller/callbacks.rb:19:in `process_action'
actionpack (4.2.1) lib/action_controller/metal/rescue.rb:29:in `process_action'
actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
activesupport (4.2.1) lib/active_support/notifications.rb:164:in `block in instrument'
activesupport (4.2.1) lib/active_support/notifications/instrumenter.rb:20:in `instrument'
activesupport (4.2.1) lib/active_support/notifications.rb:164:in `instrument'
actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:30:in `process_action'
actionpack (4.2.1) lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
activerecord (4.2.1) lib/active_record/railties/controller_runtime.rb:18:in `process_action'
actionpack (4.2.1) lib/abstract_controller/base.rb:137:in `process'
actionview (4.2.1) lib/action_view/rendering.rb:30:in `process'
actionpack (4.2.1) lib/action_controller/metal.rb:196:in `dispatch'
actionpack (4.2.1) lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
actionpack (4.2.1) lib/action_controller/metal.rb:237:in `block in action'
actionpack (4.2.1) lib/action_dispatch/routing/route_set.rb:74:in `call'
actionpack (4.2.1) lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
actionpack (4.2.1) lib/action_dispatch/routing/route_set.rb:43:in `serve'
actionpack (4.2.1) lib/action_dispatch/journey/router.rb:43:in `block in serve'
actionpack (4.2.1) lib/action_dispatch/journey/router.rb:30:in `each'
actionpack (4.2.1) lib/action_dispatch/journey/router.rb:30:in `serve'
actionpack (4.2.1) lib/action_dispatch/routing/route_set.rb:819:in `call'
omniauth (1.2.2) lib/omniauth/strategy.rb:186:in `call!'
omniauth (1.2.2) lib/omniauth/strategy.rb:164:in `call'
omniauth (1.2.2) lib/omniauth/strategy.rb:186:in `call!'
omniauth (1.2.2) lib/omniauth/strategy.rb:164:in `call'
omniauth (1.2.2) lib/omniauth/builder.rb:59:in `call'
warden (1.2.3) lib/warden/manager.rb:35:in `block in call'
warden (1.2.3) lib/warden/manager.rb:34:in `catch'
warden (1.2.3) lib/warden/manager.rb:34:in `call'
rack (1.6.0) lib/rack/etag.rb:24:in `call'
rack (1.6.0) lib/rack/conditionalget.rb:25:in `call'
rack (1.6.0) lib/rack/head.rb:13:in `call'
actionpack (4.2.1) lib/action_dispatch/middleware/params_parser.rb:27:in `call'
actionpack (4.2.1) lib/action_dispatch/middleware/flash.rb:260:in `call'
rack (1.6.0) lib/rack/session/abstract/id.rb:225:in `context'
rack (1.6.0) lib/rack/session/abstract/id.rb:220:in `call'
actionpack (4.2.1) lib/action_dispatch/middleware/cookies.rb:560:in `call'
activerecord (4.2.1) lib/active_record/query_cache.rb:36:in `call'
activerecord (4.2.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:649:in `call'
activerecord (4.2.1) lib/active_record/migration.rb:378:in `call'
actionpack (4.2.1) lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
activesupport (4.2.1) lib/active_support/callbacks.rb:88:in `call'
activesupport (4.2.1) lib/active_support/callbacks.rb:88:in `_run_callbacks'
activesupport (4.2.1) lib/active_support/callbacks.rb:776:in `_run_call_callbacks'
activesupport (4.2.1) lib/active_support/callbacks.rb:81:in `run_callbacks'
actionpack (4.2.1) lib/action_dispatch/middleware/callbacks.rb:27:in `call'
actionpack (4.2.1) lib/action_dispatch/middleware/reloader.rb:73:in `call'
actionpack (4.2.1) lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
better_errors (2.1.1) lib/better_errors/middleware.rb:59:in `call'
web-console (2.0.0.beta4) lib/action_dispatch/debug_exceptions.rb:18:in `middleware_call'
web-console (2.0.0.beta4) lib/action_dispatch/debug_exceptions.rb:13:in `call'
actionpack (4.2.1) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
railties (4.2.1) lib/rails/rack/logger.rb:38:in `call_app'
railties (4.2.1) lib/rails/rack/logger.rb:20:in `block in call'
activesupport (4.2.1) lib/active_support/tagged_logging.rb:68:in `block in tagged'
activesupport (4.2.1) lib/active_support/tagged_logging.rb:26:in `tagged'
activesupport (4.2.1) lib/active_support/tagged_logging.rb:68:in `tagged'
railties (4.2.1) lib/rails/rack/logger.rb:20:in `call'
quiet_assets (1.1.0) lib/quiet_assets.rb:27:in `call_with_quiet_assets'
actionpack (4.2.1) lib/action_dispatch/middleware/request_id.rb:21:in `call'
rack (1.6.0) lib/rack/methodoverride.rb:22:in `call'
rack (1.6.0) lib/rack/runtime.rb:18:in `call'
activesupport (4.2.1) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
rack (1.6.0) lib/rack/lock.rb:17:in `call'
actionpack (4.2.1) lib/action_dispatch/middleware/static.rb:113:in `call'
rack (1.6.0) lib/rack/sendfile.rb:113:in `call'
railties (4.2.1) lib/rails/engine.rb:518:in `call'
railties (4.2.1) lib/rails/application.rb:164:in `call'
rack (1.6.0) lib/rack/lock.rb:17:in `call'
rack (1.6.0) lib/rack/content_length.rb:15:in `call'
rack (1.6.0) lib/rack/handler/webrick.rb:89:in `service'
/home/me/.rvm/rubies/ruby-2.2.2/lib/ruby/2.2.0/webrick/httpserver.rb:138:in `service'
/home/me/.rvm/rubies/ruby-2.2.2/lib/ruby/2.2.0/webrick/httpserver.rb:94:in `run'
/home/me/.rvm/rubies/ruby-2.2.2/lib/ruby/2.2.0/webrick/server.rb:294:in `block in start_thread'

This error occurred while loading the following files:
   coffee_script

Request

Parameters:

None

If I add gem "sprockets", "2.12.3" to the Gemfile it works again.
Does version 3 make some hard assumption on the presence of CoffeeScript?

If this is still an active issue can you close this one and re-open it at http://github.com/rails/sprockets. Active development has moved to that repo.
If you've got a bug with sprockets 3 please make sure you've tried the latest 3.3.3. If you can confirm this is still an active issue, the fastest way to get it fixed is to create a small example app that reproduces the failure and open an issue in the new repo http://github.com/rails/sprockets.

I have also encountered this but have tracked it down to the teaspoon-jasmine gem. Are you also using this @pmontrasio?

@benpickles I checked and I'm not using that gem.
@schneems I'll check with the new version as soon as I resume working on that project. I'll open an issue in its repository if I run again into that problem.
Thanks to both of you.

FYI I've created an issue in the Teaspoon repo for this: https://github.com/modeset/teaspoon/issues/405

Either way, in my case at least, the problem resides in another library and not Sprockets.

This issue was moved to rails/sprockets#183

Clearing the cache fixed it for me. https://github.com/rails/sprockets/issues/183#issuecomment-162203288


Ciphered values in YAML should be quoted?

Again maybe I misunderstood sth but when taking a look at the documentation (http://projects.spring.io/spring-cloud/spring-cloud.html#_spring_cloud_config) with such a snippet:
spring:
  datasource:
    username: dbuser
    password: {cipher}FKSAJDFGYOS8F7GLHAKERGFHLSAJ

I got an exception during YAML parsing that "{" was unexpected. Only after writing
spring:
  datasource:
    username: dbuser
    password: '{cipher}FKSAJDFGYOS8F7GLHAKERGFHLSAJ'

did I manage to have it done properly. Have I done sth wrong or is there a bug in the doc?

@marcingrzejszczak bug in the docs.  We quote it in our sample


Move the site to AngularJS

For the v2, I propose to move the site to AngularJS.
Things would be much more simplified. Suggestions/comments/feedback is welcomed.

I second that, angular JS 2.0 would be a great fit for the website requirements.

Angular 2.0 is still in beta and Angular 1.x has been completely changed in Angular 2.0. So, I don't see how this is a smart move or how it will simplify things.

Let's leave the discussion about Angular 1 or Angular 2 right now. We're sure, that we'll be moving this site to Angular.
So, let's start with developing wire-frames.
Also, IMHO, we should wait and then use Angular 2

That would be the better option.

Seeing the discussion here on Angular, i will strongly recommend Angular 2. Yes, Angular 2 is a complete rewrite of AngularJS with completely new concepts. However, i am learning Angular 2, i realised it takes strong features of ES6+TypeScript  and really makes code more future-ready with concepts of Components(replacing Controller), Observables etc.. Future support to Angular 2 will be stronger than AngularJS. Angular 2 is the future. :)

@Subway19 Angular was considered the future as well. Anyhow, my main concern is it being in beta, as of now.

Just updating here with the internal discussions among core-contributors. We'll be designing mocks for the v2. Currently @Slayslot @chawlaaditya8 @kanikaa1234 have opted for it.
Others also, please feel free to submit their mocks, we can further iterate them and move towards implementation :)

My 2 cents:
I went through the mozpacers website and noticed that it is extremely static. What really are the advantages that you will get by moving to Angular?
IMHO, things will get needlessly complicated and also, SEO will become very difficult.