text:
Rename binary to cargo-fix

After a cargo install rustfix, the subcommand cargo fix would be available.

Can we cheat and add two [[bin]] with "rustfix" and "cargo-fix" as names, but both with src/main.rs as target? :D

Cargo will produce
warning: file found to be present in multiple build targets: src/main.rs

if we do that :(
I guess we can move the logic to lib.rs and load it from both src/bin/rustfix.rs and src/bin/cargo-fix.rs which simply have the same source code. Or go the extremely hacky route of creating src/bin/cargo-fix.rs with the content include!("../main.rs")

authors: killercup oli-obk

repo: killercup/rustfix


text:
Interpolation Module

Requirements: smtinterpol.jar is in the base directory (http://ultimate.informatik.uni-freiburg.de/smtinterpol/)
Example invocation:
bin/kind2 --enable INTRPO -v --smt_trace --smtlogic UFLIA --smtsolver SMTInterpol examples/two_counters.lus

I think there are some files missing. I cannot compile it. You should probably add at least

src/kind2.ml
src/SMTInterpolDriver.ml
src/SMTInterpolDriver.mli
src/interpolation.mli

Look good otherwise.

Christoph,
I have committed the missing files. Hopefully it will compile now.
On a different note, I am going to start making the changes for PDR+IA. How
can I commit this to develop without it updating the pull request. Do I
need to create a new branch?
Regards
On Thu, Feb 12, 2015 at 12:36 PM, Christoph Sticksel <
notifications@github.com> wrote:

I think there are some files missing. I cannot compile it. You should
probably add at least

src/kind2.ml
src/SMTInterpolDriver.ml
src/SMTInterpolDriver.mli
src/interpolation.mli

Look good otherwise.
—
Reply to this email directly or view it on GitHub
https://github.com/kind2-mc/kind2/pull/223#issuecomment-74125743.

Need to be completed before pull request is ready for acceptance:

Port interpolant generation to sequence interpolant generation
Evaluate and test invariant generation via interpolation

source: gharchive/pull-request

authors: chsticksel jbodeen

license_type: permissive

license_source: bigquery


text:
checkout hyperledger/fabric origin

Description

Motivation and Context

Fixes #
How Has This Been Tested?

Checklist:

[] I have added a Signed-off-by.
[] I have either added documentation to cover my changes or this change requires no new documentation.
[] I have either added unit tests to cover my changes or this change requires no new tests.
[] I have run golint and have fixed valid warnings in code I have added or modified. This tool generates false positives so you may choose to ignore some warnings. The goal is clean, consistent, and readable code.

Signed-off-by:

march 17 2017


text:
Section 2.4. Http Server and Client

Questions:

'Note that the configuration of the Kinode will still determine whether it is accessible over IPv4/IPv6 – Kinode OS does also not provide any DNS management for nodes.'

can you elaborate on this? what exactly does the fact that Kinode OS doesnt provide DNS management have to do with IP accesibility?

'All server functionality can be either authenticated or public.'

there is talk about public functionality, but authenticated functionality is not elaborated upon.

'However, indirect nodes are not expected to be accessible over IP, so in the near future, the HTTP server will include a proxying feature to allow indirect nodes to serve HTTP requests.'

the proxying feature will be served by direct nodes?
does this mean that indirect nodes will use authenticated functionality?

Let's remove all reference of proxying for now. That was a direction we thought we needed to take, but with hosting it's a way lower priority.

The authenticated functionality requires you be logged in to your node. There is (was?) another functionality to make it so there is a 1-1 correspondence between frontend and node. I think that is something else (can you please confirm @dr-frmr ?)

Nope, it's just public vs. private. Public means it's HTTP served on the open web. Private = authenticated = you need your node's password to generate a cookie that gives access.

authors: dr-frmr jurij-jukic

repo: kinode-dao/kinode-book

license_source: github-api


text:
Upgrade dependencies to latest patch version

1.9.2 of https://github.com/kubernetes/apimachinery and company have been released.

I tried upgrading to the latest pach, 1.9.2, but somehow dep seems to think that's not possible, and only upgrades to 1.9.1.
No idea if that's correct, or if dep is misbehaving.

@LiliC Should we pin to the kubernetes-1.9.0 ta for dependencies, or the release-1.9 one? I'm confused by this and how it interacts with client-go dependencies.

OK, found this about the kubernetes-vx.y.z tags:

These tags have limited test coverage, but can be used by early adopters of client-go and the other libraries. Moreover, they help to vendor the correct version of k8s.io/api and k8s.io/apimachinery. Note that we only create a v6.0.3-like semantic versioning tag on k8s.io/client-go. The corresponding tag for k8s.io/api and k8s.io/apimachinery is kubernetes-1.9.3.

Also note that only these tags correspond to tested releases of Kubernetes. If you depend on the release branch, e.g., release-1.9, your client is running on unreleased Kubernetes code.

@asymmetric I would just stick to v0.6.0 and not worry about supporting 1.9.x versions. Unless you have a very good reason for that?

Also, did you mean v6.0.0? And when you say "not worry about supporting 1.9.x" you mean sticking to 1.9.0?

Yes I would stick to 1.9.0 and client-go v6.0.0.

Thanks. I think that's the recommended approach anyway (matching minor versions), although I'm not 100% sure.

source: gharchive/issue

authors: LiliC asymmetric

repo: kinvolk/habitat-operator


text:
invalid guessing state while guessing uts namespace, got checking expected checked

I'm evaluating this project by running it on a local Minikube installation.  When I deploy via krew, here is what gets logged in the gadget container:
05:50 $ kubectl logs -n kube-system gadget-6sl8p
OS detected: "Ubuntu 20.04 LTS"
Kernel detected: 5.4.0-7642-generic
bcc detected: 0.1.8-2644.git.5fed2a94
Gadget image: docker.io/kinvolk/gadget:202007010134320f732c
Deployment options:
INSPEKTOR_GADGET_OPTION_RUNC_HOOKS_MODE=auto
INSPEKTOR_GADGET_OPTION_TRACELOOP=true
INSPEKTOR_GADGET_OPTION_TRACELOOP_LOGLEVEL=info,json
Inspektor Gadget version: v0.2.0
Falling back to podinformer runc-hook-mode.
Starting the Gadget Tracer Manager in the background...
traceloop version 3a57301
time="2020-09-21T12:50:09Z" level=info msg="Starting Pod controller"
{"level":"info","msg":"Starting pod informer","time":"2020-09-21T12:50:09Z"}
I0921 12:50:09.963990   10113 podinformer.go:268] Starting Pod controller
invalid guessing state while guessing uts namespace, got checking expected checked

I will poke around the source to see if I can resolve it, but it's not clear what my next step should be from the logs.

Hi @mattrjacobs, what is your Minikube version, and which Minikube driver are you using?
Unfortunately, Inspektor Gadget requires a couple of changes in Minikube, and that work is not yet completed in Minikube upstream (https://github.com/kubernetes/minikube/issues/8556 and https://github.com/kubernetes/minikube/issues/8637). Meanwhile, you could try a Minikube build with our Minikube branch, where Inspektor Gadget should work fine:
https://github.com/kinvolk/cloud-native-bpf-workshop/blob/master/minikube.md#our-branch

Ah thanks - those pointers are great.
I am currently running Minikube 1.13 with the Docker driver:
06:39 $ minikube start
😄  minikube v1.13.0 on Debian bullseye/sid
✨  Using the docker driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🔄  Restarting existing docker container for "minikube" ...
🐳  Preparing Kubernetes v1.19.0 on Docker 19.03.8 ...
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "minikube" by default

I got the same error on MacOS inside a kind Cluster
MacOS: 11.2.3
kind version: 0.10.0
k8s version: v1.20.2

Would be great to test this on a local installation.

As mentioned by Alban, this was a known issue regarding the eBPF compatibility in minikube. We provide a minikube image in the https://github.com/kinvolk/cloud-native-bpf-workshop, that can be used with Inspektor Gadget for testing purposes (the workshop itself is outdated and would need to be updated to the latest IG version, but the Minikube image is still working and usable for testing IG functionality).
Closing as this is not actionable. Thanks for the report!

authors: TheKangaroo alban marga-kinvolk mattrjacobs

repo: kinvolk/inspektor-gadget


text:
Add kubelet-wrapper and etcd-wrapper

The kubelet-wrapper and etcd-wrapper scripts are part of Flatcar
Container Linux. They are tightly coupled with the service files
kubelet.service and etcd-member.service, respectively. The service files
are part of Lokomotive.
This coupling consists of environment variables and container runtime
parameters. This causes problem because any change (e.g. moving from rkt
to Docker) requires synchronisation between Flatcar and Lokomotive
releases.
This patch makes Lokomotive provide its own kubelet-wrapper and
etcd-wrapper scripts so that it is not dependent on the a specific
channel of Flatcar.
This patch also changes the container runtime to Docker.
Since Docker does not support sd_notify, I remove the related code.
To fix this, we could use sdnotify-proxy. See links:
https://www.freedesktop.org/software/systemd/man/sd_notify.html
https://github.com/coreos/sdnotify-proxy
In practice, Lokomotive works without sd_notify, but other services that
have a dependency on etcd-member might have not run in the correct
order. I found only one service in this case: flanneld:
/usr/lib/systemd/system/flanneld.service:4:After=etcd.service etcd2.service etcd-member.service

This patch only fixes AWS: packet and others are left as TODO.
I expect that kubelet-wrapper and etcd-wrapper can be shared for all
cloud providers, so I've put them in the 'common' directory. This will
make future changes easier to manage.
To make terraform modules self-sufficient (e.g.
aws/flatcar-linux/kubernetes), required files should normally not be
outside of the root directory of the terraform module (e.g. no access
via ../../../). I've added symbolic links to the common directory. If
you create assets with vfsgen, the symbolic links are read as regular
files so they get added several times in the assets, making the
terraform module self-sufficient.
Note: with this patch, we are dangerously close to the 16384 size limit
on AWS user_data. In my tests, we're around 15860.
TODO:

[ ] Fix sd_notify for Flannel
[ ] Other cloud providers
[ ] Longer-term solution for the 16384 size limit on AWS user_data
[ ] Remove rkt from other parts of Terraform scripts

This patch makes Lokomotive provide its own kubelet-wrapper and
etcd-wrapper scripts so that it is not dependent on the a specific
channel of Flatcar.

I guess there was a reason to couple Flatcar Linux with etcd-wrapper, at least (probably kubelet-wrapper too). Is this just overriding it or removing them from Flatcar Linux? Would it make sense to double check why this was coupled in the first place? IMHO, that would be ideal.
Also, if we are removing these from Flatcar Linux, couldn't this affect Flatcar Linux users not using Lokomotive?

I'm not sure why it was coupled in the first place.
We'll not remove them from Flatcar immediately, it should follow a deprecation period. Note that the path is different: Flatcar has the wrapper scripts in the read-only /usr and this Terraform patch adds the scripts in /etc/kubernetes (it needs a mount with write access).

@alban oh, okay. It sounds reasonable to me, then. Thanks! :-)

@rata we don't remove them from Flatcar. We just make it independent, so we have better control over it in Lokomotive.

I guess there was a reason to couple Flatcar Linux with etcd-wrapper, at least (probably kubelet-wrapper too).

I'm not aware of the exact history of kubelet-wrapper, etc.
I suppose what happened was:
kubelet-wrapper was first written only for CoreOS Container Linux.
After that, CoreOS built Tectonic upon Container Linux, by simply calling kubelet-wrapper that was supposed to be already included in the underlying OS.
Afterwards, Typhoon was forked from Tectonic, Lokomotive was forked from Typhoon, but the coupling has not changed.

How does Typhoon solves that on non-CoreOS distros?

On Wed, Nov 27, 2019 at 11:43 AM Mateusz Gozdek notifications@github.com
wrote:

How does Typhoon solves that on non-CoreOS distros?

It runs it with totally different approach, this issue has some of the
reasoning:
https://github.com/poseidon/typhoon/issues/91#issuecomment-386847684

How does Typhoon solves that on non-CoreOS distros?

Good question. A while ago, it was using "atomic install" to set up a super-privileged container and pull the kubelet from quay.io/poseidon/kubelet:v1.14.1:
https://github.com/poseidon/typhoon/blob/5eb11f510493bdcfac83ae530552a4f144fbd0b1/aws/fedora-atomic/kubernetes/cloudinit/controller.yaml.tmpl#L95
But then, "atomic install" has been deprecated and it is not used in Typhoon anymore:
https://github.com/poseidon/typhoon/pull/501/files
Now it is using podman:
https://github.com/poseidon/typhoon/blob/ddea7dc45252080eefabaf26d3bd18c3931abfb1/aws/fedora-coreos/kubernetes/workers/fcc/worker.yaml#L34

Merge conflicts here.

I will close it for now then and we can come back to in in the future.

Would be great to have this picked up again.
The Flannel ToDo can be ignored since it is not supported anymore.
If AWS user data is still a problem, you could also store the scripts in the GitHub repository and refer to them via URL in Ignition:
"contents": {
          "source": "https://raw-github-url",
          "verification": { SHASUM if wanted }
}

authors: alban dongsupark invidian pothos rata

repo: kinvolk/lokomotive-kubernetes

license: MIT


text:
🛑 Trading Post - Production is down

In 97dd40f, Trading Post - Production (https://tradingpost.kiondaga.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Trading Post - Production is back up in c72c41c after 2 minutes.

repo: kiondaga/status


text:
Docker-compose typo

Ran into an issue when setting up the docker-compose, turns out it was just because it's missing a semicolon after "environment" lol.
Added ":" after environment in docker-compose

Nice catch!

repo: kiranshila/Doplarr


text:
Update README.md

Hey, I came across this packages after searching the internet for a good directive to use with Disqus, and I think this is the best one so far. I hope to make it even better by first editing the README.md.
I made some edits to the 'Getting Started' section by adding steps. I also added code examples for the steps. I kept only the provider method for setting the shortname.

Webber

Thanks for the changes!

authors: kirstein webbur

repo: kirstein/angular-disqus

license: mit


text:
[Tracker] Adoptable Packages

If anybody feels like maintaining more things, you are more than welcome to adopt the following packages.
Mention this issue when adopting.
Comment on this issue to orphan.

[ ] aria2
[ ] birch
[ ] bkeymaps
[ ] caddy
[ ] ccls
[ ] crosstool-ng
[ ] falkon
[ ] fff
[ ] hack
[ ] hexyl
[ ] iosevka-nerd-fonts
[ ] keyutils
[ ] libtirpc
[ ] lm-sensors
[ ] lz4
[ ] neofetch
[ ] pciutils
[ ] qt5-declarative
[ ] qt5-svg
[ ] qt5-wayland
[ ] qt5-webchannel
[ ] qt5-webengine
[ ] qt5
[ ] rage
[ ] ranger
[ ] runit
[ ] sbase
[ ] shfm
[ ] shinit
[ ] sysmgr
[ ] ubase
[ ] wyeb
[ ] wyebadblock
[ ] zzz

For Reference
The following packages are assumed orphaned (once out of date):

[ ] chorizo
[ ] ed
[ ] exa
[ ] sc

@ioraff my hero

I haven't used KISS in a while so I'm dropping my packages

glib-networking
harfbuzz-icu
libsoup
webkit2gtk

see https://github.com/kiss-community/community/pull/1021: libusb needs a new maintainer.

I'll take ruby

Closing -- More convenient to annotate on the outdated tracker.

authors: aabacchus dilyn-corner mar-foo mmatongo

repo: kiss-community/community


text:
nfs-utils: bump to 2.5.2

Existing package

[Y] I am the maintainer of this package.

Version file change is missing?

messed up the commit, sorry

repo: kisslinux/community


text:
new package: timezone 2019c

Description of package
IANA time zone database and utilities.
IANA database page
github link
Checklist

[x] Latest upstream version.
[x] I agree to maintain this package (required).
[x] I agree to notify KISS if I can no longer maintain this package (required).

This is already packaged as tzdata.  :+1:
Thanks :)

authors: IslandAlpha dylanaraps


text:
feat(teler): add listen_addr & caller fields in the log

IMPORTANT: Please do not create a PR without creating an issue first!
(Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request).
Summary

feat(teler): add listen_addr & caller fields in the log
Proposed of changes
This PR fixes/implements the following bugs/features:

Bug 1
Bug 2
Feature 1
Feature 2
Breaking changes

How has this been tested?
Proof:

Closing issues
Fixes #
Checklist:

[x] My code follows the code style of this project.
[x] My changes successfully ran and pass linters locally (run make lint).
[x] I have written new tests for my changes.

[x] My changes successfully ran and pass tests locally.

[x] My change requires a change to the documentation.

[x] I have updated the documentation accordingly.

decisions:

why do I go with caching when calling getListenAddr? well after putting it through some benchmarking, I saw it was doing 3 allocs per op w/o any caching. fetching local addresses was turning out to be a bit of a performance hog, so i figured caching would smooth (cut down that overhead) things out and make everything run way more efficiently.
since it required by (1), refactoring to initialize (root) cache no matter what the Options.Development value does NOT really have any downsides.

Codecov Report
Attention: Patch coverage is 92.85714% with 1 line in your changes missing coverage. Please review.

Project coverage is 78.64%. Comparing base (20b5e7c) to head (48c2ac9).
Report is 5 commits behind head on master.

:exclamation: Current head 48c2ac9 differs from pull request most recent head 18f804e
Please upload reports for the commit 18f804e to get more accurate results.

Files
Patch %
Lines

utils.go
90.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #194      +/-   ##
==========================================
+ Coverage   78.47%   78.64%   +0.16%
==========================================
  Files          12       12
  Lines         920      932      +12
==========================================
+ Hits          722      733      +11
- Misses        131      132       +1
  Partials       67       67

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

repo: kitabisa/teler-waf


text:
Problem with NERDTree and CoC

When I want to open a file with NERDTree, Kite show me this error multiple times:
Kite: disabling coc.nvim's completions in this buffer

And I have to 'Press ENTER or type command to continue'.
I have this lines in my .vimrc:
  autocmd FileType python let b:coc_suggest_disable=1
  autocmd FileType javascript let b:coc_suggest_disable=1

  let g:kite_supported_languages = ['javascript', 'python']

Thanks for reporting this.  I've opened #343 to fix this.  If you have time, it would be great if you could try it out.

Thanks for reporting this.  I've opened #343 to fix this.  If you have time, it would be great if you could try it out.

It's working :)

It's working :)

repo: kiteco/vim-plugin


text:
Change the merge_type to rebase.

Change the PR merge type from merge as default to rebase.
Add tide target url to jump to.

/lgtm

authors: Jeffwan Summer-Field

repo: kitex-contrib/test-infra


text:
Scrollview blurs content

Some uses of the ScrollView blurs the content in it. Also when clicking buttons it only works once every 5 clicks. Probably because the content is set to non-integer points like 1,0000001 or something and some rendering kicks in.
I posted this on the google groups: https://groups.google.com/forum/#!topic/kivy-dev/dthCWk8lzCs
Code:
http://dpaste.com/3FVZ9N6/
Screenshot:
https://i.imgur.com/bmStIbT.png
Try (un)commeting size_hint_y: None to see the blurry effect yourself.
Here some small code to try it:
https://gist.github.com/NumesSanguis/3e0282bc8252cd86b76b
Same code without ScrollView:
https://gist.github.com/NumesSanguis/ded56793795ed79697ce

[INFO              ] [Kivy        ] v1.9.1-dev
[INFO              ] [Python      ] v2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2]
[INFO              ] [Factory     ] 177 symbols loaded
[INFO              ] [Image       ] Providers: img_tex, img_dds, img_gif, img_sdl2, img_pil (img_ffpyplayer ignored)
[INFO              ] [Text        ] Provider: sdl2
[INFO              ] [OSC         ] using  for socket
[INFO              ] [Window      ] Provider: sdl2(['window_egl_rpi'] ignored)
[INFO              ] [GL          ] OpenGL version <3.0 Mesa 10.1.3>
[INFO              ] [GL          ] OpenGL vendor
[INFO              ] [GL          ] OpenGL renderer <Mesa DRI Intel(R) Sandybridge Desktop >
[INFO              ] [GL          ] OpenGL parsed version: 3, 0
[INFO              ] [GL          ] Shading version <1.30>
[INFO              ] [GL          ] Texture max size <8192>
[INFO              ] [GL          ] Texture max units <16>
[INFO              ] [Window      ] auto add sdl2 input provider
[INFO              ] [Window      ] virtual keyboard not allowed, single mode, not docked

I've seen this many times with canvas lines, not just in a scrollview.
A workaround by tito/kovak was to do this for the problematic widget:
on_pos: list(map(int, self.pos))

Reopening, even if fixing is not practical, this case should be documented.

This solution doesn't help unfortunately.

@pyfrid where have you applied it?

directly to the labels which are blurred

@pyfrid, sorry, that should have been:
on_pos: self.pos = tuple(map(int, args[1]))

Similarily, if your width or height is also a float (it can happen if you use size_hint), you can do:
on_size: self.size = tuple(map(int, args[1]))

But doing this for size can also lead to a crash on resize, i've got this with ModalView:
RuntimeError: maximum recursion depth exceeded while calling a Python object

Wrapping with tuple() is not needed if you use Python 2.

still doesn't work for me. I will attach today a simple example for the demonstration.

Below is a short example and result. The problematic label is the first Label in the ParameterView class. I have tried both on_size and on_pos with custom height (and size_hint_y: None) of the Label and with automatic height, both without success. Actually if I change size of the window Tab labels become also blurred.
from kivy.uix.label import Label
from kivy.uix.boxlayout import BoxLayout

from kivy.properties import StringProperty

from kivy.base import runTouchApp
from kivy.lang import Builder
from kivy.app import App
from kivy.uix.tabbedpanel import TabbedPanel

Builder.load_string('''

<ParameterLimitButton@Button>:
    text_size: self.size
    text: ''
    size_hint_x: None
    width: self.height
    font_size: 10
    font_name: './data/fonts/DejaVuSans.ttf'
    halign: 'center'
    valign: 'middle'

<ParameterValueCombined@BoxLayout>:
    orientation: 'horizontal'
    size_hint_y: None
    height: '27sp'
    ParameterLimitButton:
        text: '|<'
    Slider:
        id: slider
        value: 0.3
        min: 0.1
        max: 0.5
    ParameterLimitButton:
        text: '>|'
    TextInput:
        text: '{0:.4g}'.format(slider.value)
        multiline: False
        size_hint_x: None
        width: '80sp'
        font_size: 10

<ParameterView@BoxLayout>:
    orientation: 'vertical'
    size_hint_y: None
    height: '50sp'
    BoxLayout:
        orientation: 'horizontal'
        CheckBox:
            active: True
            size_hint_x: None
            width: self.height
        Label:
            text_size: self.size
            shorten: True
            shorten_from: 'right'
            text: 'Parameter Name'
            font_size: 12
            bold: True
            halign: 'left'
            valign: 'middle'
            on_size: self.size = tuple(map(int, args[1]))
        Button:
            text: 'S'
            size_hint_x: None
            width: self.height
            font_size: 10
            halign: 'center'
            valign: 'middle'
    BoxLayout:
        id: value_container
        orientation: 'horizontal'
        ParameterValueCombined:

<ScrollableWidget>:
    orientation: 'vertical'
    padding: 10
    ScrollView:
        GridLayout:
            cols: 1
            size_hint_y: None
            height: self.minimum_height
            spacing: 15
            ParameterView:
            ParameterView:
            ParameterView:
            ParameterView:

<Test>:
    size_hint: .5, .5
    pos_hint: {'center_x': .5, 'center_y': .5}
    do_default_tab: False

    TabbedPanelItem:
        text: 'first tab'
        ScrollableWidget:

    TabbedPanelItem:
        text: 'tab2'
        BoxLayout:
            Label:
                text: 'Second tab content area'
            Button:
                text: 'Button that does nothing'
    TabbedPanelItem:
        text: 'tab3'
        RstDocument:
            text:
                '\\n'.join(("Hello world", "-----------",
                "You are in the third tab."))
''')

class ScrollableWidget(BoxLayout):
    pass

class Test(TabbedPanel):
    pass

class DemoApp(App):

    def build(self):
        return Test()

if __name__ == '__main__':
    DemoApp().run()

I can reproduce this with the example, indeed on resize it becomes more evident, all labels are blurred.

I would appreciate it if there will be any ideas how to fix it. As for me, it is a critical bug which makes kivy unusable on desktops.

I think I have found a possible solution for this problem.
If I change the default min_filter and mag_filter of label Texture to nearest, all labels become sharp.
In the file kivy.core.text.init.py
def refresh(self):
        '''Force re-rendering of the text
        '''
        self.resolve_font_name()

        # first pass, calculating width/height
        sz = self.render()
        self._size_texture = sz
        self._size = (sz[0], sz[1])

        # if no text are rendered, return nothing.
        width, height = self._size
        if width <= 1 or height <= 1:
            self.texture = self.texture_1px
            return

        # create a delayed texture
        texture = self.texture
        if texture is None or \
                width != texture.width or \
                height != texture.height:
            print "Creating texture"
            texture = Texture.create(size=(width, height),
                                     mipmap=self.options['mipmap'],
                                     callback=self._texture_fill)
 -->      texture.min_filter='nearest'
 -->      texture.mag_filter='nearest'
            texture.flip_vertical()
            texture.add_reload_observer(self._texture_refresh)
            self.texture = texture
        else:
            texture.ask_update(self._texture_fill)

I have checked it only on Windows and it seems to work.

As explained on the PR #3778:
Changing the mag filter or using int will mislead the resolution of this issue. I mean, as an user, if i activate this option, i expect that it will be not blurry and works. But it wont, if the widget tree is not pixel aligned.
I think we can make the distinction between 2 phases:
when something animate: we want smooth animation, int is not desirable, as well as mag filter.
when it's static: we want pixel-perfect rendering, no blur.
This could be resolved by a total another approach, more general:

ensure all the layout are computing pixel perfect layout, no half pixel: ie, use int() when it should be, as long as the width or height is an integer as well (we can't have pixel perfect calculation if the width/height are not integer). size_hint could compute integer width/height as well.
ensure any scrollview will end the scrolling to a pixel, not a portion of it. So when moving / animating, stay as today, but when we reach the end of the movement (delta too low to say there is a movement), then move to the nearest pixel in the direction of the movement.

That should cover all the standard case. The one that wont work will be the one when user use its own matrix and do it's own translation.

I am experiencing this issue as well.
ScrollView:
    size_hint: 0.41, 1

    Label:
        id: abc
        font_size: 13
        height: self.texture_size[1]
        markup: True
        size_hint_x: 1
        size_hint_y: None
        text_size: self.width, None
        valign: 'top'

By commenting out size_hint_y the blurring issue is resolved, however I can't get the label's content to be vertically aligned to the top.

I just upgraded my kivy env from 1.9.1 to latest 1.10. Unfortunately my listviews and scrollviews became (very) blurry again so I had to make the mag filter and int() code changes again.
Without these changes kivy is practically unusable for my windows desktop application.

I've been having this issue too with text being blurred. It becomes sharp again if I resize the app window just right. Adding the min_filter and mag_filter is working for now but can't say yet at this moment if it breaks other widgets in the process.

For me this doesn’t happen normally, but it does happen if a ScreenManager is at a non-integer position.

I always have blurred scrollviews on PC (Windows 10, Kivy 2.1.0). They may suddenly become sharp on window resizing, but then again get blurred. Everything is very random.

I have seen this with the Accordion vertical text tabs as the application window is resized. Here is an example where the labels are a little blurred.

Then if I resize the app window, I get the following sharper labels:

authors: BillBridge E-Unit NumesSanguis abedhammoud antorix dessant jurf pyfrid rubenanagua tito

repo: kivy/kivy


text:
ListProperty cannot be deepcopy'd (or pickled, probably)

Versions

Python: 3.7.4
OS: Gentoo Linux
Kivy: 1.11.1
Kivy installation method: pipenv

Description
ListProperty does not implement a valid __reduce__ or __reduce_ex__ method, making it impossible to deepcopy (or presumably pickle).
Code and Logs
import copy
from kivy.properties import ListProperty
from kivy.event import EventDispatcher

class A(EventDispatcher):
    attr = ListProperty()

a = A()
b = copy.deepcopy(a)

[INFO   ] [Logger      ] Record log in /home/dylan/.kivy/logs/kivy_19-09-05_17.txt
[INFO   ] [Kivy        ] v1.11.1
[INFO   ] [Kivy        ] Installed at "/home/dylan/.local/share/virtualenvs/venv/lib/python3.7/site-packages/kivy/__init__.py"
[INFO   ] [Python      ] v3.7.4 (default, Aug  1 2019, 15:47:41)
[GCC 8.3.0]
[INFO   ] [Python      ] Interpreter at "/home/dylan/.local/share/virtualenvs/venv/bin/python"
 Traceback (most recent call last):
   File "foo.py", line 9, in <module>
     b = copy.deepcopy(a)
   File "/home/dylan/.local/share/virtualenvs/venv/lib/python3.7/copy.py", line 169, in deepcopy
     rv = reductor(4)
   File "stringsource", line 2, in kivy._event.EventDispatcher.__reduce_cython__
 TypeError: no default __reduce__ due to non-trivial __cinit__

I'm guessing this would be an easy fix, so PR with unit test is welcome. DictProperty presumably has a similar issue.

I think this issue is not related to ListProperty, because the following code produce the same error.
import copy
from kivy.event import EventDispatcher

class A(EventDispatcher):
    pass

a = A()
b = copy.deepcopy(a)

Also, I believe we can't just copy.deepcopy() a EventDispatcher even if no error is occured.

Unfortunately this is still an issue in the latest version.
File "/usr/lib/python3.10/copy.py", line 172, in deepcopy
     y = _reconstruct(x, memo, *rv)
   File "/usr/lib/python3.10/copy.py", line 271, in _reconstruct
     state = deepcopy(state, memo)
   File "/usr/lib/python3.10/copy.py", line 146, in deepcopy
     y = copier(x, memo)
   File "/usr/lib/python3.10/copy.py", line 231, in _deepcopy_dict
     y[deepcopy(key, memo)] = deepcopy(value, memo)
   File "/usr/lib/python3.10/copy.py", line 161, in deepcopy
     rv = reductor(4)
   File "stringsource", line 2, in kivy.properties.ListProperty.__reduce_cython__
 TypeError: no default __reduce__ due to non-trivial __cinit__

Process finished with exit code 1

I have a similar / the same problem.
from copy import deepcopy
from kivy.properties import ListProperty
from kivy.uix.widget import Widget

class A(Widget):
    attr = ListProperty()

a = A()
deepcopy({'value': a.attr})

my workaround was to cast it to list.
Versions:

Python: 3.10.11
OS: Windows 11
Kivy: 2.2.1

authors: JacekJagosz dcbaker gottadiveintopython matham philip501


text:
pip install kivy[base] doesn't work on Apple Silicon

Software Versions

Python: 3.9.2
OS: macOS Big Sur 11.2.3
Kivy: 2.0.0
Kivy installation method: pip install "kivy[base]"

Describe the bug
It appeared to install fine:
Using legacy 'setup.py install' for Kivy-Garden, since package 'wheel' is not installed.
Building wheels for collected packages: kivy
  Building wheel for kivy (PEP 517) ... done
  Created wheel for kivy: filename=Kivy-2.0.0-cp39-cp39-macosx_11_0_arm64.whl size=13473950 sha256=ea574162775418cbe9aa83e93f9090a910224de64627a5a865bc124ace30810b
  Stored in directory: /Users/anentropic/Library/Caches/pip/wheels/1c/63/58/77cfa5999369eea092050f026f7a89bf183acc4b7c28fcb4cf
Successfully built kivy
Installing collected packages: docutils, pygments, idna, chardet, certifi, urllib3, requests, Kivy-Garden, pillow, kivy, numpy
    Running setup.py install for Kivy-Garden ... done
Successfully installed Kivy-Garden-0.1.4 certifi-2020.12.5 chardet-4.0.0 docutils-0.16 idna-2.10 kivy-2.0.0 numpy-1.20.1 pillow-8.1.2 pygments-2.8.1 requests-2.25.1 urllib3-1.26.4

But when I run my app:
[INFO   ] [Logger      ] Record log in /Users/anentropic/.kivy/logs/kivy_21-03-23_7.txt
[INFO   ] [Kivy        ] v2.0.0
[INFO   ] [Kivy        ] Installed at "/Users/anentropic/Documents/Dev/Personal/myproj/.venv/lib/python3.9/site-packages/kivy/__init__.py"
[INFO   ] [Python      ] v3.9.2 (default, Mar 18 2021, 20:48:06)
[Clang 12.0.0 (clang-1200.0.32.29)]
[INFO   ] [Python      ] Interpreter at "/Users/anentropic/Documents/Dev/Personal/myproj/.venv/bin/python"
[ERROR  ] [Clock       ] Unable to import kivy._clock. Have you perhaps forgotten to compile kivy? Kivy contains Cython code which needs to be compiled. A missing kivy._clock often indicates the Cython code has not been compiled. Please follow the installation instructions and make sure to compile Kivy
 Traceback (most recent call last):
   File "/Users/anentropic/Documents/Dev/Personal/myproj/myproj/kivy_canvas.py", line 6, in <module>
     from kivy.app import App
   File "/Users/anentropic/Documents/Dev/Personal/myproj/.venv/lib/python3.9/site-packages/kivy/app.py", line 411, in <module>
     from kivy.base import runTouchApp, async_runTouchApp, stopTouchApp
   File "/Users/anentropic/Documents/Dev/Personal/myproj/.venv/lib/python3.9/site-packages/kivy/base.py", line 28, in <module>
     from kivy.clock import Clock
   File "/Users/anentropic/Documents/Dev/Personal/myproj/.venv/lib/python3.9/site-packages/kivy/clock.py", line 466, in <module>
     from kivy._clock import CyClockBase, ClockEvent, FreeClockEvent, \
 ImportError: dlopen(/Users/anentropic/Documents/Dev/Personal/myproj/.venv/lib/python3.9/site-packages/kivy/_clock.cpython-39-darwin.so, 2): no suitable image found.  Did find:
 	/Users/anentropic/Documents/Dev/Personal/myproj/.venv/lib/python3.9/site-packages/kivy/_clock.cpython-39-darwin.so: mach-o, but wrong architecture
 	/Users/anentropic/Documents/Dev/Personal/myproj/.venv/lib/python3.9/site-packages/kivy/_clock.cpython-39-darwin.so: mach-o, but wrong architecture

Expected behavior
I also have a non-M1 mac (Mojave) and it works fine there, so I guess this is a problem on the new hardware.

Yep, options to build binary packages in the CI are very limited at the moment, and github actions (that we use to build and release wheels) doesn't have any, when that happen, we should be able to make universal2 compatible wheels and upload them to pypi. Not sure why it even installs the existing wheels now, as i though pip would detect it's not a proper wheel for your system, but maybe you need to update setuptools or pip, as things were defined relatively recently. You can certainly install from the source package using pip install kivy[base] --no-binary=all, though it'll require having cython installed and other dependencies.

Not sure why it even installs the existing wheels now

I think it's maybe because there is a "source distribution" on PyPI (https://pypi.org/project/Kivy/2.0.0/#files) as well as the wheels, so pip automatically builds its own wheel locally when installing. But something in the sdist is maybe platform dependent?

So maybe I just needed Cython installed first

You shouldn't need to have anything installed because pyproject.toml will make sure the deps (including cython) are installed in the build env.

Kivy 2.1.0 is out and we now ship universal2 binaries for Python 3.8-3.10.
Closing the issue cause should be fixed, anyway, if you still have some issue feel free to re-open it.

authors: anentropic matham misl6 tshirtman


text:
Horizontal align for popup title

This will allow to center the text of the popup title.

Can be used just by passing 'title_align' to the Popup options.

@Cuuuurzel good job. Could you also add the versionadded (1.9.0) tags?

authors: Cuuuurzel dessant


text:
pos_hint in MDBoxlayout

I used a MDBoxLayout and after adding some textfields and a button , I placed it on screen.
Then when I am trying to center it in screen I used pos_hint. It is taking the center_x value and placing it at the center but center_y value is ignored and the box layout stays at the bottom.
Is this intended or there is some bug?

:
    name: 'Register'
    canvas.before:
        Color:
            rgba: app.theme_cls.primary_color
        Rectangle:
            pos:self.pos
            size:self.size
MDBoxLayout:
    orientation: 'vertical'
    size_hint_x: 0.8
    pos_hint: {'center_x': 0.5,'center_y': 0.5}
    spacing: 20

@Prakash1124 You need to remember that all the widgets in the KivyMD library are Kivy widgets. So first you need to study the behavior of the BoxLayout widget - https://kivy.org/doc/stable/api-kivy.uix.boxlayout.html

I am sorry Yuri if I am bothering you but I tried this in kivy. Here the centre_x and centre_y worked. So my question stays as it is. I mean is it as per design or a bug?
Below are two snapshots:

pos_hint: {'center_x': 0.5,'center_y': 0.5}
pos_hint: {'center_x': 0.5,'center_y': 0.3}

repo: kivymd/KivyMD


text:
Added on_pre_dismiss, on_open, on_pre_open events fix on_dismiss

from kivy.lang import Builder

from kivymd.app import MDApp
from kivymd.uix.menu import MDDropdownMenu

KV = '''
MDScreen:

    MDRaisedButton:
        id: button
        text: "Open"
        pos_hint: {"center_x": .5, "center_y": .5}
        on_release: app.menu.open()
'''

class Test(MDApp):
    def __init__(self, **kwargs):
        super().__init__(**kwargs)
        self.screen = Builder.load_string(KV)
        menu_items = [
            {
                "text": f"Item {i}",
                "viewclass": "OneLineListItem",
                "on_release": lambda x=f"Item {i}": self.menu_callback(x),
            } for i in range(5)
        ]
        self.menu = MDDropdownMenu(
            caller=self.screen.ids.button,
            items=menu_items,
            width_mult=4,
        )
        self.menu.bind(on_open=lambda *args: print('on_open'))
        self.menu.bind(on_pre_open=lambda *args: print('on_pre_open'))
        self.menu.bind(on_dismiss=lambda *args: print('on_dismiss'))
        self.menu.bind(on_pre_dismiss=lambda *args: print('on_pre_dismiss'))

    def menu_callback(self, text_item):
        print(text_item)
        self.menu.dismiss()

    def build(self):
        return self.screen

Test().run()

https://user-images.githubusercontent.com/40869738/205523984-f9a3776e-2110-4ebc-97a6-80da8d4777ab.mp4

While there are no tests, these changes cannot be merged.

While there are no tests, these changes cannot be merged.

No problem. If test will be done, let me know, I add :versionadded 1.2.0 to 3 new events, and then you can merge it.

Can I change this code to match version 1.2.0 and you will merge?

The PR is deprecated due to the new API of the KivyMD library 2.0.0 version

authors: HeaTTheatR Neizvestnyj


text:
Add the ability to save the saved pages for offline reading in the internal memory

Is it possible to make the saved pages for offline reading and save them in a folder in the internal memory instead of saving them within the browser data, as the saved page files can only be accessed by root users.

The original Google Chrome actually saves pages into the download folder of the shared internal storage, and also has an option for saving downloads on MicroSD! (Benefits: mass storage access on PC for more convenient file transfer; files not lost if smartphone defective).
I wonder why it was changed for Kiwi browser in first place. Browsers locking saved pages away in /data, which is also done by Opera Mini and Samsung S Browser last time I checked, has been one of the long-term annoyances in mobile web browsing.
This lack of data portability denies backups, meaning without root access, the files will be trapped on that one smartphone indefinitely.
Who thought it would be a smart idea to store saved pages in a locked directory?!

Closing this and linking to #122


text:
Battery draining issue

I am battery draining issue since last update.

This is very unclear, and can be due to any number of reasons. Could you be more specific?

Installing too many plugins and scripts will lead to excessive power consumption

@Subbarao6338 I'm closing this as it's quite old. Feel free to reopen it if the problem still exists.


text:
Create circled Button

Opened by @jvaclavik

(Original issue https://github.com/kiwicom/universal-components/issues/257)

Done: https://github.com/kiwicom/universal-components/pull/261
(working also in Margarita)

authors: RobinCsl jvaclavik

repo: kiwicom/margarita


text:
IE freezes after clicking on "Select another booking"

When a user clicks on "Select another booking" in IE, loading is shown and browser freezes after a while and "IE to stop responding due to long time running script" warning is shown
Video: https://monosnap.com/file/et7UgzKVtNVbHxa7naqunTHwpV7kFS

possible related issue https://github.com/kiwicom/smart-faq/issues/554

authors: jalbertsr jaroslav-kubicek

repo: kiwicom/smart-faq


text:
Exclude scenarios using the NOT operator '~' for tags

Hi! I needed the ability to be able to commit incomplete scenarios but mark them so that the CI-system would not run them. I simply added the not-operator '~' that can specify tags that must not be present on scenarios if they are to run. The '~@TAG'-style is older gherkin, while the newer style uses "not @TAG" instead, but I did not want to include a space lest it interferes with the CLI.
My first pull request btw :)

Thank you for your contribution, @JakeTheSnake!
I added you as a contributor to the package.json and published v1.4.0. :)

authors: JakeTheSnake Lukas-Kullmann

repo: kiwigrid/gherkin-testcafe


text:
🛑 Thainess is down

In 4a09d94, Thainess (https://thainess.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Thainess is back up in 679c8e0.

repo: kizzna/uptime


text:
Documentation and Examples?

This looks interesting. Is there any documentation and examples on how to use it?

Not yet. While it is pretty easy now, starting to build documentation may be a good next step now :)

authors: RealDotNetDave kkokosa

repo: kkokosa/dotnet-counters-ui


text:
[feature] Wowhead link

Add wowhead link to quest, like in leatrix plus.

This is a leatrix code that implement this feature:
`
	-- Wowhead Links
	----------------------------------------------------------------------

	if LeaPlusLC["ShowWowheadLinks"] == "On" then

		-- Get localised Wowhead URL
		local wowheadLoc
		if GameLocale == "deDE" then wowheadLoc = "de.classic.wowhead.com"
		elseif GameLocale == "esMX" then wowheadLoc = "es.classic.wowhead.com"
		elseif GameLocale == "esES" then wowheadLoc = "es.classic.wowhead.com"
		elseif GameLocale == "frFR" then wowheadLoc = "fr.classic.wowhead.com"
		elseif GameLocale == "itIT" then wowheadLoc = "it.classic.wowhead.com"
		elseif GameLocale == "ptBR" then wowheadLoc = "pt.classic.wowhead.com"
		elseif GameLocale == "ruRU" then wowheadLoc = "ru.classic.wowhead.com"
		elseif GameLocale == "koKR" then wowheadLoc = "ko.classic.wowhead.com"
		elseif GameLocale == "zhCN" then wowheadLoc = "cn.classic.wowhead.com"
		elseif GameLocale == "zhTW" then wowheadLoc = "cn.classic.wowhead.com"
		else							 wowheadLoc = "classic.wowhead.com"
		end

		-- Create editbox
		local mEB = CreateFrame("EditBox", nil, QuestLogFrame)
		mEB:ClearAllPoints()
		mEB:SetPoint("TOPLEFT", 70, 4)
		mEB:SetHeight(16)
		mEB:SetFontObject("GameFontNormal")
		mEB:SetBlinkSpeed(0)
		mEB:SetAutoFocus(false)
		mEB:EnableKeyboard(false)
		mEB:SetHitRectInsets(0, 90, 0, 0)
		mEB:SetScript("OnKeyDown", function() end)
		mEB:SetScript("OnMouseUp", function()
			if mEB:IsMouseOver() then
				mEB:HighlightText()
			else
				mEB:HighlightText(0, 0)
			end
		end)

		-- Set the background color
		mEB.t = mEB:CreateTexture(nil, "BACKGROUND")
		mEB.t:SetPoint(mEB:GetPoint())
		mEB.t:SetSize(mEB:GetSize())
		mEB.t:SetColorTexture(0.05, 0.05, 0.05, 1.0)

		-- Create hidden font string (used for setting width of editbox)
		mEB.z = mEB:CreateFontString(nil, 'ARTWORK', 'GameFontNormal')
		mEB.z:Hide()

		-- Function to set editbox value
		local function SetQuestInBox(questListID)

			local questTitle, void, void, isHeader, void, void, void, questID = GetQuestLogTitle(questListID)
			if questID and not isHeader then

				-- Hide editbox if quest ID is invalid
				if questID == 0 then mEB:Hide() else mEB:Show() end

				-- Set editbox text
				mEB:SetText("https://" .. wowheadLoc .. "/quest=" .. questID)

				-- Set hidden fontstring then resize editbox to match
				mEB.z:SetText(mEB:GetText())
				mEB:SetWidth(mEB.z:GetStringWidth() + 90)
				mEB.t:SetWidth(mEB.z:GetStringWidth())

				-- Get quest title for tooltip
				if questTitle then
					mEB.tiptext = questTitle .. "|n" .. L["Press CTRL/C to copy."]
				else
					mEB.tiptext = ""
					if mEB:IsMouseOver() and GameTooltip:IsShown() then GameTooltip:Hide() end
				end

			end
		end

		-- Set URL when quest is selected
		hooksecurefunc("QuestLog_SetSelection", function(questListID)
			SetQuestInBox(questListID)
		end)

		-- Create tooltip
		mEB:HookScript("OnEnter", function()
			mEB:HighlightText()
			mEB:SetFocus()
			GameTooltip:SetOwner(mEB, "ANCHOR_BOTTOM", 0, -10)
			GameTooltip:SetText(mEB.tiptext, nil, nil, nil, nil, true)
			GameTooltip:Show()
		end)

		mEB:HookScript("OnLeave", function()
			mEB:HighlightText(0, 0)
			mEB:ClearFocus()
			GameTooltip:Hide()
		end)

	end

`

Accepted

Added.

authors: Kkthnx amonsat


text:
Why is the joystick guid not matching gamepadtool etc?

I noticed this library shows different GUIDs than the https://generalarcade.com/gamepadtool/ and other sdl applications.
~I wonder if that's because this library uses SDL_JoystickGetDeviceGUID instead of SDL_JoystickGetGUID.
could you expose both?~ for my app to work I need to find the same guid as the other tools.
Xbox One elite 2 controller
this library:
0300938d5e040000ff02000000007200
gamepad tool:
030000005e040000ff02000000007801

what I found so far is that for my use case, im trying to match guide with yuzu.
they're resetting the crc part in the guid to 0. this makes my ps5 controller guid match properly.
and my xbox controller also, until the last 3 numbers; 7200 - 7801.
I can't for the life of me figure out why...

yuzu (sdl 2.8) and sdl2 gamepad tool (sdl2.0.7) : 030000005e040000000b000000007801
node-sdl (sdl 2.8 with crc set to 0), and sdl2 gamepad mapper (sdl 2.26.1): 030000005e040000000b000000007200

interestingly enough, for the ps5 dualsense pro wired it matches differently:

yuzu (sdl 2.8),  node-sdl (sdl 2.8 with crc set to 0): 030000004c050000f20d000000016800
sdl2 gamepad mapper (sdl 2.26.1): 030072264c050000f20d000000016800 (crc not removed)
sdl2 gamepad tool (sdl2.0.7): 030000004c050000f20d000000000000

so I guess im mainly wondering why xbox is so different..

found it,
        // Disable raw input. When enabled this setting causes SDL to die when a web applet opens
        SDL_SetHint(SDL_HINT_JOYSTICK_RAWINPUT, "0");

sorry for barking up the wrong tree :)

@patroza you type much faster than me :p I was about to post the following, wich might still be useful to to have in the future so here it is anyway:
You probably figured this out yourself (and that's why you crossed out that part) but SDL_JoystickGetGUID and SDL_JoystickGetGUID get their values from the same place so that can't be the issue.
SDL_GUID looks like this:
        /* This GUID fits the standard form:
         * 16-bit bus
         * 16-bit CRC16 of the joystick name (can be zero)
         * 16-bit vendor ID
         * 16-bit zero
         * 16-bit product ID
         * 16-bit zero
         * 16-bit version
         * 8-bit driver identifier ('h' for HIDAPI, 'x' for XInput, etc.)
         * 8-bit driver-dependent type info
         */

So the last 4 digits are different because they depend on what input driver you are using. 72 is 'r' (raw) and 78 is 'x' (x-input). You can set the SDL_JOYSTICK_RAWINPUT environment variable to override the default input driver. Whether you should do that depends on what you are building. Why do you need the exact GUID?
As a sode note: latest node-sdl is using SDL 2.26.1. You have it listed as 2.8 in your tests?

@kmamal thanks a lot. yea I got there too after a long hard road.
listed as 2.28 as thats what I updated the lib to, to see if the older version was my problem.
regarding why; I have 4 different controllers in different parts of my home, which I either direct connect via usb, or via bluetooth/wireless dongle, or virtually via Moonshine/SteamLink. it is rather bothersome to manually go into settings to pick the right controller, so I decided to scan for the latest gamepad added, and pick a relevant profile and update the guid accordingly.
so for yuzu to like my profile changes, the guid of the controller must be one it understands :)

authors: kmamal patroza

repo: kmamal/node-sdl


text:
Pass eventtype owner to data plane

Part of #3181
We need the eventtype Reference/Owner information in the dataplane so that we can auto create event types in #3181.

Proposed Changes

Pass the event type ownership info through the data plane contract

/cc @Leo6Leo @matzew @creydr

/retest-required

/retest-required

/retest-required

/test upgrade-tests

/test upgrade-tests

I think the upgrade test failures might be real failures, I will look into it

/retest-required

@Leo6Leo I think the test failure is an actual issue, not a flaky failure here. Not sure what is causing the issue though...

Now that changes to the contract are backwards compatible, the tests are passing on this PR.
/cc @pierDipi @Leo6Leo

/test upgrade-tests

/retest-required

/test upgrade-tests

/retest

/test reconciler-tests


text:
[Automated] Update eventing-kafka-broker-eventing nightly

/assign @knative-extensions/eventing-wg-leads
/cc @knative-extensions/eventing-wg-leads
Produced via:
for x in eventing-crds.yaml eventing-core.yaml eventing-tls-networking.yaml; do
  curl https://storage.googleapis.com/knative-nightly/eventing/latest/$x > ${GITHUB_WORKSPACE}/./third_party/eventing-latest/$x
done

Details:
bumping knative.dev/eventing 67ceb9e...43cf75a:
  > 43cf75a [main] Upgrade to latest dependencies (# 8004)
  > ea8f0fd Add `AppliedEventPoliciesStatus` type (# 7999)
  > 8da4543 Add `default-authorization-mode` feature flag (# 7996)
  > 7f37d64 Add EventPolicy types  (# 7995)
  > 6259113 Fix possible nil pointer dereference in event-dispatcher (# 7994)

/retest

/test upgrade-tests

authors: creydr knative-automation


text:
refactor kafka producer from being called a channel to a receiver.

Recently, in the distributed kafka channel implementation, we renamed the Kafka Producer pod's top level directory from channel/ to receiver as the term "channel" was being abused/overused.  This PR finishes that renaming effort by changing the code to read consistently, and altering the runtime artifacts naming to include receiver instead of channel.  Other than naming, and some other general code clean-up, there are no intended behavioural differences.

/hold
found additional touch-points

/test pull-knative-sandbox-eventing-kafka-integration-tests

/unhold

/test pull-knative-sandbox-eventing-kafka-unit-tests

/lgtm

authors: phamilton travis-minke-sap

repo: knative-sandbox/eventing-kafka


text:
[KOGITO-6047] Introduce KogitoSource as Binding and Sink

Changes

:broom: Change the KogitoSource interface to behave as a Subject Binding instead to wrap the KogitoRuntime object owned by the Kogito Operator
:wastebasket: Completely removed the Kogito Operator dependencies. Now you can deploy any kind of Podspecable object and bind to this source.

/kind enhancement

Release Note

`KogitoSource` interface has changed to act as a Subject Binding instead of wrapping the `KogitoRuntime` CR.
Now the Kogito Operator is not a requirement to use the Kogito Eventing anymore. The subject must be a Kogito application deployed via any Podspecable object (Deployment, KService, DeploymentConfig, and so on).

In the next releases, the source will enforce the subject to be a Kogito service and will add more capabilities and configuration to the service to enhance the integration with the Knative Platform.

@lionelvillard can you take a look? :)

/kind enhancement

repo: knative-sandbox/eventing-kogito


text:
[master] Upgrade to latest dependencies

Cron. -knative-prow-robot
/cc knative-sandbox/channel-wg-leads
/assign knative-sandbox/channel-wg-leads
Produced via:
./hack/update-deps.sh --upgrade --release v0.21
./hack/update-codegen.sh

Details:
bumping knative.dev/pkg 1bbf0a6...992644a:
  > 992644a Update common github actions (# 1996)
  > 8cd47b5 drop excess logger properties (# 1993)
bumping knative.dev/hack 4422dca...8d623a0:
  > 8d623a0 Use git tag directly in master to get latest version (# 43)
bumping knative.dev/eventing b10d720...d1bac1e:
  > d1bac1e use v1beta2 as the storage version of PingSource (# 4750)
  > 5dc363d [# 4744] Update conformance test helper (# 4756)
  > 764685c upgrade to latest dependencies (# 4761)

/lgtm
/approve

/lgtm
/approve

authors: knative-automation vaikas

repo: knative-sandbox/eventing-rabbitmq


text:
jobRunner.Run isn't waiting properly for the end of the Job it creates

jobRunner.Run is supposed to create a given batchv1.Job and wait until it finishes with some outcome, and after successful run deletes the job. The current implementations is buggy and doesn't wait properly.
https://github.com/knative-sandbox/kn-plugin-event/blob/dd15346ae76b9e0c7168d2166ce45c491526a7c4/internal/k8s/jobrunner.go#L43-L52
Proper implementations should support the retries that batchv1.Job can specify, and return error only if those retries exceeds limits.

/assign

repo: knative-sandbox/kn-plugin-event


text:
[master] Upgrade to latest dependencies

Produced via:
./hack/update-deps.sh --upgrade
./hack/update-codegen.sh

Cron. -knative-prow-robot
/cc knative-sandbox/networking-wg-leads
/assign knative-sandbox/networking-wg-leads

/lgtm
/approve

authors: ZhiminXiang knative-automation

repo: knative-sandbox/net-istio


text:
Add dep-collector to the list of required tools in Gopkg.toml

We need it as a tool, but not its dependencies.
For details, see https://github.com/knative/build/pull/487#issuecomment-443476057

/retest

repo: knative/build-pipeline


text:
Format markdown

Produced via: prettier --write --prose-wrap=always $(find -name '*.md' | grep -v vendor | grep -v .github)

/close
Already taken care in https://github.com/knative/build-pipeline/pull/349
cc @mattmoor we should update the bot to open a new PR only if there is not a existing one :angel:

authors: mattmoor-sockpuppet vdemeester


text:
chore: deploy cmd namespace

:broom: separates namespace warnings from derivation logic
:broom: tests cleanup and simplification
:broom: integrates deploy namespace value derivation with flag init flow

Prepratory cleanup for switch to use Global Config namespace value when available.

/lgtm
/approve

authors: lkingland matejvasek

repo: knative/func


text:
[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative/func-approvers
/assign knative/func-approvers
Produced by: knative-extensions/knobots/actions/update-deps

/approve
/lgtm

authors: knative-automation matejvasek


text:
[release-0.15] update knative.dev/pkg which includes webhook fixes

Proposed Changes

This includes webhook fixes that should make upgrading from 0.15 to 0.16 smooth

Release Note

Webhook responses now return TypeMeta which would interrupt serving upgrades

/assign @tcnghia

/lgtm
/approve

authors: dprotaso tcnghia

repo: knative/net-istio


text:
[WIP] Experimenting with new manifestival package structure

WIP, not merged yet: https://github.com/manifestival/manifestival/pull/59

/test all

/retest

repo: knative/operator


text:
Reduce the boilerplate for setting up duck.InformerFactory's.

This augments the injection codegen with the capability to produce a duck.InformerFactory
attached to context for each type that we process.
Now a duck.InformerFactory for "Addressable" can be produced by "Get"ing it from the context.
This is triggered by placing // +genduck on the type that implements duck.Implementable.
/hold
I am going to stage this into the downstream repos (partially to make sure everything WAI).

This is going to be so awesome. 👏 😎
/lgtm

/hold cancel

repo: knative/pkg


text:
Validation Script

In what area(s)?

/area API
/area autoscale
/area build
/area monitoring
/area networking
/area test-and-release

Describe the feature
It would be helpful to have a validation script that took in a kubeconfig and gave a pass/fail or likelihood of passing if knative could be run on the cluster. The script would be run by a cluster admin and validate that the kubernetes cluster is properly setup to support knative.
It would be run like: validate-cluster.sh --kubeconfig=/path/to/kubeconfig
I'm not immediately sure what all the checks would be, one initial suggestion by @dgerd is the initial check would simply check the k8s version and perhaps a version of a supported ingress/gateways services.

I would like to work on this item.

/assign @yu2003w

@yu2003w Are u a member of Knative? Why cannot I assign it to you?

@houshengbo I'm not member of knative.

@yu2003w You definitely need to join the knative community as a member. However, you can start working on it anyhow
@k4leung4 @greghaynes Since we folks have gone the process of proposing knative member before, could you propose @yu2003w as a member of knative? I can be another member proposing @yu2003w if needed.

validation scripts check following items:
1,  k8s cluster version
2, Istio version and following services deployed
cluster-local-gateway
istio-ingressgateway
3, cert manager installed

Thanks for working on this. What do we think about rather than a shell script we make this go code which our operator can run? I expect we will want our operator to perform checks like this as part of normal operation and it will be difficult to bake in a shell script which it runs.

Operator should perform the checks before installing Knative Serving.
Does operator need to check the conditions such as ingress gateway periodically after knative serving installed?
Does operator support to install serving with Gloo preinstalled rather than istio?

Operator should perform the checks before installing Knative Serving.
Yes. I am open to the idea of updating the KnativeServing CRD to add the desired dependency configuration. @houshengbo  @greghaynes and @trshafer jcrossley3

Something like this?
spec:
  deps:
    istio: true
    gloo: false
    mtls: false

Does operator need to check the conditions such as ingress gateway periodically after knative serving installed?
I don't think it's necessary for the operator to be continually checking conditions for ingress gateway. Actually the more I think about this, I think it might make sense for the operator to be in a caution state if the ingress gateway goes away. One thing I'm thinking of is upgrading a cluster from one version to another. Upgrading the operator should upgrade the knative config and report any dependency issues. So if we're upgrading in a cluster where the operator is in a "caution" state, that should probably still update knative-serving.

I'm also thinking if upgrading the operator means knative has a backward incompatible change with a prior version of istio. It would not want to squash an existing istio configuration, but also it should fail to install.

Does operator support to install serving with Gloo preinstalled rather than istio?
I think it's still undecided if the operator should install the dependencies or just report the dependencies are uninstalled. We definitely don't want the operator to override an existing istio/gloo installation.

@greghaynes Per your comments, instead of running scripts to validate. We can use the kind job to run commands for the validations, like the following pods in istio:
istio-cleanup-secrets-1.2.0-wblhw         0/1     Completed   0          2m43s
istio-init-crd-10-qcfkp                   0/1     Completed   0          2m55s
istio-init-crd-11-c9sps                   0/1     Completed   0          2m54s
istio-init-crd-12-v7v8z                   0/1     Completed   0          2m54s
istio-security-post-install-1.2.0-tc2p5   0/1     Completed   0          2m42s

We can have a pod named "knative-serving-operator-dependency-validation" running the validation one by one. Completed means the validation has passed. If it fails, we can either try to fix it, or log the error message. Any thoughts on that?
@trshafer @yu2003w We can list the desired dependencies, and specify whether to validate them in a ConfigMap, for example? The pod "knative-serving-operator-dependency-validation" can access this ConfigMap and run the validate one by one.
This is currently some of my consideration. Welcome your comments.

Do we need to run all validation tasks in one job and check error message to determine which failed? Or is validation divided into several jobs?

What value do we get from the additional complexity of a separate job and possibly a configmap when we already have an operator and a CRD? I think we agreed in the recent WG meeting that the best way to communicate the status of the installation (including any missing deps) is through the status field of the custom resource. And I think the best way to do that is by having the operator invoke any necessary validation logic.

Thanks for the comments. I will try to update CRD and send PR later this week.

A few comments on script vs-CRD:

Being able to run these on an ongoing basis would be great. This is probably pro-CRD.
There are a set of getting-started problems that may be difficult to diagnose which happen before the CRD and operator are running on the cluster. Some examples (these are mostly fixed, but there may be others):

Calling role does not have sufficient RBAC (this is a sample from GKE that I'm aware of).
Certain Kubernetes flags or addons are disabled in the cluster (e.g. mutating admission control)

It may be desirable to capture the output of the tool for later analysis. apiserver CRD storage might be good for this, though a text file is probably also fine.
Whatever is running the system checks may need a fairly broad RBAC role (though hopefully this would mostly be "read" capabilities). This may run into some of the same problems as Tiller. (Though, see point 1 about running on an ongoing basis.)

For the dependencies, shall we also check the version?
For example, for istio, except validating ingress/cluster-local gateway working as expected, shall we check wether Istio-version is meet the requirement?
Maybe version is in a range of 1.1.3,1.1.7, 1.2.0.

I think so, it makes sense for knative to support a range of istio installations. Probably makes sense to be a wildcard on patch version. Currently the installation guide supports one version, 1.1.7: https://knative.dev/docs/install/installing-istio/#downloading-istio-and-installing-crds

@trshafer what's your meaning of patch?

The third number in a release: Major.Minor.Patch.

@trshafer
How could istio/certmanager version be retrieved? From image tag or other? I need some advice.
For istio, version could be get from at least two points:
1, "productVersion" in annonation
Annotations:        productID: istio-galley_1.1.7_apachev2_00000
                    productName: istio-galley
                    productVersion: 1.1.7
                    sidecar.istio.io/inject: false

2, image tag
now istio images are tagged with version.  {docker repo}/istio-galley:1.1.7
For certmanager, it seems that image tag is the only approach to get version.
quay.io/jetstack/cert-manager-controller:v0.6.1

Which do you prefer? Or is there any other conventional method?
For patch, could we use a smallest number rather than wildcard?
Take istio as an example, now istio 1.1.2, 1.1.3, 1.1.7 and 1.2.0 could be installed, if wildcard used and user installed istio 1.1.0, it will pass validation check. However, maybe istio 1.1.0 couldn't be supported.
If using istio 1.1.2 as the baseline version, versions higher than 1.1.1 could be accepted.
Do you think this make sense?

/assign yu2003w

I don't think it can reliably be used from the image tag. Similarly how users can change the format of the image digest in the operator using the KnativeServing CRD, users may change the istio image digest.
Does this work for getting the istio version? It grabs the istio version from the environment variable in the proxy container?
ISTIO_PILOT_POD=$(kubectl get pod --selector=istio=pilot -n istio-system -o jsonpath='{$.items[0].metadata.name}')
kubectl exec -it $ISTIO_PILOT_POD -n istio-system --container istio-proxy env | grep VERSION

@trshafer  Thanks a lot. I think we should rely on ISTIO_META_ISTIO_VERSION=1.1.7 to get Istio version.

@trshafer I have updated code and got Istio version from Istio-pilot code.
Currently version of cert-manager should be the image tag. Developer of cert-manager confirmed this.

@trshafer For istio 1.2.4, in isitio-pilot pod, env ISTIO_META_ISTIO_VERSION is not set any more.
I'm afraid we couldn't get Istio version from pod.
Maybe we need to get it from image tag.
Any thoughts about this?

authors: evankanderson greghaynes houshengbo jcrossley3 trshafer yu2003w

repo: knative/serving-operator


text:
OOCSS with BEM

Hi, is it works with BEM syntax - can you add some examples? :)
The BEM uses modifiers (--) and children (__) for object, so how to write documentation? :)

Yes, it works fine with BEM. Here's a styleguide using KSS with BEM:
http://scan.me/styleguide/statuses

@janiv thanks!
KSS looks really awesome, I have to try it. :)

authors: hobi janiv

repo: kneath/kss


text:
feat: Add types to the Migrator interface

Add typings to the list and forceFreeMigrationsLock methods.

Thanks!

authors: kibertoad lffg

repo: knex/knex


text:
feat: add spacing token for card width

Description

Adds spacing unit 160 (40rem / 640px) to use as the default width for cards

Tasks
KNO-6153

#110  👈
main

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

Join @kylemcd and the rest of your teammates on  Graphite

Merge activity

Jun 6, 4:46 PM CDT: @kylemcd started a stack merge that includes this pull request via Graphite.

repo: knocklabs/telegraph


text:
MQTT client.publish, How do I publish a dynamic string? Stopped working after recompile!

I cannot publish any strings in variables anymore!
All worked fine for a year or so. Then I recompiled my sketch and it stopped working.
I can do client.publish("topic","Sometext"),
but not
char msg[] = "Sometext";
client.publish("topic",msg);
I see the definition of publish in the API documentation says you have to use const char[] As I am not a C programmer I don't really understand the fine meaning of that definition. But if I define the variable then it will give a compile error when I try to change that "variable" because it is readonly.

I found out that the MQTT_MAX_PACKET_SIZE variable was set too low. This has to be done in the PubSubClient.h file of the library, it cannot be redefinied in the Sketch!
See also https://gist.github.com/igrr/7f7e7973366fc01d6393 for the precise commands to publish a String and here you will find the statement of the builder of the lib what to do.

I tried char[10] = "abc";
it's ok , but not dynamic

incomming = .....
char charBuf[incoming.length() + 1];
incoming.toCharArray(charBuf,incoming.length() + 1);
client.publish(mqtt_topic_pub, charBuf);
Try it ^^

It works. Thank you!

authors: hoekbrwr phungorquan quini27

repo: knolleary/pubsubclient


text:
[Problem] Text frame aggregation disabled

When we use this plugin we have a problem.
Socket closed with error code 1008 and message Text frame aggregation disabled.
Can you describe how can be fix or resolve it.
Yes, we can crop data but we want get it without cropping.

Thank you for using this plugin and reporting the issue. I've figured out what causes the error and fixed it. That test version is now push on a develop branch. Could you try it out? If will be resolved the error, will publish it as ver 0.8.1.
In order to try it out, need to remove it and install the test version on a develop branch:
$ cordova plugin remove com.knowledgecode.cordova.websocket
$ cordova plugin add https://github.com/knowledgecode/WebSocket-for-Android#develop

Did not help.
We can send only 8192 bites.

Did not help.
We can send only 8192 bites.

Hm...
We could have certainly sent only 8192 bytes by using the master version, but the develop branch version has been probably fixed. Make sure whether you installed the develop branch version. I additionally pushed updating to the branch to update version of the plugin a little ago. If you succeed installing the new version, you can see the display as follows:
$ cordova plugin
com.knowledgecode.cordova.websocket 0.8.1 "WebSocket for Android"

I decide to publish the new version formally though your response is nothing because I believe that this bug is already fixed. And then I will close this issue once, but if you think it is not resolved, please post a message again here.
If it weren't for your report, I wouldn't notice it. Thank you very much.

authors: Atsyn knowledgecode

repo: knowledgecode/WebSocket-for-Android


text:
Line annotations out of chart area

Hi,
it would be great to have the line annotations just inside the chart area, not on the whole panel.

I added a tag. good suggestion.

authors: landret timmolter

repo: knowm/XChart


text:
Pool and CDP options to specify target timeout

I was getting a lot of "timeout waiting for response from target" errors and noticed that the DefaultNewTargetTimeout was hard-coded. So I added a CDP Option and matching PoolOption to specify these when configuring a pool.

Coverage decreased (-0.8%) to 40.258% when pulling ed9a3bdb57065faa9d14e574f51072014e400075 on JalfResi:default-timeout into b5032069e3ac10c0636bf0bde9f1d18bc5475d01 on knq:master.

I'll add tests for these

Hey -- seriously, I do appreciate your submission, but this is another one of those things that the existing code (all the timeout stuff) was only put in temporarily, and will be moved to setting a value on the context. I actually have most of that written on a separate branch, but haven't pushed the changes, as I have not yet written up the documentation on how to use it. Please keep a look for the revisions over the next couple days.

Cool no probs

authors: JalfResi coveralls kenshaw

repo: knq/chromedp


text:
subgraph fails to render when subgraph ID starts with a number

Describe the bug
A subgraph id cannot start with a Number[0-9] - it needs to start with a letter [a-z][A-Z]
To Reproduce
Working
Not Working
Working Workaround
Not Working Workaround
Expected behavior
subgraph 1test
A-->B
end
should render
Desktop (please complete the following information):

Version 8.2.3

Additional context
Add any other context about the problem here.

It works if you set the subgraph title  in quotes:
subgraph "1test"
A-->B
end

If i quote it and want to add another text it fails:
subgraph "1test"[hello]
A-->B
end

Ah sorry, when I read it I missed that you want an ID to be named that way, so it's not about the title.

repo: knsv/mermaid


text:
Display git version & date to introduction section

This change is to know which specific commit of the book is published on the official site: https://defmt.ferrous-systems.com/
Note the sed command is written to work on OSX (the extra .bak parameter) and Unix systems, for some details check this SO discussion

add mdbook preprocessor to replace the version placeholder string with the used git version & date
add short section in the introduction to display version

Reference:

issue 494 discussion in the official mdbook repository

The deploy preview still shows the placeholder, did it not work?

Yes, it seems the sed command failed in the preprocessor. Will check again and update accordingly.

The preview now displays used git hash and commit date.

cool!
bors r+

That's neat! 🎉

authors: Urhengulas jonas-schievink justahero

repo: knurling-rs/defmt


text:
feat: support sameSite=none cookies (bump cookies dependency) (#1390)

Updated cookie dependency on v1 branch to support sameSite=none cookies.
This change was already applied to the current (v2) but we needed this same functionality for v1.

koa@1.7.0 released

authors: Elias-Serneels dead-horse

repo: koajs/koa


text:
Issue 197 misc

Updated README with npmcdn link
Refactored helper modules

#197 and #225 related

:+1:

repo: koalyptus/TableFilter


text:
Add Istio plugin

[ ] I added a CHANGELOG entry for this change.
[ ] I adjusted the corresponding documentation for this change.
[ ] I adjusted the values.yaml file and the documentation for all values.

Codecov Report

Merging #342 (17499a6) into rework-kobs-architecture (8a0abd4) will decrease coverage by 2.83%.
The diff coverage is 7.77%.

:exclamation: Current head 17499a6 differs from pull request most recent head 911f9cd. Consider uploading reports for the commit 911f9cd to get more accurate results

@@                     Coverage Diff                      @@
##           rework-kobs-architecture     #342      +/-   ##
============================================================
- Coverage                     46.43%   43.60%   -2.84%
============================================================
  Files                            98       98
  Lines                          6803     7295     +492
============================================================
+ Hits                           3159     3181      +22
- Misses                         3577     4043     +466
- Partials                         67       71       +4

Impacted Files
Coverage Δ

plugins/plugin-istio/pkg/instance/instance.go
5.79% <5.79%> (ø)

plugins/plugin-istio/cmd/istio.go
9.79% <9.79%> (ø)

plugins/plugin-jaeger/cmd/jaeger.go

plugins/plugin-jaeger/pkg/instance/instance.go

plugins/plugin-prometheus/pkg/instance/instance.go
5.72% <0.00%> (+5.72%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: axdotl codecov-commenter

repo: kobsio/kobs


text:
💅 favicon

close #6784

authors: roiLeo yangwao

repo: kodadot/nft-gallery


text:
style: signing on migration page

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Needs Design check

@exezbcz please review

Context

[x] Closes #8579
[x] Closes #8685

Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

Screenshot 📸

[x] My fix has changed UI

feedback
button to start signing

its this one from components in figma:

https://www.figma.com/file/JXNtryaNYhY0XJNArzvPQx/Handoff?type=design&node-id=5311-18771&mode=design&t=LP9IswSuLvP6u3xk-11
lets put this button to a sign all transaction to continue - so the upper new button is the primary now

by default its active

Signing styling

could you please have a look at the signing issue please

underlined text in the img (blue) should be 16px font size

this one is correct

inactive section should be grey

its this one from components in figma:
figma.com/file/JXNtryaNYhY0XJNArzvPQx/Handoff?type=design&node-id=5311-18771&mode=design&t=LP9IswSuLvP6u3xk-11

hooo, nice

Time to adjust our colour token in SCSS according to Figma https://github.com/kodadot/nft-gallery/blob/main/libs/ui/src/scss/tailwind.scss

lets put this button to a sign all transaction to continue - so the upper new button is the primary now

by default its active

@exezbcz updated, but I dont understand this one. Did you mean to change the text to "continue"?

lgtm, maybe check if 'border' is not used elsewhere and replace is-size-7 with text-xs

Time to adjust our colour token in SCSS according to Figma main/libs/ui/src/scss/tailwind.scss

will open these in a separate PR. for border should be fine, because will fallback to tailwind class

Thanks!
pay 50 usd

😍 Perfect, I’ve sent the payout
💵 $50 @ 7.58 USD/DOT ~ 6.596 $DOT
🧗 1xjvRADwdJcnmUCLWerEHR4iGCT5EBTm4D4fzLLg4LcAC9p
🔗 0xcbddf51d5f81c266a276d24a444fe802f05082031d7b938a9a7f920f56e195e1
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues

authors: exezbcz preschian yangwao


text:
refactor(core.security) simple and clean structure have been used in …

…verify password hash method

Looks good to me. Thanks for your contribution. 🚀

authors: ahmet-cetinkaya uygurrmustafa


text:
Getting error upon compiling in gcc

cannot execute binary file: Exec format error

Come on, this is a basic dev problem (with no detail) that you should not be pestering the maintainer with.  Please make SOME effort.
Rgds
Damon

Hi @prtkdas96 and thanks for checking out this project :)
If you would like help compiling the project, I'll need a bit more information to be able to.
I need to know how you compiled the code and how you tried to run it.
In other words: What have you tried and why did it not work?
I do agree with @DamonHD that perhaps you could try seeking help on stackoverflow.com or something similar.
Issues are usually reserved for reporting defects and I am sure that your problem comes from incorrect use somehow :)

Thanks for the help. I am sorry for disturbing you all. I am a newbie and was confused where to address my problem. @kokke I am using the latest version of Ubuntu and using gcc compiler. Although the program is compiling, running the same generates the error mentioned above.

No problem @prtkdas96 we were all newbies once :)
How are you compiling the program?
Which commands are you running?

I am compiling the program using gcc -c aes.c -DCBC=1 -DECB=0 -o aes2. After that I am running ./aes2 which initially gave me error. But after some digging, I found out that using chmod results in successful compilation. But even after doing so, I am getting the cannot execute binary file error. Should I try recompiling it in a virtual box with ubuntu server for arm installed?

If you are just running gcc -c aes.c -DCBC=1 -DECB=0 -o aes2 you cannot execute the output. That is just object-code, not a binary.
You need to also add a main()-function and compile that and link with the aes2-object code.

I'm closing this issue since it seems it wasn't a problem with the code.
Did you get the code to compile and run after all ?

authors: DamonHD kokke prtkdas96

repo: kokke/tiny-AES-c

license: Unlicense


text:
feat: store free rests in modifiers

Add Noncombat / Passive category for Disco Nap.

I just woke up so sorry if it's obvious - what's the difference between Passive and Noncombat/Passive?

Passive is for skills which have type Passive. Noncombat / Passive is for Noncombat skills which have a Passive ability, as well. Compare Combat / Passive.

authors: gausie midgleyc

repo: kolmafia/kolmafia


text:
Möjlighet att bläddra mellan matseldar

Det är bra för historik och planering att kunna se andra veckors matsedlar. Slutna Skolplattformen har denna funktion.

Jag kan inte heller testa den nya matsedelsfunktionen eftersom det inte råkar ligga något matsedel just nu under påsklovet. :)

Tack för synpunkten!
Vi arbetar med det vi får. Slutna plattformen har inte mindre än 4 olika sätt att hantera menyer:

Sharepoint-lista (vilket är alternativet du har ovan) har menyer för massor av veckor bakåt men endast fram till och med aktuell vecka. Vi kan inte få fram nästa veckas meny (tex på söndag kväll)
RSS - har får vi endast aktuell vecka. Har inte lyckats luska ut om man kan skicka in något smart till anropet för att får annan data. Slutna plattformen har ingen sådan funktion.
Google Calendar - tydligen används detta av vissa skolor. Inget vi stödjer då ingen utvecklare i teamet har en skola med denna funktionen
Iframe - man tar matsedeln från ett externt system. Här har vi ingen kontroll. Men en utvecklare i teamet har en skola med denna lösning så det kan kanske dyka upp

Vi skulle kunna implementera bläddring bakåt på alternativ 1 ovan.
Vi är lite låsta av staden här. Vill man ha mer funktioner får jag peka mot https://www.skolmaten.se/

Ah, det är ju just framåt man vill kunna bläddra när man ska planera veckan, men att kunna bläddra bakåt kan också vara trevligt. Många kök lägger kanske inte in menyn i förväg heller. Så alternativ 1 är det bästa i nuläget tycker jag det känns som.
Mina barns förskola har för övrigt inte anslutit sig till https://www.skolmaten.se/ Jag ska fråga om de kan göra det. Dock gillar jag inte att info om skolgång och dylikt delas upp i pyttebitar på olika privata lösningar och hoppas inte att ÖS gör sig beroende av sådana.

Jag var otydligt ser jag nu. Vi kan alltså inte välja alternativ. Vissa skolor kör alternativ  1, andra alternativ 2 osv. Det beror helt enkelt på barn.
Då staden inte kapslat in de olika alternativen bakom ett gemensamt api, måste alla klienter (dvs både Slutna Plattformen och vi) stödja alla 4 alternativen. Det är urbota dumt gjort.

Ah, jag förstår. Tråkigt.
Som sagt är inte alla förskolor och skolor anslutna till Skolmaten.se, och det kostar tydligen att ansluta sig.
Det bästa är kanske att låta det vara som det är och att eventuellt lägga till något i stil med "för att se andra veckors matsedlar hänvisar vi till Skolmaten.se" och/eller en förklaring, eller en länk till en förklaring, om varför det är tekniskt omöjligt att själva erbjuda detta. Tillägget är inte nödvändigt såklart men jag kan tänka mig att fler än jag kommer att fundera över varför de inte kan se andra matsedlar än den innevarande veckans.

authors: whyer zhouhana

repo: kolplattformen/skolplattformen


text:
Undesirable results for "flat" meshes

I've noticed that meshes which have "flat" regions have some issues with being highlighted correctly.
Here's a gist to illustrate the problem. The code there should be compatible with the latest master of bevy_mod_outline.
Here's a screenshot to give a rough idea of the problem:

The cyan shape is "flat" meaning it has infinitely sharp edges. The outlining technique used by bevy_mod_outline doesn't have any good choice of direction to move the outline vertices, so certain edges of the outline will get cut off depending on the angle of the camera relative to the mesh face.
I don't expect bevy_mod_outline to solve this problem completely because a flat mesh doesn't generally provide enough information to reliably infer how to construct the outline mesh. I believe getting a good outline for the flat shape would require adding extra vertices and elements to the outline mesh, and that's probably beyond the scope of what bevy_mod_outline can/should be doing.
However, I think this adjustment to bevy_mod_outline could allow users to fix these edge cases themselves while still taking advantage of bevy_mod_outline:

Add an optional component to the API struct OutlineMesh(Handle<Mesh>) which defines the mesh that gets used to draw the outline. If OutlineMesh isn't specified, then fall back to using the regular Handle<Mesh> component.
Add a Without<OutlineMesh> or some other filter to auto_generate_outline_normals to allow users to exclude specific entities from automatic normal generation.
Maybe some public utility functions to help generate custom OutlineMesh instances for edge cases.

Users can then customize the outline mesh however they need to for the effect that they want. For the flat mesh, extra vertices can be added at each corner with normal vectors that go out in all the necessary directions, and those new vertices can be connected together with new index elements. The rest of the pipeline, including the stenciling, can remain the same.
There are probably other edge cases that this adjustment would help to solve as well.
Does this sound like a desirable change to the crate? Since OutlineMesh would be an optional component, I believe the change could be made without breaking the API.

Thanks for bringing this up. This idea has occurred to me and I called the proposed component OutlineMesh in my head too. However, it's quite a blunt feature and I'm not sure that it's the best way to add value.
Firstly, I assume you're aware of ATTRIBUTE_OUTLINE_NORMAL. In the case of flat polygons like the one shown in your screenshot, it is possible to calculate outlining normals that would not result in the outline being partially occluded. Although, i) the library doesn't offer such a calculator at present and ii) as with any hard edges the line thickness becomes inconsistent to some degree. auto_generate_outline_normals assumes the object is closed and has sensible normals already.
So, as you say more or less, to improve the quality of outlining hard edges you need to add extra triangles connecting surfaces that face in different directions. These triangles would be degenerate in the original object, but expand to fill the gaps when rendering the outline. You can author these into a mesh today, but you will pay the (small?) cost of the degenerate triangles when rendering the original object.
I see OutlineMesh as on one hand a performance improvement to only include the degenerate triangles when outlining, but on the other hand a waste of memory to be duplicating the rest of the mesh. I'm interested in whether I could i) calculate the degenerate triangles needed from a mesh automatically and ii) how to efficiently store the mesh so that I can render it with or without them as needed.
My question to you is then, do you really feel the need to have outline and non-outline versions of each mesh?

I do imagine there could still be a use case for an OutlineMesh component if someone wants to artistically customize their outline in a way that would require them to have elements with non-zero area in the outline mesh. But my use case doesn't require that, so I suppose it's fair to kick that down the road until someone actually needs it.

I do imagine there could still be a use case for an OutlineMesh component if someone wants to artistically customize their outline in a way that would require them to have elements with non-zero area in the outline mesh. But my use case doesn't require that, so I suppose it's fair to kick that down the road until someone actually needs it.

I don't disagree. I guess my own intuition was that it was "bad hygiene" to duplicate the mesh just add some more triangles. However, maybe this may end up being the best solution. I was wondering is something like... having a separate index buffer for additional triangles which shared the main mesh's attribute buffer would be nicer.

I do still think there should be a unit component for blocking the auto outline normal generation for specific entities. I'd like to have that feature enabled for most meshes but not the ones where I'm specifically customizing the outline normal attribute.

You're using AutoGenerateOutlineNormalsPlugin? Really, I envisaged this as quick way to help people whose "outlines are broken" and that more advanced users would call generate_outline_normals specifically on the meshes that need it, or have outline normals saved in their asset files (see bevy_mod_gltf_patched and https://github.com/bevyengine/bevy/pull/5370).
The auto-generator plugin hooks AssetEvent to process Meshes so it can't do anything entity specific. One related idea that does occur to is that I could add ATTRIBUTE_OUTLINE_NORMAL_AUTO as a third option for outline normals with a precedence between the existing two. The auto-generator would create this attribute instead of ATTRIBUTE_OUTLINE_NORMAL so that custom outline normals would never be overridden or overwritten. Would that be helpful to you?

Ah good point about meshes not being owned by a single entity. That does make the component filtering approach ineffective. Having an ATTRIBUTE_OUTLINE_NORMAL_AUTO is an interesting idea.

You're using AutoGenerateOutlineNormalsPlugin?

In my application there are meshes being loaded from arbitrary sources, so I figured auto-processing all the normals would be a better idea than not. But I suppose it wouldn't be much work to remove that plugin and be more selective in my application logic about which meshes are getting processed.

I've created a new gist of the previous example but with a function that creates outline normals along the edges in the way we've discussed. I think the result is pretty nice, and the function I came up with is fairly general for closed-loop paths, so others can feel free to copy/paste it.
I'll close this issue since I think the changes I requested aren't necessary for the motivating problem.

FWIW, I've been leaning towards just adding OutlineMesh anyway.
@mxgrey I haven't had the time to properly examine your function yet, but it looks interesting. For future reference, is it licensed under the Apache/MIT arrangement suitable for inclusion into bevy_mod_outline?

Yes, please consider that gist to be licensed under Apache + MIT, and feel free to include it in bevy_mod_outline. I would open a PR myself but it's not clear to me how to make it ergonomic for general purpose use. For example, with some small tweaks the same function would also be suitable for producing an outline of an open line path rather than a closed loop path.

authors: komadori mxgrey


text:
feat(KONFLUX-3866): Scripts to create and prepare Stage users

Description
Scripts to create and prepare Stage users, adding them mostly for record as they will not be needed probably.
Issue ticket number and link
https://issues.redhat.com/browse/KONFLUX-3866
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Running manually from my laptop to get the users. I do not expect these scripts will be needed any time soon.

/lgtm

authors: jhutar kasemAlem


text:
chore(RHTAPWATCH-973): functional tests

Adds functional tests for the different endpoints in the workspace-manager webserver

/retest

looks good! One last thing, did you check that the tests you added fail the CI when one of them fails?

looks good! One last thing, did you check that the tests you added fail the CI when one of them fails?

Yes, when an entry fails, the test results are as follows:
Ran 7 of 7 Specs in 7.350 seconds
FAIL! -- 6 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestCmd (7.35s)
FAIL
coverage: 1.1% of statements
FAIL    github.com/konflux-ci/workspace-manager/cmd     7.379s
FAIL
make: *** [Makefile:65: test] Error 1

looks good! One last thing, did you check that the tests you added fail the CI when one of them fails?

Yes, when an entry fails, the test results are as follows:
Ran 7 of 7 Specs in 7.350 seconds
FAIL! -- 6 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestCmd (7.35s)
FAIL
coverage: 1.1% of statements
FAIL    github.com/konflux-ci/workspace-manager/cmd     7.379s
FAIL
make: *** [Makefile:65: test] Error 1

Is this in CLI or in CI on the repo?

looks good! One last thing, did you check that the tests you added fail the CI when one of them fails?

Yes, when an entry fails, the test results are as follows:
Ran 7 of 7 Specs in 7.350 seconds
FAIL! -- 6 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestCmd (7.35s)
FAIL
coverage: 1.1% of statements
FAIL    github.com/konflux-ci/workspace-manager/cmd     7.379s
FAIL
make: *** [Makefile:65: test] Error 1

Is this in CLI or in CI on the repo?

CLI, those tests are yet to fail in the PR (besides the first iteration of it, which did fail the CI).
are we expecting any unusual responses from go test or ginkgo ?

looks good! One last thing, did you check that the tests you added fail the CI when one of them fails?

Yes, when an entry fails, the test results are as follows:
Ran 7 of 7 Specs in 7.350 seconds
FAIL! -- 6 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestCmd (7.35s)
FAIL
coverage: 1.1% of statements
FAIL    github.com/konflux-ci/workspace-manager/cmd     7.379s
FAIL
make: *** [Makefile:65: test] Error 1

Is this in CLI or in CI on the repo?

CLI, those tests are yet to fail in the PR (besides the first iteration of it, which did fail the CI). are we expecting any unusual responses from go test or ginkgo ?

I just want to see that we're adding tests that can fail the CI in case of regressions. Can you try and push a broken test (e.g. change the value of an assertion) and confirm the CI is failing?

I see it's failing as expected. Let's fix it, and we can merge.

@yftacherzog Sure, confirmed

/retest

authors: Omeramsc yftacherzog

repo: konflux-ci/workspace-manager


text:
Huge updates and fixes.

Refactored a lot of stuff.

This is mostly targeted towards security and bug fixes.

repo: konishi-project/kagawasan


text:
Incompatibility with Xcode 10.2 (Swift 5)

Couldn't compile in Xcode 10.2 (Swift 5) due to version incompatibility
-> Related (Alamofire resolution): https://github.com/Alamofire/Alamofire/issues/2761

+1

+1

Should be fixed in the latest release.

authors: donpironet konkab lnfnunes sebastienkb

repo: konkab/AlamofireNetworkActivityLogger


text:
Fix: Update URL Redirect (docs.kubefirst.io)

What type of suggestions?
Missing Information
What page is concerned?
http://docs.kubefirst.io
What version of the docs?
ALL
What is the issue?
Update the URL http://docs.kubefirst.io to redirect to
to https://kubefirst.konstruct.io/docs/
Code of Conduct

[X] I agree to follow this project's Code of Conduct

John is working on it.

Will become a P0 once the new docs URL will have docs updates.

@johndietz I believe this has been updated when I go to the original URL it redirects to https://kubefirst.konstruct.io/docs/
Can you confirm this is good to close out or if there are other tasks remaining?

authors: fharper konstructcarrie

repo: konstructio/kubefirst-docs


text:
More YAML safe interpolation result

Fixes #1497

Maybe "more safe" but still not really "safe"...
stack: terom/test
version: 0.0.1
variables:
    password:
        type: string
        from:
            random_string:
                length: 32
                charset: ascii_printable

services:
    test:
        image: debian:jessie
        command: sh -c 'echo the password is $$PASSWORD'
        environment:
            PASSWORD: "foo-${password}-bar"

With some debug-dumping of the interpolated YAML:
stack: terom/test
version: 0.0.1
variables:
    password:
        type: string
        from:
            random_string:
                length: 32
                charset: ascii_printable

services:
    test:
        image: debian:jessie
        command: sh -c 'echo the password is $PASSWORD'
        environment:
            PASSWORD: "foo-"\"T=_eN/D0wWmt],%i#!b:!u]M]./P$;`"-bar"

and thus
RuntimeError: Error while parsing /home/kontena/kontena/examples/stacktest/kontena.yml (<unknown>): did not find expected key while parsing a block mapping at line 16 column 13
  /home/kontena/kontena/kontena/cli/lib/kontena/cli/stacks/yaml/reader.rb:107:in `rescue in load_yaml'
  /home/kontena/kontena/kontena/cli/lib/kontena/cli/stacks/yaml/reader.rb:101:in `load_yaml'
  /home/kontena/kontena/kontena/cli/lib/kontena/cli/stacks/yaml/reader.rb:66:in `execute'
  /home/kontena/kontena/kontena/cli/lib/kontena/cli/stacks/common.rb:33:in `stack_from_yaml'
  /home/kontena/kontena/kontena/cli/lib/kontena/cli/stacks/upgrade_command.rb:20:in `execute'
  /home/kontena/kontena/kontena/cli/lib/kontena/command.rb:187:in `run'
  /home/kontena/kontena/kontena/cli/vendor/bundle/ruby/2.3.0/gems/clamp-1.1.1/lib/clamp/subcommand/execution.rb:11:in `execute'
  /home/kontena/kontena/kontena/cli/lib/kontena/command.rb:187:in `run'
  /home/kontena/kontena/kontena/cli/vendor/bundle/ruby/2.3.0/gems/clamp-1.1.1/lib/clamp/subcommand/execution.rb:11:in `execute'
  /home/kontena/kontena/kontena/cli/lib/kontena/command.rb:187:in `run'
  /home/kontena/kontena/kontena/cli/vendor/bundle/ruby/2.3.0/gems/clamp-1.1.1/lib/clamp/command.rb:132:in `run'
  bin/kontena:16:in `<top (required)>'

Making it truly safe will not be possible/reasonable with this approach anyway.
Perhaps the interpolation should happen in the resulting hash after the yaml has been parsed.

Reimplemented in #1528

authors: SpComb kke

repo: kontena/kontena


text:
Backend: ServiceNow failure exporter

Treat this issue as a Master issue that will track child issues.

Closing as a cleanup.
This was supposed to be used by the query on the following page, however we switched to use GitHub labels instead of the master issue:
https://github.com/konveyor/pelorus/blob/master/docs/UpstreamSupport.md

authors: mpryc weshayutin

repo: konveyor/pelorus


text:
:ghost: Remove shared app filter and unused menuActions

Removes some old code I noticed after the dropdown update & analysis table PRs were merged
Menu actions are no longer used in the page header component and have been moved to the toolbar
Removes old shared app filter hook that is no longer in use

i noticed menuActions was only given empty arrays as well (had to put some fake data in to test it locally), but left it in assuming that there may be a need for it coming up. if not, lgtm.

Appreciate it!


text:
kp的问题

kp开启以后  哔哩哔哩app的文章区的评论打不开  已安装证书  也自定义了@@@@||https://bilibili.com

这里不接受KP的反馈，请到KP界面的反馈通道反馈！谢谢合作！

repo: koolshare/ledesoft