Feature Idea - Point entity should be be able to support labels and other editor component features

Point should be a geometry editor component similar to polyline-editor.component.ts so that it can support labels and other features that are supported by the editor components.
I suggest creating the following classes to support this:
Models:
angular-cesium-widgets/models/editable-point.ts
angular-cesium-widgets/models/point-edit-options.ts
angular-cesium-widgets/models/point-edit-update.ts
angular-cesium-widgets/models/point-editor-observable.ts
Components:
angular-cesium-widgets/components/point-editor/point-editor.component.ts
Services
angular-cesium-widgets/services/entity-editors/point-editor/point-editor.service.ts
angular-cesium-widgets/services/entity-editors/point-editor/point-manager.service.ts
I have already started on this and should have a PR open soon.

Hi,
Thx we happily accept PRs.
The file structure seems right, but notice some of the entities already exists (edit-point.ts and PointProps in polyline-edit-options.ts).
Let us know if you need help :)

I created the point editor to display the point once the mouse drag event registers on the map. I think that this would also be a good feature for the other components (circle, polygon, etc).  See this demo for further example. I know that when I am drawing entities it is sometimes confusing to know if I already selected the draw feature or not.  This way you know that it is ready to be drawn to the screen as soon as you click.
https://youtu.be/reTXhCrFsRw

#322 looks good, merged!

I add the point draw icon to the toolbar component in the demo code.  I can also add it to the landing-page if you like.

Thx I noticed it.
will do later :)
On Thu, Jan 2, 2020 at 4:25 PM Andy<EMAIL_ADDRESS>wrote:

I add the point draw icon to the toolbar component in the demo code. I
can also add it to the landing-page if you like.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/articodeltd/angular-cesium/issues/320?email_source=notifications&email_token=ACF5JDHZY62WQ5TF5NG2DXTQ3X2PNA5CNFSM4J4FV7NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH6OPIA#issuecomment-570222496,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACF5JDD6X3ZQ7P4YZJGPUSLQ3X2PNANCNFSM4J4FV7NA
.


Edit line 157 "Buton" to "Button"

I think this was a typo?

Learn Build status updates of commit 24f303e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/markup/extensions/grid-extensions.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Fixed Typo in README.md

Fixes

Fixes #1533
Description

Testing Instructions

Checklist

[ ] My pull request has a descriptive title (not a vague title like Update index.md).
[ ] My pull request targets the default branch of the repository (main) or a parent feature branch.
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@PrajwalBorkar thanks so much for the contribution and welcome to Openverse :slightly_smiling_face: Could you also update the text referring to the "production Storybook" based on the suggested changes in the issue? Thanks!

@PrajwalBorkar thanks so much for the contribution and welcome to Openverse 🙂 Could you also update the text referring to the "production Storybook" based on the suggested changes in the issue? Thanks!

Review if any changes required.

Once this gets another approval from one of the requested reviewers we'll get it merged quickly for you.


Expand module:create/destroy to 'run' in subfolder (Enhancement of #201)

(see #201 for original but all info is copied here for convenience)
By default ceedling expects the following project structure:

project_root

src
test
However, we are using ceedling in the following directory/project structure:

project_root

driver1

src
inc
test

driver2

src
inc
test

Instead of having separate Ceedling projects for every driver, we wanted Ceedling to manage all the tests for all drivers. That way it was also easier to generate a complete code coverage report (since Ceedling had everything built-in to do so).
This worked out-of-the-box but the slightly annoying thing was that module:create/destroy did not work properly with this project structure.
So I added a way to create a module in a subdirectory of the project_root.
By specifying <module_root>:<module_name>, the necessary files are created using <module_root> as root instead of project_root.
Applied to the project structure described above:
$> ceedling module:create[driver1:driver_code]
--> this will create the following files:

<project_root>/driver1/src/driver_code.c
<project_root>/driver1/src/driver_code.h
<project_root>/driver1/test/test_driver_code.c

The other thing was that we put our headers in a separate inc folder. So I added the MODULE_GENERATOR_INC_ROOT. If it is not specified in the .yml file (:inc_root:), Ceedling falls back to using the SRC_ROOT.
Tell me what you think and also if I missed something in the docs explaining how to do either of these two things.
As you might notice, I'm not a ruby programmer. So if this is a valuable addition to ceedling but there are better, more rubyish ways to do stuff, please let me know (and I can refactor if necessary).

Can you add tests for the new feature in spec/system/deployment_spec.rb? It will help insure that in the future this feature works as expected. There's been a few issues with this module so this will help a lot.
There are already 3 test cases for the module as seen here: https://github.com/ThrowTheSwitch/Ceedling/blob/master/spec/spec_system_helper.rb#L263
If you need help let me know and I can get you thinking in the right direction.

@dpostorivo Yes, will do. I was having some trouble understanding the test system but I was able to add a first test now with your guidance to the right file. I'll keep you updated.


Some formal fixes

Removed unused variable in IsEveryWhere
Coherent variable naming between README.md and solutions in DivideArray and DivideArrays

OK!


⚠ Bofrost.at has degraded performance

In 6b8c0f9, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1788 ms

Resolved: Bofrost.at performance has improved in b6c1736.


add License to ./pkg/common/alluxio.go

Ⅰ. Describe what this PR does
This PR is to add License to ./pkg/common/alluxio.go
Ⅱ. Does this pull request fix one issue?

fixes #XXXX
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

/lgtm


⚠ Bofrost.nl has degraded performance

In da3e800, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1332 ms

Resolved: Bofrost.nl performance has improved in 9270b4d.


fix Operation.isExecuting

@swift-ci please test

@swift-ci please test

@swift-ci please test and merge

@phausler I can't see the results of the CI run here even though we both asked to test it. Any idea what's going on?

@swift-ci please test and merge

@swift-ci please test and merge

Sometimes swift-ci ignores certain channels for some reason. This change looks solid to me.

@phausler dang, forgot to record a little change in the tests so tests will fail :. Pushing a new commit any second now

@swift-ci please test

@swift-ci please test

@phausler this now passed the checks. Didn't merge it as I made some (cosmtic) changes in the tests and wanted to give you the chance to have a look at that.


[WIP]: [Livy-336]: Replacing YARN interface with YARN REST API

What does this PR add?
Currently, Livy uses YARN's Java API to get the status of running applications or to kill applications.
This PR replaces the Java API with YARN REST API.
What needs to be done yet

Calls to yarnClient.kill should be replaced with REST API to kill YARN apps. The current REST API provided to kill apps is experimental.
If we refactor all YARN interactions to use REST API, we can drop all maven dependencies to YARN. Is this the direction we should be moving? If yes, we should decide how to put YARN configs in cong/livy.cof.

we can drop all maven dependencies to YARN

Not sure that brings a lot of gains; unless something changed, Livy uses a bunch of HDFS APIs already, so removing YARN would probably not remove a whole lot of dependencies.

Not sure that brings a lot of gains; unless something changed, Livy uses a bunch of HDFS APIs already, so removing YARN would probably not remove a whole lot of dependencies.

On top of that, if we remove all dependencies to YARN, we have to put the YARN cofings, such as resouce manager REST URL, in livy.conf. If we keep the dependencies, we can read the configs from yarn-site.xml and build the REST URL.

Codecov Report

Merging #44 into master will decrease coverage by 4.2%.
The diff coverage is 47.54%.

@@             Coverage Diff              @@
##             master      #44      +/-   ##
============================================
- Coverage     70.73%   66.52%   -4.21%
+ Complexity      788      787       -1
============================================
  Files            97       99       +2
  Lines          5388     5556     +168
  Branches        802      850      +48
============================================
- Hits           3811     3696     -115
- Misses         1037     1323     +286
+ Partials        540      537       -3

Impacted Files
Coverage Δ
Complexity Δ

...main/scala/org/apache/livy/server/LivyServer.scala
1.75% <0%> (-35.31%)
2 <0> (-8)

...rver/src/main/scala/org/apache/livy/LivyConf.scala
92.96% <100%> (-2.97%)
12 <0> (-3)

...rc/main/scala/org/apache/livy/utils/SparkApp.scala
53.12% <37.5%> (-27.65%)
1 <0> (ø)

...in/scala/org/apache/livy/utils/YarnInterface.scala
42.23% <42.23%> (ø)
20 <20> (?)

...ain/scala/org/apache/livy/utils/SparkYarnApp.scala
30.26% <59.25%> (-31.71%)
33 <22> (+4)

...cala/org/apache/livy/utils/ApplicationReport.scala
93.75% <93.75%> (ø)
1 <1> (?)

...r/src/main/scala/org/apache/livy/utils/Clock.scala
42.85% <0%> (-57.15%)
0% <0%> (ø)

core/src/main/scala/org/apache/livy/Logging.scala
54.54% <0%> (-18.19%)
0% <0%> (ø)

... and 25 more

Continue to review full report at Codecov.

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

What's the benefit of using REST API?

The main benefit is that with one call we can get all the info we need for the app, that is appId, state, finalStatus, diagnostics, trackingUrl, SparkUiUrl, etc.
With Yarn's Java API, we can get appId with one call, but to get trakingURL, SparkUiUrl, etc., we have to make extra calls. First we need to get the attemptId, then we need to get the containerId, and then we can get the remaining information.
There is one other potential benefit, which is we can drop dependencies to YARN. But, as Marcelo described, the gains from dropping YARN dependencies are minimal.
I am alright with either YARN's Java API or REST API. I just added this PR because the proposal on the mailing list recommended REST.

Thanks @ajbozarth. This was helpful feedback.

I don't have a strong preference on changing to REST APIs, except one advantage you mentioned above (get all infos in one request). I'm not sure usually how many application will we launch in one Livy server, if it is only tens or hundreds of application, I think the communication overhead should not be big.
Also avoiding yarn dependency is not a big problem, anyway we still need to depend on hadoop jars.
One difference I can think of is to visit security Hadoop, now because we change to REST API, so we should provide spnego principal/keytab, rather than Livy principal/keytab.

I don't have a strong preference on changing to REST APIs, except one advantage you mentioned above (get all infos in one request).

The main gain from this PR is LIVY-336: Livy should not spawn one thread per job to track the job on Yarn.

One difference I can think of is to visit security Hadoop, now because we change to REST API, so we should provide spnego principal/keytab, rather than Livy principal/keytab.

YARN's Cluster Applications API does not need authentication with one exception: deleting a YARN app needs authentication. But the delete API is experimental and I am not sure if it is a good idea to use it.
Since dropping the YARN dependencies has minimal benefits, it makes sense to kill YARN apps with java


Mongodb for fun

This was mostly finished in #28 but still need the k8s for it. Will close with next mr


NET::ERR_CERT_INVALID Error

Component
Version

Operating system
macos catalina 10.15.7

Node.js
v14.15.1

Chrome/Chromium/...
86.0.4240.198 stable

chrome-remote-interface
0.28.2

Is Chrome running in a container? NO
first，I execute this command:
sudo /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
second, I execute this command:
chrome-remote-interface new "https://www.bilibili.com/video/BV1c5411L7qC"
I got this error in browser tab:
Your connection is not private Attackers might be trying to steal your information from www.bilibili.com (for example, passwords, messages, or credit cards). Learn more NET::ERR_CERT_INVALID ...

It doesn't happen here. Do you get that error also if you manually navigate to that website?
Also, why sudo?

It's so strange, my localhost domain name point to <IP_ADDRESS> and [::1], some times, chrome --remote-debugging-port=9222 bind to <IP_ADDRESS>, some time bind to [::1]。i solved this by specify hostname use option -t. and if close previous opened chrome windows, no error.
sudo just is an attempt, because i cannot connect to port 9222, i'm doubt no privilege. but it's useless indeed.
thank you, this project is helpful for me!
(sorry for my poor english)

Uh, weird indeed, so can we close this?
I'm glad you can find it useful! :)
(Your english is fine!)


Support filenames with '{var}' in them

For example, we currently generate a setup.cfg snippet with:
packages =
  {package}

It would often be convenient to also generate a stub {package}/__init__.py as well.  Variable interpolation doesn't happen on the filenames currently.
For this issue, regen.py needs to be updated to apply variable_format to local_path as well.  It's currently a Path, not a str, which makes this a little more interesting, and the logic from VARIABLE_RE through the call to variable_format should be extracted out to a function that can be called multiple times.  Moving this to a class to make it easier to test is ok too!
Steps to test:

Create templates/{package}/__init__.py with some text.
cd /tmp/example
/path/to/skel/regen.py (and answer some questions, say package is "foo")
Check that /tmp/example/foo/__init__.py contains the appropriate text

would like to be assigned to this issue.


Remove support for 2.6

Perhaps it's time to say bye-bye to 2.6? There's a decent amount of stuff that would need cleaning up, especially with some of the utils, but it should be relatively straight-forward.

i'm 110% in support of this.
various things to look for:

use of dict() or otherwise in place of dictionary comprehensions
better asserts in nose.tools
set comprehensions and set literals


Use Recreate strategy for LCA Deployment and drop leader election

/cc @browsell @jc-rh

/lgtm

/approve

/override ci/prow/integration


Style/RedundantReturn throws exception on case statement

On this file:
$ cat a.rb
def bar
  case a
  when 1
  else
    'oops'
  end
end

It fails with this backtrace:
An error occurred while Style/RedundantReturn cop was inspecting /private/tmp/a.rb.
undefined method `type' for nil:NilClass
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/style/redundant_return.rb:79:in `check_branch'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/style/redundant_return.rb:102:in `check_when_node'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/style/redundant_return.rb:96:in `block in check_case_node'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/style/redundant_return.rb:96:in `each'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/style/redundant_return.rb:96:in `check_case_node'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/style/redundant_return.rb:81:in `check_branch'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/style/redundant_return.rb:75:in `on_method_def'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/mixin/on_method_def.rb:14:in `on_defs'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/commissioner.rb:41:in `block (2 levels) in on_defs'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/commissioner.rb:96:in `with_cop_error_handling'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/commissioner.rb:40:in `block in on_defs'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/commissioner.rb:39:in `each'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/commissioner.rb:39:in `on_defs'
(eval):2:in `block in on_begin'
(eval):2:in `each'
(eval):2:in `on_begin'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/commissioner.rb:45:in `on_begin'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/ast_node/traversal.rb:141:in `on_while'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/commissioner.rb:45:in `on_module'
(eval):2:in `block in on_begin'
(eval):2:in `each'
(eval):2:in `on_begin'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/commissioner.rb:45:in `on_begin'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/ast_node/traversal.rb:12:in `walk'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/commissioner.rb:58:in `investigate'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/team.rb:120:in `investigate'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/team.rb:108:in `offenses'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cop/team.rb:51:in `inspect_file'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:243:in `inspect_file'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:190:in `block in do_inspection_loop'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:222:in `block in iterate_until_no_changes'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:215:in `loop'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:215:in `iterate_until_no_changes'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:186:in `do_inspection_loop'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:101:in `block in file_offenses'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:111:in `file_offense_cache'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:99:in `file_offenses'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:90:in `process_file'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:68:in `block in each_inspected_file'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:65:in `each'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:65:in `reduce'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:65:in `each_inspected_file'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:57:in `inspect_files'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/runner.rb:36:in `run'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cli.rb:71:in `execute_runner'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/lib/rubocop/cli.rb:27:in `run'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/bin/rubocop:13:in `block in <top (required)>'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/2.2.0/benchmark.rb:303:in `realtime'
/Users/pt/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/rubocop-0.44.1/bin/rubocop:12:in `<top (required)>'
/Users/pt/.rbenv/versions/2.2/bin/rubocop:23:in `load'
/Users/pt/.rbenv/versions/2.2/bin/rubocop:23:in `<main>'
.
1 file inspected, no offenses detected

1 error occurred:
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
Mention the following information in the issue report:
0.44.1 (using Parser <IP_ADDRESS>, running on ruby 2.2.5 x86_64-darwin15)
Finished in 0.1586333679999825 seconds

Pretty sure this was fixed in #3645, as I can no longer reproduce on current master using your example. 😀

Why wasn't a point release cut for it? It is failing all over our codebase
Sent from my iPhone

On Oct 18, 2016, at 10:03 PM, Ted Johansson<EMAIL_ADDRESS>wrote:
Pretty sure this was fixed in #3645, as I can no longer reproduce on current master using your example. 😀
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

This also extends to empty if statements:
def init
  if true
  else
    puts "hi"
  end
end

0.44.1 (using Parser <IP_ADDRESS>, running on ruby 2.3.1 x86_64-darwin16)

Fixed in #3621 and released in v0.45.0.


hubble: Memory consumption increases until hubble gets unresponsive and restarts

What is the bug?
Hubble's memory consumption increases until it gets unresponsive and restarts

How can it be reproduced? (optional)
Run hubble
Additional context (optional)

The problem has subsided. It also appears to be highly correlated to the incoming gossip

still seeing it, just not as frequent

@sds haven't seen it since 2/27

although, as mentioned before - it seems correlated with incoming gossip

Ah, makes sense. I'm going to close since we believe with the recent min version we pushed out we should no longer have floods of gossip messages like we used to.
Let us know if you see otherwise!

We had this happen again earlier today. Hubble ran out of memory and restarted


[BUG] Scraper didn't scrape plenary meetings 22/09/22

Describe the bug
It seems there is again an issue with the scraper. If we go to https://parlement.thundr.be/sessions/55/session.json you will see that the last plenary meeting is id 201 with date 2022-07-20T00:00:00. Normally there should be a new one with id 202 from 22/09/22.
To Reproduce
Steps to reproduce the behavior:

Go to https://parlement.thundr.be/sessions/55/session.json
Click on meetings.plenary[0]
You will see the most recent plenary meeting that has been scraped (https://parlement.thundr.be/sessions/55/meetings/201.json)

Expected behavior
I would expect to see the most recent plenary meeting that has happened
Screenshots
/
Desktop (please complete the following information):

OS: Windows 11
Browser: Firefox
Version: 105.0

Smartphone (please complete the following information):
/
Additional context
/

https://parlement.thundr.be/sessions/55/meetings/202.json does exist however, so I believe this is Cloudflare caching which did not yet invalidate the cached version of sessions/55/session.json.
I'll check back at this later.

The cache has updated, the meeting is reachable from the sessions json now. I'll go ahead and close this issue now.

Thank you for looking at it!


Verify ref safety rules

See https://github.com/dotnet/csharpstandard/pull/795/files#r1218623949
We believe we've managed to capture all the original rules correctly. @gafter made this gist which translates the speclet terms to those used in the standard.
Changes can be found in #795
The edits made incorporating those rules are as follows:

Re-order local and parameter rules.
Change title of "method invocation" to "function invocation" because the same rules would apply to local function declarations.
"Rvalue" changes to "Value" for consistency with the standard's existing terms.
"Span constructor" and "default" rules move to structs.md, in the section of "safe context" for ref struct types.

I did a quick scan, and none of the rules were removed, or had other semantic edits.

Ping @jskeet
I captured this discussion so I could resolve those conversations and merge the PR.

Thanks - I'll try get to this tomorrow or Friday.

For the open issue bit: the standard is tighter than the compiler. 16.2.3 states that ref struct can't be used in async methods at all.

It looks like we're actually okay for safe-context for operators. So #816 should close this.


iOS - handler is not a function. (In 'handler(rtn)', 'handler' is undefined)

I get this issue running on both iOS Simulator and on iPhone 6. This occurs immediately once the call starts ringing. This error is dismissible, and does not cause the app to crash. I am adding all of the necessary event listeners to the TwilioVoice Instance.
This error is originating from line 88 in index.js
Thanks in advance!

@hoxfon @jrperson Have either of you experienced this issue? Thanks!

@nkarman is there any chance that you are passing to the listener an undefined reference?
In my JS app I have something like this:
 //...
       TwilioVoice.addEventListener('deviceReady', _deviceReady)
        if (Platform.OS !== 'ios') {
            TwilioVoice.addEventListener('deviceNotReady', _deviceNotReady)
        }
 //...
        if (Platform.OS !== 'ios') {
            TwilioVoice.addEventListener('deviceDidReceiveIncoming', _deviceDidReceiveIncoming)
        }
        if (Platform.OS === 'ios') {
            TwilioVoice.addEventListener('callRejected', _deviceCallRejected)
        }
        TwilioVoice.addEventListener('connectionDidConnect', _connectionDidConnect)
        TwilioVoice.addEventListener('connectionDidDisconnect', _connectionDidDisconnect)

let me know if that helps

@fabriziomoscon I have something very similar. Do you think you could possibly provide an example of where the listeners are defined? such as _deviceReady or _connectionDidConnect? In my code, I have them defined as such
  _connectionDidConnect (args) {
    console.tron.log('connectionDidConnect', args)
  }

  _connectionDidDisconnectHandler (error) {
    console.log('connectionDidDisconnectHandler', error)
  }

I am also getting this issue.

Please paste your file, there is really nothing special in my _ handlers

Hey @fabriziomoscon, thanks for replying. I actually figured it out shortly after posting, should of deleted it. Thank you very much for writing this module!

My pleasure, maybe you could post your solution anyway for others.


port staggered layout.

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Avaloniaui.net with user documentation

Breaking changes

Fixed issues

closed due to inactivity

Even though I think I need StaggeredPanel rather than StaggeredLayout, it's too bad this was closed because it could've been useful. I'll probably have to port StaggeredPanel myself unless someone else already did it.


Fix get_column_width returning None

Coverage remained the same at 49.589% when pulling b0a2aad8af1cb3419676d5e58b6a208bcc2c0ca4 on jlalleve:master into 4eb8a65a7f345fb447ba7d6902be86ecb5413e1e on swistakm:master.

Thanks for contribution!

Released as 1.3.0:

release notes
available distributions


Request for an official Dockerfile

I should be very effective (for diffusion) if this project can be easily started in a docker.

Docker file and container added with commit d65c321 / release v0.12.3 should solve issue #17 .


uninstall of vcredist redistributables

I have some concerns in regards with uninstalling of redistributables like vcredist2015 etc. Consider the following situation:

the vcredist redistributable was installed as part of another application the user installed without choco.
user installs a choco package X which has a dependency on vcredist
choco decides to install vcredist. In reality the vcredist installation is skipped because it is already installed. vcredist has no reference count (http://stackoverflow.com/questions/18603313/how-to-avoid-uninstalling-previously-installed-exepackage-redistributables-whi)
users decides to uninstall package X. Assuming there are no other packages which depend on vcredist, the choco reference count of the dependency (vcredist) reaches 0 and vcredist will be uninstalled.
All applications depending on vcredist will fail to start

My recommendation is to mark the vcredist package as permanent, meaning it will never be uninstalled. If there is currently no such flag, no uninstall method should be included in the nuspec.

@matbech by derfault, uninstalling packages will leave the dependent packages in place.  You would need to pass the -x parameter in order to force the uninstallation of the dependencies.  See choco uninstall /? for more information.
Does that help with your concern?

Yes in that case the problem doesn't happen. I did assume that the dependencies were ref counted.

Cool, so sounds like we are ok :smile:


Add component for generate event attributes and event batching

Add component for generating event attributes and event batching for event generator test framework. This is part of 3+DC

Moved to #2280 due to commit disorder


I want you to describe the correct copyright to UIIimage+GIF.h and UIImage+GIF.m

Hi:
Since the copyright that has been described in these file is in the unknown, I want you to describe the correct copyright
https://github.com/larcus94/LBGIFImage/blob/master/LBGIFImage/UIImage%2BGIF.h#L6
https://github.com/larcus94/LBGIFImage/blob/master/LBGIFImage/UIImage%2BGIF.m#L6
Although this code is what is used in SDWebImage
https://github.com/rs/SDWebImage/blob/3.7.5/SDWebImage/UIImage%2BGIF.h#L6
https://github.com/rs/SDWebImage/blob/3.7.5/SDWebImage/UIImage%2BGIF.m#L6
because the Copyright has become unclear, I think that dangerous as a license.
If described the copyright in this code, we wanted to also fixes SDWebImage side.
thank you.

I fixed this in the latest commit. Check it out and let me know if that is sufficient.

Thank you!!  I think I try to convey to SDWebImage side.


[request] Create new doc from alfred

Would be cool

that is a great feature. I will work on that.

just added to latest version. create a doc by typing in "d > create google doc." please try it out and let me know what you think.

Where do I download it? There is no workflow file in the repo

https://github.com/azai91/alfred-drive-workflow/releases/tag/v1.2

Great work, @azai91. Creating new doc is nice. It would be great if we could do something like "d n s [name]" to create a new google sheet. [d to initiate, n to new, s to sheets, and [name to file name]


Source parameter returns InputError

Description
The docs here https://api.creativecommons.engineering/v1/#operation/image_search list 'source' as a parameter name which was working a couple weeks ago. It seems this parameter was recently renamed to 'sources' but the docs aren't updated. I'm not sure whether this is a purposeful change or a bug?
Reproduction

Try to hit URL using 'source' parameter listed in docs:
http://api.creativecommons.engineering/v1/images?q=cat&license_type=all-cc&page=1&page_size=50&source=woc_tech,wikimedia,thorvaldsensmuseum,svgsilh,statensmuseum,spacex,smithsonian_postal_museum,smithsonian_portrait_gallery,smithsonian_national_museum_of_natural_history,smithsonian_libraries,smithsonian_hirshhorn_museum,smithsonian_gardens,smithsonian_freer_gallery_of_art,smithsonian_cooper_hewitt_museum,smithsonian_anacostia_museum,smithsonian_american_indian_museum,smithsonian_american_history_museum,smithsonian_american_art_museum,smithsonian_air_and_space_museum,smithsonian_african_art_museum,smithsonian_african_american_history_museum,sciencemuseum,rijksmuseum,rawpixel,phylopic,nypl,nasa,museumvictoria,museumsvictoria,met,mccordmuseum,iha,geographorguk,floraon,flickr,europeana,eol,digitaltmuseum,clevelandmuseum,brooklynmuseum,bio_diversity,behance,animaldiversity,WoRMS,CAPL,500px&extension=jpg,jpeg,png
When looking in browser this returns a 400 error regarding invalid input for the 'source' field.
Next, try opening URL which uses 'sources' as the parameter and the results seem to be returned fine:
http://api.creativecommons.engineering/v1/images?q=cat&license_type=all-cc&page=1&page_size=50&sources=woc_tech,wikimedia,thorvaldsensmuseum,svgsilh,statensmuseum,spacex,smithsonian_postal_museum,smithsonian_portrait_gallery,smithsonian_national_museum_of_natural_history,smithsonian_libraries,smithsonian_hirshhorn_museum,smithsonian_gardens,smithsonian_freer_gallery_of_art,smithsonian_cooper_hewitt_museum,smithsonian_anacostia_museum,smithsonian_american_indian_museum,smithsonian_american_history_museum,smithsonian_american_art_museum,smithsonian_air_and_space_museum,smithsonian_african_art_museum,smithsonian_african_american_history_museum,sciencemuseum,rijksmuseum,rawpixel,phylopic,nypl,nasa,museumvictoria,museumsvictoria,met,mccordmuseum,iha,geographorguk,floraon,flickr,europeana,eol,digitaltmuseum,clevelandmuseum,brooklynmuseum,bio_diversity,behance,animaldiversity,WoRMS,CAPL,500px&extension=jpg,jpeg,png

Expectation
No errors & clarification on which is the correct parameter name and updated documentation if necessary.
Environment

Device: Desktop PC
OS: Windows 10
Browser: Chrome
Version: 85.0.4183.83

Resolution

[ ] I would be interested in resolving this bug.

I did some git spelunking, I don't think we ever accepted sources as a parameter (maybe you can dig up a commit that proves me wrong). The reason your second query works is because sources isn't a valid parameter and thus does not actually narrow down the search any further / get validated like source would.
Most likely, one of the sources that you hardcode in your list has been removed or has a typo. Unfortunately the current error message for this parameter makes it difficult to figure out which one; v1.8.1 will fix this (see https://github.com/creativecommons/cccatalog-api/pull/614). I'll check in here once that's in production.

Ok, now we have some better error messages in place, and the root issue is apparent:
HTTP 400 Bad Request
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "error": "InputError",
    "detail": "Invalid input given for fields. 'source' -> Source 'museumvictoria' does not exist.",
    "fields": [
        "source"
    ]
}

It looks like you have both museumvictoria and museumsvictoria in your query. Only the latter is valid.

@aldenstpage Thanks for the info, was 'museumvictoria' recently removed? That source was included at the time we were testing a week or so ago and all was working well. I'm a bit concerned that changes to the source list would break any older queries that might have listed those sources?
I'm fine with updating our code to match this change but I feel it would be nice if the API could disregard any invalid sources that might be listed or were listed previously. That way if only one source is invalid like in this case it could still return results for all the others. Mostly I'd just like to avoid having to deploy hotfixes to patch the query whenever the source list changes, should I log this as a feature request?

museumvictoria was never a real source; the correct code is museumsvictoria. It looks like it was included in the list of valid sources as a fat finger typo, which someone fixed.
I agree that there isn't really a need to be so strict with source validation, especially since the list of sources can change arbitrarily. We'll remove that requirement in the near term. https://github.com/creativecommons/cccatalog-api/issues/615

@aldenstpage Ah, yeah I was curious about that one but didn't really question it. Thanks for the quick responses and quick resolution, I look forward to seeing #615 soon!


Replace our use of main with directories config

Used to "Tell people where the bulk of your library is. Nothing special is done with the lib folder in any way, but it's useful meta info."
https://docs.npmjs.com/files/package.json#directorieslib
This signifies the location of our public API and removes the implication that our index.js file has the entire API.
cf #728
cf https://github.com/jupyter/jupyterlab/issues/224#issuecomment-241551346
cf https://github.com/phosphorjs/phosphor/pull/136

Thanks!


[cloud_functions] Support the v2 Android embedder plugins API

@amirh
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/1188. Any further collaboration will be done there.

To avoid confusing with project https://github.com/flutter/flutter/projects/59 this issue will remain open here till resolved.


[Bug] Request exited with code 422

Godot Version & Plugin Version
Godot: 3.4.4
Plugin: 0.9.0
Describe the bug
Trying to Commit and Push my entire Res folder. Spinner just continues spinning and have to close and reopen godot to try again. Have tried twice. However when I just try and commit one folder it works.
gitignore:
.import/
export.cfg
export_presets.cfg
addons/
export/
blobbed each file with success, start committing...
REQUEST TO API : Request exited with code 422
[GitHub integration] >> could not process the new tree, the file may be corrupted or already present in the repository without any changes.
REQUEST TO API : Request exited with code 422
[GitHub integration] >> could not process the new commit, tree may be invalid.
REQUEST TO API : Request exited with code 422
Screenshots

I have the exact same issue. It does work when i commit certain folders but when i commit the entire project it freezes.


[SBT-BASE-01] - consolidate logging into one dependency

resolved with https://github.com/reynoldsm88/sbt-base/commit/af061a0d0d1d6c1b2e2f669a240b720c8273141e


Minor updates to pngrutil.c instances

I have gone through and added some updates that were made in libpng's recent updates (starting in commit 347538efbdc21b8df684ebd92d37400b3ce85d55). These are minor changes that should provide capability for a user limit on the size of chunks of png files read.

Hello!
Thank you for your contribution, however, this is an university project and did not accept contributions outside us 8 original developers, nor I think we should now, as one subject requires us to re-use an old game (this included) untouched as we released them.

That's no problem, thank you for letting me know! I was also completing this as part of a university class, so I just needed to submit a pull request for credit.

This has been resolved in #114 by using latest commit of the v0-8.


Controller Input Issues

It looks like this mod somehow breaks controller inputs in an odd way, but it is circumventable. The issue also disappears when removing the mod.
When launching the game through steam with a Playstation 5 controller in big picture mode, Ultimate Chicken Horse fails to recognize the input (doesn't work for anything) when launched. This only happens if you don't have "Playstation controller support" ticked in Big Picture Mode's controller settings.
This also happens with the Xbox 360 controller, if you don't have "Xbox controller support" ticked in big picture mode's setting.
The vanilla game recognizes these inputs fine even if you don't have the controller option ticked in Steam's big picture mode settings.  Not sure about Switch Pro controllers, as one of our players was using one, but we didn't check her Steam controller settings.

Thanks for figuring out the issues and possible solutions.
The mod needs to change the mode of the library used to get more than 4 controllers to work locally.
(InputManager.EnableNativeInput is forced to always be true.)
That is the most likely explanation for the changes you encountered.
I don't think I can fix the issues directly and the best solution is to document the need to use Xbox controller support and Playstation controller support in Big Picture Mode at some place (maybe Readme or a Wiki entry).
I will try to find a few more people to verify the settings.
An alternative would be to make a config file option to disable the EnableNativeInput mod, but that would limit local players to 5 (4 controllers + 1 keyboard).

Created a wiki page to help with controller issues:
https://github.com/batram/UCH-EvenMorePlayers/wiki/Controller-Input-Issues


Tracking GlobalAllocator

As described in https://rust-analyzer.github.io/blog/2020/12/04/measuring-memory-usage-in-rust.html, memory profiling long-runing applications in Rust is hard, because it's impossible to pause the program and "pares the heap" -- inspect all the currently allocated blocks and their owners.
I think it's possible to recover heap parseability by writting a special global allocator. Specifically, this allocator will maintain an intrusive doubly linked list of currently allocated heap blocks, and will provide an API to iterate the blocks. Internally, it'll just wrap some other allocator, and will over-allocate each requested block to stuff meta with pointers at the start of the block.
Additionally, the allocator will maintain a therad-local stack of active "heap tags", and it will tag each block with the topmost tag. Having tags will allow the user to classify the allocated blocks.
Draft API
pub struct TrackAlloc<A: GlobalAllocator> {
    a: A
    first_allocated_block: Option<*const ()>
}

impl<A: GlobalAllocator> GlobalAllocator for TrackAlloc<A> { }

therad_local! {
    static tags: RefCell<Vec<AllocTag>> = default()
}

pub struct AllocTag(pub NonZeroUsize);

impl AllocTag {
    pub fn push(self) -> impl Drop { ... }
}

pub struct MemoryBlock { ... }

impl MemoryBlock {
    pub fn for_each_allocated(f: impl FnMut(&MemoryBlock)) {}
    pub fn size(&self) -> usize {}
    pub fn tag(&self) -> Option<AllocTag> {}
}

The user (rust-analyzer) will then do something like this:
pub fn item_tree_query(file_id: FileId) -> Arc<ItemTree> {
    let _a = AllocTag("ItemTree" as *const as NonZeroUsize).push();
     // allocate stuff
}

pub fn pares_query(file_id: FileId) -> ParesTree {
    let _a = AllocTag("ParseTree" as *const as NonZeroUsize).push();
     // allocate stuff
}

That is, the user can answer questions like "how much memory is occupied by all ItemTrees" and "how much memory is occupied by all parse ItemTrees"

Note that we do not shoot for zero overhead here -- maintaining linked list requires extra time and space. The idea is that one would use this allocator only when investigating a specific perf problem.
That being said, the following are nice to have:

minimize slow-down and memory overhead (can we use a xor-list here?)
make it possible to run this "in production", by adding some kind of env-variable or some such to toggle the tracking on and off

Minimizing the tag overhead could be done by using a separate chunk of memory for each tag I think. If it is fine to round all allocation sizes to the nearest size class of the inner allocator (which would also account for the overhead of the inner allocator due to internal fragmentation) then I don't think any memory overhead is necessary. Just a way to query the data structures used by the inner allocator, which could be done by forking an existing rust allocator.

If I understand this issue right, the only reason to tag every allocation with some extra metadata, is to be able to know the category / tag of memory this is on deallocation. The whole purpose of this is to have memory stats per tag.
Rather than allocating extra memory, and storing the tag inline, why not store the tag as a part of the heap pointers?
Usually devs run 64bit systems like x86_64, where we have massive 48bit virtual address spaces. That would give us two ways to store the tag information in the pointer:

Build / modify a allocator, to use several distinct memory mappings in the virtual address space, each containing its own heap. Each tag would essentially only claim memory from a very specific section of the virtual address space. Pointers can be quickly recognized in dealloc. Massive virtual address spaces, and mmap with MAP_ANONYMOUS, MAP_PRIVATE give us the necessary API to control the address space, at least in linux.

Just use the few bits in pointers, which are not touched by address translation, e.g. I think 16 bits on x86_64. This would then be somewhat architecture specific but simpler. I have no idea, if this can cause undefined behavior. Should be fine, since the tagging would be done inside the GlobalAlloc implementation.

I think both of these methods would keep the performance / behavior of the code closer to uninstrumented use case.

Performance of method 2 would probably be better. Method 1 will probably trash the TLB more than usual code (because more pagetables are needed).

Genius!

Update: method 2 will probably not work for some things. If e.g. a buffer with a tag is passed to the kernel in a syscall, the pointer is also checked by the kernel, which means it will become impossible to use the tags for anything talking to the kernel.
I liked method 1 better anyway ^^

Seems like jemalloc already uses arenas internally, to improve heavily multi threaded code. Might be possible to manually create them, and control their place in the address space. I think I will experiment with this for a little, and maybe try to integrate something in ra, if it works out.

Just use the few bits in pointers, which are not touched by address translation, e.g. I think 16 bits on x86_64. This would then be somewhat architecture specific but simpler. I have no idea, if this can cause undefined behavior. Should be fine, since the tagging would be done inside the GlobalAlloc implementation.

x86_64 requires that pointers are canonicalized using sign extension. If you try to use a pointer with the upper 16 bits changed you are guaranteed to get a page fault.

Build / modify a allocator, to use several distinct memory mappings in the virtual address space, each containing its own heap. Each tag would essentially only claim memory from a very specific section of the virtual address space. Pointers can be quickly recognized in dealloc. Massive virtual address spaces, and mmap with MAP_ANONYMOUS, MAP_PRIVATE give us the necessary API to control the address space, at least in linux.

This option would work though, but only on 64bit systems. 32bit systems only have 2GB worth of allocatable address space.

@bjorn3 thanks! Did not know that about x86_64. That is probably also the reason, why linux uses only very limited pointer tagging in the kernel itself.


Duplicate constraints sometimes ignored

Hello,
Runnable repro: https://github.com/tgolsson/pants-repros/tree/main/sentry-lost-constraint
As the readme there says, Pants 2.15.0 + Pex v2.1.129 is randomly failing to lock correctly. Sentry has the following constraints for urllib3:
        [
            "urllib3<2.0.0",
            "urllib3>=1.25.7; python_version <= \"3.4\"",
            "urllib3>=1.26.11; python_version >= \"3.6\"",
            "urllib3>=1.26.9; python_version == \"3.5\""
        ]

But the lockfile will (randomly) resolve with the below for urllib3. Note that the locked version is 2.0.2. The other version it will find is 1.26.15, which is permissible with all constraints. I've not tested extensively but it seems to be 50/50 which one it ends up locking, with no huge bias to either one. I didn't see anything in the changelog from the few latest releases that would affect this.
          "artifacts": [
            {
              "algorithm": "sha256",
              "hash": "d055c2f9d38dc53c808f6fdc8eab7360b6fdbbde02340ed25cfbcd817c62469e",
              "url": "https://files.pythonhosted.org/packages/4b/1d/f8383ef593114755429c307449e7717b87044b3bcd5f7860b89b1f759e34/urllib3-2.0.2-py3-none-any.whl"
            },
            {
              "algorithm": "sha256",
              "hash": "61717a1095d7e155cdb737ac7bb2f4324a858a1e2e6466f6d03ff630ca68d3cc",
              "url": "https://files.pythonhosted.org/packages/fb/c0/1abba1a1233b81cf2e36f56e05194f5e8a0cec8c03c244cab56cc9dfb5bd/urllib3-2.0.2.tar.gz"
            }
          ],

That is an absolutely bizarre set of requirements. I'm surprised Pip doesn't just die with a dup requirement error. It should just be 3 requirements, each with the existing marker but also the upper bound from the current 1st requirement.
I'll take a look later today or tomorrow.

Fully in agreement. :P

For what it's worth, I cannot repro this without pants, though I'm definitely not doing a 1-1 repro given my unfamiliarity with Pants/Pex invocation styles... Raw pip seems to work fine (consistently picks 1.26), and raw pex seems to complain about duplicate dependencies. PDM and poetry also pick 1.26... Not sure what's going on.

Apples to apples this works fine.
$ pex3 lock create --style universal --resolver-version pip-2020-resolver --pip-version latest --interpreter-constraint "==3.9.*" --target-system linux --target-system mac --indent 2 -o lock.json sentry-sdk==1.22.2

The apples here is Pip. Pants defaults to Pex default which is 20.3.4 which picks urllib3 2.0.2. Using --pip-version latest (which is currently 23.1.2), picks urllib3 1.26.15.

@tgolsson I'm going to close this as answered. Pants supports setting --pip-version in 2.16.x+:

https://www.pantsbuild.org/v2.16/docs/reference-python#pip_version
https://www.pantsbuild.org/v2.17/docs/reference-python#pip_version

The 23.0.1 supported by 2.16.x appears to be enough to get the expected result of urllib3 1.26.15.
Let me know if you have further questions.

Ah dang it. I downgraded to 20.0 but couldn't repro there either, maybe bad luck. Hopefully 2.16 is out soon then! :-) Thank you.


[BUG] Problems with colors with subprocess, PIPE, and legacy_windows

Colors are not displayed as expected when running through subprocess.popen with stdout redirected to subprocess.PIPE on Windows.
Repro Steps
In this example, the code is running with_colors.py via

os.system [Works]
subprocess.popen [Works]
subprocess.popen with subprocess.PIPE [Doesn't Work]
subprocess.popen with subprocess.PIPE with FORCE_COLORS [Doesn't Work]

Attempt number 3 seems like something wonky that subprocess.popen is doing when redirecting to subprocess.PIPE and probably outside the scope of rich. However, I expected number 4 to work around the issue with subprocess.popen but setting the FORCE_COLOR environment variable didn't seem to help.
When I dug into the rich code, I saw that FORCE_COLOR is being ignored because legacy_windows is set to True in the scenario with subprocess.PIPE. When I added the patch below to console.py in __init__.py, all scenarios worked as expected.
Will a change like this break other exotic scenarios? If it seems safe, I can put together a PR.
Thank you!
with_colors.py
from rich import print

print("[red]This is red![/]")

run_with_colors.py
import copy
import os
import subprocess

# ==== 1) Works ====
print("Via `os.system`:")
os.system("python with_colors.py")

# ==== 2) Works ====
print("\nVia `subprocess.run` (no pipe):")
subprocess.run("python with_colors.py")

# ==== 3) Doesn't Work ====
print("\nVia `subprocess.run` PIPE:")
result = subprocess.run(
    "python with_colors.py",
    stdout=subprocess.PIPE,
)

print(result.stdout.decode("utf-8"))

# ==== 4) Attempted work around (Doesn't work) ====
print("\nVia `subprocess.run` PIPE (Attempted workaround):")

env = copy.deepcopy(os.environ)

env["FORCE_COLOR"] = "1"

result = subprocess.run(
    "python with_colors.py",
    stdout=subprocess.PIPE,
    env=env,
)

print(result.stdout.decode("utf-8"))

Potential Patch
diff --git a/rich/console.py b/rich/console.py
index 3653721..30f8092 100644
--- a/rich/console.py
+++ b/rich/console.py
@@ -687,11 +687,6 @@ class Console:
         self._emoji = emoji
         self._emoji_variant: Optional[EmojiVariant] = emoji_variant
         self._highlight = highlight
-        self.legacy_windows: bool = (
-            (detect_legacy_windows() and not self.is_jupyter)
-            if legacy_windows is None
-            else legacy_windows
-        )

         if width is None:
             columns = self._environ.get("COLUMNS")
@@ -717,6 +712,12 @@ class Console:
             if force_color is not None:
                 self._force_terminal = True

+        self.legacy_windows: bool = (
+            (detect_legacy_windows() and not self.is_jupyter and not self._force_terminal)
+            if legacy_windows is None
+            else legacy_windows
+        )
+
         self._file = file
         self.quiet = quiet
         self.stderr = stderr

I'm not sure that is the fix. Although it will be something along those lines.
I suspect that legacy_windows should not apply, if we're not writing to a console.


UI not accessible with path-based ingress

Using a path based ingress is possible, but the OpenCost UI itself does not load as it ignores the path defined within the ingress:
values.yaml
opencost:
  ui:
    ingress:
      enabled: true
      hosts:
        - host: test.intern.ch
          paths:
            - /opencost
      tls:
        - hosts:
            - test.intern.ch

The page is served at test.intern.ch/opencost but it serves an empty page as the index.js and other resources result in 404 as it is trying to load from test.intern.ch/index.js which is not a valid path.
Maybe this could be solved by providing the BASE_URL_OVERRIDE environment variable to the ui container. But I'm not quite sure. See the opencost/ui Github page for reference. The current deployment.yaml does not allow to add additional env-values. This could be solved by adding the following block to the opencost-ui container in the deployment.yaml:
{{- with .Values.opencost.ui.extraEnv }}
env:
{{- toYaml . | nindent 10 }}
{{- end }}

Merged https://github.com/opencost/opencost-helm-chart/pull/149


Dense Runestone - Highlight not working

Ever since the highlight altars was added, the dense runestones when runecrafting bloods stop working when you walk away and come back. In order to fix, you have to disable and re-enable the plugin but it does the same thing when you walk away again.

I'm aware haven't had time to take a look at it, I'll fix it on the 17th when I'm home from vacation.
I didn't test it thoroughly whoops.

Fixed.


glscopeclient: Check WIXPATH before creating MSI installer

The CI build failed. Do you need to install additional software in the CI environment perhaps? (see the .github directory for the scripts)

Done. @umarcor

One litte question. Why does the CI compile the program twice?

One litte question. Why does the CI compile the program twice?

It should build once for Linux and once for Windows. If there's multiple builds, then we've got a bug in the scripts.

@azonenberg, on Windows it is built twice:

https://github.com/azonenberg/scopehal-apps/blob/master/.github/workflows/build.yml#L146-L149 generates an MSYS2 package (a .zst tarball).
https://github.com/azonenberg/scopehal-apps/blob/master/.github/workflows/build.yml#L162-L171 generates a portable zipfile with an installer.

I guess @Biswa96 is asking why don't we extract the .zst for generating the zipfile, instead of creating it from scratch. I guess the answer is that we want to keep the portable zipfile build procedure standalone, so contributos can ignore the PKGBUILD recipe if they want.

As you are distributing the ZIP file to users, why not skip the msys2 package build or PKGBUILD entirely?

The MSYS2/PKGBUILD build is executed for Continuous Integration/Testing purposes. That provides "nightly" artifacts for contributors to test enhancements/PRs, before the package is bumped in MSYS2 repositories.

OK, all doubt cleared 😌


Use Path::GetTempFileName() instead of creating random filename

The [random]::new() is not supported and causing failure in PS4 (like in Windows Server 2012)

@arunkm,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

This is not good. Path.GetTempFileName can only create 65k files in the temp directory and then fails. It's better to use GUID.


Refactor board_database and find_mpy_root functions to accept Path objects

While chasing down the missing mpy_path assignment I was utterly confused by the mismatch between the actual types and the type annotations.
this is my take on it which are mostly updates to the annotations,
but also includes some casts and changes of defaults to better match the type.
This commit refactors the board_database and find_mpy_root functions to accept Path objects instead of strings for the mpy_dir parameter. This change improves the code's readability and makes it more consistent with the use of Path objects throughout the project.

Looks good, testing seemed perfectly fine. Tidies up some sloppy code I'd introduced! Thanks. :)


[DO NOT MERGE] fix: releasing 1.15.2-grpc on top of 1.15.2 with legacy grpc dependency

We'll use it to workaround https://github.com/googleapis/nodejs-dlp/issues/445 by using legacy grpc.

Please ignore the lint failure, it's something with eslint on samples/ folder that I'm not gonna fix here in this branch at all.

@feywind I will hold it for now, I'll be ready to push it to npm if really needed, but seems like we have other solutions here (fix grpc-js, rollback the backend change).


Not Found Error in Model D Checkpoint (710K)

I get this error when trying to run eval_ckpt_file.py:
NotFoundError (see above for traceback): Key resnet_v1_50/block1/unit_1/bottleneck_v1/shortcut_bn/BatchNorm/beta not found in checkpoint
	 [[Node: save/RestoreV2 = RestoreV2[dtypes=[DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, ..., DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT], _device="/job:localhost/replica:0/task:0/device:CPU:0"](_arg_save/Const_0_0, save/RestoreV2/tensor_names, save/RestoreV2/shape_and_slices)]]
	 [[Node: save/RestoreV2/_79 = _Recv[client_terminated=false, recv_device="/job:localhost/replica:0/task:0/device:GPU:0", send_device="/job:localhost/replica:0/task:0/device:CPU:0", send_device_incarnation=1, tensor_name="edge_84_save/RestoreV2", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:GPU:0"]()]]

Is here anyone could solve this problem?
I met a similar Error, resnet_v1_50/block1/unit_1/bottleneck_v1/conv1/kernel not found in checkpoint

I met a similar Error

Change your Tensorflow and Tensorlayer version to satisfied the requirements of this project, that error would disappear.

@david-di
I use Tensorflow1.6 and Tensorlayer 1.7 version,still got this error
Could you show me your version list?

I had the similar error with model A (Tensorflow 1.4 and Tensorlayer 1.7). The error disappeared when I switched to model C. I haven't figured out why though.

@Neltherion have you solved this problem

@zijing-wu  Could you share the model A, B and C (through Google Drive)? I can't download them from Baidu because I don't know to use Baidu and it's quite complex.


copy change

https://healthsites.io/#lifecycle
change 'Healthsites data lifecycle' to 'Envisioned Healthsites data lifecycle'

our lifecycle already changed


[QUESTION] Avoid embedding image assets in bundle

@peter-jozsa, this issue really is not directly related to this library so feel free to close this but I wanted to know how can one avoid the assets being merged into the bundle?
I would like to decrease the bundle size by decoupling the static images from the bundle. Can you help me please.
Please refer https://github.com/oblador/react-native-vector-icons/issues/980 for my configs

Hey there,
The problem is that you are using url-loader to process images in your webpack build:
// This is needed for webpack to import static images in JavaScript files.
const imageLoaderConfiguration = {
  test: /\.(gif|jpe?g|png|svg)$/,
  use: {
    loader: 'url-loader',
    options: {
      name: '[name].[ext]'
    }
  }
};

In your case url-loader will always put files matching /\.(gif|jpe?g|png|svg)$/ into your bundle as a dataURI. You can set the maximum file size for url-loader with the limit option (More info here: https://github.com/webpack-contrib/url-loader#limit)
I suggest you not to use url-loader to bundle images, use file-loader instead: https://github.com/webpack-contrib/file-loader#getting-started
I hope I could help. Have a nice day!

@peter-jozsa, thanks for the quick revert. Really appreciate your help. I think that makes sense. Thank you again for pointing that out


Move scripts and docker out of source folder

We should reserve the runhouse/ folder for package source code, moving auxiliary files like scripts and docker out into the root branch.

Current dependencies on/for this PR:

main

PR #360   👈

This stack of pull requests is managed by Graphite.


Add support for getline < "-" to read from stdin

gawk, mawk and the "one true awk" have support for this, and it seems reasonable considering that POSIX requires interpretation of - as stdin in basically all other areas.
Only issue is that read prompts in general are a bit awkward with #47. For example:
$ goawk 'BEGIN { ARGV[ARGC++] = "-"; print "Enter input:"; getline; print "You entered: " $0 }'
this is my input
Enter input:
You entered: this is my input

Thanks for this. Merged in https://github.com/benhoyt/goawk/commit/0eb3f8c8b7889fe1feff86aed767dcdb30cbc98e.
Point about prompts noted -- I intended to fix that at some point, and even had a half-working branch, but didn't get to it. Another time...


Failed building wheel for rcssmin

Failed building wheel for hiredis
Running setup.py clean for hiredis
Running setup.py bdist_wheel for rcssmin ... error
Complete output from command /home/c013ra/Desktop/django-shop/myenv/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-install-24x5vmdv/rcssmin/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" bdist_wheel -d /tmp/pip-wheel-ip9ie3jm --python-tag cp35:
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.5
copying ./rcssmin.py -> build/lib.linux-x86_64-3.5
running build_ext
building '_rcssmin' extension
creating build/temp.linux-x86_64-3.5
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DEXT_MODULE=_rcssmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.5m -I/home/c013ra/Desktop/django-shop/myenv/include/python3.5m -c rcssmin.c -o build/temp.linux-x86_64-3.5/rcssmin.o
In file included from rcssmin.c:18:0:
_setup/include/cext.h:34:20: fatal error: Python.h: No such file or directory
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

Failed building wheel for rcssmin
Running setup.py clean for rcssmin
Running setup.py bdist_wheel for rjsmin ... error
Complete output from command /home/c013ra/Desktop/django-shop/myenv/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-install-24x5vmdv/rjsmin/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" bdist_wheel -d /tmp/pip-wheel-fe4qkzhn --python-tag cp35:
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.5
copying ./rjsmin.py -> build/lib.linux-x86_64-3.5
running build_ext
building '_rjsmin' extension
creating build/temp.linux-x86_64-3.5
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DEXT_MODULE=_rjsmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.5m -I/home/c013ra/Desktop/django-shop/myenv/include/python3.5m -c rjsmin.c -o build/temp.linux-x86_64-3.5/rjsmin.o
In file included from rjsmin.c:18:0:
_setup/include/cext.h:34:20: fatal error: Python.h: No such file or directory
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

Failed building wheel for rjsmin
Running setup.py clean for rjsmin
Failed to build hiredis rcssmin rjsmin
django-filer 1.3.0 has requirement easy-thumbnails<2.5,>=2, but you'll have easy-thumbnails 2.5 which is incompatible.
django-haystack 2.5.0 has requirement Django<1.10, but you'll have django 1.10 which is incompatible.
django-allauth 0.35.0 has requirement Django>=1.11, but you'll have django 1.10 which is incompatible.
Installing collected packages: rcssmin, rjsmin, django-compressor, Unidecode, django-polymorphic, olefile, Pillow, easy-thumbnails, django-mptt, django-filer, django-filter, django-fsm, django-fsm-admin, django-haystack, django-ipware, django-parler, jsonfield, django-post-office, redis, django-redis-cache, django-redis-sessions, djangorestframework, six, django-rest-auth, django-sass-processor, djangocms-bootstrap3, html5lib, djangocms-text-ckeditor, djangocms-cascade, python-dateutil, drf-haystack, elasticsearch, hiredis, libsass, python-openid, pytz, virtualenv, wheel, beautifulsoup4, bs4
Running setup.py install for rcssmin ... error
Complete output from command /home/c013ra/Desktop/django-shop/myenv/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-install-24x5vmdv/rcssmin/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-record-y8abyajq/install-record.txt --single-version-externally-managed --compile --install-headers /home/c013ra/Desktop/django-shop/myenv/include/site/python3.5/rcssmin:
running install
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.5
copying ./rcssmin.py -> build/lib.linux-x86_64-3.5
running build_ext
building '_rcssmin' extension
creating build/temp.linux-x86_64-3.5
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DEXT_MODULE=_rcssmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.5m -I/home/c013ra/Desktop/django-shop/myenv/include/python3.5m -c rcssmin.c -o build/temp.linux-x86_64-3.5/rcssmin.o
In file included from rcssmin.c:18:0:
_setup/include/cext.h:34:20: fatal error: Python.h: No such file or directory
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
----------------------------------------

Command "/home/c013ra/Desktop/django-shop/myenv/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-install-24x5vmdv/rcssmin/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-record-y8abyajq/install-record.txt --single-version-externally-managed --compile --install-headers /home/c013ra/Desktop/django-shop/myenv/include/site/python3.5/rcssmin" failed with error code 1 in /tmp/pip-install-24x5vmdv/rcssmin/

i do not know if it helps but it looks like this issue https://github.com/overshard/timestrap/issues/15

@suthargk Please don't post long listing of build errors, since they are specific to your projects setup. If unsure, use the prepared Docker container, there everything works.

Encountered the same problem when using pip install but I use anaconda cloud and those packages that fail with pip work with conda install given the package is available in the repo's


Add SamlChallenge.

This challenge will always raise an exception. It should be bubbled up
to the app (such as gcloud or gsutil) to display informative messages
so that the users can complete re-authentication properly (e.g. by
running gcloud auth login or gsutil config again).

Ping please. Travis failed but I don't think the failure is related to this PR.


refactor: remove isRequired from name, firstName, lastName fields of ProfileInfo

Impact: minor
Type: refactor
After working with the AccountProfileInfo component with live data, we've seen that name, firstName and lastName fields are not always present on an account. For instance a brand new account has none of the fields attached to it.
This PR removes the isRequired from these fields so that the component will display without error even when a name is not present.
Breaking changes
None
Testing

Try different combinations of having name, firstName, and lastName fields on a viewer object and make sure the component renders at all times, either with a full name (name OR firstName + lastName), first name only, or no name at all.

🚀 Preview deployed
Built with commit 31a2813c11b86ed25b9af0c0efd4ce848d34be0e
https://deploy-preview-335--stoic-hodgkin-c0179e.netlify.com

:tada: This PR is included in version 0.47.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Roslaunch got a "No such file or directory'

When I run the 501.bag demo, I got the following error:
RLException: Roslaunch got a 'No such file or directory' error while attempting to run:
/home/xxx/catkin_ws/src/hdl_graph_slam/scripts/map2odom_publisher.py __name:=map2odom_publisher __log:=/home/gcong/.ros/log/d4ec18c8-0b6a-11eb-b086-2fcb12979160/map2odom_publisher-7.log
Please make sure that all the executables in this command exist and have
executable permission. This is often caused by a bad launch-prefix.
The traceback for the exception was written to the log file
Why: I am on ubuntu 20 and ros noetic.

At this moment, this package cannot be built on Ubuntu 20 due to some changes on PCL. You can consider giving the following docker image a try instead of directly building it on Ubuntu 20.
https://github.com/koide3/slam_docker_collection


Changing gazebo SITL source files doesn't rebuild

There is no dependency rule to invoke rebuild in case of internal files on the SITL has been changed

This is a limitation of cmake ExternalProject_Add. https://cmake.org/cmake/help/v3.5/module/ExternalProject.html
@jgoppert what was the benefit of pulling the gazebo_sitl build into PX4's build system? I'm wondering if we could structure this differently and avoid this issue and make it easier to build sitl_gazebo with or without PX4.

I'm in favor of moving the sitl_gazebo stuff for sim and CI outside of px4/Firmware. We are getting ready to sync with rotors and the current approach is more of this, so see my comments here: https://github.com/PX4/Firmware/pull/6380

I have found way to rebuild external. you can see at PR #6845
From my tests it works, can you check?
I seen today that also changes on nuttx doesn't re-compile the lib, but in different way. if you rebuild second time, it rebuild the whole project, not just the lib (or the changed file). I think its better to leave it to other issue, mybe check all the libs/files for good dependency build.


Using caption with different toc sections instead of JS/CSS hack.

Using caption with different toc sections instead of JS/CSS hack.
This fits within the Sphinx construct and would allow our docs to be built on readthedocs.org.

Building with tox -e docs we get:

Building with LOCAL_RTD=True tox -e docs we get:

AFAICT, by using :titlesonly: and some other rules we can get rid of the expandable sections (or just not use h1, or change maxdepth).

Note the dont-merge label. I just wanted to discuss the issues with either approach.

Previous comments that were addressed in later changes:

This fits within the Sphinx construct and would allow our docs to be built on readthedocs.org.
Unfortunately, this doesn't quite agree with our CSS (we need some left-hand padding):

I got this inspiration / technique from (source):
https://docs.readthedocs.org/en/latest/

As a test to see if our docs would build in the readthedocs theme, I swapped out html_theme for 'sphinx_rtd_theme' and turned off our custom html_style. The resulting output is a mess (I think our custom template is to blame):

@tseaver I fixed the failure (was really just #1029 showing) and rebased against master. The merging of #1026 makes this "ready to go" for activating RTD.

I jumped the gun on getting it up on RTD, looks pretty silly :smile:

@tseaver and @jgeewax, what are your readthedocs.org usernames so I can add you as admins of the project?

Mine is tseaver.

@tseaver Added you as a maintainer. Are you reviewing this?

@tseaver Any issues with these changes?

Sorry, I thought from the botched rendering in the last example it wasn't ready to go.  LGTM.

@tseaver Do you know much about RTD?
It's using the old Sphinx theme for some reason (though not locally via LOCAL_RTD=True tox -e docs):
http://gcloud-python.readthedocs.org/en/latest/

I think it might be my use of
if ON_READ_THE_DOCS or LOCAL_READ_THE_DOCS:
  templates_path = []
else:
  templates_path = ['_templates']

i.e. I think RTD uses _templates.

Scratch that, it was the use of html_theme = 'classic', which gets picked up by us here.


Request: emmc support for installing ArkOS on rg353m devices to internal memory rather than to only sdcard on TF1

Would it be possible to add support for internal emmc memory for arkos? Currently it does not show emmc memory when you ssh into the device.
Using other means I was able to flash arkos img to internal memory; however, at first boot (with no sdcards installed) while It does boot to the ArkOS logo it doesn't proceed to install. After a short bit of time it switches from arkos logo to a blank screen and moves no further.

It is something I'd be interested in as I have no use for Android on the 353 devices and would prefer to make use of the internal emmc for my own use case at least.  How did you flash ArkOS to the internal emmc?

Thanks for this info.  In reviewing this and conversing with the JELOS team, I was able to get a solution for supporting this and it seems to be working well.  See here for more information. https://github.com/christianhaitian/arkos/wiki/Frequently-Asked-Questions---RG353M#q-can-i-load-arkos-onto-the-internal-emmc-storage

Sorry for the late reply, thank you for the update. - this worked
perfectly. Successfully installed ArkOs on internal. Just need to move some
games to the new sd card in slot 2 and do a little setup, i'll leave sdcard
1 blank
Have a spot where i can donate something for your efforts as a thank you?
On Thu, Jan 4, 2024 at 10:55 PM christianhaitian @.***>
wrote:

Thanks for this info. In reviewing this and conversing with the JELOS
team, I was able to get a solution for supporting this and it seems to be
working well. See here for more information.
https://github.com/christianhaitian/arkos/wiki/Frequently-Asked-Questions---RG353M#q-can-i-load-arkos-onto-the-internal-emmc-storage
—
Reply to this email directly, view it on GitHub
https://github.com/christianhaitian/arkos/issues/880#issuecomment-1878123554,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPDSD5CGZMFB7C7NO5GZ3LYM6BSRAVCNFSM6AAAAABBERAUPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZYGEZDGNJVGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

You're welcome.  The main page of the wiki has a donation link at the top and bottom.  No donation is needed but if you'd like to donate, I appreciate it.  Enjoy!


Init proposal box Visualization

Hi. I have a querstion.
I debuged the code [projexts/sparseRCNN/sarsercnn/head.py]
I visualize init_bboxes in forward of DynamicHead

But in your paper, the boxes visualized was this.

Is there something I am missing?
Why are the two box visualization image different?

Hi~
Please refer to issues 47

Thank you very mush for your quick reply.

I have the same confusion. Has the author explained the issue, and where?


Fix for Android music Nu Player issues

Android Music has several issues on Android 5.0+ devices using the new Nu Player by default.
These are two of the issues specific to Nu Player this patch fixes
1- setPosition() not working after stop() is called
music.play();
// Wait
music.stop();
// Wait
music.play();
music.setPosition(30f);
[Music starts from the beginning]

2- Calling stop() before play() throws IllegalStateException()
music.stop();
music.play();

The problem seems to be related to the call to player.seekTo(0) on the AndroidMusic stop() method. This was added most probably as a workaround to MediaPlayer not restarting the music after a stop call in some cases (see http://stackoverflow.com/questions/5985874/android-mediaplayer-clipping-on-restart-after-seekto and http://stackoverflow.com/questions/6849045/mediaplayer-instance-stop-behaves-like-a-pause). Porbably what's happening is that because seekTo() is assynchronous (http://developer.android.com/reference/android/media/MediaPlayer.html) it's returning after stop() has been executed and that is messing with Nu Player state.
The fix has been tested on a Nexus 4 and a Nexus 5 for both default Nu Player and Awesome Player for backwards compatibility but it has not been tested on Froyo devices that are supposed to be buggy (does libGDX support that?).
Other issues have been reported that may be related like https://github.com/libgdx/libgdx/issues/2663 but I haven't tested.

Hi I same problem with the music , I used 1.9.3-SNAPSHOT but this fix don`t exist , Please any hellp?


0.5px/1px E/SE misaligment

Have you found on your experiment runs a 0.5px/1px misaligment bias in right/bottom-right direction?
I have noted this both with aligned and not aligned corners models that you have used (e.g. R50/Swin Deaotl).
As these kind of errors are very hard to debug I want to know if you have experienced something like this on your side.
Thanks.

I will try to find an example on DAVIS to share.
In the meantime have you already experienced something like this?

@yoxu515  @z-x-yang  Just to give more evidence to this effect I've replicated the same frame (0) from DAVIS speed-skating 100 times.
Here the original annotation (frame  0/GT):

Frame 0 after 50 propagation:

Frame 0 after 99 propagation:

Down/Right  accumulated Drift 0-10:

Down/Right accumul

ated Drift 0-50:
Down/Right accumulated Drift 0-99:

Any feedback on this?

@yoxu515 There is a rounding error in the eval engine and the related interpolations as this happen and it is reproducible when input W or H is not divisible by 16.

@z-x-yang Other then some edge case precision about the max_stride alignment you are also affected by https://github.com/pytorch/pytorch/issues/34808.

@yoxu515 There is a rounding error in the eval engine and the related interpolations as this happen and it is reproducible when input W or H is not divisible by 16.

Thank you for your ongoing attention to this issue. To be honest, at this point, I am also still trying to understand why this misalignment is occurring. Perhaps, as @s-deeper commented, the nearest interpolation in PyTorch could introduce misalignment, leading to this situation. However, AOT should be able to learn how to eliminate this misalignment during training, unless there is a lack of strict alignment between the training and testing settings.
As far as I remember, the handling of mask interpolation in both the training and testing processes of AOT should be consistent. In any case, I will pay closer attention to this issue. Thank you!

@yoxu515 There is a rounding error in the eval engine and the related interpolations as this happen and it is reproducible when input W or H is not divisible by 16.

Furthermore, has this kind of misalignment caused any difficulties for you in the actual use of DeAOT? If not, I don't believe it's a critical issue.
Indeed, I have also noticed in some early versions of DeAOT experiments that when the video frame rate is very high, and the target remains stationary, there is some weird drift in the segmentation mask. However, in the released versions of DeAOT on YouTube-VOS and DAVIS, this issue does not arise (though I am not sure if it persists in videos with even higher frame rates or smaller object movements).

@z-x-yang Other then some edge case precision about the max_stride alignment you are also affected by pytorch/pytorch#34808.

Thank you for pointing out the bug in PyTorch that I had not previously noticed! I will review the relevant code and strive to prevent all unexpected misalignments.


updated to net 6

updated to net 6
restructured app
Just getting the project working.

sorry github pulled a fast one on me and I did the pull for the wrong repo


FlutterDriver commands result in null on certain devices.

I am currently testing a Flutter app using Appium-Flutter-Driver both locally and on AWS Device Farm. On some of the phones on Device Farm, Appium-Flutter-Driver has been unable to interact with elements. When I checked the Appium logs I noticed that all of the 'click' commands for FlutterDriver result in a null response, such as in the below example
2022-01-18 16:43:14:002 - [debug] [W3C (acee1730)] Calling AppiumDriver.click() with args: ["eyJmaW5kZXJUeXBlIjoiQnlWYWx1ZUtleSIsImtleVZhbHVlVHlwZSI6IlN0cmluZyIsImtleVZhbHVlU3RyaW5nIjoiY29ubmVjdFdpdGhQYXNzd29yZEJ1dHRvbktleSJ9","acee1730-88f2-438c-a867-565109f8b3e2"]
2022-01-18 16:43:14:003 - [debug] [FlutterDriver] Executing Flutter driver command 'click'
2022-01-18 16:43:14:003 - [debug] [FlutterDriver] >>> {"command":"tap","finderType":"ByValueKey","keyValueType":"String","keyValueString":"connectWithPasswordButtonKey"}
2022-01-18 16:43:14:009 - [debug] [FlutterDriver] <<< {"type":"Sentinel","kind":"Collected","valueAsString":"<collected>"} | previous command tap
2022-01-18 16:43:14:009 - [debug] [W3C (acee1730)] Responding to client with driver.click() result: null

Also when I try to get the render tree on this device I am met with this error

2022-01-18 16:43:14:024 - [debug] [FlutterDriver] Executing Flutter driver command 'execute'
2022-01-18 16:43:14:024 - [debug] [FlutterDriver] >>> {"command":"get_render_tree"}
2022-01-18 16:43:14:030 - [debug] [FlutterDriver] <<< {"type":"Sentinel","kind":"Collected","valueAsString":"<collected>"} | previous command get_render_tree
2022-01-18 16:43:14:046 - [debug] [W3C (acee1730)] Encountered internal error running command: TypeError: Cannot read property 'tree' of undefined
2022-01-18 16:43:14:046 - [debug] [W3C (acee1730)]     at getRenderTree (/usr/local/avm/versions/1.22.2/node_modules/appium/node_modules/appium-flutter-driver/lib/commands/execute.ts:70:57)
2022-01-18 16:43:14:046 - [debug] [W3C (acee1730)]     at processTicksAndRejections (internal/process/task_queues.js:97:5)

[Here is the full Appium log for this phone](https://gist.github.com/mankey2021/803e28c7b045a1ec0f70d6859f8a66a4)
[And here is the Appium log for a phone I tested locally that didn't have this problem](https://gist.github.com/mankey2021/245bcc007d9a8fb9c4f3d59cd611e82b)

I am currently using Appium 1.22.2 and Appium-Flutter-Driver 0.0.34. I believe that this issue is possibly related to this one on the Appium-Flutter-Driver page.

@mankey2021
Since you mentioned that the behavior is occuring on device farm, you may need to reach out to the device farm support for this. Also, you can share this behavior on the issue you linked related to appium-flutter-driver dedicated repo.
Closing from here. If you think this behavior persists by running locally on devices, then write in comments and I'll reopen the issue.

@darshankawar
I reached out to the device farm support team prior to opening this issue and I was told that it looks like a bug with the underlying Flutter Driver and not the device farm environment. I was able to get my hands on a Google Pixel 4a and reproduce this issue locally (Here are the logs for that device). I have also found that this issue only seems to happen on the first install of the app. My test suite is set up so that the app is uninstalled and reinstalled between test cases, and I only had this issue on the first test case and none of the subsequent ones.

@mankey2021
Thanks for the update. Since you are using flutter driver, now integration_test is now recommended way to write automated, integrated tests. See these documentation: https://docs.flutter.dev/testing/integration-tests. So can you try to use this instead of flutter driver and see if you still get same behavior ?


Fix up some whitespace nits

This fixes up some bikesheddy stuff with respect to the command output whitespace, specifically it trims the newlines before and after the help output.
cc @ehazlett @hairyhenderson
Signed-off-by: Nathan LeClaire<EMAIL_ADDRESS>

EDIT: I screwed something up, NOT LGTM... I'll fix it.

OK I fixed it <3 <3 <3

LGTM


time for generating local clusters for ogbn-papers100M and MAG-Scholar-F

Hi,
Thanks for the great work.
I am wondering what is the time (number of cpus, etc) for generating local clusters for ogbn-papers100M and MAG-Scholar-F.
I tried to run localclustering.py for ogbn-papers100M (considering all nodes, including unlabeled nodes), but it still haven't finished yet after running for 5 days with 20 cpus.
In addition, could you provided the pre-generated local clusters for ogbn-papers100M and MAG-Scholar-F?
Thanks in advance!

Thank you for your interest in our work! Yes, performing LC sampling on a large graph like papers100M can be very slow. If sampling is done for all unlabeled nodes, the time you reported might be normal...
We have tried uploading the sampled indices on a cloud drive, but the cloud drive we can use has a file size limitation and cannot accommodate such a large file. I will try to find a solution, but I cannot guarantee anything...
From a personal perspective, I still have some suggestions to address this issue (besides using more CPUs):

Use a faster PPR algorithm. I personally recommend the approximate algorithm in PPRGo(https://github.com/TUM-DAML/pprgo_pytorch/blob/master/pprgo/ppr.py), which can be very fast after adjusting some hyperparameters.
Use subgraph sampling algorithms other than PPR, such as Neighbor Sampling(https://docs.dgl.ai/en/latest/generated/dgl.dataloading.NeighborSampler.html) and K-hop Sampling(https://docs.dgl.ai/en/latest/generated/dgl.dataloading.ShaDowKHopSampler.html). In my experience, these can achieve similar performance to PPR.
For large graphs like papers100M, you can appropriately sample fewer unlabeled nodes, such as only taking 5%. In my experience, the results will not differ significantly (sadly).


Inserting Additional Entities

In our service, we can have multiple markets, but these markets are retrieved individually and separately, not as one large request.  I noticed that if I retrieve an initial market and insert it using Sync, then retrieve a subsequent (different) market and insert it, it removes the first market from Core Data, and so on, even if they have different remoteIDs.  This is fine if you are feeding it one huge JSON with your entire model, but would it be possible to support use cases like ours, where you may be retrieving new entities separately and needing to add them into the existing Core Data model, instead of overwriting everything?

Hi @bonebox, the predicate attribute might be helpful here. Giving a predicate to Sync it tells it to only sync the attributes that comply to the predicate. When a predicate is not present Sync will diff all the changes removing the elements that are not present in the JSON.

Hey @3lvis! Thanks for the info. I'm having trouble determining what the predicate would look like in this case.  I tried let predicate = NSPredicate(format: "remoteID = %@", marketID) which seemed to work at first--the second market entity was added without removing the first.  But then I also noticed that when I inserted the second market, the items in the first market got duplicated.  Syncing the first market again fixes the duplication.

Well the duplication I'm seeing seems to be somewhat random--I tried some different markets (that had fewer items) and it didn't occur with them.  The multiple markets get retrieved and subsequently Sync'd more or less concurrently--I'm wondering if that could be an issue?

@bonebox How many entries there are in the JSON you're using for updating? 2 or 1?
I can make a test case in out tests projects to check what's the problem behind it, personally I've only used Sync for the main sync (the one with all the entries in the JSON). For updates I fetched the item in a background thread and made the updates there.
If this is something we can automate it would be fantastic!

@3lvis I was syncing a single market at a time, just testing with 2 of them, so 2 calls to the sync method.  Each market has varying items, but typically between 25-50.  The markets and items have a many-to-many relationship, not sure if that makes a difference.
The duplication issue was partially my own fault--I had set up a test and forgot to disable it so it was attempting to sync the same markets twice. So the sync method was getting called 4 times instead of 2. Still not sure why it duplicated the market items instead of replacing them since it was the same market, but after disabling the additional syncs it stopped duplicating things.  So using the predicate I posted above seems to be working for my situation.  Thanks for the help!

Also wanted to mention that my app re-syncs the data whenever the page is refreshed, and that is working correctly (no duplicated items), so it seems that the issue has something to do with the sync method calls occurring so close together.  I did a test by wrapping the sync method call in a GCD synchronous queue and the duplication still occurred when doing the 4 concurrent calls to sync like I mentioned above.

@bonebox If you're using AFNetworking I would recommend something like AFUniqueGet, works quite well for multiple GET calls to the same resource.
https://github.com/3lvis/AFHTTPSessionManager-AFUniqueGET

@bonebox Two or more syncs to the same entity shouldn't happen at the same time, there could be some inconsistency in the persistent store and you'll get crashes saying.
"Couldn't not fullfill fault.."


Add support for creating alerts against a person in the TRS database to use in tests

Context
Our tests currently create alerts using a DQT-like schema. This needs to be amended to use the new TRS schema.
Changes proposed in this pull request
Add a WithAlert()  method on CreatePersonBuilder and use a builder type (like MQs).
All properties should be optional.
If the alert type is not specified, choose a random alert type.
If the details property is not specified, use some lorem ipsum (Faker.Lorem.Paragraph())
If the external link property is not specified, generate a fake URL.
If start date is not specified, generate a random date (see MQs).
If end date is not specified, use null.
If end is specified but is before start date, throw an exception.
Leave the existing WithSanction() method for now until we have fully migrated alerts from DQT to TRS.
Checklist

[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Update TestData for TRS alerts schema


Provide a method for reading longer descriptions.

The current description field only displays a small amount of text at once. This enhancement would be to make the description a long text box or a popup box.

Will need to convert our repeatable description field into a block like:
    <%= f.repeatable_attr_input(:admin_note, build: :at_least_one) do |input_name, value| %>
      <div class="form-group">
        <%= f.input_field :admin_note, name: input_name, value: value, as: :text, class: "form-control", rows: 4 %>
      </div>
    <% end %>

As repeatable textarea elements, it'll look like this:


PDF representation of the DGC

Hello all,
We are going to generate also a PDF representation of the DGC. We have many non-digital citizens, which we hope to reach with such representations. Anybody has experiences to share with respect to the look and feel of paper DGCs?
Are there any European specifications or directives concerning the look and feel of the digital green card, for the PDF and paper version? Will there be specifics concerning the format, pixels, design,... Or does every issuer just have to make sure that the required fields are present and is the layout the responsibility of the issuer?
Thanks in advance,
Peter

Although this is an important question, I believe it is out of scope for the schema work. Perhaps @gabywh can give some advise what table to bring this issue to?

Page 3 in https://ec.europa.eu/health/sites/health/files/ehealth/docs/trust-framework_interoperability_certificates_en.pdf suggests a format. Helpful, or were you looking for something different?

Or does every issuer just have to make sure that the required fields are present

That's the legal basis, for sure. As long as this is met, it will be fine.
I am not aware of any UX/UI specific layout criteria at EU level (e.g. so many pixels wide, so much % screen etc) but I'll ask around.

Hi guys,
Thanks for the feedback.
I had already read that PDF. Not really what I was looking for. I would prefer to get a clean template for each kind of attestation.
Also, I would like to obtain legal directives. Are we allowed to print all the medical details (that are hidden behind the QR code) in plain text on the PDF or paper copy?
Any ideas?

Hi guys,
Thanks for the feedback.
I had already read that PDF. Not really what I was looking for. I would prefer to get a clean template for each kind of attestation.

UI Masks.
All I have seen so far are mock-ups as per in these docs.
Will ask around.

Also, I would like to obtain legal directives. Are we allowed to print all the medical details (that are hidden behind the QR code) in plain text on the PDF or paper copy?

The proposed EU regulation could be what you are looking for, also mentions "human readable" and paper versions, etc:
https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52021PC0130 (e.g. Point 14)
Other than that, best place to look for legal guidance your country's legal representative in the EU eHealthNetwork.

Also interested in this topic, we (SK) also plan to provide pdf (as print stable version) for non electronic use.

Find our working template for a vaccination attestation on http://peter.ebraert.be/Attest COVID-19 Vaccination EU 20210429A.pdf
-- In vitro data (QR code not in sync with data - and signed with a self generated key pair).

01SKF2333D546F684533AF828A05CAC92D5C.pdf
Here is our working template, multi lang version is implemented in way, that every language has separate page.

UI layout has been quite an active topic of discussion these past couple of days within the eHealthNetwork, so I'll try to summarize here:

there are no EU-wide guidelines for UX/UI etc.
EU doesn't want to dictate to each Member State exactly how it must be, but to provide sample mock-ups etc as template / reference ideas for Member States
thus mock-ups are available in relevant docs (as above) to give some idea / reference
reference paper version of DGC has been worked on / discussed in EU eHealthNetwork, who will publish a version when formally approved

Until then... here some general reference points we (NL) have been using, maybe of use to others to get started / refine their own ideas:

https://support.google.com/googleplay/android-developer/answer/9889712?hl=en
https://developer.apple.com/design/human-interface-guidelines/

Glad to see the suggested template is a foldable design on A4 paper: https://ec.europa.eu/health/sites/default/files/ehealth/docs/covid-certificate_paper_guidelines_en.pdf


How can I disable whichkey for everything but ctrl-r?

I only want to use  functionality in insert mode, which gives me a pop up of register contents. How can I disable everything else in which-key but that?

If that's all you were going to use from Which-Key then you may only need this (tversteeg/registers.nvim)[https://github.com/tversteeg/registers.nvim]

Agree, you don't need which-key for just registers