Birt reports

Birt runtime environment seems to have problems when deployed on server which is run with java 8. The output from engine is:
enBIRT Report Viewerhttp://localhost:8180/birt/webcontent/birtfalsenullltrBIRT Report Viewer Toggle table of contentsToggle table of contentsRun reportRun reportExport dataExport dataExport reportExport reportPrint reportPrint reportPrint report on the serverPrint report on the server simpleExportDataDialogsimpleExportDataDialogsimpleExportDataDialogsimpleExportDataDialogExport DatasimpleExportDataDialogClosesimpleExportDataDialogsimpleExportDataDialog Available result setsAvailable ColumnsAdd allAdd allAddAddRemoveRemoveRemove allRemove allUpUpDownDownSelected ColumnsExport format:org.eclipse.birt.report.engine.dataextraction.csv">CSVcsvOutput encoding:Other(If blank,use the local encoding)Separator:Comma ( , )Semicolon ( ; )Colon ( : )Vertical Line ( | )Tab ( \t )Export column's data typeExport column as locale neutralExport data with Carriage ReturnsimpleExportDataDialogsimpleExportDataDialogsimpleExportDataDialogsimpleExportDataDialogOKOKsimpleExportDataDialogCancelCancel exceptionDialogexceptionDialogexceptionDialogexceptionDialogExceptionexceptionDialogCloseexceptionDialogexceptionDialog Show Exception Stack TraceHide Exception Stack TraceStack Trace:exceptionDialogexceptionDialogexceptionDialogexceptionDialogOKOKexceptionDialogCancelCancel parameterDialogparameterDialogparameterDialogparameterDialogParameterparameterDialogCloseparameterDialogparameterDialog Parameters marked with * are required. SessionId9dcd71fa20f3244b5bd934b43eceSessionId_displayText9dcd71fa20f3244b5bd934b43ece WSDLURLhttp://localhost:8180/Report/ReportingServiceBean?wsdlWSDLURL_displayTexthttp://localhost:8180/Report/ReportingServiceBean?wsdl SOAPEndPointhttp://localhost:8180/Report/ReportingServiceBeanSOAPEndPoint_displayTexthttp://localhost:8180/Report/ReportingServiceBeanparameterDialogparameterDialogparameterDialogparameterDialogOKOKparameterDialogCancelCancel exportReportDialogexportReportDialogexportReportDialogexportReportDialogExport ReportexportReportDialogCloseexportReportDialogexportReportDialog Export Format:docx">DOCXxls">Excelodp">OpenDocument Presentationods">OpenDocument Spreadsheetodt">OpenDocument Textpdf">PDFpostscript">PostScriptppt">PowerPointpptx">PPTXxls_spudsoft">Spudsoft Exceldoc">Wordxlsx">XLSXPagesAll pagesCurrent pagePages:( Enter page number(s) and/or page range(s). For example: 1-6 or 1,3,6 )Fit ToAutoActual sizeFit to whole pageexportReportDialogexportReportDialogexportReportDialogexportReportDialog
The problem occurs on birt runtime version 4.6 and 4.3 so we can assume the problem lies somwhere else.

This is official bug on eclipse birt runtime:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=459440

There is an issue with buffer="none" in jsp pages. It has to be removed from birt. In addition this has to be fixed as well in scope of this bug:
https://java.net/jira/browse/GLASSFISH-20880

As a workaround I may advise to deploy and set up birt runtime on glassfish 3 (or Tomcat) set up on Java 7. After that set REPORT_ENGINEURL property using platform_operator user to that address, ie:
http://<glassfish3_host>:/birt/frameset?__report=${reportname}.rptdesign&SessionId=${sessionid}&__locale=${locale}&WSDLURL=${wsdlurl}&SOAPEndPoint=${soapendpoint}&wsname=Report&wsport=ReportPort
work in progress to get the reports running on java8.

It cannot be fixed easy (in short time). I was able to get the reports without parameters to work but those which use parameters needs more work. We will wait for ecplise birt community to fix the problem.

Tested birt on:
Apache Tomcat/7.0.42
JVM Version 1.7.0_45-b18
Reports are displaying properly.

@DawidCh, did you report the problem as a bug in birt?

Nope, the bug is already reported. See comment.

@gertipoppel, we will document how to run birt.

Birt reports needs to be tested with https setings in configurationsettings.

I have added the corresponding information to the Installation Guide. It is currently in review. I will close this issue as soon as I get the information that the documentation is correct now.
The updated documentation is available in the GlassFish feature branch of the documentation repository.

I tested Birt with https setings and the reports work correct.

@gertipoppel Are you still waiting for review?

Included review comments. New version is available in the GlassFish feature branch of the documentation repository.

Checked on Windows Server 2016, jdk1.8u121, glassfish 4, build: BES_MASTER_DELIVERY-10192017/04/20 in SAML mode. It is working as expected.


Logs failing to send to Elasticsearch and not throwing an error

A few questions before you begin:

Is this an issue related to the Serilog core project or one of the sinks or
community projects.
This issue list is intended for Serilog Elasticsearch Sink issues. If this issue relates to another sink or to the code project,
please log on the related repository.  Please use Gitter chat and Stack Overflow  for discussions and questons.

Does this issue relate to a new feature or an existing bug?

[x ] Bug
[ ] New Feature

What version of Serilog.Sinks.Elasticsearch is affected?  Please list the related NuGet package.
7.1.0
What is the target framework and operating system? See target frameworks & net standard matrix.

[x ] netCore 2.2
[ ] netCore 1.0
[ ] 4.7
[ ] 4.6.x
[ ] 4.5.x

Please describe the current behavior?
I am attempting to log an error to Elasticsearch and using the EmitEventFailure flag of EmitEventFailureHandling.ThrowException and it is not throwing an exception.
I have an ElasticSearch Instance that I have set up and can access it by browsing to port 9200 but no logs are getting saved and there is no visibility into the error.   Below is the configuration

 Log.Logger = new LoggerConfiguration()
                            .MinimumLevel.Information()
                            .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
                            .Enrich.FromLogContext()
                            .WriteTo.Console()
                            .WriteTo.File("C:\\temp\\adminlog.txt", rollingInterval: RollingInterval.Day)
                            .WriteTo.Elasticsearch(new ElasticsearchSinkOptions(new Uri("http://vpsname.vps.ovh.ca:9200"))
                            {
                                AutoRegisterTemplate = true,
                                AutoRegisterTemplateVersion = AutoRegisterTemplateVersion.ESv6,
                                //IndexFormat = "AdminLogs-{0:yyyy.MM.dd}",
                                //OverwriteTemplate = true,
                                //RegisterTemplateFailure = RegisterTemplateRecovery.IndexToDeadletterIndex,
                                EmitEventFailure =
                                        EmitEventFailureHandling.WriteToSelfLog |
                                        EmitEventFailureHandling.RaiseCallback|
                                        EmitEventFailureHandling.ThrowException,
                                FailureCallback = e => {
                                    Console.WriteLine("Unable to submit event " + e.MessageTemplate);
                               }
                            })
                            .CreateLogger();

Please describe the expected behavior?
It should throw an error.  If I put a debugger on the FailureCallback it is getting called but no errror is thrown.
If the current behavior is a bug, please provide the steps to reproduce the issue and if possible a minimal demo of the problem

Hi,
I’m not in front of the code right now so I can’t say if it is the same version or not but we had a similar problem with a .Net Framework project and it only manifested when all three EmitEventFailureHandling values were set (as per the example on the serilog docs page!).
We only wanted callback or selflog in fact, so when we changed to just one of then, we got the expected result.
Try only setting the ThrowException option, then add RaiseCallback if you want that also and see what happens...

@runxc1 did the trick of @freeranger help you? If so, then it is still incorrect behavior as you should be able to use all three options.

So the behavior is definitely incorrect but before hearing back from anyone I rebuilt my ELK stack and am no longer getting the error.  I had used one of the images from Bitnami and so am unsure if there was some ELK configuration issue that the sink didn't handle or what as it was a black box as to why it was failing.


python311Packages.blosc2: 2.3.2 -> 2.5.1

Diff: https://github.com/Blosc/python-blosc2/compare/refs/tags/v2.3.2...v2.5.1
Changelog: https://github.com/Blosc/python-blosc2/releases/tag/v2.5.1
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 283845 run on x86_64-linux 1

24 packages failed to build:

python311Packages.apptools
python311Packages.apptools.dist
python311Packages.deepdish
python311Packages.deepdish.dist
python311Packages.elegy
python311Packages.elegy.dist
python311Packages.envisage
python311Packages.envisage.dist
python311Packages.flammkuchen
python311Packages.flammkuchen.dist
python311Packages.layoutparser
python311Packages.layoutparser.dist
python311Packages.mdtraj
python311Packages.mdtraj.dist
python311Packages.pandas-stubs
python311Packages.pandas-stubs.dist
python311Packages.pdfplumber
python311Packages.pdfplumber.dist
python311Packages.sfepy
python311Packages.sfepy.dist
python311Packages.stytra
python311Packages.stytra.dist
python311Packages.tables
python311Packages.tables.dist

2 packages built:

python311Packages.blosc2
python311Packages.blosc2.dist

tables is already broken.

See  #287081

Superseded by https://github.com/NixOS/nixpkgs/pull/287081


Where to get Twitch authentication from?

Is your feature request related to a problem? Please describe.
When setting up the bot, there is not direct documentation for how to get the TWITCH_CLIENT_ID, TWITCH_CLIENT_SECRET, and TWITCH_BOT_AUTH_TOKEN.  For folks just starting out it would be helpful to have this documented.
Describe the solution you'd like
Add documentation on where to find the values for the more esoteric environment variables.

@exegete46 thanks for contributing.
Check out the existing docs in our dev branch.  I think they cover what you're looking for.
https://github.com/MichaelJolley/number-one/blob/dev/CONTRIBUTING.md

Hola @exegete46! Did the link above cover what you're thinking?

Apologies, your reply got lost in my emails somewhere.  I should have read through the CONTRIBUTING before opening a pull request, sorry.
The documentation in CONTRIBUTING does address my concerns.  The reason I was looking for the information in the README, is that I was expecting it to be listed for someone using the app, rather than contributing.


What does it need network access for?

Probably because you can send bug reports and feedback directly from within the app. Also the check for updates feature.


MotionCor3 1.1.1

MotionCor3 1.1.1 changes

Created LibSrc directory where the source code of Util and Mrcfile are provided.
Removed the dependency on libcuutil.a
Improved CTF estimation
Bug fix in CFmIntParam.cpp, CBufferPool, and CGpuBuffer
Added -InSkips for skipping movie files whose names have specified strings.

Thanks for all of this!
Shawn
On Wed, Feb 21, 2024 at 10:31 PM apeck12 @.***> wrote:

Merged #15 https://github.com/czimaginginstitute/MotionCor3/pull/15
into main.
—
Reply to this email directly, view it on GitHub
https://github.com/czimaginginstitute/MotionCor3/pull/15#event-11886518452,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BBUDUP4Y25EFAUPFDTUF75LYU3Q3XAVCNFSM6AAAAABDUHAEECVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHA4DMNJRHA2DKMQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Fire customEvent from domready so that prototype kits can hook into it

Fire a customEvent from the onReady function of domready.js so that the prototype kit can listen for that event and delay booting of components until the dom is ready and polyfills have loaded.

 Issue #177: Fire customEvent from domready so that prototype kits can hook into it


Support password-protected PDFs

This proposal aims to support specifying a password for opening PDFs.

thanks. this is now deployed, pending nuget updating their cache (15min)


Change Data Capture

Closes #2993.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a8a33012e6cbf96776e4b8e499bc0777dc32e96a/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/78be40f91c6e33c513af7adb4178e8c80604bebc/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/8d4fad12ed9cbb675a57eebbdc3caf0dd4fda240/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a004b8a8b4bbbc580bb84ccc125ff7ef54172e52/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/49eb216123131a53437ff7bad685ab12c1b56edd/

Review status: :shipit: complete! 0 of 0 LGTMs obtained

v2.1/create-changefeed.md, line 25 at r1 (raw file):

## Synopsis

{% include sql/{{ page.version.version }}/diagrams/create_database.html %}

TO DO: generate new diagram

Comments from Reviewable

Looking good so far! Here's my first pass. I'll think some more about the ordering guarantees section and also get you the known limitations

Review status: :shipit: complete! 0 of 0 LGTMs obtained

v2.1/change-data-capture.md, line 3 at r1 (raw file):

---
title: Change Data Capture (CDC)
summary: Partitioning is an enterprise feature that gives you row-level control of how and where your data is stored.

copy paste error?

v2.1/change-data-capture.md, line 53 at r1 (raw file):

For more information, see [`CREATE CHANGEFEED`](create-changefeed.html).

### Pause

also unpause I guess?

v2.1/change-data-capture.md, line 158 at r1 (raw file):

    This will start up the changefeed in the background and return the `job_id`. The changefeed writes to Kafka and survives node failures.

9. In a new terminal, start watching the Kafka topic:

we should note that the initial scan has output the state of the table as of when the changefeed started (so the initial value of "Petee" is missing")

v2.1/create-changefeed.md, line 29 at r1 (raw file):

## Parameters

Parameter | Description

we should also document INTO and WITH (https://github.com/cockroachdb/cockroach/blob/fb4e761f83623e862d9896af7cded1f7dc5770e4/pkg/ccl/changefeedccl/changefeed_stmt.go#L36-45)
the INTO uri is very similar to what we've done with BACKUP/RESTORE/IMPORT where the "scheme" of the uri indicates what type it is and there are query parameters that vary per type.

the kafka scheme currently only has topic_prefix which adds a prefix to all the topic names it has
So CREATE CHANGEFEED FOR TABLE foo INTO 'kafka://...?topic_prefix=bar_' would emit things under topic bar_foo instead of foo.

the available WITH parameters are  cursor, envelope, and timestamps

WITH timestamps turns on the updated and resolved timestamps that we talk about in the ordering section. we might make this the default in 2.1
WITH envelope=key_only only emits the key and no value (this is faster and some people only want to know when the key changes). WITH envelope=row is the default. I'm fine leaving this out of the alpha docs if you want. in 2.1, there will also be a WITH envelope= diff that emits the old and new value of the changed row, but this is not in the alpha
WITH cursor=<timestamp> starts emitting any changes after the given timestamp, but doesn't output the current state of the table first. if cursor is not specified, the changefeed starts by doing a consistent scan of all the watched rows and emits the current value, then moves to emitting any changes that happen after that
WITH format=json is the default. in 2.1, we'll also have WITH format=avro

v2.1/create-changefeed.md, line 32 at r1 (raw file):

----------|------------
`IF NOT EXISTS` | Create a new changefeed only if a changefeed of the same name does not already exist; if one does exist, do not return an error.
`name` | The name of the changefeed to create, which [must be unique](#create-fails-name-already-in-use) and follow these [identifier rules](keywords-and-identifiers.html#identifiers).

note: name will be in 2.1 but is not present on the alpha. I hadn't thought about IF NOT EXISTS, but that's a good idea. also not in the alpha

Comments from Reviewable

Review status: :shipit: complete! 0 of 0 LGTMs obtained

v2.1/change-data-capture.md, line 3 at r1 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
copy paste error?

oops. fixed

v2.1/change-data-capture.md, line 53 at r1 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
also unpause I guess?

Done.

v2.1/change-data-capture.md, line 158 at r1 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
we should note that the initial scan has output the state of the table as of when the changefeed started (so the initial value of "Petee" is missing")

Done.

v2.1/create-changefeed.md, line 29 at r1 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
we should also document INTO and WITH (https://github.com/cockroachdb/cockroach/blob/fb4e761f83623e862d9896af7cded1f7dc5770e4/pkg/ccl/changefeedccl/changefeed_stmt.go#L36-45)
the INTO uri is very similar to what we've done with BACKUP/RESTORE/IMPORT where the "scheme" of the uri indicates what type it is and there are query parameters that vary per type.

the kafka scheme currently only has topic_prefix which adds a prefix to all the topic names it has
So CREATE CHANGEFEED FOR TABLE foo INTO 'kafka://...?topic_prefix=bar_' would emit things under topic bar_foo instead of foo.

the available WITH parameters are  cursor, envelope, and timestamps

WITH timestamps turns on the updated and resolved timestamps that we talk about in the ordering section. we might make this the default in 2.1
WITH envelope=key_only only emits the key and no value (this is faster and some people only want to know when the key changes). WITH envelope=row is the default. I'm fine leaving this out of the alpha docs if you want. in 2.1, there will also be a WITH envelope= diff that emits the old and new value of the changed row, but this is not in the alpha
WITH cursor=<timestamp> starts emitting any changes after the given timestamp, but doesn't output the current state of the table first. if cursor is not specified, the changefeed starts by doing a consistent scan of all the watched rows and emits the current value, then moves to emitting any changes that happen after that
WITH format=json is the default. in 2.1, we'll also have WITH format=avro

Done.

v2.1/create-changefeed.md, line 32 at r1 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
note: name will be in 2.1 but is not present on the alpha. I hadn't thought about IF NOT EXISTS, but that's a good idea. also not in the alpha

ah right, duh. hid for now

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/347b860e2367e8ac7405e8a4c114d9d38efec05a/

Review status: :shipit: complete! 0 of 0 LGTMs obtained

v2.1/create-changefeed.md, line 25 at r1 (raw file):
Previously, lhirata wrote…
TO DO: generate new diagram

will add actual diagram for 2.1

v2.1/create-changefeed.md, line 33 at r2 (raw file):

Targets:
    TABLE <table_name> [, ...]

Can we do changefeeds on partitions / individual rows yet? If so, how do we do that?

Comments from Reviewable

Review status: :shipit: complete! 0 of 0 LGTMs obtained

v2.1/change-data-capture.md, line 21 at r3 (raw file):

While CockroachDB is an excellent system of record, it also needs to coexist with other systems. For example, you might want to keep your data mirrored in full-text indexes, analytics engines, or big data pipelines.

The core feature of CDC is the [`CHANGEFEED`](create-changefeed.html). Changefeeds target a whitelist of databases, tables, partitions, rows, or a combination of these; called the "watched rows." Every change to a watched row is emitted as a record in a configurable format (i.e., `JSON` or Avro) to a configurable sink (i.e., [Kafka](https://kafka.apache.org/).

should we remove references to partitions and rows here for the now?

v2.1/change-data-capture.md, line 135 at r3 (raw file):

    {% include copy-clipboard.html %}
    ~~~ sql
    > CREATE TABLE demo_cdc (

can we call this dogs and call the database cdc_demo? (or office_dogs or something)

v2.1/change-data-capture.md, line 197 at r3 (raw file):

## Known limitations

<!-- TO DO: Dan to add -->

Whoops, this keeps slipping my mind. I'll do it right now.

v2.1/create-changefeed.md, line 33 at r2 (raw file):
Previously, lhirata wrote…
Can we do changefeeds on partitions / individual rows yet? If so, how do we do that?

nope. this is one of the alpha limitations
also, we can only do one table or database per changefeed right now (so no [, ...])

v2.1/create-changefeed.md, line 36 at r3 (raw file):

    DATABASE <database_name> [, ...]

Location:

Should this also be "sink"?

Comments from Reviewable

Review status: :shipit: complete! 0 of 0 LGTMs obtained

v2.1/change-data-capture.md, line 197 at r3 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
Whoops, this keeps slipping my mind. I'll do it right now.

Okay, here's what I have. The tense is all over the place, we should clean that up. Also, I tried to omit things like "does not yet", but that makes this list sound terrifying if you don't read the header. Thoughts?
The following are limitations in July 2nd alpha, but they will be addressed before the final 2.1 release.

Changefeeds created with the alpha may not be compatible with future alphas and the final 2.1 release. Do not use this feature on production data. (Lauren: we should also add this to the big red warning we have at the top of the page.)
The CockroachDB core CHANGEFEED is not ready for external testing.
Some intermediate updates on frequently changed rows are never emitted. [#27101]
Changefeed progress is not exposed to the user.
The SQL interface is not final and may change.
Changefeeds only work on tables with a single COLUMN FAMILY (which is the default for new tables).
Changefeeds do not work on interleaved tables.
Many DDL queries (including TRUNCATE, RENAME, and DROP) will cause undefined behavior on a CHANGEFEED watching the affected tables.
Changefeeds cannot be backed up or restored.
Changefeed behavior under most types of failures/degraded conditions is not yet tuned.
Changefeed internal buffering does not respect memory use limitations.
Changefeeds do not scale horizontally or to high traffic workloads.
Changefeeds use a pull model, but will use a push model in 2.1, lowering latencies considerably.
Changefeeds are slow on data recently loaded via RESTORE/IMPORT.
Additional format options will be added, including Avro.
Additional envelope options will be added, including one that includes the old and new values for the changed row.
Additional target options will be added, including partitions and ranges of primary key rows.

Comments from Reviewable

Basically LGTM for today's release, after addressing some nits/questions and Dan's additional content. I can take another look once you're ready.

Review status: :shipit: complete! 0 of 0 LGTMs obtained

v2.1/change-data-capture.md, line 7 at r3 (raw file):
Given that this feature works only with Kafka, we probably want to mention that system in the intro. Here's what Nate wrote for the release notes, in case it helps:

Stream changes to Kafka with CDC [enterprise] - CockroachDB can now stream changes into Apache Kafka to support downstream processing such as reporting, caching, or full-text indexing.

Or does this work with systems other than Kafka? If no, I think we might want to make sure the page doesn't read as though that's possible. This can be follow-up work though.

v2.1/change-data-capture.md, line 21 at r3 (raw file):

While CockroachDB is an excellent system of record, it also needs to coexist with other systems. For example, you might want to keep your data mirrored in full-text indexes, analytics engines, or big data pipelines.

The core feature of CDC is the [`CHANGEFEED`](create-changefeed.html). Changefeeds target a whitelist of databases, tables, partitions, rows, or a combination of these; called the "watched rows." Every change to a watched row is emitted as a record in a configurable format (i.e., `JSON` or Avro) to a configurable sink (i.e., [Kafka](https://kafka.apache.org/).

nits:

remove the semicolon in the first sentence.
Add closing parenthesis at end of second sentence.

v2.1/change-data-capture.md, line 58 at r3 (raw file):

{% include copy-clipboard.html %}
~~~

Need to add sql to get syntax highlighting to work.

v2.1/change-data-capture.md, line 64 at r3 (raw file):

For more information, see [`PAUSE JOB`](pause-job.html).

## Resume

Make this an h3.

v2.1/change-data-capture.md, line 69 at r3 (raw file):

{% include copy-clipboard.html %}
~~~

Need to add sql to get syntax highlighting to work.

v2.1/change-data-capture.md, line 80 at r3 (raw file):

{% include copy-clipboard.html %}
~~~

Need to add sql to get syntax highlighting to work.

v2.1/change-data-capture.md, line 90 at r3 (raw file):

### Create a changefeed connected to Kafka

In this example, you'll set up a changefeed that is connected to a Kafka sink.

I think this example is for testing CDC with a single-node local cluster? If so, we should be explicit about that.

v2.1/change-data-capture.md, line 167 at r3 (raw file):

    ~~~

    This will start up the changefeed in the background and return the `job_id`. The changefeed writes to Kafka and survives node failures.

Since this is a single-node local cluster, node failures are kind of beside-the-point. I wonder if we should make this example a multi-node cluster, either local or real? We could then kill one node and prove that the changefeed keeps going. This can come later, though.
Also something for later: We might want to use one of the workload load gens to make this more interesting.

Comments from Reviewable

Review status: :shipit: complete! 0 of 0 LGTMs obtained

v2.1/change-data-capture.md, line 23 at r3 (raw file):

The core feature of CDC is the [`CHANGEFEED`](create-changefeed.html). Changefeeds target a whitelist of databases, tables, partitions, rows, or a combination of these; called the "watched rows." Every change to a watched row is emitted as a record in a configurable format (i.e., `JSON` or Avro) to a configurable sink (i.e., [Kafka](https://kafka.apache.org/).

## Ordering guarantees

Here's a reordering of what you have in this section that I think is a bit clearer to me

In the common case, each version of a row will be emitted once. However, some (infrequent) conditions will cause them to be repeated. This gives our changefeeds an at-least-once delivery guarantee.
Once an update to a given row is emitted, it is guaranteed that all previous updates to that row have been emitted.
If a row is modified more than once in the same transaction, only the last change will be emitted.
Rows are sharded between Kafka partitions by the row’s primary key.
The WITH timestamps option adds an update timestamp to each emitted row. It also causes periodic resolved timestamp messages to be emitted to each Kafka partition. A resolved timestamp is a guarantee that no (previously unseen) rows with a lower update timestamp will be emitted on that partition.
Cross-row and cross-table order guarantees are not given. However, the resolved timestamp notifications on every Kafka partition can be used to provide strong ordering and global consistency guarantees by buffering records in between timestamp closures. (Because CockroachDB supports transactions that can affect any part of the cluster, there is no way to horizontally divide the cluster's transaction log in a way where each piece is independent, so it's impossible for us to scale this in the general case.)

Comments from Reviewable

I think that's everything I have, so LGTM to me after addressing outstanding comments (though I'd perfer to take a pass on the final version before merging)

Review status: :shipit: complete! 0 of 0 LGTMs obtained

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/99f15f6291c3c208386edb46dbb1b070bc25a4c1/

Review status: :shipit: complete! 0 of 0 LGTMs obtained

v2.1/change-data-capture.md, line 7 at r3 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Given that this feature works only with Kafka, we probably want to mention that system in the intro. Here's what Nate wrote for the release notes, in case it helps:

Stream changes to Kafka with CDC [enterprise] - CockroachDB can now stream changes into Apache Kafka to support downstream processing such as reporting, caching, or full-text indexing.

Or does this work with systems other than Kafka? If no, I think we might want to make sure the page doesn't read as though that's possible. This can be follow-up work though.

Updated. Only Kafka is supported - will update to be more specific.

v2.1/change-data-capture.md, line 21 at r3 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
should we remove references to partitions and rows here for the now?

Done.

v2.1/change-data-capture.md, line 21 at r3 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
nits:

remove the semicolon in the first sentence.
Add closing parenthesis at end of second sentence.

Done.

v2.1/change-data-capture.md, line 23 at r3 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
Here's a reordering of what you have in this section that I think is a bit clearer to me

In the common case, each version of a row will be emitted once. However, some (infrequent) conditions will cause them to be repeated. This gives our changefeeds an at-least-once delivery guarantee.
Once an update to a given row is emitted, it is guaranteed that all previous updates to that row have been emitted.
If a row is modified more than once in the same transaction, only the last change will be emitted.
Rows are sharded between Kafka partitions by the row’s primary key.
The WITH timestamps option adds an update timestamp to each emitted row. It also causes periodic resolved timestamp messages to be emitted to each Kafka partition. A resolved timestamp is a guarantee that no (previously unseen) rows with a lower update timestamp will be emitted on that partition.
Cross-row and cross-table order guarantees are not given. However, the resolved timestamp notifications on every Kafka partition can be used to provide strong ordering and global consistency guarantees by buffering records in between timestamp closures. (Because CockroachDB supports transactions that can affect any part of the cluster, there is no way to horizontally divide the cluster's transaction log in a way where each piece is independent, so it's impossible for us to scale this in the general case.)

Done.

v2.1/change-data-capture.md, line 58 at r3 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Need to add sql to get syntax highlighting to work.

Done.

v2.1/change-data-capture.md, line 64 at r3 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Make this an h3.

Done.

v2.1/change-data-capture.md, line 69 at r3 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Need to add sql to get syntax highlighting to work.

Done.

v2.1/change-data-capture.md, line 80 at r3 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Need to add sql to get syntax highlighting to work.

Done.

v2.1/change-data-capture.md, line 90 at r3 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
I think this example is for testing CDC with a single-node local cluster? If so, we should be explicit about that.

Done.

v2.1/change-data-capture.md, line 135 at r3 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
can we call this dogs and call the database cdc_demo? (or office_dogs or something)

Done.

v2.1/change-data-capture.md, line 167 at r3 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Since this is a single-node local cluster, node failures are kind of beside-the-point. I wonder if we should make this example a multi-node cluster, either local or real? We could then kill one node and prove that the changefeed keeps going. This can come later, though.
Also something for later: We might want to use one of the workload load gens to make this more interesting.

Done.
Will update the example later.

v2.1/change-data-capture.md, line 197 at r3 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
Okay, here's what I have. The tense is all over the place, we should clean that up. Also, I tried to omit things like "does not yet", but that makes this list sound terrifying if you don't read the header. Thoughts?
The following are limitations in July 2nd alpha, but they will be addressed before the final 2.1 release.

Changefeeds created with the alpha may not be compatible with future alphas and the final 2.1 release. Do not use this feature on production data. (Lauren: we should also add this to the big red warning we have at the top of the page.)
The CockroachDB core CHANGEFEED is not ready for external testing.
Some intermediate updates on frequently changed rows are never emitted. [#27101]
Changefeed progress is not exposed to the user.
The SQL interface is not final and may change.
Changefeeds only work on tables with a single COLUMN FAMILY (which is the default for new tables).
Changefeeds do not work on interleaved tables.
Many DDL queries (including TRUNCATE, RENAME, and DROP) will cause undefined behavior on a CHANGEFEED watching the affected tables.
Changefeeds cannot be backed up or restored.
Changefeed behavior under most types of failures/degraded conditions is not yet tuned.
Changefeed internal buffering does not respect memory use limitations.
Changefeeds do not scale horizontally or to high traffic workloads.
Changefeeds use a pull model, but will use a push model in 2.1, lowering latencies considerably.
Changefeeds are slow on data recently loaded via RESTORE/IMPORT.
Additional format options will be added, including Avro.
Additional envelope options will be added, including one that includes the old and new values for the changed row.
Additional target options will be added, including partitions and ranges of primary key rows.

Added.

v2.1/create-changefeed.md, line 33 at r2 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
nope. this is one of the alpha limitations
also, we can only do one table or database per changefeed right now (so no [, ...])

Done.

v2.1/create-changefeed.md, line 36 at r3 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
Should this also be "sink"?

Done.

Comments from Reviewable

@jseldess @danhhz TFTRs! Can you take a final look before I merge for the alpha? Thanks

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/93aa4a34a9032044a290aa5bcf5745c6423d4f58/

 with some final comments.

Review status: :shipit: complete! 0 of 0 LGTMs obtained (and 1 stale)

v2.1/change-data-capture.md, line 7 at r3 (raw file):
Thanks, Lauren. Would you allow me one more nitty rewrite?

Change data capture (CDC) provides efficient, distributed, row-level change feeds into Apache Kafka for downstream processing such as reporting, caching, or full-text indexing.

Also, you need to add a space after </span>.

v2.1/change-data-capture.md, line 205 at r5 (raw file):

- The CockroachDB core `CHANGEFEED` is not ready for external testing.
- Some intermediate updates on frequently changed rows are never emitted. [#27101]

Do we want [#27101] at the end of the line?

v2.1/change-data-capture.md, line 208 at r5 (raw file):

- Changefeed progress is not exposed to the user.
- The SQL interface is not final and may change.
- Changefeeds only work on tables with a single column family (which is the default for new tables).

Make column family a link to column-families.html.

v2.1/change-data-capture.md, line 209 at r5 (raw file):

- The SQL interface is not final and may change.
- Changefeeds only work on tables with a single column family (which is the default for new tables).
- Changefeeds do not work on interleaved tables.

Make interleaved tables a link interleave-in-parent.html.

v2.1/change-data-capture.md, line 211 at r5 (raw file):

- Changefeeds do not work on interleaved tables.
- Many DDL queries (including `TRUNCATE`, `RENAME`, and `DROP`) will cause undefined behavior on a changefeed watching the affected tables.
- Changefeeds cannot be backed up or restored.

Make backed up a link to backup.html and restored a link to restore.html.

v2.1/change-data-capture.md, line 216 at r5 (raw file):

- Changefeeds do not scale horizontally or to high traffic workloads.
- Changefeeds use a pull model, but will use a push model in v2.1, lowering latencies considerably.
- Changefeeds are slow on data recently loaded via `RESTORE` or `IMPORT`.

Make RESTORE a link to restore.html and IMPORT and link to import.html.

Comments from Reviewable

Review status: :shipit: complete! 0 of 0 LGTMs obtained (and 1 stale)

v2.1/change-data-capture.md, line 7 at r3 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Thanks, Lauren. Would you allow me one more nitty rewrite?

Change data capture (CDC) provides efficient, distributed, row-level change feeds into Apache Kafka for downstream processing such as reporting, caching, or full-text indexing.

Also, you need to add a space after </span>.

Done.

v2.1/change-data-capture.md, line 205 at r5 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Do we want [#27101] at the end of the line?

Removed.

v2.1/change-data-capture.md, line 208 at r5 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Make column family a link to column-families.html.

Done.

v2.1/change-data-capture.md, line 209 at r5 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Make interleaved tables a link interleave-in-parent.html.

Done.

v2.1/change-data-capture.md, line 211 at r5 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Make backed up a link to backup.html and restored a link to restore.html.

Done.

v2.1/change-data-capture.md, line 216 at r5 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Make RESTORE a link to restore.html and IMPORT and link to import.html.

Done.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/03e6791aaf51c26a6bdabd826b9122a22971ae7e/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/589b9c1f418866bb178c41e27e31b0223c481c6b/

Review status: :shipit: complete! 1 of 0 LGTMs obtained (and 1 stale)

v2.1/change-data-capture.md, line 35 at r6 (raw file):
Previously, danhhz (Daniel Harrison) wrote…
I realize I wrote this, but can you make this something like "are not directly given", plz

Done.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1cbcade06a1bb0f069a24ce3640d0c51023441b2/


Dynamic Nested Routes Not Support

Version
v1.4.2
Reproduction link
null
Steps to reproduce
my pages

What is expected ?
routes: [
		{
			path: "/brand/brief/:categoryId/:brandId",
			component: "pages/brand/brief/_category/_brandId/index.vue",
			name: "brand-brief-categoryId-brandId"
		},
],

What is actually happening?
routes: [
		{
			path: "/brand/brief/:categoryId?/:brandId?",
			component: "pages/brand/brief/_category/_brandId/index.vue",
			name: "brand-brief-categoryId-brandId"
		},
],

Additional comments?
I dont want that '?' , is that a bug?

This bug report is available on Nuxt community (#c7543)

This is no bug. :relaxed:
As you don't have other pages defined yet, the dynamic variables are optional, so brand/brief/, /brand/brief/a/ and /brand/brief/a/b/ will all link to the index.vue. As soon as you set these up (f.ex. pages/brand/brief/_category/index.vue ) the ? will vanish from the route and the parameters will become mandatory.
Alternatively, you can set up route validation

OK，thx🤝。 I used the extendRoutes to do this. like that:
  router: {
    extendRoutes () {
      return [
        {
          path: '/brand/brief/:categoryId/:brandId',
          component: resolve(__dirname, 'pages/brand/brief/index.vue'),
          name: 'brand-brief'
        }
      ]
    }
  },

That's another way.


Normalize null input behavior

This PR normalizes the behavior for null or not string inputs.
escapeHtml() and escapeUrl() are using a implicit string cast so $escaper->escapeHtml(null) and $escaper->escapeUrl(null) will return an empty string.
$escaper->escapeCss/escapeJs/escapeHtmlAttr(null) will throw the following Exception instead:
Zend\Escaper\Exception\RuntimeException: String to be escaped was not valid UTF-8 or could not be converted.
With this PR all inputs will be casted to a string so the behavior of all methods is consistent.

I think the exception raised on escapeJs has sense because if someone want to print null as JS output the function should be or return the PHP string "null" or warn the user he/she must check if the value is null and print the null value itself.
($value === null) ? "null" : escapeJs($value)
If the exception is not raised the user is not aware he may produce invalid JS code.
var foo = escapeJs(null);

Uncaught SyntaxError: Unexpected token ;

So, the method should throw exception or return the PHP string "null"
The same reasoning is applicable to CSS. If you try to escape an invalid value then exception should be thrown.
Finally, the idea behind of different escape strategies its language require his own set of rules so I don't think any normalization (in the output) its possible. The only normalization could be in the input.

I think the exception raised on escapeJs has sense because if someone want to print null as JS output the function should be or return the PHP string "null" or warn the user he/she must check if the value is null and print the null value itself.

A couple of things before we go anywhere:

this would be a huge BC break
the escapers (All of them) are supposed to work with string-alike values, with string-alike following PHP's semantics

Suggestion:

verify that input value is either a string, an int, a float, a double or an object with __toString, then cast
fail with an exception in all other cases

So, the method should throw exception or return the PHP string "null"

Exception please: this would otherwise be a "WTF" from a user perspective

the escapers (All of them) are supposed to work with string-alike values, with string-alike following PHP's semantics

Wouldn't that imply also casting null/false to '' and true to '1'?

verify that input value is either a string, an int, a float, a double or an object with __toString, then cast

That seems to be overly strict to me given the loosely typed nature of PHP:
protected function isCastableToString($string)
{
    return is_string($string)
        || is_int($string)
        || is_float($string)
        || is_double($string)
        || (is_object($string) && method_exists($string, '__toString'));
}

I would rather keep the existing null, true and false behavior of escapeHtml() and escapeUrl() to minimize the BC break:
protected function isCastableToString($string)
{
    return is_scalar($string) || ($string) && method_exists($string, '__toString'));
}

Wouldn't that imply also casting null/false to '' and true to '1'?

Agree

That seems to be overly strict to me given the loosely typed nature of PHP:

This is a security-sensitive component: make it fail a lot, and eagerly.
Anyway, more strictness reduces space for misinterpretation as well, and is pretty much always welcome.

Closing. As noted, we cannot accept this as-is due to the huge BC and security implications. @Ocramius has given copious notes on approaches we would consider, if anybody would like to take this up again.


Full alert setup and display

These are the details that are required for a new alert setup and I will be making a UI to edit each of these parameters before sending a request. There will a Floating Action Button on the home screen for creating a new alert.

Done and Merged


update osx builds to xcode10

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

bad VM_FLAGS_USER_ALLOCATE value at byte 0: rust: 27 (0x1b) != c 31 (0x1f)
bad VM_FLAGS_USER_MAP value at byte 0: rust: 27 (0x1b) != c 31 (0x1f)

Damn. Did we already had any backwards incompatible changes between Xcode versions? If so, how where these resolved?

r=me w/ green CI

@alexcrichton CI is green

@bors: r+

:pushpin: Commit 4182efd1671dd93acc517cc2e19c14ea4a23ad9f has been approved by alexcrichton

:hourglass: Testing commit 4182efd1671dd93acc517cc2e19c14ea4a23ad9f with merge 4a8304d47e844eeec8a4619b3d3e0f3bdd958521...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 4a8304d47e844eeec8a4619b3d3e0f3bdd958521 to master...


dynamic template

vue.js dynamic template，http://knockoutjs.com/documentation/template-binding.html#note-5-dynamically-choosing-which-template-is-used

Please provide more information on what you want. Have you looked at http://vuejs.org/api/#partial ?


Time To Interactive is different from WebPageTest audit

Reproduction
Steps to reproduce:

Check TTI given by Falco
Open an audit
Check TTI given by WPT

Expected Behavior
What behavior were you expecting to see?
The values are equal
Actual Behavior
What behavior did you actually see?
Environment
TTI (Falco): 6,02s
TTI (WPT): 2078ms

Hi @jeanphilippeds! the relevant piece of code is there:
https://github.com/theodo/falco/blob/c4713d0ab38f3a8a4601b1594fd22a4be170933d/backend/audits/wpt_utils/normalizer.py#L50-L55
WebPageTests has many metrics related to interactivity (some of them sometimes absent), the way we are handling it in Falco seems to not reflect 100% the way it’s displayed in WebPageTest.org. Maybe some searching around in WPT’s codebase can show us what metric they actually use/discard?


WHERE TO PUT TOKEN

Where to put token ?

You have to put it in the token area, there is a comment it says token here


Update layers/meta-balena digest to 00324bf

This PR contains the following updates:

Package
Update
Change

layers/meta-balena
digest
73bc188 -> 00324bf

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Can one of the admins verify this patch?


Add support for generating only CJS bundle

Currently, the bundler can generate both CJS and ESM versions or only the ESM version of the given entrypoint. However, there are some cases when only CJS one should be generated. Let's add such an ability to the tool.

No longer planned.


Indenter doesn't work intuitively with ignored tokens

Describe the bug
Indenter is cited as the way to parse whitespace-sensitive languages, but it has unintiutive and obtrusive behavior when there is an ignored token (ex a comment) in the middle of a newline sequence.
To Reproduce
Example:
GRAMMAR = r"""
	%import common.WS_INLINE
	%import common(C_COMMENT, CPP_COMMENT, SIGNED_NUMBER)

	%declare _INDENT _DEDENT
	%ignore WS_INLINE
	%ignore CPP_COMMENT
	%ignore C_COMMENT
	_NL: /(\r?\n[\t ]*)+/

	VARNAME: /[_a-zA-Z][_a-zA-Z0-9\/]*/

	start: [_NL] stmt*
	stmt: VARNAME _NL [_INDENT stmt+ _DEDENT]
"""

from lark import Lark
from lark.indenter import Indenter

class TreeIndenter(Indenter):
	NL_type = '_NL'
	OPEN_PAREN_types = []
	CLOSE_PAREN_types = []
	INDENT_type = '_INDENT'
	DEDENT_type = '_DEDENT'
	tab_len = 4

parser = Lark(GRAMMAR, postlex=TreeIndenter(), parser="lalr", start="start")
data = """
foo
bar
	/* */
	baz
"""
for tok in parser.lex(data):
	print(repr(tok))
print(parser.parse(data).pretty())

Remove the /* */ from the data variable and it parses ok.
Happens because the ignored comment splits up the _NL tokens, and the indenter does not coalesce them.

The recommended solution is to capture comments in the newline.
Something like:
_NL: (NEWLINE | COMMENT)+

If you have a better way, we'll be happy to hear it.

@erezsh Thanks for the quick response. Looks like that works.
Might be worth putting that in the docs somewhere - seems like a gotcha. I think that the Indenter could be altered to coalesce adjacent _NL tokens too, so that the alteration isn't needed.

I think you're right, it might be possible to do so. It would prevent languages in which a blank space is a dedent, but perhaps those aren't very common.
Anyway, in terms of performance, the current solution works best.
We can keep this issue open, while I consider the best option. If the code remains the same, I agree we should mention this somewhere in the docs.

@erezsh It might in general be worth considering creating a FAQs/best practices/common misunderstanding page.

@MegaIng What would you put there? It doesn't seem like there are a lot of repetitive issues, since most of them are solved in the code.

Not necessarily repetitive (right now), but tricks that can't really be fixed and shut be documented somewhere. Of course, we can just keep them in issues, but I think adding a page in the docs for them is worth it. #857 (which is actually a 'duplicate' of #517), #841, this issue, #838, #833, etc. (+ stuff from gitter, which is even less searchable than github issues). Most of them were just answered with a short text, explaining what is going on and how to fix the grammar. These could all just be formulated into a "FAQ" page. If you don't want this it's fine, but I think it is worth it.

@MegaIng I have no objection. I you want to write such a page I'll add it.
Maybe some of those can fit in https://lark-parser.readthedocs.io/en/latest/how_to_use.html or https://lark-parser.readthedocs.io/en/latest/recipes.html

@erezsh

The recommended solution is to capture comments in the newline.
Something like:
_NL: (NEWLINE | COMMENT)+

That doesn't seem to work in my case where the comments are SH_COMMENTS because the comment eats the \n before NEWLINE sees it.
Any suggestions for a grammar that

uses SH or Python style comments
uses indentation for structure and therefore uses Indenter

@julie777 That's what the official Python grammar does.. https://github.com/lark-parser/lark/blob/master/lark/grammars/python.lark


Fix selfplay reward calculation

Was comparing with action only one ticket
Now comparing with expected_action with multiple available tickets

@googlebot I fixed it.

@googlebot I fixed it.


Support SSL between backend, db, frontent

I've set up a fresh instance of ODK Central as K8s pods with a blank postgres11 db. The db apparently requires SSL.
I'm getting this error:
root@service-d47b965cd-d4td4:/usr/odk# odk-cmd --email florian.xxx@xxx user-create
prompt: password: xxx

Error: The server does not support SSL connections
    at Socket.<anonymous> (/usr/odk/node_modules/pg/lib/connection.js:86:33)
    at Object.onceWrapper (events.js:291:20)
    at Socket.emit (events.js:203:13)
    at addChunk (_stream_readable.js:294:12)
    at readableAddChunk (_stream_readable.js:275:11)
    at Socket.Readable.push (_stream_readable.js:210:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:166:17)Problem [Error]: An unknown internal problem has occurred. Please try again later.
    at Object.unknown (/usr/odk/lib/util/problem.js:39:3)
    at postgresErrorToProblem (/usr/odk/lib/util/db.js:282:34)
    at tryCatcher (/usr/odk/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/usr/odk/node_modules/bluebird/js/release/promise.js:517:31)
    at Promise._settlePromise (/usr/odk/node_modules/bluebird/js/release/promise.js:574:18)
    at Promise._settlePromise0 (/usr/odk/node_modules/bluebird/js/release/promise.js:619:10)
    at Promise._settlePromises (/usr/odk/node_modules/bluebird/js/release/promise.js:695:18)
    at _drainQueueStep (/usr/odk/node_modules/bluebird/js/release/async.js:138:12)
    at _drainQueue (/usr/odk/node_modules/bluebird/js/release/async.js:131:9)
    at Async._drainQueues (/usr/odk/node_modules/bluebird/js/release/async.js:147:5)
    at Immediate.Async.drainQueues (/usr/odk/node_modules/bluebird/js/release/async.js:17:14)
    at processImmediate (internal/timers.js:439:21) {
  problemCode: 500.1,
  problemDetails: {
    error: Error: The server does not support SSL connections
        at Socket.<anonymous> (/usr/odk/node_modules/pg/lib/connection.js:86:33)
        at Object.onceWrapper (events.js:291:20)
        at Socket.emit (events.js:203:13)
        at addChunk (_stream_readable.js:294:12)
        at readableAddChunk (_stream_readable.js:275:11)
        at Socket.Readable.push (_stream_readable.js:210:10)
        at TCP.onStreamRead (internal/stream_base_commons.js:166:17)
  }
}

Is that SSL option something the backend could easily support? Not wanting to pile on unnecessary work, but probably required for moving postgres versions forward.

are you sure you aren't attempting to connect to a non-SSL database with an SSL connect string?
given the PG client is complaining that "the server does not support SSL connections" i would assume that this means it's trying to connect with SSL to postgres but postgres isn't liking it.

The db is a plain postgres:9.6 running in the same cluster/project, no SSL anywhere in the config. The service container also has no SSL config. The only difference to my other, working, ODK Central instance is a slightly newer Docker image (both 0.6 though) and a different k8s cluster (only our infra folks could tell).
I did try connecting to a separately hosted (way gruntier) pg cluster with SSL, setting an env var 'SSLMODEREQUIRE=true' (IIRC), also no joy.
I guess since the images work fine in the docker-compose version, the error must be some kind of wrong config on my end. Complication: all config I can see/edit is exactly identical between working and non-working.

okay let's step back.
clarification question:
is it that you're running into this error for whatever reason and therefore your ask is SSL so the error goes away, or
is it that you're trying to set up SSL between all these components and that's why you're getting this error?

Context needed ;-)
what I'm doing:

Trying to run self-hosted ODK Central
Must run on our own infra - flavour of the month is Azure, K8s, Rancher. Own nginx proxy/reverse proxy and firewall. Own SSL certs (for reverse proxied name) and mail server.
Expected data volume exceeds local pod allocation, would like to use our hosted pg cluster (has ample storage), but that's pg11 with SSL required.
Running as close to vanilla ODK Central docker-compose as possible, even using local postgres pod.
Setup described here.

Current problem narrowed down to:
frontend talks to localhost:8383:

https://github.com/opendatakit/central-frontend/blob/43a7ed499dc1690253e7b47501ed159dd0c333a2/nginx.conf

# backend allows me to create a web user on odk-cmd
# trying to login through frontend
2019/09/27 05:06:42 [error] 11#11: *28 connect() failed (113: No route to host) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "POST /v1/sessions HTTP/1.1", upstream: "http://<IP_ADDRESS>:8383/v1/sessions", host: "odkcentral-migrated.dbca.wa.gov.au", referrer: "https://odkcentral-migrated.dbca.wa.gov.au/"
<IP_ADDRESS> - - [27/Sep/2019:05:06:42 +0000] "POST /v1/sessions HTTP/1.1" 502 166 "https://odkcentral-migrated.dbca.wa.gov.au/" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0"

So the nginx container can't find a route to the service container, although they run side by side (same namespace).
Apologies if this problem strays from the original "but the db wants SSLMODE".
Has anything changed in the last two months in how the frontend finds a route to the backend?

from my reading of the error message the central-backend service is already trying to use SSL to connect to the database, and the database is the one that doesn't allow that.
Error: The server does not support SSL connections - remember that from the context of libpg, it is the client and the database is the server.
as for the route to backend stuff, i'm not sure. sounds like a transient issue in your networking. we didn't change anything there. in this case, remember that the "frontend" is just your web browser. it's nginx that's seeking the backend in those logs. if it thinks there is no route, then there is a hostfile issue, or a gateway issue, or something else networky. is <IP_ADDRESS> local to the nginx host? next time this happens, log into nginx and trace that route and you may get some clues.

(i do see that you've done some investigation on this line of thinking, but i'm still pretty sure the problem is more in that direction.)

i dug up the source of the error message and indeed it occurs as a result of a response from the database that it does not like SSL:
https://github.com/brianc/node-postgres/blob/master/lib/connection.js#L88

(i do see that you've done some investigation on this line of thinking, but i'm still pretty sure the problem is more in that direction.)

The "route to host" problem was solved by building and restarting the two images.
Thanks for the SSL/pg client tip, chasing up with IT now.

I think I saw a comment that mentioned the nginx.conf in central-frontend, so I also wanted to note that that file is mostly intended for local development. The nginx.conf in central-frontend doesn't do everything that the configuration in the central repo does; for example, it doesn't support request-body gzip decompression. This doesn't sound like the source of the issue here, but in case you weren't already, I wanted to recommend that you use the NGINX configuration in the central repo as the basis of your work.

@issa-tseng @matthew-white retrying while still jet lagged:

Rebuilt ODK Central images front & backend from latest master.
Configured our hosted db (server name, un, pw, db name) in local.json.
Our db requires SSL.

Getting this error:
wait-for-it.sh: waiting 15 seconds for postgres:5432
wait-for-it.sh: timeout occurred after waiting 15 seconds for postgres:5432
running migrations..

Unhandled rejection error: SSL connection is required. Please specify SSL options and retry.

at Connection.parseE (/usr/odk/node_modules/pg/lib/connection.js:545:11)
at Connection.parseMessage (/usr/odk/node_modules/pg/lib/connection.js:370:19)
at Socket.<anonymous> (/usr/odk/node_modules/pg/lib/connection.js:113:22)
at Socket.emit (events.js:203:13)
at addChunk (_stream_readable.js:294:12)
at readableAddChunk (_stream_readable.js:275:11)
at Socket.Readable.push (_stream_readable.js:210:10)
at TCP.onStreamRead (internal/stream_base_commons.js:166:17)
starting cron..
starting server.

Do I read above error correctly that the db complains that it requires SSL?
How can I tell ODK Central to use SSL when accessing the db?

okay, so now i think we agree that postgres wants central to use ssl but it is not. this makes more sense.
i think most likely all you need to do is set the correct configuration in default.database in config.json.template. i don't know exactly that that would be but if you use a connection string instead of an object i think you'll be able to specify whatever the standard ssl-ish connection string would be. or there may be a config key you can add to the existing object to specify ssl/secure. report back if you figure it out!
we use knexjs.org under the covers, but that just uses the nodejs pg client library under its covers.

@issa-tseng knowing that you use knex.js and node-postgres helped me to find the docs about SSL mode at https://node-postgres.com/features/ssl.
Config just needed the addition of "ssl": {"rejectUnauthorized": false}:
 "database": {
      "host": "DBHOST",
      "user": "USERNAME",
      "password": "PASSWORD",
      "database": "DBNAME",
      "ssl": {"rejectUnauthorized": false}
    },
...

Thanks for the help Issa!


Rancher v2.6.6 install errors: Failed to read API for groups map; Failed to install system chart fleet-crd[BUG]

Rancher Server Setup

Rancher version: v2.6.6
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):
RKE version v1.3.8
Docker version v20.10.12

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: v1.22.7
Cluster Type (Local/Downstream): Local/Custom

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions:
Admin

Describe the bug

After installing using Helm v3.2.4 Rancher throws the following error:
Error: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s": remote error: tls: internal error
POD's status:
k -n cattle-system get pods
NAME                       READY   STATUS             RESTARTS         AGE
helm-operation-2nmlz       2/2     Running            0                14s
helm-operation-2nqp2       1/2     Error              0                35m
helm-operation-46cvb       1/2     Error              0                50m
helm-operation-58rbl       1/2     Error              0                20m
helm-operation-5mxdp       1/2     Error              0                26m
helm-operation-64shq       2/2     Running            0                2m15s
helm-operation-6wvhw       1/2     Error              0                19m
helm-operation-7xcd5       2/2     Running            0                3m15s
helm-operation-7xrd9       1/2     Error              0                36m
helm-operation-84vr8       1/2     Error              0                28m
helm-operation-89s69       1/2     Error              0                41m
helm-operation-9drbx       1/2     Error              0                57m
helm-operation-9mjwv       1/2     Error              0                33m
helm-operation-9pmh8       1/2     Error              0                24m
helm-operation-b6v8l       1/2     Error              0                53m
helm-operation-bdwlh       1/2     Error              0                54m
helm-operation-cf56l       1/2     Error              0                13m
helm-operation-cftff       1/2     Error              0                55m
helm-operation-cg726       1/2     Error              0                58m
helm-operation-cklpp       1/2     Error              0                9m15s
helm-operation-dk2f6       1/2     Error              0                48m
helm-operation-glzbc       1/2     Error              0                31m
helm-operation-h6jhr       2/2     Running            0                4m15s
helm-operation-hglv6       1/2     Error              0                23m
helm-operation-hsz2c       1/2     Error              0                22m
helm-operation-jqs9c       1/2     Error              0                44m
helm-operation-k5vfg       1/2     Error              0                16m
helm-operation-kqj2w       1/2     Error              0                25m
helm-operation-kt6sg       1/2     Error              0                45m
helm-operation-lfrjn       1/2     Error              0                47m
helm-operation-lgd7h       1/2     Error              0                6m15s
helm-operation-lmxvx       1/2     Error              0                17m
helm-operation-mcptb       1/2     Error              0                51m
helm-operation-mg4th       1/2     Error              0                8m15s
helm-operation-mjlxr       1/2     Error              0                34m
helm-operation-n56t7       1/2     Error              0                43m
helm-operation-nbbck       1/2     Error              0                10m
helm-operation-nbjft       1/2     Error              0                59m
helm-operation-nf6jl       1/2     Error              0                30m
helm-operation-nj7vk       1/2     Error              0                11m
helm-operation-nx9gp       1/2     Error              0                37m
helm-operation-pkx4l       1/2     Error              0                56m
helm-operation-pvsr8       1/2     Error              0                49m
helm-operation-pxls9       1/2     Error              0                38m
helm-operation-r2w7p       1/2     Error              0                12m
helm-operation-rr4st       1/2     Error              0                7m15s
helm-operation-rrvt4       2/2     Running            0                74s
helm-operation-rwgs9       1/2     Error              0                21m
helm-operation-rzbhl       1/2     Error              0                32m
helm-operation-sftfj       1/2     Error              0                40m
helm-operation-tfc5b       1/2     Error              0                39m
helm-operation-thszl       1/2     Error              0                27m
helm-operation-tmdv5       1/2     Error              0                42m
helm-operation-v24vc       1/2     Error              0                46m
helm-operation-w7zns       2/2     Running            0                5m15s
helm-operation-wcn6n       1/2     Error              0                29m
helm-operation-wndpx       1/2     Error              0                52m
helm-operation-z2ktz       1/2     Error              0                15m
helm-operation-zc469       1/2     Error              0                14m
helm-operation-zn7tj       1/2     Error              0                18m
rancher-5d9bc8bf5b-7x4b6   1/1     Running            0                13h
rancher-5d9bc8bf5b-8wjzc   0/1     CrashLoopBackOff   22 (4m1s ago)    92m
rancher-5d9bc8bf5b-bzbn8   0/1     CrashLoopBackOff   22 (3m31s ago)   92m

To Reproduce

Deploy cluster with RKE v1.3.8 (I had 13 nodes with 1 controlplane/etcd, 2 controlplane/etcd/worker and rest are worker nodes)
rke up --config $KUBE_CONF_FILE
Create namespace cattle-system
Create Docker pull secret and TLS secrets.
Install Rancher using downloaded helm chart:
helm install rancher   --namespace cattle-system   --set hostname=rancher.my.domain.com   --set bootstrapPassword=<password>   --set ingress.tls.source=secret   --set privateCA=true  -f values.yaml .

Result
Rancher pods keeps crashing with "CrashLoopBackOff" status Liveness check
Logs:
2022/07/26 15:13:47 [INFO] Rancher version v2.6.6 (9b2f2ae0e) is starting
2022/07/26 15:13:47 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2022/07/26 15:13:47 [INFO] Listening on /tmp/log.sock
2022/07/26 15:13:48 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host

Events:
  Type     Reason     Age                    From     Message
  ----     ------     ----                   ----     -------
  Normal   Pulled     12m (x18 over 77m)     kubelet  Container image "rancher/rancher:v2.6.6" already present on machine
  Warning  BackOff    7m44s (x142 over 63m)  kubelet  Back-off restarting failed container
  Warning  Unhealthy  115s (x58 over 76m)    kubelet  Liveness probe failed: Get "http://<IP_ADDRESS>:80/healthz": dial tcp <IP_ADDRESS>:80: connect: connection refused

kubectl -n cattle-system logs -l app=rancher
2022/07/26 14:34:36 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:39 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:42 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:45 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:48 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:51 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:54 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:57 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:35:00 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:35:03 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
E0726 14:34:48.083644      34 gvks.go:69] failed to sync schemas: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request
2022/07/26 14:34:52 [ERROR] Failed to read API for groups map[metrics.k8s.io/v1beta1:the server is currently unable to handle the request]
E0726 14:34:53.095150      34 gvks.go:69] failed to sync schemas: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request
2022/07/26 14:34:57 [ERROR] Failed to install system chart fleet-crd: pod cattle-system/helm-operation-cftff failed, watch closed
2022/07/26 14:34:59 [ERROR] error syncing 'library': handler catalog: Clone failed: Cloning into 'management-state/catalog-cache/380859f1003fe7603cddc6c15b34b7263f1f0deaa92ddcde465811d032ee7078'...
fatal: unable to access 'https://git.rancher.io/charts/': Could not resolve host: git.rancher.io
: exit status 128, requeuing
2022/07/26 14:35:03 [ERROR] Failed to read API for groups map[metrics.k8s.io/v1beta1:the server is currently unable to handle the request]
E0726 14:35:03.108336      34 gvks.go:69] failed to sync schemas: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request
2022/07/26 14:35:04 [ERROR] Failed to read API for groups map[metrics.k8s.io/v1beta1:the server is currently unable to handle the request]
2022/07/26 14:34:36 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:39 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:42 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:45 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:48 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:51 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:54 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:34:57 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:35:00 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host
2022/07/26 14:35:03 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:443: connect: no route to host

Expected Result

Rancher installed successfully and I should be able to login to Rancher UI
Screenshots

Additional context

watch


Camera improvements

Grouping various camera-related issues here:

The Camera is not yet very practical. Users would like to directly move the camera with the viewport controls, using the viewport camera as preview
Camera navigation is a bit clumsy, and inconsistent between editors (prefab / l3d). Quoting @ncannasse " review camera movement entirely (wrt zoom / translation) - base on looking at object (ray cast)".
Bug: changing animation speed also change camera movement (speed = 0 -> can't move camera)
The ability to adjust FoV using Alt is not super practical: it's often changed by mistake, and we would rather control the FoV manually for a given project
It would be nice to be able to switch between perspective and top-down ortho view without losing the perspective camera
For Darksburg, users requested to use the "game camera" to preview levels, using same settings and controls, without having to launch the game

What else?

Last point I think works well by setting a custom camera to use the same view as ingame, and adding a GameController that allows you to scroll using the gamepad - that's what we used for WT. Also follows terrain elevation. Works best if the game actually uses this camera preset at runtime too.

Suggestion for top view : single click on the icon to move from current-view to current-view with top camera (don't change the target viewed object), double click for full reset at (0,0,0) + top view


ISPN-13139 documentation revision

Needs backport to 12.1.x
https://issues.redhat.com/browse/ISPN-13139

Merged, thanks Don!


Resetting badge number on applicationDidBecomeActive creates strange behavior for the user

I'm using the firebase_messaging plugin for push notifications. On iOS this plugins resets the badge number on each applicationDidBecomeActive in the AppDelegate. This also clears all notifications in the notifications center.
This creates unexpected behavior for the user in several cases:

if the user receives several notifications at once he is only able to click on one notification since the other notifications are deleted after the app is opened
if the user opens the app directly after receiving a notification the notifications are also lost
if we show a local notification using the flutter_local_notifications plugin while the app is the foreground the notification disappears once the user tries to open the notification center.

Please fix this behavior like described in the TODO or make it configurable so the badge number is not reset. In our case we are not sending a badge number with the push notification so resetting it is not needed.

@grundid
The issue at https://github.com/flutter/flutter/issues/28093 has been closed and moved here. Future collaboration on this issue will be done here.

Hi @grundid
(and hello to @DarshanGowda0  as well)
If are you still experiencing this issue
with the latest version of Flutter and FlutterFire plugin
can you please provide your flutter doctor -v
and your and your flutter run --verbose/flutter build --verbose ?
Also, to better address the issue, would be helpful
if you could post a self contained app on github
or the steps to reproduce it.
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so its always better to open new issues and reference related issues.


Add UiPath account ID

@p-h-0-x This looks good to me. Can you change it from a draft to a pull request so I can merge it?

Thank you @p-h-0-x !


TfEzFC4W: implement cross domain google analytics tracking for verify

What
We need to implement some Google Analytics (GA) tracking code on the Hub.
This isn't because we're going to use GA for Verify analytics.
It's because GOV.UK is now implementing GA tracking across various x.gov.uk subdomains.
GDS needs to be able to track user journeys across campaign pages, GOV.UK content and transactions on the service domain.
Verify is part of these journeys, hence the need to get the GA code up and running on the Hub.
How
Add GoogleAnalytics class for configuration
Add configuration class instance to AnalyticsPartialController
Initialise GA config from environment
Add GA shared view
Render GA shared view in application layout
Update CSP to allow GA source domain
Update analytics.js to execute GA code if config values present
Add _ga parameter handling to authn_request_controller
Adjust CSP to allow Google Analytics to make calls to www.google-analytics.com
Correct links to gov.uk to www.gov.uk to ensure link decoration works
Add form decoration and ensure works on SAML response form

Get an OK from Tom or Michaela before putting live please – not until Monday now I think.


The scrapers seem to get broken a lot.  Let's add tests for them.

They currently fail -- Fix them!

Tappedout was failing because of Nezumi Graverobber, so I pushed the deck responsible to the second page ;)


Single Voice Mode from single voice SYX...

Single Voice Mode from single voice SYX...    Header in code

fixed


Bump ouath version

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/8846071477
Status: success


Small event related refactors

Codecov Report

Merging #504 into master will increase coverage by 0.00%.
The diff coverage is 53.84%.

@@           Coverage Diff           @@
##           master     #504   +/-   ##
=======================================
  Coverage   61.86%   61.87%
=======================================
  Files          55       55
  Lines        4277     4275    -2
=======================================
- Hits         2646     2645    -1
+ Misses       1631     1630    -1

Impacted Files
Coverage Δ

src/relay/ethindex_db/ethindex_db.py
22.94% <ø> (ø)

src/relay/ethindex_db/events_informations.py
24.44% <25.00%> (ø)

src/relay/api/resources.py
43.89% <100.00%> (ø)

src/relay/relay.py
31.70% <100.00%> (-0.08%)
:arrow_down:

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 7997b1c...c4a082f. Read the comment docs.


[macOS] VSCode doesn't keep the last window in focus on Cmd+Tab

Issue Type: Bug

Using macOS with 2 or more screens.
Open 2 or more VS code windows.
Focus any but the first opened VSCode window.
Cmd+Tab to a different app.
Cmd+Tab back to VSCode.

Expected behaviour: last active (focused) window keeps the focus.
Actual behaviour: the first opened window always receives the focus.
But if you click the icon in the dock instead of Cmd+Tab, the focus restores properly.
Probably it's a macOS bug, since the same problem exists with other apps. But if it could be fixed in VSCode alone, it would make life better.
VS Code version: Code 1.66.2 (Universal) (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:49:20.994Z)
OS version: Darwin x64 20.2.0
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-3635QM CPU @ 2.40GHz (8 x 2400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 2, 2

Memory (System)
8.00GB (0.21GB free)

Process Argv
--crash-reporter-id c45ad719-2498-406c-9421-8cd79d6b01c2

Screen Reader
no

VM
0%

Extensions (21)

Extension
Author (truncated)
Version

vscode-css-formatter
aes
1.0.2

svelte-intellisense
ard
0.7.1

vscode-tailwindcss
bra
0.8.2

bracket-pair-colorizer
Coe
1.0.62

dart-code
Dar
3.38.2

flutter
Dar
3.38.1

vscode-great-icons
emm
2.1.86

vsc-material-theme-icons
equ
2.2.1

json-to-dart
hir
3.5.7

vscode-github
Kni
0.30.7

dart-import
lua
0.3.1

svelte-format
mel
0.0.7

fluent-icons
mig
0.0.17

awesome-flutter-snippets
Nas
3.0.3

svelte-autoimport
piv
1.0.4

material-icon-theme
PKi
4.16.0

vscode-yaml
red
1.6.0

svelte-vscode
sve
105.16.0

icons
tal
3.1.0

vscode-icons
vsc
11.11.0

vscode-todo-highlight
way
1.0.5

(1 theme extensions excluded)

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


[Documentation] Mention github_token required permissions

It would be great to know which of the whole set of permissions this actions requires with which level of access: https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#permissions. That way we can restrict the token permissions to the bare minimum on user side.

it would also be useful to know the required permissions to help debug why clippy-check is failing to push comments in some repos (even when the branch is not from a forked repo)


Flutter with Firebase is completely broken in Xcode 12

Flutter is completely broken when integrating with Firebase. Getting the following error:
<pb_decode.h>
/Users/azamsharp/Desktop/todo_list/ios/Pods/Target Support Files/nanopb/nanopb-umbrella.h:19:9: error: double-quoted include
"pb_common.h" in framework header, expected angle-bracketed instead [-Werror,-Wquoted-include-in-framework-header]
#import "pb_common.h"
^~~~~~~~~~~~~
<pb_common.h>
/Users/azamsharp/Desktop/todo_list/ios/Pods/Target Support Files/nanopb/nanopb-umbrella.h:20:9: error: double-quoted include
"pb.h" in framework header, expected angle-bracketed instead [-Werror,-Wquoted-include-in-framework-header]
#import "pb.h"
^~~~~~
<pb.h>

Hi @azamsharp
From what I can see, the issue is related to a FlutterFire plugin rather than to Flutter itself. Please open the issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself.
If you disagree, please write in the comments,
providing your flutter doctor -v, your flutter run -v,  your pubspec.yaml
a minimal reproducible code sample that does not use 3rd party plugins,
and I will reopen it.
Thank you


False positive error when accessing property method that returns never using --strict

Bug Report
I get a compile error when calling a property method that returns never using --strict, when I expect to get no compile error. I am unable to reproduce the error with toplevel functions.
🔎 Search Terms

never strict label:bug
never property
false positive never label:bug

🕗 Version & Regression Information

I am able to reproduce this behavior with versions 4.1.3 (my application), 4.4.3 (the minimized reproduction above) and 4.5.0-beta (playground link)
This is the behavior in every version I tried, and I reviewed the FAQ for entries about never

⏯ Playground Link

Playground link https://www.typescriptlang.org/play?ts=4.5.0-beta#code/EQVwzgpgBGAuBOBLAxrYBuAUAMxAO1UQHs8oAjIogWwAoBKALijwgDcJ4oBvTKKWABbwiAd2YQxAUXjD4NAOQVq8upgC+mTMhJwoAeRCwOUALzdefcpVqNx7Tj0tP+Q0eKkyicxdZUW+GhpaADYAhmBgUABCoQ7+UAAOIGTBKFbUAGL4hCT0THggVGTGjs58SjbxGk5JKWkVAArCCRywAJ55zIXFcWV8BkbwAHQV9FXqmEA
💻 Code
Minimized reproduction
❯ cat boom.ts
function boom(): never {
  throw new Error('boom')
}

const Outer = {
    boom(): never {
        throw new Error('boom')
    }
}

class Bar {
    public boomFunction(): number {
        boom()
    }
    public boomProperty(): number {
        Outer.boom()
    }
}

🙁 Actual behavior
❯ npx -p<EMAIL_ADDRESS>tsc --strict boom.ts
boom.ts:18:28 - error TS2366: Function lacks ending return statement and return type does not include 'undefined'.

18     public boomProperty(): number {
                              ~~~~~~

Found 1 error.

🙂 Expected behavior
I expected there to be 0 errors because there is no error for boomFunction(), only boomProperty().
Workarounds

add return Outer.boom().
remove the --strict flag.

It's still related to control flow. It doesn't consider the Outer.boom() method to be "terminating" (aka never returning). The initial example of #12825 already works, but there have been several comments regarding this behaviour in that issue.

@MartinJohns You're right, this issue is about control flow. This is indeed a duplicate. Thank you!


[FE] Finish Dog Table Page

Description
Make revisions, finish styling, and add pagination to the dog table page.
Acceptance Criteria

[x] Add Other column
[x] Tags link to the log section of the individual dog's page (once we have log endpoints done, we can also link to individual log)
[x] Date Of Birth should turn into Age. Age in years can be calculated based on date of birth
[ ] Add Filter component and connect it to our search dogs api
[x] Add pagination so only 10 dogs are visible on the screen (note: we are still retrieving all dogs on page load, just restricting how many appear on the page)
[ ] Styling reflects design documents

Other Notes

N/a

Current TODO Changes:

[ ] Dog schema must be adjusted to allow recent log tags to be queried
[ ] (Low priority) Visual update for when log filter becomes too big (and can't be displayed visually)
[ ] (Low priority) Slightly adjust padding for filter cards to prevent shift in content
[ ] (Low priority) Increase clickable size for pagination buttons


npm run dev 进度卡住不动

npm run dev

<EMAIL_ADDRESS>dev /Users/apple/awesome-project
webpack --watch

Hash: 75431730f55e6417e0c2
Version: webpack 1.14.0
Time: 1798ms
Asset     Size  Chunks             Chunk Names
app.weex.js  4.39 kB       0  [emitted]  app
+ 5 hidden modules
Hash: 8c832d157f9e840d3d61
Version: webpack 1.14.0
Time: 1977ms
Asset     Size  Chunks             Chunk Names
app.web.js  15.4 kB       0  [emitted]  app
+ 10 hidden modules
卡住不动了 是怎么回事啊

建议去了解下这个命令实际作用，你就明白了。

我也遇到这个问题了，请问解决了吗

我也遇到了，请问怎么解决的

正常的, 此时 Ctrl + C 终止, 根目录下会生成一个 dist 目录：
dist
├── app.web.js
└── app.weex.js // 这个文件就是以后供移动端访问的

运行 npm run serve 启动静态服务器, 然后打开 http://localhost:8080/index.html 预览项目.

分别在 2 个 终端 中 输入 npm run dev 和 npm run serve 就好了。 注意 是serve 不是 server。

This PR/issue doesn't received response since Weex migrated to Apache two years ago and this repository is no longer active yet.
Feel free to ask question in new repository and thanks for your contribution.

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.


Removing students

Hi @uit-inf-3200/students !
I'm going to clean up this organization on Friday. If you want to grab some content from any of the private repos we've got in the @uit-inf-3200 organization please do so now!
Bjørn

If you are planning to have students fork repositories in the future I would recommend using non-generic (e.g. prefix with "uit-inf-3200-") names for the repositories, because forked github projects are given the same name as that of their source repository. Leaving students with repositories such as https://github.com/johslarsen/Project-1 or, even worse, https://github.com/johslarsen/Project. Otherwise students taking more than 1 course using the fork+pull-request workflow simultaneously will have namespace issues and end of with repositories such as Project-1-1, because github appends "-$i" to resolve namespace issues.

Thanks for the heads up @johslarsen !


EK-156: Changed breakpoint to align with site.css.

See EK-156 in Jira for specifics on replicating the issue.


Expose the error states possible for a PipelineSchedule in the UI

Previously, PipelineSchedules would be disabled and there was no indication other than no builds being generated, and the "next build" in the UI becoming further and further in the past that it was disabled. This exposes both the "disabled" state and failure messages in the UI, and allows re-enabling it from the error message itself.

This PR does not address taking ownership of a Schedule in order to re-authorise the schedule itself, but this would be a good next step.

This is great! It’s going to help a lot of people, I’ve had a number of confused support requests about this.
Small things that shouldn’t necessarily block this:

Do we have a “badge” like (small, uppercase) component for the “Disabled” label on the list view? Perhaps we put that to the left or right side of the name?
Maybe we out a notice at the top of the list view too? That one or more schedules are currently disabled because the user is no longer a member of the org.
Could even even just have a “re-enable” button that re-saves the schedule for them?

This has been expanded to add an “enabled” checkbox to the schedule page, and to add a “re-enable” button for schedules which have failed (it doesn’t show for manually disabled schedules). The text in the alert has been updated to reflect this.

Clicking that button doesn’t take ownership, no. That’s also something I’d like to address, but I know that temporarily turning off the schedule is a feature we’ve been asked for, and this both addresses that and makes it clear when a schedule is disabled, in either case.

Just added a note to the list page about the errors.

Cool okay, sounds like a good improvement either way.
How about we remove the second sentence on the list page, and just state there’s some disabled schedules? Avoids introducing new terms like “review” etc.
On the schedule page error message, if it was disabled due to an access/permissions error, and the membership hasn’t been fixed, I wonder if we should include the re-enable button or change the wording? At the moment “If their access has been restored” puts the burden on them to go and figure out whether it can be re-enabled. Or is it just a “Press re-enable and hope for the best”? If it is, then maybe we just remove “If their access was restored” sentence and let them hit the button, and get an error if it wasn’t?

How about we remove the second sentence on the list page, and just state there’s some disabled schedules? Avoids introducing new terms like “review” etc.

👌🏼

is it just a “Press re-enable and hope for the best”

From my understanding, the “Re-Enable” operation will always succeed. If the user who owns the Schedule still lacks build creation access, the schedule will simply be disabled again the next time it tries to run. I think this means that a “take ownership” option is going to be important.

Cool, we’ll maybe then the current message is cool, but we just remove the newline?
And look into ownership stuff as a new thing?

Taking ownership looks easy enough to do, I’d just like to look into whether it’s a reasonable step to take, and what we need to do to determine if a user can safely do so!

OK I pinched a Bass stanza from the new team “recommended” thing, but turned it red. I’m not sure it looks good in the big size. Feel free to tweak while I’m offline, @toolmantim 😃

No need to badge the big heading I reckon! The small one looks great 👌🏼

Well, something needs to be present; on manually disabled schedules the badge is currently the only indication it’s disabled!

Oh I see! Sorry.
Can we not inherit the font size from the heading then? As in, make it the same as on the list page?

We can, but I’ll have to do it manually I believe (it’s using bass’ small class which just drops it to something like .7em)!

OK! Both schedule badges are now rendered with 12px fonts. This only changes the one on the individual schedule page.

Hey, looking great! A few small word things:

s/no longer has access/no longer had access/
s/on this Pipeline/on this pipeline/
Given our above discussion, let’s just remove the second sentence perhaps?

Aside from these… 🚀🎉

Both of those messages are part of the back-end infrastructure which handles this error, and such errors already exist in this current form (they’re set when the error occurs). I can change it going forward, if that makes sense?

Ahh okay. Hrmm, maybe let’s change it for errors going forward then?

Done in https://github.com/buildkite/buildkite/pull/2709/commits/4572ab643000fbd802ccfc3d24a13d29da78afe3 !

@toolmantim if you’re around, wanna give this a once-over? I’d love to deploy it today and get started on the “take ownership” bit

Ship it! 🚀🚀🚀

(Sorry I didn’t have a chance to give it more of a once over, but I reckon it looks great from the PR here!)


Airflow agent

TL;DR
Airflow agent allows you to seamlessly run Airflow tasks in the Flyte workflow without changing any code.
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
Use bashSensor in the flyte workflow
from airflow.sensors.bash import BashSensor
from flytekit import task, workflow, ImageSpec

image_spec = ImageSpec(packages=["apache-airflow"], registry="pingsutw")

@task(container_image=image_spec)
def t1():
    print("flyte")

@workflow
def wf():
    sensor = BashSensor(task_id="Sensor_succeeds", bash_command="echo hello")
    sensor >> t1()

if __name__ == '__main__':
    wf()

FileSensor
from airflow.sensors.filesystem import FileSensor
from flytekit import task, workflow, ImageSpec

image_spec = ImageSpec(packages=["apache-airflow"], registry="pingsutw")

@task(container_image=image_spec)
def t1():
    print("flyte")

@workflow
def wf():
    sensor = FileSensor(task_id="id", filepath="/tmp/1234")
    sensor >> t1()

if __name__ == '__main__':
    wf()

TimeSensor
from datetime import datetime, timedelta
from pytz import UTC

from airflow.sensors.time_sensor import TimeSensor
from flytekit import task, workflow, ImageSpec

image_spec = ImageSpec(packages=["apache-airflow"], registry="pingsutw")

@task(container_image=image_spec)
def t1():
    print("flyte")

@workflow
def wf():
    sensor = TimeSensor(task_id="fire_immediately", target_time=(datetime.now(tz=UTC)+timedelta(seconds=5)).time())
    sensor >> t1()

if __name__ == '__main__':
    wf()

PythonSensor
from airflow.sensors.python import PythonSensor
from flytekit import task, workflow, ImageSpec

image_spec = ImageSpec(packages=["apache-airflow"], registry="pingsutw")

@task(container_image=image_spec)
def t1():
    print("flyte")

def py_func():
    print("airflow python sensor")
    return True

@workflow
def wf():
    sensor = PythonSensor(task_id="fire_immediately", python_callable=py_func)
    sensor >> t1()

if __name__ == '__main__':
    wf()

Tracking Issue
NA
Follow-up issue
NA

Crossposting a PR review:
Airflow plugin is still required (even though we've swapped to agents), backend plugin will need to be installed
Examples run fine, and can be bundled together:
from datetime import datetime, timedelta
from pytz import UTC

from airflow.sensors.time_sensor import TimeSensor
from airflow.sensors.filesystem import FileSensor
from airflow.sensors.bash import BashSensor
from flytekit import workflow, ImageSpec
@workflow
def wf():
    sensor = TimeSensor(task_id="fire_immediately", target_time=(datetime.now(tz=UTC)+timedelta(seconds=5)).time())
    file_sensor = FileSensor(task_id="id", filepath="/tmp/1234")
    t3 = BashSensor(task_id="Sensor_succeeds", bash_command="exit 0")
    sensor >> file_sensor >> t3

This is great! Very cool, however any operator does not function. Lets add a bashOperator to the example
from datetime import datetime, timedelta
from textwrap import dedent

from flytekit import workflow, task, ImageSpec
# The DAG object; we'll need this to instantiate a DAG

from datetime import datetime, timedelta
from pytz import UTC

from airflow.sensors.time_sensor import TimeSensor
from airflow.sensors.filesystem import FileSensor
from airflow.sensors.bash import BashSensor
from airflow.operators.bash import BashOperator
from flytekit import workflow, ImageSpec
@workflow
def wf():
    sensor = TimeSensor(task_id="fire_immediately", target_time=(datetime.now(tz=UTC)+timedelta(seconds=5)).time())
    file_sensor = FileSensor(task_id="id", filepath="/tmp/1234")
    t3 = BashSensor(task_id="Sensor_succeeds", bash_command="exit 0")
    foo = BashOperator(task_id="foo", bash_command="echo foo")
    sensor >> file_sensor >> t3 >> foo

error is
pyflyte run workflows/example.py  wf
Failed with Unknown Exception <class 'AttributeError'> Reason: Error encountered while executing 'wf':
  'BashOperator' object has no attribute 'ref'

I have not tested remote functionality yet @pingsutw

@pingsutw What's the status of this PR?