Fix new stylelint-config-recess-order issues

@julien-deramond LGTY?

@julien-deramond LGTY?

I don't know if it must be rebased onto something or if there's a missing dep bump, but you got a "Lint" error in the workflow:
scss/_nav.scss
  173:5  ✖  Expected "flex-basis" to come before "flex-grow"  order/properties-order

scss/_navbar.scss
  143:3  ✖  Expected "flex-basis" to come before "flex-grow"  order/properties-order

✖ 2 problems (2 errors, 0 warnings)

ERROR: "css-lint-stylelint" exited with 2.

Yeah that's normal, it will work after #40895

In that case, yeah, no problem with this modification :)

My point is if any of the behavior changes because some properties were overridden, https://github.com/stormwarning/stylelint-config-recess-order/issues/385


Revert "HADOOP-17371. Bump Jetty to the latest version 9.4.34. Contributed by Wei-Chiu Chuang."

Reverts apache/hadoop#2453

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
26m 20s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m  9s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
21m 20s

trunk passed

+1 :green_heart:
compile
20m 28s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
compile
17m 46s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
checkstyle
2m 41s

trunk passed

+1 :green_heart:
mvnsite
5m 49s

trunk passed

+1 :green_heart:
shadedclient
24m 18s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
4m 45s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
5m 49s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+0 :ok:
spotbugs
0m 35s

Used deprecated FindBugs config; considering switching to SpotBugs.

+0 :ok:
findbugs
0m 39s

branch/hadoop-project no findbugs output file (findbugsXml.xml)

+0 :ok:
findbugs
0m 35s

branch/hadoop-client-modules/hadoop-client-minicluster no findbugs output file (findbugsXml.xml)

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 57s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
7m 27s

the patch passed

+1 :green_heart:
compile
19m 31s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javac
19m 31s

the patch passed

+1 :green_heart:
compile
17m 25s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
javac
17m 25s

the patch passed

+1 :green_heart:
checkstyle
2m 43s

the patch passed

+1 :green_heart:
mvnsite
5m 50s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
xml
0m  4s

The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
15m 14s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
4m 43s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
5m 42s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+0 :ok:
findbugs
0m 37s

hadoop-project has no data from findbugs

+0 :ok:
findbugs
0m 38s

hadoop-client-modules/hadoop-client-minicluster has no data from findbugs

_ Other Tests _

+1 :green_heart:
unit
0m 36s

hadoop-project in the patch passed.

+1 :green_heart:
unit
3m 23s

hadoop-auth in the patch passed.

+1 :green_heart:
unit
9m 39s

hadoop-common in the patch passed.

+1 :green_heart:
unit
3m 44s

hadoop-kms in the patch passed.

-1 :x:
unit
39m 39s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

-1 :x:
unit
0m 40s
/patch-unit-hadoop-client-modules_hadoop-client-minicluster.txt
hadoop-client-minicluster in the patch failed.

+0 :ok:
asflicense
0m 44s

ASF License check generated no output?

296m 43s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestDFSStripedOutputStreamWithRandomECPolicy

hadoop.hdfs.TestDFSStripedOutputStreamWithFailure

hadoop.hdfs.TestDecommissionWithStripedBackoffMonitor

hadoop.hdfs.TestDecommissionWithStriped

hadoop.hdfs.TestErasureCodingExerciseAPIs

hadoop.hdfs.TestErasureCodingPolicies

hadoop.hdfs.TestDFSOutputStream

hadoop.hdfs.TestPipelines

hadoop.hdfs.TestModTime

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2635/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2635

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle

uname
Linux bd7a2da5e9ab 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 06fef5ee43d

Default Java
Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2635/1/testReport/

Max. process+thread count
3271 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-common-project/hadoop-auth hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms hadoop-hdfs-project/hadoop-hdfs hadoop-client-modules/hadoop-client-minicluster U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2635/1/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
26m 20s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m  9s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
21m 20s

trunk passed

+1 :green_heart:
compile
20m 28s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
compile
17m 46s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
checkstyle
2m 41s

trunk passed

+1 :green_heart:
mvnsite
5m 49s

trunk passed

+1 :green_heart:
shadedclient
24m 18s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
4m 45s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
5m 49s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+0 :ok:
spotbugs
0m 35s

Used deprecated FindBugs config; considering switching to SpotBugs.

+0 :ok:
findbugs
0m 39s

branch/hadoop-project no findbugs output file (findbugsXml.xml)

+0 :ok:
findbugs
0m 35s

branch/hadoop-client-modules/hadoop-client-minicluster no findbugs output file (findbugsXml.xml)

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 57s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
7m 27s

the patch passed

+1 :green_heart:
compile
19m 31s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javac
19m 31s

the patch passed

+1 :green_heart:
compile
17m 25s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
javac
17m 25s

the patch passed

+1 :green_heart:
checkstyle
2m 43s

the patch passed

+1 :green_heart:
mvnsite
5m 50s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
xml
0m  4s

The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
15m 14s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
4m 43s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
5m 42s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+0 :ok:
findbugs
0m 37s

hadoop-project has no data from findbugs

+0 :ok:
findbugs
0m 38s

hadoop-client-modules/hadoop-client-minicluster has no data from findbugs

_ Other Tests _

+1 :green_heart:
unit
0m 36s

hadoop-project in the patch passed.

+1 :green_heart:
unit
3m 23s

hadoop-auth in the patch passed.

+1 :green_heart:
unit
9m 39s

hadoop-common in the patch passed.

+1 :green_heart:
unit
3m 44s

hadoop-kms in the patch passed.

-1 :x:
unit
39m 39s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

-1 :x:
unit
0m 40s
/patch-unit-hadoop-client-modules_hadoop-client-minicluster.txt
hadoop-client-minicluster in the patch failed.

+0 :ok:
asflicense
0m 44s

ASF License check generated no output?

296m 43s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestDFSStripedOutputStreamWithRandomECPolicy

hadoop.hdfs.TestDFSStripedOutputStreamWithFailure

hadoop.hdfs.TestDecommissionWithStripedBackoffMonitor

hadoop.hdfs.TestDecommissionWithStriped

hadoop.hdfs.TestErasureCodingExerciseAPIs

hadoop.hdfs.TestErasureCodingPolicies

hadoop.hdfs.TestDFSOutputStream

hadoop.hdfs.TestPipelines

hadoop.hdfs.TestModTime

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2635/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2635

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle

uname
Linux bd7a2da5e9ab 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 06fef5ee43d

Default Java
Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2635/1/testReport/

Max. process+thread count
3271 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-common-project/hadoop-auth hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms hadoop-hdfs-project/hadoop-hdfs hadoop-client-modules/hadoop-client-minicluster U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2635/1/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Support for Dynamic Media Folder Paths per Post

Hello,
I'm currently seeking a way to configure individual media folders for each post. In Netlify CMS, you can achieve this by setting the media_folder and public_folder paths dynamically based on the slug like so:
media_folder: '{{slug}}'
public_folder: '{{slug}}'

However, this approach doesn't seem to work in Sveltia. When I try to set the path to /src/content/blog/{{slug}}, the directory is incorrectly created with the literal name "{{slug}}" rather than substituting the actual post slug.
Additionally, I need to maintain locale-specific directories within the blog folder, like this:
blog
|
├── en
│   └── something.md
├── de
│   └── something.md
└── something
    └── image.png

Is there currently a way to have a separate directory for each post's media while also keeping the locale directories intact? Any guidance or workaround would be greatly appreciated.

Assuming you’re using Folder Collections Media and Public Folder... When I see the Sveltia code, {{slug}} seems already supported. I’ll figure out why it’s not working.
And okay, you use the i18n support. I actually saw you posted a comment on https://github.com/decaporg/decap-cms/issues/4781 and realized that Sveltia has the same issue here. I’m happy to fix it.

Thanks for the reply. I'll try again with the slug directory. If you say it's supported, I'm sure the problem is on my end.


Mitigating Veracode Scan Issues

Hi Paul,
Our company uses Veracode code scanning to find issues in code that may be vulnerable to attacks.  There are a few hits on the jexcel files and wanted to share this with you and see if there's a way this can be fixed.  The jexcel version we're using right now is 3.8.2.
The code that's triggering the issues (link below).  From jexcel.js
if (eval('typeof(' + tokens[i] + ') == "undefined"')) {
...
var res = eval(evalstring + expression.substr(1));

From jsuites.js
eval(script[i].innerHTML);
http://cwe.mitre.org/data/definitions/95.html
Thank you and let me know if you have questions.

Thank you for your message.
It is important, when dealing with security, to keep your version updated. There were included many new options thinking on the level of security you would like to instruduce in your application, and particular from v3 to v4 there are a big differences on that regards. For example you can disable formulas, so eval would never be used. You can secureFormulas which will only execute formulas (excel like formulas). And you can use stripHTML which only accept innerText on DOM elements.
Those are some of the variables introducted on the most recent versions.
        // Execute formulas
        parseFormulas:true,
        autoIncrement:true,
        autoCasting:true,
        secureFormulas:true,
        stripHTML:true,
        stripHTMLOnCopy:false,

In regards to jSuites. The eval mentioned is no longer on the jexcel distributions. So, it won't be included on jSuites.js or jSuites.basic.js, althoght we still using for a very special case in a special distribution not related to jexcel.
Best regards,

Thanks Paul.

I grabbed jExcel via npm and it downloaded the 4.3.0 version.  I noticed the jsuites distribution included all these files:
jsuites.basic.js
jsuites.js
jsuites.layout.js
jsuites.mobile.js
jsuites.webcomponents.js

Do we need all the files or just jsuites.js and jsuites.basic.js per what you mention above?
The jExcel dist files include jexcel.webcomponent.js which I assume is needed for formulas when enabled.
Thanks for your help.

If you are interested only on the absolutely necessary to run jexcel, you can use ONLY jsuites.basic.js and nothing else.

Great, thank you.


MLT-41 Change handling of duplicate orders

This pull requests aims to make handling of duplicate orders similar to the way we handle duplicate products.
It comes with the same weakness in case SynQ informs us that the order is a duplicate, not our DB. Problem being we have no information about the order and no way of getting that information through API.

I forgor about the API Doc...


Inconsistent captcha response keys

Description
Two of the kCaptchaResponseKey are "captchaResp". The rest are "captchaResponse". Is this correct?
Reproducing the issue
~/gh7/firebase-ios-sdk (master) $ git grep "const kCaptchaResponseKey"
FirebaseAuth/Sources/Backend/RPC/FIRGetOOBConfirmationCodeRequest.m:static NSString *const kCaptchaResponseKey = @"captchaResp";
FirebaseAuth/Sources/Backend/RPC/FIRSetAccountInfoRequest.m:static NSString *const kCaptchaResponseKey = @"captchaResponse";
FirebaseAuth/Sources/Backend/RPC/FIRSignUpNewUserRequest.m:static NSString *const kCaptchaResponseKey = @"captchaResponse";
FirebaseAuth/Sources/Backend/RPC/FIRVerifyPasswordRequest.m:static NSString *const kCaptchaResponseKey = @"captchaResponse";
FirebaseAuth/Tests/Unit/FIRGetOOBConfirmationCodeRequestTests.m:static NSString *const kCaptchaResponseKey = @"captchaResp";
FirebaseAuth/Tests/Unit/FIRSetAccountInfoRequestTests.m:static NSString *const kCaptchaResponseKey = @"captchaResponse";
FirebaseAuth/Tests/Unit/FIRSignUpNewUserRequestTests.m:static NSString *const kCaptchaResponseKey = @"captchaResponse";
FirebaseAuth/Tests/Unit/FIRVerifyPasswordRequestTest.m:static NSString *const kCaptchaResponseKey = @"captchaResponse";

Firebase SDK Version
10.16.0
Xcode Version
15.1
Installation Method
N/A
Firebase Product(s)
Authentication
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Yeah, it's intended. It's due to the legacy backend field namings.

Thanks for checking


Feature Request: Include connection name in results set along with details of rows fetched

Can you include the Database connection name in the result set like shown below. I often run the same query across different environments such as PROD and Test with multiple tabs and often loose track of which tab was executed with which DB connection

Thanks for fixing this. But it doesn't fully fix the issue. Thought the connection name shows in the status, the moment I switch connections, the information refreshes to show as below

The main request for this feature is that many often run the same query across different environments such as PROD and Test with multiple tabs and may want to keep track of which results set tab was executed with which DB connection.

I see. Connection change status message shouldn't be updated in all tabs, just in the active one.

See fix in the next version

I still see the same issue in 4.2.2. Switching connection and moving to previous tab doesn't list the connection with which the query was executed.

Can't reproduce. This is how it works in my env:

Can you please check this out ? The moment you change the connection, the status info is lost.

@serge-rider Did you get a chance to check my screenshots above ?
Thanks

Yes, I can reproduce this.
And I don't know how to fix this. Because previous status message is removed by connection re-opening operation status. I can't just ignore this new status message...


Is this API still working?

I'am writting API wrapper using Kotlin lang, and took your wrapper and other one as an example. But, I have a problem with getting data from requests, I think, tiktok implemented new security fixes, so, every request return empty data. Can you check is your api still working? For me it returns empty data, as mine.

I'am writting API wrapper using Kotlin lang, and took your wrapper and other one as an example. But, I have a problem with getting data from requests, I think, tiktok implemented new security fixes, so, every request return empty data. Can you check is your api still working? For me it returns empty data, as mine.

At the moment, faced with the same problem. Now, when querying the server, you must pass two mandatory parameters "X-Gorgon, X-Khronos"

hey can you login by using this API.

Tiktok changed quite a bit to their api last month that probably broke this one. I don't have all the same functionality in my module, but you can get TikTok json objects and download videos and more.
TikTok-Api

Tiktok changed quite a bit to their api last month that probably broke this one. I don't have all the same functionality in my module, but you can get TikTok json objects and download videos and more.
TikTok-Api

https://github.com/tolgatasci/musically-tiktok-api-python/blob/master/README.md

@tolgatasci Thanks for the shout out


Ignore  the contents of the _MACOSX folder when applying the translation package

If the translator is on Mac, when it zips the translated resources, a _MACOSX folder will be present inside the archive. We should ignore this folder when we collect the resources in the package.

The .DS_Store files in the archive should be ignored too.


Rangler Starter with CRA

Three outstanding items with the CRA version of rangle starter:

npm start needs to do the prod start not the dev start.
npm eject puts stuff in node-modules which is not correct
update rangle-starter Readme and deprecate the existing react-starter repo.

@danielfigueiredo


Add tagging actions for ElasticBeanstalk Environments

This adds tagging actions (mark-for-op, mark, tag, unmark, remove-tag) for ElasticBeanstalk Environments. I've tried to use the feedback from my other recent PRs in the hopes of making this one a bit simpler to review.
A few notes:

Yes, this calls list_tags_for_resource once for each EB environment in the augment. I'm not sure if there's a better way to handle this, but the ListTagsForResource API call only takes a single environment at a time. I setup the retry handler for the ThrottlingException, even though botocore should handle retries for that automatically (up to 4, I believe).
According to the docs, the Resource Groups tagging API doesn't support EB environments.
The actual action implementations are based on those for the rdscluster resource as it has a very similar API, though Beanstalk uses one API call to Add and/or Remove tags.
The placebo tests are a bit ugly because EB environment tag updates trigger an update of the actual environment, and take 60+ seconds to appear on a subsequent query. I've included some comments about that in the tests.

yeah, i've reached out to the resource group tagging api folks to see if their going to update (they haven't since launch), also pr getting some flake8 fails
 c7n/resources/elasticbeanstalk.py:24:1: F401 'c7n.filters.OPERATORS' imported but unused c7n/resources/elasticbeanstalk.py:24:1: F401 'c7n.filters.AgeFilter' imported but unused

@kapilt Yeah, the inconsistency in some APIs is bothersome. I'll ping our TAMs about that, though we've been trying to put pressure for an internal feature request around limits in service APIs (like how RDS and IAM do it) for almost a year, to no avail.
Oops. :( I'll get a fix for that pushed up in the morning.

@kapilt Apologies. All 3 tox envs (27, 36, lint) are now passing locally. I'll keep an eye on the checks here too.

@kapilt Ok, dropped mark/unmark

@kapilt I believe I've addressed all of the latest round of comments. Once again, thanks so much for taking the time to review these.


Event time doesn't refer to field defined by time_key

Bugs should be filed for issues encountered whilst operating logging-operator.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors. #logging-operator
Please provide as much detail as possible.

Describe the bug:
I'm trying to ship container's stdout to elasticsearch cluster. Input on worker node level looks like this:
{"log":"[26/Apr/2023:06:56:48 +0000] <IP_ADDRESS> - - http HTTP/1.1 \"GET /health\" 200 0.000 94 - - \"-\" \"kube-probe/1.21\" \"-\" \"-\" \"<IP_ADDRESS>:8000\" \"-\"\n","stream":"stdout","time":"2023-04-26T06:56:48.118043458Z"}

I have set up appropriate flow as follows:
apiVersion: logging.banzaicloud.io/v1beta1
kind: Flow
metadata:
  name: some-flow
  namespace: some-namespace
spec:
  globalOutputRefs: []
  localOutputRefs:
    - some-output
  match:
    - select:
        container_names:
          - some-container-name
        hosts: []
        labels: {}
  filters:
  - tag_normaliser: {}
  - parser:
      key_name: log
      remove_key_name_field: false
      reserve_data: true
      parse:
        type: multi_format
        patterns:
          - format: regexp
            expression: /^\[(?<http.timestamp>[^\]]+)\]\s+(?<http.clientip>[0-9\.]+)\s+(?<http.remoteUser>\S+)\s+((?<http.x_forwarded_forProxy>\S+)|-)(,\s+(?<http.x_forwarded_for>\S+))*\s+(?<http.scheme>\w+)\s+HTTP/(?<http.version>[0-9\.]+)\s+\"(?<http.methode>\w+)\s+(?<http.request>[^\"]+)\"\s+(?<http.statusCode>\d+)\s+(?<http.requestTime>[0-9\.]+)\s+(?<http.bytesSent>\d+)\s+(?<http.upstreamStatusCode>\d+|-)\s+((?<http.upstreamResponseTime>[0-9\.]+)|-)\s+\"(?<http.referrer>[^\"]+)\"\s+\"(?<http.useragent>.*?(?=(\w{40})?))\"\s+\"(?<SESSIONID>[^\"]*)\"\s+\"(?<http.upstream_addr>[^\"]+)\"\s+\"(?<http.host>[^\"]+)\"\s+\"(?<http.location>[^\"]+)\"$/
            time_format: "%d/%b/%Y:%H:%M:%S %z"
            time_key: "http.timestamp"
            keep_time_key: true
            types: "http.statusCode:integer, http.requestTime:integer, http.bytesSent:integer, http.upstreamStatusCode:integer, http.upstreamResponseTime:integer"
          - format: none

Parsing works quite well but it uses time instead of http.timestamp as event time.
_id
asdasdasd1234

_index
some-index

_score
 -

SESSIONID
-

http.bytesSent
94

http.clientip
<IP_ADDRESS>

http.host
<IP_ADDRESS>:8000

http.location
-

http.methode
GET

http.referrer
-

http.remoteUser
-

http.request
/health

http.requestTime
0

http.scheme
http

http.statusCode
200

http.timestamp
26/Apr/2023:06:56:48 +0000

http.upstream_addr
-

http.upstreamStatusCode
0

http.useragent
kube-probe/1.21

http.version
1.1

http.x_forwarded_forProxy
-

...

log
[26/Apr/2023:06:56:48 +0000] <IP_ADDRESS> - - http HTTP/1.1 "GET /health" 200 0.000 94 - - "-" "kube-probe/1.21" "-" "-" "<IP_ADDRESS>:8000" "-"

stream
stdout

time
Apr 26, 2023 @ 06:56:48.118

Why is it?
Expected behaviour:
I'm using fluentbit as a sidecar for another project and when setting Time_Key timestamp in elastic there is a field named @timestamp as date. I'd expect same in this scenario.
Steps to reproduce the bug:
Use input and flow from above to reproduce the issue.
Additional context:
Nothing at all.
Environment details:

Kubernetes version v1.21.14
Cloud-provider/provisioner: RKE (self-managed)
Resource definition (possibly in YAML format) that caused the issue, without sensitive data: Added above

/kind bug

I can't see that this issue has anything to do with the logging operator, so converting this to a discussion, with Q&A category.


Export resultset - run again the query

Hi,
When exporting a resultset (right click on result, in context menu, choose export resultset), it's run again the query on the db server which is useless as all the result is already displayed / grabbed.
Moreover, when doing this, it seems that the query is run again inside a transaction; which can cause some troubles. In sybase ASE for example, some sql statement can't be done inside a transaction (select into #tempable from...); which make the result to be no exportable.

The purpose of Export Resultset... is to export the entire set of records that would be generated by the query that was run. Typically, DBeaver limits this to 200 records in the client at a time to be efficient. So, in order to actually grab the entire result set, DBeaver must requery the database when exporting.
If the result set contains all the records you want to export (be wary of the default 200 record limit), you could do an Advanced Copy to copy and paste the records, though this is much more limited than the export.
An alternative is to highlight the selected query, prior to executing in DBeaver, and right click, Execute -> Export from Query. This saves the step of performing the initial query to populate the Resultset pane. This might or might not help with the transaction issue. I'm not well-versed (aka not versed at all) in Sybase, but it might be worth a shot.

The advance copy is working fine. Thanks :)
Just to do not forget to select the whole result (ctrl+a).
But I have then to create the file myself and paste in it.
And if I have 10 resultset to export... I have to do it 10 times, which is a little bit borring.
And what about to copy (i.e. export) to another format than pure text (like excel, I saw that it's in the pipe for "export resultet" feature)? We maybe have an option to "export result" from displayed data or to run again the query to grab all data?

Ok, so if I uncheck the "open new connection" when exporting resultset, I do not have anymore the transaction problem; but I'm getting an error:

My big query create 20 resultsets.
Is there a limitation when exporting?

Please post full error stacktrace. You can get it in Error Log view ( or in error/debug logs: https://github.com/serge-rider/dbeaver/wiki/Log-files).

Here are the logs
log.zip

Just notice that the exported file is created (without all the data) and DBEaver keep the file locked after this crash. Maybe add a "finally" part into the java code to close opened files?

I've fixed this particular error but I still can't reproduce it. It would be helpful to understand why it happens (looks like real results column count doesn't match expected count).
Could you send a sample of query you are exporting from?


store collapsible expand state to sessionstorage

It always bothered me that I had to re-open/close collapsibles after reloading, so I made the collapsibleGroup component use sessionStorage.

Note to self: Fix collapsibles in modals, then it should be ready for review.

Good idea, but I think the changes you made are overkill. It doesn't make sense to store this in the SessionStorage since this is more of a global configuration. Also, you could achieve the same result with just:
function CollapsibleGroup({ label, expanded, children }) {
	const contentArea = useRef(null);
	const [isCollapsed, setIsCollapsed] = usePersistentState(`(${label}).isCollapsed`, !expanded);
	const [contentHeight, setContentHeight] = useState(isCollapsed ? 0 : '');

However, modals would still need some special treatment in case there are collapsible groups with the same labels inside them.

Switched it to your solution and added an option to use a different name for the state with stateLabel.
This is definitely more elegant, but I thought it was actually nice that the Parameters and Sampling collapsibles would always open when making a new session.
If you say sessionStorage is too much, I'll trust your call on this. I don't have any particularly strong feelings here, and it's still way better than the previous behaviour.

I think there is a different way to accomplish what you want (which isn't a bad idea). Maybe something like this:
function CollapsibleGroup({ label, expanded, expand, children }) {
	const contentArea = useRef(null);
	const [contentHeight, setContentHeight] = useState(!expanded ? 0 : '');
	const [isCollapsed, setIsCollapsed] = useState(!expanded);

	if (!expand.current) {
		expand.current = (value) => setIsCollapsed(value);
	}

	...
}
...
const expandParameters = useRef();
...
<CollapsibleGroup expand={expandParameters} .../>

Then this could be used when a session is created to programmatically expand the collapsibles we want to expand. I guess it would be necessary to create a session creation event and then listen for that event in the useEffect at the bottom of the App component.
I will merge this PR now but feel free to open another PR if you decide to do this! Thank you for this contribution.


JRuby9x, Java::JavaLang::ArrayIndexOutOfBoundsException

I got below exception when start up a Rails project.
Looks like the RubyGem-mail parser has problem
An error occurred while loading ./spec/controllers/application_controller_spec.rb. - Did you mean?
                    rspec ./spec/controllers/ping_controller_spec.rb
                    rspec ./spec/controllers/errors_controller_spec.rb
Failure/Error: require File.expand_path("../../config/environment", __FILE__)
LoadError:
  load error: mail/parsers/address_lists_parser -- java.lang.ArrayIndexOutOfBoundsException: -32624
# ./config/environment.rb:5:in `<main>'
# ./spec/spec_helper.rb:50:in `<main>'
# ./spec/controllers/application_controller_spec.rb:1:in `<main>'
# ------------------
# --- Caused by: ---
# Java::JavaLang::ArrayIndexOutOfBoundsException:
#   -32624
#   org.jruby.parser.ParserConfiguration.coverLine(ParserConfiguration.java:193)
An error occurred while loading ./spec/controllers/errors_controller_spec.rb.
Failure/Error: require File.expand_path("../../config/environment", __FILE__)
FrozenError:
  can't modify frozen Array
# ./config/environment.rb:5:in `<main>'
# ./spec/spec_helper.rb:50:in `<main>'
# ./spec/controllers/errors_controller_spec.rb:1:in `<main>'
An error occurred while loading ./spec/controllers/ping_controller_spec.rb.
Failure/Error: require File.expand_path("../../config/environment", __FILE__)
FrozenError:
  can't modify frozen Array
# ./config/environment.rb:5:in `<main>'
# ./spec/spec_helper.rb:50:in `<main>'
# ./spec/controllers/ping_controller_spec.rb:1:in `<main>'

+1 facing the same issue.

Eventually overcome the build failure. Dive deeper the open source code here https://code.yawk.at/org.jruby/jruby-core/<IP_ADDRESS>/org/jruby/parser/ParserConfiguration.java#193
This failure happened to store the code coverage line number. It does not impact the major runtime function. So, we can temporarily disable the code coverage inspection to bypass this failure, though still no idea why the array access would be ArrayIndexOutOfBoundsException. This may need the open source owner to fix the problem.
My solution is to add NO_COVERAGE=true env variable at the Rakefile CLI. For example:
sh "cd rails-root && RAILS_ENV=test NO_COVERAGE=true JRUBY_OPTS=--debug rspec --options=.rspec spec/"
And reference this NO_COVERAGE env variable at the Coverage inspection. For example:

unless ENV["NO_COVERAGE"]
SimpleCov.start 'rails' do
Code to inspect the covage
...
end
end

@solsticejc it's an internal limitation on how JRuby stores line numbers for coverage. See https://github.com/jruby/jruby/issues/6984
I agree that an exception is bad and it should be fixed on the JRuby's side. For now as a workaround, just disable coverage, the bug doesn't affect the regular runtime.

it should be fixed by https://github.com/jruby/jruby/pull/6991


To create new careeropportunity in dashboard you have to click 'ny karrieremulighet' twice

The first time you push 'Ny karrieremulighet' the dropdown closes and you have to reopen it to get the view.

Nvm, user error.


wrong approach in rewrite+add-base-url ?

Moved this here from contrib.
Maybe I'm getting this wrong, but the base-url should be constructed from matched path instead of rewrite target.
Problem description:
Ingress rule:
path = "/p"
rewrite-target = "/"
add-base-url = true

How it works:
base-url=protocol://host/target => http(s)://some.host/

css/test.css becomes http(s)://some.host/css/test.css (ingress rule is not matched anymore)

How it should work:
base-url=protocol://host/target => http(s)://some.host/p

css/test.css becomes http(s)://some.host/p/css/test.css (matches the ingress rule and URL is rewritten to /css/test.css for the backend to be loaded correctly)

If a path "/p" is matched by the ingress rule, the backend is rewritten to /, but the resources should still be pulled by /p/ from the browser point of view, otherwise there is no matching path in ingress rule.

I don't understand this either. The nginx template file doesn't seem to make use of the Target or AddBaseURL fields of the struct decoded from the annotations aside from disabling compression when AddBaseURL is true...

gcr.io/google_containers/nginx-ingress-controller makes rewrite as following:
rewrite /studio-test/(.*) /studio/$1 break;
But it should be
rewrite /studio-test(.*) /studio$1 break;

Here are my Ingress resource
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    ingress.kubernetes.io/rewrite-target: /studio
  name: studio-test
spec:
  rules:
  - host: test.dom.net
    http:
      paths:
      - path: /studio-test
        backend:
          serviceName: studio
          servicePort: 80

What is the status of the issue? Because indeed, the base tag doesn't contains the application path set in the ingress...

/reopen


chore：adapt mysql addon for API 1.0

Codecov Report
Attention: Patch coverage is 0% with 69 lines in your changes missing coverage. Please review.

Project coverage is 0.00%. Comparing base (3913852) to head (ee35d09).

Files with missing lines
Patch %
Lines

...ns/mysql/scripts-ut-spec/configre_proxysql_spec.sh
0.00%
45 Missing :warning:

...ddons/mysql/scripts-ut-spec/proxysql_entry_spec.sh
0.00%
24 Missing :warning:

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #1105   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files         22      24    +2
  Lines       3576    3645   +69
=====================================
- Misses      3576    3645   +69

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


Support activity retry policies

required of https://github.com/dapr/go-sdk/issues/541
adds the ActivityRetryPolicy struct and updates CallActivity to execute a different code path if retries are needed.
I tried to mimic the behavior of https://github.com/Azure/durabletask/blob/main/src/DurableTask.Core/RetryInterceptor.cs#L52
but in the case of golang I had to make it a recursive algorithm

Note that I've updated the title of this PR to clarify that it only covers activity retry policies. Another PR will be needed to cover orchestration retry policies (which cover sub-orchestration scenarios).


Default Volume = 89

I left some testing code in there that sets the "Configure Defaults" default volume behind the scenes to 89% but only if you haven't configured a default volume on the "Configure Defaults" page.
This will need to be resolved in the next release.

This is corrected in the current development version.
If you do not mind testing development code, please try the latest in-development version of 2.0 which is here: https://community.smartthings.com/t/bigtalker-2-0-development/55305/29
Please note, this branch is constantly adding/adjusting/removing features based on feedback and has at least once required a complete removal and re-install to resolve an issue (which I work to prevent, but it was unavoidable in this instance).
The current version is P2.0.a6 and C2.0.a6.
I highly recommend using GitHub Integration to retrieve the updates.
When installing, "Publish the parent and save the child"

Resolved in the 2.0 development release.  I am hoping to graduate this to the normal release track in the next couple of weeks.  http://thingsthataresmart.wiki/index.php?title=BigTalker


feat(front): duplicate projects and scenarios [MARXAN-599]

Duplicate projects and scenarios
Overview
At the moment only posting a project id to be able to generate a response of this data project with a "duplicate key" and "user who duplicates it".
Feature relevant tickets
MARXAN-599

I am not sure if success/error toasts must be mapped to show various in column


Switch logger filename creation to non-templated format function

This avoids #19252 allocating 2GB of RAM per call.

The compiler fix seems to be stalled. Pull this instead?

#19252 has been fixed a year ago


🐣 Add initial RHEL 8.3 support

Oh, the test file needs to be in the rhel83_test package.

Yup, just saw that and pushed more code. :hugs:

schutzbot

schutzbot

So it looks like dnf-json fails with:
=== RUN   TestCrossArchDepsolve/fedora-30/aarch64/ami
    TestCrossArchDepsolve/fedora-30/aarch64/ami: main_test.go:75:
        	Error Trace:	main_test.go:75
        	Error:      	Received unexpected error:
        	            	unexpected end of JSON input
        	Test:       	TestCrossArchDepsolve/fedora-30/aarch64/ami

and osbuild-tests fails with:
=== RUN   TestEverything
    TestEverything: main_test.go:104:
        	Error Trace:	main_test.go:104
        	            				main_test.go:61
        	Error:      	Not equal:
        	            	expected: "FAILED"
        	            	actual  : "FINISHED"

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-FAILED
        	            	+FINISHED
        	Test:       	TestEverything
        	Messages:   	Unexpected compose result: FAILED

Verifying that Jenkins is behaving in #520

schutzbot

schutzbot

@ondrejbudai Děkuji!


Encoder + Model Interpolation

hi,
I have a question about the encoder+model interpolation. I have downloaded naver webtoon generator model, and I replaced high level layer with FFHQ model(test from 3-11 till 10-11, trucation=0.6), but I can't get the same result as yours. Can you give   me some advices? Or there are some different hyperparametric?
Hoping for your reply!

Anyone have idea about this？

Hi, I guess the webtoon checkpoint is different.

I got it! If the latent code Z1 is from generator.get_latent(), the result is good, but if the latent code Z2 is from the Encoder dirctly, the result becomes bad. After some iterative optimization of the latent code Z2 may make result better.


[Bug] Overlay multi monitor issue

Currently, when using multiple monitors, the overlay stores its position relative to the leftmost monitor's top left corner
which is not ideal because disconnecting one of the monitors may result in the overlay disappearing as it's placed out of the monitor's bounds.

This is fixed by commit 65deeadc56f3604efbc8e3dc8e90b7d6289e0845
The overlay's relative position (as a percentage of the display resolution) is now used instead of the actual position, also multiple positions are now stored for each monitor, this allows the overlay to switch to different positions based on the connected displays.


Microsoft Defender Antivirus has detected malware in lexart model included with this extension

Until this is resolved, I highly recommend switching to a different, safe model, and if you don't know how to do that, cease using this extension.
As I believe promptgen downloads this direct from huggingface, I will be making a report over there as well and will tag this issue.
Repro steps:

Install extension
Switch to promptgen tab, generate a result
Windows Defender alerted me to a threat

I'll note that I've been using promptgen happily for months, this is the first time Defender popped up. Possible this is a false alarm, but also possible it's a newly updated model on huggingface.
See details below:
auto1111 console:
Error completing request
Arguments: ('task(haiekb5zjbi57or)', 'AUTOMATIC/promptgen-lexart', 1, 10, 'android', 20, 150, 1, 1, 1, 1, 'Top K', 12, 0.15) {}
Traceback (most recent call last):
  File "D:\hal\stable-diffusion\auto\modules\call_queue.py", line 56, in f
    res = list(func(*args, **kwargs))
  File "D:\hal\stable-diffusion\auto\modules\call_queue.py", line 37, in f
    res = func(*args, **kwargs)
  File "D:\hal\stable-diffusion\auto\extensions\stable-diffusion-webui-promptgen\scripts\promptgen.py", line 99, in generate
    current.model = transformers.AutoModelForCausalLM.from_pretrained(path)
  File "D:\hal\stable-diffusion\auto\venv\lib\site-packages\transformers\models\auto\auto_factory.py", line 463, in from_pretrained
    return model_class.from_pretrained(
  File "D:\hal\stable-diffusion\auto\venv\lib\site-packages\transformers\modeling_utils.py", line 2258, in from_pretrained
    loaded_state_dict_keys = [k for k in state_dict.keys()]
AttributeError: 'NoneType' object has no attribute 'keys'

Error verifying pickled file from C:\Users\hal/.cache\huggingface\hub\models--AUTOMATIC--promptgen-lexart\snapshots\fe1dd16ac290199872bb27a0f72dc20839e81ed5\pytorch_model.bin:
Traceback (most recent call last):
  File "D:\hal\stable-diffusion\auto\modules\safe.py", line 135, in load_with_extra
    check_pt(filename, extra_handler)
  File "D:\hal\stable-diffusion\auto\modules\safe.py", line 81, in check_pt
    with zipfile.ZipFile(filename) as z:
  File "C:\Users\hal\AppData\Local\Programs\Python\Python310\lib\zipfile.py", line 1249, in __init__
    self.fp = io.open(file, filemode)
OSError: [Errno 22] Invalid argument: 'C:\\Users\\hal/.cache\\huggingface\\hub\\models--AUTOMATIC--promptgen-lexart\\snapshots\\fe1dd16ac290199872bb27a0f72dc20839e81ed5\\pytorch_model.bin'

The file may be malicious, so the program is not going to read it.
You can skip this check with --disable-safe-unpickle commandline argument.

 For more information please see the following:
https://go.microsoft.com/fwlink/?linkid=37020&name=Trojan:Script/Wacatac.H!ml&threatid=2147814524&enterprise=0
 	Name: Trojan:Script/Wacatac.H!ml
 	ID:<PHONE_NUMBER>
 	Severity: Severe
 	Category: Trojan
 	Path: file:_C:\Users\hal\.cache\huggingface\hub\models--AUTOMATIC--promptgen-lexart\blobs\8bb89c281830a1a860eab274def8a89f401ef1a38f727ace494edd0f90081404
 	Detection Origin: Local machine
 	Detection Type: FastPath
 	Detection Source: Real-Time Protection
 	User: MANDO\hal
 	Process Name: C:\Users\hal\AppData\Local\Programs\Python\Python310\python.exe
 	Security intelligence Version: AV: 1.385.456.0, AS: 1.385.456.0, NIS: 1.385.456.0
 	Engine Version: AM: 1.1.20100.6, NIS: 1.1.20100.6

Interesting, someone submitted PR for a safetensors version on hf here https://huggingface.co/AUTOMATIC/promptgen-lexart/discussions/1
That'd be nice right about now @AUTOMATIC1111

Reported on hf https://huggingface.co/AUTOMATIC/promptgen-lexart/discussions/2


Match simple node names not just FQDN

At the moment it is possible to filter records by host name, but the entire host name must be presented.  This is tedious and will be even worse once we start looking at multi-node jobs.  It will be desirable to match host name prefixes in various ways, obviously literally (so, ml8 rather than ml8.hpc.uio.no) but probably by globbing ml*, ml[5-8], ml[1,3,5].  None of this is hard.

jobgraph has code for matching that we could usefully steal.

Since the filtering by host name can happen both during directory tree traversal and during subsequent record filtering, it seems most natural to break the matching out into its own little ADT, likely in the sonarlog library.


As a content editor, I want to optionally enter author and copyright information for documents in editorial content so that I can properly attribute documents.

how soon is this needed?


Tab title shows dirty long file path after relaunching workspace on WSL

Issue Type: Bug

Open 2 files with same name from different folders. Something like views.py from multiple Django apps. It will look like this:

Relaunch VS Code. Both tabs will show dirty file paths instead of just folder names, like in following picture. Note - The tab which was active while you closed VS Code won't be affected.

This bug extends the tab width and takes more space, also makes it difficult to see and switch between lot multiple files with the same name.
For example, I have a Django workspace with about 6-7 different apps and all contain views.py, models.py, etc. So need to switch between them a lot frequently, and this bug makes it difficult to read the app name quickly.
VS Code version: Code 1.46.1 (cd9ea6488829f560dc949a8b2fb789f3cdc05f5d, 2020-06-17T21:13:20.174Z)
OS version: Windows_NT x64 10.0.18363
Remote OS version: Linux x64 4.4.0-18362-Microsoft

System Info

Item
Value

CPUs
AMD Ryzen 9 3900X 12-Core Processor             (24 x 3800)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.95GB (7.84GB free)

Process Argv

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu

OS
Linux x64 4.4.0-18362-Microsoft

CPUs
AMD Ryzen 9 3900X 12-Core Processor             (24 x 3800)

Memory (System)
15.95GB (7.84GB free)

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

vscode-postgres
cko
1.1.11

gitlens
eam
10.2.2

python
ms-
2020.6.90262

vscode-edge-devtools
ms-
1.0.7

remote-wsl
ms-
0.44.4

(1 theme extensions excluded)

Looks like a label formatter issue to me, maybe an event missing when the remote connection is resolved?

There were similar issues filles filled.
I ackonlewdge this bug, however I will not have time to look into it in the near future.
In case somebody from the community wants to investigate, code pointer
https://github.com/microsoft/vscode/blob/b58df64fd23e9639972d4b669d37365a76955d07/src/vs/workbench/services/label/common/labelService.ts#L136

This issue seems to be fixed now.


Query Apps is broken

Example:
groku apps
2015/02/25 16:17:34 XML syntax error on line 33: unexpected EOF
same issue if you try launch app Example:
groku app "Netflix"
2015/02/25 16:19:18 XML syntax error on line 33: unexpected EOF
.

@dynamitemedia sorry for the delay, github didn't notify me of this issue!
Did you build from source? If so, which version of go are you running and on what operating system?

@dynamitemedia This has been fixed in the 0.4 release


Add SecretStream API to sel

Let's add a high-level interface to https://hackage.haskell.org/package/libsodium-bindings/docs/LibSodium-Bindings-SecretStream.html in sel.
@domenkozar I would love to hear about your use-case, this will help us define the initial scope and write tests. :)

I'd like to replace https://hackage.haskell.org/package/crypton-conduit-0.2.3/docs/Crypto-Cipher-ChaChaPoly1305-Conduit.html with libsodium :)

@domenkozar okay, are you tied with conduit as the streaming library?

At the moment, yes.
Long term I want to switch to streamly and that requires quite a bit of code writing.

Alright, so in order to make the transition smooth we'd have to have an IO-based solution that could be plugged into Conduit, streamly and the rest.


How long does ATS take to reinstate a downed parent?

ATS version : 8.1.1
To be more descriptive : I'm trying to figure out what is the amount of time a child node takes to reinstate it's respective parent node after it has been marked down due to any reasons.
What I have done:
I have gone through detailed debug logs to find out parameters and timing under which a child node decides to try to mark a parent up after it has been downed by ATS. All I have found is there is some sort of ticker based mechanism, but I'm unclear as to it's timing and deciding factors if any.
Please provide a detailed answer or a documentation link which I can refer to. I have referred parent.config and other such configs but have not found anything helpful that gives me a detailed answer.
Thank you in advance.

The settings are in records.config:
https://docs.trafficserver.apache.org/en/8.1.x/admin-guide/files/records.config.en.html#parent-proxy-configuration
There are a lot of variables here.
First, it will retry a parent proxy.config.http.parent_proxy.fail_threshold times before marking it down. Each time, the timeout will be proxy.config.http.parent_proxy.connect_attempts_timeout. The time before the attempt fails can be up to that time, such as if a firewall is simply dropping packets, but maybe be shorter, such as a firewall returning a TCP Reset.
If your proxy.config.http.parent_proxy.total_connect_attempts is less than proxy.config.http.parent_proxy.fail_threshold, the time to mark down will also depend on how long in-between client requests.
After a parent is marked down, ATS will wait proxy.config.http.parent_proxy.retry_time before trying it again for a future client request.
ATS will make proxy.config.http.parent_proxy.per_parent_connect_attempts to a single parent. Then it will try the next parent (per the parent selection algorithm - round_robin, strict, consistent hash). After making a total of proxy.config.http.parent_proxy.total_connect_attempts attempts, it will return an error to the client.
So, the time to reinstate a downed parent after the initial attempt could be as much as proxy.config.http.parent_proxy.fail_threshold *  (proxy.config.http.parent_proxy.connect_attempts_timeout + proxy.config.http.parent_proxy.retry_time) * "the time between clients requesting" +  proxy.config.http.parent_proxy.retry_time +  proxy.config.http.parent_proxy.connect_attempts_timeout
Or as little as proxy.config.http.parent_proxy.fail_threshold.
Assuming my math is right. Again, there are a lot of variables in-flight here.
This is also assuming you're using parent.config and have proxy.config.http.parent_proxy_routing_enable set to 1. If you're not, the similar settings here will be used instead:
https://docs.trafficserver.apache.org/en/8.1.x/admin-guide/files/records.config.en.html#origin-server-connect-attempts
You might also find this helpful:
https://docs.trafficserver.apache.org/en/8.1.x/admin-guide/performance/index.en.html#timeout-settings

Thank you @rob05c I think that answers my question, also thank you for the documentation links.
Closing the issue.

Thank you @rob05c for the detailed explanation!


fix(server): Remove Socket.IO listeners

Not removing Socket.IO listeners can cause memory issues
in long running processes that spawn many Karma instance.
Fixes #2980

I signed it! I signed this last year so not sure why it says I haven't...I guess my email address is different?

The Travis CI failure seems odd, it's only failing in node 8 but it's complaining about the commit message. Surely that should fail in all node envs if that's incorrect?

The AppVeyor failure was present before my changes (I ran the build before making any changes).
1) middleware.proxy
       should bind proxy event:
     AssertionError: expected [ [Function: proxyReq] ] to equal true
      at Context.<anonymous> (test\unit\middleware\proxy.spec.js:349:71)

Should I look at it or is a well know failure?

Seems like the Travis was run against c1cd5cba8df61d7657485756fe1394ee7fbc1ffd which is a merge.
Please try pulling the new upstream  head and rebasing your change.  I bet that fixes it.

I signed it!

OK, the Travis failure is fixed and I signed the CLA with my other account so there's just the AppVeyor failure to fix.

It looks to me like the AppVeyor build is running on node.js 4 which doesn't fully support let. It's nothing to do with my changes that I can see. Does Karma still support node.js 4? Will I remove it from the appveyor.yml file?

Sorry the package.json still says
"engines": {
    "node": ">= 4"
  },

In the past changing the node support triggered a major version number update.  So I think the short path is to  add "use strict" to your code to allow the let

I don't think it's my code that's causing the failure, it's npm?
https://ci.appveyor.com/project/dignifiedquire/karma/build/1705/job/30vsaqw8pw30gmta
npm --version
C:\Users\appveyor\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js:79
      let notifier = require('update-notifier')({pkg})
      ^^^
SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode

In the AppVeyor yml file npm is upgraded
  # Upgrade npm
  - npm install -g npm

as part of the setup. I wonder if it ends up installing a version of npm that's not compatible with node4? I can remove the upgrade of npm from the AppVeyor yml file?

We should use a fixed version of npm that matches the lowest nodejs we support (4).  I guess
npm install -g npm@3

From what I can tell node.js 4 is shipped with npm 2, https://nodejs.org/en/download/releases/ I presume that's the latest npm it supports. The node.js 4 version installed during the tests is one of the latest (4.8.7) and it would naturally ship with an up to date npm for its node version (2.15.11).
I feel removing the npm upgrade step might be the safest initial step. I'll try that and see what happens.

OK that progresses the build further so the UTs start running but I see a failure in the UTs that was there from before my changes. I debugged it and it looks to me like the failing UT is incorrect. The UT was added in this small PR https://github.com/karma-runner/karma/pull/2596
The original PR didn't seem to have a green build and was merged regardless, unless I'm misunderstanding the conversation in the PR?
The lines which I believe are incorrect in the test are these
expect(parsedProxyConfig[0].proxy.listeners('proxyReq', true)).to.equal(true)
expect(parsedProxyConfig[0].proxy.listeners('proxyRes', true)).to.equal(true)

The listeners method is this method https://nodejs.org/api/events.html#events_emitter_listeners_eventname on EventEmitter which returns <Function[]> and not bool. So I'm changing those two lines to:
 expect(parsedProxyConfig[0].proxy.listeners('proxyReq')[0]).to.equal(config.proxyReq)
 expect(parsedProxyConfig[0].proxy.listeners('proxyRes')[0]).to.equal(config.proxyRes)

@dignifiedquire @kyo-ago does that seem reasonable?

OK the build is all green, for what it's worth the test added in this small PR fails for me locally https://github.com/karma-runner/karma/pull/2595/files I think it's assuming that trying to call toString() on a Proxy will always throw a TypeError but it doesn't seem to in the latest Chrome, it does in Fx.
Test it with
new Proxy(function abc (a, b, c) { return 'whatever' }, {}).toString()
In the console. I've left that UT alone for the moment but it might fail in future if the browser the tests are running against changes.

Sorry Brian we're blocked by #2951 now that Travis is running chrome 61.

@briandipalma please sync up and retest, master now builds for me.

@johnjbarton Done, I kept the removal of the npm upgrade step in the build as the node.js deployed by AppVeyor seems to come with the latest npm available in the official node.js releases (https://nodejs.org/en/download/releases/) so I have a feeling that those are the "safe/approved" npm versions per node.js version.


💬 Support quote environments in latex

Support quote, displayquote and epigraph

Tests were a timeout on SPDX. Merging!


Fix add local dependency

Add call to function forgotten in https://github.com/noah-severyn/SC4PackMan/commit/5c16cd32df9fd5caefb0d4ce0eb3d21de461be5f#diff-73fc5c21e2fd36321f7f65f1ff0fdc6aebc7a4130eda4f614f528f115444bb11R133.
Fix addition of semi-colon (;) at the end of local package lines.

Duplicate of #22.


Simplify Getting Started

I just pulled the repository, ran cargo test and it failed due to what looks like missing test data.  Digging deeper I see that I need to download test data into dcmpipe_tests/fixtures but it isn't clear what I need to download, especially from David Clunie's web site.  This is going to discourage new users from engaging with the project as they won't be able to get a clean build right away.  Is there a reason you don't want to check the test images into the repo itself?  If the images are too large, find or create smaller ones using gdcm or dcmtk.

Shoot I thought there was a publicly accessible link to download a zip of the test image sets. The download is ~700mb so it's quite large so I did not want to include them in the repository. Let me see if I can upload it to Google Drive or similar.
I would ideally like to craft specific unit test datasets however I wasn't sure the best way to go about doing that.

I was able to download the gdcm ones, but David Clunie's site has several links to images in the "Images" section - do I need to download all of them?

Also - I think it is good to have unit tests inline in the source files that don't have dependencies on actual dicom files - everything is created/built on the fly in the unit tests.  Actual testing of DICOM files can be done via integration tests in a tests folder.  I took this approach with the RLE Decoder and like how it turned out

From David Clunie's site I believe I downloaded anything which still had a valid link (not all of them did). I believe the primary datasets from his site are the "Internationalized character set test DICOM images".
The tests which rely on dicom files expect them to be in a specific layout relative to the dcmpipe_tests folder. The attachment (uploading to Google Drive) should just need downloaded into the dcmpipe_tests folder and extracted there - it should create a fixtures folder and everything should be in the right location. I have tested this procedure setting up another workstation so there will hopefully not be too many other difficulties.
I agree it makes sense to inline unit tests however I found a lot of the tests I started putting together ended up adding a lot of additional code into the file which I found made navigating the files more difficult. I'm open to restructuring these, particularly as I think it is more idiomatic rust to have unit tests right inline with the code being tested.

Here is the link to download from Google Drive:
https://drive.google.com/file/d/1VI89r3leiLPm9-8sClyy0o15KtGZeqaD/view?usp=sharing
I will update the readme for dcmpipe_tests to include this link.

One thing to note about the test fixtures - there are two tests currently marked with #[ignore] at the bottom of the parsing tests which recursively walk the fixtures folder and attempt to parse all the dicom files including parsing element values. I used these tests to locate data which caused the parser to fail, then typically added those files as individual tests. So there are a great many test files but the written tests don't use all of them -- with exception to the ignored ones which I only turned on temporarily to locate other parsing issues.

Just downloaded and ran cargo test but still have 4 failed tests.  Can you double check to make sure all tests pass?

Oh not all tests pass -- having 74 pass, 12 ignored, and 4 failing is expected right now.
These tests are expected to fail right now as they are all testing the same dicom file. This dicom file utilizes multiple character sets when encoding string values and that support is not yet implemented (I need to make a task). Implementing this will likely need to change the API for how characters sets are handled.

charsets::test_scs_h32
parsing::test_dicomdir_with_std
parsing::test_dicomdir_withoutstd

This parsing::test_unknown_explicit_vr_is_error is also expected to fail right now as I recently made some changes to not consider an unknown explicit VR as an error. Previously if the explicit VR did not map to a standard VR this would result in an error parsing the element. To allow the parser to be more lenient however it should still be possible to parse the binary stream as the VR only indicates how the element value should be parsed. An invalid VR should not prevent accessing the element or its value as bytes however. The test here needs updated.

can we set the failing tests to ignore and create issues to track them?

Yes I think that's a good idea. I added you as collaborator to the project so you should be able to help with setting up tasks and such.

I can create the tasks and change the tests to be ignored but I probably will not be able to get to that until later today or tomorrow. You are welcome to create the tasks for that now if you'd like to get a head start.

I split out the UT failures into #6  and #7 and made commits for the tests to be ignored. A clarification about what I said earlier. I indicated that all 3 tests failing due to #6 are using the same file. That's not actually true -- the DICOMDIR tests a different file but it's failing for the same reason. The DICOMDIR is a directory listing of the character set files, and includes the patient name which is encoded in the same way, resulting in the same error.


Could not claim the USB device when using Canon

when try to test Canon by 'RemotePhotoToolCmdline.exe -o {2}', but shown "Could not claim the USB device"

which's step i miss? how to fix this problem?

i use this exe program in WINDOWS 10

Can you use the camera using the Canon remote program that's installed with the Canon CDs?

Ah I see that the program tries to use the libgphoto2 driver. This driver is not usable at the moment, so you have to switch back your Canon camera to use the Windows driver, not the libusb driver to use it.

canon sdk is work. i switch to windriver, this RemotePhotoToolCmdline.exe program can work in libgphoto2. Thx.  and i try to test gphoto2 lib, but can't work,  show below message.

this error shown from gp_camera_init  step.
'''
printf ("Creating camera...\n");
context = gp_context_new();
gp_context_set_error_func(context, ctx_error_func, NULL);
gp_context_set_status_func(context, ctx_status_func, NULL);

CHECK (gp_camera_new (&camera));

/*
 * Now, initialize the camera (establish a connection).
 */
printf ("Initializing camera...\n");
CHECK (gp_camera_init (camera, context));

'''

and i try to run in WpfDotNetCameraControl.exe, it also can't work in libgphoto2.  what's the different of connection between WpfDotNetCameraControl.exe and  RemotePhotoToolCmdline.exe

As I said, the libgphoto2 is not usable. WpfDotNetCameraControl.exe is an example how to work with the C# wrapper and should not used by the end user as is.


Database init performance adjustments & cleanups

drops the database seeds, db warmup operation

initial usage seems to have been to warm up the serverless database (for cost reasons), which is not the responsibility of the app but of the infra

disabled the automatic database migration from production stage

TODO: create strategy for the production migrations..

https://mabster.net/posts/ef-migration-github-actions/


doc/template: write example read dynamic http header request

fixed: #251

@coderabbitai write next.md with this changed

@coderabbitai review

@coderabbitai write docs/releases/next.md with this changed


gender inclusive language

Change "her" to "their"

@emberstevens : Thanks for your contribution! The author, @MicrosoftGuyJFlo, has been notified to review your proposed change.

#please-close


publish ContentProviderHelper in the android-opensource-appstore http://fdroid.org/

Goal : publish ContentProviderHelper in the android-opensource-appstore http://fdroid.org/
ToDo:

Create a branch "fdroid"
remove the "report-errors-and-send-them-home" (frdoid does not like this)
remove permission internet (was needed only for error-reporting)

I have already started this with https://github.com/k3b/ContentProviderHelper/tree/FDroid
but of course I will not publish it on fdroid if projectowner does not want it

I have just added a LICENSE to the project so feel free to publish your fork on F-Droid ✌

ContentProviderHelper is now available in FDroid app store at https://f-droid.org/wiki/page/de.k3b.android.contentproviderhelper. The chages i made are licensed under gpl-v3+.
@jenzz : thankyou for releasing this valuable tool to the public domain.


Paper

Hi Pratik, thanks for sharing the code. I am a newbie in this domain,  I want to explore your system in detail. kindly if you let me know about the theoretical background of this code for better understanding the flow and working methodology.
Waiting actively for your positive response.
Thanks :)

@usman776  Steps/Flow of the code is mentioned with more details in documentation folder as mentioned in the README of the project. You can go through that and ask for specific question you want to know more about.

ok. I check and follow.
Thanks.


What about autocomplete

I need for autocomplete (searching) users.
How to get that?

@marijang you need to map your model first here is a simple tag suggestions example
First you create a tag model map
use Sleimanx2\Plastic\Map\Blueprint;
use Sleimanx2\Plastic\Mappings\Mapping;

class AppTag extends Mapping
{
    /**
     * Full name of the model that should be mapped
     *
     * @var string
     */
    protected $model = App\Tag::class;

    /**
     * Run the mapping.
     *
     * @return void
     */
    public function map()
    {
        Map::create($this->getModelType(),function(Blueprint $map){

          $map->string('name')->store('true')->index('analyzed');

          // instead of the fluent syntax we can use the second method argument to fill the attributes
          $map->completion('tag_suggest',['analyzer' => 'simple', 'search_analyzer'=>'simple'];

        });
    }
}

Then in your tag model you add this function
    /**
     * This function will be called by elastic to map eloquent to db.
     *
     * @return array
     */
    public function buildDocument()
    {
        return array(
            'id' => $this->id,
            'name' => $this->name,
            'tag_suggest' => $this->name,
        );
    }

Finally you query as suggested by @nivv


Update schedule

Is there a set update schedule for these data? It would be helpful to have some note in the README file as to how often new/revised data will be committed to the repository (monthly? quarterly? "periodically"? etc.) (please for goodness sake, try to have the answer not be "periodically" :stuck_out_tongue_closed_eyes:)

Thanks for the feedback. We've updated this in our README.


Examples

Could someone upload an example here please?

Example of what?

Example of what?

I can't even remember now...


Relative amounts cannot be included in the json config

I'm trying to include --rel-amount-to and   --rel-amount-from  in my config.json but both values are not recognized. Both as they are written here and using underscore instead of dashes.

Looks like the toml/json fields were missing for these two, thanks for reporting. Can you check the master branch? Should work now.

Great! Now it works. Not sure if the different naming (rem instead of rel) was done on purpose but it is working at least.

That's a typo, of course, fixed it to be consistent with TOML. Thanks!


Deprecation notice in Symfony 5.1

Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Version/Branch
0.2.1

closed by #28


Update scalafmt-core to 3.4.0

Updates org.scalameta:scalafmt-core from 3.3.3 to 3.4.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Codecov Report

Merging #613 (d084b0a) into master (82b507f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #613   +/-   ##
=======================================
  Coverage   62.54%   62.54%
=======================================
  Files          39       39
  Lines        1303     1303
  Branches        7        7
=======================================
  Hits          815      815
  Misses        488      488

Continue to review full report at Codecov.

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


ENH: Complex filtering fix using sosfiltfilt and similar

Is your feature request related to a problem? Please describe.
Complex filtering
A complex filter is a filter in which the response of the positive and negative frequencies are not conjugate symmetric. This can be useful for generating analytic signals for signal processing. One can easily design such a filter by frequency shifting a low pass filter, such that it is no longer centered at DC, but at some center frequency. Second-order sections have their coefficients listed sequentially for the numerator and denominator in increasing polynomial order:
$H_{sos}(z) = \frac{b_0+b_1 z^{-1}+b_2 z^{-2}}{1+a_1 z^{-1}+a_2 z^{-2}}$
sos[stage_idx, :]=[b0, b1, b2, 1, a1, a2]
Replacing $z$ with $e^{j2\pi f_center/f_s}$ means multiplying each sos stage by
freq_shifter = np.exp(2j*np.pi*freq_center/sample_rate*np.array([0, 1, 2, 0, 1, 2])
from scipy.signal import buttord, butter
import numpy as np

sample_rate = 200
freq_center = 25
bandwidth = 3
transition_width = 1
filter_order, Wn = buttord(wp=bandwidth/2, ws=bandwidth/2 + transition_width, gpass=0.01, gstop=100, fs=sample_rate)
sos = butter(filter_order, Wn, 'lowpass', output='sos', fs=sample_rate) * np.exp(2j*np.pi*freq_center/sample_rate*np.array([0, 1, 2, 0, 1, 2])

Because IIR filters like Butterworth contain nonlinear phase responses, one commonly employs using filtfilt like methods, such that the synchronization of the input and output is maintained. filtfilt causes the data to first be passed through the filter as normal, and then passed through it in reverse, which is where the issue lies.
The Problem
When a signal is reversed, its frequency components are negated. A complex exponential that rotates in a clockwise fashion in forward time instead rotates anti-clockwise in reverse time. This means that the effect of the complex filter, when applied with the current implementation of sosfiltfilt first appear as a bandpass centered at +freq_center for the first pass and -freq_center for the second reversed pass. So the total effect of this filtering causes the bandpass portions of the filter to not overlap.
Describe the solution you'd like.
The solution
To solve this problem, we can perform a complex conjugation on the sos of the reverse filter:
def sosfiltfilt(sos, x, axis=-1, padtype='odd', padlen=None):
    "<docstring>"
    sos, n_sections = _validate_sos(sos)
    x = _validate_x(x)

    # `method` is "pad"...
    ntaps = 2 * n_sections + 1
    ntaps -= min((sos[:, 2] == 0).sum(), (sos[:, 5] == 0).sum())
    edge, ext = _validate_pad(padtype, padlen, x, axis,
                              ntaps=ntaps)

    # These steps follow the same form as filtfilt with modifications
    zi = sosfilt_zi(sos)  # shape (n_sections, 2) --> (n_sections, ..., 2, ...)
    zi_shape = [1] * x.ndim
    zi_shape[axis] = 2
    zi.shape = [n_sections] + zi_shape
    x_0 = axis_slice(ext, stop=1, axis=axis)
    (y, zf) = sosfilt(sos, ext, axis=axis, zi=zi * x_0)
    y_0 = axis_slice(y, start=-1, axis=axis)
    (y, zf) = sosfilt(np.conj(sos), axis_reverse(y, axis=axis), axis=axis, zi=zi * y_0)            # sos replaced with np.conj(sos)
    y = axis_reverse(y, axis=axis)
    if edge > 0:
        y = axis_slice(y, start=edge, stop=-edge, axis=axis)
    return y

A similar solution would be recommended for non-sos filtering (e.g., filters with b & a input directly).
Describe alternatives you've considered.
Instead of altering the existing sosfiltfilt, one could create a sosfiltfiltc - a complex version of sosfiltfilt. However, this seems unnecessarily complicated as the complex conjugation does not impact real filter coefficients that are the typical use case of sos.
Additional context (e.g. screenshots, GIFs)
No response

x-ref gh-19771

cc @roryyorke

This is a duplicate of gh-17877, though @Seaspider1's explanation of why the conjugate is needed is clearer.
The proposed change seems right  to me, though as always it's worth trying to imagine unexpected side-effects.  And, also as always, the main work will be a unit test, though I think here it's not too difficult; one could use the example in gh-17877 which is fairly simple.
A PR that fixes sosfiltfilt should also address filtfilt, as @Seaspider1 noted.
When I raised gh-19771 @ilayn noted that there were bigger scipy.signal changes in planning, so a PR for this might not be accepted.  Having said that, this specific fix is relatively small and obvious, and doesn't touch the LTI classes or machinery.


Add loading examples to serverside example

Closes https://github.com/gregnb/mui-datatables/issues/146 with example for demonstration purposes.

Coverage remained the same at 73.02% when pulling 0db4bfcf22f981e081d98a663355690a9e3dcfa6 on enhancement/issue-146-loading-example into af7b1069ac816cfaa57babba63b2d19458f4a31e on master.


Add page rerendering

This allows us to rerender the page with other data.
Helpful if the data has changed. With this you can easily rerender the page and musn't reinit the complete page nor change any data manually with .html()
See: #751 (I've updated it to be ready to merge)

This PR has fundamental issue. As such rerendering will break all components initialized by "page:init" and won't detach all assigned events and destroy initialized components, so potentially can lead to memory leaks. So it is good for something simple but won't work and break things in case you have something more complex. Also, it won't work on iOS theme if you have some dynamic data in navbar because it is rendered outside of page. So to make it work correctly the page should be destroyed correctly then rerendered and added/replaced by new one and re-initialized. To make it work, it is possible to use view router's method, something like:
function renderPage(data) {
    var tpl = Template7.cache[this.url];
    var newData = data || this.data || {};

    view.router.load({
        template: tpl,
        reload: true,
        reloadPrevious: $(this.container).hasClass('page-on-left'),
        context: newData
    });
}

Okay then I'll close it.


Implement pagination for jobs view

Coverage decreased (-0.23%) when pulling f50544a914540322e0fede51ce3cbdf0947e8ab9 on guidow:jobs_pagination into a0a285dd0efc7825a8bc2e077f60a7a2094d38e6 on pyfarm:master.

LGTM, merging.


trying to spruce up our native experience

changed some config language
added some icons

closes #138

I think the scaling got out of whack for the logo in Sketch because the outlines are too thin. Here's how it should look in large sizes:
black.pdf

good eye @nylira — i used an icon generator — will fix.

@nylira yep, i can figure out how to make the app draggable still. and we will have to make some adjustments for the top area.

@nylira i added the draggability in! we should talk about sidebar alignment stuff... you'll see when you open the app!

closes #164 too!

Okay this looks awesome:

With your other PR @jolesbi on increasing the height of the PageHeader, it's going to appear well balanced.

Moving the maximize window line to another PR to merge this. I am opposed to this, as this feels very unnatural. There we can continue discussing it.


Add optimization to flat systems trajectory generation

This PR adds the ability to generate trajectories for differential flat systems taking into account cost functions and constraints, in a manner that is consistent with the control.optimal module.  In particular, you can now call flat.point_to_point with cost and constraints keywords.  The code then uses any extra degrees of freedom in the flat trajectory to minimize cost and satisfy constraints at a list of time points.  For differentially flat systems, this method is much faster than solving an optimal control problem with terminal constraints.
I also found and fixed some docstring glitches and naming inconsistencies in control.optimal along the way (these are all minor and don't change behavior.  Unit tests, examples, and updated documentation are included.

Coverage increased (+0.2%) to 89.027% when pulling 0c1d63867d1fe6da82f1a4b055b7f82fb12f0832 on murrayrm:optimal_flatsys into 0f951e19fc36a40c0116afa81f26e9bc905601a5 on python-control:master.

I am not in a position to evaluate this at the moment, but my inclination would be to merge and include with 0.9 so people can play with it/find rough edges sooner rather than later.


Added switch component (#1299)

#1299

@CalebLuster , as discussed, since we are using button element as a toggle (not default behavior) we shall use associated aria- attributes to explicitly declare that. Check out https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-pressed for details, but essentially you should add aria-pressed attribute to the button element with true/false values reflecting current state.
Another accessibility issue we have to address is that  element must have a label all the time. Regardless its visibility, which will be governed by that control, but markup should include label all the time. To achieve that use persistent  aria-label attribute for the button.

@CalebLuster , changes in https://github.com/undp/design-system/pull/1328/files#diff-8c0b50e63802ff6a0da7dc6063f43563c1ae8b81f2d56d3bc34658edd34927e4 shouldn't be mixed with this ticket. We will leave it as is for the time being as it is not a big deal, but for the future - we should keep changes pertinent to specific ticket within relevant PR. THis one was marked as fixing #1299 , so other changes shouldn't be included as a matter of practice. No action required.


how to move an installation

Hello there,
we installed a concrete <IP_ADDRESS> into a htauth protected subdirectory for initial configuration and setup (customizing themes, writing initial content, etc) and now wanted to move out of that subdirectory to our domain root. unfortunately it seems concrete 5.7 does not offer an option to change the BASE_URL as in previous versions. now all our links, images and most likely other stuff still excepts concrete5 to be installed in that subdirectory.
is there an easy way to migrate the data? for now it looks i have to do a sql dump, grep/search&replace all references to the directory and re-import the database. is there anything better i can do? all i found on google is related to previous versions that used the BASE_URL in config...
Thanks in advance.

This really isn't the place to ask this question – this is specifically for verified bugs and updates to the code base.
As with previous versions, base url shouldn't be stored in your database at all, and moving a site is usually a simple process.
https://www.concrete5.org/documentation/developers/5.7/installation/moving-a-site/


Pin visual to a personnal dashboard

I've read in a in the "Spring '18 Release Overview" (https://docs.microsoft.com/en-us/business-applications-release-notes/april18/release-overview) that you can pin visual from a shared report or an apps. But today if I try that I cannot because the pin is greyed-out with the message "read-only content can't be pinned". Which will be the case every time you share, because share is "read-only".
The only workaround I see is to use a content pack to take the ownership of the report. But in a recent communication I saw that content pack will be replaced by APPS (which doesn't give me this flexibility).
Could someone from the Power BI team comment on this ?
Thanks in advance,
Daniel

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

ID: eccfbc1d-74ab-9c0d-9fee-608508056da5
Version Independent ID: 8c090f12-937c-b9cf-44db-c7014d9a9e23
Content: Pin a tile to a Power BI dashboard from a report - Power BI
Content Source: powerbi-docs/service-dashboard-pin-tile-from-report.md
Service: powerbi
GitHub Login: @mihart
Microsoft Alias: mihart

Hi, kind of and old message but you cannot pin from the APP as its read only, must pin from the workspace.

Hello,
So why it's written in the Release Note (page 263) https://aka.ms/dynamics365releasenotes.
Is this a upcoming feature ?
Thanks in advance.

Hi @danievalle ,
Thanks for pointing this out.  I'll contact the Release Notes author and have this updated.


Making docker local volume driver support external FS mount type

- What I did
Allow docker local volume driver to mount fs using external mount command
- How I did it
The volume will be mounted by external mount only if mounting type starts with '^'.
- How to verify it
For all original mount type (tmpfs/nfs/..), it will be mounted by built-in mount and there will be no difference.
For mount type which starts with '^', it will be mounted by external mount command.
Test Step:
For orginal:
# docker volume create --driver local --opt type=tmpfs --opt device=tmpfs --opt o=size=100m,uid=1000 --name foo
# docker run -it --rm -v foo:/foo ubuntu:xenial ls -la /foo
For advanced sFTP:
# apt-get install sshfs openssh-server
# ssh-keygen -t rsa -P ''
# mv ~/.ssh/id_rsa.pub ~/.ssh/authorized_keys
# ssh $(whoami)@localhost true # Make sure this step needn't input password
# docker volume create --driver local --opt type=^fuse.sshfs --opt device=$(whoami)@localhost:/tmp  --opt o=StrictHostKeyChecking=no --name sftp1
# docker run -it --rm -v sftp1:/sftp1 ubuntu:xenial ls -la /sftp1
For docker swarm:
# docker service create -p 8443:8443 --mount type=volume,volume-opt=type=^fuse.sshfs,volume-opt=device=$(whoami)@localhost:/tmp,volume-opt=o=workaround=all:o=reconnect:o=StrictHostKeyChecking=no,source=user1-home,target=/sftp1 ghostplant/flashback
Making docker local volume driver support external FS mount type. such as glusterfs, cephfs, fused-based fs (sshfs/curlftpfs/..) and so on. Options for each kind of fs-type are configurable via '--volume-opt'. To mount volume with external mount command, type option is supposed to start with '^'.
Signed-off-by: CUI Wei<EMAIL_ADDRESS>

https://github.com/docker/docker/pull/28643
https://github.com/docker/docker/pull/28482
https://github.com/docker/docker/pull/28480
You do not need to open new PR when you update the code.
Please reuse the existing PR next time :+1:
$ git commit -a -s --amend
$ git push -f

Thank you. @AkihiroSuda
I didn't find ways to delete those old ARs, and the "Reopen PR" was unpressable.

cc @cpuguy83 @MHBauer @thaJeztah @stevvooe

The ^ syntax is horrible. Maybe an option like --mount mount=external ?

That might cause much more code change if "mount=" flag is defined, since only --opt could be used and validOpts includes only 'type', 'o', 'device'.
Maybe mount=external could be added into validOpts, such as:
docker volume create --driver local --opt type=fuse.sshfs --opt mount=external --opt device=$(whoami)@localhost:/tmp --opt o=StrictHostKeyChecking=no --name sftp1
How about this one?

@ghostplant As I said in #28482, this design is still heavily confounds mounts and volumes. The concept of "mounts" in docker parameterize how things like binds, volumes and tmpfs are mounted. Please take some time to see how these are implemented, end to end, and you'll see the difference.
The simple difference is that volume-opt, as passed to the local driver, has nothing to do with the --mount flag. The volume options passed to the mount flag do not parameterize the mount; they parameterize the volume if it is missing at the time the mount is performed. These options may be passed through to a mount call, through the local driver, in the course of a volume creation, which, in the case of the local driver, are a syscall to mount(3). Understanding this distinction is critical when proposing design changes.
It seems like this proposal would be better formed as an extension to the local volume driver that adds an option for helper, that, if defined, will call out to a mount helper on the system to perform the mount. This design would manifest in the --mount flag as volume-opt=helper=fuse.sshfs, which is a result of how the data structure is designed.

So which one to be added into validOpts is better, helper=external or helper=fuse.sshfs?
If we choose the latter one, should we skip the type option even if a user set its value?
For example:
--opt type=some-fs-type --opt helper=fuse.sshfs --opt device=$(whoami)@localhost:/tmp --opt o=StrictHostKeyChecking=no
It seems type option is unnecessary if helper option is defined, is it reasonable to just ingore it since both type and helper is an option to fill fs-type.

I didn't see where method-A ( which proposes type=^external-fstype style ) and method-B ( which proposes helper=external type=fuse.sshfs style) confound with mounts and volumes according to the source codes, since all mounting cases are without any conflicts.

According to all of your advices, I think this design would satisfy most of person's feeling, that is:
Extend a helper flag to --opt options which originally include ['device', 'o', 'type'], so all valid options should be ['device', 'o', 'type', 'helper'].
Besides, we define helper = [ 'built-in' (by default) | 'external' ], so if helper is not set or set to be built-in, local volume driver would perform completely as same as the orginal version.
If helper is set to be external manually, it would use external mount as the helper to mount more fs-type that includes not only fs types supported from kernel layer (tmpfs/sysfs/ext4/procfs/..).
Would this design be better supported?

To clarify, --mount and the option set you are proposing are completely different subsystems. For example, type passed to mount selects the type of the mount, whereas type passed to the local volume driver sets the filesystem type. It seems like we are on the same page, since you're proposing volume options.
Can we just have the mount help get looked up based on the type?
Volume creation would be the following:
docker volume create --opt type=fuse.sshfs --opt device=$(whoami)@localhost:/tmp --opt o=StrictHostKeyChecking=no

Or, creation with a mount:
--mount src=sshfs-user-$(whoami),dst=/mnt,volume-opt=type=fuse.sshfs,volume-opt=device=$(whoami)@localhost:/tmp,volume-opt=o=StrictHostKeyChecking=no

(Note that if you pre-create the volume, you only need src and dst for this to work, since the volume will already be mounted as a local volume)
@cpuguy83 @justincormack Am I missing something here?

If we let local volume driver support it:
docker volume create --opt type=fuse.sshfs --opt device=$(whoami)@localhost:/tmp --opt o=StrictHostKeyChecking=no
then docker swarm will automatically support the following:
docker swarm create .. --mount src=sshfs-user-$(whoami),dst=/mnt,volume-opt=type=fuse.sshfs,volume-opt=device=$(whoami)@localhost:/tmp,volume-opt=o=StrictHostKeyChecking=no
Because swarm arguments exactly map with docker volume driver.
So deciding the pattern on how local volume options describe external mount will fix everything above.

I found supporting this will bring more interesting usage:
cat <<EOF > /sbin/mount.hello
#!/bin/bash
zfs create $1 --mount-point=$2
zfs set-quota $1 size=10G
EOF
chmod a+x /sbin/mount.hello
Then new fs-type will be supported
docker volume create --opt type=hello

@cpuguy83 @stevvooe what do you think about this? Should we proceed?

@LK4D4 We both had said that these need to options for the local volume driver. Such an approach would work without modifications to API or swarmkit.
I am not sure about the current state of this PR.

@ghostplant looks like we can close this PR and open with options to local drivers, right?

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "local_fs_mount" git@github.com:ghostplant/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842354568400
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Do you think adding a new option "helper" (whose value could be either built-in or external) is acceptible?
If so, usage of local driver could be like this:
docker volume create --opt type=fuse.sshfs --opt device=root@<IP_ADDRESS>:/tmp --opt helper=external
and all platform that uses original local driver is not affected since they were not allowed to define helper option in old versions.

@LK4D4 Updated with options to local drivers

@cpuguy83
Case 1:  .. (no helper defined) ..
This indicates helper=built-in by default, compatible with old versions
Case 2:  .. helper=built-in ..
The same as Case 1. This indicates helper=built-in implicitly
Case 3:  .. helper=external ..
This indicates helper=external using mount from PATH
Case 4:  .. helper=external:/bin/mount ..
This indicates helper=external using mount at location /bin/mount
Is the protocol like Case 4 needed?

Now we have volume drivers that are just containers, so are simple to
create and install, this seems like a regression. This assumes that the
user has a compatible version of the helper installed on the root fs docker
has access to which understands a set of options, which is a big ask. A
plugin volume driver can install its dependencies in known versions, and
can be portable. I think executing arbitrary local commands is a mistake.
We do not provide a way to install non containerised software on docker for
Mac for example, so you will never be able to use this.
So not LGTM.
On 31 Jan 2017 9:35 a.m., "ghostplant"<EMAIL_ADDRESS>wrote:

Do you think adding a new option "helper" (whose value could be either
built-in or external) is acceptible?
If so, usage of local driver could be like this:
docker volume create --opt type=fuse.sshfs --opt device=root@<IP_ADDRESS>:/tmp
--opt helper=external
and all platform that uses original local driver is not affected since
they were not allowed to define helper option in old versions.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/pull/28645#issuecomment-276316639, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdcPAXjK80GBX4nFYA7b8YLzdtKBZgkks5rXwB7gaJpZM4K3zlv
.

@justincormack
In most cases, docker plugin is a good choice for beginners.
In the following cases, docker plugin might not be a choice.

ARM platform (raspberrypi, etc) or hyper platform;
Private docker platform which doesn't allow downloading drivers from public network;
Options that 'docker plugin' that doesn't support, such as hook-able options like pre/post-mount;

If one meets any one of the cases above, he really needs plenty of works to do.
Local volume driver supporting standard mount seems to be just providing an alternative choice exactly solving above problems when people can't use docker plugin, just like both vip and dnsrr have their own suitable applications.

@justincormack
A plugin volume driver can install its dependencies in known versions
I think this statement is not very correct. It seems docker 1.13 still doesn't support dependencies installation. Instead, it is just to execute an external mount which is compiled with Linux ELF64, bringing about:

dependencies problem: sshfs is not installed from external host;
binary compatibility problem: turn a cross-platform mount-script into an amd64 run-able script;
mount counter problem: each driver requires booting a new container, when it crashes (even restarted later), mount counter system will mess up;

In order to make docker plugin better supported by users in the future, I'd like to provide some useful suggestion below:
1) docker plugin itself should  manage mount counter instead of let plugin driver to do this:
After reading source code from not only glusterfs plugin driver but also sshfs plugin driver, I saw both of them maintain counter themselves, this is potential to break engine robust after the running plugin container crashes, see this case:
mount volume1 by container1
mount volume1 by container2
(.. volume driver crash ..)
mount volume1 by container3
umount volume1 by container3
(.. volume driver counter mess up ..)
2) reservce a special name field or namespace to store binary architecture:
docker pull install xxx/glusterfs-amd64
docker pull install xxx/glusterfs-arm32
docker pull install xxx/glusterfs-i386
..
this can let platform support hyper cloud.
3) when docker daemon is pulling glusterfs driver, it should know whether the system already installed glusterfs-client, if not, try to installer it, otherwise, running the plugin driver as a container is useless.
Before above 3 features are fixed, using local driver with helper=external:mount is a good choice.

I suggest changing 2 interfaces for the next version of docker volume API in order to avoid mount counter problem.

Update Mount(r volume.MountRequest) volume.Response to
Mount(r volume.MountRequest, firstMount bool) volume.Response

Update Unmount(r volume.MountRequest) volume.Response to
Unmount(r volume.MountRequest, lastMount bool) volume.Response

If the above interfaces not fixed, docker plugin is not good in product.
Besides, volume image for new version should have a different namespace with old version in case lots of current existing old volume images conflicting with fixed version.

Why are we talking about mount counters here? Also not aware of any issues with counting mounts. If a plugin stores counts only in memory then it is a plugin bug.

An alternative approach is to update the Request structure to provide more information:
type volumeDriverProxyMountRequest struct {
Name string
ID   string

FirstMount bool
}

type volumeDriverProxyUnmountRequest struct {
Name string
ID   string

LastMount bool
}

What do you think of this one to solve mount counter? If fine, I will create another AR to focus on it.

@cpuguy83
At least all current plugin driver have this bug. Only docker daemon knows whether a certain volume is shared or not.

I think let all volume drivers itseft to find out how many volume is shared is a big task. Persisting the counter value to disk is useless because mount command is not idempotent operation so it is hard to packaged into one transaction.
If docker daemon provide whether the volume is shared, things will be much easier to solve mount counter

It seems local driver is still more stable at the moment.

@justincormack It's not much different than what's currently available where we can specify any type and expect the kernel module to be loaded for it.
I see this as essentially the equivalent of underlay networking (macvlan, ipvlan).
@ghostplant Let's please try to keep the discussion focussed on this PR and not on several different topics.
The question is, do we allow users to specify a helper application for performing mounts with the local volume driver?

@cpuguy83
I'll explain some security consideration.
if helper is using an external application, it is superficial that helper using external mount is unsafe.
But actually there are still many other possibilities for users to do unsafe things using volume options without supporting helper. For example:

docker volume create -d local --opt type=tmpfs --opt o=4094m ..: It seems that user can simply hack the host memory with this approach
docker volume create -d local --opt type=bind --opt device=/ --opt ..: It seems that user can totally seem the host fs-root directory, which is unimaginable.

So from the examples above, the principle is that we must not allow users to customize volume options if users are untrusted. For helper using external mount, the fact is the same that we should only allow trusted administrators to use it to simplify volume description.

After discussing this with other maintainers, I'm in agreement with Justin, we don't want to rely on these distro-dependent helpers which are essentially exec-level plugins for a not well defined interface.
If, for instance, someone wants to mount a gluster volume, they can do exactly what this PR is doing but in the form of a volume plugin where the available helpers are well tested, controllable, and distributable.
Thanks for spending the time looking at this, though in the future it may be better to open an issue to discuss such changes.
Sorry we seem to be on a bit of a streak here! Let's definitely collaborate on issues so we can come up with solutions together.
Thanks again!