Rewrite Test 1

Setup a test case in a style that allows us to succinctly test LDS and
CDS on the same behaviour.  This required refactoring our runner
functions to work for any service, and to write new step functions to
take advantage of the new way we are passing in parameters.
The new test is designed to fail on 2 of the 6 cases, to assure that a
test can fail but the test suite itself can continue to run.
Running the Test
1. Setup Test Target
In one terminal window, from the root of this repo, invoke:
go run example/go-control-plane/main/main.go

You should see:
{timestamp} management server listening on 18000
{timestamp} Testsuite Adapter listening on 17000

2. Run Test Suite
In a new terminal window, from the root of this repo, invoke:
go run . -t "@wip"

This will run our test 6 times, and it should fail twice.
Optionally you can run:
go run . -t "@wip" --debug # verbose logging through test
go run . # run the whole suite

Note:
When you look at the code in entirety, you'll see there are some overly similar functions.  This is to ensure that all the previous steps can still run, and to keep this PR as small as possible.  When this work gets merged, I will refactor and delete those now deprecated steps.

README.md / Run the examples block:
Update to use examples folder:
go run examples/go-control-plane/main/main.go


V1.5 Bugfix of oscillator amplitude

While creating 'Realms' for Robert Pabst (Cinematic Laboratory), I found out that I interpreted the oscillator amplitude in CSound incorrectly. The value isn't a factor, but a fixed value. Probably not audible (amplitude is usually close to '1' when using wave tables), still a bugfix.
Changes:

Using original amplitude of wavetable file.
Code clean-up (removed old commented code).
Added "First Patch 'initial settings'" instructions to readme.

Oooh excited for more info on Realms. I love that you’re pushing the nebulae platform further ❤

Hopefully we get another sweet Cinematic Laboratory video

Looks great! 👍


判定Timezone是否需要转义

判定Timezone是否需要转义

Codecov Report
Base: 79.63% // Head: 79.60% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (22077a5) compared to base (a746794).
Patch coverage: 0.00% of modified lines in pull request are covered.

:exclamation: Current head 22077a5 differs from pull request most recent head 895fc0b. Consider uploading reports for the commit 895fc0b to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2412      +/-   ##
==========================================
- Coverage   79.63%   79.60%   -0.03%
==========================================
  Files         595      598       +3
  Lines       49375    49686     +311
==========================================
+ Hits        39318    39551     +233
- Misses       8077     8136      +59
- Partials     1980     1999      +19

Flag
Coverage Δ

go-1.15-386
79.63% <0.00%> (+0.01%)
:arrow_up:

go-1.15-amd64
79.62% <0.00%> (+0.05%)
:arrow_up:

go-1.16-386
79.62% <0.00%> (+0.04%)
:arrow_up:

go-1.16-amd64
79.64% <0.00%> (+0.02%)
:arrow_up:

go-1.17-386
79.64% <0.00%> (?)

go-1.17-amd64
79.61% <0.00%> (?)

go-1.18-386
79.54% <0.00%> (?)

go-1.18-amd64
79.56% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

contrib/drivers/dm/dm.go
73.13% <0.00%> (-0.55%)
:arrow_down:

contrib/drivers/mysql/mysql.go
68.00% <0.00%> (-1.39%)
:arrow_down:

internal/empty/empty.go
72.51% <0.00%> (-2.30%)
:arrow_down:

util/gvalid/gvalid_validator_check_struct.go
83.53% <0.00%> (-1.51%)
:arrow_down:

os/gstructs/gstructs_field.go
90.27% <0.00%> (-1.39%)
:arrow_down:

util/gconv/gconv_struct.go
81.54% <0.00%> (-0.42%)
:arrow_down:

database/gdb/gdb_core_underlying.go
73.31% <0.00%> (-0.26%)
:arrow_down:

encoding/gyaml/gyaml.go
87.23% <0.00%> (ø)

os/gtimer/gtimer_timer.go
100.00% <0.00%> (ø)

contrib/config/kubecm/kubecm.go
38.38% <0.00%> (ø)

... and 9 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


fix: flink account cannot get resource "services" in API group

What is the purpose of the change
When I remotely connected to the Flink cluster using local SQL client, I encountered an error while submitting an SQL statement:
[ERROR] Could not execute SQL statement. Reason:
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://<IP_ADDRESS>/api/v1/namespaces/flink-operator/services/basic-example-rest. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. services "basic-example-rest" is forbidden: User "system:serviceaccount:flink-operator:flink" cannot get resource "services" in API group "" in the namespace "flink-operator".

this error indicating that Flink account lacks permission to operate services resource, missing permissions should be added to the Flink account in chart templates.

Hi @huaxk! Connecting to a cluster managed by the Kubernetes Operator is an antipattern in its current form, because the operator will not be aware of the jobs you submit this way. Only jobs that are represented by the Kubernetes custom resource (as of today FlinkDeployment or FlinkSessionJob) can be managed by the operator. Adding an SQL gateway type functionality is interesting, but it would require a larger reconsideration. You can run SQL jobs directly via the operator as presented in this example.

Yes, I see.

Hi @mbalassi ! Is it possible to get this information added to the official documentation of the flink-kubernetes-operator?
I was stuck on the same issue for very long, and later updated the flink role to give access to "service" resource; only to find this discussion and realize that I created an antipattern.
It'd be very helpful if this was available in the main document itself. I can help in that documentation update if needed. Thank you!

@prakash-42 You would greatly help us out here if you could open a PR against the this repo with the documentation changes 🙏

Thanks @mxm  ! I have a few questions before I can start working on the PR, hopefully this is the right place to ask.

Where should I put this guide (new document) in the project structure? I suggest that we create a folder by the name "examples" (in the docs folder), and create this single guide in there. We can later add more examples to the folder. What do you think?

I will copy a lot of content from the readme of the flink-sql-runner-example, with maybe a few additions. Is there a way to directly add that file as a page instead of duplicating content?

I would add it on this page: https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/custom-resource/overview/ Actually, the examples linked above are already linked at the bottom of the page. Maybe we can add a section which expands a little bit on the concept.

Sorry to bug you again @mxm , but where is the place to submit bugs/ask questions for the flink operator? (The JIRA project doesn't have public signup, are the flink mailing lists active?)
I tried to use the flink-sql-runner-example before writing documentation about it, and stumbled into two issues:

The regex for SET statement is not flexible. (not a blocker)
The regex for SET statement enforces that the user provides single quote (') around the key and value. Also there must be space on both sides of the equals (=)

Any text present between backticks(`) is getting lost (unable to debug the reason)
When I try to submit a script that uses backticks around field names, the text between backticks isn't read by the code. (FileUtils.readFileUtf8 is responsible for this, I added a log). (I used flink:1.17 as my base image). I'm not able to reproduce this behavior locally, only happens when I package the job and deploy it in our EKS cluster.

Here's a portion of SQL script I used (I printed the full script to console, even the content b/w backticks from the comments was gone)
SET 'execution.checkpointing.interval' = '30s';
SET 'pipeline.name' = 'MyFlinkJob';

-- some comment text in `back ticks`
-- some more text in ```back ticks x3```

CREATE TABLE Library_Book_Source (
  database_name STRING METADATA VIRTUAL,
  table_name STRING METADATA VIRTUAL,
  `ID` INT NOT NULL,
  Title VARCHAR(255),
  `Price` VARCHAR(50),
  PRIMARY KEY (`ID`) NOT ENFORCED
) WITH (
  'connector' = 'mysql-cdc',
  'hostname' = 'DB_HOST',
  'port' = '3306',
  'username' = 'username',
  'password' = 'password',
  'database-name' = 'Library',
  'table-name' = 'Book',
  'jdbc.properties.useSSL' = 'false'
);

Due to these problems, I'm not sure if this example is production ready and whether or not it should be added in our documentation.

@prakash-42 You can request a JIRA account here: https://selfserve.apache.org/jira-account.html Let me know the username once you have requested an account, I can then approve your request.

Hi @mxm ! I have submitted the request for account with username prakash.tiwari

Great! The request is approved 👍


Add Class prop

Is your feature request related to a problem? Please describe.
I am currently using the word add in, when I hover over the button, it changes its background to white and there is no prop to handle hover
Describe the solution you'd like
instead of three different prop( Action button, Action Button Bg, Action Button Border) on any item i.e. Action we can just use a prop class which will cater all the things.
Additional context
I would like to work on this behaviour

I believe this issue is tracking a solution to this problem. Does that sound accurate?

yes, closing this issue


Delete rows from TSV7(TN,TWLs)

click minus to delete a row
Popup confirmation like it shows in tCC

For tWLs, the add/delete buttons must be for each row, since the card displays the list of words.

@jincypjose @theNerd247 @kintsoogi Here are some various screenshots of different UIs for adding and removing rows.  The first one (material-ui) is what I was trying to describe yesterday.  After that are just a few of the seemingly infinite ways people have done it. What's your pick?

https://mui.com/material-ui/react-table/

https://material-table.com/#/docs/features/actions

https://github.com/RXNT/react-json-schema-form-extras/issues/98

https://stackoverflow.com/questions/51095527/delete-dynamically-added-table-row-react-js

https://www.youtube.com/watch?v=MINQoCSBmds

I really like (2). The icons are self explanatory and as someone who reads left to right it flows well.

(1) is great if the number of actions per row is >= 3 (as the icons would take up to much real-estate)

I too liked 1 and 2 both makes sense.

We will do #3 and put both add and delete button in an actions column

@elsylambert @danielklapp This issue is in the latest GWE develop build v2.1.0 build f85dc07

Private Zenhub Image

Verified everything listed on the test instructions. Looks good to me and tested with v2.1.0 build f85dc07 QA.

@elsylambert @danielklapp I was able to reproduce the problem I saw before:
https://github.com/unfoldingWord/gateway-edit/assets/14238574/f34ccc91-df8f-442c-a0f1-e889ffd0af2f

@kintsoogi - It seems related to adding the tN to the end of the book.  It's throwing an exception.

Moved the bug to #592


fix(atomic): managed focus for breadbox show more/less

https://coveord.atlassian.net/browse/KIT-1724

when doing show more/less the focus state is kind of weird

vs the normal one

when doing show more/less the focus state is kind of weird

vs the normal one

I'll fix that.


Update supportedlanguages.md

Added newly supported Indian languages - Gujarati, Tamil, and Telugu.

@rrmehta : Thanks for your contribution! The author, @zhouwangzw, has been notified to review your proposed change.

@erhopf
Please check this PR and sign off as appropriate.

#sign-off
@cjgronlund

@erhopf: I'm sorry - only the author of this article, @zhouwangzw, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Column Property And  Factory to create Dictionary related services

1.Column property
This will add column related property in schema and persist it
Command

create table employee(empName string, empid int , salary double) stored by 'org.apache.carbondata.format' tblproperties('columnproperties.empname.key'='value','columnproperties.empid.key'='value')

Add a factory to create dictionary and path related services

It's handled as per pr https://github.com/HuaweiBigData/carbondata/pull/641


Can't disable depth of field effect

I've been trying to disable the depth of field effect in the latest version of Elysium but I'm unable to do so. I've disabled the vanilla effect in the .ini files as well as turning it off in the ENB settings. I've even removed the .fx file for depth of field from the enbseries but no luck. I've looked through the mod list but I can't find any other potential mods that would add the effect to the game. Is there another way to disable this feature? It's a bit distracting and makes my head swim when trying to take in the entire screen, due to the blurriness. Thanks!

I think I can field this one.
1: you want the depth of field in the ini enabled or you get issues with water and ENB
2: in the In-Game settings menu there is a Depth of Field Slider that you are probably missing. You need to slide this all the way to the left. This is probably what you're seeing.


Fix #874 noinsert breaks redo register problem

It fixes #874 problem

Hi,
2016-7-5(Tue) 21:52:46 UTC+9 Shougo:

It fixes #874 problem
You can view, comment on, or merge this pull request online at:
https://github.com/vim/vim/pull/905
Commit Summary
Fix #874 noinsert breaks redo register problem
File Changes
M
src/edit.c
(1)

Patch Links:
https://github.com/vim/vim/pull/905.patch
https://github.com/vim/vim/pull/905.diff

Why you do not write a test?
You will surely write?
--
Best regards,
Hirohito Higashi (a.k.a. h_east)

Shougo wrote:

It fixes #874 problem

We also have #875 that is supposed to fix this.  What is the best
solution?
--
hundred-and-one symptoms of being an internet addict:
208. Your goals for the future are obtaining an T1 connection and
a 130 gig hard drive.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Am 2016-07-05 23:18, schrieb Bram Moolenaar:

Shougo wrote:

It fixes #874 problem

We also have #875 that is supposed to fix this. What is the best
solution?

According to PR #875, this does not fix issue #874 but a different
problem
(that no entry is inserted on pressing enter)
Best,
Christian

Duplicate

Thanks.


Display SlimeVR Tracker Battery Life

Adds support for receiving tracker battery info from the SlimeVR Server.

Trackers that do not have battery info are not affected.
Trackers that do have battery info will report their battery percentage, as well as whether they're charging or not.
Works for owoTrack devices (However, these will not display whether they're charging, as owoTrack does not send battery voltage info)

This depends on another pull request. (https://github.com/SlimeVR/SlimeVR-Server/pull/668)

The only thing battery voltage is used for here is for detecting if the tracker is charging or not, correct? I'd rather kick charging detection into firmware (or at least server for now) (i.e. the device reports the right thing depending on the setup) and just receive a boolean is_charging in driver.


Notification delay time

I was testing the library and can't understand one thing, how much time should pass after I changed or posted review and I will get the notification using subClient.pull, because, I changed something and get only 4 DEADLINE_EXCEEDED: Deadline exceeded , as I understand this error occurs if the queue is empty, but one time I got some message but unfortunately didn't check is it the message about review I have changed earlier or some another review was changed or added by some client

Generally the lag between posting to a topic and receiving on a subscription should be fairly short. I'm not as familiar with the queue empty behavior, but DEADLINE_EXCEEDED does kind of make sense if you're doing synchronous pull calls.

@Zimovets Are you still having trouble with this one? If so, can you go into a bit more detail on what you're doing in your publisher and subscriber, and what changed between it working and not working?

@Zimovets I'm going to close the issue, but please just let us know if there's more we can help with.


Migrate primary branch from master to main

See https://github.com/Senzing/stream-loader/issues/283

Pull requests:

https://github.com/Senzing/docker-installer/pull/20


ACM v0.2 - Vertical Arcade games rotated

When using the v0.2 pre-release of the ACM if you run a vertical arcade game it appears rotated 90 degrees inside a vertical display on the 16:9 screen. It's very weird.
None of the normal retroarch rotation options when in the game fix the issue.
Tried with several vertical games with the same result. I believe this worked on v0.1 but can't confirm.

When using the v0.2 pre-release of the ACM if you run a vertical arcade game it appears rotated 90 degrees inside a vertical display on the 16:9 screen. It's very weird.
None of the normal retroarch rotation options when in the game fix the issue.
Tried with several vertical games with the same result. I believe this worked on v0.1 but can't confirm.

inside a system (eg mame) push select (list options),advanced options, and: vertical rotation (tate) to off and allow rotation set to off

@fakemaria  thank you! Solved with these settings.

@acmeplus that settings is worth it to add it in a faq for acm


[theme] Add missed variants in Components interface

[x] I have followed (at least) the PR section of the contributing guide.

Closes #27409

@nikitabobers looks great. Can we also update https://github.com/mui-org/material-ui/blob/next/packages/material-ui-lab/src/themeAugmentation/components.d.ts?

@mnajdova sure. I'll add it

@nikitabobers Great, thanks


Error type in ZIO wrappers for LWJGL

I noticed that most of the functions in e.g. glfw\package.scala have a return type like UIO[A] or  ZIO[GLFW, Nothing, A], implying that exceptions should not be possible. However, it seems that it like is possible - here's a case for NullPointerException:
https://linustechtips.com/topic/584923-java-lwjgl-3-exception/?tab=comments
My understanding is that it may be more accurate to model these with the Throwable error type, e.g. Task[A] or RIO[GLFW, A], though there may be downsides to this I'm not aware of (likely related to needing to handle that rather ambiguous error type).

@bbarker ZIO's error channel is for recoverable errors though - I think if LWJGL's runtime checks throw an exception then it is a code defect (hopefully only observed during development) and is thus unrecoverable and we should let it crash. And if we ignore the runtime checks (it's possible to disable them) and treat LWJGL as a native wrapper - that native code cannot throw exceptions anyway (since it's not java code).

@wongelz ah I see, thanks for the explanation - makes sense!


correct k8s name parsing response codes

Fixes #491.
When a query string is invalid for kubernetes, return NXDOMAIN, so that clients will continue to try other domains in the search list.

I fixed up the logic a bit too - so that we don't go down the SRV validation path for non-SRV requests (even if the outcome would be the same)

Current coverage is 38.48% (diff: 75.00%)

Merging #493 into master will decrease coverage by 0.03%

@@             master       #493   diff @@
==========================================
  Files           115        115
  Lines          5792       5790     -2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           2231       2228     -3
+ Misses         3376       3375     -1
- Partials        185        187     +2

Powered by Codecov. Last update 299360f...0ebcc0e


Added the first application structure.

Added the first application structure.

LGTM! ;)
Note: Since I'm the only one contributing to this project, I'm merging it to master without a Code Review. Please, forgive me!


avoid and silence warnings

[ ] Closes issue #xxxx
[ ] I am familiar with the contributing guidelines.
[ ] Fully tested. Added and/or modified tests to ensure correct behavior for all reasonable inputs. Tests (usually) must pass on the TravisCI and Appveyor testing services.
[ ] Updates entries to docs/sphinx/source/api.rst for API changes.
[ ] Adds description and name entries in the appropriate docs/sphinx/source/whatsnew file for all changes.
[ ] Code quality and style is sufficient. Passes LGTM and SticklerCI checks.
[ ] New code is fully documented. Includes sphinx/numpydoc compliant docstrings and comments in the code where necessary.
[ ] Pull request is nearly complete and ready for detailed review.

Avoid or silence a lot of test warnings, plus a few that users might encounter (klucher and calcparams_desoto divide by 0).
Also some pep8 along the way. Waiting on #697.

Warnings status:

py27-min: 2 old numpy warnings. let's overlook this.
py27: forecast.py import warning (fix this). forecast's NDFD and HRRR_ESRL models produce warnings (maybe silence). pvfactors uses deprecated pvlib api -- maybe pvfactors 1.0.0 fixes this, but it's not compatible with our wrapper. cc @anomam
py34: all of py27 plus invalid warning in test_ashraeiam_scalar. maybe does not warning invalid values in np.minimum and np.maximum because it's using very old pandas and numpy and this was a more recent problem. We should drop this build soon anyways.
py35: all of py27 plus warnings about invalid values in np.minimum and np.maximum because conda-forge supplies only numpy 1.15 for python 3.5.
py36: same as py27
py37: only pvfactors warnings (this build doesn't test forecast.py).

To do:

[ ] silence forecast.py import warnings
[ ] look into NDFD and HRRR_ESRL warnings
[ ] overlook everything else

Lots of format fixes !

Yeah :( Trying to strike a compromise with my IDE's linter. The stickler objections here are wrong. Maybe a flake8 bug.

Everything lgtm so far, thanks!

@cwhanse ready to merge if you approve of the last few commits. I'd like to keep the pvfactors and forecast.HRRR_ESRL warnings as a reminder of work to do.


fix(infra): expose email auth header with cors request

Description
프론트엔드에서 Email-Auth 값을 못 읽는다고 해서 Caddyfile에 CORS 설정 추가했어요

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines
[x] Read the Contributing Guidelines and follow the Commit Convention
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

프론트엔드에서 필요로 해서 먼저 머지해둘게요

앗;; 밥먹고나서 확인한다는걸 깜빡했다 ;;; ㅅ쏘리쏘리


Add support for compiler-managed CFSTR() on non-Darwin systems

This gets the swift-corelibs-foundation implementation closer to the Darwin implementation by making the compiler lay out constant CFStrings produced by CFSTR(). It requires a corresponding clang patch to work.
This is only enabled for not-TARGET_OS_MAC for now, since the clang used to build Swift here is not the same as the one used by Xcode when using a Swift toolchain. When Xcode gets the new clang, we can enable this for TARGET_OS_MAC as well.

Please test with this pull request:
https://github.com/apple/swift-clang/pull/213
@swift-ci please test

Please test with this pull request:
apple/swift-clang#213
@swift-ci please test

Ready to merge whenever the clang change is.


Granular roles and privileges

Background: https://airtable.com/tblD3oZPLJgGhCmch/viw1DKmbKhg2MIECH/recCHyCs4TR6kO3gs
Description: The permissions that CockroachDB administrators can grant to users are now more granular. Instead of granting superuser access, administrators can assign narrower permissions for specific operations like IMPORT or BACKUP.
Enables non-admin users to perform the cluster administration/management tasks they need to do. IMPORT is the big-ticket item here but this should also take into account the other cluster operations (CDC, backup, restore, partition) that are currently restricted to admin users. We are also getting more requests for the ability to grant narrower sets of privileges from enterprises with serious security controls.
Team: Marc Berhault, Jesse Seldess, Roland Crosby, Lakshmi Kannan, Lauren Hirata
Github Tracking Issue: https://github.com/cockroachdb/cockroach/issues/15005 https://github.com/cockroachdb/cockroach/pull/20149 https://github.com/cockroachdb/cockroach/issues/29633 https://github.com/cockroachdb/docs/issues/4766 https://github.com/cockroachdb/cockroach/issues/41380 https://github.com/cockroachdb/docs/issues/5960

Dupe of #4766

@Amruta-Ranade, this is the one that's connected to the 20.1 roadmap. Notice the "milestone". Let's leave this one open and close the other, which is a leftover from previous roadmaps.

Addressed in https://github.com/cockroachdb/docs/pull/7061


Query timing in the cli depends on time spent in the pager

When I run a query that forces a pager to be invoked, the timing of such query includes time spent in the pager.
If I run a query with PRESTO_PAGER=cat, I get
$ PRESTO_PAGER=cat presto
presto> with t as (select sequence(1,100) as s) select 1 from t cross join unnest(s);
 _col0
-------
     1
 [...]
     1
(100 rows)

Query 20190424_102908_00047_cxygj, FINISHED, 1 node
Splits: 17 total, 17 done (100.00%)
0:01 [0 rows, 0B] [0 rows/s, 0B/s]

If instead I don't supply a PRESTO_PAGER and use the default (less), then if I spend some time paging the results (or doing nothing), then this time spent is reflected in the query timing.
Query 20190424_103044_00048_cxygj, FINISHED, 1 node
Splits: 17 total, 17 done (100.00%)
0:16 [0 rows, 0B] [0 rows/s, 0B/s]

So you see the exact same query, the same execution time (judging by the Presto UI), but the cli reports two wildly different numbers.

@kokes there might be some reporting friction here that can be improved.
However in general, when you use pager your query can actually take longer to complete.
This is because coordinator is streaming query results to the client. When you start a pager,
query results are loaded lazily and so they query can become blocked on the client, as
coordinator's buffers fill up.

@kokes If the PRESTO_PAGER is set to use default (less) the timer continues to run till we press q to stop it.(Typical behavior of less command in Linux)

I know, that's what I reported above.
The issue is not only that time is misrepresented, but also the performance characteristics (rows/s, MB/s), since they appear to be computed on the client side.
So this way of reporting may give the user an impression that their query is slow and not performant. It also doesn't match the UI, so that adds further confusion.

Okay. So in that case we can modify the StatusPrinter to use the elapsed time which is obtained from the StatementStats rather the timer from the cli.
So we can modify
Duration wallTime = nanosSince(start);
to
Duration wallTime = succinctNanos(stats.getElapsedTimeMillis());
and the final stats line would be running on the actual counter.
@findepi Your insights on this ?

@Praveen2112
yes, i think we should improve. CLI-reported stats ideally should match UI-reported stats.
I don't know the CLI code that well, so can't say of this is the right fix.
@electrum ?
@kokes,
please be aware that even after this change, query stats with page and query stats without pager will be different.
if you have large query results and you're using a pager -- pager will prevent CLI from reading all results,
and this in turn will prevent the query from completing. (In such a case, query will ultimately complete when user
scrolls to the tail of the pager (eg G) or quits it.)


Context setup doc link is broken

In the graphql-tools doc page, in the Resolver function signature section,  the link for how to setup context is broken. Is there a page for that could be found somewhere?

Seems to be fixed now.


✨ Allow main branch for trusted builder

This is part of trying to reduce the time of compilation https://github.com/slsa-framework/slsa-github-generator/issues/74
This PR allows the trusted builder to use itself at @main to be built. This is an exception that is needed to use the builder binary generated during a release: the builder needs to build itself from main. For any other repos, this is not allowed, and a version/tag is required.

In order to fix the unit tests, we need to merge https://github.com/slsa-framework/slsa-github-generator/pull/86 and generate the provenance with the trusted builder pinned with a tag. This ie because starting with this PR, we only accept tagged's trusted builders (except for the old ones which we're going to deprecate as well once we fix the other unit tests)

Ready for review, PTAL


[Exploratory] Use gralde projects for framework components

DO NOT MERGE
Exploratory branch - see how we can approach components dependency https://issues.apache.org/jira/browse/OFBIZ-3500
This is to start discussion around improving ofbiz codebaase to allow more contributions.
Goals:

Migrate ofbiz components to use gradle projects.
Expose dependencies of each component.
Expose circular dependencies between components.
Allow easier future code changes / dependency updates.

Test with:
cd framework
./gradlew clean build

Done so far:

Created build.gradle files for some components; start, base, common, etc.
Circular dependencies between components needs to be fixed before we move forward.
** start depends on base and reverse
** common depends on base and reverse
** base depends on entity and webapp
** etc ?!

cc @nmalin : This is to start discussions.
The job is a bit more complex because of circular dependencies between modules.
If you
cd framewrok
./gradlew clean build

(or open framework project in IDE) you will see what I mean.
Right now start depends on base and base on start .
base also depends on entity and webapp.
I believe these circular dependencies should be fixed and I would need some help here.

Superseded by https://github.com/apache/ofbiz-framework/pull/678 .


Update Wachowskis entry

This PR updates the entry on the Wachowskis as suggested in #2. It uses the first image referenced in the comment. This image is about 60kB larger than the previous one. If this is an issue, let me know, and I'd be happy to go and find a different one or compress this one. If the image is an issue, I'm also happy to exclude that from the PR and just update the name for now.
Any other input or feedback is also much appreciated! 🙏🏾

Hmm.. Rather than manipulating the export files inside the code, you should rather import the content in a local instance, modify it than export the result and place it in the app. That way everything will be peaches in terms of consistency.

Sure; that sounds good! I’m not entirely sure how to do what you’re describing, though. Is there a guide for this? Or will it become obvious once I start? I’m not at my computer right now, so it’s a bit abstract at the moment. Thanks for the quick feedback ☺

On 16 Mar 2021, at 18:50, Thomas Sigdestad @.***> wrote:

Hmm.. Rather than manipulating the export files inside the code, you should rather import the content in a local instance, modify it than export the result and place it in the app. That way everything will be peaches in terms of consistency.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Just Install hmdb, modify the content and export with data toolbox

Got it! Just to make  sure I got it right:
In data toolbox, you can use the 'data tree' option to find the project you want. Navigate to the 'draft' branch (master was empty) and export the content. You can then copy this into the source repo where you got the content from originally.
Seems to work alright, except that for a few issues that I'm hoping you can help me with.
At first it seemed that I had changed a bunch of permissions. In more or less every node.xml file, I had a diff that said I added new users with privileges and removed cms.cm.app:

Permissions changes
@@ -5,12 +5,24 @@
     <timestamp>2020-09-23T12:34:46.777Z</timestamp>
     <inheritPermissions>true</inheritPermissions>
     <permissions>
-        <principal key="role:cms.cm.app">
+        <principal key="role:cms.project.hmdb.viewer">
             <allow type="array">
                 <value>READ</value>
             </allow>
             <deny type="array"/>
         </principal>
+        <principal key="role:cms.project.hmdb.owner">
+            <allow type="array">
+                <value>READ</value>
+                <value>CREATE</value>
+                <value>MODIFY</value>
+                <value>DELETE</value>
+                <value>PUBLISH</value>
+                <value>READ_PERMISSIONS</value>
+                <value>WRITE_PERMISSIONS</value>
+            </allow>
+            <deny type="array"/>
+        </principal>
         <principal key="role:system.admin">
             <allow type="array">
                 <value>READ</value>
@@ -23,6 +35,18 @@
             </allow>
             <deny type="array"/>
         </principal>
+        <principal key="role:cms.project.hmdb.editor">
+            <allow type="array">
+                <value>READ</value>
+                <value>CREATE</value>
+                <value>MODIFY</value>
+                <value>DELETE</value>
+                <value>PUBLISH</value>
+                <value>READ_PERMISSIONS</value>
+                <value>WRITE_PERMISSIONS</value>
+            </allow>
+            <deny type="array"/>
+        </principal>
         <principal key="role:cms.admin">
             <allow type="array">
                 <value>READ</value>
@@ -35,6 +59,27 @@
             </allow>
             <deny type="array"/>
         </principal>
+        <principal key="role:cms.project.hmdb.contributor">
+            <allow type="array">
+                <value>READ</value>
+            </allow>
+            <deny type="array"/>
+        </principal>
+        <principal key="role:cms.project.hmdb.author">
+            <allow type="array">
+                <value>READ</value>
+                <value>CREATE</value>
+                <value>MODIFY</value>
+                <value>DELETE</value>
+            </allow>
+            <deny type="array"/>
+        </principal>
+        <principal key="role:system.everyone">
+            <allow type="array">
+                <value>READ</value>
+            </allow>
+            <deny type="array"/>
+        </principal>
     </permissions>
     <data>
         <boolean name="valid">true</boolean>

This seems to suggest that I've added a bunch of new roles (or even users). I managed to get around this by changing the permissions structure according to the of the root node (not inheriting permissions, removing hmbd users).
Now, every node.xml (or at least 70 of them; I'm assuming that's the lot), has updated timestamps because of permissions changes (presumably):

     <id>c2998dba-c56e-491e-af36-0ffc4a74c67a</id>
     <childOrder>modifiedtime DESC</childOrder>
     <nodeType>content</nodeType>
-    <timestamp>2020-09-23T12:34:46.762Z</timestamp>
+    <timestamp>2021-03-17T09:09:49.583Z</timestamp>
     <inheritPermissions>true</inheritPermissions>
     <permissions>
         <principal key="role:cms.cm.app">

Should I include this or can I discard those changes? Is there a better way to do this? I spun up the app in a clean sandbox.

Using inherit = true and cleaning away other permissions sound correct to me. Also new timestap is no problem I guess.
Just create a new branch and I can give it a spin before we merge to master.

Thanks for the input. Here's what I've done now.
I've broken up the changes into three commits.

The first one (7442f131) contains what I consider the essential changes. From my little testing, it seems to work as expected. If this does indeed work, I suggest we discard any later commits and use only this.

The second one (a9c4c5a) contains what I consider to be accidental changes to the Wachowskis' entry. This is stuff such as workflow and SoMe property sets, pathIndexConfig, etc. I don't know whether this is necessary, but it seems superfluous and is probably a result of me touching some fields I shouldn't have. If these changes are necessary and sufficient, I suggest we use this commit or, if desired, break it into smaller pieces (if there are some of these changes that we want, and others not).

The third commit is the one that updates the timestamp on all the nodes. It touches 69 files and I don't think it is important. Again, I think it's just a function of me touching some controls in an unfortunate manner.

So to recap: If it's sufficient, let's merge only the first commit. If necessary, we'll add the second one. If that's not enough, let's consider the third one. Does that sound alright?

@tsi?

@tsi Any updates on this?  I'm so sorry 🙈  We use 3-letter identifiers internally, and tsi is @sigdestad's 😅
So indeed, @sigdestad: where are we at with this?

Maybe you could rather demo this for me, and we could conclude in meeting?


"nd_patch_step" variable is not define

Hello there,
In your "test.py" file the variable "nd_patch_step" is not defined. If I track down the variable it should be equal to "nStride", but with such setting the test does not seem to be working correct.
Am I missing some thing?
Thanks

Dear @mshahabi ,
I'm so sorry for the late reply because of my busy time in these days.
Yes, as you said, the nd_patch_step is like as below:
    nd_patch_step = (n_stride, n_stride)
Also, you can use any other configuration, and it is not related to the main idea of our work.
Best regards,
Mohamma


Everyone can't read chef.log

Cookbook version
[7.0.0]
Chef-client version
[12.16.42]
Platform Details
[Ubuntu 14.04]
Scenario:
Can't read chef.log as non-root\owner
Steps to Reproduce:
Output logs to /var/log/chef/chef.log.  Try to open without sudo permission, eg less chef.log
Expected Result:
Should be able to read log.
Actual Result:
Can't.    Get error "chef.log: Permission denied."
attributes/default.rb has:
# If log file is used, default permissions so everyone can read
default['chef_client']['log_perm'] = 00640
If the intention is as per the comment (everyone to have read-access), needs to be:
default['chef_client']['log_perm'] = 00644_

In general users consider these logs to be sensitive and we've chosen to default the config to 640 due to that. The permissions are and attribute if you wise to make them 644.


Add options to the properties converter to update from 0.6.x to 0.7.x

Add the -c option to specify one of FIVE_TO_SIX or SIX_TO_SEVEN

CI failed only on java 8 on
Failed tests:   testQueryCancellation(io.druid.query.ChainedExecutionQueryRunnerTest)

We also need to add conversion for cache settings

druid.announcer.type=batch
druid.curator.compress=true

settings can be removed if set to those specific values, since they are now the defaults.
druid.db.connector.useValidationQuery

should be removed, since it does not exist anymore and is always true

Victim of #1032


One FEST test failing: verifySendRequestScreen

I just ran the FEST tests and there was one failure:
verifySendRequestScreen
java.lang.AssertionError: <'Trezor "Example" attached. Do you want to use it ?'> should contain the String:<'Please donate to MultiBit'>
at org.fest.assertions.Fail.failure(Fail.java:206)
at org.fest.assertions.Assert.failure(Assert.java:141)
at org.fest.assertions.StringAssert.contains(StringAssert.java:237)
at org.multibit.hd.ui.fest.use_cases.AbstractFestUseCase.assertLabelContainsValue(AbstractFestUseCase.java:232)
at org.multibit.hd.ui.fest.use_cases.sidebar.send_request.send.SendDisplayUntrustedPaymentRequestUseCase.execute(SendDisplayUntrustedPaymentRequestUseCase.java:43)
I think there were two alerts in a stack and the test is looking for the wrong one (couldn't swear to it though as this is just what I noticed when it ran).

Updated FEST text - Next button in Send progress is enabled rather than disabled as per old test.
It's the MultiBitFESTTest#verifySendRequestScreen() test suite.
Awaiting review and closing.

Verified working.
Closing.


PanicException('called Option::unwrap() on a None value')

When using a yjs-websocket server (https://github.com/yjs/y-websocket) the ypy-websocket provider does not sync properly:
thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/yrs-0.11.1/src/block.rs:1073:54

Traceback (most recent call last):
  File "/root/yspine-client/.venv/lib/python3.10/site-packages/ypy_websocket/websocket_provider.py", line 34, in _run
    await process_sync_message(message[1:], self._ydoc, self._websocket, self.log)
  File "/root/yspine-client/.venv/lib/python3.10/site-packages/ypy_websocket/yutils.py", line 130, in process_sync_message
    Y.apply_update(ydoc, update)
pyo3_runtime.PanicException: called `Option::unwrap()` on a `None` value

Other yjs clients on the same server work fine.
Please let me know if you need further details or something to reproduce.
Cheers,
chwzr

Thanks for reporting @chwzr, yes a reproducible example would help a lot.

hi @davidbrochart  thanks for the quick reply!
here is a repo to reproduce the bug:
https://github.com/chwzr/ypy-sync-issue


Auth status API (or consistent way to determine if auth is enabled)

There are a number of places throughout the UI where I'd like to know if auth is enabled. For some of these, i can just check if the user is logged in, but for others, I need to know if auth is enabled regardless of login status (eg: what to show on the login screen if auth is disabled)
I think the most straightforward would be to have an auth status API method, but failing that, having a single, definitive answer from some other endpoint return this info would suffice

Per our discussion: Auth.WhoAmI (https://github.com/pachyderm/pachyderm/blob/master/src/client/auth/auth.proto#L157) should work. It'll tell you:

if auth isn't activated ("the auth service is not activated")
if you're not logged in ("auth token not found in context")
if your login has expired ("token not found")
who you are, if auth is active and your authentication token is valid


import syntext

import  d3 from 'd3-webpack-loader!';
did not worked for me
but
import * as d3 from 'd3-webpack-loader!';
did

@osadan,  your note helped me resolved the same problem.  Thank you very mush.
@pbeshai, thank your for creating d3-webpack-loader; it helps me to use modules like d3-selection-multi  seamlessly, except this build error.
ERROR in ./~/d3-webpack-loader!
Module build failed: TypeError: Cannot read property 'map' of undefined
    at getModuleDirectories (..../node_modules/d3-webpack-loader/index.js:51:38)

Here is the code on at index.js:51.
    resolveOptions.modulesDirectories.map(function (dir) {
      return path.join(webpackContext, dir);
    }),

After showing the build error, the server runs without error.
Here is one noticeable difference is  devtool: 'eval' in your example/webpack.config.js, vs. devtool: 'source-map' my webpack.config.js .

I think that's because d3-webpack-loader is not compatible with Webpack 2


Add the Struct Interface and make generated Thrift structs implement it

Per https://github.com/Microsoft/thrifty/issues/39 this adds the Struct interface which has a write method and makes all generated Thrift structs implement it. This will add one method per generated struct but with the advantage that a generic Struct can be written out to a protocol.
For example, this is now possible:
Buffer buffer = new Buffer();
Transport transport = new BufferTransport(buffer);
Protocol protocol = new BinaryProtocol(transport):

Struct fooStruct = Foo.Builder().build();
Struct barStruct = Bar.Builder().build();

fooStruct.write(protocol);
barStruct.write(protocol);

Paired with @felipecsl

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

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

Hi, thanks for the speedy PR and CLA!
It looks like this failed checkstyle; please run ./gradlew check and fix whatever it is complaining about, usually it's very minor.
This is quite useful as-is; now that I see this, however, I'm wondering if it might be better to have Struct as a common base class rather than an interface.  It would then be trivial to say:
protected abstract Adapter<T, B> adapter();
public void serialize(Protocol protocol) {
  adapter().write(protocol, (T) this);
}

Not a huge difference yet, but it would lay the groundwork for adding common functions to generated classes without codegen.
What do you think?

+1 for that suggestioN!

Good idea, I'll fix the checkstyle real quick (missing period in javadoc) and then modify the change to extend from Struct instead.

So, one issue with extending from a Struct abstract class as opposed to implementing a Struct interface is the existing behavior in the buildStruct method. It looks like if the StructType is StructElement.Type.EXCEPTION the generated class is meant to be a subclass of Exception:
    if (type.isException()) {
      structBuilder.superclass(Exception.class);
    }

Of course - how could I forget!  That certainly complicates things.
It's really a shame that, even with the new Java 8 features coming in Android N, default methods on interfaces will not be supported below API 24; that would give us the best of all worlds.  I suppose we can proceed with an interface.
Thanks for your contribution!


Code Refactor & Bot Replies

The bot now replies to messages posted by users which reduces the number of commands needed.

The code has also gone through a big refactor so the commands folder is properly linked to main.js using the methods outlined in Discord.js docs

Commands in the commands folder are now automatically linked and we can access the message object rather than having to use botMessage.call and create a new function.

To Fix:
-The -github-info command reply isn't working but think that may be due to conflicting bot instances running.

To refactor help.js to be compatible with this PR.
cc - @Inoxia25


feat: selection sort

Pull-request Type (fix, feat, bug, doc, chore, test, etc...)

feat

Current Behavior (Link to an open issue)

selection_sort 함수가 비어있습니다.

New Behavior (if this is a feature change)

selection_sort를 통해 정렬 수행

Other information

Awesome Code!!👍


[BUG] - Sequential averaging mode broken

Describe the bug
Sequential averaging mode can not be used with L1Q

[ ]  A: Measured results have unexpected / wrong results

-- Sequential

experiment.zip
-- Cyclic

experiment.zip

[ ]  B: Compilation does takes forever with LinearSweepParameters
Cyclic:
experiment.zip
Sequential:
experiment.zip

To Reproduce
Execute experiments with above experiments using the following setup.
setup.zip
Expected behavior
A) The results of the experiments should be qualitatively the same
B) It should be possible to compile the experiment in sequential mode without substantial overhead.
Code & Screenshots
Versions used:

laboneq: 1.0.0
zhinst-core
others

Context

[ ] Do you know a workaround for the issue? If yes, please provide a short description.
[ ] Does the issue block your experiments?

Hi @GlaserN , a short update: We could reproduce both issues.
A) Currently, our compiler does not support multiple acquire statements within one real-time acquisition loop in sequential mode. As I understood from @zi-2k, this is not blocking for you?
B) We are currently testing a fix (which will probably go into 1.4) and have a new regression test in place that checks for the compilation times both in sequential and cyclic averaging.

Hi @GlaserN ,
With release 1.3 coming this week, compilation times in Sequential mode will be back to fast!


Representation of Results (Flacoco API)

Flacoco API returns the suspicious data as a Map (see here)
This means that the client should sort the results.
I think that we can return the results already sorted.
One option, that does not break the API, would be to use to use LinkedHashMap (e.g., here).
Another option to change the API and use for instance, SortedMap.
WDYT?

I've updated the wiki to make it more explicit! (https://github.com/SpoonLabs/flacoco/wiki/API)


basic example, update react router to 3.0, and onUpdate run twice

hi, i just git clone the basic example and update react-router to 3.0
modify to
<Router history={history} onUpdate={()=>{console.log('jsdjfjsdlf');}}>

and the console shows that onUpdate run two times
and i remove react-router 3.0 and reinstall react-router 2.8.1
and it works just print console once.
is it a react-router-redux problem or react-router problem?

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux. Thanks!


PSN user is not authenticated

Im sure it's already authenticated but still get this error

same for me

same for me :(

Same problem here, Playnite 10.9 and SuccessStory 3.1

I'm having the same problem as well, with latest version of Playnite (10.9) and SuccessStory (3.1).
I did some debugging and the code correctly detects that the user is logged in but then fails to get the mobile token because the request to mobileCodeUrl fails with a 400 BadRequest. Did a Sony API change?

Same issue
o/

any solution?

is psn trophies abandoned?

is psn trophies abandoned?

Yes

fixed


How can I get current logged in user details in controller?

I am trying to get the current user from the socket controller.
Trying to get it like this
`constructor ({ socket, request , auth, session}) {
this.socket = socket
this.request = request
this.auth=auth
}
async onClose (data) {
const user = await this.auth.user
console.log(user) // it gives null
}`
Also tried to get some values from session. Sessions works in all controller except here.
Any ways I can get the user id from here?
Many thanks.

HI, Thank you so much for your valuable time :)
I think I have the default code from start/kernel.js . Here is the code without comments
'use strict'

const Server = use('Server')
const globalMiddleware = [
  'Adonis/Middleware/BodyParser',
  'Adonis/Middleware/Session',
  'Adonis/Middleware/Shield',
  'Adonis/Middleware/AuthInit'
]
const namedMiddleware = {
  auth: 'Adonis/Middleware/Auth'
}
const serverMiddleware = [
  'Adonis/Middleware/Static',
  'Adonis/Middleware/Cors'
]

Server
  .registerGlobal(globalMiddleware)
  .registerNamed(namedMiddleware)
  .use(serverMiddleware)

I am using adonuxt. All other socket related things are working nicely. Just need the logged in user data.
Here is how I am connecting.
    const myRoom=this.authUser.id
    const ws = adonis.Ws()
    ws.connect()
    // subscribe to topic that are coming for me
    const chat = ws.subscribe(`noti:${id}`)
    chat.on('error', (error) => {
        console.log(error)
      })

     ws.getSubscription(`noti:${id}`).on('message', (msg) => {
           console.log(msg)
           // many more code here and all works fine...
     })

My socket route is like this
const Ws = use('Ws')
Ws.channel('noti:*', 'NotifyerController')

And in my NotifyerController I have
'use strict'
const notiClass = use('App/classes/notification')
const noti = new notiClass()
class ChatController  {
  constructor ({ socket, request, auth}) {
     this.socket = socket
     this.request = request
     this.auth = auth // this doesn't work.
  }
  async onClose (data) {
        // here I am trying to get the user id so that I can make database query to make this user offline.
  }

}

The default one. Sessions (session).

Kind of weird. Lemme try to reproduce the issue and update you

Thank you so much..

Any update on it? If you could at least show an example how you would have done this
How to know which user is disconnected from the subscribed topic or in any other way.
Waiting for a help. Thank you so much for this great work.

I believe I may be getting a similar issue:
wsKernel.js
'use strict'

const Ws = use('Ws')

const globalMiddleware = [
  'Adonis/Middleware/Session',
  'Adonis/Middleware/AuthInit'
]

const namedMiddleware = {
  auth: 'Adonis/Middleware/Auth',
  guest: 'Adonis/Middleware/AllowGuestOnly',
}

Ws
  .registerGlobal(globalMiddleware)
  .registerNamed(namedMiddleware)

socket.js
const Ws = use('Ws')

Ws.channel('report', 'ReportController').middleware('auth')
Ws.channel('authentication', 'AuthenticationController')

and finally in AuthenticationController.js
  async onLoginAs(message){
    var user = ...;// My special login/search function
    if(user){
      this.auth.login(user);
      this.socket.emit('login-success',{user})
    }else{
      this.socket.emit('login-failed',true)
    }
  }

When user is found, the following error occurs:
[0] warning:
[0]   WARNING: Adonis has detected an unhandled promise rejection, which may
[0]   cause undesired behavior in production.
[0]   To stop this warning, use catch() on promises or wrap await
[0]   calls inside try/catch.
[0]
[0] RuntimeException: E_RUNTIME_ERROR: Session store is freezed and you cannot write values to session. This usually happens during the Websocket request
[0] > More details: https://err.sh/adonisjs/errors/E_RUNTIME_ERROR
[0]     at Function.invoke (/Users/nickartman/Sites/strongsville/special-attention/node_modules/@adonisjs/generic-exceptions/src/RuntimeException.js:102:12)
[0]     at Session._ensureNotFreezed (/Users/nickartman/Sites/strongsville/special-attention/node_modules/@adonisjs/session/src/Session/index.js:129:10)
[0]     at Session.put (/Users/nickartman/Sites/strongsville/special-attention/node_modules/@adonisjs/session/src/Session/index.js:214:10)
[0]     at SessionScheme._setSession (/Users/nickartman/Sites/strongsville/special-attention/node_modules/@adonisjs/auth/src/Schemes/Session.js:88:23)
[0]     at SessionScheme.login (/Users/nickartman/Sites/strongsville/special-attention/node_modules/@adonisjs/auth/src/Schemes/Session.js:228:10)
[0]     at AuthenticationController.onLoginAs (/Users/nickartman/Sites/strongsville/special-attention/app/Controllers/Ws/AuthenticationController.js:23:17)

I believe I may be getting a similar issue:
wsKernel.js
'use strict'

const Ws = use('Ws')

const globalMiddleware = [
  'Adonis/Middleware/Session',
  'Adonis/Middleware/AuthInit'
]

const namedMiddleware = {
  auth: 'Adonis/Middleware/Auth',
  guest: 'Adonis/Middleware/AllowGuestOnly',
}

Ws
  .registerGlobal(globalMiddleware)
  .registerNamed(namedMiddleware)

socket.js
const Ws = use('Ws')

Ws.channel('report', 'ReportController').middleware('auth')
Ws.channel('authentication', 'AuthenticationController')

and finally in AuthenticationController.js
  async onLoginAs(message){
    var user = ...;// My special login/search function
    if(user){
      this.auth.login(user);
      this.socket.emit('login-success',{user})
    }else{
      this.socket.emit('login-failed',true)
    }
  }

When user is found, the following error occurs:
[0] warning:
[0]   WARNING: Adonis has detected an unhandled promise rejection, which may
[0]   cause undesired behavior in production.
[0]   To stop this warning, use catch() on promises or wrap await
[0]   calls inside try/catch.
[0]
[0] RuntimeException: E_RUNTIME_ERROR: Session store is freezed and you cannot write values to session. This usually happens during the Websocket request
[0] > More details: https://err.sh/adonisjs/errors/E_RUNTIME_ERROR
[0]     at Function.invoke (/Users/me/Sites/myproject/site/node_modules/@adonisjs/generic-exceptions/src/RuntimeException.js:102:12)
[0]     at Session._ensureNotFreezed (/Users/me/Sites/myproject/site/node_modules/@adonisjs/session/src/Session/index.js:129:10)
[0]     at Session.put (/Users/me/Sites/myproject/site/node_modules/@adonisjs/session/src/Session/index.js:214:10)
[0]     at SessionScheme._setSession (/Users/me/Sites/myproject/site/node_modules/@adonisjs/auth/src/Schemes/Session.js:88:23)
[0]     at SessionScheme.login (/Users/me/Sites/myproject/site/node_modules/@adonisjs/auth/src/Schemes/Session.js:228:10)
[0]     at AuthenticationController.onLoginAs (/Users/me/Sites/myproject/site/app/Controllers/Ws/AuthenticationController.js:23:17)

I am trying to get the current user from the socket controller.
Trying to get it like this
`constructor ({ socket, request , auth, session}) {
this.socket = socket
this.request = request
this.auth=auth
}
async onClose (data) {
const user = await this.auth.user
console.log(user) // it gives null
}`
Also tried to get some values from session. Sessions works in all controller except here.
Any ways I can get the user id from here?
Many thanks.

I had this same issue. I just had to add the Auth Middleware in the wsKernel.js file.
`'use strict'
const Ws = use('Ws')
const globalMiddleware = [
'Adonis/Middleware/Session',
'Adonis/Middleware/AuthInit'
]
const namedMiddleware = {
auth: 'Adonis/Middleware/Auth'
}
Ws
.registerGlobal(globalMiddleware)
.registerNamed(namedMiddleware)`

HI, where did you write your onLoginAs  method? In socket controller or normal http controller?


'OSError [Errno5] Input/output error' occurred while invoking logger

I designed a robot framework testing library, a specific method defined as below:
import json
from robot.api import logger
@staticmethod
def select_list_first_element_info(select_list, select_key):
    if select_list and isinstance(select_list, list) and select_key:
        data_dict = select_list[0]
        json_dict = json.loads(data_dict)
        if select_key in json_dict.keys():
            return json_dict.get(select_key)
        else:
            logger.error(r"%s cannot be found in keys of dict variable json_dict." % select_key, html=True)
            return ""
    else:
        logger.error(r"select_list is not valid list or select_key is null.", html=True)
        return ""

But, I/O error occurred regardless of html=True or not.

20180302 01:18:55.723 - INFO - +--- START KW: lhvapi.Select List First Element Info [ ${dc_list} | ${key_dcid} ]
20180302 01:18:55.724 - ERROR - select_list is not valid list or select_key is null.
20180302 01:18:55.727 - FAIL - OSError: [Errno 5] Input/output error
20180302 01:18:55.727 - DEBUG - Traceback (most recent call last):
File "/home/autorunner/virtual_env/lib/python3.6/site-packages/lhvapi/LhvRequests.py", line 162, in select_list_first_element_info
logger.error(r"select_list is not valid list or select_key is null.", html=True)
File "/home/autorunner/virtual_env/lib/python3.6/site-packages/robot/api/logger.py", line 131, in error
write(msg, 'ERROR', html)
File "/home/autorunner/virtual_env/lib/python3.6/site-packages/robot/api/logger.py", line 88, in write
librarylogger.write(msg, level, html)
File "/home/autorunner/virtual_env/lib/python3.6/site-packages/robot/output/librarylogger.py", line 44, in write
LOGGER.log_message(Message(msg, level, html))
File "/home/autorunner/virtual_env/lib/python3.6/site-packages/robot/output/logger.py", line 154, in _log_message
self.message(msg)
File "/home/autorunner/virtual_env/lib/python3.6/site-packages/robot/output/logger.py", line 141, in message
logger.message(msg)
File "/home/autorunner/virtual_env/lib/python3.6/site-packages/robot/output/console/quiet.py", line 28, in message
self._stderr.error(msg.message, msg.level)
File "/home/autorunner/virtual_env/lib/python3.6/site-packages/robot/output/console/highlighting.py", line 74, in error
self.write(' ] %s\n' % message)
File "/home/autorunner/virtual_env/lib/python3.6/site-packages/robot/output/console/highlighting.py", line 51, in write
self.stream.write(console_encode(text, stream=self.stream))

OS: CentOS Linux release 7.4.1708 (Core)
Python: v3.6.3
Robot Framework: v3.0.2
It confused me for while, right now I have to remove logger codes.

Open the same issue in stackoverflow .

The error occurs when Robot tries to write into the stderr. Have you redirected it or otherwise somehow configured it somehow? Do you run tests directly on the command line or otherwise?

@pekkaklarck
Robot was invoked in python code instead of command line, see below.
from robot import rebot_cli, run as robot_run
...
result = robot_run(test_suite,
                        variable=self.rf_variables,
                        listener=self.rf_listener,
                        include=self.rf_include,
                        quiet=True)
...

You didn't answer the question about stderr. Do you get same error if you run tests normally with the robot command?

@pekkaklarck
With updated method like below, robot can logging error normally in command line.
    @staticmethod
    def select_list_first_element_info(select_list, select_key):
        if select_list and isinstance(select_list, list) and select_key:
            data_dict = select_list[0]
            json_dict = json.dumps(data_dict)
            json_dict = json.loads(json_dict)
            if select_key in json_dict.keys():
                logger.error("ABCD EF")
                return json_dict.get(select_key)
            else:
                return ""
        else:
            return ""

@pekkaklarck
Need to mention that, the system that invokes robot_run consists of flask, celery&redis.

I don't see any real difference between the two examples. Can you provide a simple example that demonstrates the problem? Also, please answer the questions I asked earlier.


Linux -- inconsistent Makefile archs translation

When compiling a tweak with a standard Makefile, dragon occasionally fails to adhere to the archs specified. Instead, it seems to default to arm64, arm64e, and armv7, though armv7 wasn't specified in the Makefile.

I have the same issue on macOS


Unclosed block comments leave odin.exe in an infinite loop

If you open a block comment /* but never close it, odin.exe build $filename will go into an infinite loop.
Code to reproduce:
main :: proc(){
  /*
}

Fixed


How to use this code

Hi,
Thank you for your sharing. But would you mind helping me to use this drive?
I have a lidar lite v3 in hand and I want to get data from it using my PC, with Ubuntu installed. But when I run the code, I get error like this:
I2C: Failed to write data to register 0x00: 9-Bad file descriptor
[ERROR] [1533632560.636237716]: Failed to write 0x04 to 0x00
[ERROR] [1533632560.636255662]: Failed to read distance - setting bias correction
How can I get data from the sensor with this drive?
Thanks a lot!

@weiqil I have only tried running it on odroid C2 board, but not on PC.

I used to get errors like that but it was because my i2c interface was broken, not the lidar_lite node. Make sure your wiring is good and you have i2c enabled on your PC


OCPVE-747: chore: move tagging to avoid coverage on cmd

Moves the temporary tagging logic for 4.15 out into an internal package so that coverage doesn't attempt to cover the cmd package (which is CLI interfacing that we don't want to test)

/lgtm


Change citebordercolor to tugreen

It has always been bothering me that the color for the links is tugreen, while the color of citations has a slightly different color. This PR fixes the issue, making the borders for both links and citations tugreen.
If this is intentional that the colors are different, I think it would be better to have two colors that are more distinguishable.

Nice, thanks

I normally don't use the link borders at all.


Default NGINX page post deploy.

It serves the standard nginx page for this application only.
The steps at https://github.com/dokku/dokku/blob/master/docs/troubleshooting.md don't seem to apply - as the other applications on the host all work (with longer names)
Looking at the config file in the container it seems to look good, and curling the address listed in the /home/dokku/app/nginx.conf http section from the host machine works.
Is dokku not registering the new application correctly? Or is it something to do with this applications configuration?

Can you provide more details about the application being deployed? Specifically, please include all of the info specified here. Thanks!

My apologies. PEBKAC - forgot to modify some DNS settings.


Fix for changed command-line options

It seems that with the move to version 1.x, inkscape's command-line options were overhauled. Your script dies without any indication of what the problem might be. Executing the command manually yields
Warning: Option --without-gui= is deprecated
Unknown option -A

One solution that ensures backwards compatibility is to check inkscape's version string and choose the command line options appropriately. I'm not entirely sure that my method is robust, but it was tested on Ubuntu 18.04 (Inkscape 0.92.3 (2405546, 2018-03-11)) and Fedora 33 (Inkscape 1.0.1 (3bc2e813f5, 2020-09-07)) and is working as expected.

@TpmKranz Thanx for this PR!  I'll run it thru a few more tests and merge if OK.

@TpmKranz Thanx for this PR!  I'll run it thru a few more tests and merge if OK.


Added support for Android 9 and 10

I had to rebuild the android image on Centos 7 and I am able to build 8.1, yet when building 9.0 I get the following error:
resize2fs: Bad magic number in super-block while trying to open /root/.android/avd/android9.0-1.avd/userdata.img

Any ideas?


⚠ Bofrost.es has degraded performance

In 0c93806, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1401 ms

Resolved: Bofrost.es performance has improved in 22bc25b after 6 minutes.


Add gefdc to docs

Codecov Report

Merging #77 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #77   +/-   ##
=======================================
  Coverage   90.26%   90.26%
=======================================
  Files           9        9
  Lines         668      668
  Branches      109      109
=======================================
  Hits          603      603
  Misses         44       44
  Partials       21       21

Impacted Files
Coverage Δ

pygridtools/misc.py
93.9% <ø> (-1.72%)
:arrow_down:

pygridtools/gefdc.py
96.72% <100%> (+1.16%)
: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 fb0f9fe...3683d86. Read the comment docs.


Jenkins Grinder jobs using jdk_custom can no longer find tests in the test directory

Eg.
Error: Cannot find file: /home/jenkins/workspace/Grinder_Advanced/openjdk-tests/TestConfig/scripts/testKitGen/../../../openjdk/openjdk-jdk/java/util/Arrays/TimSortStackSize2.java
I reset some commits and found that this commit caused the problem: https://github.com/AdoptOpenJDK/openjdk-tests/commit/91c4c4b128445665860b342fd4d5357947b6856d although cannot determine the issue
Tested this on multiple tests and versions.
Eg. https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder_Advanced/631/

We updated the code. We are expected CUSTOM_TARGET to contain full path after yourTestImageLocation. For example,
export JDK_CUSTOM_TARGET=test/jdk/java/lang/Class/GetModuleTest.java

Please see the wiki https://github.com/eclipse/openj9/wiki/Reproducing-Test-Failures-Locally#run-specific-test-class-from-openjdk-tests-on-jdk11-linux-s390x-openj9-sdk
Close the issue for now. Please reopen if you still have problem.


dynamic channel on the teams sink

Is your feature request related to a problem?
The need is to choose the teams where to send info dynamically without having to change anything in robusta.
Teams are associated to projects that are managed outside Robusta: the ability to read labels from Alerts (through alert relabeling) will enable Robusta to send to a sink it does not know and is not hard coded in its configurartion
Describe the solution you'd like
Solution similar to slack where sink info is red from labels/annotations
Describe alternatives you've considered
Defining CR for sink that are placed in the project NS and Robusta able to watch for these CR and configure itself to use those new CR
Additional context
Talked about this on Slack with @arikalon1

to be more specific the need is to override the existing configuration of the teams configuration:
sinksConfig:
- ms_teams_sink:
    name: dynamic_ms_teams_sink
    webhook_url: teams channel incoming webhook  # see video below

I believe that at the moment Robusta require that we define a MSTeams like the dynamic_ms_teams_sink
The need is to override the webhook_url with the value taken from the label/annotation (probably annotations should be better).
In this way we can have an existing sink configuration that robusta needs to wire its stuff but we would dynamically send to different destinations every time.

@gioppoluca This will be available in the next version


Facing Issue while Saving the Production Prerequisites

Module: 02
Lab/Demo: 04
Task:
Step: 06-22
Description of issue

While saving the Production Prerequisites we are facing this issue.
Repro steps:
Select Route on the Action Pane then in the Maintain group, select Route details.
Select New.
In the Operation field, enter or select Assembly.
In the Scrap Percentage field, enter 20.
In the Link type field, select Soft.
Select New.
In the Oper. No. field, enter 20.
In the Operation field, enter or select Padding.
In the Scrap percentage field, enter 30.
In the Link type field, select Hard.
Select New.
In the Oper. No. field, enter 30.
In the Priority field, select Primary.
In the Operation field, enter or select Packing.
Refresh the page.
Select Save.
Close all pages.

Thanks for reporting this on GitHub! Module 2 / Case study 1A / Exercise ? Step 06-22. We are reviewing this and will provide an update once a resolution is in place. Please elaborate as to which exercise this issue is in reference to along with repo steps

Thanks for reporting this on GitHub! Module 2 / Case study 1A / Exercise ? Step 06-22. We are reviewing this and will provide an update once a resolution is in place. Please elaborate as to which exercise this issue is in reference to along with repo steps.
Module 2: Configure production prerequisites.
Exercise 4: Create an operation, assign relations, and create a route.
Step 06-22

Select Route on the Action Pane then in the Maintain group, select Route details.
Select New.
In the Operation field, enter or select Assembly.
In the Scrap Percentage field, enter 20.
In the Link type field, select Soft.
Select New.
In the Oper. No. field, enter 20.
In the Operation field, enter or select Padding.
In the Scrap percentage field, enter 30.
In the Link type field, select Hard.
Select New.
In the Oper. No. field, enter 30.
In the Priority field, select Primary.
In the Operation field, enter or select Packing.
Refresh the page.
Select Save.
Close all pages.

Thanks for reporting this on GitHub! I did not run into any issues during replication with errors on the Route details page. The route is created prior to creating the route relation as there has to be route details and assignments for the operation. The route contains the order of operations which sit within the route. The route group is automatically added to the grid after the first record is created for the Assembly operation.
It seems that you skipped steps 11 through 15 during the exercise. Please ensure to follow the instructions for completing the operations according to the steps. Please retry initiating the steps again.


upgrade to openshift-pipelines 1.11; have openshift-pipelines install PaC

We've tried this a few times now, but with my local reproducer, I've confirmed that 1.11 tekton controller (0.47.x  vs. 0.44.x for 1.10), fixes https://issues.redhat.com/browse/SRVKP-3131 , where as 1.10.4 does not, so an extra motivation to retry the leap to 1.11
Also had to do the additional step of having openshift-pipelines install PaC, as the 0.16 PaC yaml does not install the 1.11 PaC image correctly.
It gets the error
{"severity":"EMERGENCY","timestamp":"2023-06-20T17:24:16.183286264Z","logger":"pipelinesascode","caller":"v2/main.go:239","message":"Failed to start configuration manager","error":"configmap \"config-logging\" not found","stacktrace":"knative.dev/eventing/pkg/adapter/v2.MainWithInformers\n\t/go/src/github.com/openshift-pipelines/pipelines-as-code/vendor/knative.dev/eventing/pkg/adapter/v2/main.go:239\nknative.dev/eventing/pkg/adapter/v2.MainWithEnv\n\t/go/src/github.com/openshift-pipelines/pipelines-as-code/vendor/knative.dev/eventing/pkg/adapter/v2/main.go:158\nknative.dev/eventing/pkg/adapter/v2.MainWithContext\n\t/go/src/github.com/openshift-pipelines/pipelines-as-code/vendor/knative.dev/eventing/pkg/adapter/v2/main.go:133\nmain.main\n\t/go/src/github.com/openshift-pipelines/pipelines-as-code/cmd/pipelines-as-code-controller/main.go:46\nruntime.main\n\t/usr/lib/golang/src/runtime/proc.go:250"}

If for some reason this does not hold water in RHTAP e2e's, I'll revert that and portion of the change, and use the 0.19 version of the upstream yaml.
Conversely, as our current manual deploy of tekton-chains via upstream yaml still works with 1.11, I left that alone and just bumped the image replacement.  I say we minimize the change there for now, and address that in a subsequent PR.

rosa failure on the upgrade test
/retest

@gabemontero Upgrade test is failing on the metrics test post-upgrade with:
Error from server (InternalError): error when creating "/workspace/source/operator/test/manifests/test/metrics/curl-metrics-service-pipeline.yaml": Internal error occurred: failed calling webhook "webhook.pipeline.tekton.dev": failed to call webhook: Post "https://tekton-pipelines-webhook.openshift-pipelines.svc:443/defaulting?timeout=10s": service "tekton-pipelines-webhook" not found

@gabemontero Upgrade test is failing on the metrics test post-upgrade with: Error from server (InternalError): error when creating "/workspace/source/operator/test/manifests/test/metrics/curl-metrics-service-pipeline.yaml": Internal error occurred: failed calling webhook "webhook.pipeline.tekton.dev": failed to call webhook: Post "https://tekton-pipelines-webhook.openshift-pipelines.svc:443/defaulting?timeout=10s": service "tekton-pipelines-webhook" not found

yeah I asked you about that in slack :-) ..... I think that means the 1.11 uninstall is not totally clean, and the webhook it is adding is not fully removed

also, per slack conversations, we have 2 chains controllers running, and there is not quick disable field like with PaC
need to take on having the operator deploy chains

I think at this point we go with @Roming22 's https://github.com/openshift-pipelines/pipeline-service/pull/688


UP-4429 Use BROWSE to determine portlet visibility in Customize Gallery, search, apis

https://issues.jasig.org/browse/UP-4429
Suggest this goes into uPortal 4.2.0 release since it includes a change to /api/portletList.  This change will also require uPortal 4.1 and prior to review their data entities to add BROWSE permissions when upgrading to uPortal 4.2.0
Change behavior of uPortal so it consistently uses BROWSE permission to determine if a portlet is available to a user in the Customize Gallery, Search results, and the /api/portletList API (used by Customize Gallery).  Also changed behavior of /api/portletList to include portlets with no categories in a Uncategorized category.
See Jira issue.  Previously there were inconsistencies in determining whether a user should see a portlet.  Now the various system aspects (gallery, Marketplace, Search, and /api/portletList) are consistent.
Changes
New category 'Uncategorized' in Customize Gallery
Portlets not in any category are put into a new category called Uncategorized.  For demonstration purposes, I removed the category from About.com College Life.

Customize gallery now uses BROWSE permission.  Doesn't matter if portlets have a category or not (previously no category hid portlets from customize gallery).

One consequence of this is administrative users will see portlets in the gallery they did not used to since administrative users have BROWSE on all portlets.

Portlet search and Marketplace Search now respect BROWSE permission
Users doing search no longer see portlets they don't have access to
Default/quickstart data updated
Corrects a few issues with portlets that user's shouldn't see being visible.

Coverage decreased (-0.02%) to 22.82% when pulling 4d4dc03fe9a09f55e84e57a7be44e8d1b0572135 on UP4429BrowseForSearchAndGallery into 6619b61023aaaa86b8b4cbd0327af773130fa08f on master.

Some of the changes feel unrelated, so I kind of wish they were in separate commits that were in separate pull requests.

Since we can now grant BROWSE within the portlet-definition.xml files, maybe we should drop the BROWSE-granting permission-set files and just grant this permission within the portlet-definition files, ala the way SUBSCRIBE is in practice granted?

Is none of this changeset amenable to coverage with unit testing?

:+1: -- this is what BROWSE should have meant when it was introduced, and it's quite good to do this cleanup.

RE unit testing, yes some of the change is amenable.  Unfortunately I ran over on time working on this and am backlogged on other work I need to get done so I decided to unfortunately punt on adding unit tests.  Sadly I looked for some to update and there were none either. :disappointed:

RE dropping BROWSE in permission-set, I don't think you want to do that.  It is still used for portlet categories; e.g. https://github.com/Jasig/uPortal/blob/uportal-4.2.0-M1/uportal-war/src/main/data/quickstart_entities/permissions_set/Everyone_BROWSE_SpecificPortlets-permission-set.xml.  I think that is pretty useful.

Will merge Thu 4/2 if no objections.


LP image update

Images in synergy with the colors of the dApp, along with visual quality and branding.

The landing page is delivered in https://staging.web3task.w3d.community/


CLI: On new machine, present instructions for installing sources

When a user first installs codeclimbers, they will have no data and no sources. Present the add sources modal so they know how to get started

I wonder if there should be a landing page if the account doesn't have any sources, where it just goes over how to add one, and transitions to the home page as soon as it gets a pulse from one?

Rather than a different page, maybe the "empty" state for the components directs the users to the sources. Like the time widget empty state is just a button with some text that says "To start tracking your time, add a source"

I like that too.
Another idea I have is to use the animation we want to do for deep work timers, and outline the add source button with it when there's no sources to really drive your attention there

Ooo, that's a nice way to do it. That's probably best of all these ideas because it teaches the user how to add sources the way they will always add sources

Fixed in https://github.com/CodeClimbersIO/cli/pull/145


tables and bib examples

fixes #14 and fixes #15

As new users pull this template, these examples are necessary. @venku122 please look this over and see if you think it's useful, no in-depth review required.

👍 :shipit:


nimble: Refactor UUID handling (ATT/GATT)

This patch introduces dedicated type for UUIDs in order to handle them
consistently everywhere. It not only makes handling of UUIDs easier,
but also allows for some flash and RAM savings due to some extra code
being removed and less memory required to store UUIDs in common cases
(especially with 16-bit UUIDs).
IMPORTANT NOTES

ble_uuid_t is a "stub" type which shall be always used as a pointer;
to access actual UUID value other helpers and types shall be used
when registering services using new API, only UUID pointer is stored
for all attributes (there is no copy of value made) thus it is not
allowed to pass UUIDs created e.g. on stack
it is illegal to have 128-bit UUID declared which has its 16-bit UUID
equivalent - there is no implicit conversion from 128-bit to 16-bit
UUID done inside Nimble
...but this means you can rely on UUID type received from Nimble and
128-bit UUID will be always non-Bluetooth one

Below are few examples how to use new UUIDs API:
// 16-bit UUID value with initialization
ble_uuid16_t uuid16 = BLE_UUID16_INIT(0x2801);
// 128-bit UUID value with initialization
ble_uuid128_t uuid128 = BLE_UUID128_INIT(0x00, 0x11, ... 0xFF);
// "stub" type is used to pass any type of UUID via API
ble_uuid_t *uuid1 = &uuid16.u;
ble_uuid_t *uuid2 = &uuid128.u;
// comparing UUIDs is really easy now
if (ble_uuid_cmp(uuid1, uuid2) == 0) { /* equal */ )
// since in most cases we use 16-bit UUIDs, it's convenient to easily
// retrieve 16-bit value (or 0 if UUID is not 16-bit)
uint16_t u16 = ble_uuid_u16(uuid1);
// the above is equivalent of
u16 = uuid1->type == BLE_UUID_TYPE_16 ? BLE_UUID16(uuid1)->value : 0;
// we can easily define UUID inline as well, e.g. when defining service
static const struct ble_gatt_svc_def ble_svc_gap_defs[] = {
{
.type = BLE_GATT_SVC_TYPE_PRIMARY,
.uuid = BLE_UUID16_DECLARE(BLE_SVC_GAP_UUID16),
(...)
// finally, if we need to store any UUID there is an union defined to help
ble_uuid_any_t uuid;
uuid.u16 = uuid16;

Thanks, Andrzej.  This is great.


Exception when receiving the response from the request / response after its TTL

Environment
Dotnet 3.1
MassTransit 7.1.1
Steps to Reproduce

Server + client configuration
Server sending a request over a request client from the server with a TTL of 15 seconds
Client takes longer than 15 seconds to respond

(might potentially require overriding the publisher endpoint queue name)

Expected Behavior
Server can continue to receive future responses on later requests.
Actual Behavior
Receiver is shut down. The skipped queue is not created

    "properties": {
      "MT-Reason": "fault",
      "MT-Fault-ExceptionType": "Microsoft.Azure.ServiceBus.MessagingEntityNotFoundException",
      "MT-Fault-Message": "Put token failed. status-code: 404, status-description: The messaging entity 'sb://zzz-url.servicebus.windows.net/ManagerPublisherQueue_skipped' could not be found. To know more visit https://aka.ms/sbResourceMgrExceptions.  TrackingId:6120b037-f29f-470b-991f-bf9541c00c0d_G30, SystemTracker:zzz-url.servicebus.windows.net:ManagerPublisherQueue_skipped, Timestamp:2021-03-18T01:43:21.",
      "MT-Fault-StackTrace": "   at Microsoft.Azure.ServiceBus.Core.MessageSender.OnSendAsync(IList`1 messageList)\r\n   at Microsoft.Azure.ServiceBus.RetryPolicy.RunOperation(Func`1 operation, TimeSpan operationTimeout)\r\n   at Microsoft.Azure.ServiceBus.RetryPolicy.RunOperation(Func`1 operation, TimeSpan operationTimeout)\r\n   at Microsoft.Azure.ServiceBus.Core.MessageSender.SendAsync(IList`1 messageList)\r\n   at MassTransit.Azure.ServiceBus.Core.Transport.BrokeredMessageMoveTransport.<>c__DisplayClass2_0.<<Move>b__0>d.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at GreenPipes.Filters.AsyncDelegateFilter`1.<>c__DisplayClass3_0.<<Send>g__SendAsync|0>d.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at GreenPipes.Agents.PipeContextSupervisor`1.GreenPipes.IPipeContextSource<TContext>.Send(IPipe`1 pipe, CancellationToken cancellationToken)\r\n   at GreenPipes.Agents.PipeContextSupervisor`1.GreenPipes.IPipeContextSource<TContext>.Send(IPipe`1 pipe, CancellationToken cancellationToken)\r\n   at GreenPipes.Agents.PipeContextSupervisor`1.GreenPipes.IPipeContextSource<TContext>.Send(IPipe`1 pipe, CancellationToken cancellationToken)\r\n   at MassTransit.Pipeline.Filters.DeadLetterTransportFilter.GreenPipes.IFilter<MassTransit.ReceiveContext>.Send(ReceiveContext context, IPipe`1 next)\r\n   at MassTransit.Pipeline.Filters.DeadLetterFilter.GreenPipes.IFilter<MassTransit.ReceiveContext>.Send(ReceiveContext context, IPipe`1 next)\r\n   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock)",
      "DeadLetterReason": "TTLExpiredException",
      "DeadLetterErrorDescription": "The message expired and was dead lettered."
    },

Reproducible Demo
Have not been able to reproduce this yet, but will upload something as soon as I can. It's not clear how to get get MassTransit to try to add the response to the _skippedqueue, as most of them usually go to the Deadletter queue just fine. Edit: actually, these deadlettered message sseem to only happen once the receiver has stopped receiving due to the above issue, so it's probably not deadlettering usually.  I suspect that maybe it occurs when this message is returned, and perhaps only when this response is returned after the TTL:
      "messageType": [
        "urn:message:MassTransit:Fault[[MyRequestType]]",
        "urn:message:MassTransit:Fault"
      ],

Have you tried with 7.1.6 by the way? There were some strange early bugs with ASB that works themselves out over a few releases.
Also, why if you have a named queue are you creating/destroying the queue so often? Why not just set it up without an expiration if it has a fixed name to avoid the issue entirely? (not to mention it's less work on ASB by not having to create/delete the queue constantly).

Since we haven't been able to replicate locally, the only place we can see
the issue is in production. I've updated our code to use 7.1.6 but I'm not
sure when they'll let it out into prod (since I can see some specific fixes
in 7.1.3 that at least appear related to what we've seen).

Also, why if you have a named queue are you creating/destroying the queue
so often
Is this in reference to the publish queue?
To be honest, I don't know why that was added, if you would advise removing
it I'm happy to remove any complications. I assume you are referring to the
300s timeout? That gets put on there but MT as far as I know, when it makes
the queue.

On Thu, Mar 18, 2021 at 8:28 PM Chris Patterson @.***>
wrote:

Have you tried with 7.1.6 by the way? There were some strange early bugs
with ASB that works themselves out over a few releases.
Also, why if you have a named queue are you creating/destroying the queue
so often? Why not just set it up without an expiration if it has a fixed
name to avoid the issue entirely? (not to mention it's less work on ASB by
not having to create/delete the queue constantly).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MassTransit/MassTransit/issues/2372#issuecomment-801885867,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHA4T5YF3Z3EFZMPPPAHRBLTEHWXBANCNFSM4ZL2Q2YQ
.

So when the consumer receives the message, and it has expired, I wonder if that is causing the Fault to be returned as a response. When in reality, it should be discarding the message without error. Hmm.

I'm pretty sure the update will fix the issue with the receive endpoint stopping. I'm going to call this "dupe" of https://github.com/MassTransit/MassTransit/issues/2289


Update docs.json

Typo. :)
Summary of the changes (Less than 80 chars)

Detail 1
Detail 2

Closes #bugnumber (in this specific format)

/AzurePipelines run

@ferdeen thanks for your contribution! Make sure to ⭐ the project if you haven't already :)


build_visit vtk: use of enum ”EndiannessType” without previous declaration

Describe the bug
Running approximately this:
./build_visit3_4_1 --system-cmake --system-python --system-qt --qt6
gives:
...
.../visit/VTK-9.2.6/IO/Image/vtkSEPReader.h:33:12: virhe: use of enum ”EndiannessType” without previous declaration
   33 | enum class EndiannessType : std::uint8_t
      |            ^~~~~~~~~~~~~~
.../visit/VTK-9.2.6/IO/Image/vtkSEPReader.h:33:27: virhe: expected unqualified-id before ”:” token
   33 | enum class EndiannessType : std::uint8_t
      |                           ^
.../visit/VTK-9.2.6/IO/Image/vtkSEPReader.h:103:19: virhe: ”int32_t” is not a member of ”std”; did you mean ”int32_t”?
  103 |   std::array<std::int32_t, 6> ComputeExtent() const;
      |                   ^~~~~~~
...

I bypassed compilation of QT and prior stuff in build_visit but assuming those compile this should still happen.
Expected behavior
VTK should compile successfully
Desktop

OS and version: Fedora 40

Changing to vtk 9.3.0 in build_visit seems to work:
        export VTK_FILE=${VTK_FILE:-"VTK-9.3.0.tar.gz"}
        export VTK_VERSION=${VTK_VERSION:-"9.3.0"}
        export VTK_SHORT_VERSION=${VTK_SHORT_VERSION:-"9.3"}
        export VTK_SHA256_CHECKSUM="fdc7b9295225b34e4fdddc49cd06e66e94260cb00efee456e0f66568c9681be9"

But compiling visit fails with
...
.../visit/visit3.4.1/src/visit_vtk/full/vtkCSGGrid.C: In member function ”vtkUnstructuredGrid* vtkCSGGrid::DiscretizeSpaceMultiPass(int, bool, const double*, const int*, const int*)”:
.../visit/visit3.4.1/src/visit_vtk/full/vtkCSGGrid.C:3019:16: virhe: ”class vtkThreshold” has no member named ”ThresholdByUpper”; did you mean ”ThresholdType”?
 3019 |     threshold->ThresholdByUpper(0.5);
      |                ^~~~~~~~~~~~~~~~
      |                ThresholdType
make[2]: *** [visit_vtk/full/CMakeFiles/visit_vtk.dir/build.make:127: visit_vtk/full/CMakeFiles/visit_vtk.dir/vtkCSGGrid.C.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:12260: visit_vtk/full/CMakeFiles/visit_vtk.dir/all] Error 2
make: *** [Makefile:156: all] Error 2

Don't know whether that's related to using vtk 9.3.0 instead of 9.2.6

Yes, API for VTK changed between 9.2 and 9.3.   VisIt 3.4.1 does not support VTK 9.3.
Your use of system Qt and Python might also not work witn VisIt 3.4.1, depending on the version of Qt / Python and how they were built.
Please see our docs on the subject of System libraries.

I have modified build_visit to patch the necessary VTK, qt and other files in order to build sucessfully with gcc-13.
I ran and tested in a  Fedora39 docker container.
If you would like to try the binary distro I created, it is available at:
https://github.com/visit-dav/visit/releases
Look for visit3_4_1.linux-x86_64-fedora39-beta.tar.gz.  You will also need the visit-install script.
Beyond that, I can make an updated build_visit3_4_1 script available to you, if you really need to build from sources.

I've never had problems installing visit binaries but thanks. Updated build_visit3_4_1 would be great as now I need to use my own plugin(s) which I understand requires compiling visit.

You don't need to build VisIt from source in order to build and use your own custom plugins.
The main thing is to run /path/to/installed/visit/bin/xml2cmake -clobber yourplugin.xml.
This will create a CMakeLists.txt that has all the information your plugin needs to build against the installed VisIt.
Then run cmake to generate your Makefiles and then run make.  Running make will write the shared libraries to
~/.visit in a manner that VisIt will understand in order to load your plugin.
The biggest thing is using a compatible compiler version.
We have detailed documentation on how to Create a database plugin.
While database reader specifics are contained there, the instructions should prove useful for plot or operator plugins, too.
When the new build_visit script is available, I will let you know.

@iljah, did you try the modified fedora39 distro?

Didn't try binary since they've always worked so far so I'm guessing that one would also work.

Here's a modified build_visit module for 3.4.1 that has fixes for building correctly with gcc13, it may help.
build_visit3_4_1_mod.tar.gz

Thanks, it seems to ignore  --system-qt, is that intentional?

Build eventually fails with:
...
-- Configuring done (11.2s)
CMake Error: The INTERFACE_QT_MAJOR_VERSION property of "Qt6::Core" does
not agree with the value of QT_MAJOR_VERSION already determined
for "viewersubjectproxy".
...
CMake Error: The INTERFACE_QT_MAJOR_VERSION property of "Qt6::Core" does
not agree with the value of QT_MAJOR_VERSION already determined
for "mcurvit".

-- Generating done (4.0s)
CMake Generate step failed.  Build files cannot be regenerated correctly.
VisIt configuration failed.

Perhaps system qt6 (6.7.1) is used somewhere instead of qt6 in third_party (6.4.2)? Build command in this case was: ./build_visit3_4_1_mod --system-cmake --system-python

Sorry to suggest, but a fresh run of build_visit might be in order.
Either completely destroy the directory where you previously ran build_visit, or start from a new directory, and have the script build all required libraries instead of attempting to use system versions.
I suggest this so that you can move forward, it is much too difficult to diagnose build_visit issues related to system versions of libraries.
So run:
./build_visit3_4_1_mod --required --qt6 --vtk9
This will allow building of the minimum libraries required to build visit.
You may need to also add --llvm --mesagl depending on the graphics drivers available.
Then if VisIt builds successfully, and you need more I/O libraries for the database plugins, you can add --optional or add each individual library like so: --hdf5 --silo.

Got several errors from ./build_visit3_4_1_mod --required --qt6 --vtk9 in new directory on fedora 40, first one:
...
Configuring Qt6 tools . . .
-- The CXX compiler identification is GNU 14.1.1
-- The C compiler identification is GNU 14.1.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/lib64/ccache/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/lib64/ccache/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Performing Test HAVE_STDATOMIC
-- Performing Test HAVE_STDATOMIC - Success
-- Found WrapAtomic: TRUE
-- Found OpenGL: /usr/lib64/libOpenGL.so
CMake Error at /usr/lib64/cmake/clang/ClangConfig.cmake:10 (find_package):
  Could not find a package configuration file provided by "LLVM" (requested
  version 18.1.6) with any of the following names:

    LLVMConfig.cmake
    llvm-config.cmake

  Add the installation prefix of "LLVM" to CMAKE_PREFIX_PATH or set
  "LLVM_DIR" to a directory containing one of the above files.  If "LLVM"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  cmake/FindWrapLibClang.cmake:14 (find_package)
  .../qtbase-everywhere-src-6.4.2/cmake/QtFindPackageHelpers.cmake:130 (find_package)
  configure.cmake:17 (qt_find_package)
  .../qtbase-everywhere-src-6.4.2/cmake/QtFeature.cmake:573 (include)
  src/CMakeLists.txt:21 (qt_feature_evaluate_features)

Right after above:
Building Qt6 tools . . .
gmake: Makefile: Tiedostoa tai hakemistoa ei ole (no such file/dir)
gmake: *** No rule to make target 'Makefile'. Seis.
Installing Qt6 tools . . .
CMake Error: Error processing file: .../qttools-everywhere-src-6.4.2-build/cmake_install.cmake
Building QT6 svg (~2 minutes)

Then:
...
[ 44%] Building CXX object src/svg/CMakeFiles/Svg.dir/qsvgtinydocument.cpp.o
Tiedostossa, joka sisällytettiin kohdasta .../qtsvg-everywhere-src-6.4.2/src/svg/qsvgrenderer.cpp:502:
.../qtsvg-everywhere-src-6.4.2-build/src/svg/Svg_autogen/include/moc_qsvgrenderer.cpp:12:10: vakava virhe: QtCore/qtmochelpers.h: Tiedostoa tai hakemistoa ei ole (no such file/dir)
   12 | #include <QtCore/qtmochelpers.h>
      |          ^~~~~~~~~~~~~~~~~~~~~~~
käännös keskeytyi.
make[2]: *** [src/svg/CMakeFiles/Svg.dir/build.make:181: src/svg/CMakeFiles/Svg.dir/qsvgrenderer.cpp.o] Error 1
make[2]: *** Odotetaan keskeneräisiä töitä....
make[1]: *** [CMakeFiles/Makefile2:895: src/svg/CMakeFiles/Svg.dir/all] Error 2
gmake: *** [Makefile:146: all] Error 2
Installing Qt6 svg . . .
-- Install configuration: "Release"
...

Last one:
...
compiling qwt_spline_polynomial.cpp
compiling qwt_symbol.cpp
qwt_symbol.cpp:20:10: vakava virhe: qsvgrenderer.h: Tiedostoa tai hakemistoa ei ole
   20 | #include <qsvgrenderer.h>
      |          ^~~~~~~~~~~~~~~~
käännös keskeytyi.
make[1]: *** [Makefile:1411: obj/qwt_symbol.o] Error 1
make[1]: Poistutaan hakemistosta ”.../qwt-6.3.0/src”
make: *** [Makefile:53: sub-src-make_first-ordered] Error 2
Qwt build failed. Giving up

Looks like qttools and qtsvg are (tried to) built several times with above errors.

Using ./build_visit3_4_1_mod --required --qt6 --vtk9 --llvm --mesagl in empty dir gives:
...
make[4]: Siirrytään hakemistoon ”.../mesa-17.3.9/src/gallium/targets/libgl-xlib”
  CC       xlib.lo
  CXXLD    libGL.la
/usr/bin/ld: ../../../../src/gallium/auxiliary/.libs/libgallium.a(u_debug_symbol.o):(.bss+0x0): multiple definition of `symbols_hash'; ../../../../src/gallium/auxiliary/.libs/libgallium.a(u_debug_stack.o):(.bss+0x0): first defined here
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:670: libGL.la] Error 1
...

Adding only --llvm to minimal command doesn't seems to change anything

Thanks, it seems to run fine. I don't have immediate need for compiling plugins but I'll try that eventually.


Add test for missing attributes in Visualization.can_be_private?

Closes #11136
Tested that reverting #11134 makes the tests fail with the same error as in production.
No acceptance needed, nor deploy to production needed, as there are only tests.

Just waiting for 🍏  would be enough.

Known Carto::Gme::TableGeocoder#run issue.


deadlock: speed up detecting leader change of the deadlock detector (…

…#5028)
Signed-off-by: youjiali1995<EMAIL_ADDRESS>
What have you changed?
Cherry pick #5028

/run-integration-ddl-test

/run-integration-compatibility-test


Data transfer service

This new service will enable heavy data transfer to be done. The idea is the following:

the user will specify a few options: data source (ZTF, Elasticc), filters (dates, class, ...), content (full packet, LC, cutouts)
A Spark job will be constructed based on options
This query to the Spark cluster via Livy
The output will be written on Kafka, so that it can be retrieved by the user.

We should also add a mechanism for hints to guess how many alerts need to be transfered. Note that the filtering mechanism will be first pre-defined (buttons and dropdowns). Later, we will provide ways to upload any filtering.
Roadmap:

[x] Web layout
[x] Spark query
[x] Livy job
[x] Hint provider

Done in #388


Re-enable ESLint Tests

[x] Remove the following rule overrides from client/package.json

[x] "no-unused-vars"
[x] "exhaustive-deps"
[x] "no-empty-patterns"

[x] Do not merge into production until after June 7th

Resolved.