evaluator: unexpected non-concrete value when unifying with Go API

What version of CUE are you using (cue version)?

$ cue version
v0.5.0-beta.5

Does this issue reproduce with the latest stable release?
Yes
What did you do?
go mod tidy
go run .
cmp stdout expect-output
-- expect-output --
{
	x: "{}"
}
-- go.mod --
module test

require cuelang.org/go v0.5.0-beta.5
-- main.go --
package main

import (
	"fmt"
	"log"

	"cuelang.org/go/cue"
	"cuelang.org/go/cue/cuecontext"
)

var cueCode = `
import "encoding/json"
x: string
json.Unmarshal(x)
`

func main() {
	ctx := cuecontext.New()
	v := ctx.CompileString(cueCode)
	if err := v.Err(); err != nil {
		log.Fatal(err)
	}
	v = v.FillPath(cue.MakePath(cue.Str("x")), "{}")
	if err := v.Err(); err != nil {
		log.Fatalf("after unify: %v", err)
	}
	fmt.Println(v)
}

What did you expect to see?
A passing test.
What did you see instead?
> go mod tidy
> go run .
[stderr]
main.go:21: error in call to encoding/json.Unmarshal: non-concrete value string
exit status 1

[exit status 1]
FAIL: /tmp/testscript645762630/x.txtar/script.txtar:2: unexpected go command failure

Here's another problem, probably closely related. The following test goes into an infinite loop:
go mod tidy
go run .
cmp stdout expect-output
-- expect-output --
unifying
unified:  {
	a: {}
}
-- go.mod --
module test

require cuelang.org/go v0.5.0-beta.5
-- main.go --
package main

import (
	"fmt"
	"log"

	"cuelang.org/go/cue/cuecontext"
)

var cueCode1 = `
a: {}
[a][0]		// Any expression involving a will behave the same here.
`

func main() {
	ctx := cuecontext.New()
	v1 := ctx.CompileString(cueCode1)
	if err := v1.Err(); err != nil {
		log.Fatal("error1: ", err)
	}
	v2 := ctx.CompileString(cueCode1)
	if err := v2.Err(); err != nil {
		log.Fatal("error2: ", err)
	}
	fmt.Println("unifying")
	v := v1.Unify(v2)
	if err := v.Err(); err != nil {
		log.Fatal("error3: ", err)
	}
	fmt.Println("unified: ", v)
}

Note that v1.Unify(v1) succeeds OK, even though technically v1 and v2 contain exactly the same CUE.

Even simpler:
go mod tidy
go run .
cmp stdout expect-output
-- expect-output --
unifying
unified:  {
	a: {}
}
-- go.mod --
module test

require cuelang.org/go v0.5.0-beta.5
-- main.go --
package main

import (
	"fmt"

	"cuelang.org/go/cue/cuecontext"
)

func main() {
	ctx := cuecontext.New()
	c := `a: {}, a`
	v1 := ctx.CompileString(c)
	v2 := ctx.CompileString(c)
	fmt.Println("unifying")
	v := v1.Unify(v2)
	fmt.Println("unified: ", v)
}

(also verified to be a regression from v0.4.3)

I've bisected the infinite loop issue to https://review.gerrithub.io/c/cue-lang/cue/+/529524

Split the second bug, which is a regression, into https://github.com/cue-lang/cue/issues/2293. Moving out of the v0.5 milestone, as this issue is now about the original reproducer.

Just to confirm, @rogpeppe: the core issue you are now reporting here is that the initial value is in error:
What did you do?
go mod tidy
go run main.go

-- go.mod --
module test

go 1.20

require cuelang.org/go v0.5.0-beta.5

-- main.go --
package main

import (
	"log"

	"cuelang.org/go/cue/cuecontext"
)

var cueCode = `
import "encoding/json"
x: string
json.Unmarshal(x)
`

func main() {
	ctx := cuecontext.New()
	v := ctx.CompileString(cueCode)
	if err := v.Err(); err != nil {
		log.Fatal(err)
	}
}

What did you expect to see?
Passing test
What did you see instead?
> go mod tidy
> go run main.go
[stderr]
main.go:19: error in call to encoding/json.Unmarshal: non-concrete value string
exit status 1

[exit status 1]
FAIL: /tmp/testscript2175928170/repro.txtar/script.txtar:2: unexpected go command failure

i.e. the FillPath() call does not play a part in the expectation.

Ping @rog to reply to https://github.com/cue-lang/cue/issues/2288#issuecomment-1499593791

Just to confirm, @rogpeppe: the core issue you are now reporting here is that the initial value is in error:

No, that's not the core issue I'm trying to report here (although I do actually believe that that's an issue in itself: I think Value.Err should return an error only when there is nothing that can be done to make the value OK).
The issue I'm demonstrating here is that even when x is filled with a concrete string value that should make the json.Unmarshal call complete OK and unify with the containing struct, it fails.
That is, the original example should be equivalent to
x: "{}"
{}

which works OK.

Update: although the original json.Unmarshal example at the top is still problematic, the other examples (this and this) that I mentioned  now work OK, as of<EMAIL_ADDRESS>


Dependency Check as Java Library

Since Dependency Check is build in Java, it would be cool to also have a plain Java API besides the CLI interface and the several tool plugins.
Would it be a big effort to provide a library that can be used to build other Java applications above Dependency Check?
Something like...
DependencyCheck dc = new DependencyCheck(dcConfiguration);
dc.scan(pathToJars, outPath);

use https://github.com/jeremylong/DependencyCheck/tree/main/core

as Mark pointed out - the core library can be used. Examples on how to use it can be found in the CLI, Maven, and Ant modules. There is also DependencyCheckScanAgent.java - but this hasn't been kept up to date like the other standard interfaces. In reality - just using the core engine isn't that hard.

Alright, thanks. I will try it that way. It's not actually the same as a Maven managed library, but it will work too, I guess.

It's not actually the same as a Maven managed library

Oh, but it is actually a Maven managed library:
https://github.com/jeremylong/DependencyCheck/blob/45080ab3ee309d9ed6945cc37bdd53594d3c6ac3/core/pom.xml#L20
https://search.maven.org/artifact/org.owasp/dependency-check-core

Oh, ok, I should have noticed the pom.xml, but I was just: Ok, cool, he pointed me to a subtree of the source code, that's nice, but not exactly what I was looking for. But actually, it was. I'm so sorry. Thank you very much.


alloyeditor support

A really simple AlloyEditor (alloyeditor.com) integration, hopefully it's useful to someone.
It's not documented on the website, but alloyeditor apparently creates a contenteditable div, copying original content, if you pass in a textarea.

Hi @caffodian! Thanks very much for the pull request. :smile:  Could you also update the README to support AlloyEditor's integration into this project?

added!


Auth0Provider sends an authorize call on mount

Describe the problem

Provide a clear and concise description of the issue

When the Auth0Provider (with refresh tokens and localstorage cache) mounts, it makes an authorize call to Auth0, even if a user hasn't initialised a session. This creates a "login required" error in the Auth0 logs, which will potentially flood them.
What was the expected behavior?

Tell us about the behavior you expected to see

Auth0Provider shouldn't automatically make an authorize query on mount, or at least this should be "opt-in".
Reproduction

Detail the steps taken to reproduce this error, and whether this issue can be reproduced consistently or if it is intermittent.
Note: If clear, reproducable steps or the smallest sample app demonstrating misbehavior cannot be provided, we may not be able to follow up on this bug report.

I used the nextjs example in the example folder and configured the provider like so:
<Auth0Provider
  cacheLocation="localstorage"
  useRefreshTokens={ true }
  domain={process.env.NEXT_PUBLIC_DOMAIN}
  clientId={process.env.NEXT_PUBLIC_CLIENT_ID}
  audience={process.env.NEXT_PUBLIC_AUDIENCE}
  scope="read:users"
  redirectUri={typeof window !== 'undefined' && window.location.origin}
  onRedirectCallback={onRedirectCallback}
>

Can the behavior be reproduced using the React SDK Playground?
If so, provide steps:

Where applicable, please include:

The smallest possible sample app that reproduces the undesirable behavior
Log files (redact/remove sensitive information)
Application settings (redact/remove sensitive information)
clientId and domain (these are publicly available)
Screenshots

Environment

Please provide the following:

Version of auth0-react used: 1.1.0
Which browsers have you tested in? Chrome Version 85.0.4183.102 (Official Build) (64-bit)
Which framework are you using, if applicable (Angular, React, etc): React
Other modules/plugins/libraries that might be involved: Auth0 SPA SDK 1.12.1

Hi @ellioseven - thanks for raising this.
This is a known issue in auth0-spa-js that stems from our decision to fallback to silent iframe auth when no refresh token is present (to prevent user's being logged out when clients switched to rotating refresh tokens).
We are currently planning some work to resolve this in auth0-spa-js, and I'll update this bug when that work has started (which may not be for a few weeks)


Allow forcing a Block Index Update via GraphQL Query

depends on https://github.com/vivid-planet/comet/pull/1222

add a force arg to dependencies() and dependents() field resolver

Is it a good idea to do this as a side effect of the dependents/dependencies queries? Shouldn't this be a separate mutation, for instance, refreshDependencies?

I think it is Ok. With a mutation you win nothing only complicate things.


save bilibili_history with json

fix https://github.com/yihong0618/GitHubPoster/issues/61

Thanks
Can you fix the lint?

I don't know what's go wrong. flake8? I didn't use it. https://github.com/yihong0618/GitHubPoster/actions/runs/3195512610/jobs/5216660597#step:7:175

black and isort
you can find the command in README

Will take a look tonight(^-^)

@zjgcjy drop .gitignore the IN_FOLDER for user easy to use GitHub Actions

Great thanks.


Fix getitem optimization such that only starting fields can be discovered as necessary

Fix for #126

Codecov Report

Merging #131 (eef2b13) into main (7fe448a) will increase coverage by 0.07%.
The diff coverage is 97.61%.

@@            Coverage Diff             @@
##             main     #131      +/-   ##
==========================================
+ Coverage   95.55%   95.62%   +0.07%
==========================================
  Files          17       17
  Lines        1686     1714      +28
==========================================
+ Hits         1611     1639      +28
  Misses         75       75

Impacted Files
Coverage Δ

src/dask_awkward/lib/optimize.py
95.83% <96.66%> (+1.66%)
:arrow_up:

src/dask_awkward/lib/inspect.py
100.00% <100.00%> (ø)

src/dask_awkward/lib/io/parquet.py
89.26% <100.00%> (-0.40%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Materialize tabs and backbonejs

hi guys, hey someone can use tabs in backbone ?
i'm trying all day but tabs become white (font and background) when initialize tabs.
someone know how i can resolve this ?
?
sorry for my english :(

Please ask support questions on Stack Overflow instead. Github is for bug reports related to the framework.

Sorry, that happened because I import jquery, materialize and jquery ui in that order.
The correct order is jquery, jquery ui and materialize

Thanks for the follow up, I'm sure it'll help others with the same problem.


added values to animal category

Codecov Report

Merging #7 into main will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main        #7   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           12        12
  Lines          148       144    -4
=========================================
- Hits           148       144    -4

Impacted Files
Coverage Δ

qual_id/categories/animal.py
100.00% <ø> (ø)

qual_id/pattern.py
100.00% <0.00%> (ø)

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 a22dd50...2dfa934. Read the comment docs.

Hey @mephi007
Thanks a lot for the contribution! I've just spotted a couple of tweaks but other than that it looks great! I'll add comments

Great job and thanks a lot for the contribution @mephi007 !

The build is automated so the code should be live in a few minutes

Thank you so much for the opportunity.. this was my first PR open-source...
Hey @gabrielbarker is there anything as such end to end product, where I can contribute, as I know Java and Python.

Congratulations on your first PR!🎉🎉🎉
You did great, and you clearly have a good understanding of git.
There is not yet an end to end product for this project, just the API here but I will let you know if that ever changes! Thanks a lot


Add new flag to "release" for specifying commitish

Resolves #820.
I see this command has no Cucumber tests. I'm too inexperienced to write one I think. I tested the new flag manually: it works fine. Let me know what you think. Thanks!

Thanks for the contribution and sorry for the late reply! I'll review this when I have the time.

Thanks! We'll probably change the release command interface a little bit (or a whole lot), but this is a good starting point!


Async Loading Screen Shows Black Screen on Startup

I'm using the Async Loading Screen plugin in Unreal Engine 5.3.2 and I'm encountering an issue where the screen just shows black on startup (regardless of if i'm playing the game in Standalone version or if it's actually packaged for shipping) and then simply goes to my main menu. I've tried updating my graphics driver, revisiting the setup instructions, looking at fixes for other issues, etc... but the issue persists.
I've tried it in different projects, disabled all other unused plugins, different mp4 files (including the ones provided in the instructions), but it doesn't work for some reason.
Any help would be greatly appreciated, thanks.

Hi,
Have you carefully followed the tutorial to understand how it works yet? Usually, this issue is caused by the movie path not being correct.

Thanks for the response,

My bad, I accdientally closed the issue.
Thank you for the response, but unfortunately. the movie path doesn't seem to be the issue. It stays on the black screen for about 3 seconds and then loads into the main menu. Is there anything I can do about this?

I recommend following the plugin's tutorial to see how it works. If the movie clip in the tutorial works (which I am sure works fine), there may be something wrong with your clip format or path, or your project has a plugin that conflicts with AsyncLoadingScreen.

@truong-bui i can verify it, the video is appearing after a long long time!

@truong-bui I can say with 100% certainty that I have followed the plugin's tutorial to see how it works and have done the exact steps mentioned there. I made a whole new blank project, enabled ONLY AsyncLoadingScreen (disabled other plugins), followed the steps, put the clip path exactly as mentioned (I used the clip in the tutorial) and it still comes up as just black for 3 seconds and then brings me to the Open Level Button. I also tried the default loading screen setting and that works just fine, however, the startup loading screen does not work. Before adding the movie clip, it does display a black screen with a white border at the bottom, but that doesn't help me considering I need a video at startup.

Well, it is very weird. Because it just works fine on my side. Here you can check the Async Loading demo that I packaged recently with Unreal version 5.3.2 https://drive.google.com/file/d/1b7rRsqwR1rl_1TJpnLYUYTImA31SyA3I/view?usp=drive_link
Can you please provide a link/screenshot/video to the issue? So I can take a look at it. I cannot help if I can't reproduce the issue on my side.

Thank you for the support, I managed to find the issue out through trial and error. Apparently, something to do with the permissions for my Windows Explorer/Account was not allowing Unreal Engine/AsyncLoadingScreen to see the file and therefore was just playing nothing. Atleast for now, I managed to fix it and now it finally works which is great.
Again, thank you for the help and I'm sorry for any inconveniences caused.


Reproducing results from the java implementation

Thanks for the package!

Problem
I'm currently trying to switch from the "official" implementation (https://gamma.greyc.fr/) to this one, but I'm having trouble getting to the same results.

Reproducing
As an example, I tried the Alex, Paul, Suzan data from the java web app. Converted to the format the continuum expects, it looks as follows:

Alex,1,2,12
Alex,2,13,19
Alex,5,24,30
Alex,6,32,36
Alex,6,36,44
Alex,7,49,60
Paul,1,2,9
Paul,3,11,17
Paul,5,19,25
Paul,6,32,44
Suzan,1,2,9
Suzan,4,11,17
Suzan,5,21,27
Suzan,6,32,36
Suzan,6,36,40
Suzan,6,42,46
Paul,7,48,58
Suzan,7,48,58

In the web app, this gives me γ = 0.451034437799.
Using the same data in your implementation gives a different value for gamma:
from pyannote.core import Segment
from pygamma_agreement import Continuum, CombinedCategoricalDissimilarity

continuum = Continuum.from_csv("test_data/aps.csv")
dissim = CombinedCategoricalDissimilarity(list(continuum.categories), alpha=1, beta=1)
gamma_results = continuum.compute_gamma(dissim, precision_level=0.01)

print(f"The gamma for that annotation is f{gamma_results.gamma}")

The gamma for that annotation is f0.5044930080375523

I've also tried my own data, where the results sometimes differ even more (negative vs. positive).
I'm using alpha=1 and beta=1, which, as I understand from the Gamma paper, seem to be the default values. However, I'm not sure whether these are the values used in the java implementation and haven't managed to find out.
Is there any parameter I'm missing or setting to a wrong value?

Environment
I'm using pygamma_agreement==0.1.6 with python 3.8.7 on Fedora 33.

PS: Curiously, I just noticed that I'm also getting different results from the java web app and the java offline app, which gives me gamma=0.55

Hi, thank you for issue,
The software from Mathet et al.  https://gamma.greyc.fr/  is not using the parameters that have been mentionned in the paper. We found the same discrepancy as you when we did the re-implementation.
The software is using alpha=1 et beta=3. It was confirmed to us by the original authors for the alpha and beta params.
Besides, there might be slight differences +- 0.01 with their implementation. We have one main suspect:
The shuffling/sampling methodology they mentionned in their paper might be hard to replicate without access to their code. So we made the most rationale choices.

Hi,
thanks for the quick reply! With these parameters, I'm getting gamma=0.405, which is still a good bit off from the java result.
With my own data, the difference is much larger: gamma=-0.07 (-0.13 <= gamma <= -0.02) for the java version and gamma=0.122 for the python version. I can upload a sample of my data if that helps.
Any suggestions on how I could debug this further? Is that in the range that you would expect from the shuffling method?

Yes a sample of your data might help us to understand how you get this discrepancy indeed!

Hi,
thanks for the quick reply! With these parameters, I'm getting gamma=0.405, which is still a good bit off from the java result.
With my own data, the difference is much larger: gamma=-0.07 (-0.13 <= gamma <= -0.02) for the java version and gamma=0.122 for the python version. I can upload a sample of my data if that helps.

If i well understood, you obtained the negative gamma value -0.07  with the java version?

Any suggestions on how I could debug this further? Is that in the range that you would expect from the shuffling method?
What range are you referring to ?

Yes a sample of your data might help us to understand how you get this discrepancy indeed!
This is the data I'm currently using: continuum.csv.gz
Note that I'm just experimenting with this data and comparing a simple baseline method to manual annotations, therefore the agreement is expected to be low.

If i well understood, you obtained the negative gamma value -0.07 with the java version?
Exactly. It also gives a range (probably a kind of confidence interval), which is the -0.13 <= gamma <= -0.02 that I reported.

What range are you referring to ?
You said that there could be slight differences to the original implementation, that's what I meant by "range".

Hi,
After investigations, your low value of gamma might come that there are many splits of your pred timeline (a segment t1-tn transformed in t1-t2, t2-t3,... t(n-1)-tn) This type error is heavily penalized by the gamma as it is looking for an alignment.
Besides, the gamma agreement has been designed to be an agreement between two annotators, not exactly as a metric for ML systems.
Therefore, we think that the chance should not depend on the pred timeline, to be able to compare all systems. we implemented this option ground_truth_annotators but it is not documented:
https://github.com/bootphon/pygamma-agreement/blob/master/pygamma_agreement/continuum.py#L173
As mentioned in this other issue https://github.com/bootphon/pygamma-agreement/issues/16 the use of the gamma as a metric remains an open research question we think.

As update v0.2.0 fixes any problems regarding differences between the java implementation and ours', and those differences are explained in the new "Issues" section of the documentation, this issue is outdated.


Why does wrapDisplayName get stripped in production?

Recompose Version: 0.21.2
In this case I am using defaultProps from the recompose lib.
When process.env.NODE === 'development', the displayName for the component is what I expect it to be- defaultProps(MyComponentName)
When process.env.NODE === 'production', the displayName for the component is DefaultProps (note: both the "D" is capitalized and "MyComponentName" is no longer present).
I see that the wrapping of the display name is intentionally omitted here
https://github.com/acdlite/recompose/blob/master/src/packages/recompose/createHelper.js#L7
And believe that the displayName of "DefaultProps" is a result of React inferring it from here
https://github.com/acdlite/recompose/blob/master/src/packages/recompose/defaultProps.js#L6
I can "coerce" it to what I want by applying setDisplayName after defaultProps but that is not ideal.
Am I misusing the lib? Is this a bug? Is this the expected/desired behavior?

Expected, displayName is only needed for dev mode, there is no need in it in production at all so in production JSX sets this value automatically

Ok. Do you happen to know the rules for how React sets that value in Production? I have found some information saying that it will still use the displayName if present and will otherwise fallback to the function/class name, but nothing authoritative.
My use case is that I want to use displayName for determining the type of the children in another components render function. So why not use true type checking? Well, we use HOCs in our app and the type checking breaks down under this scenario.  I know displayName is not the best solution, but I have a way to enforce unique display names and this was working while also giving us the flexibility of using HOCs.

It looks like this is handled by Babel. https://github.com/babel/babel/tree/master/packages/babel-plugin-transform-react-display-name

Expected, displayName is only needed for dev mode, there is no need in it in production at all so in production JSX sets this value automatically

The displayName can absolutely be useful in production. React uses displayName when logging errors caught in the render cycle, even in production builds. Also, display names are very useful when using the React developer tools, which is often used in production. It seems to me that stripping the displayName should be left to consumer and really should not be a decision that recompose makes for them.

It looks like this is handled by Babel. https://github.com/babel/babel/tree/master/packages/babel-plugin-transform-react-display-name

That plugin is only works if you're using createReactClass, which recompose is not using, as far as I know.


ImportError: cannot import name 'deform_conv_ext'

Greatly thank for your sharing.
when I run the command:
tools/dist_trainval.sh configs/trainval/tinaface/tinaface.py "0,1,2,3"

I met this problem:
ImportError: cannot import name 'deform_conv_ext'

Maybe this cause by dcn, Would you mind giving some suggestions for me?
Thx.

@gmt710 Have you installed vedadet as following?
pip install -r requirements/build.txt
pip install -v -e .

Yeah, I'll try again.

Can I use torch==1.1.0 ? Because my cuda version is 9.0.

@hxcai ,Hello, it do not include the file vedadet/ops/dcn/src/deform_conv_ext.cpp

@gmt710 we recommend using torch==1.6.0 or higher.

@hxcai ,thanks for your reply.My enviroment ,cuda9.2 torch1.6.0 test good.
I have another problem about how to prepare widerface datasets for train and test ?
Refers the code comments and the bugs, I prepare widerface data but test and train are not working properly.

Thank you for your sharing.
But I have this issue,too.  I don't know how  to figure it out.
ImportError: cannot import name 'deform_conv_ext'
I have try this :
pip install -r requirements/build.txt
pip install -v -e .
But I've got :
Using pip 20.2.4 from /home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip (python 3.7)
Non-user install because site-packages writeable
Created temporary directory: /tmp/pip-ephem-wheel-cache-l6jhmr6r
Created temporary directory: /tmp/pip-req-tracker-mxmsm8pp
Initialized build tracking at /tmp/pip-req-tracker-mxmsm8pp
Created build tracker: /tmp/pip-req-tracker-mxmsm8pp
Entered build tracker: /tmp/pip-req-tracker-mxmsm8pp
Created temporary directory: /tmp/pip-install-yi04rbse
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
Obtaining file:///home/cv/PycharmProjects/vedadet
Added file:///home/cv/PycharmProjects/vedadet to build tracker '/tmp/pip-req-tracker-mxmsm8pp'
Running setup.py (path:/home/cv/PycharmProjects/vedadet/setup.py) egg_info for package from file:///home/cv/PycharmProjects/vedadet
Created temporary directory: /tmp/pip-pip-egg-info-63ncdptk
Running command python setup.py egg_info
/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/torch/cuda/init.py:52: UserWarning: CUDA initialization: The NVIDIA driver on your system is too old (found version 10010). Please update your GPU driver by downloading and installing a new version from the URL: http://www.nvidia.com/Download/index.aspx Alternatively, go to: https://pytorch.org to install a PyTorch version that has been compiled with your version of the CUDA driver. (Triggered internally at  /opt/conda/conda-bld/pytorch_1603729138878/work/c10/cuda/CUDAFunctions.cpp:100.)
return torch._C._cuda_getDeviceCount() > 0
Traceback (most recent call last):
File "", line 1, in
File "/home/cv/PycharmProjects/vedadet/setup.py", line 146, in
'src/cuda/nms_cuda.cpp', 'src/cuda/nms_kernel.cu'
File "/home/cv/PycharmProjects/vedadet/setup.py", line 33, in make_cuda_ext
raise EnvironmentError('CUDA is required to compile vedadet')
OSError: CUDA is required to compile vedadet
No CUDA runtime is found, using CUDA_HOME='/usr/local/cuda'
Compiling nms_ext without CUDA
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
Exception information:
Traceback (most recent call last):
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/cli/base_command.py", line 228, in _main
status = self.run(options, args)
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/cli/req_command.py", line 182, in wrapper
return func(self, options, args)
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/commands/install.py", line 324, in run
reqs, check_supported_wheels=not options.target_dir
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/resolution/legacy/resolver.py", line 183, in resolve
discovered_reqs.extend(self._resolve_one(requirement_set, req))
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/resolution/legacy/resolver.py", line 388, in _resolve_one
abstract_dist = self._get_abstract_dist_for(req_to_install)
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/resolution/legacy/resolver.py", line 326, in _get_abstract_dist_for
return self.preparer.prepare_editable_requirement(req)
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/operations/prepare.py", line 526, in prepare_editable_requirement
req, self.req_tracker, self.finder, self.build_isolation,
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/operations/prepare.py", line 91, in _get_prepared_distribution
abstract_dist.prepare_distribution_metadata(finder, build_isolation)
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/distributions/sdist.py", line 40, in prepare_distribution_metadata
self.req.prepare_metadata()
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/req/req_install.py", line 555, in prepare_metadata
self.metadata_directory = self._generate_metadata()
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/req/req_install.py", line 535, in _generate_metadata
details=self.name or "from {}".format(self.link)
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/operations/build/metadata_legacy.py", line 73, in generate_metadata
command_desc='python setup.py egg_info',
File "/home/cv/anaconda3/envs/tinaface/lib/python3.7/site-packages/pip/_internal/utils/subprocess.py", line 242, in call_subprocess
raise InstallationError(exc_msg)
pip._internal.exceptions.InstallationError: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
Removed file:///home/cv/PycharmProjects/vedadet from build tracker '/tmp/pip-req-tracker-mxmsm8pp'
Removed build tracker: '/tmp/pip-req-tracker-mxmsm8pp'

@gmt710 please see this for data preparing.

@Kerr46 It seems that your environment has no cuda?

@hxcai , Greatly Thanks. I'll try.

@hxcai ,I follow  this ,also met same problem.
Maybe parse xml do not work.

@mike112223 ,Thanks. I'll try.

I took some notes for reference.   https://blog.csdn.net/qq_35975447/article/details/110430390

@gmt710 Great, thanks for sharing!

Thanks. The result is same with your paper. I test no TTA（the result is good）：

If I want to use cuda9.0, Do you have any suggestions for me to modify dcn?
I've tried the version of dcn from mmdetection several times but fail .

@hxcai You can try to use dcn in old version mmdetection that supports cuda9.0. But we don't recommend to do that.

@gmt710 You can try to use dcn in old version mmdetection that supports cuda9.0. But we don't recommend to do that.

@hxcai , Is this mainly because there is a corresponding relationship between torch and CUDA versions?

@gmt710 specified torch and dcn implementation is related to specified cuda version.

I am still facing the same problem after doing all of what was suggested above, can anyone help?


Feature: add socket_path to icinga2_idopgsqlconnection and icinga2_idomysqlconnection custom resources

Problem
With the existing icinga2_idopgsqlconnection and icinga2_idomysqlconnection custom resources, you are unable to set the socket_path option in the object.
While I was using the chef-icingaweb2 cookbook, it does not set socket_path, so it defaults to /var/lib/mysql/mysql.sock when host is set to localhost.
Justification
Users may need to specify where there socket is located if they don't want to open up permissions to /var/lib/mysql or they have a non-standard socket path.
Solution
Add the socket_path variable to both icinga2_idopgsqlconnection and icinga2_idomysqlconnection custom resources and their templates.
I didn't see any specific testing in place for the custom resource, so please let me know if I need to add a test or two.

@taylorsmcclure 👍


Jit configs deploiyment mukt av1.1

@egov-arindam A new migrate topic is defined for estimate to do reindexing


Some weapon damage types are not set

e.g. silver dagger, cold iron rapier.
Probably because of the special materials


"A valid integer must be provided to limit" only warning, should be throwing error

I have this "A valid integer must be provided to limit" message being logged to console in my logs, but there's no way or in the documentation to attach that message to a stack trace, at or least force it to throw an error instead of just logging a random message.

Would it not be fairly easy to find where you are using limits and narrow it down?
Barring that, maybe you can find that in the source code and edit it temporarily to throw?


null safe equal support in joins

Is your feature request related to a problem?
I'm planning to add intersect and intersect all operator into Daft and get some feature parity with Spark. During the evaluation and code browsing, I noticed that Daft doesn't support null safe equal in joins, it would be great that we can support null safe equal in joins.
P.S: an intersect operator could be rewritten as a semi join with null safe equal.
SELECT a1, a2 FROM t1 INTERSECT SELECT b1, b2 FROM t2
-- is effective the same as
SELECT DISTINCT a1, a2 FROM t1 LEFT SEMI join t2 on a1 <> b1 and a2 <> b2

Describe the solution you'd like

add one more parameter to indicate whether the equality condition are null safe or not in joins' DataFrame API and various join ops
passing the null safe equality property down to the native execution level
build is_equal in src/daft-table/src/ops/joins/hash_join.rs#hash_semi_anti_join and other related code, makes the execution null safe aware

Describe alternatives you've considered
Another possible solution is to make join operators to relies on join conditions rather the left_on and right_on keys directly, in that way, null safe equal could be easily added as a new expression.
However, that would require massive code change in daft's current code base and I don't think it's worthy for just null safe equal support.
Additional Context
I can submit a PR to add null safe equal support if we all agree it's the right time to add.
Would you like to implement a fix?
No

Hi @advancedxy, thanks for making an issue here! @universalmind303 is building out SQL support and @kevinzwang has done lots of work on the semi joins. Would love to hear their thoughts

What do you think about doing an outer join + filter instead?  We could make it an expression as well, similar to pyspark's eqNullSafe. @advancedxy thanks for bringing this up, and feel free to take a stab at implementation yourself first!

Thank you @advancedxy !


Write proper SPDX License strings

Signed-off-by: Nathen Harvey<EMAIL_ADDRESS>
[ ] New functionality includes tests
[x] All tests pass
[ ] RELEASE_NOTES.md has been updated if required (not required for bugfixes, required for API changes)
[x] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Beautiful


test: Small changes by go formatting & removing unused parameters

The odfcsv parameter is no longer needed to be passed for deploying &
undeploying odf as all the csvs will be checked by another function at
the end of installation. Also go formatted all the files.
Signed-off-by: Malay Kumar Parida<EMAIL_ADDRESS>

/cc @iamniting


changed link in examples.md

I get a 404 using the example link. the new link should work.

:+1: Thanks!


System.Data.SqlClient.SqlException (0x80131904)

Hello
I am trying to connect Visual Studio 2017 to SQL Server 2016 Express using the following code in my app.config:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <!-- For more information on Entity Framework configuration, visit http://go.microsoft.com/fwlink/?LinkID=237468 -->
    <section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
  </configSections>
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
  </startup>
  <entityFramework>
    <defaultConnectionFactory type="System.Data.Entity.Infrastructure.SqlConnectionFactory, EntityFramework" />
    <providers>
      <provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer" />
    </providers>
  </entityFramework>

  <connectionStrings>
    <add name="BlogDbContext" connectionString="Data Source=DESKTOP-I3K90LQ\SQL2016;Initial Catalog=CodeFirstDemo;Integrated Security=SSPI;" providerName="System.Data.SqlClient"/>
  </connectionStrings>
</configuration>

I created a sample repository to test in my program.cs file
using System;
using System.Collections.Generic;
using System.Data.Entity;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace ConsoleApp1
{
    public class Post
    {
        public int Id { get; set; }
        public DateTime DatePublished { get; set; }
        public DateTime DateEdited { get; set; }
        public string Title { get; set; }
        public string Body { get; set; }
    }

    public class BolgDbContext : DbContext
    {
        public DbSet<Post> Posts { get; set; }
    }

    class Program
    {
        static void Main(string[] args)
        {
        }
    }
}

I installed Entity Framework into my Console Application using the following command in the Package Manager Console
PM>install-package EntityFramework -version 6.1.3

Then I enable Migration and create the first migration:
PM>enable-migrations
PM>add-migrations CreatePost
PM>update-database

after submitting update-database command I get following error message:
System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
   at System.Data.Entity.Infrastructure.Interception.DbConnectionDispatcher.<Open>b__36(DbConnection t, DbConnectionInterceptionContext c)
   at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext](TTarget target, Action`2 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)
   at System.Data.Entity.Infrastructure.Interception.DbConnectionDispatcher.Open(DbConnection connection, DbInterceptionContext interceptionContext)
   at System.Data.Entity.SqlServer.SqlProviderServices.<>c__DisplayClass33.<UsingConnection>b__32()
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.<>c__DisplayClass1.<Execute>b__0()
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute(Action operation)
   at System.Data.Entity.SqlServer.SqlProviderServices.UsingConnection(DbConnection sqlConnection, Action`1 act)
   at System.Data.Entity.SqlServer.SqlProviderServices.UsingMasterConnection(DbConnection sqlConnection, Action`1 act)
   at System.Data.Entity.SqlServer.SqlProviderServices.CreateDatabaseFromScript(Nullable`1 commandTimeout, DbConnection sqlConnection, String createDatabaseScript)
   at System.Data.Entity.SqlServer.SqlProviderServices.DbCreateDatabase(DbConnection connection, Nullable`1 commandTimeout, StoreItemCollection storeItemCollection)
   at System.Data.Entity.Core.Common.DbProviderServices.CreateDatabase(DbConnection connection, Nullable`1 commandTimeout, StoreItemCollection storeItemCollection)
   at System.Data.Entity.Core.Objects.ObjectContext.CreateDatabase()
   at System.Data.Entity.Migrations.Utilities.DatabaseCreator.Create(DbConnection connection)
   at System.Data.Entity.Migrations.DbMigrator.EnsureDatabaseExists(Action mustSucceedToKeepDatabase)
   at System.Data.Entity.Migrations.Infrastructure.MigratorBase.EnsureDatabaseExists(Action mustSucceedToKeepDatabase)
   at System.Data.Entity.Migrations.DbMigrator.Update(String targetMigration)
   at System.Data.Entity.Migrations.Infrastructure.MigratorBase.Update(String targetMigration)
   at System.Data.Entity.Migrations.Design.ToolingFacade.UpdateRunner.Run()
   at System.AppDomain.DoCallBack(CrossAppDomainDelegate callBackDelegate)
   at System.AppDomain.DoCallBack(CrossAppDomainDelegate callBackDelegate)
   at System.Data.Entity.Migrations.Design.ToolingFacade.Run(BaseRunner runner)
   at System.Data.Entity.Migrations.Design.ToolingFacade.Update(String targetMigration, Boolean force)
   at System.Data.Entity.Migrations.UpdateDatabaseCommand.<>c__DisplayClass2.<.ctor>b__0()
   at System.Data.Entity.Migrations.MigrationsDomainCommand.Execute(Action command)
ClientConnectionId:00000000-0000-0000-0000-000000000000
Error Number:-1,State:0,Class:20
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

So my Visual Studio is not able to connect to my SQL Server Management Studio to create a database.
If this work right, my Code First console project should be able to use a Sql instance instead of LocalDb instance to create and update a database from Visual Studio.
I have searched google for solutions for hours last night. Some suggest that could firewall issues, that I should create a port 1433 and enable TCP/IP in the Sql Server Configuration Manager to allow VS connecting to SQL. I have all those solutions, but none of them worked for my test project.
If anyone out there have an answer, please help.
Many thanks!
Further technical details
Target Framework: .NET Framework 4.5
Operating system:
IDE: (e.g. Visual Studio 2017 15.4)

Is the sql server local?
Have you tried to put in the server name into SSMS to validate the information?

@BIngZL1983 This is the github repo for EF Core. EF6 can be found at https://github.com/aspnet/EntityFramework6
That being said, this error is not coming from EF; it is coming from the ADO.NET provider for SQL Server--otherwise known as SQLClient. It might be worth removing EF from the picture and attempting to create and open a SqlConnection object directly. If this works, but connecting from EF doesn't, then EF investigation would be warranted. On the other hand, if this doesn't work, then there is something outside of the scope of EF the is preventing the connection to SQL Server.


PageChooserPanel with foreign key linked to specific model: inconsistent behaviour

In the following example, foo is a page chooser field, where the developer has decided to limit the pages choosable to only those of a specific type rather than generic wagtailcore.Page.
class MyPageThingy(Orderable):
    page = ParentalKey('core.MyPage', related_name='thingies')
    foo = models.ForeignKey('core.DifferentPage', related_name='+', null=True, blank=True,)

    panels = [
        PageChooserPanel('foo'),
    ]

I'd expect it to behave the same as the following:
class MyPageThingy(Orderable):
    page = ParentalKey('core.MyPage', related_name='thingies')
    foo = models.ForeignKey('wagtailcore.Page', related_name='+', null=True, blank=True,)

    panels = [
        PageChooserPanel('foo', 'core.DifferentPage'),
    ]

However while in the latter, the popup modal indicates that a restriction is in force, in the former no such indication is made and any page appears to be choosable.
In fact after selecting a "wrong" page then saving the changes, the user is given the comically poor message "Select a valid choice. That choice is not one of the available choices."
Ideally the two versions above should behave the same, at least in terms of how the popup modal works.

Hi @coredumperror - just to let you know I'm now working on a refactor of edit handlers so that they have access to the model class, as this is required by #823. This will allow us to solve this easily, and also to ditch the redundant base_model argument on InlinePanel.

Glad to hear it!

I have tested with latest master and the PageChooserPanel behaves correctly as expected in the first example. However, it seems that the changes break the page chooser -- it now displays as dropdown rather that the usual "Choose a page" button and modal. c542494 is a working commit. Consequent commits show the button (does nothing) and the dropdown. Latest master does away with the button alltogether.
Worth moving to a separate issue as the gist of this one has been fixed with #960.
Will look more into this tomorrow.

@zerolab Is this still failing for you on master? I've just tried various permutations of PageChooserPanel on wagtaildemo, and they're all rendering as expected (bearing in mind that the change proposed in this ticket has not yet been implemented):

PageChooserPanel('link_page') where link_page is a foreign key to wagtailcore.Page (shows the chooser and allows choosing any page)
PageChooserPanel('link_page', 'demo.eventpage') where link_page is still a foreign key to wagtailcore.Page (shows a chooser that only allows selecting pages of type "Event Page")
PageChooserPanel('link_page', 'demo.EventPage') where link_page is still a foreign key to wagtailcore.Page (just in case capitalisation is significant - same as above)
PageChooserPanel('link_page') where link_page is a foreign key to demo.EventPage (shows the chooser and allows choosing any page, aka the current broken behaviour)

@gasman just saw the notification on this. With the master from yesterday, I also get the expected behavior, as reported initially.
However I still only get a dropdown rather than the actual page choose modal. I suspect this may be a red herring, will try with a fresh install later.

Is there a documentation update needed here? I'm now slightly unclear which of the two examples in the opening comments are correct/best.

The latter version is better, because if 'foo' is meant to point to an instance of core.DifferentPage specifically, it's better for that to be defined at the model/database level rather than just in the user interface. It's an extra level of validation to ensure that non-DifferentPage objects don't creep in, and it ensures that if you access my_page_thingy.foo in a template, you'll get an instance of core.DifferentPage back and not have to call specific on it.
There's no immediate urgency to migrate existing working code to the new scheme, though.


blz.one

Blazed One - General Integration platform for the Blazed One Solution.
Requirements:

Use Firebase (Firestore) to store and access all offered services, products, contacts, companies, and projects.
Allow users to release Applications (Desktop or Mobile), Games (Browser or Desktop), and Development Libraries (Any Language). Show "Popular Releases" on user's profile. Allow browsing of all releases in a user's Repository.
Allow users to publish Documents. Show Three (3) documents on user's profile. Allow browsing of all published documents in user's Repository.
Allow user to tweak profile style and various options on their account in the user's settings. Allow user to change billing information and account information as well.
Allow user to access their Drive (consisting of publicly released assets - called their "Repository" - and even private assets. Limit the size of this Drive, and offer tiers to increase the limit.
Allow users to access a Terminal, wherein they may pass commands which activate various functionality across leased services (blazed.systems & blazed.tel).

Daily Mission - 5/12

blz.one

[ ] Integrate Firebase
[ ] Integrate Stripe
[ ] Integrate Google Drive
[ ] Create CLI Terminal


Landuse labels layer

Add a layer for simple landuse labels, using the same landuse queries but returning centroids instead of complete polygons.

There's been some updates on master since this branch was created, specifically for the transform functions. Want to rebase onto master? Or is it easier for you if I merge master in and make the relevant changes on this branch?

sorry about that, merged...

Looks good, thanks! :zap:


Clean docker-compose up fails on ubuntu

Problem description
The stack fails to initialize properly,
Extra information
Stack configuration
No additional configuration has been done.
Docker setup
Client: Docker Engine - Community
Version:           20.10.8
API version:       1.41
Go version:        go1.16.6
Git commit:        3967b7d
Built:             Fri Jul 30 19:54:27 2021
OS/Arch:           linux/amd64
Context:           default
Experimental:      true
Server: Docker Engine - Community
Engine:
Version:          20.10.8
API version:      1.41 (minimum version 1.12)
Go version:       go1.16.6
Git commit:       75249d8
Built:            Fri Jul 30 19:52:33 2021
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.4.9
GitCommit:        e25210fe30a0a703442421b0f60afac609f950a3
runc:
Version:          1.0.1
GitCommit:        v1.0.1-0-g4144b63
docker-init:
Version:          0.19.0
GitCommit:        de40ad0
$ docker-compose version

docker-compose version 1.27.4, build 40524192
docker-py version: 4.3.1
CPython version: 3.7.7
OpenSSL version: OpenSSL 1.1.0l  10 Sep 2019

Container logs

$ docker-compose logs

Attaching to docker-elk_setup_1
setup_1          | -------- Wed Apr 20 13:09:36 UTC 2022 --------
setup_1          | [+] Waiting for availability of Elasticsearch
setup_1          |    ⠿ Elasticsearch is running
setup_1          | [+] Role 'logstash_writer'
setup_1          |    ⠿ Creating/updating
docker-elk_setup_1 exited with code 28

lasticsearch_1  | {"@timestamp":"2022-04-20T13:10:36.229Z", "log.level":"ERROR", "message":"failed to put role [logstash_writer]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[c4a91192be69][generic][T#2]","log.logger":"org.elasticsearch.xpack.security.authz.store.NativeRolesStore","elasticsearch.cluster.uuid":"DFr1zpL3ReGXQp2W2X9zVA","elasticsearch.node.id":"72t2K_k1QFKRXt4NfSbScw","elasticsearch.node.name":"c4a91192be69","elasticsearch.cluster.name":"docker-cluster","error.type":"org.elasticsearch.action.UnavailableShardsException","error.message":"[.security-7][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[.security-7][0]] containing [index {[.security][role-logstash_writer], source[{\"cluster\":[\"manage_index_templates\",\"monitor\",\"manage_ilm\"],\"indices\":[{\"names\":[\"logs-generic-default\",\"logstash-*\",\"ecs-logstash-*\"],\"privileges\":[\"write\",\"create\",\"create_index\",\"manage\",\"manage_ilm\"],\"allow_restricted_indices\":false},{\"names\":[\"logstash\",\"ecs-logstash\"],\"privileges\":[\"write\",\"manage\"],\"allow_restricted_indices\":false}],\"applications\":[],\"run_as\":[],\"metadata\":{},\"type\":\"role\"}]}] and a refresh]","error.stack_trace":"org.elasticsearch.action.UnavailableShardsException: [.security-7][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[.security-7][0]] containing [index {[.security][role-logstash_writer], source[{\"cluster\":[\"manage_index_templates\",\"monitor\",\"manage_ilm\"],\"indices\":[{\"names\":[\"logs-generic-default\",\"logstash-*\",\"ecs-logstash-*\"],\"privileges\":[\"write\",\"create\",\"create_index\",\"manage\",\"manage_ilm\"],\"allow_restricted_indices\":false},{\"names\":[\"logstash\",\"ecs-logstash\"],\"privileges\":[\"write\",\"manage\"],\"allow_restricted_indices\":false}],\"applications\":[],\"run_as\":[],\"metadata\":{},\"type\":\"role\"}]}] and a refresh]\n\tat org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase.retryBecauseUnavailable(TransportReplicationAction.java:1076)\n\tat org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase.doRun(TransportReplicationAction.java:872)\n\tat org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26)\n\tat org.elasticsearch.action.support.replication.TransportReplicationAction$ReroutePhase$2.onTimeout(TransportReplicationAction.java:1031)\n\tat org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:345)\n\tat org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:263)\n\tat org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:651)\n\tat org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:717)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)\n\tat java.base/java.lang.Thread.run(Thread.java:833)\n"}

@BartlomiejLewandowski thanks for the detailed issue report 🙌
It seems like there was a timing issue during the setup phase. Exit code 28 indicates that a client timeout occurred.
For some reason, the setup container didn't get an answer from Elasticsearch for 15 seconds and gave up without retrying. This is unexpected, we should definitely retry timeout errors.
Meanwhile, could you please verify whether retrying the setup with docker-compose up setup fixes the issue?

OK, so the fact that setup doesn't retry on timeouts isn't the real issue here. If you retried manually and it's still failing, an automatic retry wouldn't solve your specific problem. (I'm not saying we shouldn't retry)
If Elasticsearch stops responding, or takes a very long time to respond, it means the Elasticsearch instance itself is facing some issues.
If I look at the error log, I see mentions of "UnavailableShardsException" and "primary shard is not active":
org.elasticsearch.action.UnavailableShardsException: [.security-7][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[.security-7][0]] containing [index {[.security][role-logstash_writer], source[{"cluster":["manage_index_templates","monitor","manage_ilm"],"indices":[{"names":["logs-generic-default","logstash-*","ecs-logstash-*"],"privileges":["write","create","create_index","manage","manage_ilm"],"allow_restricted_indices":false},{"names":["logstash","ecs-logstash"],"privileges":["write","manage"],"allow_restricted_indices":false}],"applications":[],"run_as":[],"metadata":{},"type":"role"}]}] and a refresh]
        at org.elasticsearch.action.support.replication.TransportReplicationAction.retryBecauseUnavailable(TransportReplicationAction.java:1076)
        at org.elasticsearch.action.support.replication.TransportReplicationAction.doRun(TransportReplicationAction.java:872)
        at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26)
        at org.elasticsearch.action.support.replication.TransportReplicationAction.onTimeout(TransportReplicationAction.java:1031)
        at org.elasticsearch.cluster.ClusterStateObserver.onTimeout(ClusterStateObserver.java:345)
        at org.elasticsearch.cluster.ClusterStateObserver.onTimeout(ClusterStateObserver.java:263)
        at org.elasticsearch.cluster.service.ClusterApplierService.run(ClusterApplierService.java:651)
        at org.elasticsearch.common.util.concurrent.ThreadContext.run(ThreadContext.java:717)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:833)

Using docker-compose logs elasticsearch, you'll most likely find other errors related to unavailable shards. Those would help finding the root cause of why Elasticsearch isn't healthy.

Closing due to inactivity. Feel free to reopen if the issue is still relevant.


docs: 3442 response cache

Description
Update code to reflect API change.
Move it to examples.
Closes
Fixes #3442

@JacobCoffee Is there a mechanism to test all the scripts in examples, or is this "testing" relying on the linters? make test-examples only checks files in examples/testing.

@JacobCoffee Is there a mechanism to test all the scripts in examples, or is this "testing" relying on the linters? make test-examples only checks files in examples/testing.

You can do pytest tests/examples. If you want to add tests for those, that would also be the place to do this.


Max width support?

I'm not seeing anything in the documentation about maximum width support, that wouldn't by chance be included would it?

Ah the wrapper, yes that might do the job. Thank you very much!


Program crashes when network connection error occurs

Describe the bug
The log is as follows:
SpeechRecognitionWithMicrophone CANCELED(result): ErrorCode = 5
SpeechRecognitionWithMicrophone CANCELED(result): ErrorDetails = Connection failed (no connection to the remote host). Internal error: 1. Error details: 2485. Please check network connection, firewall setting, and the region name used to create speech factory. SessionId: df7360e0e69d4b4db7755294c587d727

I don't know what "Error details:2485" means.
I want to know if there is a problem with my network configuration.
Expected behavior
A Error returned without crash.
Version of the Cognitive Services Speech SDK
SpeechSDK-Linux-1.7.0
Platform, Operating System, and Programming Language

OS: Ubuntu16.0.4
Hardware - x64
Programming language:  C++

Hi, please upload the full SDK log and we will have a look. See https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/how-to-use-logging for instructions for how to enable logging.

Log file ：speechReco.log

Thank you for the log. It seems that there is an error while trying to download a Certificate Revocation List, thus SSL handshake fails. Are you able to access file http://mscrl.microsoft.com/pki/mscorp/crl/Microsoft IT TLS CA 4.crl manually e.g. in browser, just to check that the address is not somehow blocked?
(915): 153579ms SPX_TRACE_ERROR: AZ_LOG_ERROR:  tlsio_openssl.c:1001 Error loading CRL from http://mscrl.microsoft.com/pki/mscorp/crl/Microsoft IT TLS CA 4.crl
(915): 153579ms SPX_TRACE_ERROR:  trace_message.cpp:189 Error: File:/home/vsts/work/1/s/external/azure-c-shared-utility/adapters/tlsio_openssl.c Func:load_cert_crl_http Line:1001
(915): 153579ms SPX_TRACE_ERROR: AZ_LOG_ERROR:  tlsio_openssl.c:1612 Unable to retrieve CRL, CRL check will fail.
(915): 153579ms SPX_TRACE_ERROR:  trace_message.cpp:189 Error: File:/home/vsts/work/1/s/external/azure-c-shared-utility/adapters/tlsio_openssl.c Func:crls_http_cb Line:1612
(915): 153579ms SPX_TRACE_ERROR: AZ_LOG_ERROR:  tlsio_openssl.c:681 SSL handshake failed: 5
(915): 153579ms SPX_TRACE_ERROR:  trace_message.cpp:189 Error: File:/home/vsts/work/1/s/external/azure-c-shared-utility/adapters/tlsio_openssl.c Func:send_handshake_bytes Line:681
(915): 153579ms SPX_TRACE_ERROR: AZ_LOG_ERROR:  tlsio_openssl.c:2376 FORCE-Closing tlsio instance.
(915): 153579ms SPX_TRACE_ERROR:  trace_message.cpp:189 Error: File:/home/vsts/work/1/s/external/azure-c-shared-utility/adapters/tlsio_openssl.c Func:tlsio_openssl_close Line:2376
(915): 153580ms SPX_TRACE_ERROR: AZ_LOG_ERROR:  transport.cpp:364 WS open operation failed with result=1(WS_OPEN_ERROR_UNDERLYING_IO_OPEN_FAILED), code=2485[0x000009b5]
(915): 153580ms SPX_TRACE_ERROR:  trace_message.cpp:189 Error: File:/home/vsts/work/1/s/source/core/usp/transport.cpp Func:OnWSOpened Line:364
(915): 153580ms SPX_TRACE_INFO: AZ_LOG_INFO:  uspimpl.cpp:809 TS:129953, TransportError: connection:0xb40eb0a0, reason=2, code=1 [0x00000001], string=2485

I have tried to access the  URL by browser,but the file couldn't be downloaded. After changing a wifi connection, I reaccessed this URL successfully. And the program didn't crash.
But, I think if my program couldn't download the CRL file, the program should throw a exception instead of exiting.

I have tried to access the URL by browser,but the file couldn't be downloaded. After changing a wifi connection, I reaccessed this URL successfully. And the program didn't crash.
But, I think if my program couldn't download the CRL file, the program should throw a exception or return error code instead of exiting.

Closed the issue as resolved. Please note that upon a failure at trying to open a connection, the SDK returns a result with ResultReason::Canceled (+ details), which the client application can handle gracefully.


Jib doesn't work with build process that aut

Environment: Java/Kotlin + SpringBoot + Docker + Debian (Sorry, not sure exactly what you're looking for here)

Jib version: 2.0.0
Build tool: Gradle 6.1.1
OS: Debian

Description of the issue: Jib doesn't trigger build steps that auto-generate interfaces. Specifically, we're using swagger-codegen to generate interfaces for our API. In our build.gradle we have a task generateApi and then compileSwaggerJava.dependsOn generateApi. When running the Jib build, it complains that none of the .class files for the interfaces exist.
Expected behavior: Jib should detect all parts of the build OR the documentation should more clearly explain how to add dependsOn rules for Jib.
Steps to reproduce:

Create a Gradle task that auto-generates some code, in this case you could probably do something as simple as move some required files outside of the directory and then just cp them in during the build.
Build a container with Jib.
Notice that it hasn't run all of the steps that your Build normally does.

jib-gradle-plugin Configuration:
import io.swagger.codegen.config.CodegenConfigurator
import io.swagger.codegen.DefaultGenerator

buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath('io.swagger:swagger-codegen:2.2.3')
    }
}

plugins {
    id 'java'
    id 'org.jetbrains.kotlin.jvm' version '1.3.30'
    id 'org.springframework.boot' version "2.2.4.RELEASE"
    id 'io.spring.dependency-management' version "1.0.9.RELEASE"
    id 'org.jetbrains.kotlin.plugin.spring' version "1.3.40"
    id 'org.jetbrains.kotlin.kapt' version '1.3.41'
    id 'com.google.cloud.tools.jib' version '2.0.0'
}

jib.to.image = {Our GCR path}

def openApiGeneratedOutputDir = "$buildDir/generated/swagger"

configurations {
    ktlint
    toolsImplementation.extendsFrom implementation
}

sourceSets {
    swagger {
        java {
            srcDir "${openApiGeneratedOutputDir}/src/main/java"
        }
    }
    tools {}
}

version '1.0-SNAPSHOT'

sourceCompatibility = 1.8

repositories {
    google()
    mavenCentral()
}

ext {
    set('springCloudVersion', "Hoxton.SR1")
}

dependencies {
    implementation "com.auth0:java-jwt:3.8.0"
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk8"
    implementation "org.jetbrains.kotlinx:kotlinx-coroutines-core:1.3.2"
    compile group: 'org.springframework.plugin', name: 'spring-plugin-core', version: '1.2.0.RELEASE'
    implementation "org.springframework.boot:spring-boot-starter"
    implementation "org.springframework.boot:spring-boot-starter-web"
    implementation "org.springframework.cloud:spring-cloud-gcp-starter"
    implementation "org.springframework.cloud:spring-cloud-gcp-starter-data-spanner"
    implementation "org.springframework.boot:spring-boot-starter-security"
    implementation "com.fasterxml.jackson.core:jackson-annotations"
    implementation "com.fasterxml.jackson.core:jackson-core"
    implementation "com.fasterxml.jackson.core:jackson-databind"
    implementation "com.fasterxml.jackson.module:jackson-module-kotlin"
    implementation "org.apache.commons:commons-csv:1.7"
    implementation "io.springfox:springfox-swagger2:2.9.2"
    runtime "com.fasterxml.jackson.datatype:jackson-datatype-jdk8"
    runtime "com.fasterxml.jackson.datatype:jackson-datatype-jsr310"
    implementation "io.springfox:springfox-swagger-ui:2.9.2"
    implementation "org.springframework.boot:spring-boot-devtools"
    toolsImplementation 'org.springframework.shell:spring-shell-starter:2.0.1.RELEASE'

    testImplementation "org.springframework.boot:spring-boot-starter-test"
    testImplementation "junit:junit:4.13-beta-3"
    testImplementation "org.mockito:mockito-core:2.25.1"
    testImplementation "com.nhaarman.mockitokotlin2:mockito-kotlin:2.1.0"
    testImplementation 'pl.pragmatists:JUnitParams:1.1.1'
    testImplementation "com.google.cloud:google-cloud-pubsub:1.42.0"

    swaggerImplementation "org.springframework.boot:spring-boot-starter-web"
    swaggerImplementation "io.swagger:swagger-annotations:1.5.22"

    kapt "org.springframework.boot:spring-boot-configuration-processor"
    ktlint "com.pinterest:ktlint:0.33.0"

    // Source Set Build Dependencies
    implementation sourceSets.swagger.output
    toolsImplementation sourceSets.main.output
    testImplementation sourceSets.tools.output
}

dependencyManagement {
    imports {
        mavenBom "org.springframework.cloud:spring-cloud-dependencies:${springCloudVersion}"
    }
}

tasks.withType(org.jetbrains.kotlin.gradle.tasks.KotlinCompile).all {
    kotlinOptions.jvmTarget = "1.8"
}

bootRun {
    systemProperty "spring.profiles.active", System.getProperty("spring.profiles.active")
}

task generateApi {
    def openApiDefinition = "$rootDir/api.yaml"
    inputs.file(openApiDefinition)
    outputs.dir(openApiGeneratedOutputDir)

    doLast {
        def config = new CodegenConfigurator()
        config.setInputSpec(openApiDefinition)
        config.setOutputDir(openApiGeneratedOutputDir)
        config.setLang('spring')
        config.setAdditionalProperties([
                modelPackage: 'com.example.model',
                apiPackage: 'com.example.api',
                dateLibrary: 'java8',
                interfaceOnly: true,
                useTags: true
        ])
        new DefaultGenerator().opts(config.toClientOptInput()).generate()
    }
}
compileSwaggerJava.dependsOn generateApi

clean.doFirst {
    delete(openApiGeneratedOutputDir)
}

@saturnism

Jib will depend on the runtimeClasspath in 2.1.0 (unreleased) onwards. So I think this might work? Can you try it out? Or link to a full project (for which you have the buildfile above) so we can try it out?

@loosebazook added tasks.jib.dependsOn sourceSets.main.runtimeClasspath and it still fails.

Can you provide us with a sample project to inspect this. If it's not in your runtime classpath, then we can't pick it up, but perhaps there's a way to correctly configure it beacuse   implementation sourceSets.swagger.output doesn't seem to be working?

Can you confirm that sourceSets.swagger.output actually contains a value?
My current best guess is that the interactions between sourceSet.swagger and sourceSet.main aren't configured correctly.
It feels like you need to add something like (though I haven't tested this)
sourceSets {
  main {
    runtimeClasspath += sourceSets.swagger.output
  }
}

Can't confirm, but according to the comments above, this is supposed to be fixed 2.1.0. Closing due to inactivity.


Clarification of weighting in cell_methods

Initiated
2022-11-22 by @taylor13 in https://github.com/cf-convention/cf-conventions/issues/414, 1st point referred to in Karl's summary extracted into this issue by @JonathanGregory on 22 Aug 2023
Moderator:
@bnlawrence
Moderator Status Review [last updated: YYYY-MM-DD]
Requirement Summary
Provide metadata about weighting for cell methods
Technical Proposal Summary
Introduce default interpretations on how weighting of means and other statistics should be applied. Existing datasets may have relied on the vagueness of the convention (to this point) in accommodating a different weighting (i.e., no default specification of the weighting).
Benefits:
Those writing and reading CF-compliant data will have clearer guidance and more definitive rules for interpreting the cell_methods.
Associated pull request:
None yet.
Detailed Proposal
After the first two paragraphs of Sect 7.3, @taylor13 suggests inserting a paragraph while not modifying the paragraph immediately following:

The inserted paragraph explains how by default the grid-cell values have been computed from the contributing samples.  This greatly reduces the need to include the so-called "non-standardized information" regarding the cell_methods.
In section the 3rd paragraph of 7.3.1, @taylor13 proposes to define default weighting for 2-d (area) means  and 3-d means, which also apply to other statistics involving sums:

Without this default specification of weighting, data writers would have to provide parenthetical non-standardized information for most of the variables they write.

Copied from https://github.com/cf-convention/cf-conventions/issues/414#issuecomment-1687105193
Dear Karl @taylor13
At the moment, as you say, there is no information in cell_methods about what weighting should be assumed. Weighting is certainly an aspect of the statistical computations which are described by cell_methods, and it makes sense to include it. If we define default interpretations, as you suggest, new data and old data with the same cell_methods would have different interpretations, since the old data has undefined weights, but the new data has defined weights. Although this is not strictly a backwards incompatibility, it is a potential pitfall for data-users of the kind that principle 9 in Sect 1.2 says we should avoid:

Because many datasets remain in use for a long time after production, it is desirable that metadata written according to previous versions of the convention should also be compliant with and have the same interpretation under later versions.

Therefore, rather than defining defaults, I think we should introduce new syntax for indicating the weights explicitly. If no weighting was indicated, it would mean the same as now i.e. undefined. The syntax could be e.g. "name: method weighted_by keyword", or perhaps just by instead of weighted_by, where keyword would be chosen from a new list of possibilities, such as extent for the simple weighting by the size of the cell calculated as the difference between its bounds, unity if all cells have the same weight, or mass for mass-weighting.
Best wishes
Jonathan

Copied from https://github.com/cf-convention/cf-conventions/issues/414#issuecomment-1687132650 by @taylor13
Thanks, Jonathan, for your input on how weighting might be included without violating principle 9.   We would want to consider whether to include it within the parentheses (the way we include "interval:") or whether it would follow directly the "where" directive.  Also, we need to think about what "key words" would be needed and the procedure for expanding the list if need be (e.g., "weighted_by mass" might not be specific enough; might need "weighted_by mass_of_snow", or "weighted_by mass_of_seaice", etc.)
You are right that it is clearly specifying the weights that is highest priority.

Dear Karl
I'm glad you sound comfortable with the suggestion of weighted_by. Actually I'd like to omit the underscore. Since we have within days etc. without underscore, for consistency weighted by would be preferable. It looks more natural too.
My preference is not to put this clause in parentheses. I'd put it as the last clause before the parenthesis (if there is one).
Regarding the definition of possible keywords, I suppose it depends on how many might be needed. If a very small number, they could be defined in sect 7. If a larger but fairly small number, they could be in a new appendix. If a large number, they could be given in a separate document, like the area_type table. The first two require a change to the convention for amendment, the latter is a controlled vocabulary and easier to amend. We have discussed two which do not refer to any quantity except a metric of the cell: extent and unity. I expect we might also want area and volume (for methods that affect both horizontal dimensions together, or all three spatial dimensions together). Four is a fairly small number, I'd say. What others might be needed for CMIP7, do you think?
For mass-weighting, a keyword is not adequate. We should probably indicate what substance's mass is being referred to. It might be obvious that we mean air for a vertical coordinate of air_pressure, but height doesn't mention air. If the height coordinate is negative, the weighting might refer to soil or sea water. To be precise, one possibility would be to use a standard name in the cell_methods e.g. weighted by air_density. For mass-weighting, the standard name must identify a quantity which gives mass (possibly intensive in other dimensions and multiplied by constants) when multiplied by the thickness of the cell in the coordinate concerned, like air_density multiplied by height, which gives kg m-2. For air pressure, mass-weighting is weighted by unity, because the thickness of the cell is in Pa = kg m-1 s-2 = kg m-2 * g.
You made a proposal for area-weighting, that it should be applied by default if area is stated. That changes the meaning of area, which was introduced to indicate a method that applies to both horizontal dimensions without saying what they mean. For an area-weighted mean, for instance, I would instead suggest area: mean weighted by area. That way area: mean alone won't change its meaning, of a mean that applies to an area, with weighting undefined.
Best wishes
Jonathan

I am still trying to wrap my head around these matters. But one thing that strikes me with these additions is that the content of the cell_methods attribute is more and more turning into a formal language that not only is understandable by humans, but also can (and will) be parsed by software. Hence , I think that  omitting the underscore, as @JonathanGregory suggests is less helpful

... suggestion of weighted_by. Actually I'd like to omit the underscore. Since we have within days etc. without underscore, for consistency weighted by would be preferable. It looks more natural too.

In the construction weighted_by X,  "weighted_by" is a set phrase that is followed by a word X from a controlled vocabulary. This is indeed similar to within days, where "within" plays the same rolw as "weighted_by" and "days" plays same role of "X" (currently: X∈ {days,months,years}). If the underscore is dropped, this correspondence is lost and, essentially, there will be an independent "by" that can be understood only when/if directly related to the preceding word "weighted". Moreover, CF has since the beginning used the space as a delimiter between different entities, in which the underscore is used to indicate a space in the natural language equivalent representation of such entities. Hence, I suggest that the underscore is used, i.e. weighted_by.

Dear @larsbarring et al.
Perhaps it would be better and simpler not to make the syntax look so much like English. Instead of weighted_by we could just have weight or by e.g. height: mean by air_density. I wonder what you think, Karl @taylor13?
Cheers
Jonathan

Hello,
It might be useful to refer to https://github.com/cf-convention/discuss/issues/173, which discusses, amongst other things, how to represent weights in cell methods, and what the existing defaults are (e.g. currently it is unspecified whether or not area-weighting was applied for area: mean, but area: mean where sea_ice is assumed to be area weighted).
My interpretation of the original text is that area: mean and lat: lon: mean are wholly equivalent, so I don't agree with bestowing them with different defaults for the weights used in the calculation.
I prefer the more explicit weighted_by <standard_name> option. I feel that "by" on its own is somewhat ambiguous. It reminds me of "pi by two", for which the "by" has a different meaning than intended here. With the new keyword, there is no need to change the existing (confusing, to me!) defaults, which means no danger of misinterpreting existing datasets.
Thanks,
David

I agree with @davidhassell on this:

My interpretation of the original text is that area: mean and lat: lon: mean are wholly equivalent, so I don't agree with bestowing them with different defaults for the weights used in the calculation.

I prefer the more explicit weighted_by <standard_name> option.

OK. How about just weight e.g. height: mean weight air_density? Given the discussion previously, I feel it's better to avoid having a keyword with an underscore because it might get forgotten by confusing with within years etc.


Merge to m125: friendly YAML names

@lkillgore Is this going in or can we close it?

Closing.   We have the changes in master.


Migrate post_list_row component to typescript

Fixes https://github.com/mattermost/mattermost-server/issues/15465
JIRA: https://mattermost.atlassian.net/browse/MM-20476

Thanks @sowmiyamuthuraman! Tested and passed. LGTM.


Implement MSAA for 2D

This PR implements MSAA for the 2D/Canvas renderer. (Implements godotengine/godot-proposals#1297) In addition, this might improve the situation for godotengine/godot-proposals#1126.
Detailed changes:

Implement 2D MSAA support for the Canvas renderer, which can be controlled separately from 3D MSAA for maximum flexibility (2X, 4X and 8X are supported, same as for 3D)

implementation should be efficient since we can use automatic resolving without the need of VkCmdResolveImage, which has a negative impact on bandwidth
can be set for each viewport separately
currently not implemented for OpenGL implementation (but should be easy once the OpenGL renderer is done)

Rename project settings, viewport properties and methods from msaa to msaa_2/3d for clarity
Minor code restructuring and comment style fixes

Without MSAA:

MSAA 2x:

MSAA 4x:

MSAA 8x:

Bugsquad edit: This partially addresses https://github.com/godotengine/godot-proposals/issues/4354. This closes https://github.com/godotengine/godot/issues/56233 by adding MSAA sample checks to both 2D and 3D.

Cleaned it up and added the implementation for the OpenGL renderer:

Rebased and added checks for the maximum supported sample count for both 2D and 3D MSAA. This should fix any crashes on Mali when MSAA is above 4x.

The Vulkan side is should be done now, OpenGL still needs some work, but because of #63600 I can't test my changes - so that might take some time. If it's ok, I would prefer to only have the critical parts in the OpenGL implementation fixed and then implement 2D MSAA properly later (e.g. with webgl2 support) when the OpenGL renderer has matured. This PR was already pretty time-consuming and unfortunately I have not much time currently.

Rebased. Regarding the GLES3 part: I just looked at the code and noticed that 3D MSAA is also not yet implemented. I would rather strip the implementation completely from this PR and add both 2D and 3D MSAA together at a later point in time (and properly, so that you can set both independently from each other like in the Vulkan renderer).

Rebased. Regarding the GLES3 part: I just looked at the code and noticed that 3D MSAA is also not yet implemented. I would rather strip the implementation completely from this PR and add both 2D and 3D MSAA together at a later point in time (and properly, so that you can set both independently from each other like in the Vulkan renderer).

Fair enough. I am okay with that if you are planning on adding it back at a later time to avoid this getting too complex.

Ok, I removed the GLES3 implementation (a warning is printed when the user tries to enable it). With that I think this PR is complete :)

Does this work properly with backbuffer or clip effects? I think it would be good to test this before merging.

Yes, this seems to work fine with those (MSAA 8x):
Polygon2D with clip children enabled

Backbuffer-reading post processing shader

@reduz says it's OK so let's merge :+1:

Thanks!

Small note: this doesn't smooth the clipped items themselves, only the parent. Note the zoomed square:

(also seen w/this screenshot is the backbuffer ghosting which is not specific to MSAA, also unwanted color blending)

I wonder if 2D clipping is performed in a shader. If so, would alpha-to-coverage make it able to be antialiased?

@insomniacUNDERSCORElemon Could you open an issue and provide an reproduction project? :)

@insomniacUNDERSCORElemon Could you open an issue and provide an reproduction project? :)

https://github.com/godotengine/godot/issues/66005


Timeout setting not only in the desktop but in Power Query online as well

Article says:

This option is only available in Power Query Desktop.
In reality I can see timeout option in Power Query Online as well.

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

ID: 7f15da4f-8f22-3f68-165c-1bb0c4edc887
Version Independent ID: 29d89981-6694-8b87-d5b6-614b8680cd90
Content: Power Query Azure Synapse Analytics (SQL DW) connector - Power Query
Content Source: powerquery-docs/Connectors/AzureSQLDataWarehouse.md
Service: powerquery
GitHub Login: @bezhan-msft
Microsoft Alias: bezhan

Hi @ed7257
Thanks for the feedback! The article has been updated and the "option is only available in Power Query Desktop" has been removed from the timeout option.


[SPARK-39627][SQL][FOLLOWUP] Cleanup deprecated api usage related to JdbcDialect.compileAggregate

What changes were proposed in this pull request?

This PR aims to cleanup deprecated api usage related to JdbcDialect.compileAggregate, and unified to JdbcDialect.compileExpression
The only one left call is in JDBCScanBuilder.pushAggregation.
Why are the changes needed?

Cleanup deprecated api.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Pass GA.
Was this patch authored or co-authored using generative AI tooling?

No.

cc @gengliangwang

Merged to master.

hmm... We should not use SPARK-39627 as it belongs to the Spark 3.4.0 cycle, not the Spark 4.0 cycle.

hmm... We should not use SPARK-39627 as it belongs to the Spark 3.4.0 cycle, not the Spark 4.0 cycle.

OK, let me open a new issue.

I manually resolved https://issues.apache.org/jira/browse/SPARK-48732, but the commit message can no longer be changed.


adjust the font size on CTA buttons for small screens.

The font size for the CTA could use similar breakpoints for the h1, h2. and set to 1.2 - 1.3 rem

I'd like to work on this.

can i?

Where is this button?


Support Landscape Mode

At the moment landscape mode is deactivated.
Activate landcape mode for app and make design more responsive if necesary.
If there is a need to restructure layout of a activity in landscape mode use create new layout in landscape: http://stackoverflow.com/questions/28815769/android-studio-creating-landscape-layouts
Activating landscape mode could solve bug #69 and problems in #70

do this issue with #90


Add GitHub Actions CI

This adds rudimentary CI support to the project, with the help of haskell-ci.  Right now, it covers GHC 8.6.5, 8.8.4, and 8.10.4.  These are triggered on pull requests and pushes.
There is also a commit containing a cabal format, because the CI did not like certain decisions that were made (haskell/cabal#7018).  Besides, using an autoformatter for this kind of thing seems sensible (to me).
A future direction we could take this in would be to

compile the CI with -Werror,
automatically install and run hlint.

Both of these, however, first require us to clean up the current warnings (which is certainly doable, though beyond the imagined scope of this PR).

Oh boy. Sorry, are you aware of https://github.com/haskell/actions/tree/main/setup#readme ? What I see here looks way too overcomplicated.

Oh boy. Sorry, are you aware of https://github.com/haskell/actions/tree/main/setup#readme ? What I see here looks way too overcomplicated.

Clearly, I was not :) I went with haskell-ci because auto-generating this kind of thing seemed like the most robust way of doing things.  Then again, it probably also is the most annoying to debug when something breaks.
We may well just copy what xmonad does with regards to a stack-based solution and call it a day

We may well just copy what xmonad does with regards to a stack-based solution and call it a day

That sounds reasonable, but I would argue for using Haskell setup action instead of manually setting up the ppa. At least that works not only on Linux, but other platforms as well. I can throw together a workflow script and make a PR if you like.
On a related note, do we really need to test with multiple resolvers/GHC versions?

That sounds reasonable, but I would argue for using Haskell setup action instead of manually setting up the ppa.

If we immediately get a CI setup on other platforms due to that then I'm all for it.  If not then I don't really have a strong opinion either way; both seem quite fine to me.

I can throw together a workflow script and make a PR if you like.

Sure, that can supersede this one then.

On a related note, do we really need to test with multiple resolvers/GHC versions?

I do think it's quite sensible to be backwards compatible with a few version of GHC.  This keeps PRs from accidentally introducing e.g. language extensions that are only available in the newest release of GHC, which not all distributions may package yet.

I do think it's quite sensible to be backwards compatible with a few version of GHC

But if we're using stack, it pins and auto-installs the appropriate ghc version anyway. So unless we really want to support multiple stack resolvers for whatever reason, ghc versions are not our concern really.

If we immediately get a CI setup on other platforms

Possibly on Windows. Since macOS needs additional dependencies (kext, dext), I suspect it won't be that easy.

But if we're using stack, it pins and auto-installs the appropriate ghc version anyway (unless specifically instructed not to). So unless we really want to support multiple stack resolvers for whatever reason, ghc versions are not our concern really.

I know of many people who like to use the GHC version that their system provides, opting to set system-ghc: true in their stack config file and then adjusting the resolver when necessary.  I think it makes sense for us to try and support multiple resolvers for that reason; it's a small price to pay for something that could add a lot of convenience for users

This is how Carp does -- https://github.com/MuhammedZakir/Carp/blob/master/.github/workflows/carp.yml. We only need to change/remove the testing commands to use it.

I know of many people who like to use the GHC version that their system provides

Eh... I won't really argue this point, but just my 2¢. In my admittedly limited experience, most people familiar with Haskell on Linux use ghcup, and macOS users tend to use homebrew. Both are pretty good at providing recent GHC releases. And on Windows, chocolatey, scoop, or indeed stack is usually used to manage GHC versions -- the former two tend to provide the latest available by default.
People not familiar with Haskell on the other hand don't generally know enough about stack's idiosyncrasies to coerce it to use system GHC and not blow up.
Supporting multiple stack resolvers/GHC versions does come with a pretty heavy cost, by the way, due to API changing over time, both for GHC and dependencies. You get warnings/errors on certain resolvers that when fixed break things on other resolvers, so the code eventually becomes a horrible CPP mess. The cost is justifiable for libraries, but I don't think the same reasoning can be applied to binaries. I tried with pandoc-crossref and at some point had to give up. Won't stop you from trying, though.

On Sat, Aug 21 2021 09:23, Nikolay Yakimov wrote:

Eh... I won't really argue this point, but just my 2¢. In my
admittedly limited experience, most people familiar with Haskell on
Linux use ghcup, and macOS users tend to use homebrew. Both are pretty
good at providing recent GHC releases. And on Windows, chocolatey,
scoop, or indeed stack is usually used to manage GHC versions -- the
former two tend to provide the latest available by default.
People not familiar with Haskell on the other hand don't generally
know enough about stack's idiosyncrasies to coerce it to use system
GHC and not blow up.

Just to give a specific example; the situation when using musl libc on a
distro that's not Alpine is still somewhat... spotty.  The easiest
solution (at least that I know) is to simply use the system ghc and
override the resolver when necessary.

Supporting multiple stack resolvers/GHC versions does come with a
pretty heavy cost, by the way, due to API changing over time, both for
GHC and dependencies. You get warnings/errors on certain resolvers
that when fixed break things on other resolvers, so the code
eventually becomes a horrible CPP mess. The cost is justifiable for
libraries, but I don't think the same reasoning can be applied to
binaries. I tried with pandoc-crossref and at some point had to give
up.

In xmonad we (so far) manage quite well with just disabling certain
warnings in the cabal file 1.  I agree that sprinkling CPP throughout
the code would be a step backwards and at that point it's probably not
worth it anymore to support multiple GHC versions.  However, I'd say
we'll cross that bridge when we get to it.

Won't stop you from trying, though.

I'm fully prepared to eat my own words here, but I at least want to give
this a try before giving up :)

Closed via #345


MinGW: help ./configure find shared libraries for dynamic loading

This bug report was migrated from our old Bugzilla tracker.
These attachments are available in the static archive:

MinGW: help ./configure find shared libraries for dynamic loading (SDL2_mixer-2.0.1-find_lib.mingw.patch, text/plain, 2017-11-10 12:33:20 +0000, 4390 bytes)

Reported in version: 2.0.2
Reported for operating system, platform: Linux, x86_64
Comments on the original bug report:
On 2017-11-10 12:33:20 +0000, Fabian Greffrath wrote:

Created attachment 3078
MinGW: help ./configure find shared libraries for dynamic loading
We apply the attached patch to the mingw-w64-SDL2_mixer package in MSYS2:
https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-SDL2_mixer
When using the 64-bit variant of the MinGW compiler, the configure script fails to find any of the installed shared libraries for dynamic linking. The patch fixes this issue by replacing the "--mingw32*" search pattern with "--mingw*".
Then, some libraries are installed with a "lib" prefix while others are not. I have extended the problematic cases with both alternatives.
Last but not least, libraries might have been installed into any of the directories accessible via the PATH environment variable, so we search in these paths as well.
Best regards,

Fabian

@icculus, @slouken: I intend to replace all host checks of the like mingw32* with mingw*
in all of the SDL projects,. Any objections?

@icculus, @slouken: I intend to replace all host checks of the like mingw32* with mingw*
in all of the SDL projects,. Any objections?

Replaced all host checks of the like mingw32* with mingw* in all of the SDL projects.
Looking at the rest of the issues now.

Applied improve fluidsynth and tremor dll detection for windows

Re: PATH environment:
I don't think it would be a good idea adding this to find_lib.  @slouken?
Can we close this?

Closing.


remove deprecated /api from ollama base url

Pull Request Checklist

[x] Description: Briefly describe the changes in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[x] Documentation: Have you updated relevant documentation? (n/a)
[x] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation? (n/a)

Description
remove deprecated /api from ollama base url

LGTM, Thanks!


Remote Tech Compatibility and Bug Fixes.

changes.txt

Check changes.txt for summary.

Merged into dev branch. It all looks fine, but I haven't had a chance to test yet (plus want to add a few features of my own, and I have a horrible tendency to break things badly :P )


Refactor identity store level API

Merged in a different pull after conflit resolving.
https://github.com/wso2/carbon-security/pull/167


Possible to config custom get_trigger_characters for each source?

I have the fuzzy_path source which has trigger characters as ., /, ~. I only want it is triggered on /, I tried to config with completion = { get_trigger_characters: ... }, but that is for all completion sources and will be overwritten by each source. Is there a way to do it for each complete source?

Yes. Currently, nvim-cmp does not suppor this.
PR welcome :)

I think I found a workaround. I overwrite the function before calling cmp.setup
local cmp_path = require 'cmp_path'

cmp_path.get_trigger_characters = function()
  return { '/' }
end

😅

I've added the cmp.setup { sources = { { name = " ... ", trigger_characters = { '.' } } } }

awesome. thanks very much.


cannot build

I cloned the project on my mac book, but it does not build.
10:16:12-uwoesle~/workspace/iglu/2-repositories/scala-repo-server(master)$ sbt assembly
[info] Loading project definition from /Users/uwoesle/workspace/iglu/2-repositories/scala-repo-server/project
[info] Set current project to iglu-server (in build file:/Users/uwoesle/workspace/iglu/2-repositories/scala-repo-server/)
[info] Compiling 19 Scala sources to /Users/uwoesle/workspace/iglu/2-repositories/scala-repo-server/target/scala-2.10/classes...
[info] 'compiler-interface' not yet compiled for Scala 2.10.1. Compiling...
error: error while loading CharSequence, class file '/Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/jre/lib/rt.jar(java/lang/CharSequence.class)' is broken
(class java.lang.RuntimeException/bad constant pool tag 18 at byte 10)
error: error while loading Comparator, class file '/Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/jre/lib/rt.jar(java/util/Comparator.class)' is broken
(class java.lang.RuntimeException/bad constant pool tag 18 at byte 20)
error: error while loading AnnotatedElement, class file '/Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/jre/lib/rt.jar(java/lang/reflect/AnnotatedElement.class)' is broken
(class java.lang.RuntimeException/bad constant pool tag 18 at byte 76)
error: error while loading Arrays, class file '/Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/jre/lib/rt.jar(java/util/Arrays.class)' is broken
(class java.lang.RuntimeException/bad constant pool tag 18 at byte 765)
/var/folders/pk/3rj1jqvj5dlgml9p6q4nx5zrt8g246/T/sbt_8db2725a/xsbt/ExtractAPI.scala:479: error: java.util.Comparator does not take type parameters
  private[this] val sortClasses = new Comparator[Symbol] {
                                      ^

10:15:30-uwoesle~/workspace/iglu/2-repositories/scala-repo-server(master)$ sbt version
[info] Loading project definition from /Users/uwoesle/workspace/iglu/2-repositories/scala-repo-server/project
[info] Set current project to iglu-server (in build file:/Users/uwoesle/workspace/iglu/2-repositories/scala-repo-server/)
[info] 0.2.0
10:15:40-uwoesle~/workspace/iglu/2-repositories/scala-repo-server(master)$ java -version
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

Hey @estezz,
This is because Scala <2.10.4 is incompatible with Java 8. To solve this you need update scalaVersion to 2.10.6. But this also may not work - we highly recommend you to use our Vagrant setup - it should have all required components at their appropriate versions.
Also, please post questions on our Discourse, Github issues for bugs only.


refactor(ast_tools): add CI filter file to outputs

Generate CI filter file as a RawOutput, same as the rest, rather than specific code to write it to a file.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#6947
#6946  👈
#6945
#6944
#6943
#6942
#6941
#6940
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite

Merge activity

Oct 27, 10:32 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.