TypeError: string indices must be integers

Traceback (most recent call last):
  File "/Users/mathieudupuy/.pyenv/versions/3.6.15/bin/potodo", line 8, in <module>
    sys.exit(main())
  File "/Users/mathieudupuy/.pyenv/versions/3.6.15/lib/python3.6/site-packages/potodo/potodo.py", line 232, in main
    args.no_reserved,
  File "/Users/mathieudupuy/.pyenv/versions/3.6.15/lib/python3.6/site-packages/potodo/potodo.py", line 78, in exec_potodo
    issue_reservations = get_gh_issue_reservation()
  File "/Users/mathieudupuy/.pyenv/versions/3.6.15/lib/python3.6/site-packages/potodo/potodo.py", line 23, in get_gh_issue_reservation
    issue["title"].split()[-1].lower(): issue["user"]["login"] for issue in issues
  File "/Users/mathieudupuy/.pyenv/versions/3.6.15/lib/python3.6/site-packages/potodo/potodo.py", line 23, in <dictcomp>
    issue["title"].split()[-1].lower(): issue["user"]["login"] for issue in issues
TypeError: string indices must be integers

looks a bit similar to #117

Did you tried https://github.com/AFPy/Potodo/issues/117#issuecomment-806080136?


Perfect with 3.0-Preview in Heroku

Hi,
I try to push my server in Heroku but i have a problem with a bad swift version.
I create my project with documentation procedure :
git clone https://github.com/PerfectlySoft/PerfectTemplate.git
cd PerfectTemplate
swift build
The build work fine with swiftenv set on 3.0
After, I've generate an Xcode project with this command line :
swift package generate-xcodeproj
For upload to heroku, i have try this build pack : https://github.com/PerfectlySoft/Perfect-Heroku-Buildpack.git and i've this error :

Push rejected, failed to detect set buildpack https://github.com/PerfectlySoft/Perfect-Heroku-Buildpack.git

And with https://github.com/kylef/heroku-buildpack-swift.git :

remote: -----> Fetching set buildpack https://github.com/kylef/heroku-buildpack-swift.git... done
remote: -----> Swift app detected
remote: Cloning into 'swiftenv'...
remote: -----> Installing DEVELOPMENT-SNAPSHOT-2016-04-12-a
remote: Downloading https://swift.org/builds/development/ubuntu1404/swift-DEVELOPMENT-SNAPSHOT-2016-04-12-a/swift-DEVELOPMENT-SNAPSHOT-2016-04-12-a-ubuntu14.04.tar.gz
remote: DEVELOPMENT-SNAPSHOT-2016-04-12-a has been installed.
remote: -----> Installing clang-3.7.0
remote: -----> Building Package
remote: Cloning https://github.com/PerfectlySoft/Perfect.git
remote: Resolved version: 0.38.0
remote: Cloning https://github.com/PerfectlySoft/Perfect-Net.git
remote: Resolved version: 0.11.0
remote: Cloning https://github.com/PerfectlySoft/Perfect-OpenSSL-Linux.git
remote: Resolved version: 0.3.0
remote: /tmp/build_dfb396d0680b48eadf23ecc5211085bb/Packages/Perfect-OpenSSL-Linux/Package.swift:35:22: error: incorrect argument labels in call (have 'name:pkgConfig:providers:', expected 'name:targets:dependencies:')
remote: let package = Package(
remote:                      ^
remote: swift-build: error: The package at `/tmp/build_dfb396d0680b48eadf23ecc5211085bb/Packages/Perfect-OpenSSL-Linux' has no Package.swift for the specific version: 0.3.0
remote:
remote:  !     Push rejected, failed to compile Swift app

I've try to configure my .version-swift with  3.0-preview-1 and 3.0 but i've the same problem.
How i can upload my Prefect server with Swift-3.0-Preview-1 version in heroku ?

It looks like that buildpack is loading an old swift snapshot, so, that needs to be updated to specify the 3.0 preview, which is where Perfect master is currently building successfully.
I see that the build pack you are referencing uses swiftenv and allows for a .swiftversion file to specify which snapshot to use. you may want to try including that in your file structure as advised in the readme
You can also customise the version of Swift used with a .swift-version file in your repository:
$ cat .swift-version
2.2-SNAPSHOT-2015-12-01-b
The .swift-version file is completely compatible with swiftenv http://github.com/kylef/swiftenv.
Hope that’s useful.
Tim Taplin

On Jun 24, 2016, at 6:28 AM, Charles Harroch<EMAIL_ADDRESS>wrote:
Hi,
I try to push my server in Heroku but i have a problem with a bad swift version.
I create my project with documentation procedure :
git clone https://github.com/PerfectlySoft/PerfectTemplate.git
cd PerfectTemplate
swift build
The build work fine with swiftenv set on 3.0
After, I've generate an Xcode project with this command line :
swift package generate-xcodeproj
For upload to heroku, i have try this build pack : https://github.com/PerfectlySoft/Perfect-Heroku-Buildpack.git x-msg://8/url and i've this error :
Push rejected, failed to detect set buildpack https://github.com/PerfectlySoft/Perfect-Heroku-Buildpack.git https://github.com/PerfectlySoft/Perfect-Heroku-Buildpack.git
And with https://github.com/kylef/heroku-buildpack-swift.git x-msg://8/url :
remote: -----> Fetching set buildpack https://github.com/kylef/heroku-buildpack-swift.git https://github.com/kylef/heroku-buildpack-swift.git... done
remote: -----> Swift app detected
remote: Cloning into 'swiftenv'...
remote: -----> Installing DEVELOPMENT-SNAPSHOT-2016-04-12-a
remote: Downloading https://swift.org/builds/development/ubuntu1404/swift-DEVELOPMENT-SNAPSHOT-2016-04-12-a/swift-DEVELOPMENT-SNAPSHOT-2016-04-12-a-ubuntu14.04.tar.gz https://swift.org/builds/development/ubuntu1404/swift-DEVELOPMENT-SNAPSHOT-2016-04-12-a/swift-DEVELOPMENT-SNAPSHOT-2016-04-12-a-ubuntu14.04.tar.gz
remote: DEVELOPMENT-SNAPSHOT-2016-04-12-a has been installed.
remote: -----> Installing clang-3.7.0
remote: -----> Building Package
remote: Cloning https://github.com/PerfectlySoft/Perfect.git https://github.com/PerfectlySoft/Perfect.git
remote: Resolved version: 0.38.0
remote: Cloning https://github.com/PerfectlySoft/Perfect-Net.git https://github.com/PerfectlySoft/Perfect-Net.git
remote: Resolved version: 0.11.0
remote: Cloning https://github.com/PerfectlySoft/Perfect-OpenSSL-Linux.git https://github.com/PerfectlySoft/Perfect-OpenSSL-Linux.git
remote: Resolved version: 0.3.0
remote: /tmp/build_dfb396d0680b48eadf23ecc5211085bb/Packages/Perfect-OpenSSL-Linux/Package.swift:35:22: error: incorrect argument labels in call (have 'name:pkgConfig:providers:', expected 'name:targets:dependencies:')
remote: let package = Package(
remote: ^
remote: swift-build: error: The package at `/tmp/build_dfb396d0680b48eadf23ecc5211085bb/Packages/Perfect-OpenSSL-Linux' has no Package.swift for the specific version: 0.3.0
remote:
remote: ! Push rejected, failed to compile Swift app
I've try to configure my .version-swift with 3.0-preview-1 and 3.0 but i've the same problem.
How i can upload my Prefect server with Swift-3.0-Preview-1 version in heroku ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/PerfectlySoft/Perfect/issues/198, or mute the thread https://github.com/notifications/unsubscribe/AATZRlBEPFE8nTut3sWl2TcJt1uKBishks5qO81SgaJpZM4I9uM5.

@CharlesHarroch can you let us know if this solves the issue? That way we can take appropriate action :) Thanks!

Hi,
I have exactly the same problem as described in the first post.
Changing the .swif-version resulted in:

-----> Fetching set buildpack https://github.com/kylef/heroku-buildpack-swift.git... Done
-----> Swift app detected
Cloning into 'swiftenv'...
-----> Installing 3.0-PREVIEW-1
We don't have build instructions for 3.0-PREVIEW-1.
!     Push rejected, failed to compile Swift app

@iamjono No, this solution not resolve my problem. I've already try to update my .swift-version. I think we have a problem with buildpack and swiftenv who are not update for support swift-3.0-preview-1.

I’m working on updating the heroku build pack. It seems that the move to SPM has left all the current swift on Heroku build packs behind, and there’s some substantial issues with getting the dependencies for Perfect installed at the OS level. I hope to have something posted today that will get things moving and then work on a more flexible and useful solution.
Tim Taplin

On Jun 27, 2016, at 1:50 AM, Charles Harroch<EMAIL_ADDRESS>wrote:
@iamjono https://github.com/iamjono No, this solution not resolve my problem. I've already try to update my .swift-version. I think we have a problem with buildpack and swiftenv who are not update for support swift-3.0-preview-1.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/PerfectlySoft/Perfect/issues/198#issuecomment-228676179, or mute the thread https://github.com/notifications/unsubscribe/AATZRrGYohky51eWrGVMfk4SOSo40UHEks5qP4C6gaJpZM4I9uM5.

We're aware there are some issues with Heroku - @Sha0 is tasked to monster this - some of the restrictions Heroku places on package locations are an issue, if I understand the problem communicated to me correctly.

So, I know I posted this in Gitter last week, but I've updated to make sure it runs with the current linux preview, and wanted to make sure to post here as well.
A simple working version of Perfect on Heroku buildpack is available here:
https://github.com/taplin/Perfect-Heroku-Buildpack on branch swift3_starting_point
If you need additional dependencies, Mongoldb for example, you should be able to fork and add them to the list of apt-get install commands.
I know that Shao is working on a more comprehensive update and have passed along some of the things that I sorted out on this. This can be an interim update until that is available.


2 Website updates

1)Screwdriver needs to be added to Projects and mentioned on front page
2)SIG and Working Groups should be separated

Added to projects page and on home page we now have a button that says "view projects"


dockerv1client: fix conversions

This popped up in oc k8s bump
/assign @deads2k @damemi

This merged in https://github.com/openshift/library-go/pull/877


Feature #16 Add example .ino for servo testing

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Docs have been added / updated (for bug fixes / features)

Is this PR related to an issue?

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Arduino compiler can not work with relative path, so I think copying files is the only way?
But I think I don't actually need those libraries in example folder since the .ino file is just an example of how to use the libraries.
I'll open a new issue and re-upload files later.


Update documentation to include ClinGen references

With the inclusion of ClinGen in the 20.09 release, we need to update the documentation to reflect the new data source:

[ ] Update association score visual on scoring page
[ ] Add entry for ClinGen and description on Genetic associations page

@DSuveges, @AsierGonzalez, @d0choa:
I have drafted a potential ClinGen description for the Genetic association page in our documentation. Can you please review what I have written below and comment with any edits or alternative links?
The ClinGen Gene-Disease Clinical Validity Curation is a manual curation process that evaluates the strength of data and evidence used to support or refute a claim that variation of a particular gene causes a particular disease. Gene-disease relationships are evaluated using a set of criteria to establish clinical validity and curators make a qualitative classification using a set of agreed terms: "Definitive," "Strong," "Moderate," "Limited," "No Reported Evidence," or "Conflicting Evidence." For more information on ClinGen's curation approach, see Strande et al., 2017.

It sounds very similar to some of the lines in their website but I find those clearer:

The ClinGen Gene-Disease Clinical Validity curation process involves evaluating the strength of evidence supporting or refuting a claim that variation in a particular gene causes a particular disease.

If you want to keep your text I would say variation in rathern than of a particular gene, I have seen it like that more often.
Also, not sure if you want to list the terms used for the confidence levels or just say that "the evidence supporting a gene-disease association is described in a semi-quantitative manner" as they do in their website.
Finally, I would mention that we integrate the gene-disease pairs that have been evaluated by ClinGen available at https://search.clinicalgenome.org/kb/gene-validity.

I would also check what @emcdonagh-OT thinks, as she suggested we use this data and she is more familiar with it.

Hello...my suggestion is below:
ClinGen
The ClinGen Gene-Disease Clinical Validity curation process involves evaluating the strength of evidence supporting or refuting a claim that variation in a particular gene causes a particular disease. Gene-disease relationships are evaluated using a framework to provide a semiquantitative measurement for the strength of evidence. This results in a qualitative classification for each curated gene-disease relationship: "Definitive," "Strong," "Moderate," "Limited," "No Reported Evidence," or "Conflicting Evidence." For more details on ClinGen's curation approach, see Strande et al., 2017.
We integrate the gene-disease pairs that have been evaluated by ClinGen (available at https://search.clinicalgenome.org/kb/gene-validity) into our target-disease associations and evidence scoring. (Add details on how each assessment "Definitive," "Strong," "Moderate," "Limited," "No Reported Evidence," or "Conflicting Evidence." is scored).

I really like Ellie's suggestion. The only thing I don't see very clear is including the details of the scoring, I think that the association score page is the correct place for this information.

For consistency, the information from each paragraph could go in different pages

Confirmed and reviewed documentation available on the team Google Drive

Ticket closed - released as part of 20.09


Solver Boundary Assertions

When solving for a request that involves API breaking changes, I feel like rez encounters a grey area issue.
I would define the gray area issue like this:

A lack of explicit boundaries impacts the user's ability to verify that a given resolve does not contain a naively bounded request for a child, given the child has released an API breaking change in a version (package-BOUNDARY+).

The solution I've considered is that the resolve provides a warning if a boundary is not clearly respected. I would imagine that a boundary would be a configuration setting in either a context, the rez settings, or in a package repository.
The boundaries could be defined as assertions that have two forms:

All requests have a high bound of (BOUNDARY)
All requests have a low bound of (BOUNDARY)

The assertions should raise a warning, and if there was an appropriate place for the configuration settings, there should be the ability to turn that into an error or exception that fails a resolve.
I'm not sure if there is already something that can make these assertions, or if all the faculties for a solution like this are in place.
@nerdvegas, I would be curious about your thoughts:

If you feel like it would be feasible to implement

If so, an estimate of what needs to be done (where) to implement it

So, do you mean that a package should be able to define the constraints
under which it should be required by other packages?
For example, if I have package 'foo', and I know that major version changes
== API breakage, are you suggesting we could do something like so:
package.py
name = "foo"
requirement_rank = 1
So here, 'requirement_rank' indicates that other packages should have
requirements on foo bounded at least to the major version (rank==1).
Failure to do so will result in either a warning or error, depending on
configuration.
I think this would be a useful feature. It'd be an update to the solver - a
day or two of work I think.
Thx
A
On Wed, Feb 8, 2017 at 7:34 AM, Aaron Morris<EMAIL_ADDRESS>wrote:

When solving for a request that involves API breaking changes, I feel like
rez encounters a grey area issue.
I would define the gray area issue like this:
A lack of explicit boundaries impacts the user's ability to verify that a
given resolve does not contain a naively bounded request for a child, given
the child has released an API breaking change in a version
(package-BOUNDARY+).
The solution I've considered is that the resolve provides a warning if
a boundary is not clearly respected. I would imagine that a boundary would
be a configuration setting in either a context, the rez settings, or in a
package repository.
The boundaries could be defined as assertions that have two forms:

All requests have a high bound of (BOUNDARY)
All requests have a low bound of (BOUNDARY)

The assertions should raise a warning, and if there was an appropriate
place for the configuration settings, there should be the ability to turn
that into an error or exception that fails a resolve.
I'm not sure if there is already something that can make these assertions,
or if all the faculties for a solution like this are in place.
@nerdvegas https://github.com/nerdvegas, I would be curious about your
thoughts:

If you feel like it would be feasible to implement

If so, an estimate of what needs to be done (where) to implement
it

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nerdvegas/rez/issues/383, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABjqSjbhhQ7pANBUeV4TYmIQYIR_6oVNks5raNVzgaJpZM4L5_-Z
.

I think that would be the case. Would rank==2 then do the same for anything not bounded to the minor version?
Perhaps I can take a look at a pull request then.

Yes, rank==2 would mean requirements have to be down to the minor version.
There would also be a legitimate case for rank==0. I think you should be
able to set a global default requirement_rank (which would probably be 1),
but for the odd cases where you have a package that should allow unbounded
requests, you could override requirement_rank=0 specifically for that
package.
Cheers
A
On Wed, Feb 8, 2017 at 9:04 AM, Aaron Morris<EMAIL_ADDRESS>wrote:

I think that would be the case. Would rank==2 then do the same for
anything not bounded to the minor version?
Perhaps I can take a look at a pull request then.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nerdvegas/rez/issues/383#issuecomment-278156375, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABjqSl2dXjpWB-JumavGz94BNCR5t7M2ks5raOpfgaJpZM4L5_-Z
.

I've started by adding a package_filter rule that filters based on package requires.

does not match if the requirement family is not in requires
matches if the ranges intersect (requested x filter.required)

This allows for naive requests to be filtered with following forms of rules:
include:
  - requires('package-2')

exclude:
  - requires('package>reasonable_bound',warning)

This matches my (explicit backwards/forwards-assurance) use case:
An unexpected breakage has cropped up and we need to ensure that requests for it are unbaised
Given Unexpected breakage in bombastic-0.11

pkg-0.4.0 already requires bombastic-0.8+<1 (Upper bound is inappropriate)
Release pkg-0.4.1 (updated for bombastic-0.8+<0.11)
Release pkg-0.5.0 (updated for bombastic-0.11+<1)

rez-resolve bombastic pkg --exclude 'requires(bombastic>0.10,warning)'
23:01:08 WARNING filter(requires(bombastic>0.10)) pkg-0.4.0: 'bombastic-0.8+<1' overlaps bombastic>0.10
> pkg-0.4.1

rez-resolve bombastic pkg --exclude 'requires(bombastic<0.11)'
> pkg-0.5.0

With only 0.4.0, both resolves would fail with a MissingPackageError after reducing all package versions with naive requires for pkg-0.x+<1.
Singular resolves and PackageFilter().iter_packages() could be used for investigations in this regard.
I don't think you could accomplish this backwards-assurance with package_rank since that would be version-specific and allow for step-down resolves for that package family if not set up before the breakage.
Will continue investigating the solver route.

Hey Aaron,
Ah ok, I see your intention now. My suggestion of requirement_rank solves a
slightly different problem - it is a way for a package to advertise to
other packages where API breakage occurs (typically major version), and so
can produce errors if other packages use a requirement that is a superset
of that rank.
You are solving a different problem - the ability to add extra constraints
to a resolve, after a known bad release (ie one that breaks API when it
shouldn't have) occurs.
I think the package filter approach works. I certainly see the value in
doing this (as per your eg):
rez-resolve bombastic pkg --exclude 'requires(bombastic<0.11)'

pkg-0.5.0

However, regarding the earlier example:
rez-resolve bombastic pkg --exclude
'requires(bombastic>0.10,warning)'23:01:08 WARNING
filter(requires(bombastic>0.10)) pkg-0.4.0: 'bombastic-0.8+<1'
overlaps bombastic>0.10

pkg-0.4.1

I'm not sure we'd ever need to do this (although granted this is no
extra implementation, it's just what you can do with the
existing filters). Why wouldn't you just rez-env "pkg ~bombastic<0.11"
in this case? Why would we release a pkg-0.4.1, and
use a package filter, when we can just constrain bombastic with an
extra, normal requirement - and when we know that pkg-0.4.0
works fine with bombastic<0.11?
Cheers
A
On Thu, Feb 9, 2017 at 3:08 AM, Aaron Morris<EMAIL_ADDRESS>wrote:

I've started by adding a package_filter rule that filters based on package
requires.

does not match if the requirement family is not in requires
matches if the ranges intersect (requested x filter.required)

This allows for naive requests to be filtered with following forms of
rules:
include:

requires('package-2')

exclude:

requires('package>reasonable_bound',warning)

This matches my (explicit backwards/forwards-assurance) use case:
An unexpected breakage has cropped up and we need to ensure that requests
for it are unbaised
Given Unexpected breakage in bombastic-0.11

pkg-0.4.0 already requires bombastic-0.8+<1 (Upper bound is
inappropriate)
Release pkg-0.4.1 (updated for bombastic-0.8+<0.11)
Release pkg-0.5.0 (updated for bombastic-0.11+<1)

rez-resolve bombastic pkg --exclude 'requires(bombastic>0.10,warning)'
23:01:08 WARNING filter(requires(bombastic>0.10)) pkg-0.4.0: 'bombastic-0.8+<1' overlaps bombastic>0.10

pkg-0.4.1

rez-resolve bombastic pkg --exclude 'requires(bombastic<0.11)'

pkg-0.5.0

With only 0.4.0, both resolves would fail with a MissingPackageError
after reducing all package versions with naive requires for pkg-0.x+<1.
Singular resolves and PackageFilter().iter_packages() could be used for
investigations in this regard.
I don't think you could accomplish this backwards-assurance with
package_rank since that would be version-specific and allow for step-down
resolves for that package family if not set up before the breakage.
Will continue investigating the solver route.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nerdvegas/rez/issues/383#issuecomment-278372373, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABjqSqwxubQYg4-jSZpPl2Q1XyaBIxypks5raeh2gaJpZM4L5_-Z
.

why not just rez-env "pkg ~bombastic<0.11"

I think you're right. The only behavior a requires would provide here is additionally filtering a package that does not explicitly bound its request.


[Enhancement] Encrypt data file

So that users cannot edit it and introduce bugs

Closes due to Constraint-Human-Editable-File as mentioned here


Does not work on Docker

The latest version Docusign node client does not work on docker.
This is because the file docusign-esign/src/ApiClient.js uses require Oauth.js where as the file is OAuth.js (notice the case)
This works ok on windows or mac but does not on linux (and Docker)
We had to use 4.1.0 version of docusign to make it work.
Cannot find module './Oauth'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at new exports (/usr/local/checkbox-validator-dev/node_modules/docusign-esign/src/ApiClient.js:119:22)
    at /usr/local/checkbox-validator-dev/node_modules/docusign-esign/src/ApiClient.js:899:22
    at isArray (/usr/local/checkbox-validator-dev/node_modules/docusign-esign/src/ApiClient.js:18:22)
    at Object.<anonymous> (/usr/local/checkbox-validator-dev/node_modules/docusign-esign/src/ApiClient.js:26:2)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)

@nmjmdr A fix has been added to the existing RC. Please run npm install docusign-esign@next to receive this fix


Couldn't find the training data source

When I was training the file PhyCRNet.py, I could find the file burgers_1501x2x128x128.mat in the directory. So I am not able to determine the dimension of uv.
Many thanks!
Johnny

When I was training the file PhyCRNet.py, I could find the file burgers_1501x2x128x128.mat in the directory. So I am not able to determine the dimension of uv.
Many thanks! Johnny

Hi Johnny,
Thank you for your interest. We did not provide the simulation data since the file size is too large, but we have uploaded the code for generating the numerical data. You can find them in the file Datasets.


is the app abandoned ?

latest update was back in 2020, may i ask if this app is abandoned ?

I have been working on an update to the app that will be released within the next couple weeks or so.

Exciting 😀

I'll have an update out by this weekend, lots of IRL stuff that I've been having to deal with.


Wrappers for methods of Array.prototype broken

See https://github.com/kangax/compat-table/issues/531#issuecomment-100466634
[].map.call({length: -1}, isNaN);  // => undefined, should be []
[].some.call({length: -1}, isNaN); // => undefined, should be false

it can be simple fixed, but not so simple
var c = 0;
[].map.call({get length(){c++;return 0}}, isNaN);
c; // => 2, should be 1

var O = {length: Math.pow(2, 32) + 1};
O[Math.pow(2, 32)] = 42;
[].forEach.call(O, console.log, console); // => nothing, should be 42,<PHONE_NUMBER>, O

Repeating my comment here:
For the first one, there's simply no solution for array-like objects with getters to avoid calling it twice besides, as you said, redefining the entire method. I suspect that's not worth it for the obscure tiny edge case of an array-like object with a getter for the length.
For the second one, it goes through https://people.mozilla.org/~jorendorff/es6-draft.html#sec-tolength to https://people.mozilla.org/~jorendorff/es6-draft.html#sec-arraysetlength to https://people.mozilla.org/~jorendorff/es6-draft.html#sec-touint32 - which means Math.pow(2, 32) + 1 becomes 1 and so your Math.pow(2, 32) key should never be visited - so I think this isn't actually a bug.

If we can shim the ES5 array methods in the es6-shim without taking a performance hit, that's not a bad option, but that also means we'll be repeating es5-shim code here. If we ever move to a build model where all the shims are npm-installed, then the es5-shim's methods could be pulled in with virtually no impact, but until then, it'd be a lot of extra weight.

About second - nope, by spec there is should not be toUint32 conversion, only toLength - it's array-like object, not array.

Ah, good call. The second one is definitely something I can fix, thanks.


How does one unbox a dictionary of [String:Date]?

If I have an object that looks like:
@objc
class Foo: NSObject, Unboxable {
    var createdAt: Date
    var idHash: [String:Date]
}

I know I can use a DateFormatter to unbox the createdAt variable, but how do I unbox the idHash?
The JSON for this object may look like:
{
    "createdAt": "2017-05-22T08:04:23.283Z",
    "idHash": {
        "E8A8A6F0-A383-462A-9B4F-6A12D38C5B74": "2017-05-22T08:05:11.880Z",
        "012E423B-8586-4A4A-87AB-BF17EAC55CC1": "2017-05-22T08:04:23.283Z",
        "F58164D0-190E-4137-B775-48A9978FBAC0": "2017-05-21T14:22:18.333Z"
    }
}

Thanks!

Hmmm...seems just passing the DateFormatter seems to automatically work.  I'm not quite sure how that works, but ok.   Thanks.


Fix: Allow the usage of frozenset in the isin(...) and notin(...) functions

This merge request should allow users to use .isin(...) and .notin(...) functions with frozenset as an argument.
Current behavior throws an error as in this minimal reproducible example:
>>> from pypika import Table, Query
>>> best_customers = frozenset([1, 2, 3])
>>> customers = Table('customers')
>>> Query.from_(customers).select(customers.id, customers.name).where(customers.id.isin(best_customers))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/REDACTED_PATH_TO_PYTHON/python3.11/site-packages/pypika/utils.py", line 50, in _copy
    result = func(self_copy, *args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/REDACTED_PATH_TO_PYTHON/python3.11/site-packages/pypika/queries.py", line 930, in where
    if not self._validate_table(criterion):
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/REDACTED_PATH_TO_PYTHON/python3.11/site-packages/pypika/queries.py", line 1155, in _validate_table
    for field in term.fields_():
                 ^^^^^^^^^^^^^^
  File "/REDACTED_PATH_TO_PYTHON/python3.11/site-packages/pypika/terms.py", line 57, in fields_
    return set(self.find_(Field))
               ^^^^^^^^^^^^^^^^^
  File "/REDACTED_PATH_TO_PYTHON/python3.11/site-packages/pypika/terms.py", line 37, in find_
    return [node for node in self.nodes_() if isinstance(node, type)]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/REDACTED_PATH_TO_PYTHON/python3.11/site-packages/pypika/terms.py", line 37, in <listcomp>
    return [node for node in self.nodes_() if isinstance(node, type)]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/REDACTED_PATH_TO_PYTHON/python3.11/site-packages/pypika/terms.py", line 795, in nodes_
    yield from self.container.nodes_()
               ^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'frozenset' object has no attribute 'nodes_'
>>>

Could you add a test for this feature?

@AzisK done, tests added :heavy_check_mark:

Looks good. I am merging this but the version will be bumped later. Thanks for your effort


Initializing GRNN with default parameters will raise ValueError

Initializing GRNN with default parameters model = GRNN() will raise ValueError if scikit-learn version 0.24 or higher is used. That is caused by KFold(n_splits= self.n_splits, random_state=self.seed) call on line 161. Since ver. 0.24 it is an incorrect way to call KFold class with int value passed to random_state but without changing shuffle=True. It can be either KFold(n_splits= self.n_splits, random_state=self.seed, shuffle=True) or KFold(n_splits= self.n_splits, random_state=None, shuffle=False).
Temporary way around this issue may be to intialize your model as model = GRNN(seed=None)

Thanks a lot for pointing this out. I updated the package to include KFold(n_splits= self.n_splits, random_state=self.seed, shuffle=True)


Upgrade hyper to v1

cc https://github.com/metrics-rs/metrics/pull/411
The hyper CHANGELOG https://github.com/hyperium/hyper/blob/master/CHANGELOG.md

Looks like this requires unpublished changes to hyper-tls. I don't tie anything in metrics to unpublished crate versions, so this PR will have to wait until hyper-tls cuts a release.


Quest: Ode of destruction

oops, accidently posted without anything in it.
The quest does not give you a beautiful quest textured solgaleo but a normal 1, The capture stage is on stage 14/15.
I have checked this myself.

If this happens to all quests with special textures, please make sure that we can have a master ticket. If this only happens with this quest, please edit the title accordingly to clarify. Testing this is necessary.

If this happens to all quests with special textures, please make sure that we can have a master ticket. If this only happens with this quest, please edit the title accordingly to clarify. Testing this is necessary.

Issue same as #908 , should also be fixed. Closing.

Issue same as #908 , should also be fixed. Closing.


IPInfo region text decoding

We don't do any of the text handling in https://github.com/catalystneuro/dandi_s3_log_parser/blob/main/src/dandi_s3_log_parser/_ip_utils.py#L86-L99, assuming ipinfo would handle ASCII vs. other
But some entries of the hash table (and consequently, must be somewhere in the parsed logs) I find elements such as
"HU/Csongr\xE1d"

so maybe we need some post-parsing

# Original string with escape sequence
original_string = "HU/Csongr\xE1d"

# Directly decoding the string
decoded_string = original_string.encode('latin1').decode('latin1')

print(decoded_string)

HU/Csongrád


changed art gallery again to automated slideshow

In html files, could you remove redundant spaces for id and other attributes values, e.g.:
img src = "images/art-4.jpg" alt = "Grandma's Living Room" style="height:100%"
=>
img src="images/art-4.jpg" alt="Grandma's Living Room" style="height:100%"

done.


[Bug] Unable to delete copied nodes in unsaved workflow

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
If a node is copied in an existing workflow, it cannot be deleted without being saved

What you expected to happen
Copy a workflow node
How to reproduce

Create a workflow with nodes
Copy the node without saving it
Delete a node (cannot be deleted)

Anything else
No response
Version
3.2.x
use  docker image: apache/dolphinscheduler-standalone-server:3.2.2
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This is a known issue. Both imported and copied workflow have the same problems.

i want to try fix

I've assigned to you. Looking forward to your contribution.

the back-end interface may report errors
When the back end returns normal, but returns an empty array, the front end cannot proceed to the next step

use-dependencies.ts:152 Uncaught (in promise) TypeError: res.filter is not a function
    at use-dependencies.ts:152:14
    at async getDependentTaskLinksByTask (use-dependencies.ts:149:7)
    at async handleDelete (dag-context-menu.tsx:150:19)

For example:
await queryDependentTasks(projectCode, dependentTaskReq).then(
        (res: any) => {
          res
            .filter((item: any) => item.processDefinitionCode !== workflowCode)
            .forEach((item: any) => {
              dependentTaskLinks.push({
                text:
                  item.processDefinitionName + '->' + item.taskDefinitionName,
                show: true,
                action: () => {
                  const url = `/projects/${item.projectCode}/workflow/definitions/${item.processDefinitionCode}`
                  window.open(url, '_blank')
                }
              })
            })
        }
      )

Let me verify that again


Fixes and improvements

Fix #263
Fix #201
Fix #132

Love this program!  I can't wait to see the next release!!
I got the v2.0 release to run with all checks enabled on my win10 box (SuperMicro dual XEON, 48 GB, ECC, RAID) without issues - and was able to do a compare.
I was able to build your ImproveLogging branch, but never could get the GUI to publish properly.
I ran the CLI version of the ImproveLogging as:
asaCli.exe collect --all --runid 1stScan.
The first time a tried it, I used verbose.  It ran for about 20 minutes, and crashed my win10 box (never crashed before) with a DPC WATCHDOG VIOLOATION.  I don't think it got pas the C:\ drive (at least, only C:\ files were in the log).
I then ran it without the verbose flag - but I did NOT disable telemetry so you may have that?
It crashed Win10 again during the FileSystemCollector phase.  It made it all the way thru my C:\  D:\ and was scanning E:\ for maybe 5 minutes before BSOD (no log this time, but I could watch the DOS window remotely and did a screen shot before the BSOD).
I'll see about putting together a coherent post on my issues with publishing the GUI version.  I'm probably making some totally obvious mistake, but I spent a number of hours trying to get it to work.  It may have something to so with:
Start npm install...
Microsoft Windows [Version 10.0.18362.295]
(c) 2019 Microsoft Corporation. All rights reserved.
'npm' is not recognized as an internal or external command,
operable program or batch file.
Here's my DOS window when running the CLI.

Thanks for the feedback! I'm glad you're finding it useful!
Cli Crash feedback
Thanks for that feedback.  I haven't been able to reproduce that on my side, but I haven't done tests on systems with multiple drives.  How many records were collected as part of the (crashed) collection?  As a workaround, could you try collecting just that E drive using the --selected-directories flag?
I'm wondering if its an issue with properly handling one of your files on your E drive.
Gui Build Issues
It looks like you don't have Node installed (or its not on your path).  You need to have node.js installed to build the full GUI (Electron Based).  The BUILD instructions should be correct, but if you've followed those and are still having trouble please let me know so we can update them.
You could instead build the slim gui (runs in your own browser) by just dotnet building the Gui directory.
Note however, on the master branch/this branch the GUI is not up to date with the changes made in the Lib/Cli yet so it will basically function as it does on the 2.0 branch (the 2.1 gui interface rewrite is coming in the next week or two.)
Did you find our build documentation?  Please let me know if you found anything out of date or incorrect, or if there is something here missing (given the trouble you experienced)

Thank you - for all your great work!  The project reminds me of software I used back in the 90's called InCtrl - I think from some now defunct PC magazine.
I don't think it got to the E: drive the first time I can it in verbose mode.  It created a log and all the files it listed were on the C: drive - and then the log just ended.  So, I ?beleive? it got further along without the verbose, and was totally past C: and D:
I'll have to check the swap file - whether that's set to dynamically expand - I may have set it to a fixed size as 48GB Used to be a lot of RAM.  So, it could be something as simple as running out of swap file (if that would crash Win10?).  I've never seen that box crash before and I'm very curious!
So, the CLI is what I want to use anyway to get the extra logging enhancements?  I can't wait to see the highlighting and greater clarity.
I'm a bit out of time and will get back to this hopefully during the evening, but I'll give you my very unorganized notes and maybe they are of use as they are not very long?
I did (or thought I did) install Node.js (and certainly saw that in the docs), but ... possibly I made some error or it isn't in the correct place?
To get all the projects in the solution to build, my location for Electronize was different than yours, so I had to change:
G:\Git Repos\Gui\Properties [1]
launchSettings.json [1]
Code	File	Line	Column
"executablePath": "C:\Users\Gstoc\.dotnet\tools\electronize.exe",	G:\Git Repos\Gui\Properties\launchSettings.json	13	60
Changed to C:\Users\UserName\.dotnet\tools\electronize.exe
NOTE: also had to change workingDirectory which was
workingDirectory": "C:\Users\Gstoc\Documents\GitHub\AttackSurfaceAnalyzer\Gui"
changed to G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Gui
These are the notes I made yesterday while working on getting the GUI to publish.   I should start over and create more organized notes on this.   I am no doubt making some beginner mistake or skipping some part of the instructions:
got an error on build while running Electronize
System.AggregateException
HResult=0x80131500
Message=One or more errors occurred. (The directory name is invalid)
Source=System.Private.CoreLib
StackTrace:
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at ElectronNET.CLI.Program.Main(String[] args)
Inner Exception 1:
Win32Exception: The directory name is invalid
this MIGHT have somethign to do with it??
Copyright (C) Microsoft Corporation. All rights reserved.
Restore completed in 2.6 sec for G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Lib\AsaLib.csproj.
Restore completed in 2.62 sec for G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Cli\AsaCli.csproj.
Restore completed in 5.15 sec for G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Gui\AsaGui.csproj.
You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
AsaLib -> G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Lib\bin\Debug\netcoreapp2.2\AsaLib.dll
Created package at G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Lib\bin\Debug\AttackSurfaceAnalyzer.2.1.0-
pha-g.nupkg.
AsaCli -> G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Cli\bin\Debug\netcoreapp2.2\AsaCli.dll
AsaGui -> G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Gui\bin\Debug\netcoreapp2.2\win-x64\AsaGui.dll
AsaGui -> G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Gui\bin\Debug\netcoreapp2.2\win-x64\AsaGui.Views.dl
AsaGui -> G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Gui\obj\Host\bin
G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Gui>
node_modules missing in: G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Gui\obj\Host\node_modules
Start npm install...
Microsoft Windows [Version 10.0.18362.295]
(c) 2019 Microsoft Corporation. All rights reserved.
'npm' is not recognized as an internal or external command,
operable program or batch file.
G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Gui\obj\Host>npm install
G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Gui\obj\Host>
ElectronHostHook handling started...
Invoke electron.cmd - in dir: G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Gui\obj\Host\node_modules.bin
C:\Users\UserName.dotnet\tools\electronize.exe (process 10252) exited with code -1.
To automatically close the console when debugging stops, enable Tools->Options->Debugging->Automatically close the con
le when debugging stops.
Press any key to close this window . . .

It looks like the Electron GUI is broken on this branch.  I'll open a separate issue to investigate. #265
I'd recommend sticking to the CLI.  On that note, instead of using "compare" try using "export-collect" that will give you a json output.

In the 1st scan with -verbose where it failed in the middle of the scan of C:, there are over 98,000 entries in the log.
Might want to add C:\Windows\Temp\ to the exclude?
Right after:
019-09-02 11:31:54.517 -05:00 [VRB] C:\Windows\SysWOW64
2019-09-02 11:31:54.575 -05:00 [VRB] Couldn't access {0} to check if signature is needed.
there are hundreds of lines of the "Couldn't access {0} to check if signature is needed." as above, and then
2019-09-02 11:31:55.390 -05:00 [VRB] C:\Windows\SysWOW64\zu-ZA
Lots more of the same issue, over and over it would list a file and then give the signature is needed error until the next file like:
2019-09-02 11:31:55.480 -05:00 [VRB] C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Schemas\PSMaml
2019-09-02 11:31:55.480 -05:00 [VRB] Couldn't access {0} to check if signature is needed.
2019-09-02 11:31:55.481 -05:00 [VRB] Couldn't access {0} to check if signature is needed.
2019-09-02 11:31:55.491 -05:00 [VRB] Couldn't access {0} to check if signature is needed.
2019-09-02 11:31:55.492 -05:00 [VRB] Couldn't access {0} to check if signature is needed.
2019-09-02 11:31:55.495 -05:00 [VRB] Couldn't access {0} to check if signature is needed.
2019-09-02 11:31:55.495 -05:00 [VRB] C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules
There are a massive number of these signature needed errors until it gets to
2019-09-02 11:34:08.930 -05:00 [VRB] C:\Windows\assembly\NativeImages_v4.0.30319_64
where there are lots less - and then the signature needed errors disappear.  I have VS2019, Xamarin and Infragistics tools installed on this box.   Could be unhappy about something?
I'll try the E: drive now and see how that goes, but ... my guess is that it's not a specific file (as it would have encountered that file in my 2nd scan, but it didn't fail until way past the C: drive), but rather the total number of files or errors that accumulate and eat memory or handles or something?
I'll watch it a bit on E: to see what it does.

@exquirentibus
Thanks for spotting the bug in the verbose message.  It should read out the file which its having trouble checking.  Those messages occur when we get an UnauthorizedAccessException when attempting to read the first two bytes of a file to check if it is executable.  Those don't indicate any issue with your configuration and are safe to ignore.  I just pushed a change which improves the reporting.
It's definitely possible that its an issue that occurs when collecting a large data set at once and I was hoping to isolate which of those two it might be.  If you want to live on the cutting edge I added something which might fix it if it is a ram usage issue.
Re: Your intial question BTW - is this the correct place for my comment? I'm new to using GitHub. in the future you should create a new issue in the "Issues" section to keep things tidy.

I did a scan of E:
asaCli.exe collect --directories E: --file-system --runid E_scan
and it didn't crash (turned off telemetry first).
So, it's gotten thru C:, D: and E:.
Could the telemetry (now Off) be affecting RAM usage?
I'm going to see if I can get Directory Opus to count all the files on C: D: etc. - but ... there are a massive number and it's taking it a long time to list them.   My money is still on exhausting RAM or some other resource win10 needs to function - thus the BSOD.
It would be nice if I had a box that Didn't have a massive # of files - but this older box has the least amount of software installed of any of my boxes.
In my 'real worl;d' use, it would be great to make an Acronis Image of my main development box, install software and use ASA to monitor and keep a record of exactly what has gotten installed.

Telemetry shouldn't be much overhead. I basically only have reporting on for a few cases. Mostly exceptions.
If you have the database you can use it to enumerate how many files you have by using config --list-runs
-------- Original Message --------
On Sep 2, 2019, 5:40 PM, exquirentibus veritatem wrote:

I did a scan of E:
asaCli.exe collect --directories E: --file-system --runid E_scan
and it didn't crash (turned off telemetry first).
So, it's gotten thru C:, D: and E:.
Could the telemetry (now Off) be affecting RAM usage?
I'm going to see if I can get Directory Opus to count all the files on C: D: etc. - but ... there are a massive number and it's taking it a long time to list them. My money is still on exhausting RAM or some other resource win10 needs to function - thus the BSOD.
It would be nice if I had a box that Didn't have a massive # of files - but this older box has the least amount of software installed of any of my boxes.
In my 'real worl;d' use, it would be great to make an Acronis Image of my main development box, install software and use ASA to monitor and keep a record of exactly what has gotten installed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks - I'll definitely give your new changes a try!!
I did a Find for . using Directory Opus and then told it to NOT show folders.
There are 475,608 files on the C: drive.
I copied back over the original asa.sqlite (483 MB) that was created during the 1st BSOD.
config --list-runs reports there were no monitor runs in the database.
As we've been successful with C: D: and E: (separately), will my next step be to compile your new code and scan for all drives?
Any logging or other changes to my command line?
For my first time using GitHub and getting back up to speed with Visual Studio (took off for 2 years with some medical issues), I think I chose a challenging task ha ha - but, this code would be immediately useful to me.
Besides the obvious security features that it has, I'm hoping it will help me move my 1999 version of Timeslips over to the new Win10 box I've built.
The software runs ok on the win7-64 development box I'm on now, but thinks I don't have enough 'licenses' when I try to move it to Win10 (but I can move it to VMWare XP virtual machine) - so it must be changing some file or registry entry when it gets unhappy?
There's zero support for it - and their new software has so many bugs reported on their forums that I'd rather stay with what works and have one less stress in my life.

Correct. You should be able to just run with no new command line parameters. The change I made attempts to flush out to the database every 1000 results.
On Mon, Sep 2, 2019 at 6:08 PM, exquirentibus veritatem<EMAIL_ADDRESS>wrote:

Thanks - I'll definitely give your new changes a try!!
I did a Find for . using Directory Opus and then told it to NOT show folders.
There are 475,608 files on the C: drive.
I copied back over the original asa.sqlite (483 MB) that was created during the 1st BSOD.
config --list-runs reports there were no monitor runs in the database.
As we've been successful with C: D: and E: (separately), will my next step be to compile your new code and scan for all drives?
Any logging or other changes to my command line?
For my first time using GitHub and getting back up to speed with Visual Studio (took off for 2 years with some medical issues), I think I chose a challenging task ha ha - but, this code would be immediately useful to me.
Besides the obvious security features that it has, I'm hoping it will help me move my 1999 version of Timeslips over to the new Win10 box I've built.
The software runs ok on the win7-64 development box I'm on now, but thinks I don't have enough 'licenses' when I try to move it to Win10 (but I can move it to VMWare XP virtual machine) - so it must be changing some file or registry entry when it gets unhappy?
There's zero support for it - and their new software has so many bugs reported on their forums that I'd rather stay with what works and have one less stress in my life.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I copied over the 3 files you changed and ran:
G:\Git Repos2\ASA\Cli\bin\Release\netcoreapp2.2\win10-x64\publish>asaCli.exe collect --all --runid 1stScan
[20:55:08 INF] AttackSurfaceAnalyzerCli v.2.1.0-alpha
[20:55:09 INF] Loaded filters: Embedded
[20:55:09 INF] Begin 1stScan.
[20:55:09 INF] Starting 6 Collectors.
[20:55:09 INF] Starting FileSystemCollector.
[20:55:09 INF] Scanning root C:
[21:01:55 INF] Scanning root D:
[21:01:59 INF] Scanning root E:
[21:02:16 INF] Scanning root G:
[21:04:16 INF] Completed FileSystemCollector in 00h:09m:06s:787ms.
[21:04:16 INF] End FileSystemCollector.
[21:04:16 INF] Starting OpenPortCollector.
[21:04:16 INF] Completed OpenPortCollector in 00h:00m:00s:435ms.
[21:04:16 INF] End OpenPortCollector.
[21:04:16 INF] Starting ServiceCollector.
[21:04:16 INF] Completed ServiceCollector in 00h:00m:00s:179ms.
[21:04:16 INF] End ServiceCollector.
[21:04:16 INF] Starting UserAccountCollector.
[21:04:20 INF] Completed UserAccountCollector in 00h:00m:03s:754ms.
[21:04:20 INF] End UserAccountCollector.
[21:04:20 INF] Starting RegistryCollector.
[21:04:20 INF] Excluding Hive 'ClassesRoot' Due To Filter 'ClassesRoot'.
[21:06:14 INF] Completed RegistryCollector in 00h:01m:53s:914ms.
[21:06:14 INF] End RegistryCollector.
[21:06:14 INF] Starting CertificateCollector.
[21:07:18 INF] Completed CertificateCollector in 00h:01m:04s:286ms.
[21:07:18 INF] End CertificateCollector.
I remember that it took about 20 minutes to BSOD before, so it's running a LOT faster - and of course, it's now Finishing!!!
Thanks for your changes - they did the trick.

I ran a 2nd scan, which seemed to finish a lot quicker than I anticipated:
G:\Git Repos2\AttackSurfaceAnalyzer-gfs-ImproveLogging\Cli\bin\Release\netcoreapp2.2\win10-x64\publish>asaCli.exe collect --all --runid 2ndScan
[21:34:08 INF] AttackSurfaceAnalyzerCli v.2.1.0-alpha
[21:34:09 INF] Loaded filters: Embedded
[21:34:09 INF] Begin 2ndScan.
[21:34:09 INF] Starting 6 Collectors.
[21:34:09 INF] Starting FileSystemCollector.
[21:34:09 INF] Scanning root C:
[21:35:38 INF] Scanning root D:
[21:35:38 INF] Scanning root E:
[21:35:53 INF] Scanning root G:
[21:36:03 INF] Completed FileSystemCollector in 00h:01m:53s:912ms.
[21:36:03 INF] End FileSystemCollector.
[21:36:03 INF] Starting OpenPortCollector.
[21:36:03 INF] Completed OpenPortCollector in 00h:00m:00s:237ms.
[21:36:03 INF] End OpenPortCollector.
[21:36:03 INF] Starting ServiceCollector.
[21:36:03 INF] Completed ServiceCollector in 00h:00m:00s:170ms.
[21:36:03 INF] End ServiceCollector.
[21:36:03 INF] Starting UserAccountCollector.
[21:36:06 INF] Completed UserAccountCollector in 00h:00m:03s:153ms.
[21:36:06 INF] End UserAccountCollector.
[21:36:06 INF] Starting RegistryCollector.
[21:36:06 INF] Excluding Hive 'ClassesRoot' Due To Filter 'ClassesRoot'.
[21:37:51 INF] Completed RegistryCollector in 00h:01m:45s:285ms.
[21:37:51 INF] End RegistryCollector.
[21:37:51 INF] Starting CertificateCollector.
[21:38:55 INF] Completed CertificateCollector in 00h:01m:03s:681ms.
[21:38:55 INF] End CertificateCollector.
And then ran this export-compare:
G:\Git Repos2\ASA\Cli\bin\Release\netcoreapp2.2\win10-x64\publish>asaCli.exe export-collect
[21:41:58 INF] AttackSurfaceAnalyzerCli v.2.1.0-alpha
[21:41:58 INF] Comparing 1stScan vs 2ndScan.
[21:41:59 INF] Completed Comparing in 00h:00m:00s:365ms.
[21:41:59 INF] Loaded Analyses from Embedded.
[21:41:59 INF] Completed Analysis in 00h:00m:00s:189ms.
[21:41:59 INF] Output written to: .\1stScan_vs_2ndScan_summary.json.txt
I very likely left something off the export-compare command (a bit tired), as it didn't pick up the registry changes I made or the file system changes (but oddly enough, listed a lot of registry and file changes that I Didn't make).  I'll review this tomorrow, heading to bed.
Thanks for your assistance!!

Glad to hear you're getting a bit further with it!
It looks to me that something went wrong with that second scan.
I don't think you'd need to provide any more arguments to export-compare - (it will automatically compare the last two runs in the database) it looks like to me there were not many records being compared.  Usually I would expect comparison and analysis to take a bit longer.
How large was the resulting json.txt?

1stScan_vs_2ndScan_summary.json.txt is 115K
asa.sqlite is 2.48MB
The following seems to show 'no monitor runs' - am I missing some command line args to show the data?
G:\Git Repos2\ASA>asacli.exe config --list-runs
[10:47:57 INF] AttackSurfaceAnalyzerCli v.2.1.0-alpha
[10:47:58 INF] Dumping data from database located at asa.sqlite.
[10:47:58 INF] Begin Enumerating Collect Run Ids.
[10:47:58 INF] RunId:1stScan Timestamp:2019-09-02 20:55:09 AsaVersion:2.1.0-alpha
[10:47:58 INF] FILE : 0
[10:47:58 INF] PORT : 0
[10:47:58 INF] USER : 0
[10:47:58 INF] SERVICE : 0
[10:47:58 INF] CERTIFICATE : 0
[10:47:58 INF] REGISTRY : 0
[10:47:58 INF] RunId:2ndScan Timestamp:2019-09-02 21:34:09 AsaVersion:2.1.0-alpha
[10:47:58 INF] FILE : 0
[10:47:58 INF] PORT : 0
[10:47:58 INF] USER : 0
[10:47:58 INF] SERVICE : 0
[10:47:58 INF] CERTIFICATE : 0
[10:47:58 INF] REGISTRY : 0
[10:47:58 INF] There were no monitor runs in the database.
BTW - is thee a tool you prefer to display json?  I kind of assumed that html would be the preferred method to highlight changes, but you suggested I use json?
One request, it would be great to have optional arguments whereas any changes in a folder or registry tree would be highlighted in Red, allowing for multiple folders or trees separated by commas
such as:
--highlight-file-changes C:\Test
--highlight-reg-changes HKLM\Software\Test

The following seems to show 'no monitor runs' - am I missing some command line args to show the data?
That is correct. You don't have any monitor runs. You have only performed collection runs.  The two collection runs are listed.  It looks like due to the crash the data from those runs was lost.  I am interested in this 115 KB result file in this case, since it is reporting that there are no entries in the database.
BTW - is thee a tool you prefer to display json? I kind of assumed that html would be the preferred method to highlight changes, but you suggested I use json?
The HTML interface hasn't been updated.  I prefer searching through using a text editor with syntax highlighting like visual studio code.  You could try something like https://codebeautify.org/jsonviewer.
such as:

--highlight-file-changes C:\Test
--highlight-reg-changes HKLM\Software\Test```

This is already possible with user customizable rules provided to analysis.  The default ```analyses.json``` is in the source code [here](https://github.com/microsoft/AttackSurfaceAnalyzer/blob/gfs/ImproveLogging/analyses.json).  It highlights interesting things like Executables and certificates by default, changing the flag shown.

For your two examples, add the following rules to your ```analyses.json``` file and provide it to the ```export-collect``` command.
```  {
      "name": "Changes in a directory",
      "desc": "Flag when a files under a specific path is found.",
      "flag": "WARNING",
      "platforms": [
        "LINUX",
        "MACOS",
        "WINDOWS"
      ],
      "resultType": "FILE",
      "clauses": [
        {
          "field": "Path",
          "op": "STARTS_WITH",
          "data": [
            "C:\\Test"
          ]
        }
      ]
    },
    {
      "name": "Changes in a registry key",
      "desc": "Flag when certificates are placed on disk.",
      "flag": "INFORMATION",
      "platforms": [
        "WINDOWS"
      ],
      "resultType": "REGISTRY",
      "clauses": [
        {
          "field": "KEY",
          "op": "STARTS_WITH",
          "data": [
            "HKLM\\Software\\Test"
          ]
        }
      ]
    }```

Please take the latest changes below for the "STARTS_WITH" operation to work.

Actually, I deleted the db created during those BSOD's - this was a virgin asa.sqlite.
Glad you are way ahead of my thinking on flagging important changes.  That json viewer works well!
I'll include the 115 KB json.txt - hope it is useful.
1stScan_vs_2ndScan_summary.json.txt

Thanks.  Nothing looks wrong in your summary.json from a quick look.

But I think you are saying there are no monitor runs, even though I outlined the CMD prompt progress of both of my scans. and the export compare.  As this was not caused by the BSOD's (completely deleted the asa.sqlite db before I started the scans with your modified code), am I doing something wrong so that I'm not getting any useful output?
I changed and added a registry entry and changed a text file before my second scan and compare, and neither change showed up?  Something seems wrong if there's no detection of my changes?

Hey. Sorry for the confusion. There's two kinds of scans. "Collect" scans are what you've been doing. Capturing the static state of the system. The monitoring scans (currently only files) tracks ongoing activity.  So it is correct that you have no "Monitoring" scans from what you've mentioned doing.
From the json summary you sent it looks like it's picking up a good number of changes. But the ones you made aren't in there?

I added a key to HKLM/Software and it didn't show up in the json.  i just searched again.
I added or changed a file inside G:\Test - and it didn't show up.  I checked the time stamp when it was modified, and it was before I did the json compare output (and of course before the 2nd scan).
I ? believe ? that when I tested the 2.0 Gui version, that it picked up my changes.
I'm not sure what I could be doing wrong - you have my DOS commands and output.
I'm assuming that if I delete the asa.sqlite inside the publish directory that this starts me totally over, a clean start - and I did that before the new scans with your modified code (3 files).
It does seem odd that the json is showing changes - it's certainly picking up something, just not my test changes?
If you think it's working, I'll try it all again, deleting the asa.sqlite?

I'm not sure what you mean by copying the three files I changed.  Have you checked out the code via git?
I'm running a more thorough test of the current state of this branch and I'll let you know.

Last nite, I saw there were 3 file changes from the version I'd downloaded, so I just copied those over and did a clean and re-built everything.   then a publish.  Should I have done something different?
As I said, I'm new to GitHub.  When I originally tried to pull the files from GitHub (with VS 2019 Preview) of what I thought was your recent branch, it pulled in something different - and I spent a lot of time fixing code that was actually not broken (it wasn't' the correct version) trying to get it to build.

So the last time, I just grabbed the zip of your branch and used that - didn't use GitHub at all.  Figured this would guarantee a good outcome.

You should use Visual Studio or Git to check out the gfs/ImproveLogging branch directly if you want to test my very latest changes.  I can confirm as of tonight that is working.

ok, I'll get to that at some point Wednesday and do another test, going to be a lot during the day so not sure when.
Thanks for all the code updates - this is going to be a Very useful tool for a Lot of people!!  Maybe I can contribute something worthy to it at some point, we shall see.


Offline.on  'down' event not firing, however 'confirmed-down' event does fire.

Using /*! offline-js 0.7.13 */
When setting up an event handler the 'down' event never fires.   The 'confirmed-down' event does fire.
This is the call setup.  Offline.on('up down', this._updateState.bind(this) );
I put a conditional debug stop on the Offline.trigger function at line 70 in the transpiled offline.js module where event === 'down' and the debugger never stops at the at line 70.   If I set the conditional to event === 'confirmed-down' it finds and fires that event.
It appears to have something to do with the Offline.markDown function.  The Offline.state is 'down' when this line is executed so the Offline.trigger("down") code is never run, but the initial Offline.trigger("confirmed-down") is run, which seems to explain why I am seeing the confirmed-down event and not the 'down' event.
Offline.markDown = function() {
return Offline.trigger("confirmed-down"), "down" !== Offline.state ? (Offline.state = "down",
Offline.trigger("down")) :void 0;
I'm also using an image check.
        Offline.options = {
            // Should we check the connection status immediately on page load.
            checkOnLoad: false,

            // Should we monitor AJAX requests to help decide if we have a connection.
            interceptRequests: true,

            // Should we automatically retest periodically when the connection is down (set to false to disable).
            reconnect: {
                // How many seconds should we wait before rechecking.
                initialDelay: 3
            },

            // Should we store and attempt to remake requests which fail while the connection is down.
            requests: false,

            // Should we show a game while the connection is down to keep the user entertained?
            game: false,

            checks: {
                image: {
                    url: function() {
                        return 'images/tiny-image.png?_=' + (Math.floor(Math.random() *<PHONE_NUMBER>));
                    }
                },
                active: 'image'
            }
        };

I changed the code from
Offline.on('up down', this._updateState.bind(this) );
to separate calls for 'up' and 'down' and that seems to have resolved the problem so I am going to close the ticket.
Offline.on('up',lang.hitch(this,this._goOnline));
Offline.on('down',lang.hitch(this,this._goOffline));


[Bug] Invalid XML response encoding presentation

There's a wrong XML response encoding presentation when making requests to XML web services with response encodings like <?xml version="1.0" encoding="Windows-1251"?>. As a workaround I can save a response as a file and open it via any text editor with a proper encoding but it's quite annoying.
Insomnia: 6.3.2 (<IP_ADDRESS>88)
MacOS: 10.14.2
Wrong encoding example:

Same on Insomnia Response Preview when response charset is set like this charset=windows-1251.
Expected results on Response Preview tab: Включен отладочный режим
Actual results: Р’РєР»СЋС‡РµРЅ РѕС‚Р»Р°РґРѕС‡РЅС‹Р№ СЂРµР¶РёРј


Add create/delete KubernetesTaskManagerRunner pod lifecycle in KubernetesResourceManager

KubernetesTaskManagerRunner
KubernetesResourceManager

cc @tillrohrmann

Thanks for the additions @azagrebin. Merged it into the dev branch.


#0 [in_systemd_kubelet] Systemd::JournalError: No such file fluentd-kubernetes-daemonset:v1.3-debian-elasticsearch

fluentd
Image:
fluent/fluentd-kubernetes-daemonset:v1.3-debian-elasticsearch
Environment variables:
FLUENT_ELASTICSEARCH_HOST: elasticsearch-logging
FLUENT_ELASTICSEARCH_PORT: 9200
FLUENT_ELASTICSEARCH_SCHEME: http
FLUENT_ELASTICSEARCH_USER: elastic
FLUENT_ELASTICSEARCH_PASSWORD: changeme
FLUENT_UID: 0
FLUENTD_SYSTEMD_CONF: disable
FLUENT_ELASTICSEARCH_SED_DISABLE: true
TZ: Europe/Madrid
Commands:
I got the same problems,
019-02-27 10:54:42 +0100 [warn]: #0 [in_systemd_docker] Systemd::JournalError: No such file or directory retrying in 1s
2019-02-27 10:54:42 +0100 [warn]: #0 [in_systemd_kubelet] Systemd::JournalError: No such file or directory retrying in 1s
2019-02-27 10:54:43 +0100 [warn]: #0 [in_systemd_docker] Systemd::JournalError: No such file or directory retrying in 1s
2019-02-27 10:54:43 +0100 [warn]: #0 [in_systemd_bootkube] Systemd::JournalError: No such file or directory retrying in 1s
2019-02-27 10:54:43 +0100 [warn]: #0 [in_systemd_kubelet] Systemd::JournalError: No such file or directory retrying in 1s
2019-02-27 10:54:44 +0100 [warn]: #0 [in_systemd_bootkube] Systemd::JournalError: No such file or directory retrying in 1s
2019-02-27 10:54:44 +0100 [warn]: #0 [in_systemd_kubelet] Systemd::JournalError: No such file or directory retrying in 1s
2019-02-27 10:54:44 +0100 [warn]: #0 [in_systemd_docker] Systemd::JournalError: No such file or directory retrying in 1s
2019-02-27 10:54:45 +0100 [warn]: #0 [in_systemd_docker] Systemd::JournalError: No such file or directory retrying in 1s
2019-02-27 10:54:45 +0100 [warn]: #0 [in_systemd_bootkube] Systemd::JournalError: No such file or directory retrying in 1s
2019-02-27 10:54:45 +0100 [warn]: #0 [in_systemd_kubelet] Systemd::JournalError: No such file or directory retrying in 1s
2019-02-27 10:54:46 +0100 [warn]: #0 [in_systemd_bootkube] Systemd::JournalError: No such file or directory retrying in 1s
2019-02-27 10:54:46 +0100 [warn]: #0 [in_systemd_docker] Systemd::JournalError: No such file or directory retrying in 1s

@eskuai take a look at this https://github.com/reevoo/fluent-plugin-systemd#how-can-i-use-this-plugin-inside-of-a-docker-container-
You need to add a host volume to a /var/log/journal

can you help me?
  volumes:
  - name: varlog
    hostPath:
      path: /var/log
  - name: varlogjournal
    hostPath:
      path: /var/log/journal
  - name: varlibdockercontainers
    hostPath:
      path: /var/lib/docker/containers
  - name: config
    configMap:
      name: fluentd-config

is it ok?
but it is no working :;(

2019-02-28 17:05:44 +0100 [info]: starting fluentd-1.3.2 pid=6 ruby="2.3.3"
2019-02-28 17:05:44 +0100 [info]: spawn command to main:  cmdline=["/usr/bin/ruby2.3", "-Eascii-8bit:ascii-8bit", "/fluentd/vendor/bundle/ruby/2.3.0/bin/fluentd", "-c", "/fluentd/etc/fluent.conf", "-p", "/fluentd/plugins", "--gemfile", "/fluentd/Gemfile", "--under-supervisor"]
/fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-kubernetes_metadata_filter-2.1.6/lib/fluent/plugin/kubernetes_metadata_watch_pods.rb:34:in rescue in start_pod_watch': Exception encountered fetching metadata from Kubernetes API endpoint: pods is forbidden: User "system:serviceaccount:kube-system:fluentd" cannot list resource "pods" in API group "" at the cluster scope: RBAC: clusterrole.rbac.authorization.k8s.io "fluentd" not found ({"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:kube-system:fluentd\" cannot list resource \"pods\" in API group \"\" at the cluster scope: RBAC: clusterrole.rbac.authorization.k8s.io \"fluentd\" not found","reason":"Forbidden","details":{"kind":"pods"},"code":403} (Fluent::ConfigError) ) 	from /fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-kubernetes_metadata_filter-2.1.6/lib/fluent/plugin/kubernetes_metadata_watch_pods.rb:27:in start_pod_watch'
from /fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-kubernetes_metadata_filter-2.1.6/lib/fluent/plugin/filter_kubernetes_metadata.rb:260:in `block in configure'

You should using a manifest with -rbac prefix:
https://github.com/fluent/fluentd-kubernetes-daemonset/blob/master/fluentd-daemonset-elasticsearch-rbac.yaml
https://github.com/fluent/fluentd-kubernetes-daemonset/blob/master/fluentd-daemonset-cloudwatch-rbac.yaml
... Or copy the .rbac entries from those files and apply them into k8s.

I'm getting the same problem and I'm using the rbac version as @zerthimon suggests

This was resolved by https://github.com/fluent/fluentd-kubernetes-daemonset#disable-systemd-input for me

Mounting /var/log/journal or setting "disable" to FLUENTD_SYSTEMD_CONF should solve this issue.
Closing.


Fixed error in example

Coverage remained the same at 92.977% when pulling 6e3271ff4d9b3c4fc6248aa239d4c4a2eba3e8c8 on msayag:master into f2d21e91ab7ed929d905aa49e2b8e52f612163a8 on Unleash:master.

thanks :=)


update react-dom

Hey, cool demo. I am looking for something along these lines for a simple demo. However, I am facing with an error related with reactdom
Could be caused by a version change
Any suggestions?

Try the next branch.


CFE-380 - Improvements related to security audit

Enables gosec in .golangci.yaml
Annotate all false positives if any
Fix G306, mainly on test files, putting all os.WriteFile permissions to 0600 instead of 0644
Introduce the usage of kubelet-serving-ca.crt when calling Kubelet on HTTPS (enable TLS check)

Should not be merged before fixing the G402 - TLS InsecureSkipVerify set true

/unhold

@sherine-k @thejasn - could you take a look at the Makefile. It seems the  make generate recipe has been removed.

@sherine-k @thejasn - could you take a look at the Makefile. It seems the make generate recipe has been removed.

Looks like it never had make generate, this PR fixes the issue.

/test verify

/lgtm

/label docs-approved
/label qe-approved
/label px-approved

/test verify


ie8 download page, component icons missing

This should be fixed from e8576c6a Removing relativeURL for svg4everybody in IE8


Invalid subcommand doesn't show any errors

Currently running non-existent / invalid sub-command doesn't result in any error.
near transfer acc1 my_validator 1
[WARNING] Didn't find config at /Users/cypress/projects/nearprotocol/stakewars/staking-contract/src/config, using default shell config
{ networkId: 'local',
  nodeUrl: 'http://localhost:3030',
  keyPath: '/Users/cypress/.near/validator_key.json',
  walletUrl: 'http://localhost:4000/wallet',
  contractName: 'near-hello-devnet' }
(node:53295) ExperimentalWarning: The fs.promises API is experimental

@mikedotexe related PR https://github.com/nearprotocol/near-shell/pull/51
Note that just re-enabling strict mode is problematic, as then loading config fails when command doesn't support all of the options in config.
It should be possible to solve by loading and merging config with options manually vs going through yargs. Best place to put it is likely yargs middleware:
https://github.com/yargs/yargs/blob/master/docs/advanced.md#middleware

@mikedotexe related PR #51
Note that just re-enabling strict mode is problematic, as then loading config fails when command doesn't support all of the options in config.
It should be possible to solve by loading and merging config with options manually vs going through yargs. Best place to put it is likely yargs middleware:
https://github.com/yargs/yargs/blob/master/docs/advanced.md#middleware

Super helpful context, thank you. I took another approach here
https://github.com/nearprotocol/near-shell/pull/262
that doesn't use the strict mode, but has a default.
Knowing the history of this issue, I'll tag Jane and you on it since you'll immediately understand

Finally got this through, thanks for the patience, Illia.


Basic Dashboard View

Started Issue #12
Added a Dashboard view and updated some basic UI on the site
Current issues

Delete doesn't redirect properly by to the dashboard
still incomplete

Made @J3RN 's suggested changes and fixed the deletion redirection/edit bug :+1:
Awaiting review upon which can/should be merged.

Hey David! I'm glad to see you finished this! I'm going to be super busy over the next few days, but I should be able to review and merge this on Friday. In the meantime - Since it's finished, you can remove the Work in Progress ("WIP") label. Also, you should update the description to not include the Todo items you've finished.
PROTIP: Markdown supports checkboxes for doing todo-lists easily, like so:
- [ ] Todo item
- [x] Done item

And it renders to:

[ ] Todo item
[x] Done item

Alright, so here's my commentary:
Essentially, this PR just moves the Tasks controller to the Home controller, which doesn't really add any value. I'd like to get some more stuff in here before we merge it.
Also, the Tasks controller is still accessible (localhost:3000/tasks), but it throws an ugly error since you moved it's view.

If you want to completely remove the index view of the Tasks controller, change it's routes from resources :tasks to resources :tasks, except: :index, and delete the index method in the Tasks controller.

Completed all of @J3RN's comments. Just need to fix the test soon :tm:

Since this has gone dormant, I'm going to close it for now. We can re-open it later if necessary.


Manager update can be handled better to remove stuttering in very high FPS scenes (needs testing)

https://github.com/effekseer/EffekseerForGodot3/blob/e54e76533b29202fbffd263f7e9ab02bcc8396f1/Dev/Cpp/src/EffekseerSystem.cpp#L104
The way this function is handling the deltaFrame which is passed into manager->Update() (line 107 to 112) does not work well in very high FPS scenarios (E.g. 100+ FPS).
I have NOT YET had the chance yet to test this in Godot but I have integrated Effekseer in our separate engine, where I tried the logic in this repo (as linked above) and I found that the particle animation was stuttering (moving by small amounts suddenly after large delta times).
I fixed this by switching to the logic given below:
// Member variable defined in my renderer .h file
float m_FrameProgression = 0.0f;

// ------------------

// In the middle of the rendering function
m_FrameProgression += 60.0f * deltaSeconds;
m_Manager->Update(m_FrameProgression);
m_FrameProgression = 0.0f;

I didn't take into consideration the high FPS.
That bug will be fixed in Beta2.
Thank you for your contribution.


peer2peer network always receives messages with a timeout

I'm not 600% this is a fatal flaw, but it's an unintended discrepancy in the network providers.
For the WebSocket, only the "handshake" phase has an explicit timeout, and the ongoing process of receiving messages is not raced against a timeout. The idea being there may be extended periods of time (seconds, minutes, etc) where the connection is established, but nothing needs to be synced on the connection. With a timeout, the "waiting for a next message" on the connection would throw an error, and in the ongoing loop that would terminate the connection - potentially to see it attempt to reconnect if that was configured.
In the Peer2Peer provider, both the peering handshake process (both accepting a new connection and initiating a new connectIon) should use a timeout - we expect a timely handshake to establish the active connection, but there-after the ongoing loop - in either case - should require a timeout.

FWIW the web socket server will send a ping (the web socket ping message that is) every so often (every 5s at the moment I think) and if the client does not respond with a pong within a timeout then the server closes the connection.

Yeah, I was recalling something like that as well. I added a to-do item for myself to create a test to validate everything is working as expected with #62 - I'm not entirely clear on if or how URLSessionWebSocketDataTask does pings, and if that connection is meant to be retained with a heartbeat, if I need to add something explicit to do so.
Then there's a broader question of would it be better to drop the connection while things are idle, and attempt to reconnect when it finds a change and wants to attempt to sync it. Right now that's not an option, but maybe it should be? At least with a configurable setting.


Add review and build pipelines for autotest type for java17

Add review and build pipelines for autotest type for java17.

pipeline added and tested


07/24/2018 06:18 : Create Pull Request for branch master -> prTesting1_2018072406

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Switch from https to ffdx

Signed-off-by: Gabriel Indik<EMAIL_ADDRESS>

Important: https://github.com/hyperledger/firefly-cli/pull/156 should be merged before this change.

Codecov Report

Merging #590 (8772cc6) into main (00fda51) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #590   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          303       303
  Lines        17437     17437
=========================================
  Hits         17437     17437

Impacted Files
Coverage Δ

internal/config/config.go
100.00% <100.00%> (ø)

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 00fda51...8772cc6. Read the comment docs.

Closing based on the observations in https://github.com/hyperledger/firefly-cli/pull/156#issuecomment-1063163217

I do believe we need to fix this default @gabriel-indik, so I've done some work to fix the migration to:

Cover the case of https.url being set, with ffdx.url not being set
Avoid initializing the prefix on the default paths, so that things like ff config do not show the outdated prefix


feat: update agent interface documentation and implementation

Updated AGENTS.md to include new execute function for Buffer Editor agent.
Added detailed explanation for Command-based and Function-based agent implementation types.
Introduced Buffer Editor agent in the interface and its function execution method.
Modified init.lua to support new agent types and added agent execution logic.
Extended config.lua with Buffer Editor agent configuration.
Enhanced helpers/buffers.lua to provide buffer information and format buffer content.
Updated strategies/chat.lua to correctly require agents.init module.
Improved strategy.lua to include context in the agent strategy.
Added function to get active buffers in utils/util.lua.

During development, it is often found that purely chat models make complex code modifications very troublesome, requiring constant copying and pasting between the buffer and chat. Therefore, I attempted to introduce a type of agent that can directly interact with the buffer to allow the model to modify the buffer directly using a Search/Replace method. This part of the inspiration mainly comes from aider.


Finalize "Guide-level explanation" within Grid Purchase Order RFC

An initial version of the guide-level explanation is complete. This sprint, finalize the explanation.
[ ] Gain alignment on how a "version/draft" object will flow through Purchase Order sub-workflows.
[ ] Gain alignment on how source system records will interface/interact with the Grid Purchase Order workflows.
[ ] Review and validate permissions (and related data fields) with process SME.

The guide-level explanation was finalized and submitted as part of the Grid Purchase Order RFC. Submission occurred on 2/25/2021.


merge MiqReport#db_klass and db_class

They are both defined as db.kind_of?(Class) ? db : Object.const_get(db) The only difference being that db_klass has caching.

But db_class was already around. Must have missed that one
This is change. So closing this because we don't want to change any code is totally viable.
I just saw it and putting in the PR was less work than trying to remember to do it later

I do not know how to do a good &. with []. So I'm leaning towards ignoring this cop.


@2.4.0 -<EMAIL_ADDRESS>close #382

coverage: 99.245%. remained the same when pulling 5d9bcf6bf0bf1939b33bbbff31bf1036e1528ccb on rc-2.4.0 into 1480c1f6819d0a02a55eb08721a360903201b193 on master.


Error: [FilesCollection.users.avatars] Path "/data" is not writable! [401]

I'm afraid I don't understand the documentation. This my initialization
export default Avatars = new FilesCollection({
  collectionName: 'users.avatars',
  storagePath: '/data',
  allowClientCode: false, // Disallow remove files from Client
  onBeforeUpload: function (file) {
    // Allow upload files under 10MB, and only in png/jpg/jpeg formats
    if (file.size <= 10485760 && /png|jpg|jpeg/i.test(file.extension)) {
      return true;
    } else {
      return 'Please upload image, with size equal or less than 10MB';
    }
  }
});

Where /data is located at the root of the project, with mode 774. The user running meteor is the same who created the directory. However, when I run the app, I get

Error: [FilesCollection.users.avatars] Path "/data" is not writable! [401]

Have you tried to set config.permissions and config.parentDirPermissions?
What OS you're on?
What permissions is actually set for /data ? Could you show output of ls -la?

I didn't know about these options, but even setting them doesn't seem to change anything (i.e. 0774)
I'm on Ubuntu Gnome
Both parent (project root) and /data have drwxrwxr-x  3 yanick yanick 4096 Sep  7 14:19 data/ for permissions.

Have you tried 0777 (as a test)?

Even if it worked, this would be quite a huge security risk... but it doesn't work anyhow; I still get the same error. ... Does it actually try to set to /data from the project root, or /data from the root of the FS??

I just tried data (with no leading slash) and it seems to work. This is actually contrary to Meteor's specification that everything is absolute to the project root path. So, /data should not mean "from the root of the file system" !

leading / is server root, without slash is relative to running nodejs process
It's actually explained in FAQ:

Where files is stored by default?: by default if config.storagePath isn't passed into Constructor it's equals to assets/app/uploads and relative to running script:
On development stage: yourDevAppDir/.meteor/local/build/programs/server, note: all files will be removed as soon as your application will rebuild or you run meteor reset. To keep you storage persistent use absolute path outside of your project folder, we recommend to use /data directory
On production: yourProdAppDir/programs/server

Exactly :

To keep you storage persistent use absolute path outside of your project folder, we recommend to use /data directory

Which I supposed /data meant a directory named data at the root of the project! Which doesn't seem to be the case, since you mention /data is at the root of the server. Meteor's specification on paths is that /data would be at the root of the project (i.e. "relative to running nodejs process")
I understand that paths in this case, and paths when loading modules are two separate things, their behaviors are nonetheless contradictory, and the docs is not clear on the subject.

PR to docs is welcome

and the docs is not clear on the subject

Why? It's clearly says:

absolute path outside of your project folder

A path such as data is relative, not absolute. A path such as /data is absolute.
However, /data indicate "absolute from the server root" and data is absolute from the project path. What is clear about that? The doc does say, as /data is absolute to the project folder according to Meteor's specs when loading modules.

We are speaking of FS.
So in FS any path with leading / means root of the FS.
JS modules and etc. has not relation to FS

Hi @yanickrochon
May I assume this issue as solved?

It seems so, in the sense that the app starts. However I haven't got around to actually test it, yet.

@yanickrochon let me know if I can help you with anything else, related to this package.
Please, support this project by:

Star on GitHub
Star on Atmosphere
Share on Facebook and Twitter

Hello,
I'm getting similar error, below. How can I change the data path?
=> Exited with code: 1
W20170706-12:54:47.682(-4)? (STDERR)
W20170706-12:54:47.683(-4)? (STDERR) /Users/isingh/Phamerator/phamerator/.meteor/local/build/programs/server/packages/ostrio_files.js:967
W20170706-12:54:47.683(-4)? (STDERR)           throw new Meteor.Error(401, "[FilesCollection." + self.collectionName + "] Path "" + self.storagePath({}) + "" is not writable!", error);
W20170706-12:54:47.684(-4)? (STDERR)           ^
W20170706-12:54:48.048(-4)? (STDERR) Error: [FilesCollection.Images] Path "/data/phamerator/uploads" is not writable! [401]
W20170706-12:54:48.049(-4)? (STDERR)     at packages/ostrio_files/files.coffee:629:21
W20170706-12:54:48.049(-4)? (STDERR)     at /Users/isingh/.meteor/packages/ostrio_files/.1.7.13.r9df1f++os+web.browser+web.cordova/npm/node_modules/fs-extra/lib/mkdirs/mkdirs.js:43:19
W20170706-12:54:48.049(-4)? (STDERR)     at /Users/isingh/.meteor/packages/ostrio_files/.1.7.13.r9df1f++os+web.browser+web.cordova/npm/node_modules/fs-extra/lib/mkdirs/mkdirs.js:43:19
W20170706-12:54:48.050(-4)? (STDERR)     at /Users/isingh/.meteor/packages/ostrio_files/.1.7.13.r9df1f++os+web.browser+web.cordova/npm/node_modules/fs-extra/lib/mkdirs/mkdirs.js:55:43
W20170706-12:54:48.050(-4)? (STDERR)     at /Users/isingh/.meteor/packages/ostrio_files/.1.7.13.r9df1f++os+web.browser+web.cordova/npm/node_modules/graceful-fs/polyfills.js:284:29
W20170706-12:54:48.050(-4)? (STDERR)     at FSReqWrap.oncomplete (fs.js:82:15)
=> Exited with code: 1
=> Your application is crashing. Waiting for file change.

Hello @singhindresh ,

What Meteor and ostrio:files version you're on?
To change path use storagePath option
To make directory writable run chmod 777 /storage/path, note 777 is not the best in terms of security, but will do the trick for testing purpose

I'm on Meteor <IP_ADDRESS> and looks like ostrio:files is trying to access the file in root context which doesn't have required files. How can I change the storagePath is somewhere else where can I create folder for storagePath?
Thank
Indresh

@singhindresh as I've mentioned before:

To change path use storagePath option

I'm having the same issue and tried all of the above, but that didn't fix it.
Below is the error
"W20230219-18:19:24.667(0)? (STDERR)   reason: '[FilesCollection.ServiceFile] Path "/assets/app/uploads/ServiceFileCollection" is not writable!',
W20230219-18:19:24.667(0)? (STDERR)   details: Error: EACCES: permission denied, mkdir '/assets/app/uploads/ServiceFileCollection'
W20230219-18:19:24.668(0)? (STDERR)       at Object.mkdirSync (fs.js:1014:3)
W20230219-18:19:24.668(0)? (STDERR)       at new FilesCollection (packages/ostrio:files/server.js:350:10)
W20230219-18:19:24.668(0)? (STDERR)       at module (imports/api/service/ServiceFiles.js:10:31)
W20230219-18:19:24.669(0)? (STDERR)       at fileEvaluate (packages/modules-runtime.js:336:7)
W20230219-18:19:24.669(0)? (STDERR)       at Module.require (packages/modules-runtime.js:238:14)
W20230219-18:19:24.669(0)? (STDERR)       at Module.moduleLink [as link] (/home/runner/.meteor/packages/modules/.0.18.0.j1mso2.mw1a++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/@meteorjs/reify/lib/runtime/index.js:52:22)
W20230219-18:19:24.669(0)? (STDERR)       at module (server/main.js:1:276)
W20230219-18:19:24.669(0)? (STDERR)       at fileEvaluate (packages/modules-runtime.js:336:7)
W20230219-18:19:24.669(0)? (STDERR)       at Module.require (packages/modules-runtime.js:238:14)
W20230219-18:19:24.669(0)? (STDERR)       at require (packages/modules-runtime.js:258:21)
W20230219-18:19:24.669(0)? (STDERR)       at /tmp/meteor-test-runlvnqsp.rlri8/.meteor/local/build/programs/server/app/app.js:4255:1
W20230219-18:19:24.669(0)? (STDERR)       at /tmp/meteor-test-runlvnqsp.rlri8/.meteor/local/build/programs/server/boot.js:401:38
W20230219-18:19:24.669(0)? (STDERR)       at Array.forEach ()
W20230219-18:19:24.670(0)? (STDERR)       at /tmp/meteor-test-runlvnqsp.rlri8/.meteor/local/build/programs/server/boot.js:226:21
W20230219-18:19:24.670(0)? (STDERR)       at /tmp/meteor-test-runlvnqsp.rlri8/.meteor/local/build/programs/server/boot.js:464:7
W20230219-18:19:24.670(0)? (STDERR)       at Function.run (/tmp/meteor-test-runlvnqsp.rlri8/.meteor/local/build/programs/server/profile.js:280:14) {
W20230219-18:19:24.670(0)? (STDERR)     errno: -13,
W20230219-18:19:24.670(0)? (STDERR)     syscall: 'mkdir',
W20230219-18:19:24.670(0)? (STDERR)     code: 'EACCES',
W20230219-18:19:24.670(0)? (STDERR)     path: '/assets/app/uploads/ServiceFileCollection'
W20230219-18:19:24.670(0)? (STDERR)   },
W20230219-18:19:24.670(0)? (STDERR)   errorType: 'Meteor.Error'"

Below is the config:
"const ServiceFileCollection = new FilesCollection({
schema: mySchema,
storagePath: '/assets/app/uploads/ServiceFileCollection',
// downloadRoute: '/files/ServiceFile',
collectionName: 'ServiceFile',
// // permissions: 0o774,
// parentDirPermissions: 0o774,
// permissions: 0o755,
permissions: 0o774,
parentDirPermissions: 0o774,
allowClientCode: false,
cacheControl: 'public, max-age=31536000',
// Read more about cacheControl: https://devcenter.heroku.com/articles/increasing-application-performance-with-http-cache-headers
onbeforeunloadMessage() {
console.log(
'Upload is still in progress! Upload will be aborted if you leave this page!'
);"
I'm using Meteor 2.7.3.


Ensure that developer has enough free memory to start the web app

Recently Verena and Rong reported an issue where the web app does not start (nx serve web-app) because not enough free memory was available. I observed that the dev container uses 2.4 GB of memory after the app has successfully started. During the app startup, the memory used peaked at 2.7 GB.

In Rong's case, the dev container didn't have access to 2 GB of memory. Note that the swap provided an additional 1 GB but yet the issue occurred as the total memory of 3 GB was probably not providing a sufficient margin of error. Also swap is much slower than RAM, which makes memory-intensive operations much slower.

A solution could be to ensure that the dev container has at least 4 GB of memory available. VS Code has an option for this in devcontainer.json. This way, I expect that the dev container will not start if not enough memory is available. Hopefully VS Code will provide a descriptive message for this, thus prompting the developer to close some apps to free memory. This should reduce the risk of bumping into any memory issues during development.
Tagging @vpchung and @rrchai who bumped into this issue

Thanks @tschaffter.
I tried to add this option,  "hostRequirements" (described here) in the devcontainer.json:
"hostRequirements": {"memory": "4gb"}

With this ^ option, it did ask me if I want to continue building the devcontainer with the memory exceed my docker's memory limit.

However, after the container was built, the total memory was still same as the docker daemon's memory limit (~2G).

So, alternatively, I increased the memory limit of docker daemon to 4G using Docker Desktop and it worked:

I also tried set docker limit as 6G > devcontainer's "hostRequirements" setting as 4G. The total memory of devcontainer was 6G. It seems the "hostRequirements" either not able to overwrite the docker's limit or I didn't use the right flag.

@rrchai So the "hostRequirements" is indeed a requirement and not a "configuration" options. The behavior you described makes sense to me. Can you please open a PR that adds the 4 GB of memory requirement to the dev container definition?

@tschaffter oh right, I understand the behavior now.
If the devcontainer's requirement is larger than docker configured memory limit, the memory limit will not be overridden by the requirement. So the requirement only will be used when the docket limit is high (e.g >7G in your case). I guess we also need to change the configuration of docker somewhere?


Checkpoint -- delay to allow grid to get ready.

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry, or determined not required.
[x] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[x] Updated doc comments / prop-types, or determined not required.
[ ] Reviewed and tested on Mobile, or determined not required.
[ ] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

Don -- please take a look and let me know if this helps in the instance that you were seeing this problem?

Sorry Lee, this doesn't seem to do the trick

So Don and I took a careful look at his use-case.  I think there is a bit of a misunderstanding in the original ticket.  Will comment there

Closing. Related ticket was closed as not a bug.


IndexOutOfRangeException thrown when TextBlock text contains certain characters and TextTrimming is CharacterEllipsis

Describe the bug
When certain characters are passed to TextBlock.Text, and TextTrimming is CharacterEllipsis, the app crashes with the following exception:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at Avalonia.Media.GlyphRun.CreateGlyphRunMetrics()
   at Avalonia.Media.GlyphRun.get_Metrics()
   at Avalonia.Media.GlyphRun.get_BaselineOrigin()
   at Avalonia.Media.GlyphRun.CreateGlyphRunImpl()
   at Avalonia.Media.GlyphRun.get_PlatformImpl()
   at Avalonia.Media.GlyphRun.get_InkBounds()
   at Avalonia.Media.TextFormatting.TextLineImpl.CreateLineMetrics()
   at Avalonia.Media.TextFormatting.TextLineImpl.FinalizeLine()
   at Avalonia.Media.TextFormatting.TextLineImpl.Collapse(TextCollapsingProperties[] collapsingPropertiesList)
   at Avalonia.Media.TextFormatting.TextLayout.CreateTextLines()
   at Avalonia.Media.TextFormatting.TextLayout..ctor(ITextSource textSource, TextParagraphProperties paragraphProperties, TextTrimming textTrimming, Double maxWidth, Double maxHeight, Int32 maxLines)
   at Avalonia.Controls.TextBlock.CreateTextLayout(String text)
   at Avalonia.Controls.TextBlock.get_TextLayout()
   at Avalonia.Controls.TextBlock.MeasureOverride(Size availableSize)
   at Avalonia.Layout.Layoutable.MeasureCore(Size availableSize)
   at Avalonia.Layout.Layoutable.Measure(Size availableSize)
   at Avalonia.Layout.LayoutHelper.MeasureChild(Layoutable control, Size availableSize, Thickness padding, Thickness borderThickness)
   at Avalonia.Controls.Presenters.ContentPresenter.MeasureOverride(Size availableSize)
   at Avalonia.Layout.Layoutable.MeasureCore(Size availableSize)
   at Avalonia.Layout.Layoutable.Measure(Size availableSize)
   at Avalonia.Layout.LayoutHelper.MeasureChild(Layoutable control, Size availableSize, Thickness padding)
   at Avalonia.Controls.Decorator.MeasureOverride(Size availableSize)
   at Avalonia.Controls.Primitives.VisualLayerManager.MeasureOverride(Size availableSize)
   at Avalonia.Layout.Layoutable.MeasureCore(Size availableSize)
   at Avalonia.Layout.Layoutable.Measure(Size availableSize)
   at Avalonia.Layout.Layoutable.MeasureOverride(Size availableSize)
   at Avalonia.Layout.Layoutable.MeasureCore(Size availableSize)
   at Avalonia.Layout.Layoutable.Measure(Size availableSize)
   at Avalonia.Layout.Layoutable.MeasureOverride(Size availableSize)
   at Avalonia.Controls.Window.MeasureOverride(Size availableSize)
   at Avalonia.Controls.WindowBase.MeasureCore(Size availableSize)
   at Avalonia.Layout.Layoutable.Measure(Size availableSize)
   at Avalonia.Layout.LayoutManager.Measure(Layoutable control)
   at Avalonia.Layout.LayoutManager.ExecuteInitialLayoutPass()
   at Avalonia.Controls.Window.ShowCore(Window owner)
   at Avalonia.Controls.Window.Show()
   at Avalonia.Controls.ApplicationLifetimes.ClassicDesktopStyleApplicationLifetime.ShowMainWindow()
   at Avalonia.Controls.ApplicationLifetimes.ClassicDesktopStyleApplicationLifetime.Start(String[] args)
   at Avalonia.ClassicDesktopStyleApplicationLifetimeExtensions.StartWithClassicDesktopLifetime(AppBuilder builder, String[] args, Action`1 lifetimeBuilder)
   at TestAvalonia.Program.Main(String[] args) in /Users/astromobilesolutions/Projects/TestAvalonia/TestAvalonia/Program.cs:line 14

To Reproduce

Create a new Avalonia project.
Add the following code:

<TextBlock FontSize="13" TextTrimming="CharacterEllipsis" Width="200" Text="abcdefghijklmnopqrstuvwxyza⚡bcd"/>

Expected behavior
App should not crash
Avalonia version
11.0.6-11.0.10
OS
macOS
Additional context
This is probably introduced in 11.0.6 since issue doesn't occur on version 11.0.5

Is any workaround of this issue?

Fixed in master


Add Mac OS path for SD card

FuP to https://github.com/mendersoftware/mender-docs/pull/1571

Quick review please @mzedel ? I can't merge until reviewed. :)

I think the tests failed due to infra / timeout.
@lluiscampos  Can I re-trigger test run somehow? Sorry I'm not too familiar with the CI setup.

@estenberg I re-ran the failed test job but it failed again... I suspect you need to rebase to include a fix for the tests...

Thanks @mzedel , rebased :crossed_fingers: