Vite syntax error in parsed output

Hi all,
I am trying to migrate our project from CRA to Vite and am having trouble with loading graphql files using vite. I am using this plugin however, I'm getting the below output when trying to start the project:

[plugin:vite:import-analysis] Failed to parse source for import analysis because the content contains invalid JS syntax. You may need to install appropriate plugins to handle the .graphql file format, or if it's an asset, add "**/*.graphql" to assetsInclude in your configuration.

Here is problematic line:
12 |  const _gql_doc = {"kind":"Document","definitions":[{"kind":"OperationDefinition","operation":"query","name":{"kind":"Name","value":"CostOfLivingAdjustmentQuery"},"variableDefinitions":[{"kind":"VariableDefinition","variable":{"kind":"Variable","name":{"kind":"Name","value":"year"}},"type":{"kind":"NonNullType","type":{"kind":"NamedType","name":{"kind":"Name","value":"Int"}}},"directives":[]}],"directives":[],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"costOfLivingAdjustmentRate"},"arguments":[{"kind":"Argument","name":{"kind":"Name","value":"year"},"value":{"kind":"Variable","name":{"kind":"Name","value":"year"}}}],"directives":[],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"InlineFragment","typeCondition":{"kind":"NamedType","name":{"kind":"Name","value":"ColaRate"}},"directives":[],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"FragmentSpread","name":{"kind":"Name","value":"costOfLivingAdjustmentRateFields"},"directives":[]}]}}]}}]}}],"loc":{"start":0,"end":281,"source":{"name":"GraphQL request","locationOffset":{"line":1,"column":1},"body":_gql_source}}};

If I paste this into a code editor, I do indeed get an error on _gql_source where it is not defined anywhere.
Is there something wrong with my configuration?
vite.confg.js
import path from 'path';
import react from '@vitejs/plugin-react';
import graphqlLoader from 'vite-plugin-graphql-loader';
import tsconfigPaths from 'vite-tsconfig-paths';

/** @type {import('vite').UserConfig} */
export default {
    server: { port: 3000 },
    build: { outDir: 'build' },
    plugins: [react(), tsconfigPaths(), graphqlLoader()],
    resolve: {
        alias: {
            src: path.resolve(__dirname, 'src'),
            components: path.resolve(__dirname, 'src/components'),
            views: path.resolve(__dirname, 'src/views'),
            hooks: path.resolve(__dirname, 'src/hooks'),
            lib: path.resolve(__dirname, 'src/lib'),
            config: path.resolve(__dirname, 'src/config'),
            layouts: path.resolve(__dirname, 'src/layouts'),
        },
    },
};

Using Vite 5.4.0 and vite-plugin-graphql-loader 4.0.2
Thanks!

Thanks for the reply, I can confirm that indeed fixes the issue although Im now face with another error of a similar kind:
  25 |  const collectFragmentReferences = (node, refs) => {
  26 |      if (node.kind === "FragmentSpread") {
     |                                        ^
  27 |          refs.add(node.name.value);
  28 |      }

Ill update this comment with anything I find

Is there an error message connected with that code location?

The same one as before:
08:24:55 [vite] Internal server error: Failed to parse source for import analysis because the content contains invalid JS syntax. You may need to install appropriate plugins to handle the .graphql file format, or if it's an asset, add "**/*.graphql" to `assetsInclude` in your configuration.
  Plugin: vite:import-analysis

If it helps, contentent of the file is as below:
#import ../../Fragments/Fragment.graphql

query Query($year: Int!) {
    field(year: $year) {
        ... on Fragment {
            ...fragmentFields
        }
    }
}

Following the relative path in the import is the fragment being referenced:
fragment fragmentFields on Fragment {
    id
}

Yes! that fixes it. Thank you!


Add migration query to create new columns prJobsCount, prJobsSuccessful, prJobsFailed, prJobsTimedOut, prJobsCancelled, prJobsSkipped, prJobsUnstable to projectDailyAggs

https://github.com/Shippable/admiral/issues/1884

You cannot make it a not null column. I don't think there's any reason for this to have a default value, either.


Separation of model code and parameter data

Reported by AHaumer on 4 Nov 2008 11:32 UTC
In many cases it is desired to separate parameter data from model code, to be able to apply a ready-developed application model on different parameter sets defined by different projects.
If the parameters are all non-structural, i.e.not changing the count of unknowns and equations, the application model could be applied without re-translation.
Regarding the parameters, there are two types of parameters:

property parameters of componets (e.g. the resistance of a resistor)
boundary conditions resp. simulation parameters (e.g. the amplitude of the driving voltage source)
Reading both types of parameters from file would be convenient; currently there are 3 options to experiment with:
Modelica.Utilities (keyword-oriented)
external C-functions
XML-library (c) arsenal rsearch
We should test the different options, defining a convenient and tool-independet way to separata data from code.

Migrated-From: https://trac.modelica.org/Modelica/ticket/115

Comment by mtiller on 4 Nov 2008 15:32 UTC
A few comments.  First, I want to point out that the three options mentioned are "pull" options.  What I mean by that is that the Modelica code needs to be such that all of the parameters in question explicitly "pull" their values from another source.  The important point here is that the models need to be instrumented in advance to pull this information.
The alternative approach, which is realized to some extent in using modifications, is to push changes on a class.  For example, when we extend from one class and then make a whole series of modifications in the extend clause we are pushing modifications on the original model.
The problem I see with modifications as they stand now is that they are not programmatic.  I can't write algorithmic code to decide how to configure something.  Peter and Sebastien (I think) have talked in the past about the ability to write code the actually manipulates models in such ways.  This might address the main issue I see with "pull" approaches which is that you have to pre-instrument all these models to pull their values.  You could "push" modifications onto the model that then "pull" the values from sources (e.g. model A extends B(x=getFromFile("x"))) but it might be more scalable to implement something that could walk the model, identify candidate parameters and apply such modifications in a more programmatic way.
This doesn't really address what Anton is proposing but I just wanted to add some comments about the "big picture".

Comment by dietmarw on 20 Feb 2009 15:50 UTC
closing milestone:Design60 and postponing this discussion to the next post 3.1 Design Meeting

Modified by dietmarw on 19 Nov 2009 16:32 UTC

Comment by hansolsson on 30 Mar 2016 14:03 UTC
Correcting "Component" - the different parameterizations is primarily a library issue and version is already "Standard Library 3.0".

Changelog removed by hansolsson on 30 Mar 2016 14:03 UTC

Modified by ahaumer on 20 Dec 2016 16:47 UTC

@AHaumer There is a free library ExternData available that provides paramerization from external parameter sources.

Closing as worksforme after 9 years.


Configurables file generated with bal persist doesn't need & readonly for connectionOptions

Description:
$title, because configurable variables are implicitly final and immutable.

@MaryamZi When I remove & readonly from the connectionOptions configurable. I am getting the following error while compiling
ERROR [modules/mssql_entities/persist_client.bal:(61:135,61:152)] invalid access of mutable storage in an 'isolated' function

@MaryamZi When I remove & readonly from the connectionOptions configurable. I am getting the following error while compiling
ERROR [modules/mssql_entities/persist_client.bal:(61:135,61:152)] invalid access of mutable storage in an 'isolated' function

Error happens when initializing the client below
    public isolated function init() returns persist:Error? {
        mysql:Client|error dbClient = new (host = host, user = user, password = password, database = database, port = port, options = connectionOptions);
        if dbClient is error {
            return <persist:Error>error(dbClient.message());
        }
        self.dbClient = dbClient;
        self.persistClients = {[DATA_TYPE]: check new (dbClient, self.metadata.get(DATA_TYPE), psql:MYSQL_SPECIFICS)};
    }

Seems to be due to https://github.com/ballerina-platform/ballerina-lang/issues/43072


Gluon, Minpy and NN

It seems all those three packages are developed to suppport dynamical graph, which can provide flexible programming interface as pytorch.  Will Minpy and NN be discarded?  And will mxnet continue to complete Gluon without moving to develop a new package?  I 'm a little confused by these packages.

Thanks for the question. For MinPy project, our initial design goals include xx parts: (1) dynamic autograd; (2) fully-compatible numpy support; (3) transparent integration with MXNet's symbolic programming so one-style-achieves-all. During the process, we learned three things:

We initially intend to release MinPy as a separate package, but it seems that dynamic autograd is so popular (look at pytorch) that MXNet requires this feature very urgently. Therefore, we decide to merge the autograd feature into MXNet (see https://github.com/apache/incubator-mxnet/blob/master/python/mxnet/contrib/autograd.py) by @ZihengJiang .
A good DNN model builder and an easy-to-use toolchain (initializer, updater, etc.) is crucial for fast development. MinPy's NN module is based on CS231n, which is not sophisticated enough for researches. Therefore, we spend a lot of efforts on a better model builder structure ( @piiswrong @sneakerkg and many others). The new package is developed directly in MXNet (also called NN) and now becomes Gluon.
Speed is a dominating factor for a DL framework. We found writing fine-grained operators in python yields many efficiency issues. Therefore, the MinPy team is focusing on Just-In-Time (JIT) compilation to improve the efficiency (please stay tuned!).

TL;DR: Gluon (successor of NN package) will be our standard DNN model & solver package. MinPy will evolve more into two directions: (1) JIT functionality that can also benefit Gluon and other MXNet packages; (2) More compatible support for NumPy operators.
@zzhang-cn

@jermainewang thx for your explanation


ModuleNotFoundError: No module named 'dreamplace.ops.rmst_wl.rmst_wl_cpp'

Hi, I'm trying to implement your algorithm.
I installed packages as your description, but the error occurred.
How does rmst_wl_cpp file be created?
I assume that rmst_wl_cpp.py has to be created and imported.
However, I cannot find the file even after implementing make and make install.
Thanks.

Hi, I'm trying to implement your algorithm.
I installed packages as your description, but the error occurred. How does rmst_wl_cpp file be created? I assume that rmst_wl_cpp.py has to be created and imported. However, I cannot find the file even after implementing make and make install.
Thanks.
you need to make your environment as Dreamplace instructed

I run as below.
in EDA-AI dir,
$ mkdir build && cd build
$ cmake ..
$ make

However, I still could not find dreamplace.ops.rmst_wl.rmst_wl_cpp...
How can I handle this problem?

I run as below.
in EDA-AI dir,
$ mkdir build && cd build
$ cmake ..
$ make

However, I still could not find dreamplace.ops.rmst_wl.rmst_wl_cpp... How can I handle this problem?

When doing make.
You need to first modify the CMakeLists.txt in DREAMPlace/dreamplace/ops/CMakeLists.txt
add add_subdirectory(rmst_wl) to DREAMPlace/dreamplace/ops/CMakeLists.txt
Then you may run make to build your environment

@WOOSHIK-M
Did you solve the problem?
I still have a problem that i cannot import the rmst_wl_cpp module even I modify the CMakeLists.txt


Regarding Custom Dataset

Hi, first of all thanks a lot for this library.
I want to use my custom dataset to train a model, and it seems from here I'll have to have my dataset in the mentioned format.
Is there any way I can use my own custom dataloader to load the dataset in the pipeline?
Example: Suppose I have a dataset of numpy files which contains images in a numpy array.
I have followed the documentation here but was in vain.
Any help would be really appreciated!
Thanks!

I'm trying this for now, and hence closing this issue temporarily.


GetState() is not guarded by Mutex (concurrent read/write)

depsResolver.GetState() can be called during an indexer commit round.

 [mantle] fix mutex issue in depsresolver

fixed w/ 9f15ae341df5b5a1860801c86393fe5fbe70f3d7


Update README.md

Have updated the readme you could have a look at it at
https://github.com/PxTools/PxWeb2/tree/fix/readme?tab=readme-ov-file

En mening är inte avslutad. Autom... var felstavat

@AsaArrhen the error should be fixed now.

@AsaArrhen the error should be fixed now.

@likp Hittade ett till stavfel Right no we are working hard on the new version of PxWeb 2.  now

@AsaArrhen I hope it would be fix now :-)


docs: update controls in README

Fixes: #10

Hey @elishaestibeiro thanks for opening up a PR! This first change looks good to me. Hopefully, we'll get this merged in no time :)

Well done! Congrats on getting your first PR merged :)


Terrible performance when the vertical size of the scrollable area is big

With 14 active contracts during flights the CPU is constantly loaded when the window is displayed (even if its size is small). This cripples the overall performance. Disabling transparency (by replacing the texture) does not help. Hiding the window brings everything back to normal, as does hiding/minimizing most contracts.

Fixed by 075579edca00a2e76fe04b76c49024d8deef16c0


Update documented syntax for manual login options

Changed hyphens to underscores in authentication option names. As mentioned in issue #523, the options need underscores (not hyphens) yet the documentation still instructed to use hyphens.

There was an effort recently to switch gcalcli over to all posix-style flag conventions, so no more camel case or underscores.  To my reading, we've got a bug in the plumbing through from PROGRAM_OPTIONS to the call to the Oauth workflow on lines 141/142 of gcal.py.  But we should fix that bug, not just change the documentation to suggest using options that we've purposefully deprecated.  Even if we change course and decide to undeprecate the underscored versions of these options, we'd need a PR that actually deals with deprecations.py.
Should I close this PR or leave it open for you to work on the potential option-plumbing bug?

Obsolete now that both the instructions and program's arguments are using hyphens.


[E2E] Remove UpResultDeserializer

What does this PR do?

This PR simplifies the deserialization of data stored in pulumi context by removing UpResultDeserializer.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

💭 thought
After discussions today, I wonder if we should rename current client.Agent, client.VM, etc to AgentStackProxy, as they act as proxy between pulumi exported data and clients. clients should not be aware of pulumi, if possible, so that they can be reused, for instance in install test, where the VM is managed by Pulumi, but the agent is set after the test install act.

Another use case, still for installer test, is allowing local tests on an existing VM. In this case, the suite could be created based on an existing environment, no need to deserialise it, no need to go through Pulumi.

I think it could be done in another PR as this one is only to simplify the code.


where to download the mesh files of the 8827 objects?

where to download the mesh files of the 8827 objects?
The dataset is comprised of 8836 HDF5 files， can not  find the corresponding meshes....

See the instructions in the README:  https://github.com/NVlabs/acronym#using-the-full-acronym-dataset
You will need to register at www.shapenet.org to download the meshes for ShapeNetSem.


Tab Completion does not work as expected for versions

The following hint is displayed after sdk ls java
Use TAB completion to discover available versions     $ sdk install java [TAB]
Trying this results in
sdk install java <FILE>

Fixed with 29-tab-


Initial Windows version

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] 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)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Test A
[x] Test B

Test Configuration:

Firmware version:
Hardware:
Toolchain:
SDK:

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

This is a first version supporting Windows 10. Edge detection is based on OpenCV like in the Android version of the plugin. The camera window UI and photo capture code is entirely written in JavaScript using Windows 10 only APIs and works with all Windows 10 versions using the APIs appropriate to the version. If the device supports a separate photo stream, the photo is captured from that, otherwise the video stream is used to capture the photo.
The OpenCVBridge wrapper is written C++. OpenCV 3.1. sourc code is included together with the binaries to be able to rebuild the dependent modules. The elswhere available binary OpenVC DLLs won't confirm to Microsoft Store specifications due to wrong compiler and linker flags used. So it's better to include all here in the project.
There are some additional options to provide to the scanDoc function. Description in detail is following later.
A Windows 8.1 branch of the plugin, using a Media Transfrom Filter instead of a Media Frame Reader is in work and will be provided with coming pull request later, maybe next week.

Hey @convey-gilbert
This is brilliant!! Really appreciate your contribution.
Unfortunately though I have no way of testing this, so could you maybe send me a video of your tests? I will then test and make sure this pr doesn't break any of the other platforms (Technically it shouldn't but I'd rather not risk it) and then merge it.
Cheers and have a nice day :)
Chris
Neutrinos

Hello Chris,
You can find Videos here:
https://secure.convey.de/publish/leadsuccess/img_0353.mov
https://secure.convey.de/publish/leadsuccess/img_0354.mov


Reading a binary file throws an error as reading from unicode is not handled.

When requested to read from a binary, which has unicode, it results in ERROR: UnicodeError: invalid character index.
To reproduce, load the test file from Google https://drive.google.com/file/d/0B7XkCwpI5KDYNlNUTTlSS21pQmM/edit?usp=sharing

encoding attribute is there in the python version. That may not be exposed. Need to check.

I think there is a different reason for this. The original google-files seem to have a slightly different format and the parser for the binary file reads one byte too far.
Removing the read(f, UInt8) # new line here solves the issue (but presumably, the files created with this package can't be loaded in this case anymore)
I solved it by including the additional loading option :google to the existing :text and :binary where this read is removed.

PR #8 fixes this

I think there is a different reason for this. The original google-files seem to have a slightly different format and the parser for the binary file reads one byte too far.
Removing the read(f, UInt8) # new line here solves the issue (but presumably, the files created with this package can't be loaded in this case anymore)
I solved it by including the additional loading option :google to the existing :text and :binary where this read is removed.

would you please write the code of what you are saying I got confused honestly ,

so I did the implementation by my self, and I sharing it with you,
https://gist.github.com/alabrashJr/d71cf74bc9713bb0a5bb12ccd331a405


Issues with setting up browser_spellcheck - Need configuration help

I just installed django-tinymce==3.3.0 on Djang0=3.0.2 using python 3.6.9. I am only using tinymce in the Django admin. It all seems to be working except one part of the spell checker.
I am using the browser spell checker, so there is no plugin. Misspelled words are highlighted in the tinymce textarea by the browser and I can correct them with a right mouse click. The problem is the menu item 'spell check' and the toolbar 'spell check' buttons "crash" the application, in that the tinymce text area is grayed out and the three "wait for me" dots never go away. It seems to be looking for something (a plugin?) and I have to refresh the page to stop the waiting.
I tried the following:

Add spellchecker to the plugins in the settings, and no difference
Removing TINYMCE_SPELLCHECKER = True from the settings. The stopped the "crashing" (for want of a better word), but now I get an annoying warning message "The spelling service was not found...".

What are the correct settings to (1) either have the spell check buttons work with the browser spell checker, or (2) remove those buttons from the menu and toolbar so I don't get that annoying error message?
I am sure I have just misconfigured my setup regarding spell checking, but Google has not provided an answer to my question.
My configuration for tinymce (straight from the docs):
TINYMCE_DEFAULT_CONFIG = {
    "height": "320px",
    "width": "960px",
    "menubar": "file edit view insert format tools table help",
    "plugins": "advlist autolink lists link image charmap print preview anchor searchreplace visualblocks code"
    "fullscreen insertdatetime media table paste code help wordcount spellchecker",
    "toolbar": "undo redo | bold italic underline strikethrough | fontselect fontsizeselect formatselect | alignleft "
    "aligncenter alignright alignjustify | outdent indent |  numlist bullist checklist | forecolor "
    "backcolor casechange permanentpen formatpainter removeformat | pagebreak | charmap emoticons | "
    "fullscreen  preview save print | insertfile image media pageembed template link anchor codesample | "
    "a11ycheck ltr rtl | showcomments addcomment code",
    "custom_undo_redo_levels": 10,
    "browser_spellcheck": True,
    "contextmenu": False
}

Thanks!
Mark

I was also looking for some kinda solution on setting up the spellchecker. Did you get yours working ?

@claudep I think this issue can be closed. I cannot replicate the problem, it seems fixed.

Thanks for checking, trusting you!

@claudep I think this issue can be closed. I cannot replicate the problem, it seems fixed.

I had fixed it in the #373

Oh, of course, thanks for the reminder!


Artisan::command false positive

Larastan Version: 0.2.10
--level used: max

Description:
The $this context inside an Artisan callable is expected to be a Command, but larastan reports the following:
------ ------------------------------
  Line   routes/console.php
 ------ ------------------------------
  19     Undefined variable: $this
  19     Using $this outside a class.
 ------ ------------------------------

 [ERROR] Found 2 errors

Script php artisan code:analyse --level=max --paths="app,routes" handling the test event returned with error code 1

Laravel code where the issue was found:
routes/console.php:
Artisan::command('inspire', function () {
    $this->comment(Inspiring::quote());
})->describe('Display an inspiring quote');

It will not only be reported by larastan. I get this message on Scrutinizer CI as well.

I think the only way is to teach Larastan to handle
require base_path('routes/console.php'); in app/Console/Kernel.php

@szepeviktor Nah. I think there is a way of instruct PHPStan that $this corresponds to the class where the callback will be executed.

This area is hard, I don’t think there’s currently a way to fix this,
methods have no way of telling “this passed closure will be bound to class
X”.
On Mon, 24 Sep 2018 at 09:47, Nuno Maduro<EMAIL_ADDRESS>wrote:

@szepeviktor https://github.com/szepeviktor Nah. I think there is a way
of instruct PHPStan that $this corresponds to the class where the callback
will be executed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nunomaduro/larastan/issues/140#issuecomment-423897532,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGZuOSMMxtCJTKB4v2pdg0o-KEiZF9Yks5ueI33gaJpZM4WpaaX
.

--
Ondřej Mirtes

@ondrejmirtes Any plans of adding this to PHPStan? And can create a Feature Request on phpstan repository if you want.

I’m accepting suggestions because I don’t know how to do it, there’s
certainly no expression in phpDoc that would enable this.
The only thing I could do would be to turn off all errors about $this in
closures but that’s not always neccesary.
On Mon, 24 Sep 2018 at 10:03, Nuno Maduro<EMAIL_ADDRESS>wrote:

@ondrejmirtes https://github.com/ondrejmirtes Any plans of adding this
to PHPStan? And can create a Feature Request on phpstan repository if you
want.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nunomaduro/larastan/issues/140#issuecomment-423900794,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGZuHEwLyTknWjOrdvEejOz13l_Kgreks5ueJHpgaJpZM4WpaaX
.

--
Ondřej Mirtes

Maybe this kind of feature is too much of black magic. I don't think IDE's would ever autocomplete methods based on $this inside a callable... It'd be easier for everyone if every part of Laravel was IDE friendly (remove facades in favor of helper methods, the $this context change, etc).

FYI, I have the same problem with Laravel macros.

I’ll try to improve this and reduce false positives for a future version of
PHPStan
On Mon, 24 Sep 2018 at 15:05, Derk-Jan Hartman<EMAIL_ADDRESS>wrote:

FYI, I have the same problem with Laravel macros.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nunomaduro/larastan/issues/140#issuecomment-423967409,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGZuGf7nrHfQxSQBzulJ3REXgc_5SEiks5ueNh-gaJpZM4WpaaX
.

--
Ondřej Mirtes

Duplicated of #42

Is there actually an update on this? I am facing the same problem with a new Laravel 10 installation with Larastan at level 5:
 ------ ---------------------------
  Line   routes/console.php
 ------ ---------------------------
  18     Undefined variable: $this
 ------ ---------------------------

With routes/console.php:
17| Artisan::command('inspire', function () {
18|    $this->comment(Inspiring::quote());
19| })->purpose('Display an inspiring quote');

@eclipse313 You can subscribe to this issue #1110 for updates.
Meanwhile you can add /** @var $this YOUR_TYPE */ in the closure. Or ignore error.

Any reason that /** @var $this YOUR_TYPE */ in the closure will not work?


Delayed/repeat power effects

Added "delayedEffect", for power effects that start after a timer, and/or repeat
Added a vector of delayedEffects to each entity, which works with players and critters
I was testing logging out/zoning/dying while an effect was ticking down, and found that activation didn't properly check those as well. Oops! So I refactored checks for power range, to catch any null entity. Worked in every variation of player vs player vs critter I could think of.
Minor issue: the effects use the "character power" of the source to determine the strength of the effect, which isn't accessible without the entity. Ideally the strength would be calculated first. For now the effects end early, which was not as it was on live.

I pulled this down for some testing and ran into a segfault.
It appears to happen when you turn on auto-attack (right-click power) and target a Critter. While auto attacking continue to attack with other powers. With the delayed powers (charging) There is a small window where the Critter has died and is removed from the map, but the next auto attack fires anyway, resulting in:
[00:41:28] [log.slashcommand]Debug   : Sending 17 FloatingNumbers from 263 to 929
// charging text
[00:41:33] [log.slashcommand]Debug   : Sending 28 FloatingNumbers from 263 to 929
[00:41:33] Warning : "Entity 929 does not exist, or is not currently online."

Ok, turns out auto-attack was not checking if the target was dead either. So I added a few checks to see if a target is dead, might be redundant in some cases, but it works.
I looked into fade timing(#872) and it turns out we are not actually setting that? So when critters die, I start the fade timer, which seems to take around 15 seconds. They are unable to be affected by most powers during that timer.
Also added a get entity that returns the source if nothing is found(#871). Changed over my checks to this new function.
And split up the checkpowertimers() as discussed.

You're amazing Cyan 😍


Freeipa autodns mode - with user search filter

When using the freeipa autodns mode, the Cloudera Manager External Auth field for "LDAP User Search Filter" is being set to a ActiveDirectory type expression
Its being set to "(sAMAccountName={0})" but should be "(uid={0})"
In order to execute a seamless Base + PvC Control Plane + any DS install, this will need to be corrected, as the the CP gets this info from CM. and the DS's need LDAP working for its MagicSSO.
The confusing bit is that it looks like the CM settings are coming from:
https://github.com/cloudera-labs/cloudera.cluster/blob/main/roles/cloudera_manager/external_auth/templates/external_auth_configs.j2
and not at all from:
https://github.com/cloudera-labs/cloudera.cluster/blob/devel-pvc-update/roles/infrastructure/krb5_common/defaults/main.yml
Manual workarounds can be done, but this is actually an important area for proper automation (long term)

see pr/97


Overrides default value for dask-labextension

Fixes | Closes | Resolves #1326
Changes introduced in this PR:

Updates the default value of browserDashboardCheck from False to True
This will guarantee that every spawned profile has the fix for the dask-gateway and dask-labextension dashboard issue.

Types of changes
What types of changes does your PR introduce?
Put an x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features to not work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[x] Maintance related task.

Testing
Requires testing

[ ] Yes
[x] No

In case you checked yes, did you write tests?

[ ] Yes
[x] No

Further comments (optional)
This is a very simple addition to address the remaining needs of #1012

This is not blocked by #1321 but it's recommended to have that one merged first.

This was tested already with a GCP deployment.

Beautiful! Thanks a lot @viniciusdc :)


Capability to resize Images

It would be nice to have support to set a fixed height and width for an image.
Im using cacao::image::Image instance with  Image::with_data to set an image from bytes into
a view, but I don't seem to find a way to set image dimensions.
I have found the following snippet on StackOverflow on how could it be done:
- (NSImage *)imageResize:(NSImage*)anImage newSize:(NSSize)newSize {
    NSImage *sourceImage = anImage;
    [sourceImage setScalesWhenResized:YES];

    // Report an error if the source isn't a valid image
    if (![sourceImage isValid]){
        NSLog(@"Invalid Image");
    } else {
        NSImage *smallImage = [[NSImage alloc] initWithSize: newSize];
        [smallImage lockFocus];
        [sourceImage setSize: newSize];
        [[NSGraphicsContext currentContext] setImageInterpolation:NSImageInterpolationHigh];
        [sourceImage drawAtPoint:NSZeroPoint fromRect:CGRectMake(0, 0, newSize.width, newSize.height) operation:NSCompositingOperationCopy fraction:1.0];
        [smallImage unlockFocus];
        return smallImage;
    }
    return nil;
}

https://stackoverflow.com/questions/11949250/how-to-resize-nsimage

But given that Im not very familiar with Objective-C Im not pretty sure if there could be a simpler approach.
Thanks in advance!

Hmm, does using ResizeBehavior::Stretch not hit the behavior you're after?
https://github.com/ryanmcgrath/cacao/blob/e3bbb9366c8cf5a5474c5b134ae60e9641da3b7b/src/image/image.rs#L18-L32
(Alternatively, you could implement a custom draw closure - maybe that'd help?)

Thanks for the quick reply @ryanmcgrath!
Im trying with Image::draw this time.
        let img = Image::draw(DrawConfig {
            source: (512., 512.), // Original Image Size
            target: (64., 64.),   // Expected Size
            resize: ResizeBehavior::AspectFit, // Maintain Aspect Ratio
        }, |cg_rect, ctx| {
            // My understanding is that here I could attempt load my Image bytes into
            // a `CGImage` instance but I didn't found any `from_bytes` like method
            // in `core-graphics`
            ctx.draw_image(cg_rect, /* need a CGImage instance representing my file */);
            true
        });

Any suggestions?


Add new endpoint to fetch fork choice context from a client.

Fixes #231

Just a couple of quick comments: The API says justified_epoch but uses $ref: './misc.yaml#/Checkpoint'.
Prysm cannot know the justified checkpoints of the nodes, it does know the justified epoch though. Finalized checkpoint is fine cause we do not keep any node beyond finalized and all nodes are descendant of the same finalized checkpoint.

I feel like other store specifics are universal: the best justified checkpoint, the proposer boost root (perhaps even the previous proposer boost root),

Prysm cannot know the justified checkpoints of the nodes, it does know the justified epoch though. Finalized checkpoint is fine cause we do not keep any node beyond finalized and all nodes are descendant of the same finalized checkpoint.

The prysm structure from the issue suggested you had the checkpoint I thought?
message ForkChoiceResponse {
    // Latest justified checkpoint in forkchoice store.
    Checkpoint justified_checkpoint = 1;
    // Latest finalized checkpoint in forkchoice store.
    Checkpoint finalized_checkpoint = 2;

The prysm structure from the issue suggested you had the checkpoint I thought?
message ForkChoiceResponse {
    // Latest justified checkpoint in forkchoice store.
    Checkpoint justified_checkpoint = 1;
    // Latest finalized checkpoint in forkchoice store.
    Checkpoint finalized_checkpoint = 2;

That's the store's checkpoint, not the node's ones

I'll change that to epoch and we can always embed the extra in extra_data if we think we need it... @tbenr hopefully epoch is sufficient for what you were thinking...

I'm currently thinking about something like:
{
    "data_source": "teku", // self consistency, no API call to version required to get the context for interpreting extra_data
    "effective_ballance": "112228712638716", // effective balance for the current epoch
    "weight_mode": "NON_COMULATIVE",  // NON_COMULATIVE | COMULATIVE_TO_ROOT | COMULATIVE_TO_HEAD
    "fork_choice_store": [
        {
            "slot": "123",
            "block_root": "0x...",
            "parent_root": "0x...",
            "justified_epoch": "1",
            "finalized_epoch": "2",
            "execution_payload_root": "0x...",
            "validity": "VALID", // VAILD | INVALID | OPTIMISTIC ..
            "weight": "678976",
            "extra_data": {
                "teku_specific_field": "whathever"
            }
        }
    ]
}

@potuz does weight_mode make sense to you?

I assume the "cumulative-to-root" weight of a node  means the sum of all the  non-cummulative weights of every descendant (including itself)?  Except perhaps for proposer boost.
If that's the case then we're happy to include this but it's not necessary if this is only because of us: we track both the non-cumulative and the cumulative to root weights of nodes.
Cumulative to head seems to be the right thing for visualization. You can derive any one from any other, so if teams use majoritarily cumulative to root, we can easily adapt to that.
In addition to the list of nodes (that I would call something like fork_choice_nodes instead of store) I think it's useful to include store level information like the diverse justified/finalized checkpoints, the proposer boost root, the proposer boost score the head root, etc.
Also if possible it would be nicer to teams to avoid the extra_data field and just let them include other fields as long as they don't have name collision with the required ones. But I'm ignorant in API handling I don't know how intrusive this is to tooling

effective_ballance is something very useful IMO, for giving percentages to nodes\heads

I think it should be for the justified checkpoint which is what's used in computations and not the current epoch. It's easy for us to include this one, but not sure if it would be for other teams

I'm wondering if it's not worth to have timestamp as a mandatory field in all of the reorgs we've had from mainnet having the timestamp was instrumental to quickly assess that the cause was simply a late block

Teku doesn't currently track this and it's not a necessary thing to track (also there's a lot of variation in what you might want to track as a client - arrival time vs actual import time etc).  So I'd be keen to keep it as an optional field so we don't lock ourselves into tracking unnecessary data, but it could be provided if available. I'm not against tracking it in teku if it's useful for debugging just don't want to be locked into it forever by this API.
The other way to see if a block is late would be to request the fork choice state at 4s into the slot - if the block's not there then, it must have been late.  Teku also provides info in logs about late blocks etc so the data is available if needed.

The one big advantage of having the timestamp on the dump is when using @tbenr viewer: if you order the nodes by timestamp instead of by slot number, you get a much more clear picture of the forkchoice context in the event of reorgs. Before we added timestamps to our node, we would have to go to the logs for each slot individually to find out when the block was received. I do recognize that there's a difference between receival time, forkchoice insertion time, etc. But I think these are minor issues in front of the better UX

Yeah, I acknowledge it's useful, but I wouldn't want to require fork choice tracks it just for this API, hence I think it should be optional. Clients can then choose if its worth tracking or not and if they don't support it they just won't be able to sort by arrival time in the viewer.

I'm not sure whether we decided on finalized_checkpoint or finalized_epoch. The previous code had the label epoch, but the checkpoint structure... @tbenr this has the changes you sent me earlier I think, and lints fixed...


rosrun tf view_frames shows no tf being published

System Configuration
Please complete Your Configuration detail below. Refer to the BKC at Configuration.

Version
Your Configuration

Operating System
Ubuntu 16.04.1 LTS

Kernel
4.4.0-38-generic

Backend
Video4Linux

ROS
ROS Kinetic

ROS RealSense
1.4.0

librealsense
0.9.1 (although I used git checkout tags/stable so I would think this would say 0.9.2)

Camera Type-Firmware
R200 <IP_ADDRESS>

I'm launching two R200 cameras using the r200_nodelet_multiple_cameras.launch.  I modified the launch file as shown below to change the enable_tf parameter to true.  When I run the launch file, both cameras launch and I am getting all the data.  The ROS logs even shows that cameras should be publishing transforms (see terminal output below)  However, when I run rosrun tf view_frames, the output frames.pdf file says no tf data received. For some reason no tf is being published. Moreover, when I run rostopic echo /tf_static, I only see camera2 tf's.
r200_nodelet_multiple_cameras.launch
<!-- Sample launch file for using multiple RealSense R200 cameras -->
<launch>
  <arg name="manager" value="nodelet_manager" /> <!-- Single nodelet manager for all cameras -->
  <node pkg="nodelet" type="nodelet" name="$(arg manager)" args="manager" output="screen"/>

  <!-- MY MODS -->
  <param name="camera1/enable_pointcloud" type="bool" value="false" />
  <param name="camera1/enable_tf"         type="bool" value="true" />
  <param name="camera2/enable_pointcloud" type="bool" value="false" />
  <param name="camera2/enable_tf"         type="bool" value="true" />
  <!-- ======= -->

  <!-- User must include the .xml file for each camera with unique values for "camera" and
       either the "serial_no" or "usb_port_id" of the camera.
       "camera" should be a user friendly string that follows the ROS Names convention. -->
  <include file="$(find realsense_camera)/launch/includes/nodelet.launch.xml">
    <arg name="manager"      value="$(arg manager)" />
    <arg name="camera"       value="camera1" />
    <arg name="camera_type"  value="R200" /> <!-- Type of camera -->
    <arg name="serial_no"    value="2431002398" /> <!-- Note: Replace with actual serial number -->
    <arg name="usb_port_id"  value="" /> <!-- USB "Bus#-Port#" -->
  </include>

  <include file="$(find realsense_camera)/launch/includes/nodelet.launch.xml">
    <arg name="manager"      value="$(arg manager)" />
    <arg name="camera"       value="camera2" />
    <arg name="camera_type"  default="R200" /> <!-- Type of camera -->
    <arg name="serial_no"    value="2431018202" /> <!-- Note: Replace with actual serial number -->
    <arg name="usb_port_id"  value="" /> <!-- USB "Bus#-Port#" -->
  </include>
</launch>

Terminal output after running the above launch file
SUMMARY
========

PARAMETERS
 * /camera1/base_frame_id: camera1_link
 * /camera1/camera_type: R200
 * /camera1/color_frame_id: camera1_rgb_frame
 * /camera1/color_optical_frame_id: camera1_rgb_optic...
 * /camera1/depth_frame_id: camera1_depth_frame
 * /camera1/depth_optical_frame_id: camera1_depth_opt...
 * /camera1/enable_pointcloud: False
 * /camera1/enable_tf: True
 * /camera1/ir2_frame_id: camera1_ir2_frame
 * /camera1/ir_frame_id: camera1_ir_frame
 * /camera1/serial_no:<PHONE_NUMBER>
 * /camera1/usb_port_id:
 * /camera2/base_frame_id: camera2_link
 * /camera2/camera_type: R200
 * /camera2/color_frame_id: camera2_rgb_frame
 * /camera2/color_optical_frame_id: camera2_rgb_optic...
 * /camera2/depth_frame_id: camera2_depth_frame
 * /camera2/depth_optical_frame_id: camera2_depth_opt...
 * /camera2/enable_pointcloud: False
 * /camera2/enable_tf: True
 * /camera2/ir2_frame_id: camera2_ir2_frame
 * /camera2/ir_frame_id: camera2_ir_frame
 * /camera2/serial_no:<PHONE_NUMBER>
 * /camera2/usb_port_id:
 * /rosdistro: kinetic
 * /rosversion: 1.12.2

NODES
  /
    camera1 (nodelet/nodelet)
    camera2 (nodelet/nodelet)
    nodelet_manager (nodelet/nodelet)

auto-starting new master
process[master]: started with pid [9707]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 21dbc410-7ec2-11e6-8a74-001fc69bc102
process[rosout-1]: started with pid [9720]
started core service [/rosout]
process[nodelet_manager-2]: started with pid [9731]
process[camera1-3]: started with pid [9738]
process[camera2-4]: started with pid [9739]
[ INFO] [1474328294.635700141]: Initializing nodelet with 4 worker threads.
[ INFO] [1474328294.916099353]: /camera1 - Detected the following cameras:
				- Serial No:<PHONE_NUMBER>, USB Port ID: 2-3, Name: Intel RealSense R200, Firmware: <IP_ADDRESS>
				- Serial No:<PHONE_NUMBER>, USB Port ID: 2-4, Name: Intel RealSense R200, Firmware: <IP_ADDRESS>
[ INFO] [1474328294.916204645]: /camera1 - Connecting to camera with Serial No:<PHONE_NUMBER>, USB Port ID: 2-3
[ INFO] [1474328295.215844540]: /camera1 - Setting static camera options
[ INFO] [1474328295.223619262]: /camera1 - Enabling Color in preset mode
[ INFO] [1474328295.224040801]: /camera1 - Enabling Depth in preset mode
[ INFO] [1474328295.224279460]: /camera1 - Enabling IR in preset mode
[ INFO] [1474328295.224421585]: /camera1 - Enabling IR2 in preset mode
[ INFO] [1474328295.224537239]: /camera1 - Starting camera
[ INFO] [1474328295.256159378]: /camera1 - Publishing camera transforms
[ INFO] [1474328295.256235771]: /camera1 - Setting dynamic camera options
[ INFO] [1474328296.077065450]: /camera2 - Detected the following cameras:
				- Serial No:<PHONE_NUMBER>, USB Port ID: 2-3, Name: Intel RealSense R200, Firmware: <IP_ADDRESS>
				- Serial No:<PHONE_NUMBER>, USB Port ID: 2-4, Name: Intel RealSense R200, Firmware: <IP_ADDRESS>
[ INFO] [1474328296.077198963]: /camera2 - Connecting to camera with Serial No:<PHONE_NUMBER>, USB Port ID: 2-4
[ INFO] [1474328296.358673233]: /camera2 - Setting static camera options
[ INFO] [1474328296.365748123]: /camera2 - Enabling Color in preset mode
[ INFO] [1474328296.366053036]: /camera2 - Enabling Depth in preset mode
[ INFO] [1474328296.366201549]: /camera2 - Enabling IR in preset mode
[ INFO] [1474328296.366304975]: /camera2 - Enabling IR2 in preset mode
[ INFO] [1474328296.366402753]: /camera2 - Starting camera
[ INFO] [1474328296.398035491]: /camera2 - Publishing camera transforms
[ INFO] [1474328296.398113191]: /camera2 - Setting dynamic camera options

Hi @reaganlo, were you able to reproduce this issue?  Just checking in to see if there are any updates on this.

Hi @sinhau , I was able to reproduce the error. We will look into this and provide you an update.
As a workaround for multiple cameras, could you please do the following:

Create default launch files for each of the camera. I am attaching 2 samples.
E.g r200_nodelet_default_1.launch and r200_nodelet_default_2.launch.
Edit each of the launch files to have unique values for the arguments "manager", "camera" and "serial_no/usb_port_id".
Launch them in separate terminals.
Use rostopic echo /tf_static to view the transforms.  Note: rosrun tf view_frames does not work for static transforms.

r200_nodelet_default_1.launch.txt
r200_nodelet_default_2.launch.txt

@sinhau Yes, this can happen when you try to launch 2 cameras simultaneous because it leads 2 separate processes trying to access the librealsense "context" at the same time. Just like how you noticed, I would suggest you launch them one after the other.

It would be good for the drivers to not fail when accessing the "context" simultaneously.
@reaganlo are there plans on fixes this?

@sinhau and @tulku - I looked into this further and the root cause can be traced to this issue in the roscomm libraries (roscpp):https://github.com/ros/ros_comm/issues/146
Since that is unlikely to be fixed per their maintainers, the work-around of running from 2 launch files is the only option right now.

Hi! I agree that the solution is to have multiple launchfiles, however that option is not currently working. As soon as you try to start too nodes (via a launchfile, so they start at the same time) one of the nodes crashes. This is probably a different bug, I can open it tomorrow.

@tulku , yes I'm seeing the same issue.  Looks like this bug was introduced in one of the newer releases because launching multiple cameras via separate launch files was working for me on 1.4.0.  Thanks for opening this issue!

@mkhansen-intel I've created the issue that should be fixed before being able to use multiple nodelet managers. https://github.com/intel-ros/realsense/issues/156

Since the underlying issue is in roscpp and is not scheduled to be fixed, we're looking into a fix for this one that would fork a new process before calling the static transform publisher. We'll update this email with results.

fyi I'm also interested in having tf's for multiple cameras, so I'll be watching this.

Fixed in release 1.7.0
Use Dynamic Transforms by setting both 'enable_tf' and 'enable_tf_dynamic' to true.
https://github.com/intel-ros/realsense/releases/tag/1.7.0


Uninstall dyci

how to Uninstall dyci

https://github.com/DyCI/dyci-main/tree/master/Install
@Bintong see there


EMDLoss：取min问题

您好，请问一下，论文和代码中提到是将同一层的两个检测头数据中取loss较小的那个（min操作），不会造成一个头loss很大一个很小吗？

As described in the paper, A proposal generally need to infer 2 different detections, and there are 2 different combination choices among the detections and their targets, namely det_loss((B_0, G_0)) + det_loss((B_1, G_1))), det_loss((B_0, G_1)) + det_loss((B_1, G_0)), then a minimum operation performs on those losses to select the minimum one for updating parameters. But we hadn't noticed your hypothesis that a detection head may produce a loss largely higher than the other one. It can be attributed to the reason that a normalizer will scale the loss what is identical to the general detection loss functions.
However, what we have observed is that sometimes the first head will produce the majority of true positives while the second head infers the supplemental true positives, and sometimes the second one will predict the majority of true positives, and the first one supplements the rest of true positives. For the reason that the number of ground-truth for training the first head and the second head is different during the label assignment strategy, but the EMD loss has the property of permutation-invariance.

As described in the paper, A proposal generally need to infer 2 different detections, and there are 2 different combination choices among the detections and their targets, namely det_loss((B_0, G_0)) + det_loss((B_1, G_1))), det_loss((B_0, G_1)) + det_loss((B_1, G_0)), then a minimum operation performs on those losses to select the minimum one for updating parameters. But we hadn't noticed your hypothesis that a detection head may produce a loss largely higher than the other one. It can be attributed to the reason that a normalizer will scale the loss what is identical to the general detection loss functions.
However, what we have observed is that sometimes the first head will produce the majority of true positives while the second head infers the supplemental true positives, and sometimes the second one will predict the majority of true positives, and the first one supplements the rest of true positives. For the reason that the number of ground-truth for training the first head and the second head is different during the label assignment strategy, but the EMD loss has the property of permutation-invariance.

As described in the paper, A proposal generally need to infer 2 different detections, and there are 2 different combination choices among the detections and their targets, namely det_loss((B_0, G_0)) + det_loss((B_1, G_1))), det_loss((B_0, G_1)) + det_loss((B_1, G_0)), then a minimum operation performs on those losses to select the minimum one for updating parameters. But we hadn't noticed your hypothesis that a detection head may produce a loss largely higher than the other one. It can be attributed to the reason that a normalizer will scale the loss what is identical to the general detection loss functions.
However, what we have observed is that sometimes the first head will produce the majority of true positives while the second head infers the supplemental true positives, and sometimes the second one will predict the majority of true positives, and the first one supplements the rest of true positives. For the reason that the number of ground-truth for training the first head and the second head is different during the label assignment strategy, but the EMD loss has the property of permutation-invariance.

As described in the paper, A proposal generally need to infer 2 different detections, and there are 2 different combination choices among the detections and their targets, namely det_loss((B_0, G_0)) + det_loss((B_1, G_1))), det_loss((B_0, G_1)) + det_loss((B_1, G_0)), then a minimum operation performs on those losses to select the minimum one for updating parameters. But we hadn't noticed your hypothesis that a detection head may produce a loss largely higher than the other one. It can be attributed to the reason that a normalizer will scale the loss what is identical to the general detection loss functions.
However, what we have observed is that sometimes the first head will produce the majority of true positives while the second head infers the supplemental true positives, and sometimes the second one will predict the majority of true positives, and the first one supplements the rest of true positives. For the reason that the number of ground-truth for training the first head and the second head is different during the label assignment strategy, but the EMD loss has the property of permutation-invariance.

As described in the paper, A proposal generally need to infer 2 different detections, and there are 2 different combination choices among the detections and their targets, namely det_loss((B_0, G_0)) + det_loss((B_1, G_1))), det_loss((B_0, G_1)) + det_loss((B_1, G_0)), then a minimum operation performs on those losses to select the minimum one for updating parameters. But we hadn't noticed your hypothesis that a detection head may produce a loss largely higher than the other one. It can be attributed to the reason that a normalizer will scale the loss what is identical to the general detection loss functions.
However, what we have observed is that sometimes the first head will produce the majority of true positives while the second head infers the supplemental true positives, and sometimes the second one will predict the majority of true positives, and the first one supplements the rest of true positives. For the reason that the number of ground-truth for training the first head and the second head is different during the label assignment strategy, but the EMD loss has the property of permutation-invariance.

所以关键部分就是如何分配G_0和G_1我看您是通过iou评分来划分的, G_0为iou评分最高的gt框而G_1为iou次高的gt框, 但是在yolov5系列算法中, gt框是直接通过wh的比值来确定去留的, 直观的分出两类gt。我还有一个疑问， 直接通过iou来划分G_0和G_1的话是否也会存在同一个label同时被两个头预测的情况呢?我想此系统在Deepsort上工作, 重叠的检测框会带给我困扰

在同类遮挡的情况下,两个检测头会预测相同的label,这种情况下2个检测头预测的label虽然相同,但是检测框分别对应2个不同的同类物体.如果不存在遮挡情况,那么只会有一个检测头预测一个label,剩下的一个检测头对应的label是背景;

在同类遮挡的情况下,两个检测头会预测相同的label,这种情况下2个检测头预测的label虽然相同,但是检测框分别对应2个不同的同类物体.如果不存在遮挡情况,那么只会有一个检测头预测一个label,剩下的一个检测头对应的label是背景;

但是按照setNMS的机制如果同一层的一个框被选中, 另一个背景框岂不是也会被强制复活?

所以在进行set NMS的时候会卡一个置信度阈值0.05,在一般情况下另一个背景框会被移除.如果背景框在卡阈值阶段无法被移除,最后也只能被强行复活成为FP.所以我们设计了refinement module.但这种情况一般很少出现.

所以在进行set NMS的时候会卡一个置信度阈值0.05,在一般情况下另一个背景框会被移除.如果背景框在卡阈值阶段无法被移除,最后也只能被强行复活成为FP.所以我们设计了refinement module.但这种情况一般很少出现.

了解了，十分感谢您解答我的疑问，谢谢

如果一个proposal的label assignment按照这种分配方式的话，会不会存在一种潜在的问题呢？就是proposal的第一部分的特征和输出结果其实与GT2相关度比较高，但是分给他的label是GT1，从而影响了模型训练

如果一个proposal的label assignment按照这种分配方式的话，会不会存在一种潜在的问题呢？就是proposal的第一部分的特征和输出结果其实与GT2相关度比较高，但是分给他的label是GT1，从而影响了模型训练

我研究过原文RetinaNet实现，他是通过在原有的iou top1生成正样本代码修改为top1作为gt1，top2作为gt2，可是我用同样的方法在yolo上出现了无法收敛的情况
从 Windows 版邮件发送
发件人: Yang
发送时间: 2022年5月3日 15:59
收件人: Purkialo/CrowdDet
抄送: Eagle104fred; Author
主题: Re: [Purkialo/CrowdDet] EMDLoss：取min问题 (Issue #75)
如果一个proposal的label assignment按照这种分配方式的话，会不会存在一种潜在的问题呢？就是proposal的第一部分的特征和输出结果其实与GT2相关度比较高，但是分给他的label是GT1，从而影响了模型训练
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Placeholder for function 3

Function 2: A closer look
Suggested actions that this function will perform:

Generates EDA visualizations of the a specific variable or pair of variables. (eg the most highly correlated dependent variable in relation to the independent variable)
Generates analysis on those variables and highlights key information

Some thoughts to discuss:
Since we have already calculated the correlation coefficients from function 2, I guess we could input a threshold for the correlation coefficients. For example, if we say coeff = 0.5, this function 3 will plot each pair of variables that has coeff larger than 0.5 or smaller than -0.5.
For those pairs containing high collinearity, we might plot linear regression line plot on top of them? For example, like this?

This is also a good idea, as long as we are not repeating ourselves from function 2 and if it could add value to the analysis.

Definitely an interesting idea to add the correlation threshold.
For categorical columns, we can look at layered histograms/stacked bar charts.

So I think this one we just need to pick a different visualization from function 2. Let me know which one you are thinking

I like Luming's idea on adding the regression line on top of it. We could also add 95% confidence intervals.

Function feature is completed.


Use a unique key when creating  components so we reuse the corr…

…ect webview instance to prevent mismatching between webview page and  page. r=linclark
Currently, create two tabs, let's say "a" and "b". Closing "a", and mouse over some links on "b", and the setPageDetails calls are using id "a", which throws in our reducer assertions. We were reusing the same page instance that "a" was using for "b", resulting in this error.

Ah yes, I had noticed this key issue earlier. I expected it to have an impact on performance. I didn't realize it would have an impact on the functionality though... are we depending on the key somewhere in our code?

Actually, I see where the issue would be (in the ref that it's holding on to). LGTM!


Fixed table.set('selection'), which did not set the cached value.

Fixes table.set('selection', whatever). The passed val should be returned. As written, when this.get('selection') is called, it simply returns the already-cached value. The returned value is then written to the cache, resulting in a no-op. The selection is not set.

:+1:

Thank you for immediate attention!


fix: fix installation instruction

/azp run

Codecov Report

Merging #1268 (8fcb4dc) into master (d0406c8) will decrease coverage by 79.67%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #1268       +/-   ##
==========================================
- Coverage   83.06%   3.38%   -79.68%
==========================================
  Files         300     248       -52
  Lines       13699   11984     -1715
  Branches      660     660
==========================================
- Hits        11379     406    -10973
- Misses       2320   11578     +9258

Impacted Files
Coverage Δ

...m/src/main/scala/com/microsoft/lightgbm/SWIG.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...ain/scala/org/apache/spark/ml/param/MapParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/scala/org/apache/spark/ml/param/UDPyFParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...cala/org/apache/spark/ml/NamespaceInjections.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...cala/org/apache/spark/ml/param/DataTypeParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...ala/org/apache/spark/ml/param/ByteArrayParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...ala/org/apache/spark/ml/param/EvaluatorParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...la/org/apache/spark/ml/param/ParamSpaceParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...la/org/apache/spark/ml/param/TypedArrayParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...a/com/microsoft/azure/synapse/ml/stages/udfs.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 279 more

Continue to review full report at Codecov.

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


Fix annotation for launcher property

Fixes #15364

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.


Space

Hi, there shouldn't be a space between - and HomeSiteUrl in Set-SPOHomeSite - HomeSiteUrl <siteUrl>.

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

ID: 4d251803-3835-ca8f-f664-1a056496fbbe
Version Independent ID: 58bb7de2-7f44-d53d-8026-0f5023dcd9f9
Content: Set up a home site for your organization - SharePoint Online
Content Source: SharePoint/SharePointOnline/home-site.md
Service: sharepoint-online
GitHub Login: @kaarins
Microsoft Alias: kaarins

Thanks, @lordherbert. Fixed in PR 1561 by expiscornovus.


KAFKA-4554: Fix ReplicaBuffer.verifyChecksum to use iterators instead of iterables

This was changed in b58b6a1bef0 and caused the ReplicaVerificationToolTest.test_replica_lags
system test to start failing.
I also added a unit test and a couple of other minor clean-ups.

Ran the failing system test and it passed:
https://jenkins.confluent.io/job/system-test-kafka-branch-builder/635/
Started a full system tests build just in case, but we probably don't need to block on it:
https://jenkins.confluent.io/job/system-test-kafka-branch-builder-2/169/

JDK 8 and Scala 2.11 failed due to a test that is known to fail transiently:
kafka.producer.ProducerTest.testAsyncSendCanCorrectlyFailWithTimeout

LGTM. Thanks for the fix!


Strange filtering of data

Hey Guys,
not sure if this should go in the PowerBI support, or here, as it's specific to the Microsoft Azure Consumption Insights reports.  Let me know if there's a better place to feedback on this specific content pack.
In the Lifetime based graphs, I'm seeing data from 2015-07 to 2018-04.
In the selected months based graphs, I'm seeing data from 2017-09 to 2018-06.
Why is the end date different?
How do I change the filter on "selected months", as when I go to the sub-report and try to filter it, the only months available are 2017-09 to 2018-06.
Why does lifetime not have 2018-05 and 2018-06?
I suspect the odd end dates are due to our Enterprise Agreement renewing (for another three years) at the beginning of July this year, but does that mean if I go an create a new instance of this content pack, with the new account code, it wont have all the data in the existing content pack?  Is this going to happen every three years?
Our EA has three departments assigned - three Azure tenants - it'd be handy to have a summary that gives me the annual spend (based on our financial year) for each department, so that we can do internal charging...
Thanks
Craig

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

ID: d2d95443-afbf-fadd-6932-1edef039548f
Version Independent ID: b5a9d263-4b72-e566-a53f-5c5e0bebafae
Content: Connect to Microsoft Azure Consumption Insights with Power BI - Power BI
Content Source: powerbi-docs/service-connect-to-azure-consumption-insights.md
Service: powerbi
GitHub Login: @SarinaJoan
Microsoft Alias: sarinas

Thanks for your comment, @CraigHumphrey. I think you're right -- this looks like a support request rather than documentation feedback. You might find a solution in the Power BI Community, found at https://community.powerbi.com. If not, you can get support by going to https://support.powerbi.com.


Windows packaging

Windows users usually expect an installer. I believe MSI is the right technology, not a Windows Store program. I'm not particularly knowledgable, so if anyone has insight here, I'd appreciate it.
(Blocked on #47)

Automation works as of 8a7a7c2


[CM-136] Improvements added dep, linter, drone

Added the vendor folder with all the dependencies  and the files Gopkg.
Run go fmt
Added the pipeline of drone with the follow checks:

dep check -skip-lock
Check if the code is formatted
Run the tests
Run the linter golangci-lint run

After I correct some problem reported by the linter

 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.Mattia Bertorello seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add banner to arbitrum sepolia testnet

This enhancement adds the Arbitrum Sepolia testnet banner to be displayed when users are connected.

we really appreciate your contribution to this @guilhermebins ✨
although the issue mentions adding the banner for arbitrum sepolia, I'd advise relying on the viem's chain definition which included a testnet flag for each chain.
the condition would be like this then:
 const isConnectedToTestnet = () => chain?.testnet;

@guilhermebins thank you, looks sharp 📐✨


Create email notifications service

Still some things TODO:
Format emails nicely
Send notifications when person sends a message or contact request


Doesn't work with extended tsconfig file.

Hey, when I use "extends" in tsconfig, this plugin doesn't seem to pick it up and just gives No type errors found, however the extended tsconfig is definitely picked up in the ts-loader config.
Do you know why this might be?
tsconfig.json
{
  "extends": "../../../tsconfig.json",
  "exclude": [
    "node_modules",
    "packages/frontend"
  ]
}

webpack.config.js
HappyPack({
      id: 'ts',
      threads: 2,
      loaders: [
        {
          path: 'babel-loader'
        },
        {
          path: 'ts-loader',
          query: {
            happyPackMode: true,
            configFile: path.resolve(__dirname, 'tsconfig.json')
          }
        }
      ]
    }),
    new ForkTsCheckerWebpackPlugin(
      {
        tslint: true,
        tsconfig: path.resolve(__dirname, 'tsconfig.json')
      }
    ),

Oddly, it also doesn't lint anything when I refer to the extended tsconfig but does when I use the base one.

Are there any plans to fix this or is there any workaround?

Just checked the latest version 0.5.2 and it seems to be fixed now!


Recommended way to debug in VSCode during plugin development?

I can add new NativeScript launch configurations for npm start like this.
        {
            "command": "npm start",
            "name": "Run npm start",
            "request": "launch",
            "type": "node-terminal",
        },
        {
            "command": "npm start apps.demo-angular.android",
            "name": "Demo Angular Android",
            "request": "launch",
            "type": "node-terminal",
        },
        {
            "command": "npm start apps.demo-angular.ios",
            "name": "Demo Angular iOS",
            "request": "launch",
            "type": "node-terminal",
        }

But then all breakpoints I set are unbound and grayed out.
If I start the application via the interactive 'npm start' and try to attach a debugger (via "Attach on iOS") I get this result:
The application undefined is not installed on device with identifier 7ED7FC41-801D-46D3-A72B-915CC66884E5.
Am I missing something here?
Thanks

It turned out, I added the launch configuration at the wrong place.
The auto generated launch.json was placed inside the plugin workspace.
pluginworkspace
  .vscode
    launch.json

In order to use it with the demo app I had to move it. In the correct demo directory.
pluginworkspace
  apps
    demo-angular
      .vscode
        launch.json

Lesson learned, now it works as expected.


Game simulation on mobile is resetting too much

Leaves empty space a lot. Happens on mobile browsers when scrolling top/down

Should be fixed with 7c0056716b330290523a0492555d5cb20cf903de . Needs testing on actual devices

Fixed bug of getting canvas.width instead of actual canva.clientWidth in 934a5fe


Font Pairing Logic for Resnet

Hey great work!
I am using resnet where in my feature vector i dont get any non-negatives due to RELU layer.
What do you propose for Font Pairing contrast similarity here?
Regards,
Anand

hm.. I could be misunderstanding something, but the vectors should get centered at the origin when you do PCA


Hangs on logging in....

Install seemed to go fine. Added test URL in and launched, browser opens and logs in and proceeds to test URL  item and stops. Times out with this:
Logging in...
Traceback (most recent call last):
  File "C:\Python\Scripts\3b-bot-script.py", line 33, in <module>
    sys.exit(load_entry_point('3b-bot==0.1.0b1', 'console_scripts', '3b-bot')())
  File "c:\python\lib\site-packages\best_buy_bullet_bot\command_line.py", line 90, in main
    ops[args.COMMAND][0]()
  File "c:\python\lib\site-packages\best_buy_bullet_bot\tracker.py", line 329, in start
    login_cookies_list, predicted_prices, user_agent = login(email, password, urls)
  File "c:\python\lib\site-packages\best_buy_bullet_bot\auto_checkout.py", line 85, in login
    WebDriverWait(driver, USER_TAKEOVER)
  File "c:\python\lib\site-packages\selenium\webdriver\support\wait.py", line 80, in until
    raise TimeoutException(message, screen, stacktrace)
selenium.common.exceptions.TimeoutException: Message:

If you don't mind, can you send me the URL you added?

Sure, I used 2:
https://www.bestbuy.com/site/pokemon-pokemon-tcg-first-partner-collectors-binder/6450052.p?skuId=6450052
https://www.bestbuy.com/site/nvidia-geforce-rtx-nvlink-bridge-for-3090-cards-space-gray/6441554.p?skuId=6441554

I have updated the source code to solve your issue. Run the following to update to the newer version. Note you may need to reenter your URLs after the update.
pip install --upgrade git+https://github.com/LeonShams/BestBuyBulletBot.git

Please close the issue if this solves your problem.

Close! For tracking purposes would you like this post closed and a new one with the next issue? :)

Yes!


feat: Add fitToContent and animate to scrollToContent

This PR relates to https://github.com/excalidraw/excalidraw/issues/6283

[x] Add feature fitToContent as option to scrollToContent
[x] Add tests for fitToContent
[x] Add feature animate as option to  scrollToContent
[x] Add tests for animate
[ ] Update Documentation

Hey @typehorror, thanks for the PR and apologies for the delay! Looks very well written and also contains tests! ❤
Checking the behavior, it's working really well.
The worry I had was about performance/smoothness with more elements on the scene, and there's indeed one issue around fitToContent. Every time we change zoom, it will bust the elements canvas cache (in renderElement.ts), unlike simple movement around the canvas — movement could still be an issue if the scrolled-to-elements weren't previously rendered, or were rendered on a different zoom level, but it's less likely to happen as opposed to zooming outright.
So, when fitToContent is true, I'd suggest to zoom to the target zoom level in the first frame instead of animating it.
Does that make sense?

That makes a lot of sense, I'm not familiar with the intricacies of rendering on canvas but I can see why scrolling would be much cheaper than zooming... I'll get that adjusted.

Hey @Fanoflix ,
this is just my opinion but in general you want to go with the most expressive form. Here, I'm using startTime === undefined even if it is overkill because it also tells part of the story (startTime will be undefined) which helps the reader understand the code. Having !startTime would imply that the variable could be false, 0, null... which slightly murkies the water. The improvement is not game changing on it's own, but the accumulation of small improvements is.

@typehorror Thanks for the reply. "Most expressive form" is a great way to put it. Thanks :)

@dwelle This is ready for review, let me know if you have any question

@typehorror sorry for the delay!
I've pushed some tweaks, namely:

changing the easing function because the old one was having issues around the ending values (there was a jank).
I'm also canceling in-progress animation if user starts panning or the scrollToContent is called in the middle.
zoom to canvas center on initial anim instead of current scroll position
added opts.duration customiztion
updated docs

Thanks again for the PR! ❤


[WIP] Clean up (Cabal) package

See #20.

@jsl What do you think?
The executable is now in the app directory and has the library as a build dependency.
One thing I don't like is that I had to expose System.Hapistrano.Types because the test suite uses it. Instead, we could add the src directory to the hs-source-dirs of the test suite or re-export System.Hapistrano.Types in System.Hapistrano to keep only one exposed module. I think I like the latter, re-exporting.

LGTM!

@jsl I'll merge once the checks are complete. I re-exported ReleaseFormat(..) in System.Hapistrano, that's the only type used in the tests right now.


Windows/DOS end of line causes pgfutter to treat all data as one row

Great software and very helpful! Also withstands the csv-spectrum tests. Thumbs up!
I just identified an issue with the line endings. If the CSV file has Windows EOLs (and, for that matter, I would think legacy Mac ones too), then pgfutter treats it as containing one row only - basically the header. Thus it throws the weirdest of errors with some otherwise valid (in the Apple/Microsoft worlds) files.
To test that for yourself, you could use one of these files: file1, file2.
For those users having the same issue, a temporary fix would be to [programmatically] pass the file through a Bash script which replaces the EOLs. Good cross platform instructions here.

I realised that a quick example could be helpful:
What the file looks like on Win:
permalink,company,numEmps,category,city,state,fundedDate,raisedAmt,raisedCurrency,round
lifelock,LifeLock,,web,Tempe,AZ,1-May-07,6850000,USD,b
lifelock,LifeLock,,web,Tempe,AZ,1-Oct-06,6000000,USD,a

What vim on Linux sees:
permalink,company,numEmps,category,city,state,fundedDate,raisedAmt,raisedCurrency,round^Mlifelock,LifeLock,,web,Tempe,AZ,1-May-07,6850000,USD,b^Mlifelock,LifeLock,,web,Tempe,AZ,1-Oct-06,6000000,USD,a

Notice the ^M character in the second example.

Both of those files are \r line endings only, which the Go developers have flatly refused to support.
There is a Go package which converts \r line endings into standard \n line endings, which pgfutter could use to convert files after a short detection routine.
\r\n files load just fine. You can test it using this file from Microsoft.

I know support this by using a different csv package #51.
Use the --excel arg for csv mode to support this use case in v1.2


[SPARK-9964] [PySpark] [SQL] PySpark DataFrameReader accept RDD of String for JSON

PySpark DataFrameReader should could accept an RDD of Strings (like the Scala version does) for JSON, rather than only taking a path.
If this PR is merged, it should be duplicated to cover the other input types (not just JSON).

Merged build triggered.

Merged build started.

Test build #41583 has started for   PR 8444 at commit 127717a.

Test build #41583 has finished for   PR 8444 at commit 127717a.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Merged build triggered.

Merged build started.

Test build #41589 has started for   PR 8444 at commit f160ec4.

Test build #41589 has finished for   PR 8444 at commit f160ec4.

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

Merged build finished. Test PASSed.

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

I don't think we should rename the name of the parameter since it could break compatibility. How about just changing the description?

Merged build triggered.

Merged build started.

Test build #41611 has started for   PR 8444 at commit 3842a6b.

Test build #41611 has finished for   PR 8444 at commit 3842a6b.

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

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

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #41668 has started for   PR 8444 at commit b2d072d.

Test build #41668 has finished for   PR 8444 at commit b2d072d.

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

Merged build finished. Test PASSed.

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

Thanks - I've merged this in master.


Separate Arduino example from the rest.

See https://arduino.github.io/arduino-cli/0.33/library-specification/#library-examples.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.02%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
68

Relevant Lines:
68

💛  - Coveralls


potential memory leak: elements using delay may not be released from internal delayedElements store

Velocity permanently hangs onto DOM elements via its internal State.delayedElements store if "stop"/"finish" is not explicitly called before you remove an element from the DOM, even after velocity has completed. This causes growth of non-GCable detached nodes which can really add up over time depending on your use case.
Demo fiddle here.

open chrome dev tools and go to Timeline tab; check "memory" in capture settings
press record button
press "makes stuff" button for a few rounds, e.g. 10 times
press trashcan button (collect garbage) in Timeline.
Stop recording

Node count stays high after GC.
Rerun above steps after uncommenting marked line in makestuff(), and observe node count returns to baseline after GC.

I really need to have a look into how it does this - unifying pause and delay etc might be worth doing to simplify the code and remove potential leaks like this.

In V2 delay was rewritten to be a property on a running animation, there is on separate queue for it


 Valid RAML file: file.raml". The only thing that I can think of is that there may be tabs on or around line 29 in your file and when you copy/pasted it, it converted those tabs into spaces which explains why it works for me...

Yeah the copy/paste messed up some spacing.
I also removed some duplicate collections without much luck.
I get the same  InvalidSecuritySchemeError error with the raml from ramses-example.
Can you paste your pip list?

attrs==15.1.0
blinker==1.4
click==6.2
cryptacular==1.4.1
elasticsearch==2.1.0
inflection==0.3.1
jsonref==0.1
markdown2==2.3.0
mongoengine==0.9.0
nefertari==0.6.1
nefertari-mongodb==0.4.1
nefertari-sqla==0.4.1
Paste==2.0.2
PasteDeploy==1.5.2
pbkdf2==1.3
psycopg2==2.6.1
pymongo==2.8
pyramid==1.5.7
pyramid-sqlalchemy==1.4
pyramid-tm==0.12.1
python-dateutil==2.4.2
PyYAML==3.11
ramlfications==0.1.8
ramses==0.5.1
-e git+git@github.com:brandicted/ramses-example.git@bbc1af0f8dbd74487972124b35a5dc6d01498c20#egg=ramses_example-develop
repoze.lru==0.6
requests==2.8.1
simplejson==3.8.1
six==1.10.0
SQLAlchemy==1.0.9
SQLAlchemy-Utils==0.31.3
Tempita==0.5.2
termcolor==1.1.0
transaction==1.4.4
translationstring==1.3
urllib3==1.12
venusian==1.0
waitress==0.8.9
WebOb==1.5.1
wheel==0.24.0
xmltodict==0.9.2
zope.deprecation==4.1.2
zope.dottedname==4.1.0
zope.interface==4.1.3
zope.sqlalchemy==0.7.6

Oh, I get that error too, quick fix:
...
    - x_token_auth:
        description: Authorization header token policy
        type: x-ApiKey
        settings:
            foo: bar
...

Oh right, got it, thanks for that!
Will implement those changes and report back.

Yeah the errors were due to invalid RAML v8.
All fixed and wsgi server is now loading.

Thanks the update!