I need help

Please I need a fake bitcoin to be sent to a wallet address of $9000

yes, we are selling private desktop app, if you are interest, just let me know.

yes, we are selling private desktop app, if you are interest, just let me know.

can you send meyour telegram or whatsaapp this my email<EMAIL_ADDRESS>


I am not able to remove the logs from connect-streams.js

HI Team,
I wanted to comment/ remove the logs which are in connect-stream.js
I am using reactjs Application , I did import "amazon-connect-streams";
Under nodemodules I can amazon-connect-streams -> release->connect-stream.js
here I am trying to remove the console.log but its not reflecting in the UI.
Attached is the screenshot which I wanted to remove the logs.
Can someone tel me how can I remove the logs from streams.js , because of this our application is storing the cache in the backend.

Hi @Swethamr402:
What you're looking for is:
connect.getLog().setEchoLevel(connect.LogLevel.CRITICAL);

There is no connect.LogLevel.OFF level, but there's not a single entry so far in<EMAIL_ADDRESS>that uses that level, so for practical purposes it's the same thing.

Important: The Streams logger documentation does mention connect.LogLevel or connect.getLog().setEchoLevel(). It would be helpful if the amazon-connect-streams could clarify whether this is officially supported.

Ref:
https://github.com/amazon-connect/amazon-connect-streams/blob/996705f168c02c61693ef9b012a632231f056a8c/src/log.js#L21-L30
https://github.com/amazon-connect/amazon-connect-streams/blob/996705f168c02c61693ef9b012a632231f056a8c/src/log.js#L261-L267
https://github.com/amazon-connect/amazon-connect-streams/blob/996705f168c02c61693ef9b012a632231f056a8c/src/log.js#L283-L300

Thanks for the response,
I am expecting to remove complete logs, even INFO , Warn, may be Error I can keep it, but remaining logs i don't want to display on console logs.
connect.getLog().setEchoLevel(connect.LogLevel.CRITICAL); - What does it do exactly ?
When I add in to my js file, it does not reflect anything, all logs are showing as usual.

Hi @Swethamr402. Are you sure your implementation is using the non-minified build of streams? Your issue could be that you are editing the non-minified dist file, but importing the minified dist file instead.

@Swethamr402:

connect.getLog().setEchoLevel(connect.LogLevel.CRITICAL); - What does it do exactly ?

It basically tells amazon-connect-streams what is the minimum level of message that will be taken into account when logging. For example:
connect.getLog().setEchoLevel(connect.LogLevel.WARN);

Will only log .warn(), .error(), .critical() messages.
connect.getLog().setEchoLevel(connect.LogLevel.ERROR);

Will only log .error(), .critical() messages.
So on and so forth.

You have to make sure you call this before your call to connect.core.initCCP().
Note that an important limitation of this method, is that this will only affect the logging performed by amazon-connect-streams in the hosting window (i.e. your web app), it will not affect the logging performed in the guest window (i.e. the CCP inside the <iframe>):
No logging config:

With connect.getLog().setEchoLevel(connect.LogLevel.CRITICAL):

Notice how the entries with red squares are gone after the configuration. As you can see, there are still entries from https://your-instance.awsapps.com/connect/ccp-naws/static/streams/connect-streams-min.95eec0b9.js which is a resource used by the CCP <iframe>.
Ideally, calling connect.getLog().setEchoLevel(connect.LogLevel.CRITICAL) should affect the CCP <iframe> too (by sending a message like it does for other methods), but as mentioned before, this method is currently not publicly documented. This could mean that it's not intended to be used by customers and there's currently no "official" way of removing the console logging.

Hi, is there any way to obtain, or communicate with (e.g. by proxy) the connect obj associated with the iframe?

How I can fully disable logs from CCP?


Add tests for getBy, setBy and deleteBy, small refactorings

This is based on #510. It needs to be merged first. This fixes #511.
@crutchcorn I tried doing something cool DeepKeys and DeepValues, but DeepKeys often seems to break when arrays are involved. Do you know why?

Closing in favor of #510, which now contain these changes


Optional parameters without default value and Child Routes

I want to create routes with an optional [lang] parameter that would be used to set the application language as follows
Base example URLs
domain.com/
domain.com/page-one
domain.com/page-two
domain.com/page-two/search
In this case the language used is the default one
Example URLs with this param
domain.com/en
domain.com/en/page-one
domain.com/en/page-two
domain.com/en/page-two/search
domain.com/fr
domain.com/fr/page-one
domain.com/fr/page-two
domain.com/fr/page-two/search
In these two cases the language is defined by the user
The router configuration could be something like this:
	'router' => array(
		'routes' => array(
			'home' => array(
				'type'      => 'Segment',
				'options'   => array(
					'route'    => '/[:lang]',
					'constraints' => array(
						'lang' => 'en|fr'
					),
					'defaults' => array(
						'controller' => 'Application\Controller\Index',
						'action'     => 'index',
					),
				),
			),
			'page-one' => array(
				'type'      => 'Segment',
				'options'   => array(
					'route'    => '[/:lang]/page-one',
					'constraints' => array(
						'lang' => 'en|fr'
					),
					'defaults' => array(
						'controller' => 'Application\Controller\Index',
						'action'     => 'page-one',
					),
				),
			),
			'page-two' => array(
				'type'      => 'Segment',
				'options'   => array(
					'route'    => '[/:lang]/page-two',
					'constraints' => array(
						'lang' => 'en|fr'
					),
					'defaults' => array(
						'controller' => 'Application\Controller\Index',
						'action'     => 'page-two',
					),
				),
				'may_terminate' => true,
				'child_routes' => array(
					'search' => array(
						'type' => 'Literal',
						'options' => array(
							'route' => '/search',
						),
					),
				),
			),
		),
	),

Notice that default lang value has not been set. There is a business logic onBootstrap that sets default language if lang param hasn't been set.
With this configuration, if url view helper is used, something like this:
	<?php echo $this->url("page-one", array(), array(), true) ?>

would result in a route like /page-one if no language has been set or /fr/page-one if language has previously been set to fr.
The problem comes when I try to use the url view helper and force links to inherit params by using a child route.
This:
	<?php echo $this->url("page-two/search", array(), array(), true) ?>

will throw an exception that says that lang parameter is missing. It is solved if I set a default value for it, but then the result, assuming en is the default value, is /en/page-two/search instead of /page-two/search when no language is set.
By the moment I have solved it by removing the child route an creating a new route with 'route' => '/[:lang]/page-two/search', but it is not the best solution.
Am I doing something wrong?

Hi @towr I just wanted to let you know that I've had exactly the same problem as you and I've created a module out of the gist snippet you posted above to overcome the problem you were facing. It works for me as you have described in the code above. It's a very outline module but does what you need. https://github.com/tccltd/TccSkippableSegment.

Hmm after I used this plugin I can't seem to find the event in the EventManager.
Basically I need to access the params in the URL in onBootstrap like so:
$eventManager -> attach('route', function(MvcEvent $mvcEvent) {
  $params = $mvcEvent -> getRouteMatch() -> getParams();
  $route = $mvcEvent -> getRouteMatch() -> getMatchedRouteName();
  foreach ($params as $name => $value) {
    if (!isset($_GET[$name])) {
      $_GET[$name] = $value;
    }
  }

}
But it's not being recognized as an $mvcEvent. Any way to do this?

This issue has been closed as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html


Remove service tag and replace with a similar concept on Scope.

Background
A while ago, we added service as a tag (#119).  This is overly simplistic and has high probability for user confusion.
Problem
The problem is we scoped it as a tag specifically for a narrow use case, but as implemented, it is trivial for users to use it in ways that can fundamentally break common tracer logic.
Proposal
I propose we roll back/remove service as a tag, and move the ability to override the service name to the Scope.
Perhaps something like this (in java parlance):
Span span = tracer.buildSpan("stuff").start();
try (Scope scope = tracer.activate(span)) {
  try (Scope newScope = scope.withServiceName("foo")) {
    // newScope is now active scope and service name is overridden for any new children spans.
  }
  // new child spans without service name overridden here.
}

This also opens the possibility of additional Scope scoped tags or other things.
Consideration
I don't believe any releases have been published with the new service tag included, so at a minimum, we should at least revert #119 and https://github.com/opentracing/opentracing-java/pull/287 before they are released to prevent the need for a longer tail deprecation.

Thanks @tylerbenson. I agree the tag convention should be reverted.
I like that this won't accidentally result in a tag "service" which would be hard to grok whether it was an accident of legacy instrumentation or a new thing. It also addresses the first-class nature of service in distributed tracing. Finally, it deals with scoping properly.
One thing I would suggest is keeping this feature on the tracer as opposed to overloading the scope with more methods.
Ex
Span span = tracer.buildSpan("stuff").start();
try (Scope scope = tracer.activateForService(span, "who-I-proxy-for")) {
   // newScope is now active scope and service name is overridden for any new children spans.
}

note the span itself here should be only assigned to one service, so this is not only the children but also the activated one itself. There might be some nuance to how this plays out.
Note: the above allows you to switch services multiple times: nested scopes. If that's a feature it should end up in the tests.
An alternative would be to not allow nesting and do something similar to baggage which is write-only.
For example, adding a serviceName method to the span builder.
Ex
Span span = tracer.buildSpan("stuff").serviceName( "who-I-proxy-for").start();
try (Scope scope = tracer.activate(span)) {
   // newScope is now active scope and service name is overridden for any new children spans.
}

The pro of this is that it allocates the span from the beginning as that service. Also, it can't accidentally end up ambiguously as a "service" tag in old instrumentation. OTOH, this has the same implementation gotchas as baggage (Except the remote propagation part), even if it is only scoping a single property (service). That said, some tracers may already have a .serviceName method on their span which lets this drop in.
food for thought.. regardless, this should be tested in practice against something that proxies, and directly linked.
Test cases should include at least:

dispatch to multiple handlers based on incoming route (and those being different services)
multiple intermediate aka local spans
integration with at least one "real" implementation, to show service graph aggregation isn't hosed easily

+1 to have this integrated with span creation rather than scope.
But the description could use better justification. The only one I heard is old instrumentation already using "service" tag for different purposes. I think it's a good enough reason (I wasn't a fan of the tag in the first place), but are there other considerations?

@yurishkuro to be clear, you would prefer @adriancole's second suggestion, to see this associated with the span builder and have it propagated more like baggage?

I was only referring to the builder part. Auto-propagating sounds like assuming too much, but I can see the rationale for that. Perhaps it also needs to be explicit.

In looking at prior art (like finagle) and also offline chat with @codingfabian also thinking about this..
I think the simplest design is requiring the tracer to inherit parent-child any time it is set. This can't be assumed in tags, not safely IMHO as no other data in tags act like that. I think the span builder is the best way to achieve this in the OT api, possibly named "spanBuilder.serviceName"
For folks who are already using the "service" tag convention (ex @codingfabian or @jeffbakerexpedia), we can treat it like any other data which is sortof "old school". For example, when tracers upgrade, if they see a tag named "service" they can try to re-forward it to the correct api. This would work at builder time for example, even if be a bit dodgy later.
Aside: to underpin this, a span.serviceName() or similar method would be needed in brave to properly inherit. We were to do this anyway, just waiting for rule of three anyway. For example, we knew camel use the forwarding stuff and currently hack by using different tracers. It needed to be a repeating pattern before escalating to an api. I can manage adding this there.. cc @oscerd

@tedsuo What should be our path forward here?

I agree with @adriancole to have serviceName as a first class citizen and not as a tag. Whether we call it as serviceName or applicationName to be generic, I prefer an API like what Adrian proposed above
Span span = tracer.buildSpan("stuff").serviceName( "who-I-proxy-for").start();

This forces serviceName to be a concrete member of the data model and not as a tag.

On a side note, I would say the same for remoteServiceName instead of or in addition to peer.service tag.  Though this need not be mandatory, having it helps with building better service graphs. There is a related discussion in Haystack https://github.com/ExpediaDotCom/haystack/issues/537

Service name is insufficient. Jaeger uses Process (instance, resource, workload are the other possible names), which contains a service name and a set of tags that contain additional metadata about the workload (host name, IP, port, zone, environment, code version, etc.).
It is different from remote service (peer.service) because the current workload may not know much metadata about the peer service, and the tag itself is generally not that critical.

I think the simplest design is requiring the tracer to inherit parent-child any time it is set. This can't be assumed in tags, not safely IMHO as no other data in tags act like that. I think the span builder is the best way to achieve this in the OT api, possibly named "spanBuilder.serviceName"

+1 to inheritance & builder method (but replace "name" with a more complex object).

@tylerbenson I would prefer to make changes backwards compatible, i.e. deprecate rather than remove.

@yurishkuro I don't think it needs to be deprecated in the java repo since it was added since the last release, so technically not a breaking change there.  I would consider changing it to deprecated in the spec though with the assumption that means it probably shouldn't be added to language implementations if not already there.


Gnocchi refactor

Gnocchi Refactor
This refactor represents a comprehensive overhaul of the gnocchi codebase.
Purposes for the refactor

Migrate to spark Dataset API for increased performance
Increase memory efficiency through more efficient data models (namely moving creating models of reduced size for phenotypes and CalledVariants)
Move codebase to more functional style
Improve test coverage

Areas of interest to a code reviewer

Parametrizing SparkContext and SparkSession accesses

I had some trouble running this current branch on the BDG cluster due to not getting the SparkSession in a correct configuration
val sparkSession = SparkSession.builder().getOrCreate() works on my local machine but in the BDG cluster there is an error relating to correctly specifying the spark master node
Direction on correct practices here would be appreciated

Parametrizing the filesystem being used

similar to the previous note, when running on the BDG cluster, there were issues surrounding how gnocchi accesses files and the paths that are specified
How can we make the file paths more robust to a failure when there could be multiple filesystems that spark has access to?

Refactor of the org.bdgenomics.gnocchi.core.models package

There is a lot of code reuse here that is limited by small differences in the traits being inherited
Current reason it is written this way is to accommodate the spark dataset encoders, which I could not get working with generic higher level classes
This meant that any operation that dealt with Dataset objects had to exist in a non-abstract, non-trait class
Are there work arounds to this? Is it worth writing tests for this package if it will be refactored into a different model in the near future (with a new spark release)?

Are the maven POM's correct?

the maven POM's seem to work, but due to the limited understanding of our team on the power of maven, we're unsure if we are getting the most out of the tool
There are probably many different POM's that can build a project correctly, how do we know if ours is correct? Any pointers for Maven POM best practices?

Are there any obvious inefficiencies that need to be addressed?

Work that still needs to be completed
I am not sure if we want to address these needs before we merge this PR into the bdgenomics repo, but known future work is tracked in the list below.

[ ] Test the GnocchiModel package

specifically, test merging of two models and the I/O of the models

[ ] Integration tests that compare a run of plink on some input data with a run of gnocchi on the same input data
[ ] performance testing and documentation on how to best tune the spark cluster for performance

Note: This is very unfamiliar territory for me, but any advice on how to do this would be greatly appreciated
Are there inefficiencies in the way gnocchi deals with its genomic data? Inefficiencies in the GnocchiSession operations (Specifically the filterVariants and filterSamples functions)?

[ ] Load in ADAM formatted variants

Note: We currently use ADAM to load in a VCF from a specified file path, but we have not written capability to load in parquet files of ADAM VariantRDDs
What is the correct use here? Should gnocchi only ingest VCF? or should it be able to take in the ADAM formatted objects?

[ ] Model drift for QualityControlVariantModel
[ ] CLI tests
[ ] More rigid documentation

adding stuff to the docs directory
adding method level comments
explaining the more complicated portions of the codebase

[ ] More example use cases

Can one of the admins verify this patch?

@heuermh please review when you get the chance. Thanks!

Jenkins, test this please.

Jenkins, test this please.

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/gnocchi-prb/13/Build result: FAILUREGitHub pull request #38 of commit 0c7c93c6b5a9ddfedca02e00e22f7a347f607393 automatically merged.[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-worker-06 (centos spark-test) in workspace /home/jenkins/workspace/gnocchi-prb > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bigdatagenomics/gnocchi.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/gnocchi.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/bigdatagenomics/gnocchi.git +refs/pull/:refs/remotes/origin/pr/ > git rev-parse origin/pr/38/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains a3044d6d6d1b81a3be2fdb154876e1fb7feb86ab # timeout=10Checking out Revision a3044d6d6d1b81a3be2fdb154876e1fb7feb86ab (origin/pr/38/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f a3044d6d6d1b81a3be2fdb154876e1fb7feb86abFirst time build. Skipping changelog.Triggering gnocchi-prb ? 2.6.0,2.10,1.6.1,centosTriggering gnocchi-prb ? 2.3.0,2.10,1.6.1,centosTriggering gnocchi-prb ? 2.3.0,2.11,1.6.1,centosTriggering gnocchi-prb ? 2.6.0,2.11,1.6.1,centosgnocchi-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREgnocchi-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREgnocchi-prb ? 2.3.0,2.11,1.6.1,centos completed with result FAILUREgnocchi-prb ? 2.6.0,2.11,1.6.1,centos completed with result FAILURE
Test FAILed.

Jenkins, test this please.

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/gnocchi-prb/14/Build result: FAILUREGitHub pull request #38 of commit 163791747fc14d081dcc6d77aea413f1ad0d954d automatically merged.[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-worker-06 (centos spark-test) in workspace /home/jenkins/workspace/gnocchi-prb > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bigdatagenomics/gnocchi.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/gnocchi.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/bigdatagenomics/gnocchi.git +refs/pull/:refs/remotes/origin/pr/ > git rev-parse origin/pr/38/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains de1af23bf48a2e15986a4916e16a4b82fe5d77d4 # timeout=10Checking out Revision de1af23bf48a2e15986a4916e16a4b82fe5d77d4 (origin/pr/38/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f de1af23bf48a2e15986a4916e16a4b82fe5d77d4First time build. Skipping changelog.Triggering gnocchi-prb ? 2.6.0,2.10,1.6.1,centosTriggering gnocchi-prb ? 2.3.0,2.10,1.6.1,centosTriggering gnocchi-prb ? 2.3.0,2.11,1.6.1,centosTriggering gnocchi-prb ? 2.6.0,2.11,1.6.1,centosgnocchi-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREgnocchi-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREgnocchi-prb ? 2.3.0,2.11,1.6.1,centos completed with result FAILUREgnocchi-prb ? 2.6.0,2.11,1.6.1,centos completed with result FAILURE
Test FAILed.

Jenkins, test this please.

Merged build finished. Test FAILed.

Jenkins, test this please.

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/gnocchi-prb/17/Build result: FAILUREGitHub pull request #38 of commit a3fb778b0ea50693b4901e8bf26d8f161a4157f2 automatically merged.[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-worker-06 (centos spark-test) in workspace /home/jenkins/workspace/gnocchi-prb > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bigdatagenomics/gnocchi.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/gnocchi.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/bigdatagenomics/gnocchi.git +refs/pull/:refs/remotes/origin/pr/ > git rev-parse origin/pr/38/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains e7322c65a3e2d9c439bd262bba0dadacf47495bd # timeout=10Checking out Revision e7322c65a3e2d9c439bd262bba0dadacf47495bd (origin/pr/38/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f e7322c65a3e2d9c439bd262bba0dadacf47495bdFirst time build. Skipping changelog.Triggering gnocchi-prb ? 2.7.3,2.11,2.2.0,centosgnocchi-prb ? 2.7.3,2.11,2.2.0,centos completed with result FAILURE
Test FAILed.

Jenkins, test this please.

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/gnocchi-prb/18/Build result: FAILUREGitHub pull request #38 of commit 725004d7258c170812bcb4200b4fa6f7e7cf058c automatically merged.[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-worker-06 (centos spark-test) in workspace /home/jenkins/workspace/gnocchi-prb > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bigdatagenomics/gnocchi.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/gnocchi.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/bigdatagenomics/gnocchi.git +refs/pull/:refs/remotes/origin/pr/ > git rev-parse origin/pr/38/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains f27464e3ea7002e5ea30ccbaabb5b7253b7208d0 # timeout=10Checking out Revision f27464e3ea7002e5ea30ccbaabb5b7253b7208d0 (origin/pr/38/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f f27464e3ea7002e5ea30ccbaabb5b7253b7208d0First time build. Skipping changelog.Triggering gnocchi-prb ? 2.7.3,2.11,2.2.0,centosgnocchi-prb ? 2.7.3,2.11,2.2.0,centos completed with result FAILURE
Test FAILed.

Jenkins, test this please.

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/gnocchi-prb/19/
Test PASSed.

Jenkins, test this please.

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/gnocchi-prb/20/Build result: FAILUREGitHub pull request #38 of commit 2412da125f1407b82cd5b454df86d1e965f5f1af automatically merged.[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-worker-06 (centos spark-test) in workspace /home/jenkins/workspace/gnocchi-prb > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bigdatagenomics/gnocchi.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/gnocchi.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/bigdatagenomics/gnocchi.git +refs/pull/:refs/remotes/origin/pr/ > git rev-parse origin/pr/38/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains 51948c30d9e670812d9233974cf60ac5ae1becd7 # timeout=10Checking out Revision 51948c30d9e670812d9233974cf60ac5ae1becd7 (origin/pr/38/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f 51948c30d9e670812d9233974cf60ac5ae1becd7First time build. Skipping changelog.Triggering gnocchi-prb ? 2.7.3,2.11,2.2.0,centosgnocchi-prb ? 2.7.3,2.11,2.2.0,centos completed with result FAILURE
Test FAILed.

Jenkins, test this please.

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/gnocchi-prb/21/Build result: FAILUREGitHub pull request #38 of commit 9725166a53ef930aff1ad53651bf6986d1f0549e automatically merged.[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-worker-06 (centos spark-test) in workspace /home/jenkins/workspace/gnocchi-prb > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bigdatagenomics/gnocchi.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/gnocchi.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/bigdatagenomics/gnocchi.git +refs/pull/:refs/remotes/origin/pr/ > git rev-parse origin/pr/38/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains bba6065da1f463434aa533148e687e93910ecfca # timeout=10Checking out Revision bba6065da1f463434aa533148e687e93910ecfca (origin/pr/38/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f bba6065da1f463434aa533148e687e93910ecfcaFirst time build. Skipping changelog.Triggering gnocchi-prb ? 2.7.3,2.11,2.2.0,centosgnocchi-prb ? 2.7.3,2.11,2.2.0,centos completed with result FAILURE
Test FAILed.

Jenkins, test this please.

Jenkins, test this please.

Jenkins, test this please.

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/gnocchi-prb/23/Build result: FAILUREGitHub pull request #38 of commit a2023dca03fe505741e8bdf7cc7c599687d55692 automatically merged.[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-worker-06 (centos spark-test) in workspace /home/jenkins/workspace/gnocchi-prb > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bigdatagenomics/gnocchi.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/gnocchi.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/bigdatagenomics/gnocchi.git +refs/pull/:refs/remotes/origin/pr/ > git rev-parse origin/pr/38/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains 6586d9cc5446f09316980d83edfb034ff95fda66 # timeout=10Checking out Revision 6586d9cc5446f09316980d83edfb034ff95fda66 (origin/pr/38/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f 6586d9cc5446f09316980d83edfb034ff95fda66First time build. Skipping changelog.Triggering gnocchi-prb ? 2.7.3,2.11,2.2.0,centosgnocchi-prb ? 2.7.3,2.11,2.2.0,centos completed with result FAILURE
Test FAILed.

Jenkins, test this please.

Jenkins, test this please.

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/gnocchi-prb/24/Build result: FAILUREGitHub pull request #38 of commit a5ccb0c32aa35e404656719074c7217ea4799725 automatically merged.[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-worker-06 (centos spark-test) in workspace /home/jenkins/workspace/gnocchi-prb > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bigdatagenomics/gnocchi.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/gnocchi.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/bigdatagenomics/gnocchi.git +refs/pull/:refs/remotes/origin/pr/ > git rev-parse origin/pr/38/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains e7793920791c0cba9d366e770eb023fe4119ae1e # timeout=10Checking out Revision e7793920791c0cba9d366e770eb023fe4119ae1e (origin/pr/38/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f e7793920791c0cba9d366e770eb023fe4119ae1eFirst time build. Skipping changelog.Triggering gnocchi-prb ? 2.7.3,2.11,2.2.0,centosgnocchi-prb ? 2.7.3,2.11,2.2.0,centos completed with result FAILURE
Test FAILed.

Jenkins, test this please.

Jenkins, test this please.

Jenkins, test this please.

Jenkins, test this please.

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/gnocchi-prb/27/Build result: FAILUREGitHub pull request #38 of commit 90ad31bec7cc37bfbd1aa93173d5b606aaf5220a automatically merged.[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-worker-06 (centos spark-test) in workspace /home/jenkins/workspace/gnocchi-prb > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bigdatagenomics/gnocchi.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/gnocchi.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/bigdatagenomics/gnocchi.git +refs/pull/:refs/remotes/origin/pr/ > git rev-parse origin/pr/38/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains cdf5db67c6503a1c2b5b4d13601645c72d05e1f3 # timeout=10Checking out Revision cdf5db67c6503a1c2b5b4d13601645c72d05e1f3 (origin/pr/38/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f cdf5db67c6503a1c2b5b4d13601645c72d05e1f3First time build. Skipping changelog.Triggering gnocchi-prb ? 2.7.3,2.11,2.2.0,centosgnocchi-prb ? 2.7.3,2.11,2.2.0,centos completed with result FAILURE
Test FAILed.

Jenkins, test this please.

Jenkins, test this please.

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/gnocchi-prb/28/Build result: FAILUREGitHub pull request #38 of commit cbc2a71b107a247e4b0e0c0e0d93fa1a7cf8de74 automatically merged.[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-worker-06 (centos spark-test) in workspace /home/jenkins/workspace/gnocchi-prb > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bigdatagenomics/gnocchi.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/gnocchi.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/bigdatagenomics/gnocchi.git +refs/pull/:refs/remotes/origin/pr/ > git rev-parse origin/pr/38/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains b10056d4ac00a2e5f02561fdbbd16b93817ad9b2 # timeout=10Checking out Revision b10056d4ac00a2e5f02561fdbbd16b93817ad9b2 (origin/pr/38/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f b10056d4ac00a2e5f02561fdbbd16b93817ad9b2First time build. Skipping changelog.Triggering gnocchi-prb ? 2.7.3,2.11,2.2.0,centosgnocchi-prb ? 2.7.3,2.11,2.2.0,centos completed with result FAILURE
Test FAILed.

Jenkins, test this please.

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/gnocchi-prb/29/Build result: FAILUREGitHub pull request #38 of commit f0dc8db4b0629dfa8bbffce4992085c976436238 automatically merged.[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-worker-06 (centos spark-test) in workspace /home/jenkins/workspace/gnocchi-prb > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bigdatagenomics/gnocchi.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/gnocchi.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/bigdatagenomics/gnocchi.git +refs/pull/:refs/remotes/origin/pr/ > git rev-parse origin/pr/38/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains be79d721da0fd515094d36ba426106baa0b46b0e # timeout=10Checking out Revision be79d721da0fd515094d36ba426106baa0b46b0e (origin/pr/38/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f be79d721da0fd515094d36ba426106baa0b46b0eFirst time build. Skipping changelog.Triggering gnocchi-prb ? 2.7.3,2.11,2.2.0,centosgnocchi-prb ? 2.7.3,2.11,2.2.0,centos completed with result FAILURE
Test FAILed.

Jenkins, test this please.

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/gnocchi-prb/30/
Test PASSed.

Jenkins, test this please.

Looks like the Jenkins build source code style checker is giving you trouble:
test -n ' M gnocchi-core/src/main/scala/org/bdgenomics/gnocchi/sql/GnocchiKryoRegistrator.scala
 M gnocchi-core/src/main/scala/org/bdgenomics/gnocchi/utils/Timers.scala
 M gnocchi-core/src/test/scala/org/bdgenomics/gnocchi/algorithms/siteregression/SiteRegressionSuite.scala'

Please run './scripts/format-source'

Jenkins, test this please.


Allow redirect_uri and client_id overrides in getToken opts

The current generateAuthUrl() implementation allows for the redirect_uri opt to be overridden. Without the ability to specify the same override in the corresponding call to getToken(), the code exchange endpoint returns an error indicating a mismatch.
This change allows the redirect_uri and client_id used in the subsequent call to getToken() (and passed to the code exchange endpoint) to similarly be overridden.
A redirect_uri use case is straightforward, where a command line application (such as clasp) may wish to provide a localhost webserver to process the credentials returned from the code exchange endpoint, where the uri will contain a port number that was not known at the time the corresponding OAuth2Client was constructed. One current workaround is to re-assign the OAuth2Client.redirectUri private property. Another workaround is to re-construct the corresponding OAuth2Client object.
While I know of no similar explicit use case for overriding the client_id, this change also addresses whatever the original use case was for overriding the client_id in the corresponding call to generateAuthUrl().

Codecov Report

Merging #349 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #349      +/-   ##
==========================================
+ Coverage   94.75%   94.76%   +0.01%
==========================================
  Files          14       14
  Lines         953      955       +2
  Branches      196      198       +2
==========================================
+ Hits          903      905       +2
  Misses         50       50

Impacted Files
Coverage Δ

src/auth/oauth2client.ts
94.42% <100%> (+0.03%)
: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 11a0896...d62be1b. Read the comment docs.

@ofrobots would be great if you could take a look and keep me honest here


Meaning of the blue circle displayed around the role

This article does not explain the meaning of the blue circle displayed around the role represented by the green circle. Also, it does not explain the difference between the dotted line and the solid line.

I would appreciate it if you could document it.

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

ID: 0c790efc-82d3-b9c8-9e39-f4253751c3ed
Version Independent ID: f5e9fe88-a957-c7e5-53bc-b6e873b23093
Content: Application Map in Azure Application Insights - Azure Monitor
Content Source: articles/azure-monitor/app/app-map.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @AaronMaxwell
Microsoft Alias: aaronmax

@torumakabe
Thanks for your feedback! We will investigate and update as appropriate.


New occupancy types needed in Swiss database

The Hochschulquartier has quite a few occupancy types that currently cannot be modeled on the CEA, including:

Museum
Laboratories
Lecture halls
These need to be added to the database.

Lecture halls are assumed to be the same as the current SCHOOL archetype. Only MUSEUM and LAB archetypes were created based on the existing method. The former was partially based on the old PUBLIC archetype (which had been removed as part of issue #184 ), the latter is brand new. The following assumptions were made:
1. Schedules: As defined in the CEA documentation, schedule information was extracted from SIA 2024 for the following room definitions from SIA:
1.1. MUSEUM: 7.1 Vorstellungsraum
1.2. LAB: 9.3 Laborraum
Daily hot water use is not actually included in SIA 2024. Based on Jimeno's feedback, this profile was assumed to be the same as the occupancy profile.
2.	Architecture properties: Following the CEA documentation, a variety of sources were used.
2.1.	type_shade: for all occupancy types, the type of shading was the same; therefore, the same type was assumed for the new uses
2.2.	win_wall:
2.2.1. MUSEUM same as the old PUBLIC category
2.2.2. LAB: Most labs in the Hochschulquartier are part of university buildings and therefore share buildings with school and office functions and thus would share their architectural properties; LABs were given the same WWR as offices
2.3.	occ_m2p: taken from SIA 2024 for the aforementioned uses.
2.4.	n50: Weber et al. (2014) – same for all uses except homes
2.5.	win_op: assumed 0.5 for all uses except homes
2.6.	f_cros: European committee of standardization (2014) – used 0 for “all other uses” as defined in the source
2.7.	type_roof, type_wall, type_win: assumed for CEA; for the new archetypes, the most common values were used (i.e., same as for schools and many others)
**3.	Indoor comfort: ** The CEA database is also based on SIA 2024:
3.1.	Tcs_set, Ths_set, Ve_lps: taken from SIA 2024 for the aforementioned uses
3.2.	Tcs_setback is not actually in SIA 2024. Assumed 28°C for all uses (as done in CEA database)
3.3.	Ths_setback is not actually in SIA 2024. Assumed 12°C for all uses (as done for most uses in CEA database)
4.	Internal loads: According to the CEA documentation, a variety of sources were used.
4.1.	Qs_Wp, X_ghp, Ea_Wm2, El_Wm2: SIA 2024 for the aforementioned uses
4.2.	Vw, Vww: CEA archetypes aren't actually based on SIA 2024. For the new archetypes, I looked at SIA 2024 uses with the same demands as the new uses and used the values in the CEA database for the existing uses, i.e.:
4.2.1. ‘MUSEUM’: used value for ‘RETAIL’
4.2.2. ‘LAB’: used value for ‘INDUSTRY’
4.3.	Epro_Wm2: BFE (2013) – due to lack of information, assumed the same value for ‘LAB’ as for ‘INDUSTRY’ and 0 for ‘MUSEUM’
4.4.	Ere_Wm2, Ed_Wm2: not actually defined in SIA 2024 (at least not explicitly); assumed 0 for all new uses
5.	HVAC: According to the CEA documentation, all values were assumed!
5.1.	Ventilation: same for all except industry and homes; assumed LAB as INDUSTRIAL, MUSEUM as the rest
5.2.	Controls, Domestic hot water: same for all except PARKING; assumed the same as the majority for the new uses for LABS; for MUSEUM, the old PUBLIC category was resuscitated
5.3.	Cooling: same for all except homes and parking; assumed the same as the majority for the new uses
5.4.	Heating: assumed the same for LAB as for INDUSTRY, for MUSEUM the old PUBLIC category was resuscitated
6.	Thermal: According to the CEA documentation, some values were taken from Girardin (2012), others from a combination of ECA, Gebäudeparkmodell and SIA 380/1 (no precise calculation given). So the following were assumed:
6.1.	Es, Hs: 0.9 was used for all uses except homes, parking and server rooms; 0.9 was assumed for the new uses as well
6.2.	Thermal mass: the same values were assumed for all buildings, so the same was done for the new uses
6.3.	U_wall, U_roof, U_base, U_win: values for construction year >2005 and renovation were the same from all uses (from GPM), thus the same was assumed; for older buildings, the following assumptions were made:
6.3.1. MUSEUM: the old PUBLIC category was resucitated
6.3.2. LAB: since according to SIA 380/1, laboratories are included in the occupancy type “Schools”, so the same thermal properties of SCHOOL were assumed
7.	Embodied energy and emissions: According to CEA documentation, these values were taken from Thoma et al. (2014) except for services and excavation, which were taken from SIA 2032.
7.1.	Excavation: assumed same values as for all other uses
7.2.	Services: three groups were identified – homes, parking and everything else; assumed the same values as for “everything else”
7.3.	All other values are taken from Thoma et al. (2014). Since a detailed calculation was not provided, the following assumptions were made:
7.3.1. MUSEUM: the old category PUBLIC was resuscitated
7.3.2. LAB: Most labs in the Hochschulquartier are part of university buildings and therefore share buildings with school and office functions – both of which have the same values for embodied energy and emissions! Thus LABs were given the same embodied values as OFFICE and SCHOOL uses


Dobot Magician support

Hi,
I purchased a dobot magician. Is this project compatible with the dobot magician?
Thanks!

No, but you could drive it with RAMPS and Arduino Mega which are supported.

No activity


mod or module?

In Rust, modules are defined with mod, not module.  Since we steal so much of Rust's lexical syntax anyway...
Thoughts?

I like module better than mod, because it is a real word.  However, I like e.g. f32 better than float32, because it is shorter, so my thinking is inconsistent.
I have one argument in favour of keeping module: If module is changed to mod, why not also change include to inc, default to def, and so on for other keywords?

I had not considered changing 'include' to 'inc', and I think it looks
weird.  Maybe I am wrong?  We do have 'fun' instead of 'function',
though.  I imagine that 'module' is used much more often than 'include',
which is why a shortening may be justified.  (And of course, 'fun' and
'val' are used much more again.)
'default' can be whatever; I'd prefer to get rid of that eventually
(once we get proper type inference).  But 'default' is probably the most
rarely used keyword of them all.
--
\  Troels
/\ Henriksen

I guess I would be in favour of module as well. But as Niels I do not have consistent thinking.
Maybe I am just getting old and don't like change :D

Martin pointed out that no other keyword in the module language is abbreviated.  For consistency, module remains module.


avoid illegal characters in windows folder names

Illegal characters are replaced by other characters with a similar meaning.
I am sure you can rewrite this in a prettier way, but it's a start :)

Thanks, I fixed it with a similar solution using Python's str.translate() function. If you think it's really important I could make it use similar characters for the replacements, but that sounds unnecessary.


Non standard source formatting often reduces readability

Compare the following 2 screenshots:
Current formatting. Without counting parentheses (or using delimiter coloration) it's unclear how many arguments are being passed to sucle-mp:submit.

Formatted with slime. Indentation makes it clear that it has been called with 1 standard argument and 2 keyword arguments

There seem to be many cases resembling the above. If this is how you prefer to indent your code then feel free to ignore/close, but otherwise I'd be happy to tweak the formatting as I read through.

Thank you for taking the time to screenshot both scenarios! The first image definitely looks like the code is improperly formatted. However, the following is what appears in my editor:

My guess for the difference is that my emacs uses 8-character width tabs, and looking at this area, there are a lot of tabs. It might be a good idea for me to update the entire codebase to use spaces instead of tabs, as well as add a style-guide.
It would be incredibly helpful and greatly appreciated if you tweaked the formatting to make it correct, but it is in a lot of places so I wouldn't want you to make it hard on yourself. If you really want to help update the formatting, we should probably write it down in a style-guide.
Unrelated, how did you get the 'lambda' to look like a single-character symbol? That seems like a nice plugin.

I didn't notice, but you are 100% right; I'm using 4 character tabs. I ran a quick emacs script to convert each tab to 8 spaces and everything looks perfectly fine, so there shouldn't be any need to tweak anything manually.
As far as the lambda goes, emacs has built in support for that feature with prettify symbols mode. I also have M-l bound to insert "lambda".
(setq prettify-symbols-alist
      '(("lambda" . 955) ; Replace instances of the word lambda with λ
        ))
(global-prettify-symbols-mode 1)

I believe emacs is getting more robust ligature support in version 27 which might improve this.

I can submit a PR for the tab->space conversion if you want, or I could share the script I used.

I’ll close this issue; a new one could be made for tabs vs spaces.

regarding tab vs spaces the correct way is tabs for indentation and spaces for alignment so everybody can set their tab width how they want. I also think that emacs can autoformat code like that.

I'm not sure that works for lisp where according to common style each line is offset a on a space by space basis, with no concept of levels of indentation at all. Every form is either a top level form or an argument, and arguments are offset at (offset of the form they were called on) + (character length of the function being called) with few exceptions.

Yeah you are right - according to this website most projects use two spaces. But I think autoformatting should still be possible. Unfortunately I don't have the time to look into that.

Autoformatting is trivially done with or without tabs using emacs or any other lisp ide. The original issue only came up because in a codebase that does contain tab characters, an emacs configured with a tab-width of 8 and one configured with a width of 4 disagree on the output, since formatting is done to visually allign forms with the same depth in the abstract syntax tree.

@mohe2015 https://ukupat.github.io/tabs-or-spaces/ that pie chart is pretty stark, its a wonder how I didn't notice that before...
Also, here is the issue for formatting/editors https://github.com/gregcman/sucle/issues/45


fix: allow for sameAs links

To resolve the sameAs problem described in #819 we need to get the sameAs URIs defined in the RDF files. Other than originally thought not all of them are using owl:sameAs. This PR proposes another attribute in the toml definition that allows to set a sparql query that retrieves sameAs uris. Eg for Persons in Wikidata the definition could look like:
superclass = "apis_ontology.models.Person"
regex = "http://www.wikidata.org.*"
sameas = """
PREFIX wdtn: <http://www.wikidata.org/prop/direct-normalized/>
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
SELECT ?sameas ?parl_url
WHERE {
?subject wdtn:P227 ?sameas
OPTIONAL {
?subject wdt:P2280 ?parl_nr .
BIND(concat("https://www.parlament.gv.at/WWER/PAD_", str(?parl_nr)) AS ?parl_url)
}
}
"""
[[attributes]]
# name
sparql = """
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
SELECT ?forename
WHERE {
  ?person wdt:P735/rdfs:label ?first_name .
  BIND(?first_name AS ?forename)
}
"""

This fetches the GND link and uses the Parlament Nr to create a link and returns that. As a fallback a query for owl:sameAs is used.
The PR also changes the RootObject to accept the sameas attribute retrieved via the sparql queries (or actually any list of uris) directly via putting them in the sameas attribute.
resolves #819

I will fix the tests when we have finished discussing the proposed changes.


Edit toolbar size

Description of your problem
I would like to edit the toolbar size in spyder, I used to be able to do this. But I can't find the option anymore, google offered no solution. So I thought to ask it here.
What steps will reproduce the problem?

Open spyder through anaconda launcher

What is the expected output? What do you see instead?
The margin above and under the toolbar tabs (for files and the console in the screenshot).

Please provide any additional information below
I think it has to do with the retina resolution, because the toolbar looks "stretched"
Versions and main components

Spyder Version: Spyder 3.0.0dev (master as of 29/02)
Python Version: Python 3.4
Operating system: OSX 10.11

Dependencies
jedi >=0.8.1    :  0.8.1 (OK)
matplotlib >=1.0:  1.5.0 (OK)
nbconvert >=4.0 :  4.1.0 (OK)
numpy >=1.7     :  1.10.4 (OK)
pandas >=0.13.1 :  0.17.1 (OK)
pep8 >=0.6      :  1.7.0 (OK)
psutil >=0.3    :  3.4.2 (OK)
pyflakes >=0.6.0:  1.0.0 (OK)
pygments >=1.6  :  2.1 (OK)
pylint >=0.25   :  1.5.4 (OK)
qtconsole >=4.0 :  4.1.1 (OK)
rope >=0.9.4    :  0.9.4-1 (OK)
sphinx >=0.6.6  :  1.3.5 (OK)
sympy >=0.7.3   :  0.7.6 (OK)

The cleanlooks QT window style has smaller margins in the toolbar.


Transferring tokens from POA network token wizard to metamask

If you are reporting a problem with Token Wizard, please include the following information:
Which network did you use? (Mainnet, Kovan, Rinkeby, etc.)
Main network
If you were able to create it, what is the URL of your crowdsale?
https://wizard.oracles.org/invest?addr=0xa703ae15669AdEd2E89D598F7D63db9ecc413901&networkID=1
Do you see errors in the dev console? If yes, please include a screenshot
No problem.
QUESTION: How can I transfer the tokens from POA network wizard to meta mask? I've started my crowd sale and public wants to invest, therefore I want to send them tokens rather than providing them the link to invest on.

I've just created FAQ section. You can find there answers to your questions:
https://github.com/poanetwork/token-wizard/wiki/FAQ#4-what-is-the-total-supply-of-token-created-by-token-wizard
https://github.com/poanetwork/token-wizard/wiki/FAQ#5-i-dont-want-to-create-crowdsale-but-i-need-to-create-erc20-token-could-i-do-it-with-token-wizard

Dear Victor,
Thanks for the useful link.
However, the info in the link does not answer my query in the following link ,
https://github.com/poanetwork/token-wizard/issues/836

From: Victor Baranov<EMAIL_ADDRESS>Sent: 27 April 2018 12:58
To: poanetwork/token-wizard
Cc: drdonjuan; Author
Subject: Re: [poanetwork/token-wizard] Transferring tokens from POA network token wizard to metamask (#827)
I've just created FAQ section. You can find there answers to your questions:
https://github.com/poanetwork/token-wizard/wiki/FAQ#4-what-is-the-total-supply-of-token-created-by-token-wizard
[https://avatars0.githubusercontent.com/u/28943015?s=400&v=4]https://github.com/poanetwork/token-wizard/wiki/FAQ#4-what-is-the-total-supply-of-token-created-by-token-wizard
poanetwork/token-wizardhttps://github.com/poanetwork/token-wizard/wiki/FAQ#4-what-is-the-total-supply-of-token-created-by-token-wizard
github.com
token-wizard - Create ERC20 token and crowdsale campaigns (ICO) on Ethereum networks using open source Wizard. No coding skills required. Decentralized, open source, free.
https://github.com/poanetwork/token-wizard/wiki/FAQ#5-i-dont-want-to-create-crowdsale-but-i-need-to-create-erc20-token-could-i-do-it-with-token-wizard
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/poanetwork/token-wizard/issues/827#issuecomment-384949236, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AkmHJ0rZ4sGeqKKO8tQ9WwEyyUKD-vofks5tswfggaJpZM4Tkjpz.

Please ignore my previous reply. That was supposed to be for #836

Hello,
Recently I've transferred from Binance all my POA holdings to Trust Wallet, then I've tried to withdraw them to my personal bank account or to convert them but I was unable to find this crypto in the trade panel. After this I've tried to transfer again to metamask. The transactions appears to be successfully but I don't see any POA in Metamask..
Any help here? :/


Upgrade to v2 broke my automations

Yesterday I updated to v2.0.2 from v1.0.19. I have an automation to set the start time of my AEG dishwasher during the night when the electricity prices are lowest. The automation was broken after I updated the integration. Turns out that basically all sensors where recreated with a _2 suffix. As an example, I used to have a sensor called sensor.aeg_afwasmachine_timetoend, which is now called sensor.aeg_afwasmachine_timetoend_2. It looks like it's the exact same sensor, but with a different name. Is this a bug or a deliberate choice?
Also, there was no warning about breaking changes in the change log of the release. Would have been nice to be warned about this. It would have been even nicer to know what breaking changes there were, so that I could have changed my automation pro-actively.

I do indeed see unavailable "ghost" entities. I can supply you with logs, but I'd rather do that in a private channel, since my logs will contain a lot of info about my home. Let me know if you're interested in my logs and how I can get them to you in a secure way.

Not necessarily : you can remove all the ghost entities and then you shouldn't have duplicate entities. Then you can either :
1/ remove the integration completely and reinstall it to have the correct names
2/ rename the entities that match to previous names

Sorry this was noted as a breaking change on the PR for v2 but seems missed in notifications for upgrade
I agree with the solution being remove and re-add the integration - the entity ID format was updated as I found an issue in them not being unique on my devices

Had the same problem, that after this update all entities very duplicated with "_2" and had to fix a lot of automations and a lot of dashboards :-(  I hope this will never happen again!

Ohmy, you shouldn't have to change automations : this _2 effect happens if old entities are still there but not instantiated anymore (ghost entities). They must be removed and you can rename the _2 to the old name again, or more simple delete the integration and reinstall it to get back the regular names

@albaintor  this was side effect of the updated entity_id, becuase i was receiving duplicate entity name errors
I didnt do a migration from the old name, but did note it as a breaking change. And recommended a reinstall as part of the upgrada. that would ensure the _2 is resolved and new names maintained

Isn't there a way to prevent this from happening at all? I've never seen something like this with other integrations. I mean, it's nice that there's a work around, but it would be better if the entities weren't duplicated in the first place.

Yes there are ways to migrate them, but it's complicated and can still lead to these issues if you don't get it right, especially as the issue it was solving was duplicate id's
Anyone with the issue would also need to delete the newly created v2 entries anyway, so starting with a clean slate is 100x easier as a fix in the interim


event: reduce log level for min timer complete message

Signed-off-by: Louis Opter<EMAIL_ADDRESS>
For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Commit Message: event: reduce log level for min timer complete message
Additional Description:
Risk Level: low
Testing: existing CI
Release Notes: event: reduce log level for min timer complete message

Thanks for the fix to reduce log spam.


Passive or non-passive event listeners

It would be nice if we could set the event handlers created to be passive or non-passive. That way we can also get rid of a warning in Chrome when working with events.

Please forgive my ignorance, but isn't an event listener always passive? I've never heard of this distinction before.

If I'm not mistaken, passive event listeners cannot cancel the events they receive, while active ones can.

Thanks @Rayraz for jumping in, that really helps!
I studied the topic a bit and concluded that it's probably best to wait for https://github.com/jquery/jquery/issues/2871 to be resolved before implementing support in Backbone.


Modify access-control-allow-origin header on api request(Graphql)

We need to set cors rules on appsync to pass security checks but I was unable to find option to modify cors headers, is it even possible with amplify and appsync?

@JonMGC is there any documentation for how you did this with a cloudfront distribution?

@jamesclancy You can set AppSync API as an origin for Cloudfront, then modify the Access-Control-Allow-Origin header: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/modifying-response-headers.html
Just to clarify this is for a Cloudfront distribution provisioned through through CDK. I am not sure if/how you can do this with Amplify.


feat: project page implementation

This is definitely in the right direction, thanks for working on the PR!
Not: Could you rename the PostCard component to ProjectCard or something more representative of what it does?

Hi @kiranharidas187,
Please do not open a new pull request when you commit a change, the PR automatically gets updated with the new commit.
Closing #14 and reviewing this PR instead.
Thanks


Added Profile Readme details in data.json

@AllanRegush @Nitesh-thapliyal I have made the suggested changes.

It looks like there is a conflict could you resolve this? If you need any help let me know. :nerd_face:

I guess it is fine now @AllanRegush .

It looks like someones entry got over ridden. If you need any help let me know :nerd_face:

Really sorry about that @AllanRegush . I have created a new PR  #356  for the same as I faced some issues.


fix: loading of mongoose instrumentation due to invalid package name

The instrumentation was moved to OTel, but in the 2.2.0 release only package.json was updated

Codecov Report
Patch and project coverage have no change.

Comparison is base (86b0cdc) 85.99% compared to head (644b5eb) 85.99%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #715   +/-   ##
=======================================
  Coverage   85.99%   85.99%
=======================================
  Files          28       28
  Lines        1264     1264
  Branches      285      285
=======================================
  Hits         1087     1087
  Misses        177      177

Impacted Files
Coverage Δ

src/instrumentations/index.ts
100.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


npm run build failed

Here is my npm-debug.log:
0 info it worked if it ends with ok
1 verbose cli [ '/home/spaceboyross/.nvm/versions/node/v7.5.0/bin/node',
1 verbose cli   '/home/spaceboyross/.nvm/versions/node/v7.5.0/bin/npm',
1 verbose cli   'run',
1 verbose cli   'build' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prebuild, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /home/spaceboyross/.nvm/versions/node/v7.5.0/lib/node_modules/npm/bin/node-gyp-bin:/home/spaceboyross/Documents/Nodebuntu/node_modules/.bin:/home/spaceboyross/.nvm/versions/node/v7.5.0/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/spaceboyross/.local/bin:/home/spaceboyross/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/spaceboyross/Documents/Nodebuntu
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'scripts/build' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 10  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec build script
14 verbose stack Error<EMAIL_ADDRESS>build: scripts/build
14 verbose stack Exit status 10
14 verbose stack     at EventEmitter. (/home/spaceboyross/.nvm/versions/node/v7.5.0/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:192:7)
14 verbose stack     at ChildProcess. (/home/spaceboyross/.nvm/versions/node/v7.5.0/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:192:7)
14 verbose stack     at maybeClose (internal/child_process.js:890:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /home/spaceboyross/Documents/Nodebuntu
17 error Linux 4.9.14-200.fc25.x86_64
18 error argv "/home/spaceboyross/.nvm/versions/node/v7.5.0/bin/node" "/home/spaceboyross/.nvm/versions/node/v7.5.0/bin/npm" "run" "build"
19 error node v7.5.0
20 error npm  v4.1.2
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>build: scripts/build
22 error Exit status 10
23 error Failed at the<EMAIL_ADDRESS>build script 'scripts/build'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the Nodebuntu package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     scripts/build
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs Nodebuntu
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls Nodebuntu
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Nodebuntu? Is that a fork of NodeOS?
El 19/4/2017 3:54, "SpaceboyRoss01"<EMAIL_ADDRESS>escribió:

Here is my npm-debug.log:
0 info it worked if it ends with ok
1 verbose cli [ '/home/spaceboyross/.nvm/versions/node/v7.5.0/bin/node',
1 verbose cli '/home/spaceboyross/.nvm/versions/node/v7.5.0/bin/npm',
1 verbose cli 'run',
1 verbose cli 'build' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prebuild,
continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle
true
9 verbose lifecycle<EMAIL_ADDRESS>PATH:
/home/spaceboyross/.nvm/versions/node/v7.5.0/lib/node_
modules/npm/bin/node-gyp-bin:/home/spaceboyross/Documents/
Nodebuntu/node_modules/.bin:/home/spaceboyross/.nvm/
versions/node/v7.5.0/bin:/usr/local/bin:/usr/local/sbin:/
usr/bin:/usr/sbin:/home/spaceboyross/.local/bin:/home/spaceboyross/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD:
/home/spaceboyross/Documents/Nodebuntu
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c',
'scripts/build' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 10 signal:
null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec build script
14 verbose stack Error<EMAIL_ADDRESS>build: scripts/build
14 verbose stack Exit status 10
14 verbose stack at EventEmitter. (/home/spaceboyross/.nvm/
versions/node/v7.5.0/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:192:7)
14 verbose stack at ChildProcess. (/home/spaceboyross/.nvm/
versions/node/v7.5.0/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:192:7)
14 verbose stack at maybeClose (internal/child_process.js:890:16)
14 verbose stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:226:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /home/spaceboyross/Documents/Nodebuntu
17 error Linux 4.9.14-200.fc25.x86_64
18 error argv "/home/spaceboyross/.nvm/versions/node/v7.5.0/bin/node"
"/home/spaceboyross/.nvm/versions/node/v7.5.0/bin/npm" "run" "build"
19 error node v7.5.0
20 error npm v4.1.2
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>build: scripts/build
22 error Exit status 10
23 error Failed at the<EMAIL_ADDRESS>build script 'scripts/build'.
23 error Make sure you have the latest version of node.js and npm
installed.
23 error If you do, this is most likely a problem with the Nodebuntu
package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error scripts/build
23 error You can get information on how to open an issue for this project
with:
23 error npm bugs Nodebuntu
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls Nodebuntu
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/350, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgfvpyoLDAsIXBgoBtCYVaT8S2kCu3Yks5rxWlEgaJpZM4NBGmK
.

Yea

Seems it exited with error 10. Without having the actual code I couldn't tell you what's happening. Could you point us to it?

I found out the problem, I modified and build nodeos-userfs in its directory

Cool then :-) What changes are you doing?

Making it say something else in the usersfs init file

If you don't provide more info about what steps are you doing we can't help you... :-/

This is the repo: https://github.com/Ross-Computers/Nodebuntu
I modified the node_modules/nodeos-usersfs/resources/init.js to have:
#!/usr/bin/env node

console.log("Nodebuntu 17.04 (Zesty Zapus)");

No wonder you cant build your Nodebuntu (NodeOS) fork if you upload all dependencies which are > 500mb or so to github.
The appropriate way would be that you fork the repositories you want to modify (including NodeOS), then change the things you want to do in your usersfs and push them to your fork then clone the NodeOS fork and the usersfs fork to your machine and change the following places to build your own usersfs inside NodeOS
package.json (NodeOS fork)
{
  "name": "NodeOS",
  "version": "1.0.0-RC3",
  "description": "Lightweight operating system using Node.js as userspace",
  "scripts": {
    "BigRedButton": "scripts/BigRedButton",
    "docker": "scripts/docker",
    "dockerBuild": "scripts/dockerBuild",
    "dockerClean": "docker volume rm $(docker volume ls -qf dangling=true) || exit 0",
    "build": "scripts/build",
    "postbuild": "scripts/postbuild",
    "postinstall": "scripts/postinstall",
    "publish": "scripts/publish",
    "start": "scripts/start",
    "test": "scripts/test",
    "unbuild": "scripts/unbuild"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/NodeOS/NodeOS.git"
  },
  "keywords": [
    "OS",
    "Linux",
    "npm"
  ],
  "author": "Jacob Groundwater<EMAIL_ADDRESS>  "contributors": [
    "Jesús Leganés Combarro 'piranna'<EMAIL_ADDRESS>  ],
  "license": "MIT",
  "bugs": {
    "url": "https://github.com/NodeOS/NodeOS/issues"
  },
  "homepage": "http://node-os.com",
  "private": true,
  "dependencies": {
    "nodeos-barebones": "^1.0.0-RC3.1",
    "nodeos-initramfs": "^1.0.0-RC3.2",
    "nodeos-usersfs": "^1.0.0-RC3.2"     <--- change this to: "nodebuntu-usersfs": "^1.0.0"
  },
  "devDependencies": {
    "cpio2tar": "^0.0.5",
    "minimist": "^1.2.0",
    "nodeos-bootfs": "^1.0.0-RC3.0",
    "nodeos-cross-toolchain": "^1.0.0-RC3.1",
    "prebuild": "piranna/prebuild#prerelease",
    "qemu": "^2.8.0",
    "suppose": "^0.6.1",
    "tar2ext": "^0.0.2"
  }
}

dont install yet, go into your node_modules and search for the nodebuntu-usersfs (its just a placeholder for your usersfs fork) and open up the package.json and remove this prebuild-install -d https://github.com/NodeOS/nodeos-usersfs/releases/download/v{version}/{platform}-{arch}.tar.gz ||
it should only be this (buildDependencies && npm run build) for the install
now you go into the scripts folder of the NodeOS fork and edit the line 32 on the build script from this:
#!/usr/bin/env bash

set -o pipefail

while getopts ":k:p:" opt; do
  case $opt in
    k)
      KERNEL="$OPTARG"  # linux, netbsd, nokernel
    ;;

    p)
      PLATFORM="$OPTARG"  # lxc, qemu, wsl
    ;;
  esac
done

# Default kernel and platform
if [[ -z "$KERNEL" ]]; then
  KERNEL=linux
fi

if [[ -z "$PLATFORM" ]]; then
  PLATFORM=qemu
fi

TOOLCHAIN=`node -p "require('nodeos-cross-toolchain')"`
BAREBONES=`node -p "require('nodeos-barebones')"`
INITRAMFS=`node -p "require('nodeos-initramfs')"`
USERSFS=`  node -p "require('nodeos-usersfs')"`

source $TOOLCHAIN/scripts/adjustEnvVars.sh || exit $?

OUT_DIR=`pwd`/out/$CPU_FAMILY/$MACHINE/$PLATFORM

export MACHINE

if [[ "$PLATFORM" == "docker" ]]; then
  export KERNEL=nokernel
fi

NPMi="npm install --arch=$NODE_ARCH --production"

....

to this:
#!/usr/bin/env bash

set -o pipefail

while getopts ":k:p:" opt; do
  case $opt in
    k)
      KERNEL="$OPTARG"  # linux, netbsd, nokernel
    ;;

    p)
      PLATFORM="$OPTARG"  # lxc, qemu, wsl
    ;;
  esac
done

# Default kernel and platform
if [[ -z "$KERNEL" ]]; then
  KERNEL=linux
fi

if [[ -z "$PLATFORM" ]]; then
  PLATFORM=qemu
fi

TOOLCHAIN=`node -p "require('nodeos-cross-toolchain')"`
BAREBONES=`node -p "require('nodeos-barebones')"`
INITRAMFS=`node -p "require('nodeos-initramfs')"`
USERSFS=`  node -p "require('nodebuntu-usersfs')"` # <-- that

source $TOOLCHAIN/scripts/adjustEnvVars.sh || exit $?

OUT_DIR=`pwd`/out/$CPU_FAMILY/$MACHINE/$PLATFORM

export MACHINE

if [[ "$PLATFORM" == "docker" ]]; then
  export KERNEL=nokernel
fi

NPMi="npm install --arch=$NODE_ARCH --production"

...


OSX Install

pip install imaginairy==6.0.0a0 --upgrade
Seems to require https://github.com/huggingface/transformers/issues/2831#issuecomment-1001437376
But then:
/opt/homebrew/lib/python3.9/site-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension: dlopen(/opt/homebrew/lib/python3.9/site-packages/torchvision/image.so, 0x0006): Symbol not found: (__ZN2at4_ops19empty_memory_format4callEN3c108ArrayRefINS2_6SymIntEEENS2_8optionalINS2_10ScalarTypeEEENS6_INS2_6LayoutEEENS6_INS2_6DeviceEEENS6_IbEENS6_INS2_12MemoryFormatEEE)
  Referenced from: '/opt/homebrew/lib/python3.9/site-packages/torchvision/image.so'
  Expected in: '/opt/homebrew/lib/python3.9/site-packages/torch/lib/libtorch_cpu.dylib'
  warn(f"Failed to load image Python extension: {e}")
Traceback (most recent call last):
  File "/opt/homebrew/bin/imagine", line 5, in <module>
    from imaginairy.cmds import imagine_cmd
  File "/opt/homebrew/lib/python3.9/site-packages/imaginairy/__init__.py", line 7, in <module>
    from .api import imagine, imagine_image_files  # noqa
  File "/opt/homebrew/lib/python3.9/site-packages/imaginairy/api.py", line 14, in <module>
    from imaginairy.enhancers.describe_image_blip import generate_caption
  File "/opt/homebrew/lib/python3.9/site-packages/imaginairy/enhancers/describe_image_blip.py", line 13, in <module>
    device = get_device()
  File "/opt/homebrew/lib/python3.9/site-packages/imaginairy/utils.py", line 22, in get_device
    if torch.backends.mps.is_available():
AttributeError: module 'torch.backends' has no attribute 'mps'

Are you on an M1 laptop? what version of torch is installed?

Closing until we get more information.

torch in /opt/homebrew/lib/python3.9/site-packages (1.11.0)

Now I got it running but it just dies:
~$ imagine "a scenic landscape" "a photo of a dog" "photo of a fruit bowl" "portrait photo of a freckled woman"
Killed: 9

I think I got it working with pip3 install --pre torch torchvision torchaudio --extra-index-url https://download.pytorch.org/whl/nightly/cpu


create player class

done https://github.com/E-truco/Player_class/commit/20be1de358d00806eb7c98a9baa13c7d1f4523ce


Click anywhere within lunch block to toggle

A couple students couldn't initially figure out that they needed to click the underlined "First" or "Second" to toggle.

Fixed in 2474bf7.


Problem about using multi-camera

Hi, thank you for sharing the great work!
Our vehicle is equipped with six cameras, mounted on the front, back, left, and right, each with a different height. I have tested cameras with similar heights and achieved good results. However, I found that when I use all the cameras, some of them have significantly different heights, resulting in poor performance.
The code below only uses one camera height to estimate flat plane. I would like to know how I should modify the code to adapt to these multiple cameras？Any reply would be appreciated.
`        # 6. estimate flat plane
self.file_check()
self.label_valid_check()
ref_camera2world_all = np.array(self.ref_camera2world_all)
transform_normal2origin = robust_estimate_flatplane(np.array(ref_camera2world_all)[:, :3, 3]).astype(np.float32)
transform_normal2origin[0, 3] = -self.choose_pt[0]
transform_normal2origin[1, 3] = -self.choose_pt[1]
transform_normal2origin[2, 3] += self.camera_height
self.ref_camera2world_all = transform_normal2origin[None] @ self.ref_camera2world_all

@MrlynnBei Hi, you can refer https://github.com/DRosemei/RoMe/issues/42 for help. The estimated flat plane is not always good.

@MrlynnBei Hi, you can refer #42 for help. The estimated flat plane is not always good.

Okk. Thanks!  And I have another question: Can the world coordinate system of the camera pose be an ENU system? or Can the camera pose be expressed in ENU coordinates?（tf_enu_cami）？
I saw the code that transform the tf_cam0_cami to tf_chassis_cami：(Am I understanding this correctly?)
camera_poses = self.camera2chassis @ camera_poses  # refrece to chassis
Any reply would be appreciated.

@MrlynnBei We use local corrdinate systems and save a tranform from local to global coordinate. It would be better for understanding and reconstruction.


[BUG]: Consider changing After=network-online.target instead of After=network.target

What happened?
Just noticed this while modifying the unit file, but I believe it should be After=network-online.target instead of After=network.target ( see https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/). Could be wrong about this though.
Versions
Pipelines agent v3.220.5 / Linux
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
No response
Version controll system
No response
Relevant log output
No response

Hi @benlongo, thanks for the reporting! We will check and come back with the results

Reading the doc provided @benlongo I think this is an interesting comment about network-online.target
It is strongly recommended not to pull in this target too liberally: for example network server software should generally not pull this in (since server software generally is happy to accept local connections even before any routable network interface is up), its primary purpose is network client software that cannot operate without network.
I also looked at the default unit file for Apache (httpd) in RHEL 8 as an example to compare and it uses network.target
[Unit]
Description=The Apache HTTP Server
After=network.target remote-fs.target nss-lookup.target
Documentation=man:httpd(8)
Documentation=man:apachectl(8)

Not sure what distro you're using, but would be interested to know what other services use in that distro?
Have you had any issues with timeouts or agent communication with network.target?


Sentence segmentation correction with reference markers - Figures ref markers seems not work

I think I found something interesting, might be due to the change to the ref markers annotations for figures, when we changed from <ref>Fig. 3</ref> to Fig. <ref>3</ref>. I'm not sure it's actually something that can be fixed.
Example of document: https://pubs.rsc.org/en/content/articlepdf/2017/nr/c6nr09464c
I have a nice example between page 3684 and 3685: Moreover, a bimodal grain size distribution was observed in the magnet with a large loading rate [Fig. 19(a)]. On the contrary, it was observed that grains were well aligned with the c-axis parallel to the loading direc- tion in the slowly deformed magnet [Fig. 19(b)].
They appear in the output as this:
                    <s>Moreover, a bimodal grain size
                        <ref type="bibr" target="#b78">79</ref> distribution was observed in the magnet with a large loading rate [Fig.
                    </s>
                    <s>
                        <ref type="figure" target="#fig_16">19(a)</ref>].
                    </s>
                    <s>On the contrary, it was observed that grains were well aligned with the c-axis parallel to the loading direction in the slowly deformed magnet [Fig.</s>
                    <s>
                        <ref type="figure" target="#fig_16">19(b)</ref>].
                    </s>
                </p>

Since the sentence is segmented more than one character before the reference markers (due to the . after Fig) it seems we are not able to correct the sentence range in the first part:
https://github.com/kermitt2/grobid/blob/2c720dd55344f48edab83f636f9bff640a92fbdc/grobid-core/src/main/java/org/grobid/core/utilities/SentenceUtilities.java#L144
but also since it's not a superscript, we cannot fix when synchronizing with the layout tokens in the second part:
https://github.com/kermitt2/grobid/blob/2c720dd55344f48edab83f636f9bff640a92fbdc/grobid-core/src/main/java/org/grobid/core/utilities/SentenceUtilities.java#L198C14-L198C14
Maybe we can add a special check if it's a Figure marker and the previous sentence ends with Fig. (Figure should not be a problem, it seems the issue is that the sentence segmentation get tricked by the .)

Yes, indeed the pragmatic segmenter give much better results, but indeed it's 6 time slower or so 😅


[UEFI-compatible] auto detect & tag UEFI compatible

Cont. of https://github.com/GoogleCloudPlatform/compute-image-tools/pull/1322
Motivation: user may not have enough knowledge to determine whether their disk is UEFI-boot. Even they can determine it, gcloud & pantheon surface doesn't support importing a image with UEFI_COMPATIBLE support. (Only direct API supports that, which is not the main stream). We automatically detect it and mark it UEFI_COMPATIBLE based on the partition info.
Impl: after inflation stage & before translation stage, there is a inspection & mutation stage. We check the partition info in inspection stage to explore EFI partition. If any, we return a flag. The mutation stage will consume it: if it's true, we will create a copy of the inflated disk with an additional guestOSFeature=UEFI_COMPATIBLE.
Changes including e2e tests, which covered:
MBR+BIOS (linux + windows)
MBR+UEFI (linux)
GPT+Hybrid (linux)
GPT+UEFI (linux + windows)
Not covered: GPT+BIOS, since GCVP doesn't support that.

Refactored how to call the loggable to emit metrics


Firebase Authentication

Using Firebase:

Create Firebase project

Email<EMAIL_ADDRESS>Password: Goodgradesplease9

Allow user authentication with Firebase project

Create user login/sign-out functionality
Create user Sign-up functionality
Create “service” file for easy access to Firebase authentication functionality

This was completed in the feature-firebase-CRUD pull request


Maybe we shouldn't validate the token when using the webhook rule

Currently we validate the token before calling the webhook. Maybe we shouldn't validate the token when using the webhook rule. We can leave it to the webhook endpoint to authenticate and authorise the request.
This is beneficial since even requests with a custom token scheme which sc doesn't support will work. The downside is that users will have to validate tokens themselves.

Give a flag whether to verify in sc or not.

Fixed in next version


Extra GAPs Arg out_fpath

Add a new convenience argument out_fpath

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (fcb257d) 98.57% compared to head (29c3079) 98.57%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   98.57%   98.57%
=======================================
  Files          26       26
  Lines        2460     2460
  Branches      407      407
=======================================
  Hits         2425     2425
  Misses         22       22
  Partials       13       13

Flag
Coverage Δ

unittests
98.57% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

gaps/cli/command.py
100.00% <ø> (ø)

gaps/cli/config.py
98.96% <ø> (ø)

gaps/version.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


ERESOLVE unable to resolve dependency tree while installing typechain @typechain/hardhat @typechain/ethers-v5

Hi all,
I've tried to install like in the readme file with the command npm install --save-dev typechain @typechain/hardhat @typechain/ethers-v5 and I've got this error:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/typechain
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@ethereum-waffle/compiler
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/ethereum-waffle
npm ERR!       peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!       node_modules/@nomiclabs/hardhat-waffle
npm ERR!         dev<EMAIL_ADDRESS>from the root project
npm ERR!       1 more (the root project)
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@typechain/ethers-v5
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@ethereum-waffle/compiler
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!       node_modules/ethereum-waffle
npm ERR!         peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!         node_modules/@nomiclabs/hardhat-waffle
npm ERR!         1 more (the root project)
npm ERR!     dev @typechain/ethers-v5@"*" from the root project
npm ERR!   1 more (the root project)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! dev @typechain/hardhat@"*" from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/typechain
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@typechain/hardhat
npm ERR!     dev @typechain/hardhat@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/MY_WORKSPACE/.npm/eresolve-report.txt for a full report.

npm ERR!      /Users/MY_WORKSPACE/.npm/_logs/2021-06-21T21_07_39_358Z-debug.log

what should I do? the hardhat project is brand new

As npm suggests, try with --force. It might be due to the dep conflict with waffle...

Don't ask me why but the whole problem was because when I did npm install it installed old packages not compatible one with another

Don't ask me why but the whole problem was because when I did npm install it installed old packages not compatible one with another

I'm seeing the same error. How did you resolve the issue? To me, this looked like<EMAIL_ADDRESS>would need to update its @typechain/ethers-v5 version (or I need to use a lower version of typechain...).

Don't ask me why but the whole problem was because when I did npm install it installed old packages not compatible one with another

I'm seeing the same error. How did you resolve the issue? To me, this looked like<EMAIL_ADDRESS>would need to update its @typechain/ethers-v5 version (or I need to use a lower version of typechain...).

just remove all the libraries, clean you npm_mobules and reinstall the using the latest one

Don't ask me why but the whole problem was because when I did npm install it installed old packages not compatible one with another

I'm seeing the same error. How did you resolve the issue? To me, this looked like<EMAIL_ADDRESS>would need to update its @typechain/ethers-v5 version (or I need to use a lower version of typechain...).

just remove all the libraries, clean you npm_mobules and reinstall the using the latest one

Hmm, I think the problem is that<EMAIL_ADDRESS>is the latest version. I ended up just force installing and it worked fine. Thanks though!

I ended up with '--force installation' too!! Don't know that will it be affected for the rest.

--force alone didn't work for me. I'm using the latest hardhat (2.6.5) and latest typechain hardhat plugin (2.3.0).
But this article helped -
https://www.carlrippon.com/upgrading-npm-dependencies/
So I used npm outdated to investigate. Then -
npm install --force typechain@latest
npm install @typechain/ethers-v5@latest

So far so good :S...
@chubbyavo seem to have detected the source of the problem.


Fixed a little text format on concept of SIgnalR upstream page

I found a unmatched text format on this page.

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


Update README to point to example/.

The README currently points to a nonexistent file. I'm changing it to point to the univalence development.

I feel it is better to point to example/README.prl, and only mention the univalence for citation?

That's fine too, but I was a little confused about what README.prl is supposed to be.

example/README.prl is intended to be the first file for users to look at. Maybe example/basics.prl? @jonsterling


Merged in changes made by @bigsmoke9527

@whardier
Could you submit some test case with the new feature?
It will be great if you also update the README.md.


header-text div covers clickable home link

The header-text div covers some of the logo you can click to go back to the homepage.
This affects both the mobile and desktop views. Encountered on Chrome 57 and Firefox 50 on OS X.
I will open a PR shortly to fix.

Oooh good catch, thanks so much for putting up a PR for this :)


fix: skipLibCheck should be recommended in the reference

Description

it was added as a default for tsc --init a few months ago and
recently added to the @tsconfig/recommended base as well

Tags
Found this in https://github.com/formium/tsdx/issues/529#issuecomment-679746098 while exploring the docs to see updates on its recommended status

Cool, yeah 👍🏻


fix compile problem without sse4.2

What type of PR is this：

[ ] bug
[ ] feature
[ ] enhancement
[X ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

fix compile problem without sse4.2

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


SSL default cipher suite definition over config file

I would like to know if it would be possible to extend the code to support default cipher suite definition over config file. Today it is defined via #define SSL_DEFAULT_CIPHER_LIST, it would be great to have it on openssl.cnf.

there are open PR's that will allow this; see PR 194.


Why use bias_init_with_prob in fcos/foveabox/reppoints？

In fcos/foveabox/reppoints, conv for cls in the final always use bias_cls = bias_init_with_prob(0.01) for initialization.  Is it related to their use of Focal loss? If the numbers of positive and negative samples  balanced after sampling, is this not necessary?
def bias_init_with_prob(prior_prob):
    """ initialize conv/fc bias value according to giving probablity"""
    bias_init = float(-np.log((1 - prior_prob) / prior_prob))
    return bias_init

It's a typical convention for initializing weights when adopting the focal loss. You may refer to Focal Loss for Dense Object Detection for detailed reasons.


"/smartcard" with "/drive:*,hotplug" crash

Hey there,
I have a problem with current master. I try to get away from
/drive:USB,/media

to
/drive:*,hotplug

For its own, it's working. But whenever I combine with
/smartcard

it's crashing:

Had no time for DEBUG compile... Will do this later, but perhaps someone has an idea before.
Compiled with
cmake -DCMAKE_BUILD_TYPE=Release -DWITH_SSE2=ON -DWITH_X11=ON -DWITH_DIRECTFB=OFF -DWITH_ALSA=ON -DWITH_PULSE=ON -DWITH_CUPS=ON -DWITH_PCSC=ON -DWITH_FFMPEG=OFF -DWITH_GSTREAMER=OFF -DWITH_JPEG=ON -DWITH_IPP=OFF -DWITH_XKBFILE=ON -DWITH_XINERAMA=ON -DWITH_XEXT=ON -DWITH_XCURSOR=ON -DWITH_XV=OFF -DWITH_XI=OFF -DWITH_XRENDER=ON

ok... faster than I thought. Compiled with debug, but no more infos...
(tried freerdp 3 times... as you can see in the pic. ERROR because I cancelled login on server)

Try "/smartcard:" with "/drive:*,hotplug"

@hyacinthes don't know how you got this, but the simple ":" makes it working 1 out of 20 times... Without the ":" it never works.
Did just some quick tests. Not reliable for production. Will try more next weekend and report back.

damn... not working... I use the mentioned command line options and sometimes it connects to the server, but as soon as I connect an USB-stick, it crashes with "Speicherzugriffsfehler" (segfault?)
so... It is not working with smartcard and "usb hotplug".

I'm still digging it. I'll report back if any new information.

Excited you guys are focused on smartcard debug.... would this be a related/same issue when trying to use the FreeRDP plugin on TSX?  When set to redirect a smartcard the connection establishes but the plugin crashes; doesn't happen with the same profile and smartcard redirection disabled.   Thanks again for the dev focus!

Tested some more, but not getting useful output. Also had to switch back to an older build, because the smartcard plugin is crashing after pulling the smartcard out. Pushing it back in ends in no smartcard found... Will open another issue with more details. (No smartcard is a showstopper in this environment)
Unfortunately I have no more time to look closer at "smartcard" and "USB hotplug". Perhaps in the beginning of next year...
@hyacinthes
thx for stepping in :)

I confirm that this issue is still on the actual build. It's not possible to combine /smartcard and /drive:,hotplug
It's working with a fixed redirected drive, but not with the hotplug drive feature...
OK: xfreerdp /v:xxx /u:xxx /p:xxx /smartcard /drive:usb0,/media/usb0
OK: xfreerdp /v:xxx /u:xxx /p:xxx /smartcard
OK: xfreerdp /v:xxx /u:xxx /p:xxx /drive:,hotplug
Not OK (Seg fail): xfreerdp /v:xxx /u:xxx /p:xxx /smartcard /drive:*,/media/usb0
Example of log with WLOG_LEVEL=debug
[17:47:00:815] [4356:4356] [DEBUG][com.freerdp.client.common.cmdline] - windows: 0/1 posix: -1000/0 compat: -1000/0
[17:47:00:815] [4356:4358] [INFO][com.freerdp.client.common.cmdline] - loading channel rdpdr
[17:47:00:815] [4356:4358] [INFO][com.freerdp.client.common.cmdline] - loading channel rdpsnd
[17:47:00:815] [4356:4358] [DEBUG][com.freerdp.channels.cliprdr.client] - VirtualChannelEntry
[17:47:00:815] [4356:4358] [INFO][com.freerdp.client.common.cmdline] - loading channel cliprdr
[17:47:00:816] [4356:4358] [DEBUG][com.freerdp.client.x11] - Searching for XInput pointer device
[17:47:00:816] [4356:4358] [DEBUG][com.freerdp.client.x11] - Pointer device: 7
[17:47:00:817] [4356:4358] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[17:47:00:817] [4356:4358] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[17:47:00:817] [4356:4358] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE
[17:47:00:817] [4356:4358] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: TRUE
[17:47:00:817] [4356:4358] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[17:47:00:817] [4356:4358] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[17:47:00:817] [4356:4358] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[17:47:00:817] [4356:4358] [DEBUG][com.freerdp.core.nego] - Attempting NLA security
[17:47:00:817] [4356:4358] [INFO][com.freerdp.core.nego] - Detecting if host can be reached locally. - This might take some time.
[17:47:00:817] [4356:4358] [INFO][com.freerdp.core.nego] - To disable auto detection use /gateway-usage-method:direct
[17:47:00:826] [4356:4358] [DEBUG][com.freerdp.core.nego] - Adding terminating CRLF to routing token
[17:47:00:826] [4356:4358] [DEBUG][com.freerdp.core.nego] - RequestedProtocols: 3
[17:47:00:826] [4356:4359] [DEBUG][com.freerdp.core.transport] - Asynchronous transport thread started
[17:47:00:840] [4356:4358] [DEBUG][com.freerdp.core.nego] - RDP_NEG_RSP
[17:47:00:840] [4356:4358] [DEBUG][com.freerdp.core.nego] - selected_protocol: 2
[17:47:00:840] [4356:4358] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_FINAL
[17:47:00:840] [4356:4358] [DEBUG][com.freerdp.core.nego] - Negotiated NLA security
[17:47:00:840] [4356:4358] [DEBUG][com.freerdp.core.nego] - nego_security_connect with PROTOCOL_NLA
[17:47:00:862] [4356:4358] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExA
[17:47:00:862] [4356:4358] [DEBUG][com.freerdp.core.nla] - Sending Authentication Token
[17:47:00:862] [4356:4358] [DEBUG][com.freerdp.core.nla] - 0000 4e 54 4c 4d 53 53 50 00 01 00 00 00 b7 82 08 e2 NTLMSSP.........
[17:47:00:862] [4356:4358] [DEBUG][com.freerdp.core.nla] - 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[17:47:00:862] [4356:4358] [DEBUG][com.freerdp.core.nla] - 0020 06 01 b1 1d 00 00 00 0f                         ........
[17:47:00:872] [4356:4358] [DEBUG][com.freerdp.core.nla] - Sending Authentication Token
[17:47:00:872] [4356:4358] [DEBUG][com.freerdp.core.nla] - 0000 4e 54 4c 4d 53 53 50 00 03 00 00 00 18 00 18 00 NTLMSSP.........
[17:47:00:872] [4356:4358] [DEBUG][com.freerdp.core.nla] - 0010 92 00 00 00 2a 01 2a 01 aa 00 00 00 10 00 10 00 ..............
[17:47:00:872] [4356:4358] [DEBUG][com.freerdp.core.nla] - 0020 58 00 00 00 0c 00 0c 00 68 00 00 00 1e 00 1e 00 X.......h.......
[17:47:00:872] [4356:4358] [DEBUG][com.freerdp.core.nla] - 0030 74 00 00 00 10 00 10 00 d4 01 00 00 35 b2 88 e2 t...........5...
[17:47:00:872] [4356:4358] [DEBUG][com.freerdp.core.nla] - 0040 06 01 b1 1d 00 00 00 0f 67 ee c6 06 18 10 43 b5 ........g.....C.
[17:47:00:872] [4356:4358] [DEBUG][com.freerdp.core.nla] - 0050 a8 e2 93 03 4d b5 b5 3a 78 00 63 00 61 00 6c 00 ....M..:x.c.a.l.
[17:47:00:872] [4356:4358] [DEBUG][com.freerdp.core.nla] - 0060 69 00 62 00 75 00 72 00 72 00 6f 00 6d 00 61 00 i.b.u.r.r.o.m.a.
[17:47:00:872] [4356:4358] [DEBUG][com.freerdp.core.nla] - 0070 69 00 6e 00 4c 00 58 00 58 00 30 00 30 00 30 00 i.n.L.X.X.0.0.0.
4356 Segmentation Fault

I've fixed some argument check issues within the drive channel, fixes the crash for me.
Could you check #3079 and see if it works for you too?

I really would like to test this now... But I have hardly free time atm. Will try as soon as possible (also the other issue with the smartcard), but it seems that I won't get it done till end of february.
@BUGgs are you going to test the patch?

Yes, testing today. I will get back to you ASAP.

Fixed ! I'm going to make deeper test this week to check that smartcard isn't broken by this commit, but globally, it seems ok.

@BUGgs Good to know, smartcard is not influenced by this commit (different channel, the files are private to drive redirection)

I've remade some tests today with a full smartcard remapping, and we had the issue again.
I seems to happen when a session was disconnected and we are trying to reconnect with hotplug and smartcard...
Trying to reproduce tomorrow

This PR breaks smartcard redirection on Ubuntu 14.04, see #3112