[Event Request] Table 263 "Intrastat Jnl. Line" - OnBeforeTestfieldOnModify()

Dear Microsoft,
For table "Intrastat Jnl. Line", we like to have the ability to apply our own TESTFIELD and skip IntrastatJnlBatch.TESTFIELD(Reported,FALSE) for trigger OnModify().
Therefore we like to see the following publisher added:
trigger OnModify()
var
    IsHandled : boolean; //<< New local variable
begin
    IntrastatJnlBatch.Get("Journal Template Name", "Journal Batch Name");
//>> Start publisher
    OnBeforeTestfieldOnModify(Rec,xRec,IntrastatJnlBatch,IsHandled);
    if not IsHandled then
//>> End publisher
        IntrastatJnlBatch.TestField(Reported, false);
end;

New Publisher
[IntegrationEvent(false,false)]
local procedure OnBeforeTestfieldOnModify(IntrastatJnlLine : record "Intrastat Jnl. Line";xIntrastatJnlLine : record "Intrastat Jnl. Line"; IntrastatJnlBatch: Record "Intrastat Jnl. Batch";var IsHandled : boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Make a datapack only version

Would like to use the wordgen with structures and biome boundaries on an server running on papermc, is it possible to make a datapack out of this?

If you are just looking for a datapack to generate a void world with structure and biome bounding boxes, use this https://modrinth.com/datapack/skyblock-void-worldgen
If you want this mod, with all of its features, as a datapack that is sadly not possible because not all of the features of this mod are able to be put into a datapack.

Thanks for the hint! Sadly that linked datapack does not generate all structures that exist in minecraft but only a few selected.

You might be able to edit
get_empty_biomes.py and
get_empty_structures.py
and run generate.py to get the biomes & structures you want.

You might be able to edit get_empty_biomes.py and get_empty_structures.py and run generate.py to get the biomes & structures you want.

Thanks for pointing that out, but sadly i never created a plugin or datapack by myself. So no Idea what to change there.

It's outside of the scope of this project, because the worldgen in CarpetSkyAdditions isn't in datapack format, it's coded using Fabric API.


Property missing in type 'Readonly'

TypeScript Version:  2.6.1, 2.7.0-dev.20171031
(verified working in 2.5.3)
Code
declare var anything: Readonly<any>
let x: Readonly<{ p: number }> // or let x: { p: number }
x = anything

(tested on TS Playground)
Expected behavior:
No errors
Actual behavior:
Type 'Readonly<any>' is not assignable to type 'Readonly<{ p: number; }>'.
Property 'p' is missing in type 'Readonly<any>'.

This is particularly painful because we are converting a JS/React codebase to typescript, so some prop types are declared as any, and thus become Readonly<any>

Readonly is a mapped type. it is a type transformation that happens on the input, in this case any. so Readonly<any> is equivalent to { readonly [x: string]: any };. that is not assignable to {readonly p: number}, since this type has a required property p. Can you share more context, maybe there is something else we can do here to address the issues you are running into.

Sure! Thanks for looking at this.
To give some context, we're using React with Redux, and have some containers (i.e. Redux state-injectors) that are Typescript and some wrapped components that are Javascript. We have a .d.ts definition file for the wrapped Javascript components, that declare the components as React.Component<any, any>.
Here's some copy-pastable sample code that works in the playground, and gives the error in 2.6.1 but not 2.5.3.
// react.ts
// Massively simplified version of react
class Component<P> {
    props: Readonly<P>;
    constructor(props?: P) {}
}
interface ComponentClass<P = {}> {
    new(props?: P, context?: any): Component<P>
}

// react-redux.ts
// Massively simplified version of redux-react's connect
declare var connect: (component: ComponentClass<OwnProps & StateProps>) => ComponentClass<OwnProps>;

// my-component.js
// Declaration of a Javascript "React" component, that hasn't been typed yet
class MyComponent extends Component<any> {};

// my-container.ts
// Uses react-redux's connect function
interface OwnProps {
    a: string
}
interface StateProps {
    b: number
}

let container = connect(MyComponent)

This results in the error:
TS2345: Argument of type 'typeof MyComponent' is not assignable to parameter of type 'ComponentClass<OwnProps & StateProps>'.
  Type 'MyComponent' is not assignable to type 'Component<OwnProps & StateProps>'.
    Types of property 'props' are incompatible.
      Type 'Readonly<any>' is not assignable to type 'Readonly<OwnProps & StateProps>'.
        Property 'a' is missing in type 'Readonly<any>'.

I had a similar issue and upgrading to a more recent react release (15.6) fixed it for me.


⚠ Bofrost.es has degraded performance

In 5e75d60, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1470 ms

Resolved: Bofrost.es performance has improved in 0253ccf after 29 minutes.


cfn-lint shows W1020 Fn::Sub isn't needed on Serverless LayerVersion property LayerName when a Variable is actually present

cfn-lint version: 0.20.1
cfn-lint shows W1020 Fn::Sub isn't needed on Serverless LayerVersion property LayerName when a Variable is actually present in the layerName String of the intrinsic function Sub
Please provide as much information as possible:
sample resource:
APICommonCodeLayer:
    Type: 'AWS::Serverless::LayerVersion'
    Properties:
      Description: API common libraries
      LayerName:
        Fn::Sub: 'api-common-code-layer-${Environment}'
      ContentUri: api/common
      CompatibleRuntimes:
        - nodejs8.10
      RetentionPolicy: Retain

Where Environment is a Paramater with the following definition:
Environment:
    AllowedValues:
      - Dev
      - Qa
      - Staging
      - Mirror
      - Prod
    ConstraintDescription: You must specify a valid EnvironmentValue
    Default: Dev
    Description: Environment for to Deploy to
    Type: String

This only seems to affect LayerVersions as other resources proceed to not return the warning when using Fn::Sub in their names, even other AWS::Serverless resources.
Sample Template:
AWSTemplateFormatVersion: '2010-09-09'
Transform: 'AWS::Serverless-2016-10-31'
Description: SampleTemplate
Parameters:
  Environment:
    Type: String
    AllowedValues:
      - Dev
      - Qa
      - Staging
      - Mirror
      - Prod
    ConstraintDescription: You must specify a valid EnvironmentValue
    Default: Dev
    Description: Environment for to Deploy to
Resources:
  APICommonCodeLayer:
    Type: 'AWS::Serverless::LayerVersion'
    Properties:
      Description: API common libraries
      LayerName:
        Fn::Sub: 'api-common-code-layer-${Environment}'
      ContentUri: api/common
      CompatibleRuntimes:
        - nodejs8.10
      RetentionPolicy: Retain

I believe this bug is back on the newer version of  cfn-lint.
            Resource:  !Sub '{{resolve:ssm:/mock/lambda/my-resource/arn}}'
The line above work just fine  on previous version but with the latest version it gives me:
'Fn::Sub' isn't needed because there are no variables

I believe this bug is back on the newer version of cfn-lint.
 Resource: !Sub '{{resolve:ssm:/mock/lambda/my-resource/arn}}'
The line above work just fine on previous version but with the latest version it gives me:
'Fn::Sub' isn't needed because there are no variables

Fix in v1.6.0

Awesome, it works now, thank you

@pjlowrey looking into this.

@pjlowrey may need some more details on this one.  I can't replicate it.
The first thing this rule does is look for the SAM transform. We look at the pre transform (value of Transform prior to any transforms) as SAM will remove the transform section on completion.
Any chance you are using multiple Transforms?  Language Extension for instance?

@kddejong I am only using the single Transform: AWS::Serverless-2016-10-31 and no Language Extension.
The line cfn-lint is erroring on is FunctionArn: !Sub arn:aws:lambda:us-east-1:123456789012:function:Lambda_Function_${env} and I do have an 'env' parameter defined above in the template.
I'm not super familiar with much of this, let me know what helpful context I may be able to provide.


Calls: %dopar% ->

Hello.
Thank you for developing TRASH, I am getting the following error when running TRASH:
Error in { : task 1 failed - "'length = 28' in coercion to 'logical(1)'"
Calls: %dopar% -> <Anonymous>
Execution halted

Thank you.

Same Error what was the solution for this error. @zhouxp9709
Error in { : task 1 failed - "'length = 132' in coercion to 'logical(1)'" Calls: %dopar% -> <Anonymous> Execution halted


[GOT-4] Replace mux package with a currently maintained project.

From SyncLinear.com | GOT-4

yep, so much!

I was a bit overloaded this cycle, I'm gonna have to move this to cycle 2

Note: we will use chi to replace mux.

If you branch off from joe/rm-relay you should be fine. With that we can release the JSON-RPC drop and the new routing library in one go.

Perfect, Thanks!

@brunocalza There is a lot of potential for merge conflicts with the branch that has the JSON-RPC changes if I do the updates to change the mux package to chi.  I'm planning to wait until after JSON-RPC removal work is most of the way complete to start on that.  Does that make sense to you?

@joewagner should we move this one to cycle 3?


Fix race in lcow snapshot scratch.vhdx creation

Signed-off-by: Justin Terry (VM<EMAIL_ADDRESS>

@crosbymichael @dmcgowan - Since the snapshotter runs in proc there is no need for a file lock. The issue here was that if the creation fails after the lock was taken the lock file was leaked to the file system. Once the lock file was present because of opening with flags os.O_EXCL|os.O_CREATE we were never able to obtain the lock again and would time out on 2nd->Nth retries.

Codecov Report

Merging #2682 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #2682   +/-   ##
======================================
  Coverage      45%     45%
======================================
  Files          92      92
  Lines       10114   10114
======================================
  Hits         4552    4552
  Misses       4842    4842
  Partials      720     720

Flag
Coverage Δ

#linux
48.72% <ø> (-0.03%)
:arrow_down:

#windows
41.76% <ø> (ø)
:arrow_up:

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 3bc4ba2...e373126. Read the comment docs.

LGTM

LGTM
Since this is running inside of a transaction context there should already be a file level lock on the bolt database.


Refactored the connection a bit to not have to pass the tcp_client all the time

As stated above, the BitPal.Backends.Flowee.Connection now only requires the tcp_client passed to the connect call, not to all other calls as well.

Great! Good work on the docs too (I need to do that as well...).


mpo_500.urdf

Hi,
on a fresh installation of ros2 foxy rviz2 ca not load
https://github.com/neobotix/neo_simulation2/blob/main/robots/mpo_500/mpo_500.urdf
as it complains
No transform from [base_footprint] to [map]
No transform from [base_link] to [map]
...

Hey, on the left side of the RViz you will see the Display panes. Under the display pane, you will see the global options, under that you have to select odom under fixed frame.

I will suggest you to use Galactic rather than Foxy.

this does only change the view and not solve the complain for the missing links.
Foxy is the LTS version thought. Any particular reason to change for Galactic

The navigation stack is much mature for Galactic compared to Foxy and some of the features aren’t available. We haven’t been looking into foxy for a while as well. All the features are being targeted for Galactic.
But if you want to use foxy, I’ll try to see and backport the developments that we made for galactic

okay I might not be the most important person. Was just curious about the mp0_500 as it was used in a life class of the theconstructsim.com

@padhupradheep ok thanks. However Foxy is the LTS version and therefore should be supported first. I checked up some of the other tutorials and  failed also.
Let me know once you have a new URDF and I will check again with foxy.
Would be great to have a working simulation installed from scratch here

However Foxy is the LTS version

That is true indeed, but ROS-2 is maturing every day and the developments for the domain we are in, does not target very much for Foxy.  Rather there is a new LTS release called Humble targetting Ubuntu 22.04

and therefore should be supported first.

I totally understand your concern.

Let me know once you have a new URDF and I will check again with foxy.

The URDF is not going to change but some of the configs and executable just need an upgrade based on the updates we made in the past for the other latest distros.
In any case, I will set you up a running version of simulation for Foxy.

wonderfull news.
I did not think about the humble version right now but looks like it has already a good reputation already
Thanks for your work !

Just follow this tracker and I hope you get the backport soon.

unfortunatetly not


Fix typo, security was missing a 't' in readme.md

Fix missing 't' in the README.md file.

@rgacogne This has been approved but haven't been merged over a year now, just wanted to give you a nudge.

Sorry for the delay!


Is the CrossNorm same with AdaIN ?

Hi @weix-liu,
AdaIN was used to generate the Stylized ImageNet, which is a comparison method in our paper. We also analyzed the difference between CrossNorm and Stylized ImageNet in the related work section.


Fix Top left host name display malfunction

@xiaoqingfengATGH, This time, no more personal audits by mistake.

pleassse update to openwrt 22.03


Particle emitter death zones are positioned in global space

Version
Phaser 3.60 beta 18
Description
Emitter death zones are positioned in global space which is unexpected.
Was it an intentional change? It is quite confusing IMO because of the 2 reasons:

in prior versions death zones were positioned in emitter local coordinates space
emit zones & gravity wells are positioned in local space

Example Test Code
https://codesandbox.io/s/particles-death-zone-qpmvhn
let particles = this.add.particles(300, 300, "flares", {
	lifespan: 1500,
	alpha: { start: 0, end: 1 },
	scale: 0.2,
	quantity: 20,
	emitting: false,
})

// emit zone position is in local emitter space (as expected)
let emitZone = new Phaser.Geom.Circle(0, 0, 200)
particles.addEmitZone({
	source: emitZone,
	type: "random",
	quantity: -1,
})

// deathZone position is in global space
let deathZone = new Phaser.Geom.Circle(0, 0, 100)
// you need to manually calculate the offset to put it in the right place
// let deathZone = new Phaser.Geom.Circle(particles.x, particles.y, 100)
particles.addDeathZone({
	source: deathZone,
	type: "onEnter",
})

particles.start(1500)

I am having this issue as well. Clearly coordinates should be in emitter-space or this does not work using existing geometries. I am trying to get this to work by passing the center point but this is clearly an unacceptable hack.
Any chance this will be addressed?

This issue has been resolved.
The death zones collisions have been corrected to check local coordinates instead of global coordinates to ensure it aligns with the local emitter space.
The changes will be reflected in the next update.


FstCompiler: Symbol is not mapped to any integer arc ilabel

I am trying to integrate the homeassistant examples files into my hassio rhasspy addon. I have copied the files '/examples/homeassistant/profile' into '/shares/rhasspy/profiles/en', and after a reboot of the service, these changes are all pulling through to the rhasspy UI.
However, when training on the new sentences/words, the following below error occurs. Having a look at the language_model.txt at the stated line, I can see its failing on an unknown entity: 421 493 - - 0.0
This also occurs if an entity name has an _ in it: 183 296 kitchen_downlights kitchen_downlights 0.0

FATAL: FstCompiler: Symbol "-" is not mapped to any integer arc ilabel, symbol table = /share/rhasspy/profiles/en/kaldi/model/data/lang/words.txt, source = /share/rhasspy/profiles/en/kaldi/language_model.txt, line = 547
[ERROR:2021-06-08 21:52:30,798] rhasspyasr_kaldi_hermes: train
Traceback (most recent call last):
File "/usr/lib/rhasspy/rhasspy-asr-kaldi-hermes/rhasspyasr_kaldi_hermes/init.py", line 618, in handle_train
spn_phone=self.spn_phone,
File "/usr/lib/rhasspy/rhasspy-asr-kaldi/rhasspyasr_kaldi/train.py", line 163, in train
language_model_type=language_model_type,
File "/usr/lib/rhasspy/rhasspy-asr-kaldi/rhasspyasr_kaldi/train.py", line 342, in train_kaldi
subprocess.check_call(compile_grammar, cwd=model_dir, env=extended_env)
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['fstcompile', '--isymbols=/share/rhasspy/profiles/en/kaldi/model/data/lang/words.txt', '--osymbols=/share/rhasspy/profiles/en/kaldi/model/data/lang/words.txt', '--keep_isymbols=false', '--keep_osymbols=false', '/share/rhasspy/profiles/en/kaldi/language_model.txt', '/share/rhasspy/profiles/en/kaldi/model/data/lang/G.fst']' returned non-zero exit status 1.
[DEBUG:2021-06-08 21:52:30,801] rhasspyasr_kaldi_hermes: -> AsrError(error="Command '['fstcompile', '--isymbols=/share/rhasspy/profiles/en/kaldi/model/data/lang/words.txt', '--osymbols=/share/rhasspy/profiles/en/kaldi/model/data/lang/words.txt', '--keep_isymbols=false', '--keep_osymbols=false', '/share/rhasspy/profiles/en/kaldi/language_model.txt', '/share/rhasspy/profiles/en/kaldi/model/data/lang/G.fst']' returned non-zero exit status 1.", site_id='default', context=None, session_id='0970bdf4-456c-4d8b-970f-6897e39e81f3')
[DEBUG:2021-06-08 21:52:30,801] rhasspyasr_kaldi_hermes: Publishing 470 bytes(s) to hermes/error/asr
[DEBUG:2021-06-08 21:52:30,877] rhasspyserver_hermes: Handling AsrError (topic=hermes/error/asr, id=02c02a90-0533-4e8d-a582-7fd448a148d0)
[ERROR:2021-06-08 21:52:30,879] rhasspyserver_hermes: AsrError(error="Command '['fstcompile', '--isymbols=/share/rhasspy/profiles/en/kaldi/model/data/lang/words.txt', '--osymbols=/share/rhasspy/profiles/en/kaldi/model/data/lang/words.txt', '--keep_isymbols=false', '--keep_osymbols=false', '/share/rhasspy/profiles/en/kaldi/language_model.txt', '/share/rhasspy/profiles/en/kaldi/model/data/lang/G.fst']' returned non-zero exit status 1.", site_id='default', context=None, session_id='0970bdf4-456c-4d8b-970f-6897e39e81f3')
[ERROR:2021-06-08 21:52:30,880] rhasspyserver_hermes: Command '['fstcompile', '--isymbols=/share/rhasspy/profiles/en/kaldi/model/data/lang/words.txt', '--osymbols=/share/rhasspy/profiles/en/kaldi/model/data/lang/words.txt', '--keep_isymbols=false', '--keep_osymbols=false', '/share/rhasspy/profiles/en/kaldi/language_model.txt', '/share/rhasspy/profiles/en/kaldi/model/data/lang/G.fst']' returned non-zero exit status 1.
Traceback (most recent call last):
File "/usr/lib/rhasspy/.venv/lib/python3.7/site-packages/quart/app.py", line 1821, in full_dispatch_request
result = await self.dispatch_request(request_context)
File "/usr/lib/rhasspy/.venv/lib/python3.7/site-packages/quart/app.py", line 1869, in dispatch_request
return await handler(**request_.view_args)
File "/usr/lib/rhasspy/rhasspy-server-hermes/rhasspyserver_hermes/main.py", line 1306, in api_train
result = await core.train()
File "/usr/lib/rhasspy/rhasspy-server-hermes/rhasspyserver_hermes/init.py", line 471, in train
raise TrainingFailedException(reason=asr_response.error)
rhasspyserver_hermes.TrainingFailedException: Command '['fstcompile', '--isymbols=/share/rhasspy/profiles/en/kaldi/model/data/lang/words.txt', '--osymbols=/share/rhasspy/profiles/en/kaldi/model/data/lang/words.txt', '--keep_isymbols=false', '--keep_osymbols=false', '/share/rhasspy/profiles/en/kaldi/language_model.txt', '/share/rhasspy/profiles/en/kaldi/model/data/lang/G.fst']' returned non-zero exit status 1.

Any help or direction would be appreciated

What do your "friendly" entity names look like? If they have dashes and underscores in them, I could see this causing a problem. In the example, I was assuming they would be something like "Kitchen Light".

Hi. I used hyphens in my my automations as a type of naming convention:
Auto Lights - Kitchen - Nighttime
Auto Lights - Diningroom - Brightness
I had some switch entities that were named with underscores as well.
The 'Solution' to this is to rename these entities(of which I have 800+ in total). It's been a task. But I am operational. Thanks.

OK, glad you found a solution. I wonder if it would be possible to strip out some of these characters in the slot program. As long as the entity id is not changed, I would expect it to still work.

This seems to be how Home Assistant handles it(except scripts that throw an error on save)
name: Retain Switch - Study
Entity_id: retain_switch_study


Add @concrete5 ruleset

Hi everybody,
What about creating a '@concrete5' ruleset in the RuleSet.php file?
Would you consider a pull request with it?

I don't want to be sound rash or anything, but I have never heard of it.
Globally-defined rulesets are rulesets for well established standards across PHP community, not for one-specific project.
What is the case here ?

concrete5 is pretty big, but the CS is as unique as that of WP IIRC (been a while since I last worked with it)

Talking about CMSs, concrete5 is one of the most common CMS out there.
Sure, WordPress is the most known one and eats the greater part of the marketshare, but it goes on its way alone and don't follow modern standards (take a look at https://github.com/WordPress/WordPress if you want a subject for your nightmares - I don't think it uses autoloaders for instance).
For sure @aembler or @KorvinSzanto (which is a member of the PHP-FIG may argue better about this subject.

concrete5 is pretty big, but the CS is as unique as that of WP IIRC (been a while since I last worked with it)

Here you can find our rules: as you can see, they are almost the same as the Symfony ones, with a few exceptions (and we're going to have a final version of them here: https://github.com/concrete5/concrete5/pull/4873)

@mlocati , it's not about which project creates the rulest - example for WordPress has different meaning.
WP has weird standards, but they are used only in WP scope, for that they could have their "private" ruleset, not globalone.
eg @PSR2 is the ruleset commonly used by many developers across a lot different projects.
same with existing @Symfony or (not-existing) other frameworks - they comes from framework community, but they are used across most projects made on top of that frameworks.
But, If I would make a great project XYZ, that is installed by million of users, thousand of contributors, with unique cs style, but then - they style is used only in that one project - no reason to push it to global ruleset, as nobody will use it for different project, and also it would require XYZ owner to send a PR to PHP-CS-Fixer to adjust the ruleset every single time (eg when PHP CS Fixer would offer new rules), making the ruleset harder and slower to maintain

👎 For adding concrete5 as a preset in here.

@mlocati looking at https://github.com/mlocati/concrete5/blob/04193bdbb4c9ab324e9d2a589216bfbf360f4929/.php_cs.dist you got a nice CS config :)
The thing I wonder about is the added value of adding those rules here as a predefined set. As of now the Concrete5 community can update the config/set whenever they want, putting it here will make it less flexiable as @keradus stated (for example https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/2413 where one maintainer of SF want the set to be updated which means he has to go through here).
I'm not against added predef. sets as I see those as predef. config and pretty harmless, however the maintenance is best done by the community of that set and that typically makes it more practical for that community to do it in a repo of their own with all the flexibility that comes with it.

@GrahamCampbell I don't think that saying "No" without any argumentation can be a benefit for a discussion (any discussion, not just this one) (please, don't take me wrong, it's just a suggestion...)
@keradus @SpacePossum concrete5 is highly customizable thanks to flexibility and portability of packages. BTW you're both right: even if a developer creates and maintains a package, she/he will still (usually) need the concrete5 core, so I agree that having a .php_cs.dist file in the release archive could be enough. So yes, you are both right... This issue can be closed IMHO (if no one else has something to add).

@GrahamCampbell I don't think that saying "No" without any argumentation can be a benefit for a discussion (any discussion, not just this one) (please, don't take me wrong, it's just a suggestion...)

I was basically agreeing with @keradus. Sorry if that wasn't clear. Presets to be included should be because they target the majority of php-cs-fixer consumers, and concrete5 does not.

I was basically agreeing with @keradus. Sorry if that wasn't clear.

Now it is :wink:

Presets to be included should be because they target the majority of php-cs-fixer consumers, and concrete5 does not.

I don't think that the number of users is the point (and btw concrete5 isn't a small project after all).
IMO the point is the availability of a standard project ruleset for all the developers involved.
Since concrete5 developers always need the concrete5 core, it's enough to add the ruleset to the concrete5 core instead of adding it to php-cs-fixer.

OK, so, after all the discussion, closing this ticket.
Thanks all for discussion so far and feel free to continue it. I'm closing just to keep the tickets clean and as we know that we don't merge it into global rulesets. Feel free to continue discussion if one wants.

@mlocati , I don't know the case here.
There is concrete5 package that has the configuration.
Is there any other packages that should follow same ruleset ?
If so, then you may be interesting in making extra package like concrete5-php-cs-fixer-config which only purpose would be to reveal the Config class with concrete5 settings. Then, it would be easy to reuse that class in other concrete5 packages

I don't think it's the case for concrete5.
Think of concrete5 packages as Firefox extensions: in theory you could develop a Firefox extension without having Firefox installed, but for sure you want Firefox installed to test it before the distribution...
concrete5 packages needs to be executed inside the concrete5 core.


Add wasm-rs-* crates

Crate collection from wasm.rs

I am wondering if somebody can review this? Thanks!

Should also add this. It fixes #362 which I just added.
diff --git a/wasm-runtimes.md b/wasm-runtimes-edited.md
index 8482408..aa367de 100644
--- a/wasm-runtimes.md
+++ b/wasm-runtimes-edited.md
@@ -9,7 +9,7 @@ intro = "While the main showcase of WebAssembly initially was the web browser, t

 packages = [
   "lucet-runtime",
-  "wasmer-runtime",
+  "wasmer",
   "wasmtime",
   "watt"
 ]


Adding parameters for affirmation and rephrase action names

Proposed changes:

I added parameter names for different affirmation and rephrase action names so that they're easier to change.

Status (please check what you already did):

[ ] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog
[ ] reformat files using black (please check Readme for instructions)

Thanks for submitting this PR, we'll give it a review as soon as possible.


DetectoRS: loss is nan

Checklist

I have searched related issues but cannot get the expected help.
The bug has not been fixed in the latest version.

Describe the bug
the loss is NAN when training the detectors_htc_r50_1x_coco
Reproduction

What command or script did you run?

./tools/dist_train.sh configs/detectors/detectors_htc_r50_1x_coco.py 8

Did you make any modifications on the code or config? Did you understand what you have modified?
nothing have been modified.
What dataset did you use?
MSCOCO
Environment

sys.platform: linux
Python: 3.7.7 (default, Mar 26 2020, 15:48:22) [GCC 7.3.0]
CUDA available: True
CUDA_HOME: /usr/local/cuda-10.1
NVCC: Cuda compilation tools, release 10.1, V10.1.105
GPU 0,1,2,3,4,5,6,7: TITAN RTX
GCC: gcc (GCC) 5.4.0
PyTorch: 1.5.1+cu101
PyTorch compiling details: PyTorch built with:
  - GCC 7.3
  - C++ Version: 201402
  - Intel(R) Math Kernel Library Version 2019.0.5 Product Build 20190808 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v0.21.1 (Git Hash 7d2fd500bc78936d1d648ca713b901012f470dbc)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - NNPACK is enabled
  - CPU capability usage: AVX2
  - CUDA Runtime 10.1
  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_37,code=compute_37
  - CuDNN 7.6.3
  - Magma 2.5.2
  - Build settings: BLAS=MKL, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -fopenmp -DNDEBUG -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DUSE_INTERNAL_THREADPOOL_IMPL -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_STATIC_DISPATCH=OFF,

TorchVision: 0.6.1+cu101
OpenCV: 4.2.0
MMCV: 0.6.2
MMDetection: 2.2.0+741b638
MMDetection Compiler: GCC 5.4
MMDetection CUDA Compiler: 10.1

Please run python mmdet/utils/collect_env.py to collect necessary environment infomation and paste it here.
You may add addition that may be helpful for locating the problem, such as

How you installed PyTorch [e.g., pip, conda, source]
Other environment variables that may be related (such as $PATH, $LD_LIBRARY_PATH, $PYTHONPATH, etc.)

Error traceback
If applicable, paste the error trackback here.
A placeholder for trackback.

Bug fix
If you have already identified the reason, you can provide the information here. If you are willing to create a PR to fix it, please also leave a comment here and that would be much appreciated!

#3187

thanks~~~~

hello, have you solve this problem ?
I met the same error, and it still occur when i modified the learning rate.


Swift 4 Migration

Swift 4 migration
Pods folder added to .gitignore and is no longer checked in
Project format updated to Xcode 9.0
Updated to SnapKit 4.0, Masonry 1.1.0
Resolve warnings

See commit log/messages for specific details/changes

@jaredegan, @GriffinSchneider

👍

@Kalvin126 I just published 1.2.0 to CocoaPods

Thanks!


What is the best way to get headers at transport time?

Hi!
As I understand transports need the message headers before pumping the message up in the next part of the pipe. So I need to get them from the message. My problem is that kafka doesn't have any headerbag for it, I only have a byte[] payload.
Do I serialize and deserialize every message at transport level? I could use
https://github.com/rogeralsing/Wire <-- i think now is the fastest
And a short message schema like  headers/payload
The problem is that we will have to deserialize the message twice, one in the transport and another one at serialization/deserialization time.
Do you know any better option? @danielmarbach @sfarmar
Thanks

For historic reasons our ASQ transport does the serialize and deserialize a message envelope as well since ASQ has no concept of headers neither. It uses the endpoints serializer by default. Recently that was made pluggable. Using the endpoint serializer by default turned out to be a pretty bad choice since it is kinda obscure for the endusers and from a library perspective we shouldn't give the envelope out of control since it makes it really hard to evolve the envelope format. If you use this way stick to your opinionated choice but be aware of de risk of double serialization can lead to corruption of the payload
https://github.com/Particular/NServiceBus.AzureStorageQueues/blob/develop/src/Transport/MessageWrapperSerializer.cs
Another option would be to binary encode the headers (they are just UTF strings) and separate it from the actual payload with a binary marker
My 2 cents

Am 04.12.2016 um 09:27 schrieb Pablo Castilla<EMAIL_ADDRESS>Hi!
As I understand transports need the message headers before pumping the message up in the next part of the pipe. So I need to get them from the message. My problem is that kafka doesn't have any headerbag for it, I only have a byte[] payload.
Do I serialize and deserialize every message at transport level? I could use
https://github.com/rogeralsing/Wire <-- i think now is the fastest
And a short message schema like headers/payload
The problem is that we will have to deserialize the message twice, one in the transport and another one at serialization/deserialization time.
Do you know any better option? @danielmarbach @sfarmar
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I will go as the ASQ does. What you said seems sensible.
Thanks for the help, this is what I am looking for asking you, for sure you have a lot more experience doing NSB transports.


Change sequence identifier from assembly

We need to change the identifier in the consensus fasta sequences from '>assembly'.
There will probably need to be an input parameter for the new sequence identifier

also put the same identifier in the VCF file


MH-12332, disable workflows whose tags don't explicitly match the source type, UPLOAD|SCHEDULE 5.x

ported from the 4.x commit that conflicted with 5.x

Works as intended.


new cask "erbele" 3.8.2

please add my new cask for Erbele.app

Thank you for the submissions, but this cask is self-submitted and too obscure, so we’ll have to refuse it. This policy is documented.
Also, next time please do fill the pull request template.


Error importing getenv from vocode (python 3.11)

I am running the StreamingConversation example from the Python quickstarts. I am using Pipenv for virtualenv management. So, the Pipfile looks like so:
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
openai = "*"
wheel = "*"
pyyaml = "*"
vocode = {extras = ["io"], version = "*"}

[dev-packages]
nose2 = "*"
flake8 = "*"
isort = "*"
black = "*"

[requires]
python_version = "3.11"

When I run the example file (with python main.py), I get the following error:
Traceback (most recent call last):
  File "/path/to/project/stream_convo.py", line 5, in <module>
    from vocode.streaming.streaming_conversation import StreamingConversation
  File "/<home>/.local/share/virtualenvs/<project-virtualenv>/lib/python3.11/site-packages/vocode/streaming/streaming_conversation.py", line 9, in <module>
    from vocode.streaming.agent.bot_sentiment_analyser import (
  File "/<home>/.local/share/virtualenvs/<project-virtualenv>/lib/python3.11/site-packages/vocode/streaming/agent/bot_sentiment_analyser.py", line 6, in <module>
    from vocode import getenv
ImportError: cannot import name 'getenv' from 'vocode' (/<home>/.local/share/virtualenvs/<project-virtualenv>/lib/python3.11/site-packages/vocode/__init__.py)

I am not able to figure out why this is happening since I don't see anything wrong with the import sequence. Any ideas why this might be happening?

hi @bitsofparag , let's talk in Discord? https://discord.gg/NaU4mMgcnC

I'm having the same issue, couldn't find any meaningful references to getenv in the discord


Avoid bare except

Fixes #92

I guess the general idea of the warning is to catch more specific exceptions, but it can be hard to know what the intention was with old code so this is fine. In the future let's be more specific with new ones.

For the ones that catch Exception and then just immediately reraise, is there really even a point to having them?

They don't do much, do they? Let's remove them!

See PR https://github.com/c-w/gutenberg/pull/94.


[Investigation] Determine when USD invokes AR2 as part of stage composition.

What
Learn how USD invokes its AR2 API.
Why
Facilitates the development of an OpenAssetIO API host AR plugin. This will greatly simplify the integration of python-only and other OpenAssetIO compatible asset managers into a USD ecosystem.
ACs

Wiki page outlining:

When the USD engine invokes the various AR API methods as part of stage composition/traversal that includes referenced layers.
Which methods are required of an AR plugin (or where fallback/default implementations can be found).

As far as determining which resolver to use, the USD documentation is pretty straitforward.
In the USD implementation, a resolve call will look like this
ArGetResolver().Resolve("assetIdentifier")

ArGetResolver() (on first call), will attempt to create an ArResolver subclass that satisfies the identifier.

First, via checking for URI scheme registrars
Then by using PreferredPrimaryResolver if it's been set
Then, but using the first custom primary resolver that's registered, sorted by typename
Then, the default resolver (which is just a path resolver)

If any of the custom resolves fail, the resolve immediately falls back to using a default resolver.
URI resolvers, are pretty interesting, they're defined by setting a uriScheme when registering a custom resolver,
it might be pleasant to have a custom OpenAssetIO uri scheme, something like this.
{
    "Plugins": [
        {
            "Info": {
                "Types": {
                    "OAIOResolver": {
                        "bases": ["ArResolver"],
                        "uriSchemes": ["openassetio", "oaio"]
                    }
                }
            },
            ...
        }
    ]
}

Then an asset might be referenced in a USD document as
#usda 1.0
(
    defaultPrim = "ACoolAsset"
)

def "ACoolAsset" (
   payload = @openassetio:ACoolAsset
)
{
}

Note
It's a tad ambiguous to me whether the preferred primary resolver, or a valid URI resolver, are given precendence.
The docs here seem to indicate that a valid URI resolver
will always be chosen first. However, the docs for ArSetPreferredResolver state that it allows users to override USDs
plugin discovery entirely. I suspect URI resolvers are still given precedence, but it's something to check.

It may be important to note that whilst the USD documentation asserts that our resolver instance may be constructed at any time,
generally the resultant object from ArGetResolver() is cached, so it won't neccesarily be constructed for each Resolve call into it.
Seems to me like we'd want to make sure our resolver is stateless, and rely on USD caching as much as we can.
references :

https://graphics.pixar.com/usd/dev/api/ar_page_front.html
https://graphics.pixar.com/usd/dev/api/ar_2resolver_8h.html#ab0913ebfd579684add6b59b44983a633

Potential scenarios:

Simple multi-file stage using peer files in a directory and relative path discovery ie stage.usda references layer1.usda and layer2.usda (using subLayers, payload etc.. and other elements of the composition arg)

with nested references
with the same reference used multiple times

A usda file defining typed prims referencing asset identifiers

Duplicate references
USD seems pretty solid at avoiding resolving duplicate references multiple times.
For example, this file

parking_lot.usd
#usda 1.0
(
    subLayers = [@./car.usd@,
                 @./car.usd@,
                 @./car.usd@]
)

def "ParkingLot"
{

    def "Car_1" (
        references = @./car.usd@</Car>
    )
    {
        color3f color = (0, 1, 0)
    }
    def "Car_2" (
        payload = @./car.usd@</Car>
    )
    {
        color3f color = (0, 0, 1)
    }
}

Calls into Resolve, OpenAsset and GetModificationTimestamp for car.usd only once, this is in line with our expectations and the documentation for how the caching system works.
The same cannot be said CreateIdentifier and GetExtension however, which are called numerous times.

raw_output
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetAssetInfo, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetModificationTimestamp, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :usda
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetAssetInfo, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetModificationTimestamp, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd

It's worth noting, when doing experimentation on flattening this file, via usdcat --flatten, that our debug output was printed for many calls made by usdcat itself, attempting to resolve a file from the USD install, generatedSchema.usd

flatten_debug_output
usdcat --flatten tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::UsdOpenAssetIOResolver
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetAssetInfo, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetModificationTimestamp, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :usda
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetAssetInfo, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetModificationTimestamp, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :usda
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :usda
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usdGeom/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usdGeom/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usdSkel/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usdSkel/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usdMedia/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usdMedia/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usdSkel/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usdMedia/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usdGeom/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usdProc/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usd/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usd/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usdRi/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usdHydra/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usdRi/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usd/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usdPhysics/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usdUI/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usdRi/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usdHydra/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usdLux/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usdProc/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usdLux/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usdHydra/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usdRender/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usdProc/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usdShade/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usdRender/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usdUI/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/usr/local/USD/lib/usd/usdVol/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usdLux/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usdVol/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usdRender/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usdPhysics/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/usr/local/USD/lib/usd/usdShade/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usdUI/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usdVol/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usdPhysics/resources/generatedSchema.usda
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/usr/local/USD/lib/usd/usdShade/resources/generatedSchema.usda

flattened_parking_lot.usd
#usda 1.0
(
    doc = """Generated from Composed Stage of root layer /home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
"""
)

def "Car"
{
    color3f color = (0, 0, 0)
    color3f spec_color = (1, 1, 1)
}

def "ParkingLot"
{
    def "Car_1"
    {
        color3f color = (0, 1, 0)
        color3f spec_color = (1, 1, 1)
    }

    def "Car_2"
    {
        color3f color = (0, 0, 1)
        color3f spec_color = (1, 1, 1)
    }
}

This isn't unexpected, but it does draw to light that we need to be cognizant that our resolver may be called with many unexpected paths, so we'll have to be robust in failing out to the default resolver. This concerns me somewhat that implementing a primary resolver instead of a URI resolver may have a slight performance pessimisation, as we may need to attempt to communicate with the asset management system in order to figure out if the path is a path we're interested in resolving or not. Just an observation and not something i'd act on right now, these "system resolves" won't be that significant in terms of total runtime, just something to be aware of.

Nested references
It's a similar case for nested references. The following files define a parking lot of 2 floors, each floor references the car.usd file.

parking_lot.usd
#usda 1.0
def "ParkingLot"
{

  def "ParkingLot_Floor_1" (
      references = @./floor1.usd@</ParkingLot_Floor>
  )
  {
  }
  def "ParkingLot_Floor_2" (
      payload = @./floor2.usd@</ParkingLot_Floor>
  )
  {
  }
}

floor1.usd/floor2.usd (two identical files)
#usda 1.0
def "ParkingLot_Floor"
{
  def "Car1" (
      references = @./car.usd@</Car>
  )
  {
      color3f color = (0, 0, 1)
  }
  def "Car2" (
      references = @./car.usd@</Car>
  )
  {
      color3f color = (0, 0, 1)
  }
}

car.usd
#usda 1.0
def "Car"
{
  color3f color = (0, 0, 0)
  color3f spec_color = (1 ,1, 1)
}

As before, Resolve / OpenAsset / GetModificationTimestamp are called only once for each file, despite the fact that car.usd is referenced in multiple files

debug output
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetAssetInfo, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetModificationTimestamp, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :usda
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor2.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor2.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor2.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetAssetInfo, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor2.usd
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor2.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/instanced_parking_lot.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor1.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor1.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetAssetInfo, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor1.usd
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor1.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetModificationTimestamp, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor2.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor2.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_Resolve, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetAssetInfo, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_OpenAsset, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor2.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetModificationTimestamp, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor1.usd
OAIO Resolver: UsdOpenAssetIOResolver::_GetModificationTimestamp, resolvedPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor1.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/floor1.usd
OAIO Resolver: UsdOpenAssetIOResolver::_CreateIdentifier, anchorAssetPath :
OAIO Resolver: UsdOpenAssetIOResolver::_GetExtension, assetPath :/home/elliotmorris/data/usdOpenAssetIOResolver/elliotcmorris/tests/resources/composition/instancetest/car.usd

Multiple stage opens same process
This experiment sought to determine if opening a stage file that contained references to files already resolved in prior runs, whilst still in the same process, would cause the resolve to trigger again, ie, does the cache persist.
To that end:

Run Usd.Stage.Open on parking_lot.usd twice sequentially.

Result: The cache didn't persist, Resolve, OpenAsset etc, were called one for each asset per stage open.
Multiple resolves same process
This experiment sought to determing if manually calling resolve from the usd api would cause the cache mechanisms to trigger.

Resolve car.usd multiple times via AR method.

Code for this was
resolver = Ar.GetResolver()
resolver.Resolve("resources/composition/instancetest/car.usd")
resolver.Resolve("resources/composition/instancetest/car.usd")
resolver.Resolve("resources/composition/instancetest/car.usd")

Result : Resolver skeleton reports three entries into resolve, so the calls were not bypassed by caching.

prims referencing asset identifiers
This has been difficult to come to a conclusion on, as finding an attribute in a typed prim that could serve as a string appropriate to resolution proved difficult. Attempting to resolve any old attribute (ie, a number value, etc,) normally results in a syntax error, as you'd expect.
USD has this custom string type, represented in the usd document as the keyword asset, (SdfAssetPath in code-behind land), which represents a resolvable path to another asset (doc) . As far as i've been able to tell, this is the only context in which a string will trigger a resolve.
See (here)[https://github.com/ColinKennedy/USD-Cookbook/blob/master/concepts/mesh_with_materials/usda/simple/material.usda] for example. There are several other attributes there which could function for resolution, (ie `material:binding, or info:id, but attempting to put a resolvable path there merely triggers an error.

as we may need to attempt to communicate with the asset management system in order to figure out if the path is a path we're interested in resolving or not.

See https://github.com/OpenAssetIO/OpenAssetIO/issues/566


unable to install in python2.7

running install
running build
running build_ext
building 'chianti' extension
x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/local/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 -c dataprovider.cpp -o build/temp.linux-x86_64-2.7/dataprovider.o -std=c++11 -fopenmp
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default]
In file included from /usr/local/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1777:0,
from /usr/local/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:18,
from /usr/local/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
from dataprovider.cpp:2:
/usr/local/lib/python2.7/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2: warning: #warning "Using deprecated NumPy API, disable it by " "#defining NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
#warning "Using deprecated NumPy API, disable it by "
^
In file included from dataprovider.cpp:5:0:
utils.h: In static member function ‘static std::string PythonUtils::objectToString(PyObject*)’:
utils.h:121:61: error: ‘PyUnicode_AsUTF8AndSize’ was not declared in this scope
return std::string(PyUnicode_AsUTF8AndSize(object, 0));
^
dataprovider.cpp: At global scope:
dataprovider.cpp:30:1: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
};
^
dataprovider.cpp:30:1: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
dataprovider.cpp:30:1: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
dataprovider.cpp:30:1: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
dataprovider.cpp: In function ‘int PyDataProvider_init(PyDataProvider*, PyObject*, PyObject*)’:
dataprovider.cpp:280:75: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
static char keywordList[] = {"iterator", "batchsize", "augmentors", 0};
^
dataprovider.cpp:280:75: warning: deprecated conversion from string constant to ‘char’ [-Wwrite-strings]
dataprovider.cpp:280:75: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
dataprovider.cpp: In function ‘PyObject* sequentialIterator(PyObject*, PyObject*, PyObject*)’:
dataprovider.cpp:447:45: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
static char keywordList[] = {"files", 0};
^
dataprovider.cpp: In function ‘PyObject randomIterator(PyObject*, PyObject*, PyObject*)’:
dataprovider.cpp:485:45: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
static char keywordList[] = {"files", 0};
^
dataprovider.cpp: In function ‘PyObject sampleIterator(PyObject*, PyObject*, PyObject*)’:
dataprovider.cpp:523:56: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
static char keywordList[] = {"files", "weights", 0};
^
dataprovider.cpp:523:56: warning: deprecated conversion from string constant to ‘char’ [-Wwrite-strings]
dataprovider.cpp: In function ‘PyObject* subsampleAugmentor(PyObject*, PyObject*, PyObject*)’:
dataprovider.cpp:568:46: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
static char keywordList[] = {"factor", 0};
^
dataprovider.cpp: In function ‘PyObject gammaAugmentor(PyObject*, PyObject*, PyObject*)’:
dataprovider.cpp:590:45: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
static char keywordList[] = {"gamma", 0};
^
dataprovider.cpp: In function ‘PyObject translationAugmentor(PyObject*, PyObject*, PyObject*)’:
dataprovider.cpp:612:46: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
static char keywordList[] = {"offset", 0};
^
dataprovider.cpp: In function ‘PyObject zoomingAugmentor(PyObject*, PyObject*, PyObject*)’:
dataprovider.cpp:634:45: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
static char *keywordList[] = {"range", 0};
^
dataprovider.cpp: At global scope:
dataprovider.cpp:679:27: error: variable ‘PyModuleDef chiantiModule’ has initializer but incomplete type
static struct PyModuleDef chiantiModule = {
^
dataprovider.cpp:680:9: error: ‘PyModuleDef_HEAD_INIT’ was not declared in this scope
PyModuleDef_HEAD_INIT,
^
In file included from /usr/include/c++/4.8/cstddef:42:0,
from /usr/local/include/opencv2/core/core.hpp:58,
from /usr/local/include/opencv2/opencv.hpp:47,
from chianti/common.h:3,
from chianti/provider.h:3,
from dataprovider.cpp:4:
dataprovider.cpp: In function ‘void PyInit_chianti()’:
dataprovider.cpp:699:16: error: return-statement with a value, in function returning 'void' [-fpermissive]
return NULL;
^
dataprovider.cpp:701:16: error: return-statement with a value, in function returning 'void' [-fpermissive]
return NULL;
^
dataprovider.cpp:703:16: error: return-statement with a value, in function returning 'void' [-fpermissive]
return NULL;
^
dataprovider.cpp:705:16: error: return-statement with a value, in function returning 'void' [-fpermissive]
return NULL;
^
dataprovider.cpp:707:39: error: ‘PyModule_Create’ was not declared in this scope
m = PyModule_Create(&chiantiModule);
^
In file included from /usr/include/c++/4.8/cstddef:42:0,
from /usr/local/include/opencv2/core/core.hpp:58,
from /usr/local/include/opencv2/opencv.hpp:47,
from chianti/common.h:3,
from chianti/provider.h:3,
from dataprovider.cpp:4:
dataprovider.cpp:709:16: error: return-statement with a value, in function returning 'void' [-fpermissive]
return NULL;
^
dataprovider.cpp:723:12: error: return-statement with a value, in function returning 'void' [-fpermissive]
return m;
^
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

You're compiling against the Python 2.7 API. Please use the Python 3.5 API in order to build the module.


Fixed formatting

The BULK example for Synapse Link was missing a single quote, which really threw me off for a while. It looked as though SECRET was part of the BULK value.

@joelhulen : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


modify RELEASE workflow to auto-update tag version in readme

Fixes:  #6
Let me know if this seems alright.

Thanks for the detailed review.

too many dependency / complexity for this little feature

was somewhat expecting this. Too much resources are being used. Will try convert it to a bash script.

I have pushed an example in branch: #6_Modify_RELEASE_pipeline Would you be interested to finish that branch off?

Certainly, will do that.

Resolved by #28


WRKLDS-1431: Update testname mapping for renamed tests due to removed apps.openshift.io dependency

For https://github.com/openshift/origin/pull/28957.

/lgtm
/approve

/hold

Until https://github.com/openshift/origin/pull/28957 merges

/hold cancel

@stbenjam would you please lgtm? The PR is ready.

/lgtm


Remove Star Imports from init.py Files and Fix Circular Imports

Description
Fixes #44 and enables isort everywhere (was previously disabled due to unneeded circular imports). Importing GT4Py now only guarantees to expose gt4py.backend, gt4py.gtscript, and gt4py.storage. Other packages can be loaded on demand.
Requirements
Before submitting this PR, please make sure:

[x] You have run the code checks, tests and documentation build successfully
[x] All fixes and all new functionality are tested and documentation is up to date
[x] You looked at the review checklist

Additionally, if this PR contains code authored by new contributors:

[x] All the authors are covered by a valid contributor assignment agreement,
signed by the employer if needed, provided to ETH Zurich
[x] The names of all the new contributors have been added to an updated
version of the AUTHORS.rst file included in the PR

bors try

bors try

Looks good. I've added some small changes ontop.


base_url() value dropped between namespaces

Creating modules, but when returning from a module,  return->response->to (base_url('/'))  fails because base_url() in other namespace is blank.
Sample code:
App/Config/App.php:       public $baseURL = 'http://localhost/ci4/';
Route:   $routes->add( '/', 'App/Controllers/Home::index');
App/Controllers/Home.php:
if (!$security['logged_in']) $this->response->redirect(base_url('login'));
Auth/Controllers/Login.php:
// Login form is processed and all is good.  Return to Home now.
$this->response->redirect(base_url("/"));  ===> goes to 'http://localhost/' = not routed
$this->response->redirect(site_url("/"));  ===> goes to 'http://localhost/ci4/'  = worked

It sounds like this is working as expected.
base_url() doesn't include the "url_suffix" by design, which is the "ci4" segment in your example.


Implementing a Log-Gamma fitter

Hi,
I am trying to implement a Log-Gamma fitter. According to [1], the CDF of this distribution is

with

the incomplete Gamma ratio.
According to this definition, the cumulative hazard is given as

So I implemented this as a fitter:
from lifelines.utils.gamma import gammainc

class LogGammaFitter(KnownModelParametericUnivariateFitter):

    _fitted_parameter_names = ["lambda_", "delta_", "kappa_"]

    _bounds = [(0, 14), (0, 10), (0, 10)]

    def _cumulative_hazard(self, params, times):
        lambda_, delta_, kappa_ = params
        z = np.exp((-lambda_ + times) / delta_)

        return -np.log1p(-gammainc(beta_, z))

Notice that I have imported the gammainc function from lifelines, as there were errors otherwise. But I cannot get this to converge. Even if I choose initial values that somewhat should describe this data well. Is this because of the problem with the gammainc function, or is just that the data is not good for the distribution? (Is the implementation good?)
[1] Castillo, E., A. S. Hadi, N. Balakrishnan, and J. M. Sarabia (2005). Extreme Value and Related Models with Applications in Engineering and Science. John Wiley & Sons, Inc. isbn: 0-471-67172-X.

Ah! You've found the one function that is a problem. I haven't been able to make gammainc "work", but I have an open issue to reimplement this: https://github.com/CamDavidsonPilon/lifelines/issues/753
The problem is the derivative of the inc. gamma function is hard to write down. One option is to just use finite diff methods (like the current implementation), but this simply doesn't work (not sure why not). The other option is to try to approx. the derivative using some series representation (ala the linked issue).

Evaluating the derivative of gammainc is a common problem, but I haven't been able to find a good reference implementation. Some R packages, like flexsurv, should have a stable implementation

Thanks @CamDavidsonPilon for taking care of this. I will close this issue, as it has been addressed in 9c3a62cb41be3a432444b7ab4138d314b5ef3cb4 . The gammainc works now as expected.

Check out the new autograd-gamma library on pypi too

Already did. Works perfectly ;)


Added possibillity buttons for other languages, and corrected mistakes in nb_no.json

I planned to make most of these changes since yesterday, but was in a hurry then.
I added the button for French, Dutch, and Ukrainian since those languages has been added by others. And the button for Russian, Chinese, Korean, Japanese, Italian, Swedish, Danish, and Finnish since they are either popular languages to translate games to, or are other languages neighbouring me.
I have also fixed some spelling mistakes.

And also just a reminder:
Norwegian, Swedish, Danish, Finnish uses some special  additional letters; Ææ, Øø, Åå, Ää and Öö, just like German and Dutch has (Going to edit those in here).
But I think that thou know about that situation anyway, so i am not worried about those.
I already see that someone has proposed a texture file for some Cyrillic letters, so the .


Support more options for HTTP requests

[x]  int workers
[x]  int maxWorkers
[x]  int connections
[ ]  ~int maxConnections~
[x]  int maxBody
[x]  string localAddr
[ ]  string unixSocket
[ ]  string proxyHeader
[ ]  bool chunkedBody
[x]  bool keepAlive
[x]  bool HTTP2
[ ]  bool H2C

The current flags are enough. It would be enough to open a new issue when needed.

The current flags are enough. It would be enough to open a new issue when needed.


Sorting primary resources by fields on relationships casts exception "Mysql2::Error: Unknown column [...]"

class Track < ActiveRecord::Base
  belongs_to :album
end

class Album < ActiveRecord::Base
  has_many :tracks
end

class TrackResource < JSONAPI::Resource
  attributes :title, :duration, :liked, :disliked

  has_one :album

  def self.sortable_fields(context)
    super(context) << :"album.title"
  end
end

class AlbumResource < JSONAPI::Resource
  attributes :title

  has_many :tracks
end

GET /tracks?include=album&sort=album.title
"exception": "Mysql2::Error: Unknown column 'tracks.album.title' in 'order clause': SELECT  `tracks`.* FROM `tracks`  ORDER BY `tracks`.`album.title` ASC LIMIT 25 OFFSET 0"

I'll have a look at this.

I use v0.7.0.

v0.7.0 doesn't support sorting on relationship fields. The documentation has been updated for the new functionality but it hasn't been packaged in a release yet.

Ok, thank you very much. I think we can close this issue, then.