Can not create an account

I encountered an issue with the following code:
<?php

	$registration = new Registration($user["email"], $user["pass"], $user["name"]);
	$registration
		->setAge($user["age"])
		->setCountry($user["cc"])
		->setFemaleGender();

	if($bot->auth->register($registration)){
		echo "ok";
	}else{
		$bot->getLastError();
	}

Library version: ^5.9
PHP version: 7.2.20
I expected to get:
"ok"

But I actually get:
Array (
  [status] => failure
  [http_status] => 500
  [code] => 51
  [message] => Cannot read property 'length' of undefined
)

Thanks!

I also found the same issue, it's not like usual. i used PHP 7.2.24

I get the same error.
Any progress on issue fix?

Yes, looks like Pinterest has changed something in their API. Any help is appreciated. Feel free to debug and provide a PR 🙏

Hey. I've tries registering and it worked so the problem might not be with the API.
However, when today I tried registering another user, I've got the error presented above.
I've checked the response it contained the email, which I've used to register last time so I think there might be some cookies not deleted on new session. I've deleted all the cookies and now I'm getting the error 'UNHANDLED_EXCEPTION_IN_RESOURCE' and I'm pretty much stuck. Hope this helps.

I did something out and managed to make a new user.

Delete cookies file

Register<EMAIL_ADDRESS>

error with 'length'

DON'T delete cookies

Register<EMAIL_ADDRESS>(The same email as before)

error  'Email already taken.'

I think this proves that the problem should be cookie related rather than pinterest api related

I've found this 'workaround' to make it work.
What I've found while testing.

Also $bot->auth->register($registration) returning true did not mean in all cases, that my acc was registered
the 'Cannot read property 'length' of undefined' error appeared randomly.

while ($current_retry < $max_retry) {
$bot->getHttpClient()->removeCookies();
$current_retry += 1;
if ($bot->auth->register($registration)) {
	echo 'register_result: ok. Will try again to validate.' . PHP_EOL;
} else {
	echo 'register_result: error' . PHP_EOL;
	$error = $bot->getLastError();
	echo 'last_error: \'' . $error . '\'' . PHP_EOL;

	if (contains('Email already taken.', (string)$error)) {
		return TRUE;
	}
}

    rand_sleep();

}

Create new helpers class. Set name "RegistrationFix"
and add the code below to this class.
`<?php
namespace App\Helpers;
use seregazhuk\PinterestBot\Api\Forms\Registration;
class RegistrationFix extends Registration
{
/**
 * @var string
 */
protected $email;

/**
 * @var string
 */
protected $password;

/**
 * @var string
 */
protected $name;

/**
 * @var string
 */
protected $country = 'GB';

/**
 * @var string
 */
protected $age = '18';

/**
 * @var string
 */
protected $gender = 'male';

/**
 * @var string
 */
protected $site;

/**
 * @param string $email
 * @param string $password
 * @param string $name
 */
public function __construct($email, $password, $name)
{
    $this->email = $email;
    $this->password = $password;
    $this->name = $name;
}

/**
 * @param mixed $email
 * @return Registration
 */
public function setEmail($email)
{
    $this->email = $email;
    return $this;
}

/**
 * @param string $password
 * @return Registration
 */
public function setPassword($password)
{
    $this->password = $password;
    return $this;
}

/**
 * @param string $name
 * @return Registration
 */
public function setName($name)
{
    $this->name = $name;
    return $this;
}

/**
 * @param string $country
 * @return Registration
 */
public function setCountry($country)
{
    $this->country = $country;
    return $this;
}

/**
 * @param int $age
 * @return Registration
 */
public function setAge($age)
{
    // Pinterest requires age to be a string
    $this->age = (string)$age;
    return $this;
}

/**
 * @param string $gender
 * @return Registration
 */
public function setGender($gender)
{
    $this->gender = $gender;
    return $this;
}

/**
 * @return Registration
 */
public function setMaleGender()
{
    return $this->setGender('male');
}

/**
 * @return Registration
 */
public function setFemaleGender()
{
    return $this->setGender('female');
}

/**
 * @return array
 */
public function getData()
{
    return [
        'first_name'    => $this->name,
        'last_name'     => '',
        'email'         => $this->email,
        'password'      => $this->password,
        'age'           => $this->age,
        'country'       => $this->country,
        'container'     => 'home_page',
        'visited_pages' => "[]",
        'signupSource'  => 'homePage',
        'hybridTier' 	=> 'open',
        'page'			=> 'home',
        'user_behavior_data' => "{}"
    ];
}

/**
 * @param string $site
 * @return Registration
 */
public function setSite($site)
{
    $this->site = $site;
    return $this;
}

/**
 * @return string
 */
public function getSite()
{
    return $this->site;
}

}`
and use it that way
`$bot = PinterestBot::create();
    $registration = new<EMAIL_ADDRESS>'pasword123', 'Test Name');
    $registration
        ->setAge(27)
        ->setCountry('GB')
        ->setMaleGender();

    if($bot->auth->register($registration)){
        echo "ok";
    }else{
        echo $bot->getLastError();
    }`


Multimethods for functional programming routines

This PR adds multimethods that target functional programming routines. The multimethods are the following:

apply_along_axis
apply_over_axes
frompyfunc
piecewise

Notes:

The only multimethod missing is vectorize which is actually a class so it needs to wait for #61 to be done and its changes are merged before it can be added.
I've added onp.ufunc and da.ufunc.ufunc to the possible returned types in the tests. These are needed for testing the returned type of frompyfunc.

I'm wondering if the items in piecewise's argument condlist should be dispatched given that they are boolean arrays.

The default for apply_along_axis seems a bit complicated for now, I think I'll leave it for later.


Define how ports are requested (closes #25, #20, #19, #4)

Detailed discussions are in #25, #20, #19, #4.

Defined how requestPorts() method works
defined how getInfo() works
made SerialPortInfo into a map (was SerialPortDetails)
introduced the concept of "recommended serial port metadata"
defined the rules for "getting serial port metadata"
Updated the security considerations section.

Is this still happening?

On Saturday, May 9, 2015, Anne van Kesteren<EMAIL_ADDRESS>wrote:

Is this still happening?

Eventually... Maybe after SWs and Streams are more stable.

—
Reply to this email directly or view it on GitHub
https://github.com/whatwg/serial/pull/27#issuecomment-100436902.

Specifically, I meant this PR.

dunno anymore, it's been a long time since I last looked at this.

Ok, let me see about rebasing

Ok, I'm going to merge... there is a lot of good feedback here that still needs to be addressed, but we should open new issues for those.


Fix warning on usage

I see this warning on every usage:
~/.gem/jruby/2.3.1/gems/rack-test-0.6.3/lib/rack/test.rb:285: warning: instance variable @digest_username not initialized

Me too, please merge. I'm using Mike's fork atm :)

@mperham thank you for your pull-request.
@perlun
I think this PR's issue was fixed as below commit.
21784987fbf53ad5f9dc30adb915a193d3141131
So, I think that we do not need to merge this PR.
At least I did not see the warning message on latest Travis CI's jruby test.
https://travis-ci.org/rack-test/rack-test
@mperham @sandelius for that reason, I would close this PR.
But if you still see the issue, let us know.
Thank you.


Completion with ". " should work like with "source "

As it is not uncommon to use single dot instead of source it would be nice if completion for it would work the same. For example
source <TAB>

triggers completion with folders / files in current directory.
In bash the same goes for
. <TAB>

However, it does not seem to work in ZSH with oh-my-zsh.
Am I missing something?

The source and . (dot) builtins work slightly differently. See the documentation for . and for source.
If you want . to behave like source, i.e. to search in the current directory first, add ./ to the file argument.
Either way, this is a zsh issue, not an Oh My Zsh one. I hope that helped you understand it better.


Make partial allocation as selected when selecting promise date and partial group items when selecting partial allocation

What is the motivation for adding/enhancing this feature?

Currently when selecting promise date we enable the partial allocation value on the UI but are not updating its value in the backend.
Another case is that when selecting partial allocation, the group items allocation also needs to be updated as when partial allocation is selected we allow partial allocation for grouped items.
What are the acceptance criteria?

[ ] ...

Can you complete this feature request by yourself?

[x] YES
[ ] NO

Additional information

Verified and working fine in release v1.5.0. Hence, closing it.


configmanager add new function for update host

Issues associated with this PR
Your PR should present related issues you want to solve.
Solutions
You should show your solutions about the issues in your PR, including the overall solutions, details and the changes. At this time, Chinese is allowed to describe these.
UT result
Unit Test is needed if the code is changed, your unit test should cover boundary cases, corner cases, and some exceptional cases. And you need to show the UT result.
Benchmark
If your code involves the processing of every request, you should give the Benchmark Result.
Code Style

Make sure Goimports has run
Show Golint result

+1

Codecov Report

Merging #987 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #987      +/-   ##
==========================================
+ Coverage      55%   55.05%   +0.04%
==========================================
  Files         238      238
  Lines       23334    23367      +33
==========================================
+ Hits        12836    12865      +29
- Misses       9323     9325       +2
- Partials     1175     1177       +2

Impacted Files
Coverage Δ

pkg/configmanager/configmanager.go
95.45% <100%> (+0.8%)
:arrow_up:

pkg/module/http2/server.go
81.92% <0%> (-0.15%)
:arrow_down:

pkg/module/http2/transport.go
78.76% <0%> (-0.15%)
:arrow_down:

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 1609ae1...b8057da. Read the comment docs.


Fix precompiler to work with Handlebars 2.0.0

Added minor backward compatible changes to make barber-emblem work with new Handlebars.

@coladarci, have you been able to get this working? I am getting same issue with:
Compiler said: ReferenceError: Handlebars is not defined.
when using ember 1.10.0.beta3

No I haven't but I think my issue is with emblem
On Thu, Jan 8, 2015 at 3:54 AM Daniel Sudol<EMAIL_ADDRESS>wrote:

@coladarci https://github.com/coladarci, have you been able to get this
working? I am getting same issue with:
Compiler said: ReferenceError: Handlebars is not defined.
when using ember 1.10.0.beta3
--
Reply to this email directly or view it on GitHub
https://github.com/machty/barber-emblem/pull/1#issuecomment-69170015.

@danielspaniel try git clean -fd && git reset head? maybe just cache in tmp?

@Eric-Guo .. what are you talking about?  in which project do you mean ( to run git clean? ) ?? Do you mean rake assets:clobber or rake tmp:clear ??  puzzled
My Gemfile looks like:
gem 'barber-emblem', git:'https://github.com/simcha/barber-emblem.git'
gem 'barber'
gem 'emblem-rails'
gem 'emblem-source', git:'https://github.com/machty/emblem.js.git'
gem 'ember-source', '1.10.0.beta3'
what does your Gemfile look like?  Is it working then for you?

Merged and published 0.1.2

@danielspaniel I means sometime the pre-compile will be cache, so may need to do clean first, anyway, I try the 1.10.0.beta4, emblem need master version since 0.3.18 not release PR179 yet, but for 1.10, emblem is not ready, so highest version is 1.9.1.
source 'https://rubygems.org'

gem 'coffee-rails'
gem 'ember-rails'
gem 'ember-source', '~> 1.9.1'
gem 'emblem-rails'
gem 'emblem-source', github: 'machty/emblem.js'
gem 'faker'
gem 'haml-rails'
gem 'jbuilder'
gem 'jquery-rails'
gem 'rails_12factor', group: :production
gem 'pg'
gem 'puma'
gem 'rails', '4.0.13'
gem 'sass-rails'
gem 'uglifier'
gem 'pry-rails'


POST /v2/apps now results in 409 if there is a service ports conflict.

If a port has been claimed as a service port by some app, the next app that tries to claim it will by rejected with a 409 Conflict response.
Added ModelValidation.checkAppConflicts() which checks for any conflicts that a new or updated app may have with existing apps. Renamed ModelValidation.checkApp() to ModelValidation.checkAppConstraints() to differentiate it from the new ModelValidation.checkAppConflicts().
Tested this manually, as there appears to be no existing support for integration tests of the endpoints. Running the marathon app in vagrant, creating a new app with a new service port worked via httpie. However, creating a new app with an existing service port returned a 409 status code with the response message "Requested service port 3000 conflicts with a service port in app /demo".
https://github.com/mesosphere/marathon/issues/1002

Thanks for you contribution, much appreciated! Please see my comments.

Great, could you please squash this into a single commit?

Opened a new pull request, https://github.com/mesosphere/marathon/pull/1163, which squashes the commits. Closing this one.


Introduce poseidon2

This PR introduces a crate to employ the recently updated Poseidon2 hash function in plonky2 as the hash function to generate/verify proofs. The crate provides all necessary trait implementations to seamlessly replace existing code employing Poseidon with Poseidon2.
The crate also provides a Poseidon2 gate and the necessary trait implementations to employ Poseidon2 to compute hashes in plonky2 circuit with minimal modifications to existing code.
Although we decided to keep this implementation in its own crate for simplicity of review, it should be also possible to easily integrate this code in the plonky2 crate, if deemed more appropriate and worthy to be included by maintainers of the plonky2 crate

Rather than having a specific crate for poseidon2, now that we have the HashConfig trait that allows more flexibility on the hash function, I think it may make sense to have a dedicated plonky2_hash crate instead, moving poseidon / poseidon2 and whichever other hash functions that would be nice to be supported within. What do you think?

Yes, I agree it might be a good strategy, though I think it would require a quite relevant refactoring (e.g., replacing the Poseidon trait with a more generic Hash trait); but in case you want to introduce it I will be happy to add Poseidon2 to such plonky2_hash crate

Yes, we run the benchmarks you can find in the crate and we observed about 25-30% performance improvement of Poseidon2 over Poseidon, with small improvements also in the circuit. We speculated that these result should be ok considering that the Poseidon implementation seems to rely heavily on optimized arithmetic for multiplications in Goldilocks, while Poseidon2 should use much less field multiplications (thus it should benefit less from the optimized arithmetic for Goldilocks).
Currently we are not planning to work on asm optimizations

Hello!
This PR has been open for a long time, please review and update as following:

If this PR is no l longer relevant, close it.
If this PR is relevant but not read, mark it as Draft and make a comment of what else needs to be done.
Fix any issues and get it merged / reviewed by 10/27/2023.

If there's no update by 10/27/2023 this PR will be closed.

Closing per last message.


add DAG parallelization for streams and zq files

With the recent changes to the optimizer and the addition of dag.Scatter, we should be able to easily parallelize not just lake queries but queries over streams that don't require downstream order.
There is an error in optimizer.parallelizeScan that says this is not yet supported.    We should replace this error with  code might look something like this (though this hasn't been debuged):
// XXX make this work?
func (o *Optimizer) parallelizeStream(ops []dag.Op, replicas int) ([]dag.Op, error) {
	return ops, nil
	// concurrentPath will check that the path consisting of the original source
	// sequence and any lifted sequence is still parallelizable.
	n, outputKey, _, needMerge, err := o.concurrentPath(ops, order.Nil)
	if err != nil {
		return nil, err
	}
	// XXX Fix this to handle multi-key merge. See Issue #2657.
	if len(outputKey.Keys) > 1 {
		return nil, nil
	}
	head := ops[:n+1]
	tail := ops[n+1:]
	scatter := &dag.Scatter{
		Kind:  "Scatter",
		Paths: make([]dag.Seq, replicas),
	}
	for k := 0; k < replicas; k++ {
		scatter.Paths[k] = CopyOps(head)
	}
	var merge dag.Op
	if needMerge {
		// At this point, we always insert a merge as we don't know if the
		// downstream DAG requires the sort order.  A later step will look at
		// the fanin from this parallel structure and see if the merge can be
		// removed while also pushing additional ops from the output segment up into
		// the parallel branches to enhance concurrency.
		merge = &dag.Merge{
			Kind:  "Merge",
			Expr:  &dag.This{Kind: "This", Path: outputKey.Primary()},
			Order: outputKey.Order,
		}
	} else {
		merge = &dag.Combine{Kind: "Combine"}
	}
	return append([]dag.Op{scatter, merge}, tail...), nil
}

Actually, it probably makes more sense to merge the lake and stream case as they are simply differentiated by the head of the query (Reader vs Lister) and all the analysis depends on sortKey for now (and in the future when we data typeflow analysis, the typeset of a stream is simply unknown).


fix: Transactional Retry false x-error-message bug

Related https://github.com/Trendyol/kafka-konsumer/issues/115

Migrated to another branch, because branch name is not applicable


snap Return the currency with the highest balance after the transaction, not before.

Decode the amount of stabletoken sent by the transaction.
Refer to https://github.com/celo-org/gas-snap/pull/16#discussion_r1206762338

We scoped this task down.
And agreed to tell the user what went wrong in this scenario
Please refer to the logic we finally opted for here.


Internshala Class | Code modification

Instead of taking input from the user, add the keyword as a constructor only so that program do not wait for the user input.
https://github.com/Clueless-Community/scrape-up/blob/c7ac4c8a842b9e2fb43f25257cd3902a0a8625f8/src/scrape_up/internshala/internships.py#L41

Go ahead @Abhinavcode13

Great work buddy @Abhinavcode13  !!
Do not forget to

Share your contribution on socials(twitter mainly), tag us and Clueless 🫂
Give this repository a star ✨
Follow Clueless Community on GitHub ✅


Profile based rustflags generate unknown unstable option: build-std

When using some -Z flags in profile based rustflags such as build-std build-std-features panic-in-drop=abort, the compiler generate error unknown unstable option:  build-std ....
for example: a customized src profile with rustflags:
[profile.src]
inherits = "release"
panic="abort"
rustflags = ["-Zbuild-std=core,alloc,std,"-Zbuild-std-features=panic_immediate_abort","-Zpanic-in-drop=abort"]
[profile.std.build-override]
inherits = "release"
[profile.std.package."*"]
inherits = "release"

When build using cargo b --profile src the above error raised.
Is it a bug of cargo-features = ["profile-rustflags"] or something else?

Transferred to rust-lang/cargo
rustflags in a profile are flags that apply to rustc.  -Zbuild-std is a flag for cargo. Cargo's flags cannot be set from a profile.  I recommend using an alias to set which flags to use.

Thx @ehuss , that make sense.
Use -Zpanic-in-drop=abort in [profile.src] rustflags combined with set alias src= "build --profile src -Zbuild-std=std... --target <target>"  compiler hit error: the crate std is compiled with the panic-in-drop strategy unwind which is incompatible with this crate's strategy of abort.
But, if set -Zpanic-in-drop=abort in [build] rustflags everything works fine. It seems that profile based rustflags wasn't aware of cargo -Zbuild-std flags in this scenario.

Indeed that flag does not work in a profile rustflags because profile rustflags are being passed to build scripts. That is one of the concerns registered with the design over on the tracking issue at #10271.

I'm going to close, as I don't think cargo will be parsing profile.rustflags to validate the flags.  As for the build-script issue, that is an open question on the design tracked in #10271.


feat: add support for Endpointslices

Please answer these questions before submitting a pull request

Why submit this pull request?

[ ] Bugfix

[X] New feature provided

[ ] Improve performance

[ ] Backport patches

Related issues

#201

@tokers @membphis PTAL, thanks!

@lianghao208 PR is good to me, but we need some e2e cases to cover it.

/retest

@lianghao208 Any updates?

@tokers
I haven't figured out a proper way to add e2e test case yet . To enable and disable endpointSlice feature, it needs to run on different versions of minikube, which needs to modify the github workflow, any suggestions?

@tokers
I haven't figured out a proper way to add e2e test case yet . To enable and disable endpointSlice feature, it needs to run on different versions of minikube, which needs to modify the github workflow, any suggestions?

Just add another workflow with different minikube version, own test cases about endpointSlices will be run under this minikube, while in the normal environment, cases about endpointSlices should be skipped, you can check out the ginkgo help documents about how to skip or focus on specific test cases.

Codecov Report

Merging #252 (5a55ab8) into master (fe68c79) will increase coverage by 48.34%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           master      #252       +/-   ##
============================================
+ Coverage   51.65%   100.00%   +48.34%
============================================
  Files          34         1       -33
  Lines        2358         1     -2357
============================================
- Hits         1218         1     -1217
+ Misses        982         0      -982
+ Partials      158         0      -158

Impacted Files
Coverage Δ

pkg/apisix/service.go

pkg/api/server.go

pkg/apisix/apisix.go

pkg/version/version.go

pkg/api/router/router.go

pkg/apisix/nonexistentclient.go

pkg/seven/state/service_worker.go

pkg/ingress/apisix/plugin.go

pkg/id/idgen.go

pkg/ingress/apisix/annotation.go

... and 22 more

Continue to review full report at Codecov.

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

Need to due with some Conflicting files. @lianghao208

Ping @lianghao208

Close stale PR, feel free to reopen.


Add FP16 capablity

WIP:
This PR aims to:

[x] Add support to create FP16 tensor
[x] Add FP16 tensor operators
[x] Optimize HTM algorithm against FP16
[x] Clean up how tensor's properties are checked in the backend

Reduce LoC, more readable

To both CPU and OpenCL backend.
And for OpenCL exclusively:

[x] Check the given OpenCL device can process FP16

Tests for the type system

[x] Check types have the correct size
[x] Check resulting type of unitary operations
[x] Check resulting type of binary operations

Besides comparison ops, I;m lazy

[x] Check resulting type of general tensor operations
[x] Somehow disable the fp16 tests when GPU doesn't support FP16
[x] A way to convert SP/TM from float to float16

Just cast the permeance!

Serialize:

[x] Save/load fp16 tensors

Ref #12

Done. Merging!


Dedup provider CSVs

We need to dedup provider CSVs so that popups for the same address show different content.

Can we add a comment on what fields we need to dedup on? @viviandien @akegan ?

https://github.com/dedupeio/csvdedupe


Support for momentary buttons in frontend recipe

(shifted from https://github.com/museumsvictoria/nodel/issues/105)

Closing as this was addressed previously. Momentary buttons can be specified by adding type='momentary' to the button tag (see example).

Apologies, re-opening as there is still an outstanding task to update the XML parser to automatically generate actions for "action-on" and "action-off".

There's an issue here: -off actions doesn't fire.
Example:
<button type="momentary" action-off='VolumeStop' action-on='VolumeDownOn' class='btn-success'>Down</button>

@after_main
def custom():
  lookup_local_action('VolumeDownOn').addCallHandler(lambda arg: console.info('Down On!'))
  lookup_local_action('VolumeStop').addCallHandler(lambda arg: console.info('Stop!'))

Then when using browser, only get this:
07-26 20:42:48.38 Down On!
07-26 20:42:48.42 Down On!

And have confirmed through Chrome only the VolumeDownOn is being called.

Fixed in latest commit


price is displayed overlapping, author is not visible.

It was fixed after restarting the app? Not be reproduced.


[NG] fix alert visibility issue

In prod mode the first alert in alert list is not visible to the user. This happens when using enableProdMode() and is unrelated to AOT.
The check isHidden() only happens once during prod mode while in dev happens multiple times. In production it looks like isHidden is called before the QueryList of the parent alerts component has updated. So when isHidden checks to see if there are any alerts in the QueryList is empty the first time. Every subsequent check seems to work normally.
I found a "fix" but I don't think its a good solution. The code change checks if the list is empty then it can assume its the first alert in the alert list and can fall into the correct if block. Any feedback or ideas would be appreciated.
closes #2430
Signed-off-by: Cory Rylan<EMAIL_ADDRESS>

Actually, I just tracked the component's history and the PR that introduced this component. Eudes actually commented on the very code block here: https://github.com/vmware/clarity/pull/1530#discussion_r143845467
So you might also want to take a look into using Oompa-Loompa to solve the issue.

This logic is strange, and I think we can do better. If we agree to this fix for now, we should open a new ticket to refactor this logic and get away from running change detection this way. I'd be ok with running that fix through at the moment, if we commit to a follow up in short order.


When using code snippet from file, if no title is specified, place the file name

Is your feature request related to a problem?
Almost everytime I use a file as a code snippet, I also write the same name of the file as the title for that code snippet
For example:
```file:/frontend/Page.tsx title="frontend/Page.tsx"
```

Describe the solution you'd like.
It'll be great if when no title was specified, the file name will be used as the title by default.
Describe alternatives you've considered.
Writing it manually
Additional context
Love your work

[...] the file name will be used as the title by default

With this approach, how could users disable the title?


Allow updates to flutter default template, including new folders and files (with documentation)

Use case
I want to customize my default flutter app template. Following this advice, I can see the flutter template files but there is no documentation for adding new files such as the analysis_options.yaml to the main folder. I'd also like to preset various folders including assets, src, and other subfolders to better organize my code. I can envision wanting to add other default files in the future.
The main problem this resolves is the duplication effort required when building new projects according to organizational specifications. I have done a large search and cannot find the required documentation or know-how (other than the source listed above) on how to make the required modifications to flutter's default templates.
Alternatives - One or more plugins exist to make adding new folders and files after a project is started but they do nothing to remediate the issue of unnecessary duplicative effort created by not allowing customized templates.

Proposal
Adjust the flutter tool to allow one to customize the default templates or provide some documentation that allows devs to manually optimize the default files/folder structure that are to be generated by the tool. I think this is something that should come from the flutter tool because it removes the necessity of manually reconstructing the starting point for each new app. While the current default is good for beginners, most shops and devs will have their own architectural requirements and this change will help us to be more efficient.

We do not, in general, want to support customizations to the default flutter templates. These are meant to be as minimal as possible to get user into a working application without exposing too many features at once.
If you want to support different kinds of templates, you can always build a package outside of the flutter_tool that supports this. One such example is stagehand (https://pub.dev/packages/stagehand) which allows you to generate all kinds of project types. You could start your own template package and build off of that as an example


[WIP] GLControl

Note there is a bug in ANGLE that prevents us from using stencil buffer on software-rendered DirectX (Microsoft Basic Render Device). I have a patch to fix that, but it will be shipped with our angle nuget separately.

runs on an elderly windows laptop here, I had to add .0 to the float literals in the shaders and mediump to the shared uDisco and uTime.

PR should be ready for review

I used this to embedd libmpv into Avalonia. Worked like a charm, but I had a weird resize issue. The video from mpv would resize, the control would resize, but the visible part would stay exactly the size it was during OnOpenGlInit.
I got it working by binding the texture before resizeing it in OpenGlControlBase.Render:
if (_oldSize != GetPixelSize()) {
    gl.BindTexture(GL_TEXTURE_2D, _texture);
    ResizeTexture(gl);
}

@gulek
Do you have the same issue with the teapot example from the control catalog?

Ah, it seems that your code changes the current texture binding and doesn't restore it back.
I think we should also reset the texture binding back to zero to avoid unnecessary confusion.

Will this be  compatible with libraries like OpenTK (4.0)?

@dfkeenan that entirely depends on the library. If it's capable of using an external OpenGL context and external glGetProcAddress and isn't afraid of the context being of different types (EGL for Win32, desktop GL for Linux/OSX), it should work.

Isn't it better to use swiftshader for ANGLE instead of relying on directx WARP?

WARP allows interop with other DirectX-based APIs which is kinda important for WPF integration and future support for advanced features like DirectComposition.


ZNC Bindhost change

http://i.imgur.com/G3zkjSh.png Local host: omg.you.are.so.gay.hello2.us (<IP_ADDRESS>)
[14:33:41] <*status> This user's default bind host is [2001:41D0:2:5232::1337]
[14:33:41] <*status> This network's bind host is [<IP_ADDRESS>]
I did everything what I could do but I can't change my bindhost.
How do I fix this issue now?
My Config: http://p.maz.rocks/paste/560542d667277

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26945394-znc-bindhost-change?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

Are you sure you own the IP <IP_ADDRESS>? What is the output of ip addr in your terminal?

http://p.maz.rocks/paste/5605471e194dd
All IP's;
IP Address:
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>

Debug logs; http://p.maz.rocks/paste/5605488dc03f7

According to the debug log, you are connectiong from <IP_ADDRESS>.
$ dig -x <IP_ADDRESS> | grep HEADER
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25754

That IP doesn't have a reverse DNS entry (status: NXDOMAIN, no such domain).
Assuming you want your vhost to be omg.you.are.so.gay.hello2.us, you should try using <IP_ADDRESS> instead (or specifying omg.you.are.so.gay.hello2.us that directly as your bindhost)

Still Maz is connecting from<EMAIL_ADDRESS><IP_ADDRESS>
server -m  <IP_ADDRESS>:1337 CokeB/mijnchat:

Let me clarify, I am trying to use the ip <IP_ADDRESS> to connect to the networks (without rdns, that’s right).
The <IP_ADDRESS> ip is the network interface that my znc service itself is listening on.
I configured the <IP_ADDRESS> IP address as bindhost, but znc still uses <IP_ADDRESS>

psychon, I just want the vhost to be blank.

Network settings; http://p.maz.rocks/paste/56055b8d318da

I want the vhost to be blank

@mazlumb what exactly do you mean by 'blank'?  There is never going to be a 'blank' rDNS entry / vHost.  Whenever you connect to a network it will either be the IP or the rDNS.

@teward I putted the rDNS now to <IP_ADDRESS> to yo.i.want.titsorgtfo.me and it still doesn't connect.

netstat -tpan | grep znc, please (which hopefully only includes the connection of your test instance of znc).
If znc says using bindhost [<IP_ADDRESS>], then it really thinks it is using that IP. Something else must be messing with this.
Can you connect elsewhere with this bindhost e.g. via telnet?

@psychon
root@omg:~# netstat -tpan | grep znc
tcp        0      0 <IP_ADDRESS>:38332    <IP_ADDRESS>:6667      ESTABLISHED 20798/znc
tcp6       0      0 :::1337                 :::*                    LISTEN      20798/znc
tcp6       0      0 <IP_ADDRESS>:1337       <IP_ADDRESS>:44126    ESTABLISHED 20798/znc

tcp 0 0 <IP_ADDRESS>:38332 <IP_ADDRESS>:6667 ESTABLISHED 20798/znc

it looks like bindhost is working to me.

telnet <IP_ADDRESS>

I think @psychon wanted you to connect from that address to somewhere, but I cannot find how to specify bindhost with telnet.

(echo USER a b c d ; echo NICK hopefullyunused ; sleep 30 ) | telnet -b <IP_ADDRESS> irc.spotchat.org 6667
Also, yup. What Mikaela said. ZNC is connecting from <IP_ADDRESS>, so everything is working fine.


with tag not appearing in intellisense

The with tag (see Twig documentation) is one of those tags that does not appear in the intellisense of vscode, assuming this is missing in the implementation.
Update: Seems it's not recognized at all.

I've been working with Twig for years and have not come across this tag! Feel free to create a pull request including the "with" as a snippet or in any other way you think is necessary.

@mblode Hehe, yeah I always find new stuff too, but this one I use quite often due to cumbersome long nestings. And I still use Twig 1.x..
I will check the project code. Should probably be able to create a PR based on the fact I did the very first Twig extension for vscode back in the days (yes, the rather bad one that is still online).

Haha, your old code is probably combined into this extension because it started off as a Frankenstein's monster of all the existing work!

I'm the damn source of the problem :see_no_evil:

Any update on this? I can work on a PR, or at least... I may try. Let me know.

@gremo Go for it. I'm back on emacs at the moment so I'm not as bothered as you might be :)


Heatmap integration!

Sample Data Input:
const commitsData = [     { date: "2020-06-02", count: 1 },     { date: "2020-06-03", count: 2 },     { date: "2020-06-04", count: 3 },     { date: "2020-06-05", count: 4 },     { date: "2020-06-06", count: 5 },     { date: "2020-05-30", count: 2 },     { date: "2020-05-31", count: 3 },     { date: "2020-05-01", count: 2 },     { date: "2020-05-02", count: 4 },     { date: "2020-05-05", count: 2 },     { date: "2020-05-30", count: 4 },   ];
Example declaration:  <Heatmap dateDetails={commitsData} />.
Add this to your view! Then, import the Heatmap component in the components folder. Note that you can style this component with the styles prop, and also, there's also width and height props.

Also, resolve the conflicts before merging the PR.


JCore - Alert Fix for HostPool Resource and AVD solution

Overview/Summary
Fix customer noted issue with Local VM Disk alerts being excessive due to query rule not filtering for VMs in specified host pool. Thus, causing multiple alerts for a single issue or instance of the trigger.
This PR fixes/adds/changes/removes

BICEP and ARM template updates to the kusto query for both VM Local Disk less than 5 and 10 %
Updated YAML for Host Pool for both noted alerts (currently hidden)

Breaking Changes
N/A
As part of this Pull Request I have

[X] Read the Contribution Guide and ensured this PR is compliant with the guide
[X] Checked for duplicate Pull Requests
[X] Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
[X] Ensured my code/branch is up-to-date with the latest changes in the main branch
[X] Ensured PR tests are passing
[X] Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

PR includes other fixes not intended for this release/update.  Closing


Block examples indented improperly

I think we should use docstring method instead?

Also, imports shouldn't be copied in flow?


Starter for MP GraphQL 1.0

MP GraphQL is a standalone spec, but it would certainly be nice to have a starter for it.  It has multiple implementations that I know of including Open Liberty <IP_ADDRESS> and Quarkus 1.5 (possibly also Wildfly) and could work with any servlet-based container if you include the SmallRye GraphQL jar and the MP GraphQL API jar in the WAR file.
Because GraphQL is a standalone spec, it is not associated with any umbrella release of MicroProfile - it's release most closely coincided with MP 3.3, so perhaps it should fit under that.  Alternatively, maybe we could add a drop-down selection option of "Standalone" or "Independent" to create starters for all of the standalone specs like GraphQL, Reactive Streams Operators, LRA, Context Propagation, etc.
I'd be willing to help out with the GraphQL starter, but I might need some education on how it is done.
Thanks!

@rdebusscher and I discussed today. @andymc12 can you create a simple example so that @rdebusscher will do the template based on your example. Contact @rdebusscher if you have any problems.

I took a further look at the MP GraphQL. It looks like this spec depends on Jakarta EE8. We need to think about this. At the moment, you can not select this spec together with others as the others are still based on Java EE8. The only thing we can do is to create a dedicate project without the need to choose other MicroProfile specs. Thoughts?

Jakarta EE 8 as provided, no? So does it matter then?

@rdebusscher right - the dependency should be using provided scope, so it should work with Java EE8 or Jakarta EE 8 environments.
As for example apps, I know of a few of them:
https://github.com/andymc12/ufo-movies - a movie database (similar to IMDB) for UFO movies
https://github.com/OpenLiberty/sample-mp-graphql - a weather app
https://github.com/eclipse/microprofile-graphql/blob/1.0.x-service/tck/src/main/java/org/eclipse/microprofile/graphql/tck/apps/superhero/api/HeroFinder.java - the MP GraphQL TCK uses a "Super Hero Database"
If those apps are too complex, really the only thing a user needs to make a GraphQL app is a POJO annotated with @GraphQLApi that contains at least one non-void method annotated with either @Query or @Mutation - for example:
@GraphQLApi
public class MyGraphQLApi {

    @Query
    public String greeting() {
        return "Hello World!";
    }
}

If you have any questions about any of these samples or if I can help more with the starter creation, please let me know.  Thanks for looking into this!
Andy

I'll have a look at the Super Hero example of the TCK.


No update in POM ?

I guess POM dependencies are not upgraded along with sbt configuration. Please update POM with latest dependencies.

The pom seems invalid in any case, there's missing dependencies in it to start with.
It came in from an external contribution and was never really maintained, I think we may be better of by dropping it actually.


How do I fully remove crouton? (want to make fresh install)

Hey everybody i was just wondering how i could fully remove crouton because i just want a fresh install, anybody know how there are no tutorials i could find on how to

@SnippitCoder,
The README mentions it under the paragraph heading -

Help! I've created a monster that must be slain!

But there probably aren't many tutorials to be found since it's just a one line command -

sudo delete-chroot [chrootname]

delete-chroot is just a link to edit-chroot which has many other options unrelated to deleting a chroot but I'll list them below for completeness -
delete-chroot [options] name [...]

Edits a chroot.

Options:
    -a          Operates on all chroots in /mnt/stateful_partition/crouton/chroots.
                If no other operation is specified, prints out the names of the chroots.
    -c CHROOTS  Directory the chroots are in. Default: /mnt/stateful_partition/crouton/chroots
    -b          Backs up the chroot to a tarball. Compression format is chosen
                based on the tarball extension. Backups always take place before
                other actions on a given chroot.
    -d          Deletes the chroot. Assumed if run as delete-chroot.
    -e          If the chroot is not encrypted, encrypt it.
                If it is encrypted, change the encryption passphrase.
    -f TARBALL  When used with -b, overrides the default tarball to back up to.
                If unspecified, assumes NAME-yyyymmdd-hhmm.tar[.gz], where .gz
                is included for unencrypted chroots, and not for encrypted ones.
                When used with -r, specifies the tarball to restore from.
                If TARBALL is a directory, automatic naming is still used.
                If multiple chroots are specified, TARBALL must be a directory.
    -k KEYFILE  File or directory to store the (encrypted) encryption keys in.
                If unspecified, the keys will be stored in the chroot if doing a
                first encryption, or left in place on existing chroots.
                If specified, keyfile will be moved. Specify a dash - as the
                KEYFILE to move the key back into the chroot.
                If multiple chroots are specified, KEYFILE must either be -
                or a directory.
    -l          Prints out croutonversion details on the chroot, if available.
                Specify twice to prompt and unlock encrypted chroots as necessary.
    -m DEST     Moves a chroot. Specify a new name to keep it in the same
                directory, or an absolute path to move it entirely.
                DEST can be a directory, in which case it must end in a slash.
                If multiple chroots are specified, DEST must be a directory.
                If you are moving a chroot to a SD card/USB drive, make sure the
                storage is formatted to ext2/3/4.
    -C DEST     Like -m, but copies instead of moves.
    -r          Restores a chroot from a tarball. The tarball path can be
                specified with -f or detected from name. If both are specified,
                restores to that name instead of the one in the tarball.
                Will not overwrite a chroot when restoring unless -r is
                specified twice.
    -s SPLIT    Force a backup archive to be split into SPLIT-sized chunks.
                SPLIT is specified in megabytes (1048576 bytes), and cannot be
                smaller than 10.
                FAT32 filesystems are split by default to fit within 4GB.
    -y          Do all actions without confirmation.

You can delete more than one chroot by entering multiple chrootnames on the command line or you can delete all of them at once with the -a option as follows -

sudo delete-chroot -a

There are other ways to delete your chroot(s) using Linux commands but the above is probably the easiest and best way to do it.
Hope this helps,
-DennisLfromGA

sudo rm /usr/local/bin/crouton or you could also do a powerwash go to Settings -> about Chrome OS -> Powerwash for added security.
With the first command there could be some leftover files crouton uses in /usr/local/bin
Just list the files in there with ls -al /usr/local/bin post the output here and some of us can tell you if they are safe to delete.
The second option I mentioned using the chrome os interface erases everything you added and will leave developer mode, so your chromebook is stock again.

Showing comments from related issue now closed -

Ok, so I made an issue just like this yesterday and i got a response that seemed super helpful but im sure what it ment. I want to delete crouton, not a chroot. I'm brand new to this so I have no idea if crouton itself is a chroot or not. I have turned off developer mode and back on to see if I could erase it that way but it still works. I'm just wondering how to delete it to the point where the 'shell' command wont work at all. I just want crouton to basically delete itself.

Deleting crouton chroots essentially deletes crouton, there are a few files in /usr/local/bin (by default) that you could remove too if you like, for example:
crash_reporter_wrapper cros_funcs crouton delete-chroot edit-chroot enter-chroot mount-chroot startcli startxfce4 startxiwi, etc.
Hope this helps,
-DennisLfromGA

Thank you, I think I got the right command and it seemed to work! I'll close this issue now :)

FYI: A powerwash will erase all users and user data (on the stateful partition) but will not leave Developer mode, in fact, even a full recovery will not leave Developer mode.
Hope this helps,
-DennisLfromGA

@DennisLfromGA for me after a powerwash or a full recovery I always had to reenable developer mode, maybe it changed now.

@divx118,
Maybe it has changed over the years, it's very possible.
I seldom do either since I have so much custom stuff on my devices but, from what I've seen and heard of late, is that you have to leave Developer mode intentionally by pressing space followed by enter at the 'scary boot screen'.
-DennisLfromGA


dgpu.idr.ai:19092 for documentation doesn't work

The website doesn't work for documentation.
dgpu.idr.ai:19092
Could you please add the 3D model for the following image so that we can run the examples/test.py?

closing the issue due to no response.


Add texture coordinate type to RenderStates

[x] Has this change been discussed on the forum or in an issue before? (see https://github.com/SFML/SFML/issues/1773)
[x] Does the code follow the SFML Code Style Guide?
[x] Have you provided some example/test code for your changes?
[x] If you have additional steps which need to be performed list them as tasks!

Description
This pull request adds support for changing the texture coordinate type in RenderStates, so that VertexArray and VertexBuffer can be used with normalized texture coordinates. Other drawables still enforce texture coordinates in pixels. The rationale for this modification is provided in #1773.
This change is fully backward compatible. However, to keep the API clean and reduce header inclusion dependency, I decided to move the CoordinateType enum out of sf::Texture and into its own file. In the process, I deprecated using the sf::Texture::CoordinateType in sf::Texture::bind() and added an overload that uses sf::CoordinateType. I thought this would be neater in the long run, but if you think it's fine to just use sf::Texture::CoordinateType in RenderStates (which forces including the Texture.hpp header), and avoid the deprecation, I can revert that.
This PR is related to the issue #1773.
Tasks

[x] Tested on Linux
[ ] Tested on Windows
[ ] Tested on macOS
[ ] Tested on iOS
[ ] Tested on Android

How to test this PR?
#include <SFML/Graphics.hpp>

int main()
{
    sf::RenderWindow window(sf::VideoMode(sf::Vector2u{1280, 720}), "Minimal, complete and verifiable example");
    window.setFramerateLimit(60);

    sf::Texture texture;
    bool        success = texture.loadFromFile("../examples/assets/logo.png");

    // 'v1/s1' uses pixel coordinates
    sf::VertexArray v1(sf::PrimitiveType::Triangles, 6);
    v1[0].position = {0, 0};
    v1[1].position = {256, 0};
    v1[2].position = {256, 256};
    v1[3].position = {256, 256};
    v1[4].position = {0, 256};
    v1[5].position = {0, 0};

    v1[0].texCoords = {0, 0};
    v1[1].texCoords = {512, 0};
    v1[2].texCoords = {512, 512};
    v1[3].texCoords = {512, 512};
    v1[4].texCoords = {0, 512};
    v1[5].texCoords = {0, 0};

    sf::RenderStates s1;
    s1.texture        = &texture;
    s1.coordinateType = sf::CoordinateType::Pixels; // default

    // 'v2/s2' uses normalised coordinates
    sf::VertexArray v2(sf::PrimitiveType::Triangles, 6);
    v2[0].position = {256, 0};
    v2[1].position = {512, 0};
    v2[2].position = {512, 256};
    v2[3].position = {512, 256};
    v2[4].position = {256, 256};
    v2[5].position = {256, 0};

    v2[0].texCoords = {0, 0};
    v2[1].texCoords = {1, 0};
    v2[2].texCoords = {1, 1};
    v2[3].texCoords = {1, 1};
    v2[4].texCoords = {0, 1};
    v2[5].texCoords = {0, 0};

    sf::RenderStates s2;
    s2.texture        = &texture;
    s2.coordinateType = sf::CoordinateType::Normalized;

    while (window.isOpen())
    {
        sf::Event event;
        while (window.pollEvent(event))
        {
            if (event.type == sf::Event::Closed)
                window.close();
        }

        window.clear();

        window.draw(v1, s1);
        window.draw(v2, s2);

        window.display();
    }
}

Thanks a lot for this addition! 🙂
We've already seen a lot of points from @binary1248 in the linked issue, but I'd like to hear some more thoughts from others. If you can bear with us a bit longer, we hopefully get this reviewed soon-ish. 😉

Thank you for the comments @Bromeon, I have replied to all of them.

The last round of comments from @Bromeon was asking for opinion from other maintainers, but there has been no reply since. Should we still wait for these comments, or should I just go ahead an implement the changes suggested by @Bromeon?

I have re-targeted this PR against master, hence:

Using C++17 to improve the code.
Remove functions without care for breaking backward compatibility.

This addresses all the remaining comments from @Bromeon.

SFMLBuildMaster: Build this please.

If there are no further comments on this PR and the CI passes, are there any remaining blockers for it be merged? I have been maintaining this branch for close to two years now :)

SFMLBuildMaster: Build this please.

Thank you for creating this PR and keep it alive over time! 🙂


Convert sensor's newData signal to send QVariant data

Download:
Environment: QT=5.12, ARCH=32, PYTHON_PATH=C:\Python35
Environment: QT=5.12, ARCH=64, PYTHON_PATH=C:\Python35-x64


SSE is not enabled at the Cloud Backend using Multi-Cloud API

Issue/Feature Description:
According to the following code snippet from https://github.com/sodafoundation/multi-cloud/blob/master/api/pkg/s3/router.go#L49 SSE output is enabled in multi-cloud as per the response given by the API. But at the Cloud Backend, SSE is not set.
// router for SSE 	ws.Route(ws.PUT("/{bucketName}/?DefaultEncryption").To(handler.RouteBucketPut)).Doc("Set default encryption on bucket")
Why this issue to fixed / feature is needed(give scenarios or use cases):
How to reproduce, in case of a bug:

Issue the Following API.
/{bucketName}/?DefaultEncryption

Upload Object

Check Encryption in Cloud Backend

Other Notes /  Environment Information: (Please give the env information, log link or any useful information for this issue)

SSE as a feature need to be revisited @skdwriting this will have to be release note


[TC-IDM-3.1]Chip-tool support needed to  send a ReadRequest message from TH to DUT to read any attribute on two clusters.

#### Problem
As per Test-Plan, test-step 13 says "DUT sends a ReadRequest message to the TH to read any attribute on two clusters",
Chip-tool support needed to  send a ReadRequest message from TH to DUT to read any attribute on two clusters.
Test-Plan screenshot:-

Spec Reference:-
https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/data_model/Interaction-Model.adoc#ref_WriteRequestAction

@Rajashreekalmane - I am a bit unclear here, trying to determine if the issue is any being not strictly defined or if chip-tool does not have the ability to read or write two attributes at the same time or something else.
Please describe the issue a bit more. Generally I would expect replacing any with a concrete example maybe of some attribute that is always defined and can be changed (like labels maybe?).

@andy31415 chip-tool does not have the ability read or write any attributes from different clusters at the same time,  As my understanding here any attributes means we need to send command which should contain different attributes from different clusters.

chip-tool does not have the ability read or write any attributes from different clusters at the same time

Sure it does:
chip-tool any read-by-id "6,8" "0,17" ${NOD_ID} "1,1"

will read the "OnOff" and "OnLevel" attributes from the "On/Off" and "Level Control" clusters respectively on endpoint 1.  Resulting output is:
[1653195653340] [45076:53049833] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0008 Attribute 0x0000_0011 DataVersion:<PHONE_NUMBER>
[1653195653341] [45076:53049833] CHIP: [TOO]   on level: null
[1653195653341] [45076:53049833] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0006 Attribute 0x0000_0000 DataVersion:<PHONE_NUMBER>
[1653195653341] [45076:53049833] CHIP: [TOO]   OnOff: FALSE

Adjust the IDs as needed.

Or you can do:
chip-tool any read-by-id "6,8" "0,17" ${NODE_ID} "2,1"

to have different endpoints too:
[1653195823045] [45084:53051019] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0008 Attribute 0x0000_0011 DataVersion:<PHONE_NUMBER>
[1653195823045] [45084:53051019] CHIP: [TOO]   on level: null
[1653195823045] [45084:53051019] CHIP: [TOO] Endpoint: 2 Cluster: 0x0000_0006 Attribute 0x0000_0000 DataVersion:<PHONE_NUMBER>
[1653195823045] [45084:53051019] CHIP: [TOO]   OnOff: FALSE


Don't catch async exceptions.

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

solga/src/Solga.hs, line 103 [r1] (raw file):

-- | Serve a `Router` with Solga, returning `SolgaError`s as HTTP responses.
serve :: Router r => r -> Wai.Application
serve router req cont = serveThrow router req cont

This is dangerous, for the reasons described here: https://www.stackage.org/haddock/lts-6.6/base-<IP_ADDRESS>/Control-Exception.html#v:catches
@snoyberg , shouldn't we provide catches in safe-exceptions?

Comments from Reviewable

solga/src/Solga.hs, line 103 [r1] (raw file):
Previously, bitonic (Francesco Mazzoli) wrote…
> This is dangerous, for the reasons described here: https://www.stackage.org/haddock/lts-6.6/base-<IP_ADDRESS>/Control-Exception.html#v:catches
>
> @snoyberg , shouldn't we provide `catches` in `safe-exceptions`?

Done.

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

solga/src/Solga.hs, line 109 [r2] (raw file):

      ( status, body ) = case cast ex of
        Just SolgaError { errorStatus, errorMessage } -> ( errorStatus, Builder.byteString $ encodeUtf8 errorMessage )
        Nothing -> ( HTTP.internalServerError500, mempty )

Wouldn't it be best practice to have a minimal body? E.g. "Internal Server error"?

Comments from Reviewable

solga/src/Solga.hs, line 109 [r2] (raw file):
Previously, bitonic (Francesco Mazzoli) wrote…
> Wouldn't it be best practice to have a minimal body? E.g. "Internal Server error"?

Done.

Comments from Reviewable

Reviewed 1 of 1 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

@snoyberg , shouldn't we provide catches in safe-exceptions?

I see no reason why not, wanna open an issue or PR?


Rework imported vars in the reproducer

Until now, we were filtering out anything cifmw_openshift* related.
This leads to issues, for instance when we want to pass
cifmw_openshift_setup_ca_registry_to_add down in the environment.
In order to ensure we're not filtering too many parameter, this change
modifies a bit how things are handled:

we allow all of cifmw_openshift* parameter
but we filter out one that may be problematic: kubeconfig (due to
potential user HOME mismatch)

We also take the opportunity to reject the pull-secret and ci-token
keys, to ensure they don't leak in the env (they are mostly useless on
controller-0).
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

Manual tests
With CRC, we end with this:
[zuul@controller-0 ~]$ grep openshift openshift-environment.yml
cifmw_openshift_login_password_file: >-
cifmw_openshift_login_kubeconfig: >-

[zuul@controller-0 ~]$ grep openshift reproducer-variables.yml
cifmw_openshift_api: https://api.crc.testing:6443
cifmw_openshift_password: '12345678'
cifmw_openshift_user: kubeadmin

It really looks like what we need.

/hold
have to ignore cifmw_openshift_token

/hold cancel
updated with new rejection.


Bug fix/cross button

What kind of change does this PR introduce?
Bug Fix
Did you add tests for your changes?
No.
If relevant, did you update the documentation?
Not Required
Summary
This PR fixes the crossButton bug in Input page. The cross button now clears the input text.
Fixes Issue #70
Does this PR introduce a breaking change?
Not Applicable
Other information

Issue #70
https://user-images.githubusercontent.com/68142366/112758577-c986e400-900c-11eb-94aa-429d6ea70bbb.mov
Fixed #104
https://user-images.githubusercontent.com/68142366/112758627-f0451a80-900c-11eb-8d0e-1cf14cbab295.mov
@ARJUN-SABU @ankushdutt  @pranshuchittora  @Uyadav207 Please look into it. This PR fixes issue #70 .


Readthedocs versions

Shouldn't read the docs by default show documentation for the last released version as opposed to the master branch? Or at least have the latest stable release docs available (right now would be 0.3.0)?

Here is the relevant documentation https://docs.readthedocs.io/en/stable/versions.html
I looked into what scanpy does and they have a stable branch that seems to be a branch off master after a release.

Solved on readthedocs


enhance Support match query without inverted index

Proposed changes
Issue Number: close #xxx
Problem summary
before this pr, match query without inverted index will return error like:
ERROR 1105 (HY000): errCode = 2, detailMessage = (17x.xx.xx.xx)[NOT_IMPLEMENTED_ERROR]Match query must with inverted index, column `msg` is not inverted index column

this pr will support match query without inverted index.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run p1

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall


Can I use 3.0.5tessdata to replace 3.0.2 tessdata?

I find the 3.0.5 model is better than 3.0.2.Now my project is building by vs2010 and tesseract3.0.2.I replace the 3.0.2 tessdata by 3.0.5 tessdata ,it shows "allow_blob_division",than I use "combine_tessdata -e chi_sim.traineddata chi_sim.config" and notes the line of "allow_blob_division",finally "combine_tessdata -o chi_sim.traineddata chi_sim.config",but the tessdata is invalid.

Please use tesseract user forum for asking support

https://github.com/tesseract-ocr/tesseract/issues/410#issuecomment-244120707


Bug: Environment's sample method ignores interventions?

Hi, it looks like the sample method of the Environment base class defined in https://github.com/chritoth/active-bayesian-causal-inference/blob/master/src/environments/environment.py#L128 does not actually use the interventions to affect the ancestral sampling. Is this intentional, or a bug? (If intentional, where does the ancestral sampling with interventions actually happen?)

Hi, thanks for reporting this! You are right, the interventions parameter was unused in the ancestral sampling, with was an error introduced during the refactoring process for the initial code version published here. It's now fixed by commit 4aa8e9b.


Add separate mail_user

Added separate mail_used into inputs.conf as there are cases when stanza cannot used as a login id.

Fixed also field alias MessageID


Backward compatible change leading to non-queryable REALTIME table ?

Following Slack discussion: https://apache-pinot.slack.com/archives/C011C9JHN7R/p1624260346227200
After adding a new INT column on a REALTIME table via updating its schema file and calling the API POST /schemas and POST /tables (*) endpoints - the schema is correctly updated but querying the table results in the following error :
*: Likely an unnecessary call from a generic workflow
[
  {
    "errorCode": 500,
    "message": "MergeResponseError:\nData schema mismatch between merged block:
[communityId(STRING),documentId(STRING),eventTimeString(STRING),eventType(STRING),**hoverDuration(INT)**,ibcustomer(STRING),origin(STRING),projectId(STRING),selectionId(STRING),timeString(STRING),userId(STRING)]
and block to merge:
[communityId(STRING),documentId(STRING),eventTimeString(STRING),eventType(STRING),ibcustomer(STRING),origin(STRING),projectId(STRING),selectionId(STRING),timeString(STRING),userId(STRING)],
drop block to merge"
  }
]

Additional context:

Column was first added as Dimension, then changed to Metric
The newly added field come from a JSON sub document, and is parsed via ingestionConfig.transformConfig with defaut value (-1).

@xiangfu0 Suggested to restart the REALTIME servers - but any non "operational" and downtime-less solutions would be ideal if possible :)

This behavior is due to the fact that pinot.server.instance.reload.consumingSegment was off (false)
The following PR https://github.com/apache/incubator-pinot/pull/7078/files updated this default behavior :+1:
Closing !


chore: add tnevrlka to build OWNERS

Description
Add tnevrlka to the build-team OWNERS alias so tnevrlka can review PRs relevant to the build team
Issue ticket number and link
N/A
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
N/A
Checklist:
N/A

/lgtm
/approve


feat(rules): add filters param to rules condition

Q
A

Bug fix?
no

New feature?
yes

BC breaks?
no

Related Issue
Fix #734

Need Doc update
yes

Is this live already?

@Ant-hem I believe yes, in closed beta.


feat: Add Neo4j vector store

Porting Neo4jVector from LangChain Python.

I was actually just asking about this. What is the state of this PR? Can I help in anyway?

I was actually just asking about this. What is the state of this PR? Can I help in anyway?

Thx, I'm already having a helping hand in getting this PR ready.

You'll also need to add an entrypoint as described here - I did it for you last time:
https://github.com/langchain-ai/langchainjs/blob/main/CONTRIBUTING.md#adding-an-entrypoint

You'll also need to add an entrypoint as described here - I did it for you last time:
https://github.com/langchain-ai/langchainjs/blob/main/CONTRIBUTING.md#adding-an-entrypoint

Sorry - missed that one. Added.

Thank you! Will fix CI and merge in the next release 👍


Add a non-token approach for OpenAI

Hello, as per interest shown in https://github.com/1rgs/jsonformer/issues/2 I'd like to propose a variation for OpenAI models.
Summary

Added possibility of filling the JSONs through calls to a non-chat OpenAI model (seems to work best with curie)
Two new classes: OpenAIModel and JsonformerNoTokens, which is basically the stripped down original with no tokenizer
Instead of using logits in generate_boolean and generate_array, we're getting the next most likely token from logprobs.
As a substitute for stopping criteria, stop word ", is used to limit the model's response to a single value

Why no chat?
I found the chat model to be more querulous (As an AI model I cannot blablabla...), prompt-dependant and slow.
Solution proposed here seems to be working best with text-curie-001 as it's super fast and cheap.
Perhaps somebody can figure out an effective way to utilize the chat model, but I cannot see any other way than prompting to generate the whole JSON at once, which is completely in opposition to the concept of this project.
Why no tokens?
I spent some time trying to continue operating on tokens while using the API, but I encountered two issues:

tokenization available on tiktoken does not seem to provide word boundaries, therefore, for example, encoding "colors" will give us two separate tokens, which after decoding give "col ors". Can't work like that.
chat models do not accept tokens as input

And of course, because the models run remotely we have no access to the generation process. From my perspective, this is the reason that renders all token operations pointless here. I still left the tokenizer class just in case.
How to run it?
Make sure you have OPENAI_API_KEY env var.
poetry install
poetry run python tests/test_openai.py

You'll see the JSON being filled. You can change the used model and its temperature in that file during JsonformerNoTokens initialisation.

I am just pondering that, as far as I know, ChatModel is an inborn good JSON generator. GPT-3.5-turbo is derived from code-davinci-003 (Codex), which is fine-tuned on a large number of codes and really capable of generating JSON.

I do have a deep interset in generating JSON format from OpenAI models. Please feel free to contact me!

@zhaochenyang20 I agree it is fairly good at it, but the authors of this project don't seem to be convinced it's enough to have a good prompt for the chat. I assume it's based on their experiences, personally I don't know.

Very Excited to try this out!!!

Looking forward to using this to parse plain text outputs from CoCa into JSON for image JSON captioning.

Awesome to hear that @moro-no-kimi 🥳

@moro-no-kimi
Are you using jsonformer with the open ai model? If yes, is it possible to share the code?

This is kind of obsolete now with function calls feature from OpenAI

This is great work, but would complicate the repo, which is nice and simple
On this list there are quite a few others that support api only models https://github.com/wassname/awesome-interpretability/tree/main?tab=readme-ov-file#structured-output


CircleCI

CircleCI seems to be having some issues running our setup.py script, since we check to ensure dependencies are installed before running the actual setup function. I added a circle.yml file to try to make sure that numpy/scipy/matplotlib are installed (via pip) before the setup script is run, but that seems to have lead to other problems (I think maybe because doing pip install matplotlib is problematic).
@rth, @basaks, since you guys are better at this kind of stuff then I am, do you have any ideas?

Where can I find your circle.yaml?

Thanks @bsmurphy . I have a Circle CI setup that should work, will make a PR...

Fixed in https://github.com/bsmurphy/PyKrige/pull/61 i.e. Circle CI setup is no longer necessary for the documentation and can be removed.


plugins/wilder-nvim: init + test

Add a support for wilder.nvim.

It would be nice to expose the renderer option via nixvim...

It would be nice to expose the renderer option via nixvim...

I could try to do that, but not really sure how useful it will be. As far as I can tell, the only option would be to just add wilder-nvim.renderer.wildmenuRenderer which would accept function as an argument. Not sure if it is worth it as opposed to just adding some extraConfigLua. But if there is a better way, I would be happy to expose it.


Iterative rendering of data elements in computed property

Version
2.6.0
Reproduction link
https://kamsham.com
Steps to reproduce
If i create an http request in a computed property its it sends the request again and again that slowes down the performance of the framework itself...
And also the computed property does not compute before the system gets fully rendered, this delay should not bs there. And if i use a foreach loop in a computed property to return some specific objections it gives me the same list of objects iteratively and the lost goes on with infinite number or objects in it...
What is expected?
I need you to fixe that bug or if m not using it correctly then kindly inform me ghe right way to use it
What is actually happening?
If i create an http request in a computed property its it sends the request again and again that slowes down the performance of the framework itself...
And also the computed property does not compute before the system gets fully rendered, this delay should not bs there. And if i use a foreach loop in a computed property to return some specific objections it gives me the same list of objects iteratively and the lost goes on with infinite number or objects in it...

Please read the issue requirements and provide a valid reproduction.


Import Error

hi~, firstly, I think it is a good job.
However, when I run your code , I got the following error:
ImportError: /home/ubuntub/Guo/TinyBenchmark-master/tiny_benchmark/maskrcnn_benchmark/_C.cpython-35m-x86_64-linux-gnu.so: undefined symbol: _ZN6caffe28TypeMeta21_typeMetaDataInstanceIN3c108BFloat16EEEPKNS_6detail12TypeMetaDataEv
But I have done  python setup.py build develop following your instructions.
I am sincerely looking forword to your reply.
Thanks!

For using conda install instead of pip, the problem gone.
And we close this issue.


Possible to programmatically pre-populate S3 access/secret key?

Is it possible to programmatically pre-populate S3 access/secret key and region to avoid our users having to manually enter new credentials when we cycle keys?

What do you mean with "pre-populate"? I suggest you are requesting for an automatic mechanism of populating configuration details of a certain account? If yes, you can set your account storage location to "KeePass Configuration" (see details here: https://github.com/Kyrodan/KeeAnywhere/wiki/Advanced-Topics#which-account-storage-location-should-i-choose) and share/exchange this file.


Raise exception when generic parameters are assigned

In SMIRNOFF99Frosst, generic parameters are set to fairly ridiculous values. For example, the generic bond ([*:1]~[*:2] for any two atoms connected by any bond) the length is 4.0 angstroms and the force constant is 2,000 kcal/mol/angstrom**2.  For our molecule sets we have eliminated molecules where these parameters are assigned, indeed that is how we discovered what parameters were missing when developing smirnoff99Frosst to begin with. However, if these parameters are assigned to a molecule the simulation will run without any kind of warning and unless someone looks closely at the data they may never know there is a problem.
@davidlmobley and I agree that as more people begin to use our force field running quietly with these parameters is not ideal. Offline we discussed two options for how to handle this scenario:

We could make the parameters slightly more reasonable and add a warning that generic parameters were assigned to the parameters.

Default behavior is to have an exception raised when one of these parameters is assigned. There should be an option that allows users to run the simulation anyway where a warning would still be printed.

David and I think option 2 is the better solution, but this raises a couple of questions:

Currently generic parameters are assigned the number 1 in their category (i.e. b1 for Bonds and n1 for non-bonds). This numbering scheme comes from how we convert the "frocmodish" files into the smirnoff ffxml format where each parameter is numbered in order. Should we maintain this convention where we look at the parameter id? OR assume the first parameter in any section is generic?

Should we keep the generic parameters as is or change the numbers to be slightly more reasonable values since default behavior will be to raise an error. If we change the values what should we change them to?

@cbayly13 could we get your input on this when you have time?

It's worth noting that the parameter ID is purely optional, so when we talk about retaining the convention where we look at the parameter ID, we're really just talking about whether WE are using it internally as a way to assess whether a generic is assigned. All our documentation so far says this is optional and has no functional importance, and I'm leery about changing that.
To explain the history here, as I remember it -- Chris really wanted generics present which were "obviously wrong" because this was something he'd used previously in the past effectively. But, as we broaden this out so that more people use it, I get increasingly uncomfortable with having these present as most people are just going to plunge ahead without noticing they are being used.
As I think about it more, @bannanc , maybe this all is an argument to extend the spec slightly to allow explicit designation of generics, e.g. adding a Generic_bond tag in addition to Bond, Generic_angle, etc. These would be explicitly designated as generics by their TAGS (not their parameter IDs, which we say have no functional importance). Then, when we go with option 2, if the user does NOT insist on proceeding with generics, they would simply get an exception about a missing parameter if a parameter is missing. But if they insist on proceeding with generics, then these would be employed.
Does that sound sensible?

As I think about it more, @bannanc , maybe this all is an argument to extend the spec slightly to allow explicit designation of generics, e.g. adding a Generic_bond tag in addition to Bond, Generic_angle, etc. These would be explicitly designated as generics by their TAGS (not their parameter IDs, which we say have no functional importance). Then, when we go with option 2, if the user does NOT insist on proceeding with generics, they would simply get an exception about a missing parameter if a parameter is missing. But if they insist on proceeding with generics, then these would be employed.

This seems like a more reasonable choice to me, how much of a change to the API and forcefield code would this require?

I think it should be a minor change.

I agree with the concerns raised; we need to change the behavior. I agree that Caitlin's option 2 to raise an exception is the right way to go. I am wondering about changing the default parameters to be "slightly more reasonable": As David points out, my original reasoning is that these parameters have only one purpose and that is to tell that something really bad and unnatural is happening, never anything reasonable.
I think we should have exceptions raised, period, if the "obviously wrong" world is encountered.  Don't forget that one of the use cases for the "obviously wrong" exception is a structure with broken valence, ie an illegal valence structure, which one definitely gets in large dbs like emolecules. There are no reasonable parameters for those and we want exceptions thrown in those cases. For new but not wrong structures perhaps we should put in a little bit more due diligence on real generic parameters that are some kind of reasonable . I thought I put a complete set into smirnoff99Frosst, but if Caitlin's been hitting the "obviously wrong" parameters in such cases I guess I missed some (no surprise).
I like David's idea of tags; this could help us in a general way to track provenance; the lowest form of provenance is probably "generic". It could still be fit to QM though.

@cbayly13 - by "generic" I was thinking mainly parameters of the type "contains no element and will apply to anything I've never seen before". You certainly did do a good job (as far as I can tell) of covering elemental generics in a sensible way; what I'm mostly worried about now is people managing to come up with corner cases where they throw in an element we don't yet support and get a "bad" parameter assigned to it.
Caitlin could put in some more sensible non-elemental generics in these cases (e.g., not a bond length of 4 angstroms for the generic bond; maybe something like 1.5 angstroms) so that if people insist on running, it will at least run...
But it sounds like we're agreed.
@bannanc - let's talk at some point about how to do this.

@jchodera -- I wanted to get this issue on your radar for the SMIRNOFF spec updates in #86 -- we want a way to flag generic parameters that are in a forcefield to ensure coverage but are not really intended for use:

As I think about it more, @bannanc , maybe this all is an argument to extend the spec slightly to allow explicit designation of generics, e.g. adding a Generic_bond tag in addition to Bond, a Generic_angle in addition to Angle, etc. These would be explicitly designated as generics by their TAGS (not their parameter IDs, which we say have no functional importance). Then, when we go with option 2, if the user does NOT insist on proceeding with generics, they would simply get an exception about a missing parameter if a parameter is missing. But if they insist on proceeding with generics, then these would be employed.

Basically the thought is that this would allow us to build in bonds like [*:1]~[*:2] (which smirnoff99Frosst currently has, but which we don't like because it's risky) which will raise an exception UNLESS the user explicitly specifies an option like use_generics = True or something similar, in which case only a warning would be issued.
Basically the incentive is to take advantage of the fact we can have very broad generics to ensure everything can be simulated, but also clearly designate parameters which are not really intended for use.

Basically the incentive is to take advantage of the fact we can have very broad generics to ensure everything can be simulated, but also clearly designate parameters which are not really intended for use.

I'm a bit confused about this. Do we want to allow the user to simulate these or not?
We can't desire both things simultaneously, can we?

@jchodera

I'm a bit confused about this. Do we want to allow the user to simulate these or not?
We can't desire both things simultaneously, can we?

Yes, actually -- take the behavior of OpenEye's Omega as an example. There's an option for StrictAtomTypes; if True, it will refuse to generate a conformer if an exactly matching atom type is not found; if False, it will take the nearest atom type and proceed. I use both depending on which application I'm working on.
I would want people NORMALLY to not be able to use generic parameters here, but we could come up with generics which would be "good enough" for really rough simulations; e.g., to first order, treating a boron in an aromatic ring as "roughly like a carbon" will be preferable to some people over "you just can't model it until you fit the parameters", e.g. if you're doing docking or something similar where you aren't after a great deal of accuracy.
So, I think we CAN desire both things.

You can achieve this right now by simply having two versions of the same ffxml file (one including generics, one not), or, if we go with the latest proposal in https://github.com/openforcefield/openforcefield/issues/96, simply prepending an ffxml file with generics.
Does this really require extensions of the ffxml spec and the ForceField API if we can already do it with barely any effort?

We could of course add this option, but I just want to make sure that it's understood that you can essentially do this now (though we're still finishing #96).

Ah, I totally hadn't thought of that; while less user-friendly that may be a good idea since it doesn't require extending anything. @bannanc is this OK with you?

I hadn't thought about that as an option either, but I like it. We don't really want using generics to be too "user" friendly so this seems like a good solution to me.

Great! If you just create a generics.ffxml, it's just a difference between
forcefield = ForceField('smirnoff.ffxml', 'water.ffxml')

and
forcefield = ForceField('generics.ffxml', 'smirnoff.ffxml', 'water.ffxml')

presuming we have reached consensus in https://github.com/openforcefield/openforcefield/issues/96

It would take me about 5 minutes to make a generic.ffxml file, if someone can let me know where we should save it.

Right now, ForceField automatically searches the path where the data/ directory is installed, so if you put it here, you could specify
forcefield = ForceField('forcefield/generics.ffxml', 'forcefield/smirnoff.ffxml', 'forcefield/water.ffxml')

We can always change the search path here, or add more paths to search.

I realized I should document somewhere why I'm choosing the generic parameters I have chosen, I'm going to write out my thought process here and maybe I can get @cbayly13 to comment if he agrees.
My thought is we want the generics to be at least somewhat reasonable, but we also know what types of elements our force field is less likely to have information.  Anything we pick is likely to be better for somethings than it is for others. Since boron is the element that keeps coming up as something we want, but don't have parameters for, I was thinking I would pick parameters that seem reasonable for those.
[*:1]     1.9    0.1

[*:1]~[*:2]    310.0    1.5

[*:1]~[*:2]~[*:3]    50.    120.

[*:1]~[*:2]~[*:3]~[*:4]    1     0.0    0.0    2

@bannanc I believe this still needs to be addressed, correct? I believe this will be important to include in the 1.0 release so I was thinking of having a go at this if you're not already working on it.
Currently, in the topology branch, there are no generics, but ForceField.create_openmm_system(topology) fails silently with some unexpected behavior if no match is found for an element of the topology in the force field. A couple of examples,

When no LJ parameters are found for a particle, they just get assigned epsilon=0 and sigma=1.
When a bond is not matched, the HarmonicBondForce simply has no term for it.

In the rush to make the January workshop release, I had disabled the missing valence checks. We should re-enable those before the alpha release so exceptions can be raised if needed here.

Ah! Sorry, I had missed that. I think I'm going to reenable them, and fix the eventual test failures that come up then.

Thanks, Andrea. Sorry you're spending so much time cleaning up my messes :-/

No worries at all!! We needed to have a working prototype under time constraints so that was absolutely necessary.

OK, I was going to say that these should have been fixed by the new SMIRNOFF99Frosst that does not have generic parameters so you should get an error if you use that file if your parameters are not assigned.
A "power user" could use a generic offxml file in conjunction to get around this problem if they really wanted to run a simulation with only the generic parameters. Like John outlined above

So big picture:

If no parameters are assigned, there should be an exception (so those checks need re-enabling)
But generics are perfectly fine

I think that means THIS issue can be closed and there should be a separate issue to deal with https://github.com/openforcefield/openforcefield/issues/75#issuecomment-465211049

Thanks for your input, @bannanc, @davidlmobley .

I think that means THIS issue can be closed and there should be a separate issue

Will do!


Redirect to users list on user deletion

fixes #675

@DaneEveritt This is good now.

Yeah I would've merged this but I don't seem to be allowed to anymore 😭


Readme/Docs: mention @EnableWebMvc for Spring Boot migration

I upgraded from Springfox 2.9.2 to 3.0.0 in our Spring Boot application. We were using WebMvc without the @EnableWebMvc annotation and the swagger UI wasn't reachable. The problem was that Springfox' SwaggerUiWebMvcConfigurer was never called. After adding @EnableWebMvc to our WebMvc configuration class, http://localhost:8080/swagger-ui/index.html does now work fine.
To keep others from running into the same problem, this PR adds information about @EnableWebMvc to the Spring Boot migration sections in Readme and docs.
By the way, http://localhost:8080/swagger-ui/ still doesn't work in our application, but I haven't yet figured out what the problem is.

Thank you!


rel: prep v0.7.0 release

Which problem is this PR solving?
Prep and changelog v0.7.0 release

Looks good, LMK if you are planning to release all the way through or are looking for us to finish the tag and GitHub release 👍

I'll go ahead and take care of it, thank you!


hn launch

Explanation

[x] Add video to README

Manual test

[x] test next.js app
[x] test Redwood js app
[x] test remix app

https://news.ycombinator.com/item?id=32193506


Test label not shown in Testing panel

Testing #196332
The label given in the config file isn't shown in the UI:

Just found the labels in the Select Configuration... drop-down. It would still seem to make sense to show the label of the currently shown run since there is no way to tell which configuration was used for that run otherwise.


Rendering Freezes/Breaks when Resizing Window when In-Game

Found in b2bcc42 on AMD FX-8350 with GeForce GTX 650 Ti Boost, running Arch Linux 64-bit (4.0.2-1-ARCH kernel with nvidia-340xx 340.86-9 driver) and OpenJDK 1.8.0_45.  Steps to reproduce:

Launch Terasology normally (gradlew runPC).
Create or load a single-player world and start game.
Maximize or unmaximize window.

Expected: window resizes and rendering continues as usual.
Observed: window resizes, but rendering becomes very odd and updates strangely or not at all.  Only crosshairs, HUD/menus, and possibly sun rays render normally.  Note smear of blue/white (sky?) in screenshot below.  It's the only thing that changed as I tried to look around or move.
Workaround: Return to menu and reload world.  Rendering resets to normal.
Normal Rendering Prior to Resize

Broken Rendering after Resize

Uh-oh, that looks squarely up my alley.
I can reproduce the problem in develop. It appears some of the FrameBuffers are not being replaced with new ones matching the new size of the window. It doesn't surprise me as the resizing code, and especially its triggers, are a bit of a mess. And don't even think about taking screenshots with sizes not matching the current display! That might format your hard drive. Or worse!
Fear not however! I seem to have solved the problem in this work branch of mine. Can you by any chance grab it and confirm? There still seems to be an issue as the image is slightly stretched on the Y axis after the resize/maximize/unmaximize, but the stretching disappears as soon as the player moves or rotates, which is perhaps something we can live with for the time being.
That branch is not going to make it directly into a PR however. We need to wait until the current PostProcessor PR goes through. Then I can prioritize the work on the LwjglRenderingProcess class which will be renamed into FrameBufferManager. The functionality that refreshes the FrameBuffers when resizing occurs is there and I'll refactor it to match the code from the work branch.
So, should get fixed soon.

@prestidigitator - thanks for the catch, although no fair, that messed up version looks way more interesting than the black world I get with some streaky white :-(
@emanuele3d we need to keep track of these weird effects for goofy filters. I'm sure there's a potion you can drink one day that'll be supposed to make the world look like that :laughing:

Ha!  Yeah.  Gotta love the pastels.
@emanuele3d - Yes, the issue seems to be solved just as you describe on the emanuele3d/IntroducingPostProcessorAndBuffersManager branch.

@Cervator: I am sure we can find proper ways to render all the psychedelic potions you want to concoct. =)
@prestidigitator: good to know the refactored code solves the problem! I look forward integrating those changes in develop.

P.S. @Cervator: I certainly agree that it'd be good to keep track of these rendering bugs though, and make a gallery with them.

@emanuele3d make it so :D
(And sure, fix all the bugs while you're at it!)

Closing as fixed by #2844!


Draw Borehole

The borehole object does not have an instance for drawing a borehole. Visually representing a borehole upon creation will provide a quick and easy check to make sure the borehole physically possible.

Hello @j-c-cook.
Did you check the visualize_pipes() method of the _BasePipe class, here ?
I would agree that the visualize_pipes() method is not always practical, since the pipe objects require thermal properties for the borehole and soil.
Any reason why you considered a method within the Borehole class rather than a function in the boreholes module?

I did not notice visualize_pipes before writing this code. Is this in an example somewhere?
In borehole because its one borehole top view, however the placement inside of _BasePipe is nice.
My one complaint is that your line thickness on the u-tubes is too thick. To me the purpose of visualizing this top view is a double check that your borehole design makes sense. If the lines detract from that task, then they are too thick.
I set the other variables to 1 (0 breaks the code) in the following minimal example:
# ---- Minimal input for designing a borehole from top view
    # Borehole dimensions
    H = 400  # Borehole length (m)
    D = 5  # burial depth (m)
    r_b = 0.0875  # Borehole radius (m)
    # Pipe dimensions
    rp_out = 0.0133  # Pipe outer radius (m)
    rp_in = 0.0108  # Pipe inner radius (m)
    D_s = 0.029445  # Shank spacing (m)

    # Single U-tube [(x_in, y_in), (x_out, y_out)]
    pos_single = [(-D_s, 0.), (D_s, 0.)]
    # define a borehole
    borehole = gt.boreholes.Borehole(H, D, r_b, x=0., y=0.)
    # variables not needed to visualize borehole
    k_s = 1
    k_g = 1
    R_f_ser = 1
    R_p = 1

    SingleUTube = gt.pipes.SingleUTube(pos_single, rp_in, rp_out,
                                       borehole, k_s, k_g, R_f_ser + R_p)
    fig = SingleUTube.visualize_pipes()

    fig.savefig('mc.pdf')

Cimmino top view:
mc.pdf
Cook top view:
400_m.pdf

I cannot find an example for the visualization. It seems there is none.
Should we work on _BasePipe, or do you think there is still a need for a separate function/method in Borehole?
I agree, the line thickness is too large for the purpose of validating the geometry. Would 0.75 pt (down from 1.5 pt) be better (mc-075.pdf) ?
I see a few features in #48 that is probably useful in your activities, mainly the show_plot (for cluster computations) and save_plot options. These could also be integrated in boreholes.visualize_field().

Another point:
Your visualize_field() method plots everything in black ink. My draw_borehole method plots the outer borehole, the pipe outer radius and the pipe inner radius all a different color. Given that visualizing the top view is a double check, more information can be gathered using different colors. Also, my plot should have a legend indicating rpo, rpi, and rb. It could happen that a user has defined r_po as r_pi unintentionally, in which case the effort of this double check is wasted.
Looks to me like there are good things about both methods. The placement makes more sense inside of _BasePipe. An example could show that the additional variables can be dummy variables set to 1; not a deal breaker.
A line width of 0.75 point looks to be about default, maybe it should be even less.
Yeah #48 has some useful ideas, but your approach of returning fig could be potentially be useful for unforeseen reasons. Although the downsides being:

a user might not close() the figure, and while there should be warnings if there are 1000 figures open, maybe the error handling misses and there's unused data suspended
if a user is using a non-GUI backend, they will have to decide themselves on how to eradicate the errors on a non-GUI machine

Here's a list of improvements neither of our functions include:

low point line width (maybe less than default)
a legend detailing which color corresponds to the borehole, pipe and outer diameters
boolean operator for returning fig (default: False implies closing fig out)

In parallel, we could run a check at the initialization of the pipe object to validate the geometry, which is not done at the moment.
I can work on a class method _check_geometry for the _BasePipe to verify the geometry and return an error if any of the following are False:

r_po > r_pi
r_pi > 0.
k_s > 0. and k_g > 0. and R_fp > 0.
J >= 0
distance(pipe_i, pipe_j) >= 2*r_po
distance(pipe_i, origin) <= borehole.r_b - r_po

I should be able to quickly implement this in the next few days while you work on the visualization.

Yes! Great, thank you.

The _check_geometry method is implemented in 05bfd6.

I think it might be nice to have the borehole thermal resistance calculated and printed out in that custom_borehole.py example file I added.


Please help with some error messages

I have changed the config-example.php to config.php and added my db information and i get these errors. Please help
A PHP Error was encountered
Severity: Warning
Message: mysqli::real_connect(): (28000/1045): Access denied for user<EMAIL_ADDRESS>(using password: YES)
Filename: mysqli/mysqli_driver.php
Line Number: 202
A PHP Error was encountered
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/jrpost77/public_html/system/core/Exceptions.php:272)
Filename: core/Common.php
Line Number: 568
A Database Error Occurred
Unable to connect to your database server using the provided settings.
Filename: core/MY_Controller.php
Line Number: 141

This seems like an authentication error being reported by your MySQL server.  Make sure the your username/password is correct.  Also make sure you have granted permissions, from the error it looks like you're not using localhost.  If permissions are only granted for that user on the localhost, it won't work.
To troubleshoot, try connecting to the sql server from your webserver with the same username/password.  mysql -u jrpost7 -p -h


[SPARK-26412][PYTHON][FOLLOW-UP] Improve error messages in Scala iterator pandas UDF

What changes were proposed in this pull request?
This PR proposes to improve the error message from Scalar iterator pandas UDF.
Why are the changes needed?
To show the correct error messages.
Does this PR introduce any user-facing change?
Yes, but only in unreleased branches.
import pandas as pd
from pyspark.sql.functions import pandas_udf, PandasUDFType

@pandas_udf('long', PandasUDFType.SCALAR_ITER)
def pandas_plus_one(iterator):
      for _ in iterator:
            yield pd.Series(list(range(20)))

spark.range(10).repartition(1).select(pandas_plus_one("id")).show()

Before:
AssertionError: Pandas MAP_ITER UDF outputted more rows than input rows.

After:
RuntimeError: The length of each output series (or frame) in Scalar iterator
pandas UDF should be the same with the input's; however, the length of
output series (or frame) was 20 and the length of the input's was 10.

How was this patch tested?
Unittests were fixed accordingly.

Test build #120866 has started for PR 28135 at commit dfd959d.

Merged build finished. Test PASSed.

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

Test build #120866 has finished for PR 28135 at commit dfd959d.

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

Merged build finished. Test FAILed.

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

Test build #120869 has started for PR 28135 at commit 75c84f8.

Merged build finished. Test PASSed.

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

Test build #120869 has finished for PR 28135 at commit 75c84f8.

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

Merged build finished. Test PASSed.

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

@WeichenXu123, mind taking another look when you're available?

Test build #120992 has started for PR 28135 at commit 504ec1d.

Merged build finished. Test PASSed.

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

Test build #120992 has finished for PR 28135 at commit 504ec1d.

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

Merged build finished. Test FAILed.

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

Test build #120994 has started for PR 28135 at commit 0c1df44.

Merged build finished. Test PASSed.

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

Test build #120995 has started for PR 28135 at commit 6309034.

Merged build finished. Test PASSed.

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

Test build #120994 has finished for PR 28135 at commit 0c1df44.

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

Merged build finished. Test PASSed.

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

Test build #120995 has finished for PR 28135 at commit 6309034.

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

Merged build finished. Test PASSed.

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

Merged to master and branch-3.0.