ERR: database not found:

Trying to test the latest influx and I just got strange error:
version: influx 0.9-rc23
> show databases;
name: databases
---------------
name
imo

> use imo;
Using database imo;
> show series;
ERR: database not found: imo; (/home/philip/build/src/github.com/influxdb/influxdb/server.go:2526)

The web admin UI shows the database exists. I'm tying to use a cluster.

@NikolaBorisov Any errors in the log?  Also, can you post your config?

This is a cluster with 12 nodes. 5 brokers.
I didn't see any errors in the log.
# Welcome to the InfluxDB configuration file.

# If hostname (on the OS) doesn't return a name that can be resolved by the other
# systems in the cluster, you'll have to set the hostname to an IP or something
# that can be resolved here.
hostname = "somehostname"
bind-address = "<IP_ADDRESS>"

# The default cluster and API port
port = 8086

# Once every 24 hours InfluxDB will report anonymous data to m.influxdb.com
# The data includes raft id (random 8 bytes), os, arch and version
# We don't track ip addresses of servers reporting. This is only used
# to track the number of instances running and the versions, which
# is very helpful for us.
# Change this option to true to disable reporting.
reporting-disabled = true

# Controls settings for initial start-up. Once a node is successfully started,
# these settings are ignored.  If a node is started with the -join flag,
# these settings are ignored.
[initialization]

# Control authentication
# If not set authetication is DISABLED. Be sure to explicitly set this flag to
# true if you want authentication.
[authentication]
enabled = false

# Configure the admin server
[admin]
enabled = true
port = 8083

# Configure the HTTP API endpoint. All time-series data and queries uses this endpoint.
[api]
# ssl-port = 8087    # SSL support is enabled if you set a port and cert
# ssl-cert = "/path/to/cert.pem"

# Configure the Graphite plugins.
[[graphite]] # 1 or more of these sections may be present.
enabled = false
# protocol = "" # Set to "tcp" or "udp"
# address = "<IP_ADDRESS>" # If not set, is actually set to bind-address.
# port = 2003
# name-position = "last"
# name-separator = "-"
# database = ""  # store graphite data in this database

# Configure the collectd input.
[collectd]
enabled = false
#address = "<IP_ADDRESS>" # If not set, is actually set to bind-address.
#port = 25827
#database = "collectd_database"
#typesdb = "types.db"

# Configure the OpenTSDB input.
[opentsdb]
enabled = false
address = "<IP_ADDRESS>" # If not set, is actually set to bind-address.
port = 4242
database = "opentsdb_database"

# Configure UDP listener for series data.
[udp]
enabled = false
#bind-address = "<IP_ADDRESS>"
#port = 4444

# Broker configuration. Brokers are nodes which participate in distributed
# consensus.
[broker]
enabled = true
# Where the Raft logs are stored. The user running InfluxDB will need read/write access.
dir  = "/home/amy/data/influxdb/raft"

# Data node configuration. Data nodes are where the time-series data, in the form of
# shards, is stored.
[data]
enabled = true
dir = "/home/amy/data/influxdb/db"

# Auto-create a retention policy when a database is created. Defaults to true.
retention-auto-create = true

# Control whether retention policies are enforced and how long the system waits between
# enforcing those policies.
retention-check-enabled = true
retention-check-period = "10m"

# Configuration for snapshot endpoint.
[snapshot]
enabled = true # Enabled by default if not set.
bind-address = "<IP_ADDRESS>"
port = 8087

[logging]
write-tracing = false # If true, enables detailed logging of the write system.
raft-tracing = false # If true, enables detailed logging of Raft consensus.

# InfluxDB can store statistical and diagnostic information about itself. This is useful for
# monitoring purposes. This feature is disabled by default, but if enabled, these data can be
# queried like any other data.
[monitoring]
enabled = false
write-interval = "1m"          # Period between writing the data.

I also encounter this error, the log shows:

[srvr] 2015/05/13 07:28:20 pre-creating shard group for 1, retention policy default, database _influxdb
[srvr] 2015/05/13 07:28:20 pre-creating shard group for 2, retention policy default, database collectd
[srvr] 2015/05/13 07:28:48 retention policy enforcement check commencing
[broker] 2015/05/13 07:38:08 executing truncation check for 5 topic(s)
[srvr] 2015/05/13 07:38:48 retention policy enforcement check commencing
[broker] 2015/05/13 07:48:08 executing truncation check for 5 topic(s)
[srvr] 2015/05/13 07:48:50 retention policy enforcement check commencing
[broker] 2015/05/13 07:58:08 executing truncation check for 5 topic(s)
[srvr] 2015/05/13 07:58:50 retention policy enforcement check commencing
[broker] 2015/05/13 08:08:08 executing truncation check for 5 topic(s)
[srvr] 2015/05/13 08:08:50 retention policy enforcement check commencing
[srvr] 2015/05/13 08:13:20 shard group pre-create check commencing
[srvr] 2015/05/13 08:13:20 pre-creating shard group for 1, retention policy default, database _influxdb
[srvr] 2015/05/13 08:13:20 pre-creating shard group for 2, retention policy default, database collectd
[broker] 2015/05/13 08:18:08 executing truncation check for 5 topic(s)
[srvr] 2015/05/13 08:18:50 retention policy enforcement check commencing
[broker] 2015/05/13 08:28:08 executing truncation check for 5 topic(s)
[srvr] 2015/05/13 08:28:50 retention policy enforcement check commencing
[http] 2015/05/13 08:30:57 <IP_ADDRESS> - - [13/May/2015:08:30:57 +0800] GET /ping HTTP/1.1 204 0 - InfluxDBShell/0.9.0-rc29 527369ac-f907-11e4-8004-000000000000 81.113µs
[http] 2015/05/13 08:31:02 <IP_ADDRESS> - - [13/May/2015:08:31:02 +0800] GET /query?db=&q=show+databases%3B HTTP/1.1 200 105 - InfluxDBShell/0.9.0-rc29 55abec88-f907-11e4-8005-000000000000 1.020619ms
[http] 2015/05/13 08:31:14 <IP_ADDRESS> - - [13/May/2015:08:31:14 +0800] GET /query?db=collectd%3B&q=show+measurements HTTP/1.1 500 139 - InfluxDBShell/0.9.0-rc29 5cd908cf-f907-11e4-8006-000000000000 16.388262ms
[http] 2015/05/13 08:32:59 <IP_ADDRESS> - - [13/May/2015:08:32:59 +0800] GET /query?db=collectd%3B&q=show+measurements HTTP/1.1 500 139 - InfluxDBShell/0.9.0-rc29 9b195616-f907-11e4-8007-000000000000 634.172µs
[http] 2015/05/13 08:33:08 <IP_ADDRESS> - - [13/May/2015:08:33:08 +0800] GET /query?db=collectd%3B&q=show+series%3B HTTP/1.1 500 139 - InfluxDBShell/0.9.0-rc29 a0961cfd-f907-11e4-8008-000000000000 620.866µs
[http] 2015/05/13 08:37:09 <IP_ADDRESS> - - [13/May/2015:08:37:09 +0800] GET /query?db=collectd%3B&q=show+series%3B HTTP/1.1 500 139 - InfluxDBShell/0.9.0-rc29 30508f18-f908-11e4-8009-000000000000 633.949µs
[http] 2015/05/13 08:37:10 <IP_ADDRESS> - - [13/May/2015:08:37:10 +0800] GET /query?db=collectd%3B&q=show+measurements HTTP/1.1 500 139 - InfluxDBShell/0.9.0-rc29 3130622f-f908-11e4-800a-000000000000 13.541375ms
[broker] 2015/05/13 08:38:08 executing truncation check for 5 topic(s)
[http] 2015/05/13 08:38:50 <IP_ADDRESS> - - [13/May/2015:08:38:50 +0800] GET /query?db=collectd%3B&q=show+retention+policies+collectd%3B HTTP/1.1 200 168 - InfluxDBShell/0.9.0-rc29 6caef472-f908-11e4-800b-000000000000 718.408µs
[srvr] 2015/05/13 08:38:50 retention policy enforcement check commencing

I am sure there is data in influxdb: because when I tcpdump the traffic on port 2013 where influxdb listens on with graphite input, there is a a lot traffic like this:
host.my_hostname.type.vmpage_number.type_instance.slab_unreclaimable.vmem_value 4862.000000<PHONE_NUMBER>
host.my_hostnam.type.vmpage_number.type_instance.page_table_pages.vmem_value 2670.000000<PHONE_NUMBER>

my retention policies:
> show retention policies collectd;
name	duration	replicaN	default
1_day	24h0m0s		1		false
1_month	720h0m0s	1		false
1_week	168h0m0s	1		false
1_year	8760h0m0s	1		false
3_year	26280h0m0s	1		false
default	720h0m0s	1		true

my conf:
# Welcome to the InfluxDB configuration file.

# If hostname (on the OS) doesn't return a name that can be resolved by the other
# systems in the cluster, you'll have to set the hostname to an IP or something
# that can be resolved here.
# hostname = ""
bind-address = "<IP_ADDRESS>"

# The default cluster and API port
port = 8086

# Once every 24 hours InfluxDB will report anonymous data to m.influxdb.com
# The data includes raft id (random 8 bytes), os, arch and version
# We don't track ip addresses of servers reporting. This is only used
# to track the number of instances running and the versions, which
# is very helpful for us.
# Change this option to true to disable reporting.
reporting-disabled = false

# Controls settings for initial start-up. Once a node is successfully started,
# these settings are ignored.  If a node is started with the -join flag,
# these settings are ignored.
[initialization]
join-urls = "" # Comma-delimited URLs, in the form http://host:port, for joining another cluster.

# Control authentication
# If not set authetication is DISABLED. Be sure to explicitly set this flag to
# true if you want authentication.
[authentication]
enabled = false

# Configure the admin server
[admin]
enabled = true
port = 8083

# Configure the HTTP API endpoint. All time-series data and queries uses this endpoint.
[api]
# ssl-port = 8087    # SSL support is enabled if you set a port and cert
# ssl-cert = "/path/to/cert.pem"

# Configure the Graphite plugins.
[[graphite]] # 1 or more of these sections may be present.
enabled = true
protocol = "tcp" # Set to "tcp" or "udp"
address = "<IP_ADDRESS>" # If not set, is actually set to bind-address.
port = 2013
name-position = "last"
name-separator = "."
database = "collectd"  # store graphite data in this database

# Configure the collectd input.
[collectd]
enabled = false
address = "<IP_ADDRESS>" # If not set, is actually set to bind-address.
port = 25827
database = "collectd"
typesdb = "/usr/share/collectd/types.db"

# Configure the OpenTSDB input.
[opentsdb]
enabled = false
#address = "<IP_ADDRESS>" # If not set, is actually set to bind-address.
#port = 4242
#database = "opentsdb_database"

# Configure UDP listener for series data.
[udp]
enabled = false
bind-address = "<IP_ADDRESS>"
port = 4444

# Broker configuration. Brokers are nodes which participate in distributed
# consensus.
[broker]
enabled = true
# Where the Raft logs are stored. The user running InfluxDB will need read/write access.
dir  = "/data/data/influxdb/raft"
truncation-interval = "10m"
max-topic-size = 52428800
max-segment-size = 10485760

# Raft configuration. Controls the distributed consensus system.
[raft]
apply-interval = "10ms"
election-timeout = "1s"
heartbeat-interval = "100ms"
reconnect-timeout = "10ms"

# Data node configuration. Data nodes are where the time-series data, in the form of
# shards, is stored.
[data]
enabled = true
dir = "/data/data/influxdb/db"

# Auto-create a retention policy when a database is created. Defaults to true.
retention-auto-create = true

# Control whether retention policies are enforced and how long the system waits between
# enforcing those policies.
retention-check-enabled = true
retention-check-period = "10m"

# Configuration for snapshot endpoint.
[snapshot]
enabled = true # Enabled by default if not set.

[logging]
write-tracing = false # If true, enables detailed logging of the write system.
raft-tracing = false # If true, enables detailed logging of Raft consensus.
http-access = true # If true, logs each HTTP access to the system.

# InfluxDB can store statistical and diagnostic information about itself. This is useful for
# monitoring purposes. This feature is disabled by default, but if enabled, these data can be
# queried like any other data.
[monitoring]
enabled = true
write-interval = "1m"          # Period between writing the data.

Does the database collectd exist @liyichao ? Run SHOW DATABASES.

yes.
> show databases;
name: databases
---------------
name
_influxdb
collectd

did any of you find a solution?

Just ran into this with 0.9-rc32.

In 0.9.0-rc32 I found show series is returning ERR: database not found if the database is still empty, but is working if it contains some data.

I found the same thing @mnuessler. Very strange since the database is obviously in the meta data (as shown by show databases)

Old cluster design, no longer valid.


[HA] Issue with enabling dns when hostname-override is not resolvable

I am trying to do microk8s enable dns and it fails to perform the distributed_ops, due to the fact that it tries to access the nodes using the node's hostname.
If the node's hostname name is not resolvable, it could not connect to the nodes, preventing the enable command to update the nodes.
I think we should always contact the cluster agent using the node's IP addresses instead of the node name (as defined in the hostname_override).
In this https://github.com/ubuntu/microk8s/blob/38ced262ec52bc2fed3db4e0c5cf93258cbb70fa/scripts/cluster/distributed_op.py#L39-L42
We should get the InternalIP of the node instead.
When using jq,
microk8s kubectl get no -o json | jq '.items | .[] | .status.addresses | .[] | select(.type=="InternalIP") | .address'

Closing the issue. Pr merged


Allow passing down custom classes and ids without using a property

So the problem I've come into is that I can't put custom ids or classes to these components, and when I wanted to use the type property for a button, i have to use the btnType property which is inconvenient.
Svelte actually supports passing down properties to its children. So for example, on the button component:
// Instead of using the type={btnType}
<button type={btnType} class={buttonClass} on:click>
	{name}
	<slot />
</button>

// We can use $$restProps
<button {...$$restProps} class={buttonClass} on:click>
	{name}
	<slot />
</button>

Here's the official documentation:
https://svelte.dev/docs#template-syntax-attributes-and-props

The reason I didn't use it that the doc says "not recommended"

$$restProps contains only the props which are not declared with export. It can be used to pass down other unknown attributes to an element in a component. It shares the same optimisation problems as $$props, and is likewise not recommended.

But I can consider using this.

I think the Button component should have the default value, I will update to the following:
<button {type} class={buttonClass} {...$$restProps} on:click>
  {name}
  <slot />
</button>

I close the issue for now. Thank you for bring this up.


Decide whether to implement basis functions as higher-order functions or class-based functions

See #7


ask for help about the transfuser agent

hello, i have some problem about the difference of the agent between 2021 branch and the 2022 branch
As the network makes a prediction every two steps, for the step of not making predictions, 2021 branch directly uses the predicted waypoints of previous step, but in the 2022 branch, there are some changes. Can you tell me the details about the changes https://github.com/autonomousvision/transfuser/blob/a7d4db684c160095dec03851aff5ce92e36b2387/team_code_transfuser/submission_agent.py#L253
Thanks for your attention

This update_gps_buffer is for the custom particle filter that we use to denoise the GPS signal.
The filter is running at the full 20 Hz which is why it is called every frame.
It does not have any effect on the repeated trajectory.
The filter is described in section 2.1 of the appendix.

thanks for your reply. i will take a look at appendix


How to get BLEU score?

Hi
I'm trying to reproduce your work about YELP dataset.
However, the BLEU score that i've gotten is quite different.
I trained the model 200 times and got the score from your multi-bleu.py file.
(Hypothesis-transferred sentences from model
reference-human.txt file)
The score was 5.07.  It's quite low.
So how did you get the score 24.6? Could you let me know settings you've done?

Sorry to reply to you so late! I provided the outputs in https://github.com/Nrgeup/controllable-text-attribute-transfer/tree/master/outputs, or you can use the checkpoints I provided in https://github.com/Nrgeup/controllable-text-attribute-transfer/tree/master/method/mymodel-/save//***.pkl to generate outputs.


Lightly copyedit the text

I've been working on a tool that automatically scans prose for errors in usage. I ran it on your book. This pull request fixes some of the issues that it found, including inconsistent spacing at the end of a sentence (rather than choose 1 vs. 2 for the whole book, I made all the pages consistent, one way or the other); the lexical illusion where the word "the" is repeated multiple times; overuse of the word "very", and a few other issues. I hope this is useful to you.

This is great. Thanks! Can you point me to the tool so we can use it again?  (Since it's all LaTeX post-period spacing is irrelevant.)

The tool is still in the works, unreleased, but I'll send you a link once it's out. It doesn't yet do autocorrection, only pointing out errors, so I'm afraid I can't switch everything to be single spaced.

It would be interesting to see what you catch by running your tool on the HoTT book.


vscode-extensions.vadimcn.vscode-lldb fails to build on aarch64-darwin

Steps To Reproduce
Steps to reproduce the behavior:

run nix build github:nixos/nixpkgs/nixpkgs-unstable#vscode-extensions.vadimcn.vscode-lldb

Build log
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/rfyfxfw9alm3lfbh37b94r7idia3blvy-source
source root is source
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
applying patch /nix/store/hpb7avwnm52hp9klhxq75c02ihf5gkw6-cmake-build-extension-only.patch
patching file CMakeLists.txt
@nix { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" }
updateAutotoolsGnuConfigScriptsPhase
@nix { "action": "setPhase", "phase": "configurePhase" }
configuring
fixing cmake files...
cmake flags: -DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=OFF -DCMAKE_INSTALL_LOCALEDIR=/nix/store/ih46mjidpy6baf9klax4jj0drikqd17z-vscode-extension-vadimcn-vscode-lldb-1.7.4/share/locale -DCMAKE_INSTALL_LIBEXECDIR=/nix/store/ih46mjidpy6baf9klax4jj0drikqd17z-vscode-extension-vadimcn-vscode-lldb-1.7.4/libexec -DCMAKE_INSTALL_LIBDIR=/nix/store/ih46mjidpy6baf9klax4jj0drikqd17z-vscode-extension-vadimcn-vscode-lldb-1.7.4/lib -DCMAKE_INSTALL_DOCDIR=/nix/store/ih46mjidpy6baf9klax4jj0drikqd17z-vscode-extension-vadimcn-vscode-lldb-1.7.4/share/doc/CodeLLDB -DCMAKE_INSTALL_INFODIR=/nix/store/ih46mjidpy6baf9klax4jj0drikqd17z-vscode-extension-vadimcn-vscode-lldb-1.7.4/share/info -DCMAKE_INSTALL_MANDIR=/nix/store/ih46mjidpy6baf9klax4jj0drikqd17z-vscode-extension-vadimcn-vscode-lldb-1.7.4/share/man -DCMAKE_INSTALL_OLDINCLUDEDIR=/nix/store/ih46mjidpy6baf9klax4jj0drikqd17z-vscode-extension-vadimcn-vscode-lldb-1.7.4/include -DCMAKE_INSTALL_INCLUDEDIR=/nix/store/ih46mjidpy6baf9klax4jj0drikqd17z-vscode-extension-vadimcn-vscode-lldb-1.7.4/include -DCMAKE_INSTALL_SBINDIR=/nix/store/ih46mjidpy6baf9klax4jj0drikqd17z-vscode-extension-vadimcn-vscode-lldb-1.7.4/sbin -DCMAKE_INSTALL_BINDIR=/nix/store/ih46mjidpy6baf9klax4jj0drikqd17z-vscode-extension-vadimcn-vscode-lldb-1.7.4/bin -DCMAKE_INSTALL_NAME_DIR=/nix/store/ih46mjidpy6baf9klax4jj0drikqd17z-vscode-extension-vadimcn-vscode-lldb-1.7.4/lib -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_OSX_SYSROOT= -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_STRIP=/nix/store/lqiqj6s5jx196bpx0mr53d232b57y768-clang-wrapper-11.1.0/bin/strip -DCMAKE_RANLIB=/nix/store/lqiqj6s5jx196bpx0mr53d232b57y768-clang-wrapper-11.1.0/bin/ranlib -DCMAKE_AR=/nix/store/lqiqj6s5jx196bpx0mr53d232b57y768-clang-wrapper-11.1.0/bin/ar -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_INSTALL_PREFIX=/nix/store/ih46mjidpy6baf9klax4jj0drikqd17z-vscode-extension-vadimcn-vscode-lldb-1.7.4 -DVERSION_SUFFIX=
-- The C compiler identification is Clang 11.1.0
-- The CXX compiler identification is Clang 11.1.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /nix/store/lqiqj6s5jx196bpx0mr53d232b57y768-clang-wrapper-11.1.0/bin/clang - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /nix/store/lqiqj6s5jx196bpx0mr53d232b57y768-clang-wrapper-11.1.0/bin/clang++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
Version 1.7.4
-- Could NOT find Python3 (missing: Python3_EXECUTABLE Interpreter)
-- The C compiler identification is Clang 11.1.0
-- The CXX compiler identification is Clang 11.1.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /nix/store/lqiqj6s5jx196bpx0mr53d232b57y768-clang-wrapper-11.1.0/bin/clang - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /nix/store/lqiqj6s5jx196bpx0mr53d232b57y768-clang-wrapper-11.1.0/bin/clang++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/nix-build-vscode-extension-vadimcn-vscode-lldb-1.7.4.drv-1/source/build/debuggee
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

    BUILD_TESTING
    CMAKE_EXPORT_NO_PACKAGE_REGISTRY
    CMAKE_INSTALL_BINDIR
    CMAKE_INSTALL_DOCDIR
    CMAKE_INSTALL_INCLUDEDIR
    CMAKE_INSTALL_INFODIR
    CMAKE_INSTALL_LIBDIR
    CMAKE_INSTALL_LIBEXECDIR
    CMAKE_INSTALL_LOCALEDIR
    CMAKE_INSTALL_MANDIR
    CMAKE_INSTALL_NAME_DIR
    CMAKE_INSTALL_OLDINCLUDEDIR
    CMAKE_INSTALL_SBINDIR
    CMAKE_POLICY_DEFAULT_CMP0025

-- Build files have been written to: /tmp/nix-build-vscode-extension-vadimcn-vscode-lldb-1.7.4.drv-1/source/build
cmake: enabled parallel building
@nix { "action": "setPhase", "phase": "buildPhase" }
building
build flags: -j8 SHELL=/nix/store/49wn01k9yikhjlxc1ym5b6civ29zz3gv-bash-5.1-p16/bin/bash vsix_bootstrap
[ 12%] Generating extension.js

><EMAIL_ADDRESS>webpack
> webpack --mode=production --stats=minimal --output-path=/tmp/nix-build-vscode-extension-vadimcn-vscode-lldb-1.7.4.drv-1/source/build --output-filename=extension.js /tmp/nix-build-vscode-extension-vadimcn-vscode-lldb-1.7.4.drv-1/source/extension/main.ts

npm ERR! code EROFS
npm ERR! syscall mkdir
npm ERR! path /homeless-shelter
npm ERR! errno -30
npm ERR! rofs EROFS: read-only file system, mkdir '/homeless-shelter'
npm ERR! rofs Often virtualized file systems, or other file systems
npm ERR! rofs that don't support symlinks, give this error.

npm ERR! Log files were not written due to an error writing to the directory: /homeless-shelter/.npm/_logs
npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
make[3]: *** [CMakeFiles/extension.dir/build.make:91: extension.js] Error 226
make[2]: *** [CMakeFiles/Makefile2:175: CMakeFiles/extension.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:263: CMakeFiles/vsix_bootstrap.dir/rule] Error 2
make: *** [Makefile:231: vsix_bootstrap] Error 2
1 asset
43 modules
webpack 5.73.0 compiled successfully in 2458 ms

Additional context
Add any other context about the problem here.
Notify maintainers

@Artturin @NickHu
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"aarch64-darwin"`
 - host os: `Darwin 22.1.0, macOS 13.0.1`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.11.0`
 - channels(rasp): `""`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

adding export HOME=$TMPDIR in preBuild should fix it

adding export HOME=$TMPDIR in preBuild should fix it

Thanks! This works!

Make a pr?

Fixed by #211321
Re-open in case isn't fixed.


Feature/song detail

Hi folks. Sorry for delaying the delivery of this PR. This PR Isn't pack with all features I thought for this view. In fact, the more I developed and implemented features, the more I realized that would need to add some more (like if the user can edit a song info, he also should be able to manage the pedals.
There are some missing points, and if you look around some bugs should appear. The view and viewModels are very tightly coupled, which leads to some unexpected behaviors. I believe that once we have a service layer responsible SOT of user Data we could have better control of the app. Never the less, please, feel free to suggest any modification or points of improvement in the code.

What I Have Done

SelectPedalView rework
KnobView and Grid rework
SongDetailView displays song info
SongDetailView displays pedalsKnobs
SongDetailView edit song and pedals feature
SongDetailView edit pedal knobs feature
Modifications of Song can be saved to Song SOT
SongDetailView presents alert when saving song fails
SongDetailView animations
SongDetailViewModel responsable for dealing with SongDetailViewLogic
SongDetailViewModel tests

Thanks for the feedback, guys! All suggestions were accepted


nix develop fails with json parse exception

Describe the bug
nix develop fails with json.exception.parse_error.101
Steps To Reproduce
Steps to reproduce the behavior:

nix develop github:NixOS/nixpkgs#nix-info

Expected behavior
It does not fail
Additional context
Exact error:
error: [json.exception.parse_error.101] parse error at line 55, column 178: syntax error while parsing value - invalid string: ill-formed UTF-8 byte; last read: '" \n    local fn=\"$1\";\n    local fd;\n    local magic;\n    exec {fd}< \"$fn\";\n    read -r -n 4 -u \"$fd\" magic;\n    exec {fd}>&-;\n    if [[ \"$magic\" = '�'

I took a look at the generated /nix/store path and the issue seems to be the isMachO function which uses some non UTF-8 characters for the detection. The JSON parser rejects that because it's not valid UTF-8.
Notify maintainers
Fairly sure this affects all packages, but since nix flakes are experimental, not sure who the maintainer would be.
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.14.3-arch1-1, Arch Linux, noversion`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.4pre20210908_3c56f62`
 - channels(root): `"nixpkgs-21.11pre314682.65b70fbe4c3"`
 - channels(reeto): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

Realised I should file this in the Nix repo instead.


Fix Init sun.misc.GC for Java 9

Summary:
In java 9, sun.misc.GC is moved to sun.rmi.transport.GC , trying again
if sun.misc.GC is not found else throwing ClassNotFoundException.

So the new sun.rmi.transport.GC suffers the same problem as sun.misc.GC?

Yes, I think. This was more of a refactoring change which they did as part of this JDK-8132928.

Can this be merged?

Hi, when will this change be pushed to your mvn repo with version 2.6.1, so that I can consume this in my project.

Sorry for the delay - 2.6.1 should propagate to Maven Central shortly


automated build --> deploy on circleci

Per our discussion here --> https://twitter.com/betatim/status/1018730345712226306
I can give a first shot at this! But after some sleep :)

This is pretty great :)
# Container image Labels!
# Put these at the end, since we don't want to rebuild everything
# when these change!  I'll also mention a (somewhat nonrelated) bug to discuss for the repo mentioned in readthedocs!
1. Example Repo Bug
There is a bug with the repo provided as an example in the readthedocs, specifically this happens in the workflow:
  Downloading https://files.pythonhosted.org/packages/86/d0/b0192dc9a544da90f2d9150bcd84b981c6873e42a1f752b6affb89180ad8/scikit-image-0.12.3.tar.gz (20.7MB)
    Complete output from command python setup.py egg_info:
    To install scikit-image from source, you will need numpy.
    Install numpy with pip:
    pip install numpy
    Or use your operating system package manager. For more
    details, see http://scikit-image.org/docs/stable/install.html

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-669dg75q/scikit-image/
Removing intermediate container 25667ff23039

This is an error installing scikit-learn, from within the container build (so not something on the host?) I produced this on my local machine and on circleci, and I think it's an issue with this notebook dependency @jakevdp does this work for you?
https://github.com/jakevdp/PythonDataScienceHandbook
You can see the bug under the build step here:
https://circleci.com/gh/vsoch/repo2docker/6
2. Carry on, this one works!
I changed to the other example that I found:
https://github.com/norvig/pytudes
and this does the trick! The container builds (no run, debug mode) if you look at the build step here:
https://circleci.com/gh/vsoch/repo2docker/10
Click on build_deploy to see the tiny workflow:

and then I push it to docker hub:
https://hub.docker.com/r/vanessa/repo2docker/tags/
And the configuration example is here:
https://github.com/vsoch/repo2docker/blob/add/circleci/.circleci/config.yml
Note that I removed a section I usually have to only deploy when coming from master branch:
          filters:
             branches:
              only: master

but removed it here so that you could see the example from my development branch.
How does it work?
The user can define the following environment variables in circle:

DOCKER_USER and DOCKER_PASS, if found, will deploy to dockerhub
CONTAINER_NAME is the name of the container to deploy to (if not defined, will again try / I suppose some people have the same user/repo names across Docker Hub and Github!
REPO_NAME: is the full github url of the repo to build the notebook from. If not defined, will again use the repo that is being built from.

Next steps
documentation
I can write up some docs for this, and of course respond to your feedback! We would want to include the "next steps" for the user to instruct others to run their jupyter container from Docker Hub.
pull request
If you want to hook the repo up to circle I can wait to do a PR!
template actions
What other testing / metadata collection might be run on the containers / notebooks? We can do everything from registration to a server somewhere, upload of metadata, or even some kind of ping to notify people that something new is being deployed! Let's discuss. One cool thing to note is that circleci is (hopefully soonish) going to have a "template" kind of feature called an Orb --> https://github.com/CircleCI-Public/config-preview-sdk/blob/master/docs/structure.md and this would mean we could have shared template recipes to do some of these things.
Lots of discuss, and I hope a PR! ...but first I really am going to go sleep for a bit first :) I was too excited to work on this!

https://github.com/jakevdp/PythonDataScienceHandbook and numpy error

This is a known problem https://github.com/jakevdp/PythonDataScienceHandbook/issues/138#issuecomment-399614937
I think we should update our docs till this is fixed. pytudes seems like a good option.

Affirmative! Containershare repo2docker containers have all this.
https://vsoch.github.io/containershare
Thanks all!


[PWN-8079] [PWN-8076] [PWN-8080] Countries selection for Buy

Decided to move comments above into a separate refactoring task


WIP: Add support for NumericValue

Fixes #68

Did you measure the perf of isNumber vs hasNumericValue? Maybe we can use a benchmark for that. The difference is looking up generalCategory vs looking up numeric value, I am not sure which one is faster and if there is a significant difference.

Yes: hasNumericValue is little faster. See the benchmark.

@harendra-kumar kind reminder for a review


docs(Japanese): add bubble sort

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[x] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR
Add doc Bubble-Sort in Japanese.

Other information:

Translated docs/en/Sorting/Bubble-Sort.md into Japanese.

Hi @ming-tsai ,
I appreciate your review.
I added the index.


Update dependencies for LFortran

bison : required by build0.sh. We have a tarball so this should not be needed
re2c: required by build0.sh. We have a tarball so this should not be needed
python: again should not be needed. Used by build0.sh
toml: we do not run tests for the wasm build, so should not be needed.
Also I think when we have the LFortran_Build_to_wasm as ON, we naturally have the WITH_XEUS option as OFF, so in that case we would not need any of nlohmann_json, xeus-lite, xeus, cppzmq

I am happy to be listed as a maintainer for this recipe. Feel free to add me in.

Thanks @Shaikh-Ubaid, that would be a great help. You can submit a separate PR to add you in.


Implement NodeStage and NodeUnstage for rbd

Describe what this PR does
In NodeStage RPC call we have to map the device to the node plugin and make sure the device will be mounted to the global path.
in  nodeUnstage request unmount the device from the global path and unmap the device if the volume mode is block  we will be creating a file inside a stageTargetPath  and it will be
considered as the global path.
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>Related issues
Mention any github issues relevant to this PR. Adding below line
will help to auto close the issue once the PR is merged.
Fixes: #153

@j-griffith @humblec @ShyamsundarR @obnoxxx @nixpanic PTAL

@j-griffith @humblec @ShyamsundarR @obnoxxx @nixpanic PTAL

@ShyamsundarR @humblec PTAL

@poornimag  @ajarr
any idea why cephfs is failing?
Error EINVAL: Traceback (most recent call last):
  File "/usr/share/ceph/mgr/mgr_module.py", line 909, in _handle_command
    return self.handle_command(inbuf, cmd)
  File "/usr/share/ceph/mgr/volumes/module.py", line 182, in handle_command
    return handler(inbuf, cmd)
  File "/usr/share/ceph/mgr/volumes/module.py", line 208, in _cmd_fs_subvolumegroup_create
    return self.vc.create_subvolume_group(vol_name, group_name, mode=mode, pool=pool_layout)
  File "/usr/share/ceph/mgr/volumes/fs/volume.py", line 305, in create_subvolume_group
    sv.create_group(spec, pool=pool, mode=self.octal_str_to_decimal_int(mode))
  File "/usr/share/ceph/mgr/volumes/fs/subvolume.py", line 178, in create_group
    self._mkdir_p(path, mode)
  File "/usr/share/ceph/mgr/volumes/fs/subvolume.py", line 58, in _mkdir_p
    self.fs.mkdir(subpath, mode)
  File "cephfs.pyx", line 801, in cephfs.LibCephFS.mkdir (/home/jenkins-build/build/workspace/ceph-dev-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos7/DIST/centos7/MACHINE_SIZE/huge/release/14.2.1-636-g64f035c/rpm/el7/BUILD/ceph-14.2.1-636-g64f035c/build/src/pybind/cephfs/pyrex/cephfs.c:8613)
Error: (13, "error in mkdir 'volumes': error code 13")


build error

OS: Alpine latest docker image
package ： cmake 3.15
error msg
Scanning dependencies of target tfunnel
[ 16%] Building CXX object CMakeFiles/tfunnel.dir/src/main.cpp.o
In file included from /usr/include/boost/asio/detail/socket_types.hpp:82,
                 from /usr/include/boost/asio/detail/epoll_reactor.hpp:29,
                 from /usr/include/boost/asio/detail/reactor.hpp:21,
                 from /usr/include/boost/asio/detail/impl/scheduler.ipp:23,
                 from /usr/include/boost/asio/detail/scheduler.hpp:223,
                 from /usr/include/boost/asio/system_context.hpp:19,
                 from /usr/include/boost/asio/impl/system_executor.hpp:22,
                 from /usr/include/boost/asio/system_executor.hpp:129,
                 from /usr/include/boost/asio/associated_executor.hpp:21,
                 from /usr/include/boost/asio.hpp:21,
                 from /root/tfunnel/src/main.cpp:7:
/root/tfunnel/src/protocol.hpp:18:2: error: expected identifier before numeric constant
   18 |  TCP_CLOSE,
      |  ^~~~~~~~~
/root/tfunnel/src/protocol.hpp:18:2: error: expected '}' before numeric constant
In file included from /root/tfunnel/src/env.hpp:11,
                 from /root/tfunnel/src/main.cpp:8:
/root/tfunnel/src/protocol.hpp:8:14: note: to match this '{'
    8 | enum opcodes {
      |              ^
In file included from /usr/include/boost/asio/detail/socket_types.hpp:82,
                 from /usr/include/boost/asio/detail/epoll_reactor.hpp:29,
                 from /usr/include/boost/asio/detail/reactor.hpp:21,
                 from /usr/include/boost/asio/detail/impl/scheduler.ipp:23,
                 from /usr/include/boost/asio/detail/scheduler.hpp:223,
                 from /usr/include/boost/asio/system_context.hpp:19,
                 from /usr/include/boost/asio/impl/system_executor.hpp:22,
                 from /usr/include/boost/asio/system_executor.hpp:129,
                 from /usr/include/boost/asio/associated_executor.hpp:21,
                 from /usr/include/boost/asio.hpp:21,
                 from /root/tfunnel/src/main.cpp:7:
/root/tfunnel/src/protocol.hpp:18:2: error: expected unqualified-id before numeric constant
   18 |  TCP_CLOSE,
      |  ^~~~~~~~~
In file included from /root/tfunnel/src/env.hpp:11,
                 from /root/tfunnel/src/main.cpp:8:
/root/tfunnel/src/protocol.hpp:35:35: error: expected ')' before 'opcode'
   35 |  constexpr explicit header(opcodes opcode, uint16_t id, uint16_t len): opcode(opcode), id(id), len(len) {}
      |                           ~       ^~~~~~~
      |                                   )
/root/tfunnel/src/protocol.hpp: In static member function 'static constexpr header header::handshake(bool)':
/root/tfunnel/src/protocol.hpp:40:26: error: 'HELLO_FROM_CLIENT' was not declared in this scope; did you mean 'tfunn
el::HELLO_FROM_CLIENT'?
   40 |   return header(client ? HELLO_FROM_CLIENT : HELLO_FROM_PROXY, HELLO_MAGIC ^ PROTOCOL_VERSION, 0);
      |                          ^~~~~~~~~~~~~~~~~
      |                          tfunnel::HELLO_FROM_CLIENT
/root/tfunnel/src/protocol.hpp:10:2: note: 'tfunnel::HELLO_FROM_CLIENT' declared here
   10 |  HELLO_FROM_CLIENT = 0,
      |  ^~~~~~~~~~~~~~~~~
/root/tfunnel/src/protocol.hpp:40:46: error: 'HELLO_FROM_PROXY' was not declared in this scope; did you mean 'tfunne
l::HELLO_FROM_PROXY'?
   40 |   return header(client ? HELLO_FROM_CLIENT : HELLO_FROM_PROXY, HELLO_MAGIC ^ PROTOCOL_VERSION, 0);
      |                                              ^~~~~~~~~~~~~~~~
      |                                              tfunnel::HELLO_FROM_PROXY
/root/tfunnel/src/protocol.hpp:11:2: note: 'tfunnel::HELLO_FROM_PROXY' declared here
   11 |  HELLO_FROM_PROXY,
      |  ^~~~~~~~~~~~~~~~
/root/tfunnel/src/protocol.hpp: At global scope:
/root/tfunnel/src/protocol.hpp:52:1: error: expected declaration before '}' token
   52 | }
      | ^
make[2]: *** [CMakeFiles/tfunnel.dir/build.make:63: CMakeFiles/tfunnel.dir/src/main.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:76: CMakeFiles/tfunnel.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

sorry, I don't know why I didnt' get a notification for this. I'll have a look at it soon

Thank you for your response.
Can you provice a debian 9 x64 binary if possible while fix the build error ?

sorry, I don't know why I didnt' get a notification for this. I'll have a look at it soon

any fix to the source code ?

Hi @pisto ,
Can you provide some precompiled static binaries?
Thank you!


added keepEmptyValues option

If this option is set to true, it will stop propagation of a selected
date to other, currently empty, pickers in a date range setup.
Default for this option is false, to keep the current behavior.
fixes #1454

@steffendietz Great! Can you rebase the branch agianst the current master?

done 🚒

Thanks, LGTM. :+1:

@steffendietz The PR was merged butI had some extra comments, can you fix those in a separate pr against master? Thanks!

@acrobat Yes. Will do so tomorrow.


SafeMath - failed assert reason.

I would like to propose changing SafeMath library to use require instead of assert and also describe the reason why require failed.  It will make testing in truffle much easier.
For example current sub function is using assert.
    function sub(uint256 _a, uint256 _b) internal pure returns (uint256) {
        assert(_b <= _a);
        return _a - _b;
    }

We can change it to require and provide error description which will be then displayed truffle test.
    function sub(uint256 _a, uint256 _b) internal pure returns (uint256) {
        require(_b <= _a,"SafeMath library subtraction error");
        return _a - _b;
    }

A) internal functions of libraries are inlined in the implementing smart contract.
B) Strings cannot be compressed and hence take a good chunk of allowed bytecode size for deployment.
As a result, Adding error strings to SafeMath will considerably increase the size of contracts implementing it. I would avoid making such basic functions so heavy.
I won't mind a separate SafeMathWithReasonStrings library though. Just don't add reason strings to the default one.

I think libraries address is inlined in the contract using it. Implementing
reason will of course increase size of library and cost of its deployment,
but will not increase size of contract using this library.
Please correct me if I am wrong.
Nvertheless I think size argument is pretty important and it might be a
good reason no to implement this change. It would however help me in
debugging.
On Tue, Nov 20, 2018, 00:00 Mudit Gupta<EMAIL_ADDRESS>wrote:

A) internal functions of libraries are inlined in the implementing smart
contract.
B) Strings cannot be compressed and hence take a good chunk of allowed
bytecode size for deployment.
As a result, Adding error strings to SafeMath will considerably increase
the size of contracts implementing it. I would avoid making such basic
functions so heavy.
I won't mind a separate SafeMathWithReasonStrings library though. Just
don't add reason strings to the default one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OpenZeppelin/openzeppelin-solidity/issues/1506#issuecomment-440138698,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhG5LSVIilGICw8vEXcXlPf2fMaF6GOnks5uw4xTgaJpZM4YqNVU
.

@maxsam4 is right in that SafeMath is intended to be used as an internal library, and will be inlined in your source code (it'd be way too expensive to use otherwise). We are considering adding revert reasons, but we're not yet sure on how they should look like (there was some discussion in #888), and lack tooling to make sure they've been correctly implemented.
Regarding require, that's already part of OpenZeppelin! It was added in https://github.com/OpenZeppelin/openzeppelin-solidity/pull/1187.


Support Paths in response derives.

Up until now only Ident were supported in the response_derives section,
which unfortunately wouldn't allow us to provide fully qualified names.
This commit enables Path support, and provides us with an error message
if we couldn't parse a response_derive as a valid Path.

Thanks!


ReferenceError: global is not defined

What version of Hono are you using?
"hono": "^4.5.5"    "@hono/node-server": "^1.12.0"
What runtime/platform is your app running on?
Vercel, node
What steps can reproduce the bug?
Trying to test RPC as described here: https://hono.dev/docs/guides/rpc
Created monorepo folder:

client: sveltekit
server: Vercel based on Node.js: https://hono.dev/docs/getting-started/nodejs

Implemented RPC and trying to start the client: getting exception in the browser:

Sample repository:
https://www.dropbox.com/scl/fi/936tusnfveywjpc703ugs/monorepo-test.zip?rlkey=8d3hpjwtci055h74u783727v9&dl=0
If I comment out the line which imports routes from server, then browser starts without exceptions:
//import{ type ApiTestRoutes} from '../../../../hono-test/api/index'
What is the expected behavior?
no error in the browser
What do you see instead?
ReferenceError: global is not defined
Additional information
No response

P.S. Error occurs only if used "@hono/node-server/vercel".   If used "hono/vercel" -  no error.
import { handle } from "@hono/node-server/vercel";
//import { handle } from "hono/vercel";

Troubles is I need to run my API on Vercel using Node.js, not edge runtime.
https://hono.dev/docs/getting-started/vercel#node-js

This error appears on vite because the variable that you want to use is called before the dom is loaded...
Try this.
// vite.config.js
export default {
  define: {
    global: {},
  },
};

@caceresjayder  After applying your solution, getting another error during client start:

@Bobetti It's not the hono or hono node-server error. The issue is on the global reference. For the workaround of your example, you have to use
define: {
    global: 'globalThis',
},

@rjoydip Thank you for your response.
I started digging into what globalThis is and found interesting solution to my problem. By the way - your solution also helped. But turns out there is another one.
Inside my client application, which is sveltekit, which is using vite, I was importing route types using this line of code, after which error with global accured:
import {type ApiPricingRoutes} from "@dataServer/api/index";
Turns out, when the word "type" is inside curly braces, some server-side code could be imported along with the type ApiPricingRoutes. But we require only type, nothing more. In this case, this line should be re-written, and the word type must be moved outside of curly braces:
import type  {ApiPricingRoutes} from "@dataServer/api/index";
And the error was gone.


Documented steps for getting running on MAC/OSX?

Installing & enabling imgui-godot into my 4.2.2 GDScript Godot project works fine on Windows but the same project on my Mac machine throws an error when trying to load the addon or when trying to call any of the ImGui functions. I'm guessing this is because some binaries need to be built myself but I can't find anything in the documentation on what I need to do to move forward from here. (Do I need to build my own ImGui binaries? My own Godot binaries? Something else?)
  Can't open dynamic library: /Users/glenn/Projects/my-godot-project/addons/imgui-godot/bin/libimgui-godot-native.macos.debug.framework.
    Error: dlopen(/Applications/Godot.app/Contents/MacOS/../Frameworks/libimgui-godot-native.macos.debug.framework, 0x0002): tried:
    '/Applications/Godot.app/Contents/MacOS/../Frameworks/libimgui-godot-native.macos.debug.framework' (no such file),
    '/System/Volumes/Preboot/Cryptexes/OS/Applications/Godot.app/Contents/MacOS/../Frameworks/libimgui-godot-native.macos.debug.framework' (no such file),
    '/Applications/Godot.app/Contents/MacOS/../Frameworks/libimgui-godot-native.macos.debug.framework' (no such file).
  core/extension/gdextension.cpp:719 - GDExtension dynamic library not found: /Users/glenn/Projects/my-godot-project/addons/imgui-godot/bin/libimgui-godot-native.macos.debug.framework
  Failed loading resource: res://addons/imgui-godot/imgui-godot-native.gdextension. Make sure resources have been imported by opening the project in the editor at least once.
  res://test-ui-script.gd:19 - Parse Error: Identifier "ImGui" not declared in the current scope.

Have tried reloading the project in the Godot editor multiple times. Using Godot GDScript v4.2.2. Installed the addon using the built-in plugin manager. Works fine on Windows but not on Mac.

Nevermind, reinstalling the plugin from Godot's AssetLib fixed it. Must've been a fluke.


Remove unused patch and fix an env var typo

$CPPFLAFS is not a thing, right?
Also, #480 has been merged upstream.

X-Ref: https://github.com/conda-forge/pynacl-feedstock/pull/16

LGTM.  Thanks for putting this together @teake.  I'll get new packages built for defaults and comment here when they are available.

Packages with this change are now available in defaults


[OpenCL] Fixes CUDA specific test run on SYCL (#56)

The testBadParentValuesOnGPU should only be run on CUDA devices, as the
test checks for particular CUDA behaviour. We don't actually provide a
SYCL kernel for GatherTree and so it's not a problem that the tests
don't target SYCL.

Can one of the admins verify this patch?

@tensorflow-jenkins test this please


file extension restriction "onedrive business"

can we have docs updates for file extension restriction, specified here (https://community.office365.com/en-us/f/172/t/280295)
also "file without extension" is failing in response (500 http error) with description
code: -2130575312, Microsoft.SharePoint.SPException | message: The URL 'Documents/ankit' is invalid.  It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.
but this is not mention, what should we expect for file without extension ?

I wasn't able to reproduce the error creating a file without extension. Here's what my request looked like:
PUT /personal/{user-upn}/_api/v2.0/drive/root:/myFilename:/content HTTP/1.1
Authorization: Bearer ...
Content-Length: 23
Content-Type: application/octet-stream

The contents of my file

And I got back HTTP/1.1 201 Created

Closing out old issues. If this continues to be an issue, please reopen and provide additional details.


methodop ». / methodop >>.

In language/operator, in the precedence list, the line

Method call	left	.meth .+ .? .* .() .[] .{} .<> .«» .:: .= .^ .: i

lacks the ». operator.

I'm still wondering whether this could be intentional. If you think about it, » is a meta-operator. Meta-operators usually don't appear in the precedence list.

@0rir

In language/operator, in the precedence list, the line

Precedence Level
Associativity
Examples

Method call
left
.meth .+ .? .* .() .[] .{} .<> .«» .:: .= .^ .: i

lacks the ». operator.

As a perhaps minor point, I see that the title of the third column of the table is "Examples". That suggests to me a deliberate decision not to promise an exhaustive list. (It may be that the table originally did promise an exhaustive list and then someone altered the title of the third column to "Examples". I don't know, but it's definitely "Examples" in the rendering I'm looking at.) So from at least that perspective it's presumably perfectly cromulent not to include »..

It's perhaps interesting to note discrepancies between this table and the other precedence list on the same page, the one on the left of the page. (I tend to refer to that list instead of the table because A) it appears to be more exhaustive in intent, and B) it lists operators in order of precedence, unlike the table. cf #4085 et al.)
The list of ops on the left includes a corresponding "Method postfix" section. Here's the ops it lists, expressed in the same form and ordering as the line in the table above:

Method postfix precedence
. .& .+ .? .* .() .[] {} .<> .< > .«» .:: .= .^ .:<prefix operator> ». / >>. .postfix / .postcircumfix ,=

Here are entries in the (exhaustive?) list's "Method postfix" section but not the table's corresponding "Examples" row:
.& ». / >>. .postfix / .postcircumfix ,=
(I didn't include . because I take it to correspond to the table's .meth. Likewise .:<prefix operator> because I take it to correspond to the table's .:.)
So the table omits 5 entries that are in the list. One of these is is »..
(I'm not sure why ,= is in the list. ,= is just an op= compound op at first blush, but I vaguely recall there being something special about it; perhaps there's some good reason to explicitly list it.)
Going in the other direction, here are the "Examples" in the table's "Method call" row that aren't in the (exhaustive?) list's corresponding section:
i
So, just the one. (And as examples go, i seems like an... interesting choice to include. I shan't comment on it further but didn't want to omit at least a mention of it.

B) (I thought I thought, but as I write this wonder if I'm losing my mind) it lists operators in order of precedence, unlike the table. cf https://github.com/Raku/doc/issues/4071 et al.)

I think you are right. Something got broken around a fixup of the operator list but the links are in a somewhat better shape. Also, alas, we basically cannot deploy to that site at the moment and everyone is hoping for a swift resolution for the new docs site.

(I'm not sure why ,= is in the list. ,= is just an op= compound op at first blush, but I vaguely recall there being something special about it; perhaps there's some good reason to explicitly list it?)

Funny that you point this one out; it's still kinda foggy if = is considered a meta-operator in Raku or Rakudo, and one thing is sure - it's causing a lot of confusion with .= (which has "methodop precedence" documentedly, but... why).

@raiph, I accept that your point that the table is of 'examples' invalidates this issue.  That is rather unsatisfying since the  page's ToC is not doc'ed to be a precedence table.  And that there are errors within a single line of the examples table.
I am thinking of closing this and raising an issue that a separate page be created as a traditional precedence table.  I am sad to stack up work that I cannot do;  especially since I generally find  Raku's precedence structure to just work .
@2colours, I don't consider = a meta op; and I call WHATEVER= compound ops.  While .WHATEVER are deviant method ops.

@0rir what do you think about this issue? Can it be closed, or if not, how to make it actionable?

@2colours, I don't see how it is not actionable; other than by lack of agreement, interest or time.
I decided against dumping this and raising the idea of a separate precedence page, because there are then three datasets to resolve:  the 'partial precedence table',  the operator page's ToC, and the new page.
A precedence table could  be appended to the end of the operator page.
I am patient.  And especially so, given that the AST has been suggested as a good tool for getting alternate actions from the Raku grammar:  linting, cataloging usage, maybe even this issue.

@2colours, I don't see how it is not actionable; other than by lack of agreement, interest or time.

I mean, it is not actionable literally. It doesn't say what the desired outcome is and lies on outdated presumptions that I at least thought were well-understood.

the "precedence table" is ordered by precedence again, that issue has been resolved in the meantime.
it is actually known to be non-exhaustive - it even says "examples", and you didn't explicitly object to that?
it's not clear at all what "exhaustive" would mean. Should all op= operators be listed? Is there even a point when op= is a productive formation, i.e if you define lol as an operator, lol= will just work? (In this sense, = is surely a meta-operator.)
It might make sense to add ». to the list. That is actionable, and doesn't address the "exhaustiveness issue".
Even though, I think that begs the question what makes it stand out of usual hyper meta-operator stuff, as it seems to obey the same syntax rules. From a "precedence table" point of view, the dot is not distinguished, even though it isn't a first-class operator, just syntax in the parser. Consequently, no meta-operator can work with it "naively", and the result will always be another piece of syntax, rather than first-class citizens of the language. That is worth marking but it should be done in a consistent manner...

@2colours and  @raiph,  you have made good points that make my issue trivial as titled.  By that closing the issue makes sense.
So this conversation is misplaced and the blame is mine.   But with a view toward forming a better issue, to @2colours'  points:

That has improved the situation greatly.
I accepted (then and now that the "Examples" title  invalidates this issue.   But if one is looking for a precedence they may ignore the preamble entirely and through practice accept it as the precedence table.
"Exhaustive" ~~ "Complete".   My take:   For some reasonably inclusive definition of potential  racruits it should make the various operators recognizable and their relative precedence levels understandable.  (Using my personal terminology previously was unhelpful.)
Adding ». does address the  "exhaustiveness"  in a small way.   ». might stand out as one of the commonest of dot constructions.      The doc's Technically, not a real operator; it's syntax special-cased in the compiler. is pretty useless to one reading the page to use ops at a basic level.    Ops are doc'ed on three separate pages now and those are not well connected (when last I checked).


Doesn't register as abstract service, only as implementation.

I have this class:
public sealed class Settings
{
   public required string ConnectionString { get; init; }
}

I have a fluent validator like so:
[RegisterTransient(typeof(IValidator<Settings>))]
public class SettingsValidator : AbstractValidator<Settings>
{
   public SettingsValidator() =>
      RuleFor(static settings => settings.ConnectionString)
        .NotEmpty()
        .WithMessage($"{nameof(Settings.ConnectionString)} must have a valid connection string.")
        .Must(BeAbleToConnect)
        .WithMessage($"{nameof(Settings.ConnectionString)} is not valid or cannot connect to the database.");

   static bool BeAbleToConnect(string connectionString)
   {
      try
      {
         using SqlConnection connection = new (connectionString);

         connection.Open();

         return true;
      }
      catch { return false; }
   }
}

I expect it to register like so:
serviceCollection.AddSingleton<IValidator<Settings>, SettingsValidator>();

However, it always registers it like this instead:
// <auto-generated>
//     Automatically generated by AutoRegisterInject.
//     Changes made to this file may be lost and may cause undesirable behaviour.
// </auto-generated>
using Microsoft.Extensions.DependencyInjection;
public static class AutoRegisterInjectServiceCollectionExtension
{
    public static Microsoft.Extensions.DependencyInjection.IServiceCollection AutoRegisterFromMyProject(this Microsoft.Extensions.DependencyInjection.IServiceCollection serviceCollection)
    {
        return AutoRegister(serviceCollection);
    }

    internal static Microsoft.Extensions.DependencyInjection.IServiceCollection AutoRegister(this Microsoft.Extensions.DependencyInjection.IServiceCollection serviceCollection)
    {
        serviceCollection.AddTransient<MyProject.SettingsValidator>();
        return serviceCollection;
    }
}

This is being fixed in 1.3.1
You can track the build here:
https://github.com/patrickklaeren/AutoRegisterInject/actions/runs/8161809642/job/22311365115
It will be published to Nuget once done. Thank you for the suggestion. I trust this meets requirements.
Documentation will be updated to follow.


[QUESTION]: Next Release

Hello,
Do you have a date to the next release?
We have some crashes related with the callback call in the SDWebImageDownloader at line 145.
Many thanks

I would like to know the release date too, as I get same kind of crash at line : 173
SDWebImageDownloader.m line 173
__72-[SDWebImageDownloader downloadImageWithURL:options:progress:completed:]_block_invoke102
https://github.com/rs/SDWebImage/issues/1299

Until the release comes out, we are using the master version.

What is that ? I'm using the latest official release.

The version from master.
Instead of pod 'SDWebImage', '~>3.7.3' use pod 'SDWebImage', :git => 'https://github.com/rs/SDWebImage.git', :branch => 'master'

didn't know! thx.

Version 3.7.4 is out.


protected class

dont know were else to post this
the class cant be used to make a mod

and dont give me rubbish about its the wrong place

@Danjhop4 The yarn issue tracker is for issues with the yarn names, not modding problems. This is not the first time we have had to close these issues.


magic-numbers rule

I added it, but it's disabled for now : https://github.com/SimpliField/eslint-config-simplifield/commit/ec654d3fcd76c611d44699b124b065dfe8e092b3
It's possible to permit use of 0, 1, etc... for doing :
let last = myArray[myArray.length - 1];
let first = myArray[0];

What's your opinion about this rule ?

Il y a l'option ignoreArrayIndexes qui peut être cool \o/

Agree on { "ignoreArrayIndexes": true }


Handle default platform settings while syncing

The setting window.nativeTabs is macOS specific and enables macOS Sierra window tabs. Since the setting is macOS specific it should not be synched to Windows where this setting is unknown:

this can be known from configuration metadata, but this is not accessible in shared process where sync happens.

@sandy081, The comment is regarding default settings and not default platform settings.
while trying new settings I try few options and eventually come back to the default value for the setting. however, instead of removing the setting config I just set it to default value resulting in a long settings.json (just a stupid habit). With setting sync where syncing large settings.json can lead to unnecessary conflicts/delays, is it possible to ignore/remove such default settings while syncing?
(this could be already considered, however, if not could be worth some attention)

@sanket-bhalerao This is not about default setting. window.nativeTabs is a core (builtin) setting that is available only on Mac. It does not makes sense syncing this to a window machine.
Regarding your issue about syncing settings with default values, they are not ignored as of now. I don't see value but can be thought about if needed.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


map disappears on mobile

When on mobile, I can click on the second tab and see the map with markers, but when I switch back to the first tab, scroll up and down and then click on the second tab again the leaflet markers have disappeared and the map shows only partially.
(no such problems when on computer)

to do: add reactive event that renders leaflet after click on second tab

Solved the issue by adding an observeEvent. The leaflet map now renders when switching to the second tab


closurecompiler: 20180910 -> 20181008

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/closure-compiler/versions.
meta.description for closurecompiler is: '"A tool for making JavaScript download and run faster"'.

Checks done (click to expand)

built on NixOS
/nix/store/ws17z58144iibnly0ijbh4h83wsld60h-closure-compiler-20181008/bin/closure-compiler passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 20181008 with grep in /nix/store/ws17z58144iibnly0ijbh4h83wsld60h-closure-compiler-20181008
directory tree listing: https://gist.github.com/471f62518c09393a088ac950ea1c24aa
du listing: https://gist.github.com/eb9f46202c4e386f32c0671a7449a44e

Rebuild report (click to expand)

50 total rebuild path(s)
17 package rebuild(s)
17 x86_64-linux rebuild(s)
15 i686-linux rebuild(s)
3 x86_64-darwin rebuild(s)
15 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
closurecompiler
emscripten
faust
faust2
faust2alqt
faust2alsa
faust2csound
faust2firefox
faust2jack
faust2jaqt
faust2ladspa
faust2lv2
faustlive
foo-yc20
meguca
purePackages.faust
tambura

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ws17z58144iibnly0ijbh4h83wsld60h-closure-compiler-20181008 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A closurecompiler https://github.com/r-ryantm/nixpkgs/archive/996d07d1ac7a0889f930c9516c32e7d370534a81.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ws17z58144iibnly0ijbh4h83wsld60h-closure-compiler-20181008
ls -la /nix/store/ws17z58144iibnly0ijbh4h83wsld60h-closure-compiler-20181008/bin

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: closurecompiler
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: closurecompiler
Partial log (click to expand)
building
no Makefile, doing nothing
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/dgwf9vlagc8vybcip5xnn39fsx8cg471-closure-compiler-20181008
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/dgwf9vlagc8vybcip5xnn39fsx8cg471-closure-compiler-20181008/bin
patching script interpreter paths in /nix/store/dgwf9vlagc8vybcip5xnn39fsx8cg471-closure-compiler-20181008
checking for references to /build in /nix/store/dgwf9vlagc8vybcip5xnn39fsx8cg471-closure-compiler-20181008...
/nix/store/dgwf9vlagc8vybcip5xnn39fsx8cg471-closure-compiler-20181008

Success on x86_64-darwin (full log)
Attempted: closurecompiler
Partial log (click to expand)
configuring
no configure script, doing nothing
building
no Makefile, doing nothing
installing
post-installation fixup
strip is /nix/store/g5r4apl0za012ffs6ladinwa5w0m1l3k-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/5f5vwzlcslk32k9kgb7r7f1hqlbc25yn-closure-compiler-20181008/bin
patching script interpreter paths in /nix/store/5f5vwzlcslk32k9kgb7r7f1hqlbc25yn-closure-compiler-20181008
/nix/store/5f5vwzlcslk32k9kgb7r7f1hqlbc25yn-closure-compiler-20181008

@GrahamcOfBorg build emscripten

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: emscripten
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.


SPIKE: Validation not compatible with adding blocks inline in 4.0

Overview
Given the investigation required, we'll be spiking the effort and implementation detail required in introducing standard SilverStripe validation with inline-editable blocks.
The following issue gives the best detail: https://github.com/dnadesign/silverstripe-elemental/issues/584
Notes

Given validation isn't possible at the moment, on introducing it, we should consider a release note or documentation update to make it clear to developers that this is something that can be implemented.

I've fixed the original bug in #584, and a JavaScript error that happens when you haven't loaded any inline editable element forms yet and try to save the page - cannot convert undefined or null to object.
The state of play now (using the example code from #584) is:

If you open an element edit form and save the page, you get an error at the top of the page. It should really be targeting the elements that have the error instead:

If you haven't opened any element edit forms yet, and you save the page, it will save successfully. This is because it doesn't write any element information so it doesn't call its validator. I'm in two minds about this but I think it's correct behaviour, particularly for performance reasons.
If you open an element edit form and save the element itself, you get a toast message saying there was an error. Ideally this would tell you the validation error if there was one.

I guess the ideal situation is that the field itself shows the error rather than it being a toast message, e.g. something like this:

This would require some adjustment to the ElementalAreaController to return the errors and identify which fields they apply to, and to the SaveAction to propagate those errors back into the Redux state in a way that the element editor form can detect and update to show them. We could then do away with the toast message when there's an error, leaving the success toast message when it saves successfully.
Thoughts @silverstripe/creative-commoners?

I've tested the same patterns in asset admin:

addError($message) doesn't work - issue raised at https://github.com/silverstripe/silverstripe-asset-admin/issues/967
addFieldError($fieldName, $message) works - the field identifies its error correctly

In Elemental we "namespace" the element field names, so it might be a little tricky to support addFieldError() but I'll have a snoop and see what happens.

What I've done

Refactor the controller to use an MFA style jsonResponse() method, and provide validation error messages in responses
Refactor the SaveAction to use fetch() rather than the backend fetcher from admin

What I get

Inline editing validation errors now show in a toast message

Saving the page with an inline edit form open targets the validation error at the page's fields rather than the element (because of the form namespacing we add)

Saving the page without an inline edit form open does not show any element related validation errors, because their forms were never loaded. The save request succeeds (see below).

Ways to save content

Via the page, without any edit forms open
Via the page, with at least one edit form open
Via the element's edit form

Things to consider

If you save the page, the inline edit form is going to be closed again. If there's a validation error inside it then how do we handle that? Do we show a validation error indicator on the element title? Do we automatically expand the element forms that have errors so that they can have inline validation errors shown? When you save at the page level it doesn't have a relevant form to target the errors at yet so the information won't be immediately surfaced. This might need PUX/designs.
We want the API developers use for this to be straight forward, as in the example issue above. This would probably mean some logic in BaseElement to add namespacing to validation field errors so they don't need to concern themselves with the namespace for each form.
When saving an element inline, the error should be pushed into redux so it can show as an inline form validation error - I haven't investigated doing this yet, but it shouldn't be too much work.
When saving a page without having opened any element edit forms yet, there are no validation errors, because none of the forms with validators attached have been loaded yet. This means that the page can be saved successfully, which might be a little misleading for content authors given that the content in their page hasn't been validated at all yet. I can think of two options to work around this:

We load all element forms when you load the page (performance hit)
We manually call validate() on every element on the page when a page is being saved to ensure they're valid, and if not we attach the appropriate validation error to each form and auto-load them when the page loads (as mentioned above)

When using $validator->addFieldError('Title', 'Title is required') I'd expect it to be shown as an inline form field error state on the relevant elements (there could be multiple).

    public function validate()
    {
        $validator = parent::validate();
        if ($this->isInDB() && empty($this->Title)) {
            $validator->addFieldError('Title', 'Title is required');
        }
        return $validator;
    }

When using $validator->addError('You missed something in the element, but I don\'t have a specific field to point you at') then I'd expect the error to show on the relevant element(s) edit form. As above, this won't be expanded by default if you save at the page level, so we may need to auto-expand them on page save when errors occur.

    public function validate()
    {
        $validator = parent::validate();
        if ($this->isInDB() && empty($this->Title)) {
            $validator->addError('A non-field specific error occurred during validation');
        }
        return $validator;
    }

Is this enough to go on for the spike @brynwhyman?
I've pushed my WIP to pulls/4.1/validation-refactor for reference.

If you save the page, the inline edit form is going to be closed again. If there's a validation error inside it then how do we handle that? Do we show a validation error indicator on the element title? Do we automatically expand the element forms that have errors so that they can have inline validation errors shown? When you save at the page level it doesn't have a relevant form to target the errors at yet so the information won't be immediately surfaced. This might need PUX/designs.

Yeah I can imagine we'll need to have some validation payload to put into redux so the form can know about it when it's mounted. It looks like components like fieldHolder have some validation state logic in them. Marking a block as unsaved is already designed for but it definitely would need something to indicate it's unsaved due to validation.

When saving an element inline, the error should be pushed into redux so it can show as an inline form validation error - I haven't investigated doing this yet, but it shouldn't be too much work.

Yeah hopefully if we write something server-side to generate something to put into redux then we can share this with the page-level saving.

When saving a page without having opened any element edit forms yet, there are no validation errors, because none of the forms with validators attached have been loaded yet. This means that the page can be saved successfully, which might be a little misleading for content authors given that the content in their page hasn't been validated at all yet. I can think of two options to work around this:

We load all element forms when you load the page (performance hit)
We manually call validate() on every element on the page when a page is being saved to ensure they're valid, and if not we attach the appropriate validation error to each form and auto-load them when the page loads (as mentioned above)

Option 3; we don't bother. We don't attempt to save any blocks that haven't been opened when you do a page level save so the validation shouldn't trigger? If a block has become invalid without a content author editing it then that's just general $model->validate() weirdness that we don't have to support?

When using $validator->addFieldError('Title', 'Title is required') I'd expect it to be shown as an inline form field error state on the relevant elements (there could be multiple).

    public function validate()
    {
        $validator = parent::validate();
        if ($this->isInDB() && empty($this->Title)) {
            $validator->addFieldError('Title', 'Title is required');
        }
        return $validator;
    }

Agreed. I guess that there's some way this should work with FormBuilder but doesn't yet?

When using $validator->addError('You missed something in the element, but I don\'t have a specific field to point you at') then I'd expect the error to show on the relevant element(s) edit form. As above, this won't be expanded by default if you save at the page level, so we may need to auto-expand them on page save when errors occur.

    public function validate()
    {
        $validator = parent::validate();
        if ($this->isInDB() && empty($this->Title)) {
            $validator->addError('A non-field specific error occurred during validation');
        }
        return $validator;
    }

Perhaps this is also something that PUX can weigh in on
I'm a little worried about validation needing to show on blocks that aren't expanded. I think that means we'll have to loop the blocks and run ->validate() on all of them to gather some detail about errors they may have? Preferably we'd only do this when generating a response for a page save.
Great investigation though, this is probably enough to go on. I see that we'll probably need to:

Figure out some way to map that state to FormBuilder so that we can get field level errors showing where relevant
Include some component to show element level errors on the in-line forms
Get some designs from pux for invalid blocks in their collapsed state

Then we just need to figure out how to get validation responses to the client-side. Here is a crazy idea that I've just hatched after chatting with @unclecheese: Toss validation errors from a page level save into data-schema and use it when rendering the list of blocks again.
Currently we're stuck in a weird half-way case (again) where we're partially using REST/pjax and GraphQL. It makes sense to return validation responses with mutations, but not so much with queries. We can do some magic though where we can add validation errors to "schema data" on the ElementalAreaField when saving, and after passing that detail through to the props of the ElementalEditor component we can tag blocks as invalid.
Hopefully individual block saves aren't so painful here.

One approach to fixing hidden validation errors is to open any blocks with errors so they can be seen. We could apply an additional style to highlight those blocks (e.g. red border on left) if we want to keep them closed—design would be required) for this.

I've raised an issue to do the work outlined in this issue:
#699

One approach to fixing hidden validation errors is to open any blocks with errors so they can be seen. We could apply an additional style to highlight those blocks (e.g. red border on left) if we want to keep them closed—design would be required) for this.

Yeah - the only concern about that is performance - when you open a block you have to request the form from the server. Doing that for ~5 blocks would be slow and annoying.


[Exporters-gcc_arm] Clean up the source directory

All objects are now put into a directory named bin

I have to ask again, is this tested on windows ? :disappointed:  Because I get this:
'[' is not recognized as an internal or external command,
operable program or batch file.
mbed/.build/export/MBED_10/Makefile:70: warning: overriding commands for target `.s.o'
mbed/.build/export/MBED_10/Makefile:67: warning: ignoring old commands for target `.s.o'
'[' is not recognized as an internal or external command,
operable program or batch file.

It seems to be the same mkdir problem as discussed in PR #1769

@0xc0170 Yes @ohagendorf I'm working on it. MKDIR <directory-here> works like mkdir -p <directory-here> right?

I think yes. Here is (my translation) the help text:
MKDIR creates, when necessary, each folder. When e.g. folder \a doesn't exist, then corresponds
mkdir \a\b\c\d

the following command sequence:
mkdir \a
chdir \a
mkdir b
chdir b
mkdir c
chdir c
mkdir d

Thanks! I'll push another commit that changes the mkdir behavior.

That should do it.

No, it doesn't work.
You can't create the same folder a second time.

Oh, this is going to be fun. I need the [ -d ... ] || bash-ism on windows without bash.

That's a bad solution. I'm looking into how to actually solve the problem.

Under Windows this is working:
ifeq ($(OS),Windows_NT)
	MAKEDIR1 = mkdir
	MAKEDIR2 = 2>:null || true
else
	MAKEDIR1 = mkdir -p
	MAKEDIR2 =
endif

and then everytime you are using MAKEDIR
@$(MAKEDIR1) $@ $(MAKEDIR2)

I'm sure also for Linux this should be OK.
Maybe it is not the best solution but my make knowledge is not very wide, I'm very sorry.

Wow, that is a very different solution.

Maybe a better solution without ignoring execution result:
ifeq ($(OS),Windows_NT)
	MAKEDIR = if not exist "$(1)" mkdir "$(1)"
	RM = rmdir /S /Q
else
	MAKEDIR = mkdir -p $(1)
	RM = rm -rf
endif

And then calling:
+$(call MAKEDIR,$@)

or
$(call MAKEDIR,$(dir $@))

the rm command doesn't exist under Windows either. That's why a:
clean :
	$(RM) $(OBJDIR)

with the above RM definition would be better (or something similar).

Oh, I didn't see that you've already found a very similar solution.
But maybe you can add the RM definition.

I'm very sorry but your version doesn't work :(

switching to your implementation.

(workspace) C:\Users\samgro01\Desktop\MBED_BUSOUT>make all
/usr/bin/bash: -c: line 1: syntax error: unexpected end of file
make: [.build] Error 1 (ignored)
make: *** .build: No such file or directory.  Stop.
make: *** [.build] Error 2

Seems to error trying to create .build directory on windows

I report this here, as this one should wait until we fix make gcc for windows. The current master is broken for windows for gcc_arm makefiles, please @theotherjimmy fix it or we will revert it to the latest working version within the next 2 days. I have just tested the latest master

Not the .build is the problem. There are several spaces in the function calls. Please see exactly my example above:
+$(call MAKEDIR,$@)

no space before $@
Why did you use the - before the commands? They should be excuted successfully.

I just checked:
project.py -m NUCLEO_F446RE -i gcc_arm -p 28

unzipping and calling
make all

and it was successfull.
But it would be nice to get back the old functionality to just call:
make

That's great news! What output does make give you? Reading through the makefile, I expect make and make all to do the same thing (all is the first target in the makefile and make always builds the first target when called with no arguments).

I removed the commit that replaced things with hyphens. We no longer need it.

Tested on MBED_10 and RTOS_1, working . I used make.
arm-none-eabi-size  MBED_10.elf
   text    data     bss     dec     hex filename
  40924    2256     396   43576    aa38 MBED_10.elf

make --version
GNU Make 3.81

One note, that the text size seems to be bigger than usual (might be my wrong impression), not related to this fix, we shall check if there were changes in the last weeks.

LGTM

@0xc0170 agreed, LGTM.


How to forward a location to another location?

iOS uses a different link for webDAV then what the Nextcloud system uses, therefore requiring this bit of code if one is to configure nginx manually:
    location ^~ /.well-known {
        # The rules in this block are an adaptation of the rules
        # in `.htaccess` that concern `/.well-known`.

        location = /.well-known/carddav { return 301 /remote.php/dav/; }
        location = /.well-known/caldav  { return 301 /remote.php/dav/; }

        location /.well-known/acme-challenge    { try_files $uri $uri/ =404; }
        location /.well-known/pki-validation    { try_files $uri $uri/ =404; }

Therefore I want to know hot should I set these rules manually in the npm UI. Thank you!

This is what you need to put down, just redirect to the same Forward destination as the details page.

Just wanted to say thanks for posting this here! Saved me a big headache on my personal server.
got here from the nextcloud forms where a helpful user posted his journey.
https://help.nextcloud.com/t/cannot-connect-ios-carddav-caldav-to-nextcloud/140046/3

Hey I made a mistake an used the line "return 301 $scheme://$host/remote.php/dav;" in Advanced tab in Nginx docker. Now the site forwards directly to the remote.php/dav. Can I set this back to the original config, what do I need to write in Advanced tab? Deleting and making a new Forwarding does not help.


Db rework

https://trello.com/c/GvMczKDl
This ticket is to make the DB structure more flexible for publishers and consumers.  Each have subscriptions to pub or consume.
The types of events are explicit in the db
The dataset (or structures) are also defined
Removed the FTP part and just as a hook where we could send to S3 or POST to an endpoint.

Couple of minor comments, the thought I'd like to flesh out is around whether this ties us to having the same input and output event types - I wonder if we should be decoupling them, so there's an explicit "we're generating this event data" rather than tying us to any upstream source.


Feautre request: reduce 'googleapis' module size

On a recent project I was using the googleapis module to access the YouTube api. When attempting to reduce the size of my docker container, I realised nearly 30MB was being consumed by the 'googleapis' module.
It would be a good idea to break this up into multiple packages, shared logic in a core package that other packages depend on and individual packages for specific API groups.

Can't agree more. Noticed the package contains all the typescript files, map files and compiled js files. Adding a .npm_ignore file to remove all the *.ts and *.map files should substantially reduce this.

When we get here, this will likely be done by providing individual npm modules for each target API.  Shipping the *.d.ts and .js.map files is very much by design.  These ensure the module works with TypeScript and really don't add substantial overhead.  FWIW - we do limit what gets bundled into the end module:
https://github.com/google/google-api-nodejs-client/blob/master/package.json#L16

I've just removed all the ts and map files and it's not unsubstantial. The package size goes from 40mb to 21mb. Shame there is no way to have a js / ts version. It's still my biggest npm dependency by a long way.
Individual npm modules would also be good.
Thanks for the update!

Fair point :) Going to track this over in #806!


Parsers for meetings

Progress:
MeetParser, MeetCommand
Update Parser, UpdateCommand
CancelParser, CancelCommand
ReadOnlyMeetingBook, MeetingBook

Codecov Report

Merging #118 (e08ea6b) into master (b808066) will decrease coverage by 6.84%.
The diff coverage is 2.01%.

@@             Coverage Diff              @@
##             master     #118      +/-   ##
============================================
- Coverage     57.55%   50.70%   -6.85%
  Complexity      561      561
============================================
  Files           101      111      +10
  Lines          2111     2404     +293
  Branches        258      290      +32
============================================
+ Hits           1215     1219       +4
- Misses          821     1110     +289
  Partials         75       75

Impacted Files
Coverage Δ

...main/java/seedu/address/commons/core/Messages.java
0.00% <ø> (ø)

.../address/logic/commands/meeting/CancelCommand.java
0.00% <0.00%> (ø)

...du/address/logic/commands/meeting/MeetCommand.java
0.00% <0.00%> (ø)

.../address/logic/commands/meeting/UpdateCommand.java
0.00% <0.00%> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
73.33% <0.00%> (-21.30%)
:arrow_down:

...ress/logic/parser/meeting/CancelCommandParser.java
0.00% <0.00%> (ø)

...ddress/logic/parser/meeting/MeetCommandParser.java
0.00% <0.00%> (ø)

...ress/logic/parser/meeting/UpdateCommandParser.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/model/MeetingBook.java
0.00% <0.00%> (ø)

...u/address/model/meeting/EditMeetingDescriptor.java
0.00% <0.00%> (ø)

... and 9 more

Continue to review full report at Codecov.

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

When a clear command happens, all meetings should clear as well.
Define an empty command to clear only meetings


Tests are broken.

MONITORED_ERC721 is missing from test/application.properties.
PRIVATE_KEY value has wrong value which results in NumberFormatException

MONITORED_ERC721 added in 979bd9b25cd73eec58151f31372c9816a55f11c2
PRIVATE_KEY will not be added from security reasons