fix allocate reduplicated volumeId to different volume

What problem are we solving?
when using HashicorpRaft， it may allocate a reduplicated volume ID to new volume just after restarting masters， the volume ID had been allocated to others。
when master restarts, it does these jobs:

restore snap
select leader , after this step, if leader master gets a growing request, the nextMaxVolumeId may be the old one in the raft log
sync raft log
apply log

How are we solving the problem?
when the master became the leader， using raft.Barrier() to wait for all applying logs to be done, then began to serve leader service.
How is the PR tested?
grow volume after restarting the masters.
Checks

[ ] I have added unit tests if possible.
[ ] I will add related wiki document changes and link to this PR after merging.

@kungf Let's separate PR, separate fixed conditions and separate changes to update raft peers? Since this can lead to problems in some extreme cases.

@kungf Let's separate PR, separate fixed conditions and separate changes to update raft peers? Since this can lead to problems in some extreme cases.

ok

hi @kmlebedev  update.
Because only one place can receive the leader change event, so I have to monitor the leader change event in the place update raft peer.

Since this can lead to problems in some extreme cases.
which problems can it have?

hi @kmlebedev @chrislusf, I need some review, please.


Add Xcode 10.0 support ?

Hi @peterprokop
Like #47 do you plan a quick update for the new Xcode 10.0
Thanks

Hi @ep372 !
Yes, will update shortly. Most likely today or tomorrow.

Hi @ep372 !
Please check 5.0.1: https://github.com/peterprokop/SwiftOverlays/releases/tag/5.0.1


Dev test: Collision Lab 1.1.0-dev.13

@ariel-phet, @arouinfar, collision-lab/1.1.0-dev.13 is ready for dev testing. Document issues in https://github.com/phetsims/collision-lab/issues and link to this
issue.
Assigning @ariel-phet for prioritization.

General Dev Test

What to Test

Click every single button.
If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Try to include browser version numbers
If there is a console available, check for errors and include them in the Problem Description.
Run through the string tests on at least one platform, especially if it is about to go to rc.
Check the Game Up harness on one platform.

General Dev Test Platforms

[x] Latest macOS, Chrome and Safari
[x] Latest iOS, Safari
[x] Windows 10, all browsers (IE dropped)
[x] Latest Chrome OS, Chrome

Issues to Verify

[x] Tunneling ball in 1D collisions
[x] User reported issue: collide ball outside of reflecting border
[x] Input calculator does not clear when switched or reset
[x] Collision can push ball out of reflecting border
[x] Balls can overlap when adding additional ball
[x] Layering on balls/velocity arrow is not reset
[x] Buffering between toolbox and reset all button
[x] Balls may still have velocity if they read 0
[x] Unable to step back inelastic collisions looks buggy

These issues should have either use the labels "status:ready-for-qa" or "status:ready-for-review." If it is ready for
QA then close the issue if fixed. If ready for review then leave open and assign back to the developer.

Link(s)

Simulation

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

@KatieWoe since this sim has been through several dev tests, the main focus should be on verifying the issues noted above and then doing some checking that no new bugs have been introduced related to those fixes. However, I do not think this dev test needs to be as extensive as an "initial" test of the sim as we would like to move this towards publication. So after verifying issues, an hour or two test per platform should be more than sufficient.

@KatieWoe since this sim has been through several dev tests, the main focus should be on verifying the issues noted above and then doing some checking that no new bugs have been introduced related to those fixes. However, I do not think this dev test needs to be as extensive as an "initial" test of the sim as we would like to move this towards publication. So after verifying issues, an hour or two test per platform should be more than sufficient.

QA is done

QA is done

Thank you!

Thank you!


can compile successfully, but can't be executed.

Hi , I try to run your work , but it occurs some questions, as followings:

E tensorflow/core/common_runtime/executor.cc:643] Executor failed to create kernel. Invalid argument: NodeDef mentions attr 'dilations' not in Op<name=Conv2D; signature=input:T, filter:T -> output:T; attr=T:type,allowed=[DT_HALF, DT_FLOAT]; attr=strides:list(int); attr=use_cudnn_on_gpu:bool,default=true; attr=padding:string,allowed=["SAME", "VALID"]; attr=data_format:string,default="NHWC",allowed=["NHWC", "NCHW"]>; NodeDef: model/encoder/Conv/Conv2D = Conv2D[T=DT_FLOAT, data_format="NHWC", dilations=[1, 1, 1, 1], padding="VALID", strides=[1, 1, 1, 1], use_cudnn_on_gpu=true, device="/job:localhost/replica:0/task:0/device:GPU:0"](model/encoder/Pad, model/encoder/Conv/weights). (Check whether your GraphDef-interpreting binary is up to date with your GraphDef-generating binary.).
[[Node: model/encoder/Conv/Conv2D = Conv2D[T=DT_FLOAT, data_format="NHWC", dilations=[1, 1, 1, 1], padding="VALID", strides=[1, 1, 1, 1], use_cudnn_on_gpu=true, device="/job:localhost/replica:0/task:0/device:GPU:0"](model/encoder/Pad, model/encoder/Conv/weights)]]
2018-10-16 15:55:45.548550: F /home/dyh/work/code/monodepth-cpp/src/monodepth.cpp:166] Non-OK-status: session->Run(input, {output_name}, {}, &depth_ ) status: Invalid argument: NodeDef mentions attr 'dilations' not in Op<name=Conv2D; signature=input:T, filter:T -> output:T; attr=T:type,allowed=[DT_HALF, DT_FLOAT]; attr=strides:list(int); attr=use_cudnn_on_gpu:bool,default=true; attr=padding:string,allowed=["SAME", "VALID"]; attr=data_format:string,default="NHWC",allowed=["NHWC", "NCHW"]>; NodeDef: model/encoder/Conv/Conv2D = Conv2D[T=DT_FLOAT, data_format="NHWC", dilations=[1, 1, 1, 1], padding="VALID", strides=[1, 1, 1, 1], use_cudnn_on_gpu=true, _device="/job:localhost/replica:0/task:0/device:GPU:0"](model/encoder/Pad, model/encoder/Conv/weights). (Check whether your GraphDef-interpreting binary is up to date with your GraphDef-generating binary.).
[[Node: model/encoder/Conv/Conv2D = Conv2D[T=DT_FLOAT, data_format="NHWC", dilations=[1, 1, 1, 1], padding="VALID", strides=[1, 1, 1, 1], use_cudnn_on_gpu=true, _device="/job:localhost/replica:0/task:0/device:GPU:0"](model/encoder/Pad, model/encoder/Conv/weights)]]
Aborted (core dumped)

Besides , I want to ask what modifications have been done in  mrharicot/monodepth to make sure the frozen graph， could you share your experience ?  thank you !

look forward to your answers.
Best wishes ！

Hi, I have uploaded the monodepth.py file in the freeze_graph folder. Check it out and see if the file helps.

Thank you, I have solved it.


[yugabyte/yugabyte-db#16905] Fix metrics regex

This PR modifies the regex to use the partition id instead of just tablet id which we further use to scrape Debezium metrics for Prometheus.

Have you manually tested it?

Yes, I pushed a latest change which changed the label from id to partition - now we are good. I have tested it manually and verified the metrics.
We will require some changes in yugabyte/cdc-examples but that would be a separate PR there.


chore(demo): unify demo style

Issue
Unify demo style.

Coverage remained the same at 93.729% when pulling b9988c125e15fc0c482160736c6fc320ff9d3e74 on jongmoon:3.2.0-rc into 4aa518acfbc7bbb78391c6a18e6d68a9981a611a on naver:3.2.0-rc.


If does not use the Z axis in gesture recognition ,  can i  delete the hand_ landmark_ 3d.tflite  used to  reduce the model

MediaPipe Solution (you are using)
gesture recognition
Programming language
java
Are you willing to contribute it
None
Describe the feature and the current behaviour/state
If does not use the Z axis in gesture recognition ,  can i  delete the hand_ landmark_ 3d.tflite  used to  reduce the model

Will this change the current API? How?
No response
Who will benefit with this feature?
No response
Please specify the use cases for this feature
NO

Any Other info
No response

@chensisi0730,
Would you please elaborate your query with complete details such the platform you are using Python, Android, C++ or Other solution available in mediapipe to understand the issue better from our end. Thank you!

@kuaashish
Android ，thanks

@chensisi0730,
You will not be able to modify the internal graph depends on hand_landmark_3d.tflite.
Removing landmarks from the results will not prevent the overhead within the solution.
The binarypb contains the graph that tells the solution what to do. If that binarypb were modified (it's in proto3 format) and the nodes that compute these outputs were removed, the overhead would no longer exist. I'm sure you could figure this out, but we don't support this at this time. We have been experimenting with dynamically disabling sections of the graph based on options, and this might be a reasonable optimization. we will bring this up to the team, but I can't offer you a solution at this time.


WIP: ENH: Update external Eigen from release 3.4 to master

WIP: This update shows the same issues reported #2314, where the
history is polluted. Do not merge. Opened to see CI results, and to show
an example for that issue.

Test is passing. The failure in Windows is unrelated, it was failing for other PR's as well.

Thanks @phcerdan but would it still be an option to use a tagged revision of Eigen? Looks like 3.4.1 is quite a recent version: https://gitlab.com/libeigen/eigen/-/commits/3.4.1

Good spotting @N-Dekker, it would good to discuss what we prefer, this 3.4.1 branch or a commit from master.
We could discuss this in the open issue: #3546

@jcfr may have suggestions on how to make the mangling name configurable

@jcfr happy to hear suggestions for making the mangling name configurable. If you can provide a link to some existing CMake project with the options, I can copy it here.
This PR introduces a BOOL variable ITK_EIGEN_MANGLE, and if that's defined, we mangle with #define Eigen itkeigen (this is a header-only library). I kept the same approach than VTK (they mangle with vtkeigen).

re: mangling

See this relevant comment:

https://github.com/InsightSoftwareConsortium/ITK/pull/4102#issue-1794560793

Associated discussion for generalizing the support currently specific to Slicer[^1][^2] is discussed in https://discourse.itk.org/t/adding-support-for-customizing-itk-namespace/5170
[^2]: https://github.com/Slicer/ITK/commit/69e52f05c482012b95228c3fe46f299b1735ca99 (COMP: Add support for customizing ITK namespace (draft))

This PR introduces a BOOL variable ITK_EIGEN_MANGLE

I am not sure we want a CMake option to control this as we will always want the function name to be mangled if building against the version bundled in ITK.

I am not sure we want a CMake option to control this as we will always want the function name to be mangled if building against the version bundled in ITK.

Not mangling Eigen was proposed to facilitate external ITK modules (see ITKTotalVariation for example) using third-party libraries (libproxTV) that use Eigen to not having to fork the proxTV library and replace all Eigen references with itkeigen, or having to setup a new Eigen for that external module.
Eigen is so common in C++ ecosystem that it seemed a good helper for external modules.
However, I understand mangling is better for the general case, and we should turn it ON by default. But I would appreciate if we keep the option to turn it off, to reuse the internal Eigen on those external modules that use it.

https://github.com/Slicer/ITK/commit/69e52f05c482012b95228c3fe46f299b1735ca99 (COMP: Add support for customizing ITK namespace (draft)) ↩

Thanks for the links, amazing work!
As a side note and different topic, I think we have to keep all those changes of mangling to third party code in our own fork of the third-party, instead of handling them in ITK history. We should have an ITK/HDF5 fork and a branch with those changes on top.
We share the same tech with VTK to update-from-stream, but we don't seem to comply with their preconditions. Changes to third-party code should be handled in a third-party-fork, not in ITK (as you correctly do in Slicer/ITK). We face git history pollution, and merge conflicts because of it (see #2314).

I suggest to split this pull request and contribute the support for disabling the mangling of the Eigen include directory into its own pull request.

Not mangling Eigen was proposed to facilitate external ITK modules (see ITKTotalVariation for example) using third-party libraries (libproxTV) that use Eigen to not having to fork the proxTV library and replace all Eigen references with itkeigen, or having to setup a new Eigen for that external module.

I indeed remember the time we worked on this together. If I recall it is available at https://github.com/phcerdan/proxTV/commits/use_eigen

@phcerdan and I reviewed this pull request and concluded that updating Eigen without adding extra logic for namespacing was a sensible first step.
Approach for supporting including multiple Eigen "header only" library in one project will be evaluated and discussed later.

Tested against current ITKTotalVariation external module, which uses the internal ITK eigen, and all green.

@jcfr Review/merge?

This is ready, all @jcfr suggestions have been integrated (thanks!)


Sir  give me this project

Please 🙏🥺 sir

I don't understand what you want. You may use this project as long as you abide by the MIT license.


How to select multiple Base64 Images

Hello,
How can i make Base64 Image chooser can select and insert multiple image?

You can't for now :/
This needs some dev to support multiple insert. Multiple select is easy, but insert is more tricky.

Hello,
I create my own plugin to insert multip. I hope this help
base64multiple.zip

Hello,
I create my own plugin to insert multiple base64 image. I hope this help
base64multiple.zip

Are there any updates on this ?


Don't error on failure to delete aws account

What does this PR do?

Don't error on failure to delete a test. Deleting an AWS account that doesn't exist now returns a 400 response from Datadog, previously this returned a 2xx.
Since the test class' After method assumes the uniqueAWSAccount (from the Before) was created, it tries to delete this account after each test execution. This no longer returns 2xx for the cleanup of a unit test.
Additional Notes

Review checklist
Please check relevant items below:

[ ] This PR includes all newly recorded cassettes for any modified tests.

[ ] This PR does not rely on API client schema changes.

[ ] The CI should be fully passing.

[ ] Or, this PR relies on API schema changes and this is a Draft PR that includes tests.

Note: CI shouldn't be run on this Draft PR, as its expected to fail without the corresponding schema changes.

/azp run

/azp run


chore: Changes the text box for autocomplete query predicate as multiline text input

SUMMARY
Changes the textbox for autocomplete query predicate as multiline text input.
Closes https://github.com/apache/superset/issues/16100
@junlincc
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
https://user-images.githubusercontent.com/70410625/128563593-2a9151c9-cee9-4ce6-b1cd-dfa539b99620.mov
https://user-images.githubusercontent.com/70410625/128563631-b4249e18-4c30-4bd6-a6b2-c02241515b4d.mov
TESTING INSTRUCTIONS
Check the videos for instructions.
ADDITIONAL INFORMATION

[x] Has associated issue:
[x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

Duplicate of https://github.com/apache/superset/pull/16160


Weird default tolerance in testing function

This default rtol of 1e8 strikes me as odd.
https://github.com/JuliaMolSim/AtomsCalculators.jl/blob/2ab874239ae5b08843c7dd5e938d6ccb8f5c8e0d/src/submodules/Testing.jl#L31
I have not read through the full mechanics, but I'd expect something <1, so I suspect it's a typo and 1e-8 is meant.

good catch. And it should probably be sqrt(precision)

Thanks for notising this.
The reason for the correct value 1e-8 is that only very special methods have accuracy more than 8 significant numbers. So there should be no need smaller tolerance in practive.
On the other hand there can be issues with multithreading and even different implementations of calculators for different calls (forces vs energy_forces etc.) that cause small variations. So, it is better to have relatively loose tolerance here.


Move discriminated field to constructor.

This is necessary even when there is only one value to have it used as part of the equals function
Closes #216

👍

:+1:


[release/v1.2] Relaxed container runtime versions

What this PR does / why we need it:
Relaxed container runtime versions on control-plane and static-workers nodes
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Relaxed container runtime versions on control-plane and static-workers nodes

/lgtm

/retest

/hold

/lgtm


Markdown example

Description
Adds a markdown example using jdown which converts a directory of markdown files into JSON in the build stage so that the JSON can be used to populate content on the site with route data.
Changes/Tasks

[x] Added jdown as a dependency
[x] Populated basic example with posts and page content in markdown
[x] Updated example readme with real world example and mention of markdown
[x] Removed axios as it's no longer needed to pull the example content in

Motivation and Context

I couldn't find a good way (in my opinion) to use React Static with using simple markdown files for content, so I created one.
Types of changes

[ ] Refactoring/add tests (refactoring or adding test which isn't a fix or add a feature)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] My changes have tests around them

Are you using the the new rebuildRoutes feature to hot reload the markdown data when it changes?

I've now added hot reloading of the markdown content using rebuildRoutes!

Just needs to pass tests now!

👌Fixed that pesky bracket spacing and builds passing 💪


.next crashes music

Using .next twice in a row makes the music module crash, with the playback stopping and commands like .stop and .play returning no response; although in the console they appear as being executed correctly and show no errors. Other commands apparently work but the bot remains silent until using .destroy.

yeah same problem 1.55.3 version

screenshot

This problem is present in version 1.55-1.55.3 of the bot


Misleading error message when extending type parameter

🔎 Search Terms
"statically known members."
"could be instantiated with a different subtype of constraint 'object'."
🕗 Version & Regression Information

This changed between versions 3.6.2 and 3.7.5

⏯ Playground Link
https://www.typescriptlang.org/play?ts=3.7.5#code/JYOwLgpgTgZghgYwgAgKIA84FsAOAbCAHgBVkJ1IQATAZ2QHsAjAKwgTAD4yKJq7SA3gF8AUEA
💻 Code
interface Example<T extends object> extends T {}

🙁 Actual behavior
I get the following message:

Interface 'Example' incorrectly extends interface 'T'.
'Example' is assignable to the constraint of type 'T', but 'T' could be instantiated with a different subtype of constraint 'object'.

This error message is misleading. The interface does not vary with T and since it declares no new members, is completely compatible with T.
🙂 Expected behavior
I expect a descriptive message. Prior to 3.6.2, the error message was more helpful:

An interface can only extend an object type or intersection of object types with statically known members.

This is still the error you get if the type variable T does not have the extends constraint.
Additional information about the issue
No response

Relatedly, you can't extend other type expressions that aren't type identifiers or instantiations of generics, and the error message is similarly dense: #31843


chore: bump zeebe version

Updates default version to 0.23.4 in preparation for release :+1:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign npepinpe
You can assign the PR to them by writing /assign @npepinpe in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/not-ok-to-test
Is that the command? The release is still building

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Zelldon
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Zelldon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


runtime: execLock might deadlock on darwin/ios

If you run
GOEXPERIMENT=staticlockranking go test strings

on a Mac, it fails badly, because the preemptM can be called while holding various locks that conflict with execLock.rlock, specifically this part:
// On Darwin, don't try to preempt threads during exec.
// Issue #41702.
if GOOS == "darwin" || GOOS == "ios" {
	execLock.rlock()
}

This is indicative of a real potential deadlock on macOS and iOS, though not one that seems to have been reported yet. So probably it's very rare if it can happen at all. Unclear how to fix that.
/cc @aclements

The lock is only held while calling syscall.Exec, which is very rare.  And the amount of time for a potential deadlock is very very short.

We could probably change the code so that instead of acquiring the lock in preemptM we just check whether we are currently in syscall.Exec.  If we are, we could just skip the preemption signal.  Most likely the process is going away anyhow.  If it doesn't go away, we will presumably get another chance at preempting the thread.

I just modeled rwmutex more thoroughly in https://go.dev/cl/555055, which may be why this is showing up just now. Plus we don't have a darwin staticlockrank builder.


flutter: Fix linux-x64-profile/linux-x64-flutter-gtk artifact hash

Description of changes
This fixes a broken Flutter engine artifact hash that was accidentally used in #201027.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

i hope this is an one off and they don't make it a habit to forcepush artifacts.

They didn't - I used the wrong hash by mistake. The artifact in question hasn't been updated since it was added on April 7.

For some reason it was in nixpkgs cache, therefore it just pulled there without fetching it. Don't ask me how it got there.

isn't this just a case of https://nixos.org/manual/nixpkgs/stable/#id-<IP_ADDRESS> ?

Yes. It might have been in cache because of a previous flutter version using it.


Django 1.8 support

The following error is produced when running vagrant up after changing the requirements file to specify
Django==1.8.2
wagtail==1.0b2

==> default:   Applying home.0002_create_homepage...
==> default: Traceback (most recent call last):
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/db/models/query.py", line 405, in get_or_create
==> default:     return self.get(**lookup), False
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/db/models/query.py", line 334, in get
==> default:     self.model._meta.object_name
==> default: __fake__.DoesNotExist: ContentType matching query does not exist.
==> default:
==> default: During handling of the above exception, another exception occurred:
==> default:
==> default: Traceback (most recent call last):
==> default:   File "/vagrant/manage.py", line 10, in <module>
==> default:     execute_from_command_line(sys.argv)
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/core/management/__init__.py", line 338, in execute_from_command_line
==> default:     utility.execute()
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/core/management/__init__.py", line 330, in execute
==> default:     self.fetch_command(subcommand).run_from_argv(self.argv)
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/core/management/base.py", line 390, in run_from_argv
==> default:     self.execute(*args, **cmd_options)
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/core/management/base.py", line 441, in execute
==> default:     output = self.handle(*args, **options)
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/core/management/commands/migrate.py", line 221, in handle
==> default:     executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/db/migrations/executor.py", line 110, in migrate
==> default:     self.apply_migration(states[migration], migration, fake=fake, fake_initial=fake_initial)
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/db/migrations/executor.py", line 147, in apply_migration
==> default:     state = migration.apply(state, schema_editor)
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/db/migrations/migration.py", line 115, in apply
==> default:     operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/db/migrations/operations/special.py", line 183, in database_forwards
==> default:     self.code(from_state.apps, schema_editor)
==> default:   File "/vagrant/wagtailproj/home/migrations/0002_create_homepage.py", line 19, in create_homepage
==> default:     model='homepage', app_label='home', defaults={'name': 'Homepage'})
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/db/models/manager.py", line 127, in manager_method
==> default:     return getattr(self.get_queryset(), name)(*args, **kwargs)
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/db/models/query.py", line 407, in get_or_create
==> default:     return self._create_object_from_params(lookup, params)
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/db/models/query.py", line 439, in _create_object_from_params
==> default:     obj = self.create(**params)
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/db/models/query.py", line 346, in create
==> default:     obj = self.model(**kwargs)
==> default:   File "/home/vagrant/.virtualenvs/wagtailproj/lib/python3.4/site-packages/django/db/models/base.py", line 480, in __init__
==> default:     raise TypeError("'%s' is an invalid keyword argument for this function" % list(kwargs)[0])
==> default: TypeError: 'name' is an invalid keyword argument for this function

I have the same issue (even outside the vagrant box). Could this be a wagtail issue?

This happens because one of the Django built-in models (contenttype, IIRC) has had its definition changed in Django 1.8 to remove the 'name' field - the migration will need to be updated accordingly.

I'll rebuild the cookiecutter on top of the builtin template once it's merged (this supports Django 1.8).
https://github.com/torchbox/wagtail/pull/1109

FYI, https://github.com/torchbox/wagtail/pull/1109 has been merged.
For existing projects, edit home.0002_create_homepage and remove the name parameter in ContentType.objects.get_or_create().

Django 1.8 support added into 2.5.0


Add CODE_OF_CONDUCT and REPORTING_GUIDELINES markdown files to the root

Add CODE_OF_CONDUCT and REPORTING_GUIDELINES to the root folder of this project.
This is important for having a source of truth about our documentation.
Here's examples you can copy:

CoC: https://github.com/anitab-org/anitab-org.github.io/blob/develop/docs/code_of_conduct.md
Reporting Guidelines: https://github.com/anitab-org/anitab-org.github.io/blob/develop/docs/reporting_guidelines.md

Can i work on this


Questionable translation results from neural engine using example data

Hello,
I have built this application from source (master) and created a phrase based engine using the following:
$ ./mmt create en it examples/data/train
This yields the expected results according to the documentation:
$ ./mmt translate --context computer "hello world"

ModernMT Translate command line
>> Context: ibm 98%, europarl 2%

>> hello mondo

However, when creating a neural engine using the following:
$ ./mmt create en it examples/data/train --neural
translation results are quite different:
ModernMT Translate command line
>> Context: ibm 98%, europarl 2%

>> cavato del seminario

Do I have something configured incorrectly, or is this the expected result given the neural engine and training data size? A different result for neural vs. phrase based isn't mentioned in the documentation so I have to question if what I'm seeing is correct.
I followed the installation instructions to the letter and everything appeared to build and run without problems. This is a fresh install of Ubuntu 16.04 and an NVIDIA GTX 1080 for CUDA. Please let me know if there's any other information or logging files I can provide.
Thanks!

A statistical model can be more accurate than a neural one on a very short sentence not really in the main kind of formulations of the training data. Perhaps, try with a longer sentence, choosing it more according to the domains of the training data.

Hi @jogleasonjr
following your advice I've updated the README.md including a note that explains the differences between the two cases. Short version is: your engine is perfectly ok! For Neural engines, 6000 lines of training date are simply not enough for being able to learn actual translations.
This is the paragraph I've added to the readme file:
Note: the following quickstart example is run with a phrase-based engine for practical reasons. Neural training and Phrase-based training are two deeply different processes and if, for phrase-based engines, it is possible to achieve decent quality (under certain conditions) even with tiny datesets, Neural engines require more data and much more time in order to achive good performance.

I would suggest to prepare a  "example/train/data" for the neural engine, maybe augmenting the data or reducing the dictionary; We could add this benchmark to the one for PB, or replace it. This way, the trained engine will produce reasonable translation.

Hi, I guess one of the IWSLT benchmarks would perfectly work.

On 02 Dec 2017, at 12:42, Nicola Bertoldi<EMAIL_ADDRESS>wrote:
I would suggest to prepare a "example/train/data" for the neural engine, maybe augmenting the data or reducing the dictionary; We could add this benchmark to the one for PB, or replace it. This way, the trained engine will produce reasonable translation.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/ModernMT/MMT/issues/315#issuecomment-348686572, or mute the thread https://github.com/notifications/unsubscribe-auth/ABFS-lJ80ReyJmy_Hz3d0lUpmGEul3oNks5s8TetgaJpZM4Qy6sH.

I think we would need a benchmark on which the training takes only few (tens) of seconds.
Nicola

On 02 Dec 2017, at 14:18, Marcello Federico<EMAIL_ADDRESS>wrote:
Hi, I guess one of the IWSLT benchmarks would perfectly work.

On 02 Dec 2017, at 12:42, Nicola Bertoldi<EMAIL_ADDRESS>wrote:
I would suggest to prepare a "example/train/data" for the neural engine, maybe augmenting the data or reducing the dictionary; We could add this benchmark to the one for PB, or replace it. This way, the trained engine will produce reasonable translation.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/ModernMT/MMT/issues/315#issuecomment-348686572, or mute the thread https://github.com/notifications/unsubscribe-auth/ABFS-lJ80ReyJmy_Hz3d0lUpmGEul3oNks5s8TetgaJpZM4Qy6sH.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/ModernMT/MMT/issues/315#issuecomment-348691513, or mute the thread https://github.com/notifications/unsubscribe-auth/ABDaXIZf7OhR1seu_tqrQQ1-UCrbPEEOks5s8U4RgaJpZM4Qy6sH.

Thank you @davidecaroselli, good to know my engine is running correctly. I'll play around with larger training sets. Case closed!


App cannot be started: unhandled error event

Hi there,
Tried to download, install and start the app. Unfortuently theres an error at the startup
saying there is an unhandled 'error' event. During the installation the bower installation
didn't work proper. There had to be an choice be selected for angular-version.
$node server/
Hunts Point POS
Server started
events.js:154
throw er; // Unhandled 'error' event
^
Error: listen EACCES <IP_ADDRESS>:80
at Object.exports._errnoException (util.js:856:11)
at exports._exceptionWithHostPort (util.js:879:20)
at Server._listen2 (net.js:1218:19)
at listen (net.js:1267:10)
at Server.listen (net.js:1363:5)
at EventEmitter.listen (/Users/ak/Downloads/hunts-point-pos/node_modules/express/lib/application.js:617:24)
at Object. (/Users/ak/Downloads/hunts-point-pos/server/index.js:3:16)
at Module._compile (module.js:413:34)
at Object.Module._extensions..js (module.js:422:10)
at Module.load (module.js:357:32)

Error: listen EACCES <IP_ADDRESS>:80

This means that you need sudo/admin priviliges on your machine to run it on port 80. You will need to start with sudo on linux

@ehnydeel : all taken care of? Or are you still having issues?

ey afaqurk thanks for you help. i ran the application two times. so there was the error. issue closed. cheers


Make Elementary test tables as temp tables

Is your feature request related to a problem? Please describe.
Once elementary is set up in a DBT repository for Snowflake as the underlying Data warehouse. After running the tests there are tables getting created in the elementary schema and as long as the number of tests increases, the tables also increase and might blow up space for unwanted tables.
Describe the solution you'd like
These tables can be made temporary and should drop once the session is complete
Additional context

Would you be willing to contribute this feature?
I would like to contribute, But my availability is minimum given the bandwidth is less for me. But would love to check how to contribute for the same

I'm closing https://github.com/elementary-data/elementary/issues/979 as this feature seems to resolve it. Just wondering if there are any updated on this request?

Hi @Dineshvrma, @leilafi !
From now on Elementary's temporary test tables will automatically be deleted.
This change will be released in the upcoming version.
Thanks a lot for opening the issue.


extra-bindings has gone

Assuming this charm is a rewrite of https://charmhub.io/prometheus-openstack-exporter, the previously supported extra-bindings (https://git.launchpad.net/charm-prometheus-openstack-exporter/tree/src/metadata.yaml#n30) has gone without any commit history.
There were reasons to have such metadata especially this charm handles OpenStack with admin/internal/public endpoints.
This is a blocker to use the new charm since it doesn't cover the existing deployment scenarios, i.e. complex enterprise networking where a routing from admin network to public network is not allowed.

This is an expected bundle when extra-bindings are supported. This means that a created LXD container will have legs to each network including OAM (to forward logs and metrics to COS), internal network to fetch the keystone credentials over a relation, and public network to poke the OpenStack API endpoint. Otherwise, the underlying network requires some special routing to allow traffic from OAM to the public network, which is unlikely to be done in enterprise env.
  openstack-exporter:
    bindings:
      ? ''
      : oam-space
      cos-agent: oam-space
      credentials: internal-space
      public: public-space
    charm: openstack-exporter
    num_units: 1
    series: jammy
    to:
    - lxd:3

Technically this charm isn't a rewrite of https://charmhub.io/prometheus-openstack-exporter but rather a port of https://charmhub.io/openstack-exporter-k8s to a machine operator; this bug report is however equally valid, so I've introduced the bindings in #91


Probe awareness

I haven't run as much testing against this as I would like, but I figured I would submit so that you could get an early start on reviewing the changes.. Interested in your thoughts on the behavioral changes.. Agree/Disagree? etc..

Reviewed changes.


Fail to compile peer_connection example

Hi vsimon
I've been trying to compile, adding dependancies that are missing from the wiki page on how to compile peer_connection, and I've come to the following error compiling with gcc
/usr/bin/ld: /home/usr/Documents/webrtcbuilds/out/webrtcbuilds-26473-fa89d84-linux-x64/lib/Release/libwebrtc_full.a(psnr.o): undefined reference to symbol 'log10@@GLIBC_2.2.5'
/lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line
to which i have no idea how to handle.
Compiling with g++ gives several undefined references to webrtc:: and json:: also.

I think you should use Clang instead of g++


docs: update install instructions

Some Azure CLI command cleanup and update Helm chart installation instructions to use a values.override.yaml file as some may run into inconsistent results using yq to modify values.yaml file in place.

LGTM. Thanks a lot for the clean up!


Bugfix: wrong virial overdensity

Closes #1067

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 10 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.001%) to 97.582%

Totals

Change from base Build<PHONE_NUMBER>:
0.001%

Covered Lines:
5328

Relevant Lines:
5460

💛  - Coveralls


Kubernetes basics and links

Gather content/links for added info on Kubernetes, current mentioned in ECS Alternatives and Lock-in

Peeking under the hood of Kubernetes on AWS
Five Months of Kubernetes on AWS discussion where author shows up
Running Kubernetes on AWS EC2
Deploying Kubernetes on CoreOS to AWS with comments on currency of the content
Deploying Kubernetes to AWS using Jenkins with a comment on physical/Kubernetes/OpenStack/Kubernetes "sandwich" not exactly germane to AWS directly, but interesting in terms of stack composition
batch-optimized scaling manager for Kubernetes on ec2
Kubernetes The Hard Way
Kubernetes Bootcamp
How to deploy secure, auditable, and reproducible Kubernetes clusters on AWS

If this expands, it should probably go under or next to https://github.com/open-guides/og-aws#containers-and-aws and be linked from https://github.com/open-guides/og-aws#ecs-alternatives-and-lock-in


Allowing lane change can cause collision in bottleneck environment

This is a:

[x] Question
[ ] Feature request
[ ] Bug report

Describe the issue
I want to allow cars to change lanes in the bottleneck scenario.
I have adjusted the lane change mode several times (1621, 256 and others). However, if the inflow outnumbers 1700veh/h, there will have collisions in the experiment. I wonder if there exists a collision avoidance method for lane changing?

Which SUMO version are you at? Newer ones tend to have better collision avoidance implementation. LMK if the following helps:
# SUMO dependencies
apt-get install -y \
    cmake \
    build-essential \
    swig \
    libgdal-dev \
    libxerces-c-dev \
    libproj-dev \
    libfox-1.6-dev \
    libxml2-dev \
    libxslt1-dev \
    openjdk-8-jdk

# SUMO
cd ~ && \
    git clone --recursive https://github.com/eclipse/sumo.git && \
    cd sumo && \
    git checkout cbe5b73 && \
    mkdir build/cmake-build && \
    cd build/cmake-build && \
    cmake ../.. && \
    make

And use lane change mode of 0b011001010101 and speed mode of 0b11111.

@fywu85 Thank you for your help. My Sumo version is v0_31_0-812-g1d4338a. I will try the above method and I will let you know if it works. By the way, would you please have a look at another question at issue #454?

@fywu85  I followed the shell code you given above. In the last sentence 'make', error happens.
'user@user--Super-Server:~/sumo/build/cmake-build$ make
[  3%] Built target utils_gui_windows
[  3%] Built target foreign_phemlight
[  3%] Built target foreign_tcpip
[  3%] Built target generate-version-h
[  3%] Building CXX object src/gui/CMakeFiles/gui.dir/GUIViewTraffic.cpp.o
In file included from /home/user/sumo/src/gui/GUIViewTraffic.cpp:29:0:
/home/user/sumo/src/utils/gui/div/GUIVideoEncoder.h: In constructor ‘GUIVideoEncoder::GUIVideoEncoder(const char*, int, int, double)’:
/home/user/sumo/src/utils/gui/div/GUIVideoEncoder.h:131:36: error: ‘AV_CODEC_ID_HEVC’ was not declared in this scope
if (pCodecCtx->codec_id == AV_CODEC_ID_HEVC) {
^
/home/user/sumo/src/utils/gui/div/GUIVideoEncoder.h:148:34: error: ‘av_frame_alloc’ was not declared in this scope
myFrame = av_frame_alloc();
^
/home/user/sumo/src/utils/gui/div/GUIVideoEncoder.h: In destructor ‘GUIVideoEncoder::~GUIVideoEncoder()’:
/home/user/sumo/src/utils/gui/div/GUIVideoEncoder.h:169:17: error: ‘AV_CODEC_CAP_DELAY’ was not declared in this scope
AV_CODEC_CAP_DELAY)) {
^
/home/user/sumo/src/utils/gui/div/GUIVideoEncoder.h:178:31: error: ‘av_frame_free’ was not declared in this scope
av_frame_free(NULL);
^
/home/user/sumo/src/utils/gui/div/GUIVideoEncoder.h:198:39: error: ‘av_frame_free’ was not declared in this scope
av_frame_free(&myFrame);
^
In file included from /home/user/sumo/src/libsumo/Helper.h:27:0,
from /home/user/sumo/src/microsim/MSLane.h:45,
from /home/user/sumo/src/guisim/GUILane.h:31,
from /home/user/sumo/src/gui/GUIViewTraffic.cpp:38:
/home/user/sumo/src/libsumo/Subscription.h: At global scope:
/home/user/sumo/src/libsumo/Subscription.h:120:22: warning: unused parameter ‘refID’ [-Wunused-parameter]
virtual void setContext(const std::string& refID) {}
^
make[2]: *** [src/gui/CMakeFiles/gui.dir/GUIViewTraffic.cpp.o] error 1
make[1]: *** [src/gui/CMakeFiles/gui.dir/all] error 2
make: *** [all] error 2
'

Hi @CYBruce, with lane changing mode 1621, you do get lane changes but they should be extremely infrequent and the experiment should not crash as a result of the crashes. Are you getting that the experiment is crashing?

@eugenevinitsky Yes, I notice that when the inflow rate is more than 1700veh/h, there will be a crash. Could there be other reasons?

Could you log the error? That shouldn't happen.

Sure. Thank you for the help. I changed some places in the example bottlenecks.py.
The sumo report
'''
Loading configuration... done.
***Starting server on port 40756 ***
Loading net-file from '/home/user/flow/flow/core/kernel/scenario/debug/cfg/bay_bridge_toll_20190323-1338041553319484.7853382.net.xml'... done (1ms).
Loading additional-files from '/home/user/flow/flow/core/kernel/scenario/debug/cfg/bay_bridge_toll_20190323-1338041553319484.7853382.add.xml'... done (7ms).
Loading done.
Simulation started with time: 0.00
Warning: Teleporting vehicle 'flow_0.183'; collision with vehicle 'flow_0.186', lane=':4_0_2', gap=-1.00, time=431.00 stage=move.
Simulation ended at time: 432.00
'''
the terminal report
'''
/home/user/flow/flow/utils/flow_warnings.py:20: UserWarning: The attribute vehsPerHour in InFlows is deprecated, use vehs_per_hour instead.
dep_from, obj.class.name, dep_to))
Loading configuration... done.
Success.
Loading configuration... done.

WARNING: Inflows will cause computational performance to
significantly decrease after large number of rollouts. In
order to avoid this, set SumoParams(restart_instance=True).

Round 0, return:<PHONE_NUMBER>0000485
Average, std return:<PHONE_NUMBER>0000485, 0.0
Average, std speed: 5.041437005618326, 0.0
Closing connection to TraCI and stopping simulation.
Note, this may print an error message when it closes.
Closing connection to TraCI and stopping simulation.
Note, this may print an error message when it closes.
Skip automatic termination. Connection is probably already closed.
(flow) user@user--Super-Server:~$ python flow/examples/sumo/bottlenecks.py
/home/user/flow/flow/utils/flow_warnings.py:20: UserWarning: The attribute vehsPerHour in InFlows is deprecated, use vehs_per_hour instead.
dep_from, obj.class.name, dep_to))
Loading configuration... done.
Success.
Loading configuration... done.

WARNING: Inflows will cause computational performance to
significantly decrease after large number of rollouts. In
order to avoid this, set SumoParams(restart_instance=True).

Round 0, return:<PHONE_NUMBER>000055
Average, std return:<PHONE_NUMBER>000055, 0.0
Average, std speed: 8.17887041504013, 0.0
Closing connection to TraCI and stopping simulation.
Note, this may print an error message when it closes.
Closing connection to TraCI and stopping simulation.
Note, this may print an error message when it closes.
Skip automatic termination. Connection is probably already closed.
'''

@CYBruce To address the build error, can you conda install ffmpeg and retry?

@fywu85 Still gives the same error.

Below is the bottlenecks.py. I changed the inflow_rate, lane changing mode and speed mode.
"""File demonstrating formation of congestion in bottleneck."""

from flow.core.params import SumoParams, EnvParams, NetParams, InitialConfig, \
    InFlows, SumoLaneChangeParams, SumoCarFollowingParams
from flow.core.params import VehicleParams
from flow.core.params import TrafficLightParams

from flow.scenarios.bottleneck import BottleneckScenario
from flow.controllers import SimLaneChangeController, ContinuousRouter
from flow.envs.bottleneck_env import BottleneckEnv
from flow.core.experiment import Experiment

import logging

import numpy as np
SCALING = 1
DISABLE_TB = True
# If set to False, ALINEA will control the ramp meter
DISABLE_RAMP_METER = True
INFLOW = 1700
# congestion happens when inflow over 1700

class BottleneckDensityExperiment(Experiment):

    def __init__(self, env):
        super().__init__(env)

    def run(self, num_runs, num_steps, rl_actions=None, convert_to_csv=False):
        info_dict = {}
        if rl_actions is None:

            def rl_actions(*_):
                return None

        rets = []
        mean_rets = []
        ret_lists = []
        vels = []
        mean_vels = []
        std_vels = []
        mean_densities = []
        mean_outflows = []
        for i in range(num_runs):
            vel = np.zeros(num_steps)
            logging.info('Iter #' + str(i))
            ret = 0
            ret_list = []
            step_outflows = []
            step_densities = []
            state = self.env.reset()
            for j in range(num_steps):
                state, reward, done, _ = self.env.step(rl_actions(state))
                vel[j] = np.mean(self.env.k.vehicle.get_speed(
                    self.env.k.vehicle.get_ids()))
                ret += reward
                ret_list.append(reward)

                env = self.env
                step_outflow = env.k.vehicle.get_outflow_rate(20)
                density = self.env.get_bottleneck_density()

                step_outflows.append(step_outflow)
                step_densities.append(density)
                if done:
                    break
            rets.append(ret)
            vels.append(vel)
            mean_densities.append(sum(step_densities[100:]) /
                                  (num_steps - 100))
            env = self.env
            outflow = env.k.vehicle.get_outflow_rate(10000)
            mean_outflows.append(outflow)
            mean_rets.append(np.mean(ret_list))
            ret_lists.append(ret_list)
            mean_vels.append(np.mean(vel))
            std_vels.append(np.std(vel))
            print('Round {0}, return: {1}'.format(i, ret))

        info_dict['returns'] = rets
        info_dict['velocities'] = vels
        info_dict['mean_returns'] = mean_rets
        info_dict['per_step_returns'] = ret_lists
        info_dict['average_outflow'] = np.mean(mean_outflows)
        info_dict['per_rollout_outflows'] = mean_outflows

        info_dict['average_rollout_density_outflow'] = np.mean(mean_densities)

        print('Average, std return: {}, {}'.format(
            np.mean(rets), np.std(rets)))
        print('Average, std speed: {}, {}'.format(
            np.mean(mean_vels), np.std(std_vels)))
        self.env.terminate()

        return info_dict

def bottleneck_example(flow_rate, horizon, restart_instance=False,
                       render=None):
    """
    Perform a simulation of vehicles on a bottleneck.

    Parameters
    ----------
    flow_rate : float
        total inflow rate of vehicles into the bottleneck
    horizon : int
        time horizon
    restart_instance: bool, optional
        whether to restart the instance upon reset
    render: bool, optional
        specifies whether to use the gui during execution

    Returns
    -------
    exp: flow.core.experiment.Experiment
        A non-rl experiment demonstrating the performance of human-driven
        vehicles on a bottleneck.
    """
    if render is None:
        render = False

    sim_params = SumoParams(
        sim_step=0.5,
        render=render,
        overtake_right=False,
        restart_instance=restart_instance)

    vehicles = VehicleParams()

    vehicles.add(
        veh_id="human",
    	lane_change_controller=(SimLaneChangeController, {}),
    	routing_controller=(ContinuousRouter, {}),
    	car_following_params=SumoCarFollowingParams(
        	speed_mode=31,
    	),
    	lane_change_params=SumoLaneChangeParams(
        	lane_change_mode=1621,
        ),
        num_vehicles=1)

    additional_env_params = {
        "target_velocity": 40,
        "max_accel": 2,
        "max_decel": 2,
        "lane_change_duration": 5,
        "add_rl_if_exit": False,
        "disable_tb": DISABLE_TB,
        "disable_ramp_metering": DISABLE_RAMP_METER
    }
    env_params = EnvParams(
        horizon=horizon, additional_params=additional_env_params)

    inflow = InFlows()
    inflow.add(
        veh_type="human",
        edge="1",
        vehsPerHour=flow_rate,
        departLane="random",
        departSpeed=10)

    traffic_lights = TrafficLightParams()
    if not DISABLE_TB:
        traffic_lights.add(node_id="2")
    if not DISABLE_RAMP_METER:
        traffic_lights.add(node_id="3")

    additional_net_params = {"scaling": SCALING, "speed_limit": 23}
    net_params = NetParams(
        inflows=inflow,
        no_internal_links=False,
        additional_params=additional_net_params)

    initial_config = InitialConfig(
        spacing="random",
        min_gap=5,
        lanes_distribution=float("inf"),
        edges_distribution=["2", "3", "4", "5"])

    scenario = BottleneckScenario(
        name="bay_bridge_toll",
        vehicles=vehicles,
        net_params=net_params,
        initial_config=initial_config,
        traffic_lights=traffic_lights)

    env = BottleneckEnv(env_params, sim_params, scenario)

    return BottleneckDensityExperiment(env)

if __name__ == '__main__':
    # import the experiment variable
    # inflow, number of steps, binary
    exp = bottleneck_example(INFLOW, 1500, render=True)
    exp.run(1, 1500)

Hi, @eugenevinitsky . Is this issue a bug or did I do something wrong?


fix(general_perf): fix deberta inputs mismatch prob

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Remove redundant Rubocop rule disables

Fixes Lint/RedundantCopDisableDirective RuboCop warnings.

Suite passes apart from lint warnings.


possible spin-off project to support shims for other languages?

I've been a fan of rbenv since the beginning, preferring the shim approach over manipulation of shell builtins.
I'm also using nvm now, and I'd love to have the specified node version be picked up automatically based on the project directory without needing to run nvm use manually. This is deemed to be outside the scope of the nvm project itself (https://github.com/creationix/nvm/issues/110#issuecomment-16469680). It seems like having a shim for node would fix this.
To that end, I'm wondering if there would be any support for a spin-off project do general-purpose binstub/shim creation in other languages? As far as I can tell, https://github.com/sstephenson/rbenv/blob/master/libexec/rbenv-rehash and https://github.com/yyuu/pyenv/blob/master/libexec/pyenv-rehash are still quite similar (I'm sure intentionally so). Would there be any support for a shared version of this that is more generic, and perhaps uses a few variables at the top to specify differences (e.g. EXE_NAME=rbenv vs. EXE_NAME=pyenv).
Thoughts?
\cc @yyuu

For node, there is a direct port: nodenv

For PhantomJS, there is phantomenv.
Yes, there seems to be a trend and a need for an agnostic version switcher. I was hoping to work on one in my spare time, although I can't promise anything yet this early.

@sbull Your idea for a project that supports shims for multiple languages is good, but right now I'm focused and wrapping up rbenv 1.0 and getting it out the door, and this issue tracker is not a place where I'd want to store ideas about possible spin-off projects.
Maybe post these ideas to mislav/anyenv, a Go clone of rbenv that can manage versions of anything that you configure it for. I still have to work on that project to make it more user-friendly, since it's just a proof-of-concept right now, but it's blazing fast and 99% feature-compatible with rbenv, with exception of plugin support.


cannot create a new addr:housenumber

The addr:housenumber is now gray and I cannot enter a new house number is the box.
Actually this attribute is not usable in Id.
Regards.

@Rpnpif Could you post a screenshot and/or a link to the location where this is happening? It could be that iD does not know the address format for the location.

Sorry, i am wrong.
Wrong way to enter the number.
I am very sorry for this report and I am closing.

@Rpnpif No problem at all! I'm glad you were able to resolve the issue.


enum or allOf within oneOf false negative validation

What version of Ajv are you using? Does the issue happen if you use the latest version?
ajv: 6.5.0
ajv-cli: 3.0.0
Ajv options object

Note: I run in draft-04 mode.
ajv4.js:
import Ajv from 'ajv'
import metaSchema from 'ajv/lib/refs/json-schema-draft-04.json'

// Needed to continue to use draft-04 schemas
// @link https://github.com/epoberezkin/ajv/releases/tag/5.0.0
const Ajv4 = (options = {}, ...args) => {
  const ajv = new Ajv({
    ...options,
    meta: false, // optional, to prevent adding draft-06 meta-schema
    extendRefs: true, // optional, current default is to 'fail', spec behaviour is to 'ignore'
    unknownFormats: 'ignore', // optional, current default is true (fail)
  }, ...args)

  ajv.addMetaSchema(metaSchema)
  ajv._opts.defaultMeta = metaSchema.id

  // optional, using unversioned URI is out of spec, see https://github.com/json-schema-org/json-schema-spec/issues/216
  ajv._refs['http://json-schema.org/schema'] = 'http://json-schema.org/draft-04/schema'

  // Optionally you can also disable keywords defined in draft-06
  ajv.removeKeyword('propertyNames')
  ajv.removeKeyword('contains')
  ajv.removeKeyword('const')

  return ajv
}

export default Ajv4

import Ajv from './ajv4'

const ajv = new Ajv({
  // avoid no schema with key or ref "http://json-schema.org/draft-04/schema"
  validateSchema: false,
})

JSON Schema

{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "$id": "http://www.axa.ch/schemas/types/children.json",

  "type": "array",
  "title": "Children",
  "description": "Components rendered within a Component.",

  "additionalItems": false,
  "items": {
    "oneOf": [
      {
        "type": "object",
        "title": "Foo",
         "description": "Renders a Foo.",
        "properties": {
          "custom_to_foo": { "type": "number"  },
          "component": {
            "type": "string",
            "title": "Component",
            "description": "The name of the component used to be displayed.",
            "enum": ["Foo"]
          }
        }
      },
      {
        "type": "object",
        "title": "Bar",
         "description": "Renders a Bar.",
        "properties": {
          "custom_to_bar": { "type": "string"  },
          "component": {
            "type": "string",
            "title": "Component",
            "description": "The name of the component used to be displayed.",
            "enum": ["Bar"]
          }
        }
      }
    ]
  }
}

Sample data

[
  { "component": "Foo", "custom_to_foo": 12345 },
  { "component": "Bar", "custom_to_bar": "Will never be valid because of above enum..." },
]

Your code

https://codesandbox.io/s/yvp968ly89
Validation result, data AFTER validation, error messages
[
  {
    "keyword": "enum",
    "dataPath": "[1].component",
    "schemaPath": "#/items/oneOf/0/properties/component/enum",
    "params": {
      "allowedValues": [
        "Foo"
      ]
    },
    "message": "should be equal to one of the allowed values"
  },
  {
    "keyword": "type",
    "dataPath": "[1].custom_to_bar",
    "schemaPath": "#/items/oneOf/1/properties/custom_to_bar/type",
    "params": {
      "type": "number"
    },
    "message": "should be number"
  },
  {
    "keyword": "oneOf",
    "dataPath": "[1]",
    "schemaPath": "#/items/oneOf",
    "params": {
      "passingSchemas": null
    },
    "message": "should match exactly one schema in oneOf"
  }
]

What results did you expect?
Failing enums  or allOf within oneOf should be ignored as long as one matches.
Are you going to resolve the issue?
Don't think so.

Sorry if I bother, but  either I have a bug locally or my reduced test case is wrong.
At  the moment my suggested reduced reproduction repo works 🤔
https://codesandbox.io/s/yvp968ly89
I will check and come back later.

Sorry for spamming, it was my fault.


file locations and platform specific directories

Hi All,
sometimes one needs to get to a specific directory on a file system :

on IOS we have NSLibraryDirectory or NSTemporaryDirectory
on android the assets directory

I did not see localFS is dealing with this kind of specific data ..
should it be on the ios/bridge ? android/bridge?
Cheers,
-neshume

I think it should definitely go into platform-specific files under LocalFS, similar to the 'posix' directory. For a 'clean' solution there would be an androidFSWrapper and an iosFSWrapper (they could derive from posixFSWrapper and just override a new method called 'initAssigns()'.
This new FSWrapper::initAssigns() method would allow each platform to setup their own filesystem locations, abstracted through assigns (for instance a "temp:" assign which would point to a platform specific temp directory).
The LocalFileSystem::init() method would then call this general FSWrapper::initAssigns() instead of the current calls to getExecutableDir() and getCwd() here:
https://github.com/floooh/oryol/blob/master/code/Modules/LocalFS/LocalFileSystem.cc#L21
Does that make sense? :)

my thoughts exactly .. just wanted to make sure i have not missed any existing code already.
thx
-neshume


VScode Types validation hints don't work when "tstl" key is added to tsconfig.json

I have come across a weird quirk of vscode + typescript + tstl that I'm not sure how to debug properly. Admittedly I am very new to the typescript world so it's possible it has nothing to do with TypescriptTLua
The Problem
When I add the "tstl" key to my tsconfig, vscode stops displaying live .ts errors on the problems such as "Type '32' is not assignable to type 'string'.". As soon as I remove the tstl key it works as expected again.
tsconfig.json
{
  "exclude": ["node_modules"],
  "tstl": {}
}

example.ts
const a: number = "string";
const b: string = 32;

Expected:  Vscode should show "Type '32' is not assignable to type 'string'."
Result: No validation errors are shown
Notes:

I have tried populating the tstl options in tsconfig.json with their defaults, and got the same result
if I delete the tstl key from tsconfig vscode immediately starts recognizing validation errors

Versions:

vscode: 1.46.1
vscode typescript (shown in status bar): 3.9.4
tstl: 0.34.0

Reproduction:
repo: https://github.com/Claudiohbsantos/tstl_issue_vscodevalidation_reproduction

Hmm, very strange bug. I cloned your reproduction repo and everything seems to be working as intended. Your tsconfig is not really what I would expect for a TypeScript project, but I am using the same TS version (the vscode one 3.9.4) and it works for me, so seems like that is not the issue?
There are a couple things I am curious about:
In your project root, what happens if you run:
tsc

And what about?
npx tsc

For reference, here is a tstl project that is part of our dota 2 template, maybe the example is useful to you: https://github.com/ModDota/TypeScriptAddonTemplate/tree/master/game/scripts/vscripts

Do you have TypeScriptToLua VSCode extension installed? It's a bit outdated so it might cause such issues

Do you have TypeScriptToLua VSCode extension installed? It's a bit outdated so it might cause such issues

That was exactly it, I forgot I had it installed when putting up the issue. Thanks for the tip. As soon as I uninstalled the extension vscode started behaving as expected again.

Hmm, very strange bug. I cloned your reproduction repo and everything seems to be working as intended. Your tsconfig is not really what I would expect for a TypeScript project, but I am using the same TS version (the vscode one 3.9.4) and it works for me, so seems like that is not the issue?

Thanks for the quick answer. That tsconfig was just the bare minimum I could get to to make sure it wasn't somehow a conflict between a compilerOption and tstl.


megatools: build on darwin, update src

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Source has been removed from the GitHub repo.
https://github.com/megous/megatools#repostiory-has-been-moved

@GrahamcOfBorg build megatools


Register

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/92732
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 891aac1c91c71e6325e2a39d266e65743b561815
git push origin v0.1.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/92732
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" c03a49d8cb0d0cb792b0858390fda86eac210886
git push origin v0.1.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/102633
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" a8e87e744af1626415e486db4884d73d7089cd96
git push origin v0.1.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/102638
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" 49a71e0907a2e4802887725898de1993885c97bd
git push origin v0.1.2


Update to CPL def

Clean up to library macro checks.

Merging without clang format. Will fix in next pr.


[codec] introduce a date transport encoding based on ISO8601

baseValue encoding for a date would fail if the locale differs on both ends. introduce a transport encoding based on ISO8601.

thanks!


⚠ DDoS-Relay EU-C-fsn1-4 has degraded performance

In 933483f, DDoS-Relay EU-C-fsn1-4 (http://<IP_ADDRESS>:42069/;csv) experienced degraded performance:

HTTP code: 200
Response time: 188 ms

Resolved: DDoS-Relay EU-C-fsn1-4 performance has improved in f0470c7 after 5 minutes.


Add hackverify mandate to nest bot

Will fix tomorrow

Faisal showed me the official API so I migrated to that.


Changing Risk Finding Colors

How can I change the colors to match the schema from previous versions of Risu where Critical Findings were purple, High Findings were red, Medium Findings were orange, Low Findings were yellow, and Informational Findings were blue?  I have edited the graph colors in the risu.rb file, but they only seem to affect the headers in the technical_findings.rb file and those color headers do not match with the findings_summary.rb file.  I'd like to the headers in both templates consistent with the older Risu version risk colors.  Is that possible with the newer version?  Thanks.

Which version are you using? I think the color mismatch is fixed in the dev version. I haven't released a new one yet, as I haven't had a chance to do real world testing on some of the changes. If you check out branch 1.7.2 all the colors should be the same (New colors, based on the current Nessus ones) You can change all the colors with the GRAPH_COLORS variable. You should be able to override it in a custom template to change the colors for that template.
I will look at adding a way to configure it from the risu.cfg file.

Ah, okay.  I'm using 1.7.1.  Is there a command line install for the 1.7.2 dev version?

an easy way would be to clone the repo and use it that way, assuming a Unix shell
git clone https://github.com/arxopia/risu.git
cd risu
git checkout 1.7.2
rake build
gem install risu*.gem

then
risu --version

That should return 1.7.2
I should be able to release 1.7.2 soon maybe tonight or tomorrow night. If you can wait a few more days.

I pushed the new gem, let me know if there is any difference.
You will need to remove the 1.7.2 you installed.

Uninstalled and reinstalled with no problems.  Unfortunately, the technical findings template is still not generating a pdf.  There are no errors or warnings other than the Nokogiri warning, but that doesn't affect any of the other templates that I've used.  I type in "risu -t technical_findings -o report_technical_findings.pdf" and it gives the Nokogiri warning and then goes to the next bash prompt, just as with the other templates.  When I do a ls or browse the home directory and there's no technical findings report.  Is there something in the technical_findings.rb file that it isn't liking?

If you copy the template from the lib/templates directory to another, you will need to Change the class name and the template_info for the name
Currently Medium and Low findings are commented out, due to their verbosity. Try downloading the template on the pastebin below and place and do risu -t technical_findings_test -o test.pdf and let me know how that works.
If that doesn't work try the findings_summary template and see if there is any findings in the database.
http://pastebin.com/quv8Ppkk

Real quick... before I try that fix, I have copies of the templates in other locations.  Now, this doesn't seem to be affecting the other reports, but do I need to remove/rename these other files?
root@bt:~# find / -name 'technical_findings.rb'
/usr/local/rvm/gems/ruby-2.0.0-p0/gems/risu-1.7.2/lib/risu/templates/technical_findings.rb
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/risu-1.6.2/lib/risu/templates/technical_findings.rb
/root/risu/lib/risu/templates/technical_findings.rb
root@bt:~#

I named it technical_findings_test.rb, but it didn't register with Risu because I got the infamous error:
root@bt:~# risu -t technical_findings_test -o test.pdf
WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.7.6
[!] Template "technical_findings_test" does not exist. Please check the name
The findings summary template works like a champ with the new color scheme listing all of the findings from critical down to informational.

Is the test template in the same directory as your risu.cfg?

No, I had put it in the /risu/lib/risu/templates/ directory.  I moved it to my root directory and success!  Only problem is the colors are wrong.  The Critical Findings header is in a dark grey/green color.  High and Medium are a lime green color and Low is in blue.  Is there a way I can match them to the findings summary header colors?

I found the bug last night. I will have a update in the repo tonight.

Okay thank you.  I will try the updated version tonight.

I pushed gem 1.7.3. Let me know if you are still having the issue. I rewrote the entire template as it was using older api calls.

I uninstalled the gem and then reinstalled it and confirmed that it's version 1.7.3.  However, it's still not generating the technical findings report.  Same result as before.

Hmm this is puzzling ;/
On Thursday, January 8, 2015, mrjim72<EMAIL_ADDRESS>wrote:

I uninstalled the gem and then reinstalled it and confirmed that it's
version 1.7.3. However, it's still not generating the technical findings
report. Same result as before.
—
Reply to this email directly or view it on GitHub
https://github.com/arxopia/risu/issues/76#issuecomment-69277000.

--
Jacob Hammack
<EMAIL_ADDRESS>(210) 355-0036
http://www.hammackj.com

Do I need to manually rip out the old directories?

Try gem uninstall risu for all the versions then reinstall the latest.
Might change something.
On Thursday, January 8, 2015, mrjim72<EMAIL_ADDRESS>wrote:

Do I need to manually rip out the old directories?
—
Reply to this email directly or view it on GitHub
https://github.com/arxopia/risu/issues/76#issuecomment-69277253.

--
Jacob Hammack
<EMAIL_ADDRESS>(210) 355-0036
http://www.hammackj.com

I did that yesterday because I had 1.62 and 1.72 installed.  Just now there was only 1.7.2.  This is a VM, so I think I'm going to just stand up a new one and see what happens with a fresh install.  I'll report back what I find.

Update: I stood up a new VM for my favorite stable version of Backtrack 5r3 and was not able to update to 1.7.3 because the repositories weren't alive anymore to automagically update Ruby and Rubygems.  Instead of trying to hack through the weeds of that, I went back to Kali and started over.  I uninstalled my prior versions of Risu and updated the Ruby stuff.
Here is what I'm running now:
risu: 1.7.3
Ruby Version: 2.1.2
Rubygems Version: 2.4.5
When I ran a technical findings report, the report generated perfectly with the correct color scheme, Critical in red, High in orange.  However, despite the Medium and Low findings not being commented out, they were not included in the report.
I copied the report from the templates directory to my home directory and modified the class name and template_info to add "test" and I named the file "technical_findings_test.rb".  I made no other changes.
When I ran that report, it included Critical, High, Medium, and Low, but with the goofy color scheme of the dark grey/green for Critical. High and Medium in lime green and Low in blue.

Some more info:  I edited the GRAPH_COLORS[n] in the technical_findings_test.rb template in my home directory and went through all the variables from 0-9 and never did come close to matching the correct color schema.
Here are the GRAPH_COLORS as best I can determine from the variables 0-9.
[1]: lime green
[2]: lime green
[3]: blue
[4]: medium blue
[5]: light blue
[6]: kelly green (darker than 1&2, but not as dark as 0... reminded me of the NY Jets colors)
[7]: med-light blue (between 4&5)
[8]: black
[9]: blue-med blue (between 3&4)

Lets try this. Inside of your local technical_findings.rb, in the render method add this around line 93
puts GRAPH_COLORS.inspect

and then generate a report and let me know the output.
I get
["#d2403f", "#ec9241", "#fcc343", "#50ad51", "#397bbb", "#8E6B8E", "black", "#cccccc", "brown", "#e52d89"]
These are the correct colors set.
Also could you post the template copy you are using?

I got that same output, repeated five times.
Here's the template I'm using.  I copied the technical_findings.rb from the templates directory to my home directory, changed the class and template_info name to included the word "test" and saved it as technical_findings_test.rb  This is with the puts GRAPH_COLORS.inspect line included.
Copyright (c) 2010-2014 Arxopia LLC.
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* Neither the name of the Arxopia LLC nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.

 IN NO EVENT SHALL ARXOPIA LLC BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE.
module Risu
module Templates
class TechnicalFindingsTestTemplate < Risu::Base::TemplateBase
include TemplateHelper
		def initialize ()
			@template_info =
			{
				:name => "technical_findings_test",
				:author => "hammackj",
				:version => "0.0.8",
				:renderer => "PDF",
				:description => "Generates a Technical Findings Report"
			}
		end

		def render(output)
			text Report.classification.upcase, :align => :center
			text "\n"

			report_title Report.title
			report_subtitle "Critical and High Findings"
			report_author "This report was prepared by\n#{Report.author}"

			text "\n\n\n"

			unique_risks = Array.new
			unique_risks << Hash[:title => "Critical Findings", :color => Risu::GRAPH_COLORS[0], :values => Item.critical_risks_unique] if Item.critical_risks_unique.to_a.size != 0

unique_risks << Hash[:title => "High Findings", :color => Risu::GRAPH_COLORS[1], :values => Item.high_risks_unique] if Item.high_risks_unique.to_a.size != 0
unique_risks << Hash[:title => "Medium Findings", :color => Risu::GRAPH_COLORS[2], :values => Item.medium_risks_unique_sorted] if Item.medium_risks_unique_sorted.to_a.size != 0
unique_risks << Hash[:title => "Low Findings", :color => Risu::GRAPH_COLORS[3], :values => Item.low_risks_unique_sorted] if Item.low_risks_unique_sorted.to_a.size != 0
			unique_risks.each_with_index do |h, index|
				if h[:values].length > 0

					output.font_size(18) do
						output.fill_color h[:color]
						text h[:title], :style => :bold
						output.fill_color "000000"
					end

					text "\n"

					h[:values].each do |f|

						hosts = Item.where(:plugin_id => f.plugin_id).group(:host_id)
						plugin = Plugin.find_by_id(f.plugin_id)

						references = Reference.where(:plugin_id => plugin.id).group(:value).order(:reference_name)

						output.font_size(16) do
							text "#{plugin.plugin_name}\n"
						end

						if hosts.length > 1
							text "Hosts", :style => :bold
						else
							text "Host", :style => :bold
						end

						hostlist = Array.new
						hosts.each do |host|
							ho = Host.find_by_id(host.host_id)
							#if h.id != blacklist_host_id.first.id
								host_string = "#{ho.name}"
								host_string << " (#{ho.fqdn})" if ho.fqdn != nil
								hostlist << host_string

puts GRAPH_COLORS.inspect
#end
end
						text hostlist.join(', ')

						if f.plugin_output != nil
							text "\nPlugin output", :style => :bold
							text f.plugin_output
						end

						if plugin.description != nil
							text "\nDescription", :style => :bold
							text plugin.description.gsub(/[ ]{2,}/, " "), :inline_format => true
						end

						if plugin.synopsis != nil
							text "\nSynopsis", :style => :bold
							text plugin.synopsis
						end

						if plugin.cvss_base_score != nil
							text "\nCVSS Base Score", :style => :bold
							text plugin.cvss_base_score
						end

						if plugin.exploit_available != nil
							text "\nExploit Available", :style => :bold

							if plugin.exploit_available == "true"
								text "Yes"
							else
								text "No"
							end
						end

						if plugin.solution != nil
							text "\nSolution", :style => :bold
							text plugin.solution
						end

						if references.size != 0
							text "\nReferences", :style => :bold
							text plugin.references.reference_string, :inline_format => true
							plugin_url = "http://www.tenablesecurity.com/plugins/index.php?view=single&id=#{plugin.id}"
							text "<b>nessus_plugin</b>: #{plugin_url}", :inline_format => true, :link => plugin_url
						end

						text "\n"
					end
				end

				output.start_new_page if unique_risks[index+1] != nil
			end

			output.number_pages "<page> of <total>", :at => [output.bounds.right - 75, 0], :width => 150, :page_filter => :all
		end
	end
end

end

Looks like thats the old version of the template. Below is the newest version with the fix.
https://raw.githubusercontent.com/arxopia/risu/master/lib/risu/templates/technical_findings.rb

Ignore the extraneous backslash.  Pasting the code was a mess without them, so put them at the beginning of each new line.

Fixed!  I've been toying with it for awhile to be sure.  Your help with this also fixed an problem I've been having with Risu not liking my custom templates.  I think that's because I was changing the template_info name, but not changing the class.  Now I'm able to copy them over and toy with them.  Thank you very much for your help and your patience.  I love the tool and now I have an even better appreciation for the work that you put into it.

Great glad everything is working for you.
Risu will load templates from
$GEM_HOME/gems/risu-version/lib/risu/templates

and
/home/username/.risu/templates

and the current directory. The class name and template_info hash name has to be unique or it will not load one of the dupe'd names.
Hope that helps! Feel free to ask any other questions you have.

Yes it helps!  Thank you for doing what you do.  I have a working install of 1.7.3 with both VM and an extra laptop install of Backtrack.  It also works with my VM of Kali.    However, my each of my installs of RVM and Risu do not stay installed on my VM of Kali.
My next task is to do an install of the latest version of Kali on my extra laptop.  I will report back.  I'm betting it's NOT a Risu issue, since I have Risu working with VMs of Backtrack5R1 in a VM and in a laptop install and I also have it working with a VM of Kali 1.08.


Add tests for AddInsuranceCommand

Currently, we have no tests for AddInsuranceCommand.
Let's add tests for AddInsuranceCommand to increase our test coverage.

Linked to issue #111


testing citadel header redirects

testing #101 with https://github.com/gazebosim/gz-cmake/pull/303 on macOS using https://github.com/osrf/homebrew-simulation/commit/0aaf235054172d8a80ef0c5a33a4575076d20d93
testing only, not for merging

testing #101 with gazebosim/gz-cmake#303 on macOS using osrf/homebrew-simulation@0aaf235
testing only, not for merging

macOS build is happy:


Update base_rollup.ts to follow diagram

Description
Closes #86.

Updates base_rollup to use calldataHash instead of the separate hashes from earlier.
Updated RollupType names for rollup to be merge
Create Bytes32 for hashes.

Checklist:

[x] I have reviewed my diff in github, line by line.
[x] Every change is related to the PR description.
[x] I have linked this pull request to the issue(s) that it resolves.
[x] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[x] There are no circuit changes, OR specifications in /specs have been updated.
[x] There are no circuit changes, OR a cryptographer has been assigned for review.
[x] I've updated any terraform that needs updating (e.g. environment variables) for deployment.
[x] The branch has been rebased against the head of its merge target.
[x] I'm happy for the PR to be merged at the reviewer's next convenience.
[ ] New functions, classes, etc. have been documented according to the doxygen comment format. Classes and structs must have @brief describing the intended functionality.
[ ] If existing code has been modified, such documentation has been added or updated.

Note
If you are updating the submodule, please make sure you do it in its own special PR and avoid making changes to the submodule as a part of other PRs.
To update a submodule, you can run the following commands:
$ git submodule update --recursive

Alternatively, you can select a particular commit in barretenberg/aztec3 that you wish to point to:
$ cd barretenberg
$ git pull origin aztec3        # This will point to the latest commit in `barretenberg/aztec3`
$ git checkout <commit_hash>    # Use this if you wish to point to a particular commit.
$ cd ..
$ git add . && git commit -m <commit_msg>
$ git push

I believe this will break the TS test that does a roundtrip serialization call to C++. Unfortunately TS tests are not running in CI yet.
Here is the C++ struct: https://github.com/AztecProtocol/aztec3-circuits/blob/master/cpp/src/aztec3/circuits/abis/base_rollup/base_rollup_public_inputs.hpp#L43

Ah, forgot to update that after rebase 😅
Also, should do as for AC and convert sha256 to a field element using mod, or should we pass the actual sha256? Might as well do it in the same passing.

The ts tests just capture the output of print after we read and then we eyeball for strings like 0x101 in the right place, they might need to be updated though by deleting the snapshot folder before yarn test


Device -> Eth -> ipv6_address -> gateway shouldn't have a default value as this is a required field

I am observing this against the model version version 0.6.6

Resolved in v0.9.10


Mark default 'style' attr as safe to avoid warning

Comments welcome !

Someone already filed a PR for the same problem, my bad.


Correction for raw affiliation Department of Biochemistry, Schulich School of Medicine and Dentistry, Western University

Correction needed for raw affiliation Department of Biochemistry, Schulich School of Medicine and Dentistry, Western University
raw_affiliation_name: Department of Biochemistry, Schulich School of Medicine and Dentistry, Western University
new_rors: 02grkyz14
previous_rors: 02agqkc58
works_examples: W4387159199;W4319059273
contact: 02a044798d57ba3405c6378988043d9a:f605e523c5f16103 @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-21. The new affiliations should be visible within the next 7 days.


Topic/scaffold template with plaster

PR Summary
Adding Plaster for scaffolding new commands for the module. Also adjusted the documentation for the contribution guide to making this mandatory for every new function.
In this case we make sure:

function template file is used
unit test file template is used
documentation template is generated
optionally - types and formats for returned data is generated

It closes #292
PR Checklist

[X] Write Help
[ ] [Write Unit Test] - not needed
[ ] [Update CHANGELOG.md] - not needed

@DarqueWarrior can you check the template if you think it applies to your desired coding standards?

First this is awesome!
Some things I noticed.
When I selected Get as the cmdlet the sample code had
-Method "Post"

Should the selection of cmdlet be a freeform? I know there is an "approved" list of verbs but you can use "non-approved" verbs as well. I also noticed 'Invoke' was not listed and we have one of those.
What are your thoughts on adding Plaster as a dependency so it is downloaded for you when you install VSTeam?
Again this is a great addition.

Yes, we could add Plaster as a dependency. We have 2 options with Plaster that I can see:

Use templates for new developments for the module
Use templates included in the module which gives you jumpstart scripts when creating your own scripts based on VSTeam

Having said that to use Plaster as a dependency where we only use templates not included in the module does not make much sense (we also don't have Pester as a dependency). Unless we have jumpstart scripts for module users as well.
Yes, I wanted to ensure somehow approved verbs, but if you think it is too strict, then I can just use a free form.
We can go as complex as you want. The Method is just hardcoded in the example.

We might want to press pause on this until the Pester5 changes are done. The test structure is changing.

yes makes sense. I will be waiting to then adjust the unit test template.

@DarqueWarrior shall I resume and update the templates? Which unit test file do you think fits to convert it to a proper Pester 5 unit test template?

I think this code should be its own project in the new org.

Ok cool. But we can make another PR once we have a small base of quickstart scripts then we can include them as plaster scripts in the module to have a quickstart for people.


[Snyk] Upgrade semantic-release from 19.0.3 to 19.0.4

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade semantic-release from 19.0.3 to 19.0.4.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2022-08-22.

Release notes

Package name: semantic-release

19.0.4 - 2022-08-2219.0.4 (2022-08-22)
Bug Fixes

deps: update dependency yargs to v17 (#1912) (f419080)

19.0.3 - 2022-06-0919.0.3 (2022-06-09)
Bug Fixes

log-repo: use the original form of the repo url to remove the need to mask credentials (#2459) (58a226f), closes #2449

    from semantic-release GitHub release notes

Commit messages

Package name: semantic-release

f419080 fix(deps): update dependency yargs to v17 (#1912)
3bbf08c test(integration): upgrade the gitbox image to support arm architecture in addition to x86 (#2516)
846f4c2 build(deps): bump terser from 5.14.0 to 5.14.2 (#2513)
bd294eb docs(plugin-list): add semantic-release-space plugin (#2502)
c69445e docs: remove deprecated keyword in gitlab-ci.md (#2498)
d80e2ea build(deps-dev): bump got from 11.8.3 to 11.8.5 (#2485)
9589a96 docs: fix typos (#2476)
ec89bab docs: replace issue templates with forms (#2474)
db620aa docs: fix typo (#2473)
dd77f1f docs: fix typo (#2472)
e66b4b5 docs: drop duplicate word (#2471)
3387fb7 docs: fix typo (#2468)
587bb91 docs(configuration.md): `addChannel` step is skipped when `dryRun` is enabled (#2465)
05c9360 build(deps): bump semantic-release from 19.0.0 to 19.0.3
f1d7ad4 build(deps): bump semver-regex from 3.1.3 to 3.1.4 (#2451)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Superseded by #24


fix(topology): updates pf react-topology to standalone release

Fixes: https://github.com/janus-idp/backstage-plugins/issues/260

/lgtm


Draft: Document public API #34

I there!
Here is the doc I wrote I wrote a few weeks ago. It has been on hold for some time because I started a new job recently. I'll finish it soon, but in the mean time some can already be reviewed.

Merged in #126.


On page reload background-position gets wrong

I am using Stellar.js v0.6.2 jQuery plugin to display 6 background images with parallax effect.
Everything works fine on first load of the page, but if I reload/refresh it, I see that the background-position settings are wrong and the parallax effects are ruined.
This is Stellar.js settings that I use:
scrollProperty: 'scroll',
positionProperty: 'position',
horizontalScrolling: false,
verticalScrolling: true,
horizontalOffset: 0,
verticalOffset: 0,
responsive: true,
parallaxBackgrounds: true,
parallaxElements: true,
hideDistantElements: true,
This is what I have in HTML source, as an example:
...section class="visible" id="contact" data-stellar-background-ratio="0.6" data-stellar-vertical-offset="20"...
This is how correct background position looks when page is opened for a first time:
...section class="visible" id="contact" data-stellar-vertical-offset="20" data-stellar-background-ratio="0.6" style="background-position: 30px 82.4701px;"...
This is how it looks when I refresh the page (the same position of the section in the window) as before:
...section class="visible" id="contact" data-stellar-vertical-offset="20" data-stellar-background-ratio="0.6" style="background-position: 30px -305.2px;"...
As you see, the negative value -305.2px is what ruins the parallax.
I cannot sleep without finding what causes that. Can you help me?

var fakeListenerParallax;

fakeListenerParallax = setInterval((function() {
  $('[data-stellar-background-ratio]').each(function() {
    var ofs;
    ofs = $(this).offset().top * $(this).data("stellar-background-ratio");
    ofs = -ofs;
    ofs = ofs + $(window).scrollTop() * 0.5;
    $(this).css("background-position", "0px " + ofs + "px");
  });
}), 15);

setTimeout((function() {
  clearInterval(fakeListenerParallax);
}), 200);

this goes to $(window).load(). you can play with interval value to find lowest one for your website


AD_Discovery_TR-789_2

Active Directory Discovery batch 2
Datamodels

adsisearcher account discovery
domain account discovery with dsquery
domain account discovery with net app
domain account discovery with wmic
get aduser with powershell
get domainuser with powershell
getwmiobject ds user with powershell

Powershell ScriptBlock

get domainuser with powershell script block
get aduser with powershell script block
getwmiobject ds user with powershell script block

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
AdsiSearcher Account Discovery :white_check_mark:

diskUsage: 163840
runDuration: 1.2s
scanCount: 2

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Domain Account Discovery with Dsquery :white_check_mark:

diskUsage: 483328
runDuration: 5.9590000000000005s
scanCount: 6814

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Domain Account Discovery With Net App :white_check_mark:

diskUsage: 585728
runDuration: 2.567s
scanCount: 712

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Domain Account Discovery with Wmic :x:

diskUsage: 360448
runDuration: 2.105s
scanCount: 1

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Get ADUser with PowerShell Script Block :white_check_mark:

diskUsage: 159744
runDuration: 1.31s
scanCount: 72

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Get ADUser with PowerShell :white_check_mark:

diskUsage: 589824
runDuration: 2.041s
scanCount: 5

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Domain Account Discovery with Wmic :x:

diskUsage: 360448
runDuration: 2.475s
scanCount: 1

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Domain Account Discovery with Wmic :white_check_mark:

diskUsage: 376832
runDuration: 2.205s
scanCount: 3

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Domain Account Discovery with Wmic :white_check_mark:

diskUsage: 376832
runDuration: 2.366s
scanCount: 3

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Get DomainUser with PowerShell :white_check_mark:

diskUsage: 581632
runDuration: 2.778s
scanCount: 12

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Get DomainUser with PowerShell Script Block :x:

diskUsage: 139264
runDuration: 0.003s
scanCount: 0

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
GetWmiObject DS User with PowerShell Script Block :white_check_mark:

diskUsage: 163840
runDuration: 0.895s
scanCount: 101

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
GetWmiObject DS User with PowerShell :white_check_mark:

diskUsage: 380928
runDuration: 2.826s
scanCount: 5

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Get DomainUser with PowerShell Script Block :white_check_mark:

diskUsage: 159744
runDuration: 1.158s
scanCount: 111

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
GetWmiObject DS User with PowerShell :white_check_mark:

diskUsage: 380928
runDuration: 2.955s
scanCount: 5


Analyze your cloud mix

This section seems out of place in the timeline.  This article is focused on preparing for the cloud and identifying the Azure architectural inputs based on the customer's intended hybrid cloud strategy.  This section describes how to inventory an existing hybrid cloud deployment.  Perhaps this is meant to show that you can be intentional, understand your current deployment, then reimagine even your existing architectures.  You can follow this process even if you have already deployed?  That sentiment doesn't come across, however, and the content feels a little out of place.

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

ID: da811d0e-df5f-0715-cc72-8b4f1bb1bb49
Version Independent ID: 55e4182b-954d-0822-d6cf-2f59c37a1b2c
Content: Ready methodology for Hybrid and Multicloud - Cloud Adoption Framework
Content Source: docs/scenarios/unified-operations/ready.md
Service: cloud-adoption-framework
Sub-service: ready
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 364391

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 364391

Added to the review backlog.

Added to the review backlog.