Code block UI amendment required

Please refer to the following video for more information

UI issues: https://vimeo.com/842749776/8e3360680b

@AbhayVAshokan _a
cc: @yedhink

Action items

[ ] Saving a codeblock converts certain characters to <, >, etc.
[ ] Remove text wrapping from the CodeBlocks in edit mode.
[ ] Fix the position of copy button when the content scrolls.
[ ] Verify the behaviour of dropdowns during scroll.
[ ] Remove auto highlight and make plaintext by default.

Also, I would like to know how the syntax highlighting works for the type auto. Is it supposed to automatically detect the syntax type? If it is supposed to be a general syntax type, I don't think it's serving its purpose very well. I believe the intended purpose of the general syntax type is not being fulfilled since certain words in my plaintext or markdown document are highlighted incorrectly in the auto mode.

@gaagul _a let's take this up.

Also, I would like to know how the syntax highlighting works for the type auto.

When the type is auto the syntax highlighting is done by the "hljs" library, The "hljs" library has "highlightAuto" function which internally determine the most suitable language for syntax highlighting by parsing the provided content and selecting the language with the highest preference based on specific indexes.

@AbhayVAshokan

The copy button in the edit mode is added referring to the Notion style. We can think of hiding in the future it if it causes inconviniences.

Got it. I found no harm in having the copy button in the edit mode. We can keep it as it is for now.

The ideal behaviour for code blocks is not letting the text to wrap. We'll be adopting this behaviour as well. Here are a screenshots from GitHub and Notion for reference.

I see. That makes sense given that the intended input for a code block is code after all. But for the plaintext type, at least, I found text wrapping very readable in the view mode. I would say neither GitHub nor Notion has not done a great job in that arena. I believe that by providing an option for users to type in plaintext, we are in turn giving them an opportunity to write descriptive content without them manually having to add a newline character after each line. So would it be feasible to incorporate text wrapping for the plaintext at least? Lemme know your thoughts.

I agree that the auto syntax highlighting is not perfect. Let's adopt the GitHub style for this case. If is provided, let it default to plaintext. Language may be selected either by the dropdown or by directly typing something similar tojavascript.

Sounds great to me.
@gaagul

When the type is auto the syntax highlighting is done by the "hljs" library, The "hljs" library has "highlightAuto" function which internally determine the most suitable language for syntax highlighting by parsing the provided content and selecting the language with the highest preference based on specific indexes.

I see. I would rather recommend that the editor defaults to plaintext as Abhay pointed out. It is better to have no highlighting in the code block (which is the case with plaintext) than to have an incorrect highlighting from hljs.
I believe the auto type from hljs would be more suitable for a code editor than a general-purpose text editor.

I believe that by providing an option for users to type in plaintext, we are in turn giving them an opportunity to write descriptive content without them manually having to add a newline character after each line. So would it be feasible to incorporate text wrapping for the plaintext at least?

This seems like a good idea. The only drawback being the drastic changes in the UI (text wrapping) whenever the user toggles from plaintext to any other language. @gaagul can you check the feasibility of this implementation as well?

@gaagul can you check the feasibility of this implementation as well?

Yes, I will take a look at  the feasibility of adding this change.

We'll try keeping the text wrapping in both edit and display mode for now. This seems like the right choice for our use cases. A horizontal scrollbar is less user-friendly.


x/build/cmd/release: windows-amd64 release process is failing on tip due to unexpected stale targets after second build

As detected early by @heschi via work on #51797, Go 1.19 tip tree that will be used during the release process is not passing on the windows/amd64 release target.
Bisection shows the problem starts with CL 391809 (CC @bcmills). Either there's a problem in that CL that is uncovered only during the sequence of steps the current release process performs (since it's not being caught by builders), or there's a problem with that sequence which is only being uncovered by that change.
Its parent commit (d68615f64b0d7c1e886f4b8c1267ecc1c4da76ad) gets as far as API check successfully, but commit 0433f5770b9c92b06d5a15c8d2a70f00597faac4 fails early in the "Building (all.bash to ensure tests pass)" step with:
# (The release command uses builders to create a release artifact locally.
#  It does not publish anything, so it's safe to run for testing needs.)
$ release -target=windows-amd64 -version=go1.19alpha126 -watch -rev=0433f5770b9c92b06d5a15c8d2a70f00597faac4
[...]
2022/03/28 18:59:19 windows-amd64: Installing go1.4 (second time, for all.bash).
2022/03/28 18:59:22 windows-amd64: Building (all.bash to ensure tests pass).
Building Go cmd/dist using C:\workdir\go1.4
Building Go toolchain1 using C:\workdir\go1.4.

Building Go toolchain2 using go_bootstrap and Go toolchain1.
Building Go toolchain3 using go_bootstrap and Go toolchain2.
Building packages and commands for windows/amd64.

HASH[build internal/goarch]
[...]
HASH[link cmd/dist]: bdb2e2909c821c8e0277ce92f8c75b485d05999d0d32e4da1e549e1b9d4dbfab
cmd/dist true
go tool dist: unexpected stale targets reported by go list -gcflags="" -ldflags="" for [std cmd] (consider rerunning with GOMAXPROCS=1 GODEBUG=gocachehash=1):
	STALE cmd/addr2line: build ID mismatch
	STALE cmd/api: build ID mismatch
	STALE cmd/asm: build ID mismatch
	STALE cmd/buildid: build ID mismatch
	STALE cmd/cgo: build ID mismatch
	STALE cmd/compile: build ID mismatch
	STALE cmd/cover: build ID mismatch
	STALE cmd/dist: build ID mismatch
	STALE cmd/doc: build ID mismatch
	STALE cmd/fix: build ID mismatch
	STALE cmd/go: build ID mismatch
	STALE cmd/gofmt: build ID mismatch
	STALE cmd/internal/metadata: build ID mismatch
	STALE cmd/link: build ID mismatch
	STALE cmd/nm: build ID mismatch
	STALE cmd/objdump: build ID mismatch
	STALE cmd/pack: build ID mismatch
	STALE cmd/pprof: build ID mismatch
	STALE cmd/test2json: build ID mismatch
	STALE cmd/trace: build ID mismatch
	STALE cmd/vet: build ID mismatch

(complete log https://gist.github.com/dmitshur/80444d6afa37edb6dcdc2f2979545762)
This test failure can be reproduced with cmd/release (can only be done by someone with gomote access).
CC @golang/release.

As expected, running make.bat followed by all.bat on a raw builder does not reproduce this failure.
I suspect that it is something to do with the environment or args passed to the scripts. I'm adding some logging to cmd/release and re-running to try to suss that out.

I did eventually reproduce this by setting GO_BUILDER_NAME before running run.bat on a gomote instance. (cmd/dist's behavior changes based on whether it is running on a builder, because the builder is only supposed to run run.bat in a GOROOT that has already run make.bat and not been modified since.)


[issue] Cannot find module 'deepmerge'

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
[root@node3 streamx]# mvn clean install -DskipTests -Dscala.version=2.11.12 -Dscala.binary.version=2.11 -Pwebapp
StreamX Version
dev
1.2.4
Java Version
1.8
Flink Version

Scala Version of Flink
2.11
Error Exception
Packaging exception

Screenshots

Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

[root@node3 streamx]# npm install deepmerge


Excel file format support

Discussed this in triage. We would need a complex UI to specify which sheet to use and which columns go where. At that point it might be simpler to just let the user save those sheets as CSV.


Data corruption reading JSON out of S3 files

Hi,
I came across a strange issue today trying to read 200 newline JSON files in S3 with Dask. I am using the following code to try to load the files:
import dask.bag as db
import json
df = db.read_text('s3://<bucket>/prefix/yyyy-mm-dd/output.json/part*',
                  storage_options={
                      'key': creds.access_key,
                      'secret': creds.secret_key,
                      'token': creds.token
                  })
json_df = df.map(json.loads)
count = json_df.count().compute()

When this runs, I get the following traceback:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/opt/conda/lib/python3.7/site-packages/dask/base.py", line 175, in compute
    (result,) = compute(self, traverse=False, **kwargs)
  File "/opt/conda/lib/python3.7/site-packages/dask/base.py", line 446, in compute
    results = schedule(dsk, keys, **kwargs)
  File "/opt/conda/lib/python3.7/site-packages/distributed/client.py", line 2510, in get
    results = self.gather(packed, asynchronous=asynchronous, direct=direct)
  File "/opt/conda/lib/python3.7/site-packages/distributed/client.py", line 1812, in gather
    asynchronous=asynchronous,
  File "/opt/conda/lib/python3.7/site-packages/distributed/client.py", line 753, in sync
    self.loop, func, *args, callback_timeout=callback_timeout, **kwargs
  File "/opt/conda/lib/python3.7/site-packages/distributed/utils.py", line 328, in sync
    six.reraise(*error[0])
  File "/opt/conda/lib/python3.7/site-packages/six.py", line 693, in reraise
    raise value
  File "/opt/conda/lib/python3.7/site-packages/distributed/utils.py", line 313, in f
    result[0] = yield future
  File "/opt/conda/lib/python3.7/site-packages/tornado/gen.py", line 735, in run
    value = future.result()
  File "/opt/conda/lib/python3.7/site-packages/distributed/client.py", line 1668, in _gather
    six.reraise(type(exception), exception, traceback)
  File "/opt/conda/lib/python3.7/site-packages/six.py", line 692, in reraise
    raise value.with_traceback(tb)
  File "/opt/conda/lib/python3.7/site-packages/dask/bag/core.py", line 2457, in empty_safe_apply
    return func(part)
  File "cytoolz/itertoolz.pyx", line 1061, in cytoolz.itertoolz.count
  File "cytoolz/itertoolz.pyx", line 1075, in cytoolz.itertoolz.count
  File "/opt/conda/lib/python3.7/site-packages/dask/bag/core.py", line 2035, in __next__
    return self.f(*vals)
  File "/opt/conda/lib/python3.7/json/__init__.py", line 348, in loads
    return _default_decoder.decode(s)
  File "/opt/conda/lib/python3.7/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/opt/conda/lib/python3.7/json/decoder.py", line 353, in raw_decode
    obj, end = self.scan_once(s, idx)
json.decoder.JSONDecodeError: Unterminated string starting at: line 1 column 998 (char 997)

Normally this kind of error means the file is corrupt but I know this file is correct because I am able to parse the JSON with Spark. I made this adjustment to capture the lines Dask thinks are corrupt JSON:
def try_decode(s):
    try:
        json.loads(s)
    except:
        return s
    return None
bad_rows = df.map(try_decode).filter(lambda row: row is not None)
bad_rows.count().compute()  # 200

I get 200, so there's exactly 1 malformed line per file.
Looking at the contents of bad_rows, it looks like Dask is corrupting the second JSON line in each file. Even stranger, when I load 1 file out of the 200:
df = db.read_text('s3://<bucket>/prefix/yyyy-mm-dd/output.json/part-00000',
                  storage_options={
                      'key': creds.access_key,
                      'secret': creds.secret_key,
                      'token': creds.token
                  })
# get the second line of the file
df.take(100)[1]

The row shows up correctly. I can't figure out why the data would show up correctly in .take() but when I use .map() the second row is always cut short and fails to parse.
Possible fixes
So far, the only way I have gotten it to work is to specify the blocksize larger than my largest file (~30MB). I am confused because by default, each file should be mapped to a single partition so if I leave blocksize as the default, shouldn't it load the whole file?
A couple notes:

The files are organized in an S3 bucket as follows: s3://<bucket>/prefix/yyyy-mm-dd/output.json/part*
There are about 200 files and each one is roughly 25MB plaintext.
Each JSON line is fairly long, the one covered in this example is roughly 5000 chars.

Thanks @mrocklin! Here's the most minimal example I could come up with. It seems the issue boils down to loading data out of S3. I found an open source dataset that reproduces the issue. It seems when I load data out of S3, extra rows are inserted into the bag:
Setup:
# copy file locally first
aws s3 cp s3://nyc-tlc/trip\ data/yellow_tripdata_2019-06.csv . --no-sign-request

import dask.bag as db

local_file_df = db.read_text('yellow_tripdata_2019-06.csv')
aws_file_df = db.read_text('s3://nyc-tlc/trip data/yellow_tripdata_2019-06.csv', storage_options={'anon': True})

local_lines = local_file_df.count().compute()
aws_lines = aws_file_df.count().compute()

print(aws_lines - local_lines)
# I get a difference of 62 lines

Thanks @mcgrawia, I'm taking a look now.

And if you're able to provide a smaller example, I'd be very grateful. I'm on slow public wifi right now, and it's not liking the 600 MB download :)

A shoot ok let me find another smaller dataset

I think this one could work, only 25MB? s3://irs-form-990/index_2011.csv
import dask.bag as db

# setup: copy file locally first
# aws s3 cp s3://irs-form-990/index_2011.csv . --no-sign-request

local_file_df = db.read_text('index_2011.csv')
aws_file_df = db.read_text('s3://irs-form-990/index_2011.csv',
                           storage_options={'anon': True})

# line counts differ

local_lines = local_file_df.count().compute()
aws_lines = aws_file_df.count().compute()

print(aws_lines - local_lines)

Thanks, able to reproduce with that.
Unfortunately, I'm not able to reproduce it using moto (which we use for tests). I'm facing a similar issue trying to write a test for another issue, so hopefully I'll have something to report back later today.

Ok glad to hear you can reproduce. Look forward to hearing more! Thanks

I may have inadvertently fixed this with https://github.com/dask/s3fs/pull/229. Can you try with s3fs master. I'll be doing a release later today.

@TomAugspurger looks like the new version 0.3.4 did the trick! The json parsing works now. Do you know how that issue resulted in the malformed rows?

Glad to hear it!

Do you know how that issue resulted in the extra, malformed rows?

I may be wrong, but my best guess is a bad interaction between our in-memory cache of fetches from S3, and behavior when we make an HTTP request to S3 with a "negative" byte range. In this case we've reached the end of the file, but the caller may do some additional .read() calls. So we do another fetch. This (I think) ends up redownloading the entire file, since HTTP servers are supposed to ignore the range field when it's negative. That extra, duplicate, data gets added to our in-memory cache, leading to the duplicate rows.
I could be wrong about pieces of that, but I think that's the gist.
Once Martin is back online, I'll talk with him about testing strategies that could have caught this. I don't see an easy way right now, since moto behaves differently than S3.

ok sounds good, thanks for the explanation


E2E test: Improve Story From Template screenshot

Summary

Relevant Technical Choices

To-do

User-facing changes

Testing Instructions

Fixes #5711

But wouldn't we need to do this in all other tests as well?

It doesn't seem to be issue elsewhere. I think it is because the test navigates to the editor from the dashboard which other tests do not do.


Wrong orientation of vector tip

Description of bug / unexpected behavior

Orientation of tips of some vectors are wrong
How to reproduce the issue
class Vectors(ThreeDScene):
    def construct(self):
        self.add(Vector(RIGHT), Vector(UP), Vector(OUT))
        self.set_camera_orientation(phi=PI/3, theta=PI/6)
        self.begin_ambient_camera_rotation(rate=2)
        self.wait(PI)

Additional media files

Fixed in #1924


Fix inner padding for mj-button and mj-social

I was setting up a new project and accidentally ended up with the 4.4.0-beta.1 tag instead of ^4.3.0 and when I tried to compile an old file I had a couple of errors.
In the end, I had one error left.

Attribute inner-padding has invalid value: 12px 24px for type Unit, only accepts (px, %) units and 1 value(s)

I thought it was a little strange, considering the default value was '10px 25px'. I went down the rabbit hole of figuring out why that's invalid and I arrived at the fix that I've put in this PR. I'm not sure why it doesn't get mad on 4.3, but I've used it in this way for quite a while and have had no issues.
Sample code that works in ^4.3.0 but snags in 4.4.0-beta.1
<mjml>
  <mj-body>
    <mj-section>
      <mj-column>
        <mj-button inner-padding="10px 25px">My button</mj-button>
      </mj-column>
    </mj-section>
  </mj-body>
</mjml>

If I've done something wrong, let me know. I'd be happy to make changes.

Thanks for submitting the PR we'll merge it into the next 4.4.0 beta then !
On Thu, Feb 21, 2019 at 12:50 AM Eric Jensen<EMAIL_ADDRESS>wrote:

I was setting up a new project and accidentally ended up with the
4.4.0-beta.1 tag instead of ^4.3.0 and when I tried to compile an old file
I had a couple of errors.
In the end, I had one error left.
Attribute inner-padding has invalid value: 12px 24px for type Unit, only
accepts (px, %) units and 1 value(s)
I thought it was a little strange, considering the default value was '10px
25px'. I went down the rabbit hole of figuring out why that's invalid and I
arrived at the fix that I've put in this PR. I'm not sure why it doesn't
get mad on 4.3, but I've used it in this way for quite a while and have had
no issues.
If I've done something wrong, let me know. I'd be happy to make changes.
You can view, comment on, or merge this pull request online at:
https://github.com/mjmlio/mjml/pull/1523
Commit Summary

specify amount of units for mj-button inner-padding
specify amount of units for mj-social inner-padding

File Changes

M packages/mjml-button/src/index.js
https://github.com/mjmlio/mjml/pull/1523/files#diff-0 (2)
M packages/mjml-social/src/Social.js
https://github.com/mjmlio/mjml/pull/1523/files#diff-1 (2)

Patch Links:

https://github.com/mjmlio/mjml/pull/1523.patch
https://github.com/mjmlio/mjml/pull/1523.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mjmlio/mjml/pull/1523, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAizzSYKWqhzdco7rNybDrTTX0jD9G5hks5vPd8ngaJpZM4bGWuA
.

--
Cordialement,
Maxime BRAZEILLES

Source of the issue is commit 53ac1d55d71b82d30741aa53912b32a956ed4296.

this commit is fine, it fixes the regex, so now the validation will reveal some errors (or some wrong types definitions, like here) that were ignored in the past

Certainly - didn't mean to imply it was a buggy commit. Was just saying this particular issue has been introduced since that commit was added (since @Magnesium38 was wondering why the issue didn't exist in 4.3).


Add deprecation warning regarding cache

The client will no more handle cache as of version 3.

Closed by e69f8e9f900b1864566857e757550b8c65d64253


http_server on chrome

http_server:
./http_server -c example.com,fullchain.pem,privkey.pem -s <IP_ADDRESS>:1234 -L debug
google-chrome:
google-chrome --new-window -incognito --allow-file-access-from-files --no-sandbox --no-proxy-server --enable-quic --quic-version=h3-29 --origin-to-force-quic-on=example.com:443 --host-resolver-rules='MAP example.com <IP_ADDRESS>:1234' https://example.com:443
google-chrome appears error: "ERR_QUIC_PROTOCOL_ERROR", it seems that handshake got wrong. Could google-chrome connect to lsquic-http-server?
Thanks

google-chrome requires a valid SSL certificate. self signed cert wont work.

Thanks, it works.


Full diff change tracking mode

Adds a new full_diff change tracking mode. The goal is to get a full diff that is human readable, relatively easy to render in a UI, and contains enough data that a revert and undo action could be implemented in the future.
papertrail do
  change_tracking_mode :full_diff
end

Changes look like:
// Creating a new resource:
{ subject: {to: "my subject"}, body: {to: "my body"} }

// Updating
{ subject: {from: "my subject", to: "new subject"}, body: {unchanged: "my body"} }

// Destroying (same as updates, allowing for soft destroys to do updates
{ subject: {unchanged: "new subject"}, body: {unchanged: "my body"} }

All attributes are dumped with the dump_embedded_value, except (ironically) embedded resources.
Embedded resources are marked as created/updated/destroyed/unchanged
{ author: { to: nil } }
{ author: { created: { first_name: {to: "Bob" } } } }
{ author: { unchanged: { first_name: {unchanged: "Bob" } } } }
{ author: { updated: { first_name: {from: "Bob", to: "Joe" } } } }
{ author: { destroyed: { first_name: {unchanged: "Bob" } } } }

Arrays of embedded resources have an index change. Items in arrays move when simple types have the same value or embedded resources are updated.
{ tags: { to: []  } }
{ tags: { unchanged: [] } }
{ tags: { to: [ { index: { to: 0 }, created: { label: { to: "ash" } } } ] } }
{ tags: { to: [ { index: { to: 0 }, created: { label: { to: "phx" } }, { index: { from: 0, to: 1 }, unchanged: { label: { to: "ash" } } } ] } }

Union objects work as well and can type change type.
{ source: { to: { type: "link", value: "https://www.example.com" } } }
{ source: { from: { type: "link", value: "https://www.example.com" }, to: { type: "domain", value: "example.com" } }
{ source: { from: { type: "domain", value: "example.com" } , to: nil }

Embedded Union objects are created/updated/destroyed and can be mixed with non-embedded types
{ source: { to: { type: "book", created: { name: { to: "The book"}, page: { to: 2} } } }
{ source: { to: { type: "book", updated: { name: { from: "The book", to: "The Book" },  page: { unchanged: 2 } } }
{ source: { from: { type: "book", destroyed: { name: { unchanged: "The Book" }, page: {unchanged: 2} } }, to: { type: "link", value: "example.com" } }

You can event have arrays of unions moving. See the full_diff_test.exs for complete coverage.

We should implement the behavior for all built in types but also add a callback that can be implemented by custom types to control how they diff. This looks awesome!

One thing to consider is that we may want to capture the input to each action (attributes/arguments) unchanged too. I.e "they provided X, the changes were Y". This is probably independent of this specific work.

@zachdaniel this is feature complete and well tested. I'm going to start running it production on my app. No need to merge immediately.
If this is too much code specific to my use case, I can make the change_tracking_mode accept an mfa and have this an add-on in a separate repo. Also happy to be the maintainer for now if you need support.

Looks pretty slick! Happy to have it built in, especially since it is opt in. A few CI related things to address and then we can get it in.


I haz fraped it

I haz fraped your codez!
All your template are belong to me!

hmm yeah.. we need more ponies


All post queries appear to have unnecessary postmeta query

I noticed that even doing something as simple as the following...
Page::slug('home')->first();

will result in the following 3 queries:
select * from "wp_postmeta" where "post_id" is null and "post_id" is not null
select * from "wp_posts" where "post_type" = ? and "post_name" = ? limit 1
select * from "wp_postmeta" where "post_id" in (?)

(I didn't bother including the bindings since they're inconsequential)
The following query is unnecessary and costly:
select * from "wp_postmeta" where "post_id" is null and "post_id" is not null

If you're using Laravel 5.2, you can find this yourself by listening to query executed event, i.e...
\Event::listen('Illuminate\Database\Events\QueryExecuted', function ($query) {
    var_dump($query->sql);
});

Hi :-) This is because protected $with = ['meta']; inside Post class. It loads by default any meta data related to the current post. In a simple case like yours you'll have one more empty query, but in cases where you have to get multiple meta data you'll have only one query to do that too. Removing this you will have one new query per meta data.
If you are using your own Post class, for example, you can set protected $with = []; to remove this extra load, but after, to get meta data using only one query, you'll have to do something like Post::with('meta')->find(3);.
Thanks ;-)

That makes sense for the 3rd query in the the set above, but I don't think that makes sense for the 1st query. It's hitting the postmeta table before it ever hits the posts table. This seems like a mistake; it can't know the post_id prior to looking up the post itself.
In short, this query will never return anything:
select * from "wp_postmeta" where "post_id" is null and "post_id" is not null

Expected behavior here should be to look up the posts in the posts table, grab the post IDs, and then query the postmeta table with the set of IDs ... which is what you're describing and what is in the 2nd and 3rd queries above:
select * from "wp_posts" where "post_type" = ? and "post_name" = ? limit 1
select * from "wp_postmeta" where "post_id" in (?)

Those two queries make sense, but I don't see how the 1st query can ever do anything useful. I think there should be a guard in place to prevent it, but I don't know enough about the inner working of eloquent / query builder to do it myself.

Hi @QWp6t. The point is that with is made by Eloquent. Maybe we could try to call ->with() in the relationship, like in meta() method. Can you do that and tell us the results? Test with no meta data and 2 or more to see the difference. Thanks.

Is this what you're looking for?
var_dump('test 1: page by slug');
Page::slug('home')->first();

var_dump('test 2: page with meta, limit 1');
Page::with('meta')->first();

var_dump('test 3: pages with meta, limit 3');
Page::with('meta')->find(3);

test 1: page by slug
select * from "wp_postmeta" where "post_id" is null and "post_id" is not null
select * from "wp_posts" where "post_type" = ? and "post_name" = ? limit 1
select * from "wp_postmeta" where "post_id" in (?)

test 2: page with meta, limit 1
select * from "wp_postmeta" where "post_id" is null and "post_id" is not null
select * from "wp_posts" where "post_type" = ? limit 1
select * from "wp_postmeta" where "post_id" in (?)

test 3: pages with meta, limit 3
select * from "wp_postmeta" where "post_id" is null and "post_id" is not null
select * from "wp_posts" where "post_type" = ? and "wp_posts"."ID" = ? limit 1

As you can see, each one still begins with unnecessary query:
select * from "wp_postmeta" where "post_id" is null and "post_id" is not null

Hey @QWp6t ,
Can you try with the dev branch ?
The extra query shouldn't be there anymore.
Thanks

Yeah, that's perfect.
Thanks.


Adds Coq contribs

About 160 Coq libraries.

The hashes don't match (anymore). Is there a more stable way of downloading them?
I don't see why you add new packages that are marked as broken.

Thanks for your review.
Changing hashes: I filed a bug upstream but don’t expect much from it; I’m trying to use fetchzip since it’s just about timestamps, but it’s not completely satisfying yet (see #5851).
Broken packages: the file all.nix includes everything from this webpage. Some of the listed packages are actually broken, or I don’t know how to build them. You are right: it might be better not to include them in the first place.

@vbgl: as a work-around, you can do it without nix-prefetch-zip: just put in fetchzip with any valid hashes (incorrect ones), and then try to build. It will tell you the correct hashes when the build fails.

Unless there's the same problem in fetchzip itself.

Hashes should be correct and reliable now, thanks to fetchzip.

Pushed. Travis failed on one package, but I can't reproduce that. Perhaps it was some hidden timeout (it just says "killed").


Grey overlay background for Dialog component ?

Hi.,
I want to use MDL Dialog box for my website. I used the following code :
<dialog id="dialog" class="mdl-dialog">

Hello User

Hello world from dialog!

      <button type="button" class="mdl-button close">Disagree</button>

</dialog>

And invoked the dialog it by :
document.getElementById('dialog').showModal();
This brings up a popup like this, which doesn't have background overlay (50% opacity black background)  :

Can you please provide a working sample case via codepen? It looks like custom code is most likely interfering here or your HTML structure isn't as it should be.

I had to add this to my style to get it worked:
dialog::backdrop {
  background: rgba(0, 0, 0, 0.5);
}

I think some library was messing around. I am closing this defect now in favour of this.
Thanks.


remove package statement when harmonica task is executed

Is your feature request related to a problem? Please describe.
When the kts file contains package description,
harmonica task raises error.
Describe the solution you'd like
remove package description line

Example
>>> s = "\n\npackage dddd\n\n"
>>> s.replace(Regex("^\\s*package\\s+.+"), "")

Other Example
s.replace(Regex("package .+"), "")


Handle file-io with context manager

Describe changes
I fixed the file open context manager to achieve safe closing of files and supress warnings regarding open files.
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[x] If my change requires a change to docs, I have updated the documentation accordingly.
[x] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

I believe zenml is using this function generically to read different files. During the creation of a pipeline, i get multiple warnings because the file is not safely closed (using a context manager).

Stack `default` successfully updated!

The change has been tested locally and it solves the issue stated scenario.

 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.

Thanks @aliabbasjaffri ! Will merge after the tests run through 🥂


Add wildcard searching for keyword uptime monitors

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
New Monitor
🔖 Feature description
It would be great if would could wildcard search on the keyword monitors
✔ Solution
It would be great if would could wildcard search on the keyword monitors
Like look for "<a href=someoddlink/*?something"
❓ Alternatives
I have tried messing withing other monitors, it doesn't look this can currently be done.
📝 Additional Context
Thanks for the cool project.

I think this is a duplicate of #2735 (duplicate #2030) or previous issue #631
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

@GravisTechRyan
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in https://github.com/louislam/uptime-kuma/issues/2735 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
⇒ I am going to close this as a duplicate.


Need long-term solution for Travis CI dependencies

This is a...

[x] Feature Request
[ ] Bug Report

Problem:
Changes upstream in other repositories, such as api-machinery or client-go, that are pulled into k8s.io can cause the Travis CI test scripts to fail. Consequently, Travis is not a reliable way to determine whether a change to the k8s.io repo is causing a breakage, and it can hold back processing the PR queue when Travis is failing for this reason.
Proposed Solution:
TBD
devin-donnelly, steveperry-53, chenopis, foxish, and jeffmendoza should work on developing a long-term solution.
Pages to Update:
/.travis.yml
/test/examples_test.go

This actually has already been taken care of, so closing this issue is fine.


Draft: Fix deadlocks when trying to a close a session from a session state listener

I was able to fix the testcode in #193 with the patches in this PR.
If you think the ReadWriteLock approach is the right way to go forward with, I would replicate it into the other subclasses of AbstractSessionContext.

@der-ambi Shouldn't ReentrantReadWriteLock always be unlocked in a finally block, or am I missing something?
@pmoerenhout What is you opinion on the ReadWriteLock approach?

@PascalSchumacher there wasn't much that could have gone wrong between the lock() and unlock() calls, but you are right: best practice is to make sure to unlock() by using a finally clause.
I changed the code accordingly.
Once there is an agreement that this is a good approach I will update the other classes accordingly.

@der-ambi The unlock() in the finally sounds OK to me!

@pmoerenhout I have modified all relevant classes to use a ReentrantReadWriteLock instead of synchronized and performed some tests, I couldn't recreate another dead-lock.

@der-ambi Thanks, I will quickly test it, and merge no problems!

@der-ambi Thanks for this submission!

@pmoerenhout Thank you very much for reviewing and merging this!
A release with this would be great.

Just released version 3.0.1 of jSMPP.

Just released version 3.0.1 of jSMPP.

Thank you very much! 👍


A+C: add Jinesi Yelizati

Please take a look.

The Cache-Go still have some problem to fix.
Please don't merge.


PasswordRepeat

A core example here mentions PasswordRepeat but nothing like that exists in the Storybook.
In fact, the solution is adding this piece of code from src to Storybook source code preview:
const PasswordRepeat: FunctionComponent = () => {
const { getValues } = useFormContext()
return (
<PasswordElement margin={'dense'}
label={'Password Repeat'}
required
parseError={parseError}
validation={{
validate: (value: string) => {
const { password } = getValues()
return value === password || 'Password should match'
}
}}
name={'password-repeat'}
/>
)
}

@AntalyanGriffin the reference is this:
https://github.com/dohomi/react-hook-form-mui/blob/master/stories/TextFieldElement.stories.tsx#L35
It kind of depends on how you use this library. Since later versions of react hook form you can also use the useWatch hook to listen to changes of the password element.

Resolved since v3.5.0 with PasswordRepeatElement


Content types differ from mage2vuestorefront

Firstly, really great work on this, indexing is really quick.
I noticed that the content types of attribute options differ from the content type provided by mage2vs. This is not an issue per se, but their is a difference i think we should discuss about.
Magento Attribute boolean types are 'true' or 'false', and importing data via mage2vs these are '1' or '0'.
Multiselect attributes with multiple options for a products are imported as arrays, that's great, but the option_ids in this array should be integers but are now strings.
Attribute options that are not filled in Magento are imported as NULL value, while in mage2vs these options are stripped from the dataset

Multiselect attributes with multiple options for a products are imported as arrays, that's great, but the option_ids in this array should be integers but are now strings.

That I will check.
@pkarw what do you think about other two points ?
Magento Attribute boolean types are 'true' or 'false', and importing data via mage2vs these are '1' or '0'.
Attribute options that are not filled in Magento are imported as NULL value, while in mage2vs these options are stripped from the dataset

Hey! Im not siren if it makes any difference. I mean - we should check if the values are accepted by the default elastic scheme. If so - for JS logic it makes no difference if we have 0/1/true/false

@pkarw what do you mean by "default elastic scheme"?
In indexer, mapping is created a dynamicly base on attribute type.
We like "calculated" type base on attribute metadata.
So it different a little than mapping created by vsf-api/mage2vuestorefront.
But for now, I don't see any problem with that..
Important fields, has the same mapping like: slug, sku, url_path, url_key, etc.
In mage2vsf -> we have schema for some attributes/fields, but for the rest (custom attributes) mapping is created dynamically by ES.
we can always change the mapping for boolean attributes to 0/1 -> for me it doesn't make any difference right now. Maybe for some real use cases, it might be better, I don't have an opinion on that.

@DaanKouters
Multiselect attributes with multiple options for a products are imported as arrays, that's great, but the option_ids in this array should be integers but are now strings.

Done, multiselect values will be now exported as integers as they should.

@DaanKouters
Multiselect attributes with multiple options for a products are imported as arrays, that's great, but the option_ids in this array should be integers but are now strings.

Done, multiselect values will be now exported as integers as they should.

Great, thank you.

@DaanKouters  @pkarw I think I can close this one ?


Increase fault tolerance of installer

Rather than just returning errors which occur in the install package to the backend try function and logging them, try to recover from them here: https://github.com/Azure/ARO-RP/pull/201/files#diff-90259a58ac8d65a2b486198e4eebb9c3R182-R197.

is there actually anything to be done here @nilsanderselde ?

@jim-minter I'll take a look today.

I think there may be some common errors which occur from specific install steps for which a retry might save time, preventing us from needing to restart the entire phase. As the installation can take a while, identifying those common errors and retrying at the step level might be worth it. My concern is it might be a little to brittle to deal with specific errors from specific steps here. I suppose a new function could be written which checks 1. which step the installer is on and 2. which error was returned and then retries it - I'm not sure what else there would be to do other than retry.
I think the scope of this issue may be too broad. If we run into chronic problems with certain steps in the future, we could consider adding logic here to deal with it, but I'll close this for now.


Gather shell scripts and docker files in their respective folders

Just to have fewer files floating around in root

#334 will resolve this issue.


Enabling visible tabs/spaces

Description of the problem or steps to reproduce
Hello,
Is there a way to enable visible tabs and spaces, just like it's possible to do in vim or mcedit?
Specifications
You can use micro -version to get the commit hash.
Commit hash: af520cf
OS: 11.1-STABLE
Terminal: xterm, rxvt-unicode-256color

You need to use a colorscheme with a color set on indent-char. It needs to be different than the default or it won't be visible.

Hello sum01,
I didn't quite understand how can I use that color set?

Copy whatever colorscheme you're using from https://github.com/zyedidia/micro/tree/master/runtime/colorschemes & put it in ~/.config/micro/colorschemes/, but give it a different name. Then run set colorscheme thenameyougaveit
Then change its color-link indent-char to whatever value you want. You should see spaces/tabs being colored.

Aha, got you.
Thank you sum01!

Resolved


du: adjust one of the GNU error message as ours is better

Congrats! The gnu test tests/du/files0-from is no longer failing!

Nice :)


[6.0][Explicit Module Builds] Cherry-pick Explicit Module Loading fixes and improvements

Explanation:
This PR is a collection of Explicit Module Build improvements and fixes:

https://github.com/apple/swift/pull/72699:
Otherwise Swift Overlay paths do not get printed for dependency cycles where the sink is the same module as the source module being built.
https://github.com/apple/swift/pull/72668:
Relying on the corresponding field in the '-explicit-swift-module-map-file' provided by the driver.

Only bridging headers require a module map because that's what aids header include resolution. With lazy module loading today, '.modulemap' parsing which happens when instantiating Clang is responsible for associating headers with modules. Then upon encountering a header include inside the bridging header the compiler knows which module corresponds to said header and is then able to load explicitly-provided PCM for that module. For all other module dependencies, they are only ever queried by-name from Swift, so '.modulemap' parsing is not necessary.
[Dependency Scanning] Add libSwiftScan entrypoint to query binary module dependencies' header inputs' module dependencies

https://github.com/apple/swift/pull/72599:
Swift interfaces will only ever query module inputs by-name, so parsing modulemap files to resolve their headers is not necessary. The exception to this is textual header ingestion directly into the Swift compiler (ClangImporter). Because then the compiler may need to resolve header includes to the corresponding module (.pcm) inputs. This requires explicitly-specified module maps, until we switch to eager module loading.
This occurs when there is a a dependency on a binary Swift module, which was built with a bridging header, and this bridging header was serialized into the .swiftmodule and must be ingested by all clients. In this case, we must ensure that all clients of said binary module, direct and transitive, are passed -fmodule-map-file= flags corresponding to dependencies of said header.
https://github.com/apple/swift/pull/72499:
This operation is not necessary for explicitly-built dependencies and causes redundant filesystem traffic when checking dependency files. With explicit modules, the up-to-date checks on module dependencies are performed by the build-system (Swift Driver).
https://github.com/apple/swift/pull/72104:
Otherwise libSwiftScan clients which rely on EmbeddedSwift feature are not able to execute dependency scans.

Scope: These changes affect dependency scanning and explicit module dependency compilation. While these actions are by-default disabled in swiftc, there are projects that rely on them. swift/72699 is a diagnostic improvement that only affects the code-path triggered on build failure. swift/72104 is an [NFC] change that affects configuration of libSwiftScan to use Swift-written compiler components. swift/72499 is an [NFC] change that disables a redundant operation during explicit module pre-compilation. swift/72599 and swift/72668 reduce the amount of -fmodule-map-file flags passed to explicit module dependency compilation tasks only to the .modulemap files of modules required for header include resolution. This should be a safe change that will only affect projects with bridging headers with their own module dependencies.
Risk: Low. Code-paths disabled by-default and the changes are meant to improve overall soundness and performance of builds.
Testing: Each of the above changes has corresponding test-suite additions.
Reviewed By: @cachemeifyoucan, @eeckstein, @tshortli, @xymus, @nkcsgexi  (for various corresponding changes above).

@swift-ci test


Feat/overrides default config

Use config package to make configuration easy extendable.

Thanks for the pr!
To be honest, I'm not a big fan of external dependencies. Only necessary. Adding the config library with config/custom-environment-variables.js file for use environment variables is implicit.
If you should change the carbon URL in your environment, I'll be happy to accept changes like your first commit.
If I don't fully understand your idea, let me know.

Ok, see my latest update :-)

great, thanks!


TFLite: add NNAPI delegation for RESIZE_BILINEAR

Add NNAPI delegation for RESIZE_BILINEAR

Gentle ping @aselle

Nagging Reviewer @aselle: It has been 14 days with no activity and the awaiting review label was assigned. Can you please take a look?

Nagging Reviewer @aselle: It has been 29 days with no activity and the awaiting review label was assigned. Can you please take a look?

Nagging Reviewer @aselle: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 44 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @aselle: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 60 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @aselle: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 77 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @aselle: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 92 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @aselle: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 107 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @aselle: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 122 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @aselle: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 137 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @aselle: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 152 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @aselle: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 182 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @aselle: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 197 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @aselle: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 29 days with no activity and the awaiting review label has been applied.

@caisq I've update the PR, because there was a review for this PR and an issue #27031 mentioned this PR recently. Please take a look and take a next step if necessary, ot this PR will be abandoned again and left opened meaninglessly. :) BTW I'm not sure whether this PR is really necessary for everybody, so feel free to let me know if this is not necessary.

Hi @hqueue, we're actually just about to switch over to using the new NNAPI delegate (in lite/delegates/nnapi), which should support the bilinear resize. That change should land shortly, likely sooner than we can land this PR. If that changes, I'll re-open the PR. Thanks!

@jdduke Thanks for the review and nice to hear that bilinear is going to be supported soon :)
I will update this PR by removing assertion  later when you re-open this PR.


Upgrade to SendGrid v3 Web API

https://sendgrid.com/docs/Classroom/Send/v3_Mail_Send/how_to_migrate_from_v2_to_v3_mail_send.html
https://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/index.html
Thanks!

Thanks for the heads up. The new send API looks great and looks way more developer friendly (easier for me to maintain!). And I'm glad there's a sandbox mode 👍!

New API committed in v1.0.0 👍


DaemonSet Unavailable on AWS deployment of Openshift.

Getting the following issue when trying to install Cilium on an AWS deployment of Openshift V4.6. I am able to install cilium through the operator hub without problem however when I run the install command on the command line "cilium install --cluster-name=x" I consistently run into this error. It seems the cilium-agent containers are not able to be deployed. I cant find any reference to this issue in the docs.
:hourglass: Waiting for Cilium to be installed...
    /¯¯\
 /¯¯\__/¯¯\    Cilium:         6 errors
 \__/¯¯\__/    Operator:       OK
 /¯¯\__/¯¯\    Hubble:         disabled
 \__/¯¯\__/    ClusterMesh:    disabled
    \__/

DaemonSet         cilium             Desired: 5, Unavailable: 5/5
Deployment        cilium-operator    Desired: 1, Ready: 1/1, Available: 1/1
Containers:       cilium             Running: 5
                  cilium-operator    Running: 1
Image versions    cilium             quay.io/cilium/cilium:v1.10.2: 5
                  cilium-operator    quay.io/cilium/operator-generic:v1.10.2: 1
Errors:           cilium             cilium          5 pods of DaemonSet cilium are not ready
                  cilium             cilium-49x5q    unable to retrieve cilium status: unable to upgrade connection: container not found ("cilium-agent")
                  cilium             cilium-fnr5t    unable to retrieve cilium status: unable to upgrade connection: container not found ("cilium-agent")
                  cilium             cilium-mg2kp    unable to retrieve cilium status: unable to upgrade connection: container not found ("cilium-agent")
                  cilium             cilium-s27px    unable to retrieve cilium status: unable to upgrade connection: container not found ("cilium-agent")
                  cilium             cilium-zntcq    unable to retrieve cilium status: unable to upgrade connection: container not found ("cilium-agent")

:leftwards_arrow_with_hook: Rolling back installation...

Error: Unable to install Cilium: timeout while waiting for status to become successful: context deadline exceeded

@owainow Could you collect a Cilium sysdump for that cluster? It's hard to help otherwise as cilium status doesn't report in-depth information.

Sure let me attach it. New to Cilium so if I've not included any info etc let me know.
cilium-sysdump-20210809-164914.zip

There seem to be an issue with pulling the image for one of the operator pods:
"state": {
    "waiting": {
        "message": "Back-off pulling image \"quay.io/cilium/operator-generic:v1.10.2@sha256:a88b04cb5895610620da6e90d362af9e512d2baa51a0a0d77ab34186dfb20c68\"",
        "reason": "ImagePullBackOff"
    }
}

There are also a couple errors in agents:
2021-08-09T14:42:44.922025191Z level=error msg="ListenAndServe failed for service health server, since the user might be running with kube-proxy. Please ensure that '--enable-health-check-nodeport' option is set to false if '--kube-proxy-replacement' is set to 'partial'" error="listen tcp :32313: bind: address already in use" serviceName=router-default serviceNamespace=openshift-ingress subsys=service-healthserver svcHealthCheckNodePort=32313
2021-08-09T14:42:44.922093099Z level=error msg="ListenAndServe failed for service health server" error="listen tcp :32313: bind: address already in use" serviceName=router-default serviceNamespace=openshift-ingress subsys=service-healthserver svcHealthCheckNodePort=32313

I don't expect those issues would cause the errors you are seeing however. I didn't find anything else in the sysdump. Were the errors still visible in cilium status after you retrieved the Cilium sysdump?

Yes, after getting the syslog if I run cilium status shows a daemon error again. I have tried again on a different cluster but the problem is consistent. Unsure why because OCP is able to "Validate" the quay image. `[owain@localhost ~]$ cilium status
/¯¯
/¯¯_/¯¯\    Cilium:         1 errors
_/¯¯_/    Operator:       disabled
/¯¯_/¯¯\    Hubble:         disabled
_/¯¯_/    ClusterMesh:    disabled
__/
Containers:    cilium
cilium-operator
Errors:        cilium             cilium    daemonsets.apps "cilium" not found
`

Hi, Any updates on this?

Can anyone help point us in a direction here? The issue seems to still exist.

@v1k0d3n when I deployed cilium via OLM on OpenShift I had to manually add the service accounts from cilium to the privileged SCC. I never got it fully functioning on OpenShift though.
Cilium CLI insists the DS does not exist and other components are not configured but they do and are.
$ cilium status
    /¯¯\
 /¯¯\__/¯¯\    Cilium:         1 errors
 \__/¯¯\__/    Operator:       disabled
 /¯¯\__/¯¯\    Hubble:         disabled
 \__/¯¯\__/    ClusterMesh:    disabled
    \__/

Containers:      cilium
                 cilium-operator
Cluster Pods:    0/446 managed by Cilium
Errors:          cilium    cilium    daemonsets.apps "cilium" not found

oc get ds
NAME     DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
cilium   12        12        12      12           12          <none>          6h54m

$ oc get pods
NAME                               READY   STATUS    RESTARTS   AGE
cilium-2vsgk                       1/1     Running   0          3h43m
cilium-75sl2                       1/1     Running   0          3h43m
cilium-7g92r                       1/1     Running   0          3h43m
cilium-b8zc5                       1/1     Running   0          3h43m
cilium-dcvv4                       1/1     Running   0          3h43m
cilium-gs7f6                       1/1     Running   0          3h43m
cilium-kqqdc                       1/1     Running   0          3h43m
cilium-kvq27                       1/1     Running   0          3h43m
cilium-olm-56b8648b4f-v8mcj        1/1     Running   0          3h43m
cilium-operator-55c9dd779d-grxcc   1/1     Running   0          3h43m
cilium-operator-55c9dd779d-kgl68   1/1     Running   0          3h43m
cilium-ptk27                       1/1     Running   0          3h43m
cilium-v2p4q                       1/1     Running   0          3h43m
cilium-wpl26                       1/1     Running   0          3h43m
cilium-znggn                       1/1     Running   0          3h43m
hubble-relay-6584f5545c-99p9n      1/1     Running   0          3h43m
hubble-ui-95d74d44c-cqsqx          3/3     Running   0          3h43m

It's probably because cilium isn't installed in the default namespace. It's necessary to provide that namespace to the CLI:
E.g.
cilium status --namespace=cilium

Yes, this is the reason. We can close this issue now.


Steps for Samsung

Guys need help in the steps to compile the boot.img for this device. I've been trying to do this for about three days now, I suppose I do not have enough knowledge to work with the software&terminal, I am so tired:
MANUFACTURER: Samsung
DEVICE_NAME: Galaxy-J2
DEVICE_CODENAME: j23g
MODEL_NUMBER: SM-J200H
SOC_NAME: Exynos 3475, Cortex-A7
Processor Model:  Mali-T720
MANUFACTURER_LINUX_KERNEL_VERSION: 3.10.49
I found the kernel according to CODENAME: j23g
android_kernel_samsung_j23g
What should be the next step?
I use this patch:
https://github.com/pelya/android-keyboard-gadget/blob/master/HTCM7_patch_steps

You are using Samsung. Right? So use 3.18 patch. I am have 3.0.101 kernel for all roms from latest samsing stock 4.2.2 to 6.0.1. I used the 3.01 patch and everything worked!

Next steps are:

download the source for your kernel from your link (https://github.com/j23g/android_kernel_samsung_j23g)
Go to the root of the linux kernel tree (where you unpacked / downloaded the src)
Put the patch file there as well (download it as well)
Execute patch -p1 < name-of-patch-file


SQL Homework 2-6

Added SQL homework 2-6
Resolved empty merge conflict on Homework 3.
Deleted unnecessary files.

HW1,2,3,4,5,6 Marked.


Resiliency when JDownloader is down

I use this as a Docker container to expose the API for JDownloader. It's set up in a compose with a JDownloader container which sometimes does take a while to start up. Even though I have this container set to depend on that one, the time taken for startup might be longer, and sometimes this container exists without letting that one fully spin up. This also happens if the other container is updating.
Ideally, the container should keep retrying when the connection is down rather than just quitting. In below log, last attempt is at 11:12, and it does not retry after that. A restart of the container fixes it, but I have to do this manual step whenever I restart my host/compose.
today at 11:08:43 AM Error connection to MyJDownloader: Device not found
today at 11:08:43 AM
today at 11:08:43 AM Could not connect to My JDownloader! Exiting...
today at 11:08:58 AM Error connection to MyJDownloader: Device not found
today at 11:08:58 AM
today at 11:08:58 AM Could not connect to My JDownloader! Exiting...
today at 11:09:13 AM Error connection to MyJDownloader: Device not found
today at 11:09:13 AM
today at 11:09:13 AM Could not connect to My JDownloader! Exiting...
today at 11:09:27 AM Error connection to MyJDownloader: Device not found
today at 11:09:27 AM
today at 11:09:27 AM Could not connect to My JDownloader! Exiting...
today at 11:09:42 AM Error connection to MyJDownloader: Device not found
today at 11:09:42 AM
today at 11:09:42 AM Could not connect to My JDownloader! Exiting...
today at 11:09:56 AM Error connection to MyJDownloader: Device not found
today at 11:09:56 AM
today at 11:09:56 AM Could not connect to My JDownloader! Exiting...
today at 11:10:11 AM Error connection to MyJDownloader: Device not found
today at 11:10:11 AM
today at 11:10:11 AM Could not connect to My JDownloader! Exiting...
today at 11:10:25 AM Error connection to MyJDownloader: Device not found
today at 11:10:25 AM
today at 11:10:25 AM Could not connect to My JDownloader! Exiting...
today at 11:10:40 AM Error connection to MyJDownloader: Device not found
today at 11:10:40 AM
today at 11:10:40 AM Could not connect to My JDownloader! Exiting...
today at 11:10:55 AM Error connection to MyJDownloader: Device not found
today at 11:10:55 AM
today at 11:10:55 AM Could not connect to My JDownloader! Exiting...
today at 11:11:09 AM Error connection to MyJDownloader: Device not found
today at 11:11:09 AM
today at 11:11:09 AM Could not connect to My JDownloader! Exiting...
today at 11:11:24 AM Error connection to MyJDownloader: Device not found
today at 11:11:24 AM
today at 11:11:24 AM Could not connect to My JDownloader! Exiting...
today at 11:11:38 AM Error connection to MyJDownloader: Device not found
today at 11:11:38 AM
today at 11:11:38 AM Could not connect to My JDownloader! Exiting...
today at 11:11:53 AM Error connection to MyJDownloader: Device not found
today at 11:11:53 AM
today at 11:11:53 AM Could not connect to My JDownloader! Exiting...
today at 11:12:07 AM Error connection to MyJDownloader: Device not found
today at 11:12:07 AM
today at 11:12:07 AM Could not connect to My JDownloader! Exiting...
today at 11:12:22 AM Error connection to MyJDownloader: Device not found
today at 11:12:22 AM
today at 11:12:22 AM Could not connect to My JDownloader! Exiting...

I’ll happily accept pull requests
Since this repo is just a minimal fork of the FeedCrawler project I will not actively work on feature requests.

Have you thought about using —restart-unless-stopped ?


RedisFactoryLockProvider impl

#47 for this issue.
For this implementation you need SpringBoot.
Configuration is pretty same as the Jedis version but it uses RedisConnectionFactory instead of JedisPool.

I dunno what's go wrong with my test, if I run in IDE as JUnit it works. Any idea?

Thanks, I will look at it in next few days.

Any chance we get this check failed fixed?

Sorry, I do not understand?

Why could I not find that code on master?

It's here https://github.com/lukas-krecan/ShedLock/tree/master/shedlock-provider-redis-spring I have renamed the module. I am still not sure about the name, that's why it's not released yet.

Ahhh, ok! I just copied the Provider to my code and I will wait for the release.
Thanks @lukas-krecan

Maybe we change the Jedis one to shedlock-provider-redis-jedis to keep these two consistent like the shedlock-provider-jdbc-* ones?

Yes, but it would require to do something like this https://github.com/lukas-krecan/ShedLock/pull/51 in order to keep it backward-compatible  But maybe better now then later.

Released as 0.18.0

You should update the Wiki as well.
Thank you guys for my first contribution. :)


UI / UX Suggestion: Fixed left sidebar for waypoints

When "more information" is clicked on the left sidebar, the length of the page requires scrolling to read the complete instructions. Just thought it would be better if that section was fixed and was scrollable. Sort of the way it works on Codecademy.

On the longer challenge scrolling the page is required anyway. Given our current layout there's no way to make the more information panel fixed without it covering other important elements up. I'm closing this issue for now as the current UI works and we're more focused on ensuring all the challenges are performing their job well.


Fix most warnings and clean up code

Validation
How did you test these changes?

[x] Built and ran the app
[ ] Tested the changes for accessibility

Ok for me.


CAMEL-21018: camel-torchserve - Add ITs

Description
Added camel-test-infra-torchserve and ITs for Camel TorchServe using the test infra.
Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

/component-test ai


Background color not applied for CJK text in editor

Hey, Rien! Just installed this plugin in a snap and it works beautifully!
One issue:
If I set a text color for Japanese-character tag, it doesn't work, and resets to default color.
When I change the tag to Latin characters, it works.
Before Change

After Change
In Settings:

In Editor:

Thanks!! 🙇♂

this is the bug of obsidian, tag with CJK character does not have proper class name.
I have report this bug in obsidian forum

I see!
Thank you :-) 🙇♂
――
ミュア・エヴァン カーター
WhiteHat ICT創設者
TeA／授業内外支援
情報技術関連サポート
宮崎国際大学 (mic.ac.jp) https://www.mic.ac.jp/
〒889-1605 宮崎県宮崎市清武町加納丙1405番地1
Evan Carter Muir
Founder of WhiteHat ICT
Education + Tech Support
Miyazaki International College (mic.ac.jp) https://www.mic.ac.jp/english/
1405-1 Kanō-hei, Kiyotake-chō, Miyazaki-shi, Miyazaki-ken, Japan 889-1605
2022年10月31日(月) 13:20 RieN 7z @.***>:

this is the bug of obsidian, tag with CJK character does not have proper
class name.
I have report this bug in obsidian forum
https://forum.obsidian.md/t/cjk-tags-do-not-have-correct-class-name/46617
—
Reply to this email directly, view it on GitHub
https://github.com/rien7/obsidian-colorful-tag/issues/21#issuecomment-1296520824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPFKKYEKJ5QHA5VSFF7773WF5CKPANCNFSM6AAAAAARSRM2DQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Not work in Safari Version 11.0 (126<IP_ADDRESS>.7)

Scroll not work in Safari Version 11.0 (126<IP_ADDRESS>.7)
and no console error

Working in Safari 11 for me. It's possible you have "Reduce Motion" enabled under System Preferences > Accessibility > Display.
Right now, only Safari supports this feature, but when enabled, animation is disabled as it can be jarring to people who suffer from motion sickness.

Reduce Motion, oh! I would never have thought of this feature.  Thanks.


[PR testing][CI] - Switch to custom fork for triggering test workflows in CI

Description
Testing changes from https://github.com/opensearch-project/opensearch-benchmark-workloads/pull/319, required to run integ tests prior to creating PR
Issues Resolved
n/a
Testing

[x] New functionality includes testing

[Describe how this change was tested]

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.

@martin-gaievski I'm closing this PR as the connecting PR in the workloads repository has been merged.


MapContext: Finish basic CRUD workflow in UI (create, list, edit, delete)

Environment

Python version: 3.7+
MrMap version:  1.0-pre

Proposed Functionality

[x] Created MapContext resources shall be listed in list view
[x] Created MapContext resources can be deleted
[x] Created MapContext resources can be edited

Use Case
User wants to perform basic MapContext-related tasks

Database Changes
Probably none.

External Dependencies
None.

merged in #174 - close this


163 hovering score logs anchorel prop is invalid error

Closes #163
Description of changes

see commit messages

Additional context

errors not displaying locally:

wow hey great work on this


drivers/ovsdbDriver.go: fix govet UUID

This is green now.
ping @jojimt @abhinandanpb @erikh @gaurav-dalvi

LGTM. Any reason why this was not hit when the PR that changed this went thru the sanity run ?

@abhinandanpb I don't know right now. I've hit it on my host during the checks.

@unclejack  Weird, I just tested the []Foo{{"bar"}} declaration style with go vet on 1.7.3 and 1.5.0 and neither of them complained about it.  I'm curious what the exact error output you got was.

Yeah I'm seeing it too, I think it's a golint/go vet version issue

@erikh is probably right. I've seen this happen after switching to Go 1.7.3.

Let's merge this if we can today, #610 depends on this which I hope to have ready by EOW.


Making compatible with C++ 20

I wanted to use the format C++ 20-style on strings:
https://en.cppreference.com/w/cpp/utility/format/format
But got an error message. I think this may indicate that the makefile makes use of an older C++.

Is that the right diagnostic?
Would it be possible to make the makefiles C++ 20 compatible?

OK, just checked, I have a quite old compiler that does not support C++20, that may be the reason. Still keeping open just to check if others are able to use C++20 features.

Not all compilers are ready for C++20, some LTS versions of popular Linux distributions are not even ready for C++17. That's why there's a line CXX_STANDARD 14 in the file CMakeLists.txt.
If your compiler supports C++20 and you have a fairly recent version of CMake then you can just modify that line.
Does that help?

This is perfect, many thanks :) . Do you think it would be possible to add a line or two of explanations about this on the readme of this repo? :) .

Good idea!
I would love to have that documented somewhere.
Even better if it would contain the reasons for that decision so that we can upgrade to C++17 or later at some point in the future.

The downside of this is for mentors. A common workflow is for the mentors to download and run the exercise locally, so:

Their local environment would need to support it, and not everyone wants (or can) run a bleeding edge compiler.
They'd have to recognize the problem and change the CMakeLists locally, as the CMake file is not uploaded AFAIK.

Also, it makes the mentoring job a lot harder. C++ has had some pretty large changes in usability and best practices from C++14 to C++20, so the solutions that they would suggest would differ depending on which version you were using, and there's not a consistent way to know the version just looking at the code.
There's lots of existing discussion from when I updated things to C++14 See #189 and #292
And to be clear I'm not saying "Don't do this". I am saying that you should probably label your version at the top of your solution file if you expect a mentor to look at it.
You are welcome to add that info to the documentation - https://github.com/exercism/cpp/tree/main/docs

Coming back to this, in the past we've said that our minimum supported version should be the default installs on the oldest Ubuntu LTS version. If that still makes sense, we can now update the default to C++17, and updating to C++20 could be done when Ubuntu 18.04 goes out of support in April 2023.

@patricksjackson Tying "our" C++ to the oldest Ubuntu LTS sounds somewhat reasonable. But in practice we've already transitioned to C++17, that's what we're using in out CMakeLists.txt files (e.g. see this one from hello-world).

Oh man, I guess I've really not been paying attention. Thanks @siebenschlaefer

It is worth noting that as of June 2022, the only STL to support std::format is clang 14, which disables it by default because it's incomplete still.

Recent versions of GCC now have pretty much complete support for C++20, both core language and libraries. Is there anything holding back updating to C++20 at this point? It would be nice to be able to use ranges in solutions.

@siebenschlaefer  @mattnewport
When I look at the table for compiler compatibility ,  I see a lot of overlaps with C++20 and the latest clang (12)  and GCC (10.5) builds that are available on Ubuntu 20.04.
Many people are looking for std::format support, which is still incomplete in these versions, as far as I can tell.
I suggest we transfer to C++20 when LTS for Ubtunu 20.04 ends in April 2025.

@vaeng a year seems a long time to wait given that there are a number of other C++20 features available in GCC 10 that would be quite useful - ranges and span are the two that I see a lot of use for. Those would make for cleaner solutions to quite a lot of exercises, more so than format support in my opinion. There are some other niceties like contains() for associative containers, the spaceship operator, etc. but ranges are really the big one that could change how a lot of exercises can be solved for the better.

@mattnewport
I'm with you about ranges and spans. I also understand the hesitation to leave an LTS behind before it's due.
The next few weeks will bring Ubuntu 24.04 LTS and therefore the future compiler milestone.
I could see the argument to skip the last year with two LTS versions, but I'm very unsure about the actual version distribution with exercism users.

@vaeng
Ok, I realize now that I can set CXX_STANDARD 23 in CMakeLists.txt and add it to my config.json under files -> solution and submit that and it will mostly work, barring some missing features in whatever compiler version exercism is using (ranges::fold_left() is not available for example).
This actually addresses most of what I want as it means I can submit solutions to exercises using ranges and even some C++23 features like the monadic functions on optional.
I do think ranges makes C++ much more approachable for newcomers to the language (being able to just write sort(vec) rather than sort(begin(vec), end(vec)) defers a whole lot of questions to later in the learning process) so I think there would be value in moving the defaults to C++20 and I would probably mention the simpler C++20 solutions in some mentorship discussions but being able to use most of C++23 in my own solutions is good enough for now.

Pushing new features vs not breaking things for people (stability, compatibility) is an age old balance. People who want the new feature really want the new feature. The pros of pushing are obvious to them. But the cost of breaking things for other people can be pretty high! Try to imagine if your code suddenly stopped working one morning because someone wanted to play with some shiny new thing.

@IsaacG
I don't really see the relevance of your concern here? We're not talking about anyone's code stopping working because someone wanted to use language or library features from newer versions of C++ in this context. We're not even really talking about "pushing new features" since as I discovered it is already possible to use most of C++23 in exercism solutions that will compile and pass the automated tests.
The one reasonable issue that has been raised as a concern is that mentors may be on an older LTS version of Ubuntu that doesn't package recent versions of clang or gcc and that as a result if the default settings for C++ exercises on Exercism targeted features not available on their compiler version they wouldn't be able to build / run the mentee's solution locally. That is not really the same type of problem at all.
Exercism is a language learning platform and for C++ it is valuable to support the latest versions of the language both for newcomers to the language to learn new features that simplify the use of the language in common situations (e.g. ranges) and for experienced users of the language like me who want to learn and experiment with newer language features in a safe context that doesn't raise the types of concern you are bringing up for 'production' code that may need to work in environments that don't yet support newer C++ standards.
Isn't a big focus of Exercism to give programmers a safe place to 'play with some shiny new thing'? That's why it supports a whole range of languages that most programmers won't get much opportunity to use 'in production' in their day to day work but that they want to learn out of curiosity. If I can't use C++23 yet in my day job or when contributing to open source projects because they aren't yet willing or able to require compiler versions that support it in all of their supported build configurations then where else am I supposed to learn and practice it other than in a 'safe space' like Exercism where those concerns don't apply?

The test-runner works with alpine 3.18 and runs with the respective compiler versions. On the other hand there is the github action, that checks the promised baseline of ubuntu-20.04 (which is the lowest version available for github's images).

I could see the argument to skip the last year with two LTS versions, but I'm very unsure about the actual version distribution with exercism users.

I don't think we can possibly know. Personally I can use the newest Ubuntu release without any problems, I use a Vagrant image for solving and mentoring. But I don't have a clue about our students. I could imagine that some are stuck on older hardware and/or distributions because they cannot afford updating them for various reasons, they might not be able to afford it, it might be a big effort updating everything on their computer, or they might not own the computer and therefore have not the rights to update it.
I think this is a strategic decision where @iHiD or @ErikSchierboom might want to weigh in, whether it's more important to have newer features of the language available or being able to support older hardware/compilers.

Isn't a big focus of Exercism to give programmers a safe place to 'play with some shiny new thing'?

Is it? I'm not so sure about that. While I had lot of discussions with students and mentors about idioms and finer details I think the fundamental goal of Exercism has not changed: Teaching language fluency (being able to understand the basics of the language and being able to read code) rather than language proficiency (being able to solve real-world problems, writing at expert-level). At least I haven't heard the notion of a "safe space" for exploring brand-new features as an explicit goal of Exercism.

The open question then is whether to update the template CMakeLists.txt to enable C++20 by default. I still think ranges make this a potentially good idea for newcomers to C++ as it simplifies many common scenarios but I'm not sure who would be able to make that decision?

In the past that has been the decision of the maintainers of the C++ track. @arcuru is the most senior maintainer, @vaeng and me are have been more active in the last couple of months.
Personally I like the idea of sticking to an older but still supported LTS version of one of the popular Linux distributions. That should allow virtually all students and mentors to work locally. For me, not having access to std::ranges is just a small nuisance.

I think this is a strategic decision where @iHiD or @ErikSchierboom might want to weigh in, whether it's more important to have newer features of the language available or being able to support older hardware/compilers.

We don't have a definitive take on this, but in general tracks usually try to stay quite up to date. But, the situation for C++ is relatively unique in that there is such a wide variety of "stable" versions. There's the Ubuntu LTS as you mentioned, but also other distros and then there's GCC vs Clang.
I'm not very well known with the C++ ecosystem, but could users on older versions of their distros manually install a newer version of C++?

(I noticed the ping here so I will chime in with my very old context. It's mentioned above that I'm the most 'senior' maintainer but I have not been active for quite a while (years) and @siebenschlaefer has more recent context and experience as a Mentor.)
My comments above from many years ago were largely made before Exercism supported an online editor/tester, and the main way of testing and running was local. With the online editor, we can tell students 'hey you have a very old version, and for development you really need to be running a more recent distro. if you can't do that just use the website'. Does the mentor flow work in the online editor?
I always liked the fact that Exercism worked largely locally, but if anyone is stuck on an old distro we can always point them to the online editor. There are just a lot more options nowadays to run things.
I'll also say, I never saw an example of "What if a mentor doesn't have access to a new version locally?". If Mentors ever chimed in on this sort of issue, it was always with an understanding that other people might be effected. Mentors, as you can see above with @siebenschlaefer running things in a Vagrant container, are mostly able to solve the out of date problem themselves. And the student problem already seems solved with the online editor.

Hi there. First, thank you to the C++ track creators and maintainers! I'm finally getting around to learning C++ and so far this is some great content :pray:
I understand the complexities of the different versions, but it sounds like there's support for upgrading the test runner so that C++20 and maybe later. I wanted to voice my support for this as well, because even a "safer" method of formatting a string like std::format should be accessible to people learning C++ and want their code to by default be as safe as possible.
Again, thank you for all you do!


automatically accept owner privileges from group members

@dtarb @martinseul  A feature came up in my discussions of CZO capabilities that might have general utility for most users.
Currently we make users "accept" ownership of a resource from others. Ostensibly, this is because ownership is a responsibility. Thus, assignment of ownership is a two-step process: request and either accept or deny.
There is a case in which this is overly tedious, when the owner of a group wants to own all resources that relate to group work. This is particularly important when that owner is also the manager of a group of transient graduate students, e.g., as the PI of a grant. Then, the owner persists while the workers change.
This proposal is to allow a user to set a flag in the user profile that automatically approves assignment of ownership in the following conditions:

The user is the owner of a group g.
The initiator and current owner of the resource r is a member of that group g.
The user flag mentioned above is True. Working name is auto_approve_owner_from_groups

In this case, the ownership transfer would automatically be approved without queueing it in the request system. It would not be necessary to share the resource with the group first. Since multiple ownership is supported, assignment of ownership is sufficient and transfer of ownership is not required.
This would greatly ease workflows for the CZOs, because it is their intent that site managers should own all resources for the site. This would make that a one-step process. It strikes me that most Ph.D. advisors would like the exact same feature for their research groups.
This is really simple to implement: a day's work.

@dtarb This is curious because I specifically remember that transfer/accept was specified for ownership.

We did discuss this in our early specifications, and I think it was going to be a later implementation phase.  The first implementation did not do this because we did not have messaging, and no one has complained about the current implementation that does not have transfer/accept.

@dtarb @alvacouch are we OK to close this?

I am happy with current functionality so am happy to close this.

closing as agreed above


My result is not good

Hi, thanks for your great work.
I trained the model using script 'python train.py --gpu 0-1 --backbone LPSKI' with Human3.6M and MPII datasets with 2 GTX 1080Ti.
My config.py is like below:
    backbone = 'LPSKI'

    trainset_3d = ['Human36M']
    trainset_2d = ['MPII']
    testset = 'Human36M'

    input_shape = (256, 256)
    output_shape = (input_shape[0]//8, input_shape[1]//8)
    width_multiplier = 1.0
    depth_dim = 32
    bbox_3d_shape = (2000, 2000, 2000) # depth, height, width
    pixel_mean = (0.485, 0.456, 0.406)
    pixel_std = (0.229, 0.224, 0.225)

    ## training config
    embedding_size = 2048
    lr_dec_epoch = [17, 21]
    end_epoch = 25
    lr = 1e-3
    lr_dec_factor = 10
    batch_size = 64

    ## testing config
    test_batch_size = 32
    flip_test = True
    use_gt_info = True

    ## others
    num_thread = 12 #20
    gpu_ids = '0,1'
    num_gpus = 2
    continue_train = True

And I tested the model with test.py :
python main/test.py --gpu 0-1 --test_epoch 24-24 --backbone LPSKI

And the result is like below:
[0m Protocol 2 error (MPJPE) >> tot: 65.84
Directions: 58.14 Discussion: 66.00 Eating: 58.89 Greeting: 60.22 Phoning: 66.14 Posing: 58.50 Purchases: 57.18 Sitting: 79.16 SittingDown: 90.43 Smoking: 66.33 Photo: 74.44 Waiting: 63.51 Walking: 52.24 WalkDog: 67.90 WalkTogether: 59.40

I wonder if it's a setup issue，During training，the loss between about epoch 13 to epoch 24 has a little change。The log is here
Lastly, I want to know where can I find your trained model? :)  Looking forward to your reply！

By the way, the params of model calculated by torchsummary is inconsistent with the paper：
embedding_size = 2048, width_mult=1 : Total params: 3.50M

In your paper, the params under the same configuration is 4.07M
I want to know what is the difference? Is there have any other special settings？
Looking forward to your reply！

After review the other issues, i find the difference between above config.py and yours is:
 output_shape: (input_shape[0]//8, input_shape[1]//8) --> (input_shape[0]//4, input_shape[1]//4)
 depth_dim = 32 --> 64

Now , i find it match the original picture in the paper:
output shape is 64,64,1152
64 -->input_shape[0]//4
1152-->num_keypoints * depth_dim = 18 * 64

So I will check the result after training
It is recommended that you modify the code of config.py on github :)

@SangbumChoi I have finish the training on 2 GTX 1080Ti about 30 hours. After change the config, the GPU memory occupancy
is bigger, so i change the bacth_size to 32
I test the model on epoch 23 and 24 like this:
python main/test.py --gpu 0-1 --test_epoch 23-24 --backbone LPSKI

The log is here. The result is below:
>>> Using GPU: 0,1
Load data of H36M Protocol 2
creating index...
index created!
Get bounding box and root from groundtruth
============================================================
LPSKI BackBone Generated
============================================================
100%|████████████████████████████████████████████████████████████████████████████████████████████████████████| 136/136 [01:54<00:00,  1.18it/s]
Evaluation start...
Protocol 2 error (MPJPE) >> tot: 60.26
Directions: 55.26 Discussion: 60.47 Eating: 53.43 Greeting: 57.23 Phoning: 60.88 Posing: 52.77 Purchases: 55.38 Sitting: 73.62 SittingDown: 80.20 Smoking: 59.51 Photo: 66.54 Waiting: 56.99 Walking: 47.51 WalkDog: 62.86 WalkTogether: 54.66
Test result is saved at /home/data3_4t/wzy/codes/MobileHumanPose/main/../output/result/bbox_root_pose_human36m_output.json
03-29 15:33:15 Protocol 2 error (MPJPE) >> tot: 60.26
Directions: 55.26 Discussion: 60.47 Eating: 53.43 Greeting: 57.23 Phoning: 60.88 Posing: 52.77 Purchases: 55.38 Sitting: 73.62 SittingDown: 80.20 Smoking: 59.51 Photo: 66.54 Waiting: 56.99 Walking: 47.51 WalkDog: 62.86 WalkTogether: 54.66
============================================================
LPSKI BackBone Generated
============================================================
100%|████████████████████████████████████████████████████████████████████████████████████████████████████████| 136/136 [00:53<00:00,  2.55it/s]
Evaluation start...
Protocol 2 error (MPJPE) >> tot: 60.51
Directions: 55.71 Discussion: 60.89 Eating: 53.79 Greeting: 57.65 Phoning: 61.38 Posing: 53.04 Purchases: 55.66 Sitting: 74.17 SittingDown: 79.73 Smoking: 59.67 Photo: 66.65 Waiting: 56.86 Walking: 47.60 WalkDog: 63.12 WalkTogether: 54.74
Test result is saved at /home/data3_4t/wzy/codes/MobileHumanPose/main/../output/result/bbox_root_pose_human36m_output.json
03-29 15:34:11 Protocol 2 error (MPJPE) >> tot: 60.51
Directions: 55.71 Discussion: 60.89 Eating: 53.79 Greeting: 57.65 Phoning: 61.38 Posing: 53.04 Purchases: 55.66 Sitting: 74.17 SittingDown: 79.73 Smoking: 59.67 Photo: 66.65 Waiting: 56.86 Walking: 47.60 WalkDog: 63.12 WalkTogether: 54.74

As you can see, the result on Protocol 2 is about 60.51mm.
In your paper,  the result of large model is 51.4mm.
I don't know how to fill the gap :(
By the way, the param of  calculated by torchsummary is 3.64M, in your paper is 4.07M. I don't know what the gap.
Could you help me? Looking forward your relpy!  :)

@Berry-Wu Do you have any update on this? I really want to know If you can reproduce the result on the paper or not, I cannot match the setting as the paper said

@SonNguyen2510 Sorry, I didn't reproduce the result of the paper. My result is above, which has a gap with the paper.  After several modifications，I think my config is consistent with the original paper. You can refer the config above. I hope it will help you! :)
Besides, the author provides the pretrained model in there, you can test on it. I havn't do it.
https://drive.google.com/drive/folders/146ZFPZyFyRQejB8CBYZ_R26NEXEO4EjI?usp=share_link

@Berry-Wu thank you for your reply, in order to test the pretrain model, I think I need to match it configuration. Do you know what is the config of that model? thanks again

@SonNguyen2510  Sorry, I don't know. :(  You can refer this issue: https://github.com/SangbumChoi/MobileHumanPose/issues/30
It seems that the author just uploaded random pth files.

@Berry-Wu it's ok, thank you anyway :)


fix base64, hex string mixup

Hi @matbech, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;


fix binding list test

Description
The conformance binding test list operation used the wrong operation
Issue reference
n/a
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

Conformance tests for PR do NOT run the Azure blob storage test by default, so it does not indicate that the underlying issue in the blob storage binding noted in #1051 has been fixed.
@artursouza #1273 should be merged and then the /ok-to-test initiated on this PR to validate the Azure conformance tests on this PR.

/ok-to-test

@CodeMonkeyLeet it would be good to follow up on https://github.com/dapr/components-contrib/pull/1273 with a Dapr-Bot comment giving feeback about execution status and perhaps even a link.

@yaron2 it looks like the test ran and showed that the blob storage test will fail the list operation test, see https://github.com/dapr/components-contrib/actions/runs/1505608130, and it pulled the e0267bf commit hash that was current at the time you ran the command.
It's a good suggestion to have the bot commands respond in comments with the run info, but I was just fixing up the existing implementation that didn't work. @tanvigour to note the suggestion, if you still own the automation piece here.


Update Gulp details describing how to bundle and minify with version 4

Gulp 4 introduced breaking changes, as such the existing documentation is only valid for versions of Gulp prior to version 4. With that said, I'd like to add the documentation for Gulp 4 support into the Bundling and Minification document. I intend of having this PR count towards my Hacktoberfest contributions 🤘.
/cc @scottaddie

@IEvangelist Thanks for volunteering to do this. Ping me when the PR is ready for review.


Package won't install because<EMAIL_ADDRESS>no longer exists

If you try to download<EMAIL_ADDRESS>the NPM registry can't find it:
{
  "error": "package could not be found."
}

this is almost certainly a local cache issue on your part


[local context] refine error message

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Refine messages of local context when saving per PM feedback, below is an example:
"Your preference of: –name AzureFunctionsQuickstart-rg and –location westeurope are now saved to local context. To learn more, type in az local-context –help "
Describe the bug

To Reproduce

Expected behavior

Environment summary

Additional context

local context


Android Basics: Activities and intents

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-activities-intents?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-3-pathway-1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-training-activities-intents#6
In which task and step of the codelab can this issue be found?
Task 3 (Activities and intents), step 7 (Set Up Implicit Intent)
Describe the problem
Should this...
companion object {
val LETTER = "letter"
val SEARCH_PREFIX = "https://www.google.com/search?q="
}
be this...
companion object {
const val LETTER = "letter"
const val SEARCH_PREFIX = "https://www.google.com/search?q="
}
Maybe the keyword const can be left out...but I wanted to let you know just in case.

Thanks for filing! This should now be fixed


Use addItem + custom item are not listed with getItems

For Flint i deal with a lot of custom item classes.
Sounds like if an item is created without a legend, added to the plot, the item displayed but not listed by getItems
As result

Every items are displayed
But the getDataRange are wrong

In fact only the last or the first one is listed because i guess the plot drops the dup empty keys "".
To be checked.
plot = PlotWidget()

item = items.Curve()
item.setData([0,10], [0,10])
plot.addItem(item)

item = items.Curve()
item.setData([0,-10], [0,-10])
plot.addItem(item)

plot.resetZoom()

print(list(plot.getItems()))
print(plot.getDataRange())

My exemple was not tested, it uses normal curves. Maybe my problem is only with custom items. But i am not sure about it.


amplifyPush issue with pushing backend changes

** Please describe which feature you have a question about? **
amplify push
** Provide additional details**
Following is my amplify build settings
version: 0.1
backend:
  phases:
    build:
      commands:
        - amplifyPush --environment dev
frontend:
  phases:
    preBuild:
      commands:
        - yarn install
    build:
      commands:
        - yarn run build
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

The backend build fails with following error
2020-03-09T05:43:20.006Z [INFO]: # Getting Amplify CLI Cloud-Formation stack info from environment cache
2020-03-09T05:43:20.033Z [INFO]: # Start initializing Amplify environment: dev
2020-03-09T05:43:20.034Z [INFO]: # Initializing new Amplify environment: dev (amplify init)
2020-03-09T05:43:23.023Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2020-03-09T05:43:26.621Z [INFO]:
2020-03-09T05:43:26.622Z [INFO]: For more information on AWS Profiles, see:
                                 https://docs.aws.amazon.com/cli/latest/userguide/cli-multiple-profiles.html
                       96:   jobs: [Job] @connection(limit: 10000)
                                 ^
                                 97: }
                                 Unknown directive "aws_cognito_user_pools".
                                 GraphQL request (100:1)
                                 99: type Profile @model
                                 100: @aws_cognito_user_pools
                                 ^

My job model looks like something like
type Job @model
@aws_iam @aws_cognito_user_pools
@auth(rules:[{ allow: owner }])
@searchable
{
	id: ID
	title: String!
}

When I run amplify push from local, everything works fine. However running from amplify auto build fails the above error.

This solves the problem
https://github.com/aws-amplify/amplify-cli/issues/1566#issuecomment-498508244


Prevent empty link and script tags when custom CSS or custom JS not s…

Prevent invalid empty <link> or <script> tags being present in swagger HTML when CustomStylesheetUri or CustomJavaScriptUri properties are not populated.
Additionally, HTML encode URLs when included in page.

Thx for the PR!

v12.0.14


Spring-cloud-stream and spring-cloud-config messing up multiple binder config

issue
I found an issue when using spring-cloud-stream and spring-cloud-config using multiple binders.
Starting the demo app without config-service everything works perfect. All bindings are directed to their dedicated connection.
Activating the config-service results in false connections. All bindings are directed to the default connection. Erroneous exchanges/queues are created.
how to reproduce
I made a demo app to show it.
https://github.com/HaVonTe1/spring-cloud-stream-multiplebinder-config-issue-
In there is a demoservice with simple config in application.yml:
spring:
  rabbitmq:
    host: localhost
    virtual-host: /defaultVH
    username: defaultUser
    password: defaultPassword
  cloud:
    stream:
      bindings:
        sampleQueueA:
          binder: rabbit-A
          contentType: application/x-java-object
          group: groupA
          destination: sampleQueueA
        sampleQueueB:
          binder: rabbit-B
          contentType: application/x-java-object
          group: groupB
          destination: sampleQueueB
      binders:
        rabbit-A:
          defaultCandidate: false
          inheritEnvironment: false
          type: rabbit
          environment:
            spring:
              rabbitmq:
                host: localhost
                virtualHost: /vhA
                username: userA
                password: paswdA
                port: 5672
                connection-timeout: 10000
        rabbit-B:
          defaultCandidate: false
          inheritEnvironment: false
          type: rabbit
          environment:
            spring:
              rabbitmq:
                host: localhost
                virtualHost: /vhB
                username: userB
                password: paswdB
                port: 5672
                connection-timeout: 10000

There is also a bootstrap.yml for using the config-service:
spring:
  main:
    banner-mode: "off"
  application:
    name: demo-service
  cloud:
    config:
      enabled: true #change this to use config-service
      retry:
        maxAttempts: 3
      discovery:
        enabled: false
      fail-fast: true

When setting spring.cloud.config.enabled=false the rabbit connections are just fine:
image_rabbit_good
But with spring.cloud.config.enabled=true the connections are messed up.
image_rabbit_bad
I made 100% sure the config-service is delivering the exact same properties like the application.yml of the demoservice includes.
expected behaviour
Regardless of using the config-service. The connections should be the same.

See also https://github.com/spring-cloud/spring-cloud-stream/issues/1124 (duplicate essentially)


fabio running in nomad keep restarting

I just followed https://www.nomadproject.io/intro/getting-started/running.html to install vagrant, all the way down to nomad web ui and it's fine to access the http://localhost:4646 and the nomad management ui loaded without problem. And then I followed the load balancing guide with fabio: https://www.nomadproject.io/guides/load-balancing/fabio.html, at first I'm not able to access the fabio ui through http://localhost:9998, and then I changed port forwarding setting in vagrantfile:
config.vm.network "forwarded_port", guest: 9998, host: 9998
config.vm.network "forwarded_port", guest: 9999, host: 9999

Now I'm able to access the fabio ui, but failed to open the apache web default page at http://localhost:9999, looking at the status of fabio, the status column cycling through running->pending->failed
ID        Node ID   Task Group  Version  Desired  Status    Created     Modified
890b1f82  b817874c  fabio       5        run      failed    10m53s ago  9m19s ago
f1a6b2c8  3ded5e6a  fabio       5        run      failed    10m53s ago  9m20s ago

And the output of the fabio log is always empty, I'm new to the nomad and have tried hours can't figure out the issue, can somebody help me out?
Thanks!!!

Seems like this issue could be closed, no?