text:
cbi.lua: Problem handling optional options inside Map.parse()

Inside luci-app-privoxy and luci-app-openvpn and possibly other apps, values with ".optional" set true are not parsed correctly.
Inside OpenWrt 15.05 everything works fine.

I did not find the pull where Map.parse() was rewritten inside cbi.lua, but in current trunk
when you start the same page the optional values are missing.

If you press the [SAVE] button once (without any changes) the optional values are shown.

If you set sections property dynamic to true it's nearby the same.
After first call of the page you get an empty field to add an option but no selection list.
After pressing [SAVE] everything works as expected.
I crosscheck and only replace Map.parse() function inside cbi.lua of current trunk and everything works fine. (Screenshots are take from luci-app-privoxy)

@jow- could you please have a look at ?
To see problem on luci-app-openvpn do the following:
Create a new configuration (client ethernet bridge)
On the opened page select remove on option "verb" and "comp_lzo"
Press [Save & Apply] and go back to overview
go back and edit your configuration and all optionals are missing
Press [Save] and the selection list to add optionals is back

Will take a look soon but I'll rather remove optionals functionality entirely.

Why ?

@jow
I found additional problems with new parse function:
If using custom validate function because .datatype for an option doesn't fit:
Old: If you enter an invalid value and press [Save]/[Save&Apply] no data is written to uci.
New: data of other fields changed is written to uci (pending updates) and
really a problem, if [Save & Apply] the data except the invalid is written to uci and service is restarted.
If the list of options shown on one screen is long enough, nobody will see the error message at the bottom. because screen roll up after pressing one of this action button.

@chris5560: I do not like optionals because they're complicating the code and are counter-intuitive to use. Take an optional boolean for example: you first have to add it (which triggers an http request/response cycle already) then you have to set it (after you found out where exactly it popped up in the form), then you have to save again (next http request/response).
Optionals are especially confusing if they refer to default enabled boolean options. Take for example "option enabled 0" marked as optional - you first have to "add" the enabled option (despite the fact that it is enabled already) only to "remove" (uncheck) it once it appeared.
It is also confusing in the case of text input fields that suddenly disappear if made empty.
For new applications I rather suggest to move those optionals into an "advanced" tab or something.

@jow
OK good arguments. When I look at luci-app-radicale next time I will try to remove optionals.
I also need to change radicale package.
One reason why I use optionals was, because AbstractValue.size property is not handled by any StyleSheet.
It's defined in the corresponding views and set to nil (why) inside AbstractValue but changing it changes nothing.
By the way. Do you see a possibility to add tabs to maps not only to sections.
Looking on luci-app-radicale there are multiple sections that should be split into separate tabs.
One of these sections is currently handling the "optional" options.
Do you have a code sniplet how to realise one map and each section on a separate tab ?

@chris5560 I'll see if I can easily add map-level tab support.

The original issues should be solved now btw.

@chris5560 I added very basic support for arranging the section objects as tabs in maps. Simply set m.tabbed = true to enable it. Haven't done any extensive testing or css adjustments for this yet but it appears to work okay mostly.

@jow
map.parse fix works
m.tabbed I will check
Thanks


text:
Update luci-app-ksmbd - luci-app-ksmbd.json

match new template file name
Signed-off-by: pesa1234 andreapesaresi82@gmail.com

Merged via f0e0bccfb89bfa83af9729a94f748c6cc67cdcc7 - thanks!

It's a pleasure, next time I will be more precise!

source: gharchive/pull-request

repo: openwrt/luci

license_type: permissive

license_source: github-api


text:
luci-app-https-dns-proxy: add DNS0.EU support

add support for the new dns0.eu service
Signed-off-by: artion karreci artionkarreci@gmail.com

: Author name (artioni81) need to be your real name 'firstname lastname'
: Commit subject line MUST start with ': ' (add DNS0.EU support)
: Signed-off-by is missing or doesn't match author (should be 'Signed-off-by: artioni81 artionkarreci@gmail.com')

@artioni81 Please address the comments from https://github.com/openwrt/luci/pull/6240#issuecomment-1426910362

This PR can be closed as the Test Formalities check is failing more than 2 weeks now and once it will be addressed, then it can be reopened.

authors: BKPepe artioni81 stangri systemcrash


text:
luci-base: Add HttpOnly flag to the sysauth cookie

If the browsers enforces HttpOnly, a client side script will be unable
to read or write the session cookie.
https://www.owasp.org/index.php/HttpOnly
This minor code change may prevent client-side attacks (cookie stealing),
but should not break anything. Free security :)
The Secure flag would be nice too, but it is impossible for Lua to
determine if https is enforced at the server level.
This is my first contribution here, sorry if I missed something. Commit is gpg signed+signed-off-by

@jow- @hnyman Any comments? I don't know enough about the various browsers currently in use, to assess the impact of this, particularly on mobile devices.

@cshoredaniel this is absolutely safe change and very efficient against Session fixation via XSS.
The HttpOnly attribute is supported by all browsers starting from IE6
If you interested you can see more details here https://www.owasp.org/index.php/HttpOnly

Btw, looks like we need to make the change again in other files https://github.com/openwrt/luci/search?utf8=✓&q=sysauth&type=

No reaction and any progress on this PR

authors: cshoredaniel feckert mguerreiro stokito


text:
Compiling the Default Configuration - Syntax error, using vagrant

http://vi-firmware.openxcplatform.com/en/master/getting-started/development-environment.html
I followed the documentation like above and after do the command 'vagrant up' and 'vagrant ssh', I tried to run 'fab reference build' but it says I have to install fabric and, after I did 'sudo apt-get install fabric', when I run 'fab reference build', it gave me an error,
vagrant@precise32:/vagrant/vi-firmware-8.0.0$ fab reference build
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/fabric/main.py", line 594, in main
    docstring, callables, default = load_fabfile(fabfile)
  File "/usr/lib/python2.7/dist-packages/fabric/main.py", line 156, in load_fabfile
    imported = importer(os.path.splitext(fabfile)[0])
  File "/vagrant/vi-firmware-8.0.0/fabfile.py", line 249
    print(f"Make tests passed: {tests_passed}/2")
                                               ^
SyntaxError: invalid syntax

I have not altered anything in the default fabfile.py file in the vi-firmware-8.00 release. Then, what kind of syntax was incorrect and how do I fix this issue.
P/S: run vagrant terminal on Visual Studio Code

My VirtualBox configuration

Hi tpho216, I see you are using an old version of the vagrant virtual machine (Ubuntu 12) the current firmware v8.0.0 does not support old virtual machines as stated in the changelog and release notes,  fortunately this is an easy fix all you have to do re create the virtual machine.
To do this you should just have to run the below commands, be sure if you have created any items outside of the vi-firmware folder in the vm that you back them up before running the commands.

vagrant destroy
vagrant up

Hi tpho216, I see you are using an old version of the vagrant virtual machine (Ubuntu 12) the current firmware v8.0.0 does not support old virtual machines as stated in the changelog and release notes, fortunately this is an easy fix all you have to do re create the virtual machine.
To do this you should just have to run the below commands, be sure if you have created any items outside of the vi-firmware folder in the vm that you back them up before running the commands.

vagrant destroy
vagrant up

Hi I tried the following commands but still have issue with the syntax.

What was the output of those commands? You still seem to have not updated to the new version of the vm.

Outputs

Hmm Is the folder VI_Reference_firmware up to date with the git repo?

Hmm Is the folder VI_Reference_firmware up to date with the git repo?

It is, I cloned it from the repo

Outputs

I'll try update to Ubuntu version 14

Thats weird, unfortunatley manually updating it wont help since the new vagrant file also sets up all of the dependencies and libraries needed for compilation. What does your Vagrantfile look like?

I have 2 vagrant files, one inside the folder D:\Workspace\VI_Reference_firmware\ -> Vagrantfile,
look like this,
# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://vagrantcloud.com/search.
  config.vm.box = "hashicorp/precise32"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # NOTE: This will enable public access to the opened port
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine and only allow access
  # via 127.0.0.1 to disable public access
  # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Enable provisioning with a shell script. Additional provisioners such as
  # Ansible, Chef, Docker, Puppet and Salt are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   apt-get update
  #   apt-get install -y apache2
  # SHELL
end

one inside the git repo, D:\Workspace\VI_Reference_firmware\vi-firmware\ -> Vagrantfile
# -*- coding: utf-8 -*-
# -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

def total_cpus
  require 'etc'
  Etc.nprocessors
end

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  # For a complete reference, please see the online documentation at
  # vagrantup.com.

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "bento/ubuntu-18.04"
  config.vm.box_version = "201912.03.0"
  config.vm.provider :virtualbox do |v|
    if total_cpus > 1
      v.cpus = total_cpus - 1
	else
	  v.cpus = 1
	end
  end

  # Check for proxy enviroment variable and set it
  if ENV['HTTP_PROXY'] || ENV['HTTPS_PROXY']
    if Vagrant.has_plugin?("vagrant-proxyconf")
      if ENV['HTTP_PROXY']
        config.proxy.http = ENV['HTTP_PROXY']
        config.apt_proxy.http = ENV['HTTP_PROXY']
      end
      if ENV['HTTPS_PROXY']
        config.proxy.https = ENV['HTTPS_PROXY']
        config.apt_proxy.https = ENV['HTTP_PROXY']
      end
      if ENV['NO_PROXY']
        config.proxy.no_proxy = ENV['NO_PROXY']
      end
    else
      abort("ERROR, vagrant-proxyconf not installed run ‘vagrant plugin install vagrant-proxyconf’ to install it")
    end
  end

  config.vm.box_download_insecure = true
  config.vm.provision "shell", privileged: false, keep_color: true do |s|
    s.inline = "ln -fs /vagrant vi-firmware;"
    s.inline += "VAGRANT=1 vi-firmware/script/bootstrap.sh"

  end
end

Ok now we are getting somewhere, the one at D:\Workspace\VI_Reference_firmware\ is out of date, my guess you are running your vagrant commands from there which is why you are getting the old Ubuntu palagon box, try running the vagrant commands from within the git repo D:\Workspace\VI_Reference_firmware\vi-firmware.

Ok now we are getting somewhere, the one at D:\Workspace\VI_Reference_firmware\ is out of date, my guess you are running your vagrant commands from there which is why you are getting the old Ubuntu palagon box, try running the vagrant commands from within the git repo D:\Workspace\VI_Reference_firmware\vi-firmware.

Thanks, I'll try now

Successfully compiled the file. Thanks for your immediate help! We're able to close this issue

source: gharchive/issue

repo: openxc/vi-firmware

license_source: bigquery


text:
Add missing inline keywords to public header functions

Suppresses warnings such as the following:
In file included from iree/base/api.h:88,
                 from iree/hal/drivers/vulkan/api.h:14:
iree/base/loop_inline.h:85:13: warning: ‘iree_loop_inline_deinitialize’ defined but not used [-Wunused-function]
   85 | static void iree_loop_inline_deinitialize(iree_loop_inline_storage_t* storage) {

My methodology was to grep for ^static (?!inline) in runtime/**/*.h

repo: openxla/iree


text:
[metal] Move to iree/hal/drivers and build by default

This commit moves the metal HAL driver from the experimental/
directory to the iree/hal/drivers/, and turns on building by
default for arm64 Apple platforms. x86_64 Apple devices are
supported right now with missing features and such; that's the
next step.
These existing code is already extensively reviewed and passing
various in-tree tests. Further improvements are for performance
and tracked in https://github.com/openxla/iree/issues/14050.

Enabled tests are all passing: https://github.com/openxla/iree/actions/runs/5778824351/job/15660451695?pr=14129.


text:
feat: bump golang from 1.16 to 1.17

Signed-off-by: HIHIA 283304489@qq.com

What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #1190
Special notes for your reviewer:

@rambohe-ch
Does this PR introduce a user-facing change?

other Note

/lgtm

/approve

authors: Congrool YTGhost rambohe-ch

repo: openyurtio/openyurt


text:
WIP: Support for 128 bit TraceIDs

This PR handles the ability of the tracer to work with 128 bit TraceIDs.
See: https://github.com/openzipkin/zipkin/issues/1298

this PR has been tested with 64 bit traceID Zipkin instance and is backwards compatible if tracing with 128 bit traceIDs by simply having the high bits of the traceID be ignored.
Sampling functionality is also solely on the low 64 bits.
This PR will be merged once Zipkin backend supports 128 bit TraceIDs.

I ran the example against snapshot zipkin and looks great!
   {
      "traceId": "15225468d9e004834ec2cc8befaf251f",
      "id": "3230ce0f79a9b1d9",
      "name": "mycomplexquery",

ps for those unacclimated, here's what I did to test..
$ export GOPATH=$HOME/work
$ export PATH=$PATH:$GOPATH/bin
$ cd $GOPATH/src/github.com/openzipkin/zipkin-go-opentracing/examples/cli_with_2_services
$ git checkout -t -b 128bit-traceid origin/128bit-traceid
$ make
$ build/svc1&
$ build/svc2&
$ build/cli

awesome... sounds like merge time to me!

authors: adriancole basvanbeek

repo: openzipkin/zipkin-go-opentracing


text:
Use CSS framework in lens

Currently, most of the components are so special that CSS framework can not be used as it is.
So I thought we did not need to use CSS framework.
However, it is expected that more general purpose components will added in the future.
So I'm going to begin to use CSS framework partially to develop such general components efficiently.
@zeagord Thank you for your great idea!!

I think it is nice to use the css frameworks such as semantic-ui or material-ui. It will quicken the development and visually pleasing as well. Let me know if you need any help from my end.

We use material-ui now.

Just for tracking purposes, I believe it was #2633 that introduced Material UI

authors: shakuzen tacigar zeagord

repo: openzipkin/zipkin


text:
Update quickstart example outputs

with the release of 0.25.5 the ziti edge list... commands display in a "prettified" view that resembles a table. The quickstart docs (specifically for docker-compose but likely others as well) still reference the older style output and need to be updated to the new output.
Examples should be updated for both ziti edge list edge-routers and ziti edge list identities
OLD:
ziti@724087d30014:/openziti$ ziti edge list edge-routers
id: BZ.Y7vMdAI    name: ziti-edge-router    isOnline: true    role attributes: {}
id: NELWwjMd8    name: ziti-private-blue    isOnline: true    role attributes: {}
id: l9-W7jMf8    name: ziti-fabric-router-br    isOnline: true    role attributes: {}
id: rqZW7vMdA    name: ziti-edge-router-wss    isOnline: true    role attributes: {}
id: xmiYwvMf8    name: ziti-private-red    isOnline: true    role attributes: {}

NEW (despite the image, the command ziti edge list edge-routers should remain the same in the sample output):

Disclaimer: Fair warning that the formatting might be tricky converting the console output to look the same in markdown format. I'm not positive it will be cumbersome but it's worth noting as this is tagged "good first issue"

Probably easier to use JSON output with jq filters or JSONPath if it's really necessary to use the CLI as an API.

No. This issue is about updating the doc to align better with what people see now. jq and JSONpath aren't relevant here

authors: dovholuknf gberl002 qrkourier

repo: openziti/ziti-doc


text:
chore(testing): Use Testcontainers in integration tests

Description
This change makes the tests use Testcontainers to spawn a Keycloak instance on a random port.
fixes #10

Some tests are failing. Working in principle, but seems that I missed something. When executing the tests from the IDE, the tests succeed. I will continue later on that.
Failed tests:   testOrderByGroupId(org.operaton.bpm.extension.keycloak.test.KeycloakUseGroupPathdAsGroupIdQueryTest): expected:<9> but was:<6>
  testFilterByChildGroupIdIn(org.operaton.bpm.extension.keycloak.test.KeycloakUseGroupPathdAsGroupIdQueryTest): expected:<2> but was:<0>
  testOrderByGroupName(org.operaton.bpm.extension.keycloak.test.KeycloakUseGroupPathdAsGroupIdQueryTest): expected:<9> but was:<6>
  testQueryPaging(org.operaton.bpm.extension.keycloak.test.KeycloakGroupQueryTest): expected:<3> but was:<0>
  testQueryUnlimitedList(org.operaton.bpm.extension.keycloak.test.KeycloakGroupQueryTest): expected:<9> but was:<6>
  testQueryNoFilter(org.operaton.bpm.extension.keycloak.test.KeycloakGroupQueryTest): expected:<9> but was:<6>
  testOrderByGroupId(org.operaton.bpm.extension.keycloak.test.KeycloakGroupQueryTest): expected:<9> but was:<6>
  testOrderByGroupName(org.operaton.bpm.extension.keycloak.test.KeycloakGroupQueryTest): expected:<9> but was:<6>
  testOrderByGroupType(org.operaton.bpm.extension.keycloak.test.KeycloakGroupQueryTest): expected:<9> but was:<6>
  testGroupQueryNoFilter(org.operaton.bpm.extension.keycloak.test.KeycloakMassDataTest): expected:<169> but was:<166>
  testGroupQueryFilterByGroupIdIn(org.operaton.bpm.extension.keycloak.test.KeycloakNestedGroupsQueryTest): expected:<2> but was:<1>

Tests run: 131, Failures: 11, Errors: 0, Skipped: 0

repo: operaton/operaton-keycloak


text:
New channel due to missing replaces(aws-efs-operator)

Signed-off-by: Martin Vala martin.vala@hotovo.com
Hi @2uasimojo,
there are two options, maybe you forgot to set replaces for the latest version or it was intended.
We added a version to separate channel as it actually fall off the update graph and are orphaned and not installable / upgradable anymore due to missing replaces in the path. After this PR, it will be installable from this channel.
The main reason for this update is that we are currently preparing to enable bundle based catalogs which involves background conversion, it’s currently failing for the reason stated above.
Our PR is just technically correct workaround, but only you know if everything can be replaced by higher version or not. If replaces is missing somewhere, we have 2 options. Create new channel or add replaces where it is missing. The last option is better, but only possible for someone who knows operator very well, so you as an author. Feel free to open a new PR if you have different opinion, we can communicate and get it merged.
Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ ] Does your operator have nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Is your submission signed?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Submit operators to both upstream-community-operators and community-operators at once
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

Thanks @mvalahtv.

maybe you forgot to set replaces

It was indeed by accident that I forgot replaces in 0.0.2. I am ashamed /o\

for the latest version

The latest version is 0.0.4, and it does have replaces. Just making sure I'm understanding the issue correctly: the problem is that 0.0.1 is orphaned, but the other versions (0.0.2, 0.0.3, 0.0.4) are fine in the stable channel. So you're creating a new channel just to un-orphan 0.0.1. Right?
I'm okay with this.
However, you said you would prefer to add replaces where it is missing. Again to make sure I understand, that specifically means adding replaces ...0.0.1 into the 0.0.2 CSV, right?
That would also be highly preferred for me, as having multiple channels could be confusing for the consumer, especially since 0.0.1 is effectively obsolete.
To answer the technical side, yes, the operator should seamlessly handle any upgrade path from 0.0.1 to 0.0.4 (including skipping versions, if that's relevant).
So to summarize: if possible, let's simply add replaces ...0.0.1 into the 0.0.2 CSV. If you can do it in this PR, great; if you want me to open a separate one, just lmk.

Should probably update the PR title though.

repo: operator-framework/community-operators


text:
upstream-community-operators [CI] keycloak-operator (13.0.0)

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

authors: framework-automation vmuzikar


text:
[upstream] [kiali] add 1.3.1

Adds Kiali Operator v1.3.1

I can't tell why this failed. No obvious errors in travis logs. I see no reason why this would fail.

@jmazzitelli I tried it locally and operator was installed successfully, just scorecard has been frozen


text:
Bug 1727800: Icon Subresource for PackageManifest

Description
Adds packagemanifests/icon subresource, which serves logo icons for a given PackageManifest.
Caching will be accomplished in this way:

Console requests /packagemanifests/<pkg>/icon?resourceVersion=<pkg>.<channel>.<csvName>
Server gets bundle from gRPC operator-registry and sends the image data with an ETag header
Next time browser requests the icon endpoint, sends If-None-Match header containing the ETag
Server checks the existence of ETag and sends HTTP 304
When new ClusterServiceVersion is added to the package, console will change the resourceVersion in the request URL and bypass the cache.
User can always perform hard refresh or clear cache to retrieve fresh icons.

Resources Used

https://sourcegraph.com/github.com/kubernetes/kubernetes/-/blob/pkg/registry/core/pod/storage/storage.go#L69
https://sourcegraph.com/github.com/kubernetes/kubernetes@master/-/blob/pkg/registry/core/rest/storage_core.go#L234
https://sourcegraph.com/github.com/kubernetes/kubernetes/-/blob/pkg/registry/core/pod/rest/subresources.go#L134

Implements https://github.com/operator-framework/operator-lifecycle-manager/pull/985
Addresses https://jira.coreos.com/browse/OLM-1211

/retest

/retest

lgtm

@ecordell Is this good to merge?

/lgtm

authors: alecmerdler dinhxuanvu ecordell


text:
Gopkg.*,vendor: Bump the openshift client-go and it's dependencies to the release-4.2 branch.

In the current state of things, the openshift/api is a transitive dependency of the openshift/client-go and it's using the v3.9.0 release branch, which doesn't exist anymore. This would update the current vendoring to pin the openshift/client-go to use a specific branch instead of master and override the requisite openshift/api package to also use the release-4.2 branch, instead of a non-existent one, should resolve that problem.

/lgtm

repo: operator-framework/operator-metering


text:
Only add explicit -mod=vendor if needed

Description of the change:
-mod=vendor is not needed if it's already set in GOFLAGS. So let's not
set it unless it's needed.
This is an issue for commands such as go test and go vet (
see https://github.com/golang/go/issues/32471 ). This avoids such an
issue.
Motivation for the change:
With the enforcement of GOFLAGS=-mod=vendor in openshift, some projects got broken given that environment variable being set by default and operator-sdk setting that explicitly if the vendor directory exists..

@estroz thanks for the suggestions!

repo: operator-framework/operator-sdk


text:
kustomize provisioner

Signed-off-by: akihikokuroda akuroda@us.ibm.com
Add kustomize provisioner
It supports following bundledeployment:
apiVersion: core.rukpak.io/v1alpha1
kind: BundleDeployment
metadata:
  name: my-kustomize
spec:
  provisionerClassName: core-rukpak-io-kustomize
  config:
    path: dev
  template:
    metadata:
      labels:
        app: my-kustomize
    spec:
      provisionerClassName: core-rukpak-io-kustomize
      source:
        git:
          ref:
            branch: main
          repository: https://github.com/akihikokuroda/kustomize
          directory: ./manifests
        type: git

Closes #572

Still need to play around with this, but the overall direction makes sense. I'd like to clarify the role of the spec.confg["path"] field a bit more so I can understand how that interacts with the kustomize manifests being provided to the BD.

@timflannagan Thanks for review!  The path is required field.  You may set it to dev, production,... in the example repo

I didn't realized that messages have been changed and caused e2e error.  I fix the error, too.

authors: akihikokuroda timflannagan

repo: operator-framework/rukpak


text:
Non-FD examples

Some trivial examples showing how to express basic linear algebra operations

Codecov Report

Merging #514 into master will decrease coverage by 0.02%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master     #514      +/-   ##
==========================================
- Coverage   86.48%   86.46%   -0.03%
==========================================
  Files          73       73
  Lines        6297     6300       +3
  Branches     1286     1287       +1
==========================================
+ Hits         5446     5447       +1
- Misses        674      676       +2
  Partials      177      177

Impacted Files
Coverage Δ

devito/dimension.py
95.13% <33.33%> (-1.32%)
:arrow_down:

Continue to review full report at Codecov.

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

@mloubout can you take a final look? I addressed your comments (dumb me) and added one final example

Looks good. Maybe for the future add some tests and run the examples on non-zeros.

Merged.

authors: FabioLuporini codecov-io mloubout

repo: opesci/devito

license: mit


text:
security/acme-client: During acme.sh execution DNS resolution using internal DNS server times out

Describe the bug
While the acme.sh is executed for a single certificate renewal DNS requests on the OPNsense CLI to the private DNS servers are timing out. The renewal fails.
To Reproduce
Steps to reproduce the behavior:

Setup OPNsense with a LAN and WAN network
Configure a DNS server in OPNSense that resides on the LAN network, but goes through the OPNsense to access DNS servers on the WAN side (public DNS like 8.8.8.8)
Configure a HTTP-01 validation method on the CARP WAN IP of the OPNsense active-passive cluster
Configure a certificate for a DNS entry for the CARP IP of the WAN interface
While executing a forced re-issue of the certificate try resolving internal or external FQDNs

Expected behavior

DNS resolution should still function while re-issuing a certificate
Re-issue fails, if there is no public DNS server like 8.8.8.8 configured

Relevant log files
Excerpt from /var/log/acme.sh.log
...
[Sun Apr  7 12:20:51 CEST 2019] RSA key
[Sun Apr  7 12:20:54 CEST 2019] GET
[Sun Apr  7 12:20:54 CEST 2019] url='https://acme-v01.api.letsencrypt.org/directory'
[Sun Apr  7 12:20:54 CEST 2019] timeout=
[Sun Apr  7 12:20:54 CEST 2019] _CURL='curl -L --silent --dump-header /var/etc/acme-client/home/http.header  -g '
[Sun Apr  7 12:21:59 CEST 2019] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 6
[Sun Apr  7 12:21:59 CEST 2019] ret='6'
[Sun Apr  7 12:21:59 CEST 2019] Can not connect to https://acme-v01.api.letsencrypt.org/directory to get nonce.
[Sun Apr  7 12:21:59 CEST 2019] Can not get domain new authz.
[Sun Apr  7 12:21:59 CEST 2019] pid
...

Environment
OPNsense 19.1.4 (amd64, OpenSSL).

@stumbaumr To be honest, this looks like a configuration error. I assume your DNS configuration has one or two issues.
acme.sh (and curl) uses the configured resolvers from /etc/resolv.conf. Make sure that these DNS resolvers accept queries from the firewall. I'd suggest to connect to the CLI and test with curl:
curl -v http://letsencrypt.org

authors: fraenki stumbaumr

repo: opnsense/plugins


text:
Caddy Widget Wildcard Fix

Currently the /api/caddy/reverse_proxy/get endpoint displays wildcard domains as '*.domain.com', however the  /api/caddy/diagnostics/certificate endpoint displays wildcard 'wildcard_.domain.com'. The net effect of this is the widget shows: 'Caddy does not manage any automatic certificates'.
The function responsible for this is https://github.com/opnsense/plugins/blob/06a28c3496eabdffc1216a8630b573a4f6c2df2b/www/caddy/src/opnsense/www/js/widgets/CaddyCertificate.js#L50
This PR adds the capability to match on 'wildcard_'
Linked Issue: https://github.com/opnsense/plugins/issues/4400

Hey thanks for the PR but I already fixed it :)
https://github.com/opnsense/plugins/pull/4385
you can install that patch with:
opnsense-patch 6d79d32ea8e94e522e53d16d6c7871414340110c

Hey thanks for the PR but I already fixed it :)
#4385
you can install that patch with:
opnsense-patch 6d79d32ea8e94e522e53d16d6c7871414340110c

Ah thanks I did not see that

NP, thanks for your contribution, appreciate the effort :)

authors: Monviech dcrdev


text:
Improve performance when saving large files

Currently, saving large files takes a few seconds. I attempted to track down which operations are expensive on a 250mb (uncompressed size) project:

Copying/moving data from frontend to backend: 1.52 seconds. This was measured by printing the timestamp before window.electronAPI.saveFile is called and another timestamp after entering the save file listener callback
JSON.stringify(outputfileData): 0.51 seconds
Zipping the file: 1.10 seconds sync + 2.26 seconds async. Even though zipping is done async on a worker thread, we first need to copy all data to the worker. I believe this copying operation blocks the main thread for 1.1 seconds.

The code I used for timing can be found on this branch

Another possible idea: keep the part of the state necessary to write the output file also in the BE, in a child thread. When saving, the action input is also sent to the BE, causing the same changes in the child thread that are then written to a file without sending copies around.

For the possible other library, see https://github.com/opossum-tool/OpossumUI/issues/1893

The above solutions in table form:

strategy
1. Copying/moving data from frontend to backend: 1.52 seconds.
2. JSON.stringify(outputfileData): 0.51 seconds
3. Zipping the file: 1.10 seconds sync + 2.26 seconds async.

Send Diff to BE instead of whole manualAttributions + ...
<<1s

Do state changes on save in the BE
in parallel to 3

Do state changes on save in FE and BE
0

Send output data from FE to BE as string
before becomes much smaller, possibly by a factor 2 to 4

-------------
-------------
-------------
-------------

Use a library that does not re-zip the input file

might be about 2s from 3. before, might be slim to none

Do not zip output syncronously

<<1s

If changes are followed in BE and FE, how is consistency guaranteed? Are all these requests happening in a synchronous thread and is the ordering guaranteed?

Best solutions for reducing the time before creating the file are: diff and double calculation

The performance in the main thread is acceptable, especially because it does not actually block the renderer process.
The issue with slow performance, i.e. blocks in the renderer process is because of the vast amount of data (sometimes multiple GB) that the UI needs to handle. Expensive calculations that belong into the main thread are performed by the renderer thread.
None of the suggestions of this task will fix this issue.

authors: MarkusObendrauf leslielazzarino maxhbr mstykow

repo: opossum-tool/OpossumUI


text:
Migrate to mdoc

This PR closes #818.
For some reason the following snippet does not compile (prism.md:120):
import monocle.macros.GenIso

val jNum: Prism[Json, Double] = GenPrism[Json, JNum] composeIso GenIso[JNum, Double]
val jNull: Prism[Json, Unit] = GenPrism[Json, JNull.type] composeIso GenIso.unit[JNull.type]

Error
error: Error while emitting prism.md
assertion failed:
Trying to access the this of another class: tree.symbol = class Session$App, class symbol = <$anon: monocle.PPrism> compilation unit: prism.md
while compiling: prism.md
during phase: jvm
library version: version 2.13.1
compiler version: version 2.13.1
last tree to typer: TypeTree(class TPrintColors)
tree position: line 145 of prism.md
tree tpe: pprint.TPrintColors
symbol: case class TPrintColors in package pprint
symbol definition: case class TPrintColors extends Product with Serializable (a ClassSymbol)
symbol package: pprint
symbol owners: class TPrintColors
call site: <$anon: Function1> in package repl in package repl
== Source file context for tree position ==
142 val jNum: Prism[Json, Double] = GenPrism[Json, JNum] composeIso GenIso[JNum, Double]; $doc.binder(jNum, 2, 4, 2, 8)
143 $doc.endStatement();
144 $doc.startStatement(3, 0, 3, 92);
145 val jNull: Prism[Json, Unit] = GenPrism[Json, JNull.type] composeIso GenIso.unit[JNull.type]; $doc.binder(jNull, 3, 4, 3, 9)
146 $doc.endStatement();
147 $doc.endSection();
148

Thus I moved the problematic part to the non-mdoc statement.

@iRevive Thanks! Sorry, I missed the notification, I worked on something similar in parallel.

authors: iRevive julien-truffaut

repo: optics-dev/Monocle

license: MIT


text:
feat(fsc): Integrate feature file support for testing POC - WIP

Summary

Added support for executing BDD tests directly through feature files using godog package.
Current implementations include:

Support for is_feature_enabled and all get_feature_variable API's.
Support for dispatched_events and listeners and their Subset comparison.
Support added for Template parsing for the feature-files.
Currently, only verified execution of the given feature files:
features/get_feature_variable/feature_rollouts/audience_targeting.feature
features/is_feature_enabled/feature_rollouts/audience_targeting.feature

TODO

Verify execution of all Feature-files and add missing implementations.
Add support for rest of the API's.
Add support for DFM, event-batching etc.

@mikeng13 am working on filtering out output to just show only failed scenarios.

repo: optimizely/go-sdk


text:
1.4.x

Created the 1.4.x branch, pulled directly from tot of master. Also bumped the version numbers to 1.4.0, and updated the universal framework and podspec files.

TEST:

sh ./Scripts/build_all.sh PASSED
8 iOS test suites PASSED

Applied P.R. #182 touch ups with Alda Luong's approval.
1.4.0 is substantially identical to the D17811 and D17812 changes which Kelly Roach
has already code reviewed, tested, and approved.

authors: alda-optimizely kellyroach-optimizely

repo: optimizely/objective-c-sdk


text:
Update to egui 0.14.0 and bump version to 0.6.0

Hot off the presses!

Oops, I didn't noticed that when maked the release 😓
So, 0.6.0 is published.

authors: emilk optozorax

repo: optozorax/egui-macroquad


text:
WMS: 11496 : Implementing Access Controls using Oracle Access Governance

Add here your WMS ID
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[x] All filenames are lower case (including folders, images, files, etc.)
[x] Filenames are descriptive
[x] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[x] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[x] Image references in markdown contain an alternate text

Updated folder accessgovernance-access-controls

repo: oracle-livelabs/security


text:
Feature: Ability to specify 'io.grpc.ClientInterceptor'

It appears there is no way of specifying a io.grpc.ClientInterceptor on the MP Client channel either via config or programmatically.
Environment Details

Helidon Version: 2.0.2
Helidon SE or Helidon MP: MP
JDK version: N/A
OS: N/A
Docker version (if applicable):

Problem Description
This may be a documentation thing, but I can't see away of specifying a io.grpc.ClientInterceptor on Microprofile client. If there is a way of programmatically creating a io.helidon.grpc.client.ClientServiceDescriptor in MP mode that would help. But may want to also have no-arg constructor initialisation from application.yaml. e.g:
grpc:
  channels:
    test:
      host: localhost
      port: 1408
      client-intercptors:
      - com.acme.MyInterceptor

Steps to reproduce
N/A

Digging into the code there does seem to be io.helidon.microprofile.grpc.core.@GrpcInterceptor, io.helidon.microprofile.grpc.core.@GrpcInterceptors and io.helidon.microprofile.grpc.core.@GrpcInterceptorBinding but documentation does seem to be a little thin on how to use them.

I've found a test for Server Interceptors which does shed a little light on usage but nothing for Client. It appears @GrpcInterceptorBinding is used in io.helidon.microprofile.grpc.server.GrpcServiceBuilder but no client equivilent.

@thegridman Can you please respond?
I believe what @dansiviter is asking for is already supported, but I'm not quite certain how to do it using the annotations either  ;-)

authors: aseovic dansiviter

repo: oracle/helidon


text:
DbClient example: wrong table reference fix

Renamed table types as it collides with h2 system table
Added h2 connection options (commented out)
Signed-off-by: Tomas Langer tomas.langer@oracle.com

Will add to db client update PR (native image changes)


text:
Driver doesn't handle vnics with no public IP

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x692c55]

goroutine 1 [running]:
github.com/oracle/oci-flexvolume-driver/pkg/oci/client.(*client).findInstanceByNodeNameIsVnic(0xc4201725a0, 0xc42016c840, 0x7fffe3a9a775, 0x33, 0x0, 0xc4203e00c0, 0x51)
	/home/gbushell/src/github.com/oracle/oci-flexvolume-driver/pkg/oci/client/oci.go:260 +0x305
github.com/oracle/oci-flexvolume-driver/pkg/oci/client.(*client).GetInstanceByNodeName(0xc4201725a0, 0x7fffe3a9a775, 0x33, 0x0, 0x0, 0x0)
	/home/gbushell/src/github.com/oracle/oci-flexvolume-driver/pkg/oci/client/oci.go:362 +0x2e7
github.com/oracle/oci-flexvolume-driver/pkg/oci/driver.OCIFlexvolumeDriver.Attach(0xc420087d70, 0x7fffe3a9a775, 0x33, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/home/gbushell/src/github.com/oracle/oci-flexvolume-driver/pkg/oci/driver/driver.go:94 +0x17c
github.com/oracle/oci-flexvolume-driver/pkg/oci/driver.(*OCIFlexvolumeDriver).Attach(0x91b808, 0xc420087d70, 0x7fffe3a9a775, 0x33, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	<autogenerated>:1 +0xa6
github.com/oracle/oci-flexvolume-driver/pkg/flexvolume.ExecDriver(0x8cab00, 0x91b808, 0xc420080000, 0x4, 0x4)
	/home/gbushell/src/github.com/oracle/oci-flexvolume-driver/pkg/flexvolume/flexvolume.go:178 +0x85d
main.main()
	/home/gbushell/src/github.com/oracle/oci-flexvolume-driver/cmd/oci/main.go:50 +0x226

Fixed by https://github.com/oracle/oci-flexvolume-driver/pull/62

Fixed in 0.5.2

repo: oracle/oci-flexvolume-driver


text:
Multitenant: Usecase 3: Why is secret db-ca and db-tls created in the oprtator namespace?

$subject
https://github.com/oracle/oracle-database-operator/tree/main/docs/multitenant/usecase03
I am not able to find any reference from the operator to the secrets db-ca and db-tls.
Please clarify and document.

We will remove line 203 and 204 from usecase03 makefile in the next few days
201
202 tlssecret:
203         $(KUBECTL) create secret tls db-tls --key="$(SKEY)" --cert="$(SCRT)"  -n $(CDB_NAMESPACE)
204         $(KUBECTL) create secret generic db-ca --from-file="$(CART)" -n $(CDB_NAMESPACE)

authors: mmalvezz rbaumgar

repo: oracle/oracle-database-operator


text:
Issue 979

Enhance WDT help to:

Expand help for a folder:
-- Show the bean help for a folder, when available, at the end of the folder help.
-- Append the "alias offline" default value, when available, for each attribute listed in a folder.
-- Append a "+" at the end of an attribute line when detailed help is available for the attribute.

Provide help for particular attributes:
-- Instead of generating a 'not a folder' error when specifying a path that ends in an attribute:
-- Show bean help and the "alias offline" default value for the attribute.
-- List the legal values for the attribute if it is an enumerated type.

Support an interactive mode.
-- Get the help for multiple attributes and folders using commands like "cd", "ls", "help", and "top".

Examples:
Show known defaults for each attribute listed in a folder:
(Note that this also appends a "+" if full help is available for a particular att.)
$ modelHelp.sh resources:/JMSServer
Attributes and sub-folders for resources:/JMSServer

resources:
    JMSServer:
        'JMSServer-1':
            AllowsPersistentDowngrade:         # boolean           (default=false) +
            BlockingSendPolicy:                # string            +
            BytesMaximum:                      # long              (default=-1) +
            BytesPagingEnabled:                # boolean           (default=false) +
            ... snip ...

            JmsMessageLogFile:
                # see /JMSServer/JmsMessageLogFile

            JmsSessionPool:
                'JmsSessionPool-1':
                    # see /JMSServer/JmsSessionPool

This class represents a JMS server. A JMS server manages connections
and message requests on behalf of clients.

Show help for a particular attribute of a folder:
modelHelp.sh topology:/Server/Log/StdoutSeverity
Attributes and sub-folders for topology:/Server/Log/StdoutSeverity

topology:
    Server:
        'Server-1':
            Log:
                StdoutSeverity: # string

Default=Notice
Legal values:
   'Trace'
   'Debug'
   'Info'
   'Warning'
   'Error'
   'Notice'
   'Critical'
   'Alert'
   'Emergency'
   'Off'

The minimum severity of log messages going to the standard out.
Messages with a lower severity than the specified value will
not be published to standard out.

Access interactive help starting at directory 'top':
modelHelp.sh -interactive top
In interactive mode! Type 'help' for help.
[top] --> help

Commands:

  ls                      - list contents of current location
  top, cd, cd /, cd top   - go to "top"
  cd x[/[...]]            - relative change (go to child location x...)
  cd section[:/[...]]     - absolute change (go to exact section and location)
  cd ..                   - go up
  history                 - history of visited locations
  exit                    - exit

Sections:

 domainInfo, topology, resources, appDeployments, kubernetes

Example:

  cd topology:/Server/Log/StdoutSeverity

[top] -->

Kudos, SonarCloud Quality Gate passed!
  0 Bugs   0 Vulnerabilities   0 Security Hotspots   110 Code Smells
 20.6% Coverage  0.0% Duplication

The 110 new code smells in Sonar also need to be cleaned up as much as is possible.

@tbarnes-us I clicked the wrong button and accidentally closed this PR, please reopen

modelHelp.sh /Server

interactive and the normal command model path should work the same.

@ddsharpe I have pushed a commit that should partly fix the problem by printing an error message instead of crashing for the case of specifying a path beginning with a forward slash '/x...' where x is not a section name.  I'll start looking into honoring such paths tomorrow - but may not be able to come up with a solution soon.

authors: ddsharpe robertpatrick tbarnes-us

repo: oracle/weblogic-deploy-tooling


text:
Create Team Management Page

This will be to manage team information

Duplicate of #326

repo: orange-alliance/the-orange-alliance


text:
Update Referrers API to match RC.1

Resolves #188

@m5i-work just want to make sure you are aware of, there is a change in rc1 spec regarding to pagination. The link url has been changes to relative url. https://github.com/oras-project/artifacts-spec/blob/v1.0.0-rc.1/manifest-referrers-api.md#paging-results
Not sure if existing code can handle both. You may consider to incorporate in current or future pr.

Note: Since this PR is for rc, let's merge it after #195

There are 8 commits in this PR. It is recommended to rebase and squash them into one.

It's okay since oras only allows "squash and merge" so that the main branch is always clean.

authors: m5i-work northtyphoon shizhMSFT

repo: oras-project/oras-go


text:
Indicate possibility to update if new update available

Description
Prompts only in a selection of views as to not interrupt users during work.
Closes: #414
The easiest way to test things is to change this line to something like:
        return {"version": "v2020.01.1"}

This should trigger the update dialog.
Checklist

[X] The PR branch is set up to merge into dev instead of master.

For future reference, this was the line to change to test this feature:
https://github.com/orchest/orchest/blob/354481ff355313b922f1f23a1614a95a5d539326/services/orchest-webserver/app/app/views/views.py#L239

authors: astrojuanlu yannickperrenet

repo: orchest/orchest


text:
WIP: support testing both db backends

Proposed changes
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to
that issue.
Types of changes
What types of changes does your code introduce to the project: Put
an x in the boxes that apply

[ ] Bugfix (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 not work as expected)

Checklist
Put an x in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to
ask. We're here to help! This is simply a reminder of what we are going
to look for before merging your code.

[ ] I have read the CONTRIBUTING doc
[ ] I have signed the Contributor License Agreement
[ ] I have updated the RELEASE NOTES
[ ] I have added tests that prove my fix is effective or that my
feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in
downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion
by explaining why you chose the solution you did and what alternatives
you considered, etc...

@Cerfoglg to be sure api works fine also with postgres, i added a test configuration to use postgres instead sqlite. this anyhow creates some errors with delete operations :/ any clue?

@Cerfoglg to be sure api works fine also with postgres, i added a test configuration to use postgres instead sqlite. this anyhow creates some errors with delete operations :/ any clue?

It was due to deletes not being set to cascade with the policy to modes and agents tables, so foreign key constraints were being violated. I pushed a commit to set it.

repo: orchestracities/anubis


text:
SubMenu group, global jQuery

Codecov Report

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

@@            Coverage Diff            @@
##             master     #709   +/-   ##
=========================================
  Coverage     61.96%   61.96%
  Complexity      873      873
=========================================
  Files           135      135
  Lines          2742     2742
=========================================
  Hits           1699     1699
  Misses         1043     1043

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 f3170b0...4ef69bd. Read the comment docs.

authors: PSalador codecov-io

repo: orchidsoftware/platform


text:
Can't read the inline code due to tomorrow-night.css

Not sure if I'm the only one running into this issue.

Fixed in #4090

authors: oxSaturn raphjaph

repo: ordinals/ord


text:
Merge updates into orm

This branch has updates from the synced fork of the upstream project, but we typically point SPM to the orm branch; the coinciding PR for this is currently pointed to the ticket branch, and this will instead allow us to point it to orm (after this is merged).

So, how did you merge the newest changes on main in the original repo into your PR branch? In the past, what we've done is merge origin/main into orm (see commit 022ba98 or 70638ab. ). The last successful commit we had been using was ce751cc, which pre-dated us merging in origin/mainin70638ab, because that newer merge broke the web view snapshots.  If that issue is fixed now, then we can definitely move to a newer version of the library.  The way the git history looks right now, though, is not a merge of mainintoorm`, but rather all of the newer changes in the remote repo showing up in your PR branch, which seems a bit confusing -- it makes it less clear where we've chosen to move to the newer version of the remote library by not having a merge from main.

Okay, so we're keeping main up to date with upstream, and just merging in to orm when it's time for us to update?

Yup... that had been our plan all along, and it fell apart when the "latest" snapshot library couldn't pass our CI.  So, we've been stuck on an older merge point, even though main was newer.

Okay, cool — I'll close this, and open up a PR for that. Thanks!

authors: awaltzforvenus lj-dickey


text:
dependency questions

When using the tool in cmd way, we should provide classpath parameter. What if the dependency class itself need to be translated to java6 grammar first? Should we totally understand the compile chain and compile the files one by one in order.

You should either first backport every dependency, or combine them into one uberjar and backport it as a whole (Retrolambda doesn't yet support processing JAR files, so you'll need to unpack the JAR to process the .class files it contains).

authors: aaltonenzhang orfjackal

repo: orfjackal/retrolambda


text:
🛑 TTS (Oribi Speak talsyntes) is down

In bfc0b22, TTS (Oribi Speak talsyntes) ($TTS_ENDPOINT/speak) was down:

HTTP code: 500
Response time: 5921 ms

Resolved: TTS (Oribi Speak talsyntes) is back up in 360a635.

repo: oribisoftware/upptime


text:
🛑 Marketing Website (oribi.se) is down

In c6b95f9, Marketing Website (oribi.se) (https://oribi.se) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Marketing Website (oribi.se) is back up in facf85b after 51 minutes.


text:
[bug]  sql SELECT via HTTP GET returns always only 20 results

Hi,
thank you for this great DB !!!
sql SELECT via HTTP GET (query) always returns 20 results (even if LIMIT is set ie. 200)
SELECT via HTTP POST (command) and Binary sql select both work fine.
I've tried this on 2.0-M3 and  2.0-rc1

Note that using LIMIT in the SQL part of the URL does nothing, you have to use the / in the end of URL. Where did you specify LIMIT?
This is slightly confusing though. Probably Orient should apply both (if any), the SQL one and then the URL one, like a subquery.

well, i have tried many variations
ie:
http://mylocal.local:2480/query/mydb/sql/select from MyClass/limit 200
response:
java.lang.NumberFormatException: For input string: "limit"
how is the query supposed to be formatted?

Syntax: http://:[]/query///[/][/]
http://mylocal.local:2480/query/mydb/sql/select from MyClass/200
for more info, see:
http://www.orientechnologies.com/docs/last/orientdb.wiki/OrientDB-REST.html#query

authors: AaronSchulz SpareShade dcardin

repo: orientechnologies/orientdb


text:
SErVER Can not change cache size in runtime because storage engine plocal was not registered

any idea for following issue when start orientdb server for 2.1.7 version.
SErVER Can not change cache size in runtime because storage engine plocal was not registered

@martingg88  This issue is fixed in 2.1.8

fixed.

hey..do u have any idea on following issue. it worked before but now it can't connect to database at all.
Connecting to database [remote:localhost/voyage] with user 'root'...
Error: com.orientechnologies.orient.core.exception.OStorageException: Cannot open local storage '/var/lib/orientdb/voyage' with mode=rw

Correct access rights for the db files and orientdb?

Or trying to open a db created with a newer version of OrientDB?

access right fro the database folder is absolute correct and it work before.
@luigidellaquila the db is created before version 2.1.8 and have issue when open this database folder with 2.1.8 version. any idea how to solve this issue?

here is the stack ..'
Connecting to database [remote:localhost/voyage] with user 'root'...
Error: com.orientechnologies.orient.core.exception.OStorageException: Cannot open local storage '/var/lib/orientdb/voyage' with mode=rw
Error: com.orientechnologies.common.concur.lock.OLockException: File '/var/lib/orientdb/voyage/internal.cpm' is locked by another process, maybe the database is in use by another process. Use the remote mode with a OrientDB server to allow multiple access to the same database

@martingg88 Do you have open a orientdb console or another instance of orientdb?

i hv reboot my server and open console to connect the database.

@martingg88 You have only one connection open to the db (via console) ?

i dont' have any client connection to db yet.

ok then I don't know.

i run the following in order but have that issue.

./console.sh
connect remote:localhost/voyage username password
3, db is locked

faint faint fain

@martingg88 how do you open the db?

here is the log when i try to manual start the orientdb server.
2015-12-18 08:36:59:763 WARNI {db=voyage} Storage 'voyage' was not closed properly. Will try to recover from write ahead log [OLocalPaginatedStorage]
2015-12-18 08:36:59:763 INFO  {db=voyage} Looking for last checkpoint... [OLocalPaginatedStorage]
2015-12-18 08:36:59:778 INFO  {db=voyage} Found FUZZY checkpoint. [OLocalPaginatedStorage]
2015-12-18 08:36:59:780 INFO  {db=voyage} Data restore procedure from FUZZY checkpoint is started. [OLocalPaginatedStorage]
2015-12-18 08:36:59:783 WARNI {db=voyage} Non tx operation was used during data modification we will need index rebuild. [OLocalPaginatedStorage]
2015-12-18 08:36:59:784 WARNI {db=voyage} Record OFuzzyCheckpointStartRecord{lsn=OLogSequenceNumber{segment=0, position=63020707}} com.orientechnologies.orient.core.storage.impl.local.paginated.wal.OFuzzyCheckpointStartRecord{lsn=null, previousCheckpoint=OLogSequenceNumber{segment=0, position=62880838}} will be skipped during data restore. [OLocalPaginatedStorage]

is there possible the server is locking for the db for recovering process while i'm try to connect db from console.sh?

it's urgent please help for this issue otherwise our server will be down forever.

Yes, you cannot open a connection in console if your server is running.

Hi @martingg88
does it open correctly with 2.1.7?

yes it work for 2.1.7 and work for 2.1.8 few times then corrupted.

@martingg88 I tried to reproduce the problem locally, but without success.
How big is your db? Can you share it or something that allows me to reproduce it?
Thanks
Luigi

just another thing: when you say that it works a few times, do you mean that if you stop and restart the server then it reconnetcts for a while?
Thanks
Luigi

and again, how did you stop the db? If you hard killed the process, are you giving it time to do the full recovery?

yes...the server try to hard kiled the orientdb process that cause my database corrupted. so what i should to to resolve this issue?

ah, so the server is killing OrientDB process? Did it happen once or is it happening every time you restart the server? This could be a matter of low memory.
Does the db recovery succeed? Could you please post the full console log?
Thanks
Luigi

yes.. the server kill orientdb due to low memory. i don't think it run db recovery succeed. sorry i didn't keep the log.
in case of db recovery fail and corrupt the db, what should i should do to recover the db

in between what is the recommend memory needed to run this orientdb? 1024mb should be enough?

any update on this?

Hi @martingg88 ,
Let's do all steps one by one to recognize reason of your issue.
Do you use Linux/Windows/Mac OS ?

yes...i'm using Linux centos 7 with 2 cores and 512mb RAM

OK.
And if you right now open database you get exception that file is blocked,
do not you ?
Do you open this data database using server and remote: connection or
plocal: connection ?
On Tue, Dec 22, 2015 at 5:02 AM martingg88 notifications@github.com wrote:

yes...i'm using Linux centos 7 with 2 cores and 512mb RAM
—
Reply to this email directly or view it on GitHub
https://github.com/orientechnologies/orientdb/issues/5482#issuecomment-166490072
.

--
Best regards,
Andrey Lomakin, R&D lead.
OrientDB Ltd
twitter:@Andrey_Lomakin linkedin:https://ua.linkedin.com/in/andreylomakin

i have not idea what cause the issue. The issue was gone after i restart my server few times.
Anyway, what is the recommended hardward specification to run your orientdb at linux server?

Fixed in latest 2.1.x version

authors: StarpTech laa luigidellaquila martingg88


text:
fix #245

https://github.com/orionjs/orion/issues/245
Sorry, I know the instructions say not to make a pull request to master. Wasn't sure what branch to make a PR to. I followed the same pattern that's used in admin.js for defining routes and it works fine with no errors and shows the loading template as well.

Great!

authors: fuzzybabybunny nicolaslopezj

repo: orionjs/orion


text:
My items showing blank with no results

Here is my set up:
my returned firebase array:
statuses:
{
0011381882781204bfe840813d300cfbaddclose
 createdAt: 1486903163596
 photoUrl: "https://firebasestorage.goo/b/eno..."
 rating: 0
 sid: "0011381882781204bfe840813d300cfb"
 status: "Current Local Time in Madrid, SpainCurrent Loca..."
 tags: "blog"
 type: "Gossip"
 uid: "f1MPKQcYzvYxFTkA9vd"
},
{
 createdAt: 1486897514249
 photoUrl: "https://firebasestorage.googlea..."
 rating: 0
 sid: "1f9b4f300264255f3cf902ad4b89d240"
 status: "A Good Titile Will Make a Difference A Good Tit..."
 tags: "blog"
 type: "Opinion"
 uid: "f1MPKQcYzvYxFTkA9v3"
 updatedAt: 1486897514249
}

My template view:
<div class="ms-home search-results"
         infinite-scroll
         [infiniteScrollDistance]="scrollDistance"
         [infiniteScrollThrottle]="throttle"
         (scrolled)="onScrollDown()">
      <masonry [useImagesLoaded]="true">
        <masonry-brick class="col-md-4" *ngFor="let status of loadStatuses">
        <app-homecard
        [status]="status"
        >
       </app-homecard>
        </masonry-brick>
      </masonry>

component class :
ngOnInit() {

   this.statusService.getStatus()
    .subscribe(statuses => { this.statuses = statuses;
      if(this.statuses){
        this.statusesOk = true;
       this.addItems(0, this.sum);  // I check if the statuses are loaded
      }
 });
}
addItems(startIndex, endIndex) {
    if(this.statusesOk)
    {
      for (let i = 0; i < this.sum; ++i) {
      this.loadStatuses.push([i, ' ', this.generateArray()].join(''));
    }
  }
  }
  generateArray() {
    return this.statuses;
  }
  onScrollDown () {
    // add another 5 items
    const start = this.sum;
    this.sum += 5;
    this.addItems(start, this.sum);
  }

This just shows empty boxes in my view and when I scroll down the boxes just keep adding indefinitely. I don't exactly what am doing wrong. Any help will be appreciated!

this seems like it has something to do with the masonry component's you're using. please consult the plunkr examples.

authors: ericel orizens


text:
Do you have any plan to publish v1.0 to RubyGems?

Hi, thank you for providing the useful library!
We would like to handle multiple result files and found the usage in the current master. However, it seems v1.0 hasn't been released yet.
https://rubygems.org/gems/danger-junit
Is there any concern to block the release? Thanks.

BTW, i'm currently using gem 'danger-junit', git: 'https://github.com/orta/danger-junit', ref: '32fc5d2c026604a0880a3901783628dab06e4877' for now.

Shipped!

authors: jmatsu orta

repo: orta/danger-junit


text:
Add Bassem Riahi to contributors

Update readme file by adding my self to the contributors.

/easycla

repo: ortelius/ortelius


text:
Support response_type=code id_token

Hi there!
Hydra returns The authorization server does not support obtaining a token using this method when I pass response_type=id_token%20code to the authorization endpoint.

https://github.com/ory-am/fosite/pull/131

Verified, works.

authors: arekkas janekolszak

repo: ory-am/hydra


text:
docs: add license header to source files

closes #9

LGTM

authors: tacurran zepatrik

repo: ory/closed-reference-notifier


text:
Project won't open - TypeError: Cannot read property 'id' of undefined

Hi,
My project has stopped rendering. I haven't made any changes to files.
Environment: MacOSX Sierra
The following is displayed on the editor:
TypeError: Cannot read property 'id' of undefined
    at renderEditor (/Applications/ORY Sites.app/Contents/Resources/app.asar/transpiled/server/index.js:121:205)
    at Layer.handle [as handle_request] (/Applications/ORY Sites.app/Contents/Resources/app.asar/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/Applications/ORY Sites.app/Contents/Resources/app.asar/node_modules/express/lib/router/index.js:317:13)
    at /Applications/ORY Sites.app/Contents/Resources/app.asar/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/Applications/ORY Sites.app/Contents/Resources/app.asar/node_modules/express/lib/router/index.js:335:12)
    at next (/Applications/ORY Sites.app/Contents/Resources/app.asar/node_modules/express/lib/router/index.js:275:10)
    at SendStream.error (/Applications/ORY Sites.app/Contents/Resources/app.asar/node_modules/serve-static/index.js:121:7)
    at emitOne (events.js:96:13)
    at SendStream.emit (events.js:188:7)
    at SendStream.error (/Applications/ORY Sites.app/Contents/Resources/app.asar/node_modules/send/index.js:282:17)
    at SendStream.onStatError (/Applications/ORY Sites.app/Contents/Resources/app.asar/node_modules/send/index.js:433:12)
    at next (/Applications/ORY Sites.app/Contents/Resources/app.asar/node_modules/send/index.js:771:28)
    at /Applications/ORY Sites.app/Contents/Resources/app.asar/node_modules/send/index.js:779:23
    at FSReqWrap.oncomplete (fs.js:112:15)

Thanks

Could you share the project files with me?

authors: arekkas hemantasapkota

repo: ory/editor


text:
Update tutorials.md

Just adding a quick note into the docs, to avoid a head scratching bug I got lost in for a couple of hours!

Thanks!

authors: arekkas simlrh


text:
Additional flow in the webhook creation form

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] This issue affects my Ory Network project.
[X] I have joined the Ory Community Slack.
[X] I am signed up to the Ory Security Patch Newsletter.

Describe the bug
Hello,
I've been trying to setup a webhook in the console:

You can additionally select login/registration type for which you want to setup a new Action

This sentence sounds like it is optionnal to select a flow, so I didn't and I was thinking the hook would be fired with all the flows
After completing the form the hook is not fired when performing registration with email+pwd via the ory ui.
Here is a part of the config I got with ory cli:
"registration": {
              "after": {
                "hooks": [
                  {
                    "config": {
                      "auth": {
                        "config": {
                          "in": "header",
                          "name": "<edited>",
                          "value": "<edited>"
                        },
                        "type": "api_key"
                      },
                      "body": "https://storage.googleapis.com/bac-gcs-production/20e5c8ac40a7abc29df6b1cd897959c46178c241e74cb6d49ffc149bbc0cd21ddd9d822c08034c986e4c50661915288bf0f3cdb25ebb87c03c419cc19b1a99ed.jsonnet",
                      "can_interrupt": false,
                      "method": "POST",
                      "response": {
                        "ignore": true,
                        "parse": false
                      },
                      "url": "https://<edited>/ory-hook"
                    },
                    "hook": "web_hook"
                  }
                ],
                "oidc": {
                  "hooks": [
                    {
                      "hook": "show_verification_ui"
                    },
                    {
                      "hook": "session"
                    }
                  ]
                },
                "password": {
                  "hooks": [
                    {
                      "hook": "show_verification_ui"
                    }
                  ]
                },
                "webauthn": {
                  "hooks": [
                    {
                      "config": {
                        "auth": {
                          "config": {
                            "in": "header",
                            "name": "<edited>",
                            "value": "<edited>"
                          },
                          "type": "api_key"
                        },
                        "body": "https://storage.googleapis.com/bac-gcs-production/20e5c8ac40a7abc29df6b1cd897959c46178c241e74cb6d49ffc149bbc0cd21ddd9d822c08034c986e4c50661915288bf0f3cdb25ebb87c03c419cc19b1a99ed.jsonnet",
                        "can_interrupt": false,
                        "method": "POST",
                        "response": {
                          "ignore": true,
                          "parse": false
                        },
                        "url": "https://<edited>/ory-hook"
                      },
                      "hook": "web_hook"
                    },
                    {
                      "hook": "session"
                    }
                  ]
                }
              },
              "before": {
                "hooks": []
              },
              "enabled": true,
              "ui_url": "/ui/registration"
            },

It looks like the hook has been registered once globaly and once for webauthn
If I setup another hook and specificaly choose password, then I get the hook fired as expected.
"registration": {
              "after": {
                "hooks": [],
                "oidc": {
                  "hooks": [
                    {
                      "hook": "show_verification_ui"
                    },
                    {
                      "hook": "session"
                    }
                  ]
                },
                "password": {
                  "hooks": [
                    {
                      "hook": "show_verification_ui"
                    },
                    {
                      "config": {
                        "auth": {
                          "config": {
                            "in": "header",
                            "name": "<edited>",
                            "value": "<edited>"
                          },
                          "type": "api_key"
                        },
                        "body": "https://storage.googleapis.com/bac-gcs-production/20e5c8ac40a7abc29df6b1cd897959c46178c241e74cb6d49ffc149bbc0cd21ddd9d822c08034c986e4c50661915288bf0f3cdb25ebb87c03c419cc19b1a99ed.jsonnet",
                        "can_interrupt": false,
                        "method": "POST",
                        "response": {
                          "ignore": true,
                          "parse": false
                        },
                        "url": "https://<edited>/ory-hook"
                      },
                      "hook": "web_hook"
                    }
                  ]
                },
                "webauthn": {
                  "hooks": [
                    {
                      "hook": "session"
                    }
                  ]
                }
              },
              "before": {
                "hooks": []
              },
              "enabled": true,
              "ui_url": "/ui/registration"
            },

Should I create 3 different hooks ? Should the additionnal flow selection be mandatory in the form ? Or something else ?
Thank you
Reproducing the bug
Create an After Registration hook without selecting and additionnal flow, see above
Relevant log output
No response
Relevant configuration
No response
Version
ory cloud
On which operating system are you observing this issue?
None
In which environment are you deploying?
Ory Network
Additional Context
No response

Duplicate of https://github.com/ory/kratos/issues/3352

authors: alnr tkjwa

repo: ory/network


text:
Add an option for light themed UI

This also sets up a dark and light material theme for v21 and later
Signed-off-by: Jim Ramsay i.am@jimramsay.com

I would love to be able to change the colour / theme / opacity. I assume this would allow that. Can it be allowed through?

Closing this PR, as it doesn't seem to be wanted.

authors: fraserbooth lack

repo: oryanm/TrelloWidget


text:
ITR_UI.py version 2.0 needed

One of the consequences of the templates-v2-scopes branch is that the tool's handling of scopes has changed.  In the past, the tool required the user to stipulate for some operations (such as calculation of temperature scores) which scopes the user wanted to use for calculations.  In other cases, the interface allowed the user to pick a single scope for a given operation.  But in all cases, the tool never considered the possibility that a given set of scopes may or may not be available on a sector-by-sector basis, nor did it consider that the users themselves may not be aware of what scopes a given benchmark covers or does not cover on a sectoral and regional basis.
In the templates-v2-scopes branch, the tool now uses the convention that when scopes=None, it means "calculate for all scopes covered by the benchmark", which means that a list of N companies could return more than N rows of data (for OECM, a lot more).  There are two cases the GUI should fundamentally handle (which may require further changes to the underlying tool code):

Displaying the results of the "most complete" scope calculation.  In this case, when the tool returns multiple rows of scope data, the GUI will select the one row that covers the temperature score most completely.  In the case of TPI benchmarks, this will typically be the combined scopes for which the benchmark is defined (Scope 1 for Electricity Utilities, Scopes 1 and 2 for Steel, Scope 3 for Autos, etc).  In the case of OECM, it will be S1+S2+S3 for the normal case and S1+S2 for the "production-centric" case.  All other scopes returned will not be displayed.
Displaying the results as a "composite".  In this case, when a company's temperature score is displayed (such as when they are among the top 4 emitters in their sector), the ITR metric will be shown as a stacked chart, making it possible to see how much each scope the benchmark uses contributors to the overall ITR score.  In the case of TPI benchmarks that measure only a single scope, only that scope will be displayed (with some characteristic graphical styling of each scope).  In the case of OECM, Scopes 1, 2, and 3 (or Scopes 1 and 2 for production-centric) will be styled and stacked.  Because the "neutral" temperature score is non-zero, some math is needed so that we don't get the nonsense that a 1.5C-aligned S1+S2+S3 is somehow +4.5C.  The math is simple: if S1+S2+S3 is delta_X, then the stacking size of each is weighted as delta_X * Si / (S1+S2+S3)  for i in 1, 2, 3.

Hi, Michael, I will try to find time for this

Substantial progress has just been checked in on the template-v2-scopes branch: https://github.com/MichaelTiemannOSC/ITR/blob/template-v2-scopes/examples/ITR_UI.py

authors: MichaelTiemannOSC alexanu

repo: os-climate/ITR


text:
Request Onboarding to OSC Data Commons

Requesting onboarding for github user: duvalben
Request access to github team: Amundi
View teams here: https://github.com/orgs/os-climate/teams
Onboarding resources:

Data Commons environment setup
credentials.env file

Onboarding checklist:

[x] new user invited to os-climate github org
[x] user invited to requested teams

invites sent - @duvalben to receive credentials please create an issue with this link: https://github.com/os-climate/OS-Climate-Community-Hub/issues/new?assignees=erikerlandson&labels=Bucket-credentials&template=request-credentials-for-an-os-climate-bucket.md&title=Request+credentials+for+an+os-climate+bucket

authors: HeatherAck duvalben

repo: os-climate/OS-Climate-Community-Hub


text:
Add the structure  of the components and Routing

What does this PR do?
This PR is raised to implement the following features: 👍 :

[x] I added the structure of the components and the folders of the app👍.
[x] I used the react-router-dom to navigate into the routes of the app💯.
[x] I used the basic CSS style for styling the components.

Description of the task to be completed 👎

Create the book components
Add the routes for the app using version 6.👎
Use the basic style method for styling the components of the app💯.

How should it be tested
Clone the repository
git clone https://github.com/osamaashraf6/Bookstore

Navigate to the folder
cd Bookstore

Checkout the branch

git checkout structure__routing

#### Thanks for reviewing my PR 😊

Thanks @Gambit142  🙏 for reviewing my pull request I appreciate your review I will work on this part to enhance my code thanks for advising me 👌 💯

Thanks again for reviewing my PR  and have a good day😊

@osamaashraf6, great job implementing the changes. You are heading towards the right direction. 👍


text:
templates/dashboard: filter worker dashboard on arch

Add the ability to filter the build job types by architecture using the arch
dropdown. This depends on: https://github.com/osbuild/osbuild-composer/pull/2845
Test dashboard:
https://grafana.stage.devshift.net/d/image-builder-worker-arch/image-builder-worker-arch-test?orgId=1
This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

This file is not tested by our, it's fine to admin-merge.

authors: kingsleyzissou ondrejbudai

repo: osbuild/osbuild-composer


text:
stages(kickstart): add options "lang", "keyboard", "timezone"

This PR adds the following options to the kickstart stage:

lang
keyboard
timezone

It also adds a simple stage based test but I'm not too happy with it because it only tests the existence of the file.
The context is that we want to support the kickstart options used in
https://github.com/RedHatInsights/edge-api/blob/main/templates/templateKickstart.ks
I would (much ) prefer if something like in https://github.com/osbuild/osbuild/compare/main...mvo5:moar-kickstart?expand=1#diff-1aeb8e81696179e1d6bed004e7dc35b9290e00123a1a4af611cfd406f4530dc3R1 could be added because it would also test for the content of the file (in various permutations). But this (probably) should be done in a separate PR because while there is the seed of a discussion in https://github.com/osbuild/osbuild/issues/1404 the agreement there to move unit tests for stages  into stages/test has some practical issue (e.g. that pylint stages/* will no longer work). Plus there might be a discussion if unit tests for a trivial stage like this are really needed of course :)

Something else we could do to test this stage is pass the resulting kickstart through ksvalidator.

repo: osbuild/osbuild


text:
Add clevis-luks-bind and luks-remove-key stages

These are needed to support encrypted raw images for the simplified installer - require needed stages plumbed into osbuild-composer too once this goes in

This looks good, would love to test it in CI, I have a patch adding it to fedora-ostree-image, but the null pin is not available in Fedora (yet).

lets add tests when the null pin is available in Fedora.

it's gonna be tested anyway from the rhel pipeline in composer till the null pin gets in fedora

authors: gicmo runcom


text:
Added order link field to Part class

(for seagate, it is currently just set to the order link page: http://seagateplastics.com/order.html)

Looks good to me.

authors: Veedrac ihc

repo: oscarkey/extrusionfinder


text:
Finalsweek

Set up createBlockList function to create an array where each item in the array is a possible paragraph or another type of block.  Still working on the other proposed functions to begin formatting in possible paragraphs.  more commits to come!

@oscarlevin
I was working on the error for the else if branch in "convertBlockList".  I think when it rejoins the insideBlock array on returns, in some or all instances when that string is fed back to the "getblocklist" function it is unable to then resplit that text on returns to create the initial "textArray" array that the block runs on.  If that the case a single line of text would cause issues.  I am unable to test at this time as my codespaces are being really weird.  I was able to get some success out of the following code
`else if (block.trim().startsWith("\begin")) {
const blockArray = block.split("\n");
  const insideBlock = blockArray.slice(1, -1);

  result += blockArray[0] + "\n" + convertBlockList(insideBlock) + blockArray[blockArray.length - 1] +  "\n";

  //additional conditionals can be added within this section for /begin blocks to detemine convert|!convert
  // result += block;
}`

it has that issue of not formatting the paragraphs correctly, which is why we then called the convertBlockList(insideBlock) in the getBlockList function before adding to the string.  The error is definitely with the getBlockList call though.
Wanted to at least try something. Felt bad handing it off not working correctly.

repo: oscarlevin/pretext-tools


text:
Update osmosis.zone_chains.json

addition of Andromeda blockchain
Description

Checklist

Adding Assets

If adding a new asset, please ensure the following:

[ ] Asset is registered to the Cosmos Chain Registry.
[ ] Add asset to bottom of zone_assets.json.

[ ] chain_name and base_denom are provided and use values exactly as defined at the Chain Registry.
[ ] path is provided, and the IBC channel referenced is registered at the Chain Registry (unless native to Osmosis).
[ ] osmosis_verified is set to false
[ ] listing_date_time_utc is specified and accurate
[ ] Optional: transfer_methods, peg_mechanism, override_properties, canonical, categories, where necessary (see README for details).

[ ] I am aware that upgrading an asset to 'verified' status requires an additional PR to this repo (checklist below).

Adding Chains

If adding a new chain, please ensure the following:

[ ] Chain is registered to the Cosmos Chain Registry.

Chain's registration must have staking defined, with at least one staking_token denom specified.
Chain's registration must have fees defined; at least one fee token has low, average, and high gas prices defined.

[ ] IBC Connection between chain and Osmosis is registered.
[ ] Add chain to bottom of zone_chains.json

[ ] rpc and rest does not have any CORS blocking of the Osmosis domain, and RPC node has have WSS enabled.
[ ] explorer_tx_url correctly directs to the transaction when the hash is inserted into the URL.

Upgrading Asset to Verified

If upgrading an Asset to Verified, please see the requirements specified at LISTING, and ensure the following:

[ ] Asset is defined thoroughly at the Cosmos Chain Registry.

[ ] A meaningful description (and extended_description, unless: meme, variant, or non-primary chain token).
[ ] Associated socials, including website and twitter (unless: meme, variant, or non-primary chain token).
[ ] Logo Image has a square Aspect Ratio, < 250 KB file size, and appropriate visual contrast with Osmosis Zone colors.

[ ]  Liquidity: This pool contains contains at least $1k USD-worth of liquidity of the asset (Provide Pool ID): ______ (Skip if alloy constituent)

'Verified' Status Validation Checklist (to be completed by Osmosis Zone maintainers):

[ ] Verify appearance and metadata
[ ] Accurate Price
[ ] Trading and routing functionality
[ ] Withdraw and Deposit

[ ] Deposit Transaction URL (if in-app)

Please add the chain info in your original PR that also adds the asset

repo: osmosis-labs/assetlists


text:
[CL Incentives] Re-add JoinTime and FreezeDuration to higher level position object

Closes: #4578
What is the purpose of the change
Removing JoinTime and FreezeDuration broke a number of open PRs, as even though they were technically being double-stored in state as key & value, they still need to be retrievable.

Change Position proto to PositionContent proto (doesn't include jointime and freezeduration)
Make new Position struct in model folder that has the full backwards-compatible position interface (including jointime and freezeduration)
Make GetPosition populate jointime and freeze duration using the parameters that are passed in (should return Position

Brief Changelog

added position struct that contains joinTime, freezeDuration

Testing and Verifying
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)

Just noticed this PR which overlaps with #4573.
That change is needed to correctly implement genesis: https://github.com/osmosis-labs/osmosis/pull/4546
Could you please wait for #4573 to get in? It is the final state we would need for genesis and is going to be broken by this change.
What #4573 does is the following:

proto-generates a Position struct to be added to genesis only
Only stores liquidity as sdk.Dec for position's state value

It seems to me that the ideas of using another Position struct are similar but this would just require resolving more conflicts

Just noticed this PR which overlaps with #4573.
That change is needed to correctly implement genesis: #4546
Could you please wait for #4573 to get in? It is the final state we would need for genesis and is going to be broken by this change.
What #4573 does is the following:

proto-generates a Position struct to be added to genesis only
Only stores liquidity as sdk.Dec for position's state value

It seems to me that the ideas of using another Position struct are similar but this would just require resolving more conflicts

I'm only going to get to #4573 on Monday so if this change is needed for further incentives work, feel free to merge

Just noticed this PR which overlaps with #4573.
That change is needed to correctly implement genesis: #4546
Could you please wait for #4573 to get in? It is the final state we would need for genesis and is going to be broken by this change.
What #4573 does is the following:

proto-generates a Position struct to be added to genesis only
Only stores liquidity as sdk.Dec for position's state value

It seems to me that the ideas of using another Position struct are similar but this would just require resolving more conflicts

sorry about that @p0mvn. I didn't see you PR or else i would've branched off of it. This PR will make lots of other incentives PR backwards compatibility  and fix conflicts therefore @AlpinYukseloglu  and I are pushing to merge this asap. Moving forward will communicate extra just in case

repo: osmosis-labs/osmosis


text:
chore: Add SECUIRTY.md to repo

Closes: #XXX
What is the purpose of the change
Adds SECURITY.md, same as https://github.com/osmosis-labs/osmosis/pull/5004 but with telegram as single point of contact for vulnerablility
Testing and Verifying
This change is a trivial rework / code cleanup without any test coverage.
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

Closing in favor of #6773


text:
plugins

Some packages have differences, like aminoCasing for osmosis vs cosmos packages. We need a way to make this more dynamic per package. Here is a concept:
import { join, resolve } from 'path';
import telescope from '@osmonauts/telescope';
import { camel, snake } from 'case';

const protoDir = resolve(join(__dirname, '..', 'proto'));
const outPath = resolve(__dirname, '..', 'src', 'proto');

telescope({
  protoDir,
  outPath,
  plugins: [
    {
      name: 'aminoCasing',
      plugin: ({ protoPackage }) => {
        if (protoPackage.startsWith('osmosis')) {
          return camel;
        }
        return snake;
      }
    }
  ]
});

hmmmm another idea. maybe we can store some export or configuration inside the protobuf modules on npm https://www.npmjs.com/search?q=%40protobufs

ideas for how we'd specify options for nested packages
const options = {
    includeAminos: false,
    includeLCDClient: false,
    showDate: false,

    protos: {
        cosmos: {
            showDate: true
        },
        'cosmos.v1beta1.tx': {
            includeAminos: true,
        },
        cosmos: {
            v1beta1: {
                tx: {
                    includeAminos: true
                }
            }
        },
        osmosis: {
            aminoCasing: camel
        }
    }
};

getPluginValue ('includeAminos', pkg);

const plugins = [
    {
        name: 'includeAminos',
        plugin: (pkg) => {
            if (pkgbasename(pkg) === 'cosmos') {
                return true;
            }
        }
    },
    // HOW TO JOIN THESE?
    {
        name: 'includeAminos',
        plugin: (pkg) => {
            if (pkgbasename(pkg) === 'osmosis') {
                return true;
            }
        }
    }
]

repo: osmosis-labs/telescope


text:
Go release stuff

This is half of the go release, we build the package and notify the go-oso repo. Then the go-oso repo will download the new version and push it's own tag for it.

Used here
https://github.com/osohq/go-oso/commit/07eece5e272a90d52c243b3eec083fa8f9d95e08

repo: osohq/oso


text:
Volume data can have different resolution for different regions

I am working on an out-of-core volume renderer ( https://github.com/BlueBrain/Livre ) to display different resolutions in different regions of the data. So, I have extended the volume data API slightly to have the resolution of the data as well. It looks like below. For the current API, count = region, where resolution is same with the count but with different resolutions ( count != region ) it will be different. If you have comments, it would be nice to have before I dive deeper.
int ospSetRegion( OSPVolume object,
void *source,
const osp::vec3i &index,
const osp::vec3i &count,
const osp::vec3i &region)

Hi,
you need volumes that are kind of in-homogeneous, i.e. having a different number of voxels in different parts? The main type of volume OSPRay currently uses are structured volumes, that have (by definition) the same density of cells everywhere. Changing that behavior does not seem to be the proper route. However, maybe the following alternatives already work for you:

Why not using many (structured) volumes at once – each can have a different resolution.
How about the AMR volume type – these have adaptive resolution. If that is a match for your requirements we can think of supporting AMR directly in OSPRay.
OoC volume rendering is quite similar to an experimental feature already in OSPRay called data-parallel rendering. Each rendering machine can only access some parts of the volume data.

What is the raw data (volume) size you are targeting with Livre?
Best regards,
Johannes

Note he said "out of core". Ahmet - do I get it right that you want to use this as some form of "level of detail" ? Ie, display a coarser level while the finer is still loading in the background? Send me an email; let's discuss that with the entire group via email (or skype), that'll be faster.

Sorry for the ( very ) late reply.
Here, I understand that you are uploading the data once into the memory once ( if the KNL has a separate memory - i.e KNL PCIex card, this makes a lot of sense ) but in my case I would like to use the blocks already in memory  ( this would be possible when the renderer has full memory access - i.e. KNL as a CPU  ). Here we are using Xeons with AVX and the renderer has access to 128GB memory ( stop me if I am wrong here - 32 bit limit ? ). We can discuss of course !

Hi,
After discussing with @ingowald , we have decided to go a simpler and ( more effective I believe ) solution. So, I am closing this pr. Thanks for the support !
Cheers,

authors: bilgili ingowald johguenther

repo: ospray/OSPRay