text:
ziti agent should look for systemd ziti service unix domain sockets in well known locations

ziti controllers and routers running under systemd don't have access to /tmp, but can put their unix domain socket files under /var/lib/ziti-controller and /var/lib/ziti-router. We should check for those locations as well as scanning /tmp.

The Linux deployments will use these file paths after this issue is resolved:

/var/lib/ziti-controller/agent.sock
/var/lib/ziti-router/agent.sock

what happens when you run more than one controller or more than one router? this worries me a bit.

what happens when you run more than one controller or more than one router? this worries me a bit.

The ziti agent command has options for disambiguating the target socket when both controller and router are running concurrently. It's not currently possible to run two controllers or two routers with the Linux deployments.

Why agent.sock? Typically a unix domain socket is named for the service offering it, not the client consuming it...

Why agent.sock? Typically a unix domain socket is named for the service offering it, not the client consuming it...

The current name for controller and router socket files is like gops-agent.1110840.sock, and there's no good reason for me to pick agent.sock. Is /var/lib/ziti-controller/ziti-controller.sock superior?
My mention of new socket file names for Linux deployments is about this linked issue. The issue here about looking in additional locations for sockets would enable Linux deployments' sockets to be discoverable by a ziti agent command that is run as root, eliminating the extra steps to locate the socket.

I would think either retaining the gops portion of that name (gops-agent.sock), or naming the socket after the component, as in controller.sock or router.sock would make more sense. If you named them controller.sock and router.sock, you could keep then in a /var/run folder, which seems more appropriate to me than /var/lib.

/var/lib/ziti-controller/controller.sock or /var/lib/ziti-controller/gops-agent.sock are equally fine. I'll use /var/lib/ziti-controller/gops-agent.sock in the absence of further feedback. All that's required is that this issue changes ziti agent to include the new socket file paths in the set of well-known paths when running on Linux.
The linked issue about changing the path and filename for the Linux deployments uses the existing state directories under /var/lib assigned by systemd to the service unit, e.g., /var/lib/ziti-controller/. Using those state directories avoids the need to mount an additional packager-defined directory in the controller or router's filesystem namespace where the restricted PID has filesystem write permissions. /var/run, which is a symlink to a tmpfs filesystem mounted on /run on my system, is read-only inside the service unit's filesystem sandbox so it would not be practical for the service to create a socket file there.

authors: dovholuknf michaelquigley plorenz qrkourier

repo: openziti/ziti


text:
Too long Changelog for zone.

Hi, your work is realy great thank you.
We have zone for monitoring and using DNSUI api for make changes in it.
So, we have already more than 30000 changes and web is very slow because of that.
Can we limit the number of showing changes if we whant to see only records or can we separate changelog to diffenet scope?

We're starting to hit those limitations as well, so I'm trying to find a way to filter (or better, search in) changelogs.
I had a look in the table schemas. The changeset table stores a record for each changelog entry; each
changelog is then made up of one or more rows from the change table. However, the juicy details are stored there as serialized PHP objects, so they can't be searched through.
The (useful) information available in changeset is just author_id, change_date and comment. This leaves us with the following options:

paginate results
search through comment
limit to date range
filter by author (least useful, IMO)

I'd like to implement one or more of the above; @thomas-pike, what would be your preference here?

I think that primarily, to solve the problem of page load becoming slow, the most important thing is to implement pagination. Search and date range options definitely would be nice to have though. Any contributions you are able to make will be gratefully accepted.
Apologies for the use of serialized PHP objects, that could definitely have been done better.

Here's the pull request: https://github.com/operasoftware/dns-ui/pull/190

source: gharchive/issue

authors: sipopo thomas-pike uedvt359

repo: operasoftware/dns-ui

license_type: permissive

license_source: bigquery


text:
CRD Compatibility Check Fix

Description of the change:
Updates the validation code for CRD updates to validate all CRs present on the cluster against the schema of each served version in the new CRD.
Motivation for the change:
Previously this code checked only the newCRD.Spec.Validation field for new schema, which when using the apiextensions.k8s.io/v1 API should not be used.
Testing remarks:
We did not have any tests using apiextensions.k8s.io/v1 CRDs previously, which is likely how this became an oversight; I've added a small suite of tests to check functionality using the up-to-date CRD API.
Closes #3032

@ncdc Updated per your comments, thanks for reviewing! Let me know if you see anything else.

I don't think there is anything we can really do. This is "best effort".

@ncdc @joelanford Thank you both again for looking through this, I think I've managed to take care of all the special v1beta1 crd cases but I would appreciate another look.
Meanwhile the flaky-e2e-tests are failing which I cannot reproduce locally. I'm looking into that but I don't think it's necessarily a cause for concern (same failures as a different PR run here)

Re: race condition of new unvalidated CR sneaking in

I don't think there is anything we can really do. This is "best effort".

The only thing I could imagine would be for us to run a validating webhook for all CRDs managed by OLM where we temporarily reject CR creation during the critical section.

/lgtm
/approve

/lgtm

/approve

source: gharchive/pull-request

authors: dtfranz joelanford ncdc tmshort


text:
docs: add access control workflow

I keep fielding questions about how the access control works for admins and end users, so I figured a doc can answer these questions for all.

Thanks @robszumski, this is great!

authors: ecordell robszumski


text:
charts/openshift-metering: Fix sum fields on pod-usage-memory-bytes

The label_replace was moved to the outside of the sum, so the sum needs
to be on pod_name, not pod.

/retest

repo: operator-framework/operator-metering

license_source: github-api


text:
Dependabot alerts on GHA

Type of question

General operator-related help

Question
What did you do?
In my project: https://github.com/lsst/qserv-operator:

I use latest version of operator-sdk (1.15.0)
I have enabled GHA's "Dependabot alerts"

What did you expect to see?
I do not want to have "Dependabot alerts"
What did you see instead? Under which circumstances?
I have two "Dependabot alerts" related to  dependencies provided by "operator-sdk":
https://github.com/lsst/qserv-operator/security/dependabot
Environment
Operator type:

/language go

Kubernetes cluster type:
kind
$ operator-sdk version
operator-sdk version: "v1.15.0", commit: "f6326e832a8a5e5453d0ad25e86714a0de2c0fc8", kubernetes version: "1.21", go version: "go1.16.10", GOOS: "linux", GOARCH: "amd64"

$ go version (if language is Go)
go version go1.16.3 linux/amd64

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T18:03:20Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-21T23:01:33Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/amd64"}

Additional context

I forked so i could see the dependabot warnings.

Hi @fjammes, I just made a fresh repo with a new operator SDK project, and am not seeing any dependabot alerts. The versions locked in the go.sum files match. Can we get confirmation that you are still seeing these alerts?

Thanks @ryantking , yes I am still seeing the two alerts. Could you please provide me your go.sum? Here is two extract of mine:
$ cat go.sum| grep jwt-go
github.com/dgrijalva/jwt-go v3.2.0+incompatible/go.mod h1:E3ru+11k8xSBh+hMPgOLZmtrrCbhqsmaPHjLKYnJCaQ=
github.com/form3tech-oss/jwt-go v3.2.2+incompatible/go.mod h1:pbq4aXjuKjdthFRnoDwaVPLA+WlJuPGy+QneDUgJi2k=
github.com/form3tech-oss/jwt-go v3.2.3+incompatible h1:7ZaBxOI7TMoYBfyA3cQHErNNyAWIKUMIwqxEtgHOs5c=
github.com/form3tech-oss/jwt-go v3.2.3+incompatible/go.mod h1:pbq4aXjuKjdthFRnoDwaVPLA+WlJuPGy+QneDUgJi2k=

$ cat go.sum| grep miekg
github.com/miekg/dns v1.0.14/go.mod h1:W1PPwlIAgtquWBMBEV9nkV9Cazfe8ScdGz/Lj7v3Nrg=

The vulnerabilities are on github.com/miekg/dns <= 1.1.25 and dgrijalva/jwt-go <= 3.2.0

@fjammes here are the same commands you executed:
$ cat go.sum| grep jwt-go
github.com/dgrijalva/jwt-go v3.2.0+incompatible/go.mod h1:E3ru+11k8xSBh+hMPgOLZmtrrCbhqsmaPHjLKYnJCaQ=
github.com/form3tech-oss/jwt-go v3.2.2+incompatible/go.mod h1:pbq4aXjuKjdthFRnoDwaVPLA+WlJuPGy+QneDUgJi2k=
github.com/form3tech-oss/jwt-go v3.2.3+incompatible h1:7ZaBxOI7TMoYBfyA3cQHErNNyAWIKUMIwqxEtgHOs5c=
github.com/form3tech-oss/jwt-go v3.2.3+incompatible/go.mod h1:pbq4aXjuKjdthFRnoDwaVPLA+WlJuPGy+QneDUgJi2k=

$ cat go.sum| grep miekg
github.com/miekg/dns v1.0.14/go.mod h1:W1PPwlIAgtquWBMBEV9nkV9Cazfe8ScdGz/Lj7v3Nrg=

The versions look the same to me.
Here is my test repo

@ryantking thanks so much! On my side the Dependabot alert have disappeared from Github webpage of my project for an unknown reason... So I will close this one.

@fjammes Great! Feel free to reopen if something else crops up.

authors: asmacdo fjammes ryantking

repo: operator-framework/operator-sdk


text:
Clarify the meaning of the pre-alpha status

Someone on the Kubernetes slack channel asked to clarify on what pre-alpha status means and if this means the operator it creates is not ready for production. I think we can add a note somewhere to clarify that the operator it generates is ready for production.

Closing as we moved over from pre-alpha.


text:
Automate the build and testing workflows

Introduce github actions for the building and testing workflows.

#14 added a skeleton for ensuring we don't miss a regression when reviewing code (but not checking out locally).
In the future, we'll likely want to add additional actions. Immediate ones that come to mind:

e2e testing
building the provisioner Dockerfile and running tests against that container image

Assigning @tylerslaton to this issue.

repo: operator-framework/rukpak


text:
Intrusion detection schedules

Under system - intrusion detection -administration - schedule, even if schedule already exists GUI is always opening ADD new schedule window, it is not possible to edit or delete already configured schedules under schedules tab. (version 18.1.4)

The schedule tab is only intended for editing the IDS schedule. Go to System: Settings: Cron to edit the others.
Furthermore, it's not possible to delete the IDS schedule because it is linked to the subsystem, but it can be deactivated just fine.

I have IDS rules update scheduled...i can access/edit this via system - cron but not via IDS - schedules...also I cant disable it..every time i click on Schedules add new widnow pops up. Maybe this it how it should work, but its a little confusing..I have no problem to edit it via cron..just want to check if the behavior is correct.

It's disabled by unchecking "enabled" on top + save

authors: dimitrijp fichtner

repo: opnsense/core


text:
new Alias no working anymore

Describe the bug
Not able to create a new working alias - old ones are working good
19.1.6
NOT UPDATED/NOT REBOOTED because feeling curious if currently working alias also begin to fail. - Possible to debug a little more first?
First thought it is related to alias on floating rules. But is not limited to that. Don't think so but mention the old issue where I also had problems: #3321
To Reproduce
Steps to reproduce the behavior:

Go to Firewall/Alias
Create a new alias, type host(s) with name  h_t_itops_repo (had a longer before), IP xx.xx.xx.12
(tried that to with an Alias type network and xx.xx.xx.12/32)
(A) Used the alias on Floating Rule (incoming to ip)

PASS
IPv4
TCP
Source Any
Destination: ALIAS h_t_itops_repo
Destination Port: HTTP HTTPS

(B) Used the alias on Interface (outgoing from ip)

PASS
IPv4
TCP/IP
Source: ALIAS h_t_itops_repo
Destination: any
Destination Port: HTTP HTTPS

Expected behavior
Traffic should be passed in both rules, but isn't. As soon as i change the rules to use the ip instead of the alias, traffic is passed through.
Screenshots
Floating rule
not working

Working

Interface rule
not Working

Working

Relevant log files
not working
pass inet proto tcp from {any} to $h_t_itops_repo port $pg_HTTP_HTTPS keep state label "USER_RULE: 1122REPORULE" # f53a6faaf0b327cddd53ad2d684ef22a
pass in quick on vmx2_vlan602 inet proto {tcp udp} from $h_t_itops_repo to {any} port $pg_HTTP_HTTPS keep state label "USER_RULE: 1122REPORULE" # 7b7e21c152105d90c470d54457d64c9c

working
 grep 1122 /tmp/rules.debug
pass inet proto tcp from {any} to {10.40.2.58} port $pg_HTTP_HTTPS keep state label "USER_RULE: 1122REPORULE" # c9eb0325669251250be0c4031f1ae357
pass in quick on vmx2_vlan602 inet proto {tcp udp} from {10.40.2.58} to {any} port $pg_HTTP_HTTPS keep state label "USER_RULE: 1122REPORULE" # cff36fecc774b83a007504ee24fb9707

Additional context
Add any other context about the problem here.
Environment
(2x) VMWARE Virtual Guest in HA
OPNsense 19.1.6-amd64
FreeBSD 11.2-RELEASE-p9-HBSD
OpenSSL 1.0.2r 26 Feb 2019

just found something - Firewall Diagnostics pfTables
the entry for h_t_itops_repo is empty

did you hit apply (in the alias form)? if not, please inspect the logs for anything out of the ordinary.

yes

just created an additional one and hit apply - but no usage in a rule, only to test adding an Alias - same problem: emtpy in pfTables

(same on primary and secondary)

There was a relevant alias fix in 19.1.7.

sure? - thought I looked over the release notes? - let me try

https://github.com/opnsense/core/commit/ea2f217cf3213cc12a94155d3b5a5d5f9ea8bc43 in which case this would be a duplicate of https://github.com/opnsense/core/issues/3399

ok.. updated slave to 19.1.7 and pftable shows now the entry correctly. And sure the rules are working.
I'm sorry that I overlooked that fix. Is there any way to donate you both a 🍺 ?

No worries, all good. Thanks for the quick feedback :)

would love to

authors: AdSchellevis fichtner katamadone


text:
OPNsense 19.7.5: Not able to add value to alias

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I'm convinced that mine is new.
Describe the bug
When I try to create an new alias or add e.g. a new port to an existing alias, the mask only suggest existing host aliases. Manuell input results in deleting the input.
To Reproduce
Steps to reproduce the behavior:

Go to 'Firewall:Alias'
Click on 'New alias' or edit an existing alias
Try to input a value in the content field
Value disappears as soon as you hit enter or choose another field

Expected behavior
Value should stay in the field
Relevant log files
I have not found any related log files.
Additional context
Reverted to 19.7.4_1.
In this version I get also only suggestions for existing host aliases even when I create an port alias. But the manuell input works.
Environment
OPNsense 19.7.5 amd64
Intel(R) Celeron(R) CPU J1900 @ 1.99GHz (4 cores)
OnBoard Realtek
2 x Realtek GbE OnBoard LAN chips (10/100/1000 Mbit)

Duplicate of #3760

@mimugmail Thank you. Patch works also for me.


text:
monit: change mail format field for alerts to textbox

Change the Mail Format field for Alerts to textbox to configure it multi-line.
The problem came up with opnsense/plugins#820

yup :grinning:

Merged, thanks!

authors: fbrendel fichtner


text:
security/acme-client: Add MailinaBox to Let's Encrypt Service Plugin

Hello OPNsense developers,
Here is my fist wack at submitting a change to your project. Understand I'm new to this project and may have broken with your submission conventions. If I have please let me know, and I'll quickly set things right.
These changes to AcmeClient.xml are primarily to add support for DNS-01 authentication using MailinaBox's Custom DNS http interface. Also added another change to support debug logging from DNSAPI scripts.
There are four file changes to Let's Encrypt plugin:

certhelper.php in scripts
AcmeClient.xml in model
dialogValidation.xml in controller forms
settings.xml in controllers forms

Please let me know if I'm on the right track or have missed something important. Can report the changes work on my current test system and I'm able to issue certificates using MailintheBox as the target for DNS-01 validation.
Adding dns_miab.sh DNS API as a pull under that repository.

Frank.
Saying this here as it may be buried in the code comments.
There is probably a better way to do the debug level change. That is have a separate selection come if debug is selected and then set the debug level from there. Seems that the debug levels are somewhat open ended. Looks like a level 3 is also possible. Playing with debugging I saw that the dnsapi scripts _debug lines only show up at --debug 2. However you can declare a _debug2 in dnsapi scripts. Think those debug lines won't be logged unless you select --debug 3. I'll give it a test and post back.

Frank,
Looks like I got put back right. The number of files changed is now three and settings.xml doesn't show up in the diff.
Sorry about that. Should be using this from the cli and not the web interface.

@billgertz LGTM now. Thanks for your contribution!
I'll wait for the merge until the required changes are available in an acme.sh release.

Frank - thanks got one last bug in the dns_miab.sh I'm working on. To the debug level PR which way should we go as I originally proposed (integrated) or selecting debug brings up a new option to select level. Since acme.sh takes --debug and --debufg 2, I would suggest the integrated approach.

@fraenki
Neil Pang just merged the MailinaBox DNS-01 API script to acme.sh. Should show up with next release. See: https://github.com/Neilpang/acme.sh/pull/2534

@fraenki
Looks like Neil Pang just merged dns_miab.sh to current version. Should be available when updating or new install of acme.sh.

@billgertz Thanks, we're almost there. :) We'll just have to wait for the next official release of amce.sh.

@billgertz There's still no official acme.sh release available, but I've merged it anyway. Thanks for your contribution!
(This means that it's not working out of the box right now, but the missing acme.sh dnsapi file can still be copied manually.)

Frank,
Thanks! You already probably know running:
acme.sh --upgrade
would also install the newer DNSAPI scripts, including dns-miab.sh
Regards,
Bill
On Thu, Dec 26, 2019, 15:06 Frank Wall notifications@github.com wrote:

@billgertz https://github.com/billgertz There's still no official
acme.sh release available, but I've merged it anyway. Thanks for your
contribution!
(This means that it's not working out of the box right now, but the
missing acme.sh dnsapi file can still be copied manually.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/opnsense/plugins/pull/1531?email_source=notifications&email_token=AA3SEQIB7PEGJ7SFTGFF3HDQ2UTHNA5CNFSM4I5U63U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHWGMOA#issuecomment-569140792,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA3SEQNBIKOFIUFW56HGTHTQ2UTHNANCNFSM4I5U63UQ
.

authors: billgertz fraenki

repo: opnsense/plugins


text:
Exporter suddenly fails to show any metrics.

Ok, I've got myself an X Files case here.
Our druid-exporter suddenly died yesterday around 20:00 (CET).
This are the logs:
Jan 21 18:55:31 druid-exporter-1 druid-prometheus-exporter[2114]: time="2021-01-21T18:55:31Z" level=info msg="Successfully collected data from druid emitter, druid/historical"
Jan 21 18:56:12 druid-exporter-1 systemd[1]: druid-prometheus-exporter.service: Main process exited, code=killed, status=9/KILL
Jan 21 18:56:12 druid-exporter-1 systemd[1]: druid-prometheus-exporter.service: Failed with result 'signal'.
Jan 21 18:56:12 druid-exporter-1 systemd[1]: druid-prometheus-exporter.service: Service RestartSec=100ms expired, scheduling restart.
Jan 21 18:56:12 druid-exporter-1 systemd[1]: druid-prometheus-exporter.service: Scheduled restart job, restart counter is at 1.
Jan 21 18:56:12 druid-exporter-1 systemd[1]: Stopped Apache Druid Prometheus Exporter..
Jan 21 18:56:12 druid-exporter-1 systemd[1]: Started Apache Druid Prometheus Exporter..
Jan 21 18:56:13 druid-exporter-1 druid-prometheus-exporter[11122]: time="2021-01-21T18:56:13Z" level=info msg="Druid exporter started listening on: 8080"
Jan 21 18:56:13 druid-exporter-1 druid-prometheus-exporter[11122]: time="2021-01-21T18:56:13Z" level=info msg="Metrics endpoint - http://0.0.0.0:8080/metrics"
Jan 21 18:56:13 druid-exporter-1 druid-prometheus-exporter[11122]: time="2021-01-21T18:56:13Z" level=info msg="Druid emitter endpoint - http://0.0.0.0:8080/druid"

Since then, we've got 0 metrics. Tried reinstalling, rebooting the instance, restarting the router, broker, overlord, coordinator... 0 metrics.
Logs are empty, besides the typical "starting 8080, endpoint X, endpoint Y"
A tcpdump shows that the instance is receiving metrics from druid.
curl-ing the metrics in druid-exporter returns metrics, but takes ages, just now I timed it:
$ time curl localhost:8080/metrics
[...]
real	1m38.608s
user	0m0.007s
sys	0m0.011s

Any idea what might have happened?

As additional data: druid-exporter host is near 0% CPU usage and 0% RAM usage all the time, monitored with prometheus and htop while querying /metrics and it's a dedicated host so that's not the issue either :(

As additional data: druid-exporter host is near 0% CPU usage and 0% RAM usage all the time, monitored with prometheus and htop while querying /metrics and it's a dedicated host so that's not the issue either :(

Downloaded v0.8 of the exporter, the issue stops happening. Looks like there is something with v0.9

Downloaded v0.8 of the exporter, the issue stops happening. Looks like there is something with v0.9

Ignore this issue. Apparently the host invoked the oom-killer, druid-exporter was the target and for reasons I cannot see the service we created (that just runs druid-exporter) is not working. Doesn't matter which version run. If I run the exporter myself (or with any other user) it works. Time to investigate this on my own. Sorry for bothering you! :)

Ignore this issue. Apparently the host invoked the oom-killer, druid-exporter was the target and for reasons I cannot see the service we created (that just runs druid-exporter) is not working. Doesn't matter which version run. If I run the exporter myself (or with any other user) it works. Time to investigate this on my own. Sorry for bothering you! :)

Sorry for all the back and forth. Apparently yes, it only happens in v0.9 released. v0.9-beta works OK

Sorry for all the back and forth. Apparently yes, it only happens in v0.9 released. v0.9-beta works OK

I'll check this over the weekend

I'll check this over the weekend

Fixed in https://github.com/opstree/druid-exporter/pull/89

Fixed in v0.9 release https://github.com/opstree/druid-exporter/releases/tag/v0.9

The release one was the affected by this issue. How is it fixed on that one? 🤔

authors: iamabhishek-dubey tanisdlj

repo: opstree/druid-exporter


text:
How do I get a styled select for my custom menu item type

Hi there, thanks a lot for this nice package!
I only don't know how to make this here become a regular select dropdown:

And I'm not sure what I'm expected to add here (maybe the two things are connected??):

Thanks again! Sebastian

P.S. here's my complete class:

<?php

namespace Kraenkvisuell\NovaCms\MenuItemTypes;

use Kraenkvisuell\NovaCms\Models\Page;
use OptimistDigital\MenuBuilder\MenuItemTypes\BaseMenuItemType;

class PageMenuItemType extends BaseMenuItemType
{
    public static function getIdentifier(): string
    {
        return 'page';
    }

    public static function getName(): string
    {
        return 'Seite';
    }

    public static function getType(): string
    {
        return 'select';
    }

    /public static function getOptions($locale): array
    {
        if (class_exists('\Kraenkvisuell\NovaCms\Models\Page')) {
            $list = [];
            Page::all()
                ->each(function ($page) use (&$list) {
                    $list[$page->id] = $page->title;
                });

            return $list;
        }

        return [];
    }

    public static function getDisplayValue($value = null, array $parameters = null, array $data = null)
    {
        return Page::find($value)->title;
    }

    public static function getValue($value = null, array $parameters = null)
    {
        return Page::find($value);
    }

    public static function getFields(): array
    {
        return [];
    }

    public static function getRules(): array
    {
        return [];
    }

    public static function getData($data = null, array $parameters = null)
    {
        return $data;
    }
}

Same Problem

Hi! Fixed in version 4.0.3. Good luck!

authors: Tarpsvo manogi mohamad-shawa

repo: optimistdigital/nova-menu-builder

license: MIT


text:
Composer install fails on Nova 3.4.x

I might be doing something wrong but on Laravel Nova 3.4.1 when I try to install it I get:
optimistdigital/nova-sortable 1.4.7 requires laravel/nova ^2.0.11 || ^3.0 -> no matching package found.

Are you sure you have laravel/nova in your dependencies?

authors: Tarpsvo eugenevdm

repo: optimistdigital/nova-sortable


text:
WMS ID: 11273 - Updated docs

WMS ID: 11273 - Updated docs

Retrieving these changes and submitting these updates with another PR.

repo: oracle-livelabs/oci


text:
Fix: ssh_to_operator output use long form

This commit Updates the terraform output for ssh_to_operator so that you can use a private key that is anywhere on the filesystem.  Currently the short form (-J) does not allow you to pass any arguments like -i, therefore if your ssh key is not in a default location that openssh knows about it will fail to connect.
More info in this issue: https://github.com/oracle-terraform-modules/terraform-oci-oke/issues/246

Thanks for sending the PR. Can you please sign the OCA? We'll then merge

A space is needed after the ssh command

I left that how it was before I touched the code, it seems to output with a space so I assume local.ssh_key_arg has a space prefixed to it?
Either way it shouldn't effect the command if it has an extra space or not, let me know if you want me to add it and I can.

Can we get this merged in?

Resolves #246

authors: cwiggs devoncrouse hyder


text:
all packages reinstall with -r on centos 7 has condition error

migrating from centos 7 I have an issue with -r option, there is an error with validating condition in centos2ol.sh line 564.
List of packages looks ok, I thing problematic is second condition, which is checking count_elems > 0 is wrong, so changed it like this:
-    if [[ -n "${list_of_centos_rpms[*]}" ]] && [[ "${list_of_centos_rpms[*]}" -ne 0 ]]; then
+    if [[ -n "${list_of_centos_rpms[*]}" ]] && [[ "${#list_of_centos_rpms[@]}" -ne 0 ]]; then

so from "${list_of_centos_rpms[*]}" which i one arg list of values, to "${#list_of_centos_rpms[@]}" which is count of them
and it works as expectd :)

Simple enough fix, but I assume they need a pull request and a signed OCA...

authors: ChristianGfK trezqers


text:
Can't install package httpd on Oracle Linux based Docker image

Here's the image I'm trying to build:
FROM oraclelinux:latest
RUN yes | yum install httpd
EXPOSE 80 443
CMD ["bash"]

Here's the error message I get:
    Error unpacking rpm package httpd-2.4.6-40.0.1.el7.x86_64

Tried with different OL 7.x versions. All failed.
Tried with OL 6 (latest). It worked.
I've found some related issues:

https://github.com/docker/hub-feedback/issues/461
https://github.com/aptible/support/issues/187
https://github.com/docker/docker/issues/6980
https://github.com/boot2docker/boot2docker-cli/issues/326

I can't reproduce this issue:
[amiller@sirius ~]$ docker info
Containers: 1
Images: 740
Storage Driver: btrfs
 Build Version: Btrfs v3.16.2
 Library Version: 101
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.8.13-98.4.1.el7uek.x86_64
Operating System: Oracle Linux Server 7.2
CPUs: 8
Total Memory: 31.14 GiB
Name: sirius.lot209.com
ID: 4NBZ:IPAL:OKWW:P4WD:H7VT:SJGT:KQL4:H4X2:EVSR:6W6D:ATKS:M6BC
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

amiller@sirius ~]$ docker version
Client:
 Version:      1.8.3
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   f0bb124
 Built:        Wed Oct 14 04:38:36 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.3
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   f0bb124
 Built:        Wed Oct 14 04:38:36 UTC 2015
 OS/Arch:      linux/amd64

Dockerfile:
$ cat Dockerfile
FROM oraclelinux:latest
RUN yum -y install httpd mod_ssl
EXPOSE 80 443
CMD ["/bin/bash"]

$ docker build .
Sending build context to Docker daemon 2.048 kB
Step 0 : FROM oraclelinux:latest
 ---> a8fd27de55f5
Step 1 : RUN yum -y install httpd mod_ssl
 ---> Running in 585b8772c34a
Resolving Dependencies
--> Running transaction check
---> Package httpd.x86_64 0:2.4.6-40.0.1.el7 will be installed
--> Processing Dependency: httpd-tools = 2.4.6-40.0.1.el7 for package: httpd-2.4.6-40.0.1.el7.x86_64
--> Processing Dependency: /etc/mime.types for package: httpd-2.4.6-40.0.1.el7.x86_64
--> Processing Dependency: libaprutil-1.so.0()(64bit) for package: httpd-2.4.6-40.0.1.el7.x86_64
--> Processing Dependency: libapr-1.so.0()(64bit) for package: httpd-2.4.6-40.0.1.el7.x86_64
---> Package mod_ssl.x86_64 1:2.4.6-40.0.1.el7 will be installed
--> Processing Dependency: openssl for package: 1:mod_ssl-2.4.6-40.0.1.el7.x86_64
--> Running transaction check
---> Package apr.x86_64 0:1.4.8-3.el7 will be installed
---> Package apr-util.x86_64 0:1.5.2-6.0.1.el7 will be installed
---> Package httpd-tools.x86_64 0:2.4.6-40.0.1.el7 will be installed
---> Package mailcap.noarch 0:2.1.41-2.el7 will be installed
---> Package openssl.x86_64 1:1.0.1e-51.el7_2.1 will be installed
--> Processing Dependency: openssl-libs(x86-64) = 1:1.0.1e-51.el7_2.1 for package: 1:openssl-1.0.1e-51.el7_2.1.x86_64
--> Processing Dependency: make for package: 1:openssl-1.0.1e-51.el7_2.1.x86_64
--> Running transaction check
---> Package make.x86_64 1:3.82-21.el7 will be installed
---> Package openssl-libs.x86_64 1:1.0.1e-42.el7_1.9 will be updated
---> Package openssl-libs.x86_64 1:1.0.1e-51.el7_2.1 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package           Arch        Version                    Repository       Size
================================================================================
Installing:
 httpd             x86_64      2.4.6-40.0.1.el7           ol7_latest      1.2 M
 mod_ssl           x86_64      1:2.4.6-40.0.1.el7         ol7_latest      103 k
Installing for dependencies:
 apr               x86_64      1.4.8-3.el7                ol7_latest       99 k
 apr-util          x86_64      1.5.2-6.0.1.el7            ol7_latest       91 k
 httpd-tools       x86_64      2.4.6-40.0.1.el7           ol7_latest       81 k
 mailcap           noarch      2.1.41-2.el7               ol7_latest       30 k
 make              x86_64      1:3.82-21.el7              ol7_latest      419 k
 openssl           x86_64      1:1.0.1e-51.el7_2.1        ol7_latest      710 k
Updating for dependencies:
 openssl-libs      x86_64      1:1.0.1e-51.el7_2.1        ol7_latest      949 k

Transaction Summary
================================================================================
Install  2 Packages (+6 Dependent packages)
Upgrade             ( 1 Dependent package)

Total download size: 3.6 M
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
--------------------------------------------------------------------------------
Total                                              513 kB/s | 3.6 MB  00:07
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Updating   : 1:openssl-libs-1.0.1e-51.el7_2.1.x86_64                     1/10
  Installing : apr-1.4.8-3.el7.x86_64                                      2/10
  Installing : apr-util-1.5.2-6.0.1.el7.x86_64                             3/10
  Installing : httpd-tools-2.4.6-40.0.1.el7.x86_64                         4/10
  Installing : 1:make-3.82-21.el7.x86_64                                   5/10
  Installing : 1:openssl-1.0.1e-51.el7_2.1.x86_64                          6/10
  Installing : mailcap-2.1.41-2.el7.noarch                                 7/10
  Installing : httpd-2.4.6-40.0.1.el7.x86_64                               8/10
  Installing : 1:mod_ssl-2.4.6-40.0.1.el7.x86_64                           9/10
  Cleanup    : 1:openssl-libs-1.0.1e-42.el7_1.9.x86_64                    10/10
  Verifying  : apr-1.4.8-3.el7.x86_64                                      1/10
  Verifying  : mailcap-2.1.41-2.el7.noarch                                 2/10
  Verifying  : 1:openssl-libs-1.0.1e-51.el7_2.1.x86_64                     3/10
  Verifying  : 1:make-3.82-21.el7.x86_64                                   4/10
  Verifying  : 1:mod_ssl-2.4.6-40.0.1.el7.x86_64                           5/10
  Verifying  : 1:openssl-1.0.1e-51.el7_2.1.x86_64                          6/10
  Verifying  : apr-util-1.5.2-6.0.1.el7.x86_64                             7/10
  Verifying  : httpd-2.4.6-40.0.1.el7.x86_64                               8/10
  Verifying  : httpd-tools-2.4.6-40.0.1.el7.x86_64                         9/10
  Verifying  : 1:openssl-libs-1.0.1e-42.el7_1.9.x86_64                    10/10

Installed:
  httpd.x86_64 0:2.4.6-40.0.1.el7       mod_ssl.x86_64 1:2.4.6-40.0.1.el7

Dependency Installed:
  apr.x86_64 0:1.4.8-3.el7                 apr-util.x86_64 0:1.5.2-6.0.1.el7
  httpd-tools.x86_64 0:2.4.6-40.0.1.el7    mailcap.noarch 0:2.1.41-2.el7
  make.x86_64 1:3.82-21.el7                openssl.x86_64 1:1.0.1e-51.el7_2.1

Dependency Updated:
  openssl-libs.x86_64 1:1.0.1e-51.el7_2.1

Complete!
 ---> 2ed4741d3db4
Removing intermediate container 585b8772c34a
Step 2 : EXPOSE 80 443
 ---> Running in 9bd571126743
 ---> efac406aea3a
Removing intermediate container 9bd571126743
Step 3 : CMD /bin/bash
 ---> Running in de64425ab099
 ---> 6c68575a4076
Removing intermediate container de64425ab099
Successfully built 6c68575a4076

Note that I'm using the correct yum command (yum -y install) and I've added mod_ssl for SSL (port 443) support.

All the related issues seem to be when you're using aufs which is not supported on Oracle Linux at all.

Can you check Docker 1.9?

We haven't released Docker 1.9 for Oracle Linux yet, as it requires our as-yet-unreleased UEK4 (4.1.12) kernel. However, I tested it with an internal build of Docker 1.9.1 and kernel-uek-4.1.12 and it works fine.

Runtime info for Docker 1.9 and UEK4:
$ docker info
Containers: 1
Images: 194
Server Version: 1.9.1
Storage Driver: btrfs
 Build Version: Btrfs v3.19.1
 Library Version: 101
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.12-31.el7uek.x86_64
Operating System: Oracle Linux Server 7.2
CPUs: 4
Total Memory: 7.544 GiB
Name: ol7dev.lot209.com
ID: HOMW:B72W:LGFJ:HPNP:BVC3:XY5J:P4P5:BGIN:OIYR:QK7T:QEMB:3UBM

The docker build of the Dockerfile from above works fine.

Yeah, confirmed here too. It is an issue with autfs.
Thanks Avi for double checking tough.

Hi everyone,
I do not face this issue on my machines, but I do with my automatic build derjudge/piwik, based on centos:centos7. So the docker build service seems to be affected by this, also (see https://hub.docker.com/r/derjudge/piwik/builds/bcc7jbxwdzn7ssezehksajg/).

Here is mine: https://hub.docker.com/r/kciepluc/coreos-toolbox/
Failing every time on:
error: unpacking of archive failed on file /usr/sbin/mtr: cpio: cap_set_file
Error unpacking rpm package 2:mtr-0.85-7.el7.x86_64
Local builds on CoreOS alpha with Docker 1.10.3 work without issues.

authors: Djelibeybi The-Judge brunoborges kciepluc

repo: oracle/docker-images


text:
Added v19 of ORDS and listening to any interfaces

Hi,
added the checksum for latest version of ords and modify the configuration file to listen on any address, this allow not to specify the ip address in a k8s environment

You seem to have combined two changes into a single pull request. I'm seeing changes to both the RAC Dockerfiles/scripts as well as the ORDS ones. Also, you have switched one of the source images to the container-registry, which we don't do here on GitHub.
I'm going to close this PR as it's a little too messy to merge. I would suggest creating a separate branch from master for each changeset so that each PR can be reviewed just by a single codeowner.
You can learn more about the standard GitHub Flow here: https://guides.github.com/introduction/flow/

authors: Djelibeybi malagoli


text:
Generic path for JDK

Weblogic uses full path of JDK, not symbolic link, so to update the JDK is better to use a generic name, not one with the version.
Otherwise is necessary to update Weblogic script files to use the new JDK path (one with the new version)

Hi @lazize,
WLS is configured to use /usr/java/default, regardless what that links to. Were you facing any issue due to the original version of the env setup?

Hi @brunoborges ,
During the domain creation, Weblogic doesn't trust symlink, so it get the full path of symlink and use it inside many scripts, below you can see some example.
`[oracle@wlsadmin bin]$ grep "/usr/java/" *
grep: nodemanager: Is a directory
grep: patching: Is a directory
grep: server_migration: Is a directory
grep: service_migration: Is a directory
setDomainEnv.sh:SUN_JAVA_HOME="/usr/java/jdk1.8.0_73"
setDomainEnv.sh:DEFAULT_SUN_JAVA_HOME="/usr/java/jdk1.8.0_73"
setDomainEnv.sh:		JAVA_HOME="/usr/java/jdk1.8.0_73"
setNMJavaHome.sh:SUN_JAVA_HOME="/usr/java/jdk1.8.0_73"
setNMJavaHome.sh:DEFAULT_SUN_JAVA_HOME="/usr/java/jdk1.8.0_73"
setNMJavaHome.sh:		JAVA_HOME="/usr/java/jdk1.8.0_73"
[oracle@wlsadmin bin]$ ps -ef f
UID        PID  PPID  C STIME TTY      STAT   TIME CMD
oracle     135     0  0 09:27 ?        Ss     0:00 /bin/bash
oracle     201   135  0 09:30 ?        R+     0:00  _ ps -ef f
oracle       1     0  0 09:24 ?        Ss     0:00 /bin/sh /u01/oracle/user_projects/domains/base_domain/bin/startWebLogic.sh
oracle      52     1  0 09:24 ?        Sl     0:01 /usr/java/jdk1.8.0_73/bin/java -Dderby.system.home=/u01/oracle/user_projects/domains/base_domain/common/db -classpath /u01/oracle/wlserver/common/derb
oracle      53     1  8 09:24 ?        Sl     0:30 /usr/java/jdk1.8.0_73/bin/java -server -Djava.security.egd=file:/dev/./urandom -Dweblogic.Name=AdminServer -Djava.security.policy=/u01/oracle/wlserver
[oracle@wlsadmin bin]$
`

Thanks @lazize for highlighting this issue. I've fixed it across all Dockerfiles that used to use ln, and now the jdk folder is moved to whatever is defined under /usr/java/default.
See commit e234ae65f55 for details

authors: brunoborges lazize


text:
Docs: Config exceeding three sources

The text is invalid in
https://helidon.io/docs/latest/#/se/guides/03_config
Should be:
Config.builder()
                .addSource(directory("conf"))
                .addSource(file("config-file.properties"))
                .addSource(classpath("config.properties").optional())
                .addSource(classpath("application.yaml"))
                .build();

INCORRECT (current):
import io.helidon.config.ConfigSources;
...

  private static Config buildConfig() {
      return Config.builder()
          .sources(ConfigSources.create(
              directory("conf"),
              file("config-file.properties"),
              classpath("config.properties").optional(),
              classpath("application.yaml")))
          .build();
  }

This example for meta configuration also does not work:
private static Config buildConfig() {
	return Config.loadSourcesFrom( file("meta-config.yaml"));
}

The following options exist:
meta-config.yaml will be used if you just do Config.create()
MetaConfig.config()  to get this default instance based on meta configuration
MetaConfig.config(Config) to provide an explicit meta configuration instance
Config.builder().config(metaConfig).build()

repo: oracle/helidon


text:
fixing issue #6 update the name of the secret in webhook.yaml so that…

… it is aligned with the one in the deployment

In helm/oci-native-ingress-controller/templates/webhook.yaml line 20 the name of the secret is hardcoded (oci-native-ingress-controller-tls), and this secret is referenced in helm/oci-native-ingress-controller/templates/deployment.yaml line 47, but this time the name of the secret is derived using a helm template function

repo: oracle/oci-native-ingress-controller


text:
correctly support disabling caps with CAP REQ, fixes #337

Passes irctest, tested the bugfix manually (the bug should get an irctest regression test though).

Ahhh I see. Awesome, thanks very much for working on this fix mate, appreciate it. Thanks for reporting it as well, @Ascrod :)

authors: DanielOaks slingamn

repo: oragono/oragono


text:
Update README.md

test ci pr

CI is set up. No need for this fake PR anymore.

repo: orange-cloudfoundry/osb-cmdb-spike


text:
Help my roads are gone!!

can anyone help me out point me toward a comprehensive guide of fixing this?? I don't have any PKIM errors and everything else works (yes the roads I'm looking for exist on open street map)
it would be great to get this fixed for me!

Send your log.

I'm having the same issue

nvm i was being dumb
On Tue, Apr 7, 2020 at 6:46 PM orangeadam3 notifications@github.com wrote:

Send your log.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/orangeadam3/terra121/issues/86#issuecomment-610705277,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APDCWNTR6BWQ3BR6NGR4DBLRLPJO3ANCNFSM4MDNKXNQ
.

nvm i was being dumb
…

What do you mean? What did you do wrong and how did you fix it?

authors: orangeadam3 pohans sofaslapper


text:
Dockerfile will not build (at least not at this time)

Version: orbit-db-0.20.1
This is just an FYI. I wanted to experiment with orbitdb and wasn't able to do so with the Dockerfile. Also I don't think you need to npm install webpack and babel if its in your package.json as a dependency. Maybe something with the npm registry changed since your Dockerfile last worked.(or maybe it's just me).
Steps:

git clone the repo, or download the release source.
Uncompress and/or cd into the source directory.
Docker build it:

[user@etc orbit-db-0.20.1]$ docker build -f ./docker/Dockerfile .
Sending build context to Docker daemon 1.492 MB
Step 1/9 : FROM node:carbon
Trying to pull repository docker.io/library/node ...
carbon: Pulling from docker.io/library/node
9cc2ad81d40d: Already exists
e6cb98e32a52: Already exists
ae1b8d879bad: Already exists
42cfa3699b05: Already exists
053cac798c4e: Already exists
e11ff976ff71: Already exists
81d72bab54a7: Pull complete
fcefcb4d99e7: Pull complete
592d9f42009b: Pull complete
Digest: sha256:c1c738e90e6c1f1f44043be5d0e77f1f16253b50ec4d98ab0f887fca72820a95
Status: Downloaded newer image for docker.io/node:carbon
 ---> c83f74dcf58e
Step 2/9 : ENV NPM_CONFIG_PREFIX /home/node/.npm-global
 ---> Running in f06b0a9aceff
 ---> e06e3f18b629
Removing intermediate container f06b0a9aceff
Step 3/9 : WORKDIR /home/node
 ---> d38075caf322
Removing intermediate container 35e13844677a
Step 4/9 : USER node
 ---> Running in 6f126031f193
 ---> 30cf1032e4ac
Removing intermediate container 6f126031f193
Step 5/9 : COPY package.json ./
 ---> d61e7add4c38
Removing intermediate container aa639f5d4e7e
Step 6/9 : COPY examples/ ./examples
 ---> 2947c24a5eb4
Removing intermediate container ad8661f8b74e
Step 7/9 : COPY src/ ./src
 ---> b054399b74a4
Removing intermediate container e944db2928b3
Step 8/9 : COPY conf/ ./conf
 ---> 09518413f56c
Removing intermediate container f20dffbfb4c0
Step 9/9 : RUN npm install babel-cli webpack  && npm install
 ---> Running in 78385e5378ea

npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/webpack failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org:443

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/node/.npm/_logs/2019-08-28T15_40_06_039Z-debug.log
The command '/bin/sh -c npm install babel-cli webpack  && npm install' returned a non-zero code: 1

I can ping npmjs.org fine, and wget the webpack registry entry fine from the VM I'm running docker build:
$ ping registry.npmjs.org
PING registry.npmjs.org (104.16.26.35) 56(84) bytes of data.
64 bytes from 104.16.26.35 (104.16.26.35): icmp_seq=1 ttl=128 time=14.6 ms

$ wget https://registry.npmjs.org/webpack
--2019-08-28 12:13:07--  https://registry.npmjs.org/webpack
Resolving registry.npmjs.org (registry.npmjs.org)... 104.16.21.35, 104.16.24.35, 104.16.25.35, ...
Connecting to registry.npmjs.org (registry.npmjs.org)|104.16.21.35|:443... connected.
HTTP request sent, awaiting response... 200 OK
...
2019-08-28 12:13:07 (9.81 MB/s) - ‘webpack’ saved [4275525/4275525]

This seems to be a DNS related error. See https://stackoverflow.com/questions/40182121/error-getaddrinfo-eai-again
What happens if you try the exact same build again?

Thanks for the reply.
The problem was the built container didn't use my resolv.conf DNS. I had to edit /etc/defaults/docker and add:
DOCKER_OPTS="--dns <my DNS ip>"
Then restart docker. I've never run into this issue before. Closing the issue. Thanks again.

authors: mckenziec phillmac

repo: orbitdb/orbit-db


text:
Moderator Site Title Change

Change the Moderator Site's title to OrcaHello and give it a subtitle of "An AI for Orcas platform"

working with mike on this update

created PR https://github.com/orcasound/aifororcas-livesystem/pull/118

authors: aarjukumar micowan

repo: orcasound/aifororcas-livesystem


text:
Add collection

where have i to send or upload the 2 .json documents ?

Here is a short guide on the Bitcoin Ordinals Wikia:
https://bitcoinordinals.fandom.com/wiki/How_to_List_an_Ordinals_Collection
If you get stuck or need help ask on the r/BitcoinOrdinals subreddit here:
https://www.reddit.com/r/BitcoinOrdinals/
The reddit also has a wiki of its own with guides and links:
https://www.reddit.com/r/BitcoinOrdinals/wiki/index/resources/

@apepix , are the guides helping you? Do you have meta.json and inscriptions.json prepared already?
Navigate to ordinals-wallet/collections. Then try to create a file there, which should then create your own fork of the repository. in your own fork you will put the 2 jsons under /collections/your-collection-name . The "slug" within the meta.json should ideally be your-collection-name as well. Please try and you can let me know the pull request number here.

sorry , posible its my inability to code .
I have the meta.json and inscriptions.json.
when i go to ordinals-wallet/collections, and click the button , it redirects me to github (that i dont know how to manage it)

i think i do it .
can you help me to be sure ?
https://github.com/apepix/Bitcoin-TradeMarks-8k-47k-

not correct yet. meta.json and inscriptions.json need to be in /collections/your-collection-name/ !!! and if you have them there, then you can create a pull request we can work with

thanks so much
https://github.com/apepix/Bitcoin-TradeMarks-8k-47k-/tree/main/collections
i think its in there, can you check it ?

https://github.com/apepix/Bitcoin-TradeMarks-8k-47k-/tree/main/collections/Bitcoin TradeMarks (8k-47k)

create a pull request

thx
-Add files via upload #2322-
https://github.com/ordinals-wallet/ordinals-collections/pull/2322

issue closed. pull request not merged. reason: pictures of trademarks. thank you for your understanding.

what kind of logos? i don't know. did you inscribe them?

yes , this is one of them
https://ordinals.com/inscription/4d6beb959faccf7923f0be6e1170c0f9327e36cc8c0037a3bb80e764ebddaaf1i0

please open a pull request if you want to list a collection that you inscribed.

authors: apepix chrisconfirm cliobitcoinbank

repo: ordinals-wallet/ordinals-collections


text:
fixes inconsitency in terms.cap naming

Fixes #3502

Ah sorry just saw this. I fixed this in #3505. Thanks for the PR though!

authors: raphjaph twosatsmaxi

repo: ordinals/ord


text:
add testing for activemodel through Rails 5.0.0.beta1

Closes #340.

:+1: Better than #341.

Want to go ahead and merge this? We can keep the Gemfile up to date with the betas as they come out.

authors: AaronLasseigne tfausak

license: mit


text:
fix: don't create regex inside a loop

Description
Moves the creation of an array of TextProcessor objects, that includes the contruction of a Regex to the outside of a loop. The array is only ever user by reference, so reusing a single instance will produce the same effects.
Motivation and Context
The Lints CI check is failing due to the creation of the same Regex within a loop.
How Has This Been Tested?
The change is within the integration tests, and those continue to pass.
Screenshots / Logs (if applicable)

Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (no code change)
[ ] Refactor (refactoring production code)
[ ] Other

Checklist:

[x] My code follows the code style of this project.
[ ] ~I have updated the documentation accordingly.~
[x] I have formatted the code with rustfmt.
[x] I checked the lints with clippy.
[ ] ~I have added tests to cover my changes.~
[x] All new and existing tests passed.

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

Project coverage is 42.88%. Comparing base (99b78b5) to head (eaafe2d).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #937   +/-   ##
=======================================
  Coverage   42.88%   42.88%
=======================================
  Files          21       21
  Lines        1712     1712
=======================================
  Hits          734      734
  Misses        978      978

Flag
Coverage Δ

unit-tests
42.88% <ø> (ø)

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

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

authors: codecov-commenter kemitix

repo: orhun/git-cliff


text:
Silent failure when incorrectly querying for edges

SELECT EXPAND( inE(MyEdgeName) ) FROM #62:4 limit -1
does not fail, but instead returns ALL of incoming edges
quoting the name, on the other hand produces the correct results
SELECT EXPAND( inE("MyEdgeName") ) FROM #62:4 limit -1

MyEdgeName is replaced with the field with name MyEdgeName, but since it doesn't exist, it's null. inE(null) means get all the incoming edges, so it's correct.

Is there any way to detect these cases (some kind of strict mode)? While this is technically correct, it can (and does) lead to hard to find bugs.
The existing strict mode is a reverse of this -- it makes all fields required. What I want is requests for fields that are not in the schema to fail

Hi @lodrion
I'm afraid there is no automatic way to check it. Strict mode checks schema only during insert/update operations.
Thanks
Luigi

authors: lodrion luigidellaquila lvca

repo: orientechnologies/orientdb


text:
Provide more configuration for teleporter

For now it is impossible change target class name for source tables. It would be useful specify target properties names and types. Also would be nice filter subset of the columns to import

Hi @Koc, we are working in order to offer a smarter, more flexible and customizable importing. We have just released the last OrientDB 2.2.2 EE with a new version of Teleporter included that allows to configure the migration through a JSON file. At the moment you can affect the relationships-edges mapping (https://github.com/orientechnologies/orientdb-docs/blob/master/Teleporter-Import-Configuration.md), the next step we will work on will comprehend your proposal: a new configuration mapping between tables and vertices will be possible, with a granularity at property level.
BTW at the moment you can filter in or filter out the tables you want to import (table granularity) through the arguments '-include' or '-esclude':
https://github.com/orientechnologies/orientdb-docs/blob/master/Teleporter-Import-Filters.md
Thanks for your feedback and proposal.

@G4br13l3 thank you for fast reply. Yes, I've reading this sections in documentation.
Also teleporter which shipped with inside EE 2.2.2 not works for me, it says that cann't load class OTeleporter or similar. I've downloaded teleporter separately and put jar inside plugins dir and it works.

We have just planned a new release, I advise you to try again when the last version will be available because the package you just downloaded is outdated. I will update here when the release will be completed.

Hi @Koc, we released the new orientdb 2.2.3 version with Teleporter correctly integrated. Can you try again with the latest version?
Let me know, thanks.
Here the download link:
http://orientdb.com/download/

@G4br13l3 okay, thank you, will try.
Can you also see related issue https://github.com/orientechnologies/orientdb-docs/issues/168 ?

Hi @Koc, we released a new user interface for Teleporter in orientdb studio 2.2.24 (in the server management area), thus now you can map in a visual way the source schema of the RDBMS with the graph model in OrientDB. The Teleporter plugin is now integrated into OrientDB Community Edition (previously it was available only in the Enterprise Edition). Beware: in CE you can't synch your database.
I'm closing this thread, please reopen it if you need something more.
Thanks.
Gabriele


text:
OrientDb Pagination Issue

OrientDB Version, operating system, or hardware.

v2.1 SNAPSHOT[ ] - .9[ ]

Operating System

[ ] Windows

Expected behavior and actual behavior
Im using orientDb(version 2.1.9). When I try to implement pagination , it throws me the below error
Encountered "  "LIMIT "" at line 1, column 158.
Was expecting one of:
 ...
 ...
Steps to reproduce the problem

Hi @thanveeraqtharah
I strongly suggest you to upgrade to v 2.2, as 2.1 is currently supported only for enterprise users.
Anyway, please post your full query, maybe there is a way to work around it
Thanks
Luigi

Thank you for your reply.  Im using

	<dependency>
		<groupId>com.orientechnologies</groupId>
		<artifactId>orientdb-server</artifactId>
		<version>2.1.9</version>
	</dependency>

and below  is the query
com.orientechnologies.orient.core.sql.OCommandSQLParsingException: Error on parsing command at position #0: Error parsing query:
Select from _222d768ec2ac4241b574678fea02cd83 where meta.appId='0eb92c64078949c8bbc16daeaa0f4267' and meta.sourceId='222d768ec2ac4241b574678fea02cd83' and LIMIT 5;
Encountered "  "LIMIT "" at line 1, column 156.
Was expecting one of:
 ...
 ...
 ...

Ok, got it, you just have to remote an "AND" ;-)
Select from _222d768ec2ac4241b574678fea02cd83 where meta.appId='0eb92c64078949c8bbc16daeaa0f4267' and meta.sourceId='222d768ec2ac4241b574678fea02cd83'  LIMIT 5

Thanks
Luigi

thank you :)

authors: luigidellaquila thanveeraqtharah


text:
Deactivate control not working

Get error message when try to deactivate using control button or infowindow close button.

Looks like the latest measure control PR:s in origo-master changed something so the multiselect-plugin deactivate button not working. Worked a few days a go, with older origo-master. Not sure if the plugin needs to be fixed or should the issue be in origo-master?

Fixed superfast in origo-master PR #1140 https://github.com/origo-map/origo/pull/1140

Fixed superfast in origo-master PR #1140 https://github.com/origo-map/origo/pull/1140

repo: origo-map/multiselect-plugin


text:
Full Coverage

Added test to catch the panic response when an invalid member is entered which raises the test coverage from 97% to 100%.

Thank you! I'm always a bit lazy to test panics. That was the very last thing I covered in genesis too :)

authors: euanwm orsinium

repo: orsinium-labs/enum


text:
Importing verified email addresses not working with batchPatchIdentities if email value is not all lowercase

Preflight checklist

[X] I could not find a solution in the existing issues, docs, nor discussions.
[X] I agree to follow this project's Code of Conduct.
[X] I have read and am following this repository's Contribution Guidelines.
[X] I have joined the Ory Community Slack.
[X] I am signed up to the Ory Security Patch Newsletter.

Ory Network Project
https://account-flows-test.bonfirehub.com
Describe the bug
See https://www.ory.sh/docs/kratos/manage-identities/import-user-accounts-identities#importing-verified-addresses for context about how to import an identity as verified.
Example payload to reproduce the issue:
const { data } = await IdentityApiClient.batchPatchIdentities({
    patchIdentitiesBody: {
        identities: instances.map((instance) => {
            const credentials = generateIdentityCredentials(instance);

            let verifiableAddresses;

            if (instance.IsConfirmed) {
                verifiableAddresses = [
                    {
                        value: instance.Email,
                        verified: true,
                        via: 'email',
                        status: 'completed'
                    }
                ];
            }

            return {
                create: {
                    schema_id: IDENTITY_SCHEMA_ID,
                    state: instance.HasAcceptedInvitation ? 'active' : 'inactive',
                    traits: {
                        email: instance.Email
                    },
                    credentials,
                    verifiable_addresses: verifiableAddresses
                },
                patch_id: instance.UserUUID
            };
        })
    }
});

If instance.Email is not all lowercase, then the identity ends up as "Verification pending" instead of "verified" when viewed in the Ory Network project.
https://github.com/ory/kratos/pull/3330 fixed some related issues. I'm not sure if there has been a regression, or if this code path was never fixed by that PR. I'll do some more digging to see if this affected us in the past or not.
Reproducing the bug
See code sample in description above
Relevant log output
No response
Relevant configuration
No response
Version
Ory Network
On which operating system are you observing this issue?
Ory Network
In which environment are you deploying?
Ory Network
Additional Context
No response

I believe this may be a regression. After a quick investigation, it appears we have imported verified identities in the past where the email address wasn't all lowercase.

repo: ory/network


text:
Add onnx inference notebook

Fixes #239
This PR adds an example of int8 quantization of the distilbert model for the text relevance classification task.
Signed-off-by: Shreyanand shanand@redhat.com

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from shreyanand by writing /assign @shreyanand in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Shreyanand: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

aicoe-ci/prow/pre-commit
4af4503a576a69113ad2dd9e774ede81a4af5730
link
true
/test pre-commit

Full PR test history. Your PR dashboard. Please help us and open an issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Shreyanand
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Shreyanand]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

authors: Shreyanand sesheta

repo: os-climate/aicoe-osc-demo


text:
rpm: provide systemd and microshift defaults

Implements the in [link] proposed change.
For example, to foward journald logs to AWS cloudwatch, a user only needs to create file /etc/opentelemetry-collector/configs/10-cloudwatch-export.yaml with the following content:
exporters:
  awscloudwatchlogs:
    log_group_name: "testing-logs-emf"
    log_stream_name: "testing-integrations-stream-emf"

service:
  pipelines:
    logs:
      receivers: [journald]
      exporters: [awscloudwatchlogs]

Afterwards, the opentelemetry-collector service must be restarted via systemd.
systemctl restart opentelemetry-collector.service

The Package will also install the manifests for an OpenTelemetry Collector on microshift. Its used to accept telemetry data from inside of microshift. (e.g. scraping the kubelet api, collecting metrics, logs and events.)
The manifests will be installed in /etc/microshift/manifests/opentelemetry-collector. If microshift is not present on the machine, this will have no effect.
An example configuration would look similar to the cloudwatch config. But instead of accepting logs from the journald  receiver, we would accept data from the otlp/microshift receiver.
service:
  pipelines:
    logs:
      receivers: [otlp/microshift]
      exporters: [debug]
    metrics:
      receivers: [otlp/microshift]
      exporters: [debug]
    traces:
      receivers: [otlp/microshift]
      exporters: [debug]

NOTE: Debug can be replaced by any kind of exporter that can registered to a pipeline type.
cc @miyunari @fkolwa @major @mparram

Build:
https://copr.fedorainfracloud.org/coprs/miyunari/redhat-opentelemetry-collector/build/7390581/

This PR needs to be rebased once https://github.com/os-observability/redhat-opentelemetry-collector/pull/66 got merged.

cc @examon

The package seems now to work as expected. I used to copr build for a short test.
For testing I created a /etc/opentelemetry-collector/configs/10-debug-export.yaml file with the following content:
---
service:
  pipelines:
    logs:
      receivers: [journald]
      exporters: [debug]
    metrics:
      receivers: [hostmetrics, hostmetrics/disk]
      exporters: [debug]

After restarting the collector  instance, I was finally able to see the data the journald logs.


text:
[Web-FE] Homepage 부대 군인들/최근 매모보고 Tab

Homepage 부대 군인들/최근 매모보고 Tab 시간되시면 Integration 해주시면 감사하겠습니다.

현재 저희가 만든 api 중에 부대 군인들을 관리하는 엔드포인트가 있나요?
없다면 자신의 Unit에 해당하는 User들로 GET하는 엔드포인트 하나 생성하겠습니다.

현재 저희가 만든 api 중에 부대 군인들을 관리하는 엔드포인트가 있나요? 없다면 자신의 Unit에 해당하는 User들로 GET하는 엔드포인트 하나 생성하겠습니다.

User api에 unit에 속해있는 user들을 호출하고, default query로 자기 자신과 같은 부대에 속해있는 User들을 GET하는 엔드포인트 생성했습니다.


text:
job queue: reschedule interrupted jobs

We are currently failing a lot in staging because an interrupted job is treated as fail. Instead retry these jobs.
A follow-up would be to teach the worker to notify about interruptions, rather than rely on the heartbeat.

Do you want to implement the missing bits on the worker side also in this PR?

I think that would be better as a follow up as I think we need some rework there (and don't know when I'll have time).

I gave this another thought and I think we need a reschedule limit. If a certain job always crashes the worker (which is scary but can happen), we don't want to retry it forever (it would be very hard to get rid of such a job).

I gave this another thought and I think we need a reschedule limit. If a certain job always crashes the worker (which is scary but can happen), we don't want to retry it forever (it would be very hard to get rid of such a job).

Good point... Though should we distinguish between graceful shutdown (no limit?) and heartbeat failure (potential crash so try at most three times or something like that?).

Btw, I wanted to figure out how to unit test this better before resubmitting.

I would do restart on timeout (to a limit) in this PR, then a follow-up where workers restart the build on termination (maybe without limit or with a higher one?) and independently instance protection. If someone could has the time to pick it up I think that would be great as I'm unsure when I could get to it

I'm unlikely to have time to finish this up, feel free to take it over / consider it an RFE, if anyone is interested.

I missed a little mistake when adding the test.

Merging this PR as the fedora failures are unrelated, and this is still going on to a reduced extent :(

authors: croissanne ondrejbudai teg

repo: osbuild/osbuild-composer


text:
Added functionality to Twig extractor

Modified Twig extractor to allow user to add custom Twig extensions should they be required to parse templates for gettext

Ok, thank you

authors: exnor oscarotero

repo: oscarotero/Gettext


text:
Billing portal session

Would it be possible to create a billing portal session?
https://stripe.com/docs/billing/subscriptions/integrating-customer-portal#redirect

Follow instruction here: https://github.com/oscarychen/drf-stripe-subscription#stripe-customer-portal

repo: oscarychen/drf-stripe-subscription


text:
StringLiteral until StaticBigInt

Lowering the minimum platform requirements (#61) means that StaticBigInt be disabled by default. I'll add an ExpressibleByStringLiteral conformance to NBKDoubleWidth in its place. It will work like init(_:radix:) except it will also support the 3 most common radix prefixes: 0b, 0o and 0x. So, ideally, the change is reduced to adding quotation marks.

I suppose one somewhat surprising thing is that conforming to ExpressibleByStringLiteral causes UInt256("123") to call init(stringLiteral:) as opposed to init?(_ description:) from LosslessStringConvertible, because there's a special case for literals. So UInt256(" 12") crashes as instead of returning nil. Dunno, if that's a problem. It probably isn't given that literals are known at compile time.

one remark - enable String Literal for SBI too. Right now it will be disabled when the SBI flag is set. They can both be present.

Your right in that these methods can coexist, but should they when one is clearly better? I suppose I can alleviate some migration pain by conditionally deprecating it. Or, do you have a use case in mind that prefers init(stringLiteral:) undeprecated? I'm thinking something like:
#if swift(>=5.8) && SBI
@available(swift, deprecated: 5.8, message: "Use an integer literal instead.")
#endif
@inlinable public init(stringLiteral source: StringLiteralType) { ... }

I think it can be used with some APIs which return strings with prefixes even if we have StaticBigInt. Maybe JSON-based API with big integers in it as hex values. I don't think it should be deprecated.

the method is good too. But I think we shouldn't force developers. If someone wants to use string literals - ok. Maybe they want to support older OSes without ifdefs even when they have StaticBigInt

I changed NBKDoubleWidth/StringLiteralType to StaticString from String.

I'll remove the deprecation because there isn't an automatic way of enabling StaticBigInt via availability.

authors: oscbyspro ypopovych

repo: oscbyspro/Numberick


text:
Add 'weeder' to CI

Add weeder to our CI pipeline. Weeder checks for unused dependencies and exports. This forces us to remove some unused dependencies.

Nice! But it doesn't look like CI is running this?

oops

repo: oscoin/radicle


text:
Merging Develop with Master branch

Completed COMP 4711 Assignment 2

Approved


text:
Parse-props-state

Requests Svelte resources from the inspected window and parses them, delivering a heirarchical json file to the D3 Tree Renderer.
Co-authored-by: Daniel Aurand daurand@users.noreply.github.com

Good to go!

authors: MichaelCGrant jessdvila

repo: oslabs-beta/Sveltool


text:
Flush commit metadata even when punning fails

Description
Closes: #XXXX

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] followed the guidelines for building modules
[ ] included the necessary unit and integration tests
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Looks reasonable to me, but @ValarDragon may object because this might cause other issues that I'm not aware of. Will rerun the "crash when trying to prune snapshot height" test with the branch tho.

That's great to hear. Thanks for reviewing and testing.
Since we know that this change fixes the earlier problem related to 6.3.0 only, now we can try addressing the "active reader problem" related to both 6.2.0 and 6.3.0. I will draft it up tomorrow morning

repo: osmosis-labs/cosmos-sdk


text:
add latest buf generation

Closes: #XXX
Protobuf generation with buf has gone a long way.
buf latest version: 1.4.0 has deleted "buf protoc".
the last version of buf that still supports "buf protoc" is: https://github.com/bufbuild/buf/releases/tag/v1.0.0-rc12
this creates frustration for engineers using latest version of buf since they will have to first figure out why "buf protoc" is gone when running ancient protocgen.sh
this pr intends to upgrade osmosis proto generation to latest with benefits:

no more complex proto generation script
using more clear buf.yaml structure
up - to - date buf binary with "buf protoc" removed
leverage "Buf Schema Registry" to include cosmos-sdk, cosmos-proto, googleapis proto files remotely in generating osmosis proto

Add a description of the overall background and high level changes that this PR introduces

(E.g.: This pull request improves documation of area A by adding ....
Brief Changelog
(for example:)

The metadata is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
Daemons retrieve the RPC data from the blob cache

Testing and Verifying
(Please pick one of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added unit test that validates ...
Added integration tests for end-to-end deployment with ...
Extended integration test for ...
Manually verified the change by ...

Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (yes / no)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (yes / no)
How is the feature or change documented? (not applicable   /   specification (x/<module>/spec/)  /  Osmosis docs repo   /   not documented)

Codecov Report

Merging #1614 (9e126cd) into main (e9062fc) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 9e126cd differs from pull request most recent head ecd23a1. Consider uploading reports for the commit ecd23a1 to get more accurate results

@@           Coverage Diff           @@
##             main    #1614   +/-   ##
=======================================
  Coverage   19.60%   19.60%
=======================================
  Files         242      242
  Lines       32279    32279
=======================================
  Hits         6329     6329
  Misses      24792    24792
  Partials     1158     1158

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 e9062fc...ecd23a1. Read the comment docs.

currently, it faces a weird problem of: interfacetype only supports messages with exactly one oneof declaration
here is where the error comes from:
https://github.com/regen-network/cosmos-proto/blob/master/interfacetype/interfacetype.go#L56

Is this different then whats going on in #1589

hi :) I thinik that you might be able to use cosmos-proto to resolve this.  Maybe that's a 46 thing though?

oh, it is the same, I will move over that issue

@alexanderbez ser, can you check over .yaml files that I have written here as well as new_protocgen.sh
the code is running

@nghuyenthevinh2000 how does this differ from my PR? I'd rather merge my PR (removing pulsar/ORM stuff) as it's a direct drop-in from the SDK.

Firstly, I want to say that I understand your feelings.
Secondly, direct from the SDK is not fit to Osmosis. I wil explain why:

buf.gen.gogo.yaml lacks protoc-gen-doc which is needed to generate proto-docs.md. Through my experience and understanding of buf.gen.yaml, I have added protoc-gen-doc to buf.gen.yaml with strategy "all". This is not present in buf.gen.gogo.yaml of the SDK.
My customization also consider "make proto-gen". tendermintdev/sdk-proto-gen:v0.2 docker image has only old buf which doesn't have "buf mod". Therefore, I have to locate the correct image that supports higher buf version and find out that tendermintdev/sdk-proto-gen:v0.3 docker is the only one that fits. v0.4 and above seems to have removed protoc-gen-doc.
Understanding of buf.gen.yaml "strategy" has allowed me to write significantly shorter and easier to read protocgen.sh

I'm not sure I follow? Proto docs were and still are generated via make proto-gen.

I am in favor of only doing this upgrade when we switch to an SDK version that does it as well / changing things upstream in the SDK.
I would everything around build process / proto generation to be as standard as possible, despite costs this may induce relative to the ideal. Maintaining alternate protobuf generation doesn't seem like a great reward vs maintenance payoff.
I currently build proto-docs via make proto-all and whatever thats doing internally.
Thanks for the interest in changing things here! I'd personally prefer closing this though / making isolated issues / PR's for discussing further problems we may be having / if theres a setup problem your having.

I am in favor of only doing this upgrade when we switch to an SDK version that does it as well / changing things upstream in the SDK.
I would like everything around build process / proto generation to be as standard as possible, despite costs this may induce relative to the ideal. Maintaining alternate protobuf generation doesn't seem like a great reward vs maintenance payoff to me.
I currently build proto-docs via make proto-all and whatever thats doing internally.
Thanks for the interest in changing things here! I'd personally prefer closing this though / making isolated issues / PR's for discussing further problems we may be having / if theres a setup problem your having.

love to hear opinions. I will close this one for further discussion.

authors: ValarDragon alexanderbez codecov-commenter faddat nghuyenthevinh2000

repo: osmosis-labs/osmosis


text:
x/gamm: Catch overflow panics on CalculateSpotPrice

Closes: #2207, #2445
What is the purpose of the change
This PR prevents SpotPrice from panicing and makes it return an error for invalid or overflowing spot prices instead. It also adds tests to ensure spot prices stay within the set bounds.
Brief Changelog

SpotPrice now recovers panics and returns an error. It also sets a max spot price of 2^160

Testing and Verifying

New tests can be found in x/gamm/pool-models/balancer/pool_suite_test.go

Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (yes / no)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (yes / no)
How is the feature or change documented? (not applicable   /   specification (x/<module>/spec/)  /  Osmosis docs repo   /   not documented)

Comments should all be addressed!

Oh I didn't catch this, this was done at the balancer level, which is the wrong place to do it.
This should be done at the keeper level, will move in a follow-up PR.

Yikes, spot price rounding is also at the wrong layer of abstraction

By spot price rounding do you mean the 2^160 spot price cap? In any case it should be a quick move to here for both the overflow check and rounding if that's what you mean – the issue had originally started as balancer tests for finding min/max prices (which was easiest to implement at the balancer level) so it seems as though the rest of the changes got stuck at that abstraction layer as well. Happy to open a new PR with changes moved to CalculateSpotPrice at the keeper level if you haven't started on it yet

authors: AlpinYukseloglu ValarDragon


text:
chore[e2e]: faster epoch

Closes: #XXX
What is the purpose of the change
Epoch is currently set to 1 minute. There are two tests that wait for an epoch to pass before continuing in the e2e test suite. This means we could potentially have to wait up to a minute to continue the test. There is no need for this, so we should just speed up the epoch duration more.
Testing and Verifying
Built locally, and tested against the currently open e2e PR against main
Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

[ ] Specification (x/{module}/README.md)
[ ] Osmosis documentation site
[ ] Code comments?
[ ] N/A

@devbot-wizard add changelog misc

@devbot-wizard add changelog misc

@devbot-wizard add changelog misc

@devbot-wizard add changelog misc

@devbot-wizard add changelog misc

@devbot-wizard add changelog misc

@devbot-wizard add changelog misc


text:
Deploy frontend github pages

I can get this working for sure!

This might be interesting: https://github.blog/changelog/2021-12-16-github-pages-using-github-actions-for-builds-and-deployments-for-public-repositories/
It's a blog post that contains a new (official) GitHub Action called "deploy-pages", to automatically deploy on push

Automation through GitHub will hopefully be a go through #13

authors: DemianD Denperidge


text:
Tasks are not getting queued

When i gave new tasks they are not being pushed to the queue, so i change the the following line
https://github.com/osrf/rmf_core/blob/575a12c6e11e2e64c97a75f09aa24fc9b174d9b4/rmf_fleet_adapter/src/full_control/FleetAdapterNode.cpp#L173
to
_task_queue.emplace_back(std::move(new_task));
and problem was solved

Thanks for catching this bug! The current fleet adapters are in the process of being completely rewritten, but this is a simple and important enough fix that I'll go ahead and push it in.

We can close this issue as the problem should be long solved now.

authors: MilanMichael mxgrey


text:
Replace PROJECT_SOURCE_DIR in tests

This allows the test files to be loaded in a more abstracted way,
so that it is less dependant on the way that CMake works.
Signed-off-by: Michael Carroll michael@openrobotics.org

Codecov Report

Merging #460 (e7dd7ce) into sdf10 (2cf2c8c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            sdf10     #460   +/-   ##
=======================================
  Coverage   87.78%   87.78%
=======================================
  Files          62       62
  Lines        9577     9577
=======================================
  Hits         8407     8407
  Misses       1170     1170

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 2cf2c8c...4d06a1b. Read the comment docs.

Codecov Report

Merging #460 (e7dd7ce) into sdf10 (2cf2c8c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            sdf10     #460   +/-   ##
=======================================
  Coverage   87.78%   87.78%
=======================================
  Files          62       62
  Lines        9577     9577
=======================================
  Hits         8407     8407
  Misses       1170     1170

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 2cf2c8c...4d06a1b. Read the comment docs.

authors: codecov-io mjcarroll

repo: osrf/sdformat


text:
container: clarify that nmz container run -d runs in foreground

Addendum to #158
PTAL @v01dstar

Coverage decreased (-0.04%) to 40.796% when pulling 408a81dd2079a973412df650e8c1078843e4a986 on suda/wip into a8e405bedbc210634c6cb482cafc6a906351a13c on master.

LGTM

authors: AkihiroSuda coveralls v01dstar

repo: osrg/namazu


text:
Align on reading all config files from config directory by default

The code base currently is a bit inconsistent about what files are read from ~/.ort/config by default. For example, the main ORT configuration file (in HCOCN format) ort.conf is read from ~/.ort/config/ort.conf if no other file is specified. The same goes for the Analyzer's curations.yml, but not for the Evaluator's rules.kts. This should be aligned to read all basic configuration files from ~/.ort/config by default to a full ORT pipeline could be configued via ~/.ort/config contents only.

Closing as a duplicate of https://github.com/oss-review-toolkit/ort/issues/2424.

repo: oss-review-toolkit/ort


text:
Why does the analyzer ignore settings /project/.ort.yml and exclude node_modules?

I tried to run the analyzer for yarn packages, but it seems not use the current settings of the .ort.yml
Even if .ort.yml is renamed to .ort1.yml and empty there are settings enabled to ignore several project specific directorys not only those refering to gitlab.
So it is not possible to run a local analyzer.
Here an extract of the analyzer logs:
______________________________
/        \_______   \__    ___/ The OSS Review Toolkit, version DOCKER-SNAPSHOT.
|    |   | |       _/ |    |
|    |   | |    |   \ |    |    Running 'analyze' as 'root' under Java 17.0.5 on Linux
\________/ |____|___/ |____|    with 8 CPUs and a maximum of 6556 MiB of memory.

Environment variables:
ORT_CONFIG_DIR = /project/ort
ORT_DATA_DIR = /root/.ort
JAVA_HOME = /opt/java/openjdk
ANDROID_HOME = /opt/android-sdk

Looking for ORT configuration in the following file:
	/project/ort/config.yml

--package-managers is deprecated, use -P ort.analyzer.enabledPackageManagers=... on the ort command instead.
Looking for analyzer-specific configuration in the following files and directories:
	/project/.ort.yml (does not exist)
	/project/ort/resolutions.yml
The following package managers are enabled:
	Yarn
Analyzing project path:
	/project
14:26:32.453 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/node_modules' as it is hard-coded to be ignored.
14:26:32.454 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/build/flattened-project/.gradle' as it is hard-coded to be ignored.
14:26:32.955 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/build/flattened-project/src/main/resources' as it is hard-coded to be ignored.
14:26:32.967 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/libs/translation/src/test/resources' as it is hard-coded to be ignored.
14:26:32.967 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/libs/translation/src/main/resources' as it is hard-coded to be ignored.
14:26:32.973 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/libs/pdf/renderer-openhtmltopdf/src/test/resources' as it is hard-coded to be ignored.
14:26:32.976 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/libs/pdf/src/test/resources' as it is hard-coded to be ignored.
14:26:32.977 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/libs/pdf/src/main/resources' as it is hard-coded to be ignored.
....

The resolutions.yml does not contain excludes.
Are there still some default settings provided in by ort I have overseen which overwrite my config for .ort.yml?
I hope this helps to understand my question or to reproduce the ignored .ort.yml
Thank you very much.

as it is hard-coded to be ignored

Emphasis is on "hard-coded", see https://github.com/oss-review-toolkit/ort/blob/0baf66d4e1a52ef18c739a190bc2b5bd4f62ccf7/analyzer/src/main/kotlin/PackageManager.kt#L75-L117

Thank you. This means, that it does not make sense to analyze all the package.json files in the node_modules for a n ORT run within the local branch of the project?

I'm not sure whether I'm getting your question right, but I'm trying to answer: A node_modules directory should never be committed to a project's Git repo because their contents are generated by npm install. If node_modules still is present when running ORT, it's contents are ignored when looking for projects. Then any existing node_modules directory is stashed away before ORT runs npm install itself, the node_modules contents are analyzed to get the dependencies / packages, and then any original node_modules is restored.

authors: schvvarzekatze sschuberth


text:
build(Gradle): Remove maven-compat as a library

That library offers a Maven-2-compatibility-layer that is never directly used by ORT.

One test is failing with a Plexus related error, maybe it is important that maven-compat is on the classpath even if we don't use it directly?

Ah, crap, I keep forgetting about this. Maybe this is because we use some deprecated classes in MavenSupport and thus still run into https://issues.apache.org/jira/browse/MNG-5995 😞

thus we still run into https://issues.apache.org/jira/browse/MNG-5995 :disappointed:

Or probably it's rather https://issues.apache.org/jira/browse/MNG-6561.


text:
avoid displaying coverage analysis when no coverage

Fixes: https://github.com/ossf/fuzz-introspector/issues/486
Signed-off-by: David Korczynski david@adalogics.com

repo: ossf/fuzz-introspector


text:
Feature - Sign scorecard container with cosign

Is your feature request related to a problem? Please describe.
Sign scorecard containers with cosign

Now that https://github.com/sigstore/cosign 1.0 we could use it for signing.
Thoughts @inferno-chromium @azeemshaikh38

On a high-level the idea sounds good to me. I don't understand cosign a 100% though. Do you mind sketching out what this would look like, ie. would this be done through CloudBuild, any major changes that would be required etc.?

@naveensrinivasan assigning this to you as per yesterday's discussion. Lets come up with a one-pager proposal here to submit in the TAC meeting

Thank you @developer-guy!  We are tracking this part of this larger issue https://github.com/ossf/scorecard/issues/1051
We want to come up with a plan of it being SLSA compliant.

We still haven't yet decided on whether to use GitHub for signing the keys or use google for signing the keys and also the provenance that comes along for it to be SLSA compliant.
Once we decide that then it should be easy.
If you have any recommendations more than happy to hear on the https://github.com/ossf/scorecard/issues/1051

Would OIDC be an option? This way we don't need a special workflow to generate keys and store them in GH secrets, and we also get built-in key rotation.

Yes, that would be a great option for signing containers.
Signing blob(scorecard binary) is easy. But verifying is jumping through lots of hoops. I am trying that the tooling isn’t there yet.
Also we need to understand if it suffices the SLDA requirements.

hello @azeemshaikh38 @naveensrinivasan, here is the keyless image signing example with GoReleaser recently created as a sample project^1, thanks to @caarlos0, of course, you can find an example of signing checksum also, here is the related tweet^2
Sample 1: Signing Container Images
docker_signs:
  - cmd: cosign
    env:
    - COSIGN_EXPERIMENTAL=1
    artifacts: images
    args:
    - 'sign'
    - '--oidc-issuer={{if index .Env "CI"}}https://token.actions.githubusercontent.com{{else}}https://oauth2.sigstore.dev/auth{{end}}'
    - '${artifact}'

Sample 2: Signing checksums.txt file
docker_signs:
  - cmd: cosign
    env:
    - COSIGN_EXPERIMENTAL=1
    artifacts: images
    args:
    - 'sign'
    - '--oidc-issuer={{if index .Env "CI"}}https://token.actions.githubusercontent.com{{else}}https://oauth2.sigstore.dev/auth{{end}}'
    - '${artifact}'

Cross-linking a few things from Kubernetes tracking:

Signing release artifacts: https://github.com/kubernetes/enhancements/issues/3031
SLSA Level 3 Compliance in the Kubernetes Release Process: https://github.com/kubernetes/enhancements/issues/3027
Signing artifacts with cosign: https://github.com/kubernetes/release/issues/2227
Implement container image signing MVP (KEP-3031): https://github.com/kubernetes/release/issues/2383
KEP (Kubernetes Enhancement Proposal): https://github.com/kubernetes/enhancements/tree/master/keps/sig-release/3031-signing-release-artifacts

kindly ping @naveensrinivasan, what needs to be done? 🙏

We could also wait for the slsa-generator to have support for container (laster this month), and use that with GoReleaser.
I think some of our images use ko as well.
/cc @ianlewis

Is this something that still needs to be discussed?
If there is no feedback in the next 7 days on whether this remains important for the project, then this issue will be closed.

authors: afmarcum azeemshaikh38 developer-guy justaugustus laurentsimon naveensrinivasan

repo: ossf/scorecard


text:
Joining the WG

Hey everyone!  My name is CRob and I work with Red Hat Product Security.  We're very please to participate in these OSSF working groups (and Vulnerability Disclosure is particularly close to my heart!).  Very interested to meet and hear what the group has been toiling away on and look for opportunities where I can bring in SMEs (like from our DevOps team) to assist/collab on efforts like the API.  Talk to everyone soon!
-CRob

@RedHatCRob welcome to the WG!

@RedHatCRob Can you create a PR similar to #20 to add yourself to the list of WG members?

Now that #20 has been merged, this issue can be closed. Once again welcome to the WG!

@RedHatCRob A quick reminder about the PR to add yourself to the list of WG members.

#46 has been merged, and I think we can close this issue now 🎉 !

authors: MarcinHoppe RedHatCRob

repo: ossf/wg-vulnerability-disclosures


text:
Cannot load M3U8 file: Crossdomain access denied

I tried to play my HLS stream but the player (JWt): http://.../live/demo.m3u8 always said that: No 'Access-Control-Allow-Origin' header is present on the requested resource
My srs.conf also have:
http_server {     enabled         on;     listen          8080;     dir             ./objs/nginx/html;     crossdomain on; }
I also added Access-Control-Allow-Origi to my Nginx configuration:
`
location / {
root   html;
index  index.html index.htm;
add_header 'Cache-Control' 'no-cache';
add_header Access-Control-Allow-Origin *;
add_header Access-Control-Expose-Headers Content-Length;
    }
    location /live/ {
        types {
            application/vnd.apple.mpegurl m3u8;
            video/mp2t ts;
        }
        root html/;
        add_header Access-Control-Allow-Origin *;
        add_header Access-Control-Expose-Headers Content-Length;
    }

`
Please help me solve this issue. Thank you very much!

SRS fixed it.

authors: khachuong winlinvip

repo: ossrs/srs


text:
SRS 是否会支持通过接口控制录制文件。

SRS 是否会支持通过API接口控制录制文件，这个在NGINX-RTMP中是支持的，想录制的时候可以录制，谢谢。

RAW API实现的就是如何修改配置并reload。最自然的方式就是用Go或者Nodejs写一个后端服务器，修改配置文件后，给SRS发信号或者调用reload的API就可以。而且如何修改配置，何时修改，是和业务强相关的，属于业务系统的一部分。因此就在4.0删除了。
RAW API is removed because it implements the config file modify and reload, which should do by user server.
HTTP RAW API是在3.0引入的实验性的能力：
[Experimental] Support HTTP RAW API, please read https://github.com/ossrs/srs/issues/459 https://github.com/ossrs/srs/issues/319
它主要是提供能够修改系统的API的能力，主要是通过修改配置文件，然后Reload生效的方式实现。在提供这个能力之后，不断的有持续的bug报出来和这个相关，所以决定在4.0删除这个实验性的能力。
它问题多的主要原因是：本来应该用户实现的业务系统，被放在了RAW API中实现了。比如：按需录制，只需要录制某些流。
比较典型的方式是独立一个系统，管理FFmpeg进程，每个FFmpeg来拉流录制，用HTTP回调判断哪些流需要录制。
或者使用HLS写ts文件，用on_hls回调来决定哪些需要录制。
而RAW API修改dvr_apply，应用到某些流上来开启录制。
使用RAW API会触发相当多的边界条件，流可能会推流又停止，录制的规则可能非常多样化。这些都是典型的录制的服务需要考虑的事情，每个录制都可能会有不同的诉求，而不是适合在通用开源方案中实现。


text:
Fix typo for comments in srs_core.hpp

modify a word.
Summary
Just tow words.
Details
user -> use

Codecov Report

Merging #2832 (cbfc83d) into 4.0release (425b5cb) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           4.0release    #2832   +/-   ##
===========================================
  Coverage       60.27%   60.27%
===========================================
  Files             121      121
  Lines           51023    51023
===========================================
  Hits            30756    30756
  Misses          20267    20267

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 425b5cb...cbfc83d. Read the comment docs.

Thank you  @alongL 👍

authors: alongL codecov-commenter winlinvip


text:
Newcourseupdate-harvardcs50

I updated introduction to computer science by adding optional harvard CS50 Coursework which is less time consuming and offers quick 10 weak of intro to all aspects of computer science.Do check 2023 version if you feel it necessary please consider adding it .I did not removed other course just added another option to others to choose According to their requirements projects is included in cource work .

Hi Aryan,
Thanks for checking out OSSU and thinking through ways to strengthen the program for learners.
Our repo has a contributing guide, which has a section on making substantive changes. You'll note that those require opening an RFC in issues.
I'll also note that there's been quite a lot of discussion about CS 50, its appropriateness as an intro course and its appropriateness for OSSU. Before submitting an RFC to include CS 50 you should make sure to familiarize yourself with those conversations and be ready to address questions/concerns that have been raised in the past. You can find those conversations by searching the issues for CS 50 and for introduction. Until that RFC is opened and accepted, I'll close this pull request.
I hope this is just one of many contributions you'll make to OSSU.

authors: aryankumarakj waciumawanjohi

repo: ossu/computer-science


text:
Скласти додаткові інформаційні блоки

Можна зробити резюме менш формальним, додавши додаткові блоки, які містять корисну інформацію, але подають її в "розважальній" формі. Наприклад, що подобається і не подобається, сильні і слабкі сторони, перелік навиків чи хобі, інфографіка або ж інтерактивні модулі, тощо. Варто написати контент такого блоку раніше, ніж починати верстку, бо його розміри впливатимуть на розміщення елементів на сторінці.

Likes:
He likes playing Quidditch
He also enjoys flying on his boom stick
Harry also likes hanging out with his friends Hermione Granger and Ron Weasley
Harry also likes being with his godfather Sirius Black
He likes the spell expelliarmus and expecto patronum
Dislikes
Draco Malfoy
Voldemort
Potions Class
Professor Snape
Death eaters
Blood discrimination

нд, 2 трав. 2021 о 00:14 ostap-mamchur @.***> пише:

Closed #7 https://github.com/ostap-mamchur/homepage/issues/7.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ostap-mamchur/homepage/issues/7#event-4674039788, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AT5FYQKMABIQJZR65NWNKW3TLRVK7ANCNFSM436VW7BQ
.

Забагато Likes

authors: iryna-maselko ostap-mamchur

repo: ostap-mamchur/homepage