Add  to the list of merchants

WBN324 Talk Radio

What's the URL of the website?  https://www.wbn324.com

Write a brief description of your business/service (max 50 characters)
WBN324 is offering cheap advertising paid with Monero

Enter the URL where a Monero mention can be found

https://www.wbn324.com
How do you accept Monero? (choose only one option)

[ ] Monero integrations (github.com/monero-integrations)
[ ] Globee
[ *] Native wallet
[ ] Other payment gateaway (Coinpayments, Morphtoken, etc. Please specify)

How would you categorize your business? (choose only one option)

[ ] Exchange
[ ] Block Explorer
[ ] Payment Gateway
[ ] Web Hosting
[ ] Tool
[ *] Service
[ ] Goods
[ ] Entertainment

Comment
 WBN324 Talk Radio would like to support the Monero project by offering cheap globall advertising

HI,  I'm just checking to see if we can get listed?   Thanks. .

Yes. We will add this to the website with the next round of merges.

OK, Thanks,  FYI, We are putting togther a head to head show with Pirate chain vs Monero.  I'm in Monero camp, and another host is bringing on someone from pirate chain. The audience largey knows nothing about crypto, nevermind privavy coins. So we think its a win all round. .   Do you know anyone who would be good on air, and can represent Monero?  I can be contacted at<EMAIL_ADDRESS>Thanks. .
Rea. .

#1651


1st draft of Hart state management SBI extension.

This draft is renamed from power management to Hart state management
extension and the function names are changed accordingly. It also
adds more description to each call and fixed some table issues.
Signed-off-by: Nick Kossifidis<EMAIL_ADDRESS>Signed-off-by: Atish Patra<EMAIL_ADDRESS>

Any comments ?


Show effect descriptions better

JavaFX can show effect descriptions (but not at the same time as name) currently. Additionally, the text for some of the cards with long names go outside the card itself, as shown in screenshot.
Also, effect descriptions should be improved to actually show something that makes sense

Effect descriptions on the server-side of things have now been taken care of. Works fine in LibGDX. Only thing that is remaining is the JavaFX GUI.

This has been fixed recently with the introducing of tooltips


Could you provide your model weights？

Very nice project. Thank you! Could you provide your model weights? ^-^

Thank you! Good catch, I will upload my LoRA and decoder weights in the next commit. Also, I noticed a small mistake in the IoU computation if you're testing the code,
f_iou = IoU(
        task="multiclass",
        num_classes=config.n_classes,
        ignore_index=255,
        average="micro",
    ).cuda()

I forgot to specify average="micro" in the current commit. I will also fix this in the next commit.

I uploaded the weights and added a short explanation to the README.md :)

I uploaded the weights and added a short explanation to the README.md :)

Thanks! Look forward to your better output!

I added more pre-trained weights and corrected the IoU computation, how I used torchmetrics was incorrect. If you're ok with it, I will close this issue.


WIP - Validate character escapes

As part of this PR I am trying to use a visitor instead of casting, but for some reason this version returns no character validation errors. Am I missing something? Maybe I am using the visitor the wrong way...

(I was under the idea that a visitor would visit the descendants of the node as well, but maybe that isn't the case?)

I started working on SyntaxError and it became bigger than I anticipated, so I changed the title of the PR. Once this one is merged I want to finish the work on characters and maybe start with strings.

Just pushed a commit with the suggested changes. Any additional comments?

LGTM!
bors r+


Feature/issue-3107 add beta negative binomial lpmf

Summary
With this PR the lpmf of beta negative binomial distribution are added.
See issue https://github.com/stan-dev/math/issues/3107
Expressions involved:
PMF
$$f(n|r, \alpha ,\beta)={\frac {\Gamma (r+n)}{n!\Gamma (r)}}{\frac {\Gamma (\alpha +r)\Gamma (\beta +n)\Gamma (\alpha +\beta )}{\Gamma (\alpha +r+\beta +n)\Gamma (\alpha )\Gamma (\beta )}}$$
Partial derivatives w.r.t the three parameters
$$
\begin{aligned}
\frac{\partial \log f}{\partial r} &= \psi(n+r) - \psi(n+r+\alpha+\beta) - \psi(r) + \psi(r+\alpha) \
\frac{\partial \log f}{\partial \alpha} &= \psi(\alpha+\beta) - \psi(n+r+\alpha+\beta) - \psi(\alpha) + \psi(r+\alpha) \
\frac{\partial \log f}{\partial \beta} &= \psi(\alpha+\beta) - \psi(n+r+\alpha+\beta) + \psi(n+\beta) - \psi(\beta)
\end{aligned}
$$
Tests
Test is written follow the guide.
Side Effects
No.
Release notes
beta_neg_binomial_lpmf is available if merged. Allows modeling heavy-tail count data.
Checklist

[x] Copyright holder: Zhi Ling
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

@lingium not a review itself, but wanted to chime in to say super nice work so far! It's no small feat to have a PR pass CI on the first try; I hardly do myself even now.
Nice meeting you at StanCon, and glad you're contributing to Stan!

@lingium not a review itself, but wanted to chime in to say super nice work so far! It's no small feat to have a PR pass CI on the first try; I hardly do myself even now.
Nice meeting you at StanCon, and glad you're contributing to Stan!

Hey @WardBrian, thanks for your support! It was a pleasure meeting you at StanCon as well. I'm glad to be contributing to Stan :)

Seems like I forgot to pull pre-commit hook's commit to local

May have to require your approval to one of the workflows to continue

Thanks for the review @SteveBronder! From my side it says merging is blocked, so please go ahead from your end

@lingium check your email. You should have received an invite to the stan org and with that I believe you will be able to click the merge button :)

Hi @SteveBronder, got the invite. I was tagged as a collaborator now but don't seem to have merge pr permission

@lingium maybe now?

Yes, it's working now!

@lingium are you also interested in adding this to the compiler yourself, or would you prefer another developer do that part? It's easy enough for me to do if you want to provide a list of signatures you'd expect support for

@WardBrian could you help me to add this time? Cuz it's super easy for you.  If so for the cdf, lcdf, lccdf, and rng, I will submit in different PRs.

I’ll take a look at that today!
And yes, it is easiest if they are each in their own PR. If I remember correctly from Stan Con, isn’t there also an alternative parameterization you are interested in?

Thanks Brian!
Yes, there is an alternative parameterization. It becomes neg_binomial_2 when one of the parameters is equal to 0. Except for that, I'm planning Waring and Yule distribution, both are special cases of beta negative binomial.


Revert "fix(deps): update rust crate rust-argon2 to v2"

Reverts tauri-apps/plugins-workspace#552

My commit now 😈 (yours wasn't signed and i'm feeling special today)


Added support for DPM capacity groups

See commit message.
TODOs:

Will only work once zhmcclient PR https://github.com/zhmcclient/python-zhmcclient/pull/744 has been merged.
Update change history once zhmccli 0.21.0 has been started.

Coverage decreased (-0.1%) to 36.902% when pulling 06f94267a422a4e131ef66a5a70175a5edb6cd18 on andy/capacity-groups into a193803a4d75bfa08de6d5f0d386d1e0b72f48a6 on master.


Avoid possible memleak in X509_policy_check() [1.0.2]

When tree_calculate_user_set() fails, a jump to error failed to
deallocate a possibly allocated |auth_nodes|.

I don't really get it, why doesn't travis fail? I mean in same way as appveyor?

Merged.  58314197b54cc1417cfa62d1987462f72a2559e0
@dot-asm, dunno, but it's unrelated.


Batch beam search output error and Transformer LM init cache issue

Hello,
I converted a model created with ESPnet to ONNX and conducted tests using your repo as a reference.
However, I encountered the following two issues.
1. Batch beam search.
I discovered an issue with repeated token outputs in the CTC results and have been working to resolve it.
As a result, I found differences between the implementation in your batch_beam_search.py and ESPnet's batch_beam_search.py.
Your code omits the log_softmax operation in the batch_init_state function. Is this the intended behavior?
Here, ESPNet
https://github.com/espnet/espnet/blob/b1046403ec7a20469594cb9f6ad3cbe58a7e6c81/espnet/nets/scorers/ctc.py#L96-L97
logp = self.ctc.log_softmax(x.unsqueeze(0))  # assuming batch_size = 1
xlen = torch.tensor([logp.size(1)])

And espnet_onnx
https://github.com/espnet/espnet_onnx/blob/647f3c69013833111c1a1aa51e80e240c9db7c0e/espnet_onnx/asr/scorer/ctc_prefix_scorer.py#L180-L181
I added log_softmax, and it works well.
2. Transformer LM init.
When exporting the Transformer LM to ONNX, the dummy input is initialized with the encoder's attention unit (e.g., 512).
https://github.com/espnet/espnet_onnx/blob/647f3c69013833111c1a1aa51e80e240c9db7c0e/espnet_onnx/export/asr/models/language_models/transformer.py#L73-L79
However, when loading the ONNX model for decoding, it is initialized with the vocab size, odim.
https://github.com/espnet/espnet_onnx/blob/647f3c69013833111c1a1aa51e80e240c9db7c0e/espnet_onnx/asr/model/lms/transformer_lm.py#L89-L94
I changed odim to the attention unit, and I confirmed that it works well.

Thank you, @park-ing, for your input.

Batch Beam Search
From my understanding, the log_softmax operation is already included in the export script. Could you please confirm whether the log_softmax is indeed part of the export process? If it is included, but we still need to compute the log_softmax, I will investigate this further.
https://github.com/espnet/espnet_onnx/blob/647f3c69013833111c1a1aa51e80e240c9db7c0e/espnet_onnx/export/asr/models/layers/ctc.py#L15-L16

Transformer LM Initialization
I understand this might be a bit confusing. The Transformer LM in ESPnet shares the same module as the Transformer Encoder. This is why the initialization tensor shape uses encoder.encoders[0].size, which is actually the input size of the Transformer LM.
The odim value is initialized based on config.odim, which is defined in the export script:
https://github.com/espnet/espnet_onnx/blob/647f3c69013833111c1a1aa51e80e240c9db7c0e/espnet_onnx/export/asr/models/language_models/transformer.py#L112
In your configuration, the odim should correspond to the size of the attention unit. However, if it is set to your vocabulary size, this could a bug. Please check your configuration.

Thank you for your response!

I exported my ASR model based on espnet1 to ONNX by referring to this repo.
The ctc.py in espnet1 does not include the log_softmax operation. I appreciate your detailed explanation.

This issue also has arisen due to working with the espnet1-based model. After modifying the odim, it works well now. I appreciate your help.


RSA one singular mbedtls_rsa_context

In all RSA functions, we always create a new mbedtls_rsa_context which holds things like the public keys and private keys to do various operations.
For optimization, we should have one singular mbedtls_rsa_context once the public key and private key have been imported.

I believe a fresh RSA context should be used each time to not reuse old RNG contexts..
Will have to investigate more on this.

This is an optimization. Until we are comfortable with functionality and can move on to "nice have optimizations", this will be back logged.

Discussion:
@JeremyTubongbanua  - Maybe importing N E D P Q every time is costly for every RSA operation.
@XavierChanth @realvarx - think it is not costly, we will investigate later

Not that it's not costly, but that there are many ways to optimize this, so we should avoid over-optimizing early.


Basic CEC support.

This PR adds basic switching on the TV when booting up, and powering off when shutting down. This is safe to use even without the CEC adapter.
I'm unsure whether or not we should make these configurable, but I would like to know how you guys think about this.
Closes #358.

I have am attached HDMI-CEC adapter already on my machine. After code review I'd be willing to test builds containing this new functionality if desired and convenient to the chimera developers.


How could I avoid space sensitivity upon hierarchy build?

Describe what did you try to do with TM1py
Build a hierarchy from a pandas data frame with Parent/Child/ElementType/Weight columns ~72k unique elements.
The code:
Variant 1:
# Build hierarchy from file
elements = []
edges = {}
for element in df_hierarchy.itertuples(index=False):
elements.append(Element(name=element.Child,element_type=element.ElementType))
consolidation = (element.Parent,element.Child)
edges[consolidation] = element.Weight
Variant 2:
hierarchy = Hierarchy(hierarchy_name, dimension_name)
hierarchy.add_element(element_name=element.Child, element_type=element.ElementType)
hierarchy.add_edge(parent=element.Parent, component=element.Child, weight=element.Weight)
Describe what's not working the way you expect
Within those ~72k elements I have 4 distinct ones (PCKGROUNDSHIP, PCK GROUND SHIP, PCKAIRSHIP, PCK AIR SHIP).
After the code successfully executes I only see PCKAIRSHIP and PCK GROUND SHIP (as they were before the other 2).
By default TMPy is considering PCKGROUNDSHIP= PCK GROUND SHIP and PCKAIRSHIP = PCK AIRS HIP.
How could I override that behavior?
Version

TM1py 1.5.0
TM1 Server Version: 11.6.00004.2

That is how TM1 works. TM1 is case and space insensitive.
Since the elements already exists, TM1 isn't building them.
You have got to come up with a logic to remove those unwanted elements from the DataFrame or within the for loop.

Hi Vinoth,
Thanks for the quick reply. I was not aware that TM1 was also space insensitive... after 10 years of working with TM1 I'm glad to see I can still get surprised :)
Thanks again for the quick response.
Nico


Error installing

Hey cool app, when i try to install it i get an error:
wzm@wzm-pc:~/github/addalias/src$ sudo python addalias.py --install
[sudo] wachtwoord voor wzm:
Traceback (most recent call last):
  File "addalias.py", line 6, in <module>
    from PyQt4 import QtGui, QtCore
ImportError: No module named PyQt4

What to do?

You need to install pyqt4 in order to run this app. Find appropriate package for your distro and install it. It should be named like python-qt4 or something.

I like this, reaction in 7 minutes :+1:  Installing it now! Closing, if anything fails I'll reopen.
Thank you for this app!

addalias -add "sudo apt-get install" "install"
command addalias not found. Install worked got these messages:
Success!
	now you can use 'addalias -parameters'
	before using you have to close this terminal window and reopen
	for example
		addalias -add "my-alias" "my-command"

I closed the terminal and opened a new one.

You can run gui with: addalias -gui command.
The usage is the exact opposite of what you typed. Instead of addalias -add "sudo apt-get install" "install", you need to write addalias -add "install" "sudo apt-get install".
Can you post this command output cat ~/.bashrc | grep alias? The app adds itself to alias list, so command addalias not found something went wrong while adding.

# enable color support of ls and also add handy aliases
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'
    #alias grep='grep --color=auto'
    #alias fgrep='fgrep --color=auto'
    #alias egrep='egrep --color=auto'
# some more ls aliases
#alias ll='ls -l'
#alias la='ls -A'
#alias l='ls -CF'

alias 3g='./sakis3g --interactive'
alias trans='ssh -p 8822<EMAIL_ADDRESS>alias thuis='openvpn --auth-nocache --config /home/wzm/Bureaublad/User1.ovpn'
# ~/.bash_aliases, instead of adding them here directly.
if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliase

I'm sure you don't like the reaction in 23 hours thing. Sorry that I'm late.
It seems like the app couldn't add itself to the alias list. Do you have write permissions to ~./bashrc file? Usually you should have by default, but you could have change it.
Can you try python addalias.py -add "install" "sudo apt-get install" in "src" directory?


how to add context and reference window like sourceinsight?

The reason i like sourceinsight is that it has realtime context preview and reference map tree window. If vscode has, i will very happy and change to vscode.

Please update this issue after reading https://github.com/Microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions#writing-good-bug-reports-and-feature-requests. Thanks.


Clarify @Required annotations for validation

Describe the problem
Currently the @Required annotation is used on the schema files both at a Class level (for required files) and the Property level (for required fields). This can be confusing and recently, we in #1198 we had a scenario where a column was required, but it was not required that the field have data for the column.   We discussed adding a new annotation when a column Header  is required, but the column data can be empty (not required), which led to discussion of the existing @Required annotation.
Proposed solution
I think for additional clarity, it would make sense to break the original @Required header into two:
@RequiredFile - when the file can not be missing from the feed (valid on the schema Class)
@RequiredValue - when a value is required for the field (
@RequiredColumn - when the column (header) is required, but the field (value) is allowed to be empty
Alternatives you've considered
Leave @Required as-is, and just add the new @ RequiredColumn annotation for the new case.
Additional context
No response

On further review, the @Required annotation is not used to validate field data, but is actually only used to validate the column header exists.  It is also used on the class to validate the file exists. While I think the dual use is not ideal, I realize that a third annotation is not necessary which makes it less of an issue.
Required fields are specified in the GtfsColumnDescriptor for the column, which is created in the GtfsTableDescriptor<T> for that entity type.

@isabelle-dr mentioned another scenario in #1350 regarding a warning for a RecommendedColumn.  I think adding several more specific annotations may be useful.
Currently we have the following:
Current:

Rule
Annotation
Target
Example
Type
Occurs
Notes

File Required
@Required
Class
Agency
Error
Feed
Dual purpose annotation may cause confusion

Column & Value Required
@Required
Field
agencyName
Error
File & Record
Dual purpose annotation may cause confusion

Column & Value Optional
@RequiredColumn
Field
transferType
Error
File

I propose splitting the @Required annotation into @RequiredFile and @RequiredValue annotations, and adding  @RecommendedColumn and potentially a @RecommendedValue annotation would be clearer for readability and testability:
Proposal:

Rule
Annotation
Target
Example
Type
Occurs
Notes

File Required
@RequiredFile
Class
Agency
Error
Feed

Column Required
@RequiredColumn
Field
transferType
Error
File
Column must exist, values are optional

Value Required
@RequiredValue
Field
agencyName
Error
Record
Column must exist, value is required for each record

Column Recommended
@RecommendedColumn
Field
timepoint
Warning
File
Recommended to include column

Value Recommended
@RecommendedValue
Field
?
Warning
Record
Recommended to include value

One potential consideration is documenting these in RULES.md could be confusing? E.g. if multiple fields in multiple files are marked with @RequiredValue we would have to illustrate them all in the required_value error section, with links to the correct area of the specification.  As opposed to having a custom error notice for each situation which gives the ability to provide a specific example/link for each error.
From a development standpoint I think the proposal is much clearer as long as we feel we can document the errors effectively.


Feature - Add --tree option to podman

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:
/kind bug
/kind feature

Description

Docker removed the --tree option along time ago. It basically shows the parent child relationship of the image layers, similar to pstree. It was awesome for hunting down provenance. Now, I use a tool called DockViz which is delivered as a container image from DockerHub - sadly it's not secure because it's third part and you have to run it privileged
Steps to reproduce the issue:

docker pull

docker images --tree (gone and depricated)

podman has no option either, and you can't use dockviz

Describe the results you received:
podman run --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock nate/dockviz images -t
option parsing failed: Unknown option --exit-dir
write child: broken pipe
Describe the results you expected:
Something like:
podman run --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock nate/dockviz images -t
Unable to find image 'nate/dockviz:latest' locally
Trying to pull repository registry.access.redhat.com/nate/dockviz ...
Trying to pull repository registry.access.redhat.com/nate/dockviz ...
Trying to pull repository registry.fedoraproject.org/nate/dockviz ...
Trying to pull repository docker.io/nate/dockviz ...
sha256:902ef37d58ca85e03d0f286651f12754767ccc6704c00e8b78bf45f0ac7e32f1: Pulling from docker.io/nate/dockviz
9e912cc91e6e: Pull complete
Digest: sha256:902ef37d58ca85e03d0f286651f12754767ccc6704c00e8b78bf45f0ac7e32f1
Status: Downloaded newer image for docker.io/nate/dockviz:latest
├─ Virtual Size: 195.9 MB
│ └─ Virtual Size: 195.9 MB
│   ├─ Virtual Size: 362.7 MB
│   │ ├─09fb7aad87c8 Virtual Size: 1.1 GB Tags: registry.access.redhat.com/openshift3/ose-docker-registry:v<IP_ADDRESS>.5
│   │ └─ Virtual Size: 970.1 MB
│   │   ├─e4aa5cb65487 Virtual Size: 970.1 MB Tags: registry.access.redhat.com/openshift3/ose-deployer:v<IP_ADDRESS>.5
│   │   └─e02b7ea3c91f Virtual Size: 988.7 MB Tags: registry.access.redhat.com/openshift3/ose-haproxy-router:v<IP_ADDRESS>.5
│   ├─febdb23e8687 Virtual Size: 208.6 MB Tags: registry.access.redhat.com/openshift3/ose-pod:v<IP_ADDRESS>.5
│   └─391e5989cdec Virtual Size: 226.2 MB Tags: registry.access.redhat.co
Or even better:
podman images --tree
├─ Virtual Size: 195.9 MB
│ └─ Virtual Size: 195.9 MB
│   ├─ Virtual Size: 362.7 MB
│   │ ├─09fb7aad87c8 Virtual Size: 1.1 GB Tags: registry.access.redhat.com/openshift3/ose-docker-registry:v<IP_ADDRESS>.5
│   │ └─ Virtual Size: 970.1 MB
│   │   ├─e4aa5cb65487 Virtual Size: 970.1 MB Tags: registry.access.redhat.com/openshift3/ose-deployer:v<IP_ADDRESS>.5
│   │   └─e02b7ea3c91f Virtual Size: 988.7 MB Tags: registry.access.redhat.com/openshift3/ose-haproxy-router:v<IP_ADDRESS>.5
│   ├─febdb23e8687 Virtual Size: 208.6 MB Tags: registry.access.redhat.com/openshift3/ose-pod:v<IP_ADDRESS>.5
│   └─391e5989cdec Virtual Size: 226.2 MB Tags: registry.access.redhat.co
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):

This sounds perfectly doable, though the display code could get interesting to write

@runcom WDYT

It definitely seems doable!

@haircommander Have you looked into this?

No I have not yet @rhatdan

@haircommander if you are now working on this, Can I try this?

@rhatdan Thanks :). Also feel free to assign me anything urgent if you feel I can work on.

We have an outstanding issue on --mount support for podman run/create?  If you want to tackle that one.

@vrothberg Hi, yes I am looking into this.
I am trying to figure out to map image layers digest to Image, so I can build the dependency.
Will discuss the detail by end of day.
Thanks for pointing out #podman, Just joined #podman on IRC.

Awesome. Thanks, @kunalkushwaha!

I did a draft implementation to find out how this can be implemented.
The expected output
<Tag>  <ID>  <Size> <Short Description from history>
     ├─  <Tag>  <ID>  <Size> <Short Description from history>
     └─  <Tag>  <ID>  <Size> <Short Description from history>

Sample output below
$ sudo podman tree localhost/kk/test2
└─  [localhost/kk/test2:latest] 243d869d1 156
  ├─  [localhost/kk/test2:latest] 268e94b38 3584
  ├─  [localhost/kk/test2:latest] 5182e9677 3584 /bin/sh -c #(nop)  CMD ["/bin/bash"]     # Ideally it should show centos:latest
  ├─  [localhost/kk/test2:latest] <missing> 3584 /bin/sh -c #(nop)  LABEL org.label-schem
  ├─  [localhost/kk/test2:latest] <missing> 208290304 /bin/sh -c #(nop) ADD file:6340c690b0886

While doing this, I found few findings and limitations to show all possible/expected information as below.

OCI image's history have limited information i.e. information like each layer do not have information like  ImageID or Digest associated with it.
History layers do not have Tags associated with it.
Since Digest is not available with each layer, corresponding image ID is hard to find.
many of layers in History actually do not reflect to any real Image or layer in ImageStore

While I tried to use similar logic as dockviz project, I am able to build dependency tree for any image based on history and building lookup table for each image in local registry.
Though few things are not correct and I would like to understand if we can get these information to build the meaningful dependencies.

Is it okay, if we do not show the layers which do not have real reference in local registry? i.e. the layer info present in history but squashed/merged with Image.

This will result in less number of layers in tree, but all layers will have real reference.
This makes implementation easy and while debugging/tracing all information will have some reference to look at.
This will result into above sample output as

$ sudo podman tree localhost/kk/test2
└─  [localhost/kk/test2:latest] 243d869d1 156
  ├─  [localhost/kk/test2:latest] 268e94b38 3584
  ├─  [centos:latest] 5182e9677 3584 /bin/sh -c #(nop)  CMD ["/bin/bash"]

How to get Image Tags from Digest like docker/moby do here moby/daemon/images/image_history.go

@kunalkushwaha, that looks really nice! I think at that point, it might be helpful to look at some code to guide the conversation, so feel free to open a PR where we can continue.
@mtrmac might be interested in this change and have some valuable input.

Can someone describe in exact words what is the child/parent/peer relationship in the tree intended to be based on? (Not necessarily the exact underlying implementation, but the desired semantics at least.) It’s not entirely clear to me in the original example, and @kunalkushwaha’s example seems to be quite different (in particular, the original example clearly uses the top-level image name:tag only once, whereas the other example uses it for all layers).
AFAICS there is a fundamental problem in building the history tags based only on the layer history (ChainID) (which is the only exact way to do that, because the history text is ~arbitrary in principle, and the configs of base images are lost) in that there may exist multiple different images with the same layer set (ChainID) but different configs, and building the history based on ChainID only can’t differentiate between them. (This may not be a problem when the local system has precise “parent image” links, like Docker has for locally-derived (not pulled) images.)
That’s in addition to the smaller (but necessary to handle) output design concern, that even if the parent image is not ambiguous, it may have multiple tags.

How to get Image Tags from Digest like docker/moby do here moby/daemon/images/image_history.go

Given a github.com/containers/storage.Image, the Names array contains (at least per its use in c/image, and perhaps not exclusively, ) name:tag references. Whether you can get the Image object depends on what the input for the lookup is (as discussed above); if it is a layer, the image’s TopLayer should match (but there may be multiple matches!)

if it is a layer, the image’s TopLayer should match (but there may be multiple matches!)

that is storage.Store.ImagesByTopLayer.

@mtrmac my example is not correct due to limitations I explained in https://github.com/containers/libpod/issues/415#issuecomment-428878575. For above example, I just added Image tag to each layer (which is not expected)
As I stated, If we consider only layers which exist in local registry, it will be easier to display information.
( I updated the output in above comment, it should be different image name)
Currently the output looks like below.
$ sudo podman tree localhost/kk/test2
└─  [localhost/kk/test2:latest] 243d869d1 156
   └─ [localhost/kk/test1:latest] 268e94b38 3584
     └─  [centos:latest] 5182e9677 3584 /bin/sh -c #(nop)  CMD ["/bin/bash"]

But it can be modified as , I guess that you meant by a better picture of "parent", "child" & "peer"
$ sudo podman tree localhost/kk/test2
└─  [centos:latest] 5182e9677 3584 /bin/sh -c #(nop)  CMD ["/bin/bash"]
   └─ [localhost/kk/test1:latest] 268e94b38 3584
     └─ [localhost/kk/test2:latest] 243d869d1 156

i.e. Root will be the base image, from which test1:latest image was build. test2:latest image was build from test1:latest here.
if test1:latest & test2:latest are both build from centos:latest then the graph should be
$ sudo podman tree localhost/kk/test2
└─  [centos:latest] 5182e9677 3584 /bin/sh -c #(nop)  CMD ["/bin/bash"]
   └─ [localhost/kk/test1:latest] 268e94b38 3584
   └─ [localhost/kk/test2:latest] 243d869d1 156

@vrothberg  I will create a PR to make discussion easier.

PR made as #1642

This continues to be worked on .

Getting closer.

closing per #1642 being merged. Congrats @kunalkushwaha on fixing the current oldest open issue!


FIX: Adjust reply indicator spacing on iOS

Fixes extra space showing below the reply indicator on iOS. The culprit is safe-area-inset-bottom, iOS mistakenly still adds a value there even when the keyboard is visible. Thankfully it doesn't look like we need to account for safe areas here, the input is still clear of the device's bottom on iOS.

[x] chat-scoped -- core unaffected

View mode

[x] docked (windowed/drawer)

Browsers

[x] safari
[x] chrome
[ ] firefox

Device

[x] desktop – wide screen
[x] mobile – DiscourseHub

Awesome, thanks for looking this, very helpful ❤


Remove pokemon rule from formats.js

Should have been done when https://github.com/Zarel/Pokemon-Showdown/commit/b91c3cff905de36ceb6aac4aefb8b387d734bd41 got added.

Could've just reverted a9e28b

You're not supposed to remove all of them...

Oops

Still missing one.


[Task] Replace require statements with imports - report.js

closed by https://github.com/gabrielcsapo/module-detective/commit/c36aa8f50f34a5070ca5da3b4fac9d84d4f73ab4 (i forgot to create a branch).


Does this still work?

I'd love to run this on my Mac, but I get an error after I download and double-click the .dmg file

It says "disk image couldn't be opened.  The disk image is corrupted"


Create Suggested Link Widget

for incorporating search results from other services. This will most likely include a model change to relate suggested urls to a given TrailUrl.

Merged to Develop


Bump version to 4.5

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
We are adding support for new hardware in the RSI Module repository. This breaks compatibility with existing system definition files. Mutate existing system definition files by rewriting the module model enum.
Why should this Pull Request be merged?
Customers will not be able to load existing system definition files without this change.
What testing has been done?
Load existing system definition file prior to version 4.5 and confirm properties are deserialized correctly.

I will trigger a build and review once I can test the changes.

The tests for Specialty Digital are failing with these changes (tested in 2017, did not test the others). Curiously, if I open and save the test files such that the mutation changes are made the tests then pass. This would appear to point to the mutation not running (properly or at all?) when deployed directly through the API.
The code changes look good (aside from the test failures).

The tests for Specialty Digital are failing with these changes (tested in 2017, did not test the others). Curiously, if I open and save the test files such that the mutation changes are made the tests then pass. This would appear to point to the mutation not running (properly or at all?) when deployed directly through the API.
The code changes look good (aside from the test failures).

I will look into the mutation code and see why it is not running for the tests.

The On Load action doesn't run during deployment (and I don't feel it should). Since the mutation is called in the On Load code and the tests only deploy existing sysdefs, no mutation will happen.

This problem is likely affecting other custom devices that do mutation. Once we have found a solution here, we should apply it to the other custom devices (e.g. the Engine Simulation Toolkit custom device).

OnLoad means "when the configuration front panel is loaded" not "when the system definition is loaded". Since we don't load the front panel for the custom device in the automated test we never mutate the system definition. We could try to manually invoke the "On Load" action as part of the deployment in the automated testing tools.


Markov use should be limited to actual tables.

Markov analysis only works with actual tables that exist in the database, it can't work against queries.
There should be a warning in Builder UI, or just block the user from using this analysis to a node that's not a source node with a query like SELECT * FROM mytable
cc @ohasselblad @saleiva

Isn't this a bug and not an enhancement?

It's this way by design as of today. Andy can add more details.
Right now if you try to run Markov on a node (or if every row have at least one null value in the time series), the analysis won't work... and won't end.

Then I think we should fix it in the analysis and not in the UI :). That
goes against the general paradigm of the analysis workflows
On Tue, Jan 3, 2017, 3:55 PM Abel Vázquez Montoro<EMAIL_ADDRESS>wrote:

It's this way by design as of today. Andy can add more details.
Right now if you try to run Markov on a node (or if every row have at
least one null value in the time series), the analysis won't work... and
won't end.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/cartodb/issues/11171#issuecomment-270131701,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIENdQnU6Fcuf4bRvzVJ0_QV2XEyBttks5rOmFsgaJpZM4LZq_p
.

It's by design and part of the limitations we've experienced with PL/Python.. We've struggled with function signatures which are flexible enough to pass database data through to a Python environment, and settled on the current form which queries against the database with the Python portion, which doesn't allow for CTEs to be used.
Some of the functions like kmeans and segmentation can get around it because they only need the column info passed as arrays, but markov, moran, gwr and spatial interactions (as PRs now) need to construct more complicated objects about the spatial neighborhood that we couldn't find an easy way to cram it into the signature of a pl/python function.

summoing @javisantana

Btw, is this behaviour replicated in any other analysis? Moran?

Umh, I see it accepts SQL queries: https://github.com/CartoDB/camshaft/blob/master/lib/node/nodes/sql/moran.sql#L5

sorry: https://github.com/CartoDB/camshaft/blob/master/lib/node/nodes/sql/spatial-markov-trend.sql#L7

But the query MUST be like SELECT * FROM my_real_table in order to work

it can be an arbitrary query

@AbelVM could you provide a non-working example?

WITH tmp AS(
    SELECT * FROM my_real_table
)
SELECT * FROM tmp

does not work :(

what is the error?

no message back, it just stays there... running forever

This works from my account same as not doing the CTE.
SELECT * FROM cdb_crankshaft.cdb_spatialmarkovtrend('WITH cte as (select * from zip_zhvi_singlefamilyresidence_nyc_region) select * FROM cte', Array['_2015_01', '_2015_02', '_2015_03', '_2015_04', '_2015_05', '_2015_06', '_2015_07'])

@AbelVM, is that an actual table with valid columns? Looks like there's a different problem with error reporting on the existence of columns/tables.

what if you create the _2015_XX columns on the fly?
On the other hand, the real value test here would be running the analysis from Builder, not SQL.

on the fly meaning with 'alter table .. add column _2015_XX' and then run the analysis? as long as the column exists in that table at the time of the analysis running, all should be ok

Following our Slack chat, this pseudocode query should fail:
WITH
tmp1 AS(
    SELECT
    *,
    col1 as c1,
    col2 as c2,
    ...
    colN as cN
FROM my_real_table
),
tmp2 AS(
    SELECT * FROM tmp1
)
SELECT * FROM tmp2

when applying Markov to columns c1 to cN

Yep, that'll fail. If there's a create table in there and it's cartodbfy'd (or has an appropriate id column and valid geoms in 4326) it should work.

So the thing is that it's not the table the one that should be a real table, but the columns that should be REAL columns, am I right?

Yep, you're right. Whatever query is passed should have the columns specified in the second argument. Otherwise it should fail and report that the column doesn't exist. Just opened a ticket about that: https://github.com/CartoDB/crankshaft/issues/156

Same behavior in Moran, from this simplest node:
SELECT
*,
column_A as column_B
FROM myDataset

You can not apply Moran to column_B. It does not fail, gives no message back, but it keeps running forever and ever.


Ensure filters aren't run on missing data

Related to #51, here is one way of potentially handling inputs that do contain NaN.  This makes no interpolation assumptions, but simply only marks events continuous chunks of the input series.
Additions

Add handling of NaN in list_events input series

Testing

All existing tests pass
An additional test with missing data should probably be added

Todos

Add  test case for series with missing data

Checklist

[x] PR has an informative and human-readable title
[x] PR is well outlined and documented. See #12 for an example
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows project standards (see CONTRIBUTING.md)
[x] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output) using numpy docstring formatting
[x] Placeholder code is flagged / future todos are captured in comments
[x] Reviewers requested with the Reviewers tool :arrow_right:

@hellkite500 My preference to reject to discontinuous series and let users either fill or implement this type of groupby logic outside the list events methods.

A note on pandas groupby/apply -- it isn't guaranteed to always return the same data type.  In some cases, it is possible for the apply to return a Series where in other's it may return a Dataframe.  This largely depends on the input and the resulting set of outputs from the input.  But that means to use it in this setting, one would need to check if the event_points is empty (in which case event_points would be a Series) or not (in which case it will be the expected DataFrame)

After further conversation, I think we should warn about missing data and offer this functionality through some type of evaluation_tools.preprocessing module.
My thoughts:

The underlying filters won't break if NaN is present
Dealing with missing data is a science. I'm afraid integrating any default handling of missing data could be perceived as an endorsement of that method
I think we should avoid embedding preprocessing into event detection as much as possible (this version of event detection actually purged a lot of preprocessing)
This particular method of preprocessing/NaN handling has its own issues that I think can be more cleanly tested and maintained in a separate module
Raising a warning about NaN is any easy compromise to avoid "surprises"

In particular, I think this method will need to somehow check that the length of each continuous portion makes sense given the parameters (window and halflife). As near as I can tell the method does not distinguish between gaps and a degraded signal. It is not uncommon for missing data to occur during high-flow events, this method might split those events. This method has its own set of parameters that could be tweaked depending upon the nature of the underlying signal and the events you're trying to detect. This method does not seem any less opinionated in its treatment of NaN than other methods of no-data handling.

The underlying filters won't break if NaN is present
What about the case where NaN causes an  "event" of all 0  flow's  to be identified?  Is  the an artifact of the filter's neglecting the missing data?   What does it mean to "break"  the filters haha?

Dealing with missing data is a science. I'm afraid integrating any default handling of missing data could be perceived as an endorsement of that method
I  don't disagree.  Providing a preprocessing module isn't a bad idea.  I still think it is worth integrating that module via kwargs or  function overloads to present the user a  simple calling sequence to get events.

I think we should avoid embedding preprocessing into event detection as much as possible (this version of event detection actually purged a lot of preprocessing)
As per the previous comment, would it  make sense to provide some more tightly integrated options to simplify the calling stack?

This particular method of preprocessing/NaN handling has its own issues that I think can be more cleanly tested and maintained in a separate module
Agreed.

Raising a warning about NaN is any easy compromise to avoid "surprises"
A warning or an actual exception/error?

Zero flow events resulting from NaN are caused by the NaN in the original signal, not the event detection algorithm directly. By "break", I meant a NaN won't halt the entire process. Event detection and the underlying filters generate models of time series components. As with all models, garbage-in begets garbage-out.
I think simplifying the calling stack is a matter of personal preference worth qualifying. Which of these would you consider "simpler"?
# Example A
events = list_events(series, halflife, window, no_data_method, keyword1, keyword2)

# Example B
preprocessed_series = no_data_method(series, keyword1, keyword2)
events = preprocessed_series.groupby('subseries').apply(list_events, halflife, window)

I think Example A's interface seems simpler, but the code to handle no_data_method inside of list_events may be quite complex, especially if we're going to support multiple methods to handle NaNs. I think this will be difficult to test and maintain in the event detection module. I think Example B offers more utility and will be easier to test and maintain.
Another way to offer a more tightly integrated calling stack is through evaluation_tools.workflows. These are pre-developed data-driven computational workflows with prescribed steps for data retrieval, preprocessing, processing, analysis, and visualization. The goal here is to model the workflow as a DAG.
# Example C
run_my_event_based_analysis(observations='NWIS', simulations='NWMv2.1', date_range=('1970-01-01','2000-01-01'),
    output='output_directory')

I vote for warning about NaN, but not raising an exception. We may want to raise an exception if a significant portion of the series is all NaN.

Will revisit in a different part of the events subpackage.


Documentation Builds failing due to tornado upgrade

Seems to be a problem with Tornado 6, while 5.1.1 works.  Tornado is needed by nbconvert which is used by sphinx to render the Jupyter notebooks in the documentation.
Tornado is not a ctapipe dependency, but perhaps we can make a hacky fix to this by adding a "conda install tornado=5.1.1" before the doc builds until they fix this.

I fixed it by requiring nbconvert > 5.4 which works with tornado 6


Ctrl +  combination is only detected if  is kept pressed first and then ctrl instead of the other way around.

This happens running the tutorial 74 under Ubuntu 20.10. Expected behaviour would be to keep pressing ctrl first and then the key, but then the bracket-lib only detects  instead of ctrl+ in that case. The same happens with shift.

A workaround is to turn on the "advanced input API" (call with_advanced_input(true) on the BTermBuilder) and add the following code to the game-loop:
    let mut input = INPUT.lock();

    ctx.shift = input.key_pressed_set().contains(&VirtualKeyCode::LShift)
                || input.key_pressed_set().contains(&VirtualKeyCode::RShift);

    #[allow(clippy::single_match)]
    input.for_each_message(|event| match event {
        BEvent::CloseRequested => ctx.quitting = true,
        _ => (),
    });

Do the equivalent for ctx.ctrl. This isn't 100% correct though, but works ok for me (once in a while the release of the shift-key goes missing for some reason, I've not yet debugged why as I intend to switch all the input handling to the advanced input API).

A workaround is to turn on the "advanced input API" (call with_advanced_input(true) on the BTermBuilder) and add the following code to the game-loop:
    let mut input = INPUT.lock();

    ctx.shift = input.key_pressed_set().contains(&VirtualKeyCode::LShift)
                || input.key_pressed_set().contains(&VirtualKeyCode::RShift);

    #[allow(clippy::single_match)]
    input.for_each_message(|event| match event {
        BEvent::CloseRequested => ctx.quitting = true,
        _ => (),
    });

Do the equivalent for ctx.ctrl. This isn't 100% correct though, but works ok for me (once in a while the release of the shift-key goes missing for some reason, I've not yet debugged why as I intend to switch all the input handling to the advanced input API).

A workaround is to turn on the "advanced input API" (call with_advanced_input(true) on the BTermBuilder) and add the following code to the game-loop:
    let mut input = INPUT.lock();

    ctx.shift = input.key_pressed_set().contains(&VirtualKeyCode::LShift)
                || input.key_pressed_set().contains(&VirtualKeyCode::RShift);

    #[allow(clippy::single_match)]
    input.for_each_message(|event| match event {
        BEvent::CloseRequested => ctx.quitting = true,
        _ => (),
    });

Do the equivalent for ctx.ctrl. This isn't 100% correct though, but works ok for me (once in a while the release of the shift-key goes missing for some reason, I've not yet debugged why as I intend to switch all the input handling to the advanced input API).

Thanks for your help! This works well for shift and control. I haven't yet reproduced the missing shift release, but will keep an eye on it, so thank you for bringing that up.

A workaround is to turn on the "advanced input API" (call with_advanced_input(true) on the BTermBuilder) and add the following code to the game-loop:
    let mut input = INPUT.lock();

    ctx.shift = input.key_pressed_set().contains(&VirtualKeyCode::LShift)
                || input.key_pressed_set().contains(&VirtualKeyCode::RShift);

    #[allow(clippy::single_match)]
    input.for_each_message(|event| match event {
        BEvent::CloseRequested => ctx.quitting = true,
        _ => (),
    });

Do the equivalent for ctx.ctrl. This isn't 100% correct though, but works ok for me (once in a while the release of the shift-key goes missing for some reason, I've not yet debugged why as I intend to switch all the input handling to the advanced input API).

Thanks for your help! This works well for shift and control. I haven't yet reproduced the missing shift release, but will keep an eye on it, so thank you for bringing that up.

Labeling this as an enhancement because the library really needs modifier key handling revisited. Advanced input is the way to go for a lot of this if you want really slick results (I tried to keep the normal mode simple), but hopefully I can find some middle ground. I'll try to get to this after 0.8.2 ships.


Character

Description
This feature must enable users to use their characters to play the game, allow players to move around the map using keyboards, and interact with objects including grab or take weapons and rewards to gain advantages and move to the next round. As character moving around, they should not go out boundaries of the screen or go through the objects to enhance the user experience.
SubFeature/component (optional)

Design and implement the character
Moving mechanism using WASD keys correctly (not out of screen boundaries or pass through obstacle object)
Allow the character to pick up weapons using Z (for knife) and X (for weapon) and interact with other components.

Examples (optional)

Part/Feature: As users press W, the character must move upward, or press Z then players can take their knife out.
UI display: the character shows up when the player starts the game and moves around to illustrate the player's actions. The character must not go through obstacle objects or out of boundaries.

Dependencies

Creation of Map #9
Creation of Weapon #2

Milestones
List of sub-features you intend to have done and in Master by the end of the sprint.

[ ] Develop components to display the UI of Character, statistics(Aug. 13)
[ ] Character should be able to move with keys WASD around the map, does not go through boundaries or pass through obstacle object (Aug. 17)
[ ] Character can interact with some objects (maybe a few only like to grab and put down, not too complex) (Aug. 22)
[ ] Integration and testing of all components together (Aug. 24)
[ ]  Documentation (Aug. 26)

Completion Deadline: Aug. 28 3pm
Extras (optional)

[ ] Can develop more about the ability to interact with other objects including weapons and animals if can
[ ] Controls are mapped from a config file.

Documentation
TBD
Members

Vu Khanh Vy Ho (@VuKhanhVyHo)
Nadia D'Mello(@nadiadmello)
Manya Khosla (@manya-k)
Jordan Cole (@Jordamnmn)
Sioryn Willett (@SIN-Willett )

One of the subtasks, "Design and Implement the Character" will probably need to be broken down further as there are multiple elements to this, such as creation of the character entity, character visuals and animation, physics, and so on. Movement is not really a task as this is already implemented in the base game, unless you intend to significantly rework the movement mechanic.
Aside from these issues, the feature ticket structure and description are looking good,  make sure to update it with links to the task tickets and documentation as they are created. This ticket is approved and you can start creating the associated task tickets.

Done


removed time sleep function, reduced time step

Description
Fixed some issues with the control() method:

lowered the duration of the time step
replaced time.sleep by a new method which sleep while keeping the robot mirrored

atm the mirroring does not work in my account. Let's test it together


{main} Fix timer

Description
Fix the incorrect timing logic. Previous it only takes invoke duration into account, while forgetting about the init duration.
This PR fixes the timing logic to include both init and invoke duration.
Testing Guide
Before:
> az version -h --verbose
...
command ran in 0.881 seconds.

After:
> az version -h --verbose
...
Command ran in 1.679 seconds (init: 0.824, invoke: 0.855)

add to S171

/azp run

Because azdev doesn't honor azure-cli repo's .flake8 (https://github.com/Azure/azure-cli-dev-tools/issues/209), disabling E402 doesn't work in the CI and causes the failure:
/home/vsts/work/1/s/src/azure-cli/azure/cli/__main__.py:13:1: E402 module level import not at top of file
/home/vsts/work/1/s/src/azure-cli/azure/cli/__main__.py:14:1: E402 module level import not at top of file
/home/vsts/work/1/s/src/azure-cli/azure/cli/__main__.py:16:1: E402 module level import not at top of file
/home/vsts/work/1/s/src/azure-cli/azure/cli/__main__.py:17:1: E402 module level import not at top of file
/home/vsts/work/1/s/src/azure-cli/azure/cli/__main__.py:18:1: E402 module level import not at top of file
/home/vsts/work/1/s/src/azure-cli/azure/cli/__main__.py:19:1: E402 module level import not at top of file
6     E402 module level import not at top of file

Thus, per-file-ignores won't work wither.
Since there is no support for file-level # flake8: noqa to disable certain errors (https://gitlab.com/pycqa/flake8/-/issues/399), temporarily comply to flake8's E402 rule to make the CI pass.

Would it better to calculate the execution time under certain situations such as debug mode, --verbose mode, etc.
But this modifcation doesn't bring any (significant) regression, So, LGTM.

The execution time is calculated regardless of the execution mode (verbose, debug). --verbose and --debug only decide if the execution time is printed.
Anyway, the overhead of calling timeit.default_timer() is pretty small. So we don't need to worry about it.


E2 sound extensions

Exports some SoundCore functions
Adds SoundCore functions from modified xtrasound core (https://steamcommunity.com/sharedfiles/filedetails/?id=2221932128)
Adds EmitSound core - a simplier way to play sounds

I don't think we need a new extension for the emitsound functions. Thoughts, @Vurv78 ?

I agree, don't see any reason for them to be separate, especially if having them separate is will need you to export fields in E2Lib.

As for the rest of the unused exported fields, why? Maybe I'd understand IsAllowed in case you want to configure that as an admin, but why not just make a hook then? And I really don't like the idea of other addons depending on internal code like that (especially with #2555)

Originally soundcore stuff was exported because extra sound functions (soundDsp, etc.) were in separate core.


Javascript linting

This PR doesn't have any functional changes, only:

changes to code style (based on aldryn-boilerplate-bootstrap3)
linting setup and rules to enforce the code style
a bit of docs.

consists of

https://github.com/FinalAngel/django-cms/pull/46
https://github.com/FinalAngel/django-cms/pull/47
https://github.com/FinalAngel/django-cms/pull/48
https://github.com/FinalAngel/django-cms/pull/49
https://github.com/FinalAngel/django-cms/pull/53
https://github.com/FinalAngel/django-cms/pull/54

/cc @yakky @FinalAngel

LGTM but tests fail

@FinalAngel Failures not due to this PR but by a previous merge

LGTM @yakky +1 for merge


Support for other Cypher DBs

[This is a query rather than an issue, please close if that's a problem (I can't log-in to gitter as it only supports OAuth and my accounts which support that would not allow its requested permissions).]
Would there be any interest in PRs which add support for other Cypher Graph DBs?
One would need some mechanism for handling the peculiarities of particular DBs, something like
case DBType.name
when :neo4j
  def indexes_cypher
    "CALL(db.indexes)"
  end
when :otherdb
  def indexes_cypher
    "SHOW INDEX INFO"
  end
end

Would there be a preferred mechanism?

@jjg-dressipi thanks for the initiative. Do you think the major compatibility problems are at that high level? The 1st thing I would investigate is if neo4j-ruby-driver can be used or a completely new driver has to be written.

That does seem to be the case, I have a fork of activegraph here and using the seabolt driver (in fact a minor bugfix is needed, PR here), I can run the test-suite and at the moment have 97% of the tests passing.  The code in my branch is a bit messy, done in a hurry, but could be made more consistent; hence my query.

thx @jjg-dressipi good find. Unfortunately, nobody at neo4j is maintaining seabolt anymore. So there is nobody to accept those PRs.  If you want to team up on that and maintain seabolt than it could work.
Alternatively, I think we can fix the seabolt error in neo4j-ruby-driver by implementing the entire none method.
What would be good is if you could add to travis (https://github.com/neo4jrb/neo4j-ruby-driver/blob/master/.travis.yml) the option to run specs on Memgraph DB.

@klobuczek , thanks for your response.  How strange that Neo4j has abandoned this key piece of infrastructure!  I'm not sure that I'd be the best person to take this over though, this is a work thing (so I'd need permission from work to spend time on it) and I have a horror of CMake, I'd feel compelled to replace it with autoconf and make, and then other people would become upset :smile:
As to the alternatives, that could be good -- I have other commitments at the moment but will look at the travis setup as soon as those are done.  And for the re-implementation of none, perhaps I should raise an issue against neo4j-ruby-driver?


[Bug]: When SRID is not 0, spatial positions will swap

ODC version
odc423
OB version
mysql8.0
What happened?

What did you expect to happen?
Spatial data is not interchangeable
How can we reproduce it (as minimally and precisely as possible)?
Add data to the table of GIS type data
Anything else we need to know?
No response
Cloud
No response


Generating subscription name doesn't work when trigger i…

…s configured

This change is

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


strconv: fix a typo mistake in comments

Fix a typo mistake in comments

Not a typo. See https://en.wikipedia.org/wiki/Interval_(mathematics)#Notations_for_intervals


Review API documentation for PyT serving support for T4R models

Reviewed API documentation (generated by docstrings in code) for Transformers4Rec/transformers4rec codebase. Details are available here: https://docs.google.com/document/d/1GzM1q9Pc6amecRspbWKG0PSXbU-fCy13hSOC6UMnWWU/edit
Will review API documentation for merlin_standard_lib package next.


note: change sched_note_counter to a macro

Summary
Change inline functions to macros to unify code style
Impact
none
Testing
sim/note

[Experimental Bot, please feedback here]
This PR needs more information to meet the NuttX requirements. Here's a breakdown:
What's Missing & How to Improve:

Summary:

Specificity:  "Unify code style" is vague. Which inline functions? In what part of the codebase (drivers, kernel, etc.)?
Justification: Why is changing inline functions to macros necessary? Is it just about style, or are there performance implications?
Example: "Change inline functions for semaphore operations in sched/ to macros for consistency with other synchronization primitives."

Impact:

Overly General: Even if there's no user-facing impact, be specific.
Example:

"Impact on build: None."
"Impact on hardware:  No changes to architecture or board support."
"Impact on documentation: No updates required."

Testing:

Insufficient Detail:

Build Host: State your OS, CPU architecture, and compiler version.
Target:  "sim/note" isn't clear.  Which simulator?  What's the "note" configuration?

Missing Logs:  Provide actual testing logs (even if they're short) to demonstrate the change's effect.

Example Improvements:
## Summary

This PR changes inline functions for semaphore management in `sched/semaphore/` to macros. This aligns the code style with other synchronization primitives in NuttX and improves code readability.

## Impact

* Is new feature added? NO
* Is existing feature changed? NO
* Impact on user: NO
* Impact on build: NO
* Impact on hardware: NO
* Impact on documentation: NO
* Impact on security: NO
* Impact on compatibility: NO

## Testing

I confirm that changes are verified on my local setup and work as intended:

* Build Host(s): Linux (Ubuntu 20.04), x86_64, GCC 9.4.0
* Target(s):  sim/qemu-arm (Cortex-M3 configuration)

Testing logs before change:

(Provide a snippet of relevant log output)

Testing logs after change:

(Provide a snippet showing the effect of the change)


feat: :sparkles: bootstrap profile page (recept, profile edit)

Signed-off-by: Soren Abedi<EMAIL_ADDRESS>

bootstraped profile page


Replace apt module with apt-get shell command in test pre-requisites playbook

What this PR does / why we need it:

The ansible apt module executes the apt-get update command as part of package installation,
which randomly fails due to failed update of one or more packages (Hash sum mismatch)

This change replaces the package installation into two separate steps, executed with the
shell module to : a) perform update by ignoring errors b) Install package

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #628
Special notes for your reviewer:
Some of the other hacks for this issue included clearing the /var/lib/apt/lists folder and repeating the update, but were found to be unreliable.

Here is a verbose O/P for the two tasks mentioned in the PR :
23:23:13 TASK [Run apt-get update via shell] ********************************************
23:23:13 task path: /var/lib/[*******]/openebs/e2e/ansible/playbooks/hyperconverged/test-k8s-percona-mysql-pod/k8s-percona-pod-prerequisites.yml:7
23:23:29  [WARNING]: Consider using apt module rather than running apt-get
23:23:29 fatal: [localhost -> None]: FAILED! => {"changed": true, "cmd": "apt-get update", "delta": "0:00:15.095275", "end": "2017-10-13 17:53:28.715619", "failed": true, "rc": 100, "start": "2017-10-13 17:53:13.620344", "stderr": "E: Failed to fetch http://archive.[*******].com/[*******]/dists/xenial-updates/universe/binary-amd64/by-hash/SHA256/dcc752c964cdbe673e8c28a7dfade59cd6ff6c914d4e602928a36f7b87bf1eac  Hash Sum mismatch\nE: Some index files failed to download. They have been ignored, or old ones used instead.", "stderr_lines": ["E: Failed to fetch http://archive.[*******].com/[*******]/dists/xenial-updates/universe/binary-amd64/by-hash/SHA256/dcc752c964cdbe673e8c28a7dfade59cd6ff6c914d4e602928a36f7b87bf1eac  Hash Sum mismatch", "E: Some index files failed to download. They have been ignored, or old ones used instead."], "stdout": "Get:1 http://security.[*******].com/[*******] xenial-security InRelease [102 kB]\nHit:2 http://archive.[*******].com/[*******] xenial InRelease\nGet:3 http://archive.[*******].com/[*******] xenial-updates InRelease [102 kB]\nGet:4 http://archive.[*******].com/[*******] xenial-backports InRelease [102 kB]\nGet:6 http://security.[*******].com/[*******] xenial-security/main Sources [97.4 kB]\nGet:7 http://security.[*******].com/[*******] xenial-security/restricted Sources [2,600 B]\nGet:8 http://security.[*******].com/[*******] xenial-security/universe Sources [43.4 kB]\nGet:9 http://security.[*******].com/[*******] xenial-security/multiverse Sources [1,144 B]\nGet:10 http://security.[*******].com/[*******] xenial-security/main amd64 Packages [370 kB]\nGet:11 http://archive.[*******].com/[*******] xenial-updates/main Sources [278 kB]\nGet:12 http://archive.[*******].com/[*******] xenial-updates/restricted Sources [3,404 B]\nGet:13 http://security.[*******].com/[*******] xenial-security/main Translation-en [164 kB]\nGet:14 http://archive.[*******].com/[*******] xenial-updates/universe Sources [176 kB]\nGet:15 http://archive.[*******].com/[*******] xenial-updates/multiverse Sources [7,204 B]\nGet:16 http://archive.[*******].com/[*******] xenial-updates/main amd64 Packages [642 kB]\nGet:17 http://archive.[*******].com/[*******] xenial-updates/main Translation-en [268 kB]\nGet:18 http://security.[*******].com/[*******] xenial-security/restricted amd64 Packages [7,352 B]\nGet:19 http://security.[*******].com/[*******] xenial-security/universe amd64 Packages [175 kB]\nGet:20 http://security.[*******].com/[*******] xenial-security/universe Translation-en [92.5 kB]\nGet:21 http://security.[*******].com/[*******] xenial-security/multiverse amd64 Packages [2,756 B]\nGet:22 http://archive.[*******].com/[*******] xenial-updates/restricted amd64 Packages [7,972 B]\nGet:23 http://archive.[*******].com/[*******] xenial-updates/universe amd64 Packages [540 kB]\nErr:23 http://archive.[*******].com/[*******] xenial-updates/universe amd64 Packages\n  Hash Sum mismatch\nGet:24 http://archive.[*******].com/[*******] xenial-updates/universe Translation-en [219 kB]\nGet:25 http://archive.[*******].com/[*******] xenial-updates/multiverse amd64 Packages [15.3 kB]\nGet:26 http://archive.[*******].com/[*******] xenial-backports/main Sources [3,432 B]\nGet:27 http://archive.[*******].com/[*******] xenial-backports/universe Sources [4,376 B]\nGet:28 http://archive.[*******].com/[*******] xenial-backports/main amd64 Packages [4,860 B]\nGet:29 http://archive.[*******].com/[*******] xenial-backports/universe amd64 Packages [5,896 B]\nGet:30 http://archive.[*******].com/[*******] xenial-backports/universe Translation-en [3,060 B]\nGet:5 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [8,942 B]\nGet:31 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 Packages [6,578 B]\nFetched 3,457 kB in 13s (263 kB/s)\nReading package lists...", "stdout_lines": ["Get:1 http://security.[*******].com/[*******] xenial-security InRelease [102 kB]", "Hit:2 http://archive.[*******].com/[*******] xenial InRelease", "Get:3 http://archive.[*******].com/[*******] xenial-updates InRelease [102 kB]", "Get:4 http://archive.[*******].com/[*******] xenial-backports InRelease [102 kB]", "Get:6 http://security.[*******].com/[*******] xenial-security/main Sources [97.4 kB]", "Get:7 http://security.[*******].com/[*******] xenial-security/restricted Sources [2,600 B]", "Get:8 http://security.[*******].com/[*******] xenial-security/universe Sources [43.4 kB]", "Get:9 http://security.[*******].com/[*******] xenial-security/multiverse Sources [1,144 B]", "Get:10 http://security.[*******].com/[*******] xenial-security/main amd64 Packages [370 kB]", "Get:11 http://archive.[*******].com/[*******] xenial-updates/main Sources [278 kB]", "Get:12 http://archive.[*******].com/[*******] xenial-updates/restricted Sources [3,404 B]", "Get:13 http://security.[*******].com/[*******] xenial-security/main Translation-en [164 kB]", "Get:14 http://archive.[*******].com/[*******] xenial-updates/universe Sources [176 kB]", "Get:15 http://archive.[*******].com/[*******] xenial-updates/multiverse Sources [7,204 B]", "Get:16 http://archive.[*******].com/[*******] xenial-updates/main amd64 Packages [642 kB]", "Get:17 http://archive.[*******].com/[*******] xenial-updates/main Translation-en [268 kB]", "Get:18 http://security.[*******].com/[*******] xenial-security/restricted amd64 Packages [7,352 B]", "Get:19 http://security.[*******].com/[*******] xenial-security/universe amd64 Packages [175 kB]", "Get:20 http://security.[*******].com/[*******] xenial-security/universe Translation-en [92.5 kB]", "Get:21 http://security.[*******].com/[*******] xenial-security/multiverse amd64 Packages [2,756 B]", "Get:22 http://archive.[*******].com/[*******] xenial-updates/restricted amd64 Packages [7,972 B]", "Get:23 http://archive.[*******].com/[*******] xenial-updates/universe amd64 Packages [540 kB]", "Err:23 http://archive.[*******].com/[*******] xenial-updates/universe amd64 Packages", "  Hash Sum mismatch", "Get:24 http://archive.[*******].com/[*******] xenial-updates/universe Translation-en [219 kB]", "Get:25 http://archive.[*******].com/[*******] xenial-updates/multiverse amd64 Packages [15.3 kB]", "Get:26 http://archive.[*******].com/[*******] xenial-backports/main Sources [3,432 B]", "Get:27 http://archive.[*******].com/[*******] xenial-backports/universe Sources [4,376 B]", "Get:28 http://archive.[*******].com/[*******] xenial-backports/main amd64 Packages [4,860 B]", "Get:29 http://archive.[*******].com/[*******] xenial-backports/universe amd64 Packages [5,896 B]", "Get:30 http://archive.[*******].com/[*******] xenial-backports/universe Translation-en [3,060 B]", "Get:5 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [8,942 B]", "Get:31 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 Packages [6,578 B]", "Fetched 3,457 kB in 13s (263 kB/s)", "Reading package lists..."]}
23:23:29 ...ignoring

23:23:29 TASK [Install python-pip on K8S-minion] ****************************************
23:23:29 task path: /var/lib/[*******]/openebs/e2e/ansible/playbooks/hyperconverged/test-k8s-percona-mysql-pod/k8s-percona-pod-prerequisites.yml:13
23:23:55 changed: [localhost -> None] => (item=python-pip) => {"changed": true, "cmd": "apt-get install -y python-pip", "delta": "0:00:25.169468", "end": "2017-10-13 17:53:54.318902", "item": "python-pip", "rc": 0, "start": "2017-10-13 17:53:29.149434", "stderr": "debconf: unable to initialize frontend: Dialog\ndebconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)\ndebconf: falling back to frontend: Readline", "stderr_lines": ["debconf: unable to initialize frontend: Dialog", "debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)", "debconf: falling back to frontend: Readline"], "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nThe following additional packages will be installed:\n  build-essential dpkg-dev g++ g++-5 libalgorithm-diff-perl\n  libalgorithm-diff-xs-perl libalgorithm-merge-perl libdpkg-perl libexpat1\n  libexpat1-dev libfile-fcntllock-perl libpython-all-dev libpython-dev\n  libpython2.7 libpython2.7-dev libstdc++-5-dev python-all python-all-dev\n  python-dev python-pip-whl python-pkg-resources python-setuptools\n  python-wheel python2.7-dev\nSuggested packages:\n  debian-keyring g++-multilib g++-5-multilib gcc-5-doc libstdc++6-5-dbg\n  libstdc++-5-doc python-setuptools-doc\nThe following NEW packages will be installed:\n  build-essential dpkg-dev g++ g++-5 libalgorithm-diff-perl\n  libalgorithm-diff-xs-perl libalgorithm-merge-perl libdpkg-perl libexpat1-dev\n  libfile-fcntllock-perl libpython-all-dev libpython-dev libpython2.7\n  libpython2.7-dev libstdc++-5-dev python-all python-all-dev python-dev\n  python-pip python-pip-whl python-pkg-resources python-setuptools\n  python-wheel python2.7-dev\nThe following packages will be upgraded:\n  libexpat1\n1 upgraded, 24 newly installed, 0 to remove and 137 not upgraded.\nNeed to get 41.5 MB of archives.\nAfter this operation, 91.8 MB of additional disk space will be used.\nGet:1 http://archive.[*******].com/[*******] xenial-updates/main amd64 libexpat1 amd64 2.1.0-7[*******]<IP_ADDRESS> [71.2 kB]\nGet:2 http://archive.[*******].com/[*******] xenial-updates/main amd64 libstdc++-5-dev amd64 5.4.0-6[*******]1~16.04.4 [1,426 kB]\nGet:3 http://archive.[*******].com/[*******] xenial-updates/main amd64 g++-5 amd64 5.4.0-6[*******]1~16.04.4 [8,300 kB]\nGet:4 http://archive.[*******].com/[*******] xenial/main amd64 g++ amd64 4:5.3.1-1[*******]1 [1,504 B]\nGet:5 http://archive.[*******].com/[*******] xenial-updates/main amd64 libdpkg-perl all 1.18.4[*******]1.2 [195 kB]\nGet:6 http://archive.[*******].com/[*******] xenial-updates/main amd64 dpkg-dev all 1.18.4[*******]1.2 [584 kB]\nGet:7 http://archive.[*******].com/[*******] xenial/main amd64 build-essential amd64 12.1[*******]2 [4,758 B]\nGet:8 http://archive.[*******].com/[*******] xenial/main amd64 libalgorithm-diff-perl all 1.19.03-1 [47.6 kB]\nGet:9 http://archive.[*******].com/[*******] xenial/main amd64 libalgorithm-diff-xs-perl amd64 0.04-4build1 [11.0 kB]\nGet:10 http://archive.[*******].com/[*******] xenial/main amd64 libalgorithm-merge-perl all 0.08-3 [12.0 kB]\nGet:11 http://archive.[*******].com/[*******] xenial-updates/main amd64 libexpat1-dev amd64 2.1.0-7[*******]<IP_ADDRESS> [115 kB]\nGet:12 http://archive.[*******].com/[*******] xenial/main amd64 libfile-fcntllock-perl amd64 0.22-3 [32.0 kB]\nGet:13 http://archive.[*******].com/[*******] xenial-updates/main amd64 libpython2.7 amd64 2.7.12-1[*******]0~16.04.1 [1,070 kB]\nGet:14 http://archive.[*******].com/[*******] xenial-updates/main amd64 libpython2.7-dev amd64 2.7.12-1[*******]0~16.04.1 [27.8 MB]\nGet:15 http://archive.[*******].com/[*******] xenial/main amd64 libpython-dev amd64 2.7.11-1 [7,728 B]\nGet:16 http://archive.[*******].com/[*******] xenial/main amd64 libpython-all-dev amd64 2.7.11-1 [992 B]\nGet:17 http://archive.[*******].com/[*******] xenial/main amd64 python-all amd64 2.7.11-1 [978 B]\nGet:18 http://archive.[*******].com/[*******] xenial-updates/main amd64 python2.7-dev amd64 2.7.12-1[*******]0~16.04.1 [276 kB]\nGet:19 http://archive.[*******].com/[*******] xenial/main amd64 python-dev amd64 2.7.11-1 [1,160 B]\nGet:20 http://archive.[*******].com/[*******] xenial/main amd64 python-all-dev amd64 2.7.11-1 [1,000 B]\nGet:21 http://archive.[*******].com/[*******] xenial-updates/universe amd64 python-pip-whl all 8.1.1-2[*******]0.4 [1,110 kB]\nGet:22 http://archive.[*******].com/[*******] xenial-updates/universe amd64 python-pip all 8.1.1-2[*******]0.4 [144 kB]\nGet:23 http://archive.[*******].com/[*******] xenial/main amd64 python-pkg-resources all 20.7.0-1 [108 kB]\nGet:24 http://archive.[*******].com/[*******] xenial/main amd64 python-setuptools all 20.7.0-1 [169 kB]\nGet:25 http://archive.[*******].com/[*******] xenial/universe amd64 python-wheel all 0.29.0-1 [48.0 kB]\nFetched 41.5 MB in 12s (3,295 kB/s)\n(Reading database ... \r(Reading database ... 5%\r(Reading database ... 10%\r(Reading database ... 15%\r(Reading database ... 20%\r(Reading database ... 25%\r(Reading database ... 30%\r(Reading database ... 35%\r(Reading database ... 40%\r(Reading database ... 45%\r(Reading database ... 50%\r(Reading database ... 55%\r(Reading database ... 60%\r(Reading database ... 65%\r(Reading database ... 70%\r(Reading database ... 75%\r(Reading database ... 80%\r(Reading database ... 85%\r(Reading database ... 90%\r(Reading database ... 95%\r(Reading database ... 100%\r(Reading database ... 59064 files and directories currently installed.)\r\nPreparing to unpack .../libexpat1_2.1.0-7[*******]<IP_ADDRESS>_amd64.deb ...\r\nUnpacking libexpat1:amd64 (2.1.0-7[*******]<IP_ADDRESS>) over (2.1.0-7[*******]<IP_ADDRESS>) ...\r\nSelecting previously unselected package libstdc++-5-dev:amd64.\r\nPreparing to unpack .../libstdc++-5-dev_5.4.0-6[*******]1~16.04.4_amd64.deb ...\r\nUnpacking libstdc++-5-dev:amd64 (5.4.0-6[*******]1~16.04.4) ...\r\nSelecting previously unselected package g++-5.\r\nPreparing to unpack .../g++-5_5.4.0-6[*******]1~16.04.4_amd64.deb ...\r\nUnpacking g++-5 (5.4.0-6[*******]1~16.04.4) ...\r\nSelecting previously unselected package g++.\r\nPreparing to unpack .../g++_4%3a5.3.1-1[*******]1_amd64.deb ...\r\nUnpacking g++ (4:5.3.1-1[*******]1) ...\r\nSelecting previously unselected package libdpkg-perl.\r\nPreparing to unpack .../libdpkg-perl_1.18.4[*******]1.2_all.deb ...\r\nUnpacking libdpkg-perl (1.18.4[*******]1.2) ...\r\nSelecting previously unselected package dpkg-dev.\r\nPreparing to unpack .../dpkg-dev_1.18.4[*******]1.2_all.deb ...\r\nUnpacking dpkg-dev (1.18.4[*******]1.2) ...\r\nSelecting previously unselected package build-essential.\r\nPreparing to unpack .../build-essential_12.1[*******]2_amd64.deb ...\r\nUnpacking build-essential (12.1[*******]2) ...\r\nSelecting previously unselected package libalgorithm-diff-perl.\r\nPreparing to unpack .../libalgorithm-diff-perl_1.19.03-1_all.deb ...\r\nUnpacking libalgorithm-diff-perl (1.19.03-1) ...\r\nSelecting previously unselected package libalgorithm-diff-xs-perl.\r\nPreparing to unpack .../libalgorithm-diff-xs-perl_0.04-4build1_amd64.deb ...\r\nUnpacking libalgorithm-diff-xs-perl (0.04-4build1) ...\r\nSelecting previously unselected package libalgorithm-merge-perl.\r\nPreparing to unpack .../libalgorithm-merge-perl_0.08-3_all.deb ...\r\nUnpacking libalgorithm-merge-perl (0.08-3) ...\r\nSelecting previously unselected package libexpat1-dev:amd64.\r\nPreparing to unpack .../libexpat1-dev_2.1.0-7[*******]<IP_ADDRESS>_amd64.deb ...\r\nUnpacking libexpat1-dev:amd64 (2.1.0-7[*******]<IP_ADDRESS>) ...\r\nSelecting previously unselected package libfile-fcntllock-perl.\r\nPreparing to unpack .../libfile-fcntllock-perl_0.22-3_amd64.deb ...\r\nUnpacking libfile-fcntllock-perl (0.22-3) ...\r\nSelecting previously unselected package libpython2.7:amd64.\r\nPreparing to unpack .../libpython2.7_2.7.12-1[*******]0~16.04.1_amd64.deb ...\r\nUnpacking libpython2.7:amd64 (2.7.12-1[*******]0~16.04.1) ...\r\nSelecting previously unselected package libpython2.7-dev:amd64.\r\nPreparing to unpack .../libpython2.7-dev_2.7.12-1[*******]0~16.04.1_amd64.deb ...\r\nUnpacking libpython2.7-dev:amd64 (2.7.12-1[*******]0~16.04.1) ...\r\nSelecting previously unselected package libpython-dev:amd64.\r\nPreparing to unpack .../libpython-dev_2.7.11-1_amd64.deb ...\r\nUnpacking libpython-dev:amd64 (2.7.11-1) ...\r\nSelecting previously unselected package libpython-all-dev:amd64.\r\nPreparing to unpack .../libpython-all-dev_2.7.11-1_amd64.deb ...\r\nUnpacking libpython-all-dev:amd64 (2.7.11-1) ...\r\nSelecting previously unselected package python-all.\r\nPreparing to unpack .../python-all_2.7.11-1_amd64.deb ...\r\nUnpacking python-all (2.7.11-1) ...\r\nSelecting previously unselected package python2.7-dev.\r\nPreparing to unpack .../python2.7-dev_2.7.12-1[*******]0~16.04.1_amd64.deb ...\r\nUnpacking python2.7-dev (2.7.12-1[*******]0~16.04.1) ...\r\nSelecting previously unselected package python-dev.\r\nPreparing to unpack .../python-dev_2.7.11-1_amd64.deb ...\r\nUnpacking python-dev (2.7.11-1) ...\r\nSelecting previously unselected package python-all-dev.\r\nPreparing to unpack .../python-all-dev_2.7.11-1_amd64.deb ...\r\nUnpacking python-all-dev (2.7.11-1) ...\r\nSelecting previously unselected package python-pip-whl.\r\nPreparing to unpack .../python-pip-whl_8.1.1-2[*******]0.4_all.deb ...\r\nUnpacking python-pip-whl (8.1.1-2[*******]0.4) ...\r\nSelecting previously unselected package python-pip.\r\nPreparing to unpack .../python-pip_8.1.1-2[*******]0.4_all.deb ...\r\nUnpacking python-pip (8.1.1-2[*******]0.4) ...\r\nSelecting previously unselected package python-pkg-resources.\r\nPreparing to unpack .../python-pkg-resources_20.7.0-1_all.deb ...\r\nUnpacking python-pkg-resources (20.7.0-1) ...\r\nSelecting previously unselected package python-setuptools.\r\nPreparing to unpack .../python-setuptools_20.7.0-1_all.deb ...\r\nUnpacking python-setuptools (20.7.0-1) ...\r\nSelecting previously unselected package python-wheel.\r\nPreparing to unpack .../python-wheel_0.29.0-1_all.deb ...\r\nUnpacking python-wheel (0.29.0-1) ...\r\nProcessing triggers for libc-bin (2.23-0[*******]5) ...\r\nProcessing triggers for man-db (2.7.5-1) ...\r\nSetting up libexpat1:amd64 (2.1.0-7[*******]<IP_ADDRESS>) ...\r\nSetting up libstdc++-5-dev:amd64 (5.4.0-6[*******]1~16.04.4) ...\r\nSetting up g++-5 (5.4.0-6[*******]1~16.04.4) ...\r\nSetting up g++ (4:5.3.1-1[*******]1) ...\r\nupdate-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode\r\nSetting up libdpkg-perl (1.18.4[*******]1.2) ...\r\nSetting up dpkg-dev (1.18.4[*******]1.2) ...\r\nSetting up build-essential (12.1[*******]2) ...\r\nSetting up libalgorithm-diff-perl (1.19.03-1) ...\r\nSetting up libalgorithm-diff-xs-perl (0.04-4build1) ...\r\nSetting up libalgorithm-merge-perl (0.08-3) ...\r\nSetting up libexpat1-dev:amd64 (2.1.0-7[*******]<IP_ADDRESS>) ...\r\nSetting up libfile-fcntllock-perl (0.22-3) ...\r\nSetting up libpython2.7:amd64 (2.7.12-1[*******]0~16.04.1) ...\r\nSetting up libpython2.7-dev:amd64 (2.7.12-1[*******]0~16.04.1) ...\r\nSetting up libpython-dev:amd64 (2.7.11-1) ...\r\nSetting up libpython-all-dev:amd64 (2.7.11-1) ...\r\nSetting up python-all (2.7.11-1) ...\r\nSetting up python2.7-dev (2.7.12-1[*******]0~16.04.1) ...\r\nSetting up python-dev (2.7.11-1) ...\r\nSetting up python-all-dev (2.7.11-1) ...\r\nSetting up python-pip-whl (8.1.1-2[*******]0.4) ...\r\nSetting up python-pip (8.1.1-2[*******]0.4) ...\r\nSetting up python-pkg-resources (20.7.0-1) ...\r\nSetting up python-setuptools (20.7.0-1) ...\r\nSetting up python-wheel (0.29.0-1) ...\r\nProcessing triggers for libc-bin (2.23-0[*******]5) ...", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "The following additional packages will be installed:", "  build-essential dpkg-dev g++ g++-5 libalgorithm-diff-perl", "  libalgorithm-diff-xs-perl libalgorithm-merge-perl libdpkg-perl libexpat1", "  libexpat1-dev libfile-fcntllock-perl libpython-all-dev libpython-dev", "  libpython2.7 libpython2.7-dev libstdc++-5-dev python-all python-all-dev", "  python-dev python-pip-whl python-pkg-resources python-setuptools", "  python-wheel python2.7-dev", "Suggested packages:", "  debian-keyring g++-multilib g++-5-multilib gcc-5-doc libstdc++6-5-dbg", "  libstdc++-5-doc python-setuptools-doc", "The following NEW packages will be installed:", "  build-essential dpkg-dev g++ g++-5 libalgorithm-diff-perl", "  libalgorithm-diff-xs-perl libalgorithm-merge-perl libdpkg-perl libexpat1-dev", "  libfile-fcntllock-perl libpython-all-dev libpython-dev libpython2.7", "  libpython2.7-dev libstdc++-5-dev python-all python-all-dev python-dev", "  python-pip python-pip-whl python-pkg-resources python-setuptools", "  python-wheel python2.7-dev", "The following packages will be upgraded:", "  libexpat1", "1 upgraded, 24 newly installed, 0 to remove and 137 not upgraded.", "Need to get 41.5 MB of archives.", "After this operation, 91.8 MB of additional disk space will be used.", "Get:1 http://archive.[*******].com/[*******] xenial-updates/main amd64 libexpat1 amd64 2.1.0-7[*******]<IP_ADDRESS> [71.2 kB]", "Get:2 http://archive.[*******].com/[*******] xenial-updates/main amd64 libstdc++-5-dev amd64 5.4.0-6[*******]1~16.04.4 [1,426 kB]", "Get:3 http://archive.[*******].com/[*******] xenial-updates/main amd64 g++-5 amd64 5.4.0-6[*******]1~16.04.4 [8,300 kB]", "Get:4 http://archive.[*******].com/[*******] xenial/main amd64 g++ amd64 4:5.3.1-1[*******]1 [1,504 B]", "Get:5 http://archive.[*******].com/[*******] xenial-updates/main amd64 libdpkg-perl all 1.18.4[*******]1.2 [195 kB]", "Get:6 http://archive.[*******].com/[*******] xenial-updates/main amd64 dpkg-dev all 1.18.4[*******]1.2 [584 kB]", "Get:7 http://archive.[*******].com/[*******] xenial/main amd64 build-essential amd64 12.1[*******]2 [4,758 B]", "Get:8 http://archive.[*******].com/[*******] xenial/main amd64 libalgorithm-diff-perl all 1.19.03-1 [47.6 kB]", "Get:9 http://archive.[*******].com/[*******] xenial/main amd64 libalgorithm-diff-xs-perl amd64 0.04-4build1 [11.0 kB]", "Get:10 http://archive.[*******].com/[*******] xenial/main amd64 libalgorithm-merge-perl all 0.08-3 [12.0 kB]", "Get:11 http://archive.[*******].com/[*******] xenial-updates/main amd64 libexpat1-dev amd64 2.1.0-7[*******]<IP_ADDRESS> [115 kB]", "Get:12 http://archive.[*******].com/[*******] xenial/main amd64 libfile-fcntllock-perl amd64 0.22-3 [32.0 kB]", "Get:13 http://archive.[*******].com/[*******] xenial-updates/main amd64 libpython2.7 amd64 2.7.12-1[*******]0~16.04.1 [1,070 kB]", "Get:14 http://archive.[*******].com/[*******] xenial-updates/main amd64 libpython2.7-dev amd64 2.7.12-1[*******]0~16.04.1 [27.8 MB]", "Get:15 http://archive.[*******].com/[*******] xenial/main amd64 libpython-dev amd64 2.7.11-1 [7,728 B]", "Get:16 http://archive.[*******].com/[*******] xenial/main amd64 libpython-all-dev amd64 2.7.11-1 [992 B]", "Get:17 http://archive.[*******].com/[*******] xenial/main amd64 python-all amd64 2.7.11-1 [978 B]", "Get:18 http://archive.[*******].com/[*******] xenial-updates/main amd64 python2.7-dev amd64 2.7.12-1[*******]0~16.04.1 [276 kB]", "Get:19 http://archive.[*******].com/[*******] xenial/main amd64 python-dev amd64 2.7.11-1 [1,160 B]", "Get:20 http://archive.[*******].com/[*******] xenial/main amd64 python-all-dev amd64 2.7.11-1 [1,000 B]", "Get:21 http://archive.[*******].com/[*******] xenial-updates/universe amd64 python-pip-whl all 8.1.1-2[*******]0.4 [1,110 kB]", "Get:22 http://archive.[*******].com/[*******] xenial-updates/universe amd64 python-pip all 8.1.1-2[*******]0.4 [144 kB]", "Get:23 http://archive.[*******].com/[*******] xenial/main amd64 python-pkg-resources all 20.7.0-1 [108 kB]", "Get:24 http://archive.[*******].com/[*******] xenial/main amd64 python-setuptools all 20.7.0-1 [169 kB]", "Get:25 http://archive.[*******].com/[*******] xenial/universe amd64 python-wheel all 0.29.0-1 [48.0 kB]", "Fetched 41.5 MB in 12s (3,295 kB/s)", "(Reading database ... ", "(Reading database ... 5%", "(Reading database ... 10%", "(Reading database ... 15%", "(Reading database ... 20%", "(Reading database ... 25%", "(Reading database ... 30%", "(Reading database ... 35%", "(Reading database ... 40%", "(Reading database ... 45%", "(Reading database ... 50%", "(Reading database ... 55%", "(Reading database ... 60%", "(Reading database ... 65%", "(Reading database ... 70%", "(Reading database ... 75%", "(Reading database ... 80%", "(Reading database ... 85%", "(Reading database ... 90%", "(Reading database ... 95%", "(Reading database ... 100%", "(Reading database ... 59064 files and directories currently installed.)", "Preparing to unpack .../libexpat1_2.1.0-7[*******]<IP_ADDRESS>_amd64.deb ...", "Unpacking libexpat1:amd64 (2.1.0-7[*******]<IP_ADDRESS>) over (2.1.0-7[*******]<IP_ADDRESS>) ...", "Selecting previously unselected package libstdc++-5-dev:amd64.", "Preparing to unpack .../libstdc++-5-dev_5.4.0-6[*******]1~16.04.4_amd64.deb ...", "Unpacking libstdc++-5-dev:amd64 (5.4.0-6[*******]1~16.04.4) ...", "Selecting previously unselected package g++-5.", "Preparing to unpack .../g++-5_5.4.0-6[*******]1~16.04.4_amd64.deb ...", "Unpacking g++-5 (5.4.0-6[*******]1~16.04.4) ...", "Selecting previously unselected package g++.", "Preparing to unpack .../g++_4%3a5.3.1-1[*******]1_amd64.deb ...", "Unpacking g++ (4:5.3.1-1[*******]1) ...", "Selecting previously unselected package libdpkg-perl.", "Preparing to unpack .../libdpkg-perl_1.18.4[*******]1.2_all.deb ...", "Unpacking libdpkg-perl (1.18.4[*******]1.2) ...", "Selecting previously unselected package dpkg-dev.", "Preparing to unpack .../dpkg-dev_1.18.4[*******]1.2_all.deb ...", "Unpacking dpkg-dev (1.18.4[*******]1.2) ...", "Selecting previously unselected package build-essential.", "Preparing to unpack .../build-essential_12.1[*******]2_amd64.deb ...", "Unpacking build-essential (12.1[*******]2) ...", "Selecting previously unselected package libalgorithm-diff-perl.", "Preparing to unpack .../libalgorithm-diff-perl_1.19.03-1_all.deb ...", "Unpacking libalgorithm-diff-perl (1.19.03-1) ...", "Selecting previously unselected package libalgorithm-diff-xs-perl.", "Preparing to unpack .../libalgorithm-diff-xs-perl_0.04-4build1_amd64.deb ...", "Unpacking libalgorithm-diff-xs-perl (0.04-4build1) ...", "Selecting previously unselected package libalgorithm-merge-perl.", "Preparing to unpack .../libalgorithm-merge-perl_0.08-3_all.deb ...", "Unpacking libalgorithm-merge-perl (0.08-3) ...", "Selecting previously unselected package libexpat1-dev:amd64.", "Preparing to unpack .../libexpat1-dev_2.1.0-7[*******]<IP_ADDRESS>_amd64.deb ...", "Unpacking libexpat1-dev:amd64 (2.1.0-7[*******]<IP_ADDRESS>) ...", "Selecting previously unselected package libfile-fcntllock-perl.", "Preparing to unpack .../libfile-fcntllock-perl_0.22-3_amd64.deb ...", "Unpacking libfile-fcntllock-perl (0.22-3) ...", "Selecting previously unselected package libpython2.7:amd64.", "Preparing to unpack .../libpython2.7_2.7.12-1[*******]0~16.04.1_amd64.deb ...", "Unpacking libpython2.7:amd64 (2.7.12-1[*******]0~16.04.1) ...", "Selecting previously unselected package libpython2.7-dev:amd64.", "Preparing to unpack .../libpython2.7-dev_2.7.12-1[*******]0~16.04.1_amd64.deb ...", "Unpacking libpython2.7-dev:amd64 (2.7.12-1[*******]0~16.04.1) ...", "Selecting previously unselected package libpython-dev:amd64.", "Preparing to unpack .../libpython-dev_2.7.11-1_amd64.deb ...", "Unpacking libpython-dev:amd64 (2.7.11-1) ...", "Selecting previously unselected package libpython-all-dev:amd64.", "Preparing to unpack .../libpython-all-dev_2.7.11-1_amd64.deb ...", "Unpacking libpython-all-dev:amd64 (2.7.11-1) ...", "Selecting previously unselected package python-all.", "Preparing to unpack .../python-all_2.7.11-1_amd64.deb ...", "Unpacking python-all (2.7.11-1) ...", "Selecting previously unselected package python2.7-dev.", "Preparing to unpack .../python2.7-dev_2.7.12-1[*******]0~16.04.1_amd64.deb ...", "Unpacking python2.7-dev (2.7.12-1[*******]0~16.04.1) ...", "Selecting previously unselected package python-dev.", "Preparing to unpack .../python-dev_2.7.11-1_amd64.deb ...", "Unpacking python-dev (2.7.11-1) ...", "Selecting previously unselected package python-all-dev.", "Preparing to unpack .../python-all-dev_2.7.11-1_amd64.deb ...", "Unpacking python-all-dev (2.7.11-1) ...", "Selecting previously unselected package python-pip-whl.", "Preparing to unpack .../python-pip-whl_8.1.1-2[*******]0.4_all.deb ...", "Unpacking python-pip-whl (8.1.1-2[*******]0.4) ...", "Selecting previously unselected package python-pip.", "Preparing to unpack .../python-pip_8.1.1-2[*******]0.4_all.deb ...", "Unpacking python-pip (8.1.1-2[*******]0.4) ...", "Selecting previously unselected package python-pkg-resources.", "Preparing to unpack .../python-pkg-resources_20.7.0-1_all.deb ...", "Unpacking python-pkg-resources (20.7.0-1) ...", "Selecting previously unselected package python-setuptools.", "Preparing to unpack .../python-setuptools_20.7.0-1_all.deb ...", "Unpacking python-setuptools (20.7.0-1) ...", "Selecting previously unselected package python-wheel.", "Preparing to unpack .../python-wheel_0.29.0-1_all.deb ...", "Unpacking python-wheel (0.29.0-1) ...", "Processing triggers for libc-bin (2.23-0[*******]5) ...", "Processing triggers for man-db (2.7.5-1) ...", "Setting up libexpat1:amd64 (2.1.0-7[*******]<IP_ADDRESS>) ...", "Setting up libstdc++-5-dev:amd64 (5.4.0-6[*******]1~16.04.4) ...", "Setting up g++-5 (5.4.0-6[*******]1~16.04.4) ...", "Setting up g++ (4:5.3.1-1[*******]1) ...", "update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode", "Setting up libdpkg-perl (1.18.4[*******]1.2) ...", "Setting up dpkg-dev (1.18.4[*******]1.2) ...", "Setting up build-essential (12.1[*******]2) ...", "Setting up libalgorithm-diff-perl (1.19.03-1) ...", "Setting up libalgorithm-diff-xs-perl (0.04-4build1) ...", "Setting up libalgorithm-merge-perl (0.08-3) ...", "Setting up libexpat1-dev:amd64 (2.1.0-7[*******]<IP_ADDRESS>) ...", "Setting up libfile-fcntllock-perl (0.22-3) ...", "Setting up libpython2.7:amd64 (2.7.12-1[*******]0~16.04.1) ...", "Setting up libpython2.7-dev:amd64 (2.7.12-1[*******]0~16.04.1) ...", "Setting up libpython-dev:amd64 (2.7.11-1) ...", "Setting up libpython-all-dev:amd64 (2.7.11-1) ...", "Setting up python-all (2.7.11-1) ...", "Setting up python2.7-dev (2.7.12-1[*******]0~16.04.1) ...", "Setting up python-dev (2.7.11-1) ...", "Setting up python-all-dev (2.7.11-1) ...", "Setting up python-pip-whl (8.1.1-2[*******]0.4) ...", "Setting up python-pip (8.1.1-2[*******]0.4) ...", "Setting up python-pkg-resources (20.7.0-1) ...", "Setting up python-setuptools (20.7.0-1) ...", "Setting up python-wheel (0.29.0-1) ...", "Processing triggers for libc-bin (2.23-0[*******]5) ..."], "warnings": ["Consider using apt module rather than running apt-get"]}


Add "Refresh" command to datbases panel on Manage Page

Issue Type: Feature Request
I would like to see "Refresh" added to the right (command) click inside the Search panel showing databases. (The refresh commands is displayed off the ... menu in the panel.)

Azure Data Studio version: Azure Data Studio 1.0.0 (cab8f3e37c9ac4367e0dacef5185da08bd8021c2, 2018-09-20T21:41:50.803Z)
OS version: Darwin x64 17.7.0

Closing out older issues.  This will be addressed as part of the dashboard refactor in progress.


OpenCore Bootloader

Would be great if you found time to make efi using the new opencore bootloader.

Hi, I am in a school final actually, and I hope someone else could make an oc for us.
OC Configuration Instruction is in https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf for anyone who is intertested.

Great News! I succeeded in booting with OpenCore, will submit my branch later.

What it this for our laptops?

Opencore is a newer replacement for clover. Have a read of interested...seems like it could be good. Will test once Steve commits.

I would like to do for Mi Air and others. I will read more about this

What are your initial thoughts @stevezhengshiqi ? Improvement in performance / behavior expected with opencore? Ready for help testing? Happy to help on my i7/16gb.

@jackreeves To be honest, currently, I can't tell advantages of using OpenCore than Clover. For example, the unfriendly GUI, no common ACPI fixes in Clover(e.g. FixRTC), fewer instructions...
The things I notice that OpenCore does better: it has more customizations for patching ACPI. In Clover, we only have Find, Replace, TgtBridge(buggy), and in OpenCore, there are Mask, OemTableId... which supports advanced patching.
I once read a post which says that OpenCore supports SHA-256 hashing by running create_vault.sh to avoid unintended modifications. If you sign OpenCore.efi and BOOTx64.efi with appropriate key, it even support SecureBoot in BIOS.
However, I have great confidence for Acidanthera. They have taken over the most hackintosh kernel extensions projects, and I believe in the future, they can make their OpenCore boot loader work with their kexts in a perfect way.

I agree.
As untill now there is no diffirence in perfomance,stability etc.
But you never know in the future.

Great News! I succeeded in booting with OpenCore, will submit my branch later.

How did you do renames with TgtBridge for Opencore?

@onemanosx Sorry for delay. I didn’t see this post til today. Actually, I force myself to not use TgtBridge in Clover because it’s so buggy. All OEM SSDT will be accidentally influenced by TgrBridge in Clover.
I add more strings in Find for more specific patch.

This is how I recently figured out. Where "Count" is the number of times patch is to be executed and "Skip" is the patch location in ACPI scope
But its painstaking process. Would love to know how you did yours. Mind to share?


Assets/Create/Zenject/Project Composition Root Fails to create the prefab.

The menu item shown in the title fails to create the prefab in the resources directory.
Error messages
http://puu.sh/oBPRK/cfaf46d70c.png
http://puu.sh/oBPVw/51c590fa3e.png
My observations are that somewhere along the line, the full file path is being obtained and used (based on the full file path shown in the above screen shots) when it should probably be just the Assets/Resources/....
As an additional note, the new Edit/Zenject/Create Project Composition Root menu option works for me.

Yep, that was exactly right, it was using the full path rather than the relative one that Unity wants.  Thanks!  Fixed now.
Let me know if you have any more feedback on Zenject 4 - currently only a few teams have used it.  I really need to update the documentation for the changes, but otherwise it should be ready to merge back into master


focus jumps close tag on another line

VSCode Version: Code 1.8.0 (38746938a4ab94f2f57d9e1309c51fd6fb37553d, 2016-12-13T17:38:28.425Z)
OS Version: Darwin x64 15.2.0
Extensions:

Extension
Author
Version

stylus
Alan
0.0.4

output-colorizer
IBM
0.0.8

stylus
buzinas
0.1.0

jquerysnippets
donjayamanne
0.0.1

python
donjayamanne
0.4.2

color-highlight
naumovs
1.2.1

trailing-spaces
shardulm94
0.2.11

language-stylus
sysoev
1.6.0

twig
whatwedo
1.0.1

Steps to Reproduce:
1.When I type any html tag, and followed the class, the focus jumps to the next causing it to be separated from the closing tag in another line
2.
Happens in html

@gcamana can you pls provide an animated gif of what you are doing or explain it in more detail. Thanks!

Closing the issue for now.
@gcamana pls reopen the issue when you can provide an animated gif to illustrate the problem.


Added challenge name links

Now all challenge names link to the corresponding category page in cryptohack's website.

LGTM. thanks for the contribution! :)


Link Design System site to accessibility criteria

Fixes #1798.
This PR adds links from the Design System site to our accessibility acceptance criteria doc.
Hopefully, these links will help contributors find the doc more easily.

Note: do not merge before we finalise #1781, as before then there won't be a doc to link to.