Grouping roads/intersections together into logical units

The big pink intersection is surrounded by crossings that overall better define the overall shape of the junction.

The east/west road similarly has a loop of sidewalks/crossings surrounding it. (Actually this case is more interesting, because there are service roads interrupting things)
In both of these cases, a higher-level logical "view" on the raw edges and nodes is starting to become clear. There have been a few attempts before to handle this kind of thing, like the "zip sidepath" experiments in #210, but they've never made it far. Now that separate footways are showing up much better, I'd like to try again with a fresh idea.
Part 1: just find a cycle
Starting from a manually chosen node, use DFS to find the smallest distance cycle in the undirected graph. It'd be best to start from nodes connecting only sidewalks (and footway crossings), to represent those corners on a junction. Maybe constrain the search to only/mostly use sidewalks, or wind up with both cycleways and regular road in the resulting loop. Just start by displaying all the matching Intersections and Roads along the way.
Part 2: trace a polygon
Next, turn that cycle into a "face" / polygon by walking around the cycle's geometry in order. Previous work in the LTN blockfinder, route snapper area mode, and references in topojson / mapshaper. Just start with the original OSM center-lines. If rendered geometry is very nice, then we could try the edges of road and intersection polygons, but that ambition is what makes LTN blockfinding so buggy. So probably just stick to center-lines.
By looking at what a cycle contains, then we can maybe decide to render these polygons. In between sidewalk/crossings and regular road, we could infer that as the full shape of the pavement. Or maybe there's a grass verge between the road and sidewalk.
Part 3: consider merging / zipping things
This is where previous attempts too quickly leapt. But sometimes it might be useful to simplify the graph structure and copy over the lanes to the "main" road. Many parts of this process are hard, so that's why it'll be an optional step and only after the other two parts work reasonably. If it works, would be an alternate approach to something like https://github.com/nptscot/networkmerge

One use case is in the taipei example, figuring out which side to put the sidewalk for https://www.openstreetmap.org/way/1064488314 vs https://www.openstreetmap.org/way/1064488313. Need to know orientation relative to the road


Integer.parseInt and similar don't support non-ASCII scripts

For example, this throws:
java.lang.Integer.parseInt("\u0967\u0966")

but it should return 10.
Apparently JavaScript's parseInt simply does not support non-ASCII scripts, so it's wrong to delegate to it. We must also be careful in parseLong to skip 0's of non-ASCII scripts.

Fixed in 5653e448982654d63f1df3fc186bc53c4bd35ee9.


allow skipping of verification

calling verify with {:verification_method=>"skip"} should mark it verified

:boot:


[Event Request] Codeunit 12 Gen. Jnl.-Post Line - OnVendPostApplyVendLedgEntryOnAfterVendLedgEntryTransferFields

We need a new event in Codeunit 12 "Gen. Jnl.-Post Line" named OnVendPostApplyVendLedgEntryOnAfterVendLedgEntryTransferFields:
[IntegrationEvent(false, false)]
local procedure OnVendPostApplyVendLedgEntryOnAfterVendLedgEntryTransferFields(VAR VendorLedgerEntry: Record "Vendor Ledger Entry"; VAR GenJournalLine: Record "Gen. Journal Line")
begin
end;
called from:
procedure VendPostApplyVendLedgEntry(var GenJnlLinePostApply: Record "Gen. Journal Line"; var VendLedgEntryPostApply: Record "Vendor Ledger Entry")
var
Vend: Record Vendor;
VendPostingGr: Record "Vendor Posting Group";
VendLedgEntry: Record "Vendor Ledger Entry";
DtldVendLedgEntry: Record "Detailed Vendor Ledg. Entry";
TempDtldCVLedgEntryBuf: Record "Detailed CV Ledg. Entry Buffer" temporary;
CVLedgEntryBuf: Record "CV Ledger Entry Buffer";
GenJnlLine: Record "Gen. Journal Line";
DtldLedgEntryInserted: Boolean;
begin
OnBeforeVendPostApplyVendLedgEntry(GenJnlLinePostApply);
GenJnlLine := GenJnlLinePostApply;
VendLedgEntry.TransferFields(VendLedgEntryPostApply);
//INIT INSERT
OnVendPostApplyVendLedgEntryOnAfterVendLedgEntryTransferFields(VendLedgEntry, GenJnlLine);
//END INSERT
with GenJnlLine do begin
"Source Currency Code" := VendLedgEntryPostApply."Currency Code";
"Applies-to ID" := VendLedgEntryPostApply."Applies-to ID";
GenJnlCheckLine.RunCheck(GenJnlLine);
......
......
......

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Table parse issue

Initial checklist

[X] I read the support docs
[X] I read the contributing guide
[X] I agree to follow the code of conduct
[X] I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions
4.0.0
Link to runnable example
No response
Steps to reproduce
After updating it from 3.0.1 to 4.0.0, I am getting an error "Cannot set properties of undefined (setting 'inTable')". it works fine on version 3.
this is my code
import { MDXRemote } from "next-mdx-remote/rsc";
import remarkGfm from "remark-gfm";

const MDXContent = ({ content }: { content: any }) => {
  const mdxOptions = {
    remarkPlugins: [remarkGfm],
  };

  return (
    <>
      <MDXRemote
        source={content}
        options={{ mdxOptions }}
      />
    </>
  );
};

export default MDXContent;

Expected behavior
the table should render
Actual behavior
getting error Cannot set properties of undefined (setting 'inTable')
Runtime
Node v17
Package manager
npm 8
OS
macOS
Build and bundle tools
Next.js

See also #57.

Duplicate of https://github.com/remarkjs/remark-gfm/issues/57

A major version release is rolling out across all: mdx, unified, remark, rehype, and micromark packages.
This includes both type changes (static analysis error) and changes to the parser (potential runtime error) if the major versions are mismatched.
Hold on version 3 of remark-gfm, until the next major of MDX is released


Schema-less json ingestion

I am trying to insert JSON (without schema header) data from a topic in Kafka to BigQuery however I keep running across the same error:
org.apache.kafka.connect.errors.ConnectException: Exiting WorkerSinkTask due to unrecoverable exception.
	at org.apache.kafka.connect.runtime.WorkerSinkTask.deliverMessages(WorkerSinkTask.java:560)
	at org.apache.kafka.connect.runtime.WorkerSinkTask.poll(WorkerSinkTask.java:321)
	at org.apache.kafka.connect.runtime.WorkerSinkTask.iteration(WorkerSinkTask.java:224)
	at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:192)
	at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:175)
	at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:219)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
	at com.wepay.kafka.connect.bigquery.convert.BigQueryRecordConverter.convertRecord(BigQueryRecordConverter.java:69)
	at com.wepay.kafka.connect.bigquery.convert.BigQueryRecordConverter.convertRecord(BigQueryRecordConverter.java:51)
	at com.wepay.kafka.connect.bigquery.BigQuerySinkTask.getRecordRow(BigQuerySinkTask.java:123)
	at com.wepay.kafka.connect.bigquery.BigQuerySinkTask.put(BigQuerySinkTask.java:146)
	at org.apache.kafka.connect.runtime.WorkerSinkTask.deliverMessages(WorkerSinkTask.java:538)
	... 10 more

connect-distributed.properties
##
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#    http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
##

# This file contains some of the configurations for the Kafka Connect distributed worker. This file is intended
# to be used with the examples, and some settings may differ from those used in a production system, especially
# the `bootstrap.servers` and those specifying replication factors.

# A list of host/port pairs to use for establishing the initial connection to the Kafka cluster.
# bootstrap.servers=localhost:9092
log4j.rootLogger=DEBUG, traceFile, stdout

log4j.appender.traceFile=org.apache.log4j.DailyRollingFileAppender
log4j.appender.traceFile.DatePattern='.'yyyy-MM-dd-HH
log4j.appender.traceFile.File=/tmp/connect-worker.log
log4j.appender.traceFile.layout=org.apache.log4j.PatternLayout
log4j.appender.traceFile.layout.ConversionPattern=[%d] %p %m (%c)%n

log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=[%d] %p %m (%c:%L)%n

log4j.logger.org.apache.zookeeper=ERROR
log4j.logger.org.I0Itec.zkclient=ERROR
log4j.logger.org.reflections=ERROR

bootstrap.servers=<redacted>

# unique name for the cluster, used in forming the Connect cluster group. Note that this must not conflict with consumer group IDs
group.id=connect-cluster

# The converters specify the format of data in Kafka and how to translate it into Connect data. Every Connect user will
# need to configure these based on the format they want their data in when loaded from or stored into Kafka
key.converter=org.apache.kafka.connect.json.JsonConverter
value.converter=org.apache.kafka.connect.json.JsonConverter
# Converter-specific settings can be passed in by prefixing the Converter's setting with the converter we want to apply
# it to
key.converter.schemas.enable=false
value.converter.schemas.enable=false

# Topic to use for storing offsets. This topic should have many partitions and be replicated and compacted.
# Kafka Connect will attempt to create the topic automatically when needed, but you can always manually create
# the topic before starting Kafka Connect if a specific topic configuration is needed.
# Most users will want to use the built-in default replication factor of 3 or in some cases even specify a larger value.
# Since this means there must be at least as many brokers as the maximum replication factor used, we'd like to be able
# to run this example on a single-broker cluster and so here we instead set the replication factor to 1.
offset.storage.topic=connect-offsets
offset.storage.replication.factor=3
offset.storage.partitions=25

# Topic to use for storing connector and task configurations; note that this should be a single partition, highly replicated,
# and compacted topic. Kafka Connect will attempt to create the topic automatically when needed, but you can always manually create
# the topic before starting Kafka Connect if a specific topic configuration is needed.
# Most users will want to use the built-in default replication factor of 3 or in some cases even specify a larger value.
# Since this means there must be at least as many brokers as the maximum replication factor used, we'd like to be able
# to run this example on a single-broker cluster and so here we instead set the replication factor to 1.
config.storage.topic=connect-configs
config.storage.replication.factor=3

# Topic to use for storing statuses. This topic can have multiple partitions and should be replicated and compacted.
# Kafka Connect will attempt to create the topic automatically when needed, but you can always manually create
# the topic before starting Kafka Connect if a specific topic configuration is needed.
# Most users will want to use the built-in default replication factor of 3 or in some cases even specify a larger value.
# Since this means there must be at least as many brokers as the maximum replication factor used, we'd like to be able
# to run this example on a single-broker cluster and so here we instead set the replication factor to 1.
status.storage.topic=connect-status
status.storage.replication.factor=3
status.storage.partitions=5

# Flush much faster than normal, which is useful for testing/debugging
offset.flush.interval.ms=10000

# These are provided to inform the user about the presence of the REST host and port configs
# Hostname & Port for the REST API to listen on. If this is set, it will bind to the interface used to listen to requests.
#rest.host.name=
#rest.port=8083

# The Hostname & Port that will be given out to other workers to connect to i.e. URLs that are routable from other servers.
#rest.advertised.host.name=
#rest.advertised.port=

# Set to a list of filesystem paths separated by commas (,) to enable class loading isolation for plugins
# (connectors, converters, transformations). The list should consist of top level directories that include
# any combination of:
# a) directories immediately containing jars with plugins and their dependencies
# b) uber-jars with plugins and their dependencies
# c) directories immediately containing the package directory structure of classes of plugins and their dependencies
# Examples:
# plugin.path=/usr/local/share/java,/usr/local/share/kafka/plugins,/opt/connectors,
plugin.path=/usr/share/java

kafka-connect-bigquery configuration:
connector.class=com.wepay.kafka.connect.bigquery.BigQuerySinkConnector
key.converter.schemas.enable=false
sanitizeTopics=true
topics=dev-test
tasks.max=1
keyfile=<redacted>
value.converter.schemas.enable=false
project=devproject
datasets=dev-test=analytics
value.converter=org.apache.kafka.connect.json.JsonConverter
key.converter=org.apache.kafka.connect.storage.StringConverter

Any help is appreciated!

any update about this issue? I face the same problem. Hopefully, there is a good solution to solve this.


Fixed errors for UE 4.24.3

I have updated the GameLiftClientSDK plugin to UE 4.24 GitHub version. It should also work with the Epic Games Launcher's version.

Thanks @Koralgoll I haven't looked at this in a while since I've been studying the client service, but I will try to take a look when possible.


Forbid assertThrows

See https://github.com/prestosql/presto/issues/5320 for rationale

WIP - Requires https://github.com/prestosql/presto/issues/5320

The other problem is @Test(expectedException.... I am not sure how verify that. regex?

reflection? same way as we do other test checks
however, not sure we decided we want to bad this altogether.
it could be current consensus is oneliners are still OK, but i could be forgetting something


waiting for transaction 24c5a1935df760efc1d76398d52bd5f94c8779dd56962292f541e16376c6c6e5 to be mined: not found

TRAC[2021-05-16T23:34:51+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:34:53+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:34:54+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:34:55+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:34:56+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:34:57+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:34:58+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:35:00+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:35:01+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:35:02+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:35:03+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:35:04+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:35:06+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:35:07+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:35:08+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
TRAC[2021-05-16T23:35:09+08:00] waiting for transaction 678f23ff07d3bf261a512527ce0f219f4f0bd8f5e2f3c050437170991c06844c to be mined: not found
Help me

same problem

INFO[2021-05-17T08:50:50Z] pss public key 0349e35f38d671564184a58fd0c8c59ed5006342fdbfa22a96b2831dc04a1007c7
INFO[2021-05-17T08:50:50Z] using ethereum address 8b482bf261ffcab4aecd5454d79958413977a701
INFO[2021-05-17T08:50:50Z] debug api address: [::]:1635
INFO[2021-05-17T08:50:51Z] using default factory address for chain id 5: f0277caffea72734853b834afc9892461ea18474
INFO[2021-05-17T08:50:52Z] waiting for chequebook deployment in transaction a2aa26d9f5592818261c0e56fbc269a919914d41ad21f4e3faadc980414e8b28
TRAC[2021-05-17T08:50:52Z] waiting for transaction a2aa26d9f5592818261c0e56fbc269a919914d41ad21f4e3faadc980414e8b28 to be mined: not found
TRAC[2021-05-17T08:50:53Z] waiting for transaction a2aa26d9f5592818261c0e56fbc269a919914d41ad21f4e3faadc980414e8b28 to be mined: not found
TRAC[2021-05-17T08:50:54Z] waiting for transaction a2aa26d9f5592818261c0e56fbc269a919914d41ad21f4e3faadc980414e8b28 to be mined: not found
0x8b482bf261ffcab4aecd5454d79958413977a701TRAC[2021-05-17T08:50:56Z] waiting for transaction a2aa26d9f5592818261c0e56fbc269a919914d41ad21f4e3faadc980414e8b28 to be mined: not found
TRAC[2021-05-17T08:50:57Z] waiting for transaction a2aa26d9f5592818261c0e56fbc269a919914d41ad21f4e3faadc980414e8b28 to be mined: not found
TRAC[2021-05-17T08:50:58Z] waiting for transaction a2aa26d9f5592818261c0e56fbc269a919914d41ad21f4e3faadc980414e8b28 to be mined: not found

Thank you for trying out Bee!
Please join our Discord for support: https://discord.gg/sU8NEtaR8y


Moving to tRPC v10

Hello,
Is there a roadmap or a plan to move to v10 anytime soon ?

npx create-t3-app@next is already on v10 alpha
as long as tRPC v10 remains in alpha i don't think it makes sense to upgrade on the release branch

I asked Alex about the state of v10, he said it's production ready, and if there will be any changes, they will be minor.

I asked Alex about the state of v10, he said it's production ready, and if there will be any changes, they will be minor.

Yes, it 100% works and you can use it by using the next-release: npx create-t3-app@next. I exclusively use this myself.
However, there are still API changes up for debate so I think we're better off keeping it on next for now, and moving it to main once the API is 100% final.


v.next

@mbranscomb v.next branch ready to go into master.
All sample viewers and security samples are now running 100.1

All build issue feedback from @ThadT @dkemlage @nCastle1 rectified. Requested review changes by @mbranscomb updated.


Running image timeout problem

Expected Behaviour
I expected the code to execute correctly:
import { GenericContainer, Wait } from 'testcontainers';

const main = async (): Promise<void> => {

    const container = await new GenericContainer('surrealdb/surrealdb:1.0.0')
        .withCommand(['start', '--strict', '--auth', '--log', 'debug', '-u', 'root', '-p', 'root', '--allow-guests'])
        .withExposedPorts(8000)
        .start();

    const host = container.getHost();
    const port = container.getMappedPort(8000);

    console.info(`host=${host} port=${port}`);

    //space for my tests

    await container.stop();
};

main().then(() => {
    console.info('end');
}).catch((error) => {
    console.error(error);
});

Actual Behaviour
The program ends with an error
Testcontainer Logs
(I don't know what to type here)
Steps to Reproduce

git clone https://github.com/szagi3891/testcontainer-bug
npm install
npx run index.ts
See error...

grzegorz@MacBook-Pro-playbook testcontainers-bug % npx tsx index.ts
(node:17861) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
oError: Port 8000 not bound after 60000ms
    at <anonymous> (/Users/grzegorz/Desktop/notatki/testcontainers-bug/node_modules/testcontainers/src/wait-strategies/host-port-wait-strategy.ts:52:15)
    at IntervalRetry.retryUntil (/Users/grzegorz/Desktop/notatki/testcontainers-bug/node_modules/testcontainers/src/common/retry.ts:49:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at HostPortWaitStrategy.waitForPort (/Users/grzegorz/Desktop/notatki/testcontainers-bug/node_modules/testcontainers/src/wait-strategies/host-port-wait-strategy.ts:46:5)
    at HostPortWaitStrategy.waitForInternalPorts (/Users/grzegorz/Desktop/notatki/testcontainers-bug/node_modules/testcontainers/src/wait-strategies/host-port-wait-strategy.ts:40:7)
    at async Promise.all (index 1)
    at HostPortWaitStrategy.waitUntilReady (/Users/grzegorz/Desktop/notatki/testcontainers-bug/node_modules/testcontainers/src/wait-strategies/host-port-wait-strategy.ts:14:5)
    at waitForContainer (/Users/grzegorz/Desktop/notatki/testcontainers-bug/node_modules/testcontainers/src/wait-strategies/wait-for-container.ts:17:5)
    at GenericContainer.startContainer (/Users/grzegorz/Desktop/notatki/testcontainers-bug/node_modules/testcontainers/src/generic-container/generic-container.ts:201:5)
    at main (/Users/grzegorz/Desktop/notatki/testcontainers-bug/index.ts:5:23)
grzegorz@MacBook-Pro-playbook testcontainers-bug %

Environment Information

Operating System: MacOs Ventura 13.6
Docker Version: Docker version 23.0.5, build bc4487a
Node version: v21.2.0
Testcontainers version: 10.3.2

Testcontainer Logs
(I don't know what to type here)

https://node.testcontainers.org/configuration/#logs

I assume you are not seeing an error when running any examples from the docs, so why do you think this is an issue with Testcontainers and not with the way you are starting your container?

I don't assume anything. I am learning the tool. I made a ticket because it looks like incorrect behaviour to me
I modified the way of running the sample code:
MacBook-Pro-4:testcontainer-bug grzegorzszeliga$ DEBUG=testcontainers npx tsx index.ts
  testcontainers [DEBUG] Testing container runtime strategy "TestcontainersHostStrategy"... +0ms
  testcontainers [DEBUG] Testing container runtime strategy "ConfigurationStrategy"... +1ms
  testcontainers [DEBUG] Testing container runtime strategy "UnixSocketStrategy"... +0ms
  testcontainers [DEBUG] Testing container runtime strategy "RootlessUnixSocketStrategy"... +0ms
  testcontainers [DEBUG] Container runtime strategy "RootlessUnixSocketStrategy" works +236ms
  testcontainers [DEBUG] Checking if image exists "surrealdb/surrealdb:1.0.0"... +0ms
  testcontainers [DEBUG] Checked if image exists "surrealdb/surrealdb:1.0.0" +5ms
  testcontainers [DEBUG] Image "surrealdb/surrealdb:1.0.0" already exists +0ms
  testcontainers [DEBUG] Acquiring lock file "/var/folders/ln/vb7mq1fj1wq5c10gkggbs61r0000gn/T/testcontainers-node.lock"... +3ms
  testcontainers [DEBUG] Acquired lock file "/var/folders/ln/vb7mq1fj1wq5c10gkggbs61r0000gn/T/testcontainers-node.lock" +2ms
  testcontainers [DEBUG] Listing containers... +1ms
  testcontainers [DEBUG] Listed containers +4ms
  testcontainers [DEBUG] Reusing existing Reaper for session "e6d4559533f6"... +0ms
  testcontainers [DEBUG] [eabec8ba83f4] Connecting to Reaper (attempt 1) on "localhost:32770"... +0ms
  testcontainers [DEBUG] [eabec8ba83f4] Connected to Reaper +3ms
  testcontainers [DEBUG] Releasing lock file "/var/folders/ln/vb7mq1fj1wq5c10gkggbs61r0000gn/T/testcontainers-node.lock"... +0ms
  testcontainers [DEBUG] Released lock file "/var/folders/ln/vb7mq1fj1wq5c10gkggbs61r0000gn/T/testcontainers-node.lock" +0ms
  testcontainers [DEBUG] Creating container for image "surrealdb/surrealdb:1.0.0"... +0ms
  testcontainers [DEBUG] [d304b16c6186] Created container for image "surrealdb/surrealdb:1.0.0" +29ms
  testcontainers [INFO] [d304b16c6186] Starting container for image "surrealdb/surrealdb:1.0.0"... +0ms
  testcontainers [DEBUG] [d304b16c6186] Starting container... +0ms
  testcontainers [DEBUG] [d304b16c6186] Started container +141ms
  testcontainers [INFO] [d304b16c6186] Started container for image "surrealdb/surrealdb:1.0.0" +0ms
  testcontainers [DEBUG] [d304b16c6186] Inspecting container... +0ms
  testcontainers [DEBUG] [d304b16c6186] Inspected container +4ms
  testcontainers [DEBUG] [d304b16c6186] Waiting for container to be ready... +0ms
  testcontainers [DEBUG] [d304b16c6186] Waiting for host port 32772... +0ms
  testcontainers [DEBUG] [d304b16c6186] Waiting for internal port 8000... +0ms
  testcontainers [DEBUG] [d304b16c6186] Host port 32772 ready +4ms
  testcontainers [DEBUG] [d304b16c6186] Host port wait strategy complete +0ms
  testcontainers [ERROR] [d304b16c6186] The HostPortWaitStrategy will not work on a distroless image, use an alternate wait strategy +93ms
  testcontainers [ERROR] [d304b16c6186] Port 8000 not bound after 60000ms +1m
  testcontainers [ERROR] [d304b16c6186] Container failed to be ready: Error: Port 8000 not bound after 60000ms +0ms
  testcontainers [DEBUG] [d304b16c6186] Stopping container... +0ms
  testcontainers [DEBUG] [d304b16c6186] Stopped container +106ms
  testcontainers [DEBUG] [d304b16c6186] Removing container... +0ms
  testcontainers [DEBUG] [d304b16c6186] Removed container +6ms
Error: Port 8000 not bound after 60000ms
    at <anonymous> (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/wait-strategies/host-port-wait-strategy.js:37:19)
    at IntervalRetry.retryUntil (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/common/retry.js:29:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at HostPortWaitStrategy.waitForPort (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/wait-strategies/host-port-wait-strategy.js:34:9)
    at HostPortWaitStrategy.waitForInternalPorts (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/wait-strategies/host-port-wait-strategy.js:29:13)
    at async Promise.all (index 1)
    at HostPortWaitStrategy.waitUntilReady (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/wait-strategies/host-port-wait-strategy.js:13:9)
    at waitForContainer (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/wait-strategies/wait-for-container.js:8:9)
    at GenericContainer.startContainer (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/generic-container/generic-container.js:140:9)
    at main (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/index.ts:5:23)
MacBook-Pro-4:testcontainer-bug grzegorzszeliga$

This fragment is particularly interesting:
  testcontainers [ERROR] [d304b16c6186] The HostPortWaitStrategy will not work on a distroless image, use an alternate wait strategy +93ms
  testcontainers [ERROR] [d304b16c6186] Port 8000 not bound after 60000ms +1m
  testcontainers [ERROR] [d304b16c6186] Container failed to be ready: Error: Port 8000 not bound after 60000ms +0ms

When I don't raise the logging level, I don't see the information that the waiting strategy on this platform is not working:
MacBook-Pro-4:testcontainer-bug grzegorzszeliga$ npx tsx index.ts
Error: Port 8000 not bound after 60000ms
  at <anonymous> (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/wait-strategies/host-port-wait-strategy.js:37:19)
  at IntervalRetry.retryUntil (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/common/retry.js:29:24)
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at HostPortWaitStrategy.waitForPort (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/wait-strategies/host-port-wait-strategy.js:34:9)
  at HostPortWaitStrategy.waitForInternalPorts (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/wait-strategies/host-port-wait-strategy.js:29:13)
  at async Promise.all (index 1)
  at HostPortWaitStrategy.waitUntilReady (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/wait-strategies/host-port-wait-strategy.js:13:9)
  at waitForContainer (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/wait-strategies/wait-for-container.js:8:9)
  at GenericContainer.startContainer (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/node_modules/testcontainers/build/generic-container/generic-container.js:140:9)
  at main (/Users/grzegorzszeliga/Desktop/notatki_main/testcontainer-bug/index.ts:5:23)

It would be great if all error-related information appeared on the user's console, even when the error reporting level is not raised.

I don't assume anything. I am learning the tool. I made a ticket because it looks like incorrect behaviour to me

I didn't say you assume, I said I assume :smile:
Looks like I correctly assumed it's an issue with the way you're starting the container - because the image is distroless you'll need to configure an alternate wait strategy. You can find more info in the docs: https://node.testcontainers.org/features/wait-strategies/
I will raise a separate issue to improve error logging in this case.

Thank you. The improved logs will be very useful :)

because the image is distroless
What does it mean ?

because the image is distroless

What does it mean ?

Distroless images contain only your application and its runtime dependencies. They do not contain package managers, shells or any other programs you would expect to find in a standard Linux distribution. More info here: https://github.com/GoogleContainerTools/distroless#distroless-container-images
This is an issue for you because the default wait strategy runs some shell commands to see if a port is bound, but no shell is available. You could therefore use alternate wait strategies, for example LogWaitStrategy or HttpWaitStrategy, which don't require a shell.

Thank you very much for the explanations. This HttpWaitStrategy strategy seems very interesting.


Need access to core.sshCommand

Not sure if that should be specific like for the author but run() is private too atm, so I cannot even configure it myself.

Sounds legit, yes :) I guess the author shortcut can remain and would internally just use the setConfig().


Correct branch names in CI

Uses new naming for branches in CI.

Thanks for this well spotted, happy to merge this


Add dragging support for multiple events

Is your feature request related to a problem? Please describe.
Sometimes you want to move more then one event.
Describe the solution you'd like
When dragging it should drag all selected events.
Describe alternatives you've considered
You can leave it like it is because CRTL+X and CRTL+V already allow for very easy.

I'd have to double check before closing this one, but I believe this is working in 2.0 visual editor?

Don't think so.


Update to Golang 1.19

Description

go.mod to 1.19
Build image updated
Remove deprecated ioutil usage

Issue link
/
Checklist

Purpose

[ ] Bug fix
[ ] New functionality
[ ] Documentation
[x] Refactoring
[ ] CI

Test

[ ] Unit test
[ ] E2E Test
[x] Tested manually

Introduce a breaking change

[ ] Yes (description required)
[x] No

Introduce changes in the Operator

[ ] Yes (description required)
[x] No

/reverify


Desktop - User renamed this room comment is not appearing after editing the room name

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue was found executing the PR #7217
Action Performed:

Create a new policy room by navigating to + > New room.
Click the chat header to open up Details.
Click Settings
Enter a new value for Room name and click Save.

Expected Result:
Comment as user renamed this room is displayed
Actual Result:
User renamed this room comment is not appearing
Workaround:
Unknown
Platform:

Where is this issue occurring?

Desktop App

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/151066457-89cd0114-00fd-4000-abc4-e256c2fb7a3d.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
View all open jobs on GitHub

Triggered auto assignment to @Luke9389 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@kavimuru this might have to wait to be tested as the App hits our production API and the Web-E PR is still in staging.

Also, rooms are still pretty buggy, we're working on it in multiple design docs right now.
This is behind beta so we shouldn't treat this as a super urgent concern. This is N7 IIRC

Issue not reproducible during KI retests. (First week)

not producible

not producible

We are blocked from reproducing due to the Crash (Second week)

OOO today, coming back to this soon.

Haven't been able to look at this yet. I'll drop if I don't have time by EOW.

@mvtglobally is this still not reproducible for you guys?

@Luke9389  We had one user unable to repro the issue
https://utest-dl.s3.amazonaws.com/testRunStepMinAttachmentsResult/19023359/Recording__1257.mp4?AWSAccessKeyId=AKIAJ2UIWMJ2OMC3UCQQ&Expires=1679456860&Signature=FaDNZ60PFNbrwyLo7PWNK9GOJAc%3D
While another user was blocked as app crashed. (which may be due to unrelated issue)

Ok, I think we should close this.
If it comes back up in the future we can deal w/ it.


Improve erroring

Many errors are quite hard to guess for folks on what's actually going wrong.
People come in to the Matrix chat and it's easy for us to tell what's wrong or what might be wrong.
We should add a means to add hints to an error on what might be wrong.
@therealprof started on utilizing thiserror properly, together with anyhow. This is a great start, but we need to start adding those additional hints to the error messages.
Could be a great issue for starters at oxidize impl Days.

I guess we should also setup a few guidelines to help people who want to help.
The basic idea of the error handling is those errors will stack and bubble up. I.e:

someone starts witch a high-level task ("flash this binary")
probe-rs detects the available probes and initialises them
probe-rs breaks down the task into DAP commands and sends those down in the right format to the probe specific implementation
the probe-specific implementations tries to execute those DAP commands against the target

At any of these levels errors may occur which are of two kinds:

Errors which need error specific handling by any higher level code
Errors which need to be reported back to the user with an appropriate level of detail

For 1) we use thiserror to have specific error types. The job here is to identify which errors can actually be handled by higher level code and remove those which are irrelevant and replace them by generic anyhow errors. The remaining errors should be as detailed as possible and include error specific details. A rule of thumb is: If there's no caller matching on an error variant, there's a good chance that the error variant can go and should be replaced by an anyhow::Error.
For 2) we use anyhow. anyhow allows us to have user friendly error messages which can have context attached. To properly use anyhow, any relevant custom error enum (remaining after the error pruning) should have a
     #[error(transparent)]
     Other(#[from] anyhow::Error),

value to allow pass through of anyhow errors from lower layers. anyhow also allows to add a context, so instead of merely matching and passing on an error, a caller handling an error with the question mark operator should also consider adding a anyhow::Context to let the user know what the caller was trying to do while the error occured.


Publish from GitHub Actions

This repository has been segregated from https://github.com/embulk/embulk-standards, and it is going to be published to Maven Central from GitHub Actions.

Thanks!


Two Hornet Nodes Panic with a few hours of each other

Describe the bug
Running two nodes on Pi4 4GB Hornet 3.0 2GB Profile both are running as services (no docker)
They have been running fine for about 1 - 2 days and both had a panic error on different transactions within a few hour of each other.
I've attached the logs for analysis.
Hornet_Panic.zip

Should be solved with #199


Creating Azure Service Principal fails from script

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az ad sp create-for-rbac
Errors:
400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token
Traceback (most recent call last):
python3.6/site-packages/knack/cli.py, ln 215, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 654, in execute
    raise ex
cli/core/commands/__init__.py, ln 718, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
cli/core/commands/__init__.py, ln 709, in _run_job
    cmd_copy.exception_handler(ex)
...
python3.6/site-packages/msrestazure/azure_active_directory.py, ln 486, in get_msi_token
    result.raise_for_status()
python3.6/site-packages/requests/models.py, ln 940, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az ad sp create-for-rbac --name {} --role {} --scopes {} --sdk-auth

Expected Behavior
getting back a json object for the principal
Environment Summary
Linux-4.15.0-1095-azure-x86_64-with-debian-stretch-sid (Cloud Shell)
Python 3.6.10
Installer: DEB

azure-cli 2.12.0

Extensions:
ai-examples 0.2.3

Additional Context

add to S176


[UiKit] Place all categories to index screen without sub-categories

Categories structures should become flat, instead of a tree one. All subcategories are now placed at the root level.

Verified successfully on UiKit on production (v.1.3.4 (24) iphone 11pro


Next To Watch sensor shows all history including the finished shows

Hi,
You are doing a great work with this. Here's a thing - sensor.trakt_next_to_watch_shows, as it is now, makes no sense as it includes all shows that I have ever seen and it shows them in no particular order.
You are fetching the list from "https://trakt.tv/users//progress"
while you should get it from here
https://trakt.tv/users//progress/watched/activity?hide_completed=true

Hey @l30ns , I'll let @dylandoamaral complete or correct my answer but we're not "fetching" lists from trakt.tv website, we're using Trakt API
The shows retrieved by next_to_watch sensor are the ones you've watched in the past, but still with unseen episodes. If you already saw all episodes, the show shouldn't be there. If however you have some shows you don't want to track anymore, you can use the exclude setting as explained in the doc.
Finaly, there is an order: It's from the oldest to the newest, based on the next to watch episode airdate. The issue is, with the upcoming media card, there is no mention about the year, I strongly encourage you to modify this piece of code https://github.com/custom-cards/upcoming-media-card/blob/master/upcoming-media-card.js#L291-L311 to include the year (This is what I've done on my side), and you'll see it's ordered.
Thanks

I can't give a better answer !

Hey @Anrolosia, thanks for the answer.
I'll admit that my note "shows them in no particular order" was a bit stretched and emotional. Sorry!
I don't know which Trakt API call are you using (dividing in you / any code of such complexity is a bit much for me), but what I am saying, the current version returns uncomfortably way too many shows from my list.
It includes shows that show up with 100% watched mark and it ignores HIDDEN feature. Basically, as I am active Trakt user, I need to list all the shows in ignore list to get to what I am looking for.
Trakt API "Shows/Watched Progress/Get show watched progress" has such feature (...watched?hidden=false&specials=false), but I understand that this is for 1 show only.
https://trakt.docs.apiary.io/#reference/shows/watched-progress/get-show-watched-progress?console=1
I hope this explains my point better.

Hey @l30ns , thanks for this feedback! I checked and it seems there is an issue with Trakt.tv API, because if I understand correctly their documentation:
By default, any hidden seasons will be removed from the response and stats. To include these and adjust the completion stats, set the hidden flag to true.
Like you can see here: https://github.com/dylandoamaral/trakt-integration/blob/main/custom_components/trakt_tv/apis/trakt.py#L108 we're not specifying any value for that field, that means hidden seasons shouldn't be retrieved.
I added a workaround and I'll let @dylandoamaral take a look at the PR (https://github.com/dylandoamaral/trakt-integration/pull/52) and decide if he wants to merge it or not

Hello @l30ns , could you confirm version 0.6.1 fixes your issue? Thanks

Feel free to reopen if the bug is still here


Validations inheritance

Following https://groups.google.com/forum/#!topic/ruby-shrine/sN6Zdg1YJxI

Thanks, looks great! I'll take one more look tomorrow, and then merge it in.


cleanup(metadata): dont upload metadata for android beta, and remove images

The type of this PR is: cleanup

This PR resolves [CX-]
Description
Other teams are free to change our appstore and playstore images, so we should not mess with their changes.
On ios we don't, on android we also don't now.
With that PR I also removed the images we had for android in the repo. We don't need them here, same as with ios, so they are removed.

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[ ] I have added a CHANGELOG.yml entry or my changes do not require one.

🛳🛳🛳
#squashongreen


NIFI-5242: Exclude JTS dependency from Elasticsearch client

I ran the full suite of unit tests and also tried with DeleteByQueryElasticsearch which uses the  CS that was bringing in the JTS dependency, all worked well.
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

I ran it against the full integration suite for the client service and it worked just fine.


Oracle fails to start (database/enterprise:<IP_ADDRESS>-slim)

I'm trying to start Oracle Database 12c R2, slim edition. I've done so succesfully before with the commands mentioned below. That was on a 2vcpu + 8gb ram VMware virtual machine running RHEL Atomic Host 7.6.4. The exact same commands now fail on a bare metal RHEL Atomic Host 7.6.4 with 8 cores and 32gb of ram. My commands:
docker volume create oracle-data
docker login container-registry-frankfurt.oracle.com
docker pull oracle container-registry-frankfurt.oracle.com/database/enterprise:<IP_ADDRESS>-slim
docker run --rm --detach --interactive --tty --publish 1521:1521 --volume oracle-data:/ORCL --name oracle container-registry-frankfurt.oracle.com/database/enterprise:<IP_ADDRESS>-slim

The output of docker logs oracle -f:
Setup Oracle Database
Oracle Database <IP_ADDRESS> Setup
Mon May 20 13:21:32 UTC 2019

Check parameters ......
log file is : /home/oracle/setup/log/paramChk.log
paramChk.sh is done at 0 sec

untar DB bits ......
log file is : /home/oracle/setup/log/untarDB.log
untarDB.sh is done at 27 sec

config DB ......
log file is : /home/oracle/setup/log/configDB.log
Mon May 20 13:21:59 UTC 2019
Start Docker DB configuration
Call configDBora.sh to configure database
Mon May 20 13:21:59 UTC 2019
Configure DB as oracle user
Setup Database directories ...

SQL*Plus: Release <IP_ADDRESS>.0 Production on Mon May 20 13:21:59 2019

Copyright (c) 1982, 2016, Oracle.  All rights reserved.

Connected to an idle instance.

SQL>
File created.

SQL> ORACLE instance started.

Total System Global Area<PHONE_NUMBER> bytes
Fixed Size                  8792536 bytes
Variable Size             402654760 bytes
Database Buffers          922746880 bytes
Redo Buffers                7983104 bytes
Database mounted.
ORA-03113: end-of-file on communication channel
Process ID: 132
Session ID: 5 Serial number: 25755

SQL> ERROR:
ORA-03114: not connected to ORACLE

SQL> ERROR:
ORA-03114: not connected to ORACLE

SQL> ERROR:
ORA-03114: not connected to ORACLE

SQL> ERROR:
ORA-03114: not connected to ORACLE

SQL> ERROR:
ORA-03114: not connected to ORACLE

SQL> Disconnected from Oracle Database 12c Enterprise Edition Release <IP_ADDRESS>.0 - 64bit Production
update password

Enter password for SYS:
create pdb : ORCLPDB1

SQL*Plus: Release <IP_ADDRESS>.0 Production on Mon May 20 13:22:11 2019

Copyright (c) 1982, 2016, Oracle.  All rights reserved.

Connected to an idle instance.

SQL>   2    3    4    5      create pluggable database ORCLPDB1 ADMIN USER sys1 identified by "Oradoc_db1"
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

SQL>     alter pluggable database ORCLPDB1 open
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

SQL>     alter pluggable database all save state
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

SQL> Disconnected
Reset Database parameters

SQL*Plus: Release <IP_ADDRESS>.0 Production on Mon May 20 13:22:12 2019

Copyright (c) 1982, 2016, Oracle.  All rights reserved.

Connected to an idle instance.

SQL>       alter system set encrypt_new_tablespaces=ddl scope=both
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

SQL> Disconnected

LSNRCTL for Linux: Version <IP_ADDRESS>.0 - Production on 20-MAY-2019 13:22:13

Copyright (c) 1991, 2016, Oracle.  All rights reserved.

Starting /u01/app/oracle/product/12.2.0/dbhome_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
System parameter file is /u01/app/oracle/product/12.2.0/dbhome_1/admin/ORCLCDB/listener.ora
Log messages written to /u01/app/oracle/diag/tnslsnr/bf24ccdf8bbc/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<IP_ADDRESS>)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
Start Date                20-MAY-2019 13:22:13
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/app/oracle/product/12.2.0/dbhome_1/admin/ORCLCDB/listener.ora
Listener Log File         /u01/app/oracle/diag/tnslsnr/bf24ccdf8bbc/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
The listener supports no services
The command completed successfully

DONE!
Remove password info
Docker DB configuration is complete !
ERROR : config DB failed, please check log /home/oracle/setup/log/configDB.log for details!
TT00: Gap Manager starting (PID:134)
2019-05-20T13:22:09.816837+00:00
USER (ospid: 132): terminating the instance due to error 313
2019-05-20T13:22:09.898466+00:00
System state dump requested by (instance=1, osid=132), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/orclcdb/ORCLCDB/trace/ORCLCDB_diag_74_20190520132209.trc
2019-05-20T13:22:10.179343+00:00
Dumping diagnostic data in directory=[cdmp_20190520132209], requested by (instance=1, osid=132), summary=[abnormal instance termination].
2019-05-20T13:22:11.301865+00:00
Instance terminated by USER, pid = 132

The configDB.log file:
configDB.log
The referenced trace file:
ORCLCDB_diag_74_20190520132209.trc.log

Maybe helpful: here's what my log output (docker logs oracle -f) looks like when started on my vm environment (exact same docker run invocation):
[rubin@KURO ~]$ docker logs oracle -f
Setup Oracle Database
Oracle Database <IP_ADDRESS> Setup
Tue May 21 05:18:23 UTC 2019

Check parameters ......
log file is : /home/oracle/setup/log/paramChk.log
paramChk.sh is done at 0 sec

untar DB bits ......
log file is : /home/oracle/setup/log/untarDB.log
untarDB.sh is done at 34 sec

config DB ......
log file is : /home/oracle/setup/log/configDB.log
Tue May 21 05:18:57 UTC 2019
Start Docker DB configuration
Call configDBora.sh to configure database
Tue May 21 05:18:57 UTC 2019
Configure DB as oracle user
Setup Database directories ...
startup database instance

SQL*Plus: Release <IP_ADDRESS>.0 Production on Tue May 21 05:18:57 2019

Copyright (c) 1982, 2016, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> ORACLE instance started.

Total System Global Area<PHONE_NUMBER> bytes
Fixed Size		    8792536 bytes
Variable Size		  369100328 bytes
Database Buffers	  956301312 bytes
Redo Buffers		    7983104 bytes
Database mounted.
Database opened.
SQL> Disconnected from Oracle Database 12c Enterprise Edition Release <IP_ADDRESS>.0 - 64bit Production

LSNRCTL for Linux: Version <IP_ADDRESS>.0 - Production on 21-MAY-2019 05:19:17

Copyright (c) 1991, 2016, Oracle.  All rights reserved.

Starting /u01/app/oracle/product/12.2.0/dbhome_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
System parameter file is /u01/app/oracle/product/12.2.0/dbhome_1/admin/ORCLCDB/listener.ora
Log messages written to /u01/app/oracle/diag/tnslsnr/3c56e6a06ccf/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<IP_ADDRESS>)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
Start Date                21-MAY-2019 05:19:17
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/app/oracle/product/12.2.0/dbhome_1/admin/ORCLCDB/listener.ora
Listener Log File         /u01/app/oracle/diag/tnslsnr/3c56e6a06ccf/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
The listener supports no services
The command completed successfully

DONE!
Remove password info
Docker DB configuration is complete !
configDB.sh is done at 54 sec

Done ! The database is ready for use .
# ===========================================================================
# == Add below entries to your tnsnames.ora to access this database server ==
# ====================== from external host =================================
ORCLCDB=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<ip-address>)(PORT=<port>))
    (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=ORCLCDB.localdomain)))
ORCLPDB1=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<ip-address>)(PORT=<port>))
    (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=ORCLPDB1.localdomain)))
#
#ip-address : IP address of the host where the container is running.
#port       : Host Port that is mapped to the port 1521 of the container.
#
# The mapped port can be obtained from running "docker port <container-id>"
# ===========================================================================
0x653fc8f8      2134  package body SYS.PRVT_ADVISOR.COMMON_DELETE_TASK
0x653fc8f8      7342  package body SYS.PRVT_ADVISOR.DELETE_EXPIRED_TASKS
0x653f6650         1  anonymous block
2019-05-21T05:19:16.907394+00:00
ORCLPDB1(3):Opening pdb with no Resource Manager plan active
Pluggable database ORCLPDB1 opened read write
Starting background process CJQ0
2019-05-21T05:19:17.094277+00:00
CJQ0 started with pid=41, OS id=202
Completed: ALTER DATABASE OPEN
2019-05-21T05:20:08.244384+00:00
TABLE SYS.WRP$_REPORTS: ADDED INTERVAL PARTITION SYS_P1467 (3428) VALUES LESS THAN (TO_DATE(' 2019-05-22 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_DETAILS: ADDED INTERVAL PARTITION SYS_P1468 (3428) VALUES LESS THAN (TO_DATE(' 2019-05-22 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_TIME_BANDS: ADDED INTERVAL PARTITION SYS_P1471 (3427) VALUES LESS THAN (TO_DATE(' 2019-05-21 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))

I just ran the above exact-same setup on Ubuntu 19.04 (Pop!_OS actually) with Docker 18.09.5, worked exactly the same as on VMware + RHEL Atomic Host 7.6.4, no problems whatsoever. Score so far (exact same commands, volumes, etc used):

Bare Metal AMD Ryzen 2700U 4core 16gb with Ubuntu 19.04 + Docker 18.09.5: works.
VMware 2vcpu 8gb with RHEL Atomic Host 7.6.4: works
Bare Metal Xeon E5405 4core, 32gb with RHEL Atomic Host 7.6.4: fails

The issue above is due to a database crash and has nothing to do with the Docker build files provided by this GitHub repository. Please open a support ticket with Oracle Database Support to find the cause of the database crash.


(PUP-7042) Mark strings in resource

This commit marks user-facing error and info strings in
lib/puppet/resource.rb and lib/puppet/resource/* for translation.

CLA signed by all contributors.

Closing and reopening to fix Travis.

Closing and reopening to fix CI.


panic: unresolve external: runtime.writeBarrier

I have following "plugin" code that I am trying to load using goloader: Link to code. It has a dependency on another package (link). On compiling the code, and loading using goloader (as explained in the example, link), it throws following error:
panic: unresolve external: runtime.writeBarrier

Any clue how to solve this?

@jimil749 , i can't find your loader code, could you give me more infomations?

Hi, sorry about that! This is the link to loader code: https://github.com/jimil749/reva-plugin-benchmark/blob/2dd5c5a9ad0a54dbfca8ce1bd87db121b442ffa5/main.go.
And this is the code that I am trying to load: https://github.com/jimil749/reva-plugin-benchmark/blob/2dd5c5a9ad0a54dbfca8ce1bd87db121b442ffa5/pkg/plugins/goloader/json.go
And this is the dependency(the code that is being loaded is dependent on this interface): https://github.com/jimil749/reva-plugin-benchmark/blob/2dd5c5a9ad0a54dbfca8ce1bd87db121b442ffa5/pkg/plugins/goloader/manager/manager.go

@jimil749, the loader looks ok， Did you strip the code on compile? if you strip it, the loader could not find symbol tables for runtime symbol.

I did not. I just followed this: https://github.com/pkujhd/goloader#examples (4th example) for compiling and loading.

I did not. I just followed this: https://github.com/pkujhd/goloader#examples (4th example) for compiling and loading.

i test your code, it runs ok on macosx/amd64.
if you are not， please give me your runtime env， e.g. os version, golang version.
in addition, you need call main.New replace json.New. if you do not set package name, "main" is default

Ahh ok. I'll test it out once again.
Still I'll provide the runtime env:
go version go1.16.4 linux/amd64
os: Ubuntu 20.04

Ahh ok. I'll test it out once again.
 Thanks for the quick response. I tested this out again locally. Seems to be working.
I think the problem occurs when I directly do go run main.go. if i build the go binary first and then execute the loader, it works fine! But when I go run or even try to run benchmarks using go test -bench=., it seems to panic!

ujhd! Thanks for the quick response. I tested this out again locally. Seems to be working.
I think the problem occurs when I directly do go run main.go. if i build the go binary first and then execute the loader, it works fine!


Prefix issue

I set up everything and tried it out, but the prefix isn't working at all. Instead of "&4[Owner]" it just adds the number 4 in front of my name

LP is showing that the prefix is there, that's more going to be on your chat plugin setup

how do I change that?

not an LP issue, I'd suggest speaking to the people behind your chat plugin or asking for support on the discord

how do I change that?

Check your chat plugin configuration? Not much we can suggest without that information.

its also not working without the chat plugin

LP doesn't modify chat, it just stores/provides that information for other plugins, it's up to you to install/configure a chat plugin to fetch that info from LP

You need a chat plugin to display prefixes.
Do you also have Vault?
Maybe read the FAQ on prefixes: https://github.com/lucko/LuckPerms/wiki/FAQ

what chat pl should I use?

Whichever one fits your needs, and supports Vault (assuming you use a Bukkit based server).

what did U use?

I just need  a few examples of good plugins, supporting LP (spiggot)

There is some examples on the wiki of plugins to use, this issue tracker is for issues with LP, not for discussion/support, please use the discord for that.

what wiki?

The LuckPerms wiki. Scroll up, you'll find it (I also linked to it earlier).
You'll find the chat plugins on the prefix page.

Ok - another thing, the permisiions arent working, i can switch between the groups and will still have every permission, could be because i'm an op?

You should not use Op when debugging permissions. Please read the FAQ, almost everything you've asked is answered there.

Thx for everything


Make sure the docs build with npm3 and npm2

Merging this since the ObjC test is unrelated and is failing on other PRs. Thanks @zpao! I'll try upgrading the tests to use Node 5.... (fingers crossed!)

Noooo don't go to node 5 :( I think we should stick to using LTS versions for this sort of infra.

People are going to be using Node 5 though. Move slow is for other companies!


Add watchOS support

This SpriteKit implementation is perfect for watchOS, but the target hadn't been set up. I had to do a few things to make it build for the watch:

watchOS doesn't have CoreAnimation, so I had to add our own impl for CACurrentMediaTime().
SKView is unavailable on watchOS. Instead, you have to use WKInterfaceSKScene, which can't be subclassed. I exposed the ActivityRingScene publicly so it can be used as such:

class InterfaceController: WKInterfaceController {

    @IBOutlet weak var activityRingInterfaceScene: WKInterfaceSKScene!

    var activityRingScene: ActivityRingScene!

    override func willActivate() {
        activityRingScene = ActivityRingScene(size: contentFrame.size)
        activityRingScene.ringWidth = 15
        activityRingInterfaceScene.presentScene(activityRingScene)
    }

    override func didAppear() {
        activityRingScene.animateProgress(to: 0.75, withDuration: 1.0)
    }

}

A few other non-critical things are unavailable on watchOS (CoreImage and GLKit), so those are just if-def'd out.

With those changes, it looks great and works well!

This is some solid work, thank you so much for contributing!


fix(debug): Removing debugging lines

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


InAppBillingPlugin with ACR.UserDialogs crashing

Xamarin Forms (Android)
If you use InAppBillingPlugin with ACR.UserDialogs, after closing the InAppBilling screen (success or not), the application crashes with the error:
mono.java.lang.RunnableImplementor.run
RunnableImplementor.java, line 30
Java.Lang.IllegalArgumentException: View=DecorView@42ec0b0[ProxyBillingActivity] not attached to window manager
Versions used: 4.0.2 and 4.2.0-beta
Removed ACR.UserDialogs, it stopped crashing!

Don't call it from the pop up.

When I call the method below, it is opening a pop up with the Billing options and I think the pop up is in conflict with ACR.UserDialogs, any suggestions or just removing ACR.UserDialogs from the project? Thanks
await billing.PurchaseAsync(productId, ItemType.InAppPurchase);


fix(readableColor): add missing export of readableColor to index

the export of readableColor() is missing in the index.js
import { readableColor } from 'polished' does currently not work

That precommit hook does not work as intended either:
~/polished (master +) λ git commit -m "add missing export of readableColor"
husky > npm run -s precommit (node v6.11.2)

 ✔ Running tasks for src/**/!(*.test).js
 ↓ Running tasks for src/**/*.test.js [skipped]
   → No staged files match src/**/*.test.js
husky > npm run -s postcommit (node v6.11.2)

INVALID COMMIT MSG: does not match "<type>(<scope>): <subject>" !
add missing export of readableColor

husky > post-commit hook failed (add --no-verify to bypass)
[master 78550f4] add missing export of readableColor
 1 file changed, 2 insertions(+)

~/polished (master) λ git log -1 --pretty=%B
add missing export of readableColor

@igl Thanks for catching and fixing this. By the precommit hook not working, you mean that it isn't blocking the commit despite not meeting the format?

@bhough Yes
I did --amend and force pushed with the correct title now.

@igl I will take a look at why that might be happening. Just tried on my side and it didn't create a  commit, so will need to dig further. Thanks again for the fix.


Prevent reconnect on udp connections to localhost

We don't expect udp connections to fail because they are stateless, but ...
udp connections may fail/raise an exception if used with localhost/<IP_ADDRESS>, if there is no one listening on the respective port.
To prevent a failing udp connection to localhost from halting the event
queue in logstash, we ignore exceptions if the connection is udp.
Fixes #19

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then  say 'jenkins, test it'.


[QUERY] EventGrid client publish retries

Library name and version
Azure.Messaging.EventGrid
Query/Question
Are there recommended approaches for retries when publishing custom events using the client?
Environment
No response

Hi @gjarzab.   Thank you for reaching out.  The Azure SDK clients have retry logic built-in and should take the appropriate retry actions for each operation.   Generally, we recommend using the default retry settings, but they can be adjusted if your application has a need to do so.   Information on configuring retries can be found in this sample.
To my knowledge, we don't have any special guidance for publishing custom events to Event Grid.  If you're running into specific difficulties where you believe that the built-in retries are not helping, please let us know and we'd be happy to assist.


chore(sdf): Migrate module remote spec endpoints to v2 api

This last API test:
go to the modules tab - see that you can click "view functions from this module" in the remote module list


Recover from partial inscription using recovery key

If the reveal transaction is not or cannot be mined, we should allow recovering inputs to the reveal transaction using the saved recovery key.

Would offer a bounty on this one 👍

are we screwed if we tried inscribing with --no-backup here and it got stuck before making the reveal? @raphjaph @casey

the acidelectro satoshi card might be stuck in a commit tx forever 😂😂

If you did with --no-backup you literally do not have the key to recover it, so yea you're screwed. Otherwise Bitcoin Core seems to recognize the unspent commit output and you can use it normally after it has been mined

If you did with --no-backup you literally do not have the key to recover it, so yea you're screwed. Otherwise Bitcoin Core seems to recognize the unspent commit output and you can use it normally after it has been mined

is there a reason for using a random key pair here instead of deriving a key from the wallet's seed?

That's a good point. I always thought we take a key from the wallet but just checked and we generate a new one.
The reason we need to back it up (I think) is because it is a rawtr descriptor (a tap-tweaked script). Now if we take a key from the wallet would that be enough for Bitcoin Core to find this weird output without the accompanying descriptor?
If you want to do some testing around this and open a PR I'd be happy to help!

We do recover from this


TypeORM configuration

The challenge here is to make a proper configuration for TypeORM on the NX monorepo setup.
AC

TypeORM is configured for local/dev environment
TypeORM is configured for prod environment
Migrations are working
e2e tests are working with DB
Proper package script commands are prepared in place
CI scripts updated to test backend e2e

@CristoferPortela, could you add documentation to the Readme about how to create migrations, sync, seed, work with entities, run e2e tests, and any other information that would make sense to anyone starting fresh with this project?


HD OSD artefacts

Small graphical artefacts are observed when HD OSD is overlaid.  This occurs and is consistent no matter what font is selected for any HD system.  An example is the top of the ENE directional arrow. Multiple other artefacts are observed at edges of certain elements that is unrelated to the source font image.

The problem is that the OSD elements are loaded as one large texture and therefore the OpenGL option CLAMP_TO_EDGE cannot be set for each element.
It would be better to load each element as a single texture and let OpenGL do the work. This also simplifies the loading of the textures considerably.

Using 512 separate texures is extremely unefficient. This problem can be fixed by adding 2-4px padding  beetween characters.

Ok.  So I'm torn on this.  I raised it but I'm the main person in the community that developed all the fonts. (AKA SNEAKY_FPV).  I'm a perfectionist and seeing this stuck out like a sore thumb.  If there's enough notice by other pilots I'll see if I can generate some font examples with the glyph padding.  But if no one else is complaining/noticing this, then I'll leave sleeping dogs lie.

Please do not regenerate fonts. Padding should be added programmatically while loading. Can be easily done, but this is not a high priority task for me.

Using 512 separate texures is extremely unefficient.

Normally you would use a TextureArray, but this can only be read in a shader, so no option here, unfortunately.

This problem can be fixed by adding 2-4px padding beetween characters.

We have some elements that need to be displayed side by side without a pixel gap (e.g. numbers with decimal point), wouldn't we have a gap?
Or am I on the wrong track?

We have some elements that need to be displayed side by side without a pixel gap (e.g. numbers with decimal point), wouldn't we have a gap? Or am I on the wrong track?

Drawing side-by-side characters would be straightforward if the game operated solely in 1080p or 720p resolutions. However, since the window size can vary, scaling becomes an issue. To render such pairs correctly, the only reliable method is to place pre-defined pairs side by side on a texture, detect them, and then draw a single rectangle. This issue is distinct from the artifacts encountered when rendering individual characters.

Automatic detection of the pairs (sometimes there are also several tiles, e.g. the INAV LOGO, or the crosshairs) is very time-consuming and must be specially predefined, as a custom font that has the graphics ‘in one piece’ would be simpler.
But I think supporting the corresponding goggles fonts would be better.
I measured the performance compared to my old, first implementation with single textures:
The current plugin needs about 15 uS when drawing on my computer, the version with single textures 35 uS, which is still 0.0% compared to the rest of XPlane and has no effect on the frame rate.

You cannot directly measure the impact because OpenGL calls enqueue drawing commands, which don't correlate with actual drawing time. However, I agree that with the power of modern PC GPU hardware, an additional ~100 batches per frame isn't significant enough to warrant optimization efforts.

After a short dive into OpenGL, I think the best and solution would be to use ‘Modern OpenGL’, until now the plugin uses the outdated ‘fixed pipeline’.
With ‘Modern OpenGL’ we can use a 2D texture array, which is exactly meant for such purposes, the disadvantage is that the texture array can only be accessed in the shader, so we need a separate vertex and fragment shader, which would be a bit more complex to implement, but, I think, the cleanest solution.
Custom shaders are not a problem in X-PLane, by the way.

A simple draw Test, in X-Plane, with a INAV-Fonts, GL_TEXTURE_2D_ARRAY and shaders:


NS Deletion hardening

closes: https://github.com/Kuadrant/dns-operator/issues/106

Changes here look fine, but does this cover everything that was being asked for from https://github.com/Kuadrant/dns-operator/issues/106?
The change to setting an ownerRef instead of using the watch seems like a good one, but doesn't really change the behaviour in any way, the existing Watch was doing the same thing to ensure the record reconcile was triggered on MZ changes. What about the MZ secrets if they are modified or deleted? Do they not need to be taken into account somewhere?

Changes here look fine, but does this cover everything that was being asked for from #106?
The change to setting an ownerRef instead of using the watch seems like a good one, but doesn't really change the behaviour in any way, the existing Watch was doing the same thing to ensure the record reconcile was triggered on MZ changes. What about the MZ secrets if they are modified or deleted? Do they not need to be taken into account somewhere?

hmm, yeah, that seems out of scope for the title of that issue, but it is mentioned in the body alright and I'd overlooked it. I'll make some changes to cover the extra areas.


refactor(seed): Add break; to default statement on switch challeng

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #15131

Description
Added break;after the default statement on challenge 'Adding a default option in Switch statements'.

@camperbot > Do not include issue numbers and following keywords in commit messages.
maybe then one shouldn't add/propose that by npm run commit.

@jntme Nice work. Congratulations on your first accepted pull request!


Specialize exceptions for different run-time errors

One thing most (all?) SQL libraries for C++ do is reporting run-time errors via a single std::exception derived class; requiring to parse the returned SQL error code or even error string to get specific details.
Since this lib focuses on type-safety, it would be great if there where specialized exceptions for different run-time error (classes), that could possible also report the erroneous attributes.
For example constraint violations (unique, foreign_key etc.), readonly violations, protocol errors etc. pp. could all be reported via distinct exceptions.

I wonder if that would actually make much of a difference in how you deal with errors?
Obviously you could treat a constraint violation in a different way than a protocol error, but would you? Your code can't really adjust itself and try again, can it?
I am really curious about this, as I am about to dramatically reduce the number exception classes in another project...

Perhaps a better solution would be some kind of extension to system_error
since you usually get at least one error code. This would allow you to
determine the cause for an error without needing a separate class. For that
matter, doing error_code variants for exception-less users could prove
useful. It is something that all of the connector implementers would have
to confirm to.
One possible time you'd have a different code path for a specific error is
duplicate key inserts.
On Tue, May 28, 2019, 10:12 Roland Bock<EMAIL_ADDRESS>wrote:

I wonder if that would actually make much of a difference in how you deal
with errors?
Obviously you could treat a constraint violation in a different way
than a protocol error, but would you? Your code can't really adjust itself
and try again, can it?
I am really curious about this, as I am about to dramatically reduce the
number exception classes in another project...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rbock/sqlpp11/issues/277?email_source=notifications&email_token=ABHZB22VRCBT3CPPJEBI2WTPXU4VNA5CNFSM4HQDP6F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWMIGII#issuecomment-496534305,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHZB24CXU72PQDIGE5V5TTPXU4VNANCNFSM4HQDP6FQ
.

One possible time you'd have a different code path for a specific error is duplicate key inserts.

That's the scenario I had in mind. When an exception occurs while INSERTing rows, a protocol error would be handled differently than a constraint violation. If e.g. a unique constraint violation occurs, a new ID could be generated, or the user could be asked to supply a different value. For protocol errors, this doesn't make sense.
At the moment, it's not possible to find out which column(s) exactly conflict. Sure, you could query the DB first and check if there would be any conflicts, but that's not very C++ idiomatic IMHO.
SRombauts/SQLiteCpp for example reports at least the (extended) error codes, which could be used for further analysis. With sqlpp11, it seems like parsing the error string is necessary to find out the exact violation.
As @Erroneous1 said, wrapping the (extended) error codes in some kind of system_error would probably already help a lot.

I am not a fan of system_error. But the connectors could certainly extend sqlpp11::exception to transport error codes.
As this affects the connectors, I am closing the issue here and put it on the wish list I am compiling.


[FLINK-28846] Trigger event on validation error

What is the purpose of the change
Trigger Warning event on validation error. This is very useful in cases where the webhook is not enabled.

Brief change log

Add event triggering to validation logic
Improve ResourceLifecycleState in case of failed initial valiadation: CREATED -> FAILED

Verifying this change
Extended FlinkDeploymentControllerTest to cover the new event triggering.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changes to the CustomResourceDescriptors: no
Core observer or reconciler logic that is regularly executed: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

Thank @gyfora this was indeed missing.


Feature Request: Add active label next to the active accoun in settings

Installation Information
All versions
Share your feedback
Quality of life improvement: Add a clear label to display which account is active. The only feeback is provided by the ✓ icon but its very subtle

Additional context (logs, images, etc)
No response

+1
This should be easy to fix.


[Feature Request] Layout container pullable

Existing Component
是
Component Name
el-container
Description
在与之间是否能增加宽度拖动的功能

Can Width Drag be Increased Between and ?

Can Width Drag be Increased Between aside and  main?

pr welcomed


Uploading Files to Google Cloud Storage

Feature Request
Uploading Files to GCS

@kaplanelad Would you mind assigning the ticket to me please?

done. thanks


Integration tests: Initial framework

This is a continuation of the integration tests, related to #376

/cc @vieux @chanwit @ehazlett

This is fantastic!
@aluzzardi is it possible to have a Markdown describing Swarm's testing plan? Like what you did for the roadmap.

@chanwit Yes! I'll be working some more on the framework so it will be possible to write more advanced tests (resources, scheduler policy, constraints, ...) and then I'll put a testing plan somewhere (hopefully sometime next week).
I'm planning to use these for regression tests as well. Right now, the version of docker in declared in DOCKER_VERSION (only 1.5 is available atm). Eventually, I'd like to have all versions of docker available in the registry and run the integration tests against all the supported ones (starting at 1.4 and onwards) and perhaps even include master (so we are sure that swarm works all the time with the latest docker before it's even released).
Hopefully I can get this running on docker's jenkins to run nightly. @jfrazelle?

@aluzzardi this is great!
Waiting for this PR to be merged, I'll crafting some tests for basic commands I can think of in the mean time.

:+1:

Thanks @kojiromike, I've made the changes.
PTAL

@kojiromike PTAL

LGTM
@kojiromike please open another PR if you can to fix stuff.

Happy to, but I think it's all good now. :)


Request: guide for extensible component CSS

Background

Design and document for inheritance or else prohibit it. -Joshua Bloch, Effective Java

There are many cases where I have a component with some internal structure:
{{!-- my-component.hbs, outer HTML --}}

The SCSS for that might look like this:
// my-component.scss
&__sub-component {
  background-color: white;
  color: rebeccapurple;
}

Those class names are generated and not available to a calling component. That is, if the author of my-component didn't anticipate a use-case (bolder, grayer, rotated, or capitalized), then there's no way for consumers of my-component to extend it to get the effect they want.
There are a few standard practices for adding customization affordances:
Passed-In Class
The author of my-component accepts a class and adds it to the sub-component:
{{!-- my-component.hbs, outer HTML --}}

  {{my-component subComponentClass='sub-component-override'}}

This lets the caller add any arbitrary customizations:
// caller.scss
.some-special-context {
  .sub-component-override {
    background-color: azure;
    font-weight: bold;
    border-radius: 3px;
    transform: rotate(10deg);
  }
}

One benefit of this practice is that it lets callers pass in functional CSS classes:
{{my-component subComponentClass='font--large flex--1 color--cornflowerblue'}}

CSS Variables
NB: this currently doesn't work with ember-component-css. See #48 and #282.
The author of my-component defines (some of) its styles using CSS variables. This allows consumers to customize specific aspects of the sub-component, but not add arbitrary CSS.
// my-component.scss
:root {
  --my-component-sub-component-background: white;
  --my-component-sub-component-color: rebeccapurple;
}

&__sub-component {
  background-color: var(--my-component-sub-component-background);
  color: var(--my-component-sub-component-color);
}

The caller can customize those variables, but not anything else:
// caller.scss
.some-special-context {
  --my-component-sub-component-background: coral;
  --my-component-sub-component-color: darkolivegreen;
}

.some-special-context appears within the DOM between :root and &__sub-component so its variables override those from :root. Note that it wouldn't work to define those variables on & in my-component.scss because that element is within .some-special-context.
Static Classes
The author of my-component adds classes that don't depend on {{styleNamespace}} to each of the sub-components. These classes are only for customization and not used by the component itself.
{{!-- my-component.hbs, outer HTML --}}

// my-component.scss
&__sub-component {
  background-color: white;
  color: rebeccapurple;
}

// .my-component and .my-component__sub-component don't appear in this file

Calling contexts target the "for-specialization" classes with regular CSS rules.
Static Attributes
In order to more clearly show that this is a hook for extensibility, we can turn the classes into attributes. For example,
{{!-- foo.hbs, outer HTML --}}

// calling CSS:
& {
  [data-subcomponent="foo:bar"] {
    color: chartreuse;
    background-color: magenta;
  }
}

Summary / Request
I'd love to hear about people's experiences with these different techniques. Do you have other ideas? What's a good medium for describing best practices for extensible component-css?

Actually, the CSS variables version doesn't currently work. See #282

I think i need a like bit of clearification. So are you saying that some addon author gives you access to “my-component” you have no way to customize those styles directly? You would have to do something with in a parent component or at the root level.. Am i reading that right? @jamesarosen

If that is your use case. One thing that I do when dealing with customizing addon component styles, is just create a “my-component/styles.EXT” in my app directory, and customize the styles i want. This will get the same namespace that the addon has, and due to the app styles getting included after the vendor styles on the page, will overwrite the addon styles just due to css using the last declared thing.
It’s not as.. direct, but the times i have used it is just when tweaking one or two things do it hasn’t been an issue..
But maybe this is irrelevant due to your use case being different.

I think i need a like bit of clearification. So are you saying that some addon author gives you access to “my-component” you have no way to customize those styles directly? You would have to do something with in a parent component or at the root level.. Am i reading that right?

Yes. Imagine the following scenario: ember-power-select uses ember-component-css to define its styles.
Its generated markup looks like

  Select…

And its CSS looks like
// .ember-power-select-trigger
.__0f5e3a {
  padding: 0 2rem 0 .5rem!important;
  background-color: transparent;
  border: 2px solid #fff2f2!important;
  border-radius: 4px;
  line-height: 1.6;
  white-space: nowrap;
  outline: 0;
}

// .ember-power-select-status-icon
.__0f5e3a__icon {
  border-width: 12px 7px 0;
  border-color: #fff transparent transparent;
}

Now in my app, I want to style those elements. The first one is easy since it's a top-level element:
{{ember-power-select class='my-custom-power-select'}}

.my-custom-power-select {
  background-color: blue;
  border-radius: 6px;
  color: white;
}

But I have no way of targeting the icon within.

just create a “my-component/styles.EXT”

Are you saying I can do
// my-app/app/styles/components/ember-power-select.scss
&__icon {
  ...
}

and it will be guaranteed to get the same class (__0f5e3a__icon) as the addon's version, which got compiled into vendor.css?

@jamesarosen yes. The 0f5e3a is a md5 hash of the name of the component so it will be consistent across vendor and your app css. you should be able to do that.


Fix recursion

This PR fixes the problem with high RetryCount values. For example if you set it to 2000-4000 you will get an overflow. On my machine for  RetryCount = 5000 and RetryDelay = TimeSpan.Zero I get following
2020-01-21T14:27:33.1249537Z [Serilog.Sinks.Fluentd] Retry send 1172
2020-01-21T14:27:33.1258691Z [Serilog.Sinks.Fluentd] Send exception Exception of type 'System.Exception' was thrown.
   at Serilog.Sinks.Fluentd.FluentdSinkClient.SendAsync(LogEvent logEvent, Int32 retryCount) in C:\Users\pzixe\Documents\Repos\serilog-sinks-fluentd\src\Serilog.Sinks.Fluentd\Sinks\Fluentd\FluentdSinkClient.cs:line 111
2020-01-21T14:27:33.1272425Z [Serilog.Sinks.Fluentd] Retry send 1173
2020-01-21T14:27:33.1279368Z [Serilog.Sinks.Fluentd] Send exception Exception of type 'System.Exception' was thrown.
   at Serilog.Sinks.Fluentd.FluentdSinkClient.SendAsync(LogEvent logEvent, Int32 retryCount) in C:\Users\pzixe\Documents\Repos\serilog-sinks-fluentd\src\Serilog.Sinks.Fluentd\Sinks\Fluentd\FluentdSinkClient.cs:line 111
2020-01-21T14:27:33.1286322Z [Serilog.Sinks.Fluentd] Retry send 1174
2020-01-21T14:27:33.1290703Z [Serilog.Sinks.Fluentd] Send exception Exception of type 'System.Exception' was thrown.
   at Serilog.Sinks.Fluentd.FluentdSinkClient.SendAsync(LogEvent logEvent, Int32 retryCount) in C:\Users\pzixe\Documents\Repos\serilog-sinks-fluentd\src\Serilog.Sinks.Fluentd\Sinks\Fluentd\FluentdSinkClient.cs:line 111
2020-01-21T14:27:33.1298182Z [Serilog.Sinks.Fluentd] Retry send 1175
Stack overflow.

C:\Users\pzixe\Documents\Repos\serilog-sinks-fluentd\ConsoleApp1\bin\Debug\
netcoreapp3.1\ConsoleApp1.exe (process 31440) exited with code -1073741571.

Ping?


add deprecation callout

this pr adds a callout to the dbt fal adapter docs as its no longer being maintained actively.
this pr is the first phase inspired by @kiwamizamurai 's first pr.
https://github.com/dbt-labs/docs.getdbt.com/pull/5368
this was confirmed and ok'ed by @chamini2 (maintainer)

preview; https://docs-getdbt-qsnk7j7qw-dbt-labs.vercel.app/reference/resource-configs/fal-configs


Update README.md - fix two grammar mistakes in README.md

I have two encountered two grammar errors in REAME.md file inside section "Train"
" fine-tuned. More training details.." should be " fine-tuned. For more training details.."
"More details please refer to.."  should be "Fore more details please refer to.."
Screenshot

Please review my PR

Thanks!


Added error reporting

Adding more information about what's going on to facilitate fault finding in release builds.
Harmonised coding style.

Hi, can you explain more about what this PR does? In what way does it provide more information? Can you provide an example?
I see you've also chosen to unilaterally reformat all of the code without any explanation. That makes it hard to see what functional changes you are proposing. It is also not good etiquette to just reformat the whole code base without first discussing it. Why should I adopt your preferred style over what was already there?

The main thing is extending the class interface to include PubSubClient::getLastStatus(), and then populating the underlying buffer with information about what's going on.  ie: More result code checking and explanation.
I acknowledge the code reformatting should have been  a separate request.  The existing code is a bit inconsistent in naming and calling convention; I picked one style that was already present and adopted that throughout for readability.
I wasn't originally planning to contribute back to your code base but someone suggested I was being selfish in not doing so.  No drama if you don't want it.  Thanks for your work so far.

In this instance, reformatting the code has broken all of the unit tests.
I can see merit in having the extra debug, but I can't merge with the reformatting.

How much larger is a sketch compiled with these changes added? Keeping the library as small as possible is an important requirement.

I'm not certain what additional files you're referring to.  It's additionally pulling in stdio.h but that's all(?).
If you'd like to nominate a code standard I'm happy to work with it.  If reformatting for consistency is off the table we can call it quits now.
Beyond that, I can see the Arduino IDE isn't going to cut it for contributing so there's a bigger exercise there for me which I won't get to for a while.

You've added lots of files under a .vs directory, such as .vs/ProjectSettings.json and other binary files.
If you want to contribute a functional change, please do that without forcing a style change on the project.


fix: updates required kotlin version for react native SDK

Summary
Updates required kotlin version for react native SDK. Fixes #310.
Checklist

[x] Does your PR title have the correct title format?
Does your PR have a breaking change?:  No

Appreciate this, thanks!


feat: add VANA warp route between Ethereum and Vana

Description

Deployed by Protofire

Backward compatibility

Testing

need to add coinGeckoId later


Fixes #2922 Beta account alert is missing

Description (required)
Fixes #2922 We used to see a beta login alert text when we login to beta account previously. Somehow it has gone, this PR puts it back.
Tests performed (required)
Tested with betaDebug and prodDebug on API 26 emulator
Screenshots showing what changed (optional - for UI changes)

Codecov Report

Merging #2928 into master will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff           @@
##           master   #2928   +/-   ##
======================================
  Coverage    3.64%   3.64%
======================================
  Files         245     245
  Lines       12194   12194
  Branches     1078    1078
======================================
  Hits          444     444
  Misses      11716   11716
  Partials       34      34

Impacted Files
Coverage Δ

...n/java/fr/free/nrw/commons/auth/LoginActivity.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Delayed integration update

Most likely causing #11
I can see that switching between files create a sort of "waiting list" of presence updates that takes a very long time to be processed.
https://github.com/Azn9/JetBrains-Discord-Integration/blob/5fc962150aa65c319bf5b57f90a93f7176ffa863/plugin/src/main/kotlin/com/almightyalpaca/jetbrains/plugins/discord/plugin/rpc/RpcService.kt#L87-L91

Fixed in https://github.com/Azn9/JetBrains-Discord-Integration/releases/tag/v2.0.2

Still occuring :(

May be fixed by 6a69c3150126b92c2ad466d94b979a5851d6eb63, to monitor


Freighter exit places player underneath ship

When exiting the freighter at the Freighter Site involved in the quest "Freight Fright" from Denis in Cydonia, the player is placed beneath the freighter's landing gear instead of outside the door.

Game Version
<IP_ADDRESS>
New Game
No
Reproduction Steps

Accept quest from Denis in Cydonia
Go to Freighter Site PoI on Mars
Enter freighter
Leave freighter via the door

I provided a fix...
https://www.nexusmods.com/starfield/mods/8181

Closing as a duplicate of https://github.com/Starfield-Community-Patch/Starfield-Community-Patch/issues/13


Set ALLOW_INCORRECT_HEADERS to True

Hello,
I've got some corrupted .heic and conversion is failing for them with this error:
Unable to convert /mnt/c/Users/TiTi/Downloads/heic/2-20230525_151210.heic: corrupted image(dimensions in header: (800, 360), decoded dimensions: (800, 357)). Set ALLOW_INCORRECT_HEADERS to True if you need to load them
I tried export ALLOW_INCORRECT_HEADERS=True with no success.
I suppose this is a Pillow flag.
I there a way to set it ?
Edit:
in converter.py, i replaced register_heif_opener() with register_heif_opener(allow_incorrect_headers=True) + recompile
and it worked like a charm

Closed with 1c028af5385f91556ea374290f534c23357381d3


Form Reset + Serialize

Implementing a reset functionality to form module
I implemented this instead of using form native due to Semantic modules, such as checkbox and dropdown (select), plus to avoid having to do "return false" on submitting the form via Ajax.
As instance of module occurs, it will set a data value (defaultValue) to all field identifiers passed through.
As reset is called, it will look these fields and set their value to their respective defaults.
May need a bit more polishing, but works as expected.
Manual call: $('.ui.form').form('reset');
Working example: http://jsfiddle.net/mktm/y5zopezh/

I have added a serialize function for the module.
Example: http://jsfiddle.net/y5zopezh/1/

Nice! I'll take a look at this for 1.8.0

@jlukic I am just implementing another function and changing the location of some of the old ones:
setDefaults to set.field.defaults
As well as a set.field.values function to set input/dropdown values by passing through an object with key:value
I had used this to do a CRUD via Ajax, and not having to go through each field on the form and set them one by one. Hopefully makes use for others.
I believe tonight I will be pushing this.

Thanks for the update. I'll review tomorrow.

Err today.. delayed

All merged in and ready to go. Will add a version of your example to docs and give you credit in release notes.

Rewriting serialize as get value and get values. More natural with write API, and less jargon.

Modified to get/read value(s) so as not to disrupt get.field which is already using the name to grab field elements.

Added ``clearand dropdownclear`


Setting the width of bar chart bars

Is it possible to adjust the width of individual bars generated for a bar chart? I noticed a widthOffset property in an old commit but that seems to have been since reverted, not sure if there is a current solution?

Hey @Destaq 👋, the property is now called inset as of 0.25.0.  See this example