Add log-Normal sequence generators

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (3159fbe) 100.00% compared to head (e23b95f) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #36   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           26        27    +1
  Lines          760       822   +62
  Branches        70        73    +3
=========================================
+ Hits           760       822   +62

Files Changed
Coverage Δ

src/startorch/sequence/__init__.py
100.00% <100.00%> (ø)

src/startorch/sequence/lognormal.py
100.00% <100.00%> (ø)

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


Fix documentation

Upgraded Go from version 1.21 to 1.22 and updated various indirect dependencies. Error handling in client_test.go has been enhanced by using the errors.Is function for comparison instead of direct equality check. Fixed minor typos and inconsistencies in the comments of client.go and embed.go.

Thanks for your suggestion


Update Notification?

Is there a way to receive update notifications?
We had two major issues with this solution, both were solved after installing the latest scripts (latest one: Find-AzureRmResource breaking change).
Best, Linard

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 225c9d05-83dd-b006-0025-3753f5ab25bf
Version Independent ID: 9eecef0c-b1cb-1136-faf7-542214492096
Content: Start/Stop VMs during off-hours solution (preview)
Content Source: articles/automation/automation-solution-vm-management.md
Service: automation
GitHub Login: @georgewallace
Microsoft Alias: gwallace

@lin-art
Thanks for the feedback! We are currently investigating and will update you shortly.

@YutongTie-MSFT, reassigning to @georgewallace as I am OOF.
@georgewallace can you please look into this?

@lin-art At this time, updates notifications are not being sent out, docs will be updated when solutions are updated, the most recent updates are live in the document.  I have shared this request with the owners of the solution. #please-close

@lin-art We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Update table in README.md with tutorials

README needs updating to include links to all tutorial files in the repo.

@codeboyfriend sure, go ahead

Thanks for this
I'll make a PR by tomorrow

Can I work on this?

Can I work on this?

Sorry its already assigned.

Thanks for this
I'll make a PR by tomorrow

Hi any updates on the PR? Thanks.

Ohh
Will try it tomorrow... Sorry, for the inconveniences

update to README still needed.


fix(amplify-codegen-appsync-model-plugin): add ownerField to modelgen…

Issue #, if available:
aws-amplify/amplify-js#5687
Description of changes:
amplify codegen models will generate ownerField automatically as an optional string type String in implicit cases and will not override the field if it is defined explicitly for other type in the schema, which allows user to use custom type such as [String!] etc. The changes apply to all the SDKs(js, android and ios)
Sample input
 type Post @model @auth(rules: [
  { allow: owner , ownerField: "customOwnerField1"},
  { allow: owner , ownerField: "customOwnerField2"},
  ]) {
   id: ID!
   name: String!
 }

Sample output for Java
/** This is an auto generated class representing the Post type in your schema. */
@SuppressWarnings("all")
@ModelConfig(pluralName = "Posts", authRules = {
  @AuthRule(allow = AuthStrategy.OWNER, ownerField = "customOwnerField1", identityClaim = "cognito:username", operations = { ModelOperation.CREATE, ModelOperation.UPDATE, ModelOperation.DELETE, ModelOperation.READ }),
  @AuthRule(allow = AuthStrategy.OWNER, ownerField = "customOwnerField2", identityClaim = "cognito:username", operations = { ModelOperation.CREATE, ModelOperation.UPDATE, ModelOperation.DELETE, ModelOperation.READ })
})
public final class Post implements Model {
  public static final QueryField ID = field("id");
  public static final QueryField NAME = field("name");
  public static final QueryField CUSTOM_OWNER_FIELD1 = field("customOwnerField1");
  public static final QueryField CUSTOM_OWNER_FIELD2 = field("customOwnerField2");
  private final @ModelField(targetType="ID", isRequired = true) String id;
  private final @ModelField(targetType="String", isRequired = true) String name;
  private final @ModelField(targetType="String") String customOwnerField1;
  private final @ModelField(targetType="String") String customOwnerField2;
  public String getId() {
      return id;
  }

  public String getName() {
      return name;
  }

  public String getCustomOwnerField1() {
      return customOwnerField1;
  }

  public String getCustomOwnerField2() {
      return customOwnerField2;
  }
//...
//Constructors, getters and builders also get updated. See details in test snapshots.

Sample output for Swift
// swiftlint:disable all
import Amplify
import Foundation

extension Post {
  // MARK: - CodingKeys
   public enum CodingKeys: String, ModelKey {
    case id
    case name
    case customOwnerField1
    case customOwnerField2
  }

  public static let keys = CodingKeys.self
  //  MARK: - ModelSchema

  public static let schema = defineSchema { model in
    let post = Post.keys

    model.authRules = [
      rule(allow: .owner, ownerField: "customOwnerField1", identityClaim: "cognito:username", operations: [.create, .update, .delete, .read]),
      rule(allow: .owner, ownerField: "customOwnerField2", identityClaim: "cognito:username", operations: [.create, .update, .delete, .read])
    ]

    model.pluralName = "Posts"

    model.fields(
      .id(),
      .field(post.name, is: .required, ofType: .string),
      .field(post.customOwnerField1, is: .optional, ofType: .string),
      .field(post.customOwnerField2, is: .optional, ofType: .string)
    )
    }
}

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

in looking at your example, i noticed that your test input is:
  { allow: owner , ownerField: "customOwnerField1"},
  { allow: owner , ownerField: "customOwnerField2"},

Is this a valid use case? I have never seen a case where we would have two different custom owner fields.

The docs describe one such use case where an owner should be able to do perform all operations (create, read, update, delete), but a list of editors should only be able to read and update.

in looking at your example, i noticed that your test input is:
  { allow: owner , ownerField: "customOwnerField1"},
  { allow: owner , ownerField: "customOwnerField2"},

Is this a valid use case? I have never seen a case where we would have two different custom owner fields.

The docs describe one such use case where an owner should be able to perform all operations (create, read, update, delete), but a list of editors should only be able to read and update.

Seems like we should test that case instead?

Should there be a corresponding test for swift visitor as well?

in looking at your example, i noticed that your test input is:
  { allow: owner , ownerField: "customOwnerField1"},
  { allow: owner , ownerField: "customOwnerField2"},

Is this a valid use case? I have never seen a case where we would have two different custom owner fields.

The docs describe one such use case where an owner should be able to perform all operations (create, read, update, delete), but a list of editors should only be able to read and update.

Seems like we should test that case instead?

I include the test cases in the new commit for swift tests.


[Sun/Moon Times] Added date selection dropdown

Description

Add date picker to select a date other than today
Some minor improvements

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer regarding commit 3d67ce8 maybe you should improve your string validation, because if I change the action title to the title you changed it to I get a eslint warning. If I then use the autofix it changes the from to From.

I'll see if we can make a list of approved words, like the example in the tooltip Copy to Clipboard


Use standalone version of Selectize script

Fixes #3002
I plan to add one more commit which adjusts the version of the Selectize JS Library package to <IP_ADDRESS>, and see if that works for upgrading from 9.4.0 to 9.4.1.

😞 update with <IP_ADDRESS> package failed:

DotNetNuke.Data.PetaPoco.PetaPocoHelper - [4] Error executing SQL: ;Exec dbo.AddPackage @0, @1, @2, @3, @4, @5, @6, @7, @8, @9, @10, @11, @12, @13, @14, @15, @16
Cannot insert duplicate key row in object 'dbo.Packages' with unique index 'IX_Packages'.
The duplicate key value is (DNN, Selectize, JavaScript_Library, <NULL>, 0.12.6).
The statement has been terminated.

Hmm, my thought was that this PR would have been for all extension types, but looks like only Modules...
https://github.com/dnnsoftware/Dnn.Platform/pull/2666/files

@bdukes Did you try just using the same version, I have been digging into the installer code to try and find a solution to this and from the looks of it, it checks if the version is >= than the currently installed one and the stored procedure supports creating or updating. This is different from modules package type where the check is > and not >= ...
So I think you could just remove the fourth digit and give a try ...

@valadas weird, that seemed to have worked.  I've removed the version bump from the PR.  If someone else can do a test upgrade (from an older version to 9.4.0, then 9.4.1), that would help verify that it truly fixes the issue.
I'm confused because the whole reason we upgraded the library in the first place in #2907 was because there was a file in the package that wasn't updated during the upgrade to 9.4.0.

Strange, but yeah, I will try a couple different upgrades this weekend. Please do not merge until we get some positive reports on this.

after upgrading from version 9.4 to 9.4.1 I still have two selectize javascript libraries with no trash can to toss one out.  I was trying to dig up how to remove this to see if it cures another issue I am having with a vendor module, noticed the RC1 out so thought I would give it a try.  I have same modules on a seperate site with a fresh copy of 9.4 installed and the vendor module does not have the issue.
I can now view and edit module settings.  Trying to cleanup an older installation along with setup some new ones so I should get a lot of tests in here soon settings things up to give loads of feedback.

Hmm, this is expected since libraries installation does not work like modules, they do not upgrade and you can have multiple versions installed. Also, when the manifest specifies it is a system package, then there is no UI to remove them... So technically, this is by design.
I agree though that this is not perfect since it will add up with each new version, on the other side there might be modules consuming that older version specifically and removing it would be a breaking change for them. I never found it to be a good idea to offer javascript libraries to module developers for this specific reason.

I have upgraded from 9.4.0 to 9.4.1. In the upgraded 9.4.0 I removed the duplicated selectize.js library days ago form Extensions as weell as the unnecessary PersonaBar modules (only one PersonaBar module is listed). When I enter any module settings I still get the following errors in the browser console windows:
Selectize: Dependency MicroPlugin is missing selectize.min.js:3:6108
 selectize.min.js:3:6170
TypeError: w.define is not a function selectize.min.js:4:2404
Make sure you either: (1) are using the "standalone" version of Selectize, or (2) require MicroPlugin before you load Selectize. selectize.min.js:3:6186
ReferenceError: Selectize is not defined dnn.combobox.js:4:5
TypeError: $(...).dnnComboBox is not a function 427:3183:47
TypeError: $(...).dnnComboBox is not a function 427:3210:137
The error doesn't seem fixed... is there a way to fix manually?

Just for the record, out of 3 updated DNN to 9.4.1 only one had the selectize problem solved. The other two were still showing the dependency problem as written in my previous post.
I tried emptying the cache, restarting the application with no luck.
Finally I repaired the installation of selectize from the Extensions the selectize.zip taken from DNN_Platform_9.4.1_Upgrade/Install/JavaScriptLibrary. I emptied the cache, restarted the application and forced reload (CTRL+F5) and the problem went away from the other 2 updated DNN.
So it seems the problem as been actually fixed.


feat: Add errorFilter and warningFilter as common props

Commandeer of #508

Before merging, I just want to walk though the filter logic to ensure it will make sense from the user pov.
For example, if there is an error or warning on a table view, and they filter to a device or access code marked with the error or warning and navigate to the detail view, will they always see the error or warning, or is there a chance it gets filtered out? It would be frustrating if we created a situation where a error/warning was flagged on the table but there was no way to see the issue.


avoid multi accesstokens generated by clients using the same credentials

Hi,I come from China,and I'm not good at English,so I wish you can understand my issues.
according #276 by @dsyer using @EnableTransactionManagement and @Transactional, but can't solve the problem,I having test in github.
I need help,could you help me?

Did you actually create a transaction manager bean anywhere (I didn't see one when I had a quick look)?

I have created PlatformTransactionManager in com.selonj.getstarted.oauth2.config.OAuth2ServerConfig.AuthorizationServerConfig class,and I debug the PlatformTransactionManager and it works,but the test failed

@dsyer，did my issue  solve in 2.0.9 version by simple configuration via transaction management ?

That's what I thought. I haven't had a chance to try your test yet.

@dsyer ,you can clone https://github.com/selonj/getstarted-spring-oauth2.git in branch avoid_multi_accestoken_in_database,help me look at the issue.

We're experiencing the same problem.
We're using the following spring versions:

spring.platform.bom version is 2.0.5.RELEASE
spring-security version is 4.0.4.RELEASE
spring-security-oauth version is 2.0.9.RELEASE

The @EnableTransactionManagement is configured to use datasource transaction manager like the following:
@Bean
@Autowired
public PlatformTransactionManager txManager(DataSource dataSource) {
        return new DataSourceTransactionManager(dataSource);
}

We haven't created a unique constraint on the authentication_id field yet
To reproduce the issue we used two concurrent shell scripts that execute:
watch -n1 "curl 'http://[host]:[port]/oauth/token?grant_type=password&username=[user]&password=[password]' -X POST -H 'Authorization: Basic XXXXXXX==' -vv"

Could you please help to fix the issue in a proper way because from our standpoint it seems to be not a good solution to handle exceptions caused by unique constraint on the authentication_id field?

I managed to solve this issue.
The root cause of the problem is in "check then act" logic of the default org.springframework.security.oauth2.provider.token.store.JdbcTokenStore implementation.
The following steps take place when querying for an access token:

the access token is fetched by id
the access token is removed from the table if it was found at the previous step
finally, the access token is either re-inserted into the table or created depending on whether it previously existed in the table.

A race condition occurs when more then one transaction requests for the same access token.
In order to reproduce this issue, as mentioned in my previous post, I used two concurrent shell scripts that execute the following command:
watch -n1 "curl 'http://[host]:[port]/oauth/token?grant_type=password&username=[user]&password=[password]' -X POST -H 'Authorization: Basic XXXXXXX==' -vv"

Seemingly, the issue is likely to be solved by introducing a row-level lock in the underling RDBMS by substituting the default SELECT statement with a SELECT FOR UPDATE one in the default org.springframework.security.oauth2.provider.token.store.JdbcTokenStore implementation, but it is not the case for the Postgresql implementation.
Because in case of two concurrent transactions one of them succeeds in locking, another is blocked on the same row. According to the "check then act" logic of the org.springframework.security.oauth2.provider.token.store.JdbcTokenStore described above the winning transaction at first removes the access token, then re-inserts it back and finally releases the write lock. The blocked transaction is unlocked but due to PosrgeSQL implementation it doesn't see the newly inserted token and proceeds with creating a new token. As a result a constrain violation exception occurs. More on the default read committed transaction isolation level
So the steps to solve the issue are:

Introduce a unique constraint on the field authentication_id of the oauth_access_token table
Implement a retry logic over the org.springframework.security.oauth2.provider.token.AuthorizationServerTokenServices methods. I accomplished this by introducing an AOP interceptor that wraps all methods of the AuthorizationServerTokenServices interface with a retry logic...

We still have the same behavior under load with the JdbTokenStore. I will try your approach ... thx Rico

Closing this as questions are better suited on Stack Overflow. We prefer to use GitHub issues for bugs and enhancements.

@jgrandja why did you close the issue? it’s not a question it’s a bug isn’t it? I provided a solid reasoning on why it takes place.

@mpryahin It seems you solved it as detailed in this comment?
I'm not sure this is a bug but rather a database-level configuration and/or overall architecture setup. When there are multiple requests (from different application instances) querying the database via JdbcTokenStore, transaction management needs to be configured on the application side and likely at the database level.
If you still feel this is a bug then can you please provide a minimal sample that reproduces the issue and/or specific details in the code that you feel should be fixed.

@jgrandja thanks for taking the time to reply, you're right, I somehow overlooked my latest comment made quite a long time ago, sorry for bothering 🙂


[opendistro-1.11][backport] Add support for ResolveIndexAction handling (#1312)

opensearch-security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly

Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Github Issue # or road-map entry, if available:

Description of changes:

Why these changes are required?

What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)

Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)

TO-DOs, if any: (Please describe pending items and provide Github issues# for each of them)

Is it backport from main branch? (If yes, please add backport PR # and commits #)

By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1397 (b34b11c) into opendistro-1.11 (3643fe7) will increase coverage by 0.06%.
The diff coverage is 26.66%.

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

@@                  Coverage Diff                  @@
##             opendistro-1.11    #1397      +/-   ##
=====================================================
+ Coverage              64.13%   64.19%   +0.06%
- Complexity              3195     3196       +1
=====================================================
  Files                    241      241
  Lines                  16974    16965       -9
  Branches                3047     3044       -3
=====================================================
+ Hits                   10886    10891       +5
+ Misses                  4533     4522      -11
+ Partials                1555     1552       -3

Impacted Files
Coverage Δ

...earch/security/privileges/PrivilegesEvaluator.java
69.23% <21.42%> (+1.85%)
:arrow_up:

...earch/security/resolver/IndexResolverReplacer.java
61.45% <100.00%> (ø)

...earch/security/ssl/util/SSLConnectionTestUtil.java
95.45% <0.00%> (+2.27%)
:arrow_up:

...transport/OpenDistroSecuritySSLNettyTransport.java
73.40% <0.00%> (+4.25%)
:arrow_up:

Continue to review full report at Codecov.

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


Follow-up for cilium ip list identity lookup

Follow-up for #13304 to address review comments post-merge, namely https://github.com/cilium/cilium/pull/13304#issuecomment-700314189 and https://github.com/cilium/cilium/pull/13304#issuecomment-700314867.
The main change is the lookup of all known identities in cilium ip list by default, leading to output such as:
$ cilium ip list
IP                              IDENTITY                                          SOURCE
<IP_ADDRESS>/0                       world
::/0                            world
<IP_ADDRESS>/32                    host
<IP_ADDRESS>/32                   k8s:io.cilium.k8s.policy.cluster=default          k8s
                                k8s:k8s-app=kube-dns
                                k8s:io.kubernetes.pod.namespace=kube-system
                                k8s:io.cilium.k8s.policy.serviceaccount=coredns
<IP_ADDRESS>/32                   host
<IP_ADDRESS>/32                  health
<IP_ADDRESS>/32                  host
<IP_ADDRESS>/32                  health
<IP_ADDRESS>/32                host
<IP_ADDRESS>/32                host
fd00::b/128                     host
fd00::2d7c/128                  health
fd00::9998/128                  k8s:k8s-app=kube-dns                              k8s
                                k8s:io.kubernetes.pod.namespace=kube-system
                                k8s:io.cilium.k8s.policy.serviceaccount=coredns
                                k8s:io.cilium.k8s.policy.cluster=default
fd00::e57e/128                  host
fd00::1:e9b/128                 host
fd00::1:8742/128                health
fd01::b/128                     host
fe80::ccf4:b3ff:fe16:de79/128   host

See commit messages for details.

test-me-please


Android: run at startup

greetings,
for Android, if geofences are registered with the OS then why do you need the permission "run at startup"?

As far I know they were not persisted after reboot in version 4.x. Maybe something has changed since version 5.0, but I am not aware of those changes and I haven't tested if they persist or not on after reboot.

gotcha, thx!


Have you considered to have docker support in order not to pollute the system? Here is my solution.

Have you considered to have docker support? It isn't very difficult to do so, as there is commands in Ubuntu, which can directly be the RUN command in Dockerfile. So just build an image FROM ubuntu:22.10 after which then add the RUN commands. The only thing that has to be put into consideration is display, graphics card and working directory to be mounted onto the docker container, which can be set up in docker-compose.yml file, which you programmers need to work out.
It would be more convenient if you can wrap up the whole program into a deb package.

The window of the program appears then quits immediately just before an error occured when I tried to deploy the program with docker. In theory, this error will occur on every machine powered by any version of Debian or Ubuntu with GUI support and docker preinstalled by the official command curl -fsSL https://get.docker.com | bash -s docker.
That means, if you have the x11-xserver-utils and docker preinstalled on Ubuntu or Debian with GUI support, this error can be reproduced.
My commands:
git clone https://github.com/Anjok07/ultimatevocalremovergui.git uvr
cd uvr
touch Dockerfile
touch docker-compose.yml

then edit the two files and then change to super user mode
xhost +
docker compose up

Error:
Attaching to uvr-uvr-1
uvr-uvr-1  | playsound is relying on another python subprocess. Please use `pip install pygobject` if you want playsound to run more efficiently.
uvr-uvr-1  | 2023-01-11 18:27:59,177 - UVR BEGIN
uvr-uvr-1  | Traceback (most recent call last):
uvr-uvr-1  |   File "/usr/local/lib/python3.10/dist-packages/pyglet/__init__.py", line 336, in __getattr__
uvr-uvr-1  | No splash screen.
uvr-uvr-1  |     return getattr(self._module, name)
uvr-uvr-1  | AttributeError: 'NoneType' object has no attribute 'add_file'
uvr-uvr-1  |
uvr-uvr-1  | During handling of the above exception, another exception occurred:
uvr-uvr-1  |
uvr-uvr-1  | Traceback (most recent call last):
uvr-uvr-1  |   File "/uvr/UVR.py", line 5023, in <module>
uvr-uvr-1  |     root = MainWindow()
uvr-uvr-1  |   File "/uvr/UVR.py", line 842, in __init__
uvr-uvr-1  |     font.add_file(FONT_PATH)
uvr-uvr-1  |   File "/usr/local/lib/python3.10/dist-packages/pyglet/__init__.py", line 342, in __getattr__
uvr-uvr-1  |     __import__(import_name)
uvr-uvr-1  |   File "/usr/local/lib/python3.10/dist-packages/pyglet/font/__init__.py", line 80, in <module>
uvr-uvr-1  |     from pyglet.font.freetype import FreeTypeFont
uvr-uvr-1  |   File "/usr/local/lib/python3.10/dist-packages/pyglet/font/freetype.py", line 41, in <module>
uvr-uvr-1  |     from pyglet.font import base
uvr-uvr-1  |   File "/usr/local/lib/python3.10/dist-packages/pyglet/font/base.py", line 45, in <module>
uvr-uvr-1  |     from pyglet.gl import *
uvr-uvr-1  |   File "/usr/local/lib/python3.10/dist-packages/pyglet/gl/__init__.py", line 95, in <module>
uvr-uvr-1  |     from pyglet.gl.gl import *
uvr-uvr-1  |   File "/usr/local/lib/python3.10/dist-packages/pyglet/gl/gl.py", line 45, in <module>
uvr-uvr-1  |     from pyglet.gl.lib import link_GL as _link_function
uvr-uvr-1  |   File "/usr/local/lib/python3.10/dist-packages/pyglet/gl/lib.py", line 149, in <module>
uvr-uvr-1  |     from pyglet.gl.lib_glx import link_GL, link_GLU, link_GLX
uvr-uvr-1  |   File "/usr/local/lib/python3.10/dist-packages/pyglet/gl/lib_glx.py", line 46, in <module>
uvr-uvr-1  |     glu_lib = pyglet.lib.load_library('GLU')
uvr-uvr-1  |   File "/usr/local/lib/python3.10/dist-packages/pyglet/lib.py", line 164, in load_library
uvr-uvr-1  |     raise ImportError('Library "%s" not found.' % names[0])
uvr-uvr-1  | ImportError: Library "GLU" not found.
uvr-uvr-1 exited with code 1

This is my Dockerfile:
FROM ubuntu:22.10

COPY ./requirements.txt /uvr/requirements.txt

WORKDIR /uvr

RUN apt update && DEBIAN_FRONTEND=noninteractive apt install -y tzdata && \
    apt install -y ffmpeg python3-pip python3-tk && \
    pip3 install -r requirements.txt -i https://pypi.mirrors.ustc.edu.cn/simple

COPY . /uvr

VOLUME [ "/uvr/sources", "/uvr/results" ]

ENTRYPOINT [ "python3" ]

CMD [ "/uvr/UVR.py" ]

And this is my docker-compose.yml:
version: '3.8'

services:
  uvr:
    build: .
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /tmp/.X11-unix:/tmp/.X11-unix
      - ./sources:/uvr/sources
      - ./results:/uvr/results
    environment:
      - DISPLAY=unix:0.0
      - GDK_SCALE
      - GDK_DPI_SCALE
#    deploy:
#      resources:
#        reservations:
#          devices:
#            - driver: nvidia
#              device_ids: [ '0' ]
#              capabilities: [ gpu ]

Besides, my computer has no graphics card.

The window of the program appears then quits immediately just before an error occured when I tried to deploy the program with docker.

Personal point of view, is this because of the splash screen, which shows up before the main program launches? Is it possible that I can get rid of this error when the "splash screen" or typically the "starting page" is set disabled?

The window of the program appears then quits immediately just before an error occured when I tried to deploy the program with docker.

OK, Problem solved. It's raised by a missing package freeglut3-dev.
Now this is my new Dockerfile:
FROM ubuntu:22.10

COPY ./requirements.txt /uvr/requirements.txt

WORKDIR /uvr

RUN apt update && DEBIAN_FRONTEND=noninteractive apt install -y tzdata && \
    apt install -y ffmpeg python3-pip python3-tk freeglut3-dev x11-xserver-utils && \
    pip3 install -r requirements.txt -i https://pypi.mirrors.ustc.edu.cn/simple #This is 中科大 image repository of pip3.
#Change to your own image repository of pip3, or just delete the -i argument if you are not in China.

COPY . /uvr

VOLUME [ "/uvr/sources", "/uvr/results" ]

ENTRYPOINT [ "python3" ]

CMD [ "/uvr/UVR.py" ]

The docker-compose.yml is the same as before.
But the words are just displayed in half because the window is too small to show words in whole.
At least I can see the program running, but I'm too tired to test if it works well. Let me test it tomorrow.
I strongly recomend that the Dockerfile and docker-compose.yml should be added to your repository now that it works well and more importantly, this program will not pollute the system anymore.

First, preinstall docker by the official command and enable docker with non-user access.
curl -fsSL https://get.docker.com | bash -s docker
sudo groupadd docker
sudo usermod -aG docker $USER
newgrp docker

After that, you should need a reboot.

WORKDIR /home/$USERNAME
USER $USERNAME

# Install UVR

# RUN git clone https://github.com/Anjok07/ultimatevocalremovergui.git UVR

WORKDIR /home/$USERNAME/UVR
COPY ./requirements.txt .
ENV PATH=/home/$USERNAME/.local/bin:$PATH

RUN pip3 install scikit-learn \
    && pip3 install -r requirements.txt
    && pip3 install pygobject

COPY . .

VOLUME [ "/home/$USERNAME/UVR/sources", "/home/$USERNAME/UVR/results" ]

CMD [ "python3" , "UVR.py" ]

Then build the image.
docker build -t uvr .

Execute these commands everytime you run this program.
Linux x86_64 Minimum Required Driver Version for Nvidia >=525.60.13, otherwise you won't be able to use cuda.
--gpus all should be omitted when you have no Nvidia GPU installed.

Hi @hero-intelligent !
Thanks for your Docker example. Build it OK with just 2 small changes, but when tried to run:
``docker: Error response from daemon: could not select device driver "" with capabilities: [[gpu]].

Also tried without --gpus all flag, then it can't find NVIDIA driver.
Also last section looked to me very like x11docker. So I decided to try it with it, but it also ended up not working. Got any ideas?
Thanks

Huge thanks to hero-intelligent for the docker setup! I was able to get it the non-NVIDIA version working on my 2015 Macbook Pro running 10.14.6 Mojave with the following steps. Hopefully this can help other macOS users.

Installed https://www.xquartz.org. I discovered that I had to reboot my computer for it to work.

Used hero-intelligent's Dockerfile for "NOT an Nvidia user", with one modification. Before the pip3 install step, added this statement to fix the scikit-learn error:

ENV SKLEARN_ALLOW_DEPRECATED_SKLEARN_PACKAGE_INSTALL=True

To build the docker image, used additional build-args so that USER_UID and USER_GID matched my own.

docker build -t uvr . \
    --build-arg USER_UID=$(id -u) \
    --build-arg USER_GID=$(id -g)

Added a line to /etc/hosts file. You probably need sudo for this.

echo "$(ipconfig getifaddr en0) $(hostname)" >> /etc/hosts

Used this command to run the container.


fix: nested required fields causes joi validation to assume truthy required array means everything is required

see https://github.com/acr-lfr/generate-it-typescript-server/issues/162 for context

closes acr-lfr/generate-it-typescript-server#162

do you want to roll out the other prs with this release - think they're all good to go

the open ones?
not 100% sure where i left off with 115 but even if it doesnt solve the problem it shouldn't break anything™

yea they all look ok to me the outstanding 3

works for me


Revert "embed: fix HTTPs + DNS SRV discovery"

In 3.2.8, both configurations work with TLS/SRV
"hosts": [
  "m1.etcd.local",
  "m2.etcd.local",
  "m3.etcd.local",
  "etcd.local",
  "<IP_ADDRESS>",
  "localhost"
]

"hosts": [
  "*.etcd.local",
  "etcd.local",
  "<IP_ADDRESS>",
  "localhost"
]

In 3.2.9, we added wildcard to peer server name (e.g. *.etcd.local when DNS cluster is etcd.local).
Now the first configuration doesn't work
"hosts": [
  "m1.etcd.local",
  "m2.etcd.local",
  "m3.etcd.local",
  "etcd.local",
  "<IP_ADDRESS>",
  "localhost"
]

Second configuration still works
"hosts": [
  "*.etcd.local",
  "etcd.local",
  "<IP_ADDRESS>",
  "localhost"
]

But, not every tool supports wildcard certs.
We are reverting this change, also in upcoming patch release 3.2.10.
Address https://github.com/coreos/etcd/issues/8445.

we need to update the documentation to make it clear that the TLS certs for DNS discovery must include the root domain in SAN to prevent mitm attack.

@xiang90 I've highlighted this change in CHANGELOG and security.md.
PTAL.

lgtm

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6260df7). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #8884   +/-   ##
=========================================
  Coverage          ?   76.05%
=========================================
  Files             ?      359
  Lines             ?    29721
  Branches          ?        0
=========================================
  Hits              ?    22603
  Misses            ?     5537
  Partials          ?     1581

Impacted Files
Coverage Δ

embed/config.go
61.63% <0%> (ø)

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 6260df7...37b3108. Read the comment docs.


[bug]: Script not found

Describe the bug
While running the cmd bunx --bun shadcn-ui@latest init
I am getting the error: Script not found "shadcn-ui@latest"
Affected component/components
Not able to install the project
How to reproduce
Use this cmd bunx --bun shadcn-ui@latest init in Windows using the Git Bash

Codesandbox/StackBlitz link
https://github.com/Boby900/yogurt
Logs
$ bunx --bun shadcn-ui@latest init
error: Script not found "shadcn-ui@latest"

System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (4) x64 Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz
    Memory: 594.21 MB / 3.92 GB
  Binaries:
    Node: 21.1.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.4.0 - C:\Program Files\nodejs\npm.CMD
    bun: 1.1.6 - ~\AppData\Roaming\npm\bun.CMD
  Browsers:
    Chrome: 124.0.6367.207
    Edge: Chromium (123.0.2420.97)
    Internet Explorer: 11.0.19041.3636

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

Please fix :)

using the bun with a space worked for me.
bun x --bun shadcn-ui@latest init

using the bun with a space worked for me. bun x --bun shadcn-ui@latest init

using the bun with a space worked for me. bun x --bun shadcn-ui@latest init

this works

yes @braswelljr
bun x is an alias for bunx.


Invisible Textscreens

Researching into the issue a bit more I've noticed other people have had a similar problem but not quite the same, I'll do my best to explain it as best as I can.
Upon making a text screen whether you try to 'Perma prop' or 'Perma text screen' the text screen will refresh as normal and remain there. However upon a server restart, the text screen will then turn invisible, it's still there as you can still interact with it through the context menu and if you permit prop a Perma text screen after having the bug it will return as though nothing has happened but if the server restarts again it does not care and will go back to being invisible. Oddly though this does not happen with every text screen, only with about half, I had tested it with a friend where we placed 10 text screens each together, 'perma'd' them, restarted the server and then none of them had saved! Out of a sample size of 20, 0 had been saved which needless to say is an intolerable result. This leads me to believe it may be a database issue however I'm unsure and to be truly honest completely flustered as to what could be doing this. I have tried both the git and steam versions to no avail.
The only things that are being printed in the console in regards to 3d2d are the following
[3D2D Textscreens] Spawning textscreens...
[3D2D Textscreens] Spawned 44 textscreens for map rp_titan_base_bananakin
Thanks.

Thanks for the detailed report.
Do you have a sammyservers_textscreens.txt file in your data folder that can currently replicate this? If so, I'd love to get a copy of that.
Once this happens, does it always happen, or does it seem to be different screens that are visible/invisible on every restart? Does it happen on multiple maps, or just some specific ones?

It varies as I said, sometimes it works and others it just doesn't appear. From everything I've seen as of yet it has led me to deduce that some sort of information isn't being recorded successfully. This especially doesn't make sense as when you perma prop it then it suddenly returns from the dead, apart from rainbow text screens, the text is there but it no longer has the rainbow effect. I'm quite honestly clueless as to what could be causing it, I've tested it so much as to see if I can find any conceivable patterns that lead to a specific glitch however there are none it truly is random. I have attached the requested file to this comment for you to review. In regards to the question you asked just to clarify, it is purely random however ones that are affected are invisible upon a server restart whereas ones that have been successful work just as intended.
Thanks, I appreciate the support!
sammyservers_textscreens.txt

Hi we are having a very similar problem on our Server where only 50% of the signs are rendering (They still spawn):
sammyservers_textscreens.txt
And this is our collection if it is important:
https//steamcommunity.com/sharedfiles/filedetails/?id=2015394018

It looks like you're using a non-official version of the addon, which I can't provide support for I'm afraid, sorry.
If you can provide steps to replicate this issue in a sandbox environment using the official addon and no other addons installed, I'd be happy to investigate further.

@Cherry we tried it with normal 3D2D Textscreens again and we found out that z_anticrash was interfering with the spawning of the textscreens by ghosting it. Could it be that a ghosted Textscreen isn't rendered proberly ?

That's very possible. I'm not familiar with z_anticrash and what it does with "ghosting". If you remove that addon temporarily, do things work correctly?


related work

https://doi.org/10.12688/f1000research.15140.2

@psychemedia Did you do the comparison yet?

Sorry - no; will try to have a look at this tomorrow...

So I've done a quick review of the paper, published as Gruening B, Sallou O, Moreno P et al. Recommendations for the packaging and containerizing of bioinformatics software [version 2; peer review: 2 approved, 1 approved with reservations]. F1000Research 2019, 7(ELIXIR):742 (https://doi.org/10.12688/f1000research.15140.2) which has a focus on the containerisation of single applications ("an encapsulated and immutable version of an application, coupled with the bare-minimum operating system components (e.g. dependencies) required for execution") relevant to the bioinformatics domain .
Some things that jumped out wrt current draft of paper drafted in this repo:

metadata (eg LABEL elements) should include version of containerised application; the container should also be semantically versioned.
recommends against using ENTRYPOINT (their recommendation 4. Avoid using ENTRYPOINT): Even when the ENTRYPOINT helps the user to get a default behaviour for a tool, it is generally not recommended because of reproducibility concerns of the implicit hidden execution point. By explicitly executing the tool by its executable inside the container (using the container as an environment and not as a fat binary merely through its ENTRYPOINT) the user (e.g. workflow) can recognise and trace the tool that is used within the container.
(straddles 4. Document within the Dockerfile — Usage instructions and 8. Enable interactive usage and one-click execution) their recommendation 2. One tool, one container recommends that the container containerises a single application; to support use (11. Provide helpful usage message), "If your tool provides a help “-h”, “--help” or “?” message, consider providing this as the default command, “CMD” in case of a Dockerfile."; if no help available, add something to the README.
(relates to 9. Use a Dockerfile per project): recommendation that as well as sharing containers, Dockerfiles are shared too (10. Provide reproducible and documented builds), along with recommendation 9. Make your package or container discoverable that containers are made discoverable by publishing them to existing bioinformatics registries.
(relates to 10. Use the container daily) a recommendation to include functional tests (7. Add functional testing logic) over the containerised application somewhere in the container, ideally at a conventional location (eg runTest.sh, available via the internal container PATH).
regarding image size (which is a consideration because "containers are frequently pushed and pulled (uploaded and downloaded) to/from container registries over the internet, their size matters") 5. Reduce the size of your container as much as possible suggests " the most efficient way [to limit size] is to have two different containers: one for building the app and the second container for deploying the app (which will be the one user will download). While you may need multiple libraries, source code and dependencies for building the app, you should only include the bare necessities in the deployment container, which will actually run the app""; or at the very least, don't install additional "recommended" libraries by default, don't keep build tools in deployed image, do use a lightweight base container".
there's a handy recommendation 8. Check the license of the software to check software licenses ("The license must always be explicitly defined in your Docker labels") and ensure the license is bundled inside the container if the license requires it. (It strikes that that's the sort of thing that could be part of a build tool - check the license, bundle it if required.)

One more, regarding Extension packages and programming language modules, their recommendation 1. A package first, which suggests a) using a package manager for software release in general, b) using Bioconda in particular in their domain:

Bioconda is a channel for the Conda package manager specialised in bioinformatics software. You can create a Conda package by defining a BioConda recipe [example provided]. This recipe includes enough information about the dependencies, the license and fundamental metadata to find, retrieve and use the package. When a recipe is added to Bioconda, it is automatically built into a usable package, tested and made available as a Docker container via Quay.io and as a Singularity container, and is displayed in the BioContainers registry

Thanks @psychemedia for the analysis! Very helpful. I think there is a clear distinction: we worry less about image sizes or single applications, but about packaging whole workflows and making the image the actual research environment.
I tried to connect to the article using your thoughts in https://github.com/nuest/ten-simple-rules-dockerfiles/commit/ee13e359f3a15ead01e3ae3a65bb1bd60eff5fe2
Let me know what you think, please re-open if you think this is not an adequate referencing of the other work.
CC: @vsoch @sje30 @betatim @benmarwick


dev -> master for 0.5.0rc1

Coverage increased (+0.4%) to 51.126% when pulling afbcffb00a99eece82ec484095b6f1773bf14764 on dev into 284219efc051023786449614fdcd4b836c32cfc6 on master.

Coverage increased (+0.4%) to 51.126% when pulling 2119034c5c6f8917962aa3ff8ab6d457506d0fc1 on dev into 284219efc051023786449614fdcd4b836c32cfc6 on master.

Coverage increased (+0.4%) to 51.126% when pulling 2119034c5c6f8917962aa3ff8ab6d457506d0fc1 on dev into 284219efc051023786449614fdcd4b836c32cfc6 on master.


Bug: Not seeing the token refresh process happening

The auth server I'm using doesn't return JWT tokens so I'm using the following settings to deal with the token refresh process:
const authConfig: TAuthConfig = {
  ...
  // Example to redirect back to original path after login has completed
  preLogin: () => localStorage.setItem('preLoginPath', window.location.pathname),
  postLogin: () => window.location.replace(localStorage.getItem('preLoginPath') || ''),
  tokenExpiresIn: 120,
  refreshTokenExpiresIn: 259200,
  onRefreshTokenExpire: (event) => event.logIn(undefined, undefined)
  ...
}

I was expecting for the library to do the token refresh process on the background after tokenExpiresIn seconds, but what happens is that after tokenExpiresIn seconds the user is redirected to the auth server authorization page. Is this expected behavior? Am I misunderstanding something?
Steps To Reproduce

Set tokenExpiresIn in the settings with a low value, and a refreshTokenExpiresIn with a higher value.
Wait tokenExpiresIn seconds.

The current behavior
The user is redirected to the auth server authorization page
The expected behavior
I was expecting for the library to do the token refresh process on the background after tokenExpiresIn seconds

Hi, thank you for reporting.
I will try to recreate the bug when I get some time, but in the mean time, could you post the network log, and state of localStorage? The behavior you're describing will happen if there is no refreshToken, or the refreshRequest fails. Are you sure you have a valid refreshToken?

Nevermind, I was able to debug the auth service to check that the library is calling the token endpoint for refreshing the token and it's indeed making the request, but the server was expecting the scope I used when making the authorize request to be the same in the token refresh request, and since I was not setting the scope in the settings, the authorize request didn't have a scope and the auth server was assuming the scope was all of the scopes allowed. Then when I did the token refresh request the library send the same scope (an empty scope) and since this is different to the scope assumed by the auth server (all of the scopes) it was returning a 400. I set the scope setting and the token refresh process is working now.
Sorry for the noise


[BEAM-13740] update java_tests.yml to temporarily remove setup-go

setup-go is misconfigured and blocking the build
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java PreCommit

@chamikaramj @lostluck for review

Going to merge this in, but we may still run into failures related to Go in the Actions, assuming there's no go involved. The ultimate fix is probably to just duplicate the setup rather than having a "needs" step.


dwindle: window splits can result in windows that are higher than wide

Description
Currently, the split is determined based on the W/H ratio of the current (then parent) node:

The split is determined dynamically with the W/H ratio of the parent node. If W > H, it’s side-by-side. If H > W, it’s top-and-bottom.

With windows that are quite square already however, this can lead to windows being spawned that are quite a bit higher than they are wide. For instance: The default multiplier splits a 1716,1438 into two 856,1438 windows.
This is because it doesn't take into account that a vertical split will result in windows that are half as wide. You can work around that by setting dwindle:split_width_multiplier = 2.
This would arguably make for a better default value for that variable; should we change it?
This is imperfect though as it doesn't take window borders and spacing into account which can can differ based on direction.
The perfect solution would instead simulate what the split would actually do to the ratios of the resulting windows and then choose a vertical split only when it results in two windows where W >= H.

MRs welcome


readme: update from the slides from the presentation

From https://lavocatt.github.io/manifest-db-slides/#1

I think the content from the presentation makes sense in the README. However, I would expect it to be structured more like a README.
So basically start with what the thing in the repo is and what it does before getting into the weeds of defining terms.
Finally, the - from my pov - most important bit about the update workflow is currently at the bottom.
Just a very quick and dirty suggestion for a structure:

Introduction/Summary of what manifest-db is and does
Update cycle of manifest-db
Which problem does manifest-db solve (and what did we do before)
Appendix: Terminology
4.1 Manifests
4.2 Image Info
...

See my comment about the structure of the README

Thanks for the comments! I think it's quite better now :smile:

@lavocatt Thanks for the work you put into this - it's so much better heart
There's only one more thing I can offer, which is language improvement suggestions. Let me know if you want me to review the text from that angle and add suggestions to it. Otherwise it's good to go from where I stand!

Thanks Simon for taking the time to review! Yes I would love to see your suggestions.


[YUNIKORN-593]Optimize the UT for ListApplications

What is this PR for?
Optimize the UT for ListApplications.
What type of PR is it?

[ ] - Bug Fix
[ ] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-593
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

I can move podCase array out of Test function, and turn on the lint check, if it is necessary.


Add changelog for v1.6.0

What this PR does / why we need it:
Add changelog for the v1.6.0 release.
Fixes https://github.com/kubermatic/release/issues/8
What type of PR is this?
/kind documentation
Does this PR introduce a user-facing change? Then add your Release Note here:
NONE

Documentation:
NONE

/hold cancel

/lgtm


endpoint: Do not remove redirects on subsequence policy calculation

Fixes: #2861

test-me-please

test-me-please

Why would we keep a redirect for a port for which there are no L7 rules?

I think that we have a deeper problem here.
The policy.L4PolicyMap that is modified here is contained/owned by the Consumable. But the L7RedirectPort values are endpoint-specific. If we have more than one endpoint with the same security ID on that node, the values of L7RedirectPort may not be relevant to the endpoint being regenerated. They are basically garbage.
It's OK to write into it, because we're holding the Consumable's lock and using the values afterwards before releasing the lock. But it's not OK to trust any value that we receive in there.
So I think we should always call UpdateProxyRedirect, which should be idempotent:
for k, l4 := range m {
	if l4.IsRedirect() {
		redirect, err := owner.UpdateProxyRedirect(e, &l4)
		if err != nil {
			return err
		}
		l4.L7RedirectPort = int(redirect)
		m[k] = l4

		proxyID := e.ProxyID(&l4)
		if e.realizedRedirects == nil {
			e.realizedRedirects = make(map[string]bool)
		}
		e.realizedRedirects[proxyID] = true
		desiredRedirects[proxyID] = true
	}
}

The effect of this change is that we won't remove redirects when the policy rules applied for a port are updated and change from L7 to L3/L4.
Is that really what we want?

Rhe following code won't enter the branch after subsequent policy calculation cycles because UpdateProxyRedirect() will have allocated and set an l4.L7RedirectPort. This currently causes the redirect to be removed again on any follow-up call to regenerateBPF()
                redirect := uint16(l4.L7RedirectPort)
                if l4.IsRedirect() && redirect == 0 {
                        redirect, err := owner.UpdateProxyRedirect(e, &l4)
                        if err != nil {
                                return err
                        }
                        l4.L7RedirectPort = int(redirect)

test-me-please

This is an intermediate workaround. We need to get rid of the consumable and just treat endpoints independently. This is adding unnecessary complexity.

Submitted https://github.com/cilium/cilium/pull/2866 to stop storing endpoint-specific redirect ports in the Consumable's policy.


K8SPXC-1050 rename secrets to use default names

Test name
Status

upgrade-haproxy-8-0
passed

scaling-8-0
passed

users-5-7
passed

storage-8-0
passed

recreate-8-0
passed

scaling-proxysql-8-0
passed

self-healing-8-0
passed

self-healing-chaos-8-0
passed

security-context-8-0
passed

restore-to-encrypted-cluster-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
passed

upgrade-proxysql-8-0
passed

one-pod-5-7
passed

demand-backup-8-0
passed

scheduled-backup-5-7
passed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
passed

smart-update-8-0
passed

init-deploy-5-7
passed

pitr-8-0
failed

haproxy-5-7
passed

upgrade-consistency-8-0
passed

demand-backup-encrypted-with-tls-8-0
failed

We run 24 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1223/commits/9e973c1a930b98be2fbb595ba28d1a9a24b30077
image: perconalab/percona-xtradb-cluster-operator:PR-1223-9e973c1a

@hors should we change the default cr.yaml? https://github.com/percona/percona-xtradb-cluster-operator/blob/main/deploy/cr.yaml#L14-L17

@hors should we change the default cr.yaml? https://github.com/percona/percona-xtradb-cluster-operator/blob/main/deploy/cr.yaml#L14-L17

fixed

Test name
Status

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

demand-backup-8-0
passed

pitr-8-0
passed

demand-backup-encrypted-with-tls-8-0
failed

We run 5 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1223/commits/0ad91b8ecead067c3b81aafc205e3b20429f0250
image: perconalab/percona-xtradb-cluster-operator:PR-1223-0ad91b8e

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1223/commits/d2c6d6c3f5a1b78c9e52316dd7ddcf9fad5fefda
image: perconalab/percona-xtradb-cluster-operator:PR-1223-d2c6d6c3

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
failed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
failed

haproxy-5-7
passed

haproxy-8-0
failed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
failed

scheduled-backup-8-0
failed

security-context-8-0
passed

smart-update1-8-0
failed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
failed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failed

upgrade-proxysql-8-0
passed

users-5-7
failed

users-8-0
failed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1223/commits/d2c6d6c3f5a1b78c9e52316dd7ddcf9fad5fefda
image: perconalab/percona-xtradb-cluster-operator:PR-1223-d2c6d6c3

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
failed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1223/commits/d2c6d6c3f5a1b78c9e52316dd7ddcf9fad5fefda
image: perconalab/percona-xtradb-cluster-operator:PR-1223-d2c6d6c3


Alarm sample: 'add an alarm' doesn't work if the previous command was 'show alarms'

'add an alarm' is not a valid expression for the regex which is "add alarm(.*)"
I'm preparing a PR about those alarm-sample problems, I also noticed a crash of the Show alarms command when the user hasn't set any alarm

@cleemullins @anastasiia-zolochevska I have retested this following #261 getting merged a few hours ago and this seems to be fixed, so I believe should be good to close now.


Upgrade pre-installed packages in docker images

Sometimes, the upstream distro will release a package but we had to wait
until they made a new image before our images would get the new package.
This means the security scanners will report fixable vulnerabilities that a
rebuild would not fix. With this change, we just have to make a new
build to pull in the patched packages.
Fixes: #2408

approved, though i wonder how much longer it'll make our builds take...

approved, though i wonder how much longer it'll make our builds take...

Yeah, if it becomes a problem, we can try and turn it off for feature branches. There will be some environment variable plumbing involved, but I think it should be possible.

if it becomes a problem, we can try and turn it off for feature branches

seems like a good plan to me. i wonder if we need to be docker/binary building at all on non-main builds....

seems like a good plan to me. i wonder if we need to be docker/binary building at all on non-main builds....

So sometime a feature branch will be change something in the docker images, so you would want to build them there. So the problem reduces to that of monorepos.


Disk space usage of pipelines

ocaml-docs-ci uses a concept of Epochs to track sets of package documentation that interlink and share common dependencies. Each Epoch is self-contained and can grow to 100G or more for production.
When they are no longer used Epochs can be removed and the disk space reclaimed. Outside of epochs two directories compile and prep also take up a lot of disk space. But there is no clean way of reclaiming the un-used diskspace from them. For example on live docs.ci.ocaml.org they look like:
$ ls -l
total 940
drwxr-xr-x 4 localadmin localadmin   4096 Oct 12 17:50 compile
-rw-r--r-- 1 root       root       459760 Jan  3  2023 content.current
-rw-r--r-- 1 root       root       450418 Jan  3  2023 content.live
drwxr-xr-x 3 localadmin localadmin   4096 Aug 11 10:58 epoch-51470fc39ff110dfccafc8f0f1d882ec
drwxr-xr-x 3 localadmin localadmin   4096 Oct 12 17:50 epoch-5daeecab2ad7a2d07a12742d4cc0ab6f
drwxr-xr-x 3 localadmin localadmin   4096 Aug 11 12:23 epoch-804419edbd92ec13bc06b69d15132959
drwxr-xr-x 3 localadmin localadmin   4096 Oct 12 17:51 epoch-ae8bf595b8594945ee40c58377e03730
drwxr-xr-x 3 localadmin localadmin   4096 Jul 20 09:44 epoch-c96e56dbd72372ea5f56e27e667243ea
lrwxrwxrwx 1 root       root           44 Aug 16 05:48 html-current -> /data/epoch-ae8bf595b8594945ee40c58377e03730
-rw-r--r-- 1 root       root         1365 Aug 16 05:48 html-current.log
lrwxrwxrwx 1 root       root           44 Sep  7 13:56 html-live -> /data/epoch-ae8bf595b8594945ee40c58377e03730
-rw-r--r-- 1 root       root         1028 Sep  7 13:56 html-live.log
drwxr-xr-x 2 root       root         4096 Aug 25  2022 linked
lrwxrwxrwx 1 root       root           44 Aug 16 05:48 linked-current -> /data/epoch-5daeecab2ad7a2d07a12742d4cc0ab6f
-rw-r--r-- 1 root       root         1690 Aug 16 05:48 linked-current.log
lrwxrwxrwx 1 root       root           44 Sep  7 13:56 linked-live -> /data/epoch-5daeecab2ad7a2d07a12742d4cc0ab6f
-rw-r--r-- 1 root       root          585 Sep  7 13:56 linked-live.log
lrwxrwxrwx 1 root       root            9 Jul 21  2021 live -> html-live
drwxr-xr-x 3 localadmin localadmin   4096 Oct 12 17:45 prep

$ du -skhc *
159G	compile
452K	content.current
440K	content.live
94G	epoch-51470fc39ff110dfccafc8f0f1d882ec
28G	epoch-5daeecab2ad7a2d07a12742d4cc0ab6f
59G	epoch-804419edbd92ec13bc06b69d15132959
47G	epoch-ae8bf595b8594945ee40c58377e03730
103G	epoch-c96e56dbd72372ea5f56e27e667243ea
0	html-current
4.0K	html-current.log
0	html-live
4.0K	html-live.log
4.0K	linked
0	linked-current
4.0K	linked-current.log
0	linked-live
4.0K	linked-live.log
0	live
551G	prep
1.1T	total

Both directories appear to contain universes but they aren't linked to a specific Epoch and can't be easily pruned.
Further investigation is required to work out how we can reclaim disk space or organise these directories into epochs so they can be reclaimed.

Initial tooling for pruning prep and compile directories is available with https://github.com/ocurrent/ocaml-docs-ci/pull/161.
Running on staging freed up 83Gb worth of orphan universes.
# du -skhc /data/*
32G	/data/compile
27G	/data/epoch-097e46a4d589b9e34ed2903beecd1a04
16G	/data/epoch-3820829bb005c559218fffb16ee32f3b
17G	/data/epoch-410108220dc0168ea4d9bd697dfa8e34
56K	/data/epoch-7b9b14524382caea73504bb5a36d8879
40K	/data/epoch-8550e0f943a1074985306ec2c9d21822
25G	/data/epoch-9baa5939aca1673d141e85b6ecd1e770
0	/data/html-current
4.0K	/data/html-current.log
0	/data/html-live
4.0K	/data/html-live.log
4.0K	/data/linked
0	/data/linked-current
4.0K	/data/linked-current.log
0	/data/linked-live
4.0K	/data/linked-live.log
99G	/data/prep
212G	total
# /usr/local/bin/epoch --base-dir /data
Files to be deleted in prep/universes
000266a0eb75736fb01067c065abfdcf
00065d52d8d3a4ed06de725186e78055
0008e7ff536074039c951738c9386eff
001351655c7802dc23d2b7508c32f206
0014e3e571ed5319e5db4b6c3dc31c48
001ff6efc0fbeb22ffde83cc265ceb41
00221d8f37762a32b03e84334594560a
0024ed8660c331065b18a08bbe205a2c
00259e1f647baf2c1493e52d0d9ff07d
0035a1d03fc9aaa713d6aac6d1fe7fe8
... plus 20959 more

Deleting 20969 files in /data/prep/universes
✔ │███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████│ 20969/20969
Files to be deleted in compile/u
000266a0eb75736fb01067c065abfdcf
0014e3e571ed5319e5db4b6c3dc31c48
001ff6efc0fbeb22ffde83cc265ceb41
00259e1f647baf2c1493e52d0d9ff07d
003cafc54a9826c27f9a6a44bbbe45d2
004e68d419cbbf2cf6e49edbee60da35
0062d3b633c68a7b15fd49012400b3e5
006b995bf91c4616f744e3f862ac63cd
007077bb760550510c5a3a9cf34bbefe
0078206d4374af0bf15247fd078daced
... plus 6323 more

Deleting 6333 files in /data/compile/u
✔ │█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████│ 6333/6333

After running epoch prune
# du -skhc /data/*
23G	/data/compile
27G	/data/epoch-097e46a4d589b9e34ed2903beecd1a04
16G	/data/epoch-3820829bb005c559218fffb16ee32f3b
17G	/data/epoch-410108220dc0168ea4d9bd697dfa8e34
56K	/data/epoch-7b9b14524382caea73504bb5a36d8879
40K	/data/epoch-8550e0f943a1074985306ec2c9d21822
25G	/data/epoch-9baa5939aca1673d141e85b6ecd1e770
0	/data/html-current
4.0K	/data/html-current.log
0	/data/html-live
4.0K	/data/html-live.log
4.0K	/data/linked
0	/data/linked-current
4.0K	/data/linked-current.log
0	/data/linked-live
4.0K	/data/linked-live.log
26G	/data/prep
129G	total

The next step is to provide epoch validate epoch-c96e56dbd72372ea5f56e27e667243ea command that checks an epoch is internally consistent and does not have missing universes. Epoch pruning works on the assumption that no active jobs are running and the symlinks/universes are consistent on disk. This doesn't always hold if jobs are running and making changes to the disk layout.
After that epoch cli tool needs to have a way to diff two epochs of the same type.
For example:
# epoch diff /data/epoch-9baa5939aca1673d141e85b6ecd1e770 /data/epoch-8550e0f943a1074985306ec2c9d21822

Shows a rich diff format of which package versions are present or absent between the two epochs. This is particularly useful for the html epochs that are used by ocaml.org.
# epoch diff /data/epoch-9baa5939aca1673d141e85b6ecd1e770 /data/epoch-8550e0f943a1074985306ec2c9d21822 --summary

Provides a quick summary of how many package versions are added, missing or new between the two epochs
# epoch diff /data/epoch-9baa5939aca1673d141e85b6ecd1e770 /data/epoch-8550e0f943a1074985306ec2c9d21822 --package lwt

Provides a diff for a single package which versions are added, missing or new between the two epochs.
New packages are ones that were not present in opam-repository when the first epoch was created.
Added packages are ones that existed and now have documentation built.
Missing packages are ones that did exist in opam-repository but have no successful build.


Mangling function/class declaration names is dangerous

Code might refer to fn.name. Uglify, Closure and Babili all mangle function names by default, so maybe we should too. Either way we should certainly have the option to preserve function and class names.
(In an ideal world we might be able to determine whether it's safe to mangle a given function's name — e.g. in the following snippet there is no possibility of the name mattering, and we could determine as much statically):
function foo () {
  function bar () {
    console.log('the name of this function does not matter');
  }

  bar();
}

Incidentally, disabling mangling for classes and functions is relatively easy — just need to change this function:
Object.keys( this.declarations ).forEach( name => {
  const declaration = this.declarations[ name ];

+  if ( /^(Function|Class)/.test( declaration.node.parent.type ) && declaration.node === declaration.node.parent.id ) {
+    return;
+  }

  declaration.alias = this.createIdentifier( used );

  declaration.instances.forEach( instance => {
    const replacement = instance.parent.type === 'Property' && instance.parent.shorthand ?
      `${instance.name}:${declaration.alias}` :
      declaration.alias;

    code.overwrite( instance.start, instance.end, replacement, true );
  });
});

On the flip side, when mangling is enabled, we should remove function names for all FunctionExpression nodes whose names are not referenced inside the function (which should be easy to determine)


Fix obvious typos

Still nice they put comments to their code :)

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

@danielmatzke good point, updating it now

Sorry, we're not accepting changes to the source code or materials.


Add taxonomic filtering to reaction page

Do once https://github.com/KarrLab/datanator_rest_api/issues/37 is closed

done


Added configurable receive timeout

The fix in b020d5c looks like it probably fixes the inital issue this work was for (hang when mikrotik reboots), but the receive timeout still gets around the potential issue where the the library can block forever if the connection drops half way through a request.
TODO: Associated setting in the routeros collectd plugin.
TODO: Configurable connect timeout.

Steve,
The benefit of having this timeout is that we could detect a situation when the connection is still alive but mikrotik for some reason doesn't send us data (and we are waiting in read() call for it).
But IMHO this is another class of problem then disconnection - as this was handled by my fix in b020d5c. If mikrotik reboots/closes connection then my previous patch would be sufficient as it is breaking the while loop, before it was eating 100% cpu.
btw: How long a mikrotik could respond to any API command?

I have to test it deeply then I think I'll commit this... give me some time...

I reckon the timeout could help with both cases. The read() could block for a long time if the connection can't be closed from the other side due to a disconnect & also if the 'tik stops reasponding for some reason.
I'm more worried about EAGAIN now - apparently it can crop up all over the place even on blocking socket calls. I haven't seen it happen on my system but can't vouche for all *nix'es. There must be a reason Florian included the check in the first place.
API calls could take a while to respond, I guess for example pings could run indefinitely. I made the timeout configurable to deal with this.
I wouldnt be against cancelling this pull request. I'm not using the lib any more so it isn't urgent. Also this isn't the best timeout implementation.

TODO: Configurable connect timeout.

If you're thinking about or planning to add additional options to the connect function, please consider using a struct instead of adding a large number of arguments.
Example usage:
ros_connect_opts_t opts = {
  .connect_timeout = 10,
};

c = ros_connect_with_options (host, ROUTEROS_API_PORT,
                              opt_username, passwd, &opts);

@octo
Thank you for review. I am currently refactoring this code and merge after this with changes (I'll comply your comments - in fact I had most of them in my head already)...

Refactored and commited in: https://github.com/octo/librouteros/commit/448505117e0e584bb3ee7d9c99235243d9a3394e
ps. the code is now also prepared to easy add connect_timeout parameter.
Thank you all! :)

Thanks for all your feedback guys - really appreciated :)


[Feature Request] Allow using custom EBS volume size

Hello,
I have a use-case where I need to have more space than the machines are created with by default. I haven't found a way to increase this using terraform other than redefining the ebs_block_device block. However, only the ebs_type is exposed in the module and not the size itself.
Would it be possible to expose the size component as well?
Thanks in advance

Hi @hamyhamz,
Thanks for your feedback.
As a workaround, you can fork the module and add the disk size on main.tf file to adapt it to your environment.

Hi,
Thanks for reporting. Added to the backlog and internal tracking ID for this request is: INFRAANO-1323.


Curation raw data not showing up in component details

Consider https://clearlydefined.io/definitions/maven/mavencentral/org.glassfish.jersey.core/jersey-client/2.25.1
It is curated (there is an entry in the Curations list and it has the Curated tag) but clicking on the Curations tab in the Raw data section at the bottom shows empty data.

Opening up a notes comment here that I will update throughout my investigation.
Using my local environment, I harvested this component, then opened up a curation pull request in curated-data-dev
However, it's still now showing up in my local UI when I look at the component's page.

Opening up a notes comment here that I will update throughout my investigation.
Using my local environment, I harvested this component, then opened up a curation pull request in curated-data-dev
However, it's still now showing up in my local UI when I look at the component's page.

@jeffmcaffer what kind of information do you expect to be in the "Curations" tab under raw data?


Make the Swagger docs available when building for production

Why this feature is required (specific use-cases will be appreciated)?
When building the AdonisJS application (for production), the docs folder or the Swagger comments in the controllers/models are not included in the build folder. This then leads to the Swagger UI not showing any endpoint info when running in production.
I'm not sure if I have missed something on how to get this "out of the box" when doing a production build.
Have you tried any other work arounds?
The workaround for me has currently been to manually copy the docs folder to the build folder after the build step has completed.
Not sure if there is a workaround when adding the Swagger comments in the controllers/models? It seems like the comments get stripped out in the build step.
Are you willing to work on it with little guidance?
I currently don't have that much free time.

Yes, typescript really drop your comments from js files. Default adonis ts preset contains option removeComments=true. You should set for false for fix it.
But I use swagger with my ts files. Do you have ts files on your server ? Package should resolve path to you ts files, if build dir is inside directory with your typescript files. Could you demonstrate your file system content ? What does package version do you use ?

I have a fairly basic AdonisJS 5 app, here you can see the folder structure:

As you can see I have a docs/swagger folder with the settings.yml as well, when I remove the yaml file I don't get any endpoints in my Swagger UI, even if I have Swagger comments in the controller.

When we deploy to production we only take the /build folder and the node_modules folder, so we skip all the source files, I assume that is why it can't find the comments in the non-existing .ts files.

Yes, then I guess I have to look into that or just keep our copy step for the docs folder. But then I know what this package supports.

Yes, then I guess I have to look into that or just keep our copy step for the docs folder. But then I know what this package supports.

Yes, then I guess I have to look into that or just keep our copy step for the docs folder. But then I know what this package supports.
https://github.com/reg2005/adonis5-swagger/pull/10
I developed production mode for swagger. We will publish new features as soon as tested on our projects.

I added it like this:
"dependencies": {
    "@adonisjs/core": "^5.0.4-preview-rc-2.1",
    "@adonisjs/lucid": "^10.0.0",
    "@adonisjs/repl": "^1.1.6",
    "luxon": "^1.25.0",
    "proxy-addr": "^2.0.6",
    "reflect-metadata": "^0.1.13",
    "source-map-support": "^0.5.19",
    "adonis5-swagger": "git://github.com/reg2005/adonis5-swagger.git#swagger_mode"
  }

But when I try to start the app after building it I get this:
> node server.js

Error: Cannot find module '/app/node_modules/adonis5-swagger/build/index.js'. Please verify that the package.json has a valid "main" entry
    at tryPackage (internal/modules/cjs/loader.js:322:19)
    at Function.Module._findPath (internal/modules/cjs/loader.js:683:18)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:1007:27)
    at resolveFileName (/app/node_modules/resolve-from/index.js:29:39)
    at resolveFrom (/app/node_modules/resolve-from/index.js:43:9)
    at Object.module.exports [as default] (/app/node_modules/resolve-from/index.js:46:47)
    at Object.resolveFrom (/app/node_modules/@poppinss/utils/build/src/resolveFrom.js:25:34)
    at Registrar.loadProvider (/app/node_modules/@adonisjs/fold/build/src/Registrar/index.js:49:23)
    at /app/node_modules/@adonisjs/fold/build/src/Registrar/index.js:67:53
    at Array.forEach (<anonymous>)

Btw, will it be enough to have this in the Swagger config options?
apis: [
  'docs/swagger/**/*.yml'
]

I added it like this:
"dependencies": {
    "@adonisjs/core": "^5.0.4-preview-rc-2.1",
    "@adonisjs/lucid": "^10.0.0",
    "@adonisjs/repl": "^1.1.6",
    "luxon": "^1.25.0",
    "proxy-addr": "^2.0.6",
    "reflect-metadata": "^0.1.13",
    "source-map-support": "^0.5.19",
    "adonis5-swagger": "git://github.com/reg2005/adonis5-swagger.git#swagger_mode"
  }

Build info:
> node ace build --production

[ info ]  cleaning up "./build" directory
[ info ]  compiling typescript source files
[ error ]  typescript compiler errors
error TS2688: Cannot find type definition file for 'adonis5-swagger'.
config/swagger.ts:1:31 - error TS2307: Cannot find module '@ioc:Adonis/Addons/Swagger' or its corresponding type declarations.

1 import { SwaggerConfig } from '@ioc:Adonis/Addons/Swagger'

But when I try to start the app after building it I get this:
> node server.js

Error: Cannot find module '/app/node_modules/adonis5-swagger/build/index.js'. Please verify that the package.json has a valid "main" entry
    at tryPackage (internal/modules/cjs/loader.js:322:19)
    at Function.Module._findPath (internal/modules/cjs/loader.js:683:18)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:1007:27)
    at resolveFileName (/app/node_modules/resolve-from/index.js:29:39)
    at resolveFrom (/app/node_modules/resolve-from/index.js:43:9)
    at Object.module.exports [as default] (/app/node_modules/resolve-from/index.js:46:47)
    at Object.resolveFrom (/app/node_modules/@poppinss/utils/build/src/resolveFrom.js:25:34)
    at Registrar.loadProvider (/app/node_modules/@adonisjs/fold/build/src/Registrar/index.js:49:23)
    at /app/node_modules/@adonisjs/fold/build/src/Registrar/index.js:67:53
    at Array.forEach (<anonymous>)

Try to install in next way:

This is what happens then:
$ node ace invoke adonis5-swagger
UPDATE: .adonisrc.json { commands += "adonis5-swagger/build/commands" }
UPDATE: .adonisrc.json { providers += "adonis5-swagger" }
(node:39272) UnhandledPromiseRejectionWarning: Error: Template file not found: C:\Repositories\GitHub\setting-service\node_modules\adonis5-swagger\build\templates\config.txt
    at read (C:\Repositories\GitHub\setting-service\node_modules\smpltmpl\index.js:21:10)
    at templateFromFile (C:\Repositories\GitHub\setting-service\node_modules\smpltmpl\index.js:80:15)
    at Object.apply (C:\Repositories\GitHub\setting-service\node_modules\mrm-core\src\formats\template.js:33:14)
    at TemplateLiteralFile.apply (C:\Repositories\GitHub\setting-service\node_modules\@adonisjs\sink\src\Files\Formats\TemplateLiteral.js:43:26)
    at TemplatesManager.copyTemplateFor (C:\Repositories\GitHub\setting-service\node_modules\@adonisjs\sink\src\Tasks\TemplatesManager\index.js:98:18)
    at C:\Repositories\GitHub\setting-service\node_modules\@adonisjs\sink\src\Tasks\TemplatesManager\index.js:114:41
    at Array.forEach (<anonymous>)
    at TemplatesManager.copyTemplatesFor (C:\Repositories\GitHub\setting-service\node_modules\@adonisjs\sink\src\Tasks\TemplatesManager\index.js:114:14)
    at C:\Repositories\GitHub\setting-service\node_modules\@adonisjs\sink\src\Tasks\TemplatesManager\index.js:132:18
    at Array.forEach (<anonymous>)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:39272) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which
was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejecti
ons_mode). (rejection id: 1)
(node:39272) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit c
ode.
CREATE: ace-manifest.json file

Try remove your node_modules and reinstall dependencies. And please check, is \node_modules\adonis5-swagger\build\templates\config.txt exist

I did remove and re-install the node modules, I still get the same error. This is the contents of my adonis5-swagger/build folder:
adonis-typings/
commands/
providers/
src/
index.d.ts
index.js

We published package to npm. Could you reinstall package as usual npm package and check ?

Now I have tried it, it works when I do a production build locally and start the app from the /build folder. But when I run it in "production" it is the same problem, I still need to copy the /docs folder manually.
So where does it fetch the Swagger docs in this new release? And from what I can see it does not create any Swagger resource in the /build folder.
This is the version I tried:
"adonis5-swagger": "^1.2.1",

We recommend add post hook for build: https://github.com/reg2005/adonis5-swagger#production-using

There are some confusing things in the docs here regarding the setup for production.
When I check my config/swagger.ts file which was generated when invoking adonis5-swagger I can't see the same structure as your example.
import { SwaggerConfig } from '@ioc:Adonis/Addons/Swagger'

export default {
	uiEnabled: true, //disable or enable swaggerUi route
	uiUrl: 'docs', // url path to swaggerUI
	specEnabled: true, //disable or enable swagger.json route
	specUrl: '/swagger.json',
        ....

Your example:
const swaggerConfig = {
	mode: process.env.NODE_ENV === 'production' ? 'PRODUCTION' : 'RUNTIME',
	specFilePath: 'docs/swagger.json'
}

I would assume I just add it like so:
import { SwaggerConfig } from '@ioc:Adonis/Addons/Swagger'

export default {
	mode: process.env.NODE_ENV === 'production' ? 'PRODUCTION' : 'RUNTIME',
	uiEnabled: true, //disable or enable swaggerUi route
	uiUrl: 'docs', // url path to swaggerUI
	specEnabled: true, //disable or enable swagger.json route
	specUrl: '/swagger.json',
	specFilePath: 'docs/swagger.json',
        ...

But then my next question is why you are using process.env here? In Adonis 5 they use the Env module in the docs.
import Env from '@ioc:Adonis/Core/Env'

Env.get('NODE_ENV')

// with default value
Env.get('NODE_ENV', 'development')

And the last question then is, when you add your post build hook, you copy the whole /docs folder, that in my case contains the swagger yml files, do I then really need the generated json file?

Sorry for the late response.

And the last question then is, when you add your post build hook, you copy the whole /docs folder, that in my case contains the swagger yml files, do I then really need the generated json file?
You need to copy only swagger spec json. This file was generated by swagger-jsdoc and consists of all schemes for swagger.

But then my next question is why you are using process.env here? In Adonis 5 they use the Env module in the docs.

Of course you can use adonis env for getting access to your env variables. For this case there is no differences.

When I check my config/swagger.ts file which was generated when invoking adonis5-swagger I can't see the same structure as your example.

New options for swagger config was added in last version. Maybe your config file was generated by previous version. I will check options for rewriting config in adonis during provider installation.
Can I close issue ? Do you have additional questions ?

You can close it, thanks for the help.


【#2803】fix the endpoint cannot get instanceId without http

Make sure set the target branch to develop
What is the purpose of the change
XXXXX
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

#2803

Coverage increased (+0.01%) to 51.825% when pulling 89f8ecc4ad533422fe368435f4d59ff56625a6c3 on panzhi33:release-4.8.0 into af8a9648c75d3dac5a7e7fcd0d8047d41456d96d on apache:develop.

It would be better to write a UT.


macOS fails ./configure --without-gui

Hi, starting from version v0.17 on macOS 10.13.6 ./configure --without-gui is failing with:
configure: error: libdb_cxx headers missing, Bitcoin ABC requires this library for wallet functionality (--disable-wallet to disable wallet functionality)

and
ttps://github.com/Bitcoin-ABC/bitcoin-abc.gitor https://github.com/bitcoincashorg/bitcoincash.org

compiled successfully with https://github.com/bitcoin/bitcoin/blob/master/contrib/install_db4.sh


How to change/delete default recipes in machines?

I want to change some recipes in machines, but instead I just add one more. This is quite an important part of my modpack, so I'm interested in how it's possible to change recipes.
Thank you for attention

Are you using the alpha build?
Does the output exactly match the output of the recipe you wish to modify?

I am using: 1.0.15. As I understand it is not alpha.
Probably it is influenced by the fact that in XML I put as a result of the itemstack format, and in game put oredict format.
<Recipes>     <Recipe timeRequired="10" power="50">         <input>             <oreDict>ingotIron 4</oreDict>         </input>         <output>             <itemStack>libvulpes:productplate 1 1</itemStack>         </output>     </Recipe> </Recipes>
http://imgur.com/a/qBkQm

It only overwrites a recipe if the inputs are the same.  Unfortunatly there's no way for the program to know whether you intend to overwrite an existing recipe or just add a new one for the same output.
What you'll have to do I think is to use   and fill in the other recipes.
I do not know how well this'll work for you, but I have (and the alpha builds will generate) an XML copy of all the recipes used which I've attached for convience.
Github does not like XMLs, so you may need to change the extension
RollingMachine.txt

It works as it should, thanks a lot for the XML file. If you have files of other machines, then I would be very grateful. Although, if not, then still a big thank you to you. Typically, mod developers respond days and weeks.
There is also another small question. Is it possible in any way to modify or completely delete the recipes of a small plate press, except how to remove the recipe of the block itself? (Sorry for my bad English)

I do have files for the other machines, yes.
ChemicalReactor.txt
Crystallizer.txt
CuttingMachine.txt
ElectricArcFurnace.txt
Electrolyser.txt
Lathe.txt
PrecisionAssembler.txt
Currently there is no way to modify the recipes for the small plate press, but I'll look into changing that.


[C++]  How to define and write "Map" data (nested type)?

This is not an issue regarding the parquet lib itself but maybe with the accompanying documentation/examples:
Based on the "StreamWriter" example  stream_reader_writer, I'm trying to add another column to the parquet schema which I want to write "Map-Data" (Map<Integer, String>) to.
According to this source, Maps are supported by the C++ implementation. However, it's not clear to me how to ...

correctly add/define another column of type "Map" to the parquet schema. According to the previous link, Maps are "Logical Types", so my best try so far is

fields.push_back(parquet::schema::PrimitiveNode::Make("Map", parquet::Repetition::REQUIRED, parquet::LogicalType::Map(), parquet::Type::INT64));
This compiles without error but I'm uncertain about the last parameter "primitive_type" (parquet::Type::INT64).

how to define and write actual Map values. Again, the second links provides a general description of a parquet Map:

// Map<String, Integer>
required group my_map (MAP) {
  repeated group key_value {
    required binary key (UTF8);
    optional int32 value;
  }
}

The github repo is missing a C++ example (or test case) on how to use a Map/Logical Types.
I'm looking for advice/an C++ example, how to define and use a Map together with the StreamWriter API.

Looking at the header file and the tests, I don't believe the StreamWriter has any support for nested parquet types (structs, lists, and maps), so I don't think this is currently possible.
Maps and other nested types are supported for writing, just not through that API. The Arrow writer supports arbitrary nested types, and there's likely a lower-level API for doing that too.


Get all key-values pairs from Diagnostics Context classes

Type :  Feature request
NLog version: >=4.1.1
Platform: .NET4.5, mono
Description:
I am investigating the use of GlobalDiagnosticsContext and MappedDiagnosticsLogicalContext (MDLC) for our system.
We use a custom layout renderer that transforms the log to a json message that will be sent to a remote log collecting system. I would like to add all values available in MDLC to this json message, but the methods the MDLC class only allow retrieval of a specific item.
I would like a way to get a public readonly dictionary from these classes that contain all values.
Note that MappedDiagnosticsContext makes its dictionary "internal", so that renderers in the NLog package can access the data.

Thanks for the feature request.
We were in the middle of overhauling the context classes a few months ago, but that process has been halted due to other (more critical) features/issues. See #969
PR accepted for the new classes/interfaces.

It looks more like it has been halted because there is no good solution available right now. Is it an option that I supply a pull request to just update the current implementation?
It would oblige you to implement the feature after refactoring...
I am proposing
public static ICollection<string> GetItems()

Indeed it's halted to bad.
Your proposal sounds good,but I think the type should be readonlydictionary<string, object >

My intention was to only return the keys (so I should change my proposal to GetKeys()). What are the advantages and disadvantages of returning the dictionary vs returning the keys?
Wouldn't making the dictionary read-only involve copying the data?
If there is some filtering process in the layout renderer, returning only the keys might save some data being copied for nothing?

Ow yes, I think the keys only is a better proposal :)
I think iset<string> is then better,do you agree?

Returning a set would better indicate that we will have no duplicates. However, I have been looking for a built-in (and efficient) way to return the keys of a dictionary as an ISet, but I cannot find this (I am rather new to c# and may have missed something...)
Also I can return the keys as a IReadOnlyCollection, but there does not seem to be an IReadOnlySet.
How much added value has returning an ISet over an ICollection if we add the readonly-ness?
So my new proposal would be
public static IReadOnlyCollection<string> GetKeys()

Returning a set would better indicate that we will have no duplicates. However, I have been looking for a built-in (and efficient) way to return the keys of a dictionary as an ISet, but I cannot find this (I am rather new to c# and may have missed something...)

No indeed, you should create it yourself. Too bad ISet is .NET 4+ (HashSet is .Net 3.5+), but I think IReadOnlyCollection is also nice. An user could create his own HashSet to efficient check the keys.

By the way, would you prefer getKeys or getItems, since item is the name of the parameter used everywhere for the "key", but it may also be easily misinterpreted as the "name+value" combination.

GetNames(), as we use indeed "name" everywhere.

IReadOnlyCollection is not supported on .NET 3.5, maybe also not on .NET 4.0.
So, shall I just revert back to the original ICollection?

Or you can use #if NET3_5


L1CrossDomainMessenger vulnerability when the native token is TON

Describe the bug
You can steal the TON held by L1CrossDomainMessengerContract in the following way.
If L1CrossDomainMessengerContract holds TON of the amount, then
TON of the amount is converted to WTON, and WTON of the amount is approved to 'attackContract'.
const param = web3.eth.abi.encodeParameters(
["address", "address"],
[attackContract, extraData]
);

const functionBytecode = tonContract.interface.encodeFunctionData(
"approveAndCall", [
wtonContract.address, amount, param
])

const sendTx = await (
await l2CrossDomainMessengerContract
.connect(l2Wallet)
.sendMessage(tonContract.address, functionBytecode, 200000, { value: 1 })
).wait()

Configuration
Severity: Critical
Impact
Fund theft
Recommendation

This attack will not work because the target cannot use the native token.


Cocoapods with NZCircularImageView

Hi,
I am trying to use Cocoapods with NZCircularImageView in XCode 6.1.1 swift project but I am getting a number of errors regarding the import statements
In UIImageView+UIActivityIndicatorForSDWebImage.h:
#import "UIImageView+WebCache.h"
#import "SDImageCache.h"
#import "UIImageView+UIActivityIndicatorForSDWebImage.h"
error is "Include of non-modular header inside framework module 'UIActivityIndicator_for_SDWebImage.UIImageView_UIActivityIndicatorForSDWebImage"
and in NZCircularImageView.h
#import "UIImageView+UIActivityIndicatorForSDWebImage.h"
error is "Could not build module 'UIActivityIndicator_for_SDWebImage".
Would you have any idea about how to fix this?

Use the pre-release version of the CocoaPods.

I still get the error  Could not build module 'UIActivityIndicator_for_SDWebImage' after I switch on use_frameworks! in my Podfile. What's going on?


UIP-5: outbound PFM support

Describe your changes
Implementation of the candidate UIP-5: outbound PFM support (see https://forum.penumbra.zone/t/pre-uip-outbound-packet-forwarding-middleware-support/121)
Should be reviewed for correctness and adherence to the spec.
Note that this only includes the required protocol changes to allow clients to use the new memo field (a prerequisite for PFM support), and does not implement outbound packet forwarding directly (that is to be done in the client).

This breaks consensus, right? I think we need to retarget this PR towards release/v0.81.0 instead

Yup, consensus breaking but not proto breaking

Ugh, changing the base has picked up other commits making the diff monstruous. I will re-open this and target the 81 branch directly.