Error code -6 : Memory required for data: xxx Creating layer cluster

Hey there,
as I mentioned in the title, I am getting this error message in the DIGITS ui.
Here I am attaching the caffe output:
caffe_output.txt
I must mention that I am trying to clone a same setup that it worked properly before. Same dataset and same parameters.
Also, I know that the output says that I should use the 3.3.0 version of profobuf. I had the 2.6.x before, and it worked without any problem. Than I changed it to 3.3 (after when I saw first time this error) and still got the same error message, so I switched back to the original 2.6.x that DIGITS is using. Its quite frustrating. All I could guess is that the original error is not caused by the wrong version of protobuf but by something else.
Any help or ideas are appreciated and more than welcome!

In Ubuntu16.04, the version of protoc installedis 2.6. *, Which led to version conflict. To make sure your protoc version:
protoc --version
libprotoc 2.6.1
You can upgrade your protoc like:
sudo add-apt-repository ppa:maarten-fonville/protobuf
sudo apt-get update

This issue is being addressed and is in pull request review

#1749

To fix this, you need to build protobuf 3.2.x from source. Then rebuild caffe.

Thanks for your answer @chalesguo , I believe that could solve the problem.
However I already managed it, but reinstalling DIGITS with synaptic (I simply removed it and installed again). Now I have still the 2.6.1 version of protobuf and DIGITS works well.

I got the exactly same problem and can't get to a solution either way. I have attached my log bellow:
I0410 21:09:30.708613 10995 net.cpp:159] Memory required for data:<PHONE_NUMBER>
I0410 21:09:30.708614 10995 layer_factory.hpp:77] Creating layer cluster
[libprotobuf FATAL google/protobuf/stubs/common.cc:61] This program requires version 3.5.0 of the Protocol Buffer runtime library, but the installed version is 2.6.1.  Please update your library.  If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library.  (Version verification failed in "google/protobuf/descriptor.pb.cc".)
terminate called after throwing an instance of 'google::protobuf::FatalException'
what():  This program requires version 3.5.0 of the Protocol Buffer runtime library, but the installed version is 2.6.1.  Please update your library.  If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library.  (Version verification failed in "google/protobuf/descriptor.pb.cc".)


kube-dns in container creation state

** BUG REPORT **:
What happened:
kube-dns in container creation state after re-deploying with manually generated certificates
What you expected to happen:
kube-dns service to start normally
How to reproduce it (as minimally and precisely as possible):
Generate certificates using cfssl utility and replace the existing certificates with new ones.
Restart the services.
Anything else we need to know?:
Environment:

Kismatic version (use kismatic version): 1.9
Plan file Gist (remove sensitive information if any):
Cloud provider or hardware configuration: AWS IAAS
OS (e.g. from /etc/os-release): Ubuntu 16.04.4 LTS (Xenial Xerus)
Kernel (e.g. uname -a): x86_64 x86_64 x86_64 GNU/Linux

kube-dns events show - Failed create pod sandbox

Which certificates are you generating manually or is it all of them? Are you sure that the CN and SANs are identical to what is automatically generated?

Hey I just actually finished going through this, here are the details for all the certs.

Hey @dkoshkin - Thank you. It helps. Let me try again.


rnn_train.py fails with my_txtutils.py

Hi Martin,
first of all - thanks for the great job on the TF materials! Code, YT, slides, etc.. Very high quality and very well presented. IMHO best high-level TF materials available.
All types of mnist convolutions Pt.1 works flawlessly, but unfortunately RNN's won't start due to some, I suspect, libraries inconsistency in-between some recent upgrades. This affects your_txtutils.py
Btw, the rnn_play with downloaded checkpoints works perfectly.
Any clue of a quick fix to start training?
thx
commit: 5c3b9313b023a15d3f3ab786617c79b60cd043a1
(outrun) pawel@paweldebian:tensorflow-rnn-shakespeare$ python3 rnn_train.py
Traceback (most recent call last):
  File "rnn_train.py", line 51, in <module>
    codetext, valitext, bookranges = txt.read_data_files(shakedir, validation=True)
  File "/home/pawel/M/outrun/tensorflow-rnn-shakespeare/my_txtutils.py", line 247, in read_data_files
    shakelist = glob.glob(directory, recursive=True)
TypeError: glob() got an unexpected keyword argument 'recursive'
(outrun) pawel@paweldebian:tensorflow-rnn-shakespeare$ python3 --version
Python 3.4.2
(outrun) pawel@paweldebian:tensorflow-rnn-shakespeare$ git log | head -6
commit 5c3b9313b023a15d3f3ab786617c79b60cd043a1
Merge: 43b83b6 9a7fd70
Author: Martin Görner<EMAIL_ADDRESS>Date:   Tue May 23 10:59:56 2017 +0200

    Updates for TF 1.1
(outrun) pawel@paweldebian:tensorflow-rnn-shakespeare$

Investigated further and found the reason and solution.
This is due to the glob library not supporting 'recursive' keyword in python 3.4 yet.
For those who cannot upgrade to 3.5 there is a workaroud in 3.4 - the glob2 library:
pip3 install glob2
In my_txtutils.py change these two lines:
17   import glob
247  shakelist = glob.glob(directory, recursive=True)

to
17   import glob2
247  shakelist = glob2.glob(directory, recursive=True)

Now:

LORD POLONIUS	And, sir! how now, my lord! what is this? I hope I'll be said
that's a man of your house, and therefore, I will be so fair
that I have been a stone of the base of your house,
that I have seen the common thing to this patience of the world.

Or just drop the "recursive" parameter. At least in this example, all data files are in the same directory.


SelectionTree goes into implicit ShadowDecls

void foo(int);

namespace ns {
using ::f^oo;
};

This results in the following SelectionTree:
TranslationUnitDecl
  NamespaceDecl namespace ns {
}
   .UsingDecl using ::foo
   .UsingShadowDecl

In which the using shadow decl should not reside. Since contract on selection tree is only for "visible" ast nodes, see https://github.com/llvm-mirror/clang-tools-extra/blob/master/clangd/Selection.h#L78.

Yeah I'd seen this. It's confusing and I'm not sure the behavior is right. However I'm also not sure I agree with the characterisation of ShadowDecl as implicit, so I don't think it's clear-cut.

This no longer reproduces. I think it was https://github.com/llvm/llvm-project/commit/395fde753c912e66964e1ce097f1ea6c59c79576


Feature: magics always

Always prepend and append are implemented. As show and clear to inspect and remove them all. As conversed in issue #85
The first commit contains the real work. The rest is test and doc.
Note on t/20-end-to-end.t
(I renamed it : 10 -> 20 for it to stay the last when adding more test)
The client is not dying sometimes => address already in use (9103 iopub)
For example when my tests did freeze a Ctrl-C killed the kernel but not the client.
pkill raku
P6_JUPYTER_TEST_END_TO_END=1 ra t/20-end-to-end.t

Or more wisely
netstat -laputn | grep 9103   # to find its pid (here 666)
kill -15 666

Very cool!
However, I think it should execute whatever is in the cell -- so that you can have something like
#% always
say "-----header-----"

This makes it useful in the notebook UI, e.g. to set up a cell that does several things
In this pr  --
In [1]: #% always \
      : say "----"
Out[1]:

In [2]: 2
Out[2]: 2

However, it's cool that this works --
In [1]: #% always say 'hi'
Out[1]:

In [2]: 3
hi
Out[2]: 3

I suppose we can keep that even though it could potentially be ambiguous (e.g. if there is a prepend sub defined)
also +1 for nice tests

Awesome review : nice catch! I made a mistake for believing this was only a check:
my $magic-line = $code.lines[0] or return Nil;
$magic-line ~~ /^ [ '#%' | '%%' ] / or return Nil;

Fixed (c1e019d above):
In [6]: #% always
      : say "-----header-----"
Out[6]:

In [7]: say "May the Magic be always with you"
-----header-----
May the Magic be always with you

Great!


Unable to send message using proxy？

I am using a proxy, I can log in, but sending a message will fail, return 401
 client.send(newTdApi.AddProxy("<IP_ADDRESS>",8080,true,newTdApi.ProxyTypeSocks5("onessr","free")),defaultHandler);

Are you sure that your account wasn't banned?

@levlam  I can use Shadowsocks to send message,not banned.

401 can be returned only for unauthorized accounts. So, there are only these possibilities:

You aren't authorized yet.
You already logged out.
The account was banned and logged out by the server.
You receive not error 401.

Could you collect TDLib log with verbosity level 4 and send it to @tdlibbot to find the exact reason?

@levlam  The account was banned and logged out by the server.


coprocessor: avoid fmsketch calculation for single-column index

What is changed and how it works?

Issue Number: ref #14231
What's Changed:
Implement https://github.com/pingcap/tidb/pull/41931 in the tikv side. For the sinlge-column group, its fm_sketch is the same as that of the corresponding column. Hence, we don't maintain its fm_sketch in collect_column_group. We just copy the corresponding column's fm_sketch after iterating all rows. Also, we can directly copy total_size and null_count.

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

Manual test (add detailed scripts or steps below)

Side effects
Release note
None

/build

/run-build

/cc @skyzh @AndreMouche @Xuanwo

@skyzh Could you help trigger merge? Thx~

/merge


Screen shots out of date

The screen shots on this page don't reflect the options shown in the product any more and all need to be updated.

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

ID: a0c70e2a-c370-01ae-c46a-3a1d0b95fd61
Version Independent ID: a3d2b15f-8900-491a-c71a-ab16db108376
Content: Place a Microsoft Teams user or team on legal hold - Microsoft Teams
Content Source: Teams/legal-hold.md
Service: msteams
GitHub Login: @robmazz
Microsoft Alias: robmazz

Thanks for your feedback!


alias remote

In using the alias option, as documented at:
https://binary-array-ld.github.io/net.binary_array_ld.bald/alias.html#cli
it would be really helpful if the CLI could handle download directly from an online register that supports content negotiation
For example, there is a developing representation of the CF conventions vocabulary presented at
http://def.scitools.org.uk/CFTerms
it would be great if the CLI supported remote aliasing, such that
java -jar bald-cli.jar -a http://def.scitools.org.uk/CFTerms sampleNC/GEMS_CO2_Apr2006.nc

ran successfully, rather than requiring the user to download a ttl file first to use
(see https://github.com/binary-array-ld/bald/tree/master/lib/bald/tests/integration/CDL for example files, including GEMS_CO2_Apr2006.cdl  and ncgen -o GEMS_CO2_Apr2006.nc GEMS_CO2_Apr2006.cdl)

As far as I can tell this works and gives the expected output on the current master branch. If not please could you provide the console output for the failure?

okay, this is (as suspected) a proxy issue
functionality is working if java options specified, e.g.
java -Dhttp.proxyHost="mywebproxy.example.com" -Dhttp.proxyPort="8086" -jar bald-cli.jar -a http://def.scitools.org.uk/NetCDF,http://def.scitools.org.uk/CFTerms sampleNC/votemper.nc
at minimum, this needs documenting in the CLI, with suggested work around
perhaps a neat solution, if possible, would be to follow a common linux pattern and obtain the value of $http_proxy from the environment
caution would be required, as
$http_proxy and $https_proxy may exist and may have different values, and java options include -Dhttp.* and  -Dhttps.* options
i don't know what this looks like in M$ windows nor macOS (tho i'm happy to have unix focussed documentation at this stage)


[Proposal] Consider introducing the RPC layer

@davidfowl Thank you very much for yesterday presentation link! It was really helpful.
I was doing a lot of thinking about the new design. And I am not convinced very much about some Hub abstraction at all.
There is some design discrepancy in hubs by inheriting them from the legacy SignalR design while changing some fundamental concepts underneath.
On the one hand hubs introduces entities like groups and users which are extremely application-specific - on the other hand without ReliableConnection abstraction it tries to allow multiple HubLifetimeManager designs.
In my opinion there is at least one layer missing between Hub and Sockets (I really love the idea of separating sockets layer!). It's the RPC layer.
This layer should allow procedurę invocation on both connection sides and should allow pluggable RPC protocols.
Just to mention: gRPC, JSON RPC...
(it complies with your idea of allowing multiple serialization formats). Maybe it's not the idea of serialization format that's worth consideration, but maybe the RPC format or both?
On top of this abstraction you can then build Hubs which will pursue the Users, Group delivery abstraction.
But maybe also a ReliableHub with reliable connections? I would definitely make the Hub-layer thinner.
OK. And now long shot. Why not to allow hub abstraction over ... message oriented RPC protocols like WAMP? :)

There is some design discrepancy in hubs by inheriting them from the legacy SignalR design while changing some fundamental concepts underneath.

What discrepancy is that? The hub is a pretty high level, very specific RPC protocol to support the scenarios we think are important to the most people (based on our experience with previous versions of SignalR).

on the other hand without ReliableConnection abstraction it tries to allow multiple HubLifetimeManager designs.

Can you elaborate? There are some people that use SignalR for very simple "close to the metal" websocket like scenarios. We don't want to force everyone to go through a very heavy abstraction when their scenario doesn't care about it. Furthermore, previously scale out was very specific and not very scalable TBH and the new design gives greater flexibility without sacrificing the ease of use.

In my opinion there is at least one layer missing between Hub and Sockets (I really love the idea of separating sockets layer!). It's the RPC layer.

I'm not convinced there needs to be a generic RPC layer. Build a few of those and show me how they are all similar and why they need to build on top of each other.

This layer should allow procedurę invocation on both connection sides and should allow pluggable RPC protocols.

Just to mention: gRPC, JSON RPC...
(it complies with your idea of allowing multiple serialization formats). Maybe it's not the idea of serialization format that's worth consideration, but maybe the RPC format or both?

We have a sorta kinda

OK. And now long shot. Why not to allow hub abstraction over ... message oriented RPC protocols like WAMP? :)

We looked at WAMP but were unconvinced we needed to support it directly. It also is message based (which is fine) but we didn't want that to be the primitive we built the lower layers on top of. As for Hubs on top of WAMP directly? Sure, sounds like it could be interesting but it's not the directly we're currently going in.

The hub is a pretty high level, very specific RPC protocol to support the scenarios we think are important to the most people (based on our experience with previous versions of SignalR).

Is Hub RPC protocol really that specific? I rather see a generic RPC protocol (method invocation).

What discrepancy is that?

It is that on the one hand high level and on the other totally low-level as it does not understand reliable connection abstraction.

We have a sorta kinda have an abstract RPC layer

I would definitely excercise the classes you have mentioned by moving them to an abstract RpcLayer - those classes are definitely not-hub or SignalR specific! At the end of the day you end up with some method invocation. This is just the RPC layer.

We looked at WAMP but were unconvinced we needed to support it directly

WAMP (as other message based protocols) specifically has one advantage which is the router abstraction. It allows to establish a reliable connection on top of multiple connections.

Furthermore, previously scale out was very specific and not very scalable TBH and the new design gives greater flexibility without sacrificing the ease of use.

I partially agree, but by dropping the ReliableConnection abstraction you are making multiple you are offering quite different service than before.
I totally agree that default configurations should be similiar to what is currently available, but imagine following design.
Three layers:

Socket
RpcChannel
Hub

Most trivial, default RpcChannel is close to the metal exactly what you have now. It is tied to the socket connection (connection breaks then channel breaks). It uses your variant your json formatter, or just standard JSON RPC (it is really similar to what you did, why not to use the standarized one?).
But one can implement for example a reliable RpcChannel that does reconnects, conducts message replies if needed, store unsent messages in some durable queue to ensure guaranteed delivery, kills duplicates.
Someone else might implement an RpcChannel using gRPC to have compatbility with Binary clients on the hub-level as well.
AFAIR You said in the presentation you don't like the formatters approach. In this design you don't need formatters at all. Formatters are the implementation detail of the RPC channel. That way you can add additional fields responsible for reliable connections and stuff!
From the typescript client perspective this is the same. You can have default RpcChannel, but you can also insert an alternative RpcChannel that handles all the missing messaging. So in the TypeScript client RpcChannel should also be pluggable.


Bug fix: If-None-Match: 304 response should return a real resource ETag

In the scope of bef507e1b7ac2eb0ff012d0d40035e218a5839cc was added a bug:
curl -vv http://localhost:8080/tomcat.png -H 'If-None-Match: W/"5103-1595887733334"'
> GET /tomcat.png HTTP/1.1
> Accept: */*
> If-None-Match: W/"5103-1595887733334"
>
< HTTP/1.1 304
< ETag: "5103-1595887733334"
< Date: Tue, 11 Aug 2020 20:27:30 GMT

The real ETag is weak W/"5103-1595887733334" but returned in response was strict "5103-1595887733334".
This happens because on line 2261 value of the eTag variable is changed:
  if (eTag.startsWith("W/")) {
        eTag = eTag.substring(2);
  }

and then it goes to response.
The PR fixes this. Also I tried to make the both checkIfNoneMatch() and checkIfMatch() functions looking similar.
Now we can extract their common logic to a separate function.

The entire ETag handling requires an overhaul.

In reviewing this PR I've noticed another issue. The ETag obtained from the resource is unconditionally made strong before the comparison but that conversion should depend on useWeakComparisonWithIfMatch.
I'm not convinced of the case for aligning the two methods and fixing this new issue looks like it will weaken that case.
The test case change looks good. I'll add that, add a test for the new issue and then look at a fix for both issues.

yes, you are right and I wanted to discuss it latter. The PR fixes only one specific problem + small refactoring.
The problem that I see is that the new useWeakComparisonWithIfMatch flag is not complaint with RFC because it always should be strict.
An origin server MUST use the strong comparison function when comparing entity-tags for If-Match (Section 2.3.2), since the client intends this precondition to prevent the method from being applied if there have been any changes to the representation data.

In fact as far I understood the weak comparison for If-Match was implemented by mistake in scope of b26ad77f659de34d49dda5a248566a38383cec0e. And this happened recently. That means that in fact here we making the bug as a feature. This may have sense if there is a lot of users who used this behavior but in fact we definitely haven't any of them.
Did I miss something? Can we simplify logic and and inline useWeakComparisonWithIfMatch as a false?

I added a commit that extracts common matching logic

Let me go an look at b26ad77 in more detail. If the switch to weak comparison was introduced there then the case for fixing that and dropping useWeakComparisonWithIfMatch entirely is much stronger.

After looking at b26ad77 I have reverted the addition of useWeakComparisonWithIfMatch and switched If-Match to strong comparison. I've also fixed the regression you identified. With these changes the If-Match and If-None-Match code has diverged a little further. I thin kthe case for refactoring is rather borderline at the moment but take a look at the new code and see what you think.

I reviewed and it looks fine and simpler. I just want to note here for history that according RFC 7232 sec 2.3.2 if resource's real etag is weak than strong comparison always failed:

ETag 1
ETag 2
Strong Comparison
Weak Comparison

W/"1"
W/"1"
no match
match

W/"1"
W/"2"
no match
no match

W/"1"
"1"
no match
match

"1"
"1"
match
match

That's why in my version I added the note:
        // BZ 64265: By default Tomcat generates weak etag for resource.
        // But If-Match uses strong matching that expects a strong resource etag.
        // So we strip any leading "W/" and then compare using equals
        String resourceEtag = weakEtagToStrong(eTag);

I.e. that code is a workaround for fact that Tomcat generates weak ETag for static resource while should generate strong (that was discussed in #324). Now when client will send the received weak etag it will always get 412. And this is correct according spec but may be unexpected for a client. But I'm pretty sure that nobody uses the If-Match anyway: a browser never sends it.
I think that we should keep this version and instead in some feature releases switch Tomcat to generate strong etags by default.
But this is another story.


Hello, can you share the cleaned dataset?

Hello, can you share the cleaned dataset?I want to try to do text style transfer.

@Algabeno
Hello there!
data/quote-nlp-dataset_cleaned.csv should be the file you are looking for. I also added separate model training file notebooks/textthema-multi-classifier-model.ipynb, where you can load the file and get started right away.

I saw it, thank you very much! !


remove obsolete todo in doubleClamp lint

Also slightly adjusts the messages to avoid encouraging people to add the ignore in cases we don't want to ignore.

cc @gaaclarke


Feature request: disable polling/notifications

Is your feature request related to a problem? Please describe.
As an operator of a Camunda BPM 7 installation, I want to disable any polling mechanism, so that I can connect using an SMTP-only server (no POP/IMAP access).
Describe the solution you'd like
As soon as I do not configure mail.store.protocol, integration with the Camunda-internal notification system shall be skipped entirely.
Describe alternatives you've considered
none, since I am an operator.
Additional context
When using a mail service such as SendGrid or similar, often there is no IMAP or POP3 access available (nor wanted) since using these is for send-only cases without any mailboxes in the traditional sense.

Hello @enote-kane ,
thank you for providing this input.
Have you already configuring a pure SMTP connection and only use the send connector?
Due to the project structure (and target audience), there is no need to have a send-only mode.
What would you think about having a separate sendgrid connector just like it is in place in Camunda 8?

Hi @jonathanlukas , thank you for the response.
Well, I am using the camunda-bpm-run Docker container and have only followed the docs here: https://github.com/camunda-community-hub/camunda-platform-7-mail/blob/main/extension/spring-boot/README.md
And as soon as I skip configuring the store protocol, the Camunda BPM Run startup throws the following at me:
<#4c95cfe7> javax.mail.NoSuchProviderException: Invalid protocol: null
        at javax.mail.Session.getProvider(Session.java:489)
        at javax.mail.Session.getStore(Session.java:588)
        at javax.mail.Session.getStore(Session.java:568)
        at javax.mail.Session.getStore(Session.java:554)
        at org.camunda.bpm.extension.mail.service.JakartaMailService.provideStore(JakartaMailService.java:38)
        at org.camunda.bpm.extension.mail.service.JakartaMailService.getFolder(JakartaMailService.java:60)
        at org.camunda.bpm.extension.mail.notification.MailNotificationService.supportsIdle(MailNotificationService.java:121)
        ... 26 common frames omitted
Wrapped by: <#b5ceb084> java.lang.RuntimeException: javax.mail.NoSuchProviderException: Invalid protocol: null
        at org.camunda.bpm.extension.mail.notification.MailNotificationService.supportsIdle(MailNotificationService.java:134)
        at org.camunda.bpm.extension.mail.notification.MailNotificationService.getNotificationWorker(MailNotificationService.java:98)
        at org.camunda.bpm.extension.mail.notification.MailNotificationService.doStart(MailNotificationService.java:71)
        at org.camunda.bpm.extension.mail.notification.MailNotificationService.start(MailNotificationService.java:63)
        ... 23 common frames omitted

Would it be that hard to add an enable/disable switch to the MailNotificationService?
In the top-level README, I see 3 connectors made available by this project, so the expectation I had was that I could configure each of them, not that configuration for all would be mandatory.

Hi @enote-kane ,
thank you for the concrete feedback.
I would now put it like this:
When using spring-boot, I want to be able to disable the notification service.
That's quite easy to ship I guess.

OK, sorry for misleading terminology. Feel free to adjust it then.
But essentially your first interpretation wasn't that wrong. Essentially I only want the "mail-send" connector to be provided in the Camunda BPM engine that I am managing for our devs/users, so yeah, I don't want them to be able to listen on incoming emails, neither to allow anyone to delete some emails.
I mean it would still be OK if the connector itself was there but just throwing an error when attempting to actively use it - if that makes any difference.

I will handle it that way first.
The second request could then be to preserve the connectors as they are, but splitting them up in different modules, so that they could be excluded/seperately included?

ACK, sounds like a plan! Thank you

Hi @jonathanlukas, this would be a useful fix for me too - do you have any upcoming plans to create a release? :)

I will create a release this week


SqlLab ResultsTable Formatting long strings

Screenshot

Description
I am using SqlLab to query my data that having very long String i.e. > 10000 , SqlLab results table at the moment truncates the string with ellipsis and the result table width is too big .This all makes it hard to read. I tried to add some word=wrap
in FilterableTableStyles.less , However it is overflowing and I was not able to fix it. Is there a way I can enable word wrap , reduce the result table width and stop overflow so all results appear nicely?
.ReactVirtualized__Table__rowColumn {   /* text-overflow: ellipsis; */   /* white-space: nowrap; */   white-space: pre-wrap !important;   word-break: break-all !important;   flex-wrap: wrap !important;

@ktmud any thoughts on a way we could solve this issue? My instinct would be to add a tooltip for text that's truncated, as that preserves the layout but I'm unsure of how feasible that would be.

@nytai I finally fixed this issue my adding new CSS  inline style for rows in FilterableTableStyles.less . However it would be nice to control it somehow via superset config variable so that anyone wants data to appear in multiple rows they can enable it.

Is anyone still seeing this as an issue in Superset 1.5.x or 2.0.x? Also, I'm on the fence as to whether this is truly a "bug" or more of a feature request. If this has been solved, @pabrahamusa, would you be interested in carrying your solution forward in a PR of some sort? Leaving this open for now, but will close it if nobody is interested in pursuing this.


New OpenSlides logo.

Thanks to René, our logo designer!

all done in new commit

ready for last review

Added MIT license info to README and each svg file.
Rebased all changes to one commit.
Ready for last review and merge.

@normanjaeckel ping

Ok.

I don't like that the logo lays in this repo. But if you can accept, that we remove it from this place before the 2.0 release, then you can merge this.


skip commit secondary key

In this PR, we skip committing secondary key.

/run-all-tests

/run-all-tests

/run-all-tests


[SUC-123] First PR

ia

Current dependencies on/for this PR:

main

PR #1   👈

PR #2

PR #3

This comment was auto-generated by Graphite.


Correction for raw affiliation INSERM CIC 1414, INPHY, Université de Rennes 1  Rennes France

Correction needed for raw affiliation INSERM CIC 1414, INPHY, Université de Rennes 1  Rennes France
raw_affiliation_name: INSERM CIC 1414, INPHY, Université de Rennes 1  Rennes France
new_rors: 015m7wh34;02vjkv261;02baj6743
previous_rors: 015m7wh34;02vjkv261
works_examples: W4321167764
contact: 4e37ceb37551ff39ac82b6536d82dc6c:39ad8538405d75d50ae32245f669e6f7 @ univ-rennes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


Basic Kubernetes Docs

What?
Basic configuration docs for Kubernetes
Why?
Operators need to know what configs are required to run Heron on k8s

@jrcrawfo - is this ready to go?

@kramasamy @jrcrawfo This page has already been added to the docs:
https://twitter.github.io/heron/docs/operators/deployment/schedulers/kubernetes/
https://github.com/twitter/heron/blob/master/website/content/docs/operators/deployment/schedulers/kubernetes.md
I'd recommend closing this PR.

The Kubernetes support in Heron has changed dramatically from the initial iteration and we now have documentation for that new setup here: https://twitter.github.io/heron/docs/operators/deployment/schedulers/kubernetes/.


Focus not set correctly to editor when using up/down keys

Create two cells
Set focus to first cell editor
Press down arrow

Expected behaviour

Cursor should be in second cell (i.e. second cell should be focused)

Currently it is selected
Current release version of extension works as expected.
Here's the current master extension

Here's the current release extension

Validated with the most recent VSIX in our release branch.


Fix empty solve

#6160
This PR fixes linalg.solve and linalg.inv for empty inputs.  As a consequence, linalg.tensorsolve and linalg.tensorinv are fixed, too.

/test

run jenkins please


Add support for converting with-items

This PR adds support for converting Mistral's with-items and concurrency task attributes.
See this page of the Mistral docs for some examples.
with-items:
  - i in <% $.yaql_data %>

with-items:
  - i in <% $.yaql_data %>
  - j in <% $.more_data %>
  - k in <% $.all_the_data %>

with-items: i in <% $.yaql_data %>
concurrency: 2

with-items: i in {{ _.jinja_data }}

with-items: i in [0, 1, 2, 3]

should produce the following in orquesta
with:
  items: i in <% ctx().yaql_data %>

with:
  items: i, j, k in <% zip($.yaql_data, $.more_data, $.all_the_data) %>

with:
  items: i in <% $.yaql_data %>
  concurrency: 2

with:
  items: i in {{ ctx().jinja_data }}

with:
  items: i in <% [0, 1, 2, 3] %>

There is quite a bit of code churn in the pack tests, and it was a little difficult for me to extract the churn from the additional tests, so I recommend looking at the end results than the commit diff for that. I added quite a few additional fixtures for the integration tests for the pack client.
Interpreting and converting the with-items list correctly requires that all items in the list utilize the same expression format (eg: either all static/Jinja expressions or all static/YAQL expressions), however, it does not validate that.
Also, this does support syntax like:
with-items: i in [0, 1, 2, 3]

and converts it to:
with:
  items: i in <% [0, 1, 2, 3] %>

because we have some workflows that utilize that. I'm not 100% sure it's valid Mistral syntax, but since Mistral does seem to run it just fine I wanted to convert it to a more proper format that Orquesta can run just fine as well.

Codecov Report

Merging #17 into master will increase coverage by 0.13%.
The diff coverage is 97.72%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
+ Coverage   98.24%   98.38%   +0.13%
==========================================
  Files          11       11
  Lines         457      496      +39
==========================================
+ Hits          449      488      +39
  Misses          8        8

Impacted Files
Coverage Δ

orquestaconvert/workflows/base.py
100% <100%> (ø)
:arrow_up:

orquestaconvert/pack_client.py
92.47% <75%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


fixed typo

pilepine=>pipeline
chosing=>choosing
additioanlly=>additionally
attachmment=>attachment
initialize=>inititialize
Binded=>Bound
lattest=>latest
hi @raysan5, I ran rlgl.h into some "typo checking" program(basically a JetBrains IDE), and here are all the things that the program was able to spot and fix. as my English isn't really well I would like it if you could check that I didn't make any mistakes in the typo fixing...

@sDos280 Thank you very much for the grammar review! Really appreciated! 👍😄


Cherry picker tutorial

When setting the overlaps for the cherry it is not possible to drop agent or item in the correct slots of the "on sprite of kind Player overlaps otherSprite of kind Player" block.

You don't actually need to change the names of the parameters in the function. Especially because we use agent as a global variable (item is a global variable, as well, though its use is less consequential), I think we should revert to using the defaults sprite and otherSprite. It might be a good idea, at this point in the lesson, for the students to be introduced to the idea local variables, even if we don't actually mention them specifically. I'm thinking a bit of a Piaget element: Use local variables, but let the students pick up the idea in their own time.
I can prep a pull request with these changes, Before I do, though, @ChaseMor  and @jwunderl, what do you think?

agent was the default name for sprites for like a week I think, which is why it's listed on there weirdly. @alex-kulcsar feel free to make a PR changing /agent/mySprite/ (and maybe /item/cherry/ when they're create?) would be a good fix for sure -- and I also think it should use the standard sprite / otherSprite as you mentioned.
Thanks for looking into this (and if you're busy or anything I'm happy to make the changes as well, though I will defer to you for now)!

Thanks, Joey. I'll take care of this tonight after class.


Add table aws_waf_web_acl

References
Required for FSBP > [WAF.1] AWS WAF Classic global web ACL logging should be enabled
https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-standards-fsbp-controls.html#fsbp-waf-1

Waiting on AWS issue Case ID<PHONE_NUMBER>


should the setup scripts from dev-tools repo be merged into this repo?

During oneops build oneops-setup.sh script copies setup scripts from dev-tools repo. The scripts uses this repo url https://github.com/oneops/dev-tools which gets redirected to https://github.com/oneops-archive/dev-tools. It is redirecting to oneops-archive repo. should these setup scripts be added to main oneops repo

@rameshjanjyam : we are going to refactor the setup in the future with ansible playbook so let's stay put on that for now.


Foi trocado o URL da extensão Sussy Scan. PT-BR

Source information
Sussy Scan 1.4.41
Source language
Português PT-BR
Source new URL
https://new.sussytoons.site/
Other details
O site antigo ainda está no ar mais pararam de atualizá-lo e só estão atualizando o novo site.

Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

Duplicate of #6034


bulk push notifications

I want to know is there any way to send push notification to multiple devices at a time..in "to" parameter can we able to pass array of the registered device ids..
The curl syntax,
curl --header "Authorization: key=SERVER_API_KEY"
--header Content-Type:"application/json"
https://gcm-http.googleapis.com/gcm/send
-d "{ "data" : { "title" : "MyCoolApp", "text" : "MessageText", "extra":{"url":"someurl.js"}}, "to" : "$DEVICE_TOKEN" }"

Also it's not related to the plugin, you can check the details below
https://developers.google.com/cloud-messaging/http-server-ref#send-downstream

Thanks..that was really helpful.


Add codecov badge

Codecov Report

Merging #20 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #20   +/-   ##
=======================================
  Coverage   67.44%   67.44%
=======================================
  Files           7        7
  Lines         470      470
=======================================
  Hits          317      317
  Misses        153      153

Continue to review full report at Codecov.

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


Speed up line break prop lookup

Currently it uses 2-level linear probe. Use LUT for BMP, and binary search for higher codepoints.

Regardless of the minor issues, the performance boost is real. Thanks.

Merged.
What name would you like me to use in AUTHORS?

确定不想用真名？目前的 AUTHORS 文件里全是真名的。


Fix flaky test of visualization tool

Description
This PR is add waiting for model to be undeployed to fix flaky test introduced by #2363,
https://github.com/opensearch-project/ml-commons/actions/runs/8933312245/job/24539185907?pr=2402
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks @Hailong-am for fixing the flaky tests. @ylwu-amzn This issue is not just for flaky tests. The undeploy response is giving UNDEPLOYED immediately but we still have to rely on get model to see if the model is indeed undeployed. Could be confusing to users. We should either give a task_id or say something like UNDEPLOY INITIATED in the undeploy response if the model is not completely undeployed

Thanks @Hailong-am for fixing the flaky tests. @ylwu-amzn This issue is not just for flaky tests. The undeploy response is giving UNDEPLOYED immediately but we still have to rely on get model to see if the model is indeed undeployed. Could be confusing to users. We should either give a task_id or say something like UNDEPLOY INITIATED in the undeploy response if the model is not completely undeployed

Seems like @ylwu-amzn created an issue for this.

Do we need to backport this to 2.14 branch? I don't see any backport label to this PR.

Do we need to backport this to 2.14 branch? I don't see any backport label to this PR.

I think this test case seems not flaky in the Release CI workflow. We don't see IT failure report yet. To not block the whole release. I think it's fine to not backport


Exact version dependency on SQLite.swift can cause resolution conflicts

Describe the bug
In Package.swift, the dependency on SQLite.swift is declared with an exact version match:
.package(url: "https://github.com/stephencelis/SQLite.swift.git", exact: "0.13.2"),
While this can be good practice when defining dependencies for applications, it is better avoided in libraries that may be added to projects that depend on other libraries that may share the same dependency but which require a newer version
Steps To Reproduce

Create a new package in Xcode
Add a dependency to "https://github.com/stephencelis/SQLite.swift.git" with a version requirement that's greater than 0.13.2:
.package(url: "https://github.com/stephencelis/SQLite.swift.git", from: "0.13.3")
Add Amplify as a dependency
Package resolution will fail due to impossible to satisfy version constraints

Expected behavior
I'd expect to be able to use Amplify with other libraries that also depend on SQLite.swift, even if the require newer versions of said library.
Amplify Framework Version
2.1.0
Amplify Categories
Analytics, API, Auth, DataStore, Geo, Predictions, Storage
Dependency manager
Swift PM
Swift version
5.7
CLI version

Xcode version
14.1
Relevant log output
No response
Is this a regression?
No
Regression additional context
No response
Device
All
iOS Version
All
Specific to simulators
No
Additional context
No response

This is an intentional decision to pin to an exact version to avoid unplanned, unreviewed, untested dependency upgrade.


feature: Add option to display newer logs at the top

Did you check the docs?

[X] I have read all the docs

Is your feature request related to a problem? Please describe.
I think that it is a better UX to display the newest logs in the floating log output window at the top.
Currently when I want to check what's changed between logs (sometimes I log big objects) I have to open the floating window, hit C+w C+w to focus it and scroll to the bottom to see the newest result.
Describe the solution you'd like
Maybe add a property to the opts table of open_float ?
Something like require('timber.buffers').open_float({sort: 'asc' / 'desc'})
Or maybe add a setting to the opts table of the plugin?
'Goose97/timber.nvim',
opts = {
...
  log_summary = {
    ...
  },
  log_float = {
    sort = 'asc',
    silent = false,
  },
}
...

Describe alternatives you've considered
Can't think of something else.
Additional context
No response

That's a good use case. I tend to log small stuff so I just view them at the log snippet directly. But I think your use case is valid as well.
It should work now
require("timber.buffers").open_float({ sort = "newest_first" })

Pffff, amazing, thank you very much! It's working perfectly.


Changes: SC version and build tag.

Codecov Report

Merging #132 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #132   +/-   ##
=======================================
  Coverage   67.32%   67.32%
=======================================
  Files          18       18
  Lines        4190     4190
=======================================
  Hits         2821     2821
  Misses       1194     1194
  Partials      175      175

Impacted Files
Coverage Δ

server/service/services_dependency.go
67.6% <0%> (-0.71%)
:arrow_down:

server/service/instances.go
67.16% <0%> (+0.13%)
:arrow_up:

Continue to review full report at Codecov.

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

Coverage decreased (-0.06%) to 71.703% when pulling c1184ff58faaac60aad57d8b8b68e7ef8a44f51c on little-cui:master into 5d9a5908730d27b734e75d9fef9a9f9f77631b86 on ServiceComb:master.


NetworkPlugin cni failed to set up pod "backend-xxxx" network: add cmd: failed to assign an IP address to container

Hello
This problem happens when I try to scale my pods. The flow to get the error is:
kubectl scale --replicas=14 deployment/backend

backend-76cc5f5966-4lj6v   0/1       ContainerCreating   0          1h        <none>       ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-4wx76   0/1       ContainerCreating   0          1h        <none>       ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-57n5t   0/1       ContainerCreating   0          1h        <none>       ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-7kmbw   0/1       ContainerCreating   0          1h        <none>       ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-9pw5g   1/1       Running             0          1h        <IP_ADDRESS>   ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-9twf5   1/1       Running             0          1h        <IP_ADDRESS>   ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-fr69q   0/1       ContainerCreating   0          1h        <none>       ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-m5kld   1/1       Running             0          18h       <IP_ADDRESS>    ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-m8x95   1/1       Running             0          1h        <IP_ADDRESS>   ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-rbtv5   0/1       ContainerCreating   0          1h        <none>       ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-rf5j5   0/1       ContainerCreating   0          1h        <none>       ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-t9px6   1/1       Running             0          1h        <IP_ADDRESS>   ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-vjwlb   0/1       ContainerCreating   0          1h        <none>       ip-10-3-2-134.us-west-2.compute.internal
backend-76cc5f5966-wr9rr   1/1       Running             0          1h        <IP_ADDRESS>   ip-10-3-2-134.us-west-2.compute.internal

Getting describe over one of pods that fail:
  Normal   SandboxChanged          18m (x516 over 1h)  kubelet, ip-10-3-2-134.us-west-2.compute.internal  Pod sandbox changed, it will be killed and re-created.
  Warning  FailedCreatePodSandBox  3m (x605 over 1h)   kubelet, ip-10-3-2-134.us-west-2.compute.internal  Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "backend-76cc5f5966-4lj6v_default" network: add cmd: failed to assign an IP address to container

AWS Instance Description:

Ingress
Name:             ingress-app
Namespace:        default
Address:          1be2e68f-default-ingress-app-3016-1608344470.us-west-2.elb.amazonaws.com
Default backend:  default-http-backend:80 (<none>)
Rules:
  Host              Path  Backends
  ----              ----  --------
  dev.ingress-app.com
                    /   backend:3000 (<none>)
Annotations:
  alb.ingress.kubernetes.io/target-group-attributes:  deregistration_delay.timeout_seconds=30
  alb.ingress.kubernetes.io/target-type:              instance
  kubectl.kubernetes.io/last-applied-configuration:   {"apiVersion":"extensions/v1beta1","kind":"Ingress","metadata":{"annotations":{"alb.ingress.kubernetes.io/certificate-arn":"arn:aws:acm:us-west-2:821745794127:certificate/bb3451c6-d3f8-41f0-8c2c-a08a68f0ad8c","alb.ingress.kubernetes.io/listen-ports":"[{\"HTTP\":80,\"HTTPS\": 443}]","alb.ingress.kubernetes.io/scheme":"internet-facing","alb.ingress.kubernetes.io/subnets":"subnet-0dade30445b089391,subnet-0d536db6f9f2b4a94,subnet-0bc24c9dfe29fa4f9","alb.ingress.kubernetes.io/tags":"Environment=dev,Team=test","alb.ingress.kubernetes.io/target-group-attributes":"deregistration_delay.timeout_seconds=30","alb.ingress.kubernetes.io/target-type":"instance"},"name":"ingress-app","namespace":"default"},"spec":{"rules":[{"host":"dev.ingress-app.com","http":{"paths":[{"backend":{"serviceName":"backend","servicePort":3000},"path":"/"}]}}]}}

  alb.ingress.kubernetes.io/certificate-arn:  arn:aws:acm:us-west-2:821745794127:certificate/bb3451c6-d3f8-41f0-8c2c-a08a68f0ad8c
  alb.ingress.kubernetes.io/listen-ports:     [{"HTTP":80,"HTTPS": 443}]
  alb.ingress.kubernetes.io/scheme:           internet-facing
  alb.ingress.kubernetes.io/subnets:          subnet-0dade30445b089391,subnet-0d536db6f9f2b4a94,subnet-0bc24c9dfe29fa4f9
  alb.ingress.kubernetes.io/tags:             Environment=dev,Team=test
Events:
  Type    Reason  Age   From                        Message
  ----    ------  ----  ----                        -------
  Normal  MODIFY  37m   aws-alb-ingress-controller  1be2e68f-default-ingress-app-3016 managed security groups modified

alb-ingress-controller:
Image:         quay.io/coreos/alb-ingress-controller:1.0-beta.6

Obviously, the target-group only has healthy checks over pods created:

It is as if cannot use the free secondary private IPs to assign to pods.
Thanks.

I know that Aws allows a maximum number of network interfaces per instance type https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html. In my case, I have m5.large type-instance with 3 ENI 10 IPV4. I have tried scale to 10 pods but is happens the same.

Hi Andres,
The alb behaves correctly(target group only contains healthy pods).
This issue is more likely a CNI issues(https://github.com/aws/amazon-vpc-cni-k8s/issues/59).

Would you help check the CNI image version using kubectl describe daemonset aws-node --namespace kube-system | grep Image, if it's below 1.1.0, it needs to be updated.
If it's already 1.1.0, you can SSH into the node and executing /opt/cni/bin/aws-cni-support.sh
and then send the /var/log/aws-routed-eni/aws-cni-support.tar.gz to me (yyyng@amazon.com), so we can investigate the issue.

Thanks for your help; I have updated CNI Image version and the problem has been fixed.


toJson empty

toJson does not have equivalent mustToJson, which shows parse errors, so now I sometimes get empty output from toJson without having a chance to find out why. May I ask why not all sprig functions are passed one on one as in Helm?

May I ask why not all sprig functions are passed one on one as in Helm?

@Morriz Tha's because I'm not entirely sure if all the Helm template functions also make sense in Helmfile's context, that I wanted to add functions as requested.
But is that important to you? Isn't this issue just a feature request to add mustToJson? 🤔

You are right. Indeed. That would be helpful.

@Morriz Thanks for confirming. I've surveyed a bit and mustToJson seems to have added since sprig v3.
https://github.com/Masterminds/sprig/commit/877c54268c342eac47b061bf5378383b9b816623
So this will soon be addressed by #1294, which I'll prioritize higher than before, according to your request.


How to delete/remove user if he last logged in 'x' days ago?

I did something like this.
The error: Exception in setInterval callback: TypeError: undefined is not a function
var days = 1;
Meteor.setInterval(function() {
var days_ago = new Date(new Date.getTime() - (360000 * 24 * days))
Meteor.users.find({'status.lastLogin.date': {$lte: days_ago}}).forEach(function(user) {
Meteor.users.remove({_id: user._id}, true);
});
}, (360000 * 24 * 1));

Meteor does something similar by pruning stale login tokens from the database, search for _expireTokens in the following:

https://github.com/meteor/meteor/blob/devel/packages/accounts-base/accounts_server.js#L1044

I used javascript to solve this problem. Running the script after every 'y'
hours, and deleting the users as required.
But if meteor has something inbuilt, then I'll surely look into it
Thanks

That built-in function is not doing the same thing; I just pointed to it as an example that was doing something similar.


Screencopy Protocol Support

Closes #262

Had to dig a little deeper and import the header file
In Build.rs, I tried to make it look a little cleaner. I'll take a look at the macro you described when I can.

I'm planning to continue doing this. Protocols are fun :)

Fixed up what you suggested. If all is good, I can squash the commits if you want me to.

Looks good, I don't mind squashing or not (it's up to you). If it passes I'll merge it in.

If you want to squash them, that's fine with me!

Thanks!


Remove InitializationArgument/Parameters from ContractAbi/ServiceAbi

Motivation
#1839
Proposal
Remove them from ContractAbi
Test Plan
CI

#1844  👈
main

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

Join @andresilva91 and the rest of your teammates on  Graphite


Update travis.yml to also commit data files

The Rmd will download the opera database into this repo:
https://github.com/enram/globam-dmp/blob/25938cdeeb1d44391ec49db7a9bd6b0bb8ec142d/src/europe.Rmd#L15
However, when the bookdown is running on Travis, that file will be downloaded, but not committed. We therefore need to update .travis.yml to include those commit steps.

This is no longer applicable, radar metadata is maintained at https://aloftdata.eu/radars/


Figure out why Gemfile and Gemfile.lock are causing issues

In a few threads now (e.g., https://github.com/jupyter/jupyter-book/issues/152) we've run into issues where a Gemfile.lock that was out-of-date caused issues in the book building.
Can we

Diagnose why this is an issue, and 2
Figure out a means (either documentation or tech) that can make this less problematic

Right now I have some documentation on running the upgrade under the docker section, but it'd be great to think about a better place for this !

I think people need to remember to upgrade the jupyter book. I couldn't find it in the documentation ...

It's clearly too short of a mention on my part :)

If you navigate to http://<IP_ADDRESS>:4000/jupyter-book/ in your browser, you should see a preview copy of your book. If you instead see an error, please try to update your local book; see the Jupyter Book FAQ section for more details on how to do so.

Where would this be better placed ?

Ahhhh ... haha I missed it too. I would place it as code, saying what to do:
$ jupyter-book upgrade

actually, now I am not sure if this would solve the problem. Where does the upgrade get the template book from? It seems to me that you need to upgrade your python package and run this command. Otherwise, it won't upgrade. Since it does not get the template from the web but from the installed repository (?)

Maybe we actually just shouldn't be distributing a Gemfile.lock:
https://ben.balter.com/jekyll-style-guide/gitignore/

Also, sorry, just to actually address @choldgraf 's question of why this is an issue !
jekyll serve is trying to rely on the Gemfile.lock to determine the exact versions of all gems that should be used in serving the site. When I built the Docker image I couldn't find a way to match those exact versions in a "light" environment -- right now, the Docker image is building off of one that Jekyll distributes, where they worked to shrink the filesize down. So if you try to run the site using the created container, you need gem versions that are not accessible in the environment. What is in the environment can run the site just fine, and when you delete the Gemfile.lock it will go ahead and do so. But as long as the Gemfile.lock exists it tries to match exactly those gem versions -- and it can't :disappointed:
So I see three possible solutions:

Try to rebuild the docker image to match the original Gemfile.lock, maybe for a slightly larger image
Update the documentation to make clear why this is happening and what to do
Just stop distributing the Gemfile.lock, as it sounds this isn't necessary -- especially for GitHub pages sites

Would love to know what direction seems most reasonable for moving forward !

hmmm, I kinda feel like "don't use gemfile.lock" makes the most sense. Doesn't it get created when you run the install?

Yes, but only if it's not already existing !

hmmm, so is there any downside to removing it from the copied template?


azartifacts preview v0.1.0

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

/check-enforcer override

Hi @jhendrixMSFT do we need to add some synapse data-plane specific information in this PR? For instance like the things added to go-autorest previously by this PR: https://github.com/Azure/go-autorest/pull/552

CI has not yet been hooked up for this module as the yaml hasn't been committed yet.
The codegen is self-contained, so no need to add anything else.  Long-term, I don't know that we'll add a similar environment table like we have in go-autorest.

The README has been added.


[Story] Instructions on how to update data on financial institution details

User story
As a filer, I would like clear instructions on how to change read-only financial institution fields, so that I can correct any errors prior to filing.
Acceptance criteria

Given a user views their FI details, when they discover their FI data is incorrect, then they are presented with clear instructions on how to update this data.

Depends on

#11

Technical tasks
Coming soon...
Context
No response

@angelcardoz @shindigira
What are the tasks needed for this story?


Evaluator syntax check

Please have a look at the individual commit messages for the details.

This change is

Merging despite the unrelated AppVeyor failure.


feat: improve EditPages for touchscreen

Changes：

improve EditPages for touchscreen

demo：
http://<IP_ADDRESS>/

please review @nodece

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


Fix to perform discovery on all discoveryIPs returned by CSP (#105)

Signed-off-by: Sneha Rai<EMAIL_ADDRESS>Co-authored-by: Sneha Rai<EMAIL_ADDRESS>

Creating with release-4.1 branch for CSI patch release.


Fix: add process context in workflow

Signed-off-by: FogDong<EMAIL_ADDRESS>Description of your changes

Add process context in workflow
Add workflowName & publishVersion in process context.

Fixes #3276
I have:

[x] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[x] Run make reviewable to ensure this PR is ready for review.
[x] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

/cc @barnettZQG

@captainroy-hy Please help review and merge this PR.


Create Demo day slide

User story

As a team
we want / need to create a slide for demo day (Project idea, team photo, logo,... (Real content is in demos))
So that it can serve as overview slide of our project for demo day introduction

Acceptance criteria

Logo included
Team photo included
All other relevant info (short summary) is included

Definition of done (DoD)

Linter & Checker were performed and passed
Code Review has been completed
Code was merged in sprint release candidate
Updates are written in issue comments
Feature builds and tests successfully
Acceptance by product owner
User Story & Acceptance Criteria fulfilled

DoD general criteria

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Developers agreed to release

demo-day-slide.pdf


Correctly process sqlalchemy_utils ChoiceType fields

Fixing issue with ChoiceType field described in https://github.com/flask-admin/flask-admin/issues/1134#issuecomment-317290816

Hi @bakatrouble    ,
the build is broken. Not a biggie. need to add workaround to install correct version of Postgist, flake8 got more stringent. There are too new requirements added: E722 and E741. You might need to add following changes:

to .travis.yml: https://github.com/flask-admin/flask-admin/pull/1556/files#diff-354f30a63fb0907d4ad57269548329e3 (to install correct version of postgis);
tox.ini https://github.com/flask-admin/flask-admin/pull/1556/files#diff-b91f3d5bd63fcd17221b267e851608e8 (to ignore E722);
flask_admin/contrib/sqla/tools.py: https://github.com/flask-admin/flask-admin/pull/1556/files#diff-70f36e099fa84f21ae730c1e207f8814 (to comply with E741 ambiguous variable name 'l');

That would fix the build.
Cheer!

Looks fine now

Is this likely to get merged? It would be very useful!

+1

Bump

Fixed conflicts

I'm sorry, but I can't accept this pull request.
SQLAlchemy is just one of the supported ORM backends. The change in question changes the core Select2Field implementation that has nothing to do with databases.
If you want to support Choice type - I would recommend subclassing it and putting it in contrib.sqla.fields. Then you can either override the form scaffolding logic (use custom field instead of generic Select2Field) or just explicitly use it by overriding the form settings in the view class.


RSPM: Run RSPM as rstudio-pm instead of root

Switching RSPM to run in non-root mode using default configurations building on https://github.com/rstudio/rstudio-docker-products/pull/269
As part of our high-level goals for the RSPM team, we would like to take over support of the RStudio Package Manager docker image (and eventually the helm chart). This is one of the first major changes we would like to make when the next official release, tentatively 2022.Q1, of RSPM is out.
Here we have:

[x] Switch the image to run as the rstudio-pm user by default
[x] Include the official configuration file, with the exception of AllowUnsandboxedGitBuilds = true
[x] Switch to the default data location
[x] Remove exposed port annotations
[x] Remove the --privileged flag from our Docker examples

After some discussions, we decided on defaulting the image to using AllowUnsandboxedGitBuilds = true because it means the Git functionality will work out of the box. We think that this is optimizing for the common case because most of our users are building trusted internal packages, so the risk of cross-contamination is minimum, that said there is certainly a risk we should acknowledge.
For these users, our current recommendation is to move to a system that has sandboxing enabled. In the future, we can consider supporting the --privileged and root installation more if we get a high volume of customers asking to use those features.

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

Is this a re-go at #269?

I believe this supercedes https://github.com/rstudio/rstudio-docker-products/pull/269

Allowing the image to run as a non-root user alone feels very safe to me, as done in https://github.com/rstudio/rstudio-docker-products/pull/269. But this PR is different, running the image as both non-root and unprivileged, which means Git sandboxing must be disabled.
Are we okay with disabling Git sandboxing by default? We talked about the risks of that earlier at https://github.com/rstudio/package-manager/pull/6390#issuecomment-905579728. Maybe it's safer to run unprivileged than to disable sandboxing, but at least the --privileged flag is more explicit than having sandboxing disabled in the default config.
Jon had suggested changing Launcher.ServerUser to a different user from rstudio-pm, so at least the Launcher jobs would be isolated from RSPM data. That might be a simple enough improvement. Or we could figure out how to get sandboxing to work in unprivileged containers, as @atheriel mentions at https://github.com/rstudio/package-manager/issues/7443.

Tyler and I spoke about this a bit as well. Currently I think the need to use --privileged is very unsafe and I think non-sandboxed builds are a better security option for most users. However, I'm not sure disabling the sandbox is the right default, I'd rather have users make an explicit choice to use it (with --privileged, at least for now) or not (by setting the config entry, or potential an environment variable in future releases).
But in the defence of this current PR, the changes to the README make it very clear we're disabling sandboxing.

@glin This PR is meant to bring the Package Manager image back into the recommended configuration and making it possible to migrate the dogfood sites to.

Jon had suggested changing Launcher.ServerUser to a different user from rstudio-pm, so at least the Launcher jobs would be isolated from RSPM data. That might be a simple enough improvement.

This seems like the right answer to me, is there anything special we need to do to facilitate that again?

@atheriel @tylfin That reasoning sounds good to me. I would prefer it to be an explicit choice, or at least explain the difference between --privileged/sandboxed vs. unprivileged/unsandboxed so users can choose. Right now, the README suggests that the default is unsandboxed and insecure, but doesn't explain that sandboxed could actually be more insecure because of the --privileged limitation.
@tylfin For Launcher.ServerUser, I'm not sure, I tried it a while back but couldn't get it to work because of the launcher_internal permissions issue (https://github.com/rstudio/package-manager/issues/6388#issuecomment-905801455). I don't think I tested whether a manual chown of the launcher_internal directory would work around it, and maybe it does. You can try it out here. I think we'll also need a separate Launcher.AdminGroup since that defaults to rstudio-pm as well.

I tried using a different Launcher.ServerUser and it unfortunately doesn't work :cry:. First, both RSPM and the Launcher need read/write access to the launcher_internal directory, which is annoying but can be worked around. The big issue is that RSPM requires Launcher.ServerUser to be the same as the RSPM user if RSPM isn't running as root:
2022/02/17 23:41:02 Error: Unable to initialize the configuration: The service is currently running as 'rstudio-pm' but Launcher.ServerUser is configured to run as rstudio-pm-launcher. If the service is not running as root, we cannot run the launcher as a different user.

https://github.com/rstudio/package-manager/blob/d130806e15b0114e450f84616f649774e81d3bd7/src/rspm/config/config.go#L1253-L1259
Running RSPM as root with Launcher as rstudio-pm might be better, but then you hit another known issue with root RSPM requiring --privileged or other Docker security flags (https://github.com/rstudio/package-manager/pull/6390#issuecomment-1042323544).

But for the specific goal of serving our dogfood sites, isn't the sandboxing change to the default config irrelevant because those sites will use non-default configurations anyway?

Oh that's true, I also wanted things to just work out of the box for customers, but if there's a better way to accomplish it I'm game

Note: Do not merge. These breaking changes are scheduled for the next official RSPM release.

cc @atheriel now that 2022.04 is out, can we revisit this? Is there anything blocking its release?

@tylfin Nothing I am aware of at this point. LGTM.

This definitely strikes me as something that we should throw into NEWS.md 😄


Is this repo still maintained?

Hi,
Is this repo still maintained? If not, would it be possible for my organisation Prima.it to take ownership?
Cheers

Hello @milquetoastable, we are in the process of getting this project back off the ground.
Please send pull requests if you are interested in improving the project and we will be happy to review!

Brilliant, thank you!

@milquetoastable i now have maintainer access on this project. Are you interested in helping close any of the open issues?


Ask after a elementary desktop or elementary/files docker :-D

Can you make a docker? for:
https://github.com/elementary/files
with or without elementary desktop
in your: https://hub.docker.com/u/x11docker
be very happy if u can make it :-D
Maybe so right to "/" all connected hard disk inside pc and then connected "usb sticks" and "usb hard disks"

Currently I don't have a useable internet connection to build and try new images.
A Dockerfile like this one might work:
FROM elementary/docker:stable
RUN apt-get update
RUN apt-get install -y files
CMD files

Please try out. The package name might be different, as well the command name.


unify_core with transparency.none unfolds 0

This is slightly unexpected, as you cannot unify 0 with nat.zero but you can unify x + 0 with x + nat.zero:
set_option pp.all true
open tactic

-- fails, as expected
example := by do
a ← to_expr `((0 : ℕ)), b ← to_expr `(nat.zero),
unify_core transparency.none a b,
triv

-- works
example (x : ℕ) := by do
a ← to_expr `((x + 0 : ℕ)), b ← to_expr `(x + nat.zero),
unify_core transparency.none a b,
triv

If I see it correctly, then this happens because of the call to type_context::try_nat_offset_cnstrs.  Should we only call try_nat_offset_cnstrs in transparency reducible and above?


How to add Firefox browser support?

Workflow version
2022.5
Alfred version
5.0.6
macOS version
13.1
Debugger output
Not a supported browser

More details
I understand it's happening because it's not Chromium based. But is there anything I can do on my end to Firefox support?
No worries if too complicated. It's honestly not a big deal and don't use it a lot.
Thanks anyways. Love the new update, looks very clean.

is there anything I can do on my end to Firefox support?

Copy the link to your clipboard. dv and da support that as well and should tell you so in the subtitle.

Love the new update, looks very clean.

Than you.


VecEnvWrapper is not defined in env_wrappers.py

Thanks, and could u point out where the VecEnvWrapper is used?

https://github.com/marlbenchmark/on-policy/blob/45a13c6de9cd5a6332ebf9a709cc80e880dc5052/onpolicy/envs/env_wrappers.py#L128

Thanks for pointing out that, this function is not used actually, I will delete it.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_3emy906_i2/clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_3emy906_i2/clone/recipe/meta.yaml:26: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_3emy906_i2/clone/recipe/meta.yaml:33: http_url: http://github.com/gazpachoking/jsonref is not https
WARNING: /tmp/abs_3emy906_i2/clone/recipe/meta.yaml:33: missing_description: The recipe is missing a description
ERROR: /tmp/abs_3emy906_i2/clone/recipe/meta.yaml:33: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_3emy906_i2/clone/recipe/meta.yaml:33: missing_dev_url: The recipe is missing a dev_url
Errors were found


How are you guys calculating peak frequency?

Not exactly sure how to do this. Any suggestions?

We have used  scipy.signal and  imported find_peaks


Remove "GhostingServer.java"

This needs to be an issue so I don't forget about it before merging into master :P

What even was Ghosting server? Was this for ghosting mod?

It's for Ghosting Mod. There's one in the Ghosting repository too which I think is actually less up-to-date. This should really be fixed.

Yeah I needed somewhere to code and test it so I quickly threw it into my Botnak project and forgot about it when I pushed. I'll fix this next update.


Error at boot: eudev complains about an invalid key/value pair

Your system information

Steam client version (build number or date): <IP_ADDRESS>
Distribution (e.g. Ubuntu): Devuan 3 (beowulf)
Opted into Steam client beta?: No
Have you checked for system updates?: Yes
Eudev version: 3.2.7

Please describe your issue in as much detail as possible:
At boot, eudev complains about an invalid key/value pair:
udevd[425]: invalid key/value pair in file /lib/udev/rules.d/60-steam-input.rules on line 42, starting at character 82 ('u')

Offending line:
KERNEL=="input*", ATTRS{name}=="Lic Pro Controller", RUN{program}+="/bin/sh -c \"udevadm test-builtin uaccess /sys/%p/../../hidraw/hidraw*\""

It seems that eudev doesn't like escaped double quotes. I'm not sure whether to report it to the Eudev folks.

@xrogaan at a first glance this looks like something to report to eudev folks, I think. Here's the PR that added that feature to systemd-udev:  https://github.com/systemd/systemd/pull/6890

If eudev is meant to be compatible enough with original udev that it reads the same rules files, then it needs to accept all the same syntax, including escaped quotes; so yes, please report that to the eudev developers.
Having said that, for this particular rule, it might be possible to work around this by replacing the escaped double quotes with single quotes. Please try that? Something like this:
KERNEL=="input*", ATTRS{name}=="Lic Pro Controller", RUN{program}+="/bin/sh -c 'udevadm test-builtin uaccess /sys/%p/../../hidraw/hidraw*'"

udev(7) (from systemd 245.6) says "Single quotes can be used to specify arguments with spaces" and doesn't actually document escaped double quotes, so it seems the version in my previous comment might be the preferred form anyway.

Their issues tracker is also available on github. I'm not well versed in all the udev/eudev backend, and I'm afraid I wouldn't be capable to building a proper argument for them to be "more like systemd". The only thing I can come up with is that eudev will be broken if systemd's become prevalent over a saner approach (escaping is ugly and confusing).

While this could potentially be addressed in eudev, it seems easier all round to just use single quotes here so I've submitted a pull request.

I'm not well versed in all the udev/eudev backend

udev and systemd were originally separate projects (udev is much older), then they merged into one source tree in version 183 to be able to share code and maintenance. They're still semi-separate, and you can still use udev without booting with the systemd service manager: that's how it works in Debian systems that have been configured to boot using sysvinit, in older Ubuntu systems that boot using Upstart, and in initramfs environments. However, some people dislike systemd enough to consider that to be insufficient separation, resulting in a fork of udev under the name eudev, which is used in Devuan and optional (I think?) in Gentoo.
The escaped double quotes will also be a problem for older versions of the original udev (including any version older than the merge with systemd, if anyone is still using those). systemd/systemd#6835 was reported against the version of udev included in systemd 233, so this will affect Debian 9, Ubuntu 16.04 and contemporary distributions.
I think the right answer to this is to change steam-devices' udev rule to use single quotes (#11), and teach eudev to understand escaped double quotes so that it's more compatible with newer udev versions.

Gentoo defaults to eudev but gives you a choice of that, standalone udev, udev with systemd, or even mdev, which I do use on one oddball ARM system.

Updated udev rules released in steam-launcher <IP_ADDRESS> (currently a beta, should become the stable release later).


DefaultValue is set to '' when the value is false (for custom editor)

I have a custom editor - the values it accepts are boolean - true/false.
In TableEditColumn.js, line #176, there is this line
        defaultValue: fieldValue || '',

When the fieldValue happens to be false, defaultValue will get set to ''.
This line should probably be
defaultValue : fieldValue === undefined ? '' : fieldValue

ok, I'll handle it on next version, thanks

Wonderful - thanks

Fixed on v3.3.0, thanks :)


Causal Impact R package missing

I came across a situation where I wasn’t able to use an R visual in a Power BI service. It works perfectly fine in the desktop version.
Can you please add the Causal Impact R package? https://cran.r-project.org/web/packages/CausalImpact/CausalImpact.pdf
Thank you very much!

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

ID: df17e088-5cff-4882-79fc-cc7deb09843d
Version Independent ID: 641ddc87-0314-47c4-bee7-684ebe7f8e6e
Content: Learn which R packages are supported - Power BI
Content Source: powerbi-docs/service-r-packages-support.md
Service: powerbi
Sub-service: powerbi-desktop
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @valc1 . We’ve forwarded your feedback to the writer, who should respond to this thread shortly. Thanks!

Thanks for your post - the best place for you to submit product feedback or feature ideas like this (and perhaps get others to request it, as well) is by going to https://ideas.powerbi.com.


Overleaf Template Gallery

It might be helpful to have an official overleaf template for Compositionality Journal. The instructions for how to load it are here. Is that something that the editors would support?

Hi James, great idea. The overleaf template is now available here.


Set-AzResource : Cannot convert 'System.Object[]' to the type 'System.Collections.Hashtable' required by parameter 'Tag'

The title describes the issue.
$tags += @{ResourceType="VM"} results in a System.Object resource, checked via $tags.GetType()
While Set-AzResource ... -Tag x -Force expects x to be a Hashtable.
When I first create an empty Hashtable it seems to be ok, but when I run the below command, the name changes.
$tags = (Get-AzResource -ResourceGroupName $rg -Name $vm.Name).Tags

On an Azure subscription where it doesn't work, this is how it looks: (first is empty hashTable, 2nd is "filled" (Get-AzResource...).

Further investigation shows that $tags = (Get-AzResource -ResourceGroupName $rg -Name $vm.Name).Tags returns an 'Object[]' in some subscriptions and in other subscriptions it returns 'Directory`2'.
Not sure why, but when it returns 'Object[] - System.Array' it causes problems when trying to add a tag.

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

ID: 51b8967d-d023-899c-1418-bccabcd36314
Version Independent ID: 9bbf8516-4d1f-87f4-9af9-8715e5c9ec62
Content: How to tag a VM using PowerShell - Azure Virtual Machines
Content Source: articles/virtual-machines/tag-powershell.md
Service: virtual-machines
GitHub Login: @cynthn
Microsoft Alias: cynthn

@DiSae we'll review your feedback and get back to you shortly. Thanks.

@DiSae we'll review your feedback and get back to you shortly. Thanks.

@DiSae You can also update the tags using the Get-AzVm and Update-AzVm cmdlets. For Example:
Get-AzVm -ResourceGroupName myResourceGroup -Name myVM
$Vm.tags.Add("testtag","testtag")
Update-AzVm -vm $vm -ResourceGroupName myResourceGroup

@DiSae You can also update the tags using the Get-AzVm and Update-AzVm cmdlets. For Example:
Get-AzVm -ResourceGroupName myResourceGroup -Name myVM
$Vm.tags.Add("testtag","testtag")
Update-AzVm -vm $vm -ResourceGroupName myResourceGroup

#please-close It looks like this issue was resolved. If it isn't, please feel free to reopen this issue or create a new one. Thank you!


[R] Conflict between resize and mean.img in mx.io.ImageRecordIter make R crash

For bugs or installation issues, please provide the following information.
The more information you provide, the more likely people will be able to help you.
Environment info
Operating System: Ubuntu 16.04
Package used (Python/R/Scala/Julia): R
MXNet version: 0.9.4
R sessionInfo():
R version 3.2.3 (2015-12-10)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Ubuntu 16.04.2 LTS

locale:
 [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C               LC_TIME=fr_FR.UTF-8        LC_COLLATE=en_US.UTF-8
 [5] LC_MONETARY=fr_FR.UTF-8    LC_MESSAGES=en_US.UTF-8    LC_PAPER=fr_FR.UTF-8       LC_NAME=C
 [9] LC_ADDRESS=C               LC_TELEPHONE=C             LC_MEASUREMENT=fr_FR.UTF-8 LC_IDENTIFICATION=C

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

loaded via a namespace (and not attached):
 [1] igraph_1.0.1       Rcpp_0.12.9        rstudioapi_0.6     magrittr_1.5       munsell_0.4.3      colorspace_1.3-2
 [7] R6_2.2.0           brew_1.0-6         stringr_1.2.0      plyr_1.8.4         dplyr_0.5.0        visNetwork_1.0.3
[13] Rook_1.1-1         tools_3.2.3        grid_3.2.3         gtable_0.2.0       DBI_0.5-1          influenceR_0.1.0
[19] DiagrammeR_0.9.0   htmltools_0.3.5    lazyeval_0.2.0     digest_0.6.12      assertthat_0.1     tibble_1.2
[25] gridExtra_2.2.1    RColorBrewer_1.1-2 ggplot2_2.2.1      codetools_0.2-14   htmlwidgets_0.8    viridis_0.3.4
[31] rgexf_0.15.3       stringi_1.1.2      scales_0.4.1       XML_3.98-1.5       mxnet_0.9.4        jsonlite_1.3

Error Message:
R session aborted
no stack trace
Minimum reproducible example
`library(mxnet)
data.shape <- c(56, 56, 3) # was 28 28 3
train <- mx.io.ImageRecordIter(
path.imgrec     = "/home/user/data/image_train.rec",
batch.size      = 128,
data.shape      = data.shape,
resize          = 56,
rand.crop       = TRUE,
rand.mirror     = TRUE,
mean.img        = "/home/user/data/mean.bin"
)
`
Steps to reproduce

if i use data.shape <- c(28, 28, 3) it works perfectly
all other values c(56,56,3)  c(16,16,3)  c(27,27,3) make R session crash

What have you tried to solve it?

If i remove the mean.img parameter, it does not crash anymore

When did you generate the mean.bin file?

Hi @thirdwing, here is what i did:

run program above without resize and with 28 28 3 shape
added resize 56
run program above with 56 56 3 shape

If i understand where you are leading, i think there should a check of the size of the mean file provided with respect to the data.shape.


Allow setting LB Service name suffix

Towards https://github.com/giantswarm/roadmap/issues/583

Tested on galaxy


Add resource limits on all applications

We need to add resource limits for each app in https://github.com/networkservicemesh/deployments-k8s/tree/main/apps

Right now it is problematic because on such scenario healing starts overusing CPU:
1. Setup NSMgr + Forwarder + Registry
2. Deploy NSE
2. Deploy multiple (~10) NSC
3. Delete NSE without unregistering
4. Delete NSCs

after that NSMgr starts trying to heal all NSC -> NSE connections increasing CPU usage up to 1000m.
Waiting for the  https://github.com/networkservicemesh/sdk/pull/738 to fix it.

Issue with CPU overusing is still here, but now with refresh:
NAME                            CPU(cores)   MEMORY(bytes)
forwarder-sriov-hm2hc           1m           17Mi
forwarder-sriov-q6scc           5m           26Mi
forwarder-vpp-4x5tl             87m          356Mi
forwarder-vpp-m72gw             81m          340Mi
nsm-registry-6675db8489-qb98c   1m           12Mi
nsmgr-lmb5r                     1m           13Mi
nsmgr-pxfqr                     4163m        43Mi


Cannot connect to 9.4 server once it is running

about 6 hours ago my automated tests started failing because we could no longer connect to the database once the docker container came up and reported that it was accepting connections.
Further testing revealed that it was because we were pulling a new version of the official postgres:9.4 image.
A known good image we have is ad2fc7b9d681
The failing image seems to be 25add771b79e
I can switch back and forth between the 2 images and reproduce the bug consistently.
We do run some initialization scripts, but they're all sql commands to create our users and build our schemas and tables, not anything touching hba or similar.

I've noticed that bringing the image itself up lets me connect as the postgres user, but building the following Dockerfile breaks it.
`FROM postgres:9.4
RUN LC_ALL=C DEBIAN_FRONTEND=noninteractive apt-get update && apt-get install -y
postgresql-plperl-9.4`

After much digging I discovered that the issue is that apt upgrades postgresql to the latest version and overrides the postgresql.conf file with the default. To prevent this from happening add the --no-upgrade flag to the apt-get command.

hmm, for whatever reason that doesn't seem to have fixed our issue.

Connect to the tuning container check to see what the postgresql.conf looks
like. The listen_address should be '*'

Thanks @snopoke . I didn't find the time to debug it further along your suggestions, but apparently whatever broke is fixed in the most recent image. Closing

Re-opening, as the issue appears to be back

I'm trying to look at the configuration, after applying the same dockerfile as above (with --no-upgrade), here's what I see so far.
postgresql.conf:
root@992bac22b33c:/# cat /var/lib/postgresql/data/postgresql.conf | grep listen
#listen_addresses = 'localhost'         # what IP address(es) to listen on;

pg_hba.conf:
...
# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
local   all             all                                     trust
# IPv4 local connections:
host    all             all             <IP_ADDRESS>/32            trust
# IPv6 local connections:
host    all             all             ::1/128                 trust
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication     postgres                                trust
#host    replication     postgres        <IP_ADDRESS>/32            trust
#host    replication     postgres        ::1/128                 trust

host all all <IP_ADDRESS>/0 md5

I'll try to compare these to the base image

What's surprising is that I changed the Dockerfile to
FROM postgres:9.4

RUN LC_ALL=C DEBIAN_FRONTEND=noninteractive apt-get update && apt-get install --no-upgrade -y \
    postgresql-plperl-9.4
RUN echo "listen_addresses = '*'" >> /var/lib/postgresql/data/postgresql.conf

so that listen_addresses would be re-set correctly if the apt-get changed anything, but when I look at the file in the container, the added line isn't there.

after looking at the changes in #127 a bit closer, I found that /usr/share/postgresql/postgresql.conf.sample was being ignored because /usr/share/postgresql/9.4/postgresql.conf.sample was being overwritten by the postgresql-plperl-9.4 install.
The following Dockerfile demonstrates a functional workaround:
FROM postgres:9.4

RUN LC_ALL=C DEBIAN_FRONTEND=noninteractive apt-get update && apt-get install --no-upgrade -y \
    postgresql-plperl-9.4
RUN rm /usr/share/postgresql/9.4/postgresql.conf.sample
RUN ln -sv /usr/share/postgresql/postgresql.conf.sample /usr/share/postgresql/9.4/

I'm not sure if this project is wrong for making the symlink, or if postgres-plperl is wrong for overwriting it.

got hit by this too. Has anyone found a workaround that could be in the original dockerfile ?

Sorry for the delay -- I'm inclined to think that it's very odd for postgres-plperl to overwrite postgresql.conf.sample outright instead of modifying it in-place or something similar, especially since postgresql.conf.sample is the source material for postgresql.conf when it generates the initial database contents.
If this is still an issue, I'd recommend checking with upstream to see if they have any suggestions as to what's going on here.  If they've got a better method for us to adjust postgresql.conf.sample, a PR (or even just a pointer to their recommendations) would be grand. :+1:
Since there's not really anything we can actionably do here right now, I'm going to close.


Mijia Door Sensor no battery info

https://github.com/Jeedom-Zigate/jeedom-plugin-zigate/issues/94#issuecomment-459113493

@doudz c'est pas celle du comment ?

partiel en 0.27.0, à tester

@doudz
Version plugin 1.2.0
Version lib 0.27.5
Version firmware 3.0e
Still no battery info :-(
Abeille is showing the correct battery info

Version plugin 1.2.0
Version lib 0.27.5
Version firmware 3.0f
Still no battery info after firmware upgrade :-(

if Abeille can do it, we can too ;)
I'll take a look

if Abeille can do it, we can too ;)
I'll take a look

That's what I thought :-) 👍

Just to be sure, I reinstalled everything and added just the button.
Here is the latest json file:
{     "devices": [         {             "addr": "2ea7",             "discovery": "",             "endpoints": [                 {                     "clusters": [                         {                             "attributes": [                                 {                                     "attribute": 1,                                     "data": 10,                                     "name": "application_version",                                     "value": 10                                 },                                 {                                     "attribute": 5,                                     "data": "lumi.sensor_switch",                                     "name": "type",                                     "type": "str",                                     "value": "lumi.sensor_switch"                                 }                             ],                             "cluster": 0                         },                         {                             "attributes": [                                 {                                     "attribute": 32768,                                     "data": 0,                                     "expire": 2,                                     "name": "multiclick",                                     "type": "int",                                     "value": 0                                 },                                 {                                     "attribute": 0,                                     "data": true,                                     "name": "onoff",                                     "type": "bool",                                     "value": true                                 }                             ],                             "cluster": 6                         }                     ],                     "device": 0,                     "endpoint": 1,                     "in_clusters": [],                     "out_clusters": [],                     "profile": 0                 }             ],             "generictype": "",             "info": {                 "addr": "2ea7",                 "ieee": "00158d00026b6765",                 "last_seen": "2019-02-14 11:11:22",                 "mac_capability": "10000000",                 "rssi": 207             }         }     ],     "groups": {},     "scenes": {} }

ça sera corrigé dans la lib 0.28

Just updated manually to lib 0.28 and now it's showing battery info for all my Xiaomi/Mijia/Auara devices. I had to remove all devices and add them as new devices though (PDM/EEPROM erase not required).
I could not get the battery info by refreshing the device, but that's okay with me :-D

Great news !
You can't refresh the value manually, because the device is responsible of the update.
Since the percent is a part of Jeedom core, we don't have info command for it but I think there's way to display a battery icon on the dashboard (sorry I don't use Jeedom so I'm not a expert)

beside that, what's your native language ? Looks like we have to translate the plugin :smile:

I can see that the percentage is reported correctly elsewhere in Jeedom so I can still use it as ex battery warning :-) so that’s fine with me :-)
Thank you for your great job :-)

I’m Danish:-)

Sometimes the Jeedom team is not listening. Similar you have NextDom (fork of Jeedom)
I'm using Home Assistant, it's not always user friendly but so far more efficient and open than Jeedom

I’m actually mostly using Jeedom as a “relay” for homebridge :-)
I’m used to use plain HAP but found Jeedom a lot easier. I also love the way it handles the connection to homebridge. Just click and run :-)
Mostly my wife is using Jeedom to get an overview over our house and all the sensors


Fixes signout regex and clear cookies

What

Regex pattern was not matching on sign-out, so updated code to escape the request path and to make trailing '/' optional in the pattern.

Delete client cookies

How to review

Check cookies before and after signing out, ags_session cookie value should be different

Who can review
Not @kentsanggds
https://trello.com/c/Sb5LCBzq

Incorporated in #5


Multiple 'for' loop make rustpython panicked.

The following test defined a nested 'for' loop at line 4, then rustpython gets panicked
test.py:
class F:
    def a(self):
        x = None
        x = [[(x_1 := 2) for self in range(2)] for x in range(2)]
        print(x, self)
F().a()

Behavior on rustpython(rustpython 0.1.2):
thread 'main' panicked at 'internal error: entered unreachable code: var x_1 in a Function should be free or cell but it's Local', compiler/codegen/src/compile.rs:1215:22
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Behavior on CPython 3.9.1(Expected):
[[2, 2], [2, 2]] <__main__.F object at 0x7f91076e8fd0>
Step to reproduce:
type "cargo run --release test.py" on the console of Ubuntu 18.04 or MacOS Big Sur 11.7.1
rust version: rustc 1.65.0

it seems more like a walrus operator(:=) bug than loop itself.

Same panic has occured with the following code.
def f():
    [[x := 1 for j in range(5)] for i in range(5)]

thread 'main' panicked at 'internal error: entered unreachable code: var x in a Function should be free or cell but it's Local', compiler/codegen/src/compile.rs:1215:22
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I looked into CPython implementation.
If symbol is defined as LOCAL and in free list, Symbol scope is replaced from LOCAL to CELL.
https://github.com/python/cpython/blob/0264f634f720fbf12afaf1715a53cd1495fbd85b/Python/symtable.c#L572-L603
Symbol defined with walrus operator inside comprehension should be Cell in outer scope.


Architecture Sample Proposal with Koin

Hello!
I would like to propose a version of the app, done with Koin. A branch is almost ready here: https://github.com/InsertKoinIO/architecture-samples/tree/dev-koin
Are you interested? What is the process to integrate it?
Thanks.

Hey Arnaud! That looks great!
The project is meant to be used a base for other repos, such as the one you linked. We're not linking to external repos anymore because they tend to get outdated quickly (as our own does!) and we can't review all of them. We're moving towards a single version of the app using all the recommended tools in the architecture guidance.
Btw there's an error in the README:
The ServiceLocator class is removed. Object creation and scoping is handled by Hilt.
Also, I'd link to the "compare" view of the dev-hilt vs dev-koin in the README or Koin's documentation, which is useful to show a migration path:
https://github.com/android/architecture-samples/compare/dev-hilt...InsertKoinIO:dev-koin
Good job!


Hplsql syntax highlight

What changes were proposed in this pull request?

syntax highlight for hplsql keywords, built-in functions, datatypes.

How was this patch tested?

manual tests

looks like https://github.com/cloudera/hue/blob/master/tools/ace-editor/lib/ace/mode/_test/highlight_rules_test.js this file has unit tests already?

added new one https://github.com/cloudera/hue/pull/2682


Cursor issue

ADD ISSUE DESCRIPTION HERE
the original cursor is in the code file now when we tap on the already opened terminal and start typing it doesn't type on terminal instead it types on the last location that is in the file. Same goes the case with ctrl F for finding words in code.
Version: 1.73.1
Commit:<PHONE_NUMBER>f055b99068d3688932416f2346dd3b
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

Please provide a screenshot or a gif illustrating the problem (attaching images won't work via email, you need to go to github.com). See this wiki page for more general info on how to report actionable terminal issues.
/label "info-needed" terminal


Clarify MAXDOP and coop scheduling example

There is a really useful illustration on this docs page, but there are some confusing and inaccurate aspects to it.
My goal with this PR is to preserve the intent of the illustration while correcting some of those issues, specifically:

remove the reference to setting CPU affinity for 8 cores. I don't think a MAXDOP 32 query makes much sense on a server with 8 cores available to SQL Server.  It feels like this distracts from the example
clarify statements about the number of operators in the theoretical plan

"The query plan has a join between two tables, with a total of 3 query plan operators" - this isn't possible in a parellel plan - there would be at least one "Gather Streams" operator (making the total 4)
"Each of the operators is executed in parallel, and spawns 32 tasks" - for that to be true, each operator really needs to be in a separate branch - which would mean there are 6 operators total (2 scans, 1 join, and 3 exchanges)
I have included a screenshot in this PR of an AdventureWorks2014 query plan that demonstrates this plan shape.  I think it would go a long way towards clarifying what is meant about the operators / plan shape.  I don't know how to add it to the docs though, so if someone could help with that it would be appreciated :)

It's more accurate (and I think more clear, in the presence of the screenshot) to say that each branch spawns 32 tasks
"At any given time, the request has at least 99 tasks" - I think the math is just wrong here.  Each branch gets 32 tasks, which is 96 total.  Plus one for the coordinator is 97.  There isn't a coordinator per branch
"a single request can spawn multiple tasks, and each task is assigned to a worker, up to the MAXDOP limit" - tasks aren't limited to MAXDOP for a parallel query (they are limited to MAXDOP per branch).  The number of schedulers available for the extra parallel worker threads is what's limited by MAXDOP, which I think it the point being made in this example

For reference (it's probably not useful for the example), I used this query on SQL Server 2019 (against the AdventureWorks2014 database at compat level 150) to produce that execution plan:
SELECT
    sod.SalesOrderDetailID,
    p.ProductID
FROM Sales.SalesOrderDetail sod
    INNER MERGE JOIN Production.Product p
        ON sod.ProductID = p.ProductID
OPTION (USE HINT ('ENABLE_PARALLEL_PLAN_PREFERENCE'));

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

Thank you, but the docs are undergoing review right now, and should be published with new examples in the next 24h. Feel free to review after that change.

@pmasl I'm glad to hear it's being improved.  I put a decent amount of effort into this PR to try and help based on that Twitter exchange and the related blog posts, so I'm not sure I will invest more time to review again after the change - in case the goal posts are still moving.

I will review and see what I can incorporate from your PR. Really appreciate your input here.

Thanks, Pedro.  I appreciate that.