mathematics in reflection operator

Hi there, thanks for making your code public! I have been translating it to TensorFlow as an exercise and have therefore been reading it quite carefully.
I'm a little confused by some of the mathematics in the reflection function times_reflection (https://github.com/amarshah/complex_RNN/blob/master/models.py#L49). Basically, I'm either making a mistake in my own calculations, I didn't understand something, or the code is not quite right. So, apologies in advance for how long this is, I'm trying to be comprehensive.
As I understand it, this function is applying the typical reflection operator in a complex vector v, e.g. on an input vector h:

At the end of the above-mentioned function, there is:
output = T.inc_subtensor(output[:, :n_hidden], - 2. / vstarv * (a + b))
output = T.inc_subtensor(output[:, n_hidden:], - 2. / vstarv * (d - c))

(where vstarv is the squared norm of v)
So I conclude that

(let's call this equation 1)
Doing a bit of expanding: (sorry for ugly LaTeX)

Simplifying the appearance of this expression by rewriting the inner product terms (removing the dot and the vector symbol) to remind us these are just real scalars at this point, and gathering real and imaginary components:

So now we have:

(let's call this equation 2)
Looking back at the code, we have
a = T.outer(input_re_reflect_re - input_im_reflect_im, reflect_re)
b = T.outer(input_re_reflect_im + input_im_reflect_re, reflect_im)
c = T.outer(input_re_reflect_re - input_im_reflect_im, reflect_im)
d = T.outer(input_re_reflect_im + input_im_reflect_re, reflect_re)

LaTeXing these up for easier comparison (the outer, I think, should just be accounting for the fact that the first dimension of these input_... variables is the batch size, so this is all batched, which shouldn't matter for these calculations), and remembering that input is h and reflect is v in my notation:

Putting it together to get expressions for a+b and d-c...

According to equation 1 the right hand side here should equal the right hand side of equation 2, but... it doesn't seem to. What is going on? Some of the signs are wrong. Did I make a mistake?
I thought that perhaps the operator in question is not the typical reflection operator, but is in fact

(the dagger there denoting the conjugate transpose)
... but this also seems not to reproduce the expressions in the code [proof left to the reader]. I might also have made an error checking that, but my question would then be: if that is the intended operator, why conjugate transpose? Where does this operator come from?

A unitary matrix is defined as a matrix that has UU* = U*U = I with * the conjugate transpose. If you take the transpose instead of the conjugate transpose in your vector the transformation is not unitary.
Reflection by a complex vector uses therefore the dagger operator (or the conjugate transpose if you want to call it like that). Are you positive the code isn't doing that? I'll check the math in detail later.

Thanks for the quick response. I see, of course the operator should be unitary! Does one still have the geometric interpretation of a rotation in this case, though?
Regarding the maths: to get the expression for the unitary version, it should (I think!) be sufficient to just change the sign of the imaginary part of the reflection (v_im) whenever it appeared in a dot product. Assuming the rest of the algebra is correct, this should result in: (compare with equation 2)

... which still doesn't reproduce the expressions for d-c and a+b! What am I missing here?

I figured it out btw, your code is actually implementing the operator

... which is also unitary, and just a reflection in the conjugate of v, so it's all good.


Where translation

Adds functionality to allow searching for translated values in fields.
The primary use case I had was for this functionality was for finding translated content via slugs. However it could be used for any kind of search for value.
The two primary uses are a static call & QueryScope
$class::whereTranslation($args)
or
$class->whereTranslation($args)
The result is a query builder instance.
Example useage
class PageController extends Controller
{
    ...

    /**
     * Display the specified page or 404.
     *
     * @param string $slug
     * @return \Illuminate\Http\Response
     */
    public function show($slug)
    {
        $page = Page::whereTranslation( $this->locales, 'slug', $slug );
        abort_unless($page, 404);
        $page = $page->withTranslations($this->locales)->active()->first();
        return $this->RenderView($this->_pageData($page);
    }

Closes #3675

Sorry for being late. A few more things:
I think the locales-array should not be necessary, so if no locales are given, all are searched.
That would require to put $locales somewhere behind $value
Next, I think $default should be true by default.
So, in the end, something like
whereTranslation($field, $operator, $value = null, $locales = null, $default = true)

Sorry for being late. A few more things:
I think the locales-array should not be necessary, so if no locales are given, all are searched.
That would require to put $locales somewhere behind $value
Next, I think $default should be true by default.
So, in the end, something like
whereTranslation($field, $operator, $value = null, $locales = null, $default = true)
And for looping through the locales, you could simply use whereIn I think.

All sound like good ideas. I will look into them. When I have some downtime I will look at updating this.

I commited the stuff I suggested above and added some documentation.
@fletch3555 wanna take a look at the wording?

Good changes/refactor.
Sorry I just really have not had the time (end of the year crunch) to really finish this pr.
One thing that might be noting is in the documentation is that this function does currently override the scope of a query builder due to its static call nature on self. Might be worth putting in.
To fix this line 304 needs to have a check to see if its statically called in a query builder and use self or the query builder instance.

Laravel does all this for you.
Tested both static and normal calls. Also I simplified the default-clause.
Now it looks good in my eyes. What do you think?


Abbreviations improperly changed to City/States

Describe the bug
When processing audio with only a Language Model, If I spoke "LV" or "MD" the abbreviation would be recognized and returned as "LV" and "MD" respectfully.  After creating a speech model with training data containing the LV and MD in the dictations, creating a model with the dataset, and sending the same audio back through with the same Language Model and new Speech Model; The same dictations return "Las Vegas" where I say "LV" and "Maryland" where I say "MD".  I am sure there are more instances of this, but these are the two that I have run in to so far.
I did not put "Las Vegas" or "Maryland" anywhere in the training data.  The Language model stays the same, but the speech model is updated.
To Reproduce
Steps to reproduce the behavior:

Dictate items that contain "LV" or "MD".
Create an audio dataset with dictations containing LV and MD.
Create speech model with that dataset.
Send the same audio through for transcription and where you dictate "LV" it returns "Las Vegas" and where you dictate "MD" it returns "Maryland".

Expected behavior
If I dictate "LV" return "LV"
if I dictate "MD" return "MD"
Platform, Operating System, and Programming Language

OS:Windows
Hardware: x64
Programming language: C#
Browser: Chrome

Additional context
-The datasets and models were created using the API so I am forced to use the 20190523 (v4.14b Unified) base model for the models.

Actually, looking back on it, the base model of the Language model did change.  The original Language model had the 20191007 base model, and the newly trained Language model was using the 20190523 model.  The newer base models clearly perform better after running some tests,  when are we going to be able to use the newer base models with the api?

@nstubing Sorry about the lack of response - is this issue still valid for you or have you been able to use newer base models by now?

@nstubing you should be able to use the latest models now. The latest model is 20191202. The easiest way to train a custom model based on the new model is through the Custom Speech feature of Speech Studio at speech.microsoft.com.
Please let us know what you find when you use the latest model as your baseline model.
I will close this issue for now. If you still have issues on the latest model, please reopen the issue, and we will file a bug in our backlog to dig deeper.

I still am unable to use any newer (newer than 20190523) Base Models while creating Speech Models with the API.  @oscholz  I am also unable to re-open this issue since it was closed by a mod.   I know that the portal is "easier" if you are making datasets/models on a small scale by hand, but I have all dataset creation/deployment and model creation/deployment automated through the api since I needed to build a system to allow hundreds of physicians to complete medical documentation and keep human intervention to a minimum.
I start them on a base model that was created in the portal  with my custom Base Language Model and your Standard AcousticAndLanguage Model (20191007).   Once the Physician dictates and reviews a certain number of recognitions, we automatically make them custom language/acoustic datasets -> language/acoustic models ->endpoint.  The API does allow you to create a Language Model with the 20191202 Base Model, but it does not allow you to create an Acoustic Model with anything more recent than 20190523.
It is really disappointing that if I want to train an Acoustic model through the API I am forced to downgrade the base model to an inferior one.
It is really redundant to create separate language and speech datasets, and subsequent language and acoustic models.  When will the V3 api be out of beta?

@fmegen Can you please comment on the availability of newer Base Models when Speech Models are created with the API?

@fmegen @wolfma61 Please comment on the availability of newer base models in this use case, otherwise we'll presume it's not supported.

@fmegen @wolfma61 One more ping, please comment this week or the item will be closed.

Sorry for the late answer, the issue is occurring during the normalization of the input text before the actual adaptation. LV or MD are indeed ambiguous in term of pronunciation: they could be indeed simply "L V" or "Las Vegas". We recommend when adapting the model with audio files to use "L V" and "M D" instead. This will suppress the ambiguity of the pronunciation.

Closed since there is no more information available. If you have further questions about a specific topic, please open a new issue with details.


style: Syntax highlight.

This PR adds only some syntax highlighting for the README :-)

docker
yaml
shell

Thanks @danriedl, before merge your PR maybe you want to change the author in the commit :smirk:

Could you please sign the commit. Thanks.

Thanks @danriedl, before merge your PR maybe you want to change the author in the commit 😏

Oopsie, thx for the hint I force-pushed with the correct id.

Could you please sign the commit. Thanks.

Have to set that up. Will convert to Draft until ready 😃


Per-guild storage stuff

fixes #5, ref #6

[ ] Configurable prefix
[ ] Enable/disable commands per-guild
[ ] ...

I no longer want this kthxbye


Switch to mamba for CI environment setup

mamba is advertised as conda drop-in replacement with less memory footprint and much faster environment solving.
There's already working Github Action https://github.com/mamba-org/provision-with-micromamba but it needs some tuning before we can move to it - so far we need Windows support and ability to specify Python version.
My hopes are by moving to it we can reduce each step by about 1-2 minutes of setup time (this is not big, but still worth trying IMHO).

cc @amyskov @anmyachev


ES6 constructor erring with object doesn't support this action

the following code is throwing     object doesn't support this action on the this.Key.
it runs fine for about 30 seconds and then starts erring. this error only happens in Edge.
class Value {
constructor(key, data) {
this.Key = key;
this.Data = data;
}
}

@Quethrosar What version of Edge are you using?

25.10586.0.0
13.10586
I am going to attach the script that I have issues with.
jquery.signalR-2.2.0.zip

another hint is if I compile the typescript using ES3 it runs but edge will hit memory in the GB range overnight, where chrome will be 90mb. the memory profiler shows no leaks at only using a few MB.

@Quethrosar is there a glue html code which can be run on the browser to reproduce this problem using the script you attached here? My hunch is this problem is already fixed in later versions of Edge, but would love to validate the problem go away.

Small test case would be awesome

@Quethrosar do you have the corresponding HTML so we could verify whether this issue still exists?

Closing due to lengthy inactivity and incomplete repro.


Don't try and cast match_id unless it exists

Hey @bakert,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: e2d7af40-e967-11e9-93dd-b3a5547eb4f4


Assertion Error in output size

Hi all, thanks for the pytorch implementation!
I am trying to train 3D DeepMedic. My input image size is: torch.Size([1, 3, 144, 144, 64]). I am instantiating the 3D DeepMedic using this (3 channels and 2 classes): model = DeepMedic(3,2) I am getting the following error message:
Traceback (most recent call last):
  File "../gandlf_run", line 92, in <module>
    main()
  File "../gandlf_run", line 87, in main
    TrainingManager(dataframe=data_full, headers = headers, outputDir=model_path, parameters=parameters, device=device)
  File "/gpfs/fs001/cbica/comp_space/bhaleram/GANDLF/GANDLF/training_manager.py", line 110, in TrainingManager
    device=device, parameters=parameters, holdoutDataFromPickle=holdoutData)
  File "/gpfs/fs001/cbica/comp_space/bhaleram/GANDLF/GANDLF/training_loop.py", line 265, in trainingLoop
    output = model(image)
  File "/cbica/home/bhaleram/.conda/envs/dss/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/gpfs/fs001/cbica/comp_space/bhaleram/GANDLF/GANDLF/models/deep_medic.py", line 70, in forward
    output_size = self.get_output_size(input_size)
  File "/gpfs/fs001/cbica/comp_space/bhaleram/GANDLF/GANDLF/models/base.py", line 58, in get_output_size
    assert all(o > 0 for o in output_size)
AssertionError

I am confused what the error is. Is it something to with the dimensions - since I am not passing the dimensions anywhere in the instantiation?
Thanks for your help,
Megh

Hello,
There are two issues:

You seem to have an extra dimension in your image. How did you come to the conclusion that this is the shape of your image? If you are using the our dataloader, one image should have shape [num_channels, z, y, x], yours seems to have an extra dimension.
You need to adjust the input patch size to work for your images. The default patch size in the config is 110x110x110 which is bigger then one of the dimensions in your image. This can be changed in the config.

Hi - sorry for not being clear, I forgot to mention that I am using my own implementation of the training loop and dataloader and using only the DeepMedic Architecture from here.

I am using a custom dataloader. The shape of the tensor passed to the model is in the format [batch_size, num_channels, x, y , z].
Again, sorry for not being clear. The size that I have mentioned earlier is the patch size (the x,y,z part), not the original image size. My patch size is [144,144,64], as mentioned earlier.
Please do let me know what the issue is.
Thanks

If you are just using the model class and nothing else then the issue is:
Because our implementation does not use padding the output patch size is smaller then the input patch size. What is happening is that your patch is too small for the number of convolutions in the network creating a negative output patch size. This assertion prevents that.
You need to have less convolutions in the network or pad your input.

Oh, okay, thanks. I will try using bigger patch size (greater than 110,110,110), and check.

Your patch-size choice implies that you are using images that are not in isotropic resolution, maybe also watch out for that if you want good performance.


Bug: PSM breaks when using keyboard navigation

Steps:

Open PSM
Click on URL field
Keep pressing TAB until it breaks

Yay! I've run into that a few times, but never reproducibly - i always thought it was me being goofy. Nice

Dibs.


Restore /{db}/purge endpoint

Work is ongoing to restore purge functionality in a clustered database: https://github.com/apache/couchdb/commit/5230cf01d847705171ab28d8219dbef1c2d6f2a6
This ticket is to track these PRs landing.
It'd be ideal if these can land in 2.2.0, but if the work is going to take a while, let's push out to 2.2.1 or 2.3.0.
/cc @davisp @jiangphcn

@wohali I’ve been closing issues that have corresponding PRs, feel free to open, if you want a unified place for multiple PRs

Added reference to https://github.com/apache/couchdb/pull/1370


Ssm parameter safe parsing

Summary

This PR adds the fixes to safely handle credentialSpec file creation in Windows when the ECS task definition defines a SSM parameter to be used as dockerSecurityOptions. Currently, the agent has the following issues.

Handling hierarchical paths in SSM parameters - The current version of the code just extracts the leaf path from the hierarchy and writes a file with that name. This can create a problem on a worker node if two containers require access to an SSM parameter a/b/c and x/y/c. The current code would just write the single c file.
Handling long SSM parameter names - SSM parameters in AWS support up to 1011 characters as per the spec. However, Windows only support a max path length of 260 characters and max file length of 255 characters when writing to absolute paths. The current version of the code would encounter an error when the SSM parameter name is long which results in a path longer than 260 characters in windows.

Implementation details

In our implementation, we used the concatenated value of {task_id}{container_name}{ssm_parameter_ARN}  . The addition of the task_id and container_name add ample jitter to avoid collision within a host and a task for a given credentialSpec. We hashed the concatenated string using the SHA-256 algorithm to generate a digest size of 32 characters. This string was used as the name of the credential file created in the directory c:\ProgramData\docker\credentialspecs. Since the digest size is always a fixed length of 32 characters, this mitigates the path length issues in Windows. Also, this does not require us to refactor the deletion of the CredentialSpecs later since all of them are in the root credentialspecs folder.
Testing

Existing tests were refactored and an additional test was added to handle hierarchical SSM paths.

New tests cover the changes:  Yes
Description for the changelog

Bug - Fixed the creation of credentialSpec files in Windows when it is generated via SSM parameters that are hierarchical or the credentialSpec file path length is more than 260 characters.
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Added the changes to safely parse the SSM parameters for windows containers.

Reopening


MCS-276 Fix Transferral Target Stacking Bugs Reported by TA1

Fixes the bug with some objects (including spheres and cylinders) not being placed on top of blocks correctly.
Fixes:

Sort the receptacle trigger boxes so we test the spawn points for the highest boxes first.
Reduce the size of the receptacle trigger boxes for the letter/number blocks to restrict the spawn points that are generated to their center (and match the blank block receptacle trigger boxes).

This may also affect duck scenes, if you're trying to stack the duck on top of a block.

@rartiss55 I think the main issue here was that blocks have 6 receptacle trigger boxes, one on each side, and the algorithm was choosing the front/right/left/back side instead of the top sometimes.  Plates only have 1 receptacle trigger box along their top, so they shouldn't be an issue.


New Yeelight Device - Monitor Hanging Light

This is Yeelight new light product and it can enable "LAN control", I can use your plugin to add it in HomeKit. But look like have something wrong.
Product Model: lamp15
Response Sample: {"power":true,"color_mode":2,"bright":100,"hue":194,"sat":87,"ct":3800,"bg_power":false,"bg_bright":100,"bg_hue":194,"bg_sat":87,"bg_ct":2703,"bg_lmode":1,"nl_br":0,"active_mode":0,"name":""}
This product have 2 lights. In front of light is screen light, color temperature support 2700k - 6500k. another one is backgroundLight, it is a RGB light.
Waiting for your reply.

It automatically grouped the front and back (ambient) lights into one light group for me in the Apple Home app. You can separate this and show as two separate "tiles" if you want.

It automatically grouped the front and back (ambient) lights into one light group for me in the Apple Home app. You can separate this and show as two separate "tiles" if you want.

support added

@cellcortex This device doesn't support moonlight mode, but I found that even if I disable moonlight mode, the brightness value for this device is incorrect.


Can pip install executes package specific code?

What's the problem this feature will solve?
If so, then it may not be safe to install some pip packages in /venv/ as root. As some packages depend on other and the latter can require Makefile compilation, it seems to be the case.
Describe the solution you'd like
Not read.
Alternative Solutions
Not read.
Additional context
Not read.
Code of Conduct

[X] I agree to follow the PSF Code of Conduct.

Related to OverClock3000/issues/3.


Added MAVEN_MIRROR_URL description to env vars in README.md

fixes https://github.com/openshift/jenkins/issues/900

Add docs for MAVEN_MIRROR_URL environment variable usage

cc @gabemontero @akram

/lgtm


Merge 'ThreeMammals:develop' to 'develop'

Let's update the default branch with latest top-commits from head repository.

Guo,
Could you merge this PR please?
Merge option with fast-forwarding should be performed.
Thank you!

Could you Sync fork please? So, new develop branch will occur with all top commits!
Could you add me as collaborator to your forked repo please? I will help you to update develop branch in future.


How to check dot product performance?

hello.
I am a master's student who was impressed by your dissertation.
Looking at your code, I want to check performance via dot product, not performance via L2 similarity.
As a result of implementing it myself, it doesn't match the suggested figure. But can I check the code for the dot product??
thank you

Not sure what you mean exactly. You can change these two lines to convert them to a dot product.
https://github.com/hkchengrex/STCN/blob/c9c627e50a43c239736c298380fda1226c455724/inference_memory_bank.py#L34-L35


new release

I know asking here might not be the best place...
Could You release the current master?
If not now, are there any plans to release soon?

Hi czeras,
since this Chart currently isn't hosted on any Helm repository (see #11) I would argue a 'release' would be obsolete for now  (IMHO, and I am not part of SonarSource).
However, you can always clone this repository and install the chart directly form your clone or package and deploy it to an internally hosted Helm repo and use it that way (have tried and done both).
Hope this helps :wink:

@k3rnelpan1c-dev regarding using this repository with Helm I replied in Your issue: https://github.com/SonarSource/helm-chart-sonarqube/issues/11#issuecomment-854158327.

However, you can always clone this repository and install the chart directly form your clone or package and deploy it to an internally hosted Helm repo and use it that way (have tried and done both).

Cloning/forking is an option but it's counterproductive IMHO since I have to "maintain" by myself. I would prefer (I think this applies to others as well) to use upstream (this repository).
If releasing is not possible I will accept the reality :slightly_smiling_face:

Oh dont get me wrong, I too would take a SonarSource Helm repo over cloning this and maintaining the packaged chart in the local helm repo myself any day!
So I totally agree with you.

Hi @czerasz
master has been released yesterday. including pushing the chart to a helm repo. i will write additional more detailed documentation soon :tm: , but in the mean time you can helm repo add sonarqube https://sonarsource.github.io/helm-chart-sonarqube and use the charts there


Add license 1

Jira issue link: link

check applicable boxes

[ ] I have made tests to match the user stories
[ ] This code does not require tests that match user stories

Coverage remained the same at 75.069% when pulling 3ca812dd842890a9074775e59a67a49dc90ec063 on add-license-1 into 02c62745a9fb3ae0c4e5f8d74b2dfd6da686e1ec on develop.


Convert TcpStream back to std::net::TcpStream

I need this to get my socket2::Socket back safely.

https://github.com/async-rs/async-std/pull/1014


STORM-2882: shade storm-client dependencies

Dependencies for the client in 1.2.1
asm
clojure - removed in 2.x
disruptor - removed by this patch
gmetric4j
kryo
log4j2
log4j1.2-api
metrics-core
metrics-ganglia
metrics-graphite
minlog
objeneses
reflectasm
ring-cors - removed in 2.x
servlet-api-2.5 - removed by this patch
slf4j
storm-core - removed in 2.x
storm-rename-hack - removed in 2.x
The only dependency on the storm client classpath not in 1.2.1 is org.acplt:oncrpc:jar:1.0.7 because it was pulled in by a newer version of io.dropwizard.metrics:metrics-ganglia.

Shading here is different from how it is in 1.x.  For this one there is a separate package that creates a shaded uber jar.  The code inside storm-client and storm-server that need to use it will call the shaded APIs directly.
The upside is that IDEs work grate because they are operating on the shaded APIs and don't have to worry about how shading works.  The downside is that doing a full build is now a 2 step process.  This is because of a "bug" in maven/shade were shading in a multi-module project results in down stream builds not seeing the shaded dependencies.  I cannot really combine them into a single build step because the version of maven with this bug in it is now standard in most places, so our "fix" for 1.x is not really valid any more.

@HeartSaVioR I have addressed the other review comments, but I could not find a place in the documentation for instructions on how to do a release.  I agree that we want to publish the shaded-deps too, or clients will not be able to find their dependencies.  Just not sure where that is documented, or what scripts there are that do it, if any.

I addressed everything except for jaxb.  Because it is for java9 I will download a java9 JDK and work on that to make sure it works there too, so it might be a little longer.

Just so you don't spend too much time on it, neither HBase nor Cassandra work with Java 9 right now. I skipped those modules when testing it last year. Also I didn't get farther than building and running the tests with Java 9, so I can't say whether it works beyond that. At the time I was hoping to be able to upgrade HBase and Cassandra before too long and do more tests after that, but they are still working on Java 9 support.

All I did was build/run the unit tests and this time I was able to get everything to pass.  Oddly I was able to compile all of the code without jaxb-api but I could not run the tests...
I decided not to shade the API because I am not sure where the implementation is, and I would need to shade both.

Thanks for addressing the comments. Looks good to me. I think it makes sense to add shaded-deps as a module to the root pom though. It will likely address the release issue, and means we don't have to manually keep its version number in sync with the rest of Storm. Is there a reason to not have it listed in the root?

@srdo I can add shaded-deps to the root pom, but it is going to potentially mask a lot of build issues, and is going to make IDEs confused.
maven-3.2.6 and above added in a cache for dependencies in the pom.xml.  The shade plugin tries to modify those dependencies on the fly and the maven cache wins.
https://issues.apache.org/jira/browse/MSHADE-206
What this means is that if shaded-deps is a part of the root pom.xml, all of the code built by maven is going to have both the shaded and the non-shaded version on the classpath when it compiles and when unit tests run, but only the shaded version will be on the classpath in production.
Similarly for IDEs that don't understand the shading plugin they will get confused and will likely not see the shaded dependencies so all the code I changed will start to show up as errors, while anyone who uses it will write code against the non-shaded deps, which because of MSHADE-206, will compile under maven, but won't run in production.
In older releases we told everyone to use an older version of maven that is not impacted by this, but that is getting harder and harder to do, especially with recent security disclosures.
If you really want me to I can add it in under a profile that would be on by default, but we could turn off when we do the check-in builds and when being imported into an IDE.

+1
@srdo You asked what the maven release commands were. They are:
mvn release:prepare -P dist
mvn release:perform -P dist

Note that the process modifies the pom files, checks in changes, tags, and pushes to ASF git. So if you want to test the release process you will need to revert those changes.

@revans2 If I'm understanding the problem correctly, the bug is that if shaded-deps is in the same reactor as the other modules, Maven will read the "normal" pom, rather than the dependency reduced pom, and put all the shaded-deps dependencies onto the classpath of the other modules?
Would it work to make all the dependencies declared in shaded-deps optional (i.e. non-transitive)?

Thanks @ptgoetz

@srdo It might work to make them optional.  I am not a maven expert when it comes to that..., or really just about anything with maven beyond setting up a basic build.  I am happy to try it out, as it is a real pain.  I will also try out using a profile to control when/how it is built, so hold off checking any of this in until I have tested them.

@srdo your suggestion to mark the dependencies as optional in the shaded pom was a great one.  I have it working now where shaded-deps is built by default, maven does not include any of the unwanted dependencies on the classpath while building or testing, and when setting up and IDE there is a profile that can be used to disable shaded-deps so the IDE is happy.  What is more IntelliJ has that off by default so if you just import storm it will do the right thing out of the box.
I also updated the travis scripts to explicitly build/install shaded-deps first and then run the rest of the build with shaded-deps off, so it we know nothing is sneaking in there on accident.

Looks great. +1.


Highlight critical signals

Summary of changes
Critical signals and pre-selected attributions are highlighted in the audit and attribution view. If a critical pre-selected attribution is confirmed, it is not highlighted anymore.
Context and reason for change
In input documents, signals can now be marked as critical, if they are specifically important to consider or marked as red flags. To make the review process more effective, these signals are highlighted in OpossumUI.
How can the changes be tested
Open the test input file opossum_input.json and view the signals contained in the root folder or navigate to the attribution view.

The fact that on attribution view critical attributions are displayed the same as incomplete ones confused me and, in my opinion, should not be the case.

I just realised that there is a tooltip. However, the placement is a bit odd. First I did not see it and then I did not realize it belongs to the card:

The fact that on attribution view critical attributions are displayed the same as incomplete ones confused me and, in my opinion, should not be the case.

Yes, I agree. Originally, I chose a different highlighting for that reason, but it was decided in a team meeting to have the same highlighting and possibly fix it later.

I just realised that there is a tooltip. However, the placement is a bit odd. First I did not see it and then I did not realize it belongs to the card:
It would be great to anchor it at the current mouse position or otherwise much closer to the card

Agree. I'll fix the placement.

After some discussion, we decided to change the styling so that it is not the same as for incomplete attributions. Consequently, we also decided to drop the tooltip.


Update topic-experiences-discovery.md

Added a line to expect that suggested topics will not appear instantaneously...not sure if this is the best page to add this.

Moving this note to Set up Microsoft Viva Topics.


xAxis not synchronized

Version
5.2.0
Reproduction link
https://jsfiddle.net/fx56zahp/
Steps to reproduce
Have two yAxis (one for time series data and one for boolean data). They should be synced over the xAxis so that if you hover over the second grid items data you see also the data of the first grid item and vice versa. (see reproduction link)
What is expected?
Axis should be synchronized to always show all data on the specific date.
What is actually happening?
Axis are not synchronized and you have to hover over the each separately.

Sorry for the late reply. Please checkout https://echarts.apache.org/en/api.html#echarts.connectto see if this works for you.

Thanks for the reply. Connecting by groupId did not have any effect in my example.


Support JSON-RPC v0.5

With the imminent release of the JSON-RPC spec v0.6, nodes will remove JSON-RPC v0.4 (they have a policy of keeping the 2 most recent specs). Do you plan to add JSON-RPC 0.5 soon? Can I help with it?

Oh it's actually already done. It's on the branch dev/jsonrpc_0_5_0.

Cool, thank you!


Make WeDeploy button work

The WeDeploy one click button is currently broken. This patch fixes that problem by reconfiguring the repository URL in the button.

Thanks @sau226!


Not receiving Cloudant change feed information when using the Cloudant dashboard

Using the documentation in the README, I have tried to create a trigger associated to the change feed for a Cloudant service and looking at the wsk activation poll.
The change feed does not seems to be active when using the Cloudant dashboard, when I:

Create a database (corresponding to the name of the trigger parameter dbname.)
Creating a document.
Deleting a document.
Changing or cloning a document.

Note that I have successfully received change feed information when (from the terminal)

Invoke read and write actions for the same Cloudant service (ask action invoke ...).

Is this intentional (by design)?

How recent is your checkout if you're using OpenWhisk (and not Bluemix). I fixed a bug related to this a few days ago.

wsk -v package listgives me:
'clibuild': '2016-03-03T09:55:47-06:00'
'apiversion': 'v1'

As additional information:
I downloaded the wsk binary from https://new-console.ng.bluemix.net/openwhisk/cli that points to a file named "openwhisk-0.1.0.tar". This file name hasn't changed since my last install so I guess either this file does not contain the latest version or the name has not changed.

@kolien, this order works for me:

create DB in Cloudant
create trigger on Cloudant changes feed per README.

I don't receive updates if I reverse the order and create the trigger before the DB exists.

Thanks for clearing that up for me. I did not try that. Maybe the readme should be updated with a information that the database has to be created first.

Yes.  Perhaps return an error if the feed cannot be setup successfully.

I did a new test today.

Downloaded openwhisk CLI using pip.
Deleting old trigger.
Created a new trigger towards the same cloudant service that now already contains a testdb database.
Starting activation poll
invoking read/write actions using CLI, receiving change related messages in activation poll as expected
Manually creating docs and changing docs using cloudant dashboard, activation poll now does not reflect these changes (i.e. no updates in the changes logs)

My initial statement that "activation poll does not receive change information via the trigger" is still is valid.
@paulcastro: I cannot get the same result as you. How do you perform your test?

@kolien , I performed the same steps as you and I'm able to get change notifications using the CLI as well as the Cloudant Dashboard.  My current setup follows the "Setting up a Cloudant database outside Bluemix"

@paulcastro, I followed the "Setting up a Cloudant database in Bluemix" recipe.

@kolien , I changed my setup to use the Cloudant database in Bluemix and I'm able to replicate this issue.  I only see changes when the write is issued from the CLI.  I am unable to see changes when I use the Cloudant dashboard.  @rabbah I suppose this is a bug -- perhaps because Bluemix setups have to go thru the Bluemix Cloudant broker?
If you would like to use the Cloudant dashboard, I recommend setting up the Cloudant database outside of Bluemix as a workaround. That works for me.
Thanks for finding this!

This defect was addressed in the above mentioned commit but is not yet deployed to Bluemix. I will post an update when it's available.

This fix was deployed to Bluemix but I forgot to update the issue. I have confirmed the trigger activations now appear in the wsk activation poll.


Look up output index when force closing

that's the address index fix for react-native-ldk. I'm holding onto that until we publish the next release since it will require more internal testing.

LDK should give us the ouput @Jasonvdb / What do you think of?

already merge


add kwargs to kafka event broker

Proposed changes:

Add a **kwargs argument to the Kafka event broker to allow using the config for a Kafka event consumer, which may contain parameters not supported by a Kafka producer, such as in the case of deploying Rasa X with the helm charts

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

@rgstephens @federicotdn pointed out this will allow potential errors in endpoint configs to go unchecked, so it would be better to just add the group_id param back, and give a warning when it is provided to indicate that it doesn't do anything. I'll create a new pr for the changes.


[MISC] Document BEPs that are not active anymore, but have not been merged

I also added a reference to BEP007, which has been merged very early on

rendered version: https://651-150465237-gh.circle-artifacts.com/0/home/circleci/project/site/06-extensions.html#bids-extension-proposals

Thanks for the reviews!


[ST] Txn stuck at bump relayer fees step

Describe the bug
User already bumped the relayer fees but the system seems stuck

https://connextscan.io/tx/0x4d9f593badebf750ffdb9f4c0efe523c139d7b1ecff49249f970f38727d5c72d
bump tx: https://arbiscan.io/tx/0xf12a4a35caedeca9804f0ef820b17197b0227c258e7af76e751815d19b15a045
Link to ticket in discord
https://discord.com/channels/454734546869551114/1219912405761392682
@oncall

I've another similar case, in this opportunity user bumped twice and system is asking for more bumps.

https://connextscan.io/tx/0x7766d0a4d797fadb1685f8d716180dd1b11eee81102d0dbd530a3b25d6e183bf
bump1: https://bscscan.com/tx/0x6a913ef2f0474f79604862dd5a42cfbe8156eb91a18ee509253542e263866752
bump2: https://bscscan.com/tx/0x9170a7630197c1a836c6f1ceea0647a35b05c089b3379c04b80d45cb8628bd26
Link to ticket in discord
https://discord.com/channels/454734546869551114/1220076908545573025

Another case: https://connextscan.io/tx/0x2114dbe145065e78b22758675c30418473d86a740deb81db1d8a5ae78b01bd4b

Ticket 313 on Intercom

all are executed:

https://connextscan.io/tx/0x4d9f593badebf750ffdb9f4c0efe523c139d7b1ecff49249f970f38727d5c72d
https://connextscan.io/tx/0x7766d0a4d797fadb1685f8d716180dd1b11eee81102d0dbd530a3b25d6e183bf
https://connextscan.io/tx/0x2114dbe145065e78b22758675c30418473d86a740deb81db1d8a5ae78b01bd4b

unfortunately, these are subject to a JIT estimation and are really difficult to track down.
@pjenviri do you know how the slippage is updated in the UI? wondering if its consistent with carto.
@Tommy-R8 do you know how long they waited in between?

https://github.com/connext/monorepo/pull/5900


Added in memory chat history

Added ChatMessageHistory , that implements in memory chat history.

@jeastham1993 @CrazyBaran can you please review? Thanks guys


Logo

Not a real issue, just a place where I can store my Photohsop files
Lyo.zip

1

#2

3

4

5

Bonus

The votes are in!
Final graphical identity:


proposal : movable tabs fwith the text editor

From<EMAIL_ADDRESS>on 2010-04-13T06:25:55Z
What is the expected output?
enable the use of movable tabs when different files are open ( is possible in eclipse) What version of the product are you using? On what operating system? 1.1.0beta1
Please provide any additional information below
. add self.setMovable(True) in the init of class BaseTabs(QTabWidget) in tabs.py
Regards,
Dimitri
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=198

From<EMAIL_ADDRESS>on 2011-04-21T08:59:58Z
What is the idea behind editor cloning? Is it so that it is possible to have a separate window containing the editor widget rather than an embedded editor widget? If so, the embedded editor widget could be copied over then destroyed when creating the floating window and vice-versa, in which case tab order can be just copied over.
Is there ever a case where it is essential to have two synchronised editor instances open?

From pierre.raybaut on 2010-04-13T11:26:10Z
Tabs were movable in Spyder v1.0.x.
But since v1.1, a new editor widget was introduced with much more features like
editor cloning.
The new behaviour of the editor widget requires that tabs are not movable because
they are synchronized with the combo box above (you may choose to sort files
according to their full path or to their filenames), and when creating a new editor,
the editor widget is cloned so opened files are organized the same way in each editor
widget.

From pierre.raybaut on 2010-06-09T13:32:56Z
Status: WontFix


v-show not working as expected in IE Browser

Version
2.5.17
Reproduction link
https://jsfiddle.net/crsh7w1f/
Steps to reproduce
Created a div component modal that will show when you browse on IE browser. Used v-show to show the modal and change the value when clicking the icon to close the modal.

          Incompatible Browser

          Works best with Google Chrome and Mozilla Firefox. Please switch to either of these browsers to fully utilize the portal.

          Got it

What is expected?
It will close the modal because of change value in v-show
What is actually happening?
nothing happens even the value is changing to false

The link you provided isn't a runnable reproduction. But a minimal runnable reproduction is required. Thanks. See About Reproductions.


DIOXINs/water - add mapping from TRI

There are DIOXIN AND DIOXIN-LIKE COMPOUNDS to water in TRI 2016. Add a mapping to TRI.

Needed to add new primaryflowcontext and create new flow, then add mapping. Done.


Concurrency tweaks

A couple of fixes:

Use process aliases
don't use nosuspend, because it would not send a message if the dist socket is busy. We use async_dist=true instead. Otherwise we could use nosuspend, BUT with spawn(fun() -> Pid ! Msg end) if ok is not returned.
write_concurrency = true for mon table - not that much difference though.
read_concurrency = true for the data tables.

Github is a bit buggy today, so it does not see new commits and does not trigger CI.

will be split into two PRs


Writing to spatialite causes crs mismatch

It seems that geometries are written to spatialite in their native coordinate reference system (for instance UTM), but in spatialite they are assigned wgs84

Fixed. (As of v0.4.0)  Note: this requires use of the new spiderosm SRS object:
spatial reference system
srs = spiderosm.spatialref.SRS(
        url="http://www.spatialreference.org/ref/epsg/wgs-84-utm-zone-10n/",
        units='meters',
        spatialite_srid=spiderosm.config.settings.get('spatialite_srid'),
        postgis_srid=spiderosm.config.settings.get('postgis_srid')
        )
spiderosm.log.info('srs info:\n%s', srs.info()

...
db = spiderosm.spatialite.Slite(sqlite_fn, srs=srs)
See spiderosm_berkeley.py and README.md for details.


Update MIGRATING.md

Coverage remained the same at 94.819% when pulling e96ebabd42da460153cbd1d30670c27f1fd6a875 on saicheems-patch-1 into c02e9927d480799f8c557425bf7b3a623202bdd7 on master.


Basic Authentication displays Og=='

What happens?
When specifying Basic Authentication as a security schema in an OpenAPI spec, the string Og==' is displayed in the rendered code box and Test Request dialog:

What did you expect to happen?
The string Og==' is a base64-encoding of the colon character :
It should not be rendered but Authorization: Basic should still appear
How can we reproduce the issue?
Include a basicAuth securitySchemes in the openapi spec, for example:
openapi: 3.0.0
info:
  title: HTTPS + Basic auth example
  version: 1.0.0

servers:
  - url: https://httpbin.org

components:
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic
      description: Use `user` / `passwd` as the test credentials

paths:
  /basic-auth/user/passwd:
    get:
      security:
        - basicAuth: []
      responses:
        '200':
          description: OK
        '401':
          description: Unauthorized. The username or password provided is incorrect.

Swagger/OpenAPI Example
https://sandbox.scalar.com/e/snZUC

thanks for reporting this @hbcondo !
we will fix this ✨


Snap 1682

Changes proposed in this pull request
A thread receives a put message, it takes a Connection in the TCPConduit and then it tries to take the lock BucketRegion.lockPrimaryStateReadLock(BucketRegion.java:1237) and waits as this is already acquired.
Another thread receives a PutMessage it takes a lock in BucketRegion.lockPrimaryStateReadLock and then tries to distribute the update to the  secondary. For that it tries to get a connection and gets stuck as no connection are available.
This is a cyclic dependency between two threads. There are more than 200 threads of the first type which indicates why the connections are not available for the threads of the second type.
The cyclic dependency needs to be fixed but for 0.9, we are moving ahead by increasing the number of connections that can be created between two servers.
Patch testing
Ran the test on local. Running precheckin

threads don't return connections back to the pool
Yes this is what I suspected and discussed the same with Hemant. To confirm we also went through the logs for exceptions but did not find anything suspicious.


Synchronize APIs

Standardize API design so either they all take params prefixed with a colon or none of them do.

Requires the colon prefix:

Expression names
Special values (such as :true, :null, etc.)

Omits the colon prefix:

Column names

Colon prefix is optional (but preferred):

Operator names


Add function to retrieve wordnet synonyms

Users struggle to find the synonyms of a word (#2976) because the wordnet.py module still does not provide a convenient way to retrieve synonyms, although it claims to:
"Using synsets, helps find conceptual relationships between words such as hypernyms, hyponyms, synonyms, antonyms etc." (sic).
To remedy this deficiency, the present PR adds a function that returns a nested list with the synonyms of the different senses of a word in the given language. Collapsing the different senses into one big list is not recommendable, since the different senses are not mutual synonyms.

from nltk.corpus import wordnet as wn
print(wn.synonyms('car'))

[['automobile', 'machine', 'auto', 'motorcar'], ['railcar', 'railway_car', 'railroad_car'], ['gondola'], ['elevator_car'], ['cable_car']]

print(wn.synonyms('coche', lang='spa'))

[['vehículo', 'auto', 'carro', 'automóvil', 'máquina', 'turismo'], ['vagón', 'automotor'], ['vagón', 'vagón_de_pasajeros']]

Thanks @ekaf. Would you mind adding an example to https://github.com/nltk/nltk/blob/develop/nltk/test/wordnet.doctest please?

Thanks @ekaf!


Update policy to point to open-cluster-management helm charts

Signed-off-by: Tesshu Flower<EMAIL_ADDRESS>Policy used to deploy volsync previously pointed to backube/volsync
upstream repo - updating to use open-cluster-management/volsync-charts.
Policy will pull from the release-2.4 branch right now and images
are set to image locations at quay.io/open-cluster-management.
Ultimately the image locations will be updated to use the official
redhat.registry locations.

FYI @jnpacker @cooktheryan

Thanks @ycao56 !

@tesshuflower++


feat(cdk-drag-drop): Give a visual clue to which droplist can receive a specific dragged item.

Feature Description
Currently,
When dragging an item, the css class cdk-drop-list-receiving is displayed on all the droplists, even those that cannot receive the item due to the enterPredicate output.
This is misleading.
Use Case
Given that a dragged item is restricted to some drop lists, I want to display a visual clue about where I can drop this item

Looks it's because isReceiving here only looks at whether any connected siblings are active, but it doesn't account for the predicate. When fixing this, we have to be careful about performance, because isReceiving is invoked inside a data binding.


Update rocket-chat to 2.2.0

There was a pull request template when you submitted. It contains steps that must be followed.
If you were not presented a template, you may have submitted via a CLI tool (likely hub). It that was the case, you may wish to see if the tool has a way to let you use the template (hub is working on it).
Please add and fill the template.

@miccal yes I used hub. Sorry, next time I will add the template.


Add truffle

This PR adds Truffle to the scaffold-eth project, replacing scripts that were previously using HH. Scripts can be found in packages/truffle/scripts.

I stepped through the set up, but it doesn't seem like the UI knows about the contract I deployed:

the error from src/views/ExampleUI.jsx:40:
Unhandled Rejection (TypeError): Cannot read properties of undefined (reading 'setPurpose')

Or is the readme missing a step to update MyContract?  Happy to lend another set of eyes on this


refactor: add some spacing before Professionals table

For pleasure of the eye.
Before:

After:

:tada: This PR is included in version 1.132.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[MIG] Migrated buy_and_hodl and buy_low_sell_high to version 0.3 to work with Poloniex exchange

Migrated buy_and_hodl.py and buy_low_sell_high.py to work with Poloniex exchange specified in the catalyst run command, e.g. via catalyst run -f buy_and_hodl.py --start 2017-1-1 --end 2017-10-2 --capital-base 100000 -x poloniex.

Thank you!


How to get the 'backup_retention_period' from a rds instance

Hi, I am new to terratest and terraform.
I can see from the example that I can create an RDS instance, which I have modified to add backup_retention_period = 7
I would like to be able to test that this has been done, but i cant work out how to get that field. (It doesn't help that I am also quiet new to AWS and have no idea what that field would be classed as!)
Any help is greatly appreciated, thanks

Hi Dan, were you able to resolve this?

Yes I was able to resolve it
I used aws.GetRdsInstanceDetails and it contains an element *dbInstance.BackupRetentionPeriod


The Choose catalog/schema window doesn't keep its size after closing (in contrast to Select Data Souce window)

Description
If the window is small and the list with databases is long, it forces user to resize the window or scroll the scrollbar to find the desired database.
I would like to observe more databases in this list and avoid resizing the window on every opening.
Now the window doesn't keep its size after closing.
https://github.com/user-attachments/assets/22c685a0-70aa-4077-88ea-1015eb7c0843
So I suggest keeping its previous size and restore it on the next opening, as it works now in Select Data Souce window:
https://github.com/user-attachments/assets/9c5fa24e-497d-4a83-b3b4-77b6c68ba4ff
DBeaver Version
Enterprise Edition 24.3.1-202411300022
Operating System
Windows 10
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Thanks for suggestion


Review: Key generation

The purpose of this task is to review the following functions and prepare them for upstreaming:

mbedtls_ssl_generate_handshake_traffic_keys()
mbedtls_ssl_tls1_3_derive_master_secret()
mbedtls_ssl_generate_resumption_master_secret()
mbedtls_ssl_generate_application_traffic_keys()
mbedtls_ssl_generate_early_data_keys()
mbedtls_ssl_create_binder()

Those are mostly simple wrappers around the HKDF-based key derivation functions of TLS 1.3 which have already been upstreamed.
Those functions operate on the whole SSL context. Ideally, they'd be standalone like the other key schedule functions. If that's no feasible, it should be documented which fields of the SSL context are required as input, and which fields are being set -- this gives us a chance to write some unit tests nonetheless.
Acceptance criterion:

PRs have been filed and merged to the prototype to prepare the above functions for upstreaming.
A PR is open on upstream Mbed TLS, upstreaming all of ssl_tls13_keys.[ch] as it is in the prototype.

For mbedtls_ssl_generate_handshake_traffic_keys():

[ ] Add internal structure mbedtls_ssl_handshake_secrets (or similar) holding triple of secrets: 0-RTT, HS, Master
[ ] Compute PSK and ECDHE secret prior to mbedtls_ssl_generate_handshake_traffic_keys()
[ ] Make mbedtls_ssl_generate_handshake_traffic_keys() standalone by passing PSK + ECHDE secret as input, and taking a pointer to a mbedtls_ssl_handshake_secrets structure as the output.
[ ] Add KATs to the SSL unit test suite.

There seems to be a bigger issue here, as we're computing some secrets multiple times. For example, the early secret is computed both in mbedtls_ssl_tls1_3_derive_master_secret() as well as mbedtls_ssl_create_binder().

[ ] Structure the key schedule in such a way that each secret is derived only once.

[ ] Reuse mbedtls_ssl_tls1_3_evolve_secret() in the early_keygeneration in mbedtls_ssl_create_binder(). Currently this is calling the HKDF API directly.

[ ] Make the current handshake transcript an explicit parameter for mbedtls_ssl_create_binder(): This makes it easier to unit test, and avoids re-calculations the handshake transcript every time in case we offer multiple PSKs.

[ ] Use mbedtls_ssl_get_handshake_transcript() in mbedtls_ssl_generate_resumption_master_secret(), or make the handshake transcript a parameter.

The early data key generation is hard to follow at the moment. The logic is this: When establishing which PSK to use, the peers call mbedtls_ssl_create_binder() to compute the PSK binder from a PSK. As a somewhat hidden intermediate step in this derivation, the early secret is computed and stored in the handshake structure, overwriting the previous one if present, that is, when multiple PSKs are considered. In particular, only the one from the last call to mbedtls_ssl_create_binder() will survive. Once a PSK is chosen, mbedtls_ssl_generate_early_data_keys() is called which then builds on this early secret to derive 0-RTT keys.
While it may be true that the server stops parsing PSK binders immediately once it found an acceptable PSK, and thus the last call to mbedtls_ssl_create_binder() is indeed the one establishing the early secret to use, this logic is difficult to follow because you can't tell from the function invocations when the early secret is actually established.
Moreover, should the client ever offer more than one PSK, it simply doesn't work anymore, and we have to re-generate the early secret once we know which PSK the server has chosen.
Finally, the early secret is then re-generated in mbedtls_ssl_derive_master_secret(), which is unnecessary and slightly confusing.

Suggestion: mbedtls_ssl_create_binder() should use a local buffer to hold the early secret for the PSK under consideration. Once it's clear which PSK will be used, mbedtls_ssl_generate_early_keys() will be called to establish both the early secret, as well as keys derived from it. Finally, mbedtls_ssl_derive_master_secret() would build on the early secret instead of re-calculating it.

Logically, we need to take care of the following layers of key schedule:

Key evolution: Empty -> Early Secret -> Handshake Secret -> Master Secret
Secret derivation per

Early Secret: Binder (not needed), client 0-RTT keys, early exporter
Handshake: Client and server handshake secrets
Master: Client and server application secrets, resumption master, exporter master

Key derivation per secret

Plus, one function specifically for the PSK -> PSK binder derivation.
The core functions for those steps are

mbedtls_ssl_tls1_3_evolve_secret()
mbedtls_ssl_tls1_3_derive_secret()
mbedtls_ssl_tls1_3_make_traffic_keys()
all of which have already been upstreamed.

The functions that this issue is about are the convenience functions built on top of this. Specifically, the following functions provide some flattening of (2)+(3):

mbedtls_ssl_generate_handshake_traffic_keys()
mbedtls_ssl_generate_application_traffic_keys()
mbedtls_ssl_generate_early_data_keys()

Nitpick: Not every secret generated in (2) is converted to a traffic secret in (3). For example, the exporter secrets aren't. Should we reflect this in the naming of the functions? E.g. mbedtls_ssl_tls1_3_derive_{handshake,application,early_data}_key_material()?


⚠ Bofrost.de has degraded performance

In da56554, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1036 ms

Resolved: Bofrost.de performance has improved in 1d0716c.


Wider vector for FP16 RELU Grad on GPUs

To solve a Build issue brought by https://github.com/tensorflow/tensorflow/pull/39767
@sanjoy

@sanjoy I fixed one conflict. PTAL.


Add a function to save captions when they are submitted by the user

When trying to edit the caption of a picture, the submit button doesnt do anything. The captions are not saved and no confirmation is shown. When the generate button is used, a caption is successfully generated and automatically saved. But this caption can not be edited nor removed.
Logs dont show any activity besides caption generation.
This happens on the newest docker-compose examples.

I can confirm the same issue here

This still seems to be an issue. I'm running version 3.8 (at least that's what docker-compose.yml says). Entering text in the text field and clicking "submit" doesn't seem to do anything.
This seems like a pretty basic functionality for a photo management software - is there still no way to caption images? Thank you!

I'm looking into this on https://github.com/meichthys/librephotos/tree/lihtbox_sidebar
I'm not familiar with react, so i need to play around with the front end a bit more to get things working.

I think you can look at this file here to get a good idea on what to do: https://github.com/LibrePhotos/librephotos-frontend/blob/dev/src/components/lightbox/TimestampItem.tsx

@derneuere , If we add a user-generated caption, we will have multiple caption types:

User generated
Auto-generated via im2txt

My thoughts are to display the user-supplied caption on the Lightbox sidebar, and if a user caption doesn't exist, then display the auto-generated im2txt caption. This seems logical, but has a side-effect that the user would not be aware of the auto-generated caption that still exists after they supply their own caption. I suppose the user could re-click the "Generate" button which would re-generate the caption, at which point, we could clear the user caption so the auto-generated caption is displayed again?

start working.


Security Monkey 2.0 Tracker

We are actively working on a 2.0 release that will have a number of awesome and very important features.
The most important of which is a brand new UI and Python 3 support!
The following list documents some of the most important changes that must be completed:

[ ] New UI written in ReactJS (IN PROGRESS)
[ ] Python 3 migration (IN PROGRESS)
[ ] Strip out flask_security; replace with standard JWTs (IN PROGRESS)
[ ] Remove all existing RBAC logic and replace it with flask_principal needs (IN PROGRESS)
[ ] Go through each and every API, verify that they work properly and have adequate unit tests (IN PROGRESS)
[ ] Clean up the class registries to make use of a singleton (completed for Account registries) (IN PROGRESS)

This is being developed in the 2.0 branch.

Just completed:

New JWT logic is now implemented and in place for the account.py view.
Bug fixes and proper unit tests in for account.py and a bunch of other code that it calls.

Next to complete: account_bulk_update.py.

@mikegrima
First of all let me say that we are very happy about the objective of a Security Monkey 2.0. We are using Security Monkey a lot lately for our Cloud deployment and are quite happy with the overall architecture and the extensibility. We currently use it in a GCP environment with 50+ projects where we also found some issues which we try to address via PR's which works very well. Nevertheless we found also some pain points which we would like to mention with the hope they get considered for the Security Monkey 2.0 roadmap.

We currently realize the account management (which are projects in GCP terms) via a cron-job which syncs GCP projects with security-monkey accounts, add them if needed, or deactivate resp. reactivate if the status of the projects changes over time. This feels cumbersome and was something we had to invent in order to use security-monkey in a GCP context.
Our users can use Google SSO to login to the Security Monkey UI. Currently it is not possible to give a user for example the Justify role for some projects (accounts) and only Viewer role on other projects. An example would be that a product team has several projects for dev/qa/prod and a team consists of developers and team-admins. As a security-monkey administrator I would like to give only team-admins the possibility to justify issues and developers viewer rights. And this only for a subset of accounts which would correspond to their GCP projects.
We furthermore implemented a white-listing feature for auditors so that product team-admins can propose that for a certain combination of technology, check and item where no issues will be generated. An example would that GCE instances managed by GKE in general have an external IP address which would generate an issue which then have to be justified. Due to the nature of GKE where nodes can be autoscaled this is very cumbersome. If there is general interest we can contribute the whitelisting feature.
Security Monkey due to its name is a security tool but due to its architecture it has the potential to be used in a wider range for cloud controlling aspects. We are thinking of maybe using it for cost-controlling aspects in a cloud environment in a sense of a Cloud Resource Controlling tool. We have trouble to align our need with the mission of security-monkey. Maybe you address our concerns by mentioning which tools are better suited for cost monitoring & controlling. What do you use for that problem space?

Keep up the great work and thanks for open-sourcing security-monkey it is being a great journey since Initial commit

Hello @ottogroup-com :
A central theme to note is:
In general, Netflix's use cases around Security Monkey are quite different from the rest of the OSS community, and as such, many features are a low priority/not a priority for us to fix. Generally speaking, we use Security Monkey as a quick and easy way of getting the current and historical configuration of an item in our environment. With regards to issues and auditors, we are building out other tooling to identify and respond to them as they occur.
At the time Security Monkey was developed (2014), Netflix’s AWS environment was much, much smaller. Since then, our infrastructure massively grew in size and complexity. Thus, having one tool to do everything simply didn’t scale. The current theme and priority for us (internally) with Security Monkey is to de-couple items from it as much as possible and to migrate SM's core components onto other tools that can better handle the size of our environment and scale horizontally. A notable example is our effort to have Security Monkey rely on external event-driven Lambda functions (see Historical) and only operate on known changes that occur, as they occur with context on who/what performed the change. This is a departure from the existing Security Monkey implementation of actively watching our environments (polling model) and migrating to receiving the changes that happen via a push/event model. Solutions like Historical (still in very active development) permanently solve the massive scalability issues that we encountered.
I’m more than happy to chat over LinkedIn should you have any other questions/feedback to provide.
All that being said, please see my responses inline:

We currently realize the account management (which are projects in GCP terms) via a cron-job which syncs GCP projects with security-monkey accounts, add them if needed, or deactivate resp. reactivate if the status of the projects changes over time. This feels cumbersome and was something we had to invent in order to use security-monkey in a GCP context.

Automated account management is generally a pain. Internally, we developed a tool called SWAG(https://github.com/Netflix-Skunkworks/swag-api, and https://github.com/Netflix-Skunkworks/swag-client), which is an account metadata service. We have integrated this into Security Monkey to sync with all of our AWS accounts (it also supports GCP and any other type of cloud account infrastructure you would want to manage). The docs are lacking at the moment, and beefing that up is a priority for us.
The other really big pain point is that due to the distributed nature of the watchers, we currently need to bounce the scheduler whenever there is a change. This could be done more programmatically, however, this is not a priority for us to fix. We mostly bounce things regularly since we have ephemeral instances, and this will be a non-issue when we start pulling data from Historical.

Our users can use Google SSO to login to the Security Monkey UI. Currently it is not possible to give a user for example the Justify role for some projects (accounts) and only Viewer role on other projects. An example would be that a product team has several projects for dev/qa/prod and a team consists of developers and team-admins. As a security-monkey administrator I would like to give only team-admins the possibility to justify issues and developers viewer rights. And this only for a subset of accounts which would correspond to their GCP projects.

This has been requested by a number by other users as well. Netflix presently does not have this use case, and as such, it is not a priority for us to implement. That being said, the changes that are being made in 2.0 will make it massively easier to implement this capability.

We furthermore implemented a white-listing feature for auditors so that product team-admins can propose that for a certain combination of technology, check and item where no issues will be generated. An example would that GCE instances managed by GKE in general have an external IP address which would generate an issue which then have to be justified. Due to the nature of GKE where nodes can be autoscaled this is very cumbersome. If there is general interest we can contribute the whitelisting feature.

The issue system has been a pain-point for many users. Internally, we are moving to other tooling to detect and resolve issues as they come up (see the central theme above).

Security Monkey due to its name is a security tool but due to its architecture it has the potential to be used in a wider range for cloud controlling aspects. We are thinking of maybe using it for cost-controlling aspects in a cloud environment in a sense of a Cloud Resource Controlling tool. We have trouble to align our need with the mission of security-monkey. Maybe you address our concerns by mentioning which tools are better suited for cost monitoring & controlling. What do you use for that problem space?

I don’t work on cost monitoring and management, so I can’t really comment too much on that space. However, about a year or so ago, for a fun hack day exercise, I wrote watchers and auditors for GitHub organizations. Security Monkey has been a fantastic tool for tracking our repos, users, and teams across our many GitHub organizations (in fact, I encourage you to use that feature if you have GitHub resources and aren’t using it already). In general, Security Monkey is a great tool for tracking assets and their changes. Thus, if something can be seen as an asset, with changes to track over time, and can be audited, then SM is a potential tool for it.

Completed the audit_scores API. Next up is auditor_settings.

@mikegrima
Thank you for your elaborate answer and for clarifying the central theme around Security Monkey. Just to make thinks clear we are far away from pointing out weak spots from Security Monkey but we rather want to discuss the areas of improvement for Security Monkey where we see potential and also are interested in contributing.
To your mentioned topics:
We had also noticed some scalability issues with Security Monkey where find_changes actually has a considerable long run-time when number of accounts, checks and technologies increases. Thus the idea of a event-driven approach seems very appealing and interesting. We will definitely have an eye on how Historical  evolves. About SWAG it seems useful though I might not catched the full idea #49 helped a bit.
I more than happy to catch up with you on LinkedIn for further discussions.

We will not be moving forward with SM 2.0 as it will require a massive effort. Internally, we are undergoing another initiative to replace Security Monkey.

@mikegrima this is unfortunate to here. Can you please share some information what the initiative to replace Security Monkey are?

We're moving to AWS Config and internal tooling to wrap it.


generateJsonSchema(Pojo1.class, Pojo2.class)

I have multiple POJos that reference each other.
Would it be possible to support giving multiple classes to generateJsoNSchema()?
class Pojo1 {
  public Pojo2 member;
  public String foo;
}

class Pojo2 {
  public String bar;
}

jsonSchemaGenerator.generateJsonSchema(Pojo1 .class, Pojo2 .class);

???

I should have better demonstrated my use case. I have a colleciton of domain classes. Some have relationships, other's don't. Example:

Pojo1 -> Pojo2
Pojo2
Pojo3 -> Pojo2

Now, if I generate the schema for all 3, I get a duplicated schema for Pojo2.
I could add a "virtual" holder of the domain world:

Domain -> Pojo1, Pojo2, Pojo3

and then generateJsonSchema(Domain.class) would give me a json schema for all domain classes and w/o duplications.

Ah okay, I am no expert on the matter - but I suppose it depends what you are using the schema for exactly.
If you are just passing the domain around then a holder would make a lot more sense, as this would contain a definition per object - rather than having to pass around an entire schema per object.
Try wrapping them into a Domain, as you suggested, and see if it works for what you are trying to do?

@AlexBroadbent is correct.
You need the "virtual" top domain-class which has pojo1, pojo2 and pojo3 as subTypes to be able to tell jackson ObjectMapper that you would like to parse the jsonString into on of the types.


Delete class "carbon dioxide emission traffic sector"

Description of the issue
carbon dioxide emission traffic sector is a weird concept and currently a subclass of sector.
Ideas of solution
Delete and start from a fresh start if such a concept is needed.
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

I agree. Do we need further discussion here?

No need for discussion. I raised the issue more to document. ;)


MySQL syntax error using combine function on more than two Selects in Zend\Db\Sql\Select

The recent addition of the combine() function in Zend\Db\Sql\Select works great for doing a union of two select statements, but MySQL throws a syntax error when adding more. Specifically, it doesn't like the extra parens created in the following use case:
$selectA = new Select;
$selectB = new Select;
$selectC = new Select;

$selectB->combine($selectC);

$selectA->combine($selectB);

creates a select statement similar to the following:
( SELECT `foo` FROM `bar1` ) UNION ( ( SELECT `foo` FROM `bar2` ) UNION ( SELECT `foo` FROM `bar3`) )

See related discussion on this pull request: https://github.com/zendframework/zf2/pull/3962#issuecomment-19616900

I'm having the same issue of extra parans denied in MySQL (whereas it works fine in PGSQL) when doing multiple Unions using "combine()". I don't think it's been fixed in the latest version of ZF2?

I'm having the same issue of extra parans denied in MySQL (whereas it works fine in PGSQL) when doing multiple Unions using "combine()". I don't think it's been fixed in the latest version of ZF2?

Actually I'm getting the sql string using "getSqlString(new \Zend\Db\Adapter\Platform\Mysql())" and passing it to $dbAdapter->query(). I faced another awkward situation when SQL string was having " limit = '0' " which is denied by MySql but when the same "Select $select" object is passed to $tablegateway->selectWith( $select ) the query runs fine without any error so I think there is some problem in "getSqlString()" function.
By the way I'm unable to run "multiple union" $select using $tablegateway->selectWith( $select ). My $select object has tableName as "temp" (no such physical DB table exists and "temp" is alias of "from" clause having UNION of tables). When initializing the tablegateway object I pass it "temp" as table name to the constructor but when $tablegateway->selectWith( $select ) is called it gives me error like:
"The table name of the provided select object must match that of the table".
I tried this tablegateway approach assuming it will not have any issue as in the case of " limit = '0' ". Can you help? @ralphschindler

Actually I'm getting the sql string using "getSqlString(new \Zend\Db\Adapter\Platform\Mysql())" and passing it to $dbAdapter->query(). I faced another awkward situation when SQL string was having " limit = '0' " which is denied by MySql but when the same "Select $select" object is passed to $tablegateway->selectWith( $select ) the query runs fine without any error so I think there is some problem in "getSqlString()" function.
By the way I'm unable to run "multiple union" $select using $tablegateway->selectWith( $select ). My $select object has tableName as "temp" (no such physical DB table exists and "temp" is alias of "from" clause having UNION of tables). When initializing the tablegateway object I pass it "temp" as table name to the constructor but when $tablegateway->selectWith( $select ) is called it gives me error like:
"The table name of the provided select object must match that of the table".
I tried this tablegateway approach assuming it will not have any issue as in the case of " limit = '0' ". Can you help? @ralphschindler

I don't think it's been fixed in the latest version of ZF2?

If the issue ain't closed, then the bug ain't fixed.

I don't think it's been fixed in the latest version of ZF2?

If the issue ain't closed, then the bug ain't fixed.

I had the same issue with SQLite. I've worked around it by overriding the specifications used in the combine. Pretty? No. But it did work for me.
(new Select)
    ->setSpecification(Select::COMBINE, '%1$s %2$s ')
    ->setSpecification('statementStart', '')
    ->setSpecification('statementEnd', '')
    ...

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


Support for placeholder?

I'm trying to add a placeholder text to this as described here:
https://alex-d.github.io/Trumbowyg/documentation/#placeholder
But adding it as attribute isn't working. It also can't be put in the configuration.
Anyone have any idea on how to do it?
Thanks!

I could not reproduce it, the placeholder works fine.

  <trumbowyg v-model="content" placeholder="here we go"></trumbowyg>


readded signup page

@tomwilkie can you merge this, so that we can update the docs on the site?  There's a section on there with "old screen captures".


Responsiveness Bug in Home

Description

This Dashboard section in Home page is not sized properly in Mobile View.
This needs to be fixed asap.

Screenshots

Additional information

Maintain Folder Structure
Always use styled componets and MUI components instead of plain CSS.

Make sure to read the CONTRIBUTING and SETUP docs before proceeding
Happy contributing. 💐
Star my other Repositories here

hello there, I'd love to assist, kindly assign.

Sure I'll assign you

Hello @elidakirigo. What is the status of the work?

Hello there, I'd like to work on fixing this

Sure


Remove duplicate missing closing bracket diagnostic

Part of: https://github.com/dotnet/aspnetcore/issues/28654
Before

After

/azp run


Fix energies slice initialization in simulated annealing

Hello! I'm submitting this PR to fix the initialization of the res.Energies slice in anneal.go. It is currently initialized with a size of settings.MaxIterations and then inside the loop items are being appended to it. This causes the sizes of the res.Energies and res.States slices to be different.

Thank you for this bugfix!

Codecov Report

Merging #14 (8955635) into master (82b6e4d) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #14   +/-   ##
=======================================
  Coverage   99.30%   99.30%
=======================================
  Files          13       13
  Lines         579      579
=======================================
  Hits          575      575
  Misses          2        2
  Partials        2        2

Impacted Files
Coverage Δ

anneal.go
100.00% <100.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 82b6e4d...8955635. Read the comment docs.


Added note to email getting started about originator

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/actionable-messages/actionable-messages-via-email.md
:warning:Warning

Details

docs/actionable-messages/actionable-messages-via-email.md

Line 19: [Warning] Invalid file link:(~/actionable-messages/actionable-email-dev-dashboard).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/actionable-messages/actionable-messages-via-email.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Misc cleanups

What this PR does / why we need it:

chore: Run black formatter on project files
chore: Remove unneeded sanity test ignore files
chore: Bump docs copyright year
Use correct KubeVirt project name

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

None

/lgtm

/approve


Run benchmarks as tests in CI

Out benchmarking suite is actually a pretty valuable end-to-end test, especially when working on compute related work. This PR adds it as part of CI so we don't accidentally break it (as we've done many times in recent weeks).

I guess you have found the broken benchmarks


Collect Swift config

Stockpile doesn't currently collect swift config.

Have to move https://review.openstack.org/#/c/584992/1 to stockpile


Update string index access return type

Purpose
$title
Fixes #31758
Fixes #31749
Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

We need to add test cases for #31749


Allow windows-result to work on non-Windows platforms

This updates the windows-result crate so that it can compile and work on non-Windows platforms.  Right now, there are dependencies on things like GetErrorInfo, which are obviously not present on other platforms.
This modifies Error so that the info field is only present on Windows. Everything that reads/writes that field is also made conditional.
I also manually imported definitions for some HRESULT constants, so that we did not need to rely on bindgen for them.  This was necessary because none of the bindings should be used on non-Windows platforms.  When we convert from std::io::ErrorKind to HRESULT, we do our best to map things to error codes that make sense, although some of them are a bit of a stretch.
This is one part of fixing #3083.

What's the supporting rationale for this?

What's the supporting rationale for this?

I've opened an issue which describes the problem: #3083.  Briefly, I need cross-platform COM to work.  The windows-rs crates are expected to work on other platforms, even if their functionality is greatly reduced.

We previously explored similar changes to support DirectX, its pseudo-COM semantics, and non-Windows targeting, but it showed signs of becoming a tangled web of related issues (e.g. mismatching wide strings).

I need cross-platform COM to work [...]

There is no cross-platform COM though, right?

The windows-rs crates are expected to work on other platforms [...]

I'm not certain if this reflects a strong opinion or a shift in Microsoft's direction for this crate. I believe our current stance is to focus squarely on Windows targets only. @kennykerr thoughts?

There is no cross-platform COM though, right?

There is definitely cross-platform COM in the sense that code uses COM interfaces on different platforms.  DWriteCore is a shipping Microsoft product that has a COM-based API, and ships on Android, iOS, Mac OS, and Linux desktop.
DWriteCore is implemented mostly in Rust.  We are currently using com-rs for COM, but com-rs is the old deprecated crate for COM support.  The windows-rs crates already compile for non-Windows platforms and the repo has GitHub actions which test that it compiles for Linux and Mac.
I understand that many parts of the Windows crates will naturally not work on other platforms. But for cross-platform development and for implementing systems that interoperate with Windows, such as systems that use COM or HRESULTs and such, this is important and is easily achievable.

I'm not certain if this reflects a strong opinion or a shift in Microsoft's direction for this crate. I believe our current stance is to focus squarely on Windows targets only. @kennykerr thoughts?

There are certainly many aspects of cross-platform support that are very problematic, such as is the case with strings, but I think we can provide some minimal support for things like the essentials of COM - boiling it down to IUnknown - in such a way that it does not negatively impact our core support for the Windows platform.
I do however think that this PR is a little premature and we need to be a bit more deliberate about the scope of such work and that should be discussed in an issue like #3083 before we get too deep into an implementation such as this PR.

Maybe some basic tests for Error and HRESULT can be added here:
https://github.com/microsoft/windows-rs/tree/master/crates/tests/linux/tests
That way the linux.yml workflow will be sure to exercise it as part of PR validation.

Added test coverage for functions that are different on non-Windows platforms.

The Mac job runners appear to be failing, but without providing any error logs.  :[

I'll just override - those runners are not too reliable.


The plugin does not connect with wallets offered by https://www.safepal.com/

An issue has been raised by Ramon from ML team about the ability to connect to https://www.safepal.com/
Further details are required, for now we should attempt to replicate using mobile app and chrome extension.

I have tested this issue on mobile and web versions and have next results:

for web (Chrome extension) - there’s no reaction on after choosing SafePal Wallet in Connect Wallet
for mobile (iOS) - there an error present in the console after trying to connect via WalletConnect QR


Can't use chainer in W10 with CUDA 11.1

When trying to run chainer, I get the following error message:
Traceback (most recent call last):
  File "train_dcgan.py", line 178, in <module>
    main()
  File "train_dcgan.py", line 65, in main
    chainer.cuda.get_device_from_id(args.gpu).use()
  File "C:\Users\Beri\miniconda3\envs\ganDemo\lib\site-packages\chainer\backends\cuda.py", line 279, in get_device_from_id
    check_cuda_available()
  File "C:\Users\Beri\miniconda3\envs\ganDemo\lib\site-packages\chainer\backends\cuda.py", line 142, in check_cuda_available
    raise RuntimeError(msg)
RuntimeError: CUDA environment is not correctly set up
(see https://github.com/chainer/chainer#installation).No module named 'cupy.util'

This works fine if using CUDA 10.2, but it has no support for the most recent NVIDIA GPUs.

Conditions:

Platform: Windows-10-10.0.19041-SP0
Chainer: 7.7.0
ChainerX: Not Available
NumPy: 1.19.3
CuPy: Not Available
iDeep: Not Available

Chainer version: 7.7.0
CuPy version: cupy-cuda111==8.1.0
OS/Platform: Windows 10 x64
CUDA/cuDNN version: CUDA 11.1/cuDNN <IP_ADDRESS>

I needed also to add this line import cupy.cuda.cudnn, so that libcudnn was assgined properly

Merging to #8601

@DiKorsch either this did not work for me, or I misunderstood what I should do. Did you mean that I should add import cupy.cuda.cudnn to cuda.py between lines 121 and 122? I have tried to do so, but the error message (the same as in the first message in this issue) did not change for me. Do you know what I could do to fix it? Thanks.

@iegorval, yes, this is the change, that fixed the problem for me :shrug:

@DiKorsch ok, thank you for the fast reply. I guess I will open a new issue then.


AssertionError: Default process group is not initialized

[00:00<?,?it/s]12 15:10:26 WRN A exception occurred during Engine initialization, give up running process
Traceback (most recent call last):
  File "evaluate.py", line 284, in <module>
    main()
  File "evaluate.py", line 247, in main
    output = predict_multiscale(model, image, input_size, [1.0], args.num_classes, False, 0)
  File "evaluate.py", line 168, in predict_multiscale
    scaled_probs = predict_sliding(net, scale_image, tile_size, classes, recurrence)
  File "evaluate.py", line 130, in predict_sliding
    padded_prediction = net(torch.from_numpy(padded_img).cuda(non_blocking=True))
  File "/home/spple/anaconda3/envs/pytorch1_1_0--py3_6--cuda9_0/lib/python3.6/site-packages/torch/nn/modules/module.py", line 493, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/spple/anaconda3/envs/pytorch1_1_0--py3_6--cuda9_0/lib/python3.6/site-packages/torch/nn/parallel/data_parallel.py", line 150, in forward
    return self.module(*inputs[0], **kwargs[0])
  File "/home/spple/anaconda3/envs/pytorch1_1_0--py3_6--cuda9_0/lib/python3.6/site-packages/torch/nn/modules/module.py", line 493, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/spple/paddle/DeepGlint/CCNet-pytorch-1.1/networks/ccnet.py", line 176, in forward
    x = self.relu1(self.bn1(self.conv1(x)))
  File "/home/spple/anaconda3/envs/pytorch1_1_0--py3_6--cuda9_0/lib/python3.6/site-packages/torch/nn/modules/module.py", line 493, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/spple/anaconda3/envs/pytorch1_1_0--py3_6--cuda9_0/lib/python3.6/site-packages/inplace_abn-1.0.7-py3.6-linux-x86_64.egg/inplace_abn/abn.py", line 152, in forward
    self.activation, self.activation_param, self.group)
  File "/home/spple/anaconda3/envs/pytorch1_1_0--py3_6--cuda9_0/lib/python3.6/site-packages/inplace_abn-1.0.7-py3.6-linux-x86_64.egg/inplace_abn/functions.py", line 157, in inplace_abn_sync
    training, momentum, eps, activation, activation_param, group)
  File "/home/spple/anaconda3/envs/pytorch1_1_0--py3_6--cuda9_0/lib/python3.6/site-packages/inplace_abn-1.0.7-py3.6-linux-x86_64.egg/inplace_abn/functions.py", line 72, in forward
    ctx.world_size = distributed.get_world_size(group=group)
  File "/home/spple/anaconda3/envs/pytorch1_1_0--py3_6--cuda9_0/lib/python3.6/site-packages/torch/distributed/distributed_c10d.py", line 584, in get_world_size
    return _get_group_size(group)
  File "/home/spple/anaconda3/envs/pytorch1_1_0--py3_6--cuda9_0/lib/python3.6/site-packages/torch/distributed/distributed_c10d.py", line 200, in _get_group_size
    _check_default_pg()
  File "/home/spple/anaconda3/envs/pytorch1_1_0--py3_6--cuda9_0/lib/python3.6/site-packages/torch/distributed/distributed_c10d.py", line 191, in _check_default_pg
    "Default process group is not initialized"
AssertionError: Default process group is not initialized

@yangninghua  I have the same problem. Have you solved this problem?

no,I have given up it
On 10/20/2019 15:38, xiaoxiao wrote:
@yangninghua I have the same problem. Have you solved this problem?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@speedinghzl @yangninghua @yenpengsun I also got the problem mentioned above "AssertionError: Default process group is not initialized". Do you guys have any idea about this?
@yangninghua "gave it up" means you did not manage to run this project?
Thank you in advance!


[shaderc] Add MSL version and Apple platform configurations - iOS / macOS

The Metal Shading Language cross-compiler in shaderc is improved by being more specific with the parameters it uses to configure SPIRV-Cross for the SPIRV -> MSL. This provides a greater deal more flexibility for users targetting iOS vs macOS shaders, and provides platform specific MSL generation conditions as outlined by SPIRV-Cross.
The MSL version selection fine tuning is now made available to users of shaderc through MSL profiles, similarly matching the approach taken for users wishing to compile different versions of SPIRV for specific target Vulkan versions.
A fix is made to the current version selection of MSL 1.0.0, as it is now a deprecated version. The minimum default has now been set to MSL 1.2, based on the MSL specification. The selected MSL default version of 1.2 in this PR nicely blends the lowest version that caters to macOS 10.12 and iOS 10 - both very old versions at this point in time - so it seemed like a good choice.
In order to get specific features of the different MSL versions, the SPIRV that is generated by glslang that is then fed into SPIRV-Cross will need to have its client spec updated accordingly. This is handled in this PR, with the mapping of SPIRV version to MSL being based on the feature sets of SPIRV for Vulkan which should map to features in MSL.. the resultant feature mapping is based on what SPIRV-Cross actually implements, so it could be a case that ymmv with some of the features.

Also test your change by rebuilding all shaders with SPIRV and Metal with shaderc from master, and then switch to your change and rebuild it again and make sure nothing is changing.

Also test your change by rebuilding all shaders with SPIRV and Metal with shaderc from master, and then switch to your change and rebuild it again and make sure nothing is changing.

Are you able to provide instructions on how to perform the rebuild ?

Are you able to provide instructions on how to perform the rebuild ?

cd examples
make rebuild TARGET=5

TARGET=5 is Metal, TARGET=7 is SPIRV.

Also test your change by rebuilding all shaders with SPIRV and Metal with shaderc from master, and then switch to your change and rebuild it again and make sure nothing is changing.

Are you able to provide instructions on how to perform the rebuild ?

cd examples
make rebuild TARGET=5

TARGET=5 is Metal, TARGET=7 is SPIRV.

Thanks a bunch!
Comparing master (file: master.zip) against phniix:add_msl_version_and_apple_platform_configuration_in_shaderc (
file: branch.zip) - they are identical. No changes detected.

they are identical. No changes detected.

Then it LGTM. Let me know if you want me to merge now?

they are identical. No changes detected.

Then it LGTM. Let me know if you want me to merge now?

Niice! Yes, it'll be great if you could merge it in when you get the chance🤠 I've also got the clean up pr ready to go in #3258 too.


ADD step copies local node_modules to the container

Hello,
As I have reported here:
https://github.com/GoogleCloudPlatform/nodejs-docker/issues/22
and here:
https://github.com/dockerfile/nodejs-runtime/issues/2
the local node_modules dir is copied over the correct one in the container. I'm thinking this might only be a problem when the .dockerignore file is not supported. This is the case on Google Managed VM's.
Could someone verifie it works as intended so we know it's only a problem for Managed VM's?
Thanks!

Closing old issue, (should be reported on https://github.com/nodejs/docker-node if you still have issues).


Data integration with INCREMENTAL causes duplicates in destination table

Hello again :)
I observed a Mage pipeline with an INCREMENTAL sync from/to a Postgres table creating really odd duplicate distributions. So digged into this:
The source table provides an updated_at column (and an surrogate id column). I used  updated_at as the Bookmark value. I also set id to "Key prob" (but not to "Unique").
Now surprisingly, the source table's  updated_at column is not unique (maybe because of some bulk updates)! There are 10x batch size rows that share the same updated_at column. I assume then the load process of Mage runs those limit/offset queries ordered by updated_at - but now there is not deterministic order ensured anymore, so for every limit/offset query in the range of the duplicated updated_at value, it is not guaranteed that the batches are complete and non-overlapping.
This eventually results into duplicates (and missing rows) in the destination table :(
I could image using a Postgres cursor might solve this issues since the ordering only happens once then. Or, Mage should forbid using Bookmark values to have duplicates.
Running on docker image 0.9.10

Just tested changing unique_conflict_method to be "IGNORE" and got the same result, one new destination row, with no change to the source.

I guess "Unique" should just be compulsory 😃 Thanks @wangxiaoyou1993 !

Doing some more investigation, as with my simple test case, it still feels like a bug, and no configuration changes that I can make seem to help.
I've captured the logs of a pipeline run where the scheduler is using bookmarks to do an incremental sync, and the query that it starts with looks like:
SELECT
COUNT(*) AS number_of_records
FROM \"public\".\"product_usage_metrics\"
WHERE \"id\" >= CAST('2' AS BIGINT)

Tracing back to the mage_integrations/mage_integrations/sources/sql/base.py file, in the count_records method, this query is being generated by the __fetch_rows method, with count_records set to True.
This results in the bookmark property ('id') being used from the last bookmark state, but my question now is: Why is the operator greater than and equal to?
Code reference: https://github.com/mage-ai/mage-ai/blob/master/mage_integrations/mage_integrations/sources/sql/base.py#L353
In my (very simplified) example source database with only 2 rows, unique 'id' field with values 1, 2, for an INCREMENTAL sync, the behavior I'd expect for a 'count records' query would be to use a plain greater than operator. If that was the case, a source table with no new records would return a count of zero, not one.
Thanks for any suggestions @mattppal @wangxiaoyou1993

Adding more examples - https://mageai.slack.com/archives/C03HTTWFEKE/p1691713423028329

We've updated the operator to use greater than for unique columns. Thus, close this ticket.
Feel free to reopen it if you have more questions or issues.


fix build error with ss #106

fix:
./conn.go:154: undefined: shadowsocks.DialWithRawAddrConn

The ss.DialWithRawAddrConn is an extended function for gost, so you should not go get this repo, just clone and go build.


[WIP] multi: add bitcoind back-end (only for API use for now)

This is an addition of a bitcoind back-end for btcwallet. This is only accessible via API from third-party applications for now.
Several things need to be done to complete this:

[ ] Several bugs need to be squashed
[ ] Part of the interface should be abstracted further into a separate generic client that can provide resan functionality in the same format as neutrino and btcd
[ ] To enable bitcoind as a back-end for standalone btcwallet will require special handling of the RPC listener and client command-line options as the default wallet RPC port conflicts with the default bitcoind RPC port

@Roasbeef so is the plan to add all of btcsuite/btcwallet as a dependency? Isn't that overkill, or are you already using a lot of that library?