Fast-forward source node expansion anywhere in the succession diagram

This is a slightly more controversial update:
During the block expansion, allow to "fast-forward" the expansion of source nodes anywhere in the succession diagram. That is, if the percolation of a stable motif results in the creation of a bunch of source nodes, we automatically create 2**n successors for these without further analysis (they can't contain motif-avoidant attractors anyway). However, this only happens with block expansion and can be turned off using the recently added optimize_source_nodes flag.
This eliminates 88 978 SD nodes and almost 9 minutes of compute time for the BBM "easy" models alone. I haven't retested all the hard models yet, but this overall seems like a win. It does sometimes increase the ratio of expanded nodes vs. the non-expanded ones, but is mostly not an issue, because the ones where we expand the source nodes cost us very little compute.

Performance data for the "easy" BBM models:
biobalm-source-fast-forward.xlsx

Merging since the tests passed and this does not have any affect on the structure produced during the full expansion, so it will not interfere with any other analysis tasks except for attractor detection (where it should be faster).


Controller input

Now using Unity Input Controller library
Implemented our own Controller copied from the URDFImporter package
Xbox controller scheme added
VR controller and camera added

j'ai bin fait ça


Angular Event Bindings broken with Angular 6 with handsontable\angular 2.0

Description
Binding hooks with () in the HTML template do not fire with Angular 6 with handsontable\angular 2.0. They previously worked fine with Angular 5 and handsontable\angular 1.0 .
Does not work anymore
<hot-table data="values" (afterChange) ="afterChange($event)"> <hot-table>
vs
Works
<hot-table [settings]="settings"><hot-table>

this.settings = {
   data: this.values,
   afterChange: (changes) => this.afterChange(changes)
}

Steps to reproduce

Use event binding
Trigger a hook

Demo

https://stackblitz.com/edit/angular-bewcmg
Your environment

Angular version: 6.1
Handsontable version: 4.0
Wrapper version: 2.0
Browser Name and version: Chrome 69
Operating System: Win 10 64biy

Update: Event binding works with Angular 6 and  @handsontable/angular version 1.0.0-beta5

Hi @Calidus
I believe that this is the same issue as reported at https://github.com/handsontable/angular-handsontable/issues/123.
Can you confirm?

They are slightly different, the event is not getting triggered if you use the parentheses to do event binding in the template. In #123 if you use a settings object the event is trigger but it doesn't return the values specified in the documentation.

Hi,
Please check the release notes for 2.0.0 [1]. There was a very important change in this matter:

We've refactored @Outputs to @Inputs. Now you can use return false in callbacks.

[1] https://github.com/handsontable/angular-handsontable/releases/tag/2.0.0

Could the information from the release notes be added to the official docs? Either in the angular wrapper section or the events section?
https://handsontable.com/docs/6.0.1/frameworks-wrapper-for-angular-installation.html
https://handsontable.com/docs/6.0.1/Hooks.html#event:afterChange

Yeah, you're right. Angular section is falling behind when it comes to examples.
I've created an issue for that: #126


Minor patch breaks backwards compatibility

Hey!
Your latest version push broke backwards compatibility - we don't usually expect minor versions to do that and it caused a bit of an issue for us using it.
We have locked it back down to the 0.1.3 version for now, please keep the front-line engineers at the mercy of your tags in mind! 😃
Thanks for building this useful library, we've got almost 3 years use out of it and this is my first issue 👍

oh you are right!  Apologies.  I should have bumped it to version 1 then.  I will fix that, thanks!


Add support for Symfony 7

Fixes #238

Just a heads up that this pull request won't work with Symfony 7. The ContainerAwareInterface has been depreciated as per Symphony 6.4 and removed in 7.
On another note the composer.lock file has been committed and ideally would be removed. I notice it is in the .gitignore file but probably added there after it was committed.


file_group_count exceeds MAX_FILE_GROUP_COUNT

I'm getting trouble extracting a cabinet.
Version from header is 16:
[unshield_read_headers:226] Reading header from .hdr file 1.
[unshield_read_headers:303] Version 0x02000640 handled as major version 16
[unshield_get_cab_descriptor:81] Cabinet descriptor: 000d192a 002026f0 002026f0 00000168
[unshield_get_cab_descriptor:83] Directory count: 90
[unshield_get_cab_descriptor:84] File count: 20901

There are 20901 files.
Searching inside the setup.exe:
$ strings /mnt/1/setup.exe | grep -i shield
http://www.installshield.com/isetup/ProErrorCentral.asp?ErrorCode=%d : 0x%x&ErrorInfo=%s
InstallShieldPendingOperation
SOFTWARE\InstallShield\16.0\Professional
    name="InstallShield.Setup"
<description>InstallShield.Setup</description>

At lib/component.c on line 53, using gdb, self->file_group_count is 151, exceeding the MAX_FILE_GROUP_COUNT limit set as 71 in lib/cabfile.h at line 16.
52 self->file_group_count = READ_UINT16(p); p += 2;
53 if (self->file_group_count > MAX_FILE_GROUP_COUNT)
54     abort();

As seen in i6comp at line 34, the max file groups is 512.
33 #define CSFG_MAX 512
34 #define CSCP_MAX 512

Changing the MAX_FILE_GROUP_COUNT to 512 produces a segmentation fault:
0x00007ffff7bd59eb in get_unaligned_le32 (p=0x7ffffcd1eb10 <error: Cannot access memory at address 0x7ffffcd1eb10>) at ~/unshield/lib/internal.h:138
 138        return p[0] | p[1] << 8 | p[2] << 16 | p[3] << 24;
(gdb) bt
#0  0x00007ffff7bd59eb in get_unaligned_le32 (p=0x7ffffcd1eb10 <error: Cannot access memory at address 0x7ffffcd1eb10>) at ~/unshield/lib/internal.h:138
#1  0x00007ffff7bd605a in unshield_header_get_components (header=0x55555575a030) at ~/unshield/lib/libunshield.c:145
#2  0x00007ffff7bd66f6 in unshield_read_headers (unshield=0x555555759ff0, version=0xffffffff) at ~/unshield/lib/libunshield.c:317
#3  0x00007ffff7bd68e2 in unshield_open_force_version (filename=0x7fffffffe4a3 "/mnt/1/data1.cab", version=0xffffffff) at ~/unshield/lib/libunshield.c:369
#4  0x000055555555690c in main (argc=0x5, argv=0x7fffffffe138) at ~/unshield/src/unshield.c:578

However using the following "patch" on lib/component.c, allows to continue on big file_group_count, with the original MAX_FILE_GROUP_COUNT set at 71:
52   self->file_group_count = READ_UINT16(p); p += 2;
53   if (self->file_group_count > MAX_FILE_GROUP_COUNT)
54       printf("WARNING: self->file_group_count = %d\n", self->file_group_count);
55       if(self->file_group_count > 512)
56           abort()

This patch allows me to extract the cabinet without error, but obviously I have no idea of why.
Using valgrind to check buffer overflow (count bigger than MAX), shows no errors:
$ valgrind src/unshield -d test x /mnt/1/data1.cab
...
          19911 files
==9926==
==9926== HEAP SUMMARY:
==9926==     in use at exit: 0 bytes in 0 blocks
==9926==   total heap usage: 436,953 allocs, 436,953 frees, 8,169,910,049 bytes allocated
==9926==
==9926== All heap blocks were freed -- no leaks are possible
==9926==
==9926== For counts of detected and suppressed errors, rerun with: -v
==9926== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

And the number of files is the same as extracted, but not equal to the number of files in the header 20901:
$ find test/ -type f  | wc -l
19911

Cabinets are large, in total ~1GB. Any ideas?

Interesting. Are you able to share the installation files with me?
Increasing MAX_FILE_GROUP_COUNT will make unshield read more "file group" entries, and that will push "component" entries forward and that will cause a crash. These are listed by the g and c commands, respectively.
The reason less files are extracted than the file count can be found in the unshield_file_is_valid function. There are a number of cases where a file entry is not actually a file.

I have sent the entire iso (by torrent) to your email.
Using the original MAX_FILE_GROUP_COUNT set as 71, I can list the groups and components:
$ src/unshield g /mnt/1/data1.cab
...
1648 file groups

$ src/unshield c /mnt/1/data1.cab
...
1445 components

But with the above warning:
WARNING: self->file_group_count = 151

The invalid files (shown by a improvised printf call in unshield_file_is_valid function), sum exactly the initial ones:
$ src/unshield l /mnt/1/data1.cab | grep 'Invalid file' | wc -l
990

$ echo '19911 + 990' | bc -l
20901

And the cases, classified by increasing number in the branches starting at 1:
$ src/unshield l /mnt/1/data1.cab | grep 'Reason' | sort | uniq -c
    384 Reason 3
    606 Reason 5

For the reason 3, fd->flags has the flag FILE_INVALID, and for the 5, fd->data_offset is NULL.

Got it, thanks! I'll see if I can get it working this weekend!

Looks like I didn't get it working that weekend... Due to personal time priorities/constraints I need a PR to fix this, if it's still an issue.

MAX_FILE_GROUP_COUNT seems to only be a limitation of the CabDescriptor, ie: there's a maximum of 70 entry points for the file group offset list. I think that abort() call can be safely removed.


Stateless submit-button for login-less applications

Description
We would like to provide our respondents with a login-less survey they can fill in and then submit their answer. Using the normal submit button requires an instance, but these respondents will be responding using the anonymous stateless functionality instead, hence no instance. This "stateless submit"-button should preferably include the contents of the model (not the formData representation). Upon clicking "stateless submit" a call to an overridable endpoint on the server should be made, followed by a navigation/redirect to a customizable receipt page.
Additional Information
We have a working POC where we have created a custom Web Component that makes an http-request to a custom endpoint on the server that handles the request, after which the frontend just redirects to the start of the survey. The initial idea was to include another layout page with the receipt, but we couldn't find a way to trigger a "next page" event in the frontend.
Our POC-implementation can be found here: https://altinn.studio/repos/udir/demodemoeleveundersokelsen
Workflow:

The respondent goes to http://altinn3local.no/udir/demodemoelevundersokelsen?userid=d-mango-vann-1. This is a stateless part of the app (allowAnonymousOnStateless = true).  By inspecting the query parameter "userid" the server requests an external service for information on which survey they should partake in and provides the correct resources to the frontend.
The respondent fills in their answers. On the last page of the survey, our custom Web Component for the "stateless submit button" binds all fields from the model to dataModelBindings (this gets quite large for many questions).
The respondent clicks the "stateless submit button" which then makes a request to our custom endpoint udir/demodemoeleveundersokelsen/api/stateless/submit. The backend then converts the datamodelBindings to our model and then makes a request to an external service. When the frontend receives a response, it redirects to the front page. Instead of redirecting to the front page it should preferably present a receipt instead.

Sample layoutelement illustrating why we would like the model to be sent instead of having to define/map datamodelBindings (this example is a summary, we can have more than 70 questions, this one includes only 9)
{
          "tagName": "stateless-submit-button-component",
          "id": "formlayout-uniqueid-23",
          "type": "Custom",
          "textResourceBindings": {},
          "dataModelBindings": {
            "surveyId": "SurveyId",
            "surveyExecutionId": "SurveyExecutionId",
            "schoolClass": "Metadata.Claims.SchoolClass",
            "yearLevel": "Metadata.Claims.YearLevel",
            "orgNumber": "Metadata.Claims.SchoolOrgNumber",
            "orgNumberOwner": "Metadata.Claims.SchoolOwnerOrgNumber",
            "q0id": "Questions[0].Id",
            "q0code": "Questions[0].QuestionCode",
            "q0ans": "Questions[0].Answer",
            "q1id": "Questions[1].Id",
            "q1code": "Questions[1].QuestionCode",
            "q1ans": "Questions[1].Answer",
            "q2id": "Questions[2].Id",
            "q2code": "Questions[2].QuestionCode",
            "q2ans": "Questions[2].Answer",
            "q3id": "Questions[3].Id",
            "q3code": "Questions[3].QuestionCode",
            "q3ans": "Questions[3].Answer",
            "q3ao0code": "Questions[3].MultipleChoiceOptions[0].Code",
            "q3ao0val": "Questions[3].MultipleChoiceOptions[0].Value",
            "q3ao1code": "Questions[3].MultipleChoiceOptions[1].Code",
            "q3ao1val": "Questions[3].MultipleChoiceOptions[1].Value",
            "q3ao2code": "Questions[3].MultipleChoiceOptions[2].Code",
            "q3ao2val": "Questions[3].MultipleChoiceOptions[2].Value",
            "q3ao3code": "Questions[3].MultipleChoiceOptions[3].Code",
            "q3ao3val": "Questions[3].MultipleChoiceOptions[3].Value",
            "q4id": "Questions[4].Id",
            "q4code": "Questions[4].QuestionCode",
            "q4ans": "Questions[4].Answer",
            "q4ao0code": "Questions[4].MultipleChoiceOptions[0].Code",
            "q4ao0val": "Questions[4].MultipleChoiceOptions[0].Value",
            "q4ao1code": "Questions[4].MultipleChoiceOptions[1].Code",
            "q4ao1val": "Questions[4].MultipleChoiceOptions[1].Value",
            "q4ao2code": "Questions[4].MultipleChoiceOptions[2].Code",
            "q4ao2val": "Questions[4].MultipleChoiceOptions[2].Value",
            "q4ao3code": "Questions[4].MultipleChoiceOptions[3].Code",
            "q4ao3val": "Questions[4].MultipleChoiceOptions[3].Value",
            "q5id": "Questions[5].Id",
            "q5code": "Questions[5].QuestionCode",
            "q5ans": "Questions[5].Answer",
            "q6id": "Questions[6].Id",
            "q6code": "Questions[6].QuestionCode",
            "q6ans": "Questions[6].Answer",
            "q7id": "Questions[7].Id",
            "q7code": "Questions[7].QuestionCode",
            "q7ans": "Questions[7].Answer",
            "q8id": "Questions[8].Id",
            "q8code": "Questions[8].QuestionCode",
            "q8ans": "Questions[8].Answer",
            "q9id": "Questions[9].Id",
            "q9code": "Questions[9].QuestionCode",
            "q9ans": "Questions[9].Answer"
          }
        }

Moving this to app-frontend-react although it might require some implementation elsewhere as well. Instead of jerry-rigging some way to submit data from anonymous stateless apps to an endpoint we should probably look into supporting anonymous instances (and proper anonymous stateful apps). This could also make it possible to limit who can create new instances. It also follows the rest of our paradigm where completed instances are fetched from our APIs (PULL) rather than submitted somewhere (PUSH), as this feature-request describes.


Chain element from page object item

Proposed changes
Add test for bug reproduction related to element chaining from page object item.
Checklist

[ ] Checkstyle and unit tests are passed locally with my changes by running gradlew check chrome_headless firefox_headless command
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Same behavior on top of pure selenium


Update Makefile for ruff, remove js stuff

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

Comparison is base (78b9548) 100.00% compared to head (94cc935) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines            4         4
=========================================
  Hits             4         4

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


ToggleButton Component

As a developer who will be implementing the library, I would like to have a easily groupable set of toggle buttons, that can toggle functionality on and off. In order for this to be useful, it must interface with a container, that can utilize the buttons to create a toggle button group. These should be square buttons, simliar to the MaterialUI concept of a toggle button and a toggle button group.
Acceptance Criteria:

Buttons can toggle on and off
Buttons interface with a ToggleButtonGroup component

Giving this one a go...no idea how to do this however lol


Rust support ( Dockerfile )

Hi @andrasbacsai,
Thanks for this awesome project 🙌 , I open this one as draft since is adding the Dockerfile template for rust apps using cargo-chef but I think there are missing pieces in the frontend and I need to make a round of testing but I think is a nice first step to support rust apps.
Thanks!

Looks good to me! I've tested and it works, just needs some finetuning.
Thank you! 🙏

Awesome! Thanks 😃


use same HTTP client as dockerengine

This should reduce the number of open connections

ping @dongluochen

Job: Swarm-PRs (engine 1.10) [FAILED](https://jenkins.dockerproject.org/job/Swarm-PRs (engine 1.10)/315/console):

---
- docker network rm
ok 154 mesos - docker network disconnect connect
ok 155 mesos - docker ps
ok 156 mesos - docker run with wrong user
ok 157 mesos - docker run
ok 158 mesos - docker run short lived
ok 159 mesos - docker run no resources
ok 160 mesos - docker run with long pull
ok 161 mesos - docker stats
ok 162 mesos - docker-compose ps
ok 163 mesos - docker-compose scale
ok 164 mesos - docker-compose up
ok 165 mesos - zookeeper
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Swarm-PRs (engine 1.10)] $ /bin/sh -xe /tmp/hudson1109882199140136051.sh
+ set +x

---

@vieux is this related to #1549?

@nishanttotla yes !

Job: Swarm-PRs (engine master) [FAILED](https://jenkins.dockerproject.org/job/Swarm-PRs (engine master)/1854/console):

---

# cannot connect to docker engine
# Stopping 6a9a9a6a6b97855d9b4796b329a3b84896bb8bc1dc578157a2b33b081c281535
# Stopping 8d2ea6d2e9b56a3101c343dc52eba41f0ca3d8b83fe13b5aa6b5ce721b5ab473
# Stopping 427bd2bd2ec63d647c21ba8615d0d23c130876c9f6fc2442afbfc9c7430a6a36
# Stopping 2171f18dfc71d257afaa048a7aaed726c500543062872544e72ef845647dcf7a
# Stopping 4beb7facdd0ced03d06549ef7a666a2ce285096ec0c1f9788051733f84de3621
ok 165 mesos - zookeeper
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Swarm-PRs (engine master)] $ /bin/sh -xe /tmp/hudson8319152053695726511.sh
+ set +x

---

Job: Swarm-PRs (engine 1.10) [FAILED](https://jenkins.dockerproject.org/job/Swarm-PRs (engine 1.10)/318/console):

---

# cannot connect to docker engine
# Stopping 147759a9d09635339aeda74ecd103066721b1e3d5d75143c734d744503f8262b
# Stopping 5fe5f17da5eb734fd175a8f695fb240c2807b5559ee9cb1b5cc00b6e85b4db54
# Stopping 923134a93393485e70a8128e86421c17e226f08a819a382b5799baeaa3cbef59
# Stopping 2c4f0653e36eb56fcf6a2d7ccb5a8807774973d8cd8a1f56a51379afe51f5675
# Stopping 7dbf05d8e86f784746a8ccaa1c92dd640e273a23b092e14d372761dbdc0af57b
ok 165 mesos - zookeeper
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Swarm-PRs (engine 1.10)] $ /bin/sh -xe /tmp/hudson2532482310377837189.sh
+ set +x

---

Job: Swarm-PRs (engine 1.9) [FAILED](https://jenkins.dockerproject.org/job/Swarm-PRs (engine 1.9)/18/console):

---

# cannot connect to docker engine
# Stopping ceea6cd9c884546b756265d2015a867e7abf27ac3fa28317f328c0daad430f19
# Stopping f7ecda670a7f881894956ba16843ea562a99c477feba5134f858f85c51f51c33
# Stopping 6093a24a46d5cd13bc504846e768de24e33533c1d21fae7f8b1b10bad3da9255
# Stopping c58024db06902e1b5ef5c6372819bc2d577445bbb69e9d1a9c17785a85c70522
# Stopping f0946e46c0097c7a7bf5b2a41f5b4a08af60f423d81cbc7b395dd24ff94caa76
ok 165 mesos - zookeeper
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Swarm-PRs (engine 1.9)] $ /bin/sh -xe /tmp/hudson3041912465670730333.sh
+ set +x

---

Just to be clear, this makes it use the samalba/dockerclient instead of a raw golang http client. Right?

Job: Swarm-PRs (engine 1.10) [FAILED](https://jenkins.dockerproject.org/job/Swarm-PRs (engine 1.10)/325/console):

---
- docker network rm
ok 154 mesos - docker network disconnect connect
ok 155 mesos - docker ps
ok 156 mesos - docker run with wrong user
ok 157 mesos - docker run
ok 158 mesos - docker run short lived
ok 159 mesos - docker run no resources
ok 160 mesos - docker run with long pull
ok 161 mesos - docker stats
ok 162 mesos - docker-compose ps
ok 163 mesos - docker-compose scale
ok 164 mesos - docker-compose up
ok 165 mesos - zookeeper
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Swarm-PRs (engine 1.10)] $ /bin/sh -xe /tmp/hudson6926894103951868629.sh
+ set +x

---

Job: Swarm-PRs (engine master) [FAILED](https://jenkins.dockerproject.org/job/Swarm-PRs (engine master)/1861/console):

---
- docker network rm
ok 154 mesos - docker network disconnect connect
ok 155 mesos - docker ps
ok 156 mesos - docker run with wrong user
ok 157 mesos - docker run
ok 158 mesos - docker run short lived
ok 159 mesos - docker run no resources
ok 160 mesos - docker run with long pull
ok 161 mesos - docker stats
ok 162 mesos - docker-compose ps
ok 163 mesos - docker-compose scale
ok 164 mesos - docker-compose up
ok 165 mesos - zookeeper
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Swarm-PRs (engine master)] $ /bin/sh -xe /tmp/hudson7843053417246660124.sh
+ set +x

---

@MHBauer samalba/dockerclient uses the a  raw golang http client
Before this pr we were creating a new  raw golang http client for every proxy request,
now we simply reuse the same one as dockerlient, so we can reuse idle connection.

Job: Swarm-PRs (engine 1.9) [FAILED](https://jenkins.dockerproject.org/job/Swarm-PRs (engine 1.9)/34/console):

---
- docker network rm
ok 154 mesos - docker network disconnect connect
ok 155 mesos - docker ps
ok 156 mesos - docker run with wrong user
ok 157 mesos - docker run
ok 158 mesos - docker run short lived
ok 159 mesos - docker run no resources
ok 160 mesos - docker run with long pull
ok 161 mesos - docker stats
ok 162 mesos - docker-compose ps
ok 163 mesos - docker-compose scale
ok 164 mesos - docker-compose up
ok 165 mesos - zookeeper
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Swarm-PRs (engine 1.9)] $ /bin/sh -xe /tmp/hudson8582968936913608398.sh
+ set +x

---

Job: Swarm-PRs (engine 1.10) [FAILED](https://jenkins.dockerproject.org/job/Swarm-PRs (engine 1.10)/334/console):

---
- docker network rm
ok 154 mesos - docker network disconnect connect
ok 155 mesos - docker ps
ok 156 mesos - docker run with wrong user
ok 157 mesos - docker run
ok 158 mesos - docker run short lived
ok 159 mesos - docker run no resources
ok 160 mesos - docker run with long pull
ok 161 mesos - docker stats
ok 162 mesos - docker-compose ps
ok 163 mesos - docker-compose scale
ok 164 mesos - docker-compose up
ok 165 mesos - zookeeper
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Swarm-PRs (engine 1.10)] $ /bin/sh -xe /tmp/hudson6131753365636618642.sh
+ set +x

---

LGTM

Job: Swarm-PRs (engine 1.10) [FAILED](https://jenkins.dockerproject.org/job/Swarm-PRs (engine 1.10)/339/console):

---
- docker network rm
ok 154 mesos - docker network disconnect connect
ok 155 mesos - docker ps
ok 156 mesos - docker run with wrong user
ok 157 mesos - docker run
ok 158 mesos - docker run short lived
ok 159 mesos - docker run no resources
ok 160 mesos - docker run with long pull
ok 161 mesos - docker stats
ok 162 mesos - docker-compose ps
ok 163 mesos - docker-compose scale
ok 164 mesos - docker-compose up
ok 165 mesos - zookeeper
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Swarm-PRs (engine 1.10)] $ /bin/sh -xe /tmp/hudson2739847145240324357.sh
+ set +x

---

Job: Swarm-PRs (engine master) [FAILED](https://jenkins.dockerproject.org/job/Swarm-PRs (engine master)/1875/console):

---
- docker network rm
ok 154 mesos - docker network disconnect connect
ok 155 mesos - docker ps
ok 156 mesos - docker run with wrong user
ok 157 mesos - docker run
ok 158 mesos - docker run short lived
ok 159 mesos - docker run no resources
ok 160 mesos - docker run with long pull
ok 161 mesos - docker stats
ok 162 mesos - docker-compose ps
ok 163 mesos - docker-compose scale
ok 164 mesos - docker-compose up
ok 165 mesos - zookeeper
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[Swarm-PRs (engine master)] $ /bin/sh -xe /tmp/hudson457407981485380517.sh
+ set +x

---

LGTM


Stabilize sparse-registry

What does this PR try to resolve?
Stabilize sparse-registry

Does not change the default protocol for accessing crates.io

How should we test and review this PR?
Set environment variable REGISTRIES_CRATES_IO_PROTOCOL=sparse or set in config.toml:
[registries.crates-io]
protocol = 'sparse'

Blocking items before stabilization

[X] CloudFront invalidation deployed

[x] CloudFront invalidation approved by infra team as sufficiently stable

[X] https://github.com/rust-lang/cargo/pull/11062 (wait for publish) landed
[ ] crates.io team give a positive confirmation that they are ready to support the http index and the traffic that will be coming its way.
[X] Send description of sparse protocol to registry implementors for feedback

Closes #9069

r? @weihanglo
(rust-highfive has picked a reviewer for you, use r? to override)

Let me tag T-cargo first

Stabilize sparse-registry for accessing index.crates.io.
* Does not stabilize for alt registries.

* Does not change the default.

So I know why we aren't changing the default yet but how come we aren't supporting alt registries yet?  I guess I missed that part of the conversations and my very quick scan of the tracking issue didn't turn anything up.

how come we aren't supporting alt registries yet?

I don't think we're fully happy with the URLs having the sparse+ prefix. I want to do some experimenting with auto-detecting the protocol.

I am all for auto-detecting the protocol. But even if that worked we would still have an explicit form to allow people to disambiguate. Why not stabilize the explicit form now, and the auto detecting form when it's ready?

:umbrella: The latest upstream changes (presumably #11230) made this pull request unmergeable. Please resolve the merge conflicts.

There are a few points that I would like to resolve before moving for stabilization:

The invalidation looks like it has landed, but has it been deployed? It sounded like it required some additional keys to be set by the infra team, have those been deployed? I think it would be good to have some period of testing of those changes before stabilizing.
I'd like to see #11062 land before stabilizing, and have at least some time of testing it.
I'd like to have the crates.io team give a positive confirmation that they are ready to support the http index and the traffic that will be coming its way.
In the 2022-09-06 meeting, we discussed sending a full description of the sparse design to other registry implementers to get their feedback (since the RFC was intentionally not fully specified).  I apologize that I have not done that, yet. I will try to work on it as soon as I can. I would prefer to solicit some public comment on something that is likely a large, impactful change.

The last two seem like big blockers. Thank you for bringing them up.
The first two seem like they should block changing the default, not making the new sparse available as an opt in. But opinions can certainly differ.

Thanks for the feedback.

The invalidation hasn't been deployed yet. I'll look into that with the infra team.
JFrog has already implemented support for the sparse protocol, so it would be good to see if they have any feedback.

:umbrella: The latest upstream changes (presumably #11062) made this pull request unmergeable. Please resolve the merge conflicts.

Is stabilizing just doing source replacement of the crates.io index an option? I would really like to use this feature at work without distributing a nightly cargo.
With source replacement users have to opt into it so it doesn’t cause a load spike on the crates.io sparse index.

In https://rust-lang.zulipchat.com/#narrow/stream/318791-t-crates-io/topic/stabilize.20sparse.20index @pietroalbini said:

ok, yeah, then I don't think I have blocking concerns
I'm still worried a bit about the reliance on invalidations, but for the future if we switch cargo to use the merkle protocol then the traffic to the sparse index will likely drop to something where a really short ttl or no caching at all wouldn't break the bank

How do we wish to proceed? Checkboxes for all three teams? Ask for a more formal statement from the other two teams and checkboxes from cargo team? Take this is good enough?

Can someone start an FCP for T-crates-io, T-cargo and T-infra teams? Will it even work on this repo, or do I need to create an issue in rust-lang/rust?

The command is documented here, but I never did any cross team FCP. Maybe @ehuss know how to.

I'd like to see the documentation ready before calling for FCP.  I think it is an important step to help people making a decision to be well informed on exactly what is being stabilized.

:umbrella: The latest upstream changes (presumably #11480) made this pull request unmergeable. Please resolve the merge conflicts.

@arlosi I force-pushed an update to fix the tests for CI.

@rust-lang/cargo This is a proposal to stabilize sparse-registry support.
In summary:

The protocol: The sparse protocol exposes the index via HTTP, with the same structure as a git index.
crates.io opt-in: The registries.crates-io.protocol = "sparse" config option is added to opt-in to the sparse protocol for crates.io.

Future opt-out: At some point in the future, we may consider changing this to be the default (and a user can set this to "git" to opt-out). A risk factor here is that users may have networking configurations that prevent them from accessing index.crates.io. Additionally we are uncertain about the reliability of cargo publish (discussed below).
crates.io infrastructure: The crates.io index is now available at https://index.crates.io/, which is backed by CloudFront.

Alternate registry URLs: Other registries can use the sparse+ prefix in the URL to refer to a sparse registry, such as sparse+https://example.com/index.
Alternate registry transitions: The transition plan for alternate registries is not complete, and is tracked in #10964. In particular, since the URL is embedded in Cargo.toml, Cargo.lock, .crate files, and the index itself, Cargo will need to gain the ability to canonically map URLs to support transitioning from an existing git index (or to support both git and sparse concurrently). This mapping for crates.io is built-in to Cargo since it knows both URLs and knows they should be treated identically. In the meantime, alternate registries can use source replacement (which handles this mapping) to work around this limitation.
Publish timeouts: A risk factor is if a user opts-in to the sparse index and uses cargo publish to publish a package. It can sometimes take longer for the sparse index to update due to caching issues. cargo publish will wait up to 1 minute for the index to be updated, which may not be long enough. In our testing so far, it seems to be fine, but if there is a backlog or other hiccup, it can make it more challenging for users to publish multiple packages that depend on one another. The unstable -Zpublish-timeout option is available to adjust that 1 minute timeout, though our plans around that are currently uncertain.
Future design: A future direction is to use a new structure, perhaps something like a Merkle tree, which provides improved properties such as atomic updates, automatic cache-busting, and more. This is tracked in #10928. We have decided to proceed with the current design because we think a new index structure will present a implementation complexity hurdle that will significantly delay the rollout, and also make it harder for alternate registries.
Current issues: Current open issues are tracked in Z-sparse-registry. None of these appear to be blockers to me.

This PR contains documentation for how it works, please see that if you want more details.
@rfcbot fcp merge

The description mentions the protocol spec being sent to folks for review, but is there a standard place where we can link said protocol spec for any passive readers wanting to implement this themselves?

The protocol spec is included in this PR. You can read it now at https://github.com/rust-lang/cargo/blob/c015bfd1efb04c0bf60df9bfef2b8b3b6633310b/src/doc/src/reference/registry-index.md#index-protocols. That will be published in the corresponding nightly docs when this PR is approved and merged upstream, and then will make its way to the stable docs when 1.68 is released.

:umbrella: The latest upstream changes (presumably #11538) made this pull request unmergeable. Please resolve the merge conflicts.

@ehuss wasn't this supposed to also include infra and crates.io?

@pietroalbini, they were created as separate issues:

https://github.com/rust-lang/cargo/issues/11536
https://github.com/rust-lang/cargo/issues/11537

Oh, that's what I get from having a huge backlog of notifications and not checking all of them, sorry for the noise!

@bors r+
🎉

:pushpin: Commit 7dc55067569e99bf8fe4a23f38e1ec511f71e27d has been approved by Eh2406
It is now in the queue for this repository.

:hourglass: Testing commit 7dc55067569e99bf8fe4a23f38e1ec511f71e27d with merge 985d561f0bb9b76ec043a2b12511790ec7a2b954...

:sunny: Test successful - checks-actions
Approved by: Eh2406
Pushing 985d561f0bb9b76ec043a2b12511790ec7a2b954 to master...


Circle MarkSymbolizer: support explicitly only fillOpacity and update unsupportedProperties

Now it has the same behaviour as SLD and openlayers parsers: explicitly only support fillOpacity and ignore global opacity. I updated the unsupportedProperties accordingly.
~But I apologize for not updating the test. As I'm not familiar with the test framework, I wasn't able make it work.~ Thanks.
Edit: managed to fix the test

Sorry I wasn't able to add a test, so as you said I created the issue #139.

Hey @ocruze, any chance you can rebase this PR so we can merge it?

Hi, I rebased onto my branch. But I'm getting lint errors "haloOpacity does not exist in type SupportInfo". Are you already aware of it?

The property haloOpacity only exists on the TextSymbolizer and the IconSymbolizer so there is no need to add it to the ??unsupportedPropertiesof theMarkSymbolizer`.
If you think the MarkSymbolizer should have halo properties, please create an issue on the geostyler-style repository.


Protocol Header implementation

In section 6.4 Protocol Header it is said that

Each JSON starts with a header.  In the following sections, the following fields will be referenced as header for readability. The header consists of the following individual elements. The header is not a JSON object.

So could you please explain what exactly is meant by 'the header is not a JSON"? Is it not a part of the JSON message and instead a variable header in the mqtt protocol? Or is it not a JSON object in a sense that it is not a separate JSON object but just fields in the mqtt message?

the header is not an Json object, but all fields of the header are included in the payload object for exampel:
{
"headerId": 3,
"timestamp": "2020-11-10T10:19:35.362201Z",
"version": "1.012.0",
"manufacturer": "SEW-EURODRIVE",
"serialNumber": "IAD000",
"instantActions": [{
"actionId": 1,
"actionName": "initialize",
"blockingType": "hard",
"actionParameters": [{
"key": "x",
"value":  0.0
},{
"key": "y",
"value": 0.0
},{
"key": "theta",
"value": 0.0
},{
"key": "mapId",
"value": "SEW_graph"
}
]
}
]
}
the bold data are the header fields


Cannot pull the ghcr.io/srl-labs/clab docerk image: permission denied.

I am trying to use the official docker image from ghcr.io but I am getting a permission denied.  I haven't tried logging in with a PAT but I am under the impression I shouldn't need to?
$ docker pull ghcr.io/srl-labs/clab
Using default tag: latest
Error response from daemon: Head "https://ghcr.io/v2/srl-labs/clab/manifests/latest": denied: denied

ghcr being intermittently wonky maybe (as is so much more frequent lately IME)? just tried and was able to pull. generally I think "yeah, should be able to pull w/out logging in np"

After (very little) more digging I had an empty auth section in my docker.config for some reason.
$ cat ~/.docker/config.json
{
        "auths": {
                "ghcr.io": {}
        },
        "credsStore": "desktop",
        "currentContext": "desktop-linux",
        "plugins": {
                "-x-cli-hints": {
                        "enabled": "true"
                }
        }
}%
$ docker logout ghcr.io
Removing login credentials for ghcr.io
$ docker pull ghcr.io/srl-labs/clab
Using default tag: latest
latest: Pulling from srl-labs/clab
7264a8db6415: Already exists
42f7baef3c3d: Pull complete
01086109fb4b: Pull complete
6aebd6b0fd8a: Pull complete
Digest: sha256:52758efb18d0f1ca5a3d7c84bd522218fbff794cb3e92026df0fffc04afecc79
Status: Downloaded newer image for ghcr.io/srl-labs/clab:latest
ghcr.io/srl-labs/clab:latest

What's Next?
  View summary of image vulnerabilities and recommendations → docker scout quickview ghcr.io/srl-labs/clab


pyscf module changes the logging time

When I import pyscf (version=1.7.6)  as a module, the logging time will be changed:
Without importing pyscf, the logging time is correct:
import logging

logger = logging.getLogger(__name__)
logger.setLevel(logging.INFO)
log_handler = logging.StreamHandler()
log_handler.setFormatter(
    logging.Formatter("%(asctime)s - %(filename)s:%(lineno)d - %(message)s")
)
logger.addHandler(log_handler)
logger.info("666")

Outputs:
2021-08-24 09:25:59,796 - test_logtime.py:17 - 666

After importing pyscf module:
import logging
import pyscf

logger = logging.getLogger(__name__)
logger.setLevel(logging.INFO)
log_handler = logging.StreamHandler()
log_handler.setFormatter(
    logging.Formatter("%(asctime)s - %(filename)s:%(lineno)d - %(message)s")
)
logger.addHandler(log_handler)
logger.info("666")

Outputs:
1970-03-17 00:21:03,611 - test_logtime.py:16 - 666

I have checked that the system time is correct. So what have pyscf done ?  The loging time in the following pic makes me uncomfortable:

Coincidentally, I saw very similar behaviour in an application of my own just yesterday, and had been meaning to go looking for the cause myself.
I don't think this is an issue with PySCF itself. The reason I say this is that I use multiple machines, all with PySCF 1.7.6 installed (so identical code being executed as far as PySCF goes), but this behaviour only happens on some of them. For example, on my laptop (which runs Ubuntu 18.04), your example produces "normal" output:
2021-08-24 08:10:37,808 - script.py:11 - 666

If I run the exact same script on a machine running CentOS 7, I get
1970-01-15 20:19:07,675 - script.py:11 - 666

The obvious difference between the two would be the versions of dependent libraries that are installed. Just out of curiosity, which versions of numpy, scipy, and  h5py do you have installed?

OK, well, at least I can tell you what's happening, although I don't know how yet. The issue is that at some point during the import pyscf call, the time module is being somehow interfered with. Specifically, time.time is replaced with time.perf_counter. Check this out:
In [1]: import time

In [2]: time.time
Out[2]: <function time.time>

In [3]: time.perf_counter
Out[3]: <function time.perf_counter>

In [4]: import pyscf

In [5]: time.time
Out[5]: <function time.perf_counter>

In [6]: time.perf_counter
Out[6]: <function time.perf_counter>

Since the logging module uses time.time to get the strings for the logs, that's causing the weird output. The output of perf_counter() is a much lower number than time.time(), so when you convert it into a datetime string, it thinks we're back in the 1970s. See this wikipedia article if you're interested to know exactly why.
I have no idea why this is happening (yet) -- and again, note that this only happens on some environments for me.
The PySCF logging code does touch both time.time and time.perf_counter, but I can't find a place where it sets them.
However, I tried the above with import numpy, import scipy, and import h5py, and it doesn't happen. So maybe my first assessment was wrong and this is actually due to PySCF itself, somehow.

Thanks for your kindly reply. I test it on both Ubuntu 18.04 and Ubuntu 20.04, all comes with the weired time output. As for the versions:
In [1]: import scipy

In [2]: scipy.__version__
Out[2]: '1.6.1'

In [3]: import numpy as np

In [4]: np.__version__
Out[4]: '1.20.1'

In [5]: import h5py

In [6]: h5py.__version__
Out[6]: '3.2.1'

In [7]: import pyscf
/home/fdd/anaconda3/envs/jax_cuda112/lib/python3.9/site-packages/pyscf/lib/misc.py:46: H5pyDeprecationWarning: Using default_file_mode other than 'r' is deprecated. Pass the mode to h5py.File() instead.
  h5py.get_config().default_file_mode = 'a'

In [8]: pyscf.__version__
Out[8]: '1.7.6'

The test case you provide is interesting. I think pyscf must have done something related to it.  I just hope someone who are familiar with pyscf could solve it.

In pyscf-1.7, time.time was replaced by time.perf_counter for python >= 3.8. This problem is properly fixed in pyscf 2.0. Pip wheels for pyscf-2.0 were not built. To get pyscf-2.0, the only choice is to compile the source code from github at the moment.

Thanks for your explaination. Closed.


Anamika

Created a branch,created a file and made a commit,and opened a pull request

Something new

Something new

Something new

Something new


uif-choicefield-option not selected after load

I've added a uif-choicefield-group with multiple uif-choicefield-option's on my page as follows:
<uif-choicefield-group ng-model="form.doccacc">
    <uif-choicefield-group-title><label class="ms-Label">Kundenzugriff</label></uif-choicefield-group-title>

    <uif-choicefield-option uif-type="radio" value="true">Ja</uif-choicefield-option>
    <uif-choicefield-option uif-type="radio" value="false">Nein</uif-choicefield-option>
</uif-choicefield-group>

and this is how the corresponding controller looks like:
.controller('appController',function($scope){
    $scope.form = {
        doccacc: false
    };
})

Expected Behavior
After page load, the corresponding uif-choicefield-option should be preselected:

Actual Behavior
None of the uif-choicefield-option's are selected:

Hi @marbetschar,
Looks like the ui-choicefield-group expects a string value for the ng-model binding.
When setting the value to doccacc: "false" the correct option is selected on init:
$scope.form = {
      doccacc: "false"
};

I´m not sure if this is the expected behavior or a bug and I haven´t looked deeper into creating a fix but from having a quick look at the current source I do believe it could support Boolean values with a few small changes to the setViewValue and getViewValue functions.

Not sure it's a bug, but if that is the case @ericivarsson then we should check if the value passed in is a valid boolean value and respect it, not requiring a text value. IMHO it should expect a boolean, not a string. Need to investigate further...

The docs at https://docs.angularjs.org/api/ng/input/input[radio] states that value only supports string values and that you should use ng-value insted for non-string values like boolean in this case.
I have verified that this component word as expected when using ng-value for the uif-choicefield-option elements.
So, it looks like this component works as it should and this issue can be closed. What do you think @andrewconnell?
@marbetschar using ng-value like this should solve your problem:
<uif-choicefield-option uif-type="radio" ngvalue="true">Ja</uif-choicefield-option>     <uif-choicefield-option uif-type="radio" ng-value="false">Nein</uif-choicefield-option>

Agreed... good catch @ericivarsson

@ericivarsson this indeed solved my problem! Thank you both very much for this hint!! Updating the demo page would be fantastic!


[WebApp | Extension] Sort the token by balance

Describe the task

[x] Show the balance on the right

[x] Sort the token by the balance on the Select token when performing actions:

[x] Send fund
[x] Staking

Version test: http://<IP_ADDRESS>:8900/s/QHDs8JESA7ZfXZY

[ ] Refer to mobile

Version test: http://<IP_ADDRESS>:8900/s/mW54N6xXN2wGxqp

[ ] UI bug

Version test : http://<IP_ADDRESS>:8900/s/Yxxb6ZENLCHMY8a

[ ] UI bug on Firefox

Validation passed in case :

Show the balance on the right
Sort the token by the balance on the Select token when performing actions : Send fun, Staking
Show correct token default when send/staking
Refer to mobile
Error page in case select account when transfer

Version test : http://<IP_ADDRESS>:8900/s/TcGr9yKzp3pTJ7s

[ ] Wrong order of tokens by balance when off network

Version test : http://<IP_ADDRESS>:8900/s/aX9Lw8ZocHsoGYs
Validation passed in case :

When turn on network :

Show the balance of the token have $balance
Show the balance of the token have no $balance = 0

When turn off network :

Don't show the balance of the token

[ ] Re-check performance


[Doc] Contribute the Presto (Trino) connector to the Trino project

Background: below are some of the discussions from the Pulsar Mailing List.
We have talked to the Trino community about contributing the Presto/Trino
connector to the Trino project. The Trino community is happy to accept the
connector. So we will stop the work of moving the presto connector out of
the main repo for PIP-62. Instead, we will focus on contributing the presto
connector to the Trino project. After that is done, we will remove the
presto connector from the master.

We will try to make it before the 2.8.0 release. If we can't make it, we
will still release the presto connector for 2.8.0 and remove it once it
lands in upstream Trino.

Marvin is doing the heavy-lifting work on contributing the connector. He
might need your help on the documentation part.

@sijie @MarvinCai
For the doc side, if we contribute the Presto connector to the Trino project, can we still keep the docs on the Pulsar website and add the Presto connector link of the Trino project to the Pulsar docs? In this way, Pulsar can retain traffic and we can upgrade docs conveniently.

https://github.com/trinodb/trino/issues/7852

The issue had no activity for 30 days, mark with Stale label.

Closed as stalled. I believe we need a new initiative if still wiling to contribute the connector to the upstream.


Split commands to create / remove a PM in 2 specific ones

Currently the client sends the same command if he creates a new PM or if he creates a PM that was created on the server. This should be splitted in 2 separate commands. Same for the remove action.

public boolean checkClientAdded <- This should be an internal method (private)
Same for removed


Add nicknames

I don't think this is necessary anymore ? it was directly added through a commit not long after the PR as created.

You would be correct indeed. Since it's already in composer now I'll close this.


Video capturing

I have created a hybrid app with ionic frame work. The app contains a section to capture video and upload it to an external server. The video recording works perfectly in android phone but not in iPhone. I have already given permissions for the same in manifest.xml. But the app not capturing the video. Can any one help me to solve this issue?
Thanks and regards
Divya

Thanks for the issue! Please visit our forum or slack channel for questions about the framework. :smile:
If you believe this is an issue with the framework, please create a new issue with answers to the pre-populated questions:


ServiceMonitor 'APPCMD failed with error code 183' @ docker start for aspnet:4.7.2-windowsservercore-ltsc2016

FROM microsoft/aspnet:4.7.2-windowsservercore-ltsc2016
create a container with some docker run -e environment variables.
docker stop container
docker start container
expected result: container enters and maintains running state
actual result: container crashes, producing error at tail of log when servicemonitor attempts to start up: 'APPCMD failed with error code 183'
known workarounds:
The July-2017 <IP_ADDRESS> version also caused the same symptom and I have had to roll back to <IP_ADDRESS> in order to restart my containers because apparently that version does not attempt to update app.config
I have found numerous "duplicate issues" that have been closed yet the issue remains without a clear answer other than to roll back. Most seem to refer back to iis-docker#42 which is closed, citing a July-2017 update however it seems some problems remain
If anyone has any ideas as to what I might try to allow <IP_ADDRESS> to work in ltsc2016 please let me know and thanks in advance for the help

Can you post your exact dockerfile and the docker run command you use? I recently closed a similar issue in this repo. Perhaps it could provide an answer?

For what it's worth, I am running in to the same error message if I try to restart a container after editing the web.config file.
$ docker run -d -p 8000:80 --name aspnet_sample mcr.microsoft.com/dotnet/framework/samples:aspnetapp
$ docker exec -it aspnet_sample powershell
<edit web.config through powershell>
<refreshing the page in the browser confirms that it is still functional>
$ docker stop aspnet_sample
$ docker start aspnet_sample
$ docker logs aspnet_sample

 Service 'w3svc' has been stopped

APPCMD failed with error code 183

Failed to update IIS configuration

The container is now broken and refuses to start.

Run into the same error with dotnet/framework/aspnet:3.5  image when trying to restart IIS. As already said, the workaround is to downgrade to an old ServiceMonitor version found here.

This is preventing tasks from launching correctly in AWS ECS, using the microsoft base image.


Added getDefinition(uuid)

Added function for getDefinition(uuid) that returns a definition of specified knowledgeset id.

Closed PR since it is a Fork. Have created a new branch for the changes.


Create a simple helm chart

Hey,
I've been using kube-hunter for some time now, and I thought a helm chart was handy although very simple to do.
Here is the PR if you are interested: https://github.com/helm/charts/pull/8031

Thank you so much for this! I see the helm chart has been merged already :-)

You're welcome, it's my way to reward FLOSS. :)
Since it is your software, feel free to create a PR to add yourself in OWNERS and Chart.yaml there!

That's a good idea! PR just created
On Tue, Oct 9, 2018 at 4:33 PM Cédric de Saint Martin <
<EMAIL_ADDRESS>wrote:

You're welcome, it's my way to reward FLOSS. :)
Since it is your software, feel free to create a PR to add yourself in
OWNERS and Chart.yaml there!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/aquasecurity/kube-hunter/issues/48#issuecomment-428239843,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAb_eCOt8j3doJEqw7_O2ILOaEIFwMZsks5ujMHEgaJpZM4XDrAg
.

--
Liz Rice
@lizrice  | lizrice.com | +44 (0)<PHONE_NUMBER>

Any official aquasecurity maintained chart coming soon? The helm/charts repo is now obsolete.


Backend implementation

Hello, thanks for your plugin. Do you also share backend implementation of it? I would like to host it by myself as well :)

That's a good idea.
The backend only needs to be a simple proxy to Unsplash. I moved to Cloudflare workers recently since it's easy to use and has a free tier.
That's the repo. https://github.com/cloudy9101/obsidian-image-inserter-proxy

You need to apply a client id from Unsplash and fill it into the wrangler.yml as CLIENT_ID under the repo.
Then deploy the worker to Cloudflare.
After deployment, you need to go back to this repo and change the endpoint from https://insert-unsplash-image.cloudy9101.com/ to the Cloudflare worker's endpoint like https://xxx.xxx.workers.dev.
Build the plugin and install it from Obsidian.

You may need some knowledge of using Cloudflare workers to finish this. You can try to build it.
I will write a README for the proxy repo this weekend and If you want to follow detailed instructions, keep an eye on it maybe.

I added README for the proxy repo and a setting for the self-host proxy server in the plugin's setting tab in v0.1.6
I will close this issue, please feel free to reopen it if any problem arises.


Error when running git2consul

Hello
I'm trying to run gi2consul.
This is my config.json:
{
  "version": "1.0",
  "repos" : [
    {
      "name" : "sample_configuration",
      "url" : "http://local.test.com/git/ccms/configurations.git",
      "branches" : ["master"],
      "credentials": {
        "username": "user",
        "password": "password"}
    }
  ],
  "consul" :
    {
    "address" : "<IP_ADDRESS>:8500"
    }

but when I try to run git2consul, I got this error:
ubuntu@ubuntu:~/go/src/git2consul-go/build/bin$ ./git2consul -config config.json
  INFO[0000] Starting git2consul version: 0.1.0
  INFO[0000] Setting configuration with sane defaults caller=config
  INFO[0000] Loaded repository sample_configuration caller=repository
 ERROR[0001] Runner error              error=reference not found

@amirsoleimanii thanks for opening this issue!
We are hoping to start active development on this project again in the near future.


[Ios] in latest xcode Version 14.0 (14A309) flutter build failed

Error (Xcode): Building for iOS Simulator, but linking in dylib built for iOS, file '/Users/mac/Desktop/multi_vendor/ios/Pods/BRLMPrinterKit/BRLMPrinterKit/BRLMPrinterKit.framework/BRLMPrinterKit' for architecture arm64
Flutter Doctor
flutter doctor

[✓] Flutter (Channel stable, 3.3.3, on macOS 12.6 21G115 darwin-x64, locale en-PK)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc1)
[✓] Xcode - develop for iOS and macOS (Xcode 14.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.71.2)
[✓] Connected device (3 available)
[✓] HTTP Host Availability```
i did all the configuration accordingly but alway xcode give error build faild when running in simulator

Hi @alihassan143 ! Thanks for reaching out about this. Building to the iOS Simulator is not supported, so you'll need to build to a physical device.
Please refer here for more info: https://github.com/CodeMinion/another_brother/issues/28
Thanks again!


Added Java implementation of Average

Additionally  added a unit test for inequalities which must hold, for all average calculations

Thanks!


fixing documentation of Bigg scheme

CC: @s-shima
See https://github.com/scale-met/scale/pull/1
Hope that helps,
Sylwester

Thank you for your contribution.
I have merged the commits into the develop branch.

Great, thanks


Added DateTimeProvider property to RefreshingAWSCredentials.

Workaround for exception "The retrieved credentials have already expired".
This allows using other DateTime source (NTP) instead of device time.
Usage:
    credentials = new CognitoAWSCredentials(poolId, region);
    credentials.DateTimeProvider = GetDateTime;

...

    private DateTime GetDateTime()
    {
        // Reading and writing DateTime is not thread safe
        lock (dateLock)
        {
            return reliableDate;
        }
    }

Related issues: https://github.com/aws/aws-sdk-net/issues/393 https://github.com/aws/aws-sdk-net/issues/402

Thank you for submitting this PR.
The approach looks straight-forward, but I'm concerned that it's fairly specific to refreshing credentials. This works fine for this case, but there are other places in the SDK that are impacted by an incorrect device time, such as generating S3 pre-signed urls. If we go with this approach for credentials, we'll end up having to keep adding similar solutions (DateTime delegate) for other use-cases.
An alternative approach we're thinking about is to provide a property TimeSpan? ManualClockCorrection to the Amazon.AWSConfigs class, making it possible for a user to set this to the difference between device clock and "actual" time. This property would then be used to determine the "correct" current time, and will be used everywhere the SDK currently uses DateTime.Now or DateTime.UtcNow. Would this approach work for you? Do you see an issue with using a static offset and not a delegate?

I have opened a new PR https://github.com/aws/aws-sdk-net/pull/427 for property TimeSpan? ManualClockCorrection.

Delegate is  preferred over Delta as it gives better control to user. I am using third party tool to detect actual time, delegate would simply route it to third party library.


Swap to um2netcdf standalone

Closes #78.
This pull request updates the ESM1.5 conversion driver to use the new um2nc-standalone version of um2netcdf, rather than the older um2netcdf4.

There's one remaining um2netcdf4 reference in the recently merged config code:
https://github.com/ACCESS-NRI/um2nc-standalone/compare/78/driver-swap-um2nc-standalone...develop#diff-3ab46ee209a127470fce3c2cf106b1a1dbadbb929a4b5b13656a4bc4ce19c0b8R94
@blimlim  Do you mind merging the new develop changes into this PR, then removing the netCDF4 reference?
This should also exercise the linter settings on the git push.

Yep no worries – I've made that change


Issue with latest lru-cach v7.4.0

Dependabot is failing to upgrade the lru-cach library from 6.0.0 to 7.4.0 because the tests fail.
Check the failing PR here: https://github.com/nearform/get-jwks/pull/116

for the future. we don't actually need an issue to fix dependabot broken PRs. we can just use the PR as the issue and push code to it

The issue happens because v7.4.0 deprecates maxAge option and ttl should be used instead. I'll close the PR and open a new one where I'll update the code and docs.


Added ability to navigate with menu buttons

Added ability to navigate with browser forward/backward buttons as per #48

Moved item/module loading from the mod (data set) loader. Now loadData only gets mod data and stores it appropriately. loadModules and loadItems have been added.

Functions that change the hash now have an optional parameter called dontChangeHash

Stopped the last item being removed - it causes errors and there's no reason to remove it

Also fixes furnace bug #60

some weird stuff going on - I'll look into it tomorrow. It usually works...

Add load/save/reset settings
Settings page:

Added reset settings button (resets to default)
Added save/load custom settings button (stored in localStorage.settings, excludes the mod/data-set)

Save/load buttons are hidden when localStorage is no accessible
loadSettings now loads saved custom settings by default if all settings are default (if the user likes the default settings, then they can save default settings as custom settings so they aren't forced off the default settings or they can simply not save the custom settings)
Fixed bug where hash wasn't updated when browsing to calc.html (with no hash)
Moved hashchange detection initialization out of the DOMContentLoaded listener - it doesn't need to be there.

FYI, I have just pushed 8330172f5f244d9248824a7f586b4c310f95aec8, which directly impacts portions of this PR and will require resolving the merge conflicts.

I don't like that this PR addresses at least three different issues. (Default settings, forward/back buttons, and the furnace setting thing.) This isn't enough to make me reject the PR, but in the future, please keep things more focused.

Sure, I (believe it or not) tried to.
Do you know how to push future commits without them automatically being added here? It's my first time doing this pull request thing.
I'll work on your comments

I am also not very familiar with how github does PRs, but I believe the PR applies to a specific topic branch in your fork (in this case, the master branch). So you could push changes to other branches, and they should not affect this PR.

Closing because I'm splitting browser navigation and setting saving into different pull requests (for personal experience as well as making the pull request less confusing)

I don't know how to PM you, so here's my question: should the load/save/reset settings also handle the mod/data-set or should it ignore it? I'm in two minds about it -
On one hand the mod is on the settings page, and everything else is being saved so it makes sense for the mod to be included (and the mod should be loaded by default if the user is using the mod).
On the other hand the mod is unlikely to be changed, and if the user changes it they probably don't want it to be changed back when they load their settings.

I'm also thinking that the ignore-list should be automatically stored in localStorage (in a future commit) because it is very unlikely that the user would want individual ignore-lists (and prefer to start with nothing ignored) for each design. The mod/data-set setting could be included with the ignore-list and be automatically processed separate from the other settings.

I believe that the dataset must be part of the stored settings. In the future, when I add datasets other than vanilla, some of the settings will gain additional options when using those mods. For example, Bob's adds additional assemblers, and so the "minimum assembler" setting may be set to something that is not present in the vanilla dataset.
Indeed, the number of settings might itself change depending on the dataset, but that's something I'll be addressing in the future.
This is also why the settings tab re-renders itself whenever the dataset is changed.
As for the ignore list, I see it as being more akin to the user's selected items and modules than to their settings. The user is designing a factory, and I see the items they wish to ignore as being part of defining that factory, rather than a setting defining how they wish to use the calculator. If that makes sense. This distinction is somewhat vague, I admit, but I'm not convinced that this should be a saved setting.


feat(bpmn-js-plugin): append c7 element template as module

Description
Use bpmn-js plugin for creating/appending C7 Element Templates.
Checklist

Code is easy to understand
No obvious errors or bugs
CI/CD Pipelines did run successfully
Tests were implemented
Documentation was created

Codecov Report
Patch and project coverage have no change.

Comparison is base (8bf1877) 61.94% compared to head (62b25ed) 61.94%.

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #330   +/-   ##
=========================================
  Coverage     61.94%   61.94%
  Complexity       49       49
=========================================
  Files            35       35
  Lines           452      452
  Branches         42       42
=========================================
  Hits            280      280
  Misses          130      130
  Partials         42       42

Flag
Coverage Δ

unittests
61.94% <ø> (ø)

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

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

Great job @peterhnm!


Invalid memory regions with complex if conditions

typecheck-annotate-size := λ(: tt Type). (: (tail(
   (if (typecheck-is-sized tt) () (
      (if (==( (typecheck-is-sized tt) typecheck-do-not-size )) () (tail(
         (let sz (typecheck-annotate-size-inner tt))
         (let tt2 (maybe-deref(typecheck-annotate-size-recurse tt)))
         (let tt3 (maybe-deref(tand(
            tt2
            (TGround(
               'Sized_s
               (close (TypeSeq(
                  (close TypeEOF)
                  (TGround(
                     (to-string sz)
                     (close TypeEOF)
                  ))
               )))
            ))
         ))))
         (set tt tt3)
      )))
   ))
   tt
)) Type);

This has something to do with the tail condition. The bug doesn't happen in the true branch.

The return position is the problem, dup.


fixed java.lang.StringIndexOutOfBoundsException

fixed java.lang.StringIndexOutOfBoundsException where value is an empty string

Hi @hone-liu ,
Thanks for this PR. Do you have a reproducible test case by any chance? That would help avoiding regression in the future.
To be honest, I'm a bit surprised you can send an empty string as a valid value for a char.

Not sure if this change is the right way to achieve this. @vladmihalcea has released a custom type for this: https://vladmihalcea.com/how-to-implement-a-custom-basic-type-using-hibernate-usertype/ . Maybe he can shed some light on this.

Yes, I must admit I'm not very convinced. That's why I would like to see a proper use case.

Closing due to the lack of a JIRA issue and test case


Vimari does not work together with Alfred

In the past a few people had the issue, that vimari didn't work at all. I had the same issue and found that when Alfred (https://www.alfredapp.com) is enabled, vimari stops working.
Currently I don't have time to look further into it.
Safari: Version 11.1.2
Vimari: Version 1.12
Alfred: Version 3.6.2
Is there a solution/workaround for this?

Thank you. I was referring to https://github.com/guyht/vimari/issues/74
Vimari does work now but I don't know what caused the issue. Reinstalled Vimari and Alfred and it works.


Webpack 2 bug: "ReferenceError: exports is not defined"

Cross-posting from https://github.com/webpack/webpack/issues/3974#issuecomment-301513533 for visibility.

I can consistently reproduce this in CRA codebase:
git clone https://github.com/facebookincubator/create-react-app.git
cd create-react-app
git checkout 9e733b57f8ae7ae3df46d95910d255798107448f
npm install

npm start

Then edit packages/react-scripts/template/src/App.js to have an empty block in the render method:

Press save. The browser will reload.
Then edit it to remove the empty block and press save.
You will see the error:

Unfortunately some internal state appears corrupted because even if I refresh the page, I keep getting the broken bundle. It only gets fixed by a restart of the server.

It looks like a caching issue caused by babel-loader. I probably had some version of the module cached with CommonJS transform applied, and it was getting embedded into the bundle. Deleting node_modules/.cache fixed the issue.

Maybe using https://github.com/facebookincubator/create-react-app/pull/2092 will alleviate future cache problems?

I would actually expect the opposite effect 😄 Caches are har.d


[SPARK-34290][SQL] Support v2 TRUNCATE TABLE

What changes were proposed in this pull request?
Implement the v2 execution node for the TRUNCATE TABLE command.
Why are the changes needed?
To have feature parity with DS v1, and support truncation of v2 tables.
Does this PR introduce any user-facing change?
Yes
How was this patch tested?
By running the unified tests for v1 and v2 tables:
$ build/sbt -Phive -Phive-thriftserver "test:testOnly *TruncateTableSuite"

Test build #135323 has started for PR 31605 at commit 8db6847.

Test build #135324 has started for PR 31605 at commit 7711248.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39903/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39904/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39904/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39904/

Test build #135323 has finished for PR 31605 at commit 8db6847.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135323/

Test build #135324 has finished for PR 31605 at commit 7711248.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135324/

@cloud-fan @HyukjinKwon Could you review this PR, please.

@MaxGekk can you fix the conflicts?

Test build #135383 has started for PR 31605 at commit 3534a2b.

thanks, merging to master!


easytier: 1.2.3 -> 2.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for easytier is: Simple, decentralized mesh VPN with WireGuard support
meta.homepage for easytier is: https://github.com/EasyTier/EasyTier
meta.changelog for easytier is: https://github.com/EasyTier/EasyTier/releases/tag/v2.0.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.0.0 with grep in /nix/store/2rhnzb293b8phq718d13ci8aqja2igk5-easytier-2.0.0
found 2.0.0 in filename of file in /nix/store/2rhnzb293b8phq718d13ci8aqja2igk5-easytier-2.0.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

easytier

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2rhnzb293b8phq718d13ci8aqja2igk5-easytier-2.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A easytier https://github.com/r-ryantm/nixpkgs/archive/b314d03bb29072aa763b3940bce9fd251fe40643.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b314d03bb29072aa763b3940bce9fd251fe40643#easytier

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2rhnzb293b8phq718d13ci8aqja2igk5-easytier-2.0.0
ls -la /nix/store/2rhnzb293b8phq718d13ci8aqja2igk5-easytier-2.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

easytier

Maintainer pings
cc @L-Trump for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Document a callback with multiple arguments

It would be nice to document what happens when you promisify a node function with a callback that takes multiple arguments. Here is an ES6 example you could maybe use:
import tmp from 'tmp';  // node builtin

let createTmpDir = promisify(tmp.dir);
createTmpDir()
  .then((args) => {
    let [tmpPath, removeTmpDir] = args;
    // ...
  });

For those unfamiliar with promises, they would expect it to look more like:
createTmpDir()
  .then((tmpPath, removeTmpDir) => {
    // ...
  });

I think you got it the other way around. Promises always return a single value (could be an Array of values, of course. see Promise.all()). Callbacks indeed could take more than just (err, value).

I think you got it the other way around.

Was my proposed example incorrect? It was just a sample, the docs could contain any example.

Promises always return a single value

I know but to me it was not totally obvious how es6-promisify would wrap a node-style function that executes a callback with multiple args. If you think it's obvious then feel free to close the bug. It should be easy to document how a callback with multiple args gets wrapped by es6-promisify though, it's only a couple more lines in your docs. You could copy/paste what I added here.

I fully agree! :+1: I'd like that documentation and actually I don't even know what es6-promisify does in this case, do you?
I have misread the description of your second snippet: "For those unfamiliar with promises, THEY would expect it to look more like:". Sorry :smile:

I don't even know what es6-promisify does in this case, do you?

Yes. My first example is correct, I tried it. You have to use it like this:
import tmp from 'tmp';  // node builtin

let createTmpDir = promisify(tmp.dir);
createTmpDir()
  .then((result) => {
    let [tmpPath, removeTmpDir] = result;
    // ...
  });

Pull requests cheerfully accepted :)

Pull requests cheerfully accepted :)

Feel free to close the issue, it was just a suggestion. I don't have time for a patch right now. Maybe later.

This issue can be closed now. I just saw the new multiArg feature and it seems well documented: https://github.com/digitaldesignlabs/es6-promisify#handle-callback-multiple-arguments
FWIW, I don't fully understand this change. Any reason why multiArg: true isn't the default behavior? I can't think of a situation where one would expect it to work like multiArg: false. It seems convenient as a shortcut but it is confusing if you need to reach multiple callback arguments. Anyway, I updated my use of promisify() with {multiArg: true} and it's working fine.


Resolves: https://github.com/scylladb/scylla-operator-images/issues/10

@tnozicka shall download-file.sh script be moved out to shared utils?

@tnozicka shall download-file.sh script be moved out to shared utils?

@tnozicka shall download-file.sh script be moved out to shared utils?

it's not as straight forward because of the build contexts

true, out of the options I suppose that's a cleaner one


[Ramsey\Uuid\Exception\UnsatisfiedDependencyException]

`D:\WWW\oauth>php artisan api:generate --routePrefix=v1/*
Wrote index.md to: public/docs
Generating API HTML code
Wrote HTML documentation to: public/docs/public/index.html
Generating Postman collection
[Ramsey\Uuid\Exception\UnsatisfiedDependencyException]
When calling Ramsey\Uuid\Converter\Time\DegradedTimeConverter::calculateTime on a 32-bit system, Moontoast\Math\Big
Number must be present.`
I use win10 64-bit system, What does this exception mean?

Fixed in https://github.com/mpociot/laravel-apidoc-generator/commit/c1a50b523f2558cc9f58c5cfbbbf74ea1fe65f47

Wrote index.md to: public/docs
Generating API HTML code
Wrote HTML documentation to: public/docs/public/index.html
Generating Postman collection
docs folder is create but not came all route in my docs
only display info column
i m using windows 8.1 with 64 bit system
$collection = [
'variables' => [],
'info' => [
'name' => '',
'_postman_id' => Uuid::uuid4()->toString(),
'description' => '',
'schema' => 'https://schema.getpostman.com/json/collection/v2.0.0/collection.json',
],


JBEAP-15278 ARTEMIS-2030 only use interrupt during shutdown on RA

(cherry picked from commit 99d091a0eaa07f042ce5d689bff9a3bd5880f1b3)
Issue: https://issues.jboss.org/browse/JBEAP-15278
upstream issue: https://issues.apache.org/jira/browse/ARTEMIS-2030
upstream PR: https://github.com/rh-messaging/jboss-activemq-artemis/commit/4104986d04d50cd402f7986e785ce0d44b68a6fe

Can one of the admins verify this patch?


@meplum/cli authorize url generation problem

Hello Medplum,
Need you attention to this line in @medplum/cli sources:
https://github.com/medplum/medplum/blob/c3754a93feaab4b25297778379c789b5b22f12fd/packages/cli/src/auth.ts#L27
First slash in '/oauth2/authorize' trigger producing of url as :/oauth2/authorize and deletes a path from a medplum base url (if it presented).
And if i have medplum base url as for example 'https://example.com/medplum' - i have a problem. But if you may edit code, presented earlier, be removing first slash, it problem would be solved.

@alexgoto Thank you for filing the issue and providing helpful code pointers. We've merged #2217, let us know what else we can do to help.

@tonylee80 Thank you. Now it works good


False positives with 953110

Description
Roundcube has a function that allows users to import emails into their mail account. 953110 is matching the text Maximum allowed file size is 10 MB and is loaded everytime the mailbox is opened.
I've tuned away this false positive but this seems like something that can be very common.
Logs
Maximum allowed file size is 10 MB

Matched Data: file size is
Your Environment

CRS version (e.g., v3.3.4): CRS 4 Dev Latest
Paranoia level setting (e.g. PL1) : 1
ModSecurity version (e.g., 2.9.6): libmodsecurity 3.0.10
Web Server and version or cloud provider / CDN (e.g., Apache httpd 2.4.54): Nginx
Operating System and version: Ubuntu

Confirmation
[x] I have removed any personal data (email addresses, IP addresses,
passwords, domain names) from any logs posted.

Hi!
Thanks a lot for your report.
I can't reproduce your issue. When I test your string Maximum allowed file size is 10 MB against the regex of rule 953110 I don't see a match:
https://regex101.com/r/PtSVnW/1
This would perfectly fit into a Roundcube exclusion plugin. As long as we don't have such an exclusion package, I don't think we'll adapt the current rule 953110.

In fact @EsadCetiner is contributing several Roundcube exclusion packages.
https://github.com/coreruleset/plugin-registry
If we can reproduce I do not rule out patching the core rule set rule itself, since this sounds so generic. Can you help us here Esad?

@dune73 @franbuehler Sorry, I meant the rule 953100. Please see https://github.com/coreruleset/coreruleset/blob/1fe255d06a282927fce55d6907a497b35a0e7a96/rules/php-errors.data#L1785

Ah! This exclusion package is not yet in our coreruleset repository, therefore I didn't find it.
But, yes! Then this help would be very welcome!

I just want to clarify the FP is already fixed in the plugin, but ideally it should be fixed within CRS.

Thank you for this essential context.

@EsadCetiner, we discussed your finding in the team and we agree that it should be fixed in CRS. We think that the phrase should be moved to the file php-errors-pl2.data, that already contains some of the error strings that are prone to FPs at paranoia level 1.
Would you be willing to create a PR?

@M4tteoP has been very eager to get this done. He has provided a PR in the meantime. See #3314.

Looks like he beat me to it 😄
If there's nothing wrong with the PR then I don't see why it shouldn't be merged.

Adding just some more tests right now :)

He's a fast one.


ed25519-java don't include the license file

Not available LICENSE file in source directory structure
Please. Added license and copyright notice.
the fedora pakaging guideline is very strictly precise about this problem
https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text
thanks
regards

I'm unsure of what I need to do. The README clearly states that the code is released into the Public Domain, and therefore there is no license text to include. The guide does only say that upstream should be "encouraged", not required, to include license text if it is not a requirement of the license.
Could you please clarify how the License Text section of the Licensing Guide interacts with the Public Domain section?

Hi
talking with our staff that takes care of these issues, we have concluded that it is no longer necessary to add the license file. although other projects with the same do
regards

@str4d It's standard practice to add a LICENSE file even if you want to release it for Public Domain. Having such file is really helpful for upstream packagers and will avoid issues like this one.
If you want to place it under Public Domain go with one of the following "licenses": The Unlicense or Creative Commons Zero.

as e.g.  see https://github.com/davidB/scala-maven-plugin/blob/master/UNLICENSE

@dllud thanks, this is exactly what I was asking about.
Based on my further reading, Unlicense has significant issues, but CC0 appears to be alright for software, and is what I shall go for.
Just to ensure that all the legal boxes are ticked off: If you are one of the 6 contributors, do you consent to this change in license? If so, please leave a comment on this issue saying 'yes' or 'lgtm' or however you typically express consent.
I expect no one to have any issues, as this repo has been marked as public domain since before I forked it from @k3d3 (the fork is why you're included here btw, even though none of your code is actually in this implementation :P), so it's not really a change in license, but I want to make sure everything is kosher.

[x] @str4d
[ ] @BloodyRookie
[ ] @pmarches
[ ] @k3d3
[ ] @mbakkar
[ ] @majestrate

Yes, of course

Works fine.

ok for me.

yes
On Fri, Dec 25, 2015 at 2:56 PM, BloodyRookie<EMAIL_ADDRESS>wrote:

ok for me.
—
Reply to this email directly or view it on GitHub
https://github.com/str4d/ed25519-java/issues/11#issuecomment-167260436.

yes, woops

sorry for the late response, I'm good for a license change

Woop, that's everyone!


hotfix/pathToReadableError -> dev

This change is

Reviewed 30 of 31 files at r1, 1 of 1 files at r2.
Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable


A docker auth password that contains a colon truncates the password

Expected Behaviour
The docker auth password should not be truncated if it contains a :
Actual Behaviour
The docker auth password is truncated if it contains a :
eg. If the password is password1:1 it will be reduced to password1.
Testcontainer Logs
Since the password is truncated, it ends up producing the unauthorized error:
 testcontainers [ERROR] Failed to pull image "testcontainers/ryuk:0.5.1": Error: (HTTP code 500) server error - Head "https://registry-1.docker.io/v2/testcontainers/ryuk/manifests/0.5.1": unauthorized: incorrect username or password

Steps to Reproduce

Create a docker auth password that contains a colon (:)
Set the credentials in the ~/.docker/config.json
Run your tests with testcontainer

Code
You can clearly see in the code it is currently doing a naive string split on :
https://github.com/testcontainers/testcontainers-node/blob/main/packages/testcontainers/src/container-runtime/auth/auths.ts#L24
A simple fix could be something like this:
const [username, ...passwordParts] = decodedAuth.split(":");
const password = passwordParts.join(":");

I will raise a PR.

Thanks @cristianrgreco. When will a new build be available with this fix?


[update]: Data Center

Details (optional)
This data center definition is almost there. Here's what needs to be added to get it over the finish line:
The problem it addresses touches upon how it helps (the next section): data centers allow companies to..." This section should fully focus on the problem statement which is mentioned in the 2nd sentence.
Please rephrase so:

the problem it addresses only focuses on the problem
move what you say in the first sentence to the next section

I can do this :)

There you go :)

😀👍

Oops, just realized you are also working on debugging. Please note that we can only assign contributors one term at a time. I'll remove you now until debugging is done. Thanks for understanding :)

@CathPag  I can take this one :-)

@CathPag I can fix this

@root21cuib, let's first get digital certificates merged. The technical approvers might have feedback to work in. Thanks for your patience.

@CathPag I would like to work on this

@PrathyushaModala, you asked to be assigned to three issues. We only assign one issue per person. Which one would you like to tackle?

Hi @CathPag ,
When I'm trying to access data center defination url it is prompting as page not found. So,can you please provide detailed information about this issue which helps me in gaining deeper understanding of it.

Hi @CathPag ,
Could you please provide detailed information about this issue.

Hi @CathPag
Looks like no one got assigned to it. Can i work on this??


two additional featues added

one of the additional features lets the user decide how many comments they want to see and the other allows them to delete all of the comments

added these edits!

added those edits


Validation Issue

Challenge Declare String Variables has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.1 Safari/603.1.30.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

// Example
var firstName = "Alan";
var lastName = "Turing";

// Only change code below this line
var myFirstName = "Kumar"
var myLastName = "Ethamukkala"

The issue tracker is for reporting bugs only.
Please use the chat rooms:

HTML/CSS help chat room
JavaScript help chat room
Other Official Rooms

or try looking through our forum for help with a specific challenge.
Happy Coding!

use semicolon at the end.
like this-
var myFirstName = "Kumar";
var myLastName = "Ethamukkala";


test

Enhancement:
Reason:
Result:
Issue Tracker Tickets (Jira or BZ if any):

[citest]

[citest]


⚠ Bofrost.es has degraded performance

In 1357dbf, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1544 ms

Resolved: Bofrost.es performance has improved in 1cb4cfe after 29 minutes.


time-input element has a buggy arrow key navigation.

When arrow keys are used to navigate in the time-input element, it goes up to seconds and goes back to hours instead of milliseconds. When at hours and the left arrow is pressed it goes to milliseconds. This is because of the following code at TimeInputPattern
static get inputTemplate() {
        return `
          ${super.inputTemplate || ''}

            <number-input hidden$="[[hour12]]" index="7" class="time" min="0" max="23" pad-length="2" value="{{hours}}" placeholder="00"></number-input>
            <number-input hidden$="[[!hour12]]" index="7" class="time" min="1" max="12" pad-length="2" value="{{hours12}}" placeholder="00"></number-input>

          [[_localTimeSeparator]]
          <number-input hidden$="[[_hideMinutes]]" style="order:9;" index="9" pad-length="2" min="0" max="59" disabled="[[disabled]]" value="{{minutes}}" placeholder="00"></number-input>
          [[_localTimeSeparator]]
          <number-input hidden$="[[_hideSeconds]]" style="order:10;" index="11" pad-length="2" min="0" max="59" disabled="[[disabled]]" value="{{seconds}}" placeholder="00"></number-input>
          [[_localDecimalSeparator]]
          <number-input hidden$="[[_hideMilliseconds]]" style="order:12;" index="12" pad-length="3" min="0" max="999" disabled="[[disabled]]" value="{{milliseconds}}" placeholder="000"></number-input>

            [[_am]]
            [[_pm]]

        `;
      }

in the number-input for milliseconds it is given 12 for the index . The step for _focusNumberInput method at datetime-input-mixin is 2. This makes the right arrow key event to skip milliseconds.
Correcting the index to 13 solves the issue.

You are right, I change that. If you wonder why it is so strange that I use index and order like that, it is because of the ´local-dateformat´. Thanks

should be fixed in 2.5.1

Glad I could help @fooloomanzoo. Thank you for the fix.


Error thrown during qfx import

First, thank you for this project.
It looks like something in 23.9.0 is breaking .qfx import.
The app displays "Something internally went wrong. You may want to restart the app if anything looks wrong. Please report this as a new issue on Github." when I select a file to be imported.
Happy to provide whatever else you need.

This has been resolved on the edge container (master branch of actualbudget/actual). Expect the patch to make its way in v23.10.0. Or if you want to get it now - feel free to upgrade to edge.


Extended integration tests

This PR introduces an approach of integration testing that does the following:

Deploy a local kind cluster
Build docker images and push to local registry
Deploy manager and test services to local kind cluster
Deploy helm charts to local registry (and test them with sample values against deployed cluster (thus also tests webhooks of CRDs etc))
Run tests that are able to run against an existing cluster (thus tests should just create CRDs and observe if the resulting change in CRD status and possible creation of other K8s objects satisfies the given test)

In order to serve the helm charts in K8s from a local registry the registry has to support TLS. Thus the deployment has been moved to a TLS registry with dummy credentials. Due to a regression bug in Docker this might currently not work for current docker versions(I have issues on OS X) but the bug is fixed in current versions of the compose-cli library and will be fixed in future Docker releases.
The proposal would also be to remove the publish stages afterwards and basically have one stage that builds the images, tests them and if all the integration tests work retag the images to the public URLs and push them (master only action)
I did not remove any other travis stages yet.

Big PR, it will take me time to review it.
Reading your description, did you mean dummy certificates? We don't need password to login right?
Also, can you share reference to the docker bug you referred to? I didn't understand what doesn't work exactly and which environments it affects.

Reading your description, did you mean dummy certificates? We don't need password to login right?

Yes we're creating self signed certs for testing. The username and password are user and pwd as those are dummy values just used for a local registry.

Also, can you share reference to the docker bug you referred to? I didn't understand what doesn't work exactly and which environments it affects.

This is the error message I'm getting with docker. The issue references another PR that is already merged.
https://github.com/docker/compose-cli/issues/712

Yes we're creating self signed certs for testing. The username and password are user and pwd as those are dummy values just used for a local registry.

user and pwd for what?

Reading your description, did you mean dummy certificates? We don't need password to login right?

Yes we're creating self signed certs for testing. The username and password are user and pwd as those are dummy values just used for a local registry.

Also, can you share reference to the docker bug you referred to? I didn't understand what doesn't work exactly and which environments it affects.

This is the error message I'm getting with docker. The issue references another PR that is already merged.
docker/compose-cli#712

I suggest we handle docker installation ourselves, this will enable us using an older version of docker which does not have this bug (https://github.com/docker/compose-cli/issues/712#issuecomment-700812166)

Reading your description, did you mean dummy certificates? We don't need password to login right?

Yes we're creating self signed certs for testing. The username and password are user and pwd as those are dummy values just used for a local registry.

Also, can you share reference to the docker bug you referred to? I didn't understand what doesn't work exactly and which environments it affects.

This is the error message I'm getting with docker. The issue references another PR that is already merged.
docker/compose-cli#712

I suggest we handle docker installation ourselves, this will enable us using an older version of docker which does not have this bug (docker/compose-cli#712 (comment))

I see bo reason to do that. The docker service in Travis does work. Managing docker installation for users is a headache and doesn't really worth the effort.


UI Simplification: Allow changing background media from the panel

Feature Description
See Figma
We will be using the design with button "Replace".
Currently, the background media can be replaced by dragging a new image onto the Page, or by clicking "Set as background" while having another media element selected.
We should allow doing it directly from the Page Background panel as well.

[ ] Add a new "Replace" button.
[ ] This button will open Media library to replace the background media

Alternatives Considered

Additional Context

Let's use this button! thanks @miina

@andrew-askedall One note about the Removal button's style. Currently, only the X is really a button -- in Figma, the existing Removal button looks fully like a button though. It happened once before with UI Simplification vol 1 that the button was changed in Figma like this, however, it was confirmed with Amy that it was by mistake and it should stay as it is now.
Keeping it as it is currently, let me know if we should change it.

Just saw the comments in Figma—"Replace" seemed more obvious but given the points you brought up it would be okay to use this button instead!

Tested against https://stories-qa-wordpress-amp.pantheonsite.io/wp-admin, using PR #10134.

Visited URL above
Selected PR above
Started a new story
Added an image as background
Clicked on the background - upload button is displayed under Page Background section
Button works as expected
Existing button to replace background (beside the canvas) working as expected too


Update CLA assistant to check for newlines/spaces

cc @AndrewGable
Details
This PR updates the CLA assistant to include https://github.com/cla-assistant/github-action/pull/69.
Tests
I've removed myself from the CLA json, will test in comments.

recheck

recheck

recheckcla

recheckcla

recheckcla

recheckcla

recheckcla

recheckcla

recheckcla

recheckcla

recheck

recheck

I have read the CLA Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA

recheck

recheck

Looks great! Thank you

Looks great! Thank you


Allow inserts to alias table names

I'm not sure if all DBs allow this, but at least in postgres you can alias the table. The specific part of the spec that I'm referencing is this:

INSERT INTO table_name [ AS alias ]

So I can write
INSERT INTO some_schema.some_table AS some_alias (col1)
VALUES (1)

Since QueryCreator.insertInto doesn't have any overrides for AnyAliasedTable, there doesn't seem to be a way to do this.

Could we use TableExpression in InsertInto and not Table?


Unable to reply email with attachments

RainLoop version, browser, OS:
Version: <IP_ADDRESS>
Browser: Chrome Version 56.0.2924.87 (64-bit)
OS: Ubuntu 16.04 LTS 64bits
Expected behavior and actual behavior:
When I was trying to reply or reply-all an email, there are no attachments in the attachment area. But it works with forward function.
This is same goes to https://github.com/RainLoop/rainloop-webmail/issues/1091 , but this time is for reply function.
Steps to reproduce the problem:
Just ask someone email you with attachment and when you reply the email, there will be no attachments
Logs or screenshots:
This is the email

When I click reply or reply all, there will be no attachments in the section.

Yeah, why would you want to send the attachments to the guy who sent you the attachments? I believe some clients may have the option to include attachments when replying, but the default is off and I can't see a user-case scenario where this would be useful, not to mention it's a waste of bandwidth to keep sending attachments back and forth.


[Feature] Get the correct permissions after switching team

What changes were proposed in this pull request
Issue Number: close #1844
Get the correct permissions after switching team
Brief change log
Get the correct permissions after switching team
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): no

Hi @wolfboys , I updated this PR base on #1868 , please help review in your free time, thanks~


fix: show data also for pending tx

When clicking on pending tx, not it shows something

Apologies, tried to push to your branch, but seemed to stash the diff 😅
Merged another PR here (your commits are still retained): https://github.com/paradigmxyz/rivet/pull/17
Thanks for the contribution!


Filtering in the voting page

The number of items on the voting page (https://webpack.js.org/vote/) increases over time. Some of the items are already done and may not be interesting for everyone.
Most items already have some kind of tag in front of the title, e. g. [WEBPACK 5] PERSISTENT CACHE.
This tag could be extracted and treated as tag (maybe multiple tags separated by ,). Not locked items would also get the default tag active. Locked items without any other tag would get the default tag untagged (so I can add some tag).
A little selector on top with a few toggle buttons could be used to filter the items.
A default selection like active webpack 5 in progress and other visible, webpack 4 hidden could make the page easier to use.

@montogeek have you started working on this? I'd like to pick this up if you haven't started.


Topic/local

This pull request adds a greater amount of connection information to the Request by way of the request AttributeMap. The InetSocketAddress of the remote, and server, as well as if the connection is secure are stored together.

Helper methods are added to the Request to enabler faster lookup of the data.
Unit tests are added.
The blaze infrastructure is updated so that code for generation of the AttributeMap isn't duplicated and thus is more likely to be uniform.

:+1: .  #363 would fix Travis, or we can assume it works.


 Check your environment and configuration. Couldn't find: msfvenom
Could you help me? Thanks a lot.

@Palmus84 I cannot provide support for environment issues. Sorry.

copy the folder "backdoor-apk" to /usr/share/ and run again...  Check your environment and configuration. Couldn't find: msfvenom
Could you help me? Thanks a lot.

copy the folder "backdoor-apk" to /usr/share/ and run again... :)

Check your environment and configuration. Couldn't find: baksmali
how to solve？ Install basksmali？

thanks my dear it working now

1