int64 don't work on 32-bit arch cpu. This fix compensates for int64 unavailability

For test decode "i9012914924e". In 32-bit php, where PHP_MAX_INT =<PHONE_NUMBER> this call:
Fatal error: Uncaught SandFox\Bencode\Exceptions\ParseErrorException: Invalid integer format or integer overflow: '9012914924' in /ww/src/SandFox/Bencode/Engine/Decoder.php:116
This fix help for it

Thanks for the input. Sorry but no. Float loses precision after 254 or so. If you want, you can work on a GMP based solution, then:

Please do a patch against 1.x branch, it is still supported
Make GMP optional (decode() should have ['useGMP' => true] option)

or you can leave it to me, I think I can find some time this week

BTW do you use bencode directly or through torrent-file?

GMP solution is released as 1.5.0 and 2.5.0. I'm closing this

BTW do you use bencode directly or through the torrent-file?

I used this to parse a torrent file.

or you can leave it to me, I think I can find some time this week

Of course, you'd better do it yourself.

@shamka ok. please try version 2.5.0


refactor tests

chore: remove canaries that came back
feat: add examples for pushing all golden examples into a single location in codegen-ui

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #443 (689c9b6) into main (a6c63cb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #443   +/-   ##
=======================================
  Coverage   93.52%   93.52%
=======================================
  Files          48       48
  Lines        1808     1808
  Branches      394      394
=======================================
  Hits         1691     1691
  Misses        113      113
  Partials        4        4

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 a6c63cb...689c9b6. Read the comment docs.

I'm going to close this for now, I'm not particularly happy w/ the dev experience of being unable to run a test:update target, but will leave the branch around for now.


github repository age

📋 Description

github
either the created on date itself, or something like "3 months" / "2 years"

🔗 Data
https://api.github.com/repos/{:owner}/{:repository} + .created_at
🎤 Motivation
this info isn't shown on github desktop by default and would be nice to show off the maturity of a project

@chris48s, if it's okay, I can take this. The only question is how we'd render the datetime. There are three ways I can come up with:
Prettified Human-Readable Format
Would look similar to these:

Pros:

Look pretty
Human-readable

Cons:

Ambiguous (5 months ago but when exactly?)
Would require to introduce another dependency to the codebase unless this kinda thing is enough

Standardized
Might be ISO-8601. Example:

Pros:

A little bit verbose
Cons:
Too much verbose if we are going to include time and timezone
There are other standards to think about. See this beautiful thing.

So, there are a couple of questions as well.

In two cases (and even more than two if we consider the other standards), should we create distinct services for that? If so:

Pretty badges would lay under /github/created-at/pretty/:username/:reponame.
What about the standardized ones? Should we (a) distinct each as /github/created-at/iso/:username/:reponame and /github/created-at/rfc/:username/:reponame and such or (b) use /github/created-at/standardized/:username/:reponame?format=rfc with format query parameter defaulting to iso?

Case (a) requires two different classes (maybe extending a base CreatedAtBase?) while case (b) can be done in a single class but requires query parameters, which must be documented. Documentation part for case (b) is easy anyway, OpenAPI spec already handles that, but case (a) seems more expressive than the other when you think about it.

Apart from @nektro's assertion "nice to show off the maturity of a project", in the current UI of Github, the only way to know exactly when a project started is to do these steps:
Step 1: Click the commit count on the project page.

Step 2: Click next until you reach the initial commit / until the big bang. If the commit count is several hundred, this is really painful.

Step 3: Hover over the prettified datetime on the initial commit to learn when you've started the project.

AFAIK, there's no other easier way (unless one curls to the API). So, this would really benefit the community.

New to the codebase so wasn't aware this was a thing. So, I take this as I can start working on a PR?


fix sonar scanning

@AsfaMumtaz Image is available for testing. docker pull stakater/workshop-excercise:SNAPSHOT-PR-45-ed40db7f


Timeline for next release

Is there a timeline for the next release?  The fastapi constraint is blocking upgrades to 1.6.1.

We are planning for 1.7.x release of mlserver early next quarter depending on priorities. For the time being there is an rc 1.6.2rc1 that contains the fastapi constraint fix.

Thank you @sakoush


Unable to get storage S3 bucket name in CDK via resource dependency

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14
Amplify CLI Version
7.4.5
What operating system are you using?
Mac
Amplify Categories
storage
Amplify Commands
publish
Describe the bug
I'm trying to resolve S3 bucket in custom CDK category using amplify storage resource dependency as described in https://docs.amplify.aws/cli/custom/cdk/#reference-amplify-environment-name.
Resolved bucket name appears hardcoded storagefilesBucketName.
Expected behavior
Bucket name would be resolved correctly.
Reproduction steps
    const amplifyResources: AmplifyDependentResourcesAttributes =
      AmplifyHelpers.addResourceDependency(
        this,
        amplifyResourceProps.category,
        amplifyResourceProps.resourceName,
        [{ category: "storage", resourceName: "files" }]
      );
    const bucketName = amplifyResources.storage.files.BucketName;
    const s3Bucket = s3.Bucket.fromBucketName(
      this,
      "Amplify S3 Uploads",
      bucketName
    );

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

amplify build custom
⠙ Building custom resources🛑 There was an error building the custom resources
🛑 Error: Invalid S3 bucket name (value: storagefilesBucketName)
Bucket name must only contain lowercase characters and the symbols, period (.) and dash (-) (offset: 12)
    at Function.validateBucketName (/Users/serega/work/maklerbot/amplify/backend/custom/cdk/node_modules/@aws-cdk/aws-s3/lib/bucket.ts:721:13)

Additional information
No response

@shishkin As mentioned in our docs, you'd get the bucket-name as a ref as described here - https://docs.amplify.aws/cli/custom/cdk/#reference-amplify-environment-name
Similar to something like this.
const myBuckeetName = cdk.Fn.ref(dependencies.storage.<resource-name>.Name)

Thanks @kaustavghosh06! That works. I must have missed the ref.


Tune scoring

split query and add scores?

look at old versions of fzf https://github.com/junegunn/fzf/tree/0.9.0/src


Developer Guide v2: Read data

This chapter covers topics about reading data from a cluster.
See tracking doc for more details.
Note: We might need to split this issue into two or three issues, as this chapter of the guide introduces some new content, and will require some new code samples.

Closing this out, as we will be tracking issues individually.


Testing circle ci pipeline

Testing PR.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.d.ra seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Disregard, was testing Circle CI branch wasn't showing up, thought if I created a PR it would show up.


Add Super100ShootingStarohmygodi'mexhausted closes #3315

:+1:

It's a real shame this author didn't just call it "Super Command Pods" on merging the two.


localforage not saving in iOS cordova Apps?

Hi
This isn't a bug but more like a question, after i played around with this library and try to implement it as a functionality to let a user autologin i need to set and store some information and then ask to the backend if this is ok and continue were the user left, but it seems that if i just remove the app from the background all the information is lost.
So my question is, every time i remove my app from the background i lose the data that was saved? or i'm just doing something wrong

localForage should work in iOS Cordova apps, so there is either a bug in localforage or a mistake elsewhere.
Would you be able to share the code that's acting up? Which version of iOS and localforage are you using?

tofumatt

On 18 Dec 2015, at 00:21, coicoronado<EMAIL_ADDRESS>wrote:
Hi
This isn't a bug but more like a question, after i played around with this library and try to implement it as a functionality to let a user autologin i need to set and store some information and then ask to the backend if this is ok and continue were the user left, but it seems that if i just remove the app from the background all the information is lost
So my question is, every time i remove my app from the background i lose the data that was saved? or i'm just doing something wrong
—
Reply to this email directly or view it on GitHub.

Hi Tofumatt and thanks for the respond
i was checking the issues that you have reported in the git repo about the
webpack thing, and after some attempt i concider another approach, which at
this momment is working correctly, so i think that i might stick to the
other approach mainly because the data is stored and reachable even when i
close the app completly, because when i reopen the app and try to get the
values stored in the localforage and even the length function always return
a null
If i have to return to use this lib i might contact you again
Thanks anyway
2015-12-18 5:03 GMT-06:00 tofumatt ☕<EMAIL_ADDRESS>
localForage should work in iOS Cordova apps, so there is either a bug in
localforage or a mistake elsewhere.
Would you be able to share the code that's acting up? Which version of iOS
and localforage are you using?

tofumatt

On 18 Dec 2015, at 00:21, coicoronado<EMAIL_ADDRESS>wrote:
Hi
This isn't a bug but more like a question, after i played around with
this library and try to implement it as a functionality to let a user
autologin i need to set and store some information and then ask to the
backend if this is ok and continue were the user left, but it seems that if
i just remove the app from the background all the information is lost
So my question is, every time i remove my app from the background i lose
the data that was saved? or i'm just doing something wrong
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/localForage/issues/490#issuecomment-165749234
.

--
"...los hombres fuertes se cuidan a si mismos; pero, los mas fuertes cuidan
a los demas..."

Hi @coicoronado. If you don't mind, can you let us what alternative approach you took to avoid loss of information by localforage?

Hey @judenaveenraj after some debug of this library the problem was that one of mu scripts was removing the data after i logout so as @tofumatt said it is working correctly.
Jus for the record the lib i was using is called localStorage but you can rely on the localforage library and the data stored will be there even if you dismissed the app from the background

the problem was that one of mu scripts was removing the data after i logout so as @tofumatt said it is working correctly.
Should we close this as invalid?

@thgreasi yes you can mark it as resolved


return germline mutations

hey sangjin. just putting this here. Some people like me hate deepvariant.

himut based germline mutation detection has lower performance than deepvariant though :(
I assume you would want a separate VCF file with germline mutations?


Design: Update components that have been integrated with the link component

gcds-link was integrated into the following components, ensure the updates have been made in Figma for the following components to maintain consistency:

[x] gcds-breadcrumbs
[x] gcds-card (won't do)
[x] gcds-footer (won't do)
[x] gcds-lang-toggle

@adorayi

Won't do card because card headline is it's own text property
Won't do footer because the those links are styled differently than our standard links

cc @melaniebmn for confirmation before closing.

Hey @realdylanzheng wanted to check in on why we can't use the link component in the footer. It uses the same colour and other styles that we are currently using for the footer from what I can tell.

Looking at the link component in Figma - it seems we are missing the "light" variant for the Figma component but it is present for the coded component. Can we update the Figma component to include this as well?
https://cds-snc.github.io/gcds-components/?path=/docs/components-link--overview#variants
@adorayi tagging you for visibility

@melaniebmn Good question regarding the light link variant. I wasn't part of the initial planning for the component, but there are a few differences of the light link (for footer) from our standard links:

Colour (not blue)
Interaction (underline only appears on hover)
which might suggest why the designers didn't want to offer the footer or light link for "normal" use and it is treated like a subcomponent unique to the footer.


Add setting for automatic rollover

As a workaround to mitigate the race condition introduced by the Templater plugin, I would suggest the possibility to disable the automatic rollover on file creation. This should fix the problem for most of the people in #105
What do you think @tim-hilt?

Fixes #103


num reg images / 正則化画像の数:0

Fast Kohya Trainer how to use “num reg images / 正則化画像の数” or how to set。

I'm sorry, I don't have any plans to continue the Fast Kohya Trainer project (for now).

The code is getting longer in one cell, and my device is not powerful enough to handle it, (I run most of things in small laptop), which is causing lag.

It's really hard to maintain the 1-click cell colab.

There is another good 1-click cell colab project maintained by HollowStrawBerry, which is integrated with Google Drive. It based on my notebook (?) so you may get the same experience, or even better. You can check it out here: https://github.com/hollowstrawberry/kohya-colab


Tested on

Device:
Firmware:
fastboot Version:
OS & Version:
What happened:

Device: Play X800i
Firmware: R800i_4.0.2.A.0.58_Enhanced.ftf & R800i_4.0.2.A.0.69_World.ftf
fastboot Version: 1:8.1.0+r23-5ubuntu2
OS & Version: Ubuntu 20.04.2 LTS
What happened: Was able to boot and operate device on both firmwares.


New publish plugin action DisplayAction

Is your feature request related to a problem? Please describe.
At the moment we are dealing with repair actions on instance or context level and those are defined in @classmethod in particular plugin. In some plugins for example in Nuke we want to help user to navigate within their complex node trees to see what node had failed. But we are not having abstraction for display action as we are having for repairing.
Describe the solution you'd like
New abstraction method could be created in openpype action for this. Labeled Show instance or Display in workfile or even shorter if possible.
[cuID:1z9xfu9]

Would Selecting the nodes be enough? I assume it can be hard to "frame"/"display" the relevant nodes in Nuke automatically as they might be far apart or they might be inside groups/containers and thus still not be apparent? I assume once nodes are selected then the user can frame or do whatever they are accustomed to do in the host to find the relevant nodes.
Another approach would be to allow a little pop-up Qt list widget like UI that lists all invalid nodes where the user could select each individually. However - it seems more involved to produce and less familiar to the artist with the host/tool they are working in.

Hey @BigRoy, I am not sure how this would work in Maya or Houdini so I will talk only about Nuke.
Since this will be more related show user the failed Instance. This want shown on Context in multiple instances.
Usually in the instance you are having only one node, but there are cases where for example whole backdrop full of nodes could be failing. Here we would frame in the node graph viewer only the whole backdrop node. So roughly if in the case of more failures, the user would need to display these one by one.

I will close this as I think this is already working per host/plugin - like many Maya plugins are using action "Show Invalid" that is doing I think exactly this, so I believe this is per host per plugin, unless I am mistaken.


Full network commissioning cluster support

Problem
Currently we only implemented 3 most urgent commands for network commissioning cluster. We need a full network commissioning cluster support which also makes use of full IM features.
Proposed Solution
<suggested fix, suggested enhancement>

@erjiaqing it seems that on accessory side we are missing handling some NetworkCommissioning commands like ScanNetworks, RemoveNetwork, DisableNetwork and GetLastNetworkCommissioningResult that are planned to be used on TE2. Are you working actively on any of that? I planned to try implement it (at least some of those starting from Scan), but I noticed that this issue exists and I thought that we should sync to avoid duplicating our work.

@erjiaqing it seems that on accessory side we are missing handling some NetworkCommissioning commands like ScanNetworks, RemoveNetwork, DisableNetwork and GetLastNetworkCommissioningResult that are planned to be used on TE2. Are you working actively on any of that? I planned to try implement it (at least some of those starting from Scan), but I noticed that this issue exists and I thought that we should sync to avoid duplicating our work.

I'm current enhancing the Add(WiFi|Thread)Network and EnableNetwork commands, and a pr is expected in very soon.
I'm not current working on Scan command.

As network commissioning contains a set of complex commands, the following issues need to be addressed before:

The CommandHandler should support async command handling. (https://github.com/project-chip/connectedhomeip/pull/8197 is trying to solve this)
The command payload should support complex types. (#2182, may require ZAP update)

As of Nov 21' the implementing of full network commissioning can continue. Based on current obersivations of the code.

The plan is to continue using DeviceNetworkProvisioningDelegate, with some changes

It will be renamed to DeviceNetworkCommissioningDelegate to match the name of network commissioning cluster
I'm going to add a timeout param as well as a callback (object) param to handle network commissioning related events, for each of the network operations (Scan, Connect(Join), Disconnect)
The network commissioning won't use DeviceNetworkProvisioningDelegateImpl, instead, DeviceNetworkProvisioningDelegate will be used as an interface
Basic compatibility will be provided by "DefaultDeviceNetworkCommissioningDelegate" before platforms implemented the new interface.
The full network commissiong PR will be presented with a Linux version of DeviceNetworkProvisioningDelegate.

Fixed, follow up: https://github.com/project-chip/connectedhomeip/issues/13170 (Platform driver)


Make a list of all the library branches in the lower mainlaind

BC211 dataset does not contain service records for library branches
Acceptance Criteria

[ ]  We have a list of all library branches in the lower mainland. For each branch, we have name, description, organization id (the org id of the corresponding municipal library organization), address, phone numbers, email, website address.
[ ] The library branches show up in the app when searching for services near me.
[ ] The data is in a formal that allows for simple import into our database, @rasmus-storjohann-PG and @ian-lin-PG to assist

Steps for QA:

Here's the list of Public Libraries in Lower Mainland to add as service records.

Review of Jean's libraries file:

Organizations

[ ] There are no organization entries, because all the organizations are already in BC211, I guess?

Services

[ ] id column is not populated

Locations: Look good
Addresses: Look good, location_id column populated
Phones look good
Service at location

[ ] service id is not populated

Taxonomy:

[ ] vocabulary is BC211, should be PeaceGeeks

Services taxonomy:

[ ] service id is not populated

This is done says Jean

The library data is now imported. OF the random samples I took, first entry of Bob Prittie Metrotown Branch shows up correctly in the app. The last entry West Vancouver Memorial Library is a duplicate. This is an edge case where Jean's data and Theresa's data overlap with a different service id. Then there's Ocean Park Branch which has no description.

The library data is now imported. OF the random samples I took, first entry of Bob Prittie Metrotown Branch shows up correctly in the app. The last entry West Vancouver Memorial Library is a duplicate. This is an edge case where Jean's data and Theresa's data overlap with a different service id. Then there's Ocean Park Branch which has no description.

West Vancouver Memorial Library is no longer a duplicate. Ocean Park Branch now also has service description. I duplicated Jean's Library csv and removed all the Y entries which prevents double entry with Theresa's dataset. I also duplicated the service description from the organization description for all the related services. So now there's no more empty description. PASS QA 1.59.0

West Vancouver Memorial Library is no longer a duplicate. Ocean Park Branch now also has service description. I duplicated Jean's Library csv and removed all the Y entries which prevents double entry with Theresa's dataset. I also duplicated the service description from the organization description for all the related services. So now there's no more empty description. PASS QA 1.59.0

Staging 1.62.0 - Spot checked 10 libraries in the list. They were all in the app.


Rarities stack

There should be an application stack for dealing with rarities, and they should be linked by foreign key in the database.
This'll allow for better management of the rarities, will also mean there is a controller to call when checking rarities, table class for doing finds by rarity, etc.
Blocks #1

Duplicates #2


Zero lai

Purpose
In the current codebase, setting the area indices of the plant to zero would result in a 0/0, because, for example, we have:
 d theta_leaf/dt = [stem_flux *LAI - canopy_transpiration]/ (LAI x Delta z), where canopy_transpiration involves a multiplication by LAI as well.
Because we cannot have a changing number of prognostic variables across the domain, even when there is no vegetation present, we need to have a canopy model with some prognostic variables, parameters, etc. To turn off the canopy, setting LAI = SAI = RAI = 0 will imply zero fluxes and zero root extraction, and no change in the initial conditions of the plant prognostic variables.
Therefore, update the codebase so that when LAI=SAI=RAI = 0, d theta/ dt = 0 and there is no divide by zero.
Once we get closer to global runs, we should do some refactoring as it makes sense to make it so you dont need to define all these parameters where there is no vegetation. See Issue #250.
Content

Change "LAI/(LAI x dz)" terms to "LAI/max(LAI x dz, eps(FT))". When LAI = 0, this gives zero flux and does not divide by zero.
Add consistency checks to the PlantHydraulics constructor:

if LAI == 0, all area indices should be zero (no plant present)
if LAI is nonzero, RAI must be nonzero (a plant cannot exist without roots)
if n_stem == 0, the stem area index must be zero for consistency.

Adds unit tests to make sure consistency checks pass and that when LAI =RAI = SAI = 0, the root extraction and transpiration are both zero.

Review checklist
I have:

followed the codebase contribution guide: https://clima.github.io/ClimateMachine.jl/latest/Contributing/
followed the style guide: https://clima.github.io/ClimateMachine.jl/latest/DevDocs/CodeStyle/
followed the documentation policy: https://github.com/CliMA/policies/wiki/Documentation-Policy
checked that this PR does not duplicate an open PR.

In the Content, I have included

relevant unit tests, and integration tests,
appropriate docstrings on all functions, structs, and modules, and included relevant documentation.

[X] I have read and checked the items on the review checklist.

Looks good! I had a few comments

ok! I addressed them all, I think. If the tests pass now, good to go?

bors r+


summarize_by_time engine

Created the new pattern for summarize_by_time that now incorporates the engine parameter where users will be able to select between pandas and polars.
If successful and we like the pattern we can now extend this across all current and future functions.

Received and I'll take a look soon. I like the engine argument. Great work!


Attempt #3 to fix "rowspan" tag

I added quotes around the number 3 in the rowspan tag

Q
A

content fix?
yes

New article?
no

What's in this Pull Request?
I added quotation marks around the #3. Even though this is appearing correctly in preview, it doesn't appear correctly on staging. The source code for the rowspan row gets messed up and looks like this, causing it to not render.
<td rowspan=3 style="font-weight:bold; vertical-align:middle; color:white; background-color:#d13438">themePrimary: #d13438
Expected (plus fix): themePrimary: #d13438

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/design/themes-colors.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.

@Lauragra
Fixed - yay! Third time's a charm. In the end, the culprit was that the rowspan string lacked quotes around the number: rowspan=3 needs to be rowspan="3".
This is now good to go live. :-)

Staged version: https://review.docs.microsoft.com/en-us/sharepoint/dev/design/themes-colors?branch=master


Allow putting modules that compile into the engine in a project's folder

Godot version:
3.1
Issue description:
For my own project, I've started making a few engine modules. These modules include a custom image format loader, an ingame visual scripting system, and a voxel model importer/resource system. I have looked into NativeScript already and find it inappropriate for these use cases for many reasons (including but not limited to: fiddly setup, difficulty generating Visual Studio solution files, missing support for many native engine types, access to external libraries I need that I would otherwise have to include 2 versions of, missing engine functions and utility classes, no direct ability to register new node types or engine classes without auto-attached scripts, slightly-too-different API, and missing engine memory management functions), so please don't bring up NativeScript. If I could do this sort of thing with scripts, I would have.
My game is called Marla Died Too, so I am currently happy enough creating my modules individually with the prefix "md_" (Marla Died) and putting them into my local engine repository. I have a computer built for recompiling Unreal Engine several times a week, so scons iteration time is not an issue (scons, being a fairly good build system, also only compiles files I changed most of the time anyway). However, it would be very useful if I could put these modules somewhere in my project directory, rather than the engine directory, and still have scons find them. Ideally, I would like to be able to run builds in my own project folder and generate a Visual Studio view that visually separates my own project's module files from the engine. Then, rather than having to work inside the engine folder and with a copy of the engine repository that I need to update myself, I can work in my own project's directory and not have to worry about it.
The build process would not change. scons would still recompile the engine around my modules, depending on the SCstub files they contained, exactly as it compiles modules now. All this would add is a much greater ability for those who work with projects that add engine code to organize their work. NativeScript users would not be affected.
If there's interest in this, I could potentially start developing a pull request that does this myself. If not, I will probably make something anyway for my own use. It seems like it would be an incredibly useful thing to support.

Supporting this, perhaps there should be implemented an easy way to specify a custom search path for modules within the scons build system.
What I currently do is simply symlink all my custom C++ modules into the engine/modules with a python build script, which also acts as a wrapper over scons.
Also see for #28343 for detailed discussion and pitfalls. I ended up moving it all away from project folder, so the structure looks like this now:

project being an actual Godot project, engine added as a submodule (using master branch myself so have to keep track of exact version used), and modules hold my git modules which are symlinked into engine/modules, then I just recompile it with build.py.
You'd also want to exclude symlinked modules from checked out engine submodule by adding excluding engine/modules folder locally, just add this to .git/modules/godot/info/exclude (or similar path):
modules/

This just avoids the git displaying the repository as "dirty".

I have looked into NativeScript already and find it inappropriate for these use cases for many reasons

I'm also kinda reluctant because of these reasons tbh, I'd just rather go straight to the source. 😅

@Xrayez this is pretty cool, I think I'm going to try and do the same thing with my setup for the moment.

Are you saying that a prebuilt version of Godot should keep scons inside it and then build your module somehow integrating it, or that you want to keep Godot as a "submodule" in your project and load engine modules from outside the engine folder then rebuild it?

Are you saying that a prebuilt version of Godot should keep scons inside it and then build your module somehow integrating it, or that you want to keep Godot as a "submodule" in your project and load engine modules from outside the engine folder then rebuild it?

Neither. This would be a feature just for people who have the engine source code on their machine as you (as far as I am aware) cannot build modules without it, but I was thinking it should not require godot and the project to be any specific places relative to each other (including godot as a submodule of your repository, I guess).
Just the ability to pass an arg to the normal scons files to add additional modules folders would work well. Ideally, however, godot (if you built it from source) would optionally generate an scons file inside your project's folder and put a second modules folder in there as well. Running scons from inside your project's folder would build the engine normally, but additionally consider any modules it finds in the project's folder. And, of course, the generate visual studio solution function would generate two projects, one that contains all the godot files and runs the original godot scons build script, and one that contains your own project and runs the extended scons build script that builds the engine with your modules added in.

Stumbled upon another use case.

There's a chance that scons would fail to work properly with an SCsub that isn't contained in a descendant directory from the main selected directory.

I've seen somewhere that SCons doesn't work with relative paths outside the build root, for the reasons of simplified and reliable multi-threaded builds AFAIK.

The way I would see something like this going though would be to let someone go to Project > Tools (or something) and create a tool option that generates/initializes local module code for the user.

It would be great if Godot could support C++ module generation out of the box. Actually I've written a python package for this. The complexity arises by having to conditionally generate some parts of a module generation which are specific to each Godot version...

There's a working WIP implementation #36883 which could help solve this. The only caveat is that the implementation doesn't assume any kind of module to be passed to game_module path, but rather as a general-purpose scons C++ package (the way I see it):
scons platform=windows tools=yes target=release_debug game_module=D:/packages/my_package -j8

which could then be made to build a collection of modules instead.
To be more concrete, you'll have to either explicitly list the modules in package's SCsub, or actually replicate the way current root Sconstruct collects modules:
# my_package/SCsub

Import('env')

module_env = env.Clone()
module_env.add_source_files(env.modules_sources, "*.cpp")

for module in your_module_list:
    env.modules_sources = []
    SConscript(module + "/SCsub") # compile each module individually
    lib = env_modules.add_library("module_%s" % module, env.modules_sources)
    env.Prepend(LIBS=[lib])

So in theory you could even write your own engine/framework with this as you can build your own hierarchical chain by calling SConscript, so yeah I think this should solve most uses cases.

I've implemented #36922 to specifically resolve this, as well, whatever works! 🙂

This is very nice. Thank you for your hard work!


message list: Dates on recipient headers don't update appropriately with #10820.

This is specific to changes introduced with #10820.
Using the thread 'chat.zulip.org' on #announce from czo as an example - the date text on the right hand side of the recipient bar shows the date of the earliest message fetched in the message view's current topic, but doesn't update to show the date of the message at the top of the message view's currently visible content.
To reproduce:

Go to any topic with messages sent more than a day apart so that a date separator can appear.
Scroll up in the message view to fetch earlier messages; observe the date on the recipient bar update to an earlier time.
Scroll down in the message view to more recent messages; the date on the recipient bar does not update.

For discussion, see https://chat.zulip.org/#narrow/stream/101-design/topic/date.20separators.
@zulipbot add "area: message view" "bug"

I'm going to close this and just point to in #10820, since it's not really an independent issue but more a bug in a not-yet-merge PR.

(Thanks for the detailed, helpful notes, though!)


[D3D9] Visual novel RE:D Cherish! doesn't launch when using DXVK

The game doesn't launch when I'm using DXVK, and I simply get some DXVK-related output in the console, nothing else, no window with the game in it or anything.
Software information
I installed DXVK in a clean Wine prefix (tried both 32 bit and 64 bit, same results, 64 bit in the log) using Winetricks. A download of the game's trial can be found here: http://crystalia.amusecraft.com/red/download.html#Trial
(The reason why I'm trying DXVK is because the game's FMVs don't play in default Wine, and it seems like wined3d might be a possible culprit.)
System information

GPU: RX 5700 XT
Driver: Mesa 22.3.3
Wine version: wine-8.0-rc4 (Staging)
DXVK version: 2.1

Apitrace file(s)
n/a, tried it but it just works like on default Wine if I follow this method, and the trace is just 4.4MB or so.
Log files

d3d9.log: d3d9.log

n/a, tried it but it just works like on default Wine if I follow this method, and the trace is just 4.4MB or so.

That is expected if it's with wined3d. Upload it here if you can 🙂

Added it.

Same issue as #3207, it's running the same engine.


Document render only renders the first child

The rendering fails with the following JSON documents.
On the the following document:
{
  "document": [
    {
      "type": "heading",
      "children": [
        {
          "text": "Wanna learn how to sysadmin?"
        }
      ],
      "level": 1
    },
    {
      "type": "paragraph",
      "children": [
        {
          "text": "Don't ask"
        },
        {
          "text": " me",
          "italic": true
        },
        {
          "text": "… ask "
        },
        {
          "text": "Filipe",
          "bold": true
        },
        {
          "text": "!"
        }
      ]
    },
    {
      "type": "paragraph",
      "children": [
        {
          "text": ""
        }
      ]
    }
  ]
}

The sentence
Don't ask
is rendered, missing the rest of the children.
It should be formatted as
Don't ask me ask Filipe!

Here is another document which does not render properly
{
  "document": [
    {
      "type": "paragraph",
      "children": [
        {
          "text": "Start text "
        },
        {
          "text": "bold text",
          "bold": true
        },
        {
          "text": " rest of the text \n"
        }
      ]
    },
    {
      "type": "paragraph",
      "children": [
        {
          "text": ""
        }
      ]
    }
  ]
}

Only the text
Start text
is rendered. While it should be rendered as
Start text bold text rest of the text

The issue has been fixed, pending release.


question mark in yaml list bug

Output of helm version: version.BuildInfo{Version:"v3.8.1", GitCommit:"5cb9af4b1b271d11d7a97a71df3ac337dd94ad37", GitTreeState:"clean", GoVersion:"go1.17.5"}
Output of kubectl version: Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5", GitCommit:"5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e", GitTreeState:"clean", BuildDate:"2021-12-16T08:38:33Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"21+", GitVersion:"v1.21.5-eks-bc4871b", GitCommit:"5236faf39f1b7a7dabea8df12726f25608131aa9", GitTreeState:"clean", BuildDate:"2021-10-29T23:32:16Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.): It does not matter
Hi, so apparently a question mark in a YAML list value crashes helm with: error converting YAML to JSON: yaml: line **: did not find expected ',' or ']'
How to replicate:
--- Chart.yaml ---
apiVersion: v2
name: helm-question-mark-bug
version: 111.111.102

--- values.yaml ---
command: ["$?"]
##### In my case it is some other command with a question mark
##### I tried to escape it with \ , \\ and ?? nothing helped

--- templates/pod.yaml ---
apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: null
  labels:
    run: bug
  name: bug
spec:
  containers:
  - image: alpine
    name: bug
    command: {{ .Values.command }}
    resources: {}
  dnsPolicy: ClusterFirst
  restartPolicy: Always
status: {}

Then try to template with:
helm template question-mark-bug ./

apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: null
  labels:
    run: bug
  name: bug
spec:
  containers:
  - image: alpine
    name: bug
    command:
{{ toYaml .Values.command | indent 6 }}
    resources: {}
  dnsPolicy: ClusterFirst
  restartPolicy: Always
status: {}

@yxxhero Hi, where can I find the helm docs of this function? I know it just calls the golang JSON marshal function after a brief look at the source code, but I can not find the helm docs about this one.

@nofearOnline

https://helm.sh/docs/chart_template_guide/function_list/
https://github.com/helm/helm-www/issues/1202

There are no docs for the toYaml function on this page, yet ;)
Thanks for reraising it there :)

@nofearOnline
yes. The doc require update. welcome to do it.


"read" not working correctly in scala JS

I have an experiment in which I'm attempting to use upickle to pass Json between client / server...
object Server extends cask.MainRoutes {

  @cask.get("/")
  def index() = {
    "Hello!"
  }

  @cask.postJson("/get-suggestions")
  def suggest(search: String, prefixOnly: Option[Boolean]= None) = {
    println("ummmm")
    write(MyResponse(Seq("apple", "pear", "orange", "strawberries", "orangutan")))
  }
}

object Protocol {
  object GetSuggestions {

    case class MyRequest(search: String, prefixOnly: Option[Boolean] = None)
    object MyRequest {
      //implicit val codec = io.circe.generic.semiauto.deriveCodec[MyRequest]
      implicit val codec2: ReadWriter[MyRequest] = macroRW[MyRequest]
    }

    case class MyResponse(suggestions: Seq[String])
    object MyResponse {
      //implicit val codec = io.circe.generic.semiauto.deriveCodec[MyResponse]
      implicit val codec2: ReadWriter[MyResponse] = macroRW[MyResponse]
    }
  }
}

    val arg: Future[Response[Either[String,String]]] = req.send()
    dom.console.log("made request")
    dom.console.log(arg)
    val uhOh: Future[Either[String,MyResponse]] = arg.map(_.body.map{
      b => dom.console.log("-->" + b);
      val test = Try(read[MyResponse](b))
      println(test)
      read[MyResponse](b)}
    )
dom.console.log("Exception thrown before this message")

[Log] -->"{\"suggestions\":[\"apple\",\"pear\",\"orange\",\"strawberries\",\"orangutan\"]}" (dev.js, line 15780)
[Log] Failure(upickle.core.AbortException: expected dictionary got string at index 0) (dev.js, line 56688)

As far as I can tell, pickle is correctly "writing" the json. However, it fails to re-parse it coming back the other way, in scala JS.
val Scala      = "2.13.5"
  lazy val shared = Def.settings(
    libraryDependencies += "com.softwaremill.sttp.client3" %%% "core" % "3.3.6",
    libraryDependencies += "com.lihaoyi" %%% "upickle" % "1.4.0"
  )

addSbtPlugin("org.scala-js"       % "sbt-scalajs"              % "1.6.0")

Would this be expected?

Okay, I take this back,
  @cask.postJson("/get-suggestions")
  def suggest(search: String, prefixOnly: Option[Boolean]= None) = {
    println("ummmm")
    write(MyResponse(Seq("apple", "pear", "orange", "strawberries", "orangutan")))
  }

Changing this to
  @cask.post("/get-suggestions")
  def suggest(request: cask.Request) = {

    val test = request.text()
    println(test)
    write(MyResponse(Seq("apple", "pear", "orange", "strawberries", "orangutan")))
  }

Actually fixes the problem. Which is weird as - it does not make any sense to me, how this could change the clientside behaviour... but hey ho


Add category named "Dependency Updates"

This section should contain all updates made by greenkeeper and filter them out of the list of commits for which a type should be selected.

Here's an example of such a PR.

Why wouldn't a type be selected? Depending on the dependency update wouldn't that affect the parent project in the traditional fashion? Either major, minor, or patch? (Most typically patch).

This won't be part of the core. But now that release supports hooks, this could be a plugin.


Support native crash reporting for Windows

Sentry SDK for Flutter supports Windows since it's preview versions: https://github.com/getsentry/sentry-dart/pull/407
Since then, Flutter has made Windows support GA: https://medium.com/flutter/announcing-flutter-for-windows-6979d0d01fed
But it does not capture a native crash. The goal is to use sentry-native with the crashpad backend to capture minidumps on Windows.
This was recently done on the Unity SDK:

https://github.com/getsentry/sentry-unity/issues/527

This tracking issue contains the items we would consider when adding support to Flutter. Including:

[ ] Offline caching on by default
[ ] Crash free rate to rely on the native layer (ask native: did I crash last run?)
[ ] Scope sync so data set to the SDK in Dart, shows up in native crashes
[ ] Make sure we can bundle crashpad_handler.exe with the final app
[ ] Upload symbols automatically during build. (might require changes to: https://github.com/getsentry/sentry-dart-plugin)

Related:

https://github.com/getsentry/sentry-dart/issues/433
https://github.com/getsentry/sentry-dart/issues/487
https://github.com/flutter/flutter/issues/108974

Consider this issue when tackling this.


Archive sawtooth-supply-chain

This repo hasn't seen meaningful commits in over a year and has open PRs that are a year old

This repo hasn't seen meaningful commits in over a year and has open PRs that are a year old

I edited the README to reflect this.

This LGTM, but I think we need to do a documentation pass to make sure we aren't linking here before we merge it.

The links won't break - github does magic redirects when you move a repo.


Project icon added to icons/scalable/mimetypes

Required by https://github.com/sugarlabs/sugar/pull/697

Hi @AbrahmAB, after you resized it, the stroke widths look very small compared to the star icon.  Can you change it to ensure visual continuity with the favourites icon (the one next to it in the journal)?

Done :)


[Gateway] Adding ETH to the wallet

Adds the incorrect contract address (the others are fine). Please double check all contract addresses on all networks.

@alvaro-ricotta can you please look into this issue, might a minor!


Fix C++/CLI build problem

This fixes a build problem when using btree_set with C++/CLI.
IMO it's also slightly better style.

ok upgraded

ok upgraded  all fix there problems

OK


Exclude docstrings from PYI053

Summary
The Y053 rule of flake8-pyi ignores docstrings, it only triggers on other string literals.
The separate Y021/PYI021 rule exists to disallow docstrings.
Test Plan
Added some # OK test cases to PYI053.py(i) files.

For some reason the "PR Check Comment" workflow keeps failing on my branch: https://github.com/astral-sh/ruff/actions/runs/5395179324/jobs/9797343880

All good, this seems correct to me, will merge tonight. Thanks!


64 test coverage

Added some more tests
Closes #64

I've added the closing keyword to this PR, as I believe the issue should be closed once this is merged.
The intention was to get some momentum on the testing, which this issue succeeds in.


change add to addperson in the UG

This affects many areas of the UG. Can i confirm that we have received confirmation that this change is allowed for 1.4? @Bandov

no longer doing this


how to get InceptionInference.java

question as the title!

@yony228 Sorry for the delay.
If you are still stuck, have a look at the comment https://github.com/thammegowda/tensorflow-grpc-java/issues/4#issuecomment-332998720
I am going to close this issue. If you are still working on it, please open it. I will be happy to help!


Improve docs

Description of what has changed

Issues addressed by pull request

This is not a quality change to the repository.


👷Data Builders: make DefaultFakeResolver open and stateless

Closes https://github.com/apollographql/apollo-kotlin/issues/4453

Converted to draft because we need an API to accomodate non-@typePolicy usages


Update Measure Qualifier Flag

Codecov Report

Merging #322 (bebc2db) into develop (1eae68e) will increase coverage by 1.18%.
Report is 3 commits behind head on develop.
The diff coverage is 78.72%.

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

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##           develop     #322      +/-   ##
===========================================
+ Coverage    53.47%   54.66%   +1.18%
===========================================
  Files           12       12
  Lines         2573     2625      +52
===========================================
+ Hits          1376     1435      +59
+ Misses        1197     1190       -7

Files Changed
Coverage Δ

R/ResultFlagsDependent.R
40.20% <0.00%> (ø)

R/GenerateRefTables.R
86.54% <91.89%> (+1.81%)
:arrow_up:

R/CensoredDataSuite.R
68.60% <100.00%> (+2.32%)
:arrow_up:

R/UnitConversions.R
90.58% <100.00%> (ø)

R/Utilities.R
86.44% <100.00%> (+1.53%)
:arrow_up:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Make SeeItSayIt Label's display the correct speech commands

Overview
Modified the Button Config to have the SeeItSayIt Label for buttons display the Speech Command by default

This feature helps track part 2 of the steps needed to be done here for speech: #9686
Changes

Fixes: #9781

/azp run

/azp run


Rultor release

As far as I understand, @rultro release is not installed in this project, if so this post might be useful

@l3r8yJ, I don't trust Rultor to release packages since I have to send my credentials to it. Therefore, I decided to release packages only using GitHub actions. Here's how it works:

I request Rultor to release the package
Rultor performs a simple build
Then Rultor publishes the release on GitHub (if build is successful)
Then the release pipeline (GitHub actions) takes over and begins the release process.

You can check it here.

@volodya-lombrozo maybe we can suggest a more private way of releasing for Rultor via issue, what do you think?

@l3r8yJ To be honest, I don't like the idea of building something inside Rultor at all, because Rultor obviously is not so powerful  comparing with GitHub actions. For example, using GitHub actions, we can check our build for many different platforms at once (windows, Mac, linux) rather than Rultor that uses only one selected platform (it's a Linux by default). I'm personally use Rultor as helpful assistant that can check a build one more time and can publish releases.
I've asked similar question here.
As for security - I just don't know how else we can guaranty security in that case (in any case you have to share your credentials with Rultor). But if you want, you can ask question or send an issue to Rultor repo. I believe it would be interesting to figure out.

@volodya-lombrozo understand you, it is really hard to make it more private with the sharing of credentials


Unable to compile any contracts

OS : Ubuntu 18.04 LTS
Node : v8.10.0
Npm : 3.5.2

$ npm list -g --depth 0
/usr/local/lib
+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>
Commands run
./aion.sh
titan init
titan unpack
titan compile -d path/to/contracts/Example.sol
Error

$ titan compile -d contracts/Example.sol
(node:23938) Error Plugin: @titan-suite/cli: files attribute must be specified in<EMAIL_ADDRESS>module<EMAIL_ADDRESS>plugin: @titan-suite/cli
root: /usr/local/lib/node_modules/@titan-suite/cli
See more details with DEBUG=*
(node:23938) Error Plugin: @oclif/plugin-help: files attribute must be specified in /usr/local/lib/node_modules/<EMAIL_ADDRESS>module<EMAIL_ADDRESS>plugin: @oclif/plugin-help
root: /usr/local/lib/node_modules/@titan-suite/cli/node_modules/@oclif/plugin-help
See more details with DEBUG=*

Error with debug

$ DEBUG=* titan compile -d contracts/Example.sol
@oclif/config reading core plugin /usr/local/lib/node_modules/@titan-suite/cli +0ms
@oclif/config loadJSON<EMAIL_ADDRESS>+0ms
@oclif/config loadJSON<EMAIL_ADDRESS>+2ms
(node:24495) Error Plugin: @titan-suite/cli: files attribute must be specified in<EMAIL_ADDRESS>module<EMAIL_ADDRESS>plugin: @titan-suite/cli
root: /usr/local/lib/node_modules/@titan-suite/cli
See more details with DEBUG=*
Error Plugin: @titan-suite/cli: files attribute must be specified in<EMAIL_ADDRESS>at Plugin.warn (/usr/local/lib/node_modules/@titan-suite/cli/node_modules/@oclif/config/lib/plugin.js:173:19)
at Plugin.load (/usr/local/lib/node_modules/@titan-suite/cli/node_modules/@oclif/config/lib/plugin.js:35:18)
at
module<EMAIL_ADDRESS>plugin: @titan-suite/cli
root: /usr/local/lib/node_modules/@titan-suite/cli
See more details with DEBUG=*
@oclif/config loadJSON<EMAIL_ADDRESS>+2ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+1ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+20ms
@oclif/config:@titan-suite/cli loading IDs from /usr/local/lib/node_modules/@titan-suite/cli/lib/commands +0ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+0ms
@oclif/config:@titan-suite/cli found commands [ 'compile',
'console',
'deploy',
'init',
'lint',
'test',
'unlock',
'unpack' ] +8ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+10ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+0ms
@oclif/config:@titan-suite/cli require<EMAIL_ADDRESS>+2ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+201ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+0ms
@oclif/config:@titan-suite/cli require<EMAIL_ADDRESS>+201ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+4ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+0ms
@oclif/config:@titan-suite/cli require<EMAIL_ADDRESS>+5ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+166ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+1ms
@oclif/config:@titan-suite/cli require<EMAIL_ADDRESS>+167ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+2ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+0ms
@oclif/config:@titan-suite/cli require<EMAIL_ADDRESS>+1ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+0ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+1ms
@oclif/config:@titan-suite/cli require<EMAIL_ADDRESS>+1ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+46ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+0ms
@oclif/config:@titan-suite/cli require<EMAIL_ADDRESS>+47ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+1ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+0ms
@oclif/config:@titan-suite/cli require<EMAIL_ADDRESS>+0ms
@oclif/config reading user plugins pjson<EMAIL_ADDRESS>+0ms
@oclif/config loadJSON<EMAIL_ADDRESS>+8ms
@oclif/config loading plugins [ '@oclif/plugin-help' ] +20ms
@oclif/config reading core plugin /usr/local/lib/node_modules/@titan-suite/cli/node_modules/@oclif/plugin-help +0ms
@oclif/config loadJSON /usr/local/lib/node_modules/<EMAIL_ADDRESS>+20ms
@oclif/config loadJSON /usr/local/lib/node_modules/<EMAIL_ADDRESS>+2ms
(node:24495) Error Plugin: @oclif/plugin-help: files attribute must be specified in /usr/local/lib/node_modules/<EMAIL_ADDRESS>module<EMAIL_ADDRESS>plugin: @oclif/plugin-help
root: /usr/local/lib/node_modules/@titan-suite/cli/node_modules/@oclif/plugin-help
See more details with DEBUG=*
Error Plugin: @oclif/plugin-help: files attribute must be specified in /usr/local/lib/node_modules/<EMAIL_ADDRESS>at Plugin.warn (/usr/local/lib/node_modules/@titan-suite/cli/node_modules/@oclif/config/lib/plugin.js:173:19)
at Plugin.load (/usr/local/lib/node_modules/@titan-suite/cli/node_modules/@oclif/config/lib/plugin.js:35:18)
at
module<EMAIL_ADDRESS>plugin: @oclif/plugin-help
root: /usr/local/lib/node_modules/@titan-suite/cli/node_modules/@oclif/plugin-help
See more details with DEBUG=*
@oclif/config:@oclif/plugin-help using manifest from /usr/local/lib/node_modules/<EMAIL_ADDRESS>+0ms
@oclif/config config done +3ms
@oclif/config start init hook +0ms
@oclif/config init hook done +1ms
titan init version<EMAIL_ADDRESS>argv: [ 'compile', '-d', 'contracts/Example.sol' ] +0ms
@oclif/config runCommand compile [ '-d', 'contracts/Example.sol' ] +8ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+11ms
@oclif/config loadJSONSync<EMAIL_ADDRESS>+0ms
@oclif/config:@titan-suite/cli require<EMAIL_ADDRESS>+42ms
@oclif/config start prerun hook +2ms
@oclif/config prerun hook done +0ms
titan:compile init version<EMAIL_ADDRESS>argv: [ '-d', 'contracts/Example.sol' ] +0ms

I have tried reinstalling Titan CLI and Aion node but it didn't help.

Hey, are you passing the correct path

Yes, I am. The only thing different from documentation of aion is that I am on Ubuntu bionic rather than xenial.

Are you able to deploy the contract?

The contacts didn't compile so I didn't try deploying. Build folder was empty after trying to compile.
Also, iirc, in the default aion config, rpc was disabled. Had to enable it.

Error Plugin: @titan-suite/cli: files attribute must be specified in<EMAIL_ADDRESS>This seems to be of interest. You might wanna focus on it first.

The build folder is created only after deploying. I've just tested the command on a fresh install on a new system without getting an error. What version of node and npm are you running?

The build folder is created only after deploying. I've just tested the command on a fresh install on a new system without getting an error. What version of node and npm are you running?

They are mentioned in the opening post. I'll try deploying and a few other things later today, and get back to you.
Meanwhile, why do you need aion node to be running for compilation and why are build files not generated on compilation?

Can you try updating npm to the latest and try again? You could test this in a docker container if you don't want to modify your global npm package.

Tried using node 10 with nvm but it didn't help. Then, I edited the package.json files that were throwing the error to add the files array as in this repo's package.json. It subdued all the errors but it still didn't compile the contracts. It was like nothing was happening when I tried compiling.

Meanwhile, why do you need aion node to be running for compilation and why are build files not generated on compilation?

AION uses Solidity version 0.4.9 and a fork of<EMAIL_ADDRESS>which used to compile using web3.eth.compile.solidity instead of solc. They are working on upgrading their library to be compatible with web3v1.0.

It subdued all the errors but it still didn't compile the contracts. It was like nothing was happening when I tried compiling

This is strange, let's take a different approach. Try cloning this repo, then

go into the cloned file
install the dependencies using yarn
copy your contract into the test/contracts folder
run ./bin/run compile -d test/contracts/YourContract.sol from the project root

Then let me know what happens

What does your contract look like?

https://github.com/titan-suite/cli/blob/master/test/contracts/Example.sol

I ran yarn test and all tests failed
titan$ yarn test
yarn run v1.9.4
$ titan test

  a] Compile and deploy
    1) should compile contract
    2) should deploy contract

  b] Test contract function
    3) should return 10

  0 passing (1s)
  3 failing

  1) a] Compile and deploy
       should compile contract:
     TypeError: Cannot read property 'info' of undefined
      at Context.it (test/testExample.js:28:19)
      at <anonymous>
      at process._tickDomainCallback (internal/process/next_tick.js:228:7)

  2) a] Compile and deploy
       should deploy contract:
     Error: the string "unlock fail" was thrown, throw an Error :)
      at <anonymous>
      at process._tickDomainCallback (internal/process/next_tick.js:228:7)

  3) b] Test contract function
       should return 10:
     TypeError: Cannot read property 'add' of undefined
      at Context.it (test/testExample.js:48:24)

error Command failed with exit code 255.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Have you been able to connect to your node and deploy contracts there through other means?

What happens when you do titan console or even ./bin/run console?

Could this be related to https://github.com/aionnetwork/aion/issues/628?

Seems like it is.

Have you tried it on 16.04?

Closing this due to inactivity.


Cannot find module 'cucumber'

Hi,
I've cloned this respository and am attempting to run the example cucumber tests, but am sadly getting this error message
Using the selenium server at http://localhost:4444/wd/hub
[launcher] Error: Cannot find module 'cucumber'

I've run npm install and the cucumber module has been pulled down. Is anyone else seeing this issue?
Edit: I am also seeing the same issue with Mocha.
Edit: Installing Cucumber globally seems stop the error message. Shouldn't protractor look in the local bin folder? Do they need to be specified in the package.json file?
Thanks

I am new to using cucumber with protractor and I am receiving the same error even after installing cucumber globally. Any idea what else I can try?


[AutoPR frontdoor/resource-manager] rename frontdoor to frontDoor in readme

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4013

(message created by the CI based on PR content)


Builtins create hidden dependency on Browserify version

I spent most of today teasing out why my webapp bundle was buggy only on my own system and not my co-worker's, with the same package.json and the same versions of everything in node_modules. Long story short: something depends on the builtin Buffer, and my (somewhat old, 8.x from January) copy of Browserify had a bugged version.
The rest of Browserify's dependency determination system is so explicit and obvious, it completely threw me for a loop to learn that a select set of objects (like Buffer) can be populated automatically with whatever happens to be in node_modules for Browserify's global installation.
I can see that this is for compatibility with modules written for node.js, but it's a huge gotcha for this invisible, undeclared dependency to exist between the Browserify version and dependencies of dependencies that one is likely unaware of.
Should builtins need explicit require statements and dependency entries in package.json?
P.S: For additional fun: Watchify brings its own version of Browserify with it (with the usual npm install watchify -g). If those copies get out of sync, then Browserify and Watchify can build bundles with different versions of the builtins.

Hi @PatrickKing. Are you saying that Browserify isn't a dependency in package.json and there were different, globally installed, versions on the 2 machines? In any case, Browserify, Watchify, and anything else should be dependencies of the project.
I didn't realize Watchify depends on Browserify -- I guess that's to support the CLI. Seems like a bad idea to me, actually.

Yes indeed, Browserify is globally installed on our systems, perhaps that's our mistake. Though, I'll point out that installing Browserify globally is what's done in the readme, I'm surely not the last person who'll follow that example.

@PatrickKing Ok, thanks for the feedback. I recommend having your project depend on whatever you need, including Browserify and Watchify, rather than use globally installed modules. It seems to me that there is a general shift toward doing that.

Though, I'll point out that installing Browserify globally is what's done in the readme, I'm surely not the last person who'll follow that example.

That's a great point. That's probably bad advice at this point. Personally I'm not a fan of using CLIs in general for libraries like Browserify, but the only suitable use case I can think of for using it as a globally installed CLI is for ad hoc operations -- tinkering essentially.
Just today Babel removed the preferGlobal flag for its CLI (though the docs haven't caught up yet).
I'm going to close the issue because that seems to be the crux of it. If after making those changes there's still a problem, please open a new issue with the details. I'm going to open a new issue about the README.
Thanks!


Weapon blur being applied to 3rd person view

Issue:    While playing the game, there is a feature that blurs the gun when in the zoomed mode. This is supposed to provide a field of view perspective to make it look more realistic. Apart from the fact that it is kind of finicky and only works sometimes, it is also applied when it shouldn't be.
When you are in the 3rd person camera angle and zoom in using the right mouse button, your character will be blurred. This looks awful and does not provide any benefits.
Proposed fix:
(1) Remove the applied blurring effect when in the 3rd person camera angle
or
(2) Disable the zoom feature while in 3rd person
or
(3) Have the zoom button change to first person and zoomed while the right mouse button is held down. This would provide the most functionality.
This is how the effect looks while in 1st person. (Actually boosts realism)

This is how the effect looks while in 3rd person. (Degrades view and looks bad)

I disabled that effect alltogether since it does not work well overall, for example if you zoom on the sky it will apply max blur since it is infinitely far away, the problem is much more about that and not the 3rd person thing.
This is also just supposed to be a template and therefore you cannot make it right for everyone, disabling that feature is not that hard.

Yeah, the DoF effect needs some updating, as Duion said for example, some of the default settings of it can go pretty oddball. It's largely designed with the default settings for first preson, but if someone wants it for third, it should probably at least handle it more gracefully than it does now with the default settings.

I only propose bugs that I plan on fixing. I just want to put them out here for experienced users to see if they agree and mark as a bug or a feature request. I don't think the  default template should have the blur. I was thinking maybe we would switch to a first person zoomed perspective when aiming in the 3rd person view. Thoughts?

I don't think there are any settings you could use to make this problem go away.
There is also no difference in first person or third person, the postFX just does what it does, you can see the weapon blurred in the first image as well.
PostFX are applied to the whole screen, they ignore what mode you are in, except you make a script to manually change the postFX in certain situations.

references for ya:
https://github.com/GarageGames/Torque3D/blob/development/Templates/Full/game/scripts/client/default.bind.cs#L451
https://github.com/GarageGames/Torque3D/blob/development/Templates/Full/game/scripts/client/default.bind.cs#L416-L418

@saxonschmauderer Mulling on it, I think a good approach would be to have the zoom-in not introduce the blur, but instead we either shift it to being a default post effect that's got a options menu setting to override on/off, or we have a demoscene that utilizes it so people know how to use it. But it seems a bit odd for the view to go all DoF-y JUST when zoom occurs.

It makes sense as a concept, since when you focus on something the rest becomes more unfocussed and you can have DoF activated when not zooming as well, it will just get overwritten on zoom.
The only problem I have with this postFX is that if you aim at the sky the blur goes to the max value since the sky is infinitely far away, this is the ugly part.
But this all has not much to do with the original issue, that is not so much of an issue, since that is just the way it is supposed to work, if you don't want it that way you need a different shader.


add error handling for using sqlsrv_query without sqltype

add error handling for using sqlsrv_query without sqltype in a column encryption enabled connection

Coverage increased (+0.4%) to 73.5% when pulling 6c5ef7ad9e1ba65ad2bdd3395a9cedccc20ad62b on v-kaywon:requireSqlTypeError into 5f7eb415a4d51049219e68b2766fa970e7a517b5 on Microsoft:AlwaysEncrypted.

Coverage decreased (-0.01%) to 73.111% when pulling d5a834631997b6c38c19dc88775cb8ca55c0e133 on v-kaywon:requireSqlTypeError into 5f7eb415a4d51049219e68b2766fa970e7a517b5 on Microsoft:AlwaysEncrypted.

Coverage decreased (-0.01%) to 73.111% when pulling e70ebbaba175139300020f99c177b0be4abd6b0d on v-kaywon:requireSqlTypeError into 5f7eb415a4d51049219e68b2766fa970e7a517b5 on Microsoft:AlwaysEncrypted.

Coverage decreased (-0.01%) to 73.111% when pulling c12585b77b3cda18eb531688a8e28e82a08ba675 on v-kaywon:requireSqlTypeError into 5f7eb415a4d51049219e68b2766fa970e7a517b5 on Microsoft:AlwaysEncrypted.


RAMSNAP diverging from RAMTRJ on error

When the exception is thrown, RAMTRJ recording is finalized and closed, however ramsnap file is not saved and it may result in divergence. Either the ramsnap file should also be stored, or the appropriate error message should be shown (instructing how to use the trajectory mode to fix the RAMSNAP file).

The best way to resolve it more generally is to validate coherence of all output data: RAMTRJ, XYZ recording, RAMSNAP and observable snapshots at the start of the simulation to ensure that none of them diverged.


Add column tasks.updated_at to tabs (and maybe also tasks:completed_at to response of API)

At the moment, from API there are two useful columns about tasks:

Key
Type
Description

tasks.created_at
datetime
Date and time of task creation.

tasks.updated_at
datetime
Date and time of last update to the task.

However, in tabs (views) there are possible columns tasks:created_at and tasks:completed_at:

Could you please add also column tasks.updated_at to tabs (and, maybe, tasks:completed_at to response of API for the sake of consistency)?
In my case, I need to get all tasks.updated_at from tasks without using heavy API to known which tasks were updated compared to the previous time, and at the moment I use this solution to get all tasks with some metadata. As luck would have it, this particular field is missing.

@makseq yes, update_at is datetime of last update to the task. The column completed_at gives the date-time only for the moment of creation of the new annotation, and when it is modified, this column does not change.

This feature was added in the latest develop branch.

@makseq Hi, How can i add that column??


Pretrained model checkoint

Hello!
Thanks for the amazing work and discovering the source code.
I would like to try the pre-trained model, but goodle drive says that the ckpt file has been moved to the trash and viewers cannot download it.
Could you please share the actual link to the pre-trained ckpt file?

Hi!
My bad. I accidentally deleted it.
I recovered it. You can download using the same link.

Thank you!


Optimize and Scale Redis Caching Layer for Backend

Describe the solution you'd like
Improve the caching mechanism for frequently accessed data (e.g., active ride requests, partner availability) to handle high throughput and low latency requirements.
Steps:

Review existing caching mechanisms and identify bottlenecks.
Implement caching strategies like LFU (Least Frequently Used) or LRU (Least Recently Used).
Conduct performance benchmarking and include metrics.

Can you assign this to me? I would like to contribute

hey @visheshrwl Can I take this issue


[Validators] Stake, Unstake

As a likecoin owner, I want to stake and unstake my LIKE to a validator, so that I can support this validator and earn rewards
Acceptance criteria

[ ] When unconnected, I click and trigger connect to wallet
[ ] I can stake/unstake a validator, decide the amount and sign for it
[ ] The To, From input is disabled in the modal
[ ] Click max and auto input my available LIKE amount

Design

Remarks
Let's ignore the success modal in the figma because we are using toast right now

Modal / logic for stake [3]
Modal / logic for unstake: need to query existing stake [3]


Why does it not have .setSwipeHorizontal just like .setSnapPages and .setNightMode?

I want the pdfviewer to swipe horizontal on the click of a switch. That is the user can change the mode to either vertical or horizontal. I can't seem to find a way to set that without having to load the input stream code again. Is there a way to work it out?

Not checked but i guess we can do it this way
if(sideways.ischecked()
{
pdfview.swipeHorizontal(true)
}
else
{
pdfview.swipeHorizontal(false)
}

Not checked but i guess we can do it this way
if(sideways.ischecked()
{
pdfview.swipeHorizontal(true)
}
else
{
pdfview.swipeHorizontal(false)
}

Hi, there's no such option.

in latest release this have
pdfView.fromAsset(String)
.pages(0, 2, 1, 3, 3, 3) // all pages are displayed by default
.enableSwipe(true) // allows to block changing pages using swipe
.swipeHorizontal(false)
.enableDoubletap(true)
.defaultPage(0)

in latest release this have pdfView.fromAsset(String) .pages(0, 2, 1, 3, 3, 3) // all pages are displayed by default .enableSwipe(true) // allows to block changing pages using swipe .swipeHorizontal(false) .enableDoubletap(true) .defaultPage(0)

Yes, It has that which I have used for the first load. After the pdf loads, I want a switch button to trigger vertical and horizontal modes as indicated in the screenshot. That's where it gets tricky because there's no option for pdfview.swipeHorizontal. It seems that for me to use that option, I have to load the pdf from stream again.
Please try it out and help me.


doc: reword documentation conventions

@danielsidhion just a drive-by rephrasing to make it a bit more compact
related: maybe we should add a template for where to put argument types?

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

related: maybe we should add a template for where to put argument types?

That could be helpful. Currently it's either unspecified or needs to be written in the explanation for the argument. I'll bring this up during the next meeting.


Support environments without access to the Internet

Hi,
we have our Jenkins server running in an environment without access to the internet. Would it be possible to have a version of the build monitor plugin that does not require internet access, but have all required resources bundled with the plugin?

Hi,
I have installed Jenkins and plugins on a machine that does not has internet access. Can you please tell me how can I use Jenkins without using Git ?


Make autosummary tables work

As recently discussed at length with @aphearin on slack, it turns out there's a bug in sphinx's autosummary that was causing many of the associated problems with the docs.  This PR addresses that by adding a small sphinx extension that just fixes the bug
The extension looks complex, but it's really just copied-and-pasted from sphinx, with the one change being on line 28: if not documenter.check_module() -> if documenter.options.members and not documenter.check_module().
This also fixes up phase_space_models_functions.rst to be compatible with the extension - other docs that are supposed to have autosummary tables will need to be switched to follow this form (or similar).
This also makes a few changes in the docs, most visible of which is the addition of a section for the Reference/API.  @aphearin, I can back that out if you don't want that in, but it might make sense given that this autosummary stuff is now linking directly to that.

@eteq - when I try to compile the docs locally for this PR, I get the traceback below. It traces to the line 33 reference in docs/autosummary_workaround.py to ModuleType, which is undefined.
Traceback (most recent call last):tools.empirical_models.AnalyticDensityProf   ror
File "", line 30, in
File "/usr/local/lib/python2.7/site-packages/sphinx/application.py", line 216, in build
self.builder.build_all()
File "/usr/local/lib/python2.7/site-packages/sphinx/builders/init.py", line 177, in build_all
self.build(None, summary='all source files', method='all')
File "/usr/local/lib/python2.7/site-packages/sphinx/builders/init.py", line 234, in build
purple, length):
File "/usr/local/lib/python2.7/site-packages/sphinx/builders/init.py", line 134, in status_iterator
for item in iterable:
File "/usr/local/lib/python2.7/site-packages/sphinx/environment.py", line 478, in update_generator
self.read_doc(docname, app=app)
File "/usr/local/lib/python2.7/site-packages/sphinx/environment.py", line 628, in read_doc
pub.publish()
File "/usr/local/lib/python2.7/site-packages/docutils/core.py", line 217, in publish
self.settings)
File "/usr/local/lib/python2.7/site-packages/docutils/readers/init.py", line 72, in read
self.parse()
File "/usr/local/lib/python2.7/site-packages/docutils/readers/init.py", line 78, in parse
self.parser.parse(self.input, document)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/init.py", line 172, in parse
self.statemachine.run(inputlines, document, inliner=self.inliner)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 170, in run
input_source=document['source'])
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
context, state, transitions)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
return method(match, context, next_state)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2726, in underline
self.section(title, source, style, lineno - 1, messages)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 327, in section
self.new_subsection(title, lineno, messages)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 395, in new_subsection
node=section_node, match_titles=True)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse
node=node, match_titles=match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run
results = StateMachineWS.run(self, input_lines, input_offset)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
context, state, transitions)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
return method(match, context, next_state)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2301, in explicit_markup
self.explicit_list(blank_finish)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2331, in explicit_list
match_titles=self.state_machine.match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 319, in nested_list_parse
node=node, match_titles=match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run
results = StateMachineWS.run(self, input_lines, input_offset)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
context, state, transitions)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
return method(match, context, next_state)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2604, in explicit_markup
nodelist, blank_finish = self.explicit_construct(match)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2311, in explicit_construct
return method(self, expmatch)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2054, in directive
directive_class, match, type_name, option_presets)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2103, in run_directive
result = directive_instance.run()
File "/usr/local/lib/python2.7/site-packages/sphinx/ext/autodoc.py", line 1437, in run
self.state.nested_parse(self.result, 0, node)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse
node=node, match_titles=match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run
results = StateMachineWS.run(self, input_lines, input_offset)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
context, state, transitions)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
return method(match, context, next_state)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2299, in explicit_markup
nodelist, blank_finish = self.explicit_construct(match)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2311, in explicit_construct
return method(self, expmatch)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2054, in directive
directive_class, match, type_name, option_presets)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2103, in run_directive
result = directive_instance.run()
File "/usr/local/lib/python2.7/site-packages/sphinx/domains/init.py", line 190, in run
return BaseDirective.run(self)
File "/Users/aphearin/work/repositories/python/halotools/astropy_helpers/astropy_helpers/sphinx/ext/numpydoc.py", line 185, in run
return base_directive.run(self)
File "/usr/local/lib/python2.7/site-packages/sphinx/directives/init.py", line 155, in run
self.state.nested_parse(self.content, self.content_offset, contentnode)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse
node=node, match_titles=match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run
results = StateMachineWS.run(self, input_lines, input_offset)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
context, state, transitions)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
return method(match, context, next_state)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2301, in explicit_markup
self.explicit_list(blank_finish)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2331, in explicit_list
match_titles=self.state_machine.match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 319, in nested_list_parse
node=node, match_titles=match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run
results = StateMachineWS.run(self, input_lines, input_offset)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
context, state, transitions)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
return method(match, context, next_state)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2604, in explicit_markup
nodelist, blank_finish = self.explicit_construct(match)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2311, in explicit_construct
return method(self, expmatch)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2054, in directive
directive_class, match, type_name, option_presets)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2103, in run_directive
result = directive_instance.run()
File "/usr/local/lib/python2.7/site-packages/sphinx/ext/autosummary/init.py", line 200, in run
items = self.get_items(names)
File "autosummary_workaround.py", line 33, in get_items
if not isinstance(obj, ModuleType):
NameError: global name 'ModuleType' is not defined
Sphinx Documentation subprocess failed with return code 1

I fixed this by changing it to types.ModuleType, but then I get an error with the traceback below. This traces to line 48:
if documenter.options.members

Evidently, documenter.options is a python dictionary that has no members attribute.
I'm going to stop tracing this now because something must be wrong since you said you were having no problems compiling the docs with your patch.
Traceback (most recent call last):tools.empirical_models.AnalyticDensityProf   ror
File "", line 30, in
File "/usr/local/lib/python2.7/site-packages/sphinx/application.py", line 216, in build
self.builder.build_all()
File "/usr/local/lib/python2.7/site-packages/sphinx/builders/init.py", line 177, in build_all
self.build(None, summary='all source files', method='all')
File "/usr/local/lib/python2.7/site-packages/sphinx/builders/init.py", line 234, in build
purple, length):
File "/usr/local/lib/python2.7/site-packages/sphinx/builders/init.py", line 134, in status_iterator
for item in iterable:
File "/usr/local/lib/python2.7/site-packages/sphinx/environment.py", line 478, in update_generator
self.read_doc(docname, app=app)
File "/usr/local/lib/python2.7/site-packages/sphinx/environment.py", line 628, in read_doc
pub.publish()
File "/usr/local/lib/python2.7/site-packages/docutils/core.py", line 217, in publish
self.settings)
File "/usr/local/lib/python2.7/site-packages/docutils/readers/init.py", line 72, in read
self.parse()
File "/usr/local/lib/python2.7/site-packages/docutils/readers/init.py", line 78, in parse
self.parser.parse(self.input, document)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/init.py", line 172, in parse
self.statemachine.run(inputlines, document, inliner=self.inliner)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 170, in run
input_source=document['source'])
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
context, state, transitions)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
return method(match, context, next_state)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2726, in underline
self.section(title, source, style, lineno - 1, messages)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 327, in section
self.new_subsection(title, lineno, messages)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 395, in new_subsection
node=section_node, match_titles=True)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse
node=node, match_titles=match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run
results = StateMachineWS.run(self, input_lines, input_offset)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
context, state, transitions)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
return method(match, context, next_state)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2301, in explicit_markup
self.explicit_list(blank_finish)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2331, in explicit_list
match_titles=self.state_machine.match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 319, in nested_list_parse
node=node, match_titles=match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run
results = StateMachineWS.run(self, input_lines, input_offset)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
context, state, transitions)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
return method(match, context, next_state)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2604, in explicit_markup
nodelist, blank_finish = self.explicit_construct(match)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2311, in explicit_construct
return method(self, expmatch)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2054, in directive
directive_class, match, type_name, option_presets)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2103, in run_directive
result = directive_instance.run()
File "/usr/local/lib/python2.7/site-packages/sphinx/ext/autodoc.py", line 1437, in run
self.state.nested_parse(self.result, 0, node)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse
node=node, match_titles=match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run
results = StateMachineWS.run(self, input_lines, input_offset)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
context, state, transitions)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
return method(match, context, next_state)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2299, in explicit_markup
nodelist, blank_finish = self.explicit_construct(match)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2311, in explicit_construct
return method(self, expmatch)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2054, in directive
directive_class, match, type_name, option_presets)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2103, in run_directive
result = directive_instance.run()
File "/usr/local/lib/python2.7/site-packages/sphinx/domains/init.py", line 190, in run
return BaseDirective.run(self)
File "/Users/aphearin/work/repositories/python/halotools/astropy_helpers/astropy_helpers/sphinx/ext/numpydoc.py", line 185, in run
return base_directive.run(self)
File "/usr/local/lib/python2.7/site-packages/sphinx/directives/init.py", line 155, in run
self.state.nested_parse(self.content, self.content_offset, contentnode)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse
node=node, match_titles=match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run
results = StateMachineWS.run(self, input_lines, input_offset)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
context, state, transitions)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
return method(match, context, next_state)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2301, in explicit_markup
self.explicit_list(blank_finish)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2331, in explicit_list
match_titles=self.state_machine.match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 319, in nested_list_parse
node=node, match_titles=match_titles)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run
results = StateMachineWS.run(self, input_lines, input_offset)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run
context, state, transitions)
File "/usr/local/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line
return method(match, context, next_state)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2604, in explicit_markup
nodelist, blank_finish = self.explicit_construct(match)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2311, in explicit_construct
return method(self, expmatch)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2054, in directive
directive_class, match, type_name, option_presets)
File "/usr/local/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2103, in run_directive
result = directive_instance.run()
File "/usr/local/lib/python2.7/site-packages/sphinx/ext/autosummary/init.py", line 200, in run
items = self.get_items(names)
File "autosummary_workaround.py", line 49, in get_items
if documenter.options.members and not documenter.check_module():
AttributeError: 'dict' object has no attribute 'members'
Sphinx Documentation subprocess failed with return code 1

@aphearin That's really weird. What version of sphinx are you on?  The way this hooks into autosummary it probably won't work on versions much older than the one it's designed for (1.3.1, also what RTD is on ...).
If that's the problem it's probably best to just set a minimum version for sphinx (which is a one-liner and I can add to this if that's what's going on)

My comment was irrelevant and due to using an out-of-date version of sphinx. About to merge.

Added a version check so people don't run into @aphearin's problem again.  And merging!


Vulnerability roundup 96: sympa-6.2.56: 1 advisory [7.8]

search, files

[ ] CVE-2020-26880 CVSSv3=7.8 (nixos-20.03, nixos-20.09, nixos-unstable)

Scanned versions: nixos-20.03: fbd345dd005; nixos-20.09: d105075a1fd; nixos-unstable: 34ad166a830.
Cc @mmilata
Cc @sorki

Thank you. I've subscribed to upstream issue and will follow-up when they release a fix.

Can't 100% say I understand what's going on but the NixOS module for Sympa does not use any setuid wrappers so this can probably be marked false positive? See also #90995.

Double checked that this is the case and I agree that this doesn't affect us.


Inconsistency in SCIM2 outbound provisioning(Dumb mode)

Suggested Labels
Affected: 5.8.0-alpha2
Severity: Major
Priority: High
Component: SCIM2/Outbound Provisioning
Type-Bug
Steps to reproduce

Configure outbound provisioning using SCIM
Enable dumb mode
Start another IS instance running on a different port (SCIM inbound provisioning enabled)
Use SCIM 2.0 rest API to create a new user/group

Actual Behavior
When using SCIM API to provision users/group it works fine (entity is not created in the local user store.). However, when using SCIM 2.0 rest API the entity is created in both user stores.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


naarad.config() exception with Zopkio 0.2.0

Hello,
I recently upgraded Zopkio from 0.16 to 0.2.0. And in the runtime I encounter the following exception. It seems api for naarad.config() has changed. Can you please clarify the impact of this change and what is the expected usage of naarad.config()?
"
Traceback (most recent call last):
File "/usr/local/bin/zopkio", line 9, in
load_entry_point('zopkio==0.2.0', 'console_scripts', 'zopkio')()
File "/Library/Python/2.7/site-packages/zopkio/main.py", line 148, in main
test_runner.run()
File "/Library/Python/2.7/site-packages/zopkio/test_runner.py", line 126, in run
config.naarad_id = naarad_obj.signal_start(self.dynamic_config_module.naarad_config())
TypeError: naarad_config() takes at least 1 argument (0 given)"
Thanks,
Chuong

Hi, sorry for breaking backwards compatability, I will implement a fix and support both no arguments and 1 argument in the next micro version (hopefully by EOD friday at latest). The reason for this change was to simplify the new api by removing the passed in mapping. This is because instead of using the passed in dictionary, the same configs can be accessed using runtime.get_active_config(config_option, default=None).

this issue should be fixed in 0.2.1, please reopen if a new issue arises

Hi Joshua,
Thank you so much for delivering resolution so quick.
Best Regards
Chuong


Fixes #11241 problems of using openssl x509 -req self sign certificate

the problem is illustrated in issue #11241

The Travis "red cross" seems relevant.
Also please can you supply a CLA:
https://www.openssl.org/policies/cla.html

@zk3326312 You need to make doc-nits after making changes to docs

I think the options newly added to x509 command should be sm2-id instead of sm2_id

Furthermore, I think the initial commit's title is too long and there is not message body in it - but we can resolve this when the PR gets merged by anyone who is doing the squash job.

Close/reopen to kick CLA bot.

FYI, I'm having a closer look at this.  I'm still convinced that the use of -sigopts must be enough to set the SM2 id during signature, but something fails when I try that, so I'm trying to figure out what.

I see where this PR is coming from...  we have the same kind of SM2 hackery all over the place already.  I have some ideas on how to make it...  a little less hacky.  PR coming up!

I see where this PR is coming from... we have the same kind of SM2 hackery all over the place already. I have some ideas on how to make it... a little less hacky. PR coming up!

Any update on this?

Any update on this?

So far, an issue where I've written down my analysis of the actual problem, #11293.  I'll follow up with a PR shortly.

@william-zk, thank you for this PR. I can understand if it felt like a waste, but considering how it helped highlight problematic code, I see it as highly valuable, even if we didn't use it directly.

@william-zk, thank you for this PR. I can understand if it felt like a waste, but considering how it helped highlight problematic code, I see it as highly valuable, even if we didn't use it directly.

oh, that's all right:-), I'd very happy to see that there is a more effective way to solve the problem. Later I'd help to find if there is any problem in openssl x509 ca...，if problem exist, I would make a issue and help to fix it