Increase OutPacketBuffer::maxSize above 100000 to avoid dropped packets

I am finding that I'm getting drops in the lower half of the image.  Is it possible to have it increased to 200000 or have it as a configurable option?

https://github.com/miguelangel-nubla/videoP2Proxy/blob/34bfa47e9ed6061f72748ddc30945bc6f700e8dc/rtsp.cxx#L47
You can modify it there but it should be enough already. Sounds like a bug elsewhere.
What camera model are you using?

I am using lumi.camera.aq1 and am getting consistent packet drop errors.


PHP worker fails to run queue items in laravel 4.2

Hi, I'm trying to integrate this packege with laravel 4.2. The problem I'm having is that laravel 4.2 stores the jobs class under the "job" key and from that a new instance is created and so on.
In my case I need different message groups for each job, so I am giving an instance of the job to the queue and setting $messageGroupId for it, but doing so under the "job" the name of the class in not sent.
Expected message sent to sqs fifo
{"job":"App\\Models\\Jobs\\AJob","data":[],"group":"group-1"}
Actual message is sent to sqs fifo
{"job":{"messageGroupId":"events-1","deduplicator":null},"data":[],"group":"group-1"}

I looked into the issue, and unfortunately, it looks like Laravel didn't support passing job instances to the queue until 5.0. Laravel 4.1 and 4.2 only support passing in class names or closures.
A workaround attempting to use closures won't work, though, since it won't have the message group information on it.
This package could be updated to support passing in a job instance for 4.1 and 4.2 for the sole purpose of setting the message group, but it would need to be converted to either a plain class name or closure workaround in order to work inside the built in 4.1/4.2 queuing system.

Hi, @patrickcarlohickman, that's what I was also thinking. I'll probably will fork it and make some changes to "support" 4.2. Thanks for your answer :)

@bnagydeveloper I tagged a new release (1.1.2) that should resolve this issue. As I mentioned in my original comment, you can pass in the job instance in order to set the message group, but the job instance will get converted to just the class name when it is sent to the queue for Laravel 4.1/4.2.
I assume you've already come up with some workaround, but in case you still needed it, it should be working now.
Thank you for reporting the issue.
Thanks,
Patrick


SSO Implementation: Port from C#

Dotnet PR: https://github.com/microsoft/botbuilder-dotnet/pull/3320

Fixed in https://github.com/microsoft/botbuilder-js/pull/1738


Clean up "d.FirstTimers" issues

fixes #857
fixes #822
fixes #245
fixes #397
fixes #450
fixes #858
fixes #728
fixes #637
fixes #629
fixes #565
fixes #663
fixes #484
fixes #521
We have 37 open issues labeled "d.FirstTimers". This is 37% of our open issues.
Many of these issues do not serve as helpful issues for new contributors to start on. They usually involve renaming something or deleting something small. Also, the way to do it is completely stated in the issue itself, meaning that the new contributor would only need to follow the instructions given to complete it. This does not assist us in ensuring that the quality of contributors is high (as the issues barely test their competency), and only ensures that we have many small problems with the code base which can easily be corrected(as we end up waiting for a new first timer to fix it).
Let's close some.

@Rinder5 this PR is fixing a FirstTimer issue, did you get permission from Prof to fix them? :P

We have too many first timer issues! =0

Yes, I do think some of the first timer issues are long overdue to be resolved: e.g. #450
However, do group all of them into one PR, and resolve at least 6 first-timer issues in one single PR. Thanks.

kk, will do that then.
any preference? if not I'll try to remove the most braindead ones, to let new developers at least have to think a bit

Yeah you can start with the "braindead" ones first. After that, you can move on to solving the rest if you want as well. I can always generate more first timer issues if needed.

@Rinder5

They usually involve renaming something or deleting something small. Also, the way to do it is completely stated in the issue itself, meaning that the new contributor would only need to follow the instructions given to complete it.

Actually, that is precisely the point of First Timer issues. They are meant to get contributors acquainted with our contribution practices, not to test their competency. It's not a competition.
The only problem is that some first timer issues are not "attractive", and so no one does them. For those issues, I think it's fine for someone to clear the backlog once in awhile.

@Rinder5

Can you update the README file as well JUnit 4 -> JUnit 5? :) Thanks!

@vivekscl having another look at this?
@Rinder5

[v7 9/15] Command: inline getMessageForPersonListShownSummary(int)
Inline Command#getMessageForPersonListShownSummary(int)
[v7 10/15] CommandBox: rename method handleCommandInputChanged()
Rename CommandBox#handleCommandInputChanged()


After pulling to refresh, a line appears under the Navigation bar

After pulling to refresh, a line appears under the Navigation bar until refresh has finished. Can you point our where in the library this might be occurring?
Im setting an image as the background self.navigationController!.navigationBar.setBackgroundImage(...)
And hiding the shadow with this self.navigationController!.navigationBar.shadowImage = UIImage()

Really weird. Please look into my implementation of that in the example project. I have exactly the same case when navigation bar and wave are the same colour and I did not have any line appearing.
I am closing this ticket.
Please feel free to re-open if you cannot fix it by implementing it the same way as I did.

It looks like its because Im using a transparent navBar and transparent refreshView
Ive modified your implementation to be transparent and get the same issue. Heres the changes Ive made:
    class ViewController: UIViewController {
            override func loadView() {
                    super.loadView()

                    navigationController?.navigationBar.translucent = false
                    navigationController?.navigationBar.setBackgroundImage(self.imageWithColor(UIColor(red: 57/255.0, green: 67/255.0, blue: 89/255.0, alpha: 1.0)), forBarMetrics: .Default)
                    navigationController?.navigationBar.shadowImage = UIImage()
                    navigationController?.navigationBar.barTintColor = UIColor(red: 57/255.0, green: 67/255.0, blue: 89/255.0, alpha: 1.0)
                    // .....
                    tableView.dg_setPullToRefreshFillColor(self.getAdjustedTransparencyColor(UIColor(red: 57/255.0, green: 67/255.0, blue: 89/255.0, alpha: 1.0), alpha: 0.915))
                    // .....
            }

        func imageWithColor(color: UIColor) -> UIImage {
            let rect: CGRect = CGRectMake(0.0, 0.0, 1.0, 1.0)
            UIGraphicsBeginImageContext(rect.size)
            let context: CGContextRef = UIGraphicsGetCurrentContext()!
            CGContextSetFillColorWithColor(context, color.CGColor)
            CGContextFillRect(context, rect)
            let image: UIImage = UIGraphicsGetImageFromCurrentImageContext()
            UIGraphicsEndImageContext()
            return image
        }

        func getAdjustedTransparencyColor(navBarColor: UIColor?, alpha: CGFloat) -> UIColor {
            var red:CGFloat = 0
            var green:CGFloat = 0
            var blue:CGFloat = 0
            var alphaX:CGFloat = 0
            navBarColor?.getRed(&red, green: &green, blue: &blue, alpha: &alphaX)

            var opacity:CGFloat = 1

            let minVal: CGFloat = min(min(red, green), blue)
            if self.convertValue(minVal, withOpacity: opacity) < 0 {
                opacity = self.minOpacityForValue(minVal)
            }

            red = self.convertValue(red, withOpacity: opacity)
            green = self.convertValue(green, withOpacity: opacity)
            blue = self.convertValue(blue, withOpacity: opacity)

            red = max(min(1.0, red), 0)
            green = max(min(1.0, green), 0)
            blue = max(min(1.0, blue), 0)

            return UIColor(red: red, green: green, blue: blue, alpha: alpha)
        }

        func convertValue(value: CGFloat, withOpacity opacity: CGFloat) -> CGFloat {
            return 0.4 * value / opacity + 0.6 * value - 0.4 / opacity + 0.4
        }

        func minOpacityForValue(value: CGFloat) -> CGFloat {
            return (0.4 - 0.4 * value) / (0.6 * value + 0.4)
        }
    }

But I still can't see whats causing the line to appear

Ah so its happening because Ive set them to transparent and sometimes they overlay which causes the darker line.
If I modify DGElasticPullToRefreshView a little and put in a 1point buffer then the line doest appear, but worse theres sometimes a 1point white gap sigh
Any idea how I can fix this?
private func currentPath() -> CGPath {
    let width: CGFloat = scrollView()?.bounds.width ?? 0.0

    let bezierPath = UIBezierPath()
    let animating = isAnimating()
    var buffer:CGFloat = 0.0
    if animating {
        buffer = 1.0
    }

    bezierPath.moveToPoint(CGPoint(x: 0.0, y: buffer))
    bezierPath.addLineToPoint(CGPoint(x: 0.0, y: l3ControlPointView.dg_center(animating).y))
    bezierPath.addCurveToPoint(l1ControlPointView.dg_center(animating), controlPoint1: l3ControlPointView.dg_center(animating), controlPoint2: l2ControlPointView.dg_center(animating))
    bezierPath.addCurveToPoint(r1ControlPointView.dg_center(animating), controlPoint1: cControlPointView.dg_center(animating), controlPoint2: r1ControlPointView.dg_center(animating))
    bezierPath.addCurveToPoint(r3ControlPointView.dg_center(animating), controlPoint1: r1ControlPointView.dg_center(animating), controlPoint2: r2ControlPointView.dg_center(animating))
    bezierPath.addLineToPoint(CGPoint(x: width, y: buffer))

    bezierPath.closePath()

    return bezierPath.CGPath
}

By the way the reason I want your refreshView transparent it because I have a parallax image which, when you pull, is visible under your refreshView. Looks really cool

Did you figure out how to do it? I mean how to make create that cool effect


Ajax Grid/Razor pages

Based on the updated info for Razor pages. What am I missing syntax wise, it runs but doesn't show anything?
http://mvc6-grid.azurewebsites.net/Grid/Ajax
MailMan (Ajax Grid).zip

You need to add
@page
@model NotifyIndexModel

to NotifyIndex.cshtml, also split IndexGrid to a normal page with it's own classes and a generated page, because currently it's just a view (it doesn't work if you declare it inside the same class as other page).

I made the suggested changes.. they "NotifyIndex" link take me to the NotifyIndex page which still shows no grid then quickly redirects back to the default index page.

You need to remove the <!-- Should only include the grid --> part, because every razor page has to start to a @page symbol. I think you should start with less error prone mvc pages before moving to newer concepts like razor pages.

Thank you that  was the solution, I think I have one finally question regarding "Grid Global Search" based on looking the Ajax Grid it would be basically be implemented in the same manner correct? if so what am I doing wrong?
MailMan(Ajax Grid).zip

if you could assist on the "Grid Global Search" question it would be greatly appreciated. Thank you.

Don't copy paste :smiley:
Your NotifyIndex is using Url.Action instead of Url.Page used in razor pages, resulting in endless recursion, after you change that you just need to add search parameter and filter it on index grid.
It's bad that I'm sharing it, but here's a working copy. MailMan.zip


Migrate to use the support Sqlite library.

Closes #710. Refs #702.

This at least opens up the possibility of generating better code.

yup. probably
On Mon, 18 Dec 2017 at 08:42 Jake Wharton<EMAIL_ADDRESS>wrote:

@JakeWharton commented on this pull request.
In README.md
https://github.com/square/sqldelight/pull/716#discussion_r157486434:

@@ -497,7 +497,7 @@ public abstract class HockeyPlayer implements HockeyPlayerModel {
public static final RowMapper SELECT_NAMES_MAPPER =
FACTORY.select_namesMapper(AutoValue_HockeyPlayer_Names::new);

public List names(SQLiteDatabase) {

public List names(SupportSQLiteDatabase) {

I'm going to revert all the README changes. It'll only confuse users.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/square/sqldelight/pull/716#discussion_r157486434, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABmQwKM9I8nrsXrBW1feHgaCXQw--T7hks5tBmuqgaJpZM4RD575
.


Ability to retrieve username and password from the environment

While CLI arguments work, the username and password values are visible to anyone that can get a process list. Further, some control planes (Kubernetes, Mesos, among others), log the CLI arguments to stderr which would then include the UpCloud username and password.
This PR makes it possible to specify those values via environment variables if they aren't provided in the CLI.

The change has been pushed.

Thanks! I've just approved, and will have it merged once the pipelines run 😄


Feature request: Per-show progression

Track progress in a given show across all channels, and allow the next episode to be dynamically inserted into any timeslot designated for that show. Also, allow meta-show groupings to fulfill this function (for example, progressing from the original run of a show to its reboot or sequel).
Example: I watch Star Trek: The Next Generation, episode 1, on my 80s channel. When I flip to my Sci-Fi channel, the next Star Trek slot will be filled by episode 2 of TNG. When I finish TNG, it will be followed by Star Trek: Deep Space Nine, which follows it in the "Star Trek" meta-show grouping.

This is actually incredibly difficult to implement dizqueTV's current architecture. It's also probably not really that good because if you, as a viewer, wanted not to miss a program's episodes you'd have to remember all of the channels with it.
If your program almost-always has the same length (like, the program always fits in 30 minutes slots) you can do something similar to this by taking advantage of on-demand channels but the TV will not have info of what episode will play.
Here's what I do with one of my shows that I want to share across channels. Let's call this show, "The Simpsons" .

A channel called "The simpsons", that has all the episodes in order, padded to 30 minutes. This channel is on-demand with 30 minutes blokcs. What happens is that whenever you play this channel, it will play the next episode in your progress (or go back to the last episode you were watching if you didn't finish it)
In other channels, whenever I want them to have the Simpsons in their schedule, I add a redirect to the "The Simpsons" channel, the redirect lasts 30 minutes.

So let's say you are watching channel "Comedy" and the next program scheduled is a redirect to The Simpsons channel, it will be redirected and since the Simpsons channel is on-demand, it will continue to the next episode in the sequence.
But if there was a 40 minute-long episode in the The Simpsons channel , this would break, because imagine the next time a channel redirects to the Simpsons, it plays this episode, since the blocks are 30 minutes-long, it will only play the first 30 minutes, then the redirect ends abruptly in the middle of the episode. Next time another channel redirects to the Simpsons it will begin with the lat 10 minutes of that episode, no opening will play.


Current scrollY for Header animations

Animating Header based on scrollY value
I would like to animate the header based on the scrollY (or height from useHeaderMeasurements) value of the scroll views in the tabs. The useCurrentTabScrollY hook is only accessible within the Tabs, however.
Questions:

Is there a way to access the scrollY value from the parent component?
Will it cause performance issues?

Animating Header based on scrollY value
I would like to animate the header based on the scrollY (or height from useHeaderMeasurements) value of the scroll views in the tabs. The useCurrentTabScrollY hook is only accessible within the Tabs, however.
Questions:

Is there a way to access the scrollY value from the parent component?
Will it cause performance issues?

Found the Animated Header example in the source code which works perfectly fine. The hooks can be used if the Header is broken out into its own components rather than having a render function from the parent. See example here.


[nav, copyright, footer] Multiple fragments per page support

Is this a BUG REPORT or FEATURE REQUEST?:
feature
What happened:
Currently we recommend one per page for each of nav, copyright and footer.
What you expected to happen:
Discuss supporting multiple of each.
Anything else we need to know?:
Needs solutions to for:

sticky option and how to handle multiple navs (related: #473)
search support for multiple navs #388
configuring menus on the fragment #491

This is mainly blocked by #388 and the rest is just a documentation thing.
Happy to close this after the blocker is done and then iterate with user feedback.

Hi, have the menus become customizable yet?

Menus are customizable from within the main config.toml/json as Hugo enables (due to a limitation with Hugo). We haven't found a good way to work around this.
Theoretically multiple navs should be possible, but it would just be a duplication for now. Happy for use cases and ideas or even contributions after a bit more thoughts.

More info on the menus part from Hugo. https://gohugo.io/content-management/menus/
Let me know, if I missed some context :)

Thank you! That solves it.


Configure Dependabot

See: https://dependabot.com/
Once we're through removing unnecessary dependencies, i.e. at least after #66.
Will require some admin repo setup

Configured with a monthly update schedule for now.
/cc @cedpoilly


msg: Job for calico.service failed in worker-01

Ansible version (ansible --version): 1.9.6
Python version (python --version): 2.7.5
Git commit hash or branch: master
Cloud Environment: bare-metal
Terraform version (terraform version):

Hi. there
i am getting another error that the state of calico is failed and zookeepr does not start.
error log
2016-05-03 10:02:53,151 p=25709 u=root |  TASK: [calico | enable and start calico] **************************************
2016-05-03 10:02:59,266 p=25709 u=root |  failed: [worker-01] => {"failed": true}
2016-05-03 10:02:59,266 p=25709 u=root |  msg: Job for calico.service failed because the control process exited with error code. See "systemctl status calico.service" and "journalctl -xe" for details.
2016-05-03 10:02:59,266 p=25709 u=root |  FATAL: all hosts have already failed -- aborting
[root@worker-01 ~]# vi /var/log/messages
status_update_manager.cpp:202] Recovering status update manager
May  3 01:01:34 worker-01 mesos-slave: I0503 01:01:34.785203 10221 containerizer.cpp:386] Recovering containerizer
May  3 01:01:34 worker-01 mesos-slave: I0503 01:01:34.785979 10221 slave.cpp:4110] Finished recovery
May  3 01:01:34 worker-01 mesos-slave: 2016-05-03 01:01:34,786:10219(0x7fd922b70700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
May  3 01:01:34 worker-01 mesos-slave: 2016-05-03 01:01:34,786:10219(0x7fd922b70700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
[root@worker-01 ~]# echo "stat" | nc zookeeper.service 2181
Ncat: Could not resolve hostname "zookeeper.service": Name or service not known. QUITTING.
[root@worker-01 ~]# systemctl status calico.service
● calico.service - calico
Loaded: loaded (/usr/lib/systemd/system/calico.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2016-05-03 01:41:28 UTC; 11s ago
Process: 32319 ExecStart=/usr/bin/calicoctl node --ip=<IP_ADDRESS> --node-image=calico/node:v0.9.0 (code=exited, status=1/FAILURE)
Process: 32312 ExecStartPre=/usr/bin/docker rm -f calico-node (code=exited, status=1/FAILURE)
May 03 01:41:28 worker-01 systemd[1]: calico.service: control process exited, code=exited status=1
May 03 01:41:28 worker-01 systemd[1]: Failed to start calico.
May 03 01:41:28 worker-01 systemd[1]: Unit calico.service entered failed state.
May 03 01:41:28 worker-01 systemd[1]: calico.service failed.
[root@worker-01 ~]# journalctl -xe
May 03 01:41:23 worker-01 mesos-slave[10219]: 2016-05-03 01:41:23,673:10219(0x7fd922b70700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(
May 03 01:41:23 worker-01 mesos-slave[10219]: 2016-05-03 01:41:23,673:10219(0x7fd922b70700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(
May 03 01:41:27 worker-01 mesos-slave[10219]: 2016-05-03 01:41:27,010:10219(0x7fd922b70700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(
May 03 01:41:27 worker-01 mesos-slave[10219]: 2016-05-03 01:41:27,010:10219(0x7fd922b70700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(
May 03 01:41:28 worker-01 systemd[1]: calico.service holdoff time over, scheduling restart.
May 03 01:41:28 worker-01 systemd[1]: Starting calico...
May 03 01:41:28 worker-01 docker[4493]: time="2016-05-03T01:41:28.664115211Z" level=error msg="Handler for DELETE /v1.23/containers/calico-node returned error: No such container: ca
May 03 01:41:28 worker-01 docker[32312]: Error response from daemon: No such container: calico-node
May 03 01:41:28 worker-01 calicoctl[32319]: ERROR: Could not enable ipv4 forwarding.
May 03 01:41:28 worker-01 systemd[1]: calico.service: control process exited, code=exited status=1
May 03 01:41:28 worker-01 systemd[1]: Failed to start calico.
-- The result is failed.
[root@control-01 ~]# echo "stat" | nc zookeeper.service 2181
Ncat: Could not resolve hostname "zookeeper.service": Name or service not known. QUITTING.
[root@control-01 ~]# netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:2379            <IP_ADDRESS>:*               LISTEN      9103/etcd
tcp        0      0 <IP_ADDRESS>:2380            <IP_ADDRESS>:*               LISTEN      9103/etcd
tcp        0      0 <IP_ADDRESS>:8300            <IP_ADDRESS>:*               LISTEN      7447/consul
tcp        0      0 <IP_ADDRESS>:8301            <IP_ADDRESS>:*               LISTEN      7447/consul
tcp        0      0 <IP_ADDRESS>:8302            <IP_ADDRESS>:*               LISTEN      7447/consul
tcp        0      0 <IP_ADDRESS>:8400          <IP_ADDRESS>:*               LISTEN      7447/consul
tcp        0      0 <IP_ADDRESS>:8500        <IP_ADDRESS>:*               LISTEN      9050/nginx: master
tcp        0      0 <IP_ADDRESS>:8500          <IP_ADDRESS>:*               LISTEN      7447/consul
tcp        0      0 <IP_ADDRESS>:53              <IP_ADDRESS>:*               LISTEN      10168/dnsmasq
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*               LISTEN      466/sshd
tcp        0      0 <IP_ADDRESS>:8600          <IP_ADDRESS>:*               LISTEN      7447/consul
tcp        0      0 <IP_ADDRESS>:153             <IP_ADDRESS>:*               LISTEN      9340/docker-proxy
tcp        0      0 <IP_ADDRESS>:25            <IP_ADDRESS>:*               LISTEN      740/master

@angry-tony Please remember to fill in the Ansible version, Python version, and git commit at the top of your post!

@angry-tony it seems there is a lot broken here. Can you run a systemctl status -l zookeeper?

Yes here is the response

[ [root@worker-01 ~]# systemctl status -l zookeeper
● zookeeper.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead) ]

ansible-playbook -u hoho -i inventory
-e provider=bare-metal
-e consul_dc=dc1
-e docker_lvm_backed=true \  <-- to avoid "docker-lvm failure", I changed
-e docker_lvm_data_volume_size="80%FREE"
-e @security.yml sample.yml >& bare-metal.log
- my inventory file -
[root@localhost]~/mantl# cat inventory
[role=control]
control-01 private_ipv4=<IP_ADDRESS> ansible_ssh_host=<IP_ADDRESS> role=control provider=bare-metal
control-02 private_ipv4=<IP_ADDRESS> ansible_ssh_host=<IP_ADDRESS> role=control provider=bare-metal
control-03 private_ipv4=<IP_ADDRESS> ansible_ssh_host=<IP_ADDRESS> role=control provider=bare-metal
[role=control:vars]
consul_is_server=true
lvm_physical_device=/dev/sdb
[role=worker]
worker-01 private_ipv4=<IP_ADDRESS> ansible_ssh_host=<IP_ADDRESS> role=worker provider=bare-metal
[role=worker:vars]
consul_is_server=false
lvm_physical_device=/dev/sdb
[role=kubeworker]
kubernetesworker-01 private_ipv4=<IP_ADDRESS> ansible_ssh_host=<IP_ADDRESS> role=kubeworker provider=bare-metal
[role=kubeworker:vars]
consul_is_server=false
lvm_physical_device=/dev/sdb
[role=edge]
edge-01 private_ipv4=<IP_ADDRESS> ansible_ssh_host=<IP_ADDRESS> role=edge provider=bare-metal
edge-02 private_ipv4=<IP_ADDRESS> ansible_ssh_host=<IP_ADDRESS> role=edge provider=bare-metal
[role=edge:vars]
consul_is_server=false
lvm_physical_device=/dev/sdb
[dc=dc1]
control-01
control-02
control-03
worker-01
kubernetesworker-01
edge-01
edge-02
- my sample.yml - # followed this Tutorial
[root@localhost]~/mantl# cat sample.yml

include: "{{ playbook_dir }}/playbooks/check-requirements.yml"

hosts: all
vars:
consul_servers_group: role=control
roles:

common
lvm
docker
logrotate
consul-template
nginx
consul
etcd
dnsmasq

hosts: role=worker
gather_facts: no
vars:
mesos_mode: follower
zookeeper_server_group: role=control
roles:

mesos
**    - calico**

hosts: role=control
gather_facts: yes
vars:
consul_servers_group: role=control
mesos_leaders_group: role=control
mesos_mode: leader
zookeeper_server_group: role=control
roles:

vault
zookeeper
mesos
marathon
mantlui
kubernetes
kubernetes-master
kubernetes-addons

hosts: role=kubeworker
gather_facts: yes
vars:
consul_dns_domain: consul
roles:
#- flannel
**    - calico**

kubernetes
kubernetes-node

hosts: role=edge
gather_facts: yes
vars:
traefik_marathon_domain: marathon.localhost
roles:

traefik

@angry-tony Zookeeper isn't installed on worker nodes. Can you post the output of the same command from one of your control nodes?

here.. Same for 3 control nodes.
[root@control-01 ~]# systemctl status -l zookeeper
● zookeeper.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)

## - my sample.yml file -  followed this Tutorial
[root@localhost] mantl# cat sample.yml
CHECK SECURITY - when customizing you should leave this in. If you
take it out and forget to specify security.yml, security could be turned off
on components in your cluster!

include: "{{ playbook_dir }}/playbooks/check-requirements.yml"

BASICS - we need every node in the cluster to have common software running to
increase stability and enable service discovery. You can look at the
documentation for each of these components in their README file in the
roles/ directory, or by checking the online documentation at
docs.mantl.io.

hosts: all
vars:
consul_acl_datacenter should be set to the datacenter you want to control
Consul ACLs. If you only have one datacenter, set it to that or remove
this variable.
consul_acl_datacenter: your_primary_datacenter
consul_servers_group: role=control
roles:

common
lvm
docker
logrotate
consul-template
nginx
consul
etcd
dnsmasq

ROLES - after provisioning the software that's common to all hosts, we do
specialized hosts. This configuration has two major groups: control nodes and
worker nodes. We provision the worker nodes first so that we don't create any
race conditions. This could happen in the Mesos components - if there are no
worker nodes when trying to schedule control software, the deployment process
would hang.

The worker role itself has a minimal configuration, as it's designed mainly to
run software that the Mesos leader shedules. It also forwards traffic to
globally known ports configured through Marathon.

hosts: role=worker
role=worker hosts are a subset of "all". Since we already gathered facts on
all servers, we can skip it here to speed up the deployment.
gather_facts: no
vars:
mesos_mode: follower
zookeeper_server_group: role=control
roles:

mesos
calico # <-- add

the control nodes are necessarily more complex than the worker nodes, and have
ZooKeeper, Mesos, and Marathon leaders. In addition, they control Vault to
manage secrets in the cluster. These servers do not run applications by
themselves, they only schedule work. That said, there should be at least 3 of
them (and always an odd number) so that ZooKeeper can get and keep a quorum.

hosts: role=control
gather_facts: yes
vars:
consul_servers_group: role=control
mesos_leaders_group: role=control
mesos_mode: leader
zookeeper_server_group: role=control
roles:

vault
zookeeper
mesos
marathon
mantlui
kubernetes
kubernetes-master
kubernetes-addons

hosts: role=kubeworker
role=worker hosts are a subset of "all". Since we already gathered facts on
all servers, we can skip it here to speed up the deployment.
gather_facts: yes
vars:
consul_dns_domain: consul
roles:
#- flannel	# <-- comment

calico	# <-- add
kubernetes
kubernetes-node

The edge role exists solely for routing traffic into the cluster. Firewall
settings should be such that web traffic (ports 80 and 443) is exposed to the
world.

hosts: role=edge
gather_facts: yes
vars:
this is the domain that traefik will match on to do host-based HTTP
routing. Set it to a domain you control and add a star domain to route
traffic. (EG *.marathon.localhost)

For those migrating from haproxy, this variable serves the same purpose
and format as haproxy_domain.
traefik_marathon_domain: marathon.localhost
roles:

traefik

@angry-tony There was probably a failure in the zookeeper task during installation. Can you check higher up in the log for errors, where the zookeeper tasks were run?

I didnt find out failure log in bare-metal.log.
i guess "Install zookeeper" task did not run..
strange.. this occurred only with calico installation..
'''
TASK: [logrotate | copy component logrotate configurations] *******************
ok: [control-03] => (item=['mesos', True])
ok: [control-03] => (item=['docker', True])
ok: [control-03] => (item=['zookeeper', "role == 'control'"])
ok: [control-02] => (item=['mesos', True])
ok: [control-02] => (item=['docker', True])
ok: [control-02] => (item=['zookeeper', "role == 'control'"])
ok: [worker-01] => (item=['mesos', True])
ok: [worker-01] => (item=['docker', True])
ok: [worker-01] => (item=['zookeeper', "role == 'control'"])
ok: [edge-02] => (item=['mesos', True])
ok: [edge-02] => (item=['docker', True])
ok: [edge-02] => (item=['zookeeper', "role == 'control'"])
ok: [kubernetesworker-01] => (item=['mesos', True])
ok: [kubernetesworker-01] => (item=['docker', True])
ok: [kubernetesworker-01] => (item=['zookeeper', "role == 'control'"])
ok: [edge-01] => (item=['mesos', True])
ok: [edge-01] => (item=['docker', True])
ok: [edge-01] => (item=['zookeeper', "role == 'control'"])
ok: [control-01] => (item=['mesos', True])
ok: [control-01] => (item=['docker', True])
ok: [control-01] => (item=['zookeeper', "role == 'control'"])
TASK: [logrotate | create component archives] *********************************
ok: [control-03] => (item=['docker', True])
ok: [control-03] => (item=['zookeeper', "role == 'control'"])
ok: [kubernetesworker-01] => (item=['docker', True])
ok: [kubernetesworker-01] => (item=['zookeeper', "role == 'control'"])
ok: [edge-02] => (item=['docker', True])
ok: [edge-02] => (item=['zookeeper', "role == 'control'"])
ok: [edge-01] => (item=['docker', True])
ok: [edge-01] => (item=['zookeeper', "role == 'control'"])
ok: [control-01] => (item=['docker', True])
ok: [control-01] => (item=['zookeeper', "role == 'control'"])
ok: [worker-01] => (item=['docker', True])
ok: [worker-01] => (item=['zookeeper', "role == 'control'"])
ok: [control-02] => (item=['docker', True])
ok: [control-02] => (item=['zookeeper', "role == 'control'"])
TASK: [mesos | wait for zookeeper service to be registered] *******************
skipping: [worker-01]
TASK: [mesos | wait for zookeeper to listen] **********************************
skipping: [worker-01]
TASK: [mesos | create zookeeper acl] ******************************************
skipping: [worker-01]
'''

solved : enable ipv6


Contrib apps

What about making sanic more of a fully featured web framework and divide it from the server part in contrib catalogue as it definitely would affect performance?
I think about built in support for templates like Jinja2, maybe some implementation of asyncpg (this could be fast) etc

I agree with extending Sanic to support commonly used libraries, template engines etc.. But I don't think implementing something like asyncpg specifically for Sanic is beneficial enough.
The database access layer isn't a bottleneck to Sanic,  SQLAlchemy is able to pump out 100,000 inserts in less than half of a second using core.  Sanic can handle 33K/S meaning that SQLAlchemy can do more than 200k inserts per 33K requests.
Complex queries take longer than others but that's still 6 DB queries per request.

I agree with extending Sanic to support commonly used libraries, template engines etc.. But I don't think implementing something like asyncpg specifically for Sanic is beneficial enough.
The database access layer isn't a bottleneck to Sanic,  SQLAlchemy is able to pump out 100,000 inserts in less than half of a second using core.  Sanic can handle 33K/S meaning that SQLAlchemy can do more than 200k inserts per 33K requests.
Complex queries take longer than others but that's still 6 DB queries per request.

Gonna close this, we're not really looking into integrating a template engine or a database engine into sanic core.


harvester vmtemplateversion error logs on boot

the following error logs are showing in the harvester, can we manage to check why it appread, thanks
time="2020-09-04T06:34:44Z" level=error msg="error syncing 'harvester-system/raw-image-base-template': handler template-controller: harvester-system:raw-image-base-version version isn't assigned yet, requeuing"
time="2020-09-04T06:34:44Z" level=error msg="error syncing 'harvester-system/raw-image-base-template': handler template-controller: harvester-system:raw-image-base-version version isn't assigned yet, requeuing"
time="2020-09-04T06:34:44Z" level=error msg="error syncing 'harvester-system/raw-image-base-template': handler template-controller: harvester-system:raw-image-base-version version isn't assigned yet, requeuing"
time="2020-09-04T06:34:44Z" level=error msg="error syncing 'harvester-system/iso-image-base-template': handler template-controller: harvester-system:iso-image-base-version version isn't assigned yet, requeuing"
time="2020-09-04T06:34:44Z" level=error msg="error syncing 'harvester-system/iso-image-base-template': handler template-controller: harvester-system:iso-image-base-version version isn't assigned yet, requeuing"
time="2020-09-04T06:34:44Z" level=error msg="error syncing 'harvester-system/windows-iso-image-base-template': handler template-controller: harvester-system:windows-iso-image-base-version version isn't assigned yet, requeuing"
time="2020-09-04T06:34:44Z" level=error msg="error syncing 'harvester-system/windows-iso-image-base-template': handler template-controller: harvester-system:windows-iso-image-base-version version isn't assigned yet, requeuing"

link to PR https://github.com/rancher/harvester/pull/124

close in favor of https://github.com/rancher/harvester/pull/124


Use input mtime as date in man page

same as https://github.com/NVIDIA/nvidia-xconfig/pull/3
Use input mtime as date in man page
See https://reproducible-builds.org/ for why this is good
This date call is designed to work with different flavors of 'date'.
This patch was done while working on reproducible builds for openSUSE, sponsored by the NLnet NGI0 fund.

@scaronni-nivida Could you have a look, please?

@sndirsch I don't have access to these repositories, they are managed directly by the driver team. I'll notify them in case they don't see it.

@sndirsch I don't have access to these repositories, they are managed directly by the driver team. I'll notify them in case they don't see it.

Thanks. I think after 7 weeks and 3 releases since that without any response we can say so. Alternatively I can contact Daniel Dadap directly. Pinging @aaronp24 as well.


Measuring discussions

It would be great to be able to measure all these metrics for discussions but this currently returns no results.

https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions may be helpful for this. It looks like I can't reliably get the discussions from search results with github3.py.


[BUG] Reroll Dialog Box UI Problem

Describe the bug
When Rerolling, sometimes the reroll dialog box opens up smaller.
This causes a minor Issue when scrolling down, as the Reroll UI Elements don't stay atop of the boxes but also scroll down.
To Reproduce
Steps to reproduce the behavior:

Have a roll where you can spend willpower on
Open a Character sheet via Token on a scene
Select Willpower Reroll on the message
See error

Expected behavior
I expect the box to always spawn full size so no scrolling is needed or the UI elements to stay on top of the selected boxes/die when I scroll.
Screenshots

Desktop (please complete the following information):

Browser [Chrome]
FoundryVTT Version [11 Build 315]
Foundry-V5 Version [4.0.0-prerelease-2]

Couldn't reproduce it with prerelease3, leaving it open for validation.

As you've noted, this in fact would've been fixed with the willpower reroll rework in prerelease 3.
Closing this issue as I can't reproduce it on the latest dev build either, so the problem shouldn't be relevant for the upcoming stable release.


Update hdinsight-connect-hive-zeppelin.md

date update!

@ashishthaps1 : Thanks for your contribution! The author, @hrasheed-msft, has been notified to review your proposed change.


Bug lakectl blame hangs without output for long time

Tried to repro it locally. The setup:

10k commits.
The objects I was looking for (e.g. the one I requested blame for) was at the first commit.
Every range retrieval was exactly 100msec to simulate object store latencies.

It took 67-70 seconds to return the correct answer. It brought 8.5k objects from the object store (some ranges were cached). Given the total amount of work lower bound (8.5k * 100msec = 14.2 min) compared to the actual time, it's safe to say that parallelism work as expected.
I'm assuming that the issue occurred in a repo with hundred of thousands of commits, where the blamed file was not recently changed.
If we want to support an efficient search for blaming a repo of that scale, we need to come up with a non object-store information to retrieve the needed info.
Search algorithms are not applicable for this search task, as changes in commits are not linearly increasing.


Consider adding back concat (flatten) and concat_map

Previously we decided to deprecate concat, but it seems useful to collapse 'a bwd bwd to 'a bwd when backward lists are used as accumulators.

Actually, I might found a possibly better way to write my code without using concat.


0.19.0 tag, but no release

There is a 0.19.0 tag, but there is no 0.19.0 realese. This happend previously 0.13
This is more a heads up than a real issue, but still.

Ah damnit my github token expired. Let me fix that up!

Fixed @benalb . I'll close this off


fix readRenderTargetPixels() and adapt to implementation format

the renderTarget.texture was forgotten and I enjoyed the edit to integrate that too:
https://github.com/mrdoob/three.js/pull/7226
(I can't find an editor were I can comfortably and safely 3-way hand merge a 4kloc file, so I just copy-paste)

I think that was a bad reflex, sorry.

Well, actually, the current dev branch uses console.error instead of THREE.error(), that was a copy/paste mixup.

Since my branch has diverged quite a bit from the upstream dev branch - I'd rather merge properly rather than patch this branch. I'll give you a note once it's pushed.

@nraynaud Hey, could you give the current depthtextures branch a spin? I think I merged everything correctly, but I don't have any tests for the code you contributed...

Yes, I will give it a try in the next few hours.

I think your changes work, I tried my main depthbuffer code, and it works, and the rest of my codebase seems fine after all the API change done.
The CSS renderer is broken, but I need more time to check for API changes or actual regression problems from the branch you pulled. I'm pretty sure it's not your code.
Thanks for your work.

@nraynaud Cool - is this related to your gcode stuff or are you working on some other fun stuff?

yep, it's for my CAM system.
I am projecting a mesh of the part I want to mill into the depth buffer (that gives me a height field), and then doing a minkowski sum  of the part and the shape of the tool, that gives me a map of the lowest position the tool is allowed to be without destroying the part shape. Then I add some voodoo to actually determine a toolpath.
Currently I'm working on even more perversion of webgl: I'm extracting the medial axis of a polygon, entirely in the fragment buffer: http://nraynaud.github.io/webgcode/various_tests/test_voronoi.html
(it's still buggy for now)

was merged manually


Not work in Xcode 7.2

I install using Alcatraz. and I press the allow load the bundle when the xcode restart.
There are the  Clean Header in the Edit menu, and the shortcut do nothing!

I am on Xcode 7.2 as well, seems to work fine. Wonder if anyone else is having the same problem as you.

It also does not worked for me. I press shortcut but nothing! I try to change shortcut and it still not working:(

not work for me too


RTC_CNTL_DBIAS shifted by 0.05V

RTC_CNTL_DBIAS voltage values are shifted by 0.05V. According to technical reference it should be within range 0.85V - 1.2V
https://github.com/espressif/esp-idf/blob/051d8d69000839985e9b6a281e89ccfe6c16080e/components/soc/esp32/include/soc/rtc_cntl_reg.h#L1142-L1149

Thanks for reporting this @michprev, I've passed this to the documentation team to fix in TRM. Values in listed IDF are the correct ones.


[Bug] Joern-Scan misidentifies apk files as Java src

Describe the bug
joern-scan calls javasrc2cpg on an Android apk file, rather than jimple2cpg
To Reproduce
./joern-scan --names testQuery ./foo/app-debug.apk --overwrite produces
=======================================================================================================
Invoking CPG generator in a separate process. Note that the new process will consume additional memory.
If you are importing a large codebase (and/or running into memory issues), please try the following:
1) exit joern
2) invoke the frontend: /home/b/projects/joern/joern-cli/target/universal/stage/javasrc2cpg -J-Xmx16064m /home/b/projects/joern/foo/app-debug.apk --output /home/b/projects/joern/workspace/app-debug.apk/cpg.bin.zip
3) start joern, import the cpg: `importCpg("path/to/cpg")`
=======================================================================================================

Expected behavior
The importer calls jimple2cpg

Thanks for reporting!
For reference, importCode in joern console correctly chooses jimple2cpg.
joern-scan seems to have different heuristics to guess the language - I'll take a look.

https://github.com/joernio/joern/blob/e2a92bb/console/src/main/scala/io/joern/console/BridgeBase.scala#L320 language != frontend...


apex logs misses logging on newly deployed functions

If you have a bug report please let us know the following:

Operating system: OSX
Apex Version: 0.10.3

Sorta minor but spent some time trying to figure out why my function wasn't running. Turns out when you deploy new functions, you also need to rerun apex logs -f. Not sure if there's anything that can be done about this, but if it's possible to fix that would be awesome <3

Ahh nice catch, yea we could pretty easily re-loop to grab new functions


Create fadeout margin

Closes #160

I think we should lose the fading on the sides entirely, and maybe fade to not-quite transparent on the top and bottom. WDYT?

I think not going fully transparent on top/bottom makes top and bottom bar quite noisy visually.
I’ll try some variations.

Made the fade less abrupt on the sides.
Gonna merge and we can see if it’s still misleading.


pipenv --three install produces correct results where --two does not

Be sure to check the existing issues, both open and closed.
Describe the issue briefly here.
Describe your environment

Linux
Python version: 3.6.4 and 2.7.9
Pipenv version: 11.10.0

Expected result
I expected the wtforms package contents to be correct.
Actual result
It appears the wtforms package contents was the latest version overridden by the specified version.
Steps to replicate
This is easiest to replicate with docker where the environment is clean:
docker run -it --rm python bash

pip install pipenv==11.10.0

export PIPENV_VENV_IN_PROJECT=1

# Test python3
mkdir /test-python3 && cd /test-python3
pipenv install --three wtforms==1.0.5

# Notice files line up with wtforms==1.0.5
# (https://pypi.python.org/packages/fb/9d/9dcdb7a9a19301c0cc04eca1aa8c60da50d97156f3c10e24519eb77202e1/WTForms-1.0.5.zip)
ls -la .venv/lib/python3.6/site-packages/wtforms/

# Test python2
mkdir /test-python2 && cd /test-python2
pipenv install --two wtforms==1.0.5

# Notice it appears the files from wtforms==2.1
# (https://pypi.python.org/packages/bf/91/2e553b86c55e9cf2f33265de50e052441fb753af46f5f20477fe9c61280e/WTForms-2.1.zip)
# were overriden by the files from wtforms==1.0.5
ls -la .venv/lib/python2.7/site-packages/wtforms/

I'm still seeing the same issue with<EMAIL_ADDRESS>Can you explain why you closed the issue?

This is fixed in master via #1854

I'm still seeing the same result in 11.10.0. Are you seeing the correct package contents for python2 in my example on 11.10.0? I've updated the pipenv version in the example so it's a simple copy/paste and visual comparison on the ls output.

I’m guessing this relates to the json api which I thought we disabled...

I'm actually going to close this in favor of #1952 for now since I think it's captured a bit more clearly there


Long search text for OH searchbar is displayed improperly

When I use the search bar of the sidebar or global search to search a very long text, all the text will be displayed in the sidebar. And it may overlap the whispers in the sidebar. E.g.

Would it be better that it only shows a prefix after Searched for:  ?

Looks like another styling / rendering issue!  I'll open a bug.

HELPS-866 has been opened. We'll let you know when we have resolved the issue.


Dropdown menus overlap

simple menus hide & popup on mouse in & out as expected. But neighbor menus overlap with each other if I clicked one and move mouse onto another.

Can't reproduce anymore.


powertoys run issue

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
Awake, General
Steps to reproduce
2024-12-22.txt
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

/dup #36389


Logger does not respect the "Enable logging" setting

The log method on the WC_Adapter class does not respect the "Enable logging" setting for the current payment gateway and instead always writes to the log. An easy fix for this is to add the following as the first lines in the log method.
if (!$this->getConfiguration()[ConfigurationInterface::DEBUG]) {
    return;
}

Happy to make a PR for this, but maybe y'all have a better solution for it. :)

Any updates on this and https://github.com/SwedbankPay/swedbank-pay-woocommerce-payments/issues/46 @asbjornu @aait? :)

@lakrisgubben See this line https://github.com/SwedbankPay/swedbank-pay-woocommerce-core/blob/master/src/SwedbankPay/Core/Core.php#L171
        if (!$this->configuration->getDebug()) {
            return;
        }

This line does the same behavior

thanks for the reply @aait! We still get our logs filled with messages even though I've disabled logging, so something is up here. Looked some more at the logs and it seems like all of the messages are about either "Incoming callback" or the "Background queue". So maybe this issue can be closed, but this one needs investigation? https://github.com/SwedbankPay/swedbank-pay-woocommerce-payments/issues/46

@aait the issue is that WC_Gateway_Swedbank_Pay_Cc::return_handler calls WC_Adapter::log, not Core::log. And since Core::log is a private function it can't be called from WC_Gateway_Swedbank_Pay_Cc::return_handler. So either Core::log needs to be exposed and then changes made in WC_Gateway_Swedbank_Pay_Cc or WC_Adapter::log needs to have the same logic as Core::log.

https://github.com/SwedbankPay/swedbank-pay-woocommerce-core/commit/a026c4f6270f307660461755118521f445ffbf0c
https://github.com/SwedbankPay/swedbank-pay-woocommerce-core/commit/97cd3555a310462cdbef293904191eb007bace88


notebooks and scroll-locks

As noted in #1301, users get "lost" in the infinite sea of canvas. Another way to think about the solutions, in order of perceived complexity. Requested by @MehrotraRahul.
Horizontal Scroll Lock
Allow the user to hit a button which performs a horizontal scroll lock. The canvas would only expand infinitely in one direction. This would impose a max zoom out level. You would only zoom in to add detail and you would be oriented tightly in the x dimension. You would always be able to scroll out to your log. This is very close to how apple notes does things. If you additionally implemented a vscode style minimap it would allow them to rapidly index into a potentially long "log".
Horizontal Scroll Lock + Pages
also constrain the Y axis with regards to the aspect ratio of standard pages. The minimap generated indexes on pages and they can be named.
 A UI exists for indexing these pages. Unclear what the constraints of a page should be, but limitless is probably acceptable.

@tvanderstad expressed the idea of a "top" being a useful concept

Have been trying to take notes on a mini iPad and realized the following

When I was scrolling down, having filled up a screen, I used two fingers to scroll, and this had the effect of a small pinch/stretch on the document, changing the zoom level slightly, which was unsettling. I think in "notebook mode" the zoom should snap to a particular value and not be so sensitive to page scrolling
Given the (lack of) sensitivity of the Apple pencil (compared to, say a fine mechanical pencil or a fountain pen) I feel I would end up writing notes at 100% zoom, and reading them at a lower number, say 80%... so the ability to zoom is important but there needs to be a simple way to snap to 100% in one touch instead of having to use the drop down
A good add might be a "next page" button towards the bottom of the screen, which would just scroll in that direction to a free area to serve as the next page, maybe leaving 10% of the previous screen still visible so you know where you are
A separate problem I faced was that a two finger tap seems to work as "undo", so when I was scrolling with two fingers, I ended up undoing actions a few times.

I've seen some apps do this which could be a partial solution:

single finger is pan
two finger is zoom + pan
drawing only happens with apple pencil


Scroll to index new version for the scheduler binding issue

After the new flutter update, this warning keeps popping out
/opt/homebrew/Caskroom/flutter/3.0.2/flutter/.pub-cache/hosted/pub.dartlang.org/scroll_to_index-2.1.1/lib/scroll_to_index.dart:358:57: Warning: Operand of null-aware operation '!' has type 'SchedulerBinding' which excludes null.

'SchedulerBinding' is from 'package:flutter/src/scheduler/binding.dart' ('/opt/homebrew/Caskroom/flutter/3.0.2/flutter/packages/flutter/lib/src/scheduler/binding.dart').
package:flutter/…/scheduler/binding.dart:1
Future _waitForWidgetStateBuild() => SchedulerBinding.instance!.endOfFrame;

the solution is to upgrade the scroll to index to latest version.

Having the same issue


Issue with track title while playing local file via vlc

while playing a local file in vlc media player, it converts "spaces" in its name to "%20".

works for me

might be a problem of the file itself


Add in the Hooks to allow extension to make modifications as necessary

hey I'm Urooj Fatima. Excited for this project

Hello, Its Syed Umer Tariq !!

Hi, I am the new Operations Manager Steve from Vancouver Team.

Hi! It's Rafsun.

Hi! I'm Abdul Manan. I'm excited to work on this project!

Hi! I am Abdullah. Excited for this project !!

Hi! I am Waleed, excited to work on this project

Hi I am Talha and I am excited to start working on this project

Hi,
Jawad Ali here
Excited

Hooks are a programming concept used in many software development frameworks. Here the hooks refer to the specific locations in the code where you can write the your own custom code and to modify the behavior of the application. Hooks provide a way for developers to inject their own functionality into an existing application without modifying its original source code. It makes easier to maintain code and upgrade to the new versions of the application. Hooks are implemented as functions that are called by the application at specific points in its code. Developers can then define their own custom functions which allows extending the application behavior.
Hooks are mostly used by people who are working on open-source projects.
Adding in the hooks to allow extension to make modifications:
In order to add hooks to your application you have to follow below steps:
•	First you need to identify the places in your application where you can add custom code. These are the points where you will add hooks.
•	Create hook functions or methods that should allow the extension to pass in data or modify the behavior of the application.
•	Add calls to the hook methods at appropriate points in your code. These calls should have necessary  parameters that will be needed by the extension to edit the behavior of the application.

For adding hooks you may follow the following steps:
-Identify the areas of the system where hooks would be useful. This could include points where data is retrieved or processed, actions are performed, or decisions are made.
-Determine the inputs and outputs of each hook. What information should be passed in and out of the hook to enable extensions to modify the system as needed?
-Define the hook interface. This includes the function signature and any documentation necessary to describe how the hook should be used.
-Implement the hooks within the system. This could involve adding function calls at the appropriate points in the codebase, or creating a separate module for managing the hooks.
-Provide documentation for the hooks so that developers know where they are and how to use them.
-Test the system with and without extensions to ensure that the hooks are working as expected.

First, we need to identify the points in MariaDB where we want to modify behavior to use the AGE extension. We can then review the documentation to find hooks that are available at those points and learn how to use them with their input/output parameters. We will need to write the extension code that uses these hooks, either by modifying existing functions or writing new ones

The use of hooks in the MariaDB with AGE extension will be similar to the use of hooks in any other database. Basically, the hooks will be something close to triggers or user-defined functions and they will execute at some CRUD operation on the table. Therefore with our AGE extension on MariaDB, the hooks will be added on the raw MariaDB statements at points where we want our graph extension to intercept and produce the desired results. So, the format for hooks will be similar to triggers or user-defined functions which might take input/output parameters as needed and then return the user with some results.

Hooks in MariaDB offer several benefits for developers and users of the database:

Customization: Hooks allow developers to customize the behaviour of MariaDB to suit their specific needs, without having to modify the core source code of the database.

Extension: Hooks allow developers to extend the functionality of MariaDB by adding new features or integrating with external systems.

Integration: Hooks allow MariaDB to integrate with external systems and services, making it more flexible and useful in a wide range of applications.

Maintenance: Hooks make it easier to maintain and upgrade MariaDB, as customizations and extensions can be implemented as separate modules that can be updated independently of the core database.


Mac app doesn't recognise device already registered

I'm trying to log in to my mac app. After entering my username, the app asks me "Which keybase install would you like to connect with?". The notebook I'm using is listed there, as if it was a different device. Anyway, I choose a different device (my tablet, for example). Then the app asks me which public name I would like to set to the current device - and if I try to use its default name (which, as I mentioned, is already listed among the registered devices), it won't accept it.
I do not intend to set a different name. What should I do?
Thanks!

I'm having a similar issue, but on the same device. THIS device is already added, but within the keybase app, it somehow desynced. I can't add the device, because the device already exists, and I can't add it as a new one, because it's asking me to login to the device I'm on to setup the device I'm on.
How do I say "No, this is the device that is setup" or something

My log file: 395cfed4578e9d60528be11c

Would appreciate any help, as I'm currently unable to use the app in my main device.

We've only ever had an issue here if you blasted away the Keybase config and secret keys. Is that a possible explanation?  If you blast away your config.json, then there's no way for the software to recognize a device as "registered", it'll just look like a new device.

@maxtaco what I can say for sure is that I haven't deleted either the app or any related file myself. Anyway, trying to be more practical, how to debug/fix?

Do a keybase log send.   Also give me some vague time frames. When did the work app, and when did it fail to recognize the current device.

@maxtaco Log ID b6dfcb35e3ce509062cef61c
I can't think of any specific event related to the time frame in which the app stopped recognizing my main device. It was working fine, and simply one day (about two weeks ago I'd say) t wasn't anymore. That said, I'm always installing and updating general software and environmental stuff related to Python and also to Ethereum, but I don't remind of having changed anything related to Keybase.io (of course, I could be wrong).
Thank you in advance for your help.

@42piratas your best bet is to pick a different device name. We don't allow device reuse, and the previous device with that name is gone since the keys and config file appear wiped.

Thanks!

@maxtaco is there any to revoke a device from my account in keybase.io rather than from the device itself?


Fix issue causing import error when running /tests/test_schema_and_dto_logic.py

Context
I added tests which were not currently a part of the Github Actions tests to the run_pytest.yml file in a recent PR.
However, one minor set of tests failed due to an odd import issue:
Traceback (most recent call last):
  File "/home/runner/work/data-sources-app-v2/data-sources-app-v2/tests/test_schema_validation.py", line 6, in <module>
    from middleware.enums import JurisdictionType
ModuleNotFoundError: No module named 'middleware.enums'

This runs successfully on my local machine (#WorksOnMyMachine). For the moment, I removed that test, as it was a minor one, but ideally we want to fix this so that this runs without error.
Requirements

Resolve the above error.
Re-add /test_schema_validation.py to the run_pytest.yml test suite

Tests

Ensure the tests import properly when run in the Github Action.

Docs

Not applicable.

Open questions

None

Thank goodness, this one was really annoying me.


az mariadb create minimalTlsVersion

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
"az mariadb server create" command does not have a property for minimalTlsVersion while the Azure REST API allows for this property at creation time.
To Reproduce
az mariadb create
Expected behavior
az mariadb create command should allow the --minimumTlsVersion switch to set TLS version to 1.0, 1.1 or 1.2.
Environment summary
Tested on the latest CLI version at this time.
"azure-cli": "2.2.0",
"azure-cli-command-modules-nspkg": "2.0.3",
"azure-cli-core": "2.2.0",
"azure-cli-nspkg": "3.0.4",
"azure-cli-telemetry": "1.0.4",
"extensions": {}
Additional context
If using Azure Policy to deny older TLS version than 1.2 you can not use Az CLI to create MariaDB server unless you use custom REST request.

@itoleck thanks for reaching out. We are already working on fixing this. We will send you and update as soon we are done with the change.

Any news on this one?

@kummanish any update?

Updating assignments and tagging @savjani and @mksuni for follow-up.


Add option to display imgs in order

python run.py --sort

@MattKleinsmith Thank you! Sorry I've been busy writing a paper for a conference.
Images should be sorted by default, don't you agree?

@Cartucho Haha, no problem. Now I'm the one who is busy! I'll have my head in the books for the next  few months so I won't be contributing for a while. I hope to come back and contribute, though.
I agree that sorting should occur by default.


[builtin-function] Add builtin function: uuid

Add a builtin function. example:
mysql> select uuid();
+--------------------------------------+
| uuid()                               |
+--------------------------------------+
| cb33abbf-4fdc-41ea-9df2-8b38b0262fa5 |
+--------------------------------------+

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

@stdpain @imay PTAL

@c1oudman Good Job, Thanks for your contribution.


Bump min version of DVC to 2.23.0 (--with-dirs removed from data status)

5/5 main <- #2091 <- #2151 <- #2266 <- #2267 <- this
This PR removes the use of a --with-dirs from our call to data status. The flag was removed in 2.23.0 in favour of having that as the default behaviour.

Is #2266 needed then if you're going to merge this into it?


How to get Modifier Keys on Input events?

Hi,
I'm just getting started with Rust and Piston, but it seems like I already run into an issue. I figured out that I can poll events to get button or press/release events to check which Key was pressed, and I noticed that a modifier key enum is already available too, but I don't seem to be able to actually access that in any way via the button- press/release events. Is there full support for the modifier keys in piston already and if yes, how can I access them?
Thanks!

There is a library for this: https://crates.io/crates/piston-button_tracker
Closing. Reopen if there is still an issue.


RetryPolicy logging should include reason for retry

The RetryPolicy logging currently includes only the ClientRequestId and the retry count:
https://github.com/Azure/azure-sdk-for-net/blob/7c2ff45b0f4c60fc9ed2420969b556851e74cd4d/sdk/core/Azure.Core/src/Pipeline/Internal/RetryPolicy.cs#L126
It would be nice to also log information about why the retry happened (e.g. the exception that caused the retry).

Closed with https://github.com/Azure/azure-sdk-for-net/pull/12003


OpenLDAP: Can't log in if restricted mode is set on for LDAP

Rancher Version: master 6/15
Steps to Reproduce:

Authenticate using LDAP
Set mode to restricted and add the admin (this should happen automatically, but if not add)
Logout and try to log back in

Results: Can't log back in

Expected: should be able to log in
Comment:  In the ldapconfig collection the "allowedIdentities" field is missing.

This is a missing feature - "accessMode" is not supported for OpenLDAP.

Moving out after discussing with @will-chan

@deniseschannon Do you know when this will be implemented in a release candidate?

@vincent99 We will need SiteAccess UI added to OpenLDAP access control page.
Backend has been implemented to support "accessMode" + "allowedIdentities"

Adding back to 1.5 @deniseschannon request =)

Version - master 2/23
Verified fixed


Converge code management between reproducer usages

With this patch, it doesn't really care what you're doing, you'll end
with some code being cloned on the ansible-controller node.
In order, it will:

get related Zuul CI job code (if you're reproducing a CI job)
get your own repositories (using cifmw_reproducer_repositories)
finally, ensure you at least get install_yamls and ci-framework
repositories

As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running
[X] Appropriate documentation exists and/or is up-to-date:

[X] README in the role

/hold
will take some time today to address comments. Now that the layout is mostly working, I can focus on this one.

/hold cancel


Include the certificate management tool in docker distribution

Is your feature request related to a problem? Please describe.
Today, the OpenSearch docker distribution comes pre-installed with demo certificates. The intention is to replace the insecure demo certificates with self-signed certificates as discussed in #1618 (point 2).
Describe the solution you'd like
Package the certificate management tool (provided in #1633) in the docker distribution. While instantiating the container, check if the certificates are present in the respective mounted volume that holds the config. If missing, it should run the certificate management tool to create self-signed certificates with default arguments before bootstrapping OpenSearch. If present, skips the certificate generation and rely on user provided certificates and yml configurations.

Adding logs for OpenSearch docker run today. the demo certificates are by default enabled as seen.
docker run -it -p 9200:9200 -p 9600:9600 -e "discovery.type=single-node" opensearchproject/opensearch:1.2.0
Enabling execution of install_demo_configuration.sh for OpenSearch Security Plugin
OpenSearch Security Demo Installer
 ** Warning: Do not use on production or public reachable systems **
Basedir: /usr/share/opensearch
OpenSearch install type: rpm/deb on NAME="Amazon Linux"
OpenSearch config dir: /usr/share/opensearch/config
OpenSearch config file: /usr/share/opensearch/config/opensearch.yml
OpenSearch bin dir: /usr/share/opensearch/bin
OpenSearch plugins dir: /usr/share/opensearch/plugins
OpenSearch lib dir: /usr/share/opensearch/lib
Detected OpenSearch Version: x-content-1.2.0
Detected OpenSearch Security Version: <IP_ADDRESS>


Add Byond support

Fixes #103

Not quite sure what all needs done for this to work properly, but this is what was listed on the Contributing page.

It appears byond has to be also supported by the sourcerer-app itself. If you feel comfortable to hack on it a bit, it'd be super cool. Here's a blog post on how to do this https://blog.sourcerer.io/how-to-add-your-favorite-language-to-sourcerer-b7bcc4e4d4ed

@yaronskaya Made the requested changes, squashed commits, and changed the commit message to line up with guidelines.


Print version order when running migrate

When running rollback, it prints out ordering by [creation|execution] time while migrate did not. This adds that print line to migrate to keep them consistent.
Added tests for when no order is provided (and defaults to creation) and when an order is provided.

Nah but there is now small conflict

Addressed merge conflict and spacing for the end info tag in both migrate and rollback commands.


ci(test workflow): added

:tada: This PR is included in version 7.1.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


etcdmain: print error when non-flag args remain

current master ignores the flags and start:
$ ./bin/etcd name etcd
2015/03/23 10:10:45 etcd: no data-dir provided, using default data-dir ./default.etcd
2015/03/23 10:10:45 etcd: listening for peers on http://localhost:2380
2015/03/23 10:10:45 etcd: listening for peers on http://localhost:7001
2015/03/23 10:10:45 etcd: listening for client requests on http://localhost:2379
2015/03/23 10:10:45 etcd: listening for client requests on http://localhost:4001
2015/03/23 10:10:45 etcdserver: name = default
2015/03/23 10:10:45 etcdserver: data dir = default.etcd
2015/03/23 10:10:45 etcdserver: member dir = default.etcd/member
2015/03/23 10:10:45 etcdserver: heartbeat = 100ms
2015/03/23 10:10:45 etcdserver: election = 1000ms
2015/03/23 10:10:45 etcdserver: snapshot count = 10000
2015/03/23 10:10:45 etcdserver: advertise client URLs = http://localhost:2379,http://localhost:4001
2015/03/23 10:10:45 etcdserver: initial advertise peer URLs = http://localhost:2380,http://localhost:7001
2015/03/23 10:10:45 etcdserver: initial cluster = default=http://localhost:2380,default=http://localhost:7001
2015/03/23 10:10:45 etcdserver: start member ce2a822cea30bfca in cluster 7e27652122e8b2ae
2015/03/23 10:10:45 INFO: raft: ce2a822cea30bfca became follower at term 0
2015/03/23 10:10:45 INFO: raft: newRaft ce2a822cea30bfca [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
2015/03/23 10:10:45 INFO: raft: ce2a822cea30bfca became follower at term 1
2015/03/23 10:10:45 etcdserver: added local member ce2a822cea30bfca [http://localhost:2380 http://localhost:7001] to cluster 7e27652122e8b2ae
2015/03/23 10:10:46 INFO: raft: ce2a822cea30bfca is starting a new election at term 1
2015/03/23 10:10:46 INFO: raft: ce2a822cea30bfca became candidate at term 2
2015/03/23 10:10:46 INFO: raft: ce2a822cea30bfca received vote from ce2a822cea30bfca at term 2
2015/03/23 10:10:46 INFO: raft: ce2a822cea30bfca became leader at term 2
2015/03/23 10:10:46 INFO: raft.node: ce2a822cea30bfca elected leader ce2a822cea30bfca at term 2
2015/03/23 10:10:46 etcdserver: published {Name:default ClientURLs:[http://localhost:2379 http://localhost:4001]} to cluster 7e27652122e8b2ae

after change:
$ ./bin/etcd name etcd
2015/03/23 10:09:19 etcd: error verifying flags, unsupported non-flag arguments [name etcd]

Change the error line to this now:
2015/03/23 11:23:31 etcd: error verifying flags, 'name' is not a valid flag. See 'etcd -help'.
PTAL

LGTM


Util class for building java command line args to enable remote debugging

Both of a standard application and one running inside a Docker container.
Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage decreased (-0.4%) to 95.439% when pulling c78c029f3cfc410913d0504fcb60778a94794d2a on attachme into 3a72a8f26a462858fc51551825eac54576a6ec2c on main.


Efficient mem chunking in input plugin

What does the code in this PR do / what does it improve?
Changes in file_loader class of input plugin to make it more memory efficient.
This plugin was in some cases the one using the most amount of ram during processing.
With this new implementation, the ram requirements are reduced by at least a factor 2, and same for the speed.
Especially needed in view of the future PR #167 when we will need to keep all interactions also with zero ed.
Can you briefly describe how it works?
Instead of transforming the full awkward array with the interactions into a numpy array immediately, we use only the times to calculate chunk boundaries, and then we will only transform into numpy array after the chunks are defined.
Can you give a minimal working example (or illustrate with a figure)?
This image shows the memory usage of calling next on the file_reader.output_chunk.
The four options are: current and proposed implementation, with or without zero ed interactions.

Keeps failing with:
=========================== short test summary info ============================
FAILED tests/test_FullChain.py::TestChunkedFullChain::test_PMTResponseAndDAQ -
numpy.exceptions.DTypePromotionError: field titles of field 'pulse_id' mismatch

checked outputs and seems to be the same as before the PR, also for empty chunks it seems to give the same result. Not sure what is causing the issue here. Giving up for today..

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

26 of 29 (89.66%)  changed or added relevant lines in 1 file are covered.
186 unchanged lines in 8 files lost coverage.
Overall coverage increased (+6.5%) to 77.979%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

fuse/plugins/micro_physics/input.py
26
29
89.66%

Files with Coverage Reduction
New Missed Lines
%

fuse/plugins/detector_physics/s1_photon_propagation.py
1
96.75%

fuse/plugins/truth_information/cluster_tagging.py
4
33.33%

fuse/plugins/micro_physics/yields.py
4
75.56%

fuse/plugins/detector_physics/csv_input.py
8
89.09%

fuse/plugins/micro_physics/input.py
37
74.37%

fuse/plugins/truth_information/peak_truth.py
38
33.33%

fuse/common.py
43
55.3%

fuse/plugins/pmt_and_daq/pmt_response_and_daq.py
51
51.4%

Totals

Change from base Build<PHONE_NUMBER>:
6.5%

Covered Lines:
2323

Relevant Lines:
2979

💛  - Coveralls

Ouch.. I thought I fixed it but it's still wrong.

Fixed some mistakes, now tested again.
Based on my tests, there is no difference at all between the chunks produced before and after the PR.
I also tested again the speed and memory usage, and updated the plot in the description.
Results are the same, x2 memory efficiency, x2 processing speed.


[AutoPR healthcareapis/resource-manager] Adding autorest cli specific section for healthcareapis

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7360

(message created by the CI based on PR content)


incorrect content routing HTTP Request URL match condition regex

FortiADCIngressController: 2.0.0 (fortinet/fortiadc-ingress:2.0.0)
FortiADC-2000F v7.4.0,build0308,230706 (GA)
The content routing created for a prefix path rule does not appear to be correct.
The the ingress spec of
spec:
  ingressClassName: fadc-ingress-controller
  rules:
  - host: test3.lab.example.net
    http:
      paths:
      - path: "/"
        pathType: Prefix
        backend:
          service:
            name: test3-kuard-service
            port:
              number: 80

Creates a Content Routing entry with a HTTP Request URL regex of  ^()((/\w+)|/|)+$ and the problem with this is \w matches any word character - that excludes characters like _ . - ? - & etc... and as you can imagine this breaks all references to all files in the URL and any query parameters. Kinda important.
I would suggest changing the \w to simply a . to match any character. For example ^()((/.+)|/|)+$ .

Thanks, we will improve it in next version


It's not clear what this plugin actually does

I get the fact that you can require() css files, but the example code in README.md shows an output file ./bundle.js.
Where does the resulting CSS files get written?
Are the CSS files bundled into one big CSS file?
Do we have to add a link in the HTML file to the resulting CSS file or is it done for us automatically?
etc...
It would help if you provided a sample project showing the input files, configuration and output files. This way we can examine what the plugin actually does before refactoring our own projects.

It's a Browserify transform.
css = require('./some.css') just puts the contents of some.css into the css var.

I'm sure this sounds silly to you, but I think you should mention this fact in README.md. It's not obvious to a first-time browserify user (I've never used transforms before).

The third line of the readme states "To use, specify as a Browserify transform..."

@bclinkinbeard Agreed, but my point remains: this explains how to use the plugin, not what it does. Someone who has never used transforms before won't be able to figure out what this plugin is about.

:)

I agree. I expected a var-less require('some.css') to inline my css into some self-executing function.

https://github.com/bclinkinbeard/partialify/commit/8aa65e9f5561ef9dedec65ad778ed56205f92186


add bun dependency for building

I noticed while trying to build this locally that I needed the bun dependency for the build to complete.
After installing it in pnpm I could build it without errors.

Thanks for the PR @svelle.
Bun actually needs to be installed globally because it's not needed just as bundler but also as package manager for the CLI.
I've updated the README to reflect that as a Prerequisite.
As for building or any other development, a few other tools are needed as well like pnpm and Taskfile. So maybe I'll write a separate Development/Contribution guide where I can cover these.

great point! haven't considered that as I'm not a front end dev myself so I wasn't super familiar with the workflow :)


Deployment of functions is failing on new release of Kubeless 0.3.2 with error "spec.ports: Required value"

Tried deploying a very basic python function.
Serverless: Excluding development dependencies...
Serverless: Deploying function hello...
Serverless: Unable to find any running pod for hello. Retrying...
Serverless: Unable to find any running pod for hello. Retrying...
Serverless: Unable to find any running pod for hello. Retrying...
Serverless: Unable to find any running pod for hello. Retrying...
Serverless: Giving up, unable to retrieve the status of the hello deployment.
/workspace/devops-insight/functions/new-project/node_modules/bluebird/js/release/async.js:61
        fn = function () { throw arg; };
                           ^

Error: Unable to retrieve the status of the hello deployment
    at module.exports.logError (/root/.nvm/versions/node/v8.9.3/lib/node_modules/serverless/lib/classes/Error.js:94:11)
    at process.on (/root/.nvm/versions/node/v8.9.3/lib/node_modules/serverless/bin/serverless:21:3)
    at emitTwo (events.js:126:13)
    at process.emit (events.js:214:7)
    at methodName (/workspace/devops-insight/functions/new-project/node_modules/bluebird/js/release/debuggability.js:189:33)
    at activeFireEvent (/workspace/devops-insight/functions/new-project/node_modules/bluebird/js/release/debuggability.js:232:44)
    at fireRejectionEvent (/workspace/devops-insight/functions/new-project/node_modules/bluebird/js/release/debuggability.js:617:14)
    at Promise._notifyUnhandledRejection (/workspace/devops-insight/functions/new-project/node_modules/bluebird/js/release/debuggability.js:64:9)
    at Timeout._onTimeout (/workspace/devops-insight/functions/new-project/node_modules/bluebird/js/release/debuggability.js:43:14)
    at ontimeout (timers.js:475:11)
    at tryOnTimeout (timers.js:310:5)
    at Timer.listOnTimeout (timers.js:270:5)

Kubeless Controller log:
time="2017-12-29T15:33:47Z" level=info msg="Processing change to Function default/hello" pkg=controller
time="2017-12-29T15:33:47Z" level=error msg="Function can not be created/updated: Service \"hello\" is invalid: spec.ports: Required value" pkg=controller
time="2017-12-29T15:33:47Z" level=error msg="Error processing default/hello (will retry): Service \"hello\" is invalid: spec.ports: Required value" pkg=controller
time="2017-12-29T15:33:47Z" level=info msg="Processing change to Function default/hello" pkg=controller
time="2017-12-29T15:33:47Z" level=error msg="Function can not be created/updated: Service \"hello\" is invalid: spec.ports: Required value" pkg=controller
time="2017-12-29T15:33:47Z" level=error msg="Error processing default/hello (will retry): Service \"hello\" is invalid: spec.ports: Required value" pkg=controller
time="2017-12-29T15:33:47Z" level=info msg="Processing change to Function default/hello" pkg=controller
time="2017-12-29T15:33:47Z" level=error msg="Function can not be created/updated: Service \"hello\" is invalid: spec.ports: Required value" pkg=controller
time="2017-12-29T15:33:47Z" level=error msg="Error processing default/hello (will retry): Service \"hello\" is invalid: spec.ports: Required value" pkg=controller
time="2017-12-29T15:33:47Z" level=info msg="Processing change to Function default/hello" pkg=controller
time="2017-12-29T15:33:47Z" level=error msg="Function can not be created/updated: Service \"hello\" is invalid: spec.ports: Required value" pkg=controller
time="2017-12-29T15:33:47Z" level=error msg="Error processing default/hello (will retry): Service \"hello\" is invalid: spec.ports: Required value" pkg=controller
time="2017-12-29T15:33:47Z" level=info msg="Processing change to Function default/hello" pkg=controller
time="2017-12-29T15:33:48Z" level=error msg="Function can not be created/updated: Service \"hello\" is invalid: spec.ports: Required value" pkg=controller
time="2017-12-29T15:33:48Z" level=error msg="Error processing default/hello (will retry): Service \"hello\" is invalid: spec.ports: Required value" pkg=controller
time="2017-12-29T15:33:48Z" level=info msg="Processing change to Function default/hello" pkg=controller
time="2017-12-29T15:33:49Z" level=error msg="Function can not be created/updated: Service \"hello\" is invalid: spec.ports: Required value" pkg=controller
time="2017-12-29T15:33:49Z" level=error msg="Error processing default/hello (giving up): Service \"hello\" is invalid: spec.ports: Required value" pkg=controller
E1229 15:33:49.543861       1 controller.go:171] Service "hello" is invalid: spec.ports: Required value

cc @ngtuna

@vishweshwarp the Service specification definition was moved in the latest release from the controller to the Kubeless CLI (https://github.com/kubeless/kubeless/pull/397). We need to adapt this CLI to mimic that behavior.


Connection time out with OpenAI API

I really like spacy-llm but it is impossible for me to use it. I keep having connection time out with a working API key from OpenAI and after spending much time at setting all the framework finding this is very frustrating.
Here's the error and my config file. Thank you for any help.
Time out Error
raise ReadTimeoutError(
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='api.openai.com', port=443): Read timed out. (read timeout=30.0)
During handling of the above exception, another exception occurred:
raise TimeoutError(
TimeoutError: Request time out. Check your network connection and the API's availability.
Config.cfg
`[paths]
examples = null
[nlp]
lang = "en"
pipeline = ["llm", "llm_rel"]
[components]
Named Entity Recognition Component
[components.llm]
factory = "llm"
[components.llm.task]
@llm_tasks = "spacy.NER.v2"
labels = [##]
[components.llm.task.template]
@misc = "spacy.FileReader.v1"
path = "templates//ner_v2.jinja"
[components.llm.task.label_definitions]

[components.llm.model]
@llm_models = "spacy.GPT-3-5.v3"
name = "gpt-3.5-turbo-16k-0613"
config = {"temperature": 0.0, "top_p": 0.0}
max_request_time = 30.0
[components.llm.cache]
@llm_misc = "spacy.BatchCache.v1"
path = "local-cache"
batch_size = 20
max_batches_in_mem = 500
Relationship Extraction Component
[components.llm_rel]
factory = "llm"
[components.llm_rel.task]
@llm_tasks = "spacy.REL.v1"
labels = [##]
[components.llm_rel.task.label_definitions]

[components.llm_rel.model]
@llm_models = "spacy.GPT-3-5.v3"
name = "gpt-3.5-turbo-16k-0613"
config = {"temperature": 0.0, "top_p": 0.0}
max_request_time = 30.0`

Hi @pecto2020, this seems like you're experiencing connection issues with the OpenAI API. Under which circumstances does this happen?

Hi @rmitsch , the issue arises when I process multiple texts, each around 4,000 tokens in size. I attempted to adjust the batch parameters in the configuration to address this, but I continued to encounter the same error. Currently, I've adapted my approach to process the text files individually, sending them to OpenAI one at a time for named entity recognition and relationship extraction. Yet, the time request error persists. Additionally, I've noticed that sometimes the GPT's raw output presents labels in bullet points, as opposed to being comma-separated. It appears that when this formatting occurs, the likelihood of a time request error increases, though I'm not sure of a direct correlation (I  see they are not correctly parsed by spacy-llm, so basically the information extracted by the model is lost with an empty json  or I got time error request)
Is there anything else you'd like to know about the circumstances?

the issue arises when I process multiple texts, each around 4,000 tokens in size. I attempted to adjust the batch parameters in the configuration to address this, but I continued to encounter the same error.

You're running into rate limitations on OpenAI's side. Unfortunately there isn't anything we can do about that. The batch size config won't make a difference here, but you'll want to experiment with interval and max_request_time.


renderer: expression_t is always allocated as part of structs, ext->numOps always 0 if ext is invalid

As far as I know,

expression_t is always allocated as part of structs (texModInfo_t, shaderStage_t),
ext->numOps is always 0 if ext is invalid.

LGTM


Llama3 Processing Sink

Uses Llama3 model(from ollama) to derive insights on metrics for a given database and stores the results in postgres
References:

#32

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

12 of 19 (63.16%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+1.5%) to 17.694%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/llama_receiver/main.go
0
2
0.0%

cmd/llama_receiver/llama_receiver.go
12
17
70.59%

Files with Coverage Reduction
New Missed Lines
%

cmd/parquet_receiver/main.go
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>6:
1.5%

Covered Lines:
66

Relevant Lines:
373

💛  - Coveralls

Model Updated to tinyllama for ease of user

Looks cool! Do you have any demo output? I'm really eager to see how it works :)

Yep this is how we get the out put for some dummy metrics:
Metrics(We are picking the 10 most recent measurements for now so that my laptop does not blow up :)):
       created_time        |                        data                         | metric_name | database_id | id | dbname
----------------------------+-----------------------------------------------------+-------------+-------------+----+--------
 2024-09-18 15:09:17.744536 | [{"cpu": 0.4931227158526041, "checkpointer": 8}]    | health      |           1 |  1 | test
 2024-09-17 05:57:23.411127 | [{"cpu": 0.9391787279884108, "checkpointer": 21}]   | health      |           1 |  1 | test
 2024-09-17 05:56:55.397735 | [{"cpu": 0.9391787279884108, "checkpointer": 21}]   | health      |           1 |  1 | test
 2024-09-17 05:56:23.33855  | [{"cpu": 0.9391787279884108, "checkpointer": 21}]   | health      |           1 |  1 | test
 2024-09-17 05:55:06.514503 | [{"cpu": 0.9391787279884108, "checkpointer": 21}]   | health      |           1 |  1 | test
 2024-09-17 05:54:19.861201 | [{"cpu": 0.9391787279884108, "checkpointer": 21}]   | health      |           1 |  1 | test
 2024-09-16 10:21:46.461051 | [{"cpu": 0.17688077186140289, "checkpointer": 99}]  | health      |           1 |  1 | test
 2024-09-16 10:20:44.369418 | [{"cpu": 0.015728886965353912, "checkpointer": 22}] | health      |           1 |  1 | test
 2024-09-16 07:33:04.968043 | [{"cpu": 0.1026947434019184, "checkpointer": 0}]    | health      |           1 |  1 | test
 2024-09-16 07:31:22.365576 | [{"cpu": 0.8076059523961426, "checkpointer": 40}]   | health      |           1 |  1 | test
 2024-09-16 07:29:27.054481 | [{"cpu": 0.034741206423261346, "checkpointer": 73}] | health      |           1 |  1 | test
 2024-09-16 07:28:28.229516 | [{"cpu": 0.9956509471402158, "checkpointer": 26}]   | health      |           1 |  1 | test
 2024-09-16 07:27:24.502777 | [{"cpu": 0.8833158321966696, "checkpointer": 40}]   | health      |           1 |  1 | test
 2024-09-16 07:26:39.713865 | [{"cpu": 0.001640287333294862, "checkpointer": 0}]  | health      |           1 |  1 | test
 2024-09-16 07:25:40.452153 | [{"cpu": 0.8729865490332787, "checkpointer": 12}]   | health      |           1 |  1 | test
 2024-09-16 07:24:37.738921 | [{"cpu": 0.8742443008720868, "checkpointer": 62}]   | health      |           1 |  1 | test
 2024-09-16 07:17:10.97184  | [{"cpu": 0.22953988467236924, "checkpointer": 38}]  | health      |           1 |  1 | test
 2024-09-16 07:15:01.259699 | [{"cpu": 1.169480258119128, "checkpointer": 81}]    | health      |           1 |  1 | test
 2024-09-16 07:14:20.124188 | [{"cpu": 1.0811733871405975, "checkpointer": 65}]   | health      |           1 |  1 | test
 2024-09-16 07:13:19.391432 | [{"cpu": 1.3516906697077604, "checkpointer": 38}]   | health      |           1 |  1 | test
 2024-09-16 07:12:55.786994 | [{"cpu": 1.5481504692957349, "checkpointer": 26}]   | health      |           1 |  1 | test

Model Output:

Introduction:

In this report, we will analyze the health metrics of a single PostgreSQL database. These metrics, which include CPU usage, checkpointer frequency, and number of open files, are crucial indicators of database performance that can help identify potential issues before they become significant problems. By providing insight into these metrics, we hope to provide recommendations for maintaining optimal database performance.

Metric Name: Health:

1. CPU Usage (0.4931227158526041)
   Metric: CPU usage is the percentage of time that the database server is running on a CPU. A high CPU usage can indicate that the database is being overloaded, leading to slower performance and increased memory usage. To mitigate this issue, we recommend tuning the database configuration settings, such as increasing the number of threads or reducing the maximum connections allowed by the database server.
   Insight: This metric indicates that there are likely more than two CPUs being used, indicating that the database may be experiencing a high workload. To mitigate this issue, it may be beneficial to adjust the number of threads in the database server configuration and/or increase the maximum connections allowed by the server.

2. Checkpointer Frequency (8)
   Metric: The frequency with which the PostgreSQL database checkpointer is run. A low checkpointer frequency indicates that there may be issues with the database or storage, such as data corruption or inefficient indexes. To address this issue, we recommend regularly updating and tuning the database's storage engine, particularly for large datasets or if there are known performance issues associated with in-memory databases.
   Insight: This metric indicates that the database is performing poorly, which may be due to data corruption or an inefficient index configuration. To mitigate this issue, we recommend regularly updating and tuning the database's storage engine.

3. Number of Open Files (21)
   Metric: The number of file descriptors used by the PostgreSQL database server. A high number of open files can indicate that the database is experiencing a memory leak or other issues with the file system, which may lead to slower performance and increased disk I/O. To address this issue, we recommend regularly monitoring and tuning the database's storage and file system configuration settings.
   Insight: This metric indicates that there are likely more than two open files being used by the database server, indicating a memory leak or other issues with the file system. To mitigate this issue, it may be beneficial to regularly monitor and tune the database's storage and file system configuration settings.

Conclusion:

In conclusion, we have analyzed the health metrics of a single PostgreSQL database. We have observed that CPU usage is high, checkpointer frequency is low, and number of open files are high. To address these issues, we recommend regularly monitoring and tuning the database's storage and file system configuration settings, particularly for large datasets or if there are known performance issues associated with in-memory databases. By following these recommendations, we hope to provide optimal database performance for our target application```

This is one more example of what is being generated with the demo database in pgwatch3:
I can provide you with a summary of the metrics and observations observed during the checksum failures at pgwatch2. The key findings are:

1. Seed failures: pgwatch2 detected five failed checksums out of 472 total checksums (0.0009%). These were identified as follows:
   - PostgreSQL was running with a single-threaded server process, which caused some transactions to be committed before the other thread could update the checksum table. This led to the failed checksums.
   - The number of concurrent transactions exceeded the threshold configured by postgres (1024) in pgwatch2's configuration file.

2. In_recovery_int: This metric shows whether the server was shutting down gracefully or not. It was observed that some instances were in recovery mode at the time of the failure, which may have caused issues with checksum checkouts from other threads. However, this metric showed a low value (0.5%) during postgres' shutdown process, indicating that these checksums might have been checked out correctly.

3. In_recovery_int: This metric also showed that at least two instances were in recovery mode when the failure occurred. Some checks failed due to lack of resources or other reasons outside of pgwatch2's control, resulting in incomplete checksum checkouts for these instances.

4. Invaliid indexes: pgwatch2 identified 165 invaild indexes out of the 209 total indexes (73%) checked during the checksum failures. This may be due to various reasons, such as the postgres configuration being incorrect or a lack of resources for pgwatch2 to analyze.

5. Invaliid indexes: pgwatch2 identified 165 invaild indexes out of the 209 total indexes (73%) checked during the checksum failures. This may be due to various reasons, such as the postgres configuration being incorrect or a lack of resources for pgwatch2 to analyze.

The observed values do not indicate any significant issues with checksum generation, storage or analysis at pgwatch2 during the checks. However, some instances were observed in recovery mode, which may have resulted in incomplete checksums being checked out by other threads.

although it seems to be a little bad with the grammar

Looks really cool! We need to make it less chatty, IMHO, otherwise really cool!

Sure! will do that

@pashagolub I think this is it for this PR. Would love to get your reviews.

@pashagolub fixed the SQL formatting

Merging!


First set of active profile change fixes

This change is the first in a series of changes that will addresses the issues encountered when changing the active mixed reality toolkit configuration profile while the application is running.
The actual number of future PRs has not yet been determined. Test collateral and documentation will be included in the series as fixes enable them.

Failure to recreate the UIRaycastCamera

Change from Destroy to DestroyImmediate as the service locator expects the UIRaycastCamera to me immediately removed in order to correctly re-create it.

Handle data provider collection change during {Late]Update

This change handles the InvalidOperationException that is thrown when a collection is changed during enumeration, This prevents the code from incorrectly aborting.

Handle service collection change during ExecuteOnAllServices<In|Reverse>Order

This change replaces for with foreach and handles the InvalidOperationException that is thrown the services collection is changed during enumeration. This prevents the code from incorrectly aborting,
Testing

In editor using simulated hands
Toggle between two profiles on a click event
Confirm that interactable objects continue to function after re-acquiring the hand.


Framework for GoogleGenomics/Spark with a CLI and Pipelines

Hi Elmer and Nicole,
What about creating a framework for GoogleGenomics/Spark, and then one can connect via a command-line interface and launch different tasks via classes.  Ideally these will also have the ability to be pipelined together.
I am thinking about something along the lines of Weka:
http://www.cs.waikato.ac.nz/ml/weka/
You can perform command-line interface (CLI) like this:
http://weka.wikispaces.com/Primer
You can even have a pipeline like this:
http://weka.wikispaces.com/Exporting+Charts+from+the+Knowledge+Flow
Maybe you can integrate with Google's Dataflow on this, based on what Cassie mentioned recently.  With a framework you can easily add then a class for caching out the similarity matrices, and then just reloading them as necessary.
Paul

Its all getting closer http://blog.cloudera.com/blog/2015/01/new-in-cloudera-labs-google-cloud-dataflow-on-apache-spark/
Thanks Paul!