releases:rollback failing

The e2e releases_test is failing against current workflow-dev chart with:
------------------------------
Releases with a deployed app
  can deploy the app
  /go/src/github.com/deis/workflow-e2e/tests/releases_test.go:61
$ deis login http://deis.<IP_ADDRESS>.xip.io --username=test-81 --password=asdf1234
Logged in as test-81
$ git init
Initialized empty Git repository in /tmp/deis-workflow-test809685720/.git/
$ deis apps:create test-653929327
Creating Application... ...done, created test-653929327
Git remote deis added
remote available at ssh://git@deis.<IP_ADDRESS>.xip.io:2222/test-653929327.git
$ deis pull deis/example-go -a test-653929327
Creating build... ...o...o...o...o...o...o...o...o...o...o...o...o...o...o...o...o...o...o...o...o...o...o...o...o...o...o.done
$ deis releases:list -a test-653929327
=== test-653929327 Releases
v2	2016-03-18T02:53:53UTC	test-81 deployed deis/example-go
v1	2016-03-18T02:53:53UTC	test-81 created initial release
$ deis releases:rollback v1 -a test-653929327
Rolling back to v1... ...Error:
400 Bad Request
detail: No build associated with this release

$ rm -rf .git

• Failure [16.372 seconds]
Releases
/go/src/github.com/deis/workflow-e2e/tests/releases_test.go:63
  with a deployed app
  /go/src/github.com/deis/workflow-e2e/tests/releases_test.go:62
    can deploy the app [It]
    /go/src/github.com/deis/workflow-e2e/tests/releases_test.go:61

    No future change is possible.  Bailing out early after 0.176s.
    Expected
        <int>: 1
    to match exit code:
        <int>: 0

    /go/src/github.com/deis/workflow-e2e/tests/releases_test.go:46
------------------------------

deis-controller pod shows:
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
INFO test-638365190: config test-638365190-367856d updated
INFO test-638365190: release test-638365190-v1 created
INFO [test-638365190]: test-81 created initial release
DEBUG create test-638365190
INFO test-638365190: domain test-638365190 added
INFO [test-638365190]: domain test-638365190 added
<IP_ADDRESS> "POST /v2/apps/ HTTP/1.1" 201 172 "Deis Client v2.0.0-dev"
INFO test-638365190: build test-638365190-ce22d1c created
INFO test-638365190: release test-638365190-v2 created
INFO [test-638365190]: test-81 deployed deis/example-go
INFO Pulling Docker image deis/example-go:latest
INFO Tagging Docker image deis/example-go:latest as <IP_ADDRESS>:80/test-638365190:v2
INFO Pushing Docker image <IP_ADDRESS>:80/test-638365190:v2
<IP_ADDRESS> "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http"
<IP_ADDRESS> "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http"
DEBUG create test-638365190
DEBUG create test-638365190
DEBUG deploy test-638365190-v2-cmd, img test-638365190:v2, params {'num': 0, 'version': 'v2', 'envs': {}, 'tags': {}, 'app_type': 'cmd', 'memory': {}, 'build_type': 'deispull', 'cpu': {}, 'healthcheck': {}}, cmd ""
DEBUG scaling release test-638365190-v2-cmd to 1 out of final 1
DEBUG scaling RC test-638365190-v2-cmd in Namespace test-638365190 from 0 to 1 replicas
DEBUG waiting for RC test-638365190-v2-cmd to get a newer resource version than 30083 (30s timeout)
DEBUG RC test-638365190-v2-cmd has a new resource version 30084
DEBUG waiting for 1 pods in test-638365190 namespace to be in services (120s timeout)
<IP_ADDRESS> "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http"
<IP_ADDRESS> "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http"
DEBUG 1 out of 1 pods in namespace test-638365190 are in service
DEBUG scaled up pod number 1 for test-638365190-v2-cmd
<IP_ADDRESS> "POST /v2/apps/test-638365190/builds/ HTTP/1.1" 201 223 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/apps/test-638365190/releases/?limit=100 HTTP/1.1" 200 638 "Deis Client v2.0.0-dev"
INFO test-638365190: release test-638365190-v3 created
INFO [test-638365190]: test-81 rolled back to v1
INFO test-638365190: No build associated with this release to publish
INFO [test-638365190]: No build associated with this release to publish
DEBUG create test-638365190
<IP_ADDRESS> "POST /v2/apps/test-638365190/releases/rollback/ HTTP/1.1" 400 50 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/apps/?limit=100 HTTP/1.1" 200 231 "Deis Client v2.0.0-dev"
DEBUG destroy test-638365190
WARNING test-638365190: Error deleting existing application logs: HTTPConnectionPool(host='<IP_ADDRESS>', port=80): Max retries exceeded with url: /logs/test-638365190 (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7fa08a04a748>: Failed to establish a new connection: [Errno 111] Connection refused',))
WARNING [test-638365190]: Error deleting existing application logs: HTTPConnectionPool(host='<IP_ADDRESS>', port=80): Max retries exceeded with url: /logs/test-638365190 (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7fa08a04a748>: Failed to establish a new connection: [Errno 111] Connection refused',))
INFO test-638365190: domain test-638365190 removed
INFO [test-638365190]: domain test-638365190 removed
<IP_ADDRESS> "DELETE /v2/apps/test-638365190/ HTTP/1.1" 204 - "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "DELETE /v2/auth/cancel/ HTTP/1.1" 204 - "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/apps/?limit=100 HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"

$ deis releases:rollback v1 -a test-653929327 Rolling back to v1... ...���Error: 400 Bad Request detail: No build associated with this release

That's intentional. v1 has no build so it should return HTTP 400 and the client should exit non-zero. I guess e2e needs to be updated?

Ah ok, thanks @bacongobbler.  I'll create an e2e PR which with intent to close this issue.

In regards to the releases_test it would probably be best to call deis pull twice, then roll back to v2.

Is having the v1 release not contain a build consistent with Deis v1? On the face of it, build + config = release seems to imply that we shouldn't have a release at all until deis pull, but I know that's not how it's been implemented.
tl:dr I think @bacongobbler's diagnosis is correct and we probably should do deis pull twice here, but I'm wondering how we justified the v1 release never being associated with a build. Another question is how this test used to pass and why it began failing now--I assume there were some relevant controller changes.

my guess is that #497 fixed this overnight, but I can't confirm that.

v1 is the special snowflake, and historically it was to follow Heroku's example. Every release afterwards contains a build and a config, but v1 contains neither.

v1 is the special snowflake, and historically it was to follow Heroku's example

It's all coming back to me now. Thanks to our resident Deis historian. :older_man:


Theme does not include build date

It would be useful to:

Always have the build date included in the document header and
Optionally have the build date be displayed in the footer.

Sphinx supports this in its basic template when the html_last_updated_fmt configuration variable is set.
In its template, it is used as follows:
    {%- if last_updated %}
      {% trans last_updated=last_updated|e %}Last updated on {{ last_updated }}.{% endtrans %}
    {%- endif %}

I think the right place to include it would be theme/pydata_sphinx_theme/sections/footer.html.

I myself don't like to have the build date displayed in the documentation as most of my docs are built on weekly basis making this information perfectly useless. On the other hand I display in all my articles the lastest modification of the source.
As a consequence I'm not sure it should be set by default in the theme but I can show you how to add this template fairly easily in your documentation (wherever you see fit)

First go to the _templates directory of your documentation folder and create a last-updated.html file:
<!-- docs/_templates/last-updated.html -->
<div class="last-updated">
    {%- if last_updated %}
        {% trans last_updated=last_updated|e %}Last updated on {{ last_updated }}.{% endtrans %}
    {%- endif %}
</div>

Then add this template to any section of the documentation using your conf.py e.g. the footer:
# docs/conf.py

templates_path = ["_templates"] # don't forget to add the templates folder
html_last_updated_fmt = "" # select any format you see fit
html_theme_options = {
    # [...]
    "footer_start": ["last-updated"], # work as well with the extension
}

And voila you will see the last uodate component in your footer:

If you want to go down the path of a git based update inforamtion, I suggest you have a look to this amazing extention: https://github.com/mgeier/sphinx-last-updated-by-git/

I understand not wanting to display the timestamp, but is there any reason not to include it in the document? When I debug builds, or websites, it helps to know which version I'm looking at.

what do you call "document" ? is it articles ?

I mean inside generated html.

something like a custom tag in  ?

Yes, exactly.


Upgrade actions/cache to v3

Deprecation output from CI:
[integration_test_matrix (ubuntu-22.04, .bazelversion, updatesrc, true)](https://github.com/cgrindel/bazel-starlib/actions/runs/4642140771/jobs/8215751093)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/cache@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

It turns out that I updated gha_set_up_action_cache to use v3, but did not release it.


Fix case of appId in first README example

The first README example doesn't work because it uses appID instead of appId.

NB: I've been tidying up my github account and deleted my fork of this. Not sure if that'll have an impact on this PR, but I doubt anyone cares since we've recently passed its 6 year anniversary.


DropdownToolbar Variant Prop

Describe the desired behavior
Add the ability to change the dropdown toolbar mat-tool color from primary|warn|error|undefined
Describe the current behavior
There's no way for me to update this.
Is this request related to a current issue?
No
Additional Context

How can we spread properties more easily onto angular components?  Make a spike in JIRA for this, it would be nice to know.


API: groupby reductions

Would that have the same semantics as dropna in pandas?

Same semantics as "skipna" in pandas groupby/ndframe reductions


TwinCAT 2 and TwinCAT 3 (4020 and lower) support

Starting from TwinCAT 3.1.4022, the base data types like INT, REAL etc. are available from ADS API.
Now when the library is parsing data, it queries the data types from the PLC and PLC returns data type info. We don't need to know base data type info ourselves. This is how this library works.
TwinCAT 2 and TwinCAT 3 (< 4020) do not have this information. When the library asks for REAL data type, the PLC responds that symbol was not found. We need to manually have base data type info ourselves. This seems to be quite easy task as the library already has base data types listed. Basically if a base data type info is not found from PLC, we use our own data.
After this issue is closed, the library should support all TwinCAT versions since 2.11. Just tested first prototype with 2.11 and seems to work fine.
NOTE: TwinCAT 3.1.4020 support means that the PLC project is compiled with compiler version 4020 or lower. If runtime is 4024 but compiler is 4020, it's not working.

Released in version 1.9.0!


SvtkVcfCluster: Too many open files

Bug Report
Affected module(s) or script(s)
SvtkVcfCluster
Affected version(s)

[ ] Latest public release version [version?]
[x] Latest master branch as of 05/04/2021

Description
I'm running GATKSVPipelineBatch wdl and in Module0506 I get the following error in SvtkVcfCluster task:
[E::hts_open_format] Failed to open file temp/01022.bcf
Could not read temp/01022.bcf: Too many open files

I also attach the complete log file.
log-events-result.log
This is a scatter task and only one is failing.
Steps to reproduce
Run GATKSVPipelineBatch.wdl with AWS Backend

When I searched for your error message, I found this samtools ticket, which recommends increasing the memory for the sort task. The easiest way to do that for this workflow would be to increase the memory for the task with the runtime attribute override variable runtime_override_svtk_vcf_cluster in Module0506. Unfortunately, this would apply to all shards.
The memory for the sort command is determined dynamically for this task. We haven't encountered this error regularly before, but I will leave the issue open for now as a record in case this becomes an ongoing issue and we need to update the memory model.

Hey! I did a PR on cromwell to accept ulimits attribute and pass it to docker on AWS backend. Now it's possible to define the maximum number of opened files. I already tried running the task again and it's working fine. I will close this for now. Thank you


Investigate XHR web platform tests that time out

We have several XHR web platform tests commented out, marked as
// passes locally, and sometimes on Travis CI, but with a 60 second timeout often fails on CI

and we're about to get more as I fix #1830.
None of these tests look particularly bad, and all pass pretty fast on desktop browsers.
Furthermore, in general when running the tests even locally, the XHR tests often take multiple seconds to complete, which shouldn't be necessary.
We should investigate why XHR tests are so slow to complete and cause timeouts, and hopefully re-enable the commented-out tests when we have a solution.
My hypothesis is that we're doing something wrong in the server/jsdom interaction which is causing problems to mount as more and more XHR tests execute, due to some resource leak or contention. For example, maybe we're using keepalive too aggressively, and end up hogging all the server's potential connections? Or we're not terminating connections properly?
/cc @nicolashenry, our XHR expert.

This is quite bad. Even after disabling those two problematic tests, a new test (which has never caused problems before), XMLHttpRequest/status-basic.htm, has now started timing out.
I guess I'd better bump this up in priority, as it makes our CI slow and unreliable.

It looks like the problem is mostly in our sync XHR implementation being slow. E.g. responsetype.html does seven sync XHRs, and sprinkling some logs around makes it clear those are what's causing the holdup.

About 400 ms per sync XHR in that test is spent on JSON parsing the result from the other process. I'm not sure if there are any good workarounds for that. Maybe we could send the buffer separately somehow.

And another 800 ms per sync XHR is spent spinning up a new Node process. Of course it's an expensive one since it requires all of jsdom. Maybe we can have it just require request or http or something.

Although I think it's too much work for me at the moment, the way I'd do that is:

Change xhr-sync-worker.js to be a wrapper around request, not around jsdom.
Change its communications channels so that it streams the response body to process.stdout, and uses process.send() for response headers. (I hope this works with spawnSync, not just spawn). This avoids buffer-to-string conversion, JSON serialization, JSON parsing, and string-to-buffer conversion.
Change xhrUtils to use an abstraction over request that can use the xhr-sync-worker.js "sync request" version. Then it will behave the same as in the async case but it will fire all its events (such as "response") synchronously
Then we can update the main XHR code to treat sync and async requests the same, except for the one flag it passes to xhrUtils.

We may be able to skip some of this by using existing sync-request packages that exist on npm.

Another approach would be to keep the worker around, instead of creating a new one for each sync XHR. Maybe we could kill it after a second or something.

I didn't find any fast and clean solution to the slow child process creation. Maybe bundling jsdom module and dependencies into one unique file for the worker could help.
Anyway, I think that there is too much tests depending on sync xhr. My personal thought is that sync option in xhr should be deprecated because there is not any good reason to use it.


Update package.json to new version

Fix version-tag after updating URLs

Description

Related issues

Motivation and Context

How has this been tested

Types of changes

[ ] Docs change / refactoring.
[ ] Non-breaking change (fix or feature that wouldn't cause existing functionality to change/break).
[ ] Breaking change (fix or feature that would cause existing functionality to change/break).

Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes don't generate new warnings.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] All new and existing tests pass.

This is not required.


How can I create varchar column w/o actual length? (VARCHAR instead of VARCHAR(x))

https://github.com/tgriesser/knex/blob/d98c0b1abc44b8090f426a3d62e0541a394142d8/lib/schemabuilder.js#L151
In the source code, it looks like I have to specify varchar length.
If I will not do it then 255 will be used as vchar length.
I'm using PG.
For the sake of consistency, I would like to add columns just as VARCHAR (not a VARCHAR(...)) because I already have columns with type VARCHAR.
How can I do it using knex? Thanks

with .specificType


Loss Function

The loss function used in the training is CrossEntropy(model(G_t), G), whereas traditionally in diffusion models it is CrossEntropy(model(G_t), G_{t-1}). Does using the latter make the training worse in your experience? Thank you!

It's important to use model(G_t), G and not model(G_t), G_{t-1}, but what we are doing is what most model do in fact. Check section 2 of the paper, the reason for this is explained.
Best,
Clément

Hi Clément, Thanks for the pointer. I'm afraid I still could use your help after reading Sec. 2. To my understanding:

Ho (2020)'s loss function is L_simple
Nichol and Dhariwal (2021)'s loss function is  L_simple + L_vb
Austin (2021)'s loss function is L_vb + CrossEntropy(model(G_t), G)
Your loss function is CrossEntropy(model(G_t), G)

It seems to me that the idea that the model should be encouraged to "do as much as is can" is a novelty of Austin (2021), whereas CrossEntropy(model(G_t), G_{t-1}) is more similar to what a diffusion model is designed for.  Can you point me to other diffusion papers where only loss of the formCrossEntropy(model(G_t), G) is used? Many thanks!

If you look at L_simple for example, it tries to predict the loss that has been added to the clean sample to create z_t.
Up to a substraction, predicting the loss is the same as predicting the clean sample, so Ho et al. 2020 predict the clean sample, not z^{t-1}.
It's similar for the other ones.

I have a related question on the derivation of the loss (let me know if I should make a new issue).
Why do you train on CrossEntropy(model(G_t), G) as opposed to L_vb (general loss) or L_vb + CrossEntropy(model(G_t), G) (like in Austin (2021))?
Ho (2020) trains on L_simple but in the case of Gaussian noise L_simple, which is the MSE between the predicted and real noised mean (eq 8) or the denoising score matching objective (eq 12),  is essentially an unweighted L_vb. This simplification comes from the KL divergence of two Gaussians which leads to Eq 8.
Is the cross-entropy score you're using also an unweighted L_vb? Austin (2021) discuss this a little bit in section 3.4., paragraph 2, but I didn't understand whether the answer is yes/no.
Thanks in advance! Great implementation btw, following through the code was easy:)

Hello Najwalb,
we trained using CrossEntropy loss for simplicity, and as a way to highlight that denoising diffusion models reduce generation tasks to regression or classification tasks.
It's not so clear how it relates to L_{vb}. As Austin discuss in 3.4, we know that the optimal solutions of the two loss functions are the same, but it is not clear that for arbitrary q, L_simple can be written \sum_t \gamma_t L_vb^t. It would be interesting to explore this further.

Thanks @cvignac. I'm curious to know if you are aware other diffusion papers in which the role of the model is to transform the data, as opposed to to predict the score (in score-based models) or the noise (in DDPM).

Hello,
There is the Austin paper of course, and then there are several papers such as https://arxiv.org/pdf/2210.02303.pdf
which use v-parametrization, which is a mix between predicting the noise and the clean data.
I don't think that these things are fundamentally different. Since clean_data = noisy_data - noise, predicting the noise and the clean data is pretty much the same. Then it's a matter of stability of the inverse diffusion steps.
For discrete diffusion, predicting the clean data makes sense because it is simply one class, while the noise is the difference of two classes. That's why we chose this parametrization.
Best,
Clement


[SPARK-38219][SPARK-37691][3.3] Support ANSI Aggregation Function: percentile_cont and percentile_disc

What changes were proposed in this pull request?
This PR backport https://github.com/apache/spark/pull/35531 and https://github.com/apache/spark/pull/35041 to branch-3.3
Why are the changes needed?
percentile_cont and percentile_disc in Spark3.3 release.
Does this PR introduce any user-facing change?
'No'.
New feature.
How was this patch tested?
New tests.

ping @cloud-fan

Hm, we don't usually backport new features. Is there a reason for this?

Hm, we don't usually backport new features. Is there a reason for this?

It seems committers forgot merge feature into branch-3.3

I meant that they were likely intentionally merged to master branch only because it's a new feature.

Oh okay, I missed that this was already discussed in dev mailing list to add it. LGTM

thanks, merging to 3.3!

@cloud-fan @HyukjinKwon Thank you.


sys/linux: move openat to dev_rtc.txt

move openat$rtc to rtc_dev and change return type to fd_rtc.

Codecov Report

Merging #1077 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1077      +/-   ##
==========================================
+ Coverage   67.38%   67.39%   +<.01%
==========================================
  Files         118      118
  Lines       20582    20582
==========================================
+ Hits        13869    13871       +2
+ Misses       6068     6066       -2
  Partials      645      645

Impacted Files
Coverage Δ

prog/any.go
89.39% <0%> (+0.7%)
:arrow_up:

Continue to review full report at Codecov.

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


v1-bump/1.181.0

Release 1.181.0

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 19787f6158b5c017641979190392641b0cf7e61d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Filter estimate

What changes were proposed in this pull request?
This is a WIP PR. In this version, we set up the framework to traverse predicate and evaluate the equality (=) expression.
How was this patch tested?
We just have a simple test case for now. More tests need to be added.

cc @wzhfy Please preview.

Please remove changes of my commits, and only keep the codes necessary for your pr (maybe some functions in EstimationUtils).

I'm a little confused, I thought we only support EqualTo condition now? But there are codes for IsNotNull and all kinds of Binary conditions. Are the codes for them complete?

I have made the changes and pushed the changes to my personal remote branch filterEstimate.  In addition to the changes described above, I also did the following:

removed your source code except two methods I need to use in EstimationUtils.scala file.
Although this is an early version, I provided the framework to do recursion and some methods such as evaluateIsNotNull.  This is because evaluateIsNotNull is used even in a simple EqualTo expression.  For example, for SQL statement "select * from table1 where key1=2", Spark Parser will generate the predicate conditions as:  key1 isnotnull AND key1=2

We should evaluate both IsNull and IsNotNull, or neither of them. When evaluating IsNotNull, we use nullCount in column stats, which means we trust it. But we also say that nullCount isn't reliable because of outer joins, that's kind of contradiction.
Since the IsNotNull predicate is effective and important when it's applied to a table (it can filter lots of null values), I suggest we support both of them.

I think we can support IsNull and IsNotNull only when the child is a leaf node (table).

Agreed to support IsNull and IsNotNull only when the child is a leaf node (table).

just committed all the changes including isnull support and transformating min/max using Range class.  Please review it again.

Shall we remove unused methods in Range.scala?

Actually our code can be more concise using methods in Range, but I think it looks ok now. Let's submit it after fixing the above minor comments :)


Add support for IMU_V2_Brick

https://www.tinkerforge.com/en/doc/Hardware/Bricks/IMU_V2_Brick.html#imu-v2-brick
https://www.tinkerforge.com/en/doc/Software/Bricks/IMUV2_Brick_Java.html#imu-v2-brick-java-api
https://www.tinkerforge.com/en/doc/Software/Bricks/IMU_Brick_Java.html#imu-brick-java-examples
https://www.tinkerforge.com/en/doc/Software/Bricks/IMU_Brick_Java.html#imu-brick-java-api

Rejected by LEAN


proxy name not defined

Traceback (most recent call last):
File "auto_email_list.py", line 52, in
for proxy in proxy_config.proxy:
NameError: name 'proxy_config' is not defined

Please completely update your version (git pull)

says already up to date

Please check the repo. There you will see that auto_email_list.py does not longer exist. Therefore you can't have the newest version. Maybe download the project as .zip instead


wiki: Comparison page

For this page: https://github.com/Arkweid/lefthook/wiki/Comprasion-with-other-solutions
The title:
- Comprasion with other solutions
+ Comparison with other solutions

Another utility to compare with: pre-commit
It has nice docs, but the syntax is a bit arcane.  You can share hooks easily, though.  It lacks a curated catalog of shared hooks, alas.

FIxed.
https://pre-commit.com/ refused connection and repository haven't any docs. So I can't inspect features :(

Weird. The site works for me from the USA.
The code repo is https://github.com/pre-commit/pre-commit/
The docs are hosted on github via https://github.com/pre-commit/pre-commit.github.io
Sent with GitHawk

I researched the problem. The Russian authorities block the IP address on which the resource is located... three times.
https://gyazo.com/5bb75ab0c51e2a48d3b0e1343cfd50a5
pre-commit.github.io redirect me on https://pre-commit.com/ :(
I looked through the docs. The tool looks quite complicated.

@docwhat OK, I've got comparison results. I tested it on discourse CI example.
pre-commit version is 1.15.2
pre-commit:

Require python runtime.
Verbose config.
Not very clear documentation.
Very slow(3x). I've got 25sec execution time in average vs 7,5 secs for lefthook. Dunno know why it so slow. Parallel mode enabled by default.
Breaks original output from commands

pre-commit config:
-   repo: local
    hooks:
    -   id: rubocop
        always_run: true
        name: rubocop
        files: git ls-files --cached
        entry: bundle exec rubocop --parallel
        language: system
    -   id: prettier
        always_run: true
        name: prettier
        files: git ls-files --cached
        entry: yarn prettier --list-different app/assets/stylesheets/**/*.scss app/assets/javascripts/**/*.es6 test/javascripts/**/*.es6
        language: system
    -   id: eslint-assets
        always_run: true
        name: eslint-assets
        files: git ls-files --cached
        entry: yarn eslint --ext .es6 app/assets/javascripts
        language: system
    -   id: eslint-test
        always_run: true
        name: eslint-test
        files: git ls-files --cached
        entry: yarn eslint --ext .es6 test/javascripts
        language: system
    -   id: eslint-plugins-assets
        always_run: true
        name: eslint-plugins-assets
        files: git ls-files --cached
        entry: yarn eslint --ext .es6 plugins/**/assets/javascripts
        language: system
    -   id: eslint-plugins-test
        always_run: true
        name: eslint-plugins-test
        files: git ls-files --cached
        entry: yarn eslint --ext .es6 plugins/**/test/javascripts
        language: system
    -   id:  eslint-assets-tests
        always_run: true
        name:  eslint-assets-tests
        files: git ls-files --cached
        entry: yarn eslint app/assets/javascripts test/javascripts
        language: system

Lefthook config:
lints:
  parallel: true
  commands:
    rubocop:
      run: bundle exec rubocop --parallel
    prettier:
      run: yarn prettier --list-different app/assets/stylesheets/**/*.scss app/assets/javascripts/**/*.es6 test/javascripts/**/*.es6
    eslint-assets:
      run: yarn eslint --ext .es6 app/assets/javascripts
    eslint-test:
      run: yarn eslint --ext .es6 test/javascripts
    eslint-plugins-assets:
      run: yarn eslint --ext .es6 plugins/**/assets/javascripts
    eslint-plugins-test:
      run: yarn eslint --ext .es6 plugins/**/test/javascripts
    eslint-assets-tests:
      run: yarn eslint app/assets/javascripts test/javascripts

LGTM 😃
Sent with GitHawk

fwiw, that benchmark is sandbagged sadly -- the files:  directive you have above is entirely incorrect (it's a regex not a shell command) and results in no files being passed to the tools -- I'd suggest an apples-to-apples comparison if you want a more fair result
most of the time difference will be inside the tools in this case since you're sending different outputs
@docwhat

It lacks a curated catalog of shared hooks, alas.

You seem to have missed https://pre-commit.com/hooks.html
@Arkweid

Verbose config.

Additionally, parallel: true isn't a safe operation for fixers so pre-commit only internally parallelizes tools (without an option to footgun) so even with that I think it's only fair to benchmark non-parallel mode if you want a true comparison

you're also missing the main feature of pre-commit in your comparinson, in that it manages installation of hooks for you so you don't have to install a million tools or figure out how to get a working python / ruby / node / etc. environment up and working

Ah, yeah... that is right... installing the tools is very useful.
I'm not keen on it being "builtin" to pre-commit but having it done is great.

@asottile thank you for comments!
I am not familiar with python and its infrastructure. Also, I did not have much time to get to know pre-commit. I tried to follow the documentation, and this is the result I got. I will be glad if you correct me and show me how to do it. I am interested in a fair comparison.

you're also missing the main feature of pre-commit in your comparinson, in that it manages installation of hooks for you so you don't have to install a million tools or figure out how to get a working python / ruby / node / etc. environment up and working

I tried to avoid comparing features that come from different philosophies.
pre-commit seems to follow the view of implicit. External repositories with hooks and installation of tools automatically.
lefthook follows the opposite philosophy of explicit. Does not use external dependencies and tries to do everything obviously.
This point is quite controversial. For some, this is a plus, for others a minus. Therefore, I removed these kinds of things from the comparison.

curious what you mean here, pre-commit passes through the identical bytes that tools hand us

I mean the output from 'pre-commit' haven't colors.

Additionally, parallel: true isn't a safe operation for fixers so pre-commit only internally parallelizes tools (without an option to footgun) so even with that I think it's only fair to benchmark non-parallel mode if you want a true comparison

Well, it is safe if your tools do not try to access the same files concurrently. Or you have only linters in your tool set. As you can see in discourse example they have only linters.
The question is debatable, but many think that you should not include auto-correctors in hooks because you committed something that you didn’t see (because the auto-corrector changed the files).

lefthook follows the opposite philosophy of explicit. Does not use external dependencies and tries to do everything obviously.

I think you're misrepresenting here -- pre-commit is very explicit about the versions and tools being used whereas with lefthook you have to depend on whatever is installed at the system (and with no control over it)

I mean the output from 'pre-commit' haven't colors.

if the tool doesn't output colors, pre-commit won't output colors, there's no trickery happening here :man_shrugging:

The question is debatable, but many think that you should not include auto-correctors in hooks because you committed something that you didn’t see (because the auto-corrector changed the files).

you should probably prominently indicate that you don't support fixers in your README then -- that's a huge minus and a great big footgun :) -- most of your examples include fixers so I'm not sure why you wouldn't want to support them

if the tool doesn't output colors, pre-commit won't output colors, there's no trickery happening here
Hm, then dunno why in my installation output from Rubocop and Eslint haven't colors :thinking:
You can see what a've got on this screenshoot:
https://camo.githubusercontent.com/4d331d49b3a7712adda7e2ccbf3dd24738554d3a/68747470733a2f2f63646e312e73617665706963652e72752f75706c6f6164732f323031392f372f31312f61326337356331323034356534643133323536626564313531666533343239322d66756c6c2e706e67

:man_shrugging: probably an issue with ptys


Make rotm reminder a periodic task.

Coverage increased (+0.01%) to 91.98% when pulling 412254768f15b43c4129a61bea0dc5a7357d3b43 on akatsoulas:rotm-reminder-periodic-task into 0334f163d03c5385b71c2003b5936bda70331141 on mozilla:master.

Coverage increased (+0.01%) to 91.98% when pulling 412254768f15b43c4129a61bea0dc5a7357d3b43 on akatsoulas:rotm-reminder-periodic-task into 0334f163d03c5385b71c2003b5936bda70331141 on mozilla:master.


typeable broken in 1.5.2

I can set the typeable prop in v1.5.1, and it works great.
In v1.5.2, it doesn't work.
Thanks!

What is it that doesn't work? Seems to be ok here.
http://jsfiddle.net/charliefarley/eywraw8t/107655/


Traits to configure the container image and location fo the sources

We should support traits to configure what container image an integration should use to run integrations as well as where as where sources are located.
As example, it would be nice to be able to define a KameletBinding like:
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: my-binding
  annotations:
    trait.camel.apache.org/integration.image: "acme/image:1.0"
    trait.camel.apache.org/integration.sources-mode: "embedded"

Where:

the KameletBinding should be executed using the the container image defined by the trait.camel.apache.org/integration.image annotation (no build should be performed)
the annotation trait.camel.apache.org/integration.sources-mode: "embedded" instruct the operator that any source are embedded in the container image on a specific location, the operator still need to configure them for the runtime to be able to read but does not need to look them up in k8s.

Relates to: https://github.com/apache/camel-k/issues/2165

/cc @nicolaferraro

Thinking a little bit about this:

We may not need to add an integration.sources-mode but we could probably add an option to set the location of the source on to the source definition, like:

spec:
    sources:
    - location: "{{env.CAMEL_K_SOURCES}}/routes.yaml"

for what concern the container images, as we have a pod trait now so we may add an additional option there, like:

kamel run -t pod.integration-image=foo/bar:1.0.0

for what concern the kamelets we may add an option to the related trait to list embedded kamelets that the operator should not attempt to look up from k8s

kamel run -t kamelets.embedded=foo,bar,baz

I was thinking we could embed the location in the classpath. I'd assume that without information about the sources, the operator is not in a position to compute the right classpath, so that should be provided as part of the container image. So we may only need to choose a (fixed) relative path for sources.

I was thinking we could embed the location in the classpath. I'd assume that without information about the sources, the operator is not in a position to compute the right classpath, so that should be provided as part of the container image. So we may only need to choose a (fixed) relative path for sources.

This is probably true for kamelets but sources it is a little bit more complex so I think, the location of the sources should always be provided. The operator should then ignore any inspection task and only create the "application.properties" where the sources are configured.
Not sure if it makes any sense :)

I think the first part of the issue is captured by the container.image trait property. @lburgazzoli does the location for the source still make sense?


missing stats

All this disappeared one day and I have not changed any api settings

A fix for this was already in development, now it should be live on production.


WSL terminal profiles should be "profiles" (not "detected")

This has been happening for a while now, WSL profiles haven't been showing up in the dropdown despite the useWslProfiles setting being true. But they are being detected, just not promoted to the real profiles section:

fixed with https://github.com/microsoft/vscode/commit/2c22ffe6ae0d8d7cf38a511c3375dd68fd151595
s/o to bracketed paste mode on bash for the typo


add new error for disabled service, with test

We probably also want to match swift's error message
https://github.com/firebase/firebase-ios-sdk/pull/13007

The error message from the serverside contains the link to fix the issue, and is passed along to the customer


Not suport Little Endian Implicit DICOM

Error:
Error: Unsupported DICOM transfer syntax: '1.2.840.10008.1.2' (Little Endian Implicit)

This will be solved by switching to using dcmtk tools.  Stay tuned for v2.0


feat: put server in slow motion when server's about to crash - [merged]

Merges anti-crash -> staging

mentioned in commit 164ef75beaaedc7cd0a059ab005487360a395aca

In GitLab by @ghost1 on Oct 5, 2023, 14:41
:tada: This MR is included in version 0.11.0 :tada:
The release is available on GitLab release.
Your semantic-release bot :package: :rocket:


Split longer recordings

Currently the audio summarization functionality will fail if the meeting is too long. (over 25MB)
The first step to fixing this is being able to split up longer recordings and send them to the whisper API in chunks to avoid the API limitations: https://platform.openai.com/docs/guides/speech-to-text/introduction
Currently compression is used in this case: https://github.com/mattermost/mattermost-plugin-ai/blob/7a8c08f40e4051454ea68c872731e3b6e70c2123/server/meeting_summarization.go#L58
Go native implementation would be preferable to using ffmpeg.

Wondering if this can be made available through an API to the plugin. I have the requirement of trimming audio and video files in a plugin and it would be great to share a common implementation. I'm currently using AWS Elastic Transcoder though a Go implementation would be more efficient as mentioned in the description

@mickmister @streamer45 It actually would be really great if this part could be done by the calls infrastructure. We already have that setup for generating transcriptions with calls.


SASS Support

It would be interesting to have the option of using "sass" instead of "less".

With Bootstrap 4 on the horizon, I'll be adding SASS and LESS support for all themes (instead of just LESS)

+1

Please see PR #59 for Sass support.

The PR was added, and I need to do a little cleanup of the SASS file due to some LESS changes but now the template will have both LESS and SASS as options for developers to use!


[Details Revamp] Remove the Three Dot Menu on Affected Reports

Details

This is a final PR for the Details Revamp task which aims at removing the Three Dot Menu from reports affected by the revamp. It also fixes a bug regarding the Hold promoted action not displaying properly for single expenses.
Fixed Issues

$ https://github.com/Expensify/App/issues/42080
PROPOSAL:
Tests

Create a workspace
Go into a room of said workspace and confirm that the three dot menu in the header is missing
Create two expenses for the workspace
Go into the report view containing both those expenses and confirm the three dot menu is missing
Go into one of the expenses and confirm that the three dot menu is missing
If you have an access to an account with a Concierge guide assigned, please check whether the button for Book a call works properly, since it has been removed from the three dot menu in that chat.

A bug concerning the hold promoted action not showing was also fixed here, please test this one also:

Create a workspace / use an existing one
Submit a single expense for said workspace.
Go into the expense report view and press on the header to display it's details.
Confirm that the hold promoted action does show and works properly for this report (Since this change affects holds in ReportDetailsPage, please test multiple posibilities for hold, such as single expense for workspace, multiple expenses in one thread for workspace, single expense for user and multiple expenses for a group in a thread).

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome
https://github.com/Expensify/App/assets/88325488/8c33d26e-1d46-4d85-b7ba-8125da247947

iOS: Native
https://github.com/Expensify/App/assets/88325488/5860c59c-e9c7-4acd-af94-9fd7f154ebab

iOS: mWeb Safari
https://github.com/Expensify/App/assets/88325488/56a45763-f1a1-4f9a-889c-3e13052b8113

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/88325488/6e83fd81-152b-4b9c-9b3d-711c0133fb2c

MacOS: Desktop
https://github.com/Expensify/App/assets/88325488/413039ed-57d1-4b52-ba3c-8932f54622be

cc: @grgia

@parasharrajat from here, please give this a review now. Thanks!

BUG: I don't see Book a call button on details page.

I've moved the code a little bit so the button for Concierge Book a call action should now properly display.

Have we moved all the options related functionality to the details page?

Yes, I think so. Did you find a functionality that was removed and is not in the ReportDetailsPage?

Why did we remove this menu? It shows information about held transactions when users open one.

This is a correct observation, I'll add it back.

@parasharrajat PR should be ready for a recheck.

Triggered a test build

@grgia We've found a bug with the Hold promoted action not showing for specific cases in the Details page that is currently on main, I've commited a fix here and included additional test steps for it in the PR description.

We've found a bug with the Hold promoted action not showing for specific cases in the Details page that is currently on main, I've commited a fix here and included additional test steps for it in the PR description.

@parasharrajat Could you please retest this issue, especially the newly added test steps? We want to be sure this works and has been thoroughly tested.

@parasharrajat can we get that retested today?

I wrote them down here actually in the OP: https://github.com/Expensify/App/issues/44573#issue-2379105690

@cdOut Where is the previous PR that you created for #44573

I have not created a PR for it yet.

Yep, works for me!
*Tom Rhys Jones *
Expensify
On Thu, 4 Jul 2024 at 19:35, Rajat @.***> wrote:

@cdOut https://github.com/cdOut Ok great. Then It will be better to add
these changes to that PR and remain focused on the main issue. Currently,
the Hold/Unhold button functionality has issues as I mentioned above which
will be solved when that PR is created. I am happy to review that PR too.
Anyways, I believe these changes are unrelated to the current issue we are
solving in this PR.
What do you say @trjExpensify https://github.com/trjExpensify?
—
Reply to this email directly, view it on GitHub
https://github.com/Expensify/App/pull/44025#issuecomment-2209444124, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AD3246IWJNM4RSGMSVLBD33ZKWIXBAVCNFSM6AAAAABJSQRYSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGQ2DIMJSGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Agreed, I'll move those over there.

@parasharrajat I've reverted those two commits regarding the hold fix, I'll move it to the other issue.

@cdOut @parasharrajat let me know when this is ready for a final test build

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/grgia in version: 9.0.5-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Julesssss in version: 9.0.5-13 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.6-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


feat: add looping, fix some issues with minimal example, update deps

This PR updates the dependencies and adds looping. It also adds files needed for development on NixOS, and commits a Cargo.lock since it helps with reproducibility and is needed for the NixOS dev env to work.
The last 2 commits are cleanup commits, so should use squash while merging it :sweat_smile:

Looks good. Thanks.


Table Scan: Add Row Selection Filtering

Row Selection Skipping
This PR adds the PageIndexEvaluator, which applies an iceberg filter predicate to a parquet Page Index, allowing the fetching into memory and decoding of entire slices of rows within a row group to be skipped if the PageIndexEvaluator determines from the Page Index that they don't match the filter. The PageIndexEvaluator builds a RowSelection that it passes to ParquetRecordBatchStreamBuilder::with_row_selection.
Unlike the row group metadata, the Page Index is not parsed by default when reading in the parquet file metadata. When present, especially for files with many columns, it can be quite large and intensive to parse. In fact, during experiments on the performance testing suite on my other PR, it turns out that often the additional time required to parse the Page Index outweighs the time saved fetching, decoding, and filtering all of the rows within a row group. For this reason, I've kept Row Selection Skipping disabled by default. It can be enabled by calling with_row_selection_enabled(true) when building the scan (There's a corresponding method on the ArrowReaderBuilder if you are using that directly). If you're interested in this feature, you may want to experiment with the write.parquet.page-size-bytes and write.parquet.page-row-limit table settings (which default to 1Mb and 20,000 rows respectively) in order to get optimal performance, as well as the sort settings for your table.
More info can be found in the preceding PR to this one, https://github.com/apache/iceberg-rust/pull/558

@liurenjie1024 / @Xuanwo - PTAL when you get chance, thanks 👍🏼

Back to you @liurenjie1024, thanks for the thorough review - some good spots! 😄


stuck in an upgrade loop

What type of installation are you running?
Desktop
Which Linux OS are you using?
(venv) baggypants@raspberrypi:~/lnxlink-pip $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 12 (bookworm)" NAME="Raspbian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Which version of LNXLink has the issue?
lnxlink                          2024.3.0
Describe the problem
lnxlink seems to be stuck in an upgrade loop for the past day or so. It's trying to upgrade pycairo, when a version of pycairo already exists
(venv) baggypants@raspberrypi:~/lnxlink-pip $ pip3 list installed | grep pycairo
pycairo                          1.26.0

Additional context
No response
Configuration
(venv) baggypants@raspberrypi:~/lnxlink-pip $ cat config.yaml
mqtt:
  prefix: lnxlink
  clientId: pimodelb
  server: <IP_ADDRESS>
  port: 1883
  auth:
    user: homeautomation
    pass:
    tls: false
    keyfile: ''
    certfile: ''
    ca_certs: ''
  discovery:
    enabled: true
  lwt:
    enabled: true
    qos: 1
    retain: true
    connectMsg: 'ON'
    disconnectMsg: 'OFF'
update_interval: 5
modules: null
custom_modules: null
exclude:
- audio_select
- gpu
- screen_onoff
- screenshot
- xdg_open
- webcam
- display
- fullscreen
- camera_used
- media
- notify
- boot_select
- speech_recognition
- idle
- battery
- power_profile
- gpio
- update
settings:
  systemd: null
  gpio:
    inputs: null
    outputs: null
  hotkeys: null
  statistics: https://analyzer.bkbilly.workers.dev
hass_url: null
hass_api: null

Logs
2024-03-01 11:33:22,655 [3212:MainThread.system_monitor.exit_gracefully.69] [INFO]  stopped gracefully
2024-03-01 11:33:22,659 [3212:MainThread.__main__.temp_connection_callback.257] [INFO]  Power Down detected.
2024-03-01 11:33:22,957 [3212:MainThread.__main__.disconnect.241] [INFO]  Disconnected from MQTT.
2024-03-01 11:34:08,161 [2847:MainThread.config_setup.validate_config.81] [INFO]  Added missing configuration option: hass_url
2024-03-01 11:34:08,216 [2847:MainThread.config_setup.validate_config.81] [INFO]  Added missing configuration option: hass_api
2024-03-01 11:34:08,227 [2847:MainThread.config_setup.validate_config.81] [INFO]  Added missing configuration option: settings.hotkeys
2024-03-01 11:34:08,242 [2847:MainThread.config_setup.validate_config.81] [INFO]  Added missing configuration option: settings.statistics
2024-03-01 11:34:09,153 [2847:MainThread.__main__.__init__.45] [INFO]  LNXlink 2024.3.0, Python 3.11.2
2024-03-01 11:34:09,955 [2847:MainThread.helpers.import_install_package.47] [INFO]  Installing 'pycairo>=1.24.0'...
2024-03-01 11:35:09,762 [2909:MainThread.__main__.__init__.45] [INFO]  LNXlink 2024.3.0, Python 3.11.2
2024-03-01 11:35:10,109 [2909:MainThread.helpers.import_install_package.47] [INFO]  Installing 'pycairo>=1.24.0'...
2024-03-01 11:36:11,685 [2971:MainThread.__main__.__init__.45] [INFO]  LNXlink 2024.3.0, Python 3.11.2
2024-03-01 11:36:12,044 [2971:MainThread.helpers.import_install_package.47] [INFO]  Installing 'pycairo>=1.24.0'...
2024-03-01 11:36:43,412 [3002:MainThread.__main__.__init__.45] [INFO]  LNXlink 2024.3.0, Python 3.11.2
2024-03-01 11:36:43,760 [3002:MainThread.helpers.import_install_package.47] [INFO]  Installing 'pycairo>=1.24.0'...
2024-03-01 11:37:14,427 [3033:MainThread.__main__.__init__.45] [INFO]  LNXlink 2024.3.0, Python 3.11.2
2024-03-01 11:37:14,769 [3033:MainThread.helpers.import_install_package.47] [INFO]  Installing 'pycairo>=1.24.0'...
2024-03-01 11:37:45,123 [3064:MainThread.__main__.__init__.45] [INFO]  LNXlink 2024.3.0, Python 3.11.2
2024-03-01 11:37:45,470 [3064:MainThread.helpers.import_install_package.47] [INFO]  Installing 'pycairo>=1.24.0'...
2024-03-01 11:38:16,230 [3095:MainThread.__main__.__init__.45] [INFO]  LNXlink 2024.3.0, Python 3.11.2

looks like this is happening
(venv) baggypants@raspberrypi:~/lnxlink-pip/venv/lib/python3.11/site-packages/lnxlink $ /home/baggypants/lnxlink-pip/venv/bin/lnxlink -c /home/baggypants/lnxlink-pip/config.yaml
INFO:lnxlink:LNXlink 2024.3.0, Python 3.11.2
INFO:lnxlink:Installing 'pycairo>=1.24.0'...
Traceback (most recent call last):
  File "/home/baggypants/lnxlink-pip/venv/bin/lnxlink", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/home/baggypants/lnxlink-pip/venv/lib/python3.11/site-packages/lnxlink/__main__.py", line 528, in main
    monitor_suspend = MonitorSuspend(lnxlink.temp_connection_callback)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/baggypants/lnxlink-pip/venv/lib/python3.11/site-packages/lnxlink/system_monitor.py", line 18, in __init__
    self._requirements()
  File "/home/baggypants/lnxlink-pip/venv/lib/python3.11/site-packages/lnxlink/system_monitor.py", line 61, in _requirements
    "cairo": import_install_package("pycairo", ">=1.24.0", "cairo"),
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/baggypants/lnxlink-pip/venv/lib/python3.11/site-packages/lnxlink/modules/scripts/helpers.py", line 62, in import_install_package
    return __import__(syspackage)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/home/baggypants/lnxlink-pip/venv/lib/python3.11/site-packages/cairo/__init__.py", line 1, in <module>
    from ._cairo import *  # noqa: F401,F403
    ^^^^^^^^^^^^^^^^^^^^^
ImportError: libcairo.so.2: cannot open shared object file: No such file or directory

Fixed by running apt install libcairo2

It seems that it's trying to import the pycairo, but it has a system dependency error so it assumes it's not installed.
I'll fix this logic on the next release to log the error and make it easier to identify the issue.

All the necessary libraries, including the libcairo2-dev exists on the installation script, so I'll consider this fixed.


When the time comes, remove Github address at the mod's JSON to avoid Steam subscribed people receiving updates from Github

Doing that already.


Limit stream.Write() buffer

Currently we buffer up to the client's flow control window in RAM, this could lead to a DOS.

Currently pending:

[ ] Major refactoring to replace streamFrameQueue
[ ] Refactor blocked frame management
[ ] Extract stream map into separate class


[FLINK-19110][docs][python] Flatten current PyFlink documentation structure.

What is the purpose of the change
This pull request flattens the current PyFlink documentation structure.
Brief change log

Flatten current PyFlink documentation structure.

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (docs)

@dianfu Thanks for your review! I have fixed the order of the documents.

@flinkbot approve all
+1 to merge.
BTW, @dianfu we can using the Bot commands during  as much as possible.

@flinkbot approve all

@sunjincheng121 Thanks for the remind. Merging...


amber Smith

sounds good
On Mon, Sep 28, 2020, 5:35 PM Denise Yu<EMAIL_ADDRESS>wrote:

Closed #1739 https://github.com/github/explore/issues/1739.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/github/explore/issues/1739#event-3816564735, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ5CYVDMBGR76DI56JM3KX3SID6R3ANCNFSM4Q67TBAA
.


TypeError: Cannot read properties of undefined (reading '0')

It's very weird because you get a 404 error from ChatGPT API. Maybe try again and it will work or you api key is not valid or the api is blocked by your network.

API key is valid. I pay for API access. Network does not appear to be the issue. Same error occurs on my network. Is the build outdated? Is the endpoint different now?

I resolved it myself. I just changed the model being used. Does not work with the latest.

I have the same issue which model you used please ? @bigjohn0203

I resolved it myself. I just changed the model being used. Does not work with the latest.

@bigjohn0203 what model did you use to fix this issue? Please lmk, thanks.

You can use the extension from the dev branch on which I'm currently working on. The version button should be fixe.
https://github.com/yoannchb-pro/MoodleGPT/tree/dev

but note the dev version is not tested and could present some bugs and still under devlopement


crashing upon modules missing on import

VS crashes if I have a missing module that's not installed on the python environment for my project.
-The debugger stops at the import that is missing.
-Then I get a progress bar that says "debugger operation in progress".
-I click cancel and "Visual Studio has stopped working".
I also get a ton of messages on the output screen before the program loads that weren't there before in PTVS:
"Standard library module invoked user code during import; breakpoints disabled for invoked code."
The latest incarnation of Python in VS has become so unstable that hardly work can be done in this IDE.

Would you have a minimal repro that you could share with us? It could be a timing issue and/or something special about your local variables at the time it breaks.
As for the messages, they were added in https://github.com/Microsoft/PTVS/commit/feefb131801ad6f465dd107be0d74e9a73043b1f#diff-1c2be635c362d7c7db19558ed2d578df maybe @int19h can explain the intention there.

The only way to stop this from recurring is to uncheck Exception Settings->Python Exceptions->ImportError.

So this happens for you even with the simplest of programs, like this 1-line app?
import module_that_doesnt_exist

Yes.  However it occurs on more complicated projects with 50+ files where I am importing custom modules as well as python modules.

@sma202 we have a fix checked in that should suppress most/all of the warning messages in the output window. It will be available first in 15.6 Preview 3.
If you'd like to try it right now, you should be able to overwrite your copy of debugger.py with the latest version at https://github.com/Microsoft/PTVS/blob/master/Python/Product/PythonTools/ptvsd/debugger.py
(search for debugger.py under your microsoft visual studio install directory)
It's possible that these warnings may have been the cause of the "debugger operation in progress" or made it much worse.


Tags or Labels

For grouping of related topics, considering adding a tag or a label (not unlike GitHub Issues) to each cell. This would be a good first step.

I think, this process needs to get automated. So we need establish specific rules for that and that's probably the hardest part: breaking the content into fragments and extract labels from it. 🤔

How exactly are you retrieving the news? From the web? I am not able to locate the code section for that.

I'm loading the RSS or Atom-Feeds based on the url written down in the data.json.
The feeds are the parsed in the file render-feeds.php starting in line 31.
But beware, I'm currently in the process of restructuring the php-files and splitting it into smaller chunks. My goal is to implement some sort of api, so one could attach different frontends to it.

Okay so once you finish, you can inform me here. I might take the task up for assigning tags.
Whether I will be able to do it or not, is doubtful though. XD.


PMO: Guide doesn't explain how to get Android set up

Needs more explanation, first done you run donejs build cordova you get this message:
ERROR: Error: Please install Android target: "android-22".

Hint: Open the SDK manager by running: C:\Users\Matthew\AppData\Local\Android\sdk\
tools\android.BAT
You will require:
1. "SDK Platform" for android-22
2. "Android SDK Platform-tools (latest)
3. "Android SDK Build-tools" (latest)

Error: cmd: Command failed with exit code 2

I'm thinking we can put this in the Setting Up section and link to it.

Another error:
1. Download desired System Image by running: C:\Users\Matthew\AppData\Local\Androi
d\sdk\tools\android.BAT sdk
2. Create an AVD by running: C:\Users\Matthew\AppData\Local\Android\sdk\tools\andr
oid.BAT avd
HINT: For a faster emulator, use an Intel System Image and install the HAXM device
 driver


Wonky Shapes

So the reason the shapes are wonky is that they are either all lines or quadratic bezier curves.
https://github.com/opentypejs/opentype.js/blob/c37fcdfbd89c1bd0aac1cecb2b287dfb7d00cee0/src/tables/glyf.js#L214
Here's MIT code that does that correctly. I ran into a font that would have like 3 OFF_CURVE points in a row and it rendered completely mangled. I checked OpenType.js.org  and the had a glyph checker and it had different numbers of control points and resulting points. I hunted down the code from there.
It's a little weird but it fixes all the wonky text.

Less wonky inner-p contour.

Closed in https://github.com/johnbentcope/vpype-ttf/pull/2


We should persist view state (zoom, pan, force simulation state) when switching between tabs

We expect to switch to using the data explorer.


Transformation name is not shown in the control plane

Summary

Steps to reproduce

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Possible fixes

This is :bug: Bug Report

Current design is not showing transformer for built-in one. GTM is another kind of builtin even it’s a third party transformer.

Please check if there's still an issue with the latest version.


Add a statement

In the project named How-To-Ask-Questions-The-Smart-Way, the author wish us add 'This guide does not provide actual support services for this project!' near by where we have used his project's url.
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Hi @edgexie please follow the commit guide line and merge the same commit into one pr
https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit


Fix numerical diffusion in uniformMesh converter

Description
Mapping anything from a non-uniform assembly to a uniform assembly and then back will cause numerical diffusion of that value. This could be a block parameter (like mgFlux, detailedDpa, etc.) or number densities. This has been observed for neutron flux while using the nonUniformAssemFlags setting on control rods, and for detailedDpa when using the detailedAxialExpansion setting.
This commit deals with the issue of block parameters being mapped back and forth. The number density issue has already been addressed for the nonUniformAssemFlags case, but it seems to still be present for the detailedAxialExpansion case.
The selection of which parameters to map is very much up for discussion. Please review the categories that have been set for REACTOR_PARAMS_TO_MAP and BLOCK_PARAMS_TO_MAP, and the _setParamsToUpdate method for both neutron and gamma transport. Please leave comments on any parameters you think are missing or should be changed. My approach to these selections is summarized below:

First and foremost, we want to ensure that we are not mapping any parameters both "into" and "out of" the uniform mesh assembly, because that will cause numerical diffusion.
We also want to make sure that when a new parameter value is generated on the uniform mesh by some physics solver, that parameter is mapped back to the uniform mesh.
We should always map number densities "into" the uniform assembly but never out of it. Other parameters (like power, temperature, etc.) generally don't need to be mapped in unless they are required to set up the input for the physics kernel. It will generally be harmless to include these additional parameters so long as they are not re-mapped back to the non-uniform assembly on the way out.

Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify that the new/changed code works.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[ ] The release notes (location doc/release/0.X.rst) are up-to-date with any bug fixes or new features.
[ ] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in setup.py.

Not requesting review yet, just tagging a few interested parties @keckler @Nebbychadnezzar

@Nebbychadnezzar can't select you as a reviewer but I wanted to get your eyes on this as well.

After this is merged, though, there is still work to do in our internal plugins to move the application/calculation of cumulative parameters outside of the geometry conversion entry/exit. For instance, I can say for certain that detailedDpaRate is calculated right now when the geometry is still converted. Likely the same for many of the cumulative parameters. So we'll have to hunt all of those down and update them, if necessary.

I am aware of detailedDpa, and that looks like it's going to somewhat difficult to address. I don't know of anything else in the downstream plugins, though.

For cumulative parameters that are being calculated within the framework itself, I would argue it might make sense to update those as part of this PR (if any of them exist).

I don't know of any parameter accumulation within the framework itself that needs to be updated. The most obvious cumulative parameter is depletion/burnup, and those are calculated on the non-uniform assembly. Aside from depletion/residence/burnup, fluence, DPA (mentioned above), I can't think of any other obvious cumulative parameters.

I don't know of any parameter accumulation within the framework itself that needs to be updated. The most obvious cumulative parameter is depletion/burnup, and those are calculated on the non-uniform assembly. Aside from depletion/residence/burnup, fluence, DPA (mentioned above), I can't think of any other obvious cumulative parameters.

I agree with this sentiment. I just scanned through the framework parameters and couldn't find any which are cumulative that would also be mapped in the first place. There are some things in the fuelPerformance package that are cumulative (gasReleaseFraction, bondRemoved, cladWastage, totalCladStrain), but I guess those won't be mapped in the first place because they don't satisfy the category qualifications.
So we're probably good there!

I pulled this PR into my ARMI app, reran some extensive calculations, and then looked at the calculated DPAs.
I can confirm that this PR resolves the issues I was previously having with DPA possibly decreasing as time increases. Obviously that was non-physical, and these changes resolve that such that we are now getting physically-possible results for DPA.
I can also add another data point to add confidence to this change. The model that I ran is a benchmark of real reactor operations, and I was previously getting anomalously low reactivities in later cycles. I had suspected that this was due to the numerical diffusion of the uniform mesh generator, and it turns out that with this fix, core reactivities line up much more closely than before.
So in my book, the changes in this PR are a resounding success. I approve!

#985

I pulled this PR into my ARMI app, reran some extensive calculations, and then looked at the calculated DPAs.

So... above you were concerned that "there is still work to do in our internal plugins to move the application/calculation of cumulative parameters outside of the geometry conversion entry/exit".
Are you concerns with that over?

Are you concerns with that over?

Yes, I am sufficiently convinced after both looking though our internal code and testing this PR that we are in the clear on that concern.

I'm not sure why, but I'm getting an error in JOYO that I thought I fixed previously. I looked to make sure my previous changes were still there and they are. I don't know if any of you have seen this error before:
File "\albert\home\mhuang\site-packages\nala_main_.py", line 26, in main
code = ArmiCLI().run()
File "\albert\home\mhuang\site-packages\framework\armi\cli_init_.py", line 202, in run
return self.executeCommand(args.command, args.args)
File "\albert\home\mhuang\site-packages\framework\armi\cli_init_.py", line 231, in executeCommand
return cmd.invoke()
File "\albert\home\mhuang\site-packages\framework\armi\cli\run.py", line 33, in invoke
inputCase.run()
File "\albert\home\mhuang\site-packages\framework\armi\cases\case.py", line 367, in run
o.operate()
File "\albert\home\mhuang\site-packages\framework\armi\operators\operatorMPI.py", line 74, in operate
Operator.operate(self)
File "\albert\home\mhuang\site-packages\framework\armi\operators\operator.py", line 320, in operate
self._mainOperate()
File "\albert\home\mhuang\site-packages\framework\armi\operators\operator.py", line 329, in _mainOperate
keepGoing = self._cycleLoop(cycle, startingCycle)
File "\albert\home\mhuang\site-packages\framework\armi\operators\operator.py", line 345, in _cycleLoop
halt = self.interactAllBOC(self.r.p.cycle)
File "\albert\home\mhuang\site-packages\framework\armi\operators\operator.py", line 552, in interactAllBOC
return self._interactAll("BOC", activeInterfaces, cycle)
File "\albert\home\mhuang\site-packages\framework\armi\operators\operator.py", line 423, in _interactAll
halt = halt or interactMethod(*args)
File "\albert\home\mhuang\site-packages\framework\armi\utils\codeTiming.py", line 55, in time_wrapper
return_value = func(*args, **kwargs)
File "\albert\home\mhuang\site-packages\framework\armi\physics\neutronics\latticePhysics\latticePhysicsInterface.py", line 108, in interactBOC
self.updateXSLibrary(cycle)
File "\albert\home\mhuang\site-packages\framework\armi\physics\neutronics\latticePhysics\latticePhysicsInterface.py", line 129, in updateXSLibrary
blockList=representativeBlocks, xsLibrarySuffix=self._getSuffix(cycle)
File "\albert\home\mhuang\site-packages\plugins\terrapower-partisn\terrapower\physics\neutronics\partisn\mc2PartisnInterface.py", line 78, in computeCrossSections
executer.run()
File "\albert\home\mhuang\site-packages\plugins\terrapower-partisn\terrapower\physics\neutronics\partisn\partisnExecuters.py", line 417, in run
output = globalFluxInterface.GlobalFluxExecuter.run(self)
File "\albert\home\mhuang\site-packages\framework\armi\physics\executers.py", line 187, in run
self._performGeometryTransformations()
File "\albert\home\mhuang\site-packages\plugins\terrapower-partisn\terrapower\physics\neutronics\partisn\mc2PartisnExecuters.py", line 88, in _performGeometryTransformations
self._computeFineGroupXS()
File "\albert\home\mhuang\site-packages\plugins\terrapower-partisn\terrapower\physics\neutronics\partisn\mc2PartisnExecuters.py", line 99, in _computeFineGroupXS
blockList=self._xsgm.representativeBlocks.values()
File "\albert\home\mhuang\site-packages\plugins\terrapower-partisn\terrapower\physics\neutronics\partisn\mc2PartisnInterface.py", line 117, in computeFineGroupXs
purgeFP=False,
File "\albert\home\mhuang\site-packages\plugins\terrapower-mc2\terrapower\physics\neutronics\mc2\mc2Interface.py", line 236, in _generateXsLibrary
baseList, xsLibrarySuffix, blockList, writers
File "\albert\home\mhuang\site-packages\framework\armi\physics\neutronics\latticePhysics\latticePhysicsInterface.py", line 300, in generateLatticePhysicsInputs
fromWriter = writer.write()
File "\albert\home\mhuang\site-packages\plugins\terrapower-mc2\terrapower\physics\neutronics\mc2\mc2Writers.py", line 411, in write
self._writeComposition(f)
File "\albert\home\mhuang\site-packages\plugins\terrapower-mc2\terrapower\physics\neutronics\mc2\mc2Writers.py", line 601, in _writeComposition
self._writeSingleComposition(fileObj, compNumber, component)
File "\albert\home\mhuang\site-packages\plugins\terrapower-mc2\terrapower\physics\neutronics\mc2\mc2Writers.py", line 606, in _writeSingleComposition
allNuclides = self._getAllNuclideObjects(component)
File "\albert\home\mhuang\site-packages\framework\armi\physics\neutronics\latticePhysics\latticePhysicsWriter.py", line 187, in _getAllNuclideObjects
nucs, fissProds = self._getAllNuclidesByCategory(component)
File "\albert\home\mhuang\site-packages\framework\armi\physics\neutronics\latticePhysics\latticePhysicsWriter.py", line 204, in _getAllNuclidesByCategory
dfpDensities = self._getDetailedFPDensities()
File "\albert\home\mhuang\site-packages\framework\armi\physics\neutronics\latticePhysics\latticePhysicsWriter.py", line 370, in _getDetailedFPDensities
dfpDensitiesByName = lfpCollection.getNumberDensities(self.block)
AttributeError: 'NoneType' object has no attribute 'getNumberDensities'

@LMikeH I'll message you offline.


Default read permission for the clusters does not include secrets or nodes

Should be able to list secrets and should be able to access the nodes (oc debug node/x) using default permissions. This is not possible with the current permissions

Need to give read permission for secrets, and access to nodes.  This can be done with a job, like was done with the techzone cluster.
Needs to be added to automated for all dev/test clusters going forward, but immediate need it for the cp4d cluster (can be applied manually to this cluster).


Advanced Paste - Paste as RGB

Description of the new feature / enhancement
Advanced Paste should allow for hex color values to be pasted into the default Windows color picker. The hex value would be converted to three separate pastes into the three separate RGB input boxes. User would paste into the "R" box and the "G" and "B" boxes would subsequently be filled.
Scenario when this would be used?
This would be useful for any application that still restricts users to an RGB color choice. It's a inconvenience to try to remember the three RGB values selected from the color picker, and it would be much more useful to allow users to just paste it in.
Supporting information
This is a problem that doesn't seem to have an easy solution. I found that most forum posts now point to a piece of deprecated software called "Jovian," which was able to override the default behavior of opening up the Windows API ChooseColor function.

This actually would be hit or miss behavior wise. Color picker can do these style conversions too as FYI

My thing is having one system
to get focus on 3 text boxes we don’t control, not a predictable outcome for us


Entering and leaving directory statements are not processed, resulting in incorrect paths for the problemMatcher

VSCode Version: 1.12
OS Version: Mac OS 10.12.5 & Ubuntu 16.04
Steps to Reproduce:

download e.g. bash source code from GitHub
In top source dir mkdir build; cd build; ../configure; make
If the make is done from within studio code, it can be seen that some paths to warnings are resolved properly, but others, to files in sub projects not.
All reported paths are relative to the current working directory, however this directory changes during the build process. This change of directory is reported with statements like:
make[1]: Leaving directory '/media/psf/Home/GitHub/bash/bash-4.4/build/builtins'
make[1]: Entering directory '/media/psf/Home/GitHub/bash/bash-4.4/build/support'
In this kind of environment which is not that uncommon, it seems kind of impossible to get the problem matcher working properly. Depending on the area you are working on you have to edit the tasks file to get a correct link to the file.
To complicate things more the leaving statements pops back to the previous one, so if you parse the entering and leaving statements, it is not stateless. You have to keep track of a stack of directories.

Dups https://github.com/Microsoft/vscode/issues/11663


added code for faqs screen

Related Issue

Fixes #38  .

Proposed Changes

Added pdf of FAQs
used advance pdf viewer to display pdf
vertical scrolling

Checklist

[x] Tested
[x] No Conflicts
[x] Change In Code
[ ] Change In Documentation

@anotherwebguy Can you follow the linting rules and sort out the warning in the Problems section in your terminal. Also, you should remove the Single Child Scroll View, as the Settings screens will be redesigned soon.

@anotherwebguy Can you follow the linting rules and sort out the warning in the Problems section in your terminal. Also, you should remove the Single Child Scroll View, as the Settings screens will be redesigned soon.

I added the singlechild scroll view since it was throwing renderflex error on my screen

@anotherwebguy Can you follow the linting rules and sort out the warning in the Problems section in your terminal. Also, you should remove the Single Child Scroll View, as the Settings screens will be redesigned soon.

I'll remove it though

@anotherwebguy Can you follow the linting rules and sort out the warning in the Problems section in your terminal. Also, you should remove the Single Child Scroll View, as the Settings screens will be redesigned soon.

I added the singlechild scroll view since it was throwing renderflex error on my screen

@anotherwebguy Can you follow the linting rules and sort out the warning in the Problems section in your terminal. Also, you should remove the Single Child Scroll View, as the Settings screens will be redesigned soon.

done with all the changes u asked for @himanshusharma89


[repl] Cannot type double quotes in the interpreter

Using firefox 31.0 for Ubuntu, I cannot type the readFile "/welcome" example on http://new-www.haskell.org/, because double I cannot enter double quotes.

Same problem here on macOS. Same thing on tryhaskell.org


OAdd thread-safe collection set

Description of the Change

Add thread-safe set which operates with collections.
Add tests for it

Benefits
One step closer to BFT-Iroha
Possible Drawbacks
Absent concurrent tests

Would be nice to add a test with concurrency emulation (e.g waits on cv responses)


ARROW-7801: [R][CI] Add lint and doc GitHub Action workflows

#6411 tried to do this work automatically, but some were uncomfortable with that; this version instead is triggered by PR comment.
Currently implemented:

R documentation (roxygen2, updating r/man/*.Rd based on docstrings in r/R/*.R)
clang-format on changes to cpp/src or r/src
cmake_format is currently disabled because I didn't feel like fighting further with python versions and environments; in https://github.com/nealrichardson/arrow/runs/590355718?check_suite_focus=true#step:5:34 you can see that it pip installs cmake_format but then in the next line can't find cmake_format :shrug:

To trigger the build, add a comment with the message "autotune" (seemed appropriate since this is using computers to make sure our code stays in harmony). By default it will check for which files changed and only run the relevant tasks, but if you comment "autotune everything" it will run everything.
Since issue_comment workflows are only run off the master branch, I tested this by merging these commits to master on my fork and triggering it on a PR there. See e.g. https://github.com/nealrichardson/arrow/pull/2#issuecomment-613138356

Having this as a developer opt-in sounds good to me.

autotune, are you ready?

@nealrichardson shouldn't my previous comment trigger something?

@fsaintjacques no, it won't, not until this is merged. The PR description says:

Since issue_comment workflows are only run off the master branch, I tested this by merging these commits to master on my fork and triggering it on a PR there. See e.g. nealrichardson#2 (comment)


(Issue 1260 / Truncate Cassandra Logs) Truncate cassandra logs content to reasonable limits

Minor thing, feel free to merge afterwards

@simong you caught me in the middle of cleanup, I did a little bit more than adding logs, can you have another look?


[BUG] Fail to enable Out-of-Band Access on host

Description
Successful enabling harvester-seeder addon, but fail to enable on node.
Environment

Harvester

Version: v1.2.0-rc5
Profile: QEMU/KVM, 2 nodes (24C/128G/1.5T)
ui-source: Auto

To Reproduce

Login as admin
Go to "Advanced" -> "Addon" -> "harvester-seeder" -> Enable

Go to "Hosts" -> select host -> "Edit Config" -> "Out-of-Band Access" -> "Enabled" -> "Save"
${~~~\color{red}\textsf{X, Error "Cannot read properties of undefined (reading 'linkFor')"}}$

Expected Behavior
With harvester-seeder addon enabled, Out-of-Band Access should be able to enable on node.
Support Bundle
supportbundle_FailToEnableOOBA_2023-08-07T06-43-47Z.zip
Note

I have added a banner to fixed the issues, but I also found another trick issue: The /v1/harvester/subscribe WebSocket sometimes can not get metal.harvesterhci.io.inventory of resource.create message, which will make my changes stuck in "Waiting for "inventories.metal.harvesterhci.io" to be ready". But sometimes I can get the message from WebSocket, here are my recordings:
This recording works as expected
https://github.com/harvester/harvester/assets/18737885/4c5c1e29-7a85-45fe-ad46-c73ee629df36
This recording only receives a message from /v1/subscribe
https://github.com/harvester/harvester/assets/18737885/339be3ce-c6c3-4a49-8a9d-59602f404446
This recording can not receive a message both from /v1/subscribe and /v1/harvester/subscribe. But the PCI device work as expected.
https://github.com/harvester/harvester/assets/18737885/e0552bd9-728a-4aa4-aea3-8dd9e6d1c128
Reproduce Steps:

Install a v1.2.0-rc5 Harvester
Login and change the ui-index to my private ui-index: https://harvester-dev.oss-cn-hangzhou.aliyuncs.com/bot-dashboard/n313893254-fix-seeder/index.html (optional, if not replace, the error will show as https://github.com/harvester/harvester/issues/4387#issue-1838795500)
Take a snapshot for this Harvester (optional, easy to debug)
Go to addons and enable harvester-seeder
Check the WebSocket message or host detail page
Restore the snapshot if you need to reproduce it again (optional)

Hi @n313893254 ,
Per discussed, enablement works fine in v1.2.0-rc4 and have this issue since v1.2.0-rc5 after fresh install, or more precisely, user first time enable harvester-seeder addon.
Perhaps we can check whether there is any modification about websocket in between.
Following are my tests in v1.2-57b26312-head and v1.2.0-rc4
Note that refresh page is a workaround to show the enable form, may be a clue too.
v1.2.0-rc5 and v1.2-57b26312-head :x: (Workaround: Refresh)
https://github.com/harvester/harvester/assets/2773781/91666af9-42b7-4d85-a495-12fc3a4526b6
v1.2.0-rc4 :heavy_check_mark:
https://github.com/harvester/harvester/assets/2773781/c62fbbe2-0716-44ba-9e05-9cc7f2645944

Per discussed, enablement works fine in v1.2.0-rc4 and have this issue since v1.2.0-rc5 after fresh install,

@albinsun This issue can reproduce in v1.2.0-rc4, the root cause is the  Websocket issue, I can not totally fix it without refreshing the page, so I just added the banner to info user.

Note
Due to this issue, it takes a few more tries to verify this feature
The expected behavior will look like this recording:
https://github.com/harvester/harvester/assets/18737885/4c5c1e29-7a85-45fe-ad46-c73ee629df36

Workaround: "refresh page"
Close and trace in https://github.com/harvester/harvester/issues/4412
If this issue is not going to fix in v1.2.0, it's better to take action (e.g. doc) to let user know the workaround.


[Feature Request] Timeout during execution of the task on cluster manager node

Is your feature request related to a problem? Please describe
Many cluster manager tasks generated from user has the timeout like create-index/put-mapping/update-setting/etc. Today this task will timeout only if they are in pending task queue of cluster manager node, i.e. if tasks is waiting in queue for that timeout period then only it will be timed out and throw process_cluster_event_timeout_exception.
If task is picked up by cluster manager node then it never times out even if it take infinite time. This will cause subsequent tasks to be timeout. This can impact overall cluster resiliency as well as cluster manager will not be execute critical task like node-join/left until the task in execution is not completed.
Recently we have faced similar issue where one custom deciders was taking too long time and task execution was taking very long time and it didn't timeout. All subsequent tasks were getting timed out because of these and we were not able to do any admin operation like updating cluster setting/new index creation/deletion/etc.
Describe the solution you'd like
Cluster manager node should timeout the task even if it is in execution phase and not only during waiting period in pending task queue. We can evaluate if we want to create  any separate timeout for this or we just use the timeout of particular task during execution phase as well.
Related component
Cluster Manager
Describe alternatives you've considered
No response
Additional context
No response

[Triage - attendees 1 2]
@dhwanilpatel Thanks for filing this issue, please feel free to submit a pull request.


[SPARK-13266][SQL] None read/writer options were not transalated to "null"

What changes were proposed in this pull request?
In Python, the option and options method of DataFrameReader and DataFrameWriter were sending the string "None" instead of null when passed None, therefore making it impossible to send an actual null. This fixes that problem.
This is based on #11305 from @mathieulongtin.
How was this patch tested?
Added test to readwriter.py.

Test build #56214 has started for PR 12494 at commit 5435032.

Test build #56214 has finished for PR 12494 at commit 5435032.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56214/
Test PASSed.

cc @rxin

cc @davies for the python changes.

Test build #56341 has started for PR 12494 at commit dfc79af.

Test build #56341 has finished for PR 12494 at commit dfc79af.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56341/
Test PASSed.

https://github.com/databricks/spark-csv/blob/master/src/main/scala/com/databricks/spark/csv/DefaultSource.scala#L58
If the "quote" option is not set, it defaults to a double quote. The only way to set it to disable quoting, is to set the option to null. Spark-csv raises an error if you try to set quote to an empty string. This was working with my patch by itself, I have been using that.

Looks databricks spark-csv handles input parameters quite different spark internal csv data source...

@viirya databricks CSV library and internal CSV are not necessarily the same but @mathieulongtin is right. quote does not accept null for both.

@HyukjinKwon ok. make thing clearer...
@mathieulongtin wants to use null as option value in spark-csv from databricks. So he did the PR to allow passing None from python to Scala, instead of string "None".
The passed None will be null in Scala side.
However, passing null as option value in current codes will cause null exception. Because Spark CSV data source does not handle null.
In this PR, I filter nulls and disallow using null as option value. It is not @mathieulongtin wants in his original PR.

@viirya Ah, thanks! however, I am a bit worried if disallowing null as a value in options is correct. I don't want to be kind of so picky but I think it might not be guaranteed that every option does not take null as a value for all.
Maybe in some external datasources or future options, I think there might be some cases that setting null as an option and not setting are not the same.

@HyukjinKwon yea thanks for comment.
I will remove the null check then. And I should make change to CSVOption to avoid the null exception.

@viirya Thanks for bearing with me.

Test build #56500 has started for PR 12494 at commit 9ab2c01.

@viirya @davies  Do you mind if I open a new JIRA and PR to deal with null in options for JSON and CSV data sources after this one is merged?

@HyukjinKwon I am ok. :)

Either way is good to me.

Filed in SPARK-14800. Let me work on this if this one is merged.

Test build #56500 has finished for PR 12494 at commit 9ab2c01.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56500/
Test FAILed.

Merged build finished. Test FAILed.

Looks like the failure is related to recent changes in Hive commands.

retest this please.

Test build #56515 has started for PR 12494 at commit 9ab2c01.

Test build #56515 has finished for PR 12494 at commit 9ab2c01.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56515/
Test FAILed.

Whether null is acceptable for a given data source's options is beside the point. If I give bad options, I should get an exception, the same way I get an exception if I give any other wrong value. For example, I get an exception if I set the quote to "XYZ" with the csv datasource because it only accepts a single character.
The PR I submitted was about allowing Python to do the same thing as Scala.
This brings one question, can you specify NULL in SQL, like this:
CREATE TABLE cars
USING com.databricks.spark.csv
OPTIONS (path "cars.csv", header "true", inferSchema "true", quote NULL)

If not, then we should disable it entirely so that SQL, Scala and Python all can do the same thing.

@mathieulongtin
I think it might be more sensible that SQL in OPTIONS clause supports  null and some other types such as long, double and boolean. It looks (if I got this correctly) there is a mention about options in 23.3  Extensions and options and I think it is okay to provide other types as arguments just like Microsoft SQL (although I found Spark's SQL more like MySQL).
Currently, Scala API supports to take options with the types, Long, Double and Boolean and Python API also supports other types. I think in this way we can support data sources in a consistent way.

@viirya @davies Could I ask your thought on this? I can make a JIRA for this.

@HyukjinKwon Sounds good to me

@HyukjinKwon yea. I have no problem with it.

retest this please.

Test build #56649 has started for PR 12494 at commit 9ab2c01.

Filed in SPARK-14839. I might be able to give a shot if nobody gives a try.

Test build #56649 has finished for PR 12494 at commit 9ab2c01.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56649/
Test PASSed.

@davies any more comments regarding this pr?

Test build #56676 has started for PR 12494 at commit d82869c.

Test build #56676 has finished for PR 12494 at commit d82869c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56676/
Test PASSed.

cc @davies Test is moved as you suggested.