Example notebook 304: Missing dependencies

Summary
The following dependency errors have been observed in Quick Start Tutorial (Start here to Deploy) hosted in the following address:

https://aimodelshare.readthedocs.io/en/latest/example_notebooks.html

[ ] Missing dependencies:

regex
pydot
xgboost
networkx
importlib_resources

[ ] Environment conducting the tests:

Conda with Python 3.9

conda create -n modelshare python=3.9

Problem 1
Running the following code block
# Set credentials
from aimodelshare.aws import set_credentials
set_credentials(credential_file="credentials.txt", type="deploy_model")

raises the following error
File .../aimodelshare/modeluser.py:10
      8 import time
      9 import datetime
---> 10 import regex as re
     11 from aimodelshare.exceptions import AuthorizationError, AWSAccessError, AWSUploadError
     13 def get_jwt_token(username, password):

ModuleNotFoundError: No module named 'regex'

Solution 1
Add the regex package to the list of dependencies when the first code block in the notebook
(see below) is supposed to run
#install aimodelshare library
!  pip install aimodelshare --upgrade

Problem 2
Running the following code block after fixing Problem 1,
# Set credentials
from aimodelshare.aws import set_credentials
set_credentials(credential_file="credentials.txt", type="deploy_model")

raises the following error
File .../aimodelshare/tools.py:2
      1 import json
...
----> 2 import pydot
      3 import argparse
      4 import datetime

ModuleNotFoundError: No module named 'pydot'

Solution 2
Add the pydot package to the list of dependencies when the first code block in the notebook is supposed to run (see Solution 1).
Problem 3
Running the following code block
# Save sklearn model to local ONNX file
from aimodelshare.aimsonnx import model_to_onnx

# Check how many preprocessed input features there are
from skl2onnx.common.data_types import FloatTensorType

feature_count=preprocessor(X_test).shape[1]
initial_type = [('float_input', FloatTensorType([None, feature_count]))]  # You need to insert correct number of preprocessed features

onnx_model = model_to_onnx(model, framework='sklearn',
                          initial_types=initial_type,
                          transfer_learning=False,deep_learning=False)

with open("model.onnx", "wb") as f:
    f.write(onnx_model.SerializeToString())

raises the following error
ModuleNotFoundError                       Traceback (most recent call last)
Cell In [12], line 2
      1 # Save sklearn model to local ONNX file
----> 2 from aimodelshare.aimsonnx import model_to_onnx
      4 # Check how many preprocessed input features there are
      5 from skl2onnx.common.data_types import FloatTensorType

File .../aimodelshare/aimsonnx.py:9
      7 from sklearn.model_selection import GridSearchCV, RandomizedSearchCV
      8 import torch
----> 9 import xgboost
     10 import tensorflow as tf
     11 import keras

ModuleNotFoundError: No module named 'xgboost'

Solution 3
Add the xgboost package to the list of dependencies when the first code block in the notebook is supposed to run (see Solution 1).

[ ] Tip: In this case, installing (the GPU version of the) XGBoost from conda-forge, as suggested by the XGBoost's documentation resolved the issue

   conda install -c conda-forge py-xgboost-gpu

Problem 4
Running the following code block
# Save sklearn model to local ONNX file
from aimodelshare.aimsonnx import model_to_onnx

# Check how many preprocessed input features there are
from skl2onnx.common.data_types import FloatTensorType

feature_count=preprocessor(X_test).shape[1]
initial_type = [('float_input', FloatTensorType([None, feature_count]))]  # You need to insert correct number of preprocessed features

onnx_model = model_to_onnx(model, framework='sklearn',
                          initial_types=initial_type,
                          transfer_learning=False,deep_learning=False)

with open("model.onnx", "wb") as f:
    f.write(onnx_model.SerializeToString())

after fixing Problem 3, raises the following error
ModuleNotFoundError                       Traceback (most recent call last)
Cell In [12], line 2
      1 # Save sklearn model to local ONNX file
----> 2 from aimodelshare.aimsonnx import model_to_onnx
      4 # Check how many preprocessed input features there are
      5 from skl2onnx.common.data_types import FloatTensorType

File .../aimodelshare/aimsonnx.py:46
     44 from IPython.core.display import display, HTML, SVG
     45 import absl.logging
---> 46 import networkx as nx
     47 import warnings
     48 from pathlib import Path

ModuleNotFoundError: No module named 'networkx'

Solution 4
Add the networkx package to the list of dependencies when the first code block in the notebook is supposed to run (see Solution 1).
Problem 5
Running the following code block
# Save sklearn model to local ONNX file
from aimodelshare.aimsonnx import model_to_onnx

# Check how many preprocessed input features there are
from skl2onnx.common.data_types import FloatTensorType

feature_count=preprocessor(X_test).shape[1]
initial_type = [('float_input', FloatTensorType([None, feature_count]))]  # You need to insert correct number of preprocessed features

onnx_model = model_to_onnx(model, framework='sklearn',
                          initial_types=initial_type,
                          transfer_learning=False,deep_learning=False)

with open("model.onnx", "wb") as f:
    f.write(onnx_model.SerializeToString())

after fixing Problem 4, raises the following error
ModuleNotFoundError: No module named 'importlib_resources'

Solution 5
Add the importlib_resources package to the list of dependencies when the first code block in the notebook is supposed to run (see Solution 1).

YAML file for reproducing the adopted conda environment.
environment.zip

@SinaMostafanejad Thanks for the heads up on these errors.  We're working on them this week and plan to have a fixed conda version deployed by next Friday.


Support for external infrastructure clusters

Today kubevirt provider can only create tenant cluster VMs on the same cluster where CAPI/CAPK management plane is running, in other words, infrastructure cluster is the same as the management cluster.
As and admin, I want to be able to use one Kubernetes cluster to run the CAPI/CAPK management plane and another cluster (or multiple clusters) to run tenant clusters, meaning that in the long run we will want to split up the management cluster from infrastructure cluster.
Expectations:

Admins can add a secret to the management cluster, containing kubeconfig for an external cluster.
Template will contain a reference to the secret.
Underlying infrastructure (VMs) for tenant clusters will be created in that external cluster.

/assign @agradouski
I'm actively working on this. I should have something published in the next few days.


Build Mxnet C++ failed with "nvcc fatal   : Unsupported gpu architecture 'compute_92'"

Hi
I want build mxnet c++ from source with GPU 1060 6g and cuda9.2 on Win10， but report:
Building NVCC (Device) object CMakeFiles/cuda_compile_1.dir/src/common/Release/cuda_compile_1_generated_random_generator.cu.obj
nvcc fatal   : Unsupported gpu architecture 'compute_92'
CMake Error at cuda_compile_1_generated_random_generator.cu.obj.Release.cmake:222 (message):
Error generating
D:/study/mxnet_build/incubator-mxnet/build/CMakeFiles/cuda_compile_1.dir/src/common/Release/cuda_compile_1_generated_random_generator.cu.o
I think it's cuda version not matched  with GPU arch in CMakeFiles. How can I solve this issue? Thank you!

Hi,
Did you make changes the codebase before building ?

@zhizec ^

@zhizec I followed the instructions to build MXNet and I did not face the error.
http://mxnet.incubator.apache.org/versions/master/install/windows_setup.html
Can you try following the steps for Build from Source on this page ?

GPU 1060 6g -> compute_61,sm_61


Switch HTTP clients

The Jersey client is rather bulky to use; Unirest looks much better.

Resolved by 2ca3a87f62dca6199898ed47c3b20e4fb6cf24b8


[Fix] chaines-tv.orange.fr

Change priority in item title, leading in the test being fixed.
Also add season & episode data when available.
Closes #2395

Another possibility is to get the series' name and the episode's title. Thus, the test would need to be edited.
Instead of "Tête de liste", per the test's expected result, we would get "Esprits criminels - Tête de liste".
(this might lead to an EPG that's clearer to understand)

I've allowed myself to add some additional content that could be useful in the EPG. Feel free to check now.

> npm install

channels.json      [====================================] 100.00% | ETA: 0s | 1.7 MB | 1.9 MB/s
countries.json     [====================================] 100.00% | ETA: 0s | 4.3 KB | N/A
regions.json       [====================================] 100.00% | ETA: 0s | 2.2 KB | N/A
subdivisions.json  [====================================] 100.00% | ETA: 0s | 36.6 KB | N/A

added 56 packages, removed 97 packages, changed 56 packages, and audited 755 packages in 42s
> npx tsx scripts/commands/api/load.ts
116 packages are looking for funding
  run `npm fund` for details

7 vulnerabilities (1 moderate, 5 high, 1 critical)

To address issues that do not require attention, run:
  npm audit fix

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

>npm test --- chaines-tv.orange.fr

> test
> run-script-os chaines-tv.orange.fr

> test:win32
> SET "TZ=Pacific/Nauru" && npx jest --runInBand chaines-tv.orange.fr

 FAIL  sites/chaines-tv.orange.fr/chaines-tv.orange.fr.test.js (9.912 s)
  √ can generate valid url (13 ms)
  × can parse response (34 ms)
  √ can handle empty guide (1 ms)

  ● can parse response

    expect(received).toMatchObject(expected)

    - Expected  - 1
    + Received  + 1

    @@ -3,8 +3,8 @@
          "category": "Série Suspense",
          "description": "Un tueur en série prend un plaisir pervers à prévenir les autorités de Tallahassee avant chaque nouveau meurtre. Rossi apprend le décès d'un de ses vieux amis.",
          "image": "https://proxymedia.woopic.com/340/p/169_EMI_9697669.jpg",
          "start": "2021-11-07T23:35:00.000Z",
          "stop": "2021-11-08T00:20:00.000Z",
    -     "title": "Tête de liste",
    +     "title": "Esprits criminels",
        },
      ]

      23 | it('can parse response', () => {
      24 |   const result = parser({ date, channel, content })
    > 25 |   expect(result).toMatchObject([
         |                  ^
      26 |     {
      27 |       start: '2021-11-07T23:35:00.000Z',
      28 |       stop: '2021-11-08T00:20:00.000Z',

      at Object.<anonymous> (sites/chaines-tv.orange.fr/chaines-tv.orange.fr.test.js:25:18)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 2 passed, 3 total
Snapshots:   0 total
Time:        10.581 s, estimated 12 s
Ran all test suites matching /chaines-tv.orange.fr/i.

The test being in error is the test i've fixed... rather odd.


Usage in another repository

@mximp I started this test in another repository and it failed:
+alias org.eolang.hamcrest.assert-that
+architect<EMAIL_ADDRESS>+home https://github.com/objectionary/eo
+junit
+package org.eolang.threads
+version 0.0.0

[] > get-time-of-day
  gt. > @
    QQ.sys.call
      "gettimeofday"
    0

and get
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.012 s <<< FAILURE! - in EOorg.EOeolang.EOthreads.EOget_time_of_day_testTest
[ERROR] EOorg.EOeolang.EOthreads.EOget_time_of_day_testTest.testWorks  Time elapsed: 0.006 s  <<< ERROR!
org.eolang.ExFailure: Can't #copy() package object 'org.eolang.sys.call'
        at org.eolang.PhPackage.copy(PhPackage.java:108)

Is it possible to use it now in foreign repository?

@mximp I change QQ.sys.call to QQ.qwerty.call and got similar error:
[INFO] Running EOorg.EOeolang.EOthreads.EOget_time_of_dayTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.01 s <<< FAILURE! - in EOorg.EOeolang.EOthreads.EOget_time_of_dayTest
[ERROR] EOorg.EOeolang.EOthreads.EOget_time_of_dayTest.testWorks  Time elapsed: 0.004 s  <<< ERROR!
org.eolang.ExFailure: Can't #copy() package object 'org.eolang.qwerty.call'

It seems it just does not know QQ.sys package. May be smth wrong with pom.xml in eo repository?

@levBagryansky can you please add alias:
+alias org.eolang.sys.call

@mximp I runned this test in eo repository:
[] > get-time-of-day
  gt. > @
    call
      "gettimeofday"
    0

with metas
+alias org.eolang.sys.call
+alias org.eolang.collections.list
+alias org.eolang.hamcrest.assert-that
+architect<EMAIL_ADDRESS>+home https://github.com/objectionary/eo
+junit
+package org.eolang
+version 0.0.0

and got
[ERROR] Failed to execute goal org.eolang:eo-maven-plugin:1.0-SNAPSHOT:assemble (test-compile) on project eo-runtime: Execution test-compile of goal org.eolang:eo-maven-plugin:1.0-SNAPSHOT:assemble failed: org.apache.maven.plugin.MojoFailureException: Failed to execute org.eolang.maven.PullMojo: Failed while trying to save to ./target/eo-test/04-pull/org/eolang/sys/call.eo: https://raw.githubusercontent.com/objectionary/home/00b60c7b2112cbad4e37ba96b162469a0e75f6df/objects/org/eolang/sys/call.eo -> [Help 1]
[ERROR]

@levBagryansky looks like org.eolang.sys objects are not in Objectionary yet.
@yegor256 can we release it?

@mximp I can't, I'm waiting for https://github.com/objectionary/eo/issues/1010

@yegor256 got it.
@levBagryansky So we are blocked here for now

@yegor256 are we able to release current eo-sys version into Objectionary?

@levBagryansky @mximp it's released to objectionary


pkg_resources.DefaultProvider breaks on unreadable files

DefaultProvider._has only checks that a file exists, and DefaultProvider._get reads it without catching permission issues, so if there's an unreadable file stuff will break.  The particular case I'm looking at is reading a PKG-INFO file on some scan on import, but I think it's a general issue.
One simple solution is to use os.access in _has.  In theory we should catch exceptions either in _get or its callers, but since this isnt something that typically races we can probably just change _has and call it a day.

On second thought, I don't know what else calls those methods, so maybe it's safer to leave that behavior intact and catch the exception further up the chain.
The place where I'm seeing this is on pkg_resources import.  It looks like on import, it it crawls site-packages and loads versions (via find_distributions).  Currently one bad package anywhere in site-packages causes pkg_resources to break entirely on import, and this in turn breaks packages that import pkg_resources, effectively coupling totally unrelated packages.
Steps to reproduce:

Find a package that's oddly packaged and has world-unreadable files.  One example offender is progressbar.  The PKG-INFO in the tarball isnt readable to the world.  Download/extract the tarball.
python setup.py install --root /  This is part of a larger builder, so take the --root / as a given.  I do this with a virtualenv, but I'm guessing it applies to system-wide installations too.
The PKG-INFO in site-packages/progressbar-2.3-py2.7.egg-info will be unreadable to others
python -c 'import pkg_resources'

For more fun, install pytz and try to import pytz.  Now pytz is broken simply because it imports pkg_resources, even though the issue is in a totally unrelated progressbar package.  I should add that progressbar still works, it's just the metadata that's broken.
I think what we want is for find_distributions to skip over packages with problems (with a warning so it's not silent).  It would also be better not to do all this work on import and instead do it when it's needed, because typically people only handle ImportErrors on import.  What do you guys think?

I suspect the reason nobody has reported this before is because multi-user Python environments are rare (and also packages with restrictive permissions are rare).

I think what we want is for find_distributions to skip over packages with problems (with a warning so it's not silent).

I'm not so sure. Fail fast is often a good strategy. What if one of the packages skipped is important - then it just pushes the error down the road. At least now the error is reported where the error occurs. It might be worthwhile suppressing the error and replacing it with a warning. The question is - which errors should we replace? Just access errors?
Also, I worry that by suppressing the error we're masking a more important problem - that the permissions defined in a package's tarball are applied to the installer's system. I suspect this issue wouldn't occur if instead you built the package into a zip distribution and then installed that. Perhaps better would be for the installers to enforce a consistent permission pattern when installing files.

It would also be better not to do all this work on import and instead do it when it's needed, because typically people only handle ImportErrors on import.

Agreed, behavior on import is generally a bad model. This is another fundamental issue and one that I'd prefer to solve, but I'm not sure what the compatibility implications are. I know of several use-cases that rely on import pkg_resources to ensure that the default working set is configured. Perhaps these can be

I agree that being noisy is preferable in general.  I misunderstood what it was doing on import: I thought it was some sort of preloading, in which case it should be failsafe until someone actually loads something is missing.  It looks like it's instead loading the data that is more or less final, so if that's the case, you're right, it should fail fast.
It was very counter-intuitive to have pytz and progressbar both working as expected, and upgrading setuptools broke pytz with a progressbar error despite being totally unrelated packages.  I'd like to do whatever we can to prevent unexpected coupling like that.
I think there's two issues leading to this unexpected behavior:

The import is doing nontrivial work that can raise all sorts of exceptions.  Looking at the pytz code, they are using pkg_resources.resource_stream to find an asset in pytz itself, and they want this to be a safe operation so they catch and handle ImportError.  They don't handle other exceptions---I think a very prevalent assumption is that imports only raise ImportErrors.
Whether or not this work happens on initialization, I also dont think that pkg_resources should crawl everything without being asked to.  Callers such as pytz are looking for something very specific, and pkg_resources doesn't need to probe everything in the universe to find it.  It should do something similar to the python import mechanism, which tries a bunch of candidate paths.

Sidenote: I should also file an issue to whoever does the setup.py install to normalize metadata permissions, so a bad tarball like the progressbar one wont install files with weird permissions.  Is that also setuptools code?

Is that also setuptools code?

Yes, in most if not all cases. Even when pip installs from a source dist, it builds using setuptools, so it's conceivable that if it's fixed in setuptools, it will be fixed in all cases. It's conceivable that a package built with distutils could have the same issue if someone manually downloads the tarball and setup.py installs it without setuptools being required or present. However, in this case, setuptools can still take responsibility for correcting for the issue.

An example of the kind of unintuitive problems this can cause: https://trac.macports.org/ticket/59477
Something unrelated to python failed to build because it happened to use the xattr utility which happens to be a python script, which failed to run because of one unreadable dist-info dir on the user's system (which was not even needed by xattr).

This problem continues to affect users: https://trac.macports.org/ticket/71054


[Card] Fix unknown props warnings

[x] PR is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

@vizath Thanks!


About errors in Tutorials - Adding an Org to a Channel

Problem Description
When I followed the tutorial in this chapter to perform the relevant operations, I had already executed the following command.
cd fabric-samples/test-network

./network.sh up createChannel -c channel1

cd addOrg3

../../bin/cryptogen generate --config=org3-crypto.yaml --output="../organizations"

export FABRIC_CFG_PATH=$PWD
../../bin/configtxgen -printOrg Org3MSP > ../organizations/peerOrganizations/org3.example.com/org3.json

When I executed the command docker-compose -f compose/compose-org3.yaml -f compose/docker/docker-compose-org3.yaml up -d , an error was reported. The error is as follows:
WARNING: The DOCKER_SOCK variable is not set. Defaulting to a blank string.
Creating volume "compose_peer0.org3.example.com" with default driver
WARNING: Found orphan containers (cli, orderer.example.com, peer0.org2.example.com, peer0.org1.example.com) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
Creating peer0.org3.example.com ... error

ERROR: for peer0.org3.example.com  Cannot create container for service peer0.org3.example.com: create .: volume name is too short, names should be at least two alphanumeric characters

ERROR: for peer0.org3.example.com  Cannot create container for service peer0.org3.example.com: create .: volume name is too short, names should be at least two alphanumeric characters
ERROR: Encountered errors while bringing up the project.

I don't know much about docker, I retrieved related information but didn't find a solution.

Maybe you can try that before execute the docker-compose command:
export DOCKER_SOCK="${DOCKER_HOST:-/var/run/docker.sock}"

Thank you very much, it works.

@Eternaldeath
The YML file for launching the test network node container contains a mapping ${DOCKER_SOCK}: /host/var/run/docker.sock. When starting the node container using the script of the test network,it will assign the DOCKER_SOCK , but if you manually start the node container using the Docker Compose command, the DOCKER SOCK is empty.


Only '/public' should be accessible

Usually, all of Wordpress theme PHP files check if ABSPATH exists. This theme template doesn't have such functionality. Moreover, I can access '/config' , '/resources', '/vendor' and so on. It might pose a security risk in the long run (just my opinion).
I believe only '/public' folder should be accessible by web server. In my case, I created '.htaccess' file in theme root that denies all access and created another '.htaccess' file in '/resources' that WebPack copies into '/public' folder with complete access. I think it's worth discussing implementing this in theme.

+1

maybe this can be added via a pull request @saulens22


Are the End Gateways also personal, or only the end island?

Are the End Gateways also personal, or only the end island?

Each player would get a completely separate end dimension, so individual main island, individual dragon fight, and yes, individual outer ends islands & cities


Handle pull_request events better

Right now, Cloudflare's default behaviors for pull_request events are kinda wonky. Because PR events are against a merged commit and this action assumes push events, it's reporting HEAD for the current branch and it also isn't reporting the correct commit to the GitHub Deployments API which results in deployments not showing up on their appropriate PR.
Willing to contribute fixes for both of these.

I'll be super interested for a fix on this. Is there a fork already ?


Display python extension error message into a modal dialog

Ensure users understand that Python Extension is required for running Python notebooks.
Turn this into a modal dialog box (turn it into a blocking action).

@claudiaregio /cc


Question: Add/Modify/Remove Groups to Resources

Hello!
I was wondering if there was a command to modify the groups on a resource? I see a command to add/remove groups, but not a command to tie it to a resource.

Sorry, currently there isn't. Currently I have no access to a Global Dashboard environment so it's kind of difficult to include it


New version: hrzlgnm.mdns-browser version 0.7.6

Pull request has been created with WinGet Releaser :rocket:
Microsoft Reviewers: Open in CodeFlow

I'm closing this, as several security vendors are flagging this version with a trojan:


DBZ-5011 Register MongoDB metrics with task id

https://issues.redhat.com/browse/DBZ-5011
When starting the MongoDB connector with more than one task, the connector fails to start the additional tasks due to the MBean registration failure due to clashing names.  This PR adds a task scope to each registered MBean to include the associated Kafka task identifier assignment for each running task.

Test failure is related to https://issues.redhat.com/browse/DBZ-4004.

@Bonndan can you share your connector setup on the associated Jira and let me take a look to see if there might be a gap in the SQL Server code as well.

Et voila. The files have been anonymized. Hope this is helpful.
my_connector2.json.txt
connect-distributed.properties.txt
my_connector1.json.txt

Hi @bonndan it would seem based on the connector configurations you're using the same value for database.server.name in both connectors, which is not a valid configuration.  The database.server.name must be unique across all connectors.

HI @Naros thank you very much!

@Naros Could you please also update the docs?

@Naros Applied, thanks!


Rename committed RangeIterator to UnmarshalIterator

Codecov Report

Merging #1131 (4406ad2) into master (542ae35) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1131      +/-   ##
==========================================
- Coverage   47.30%   47.28%   -0.02%
==========================================
  Files         185      185
  Lines       14464    14464
==========================================
- Hits         6842     6840       -2
- Misses       6724     6725       +1
- Partials      898      899       +1

Impacted Files
Coverage Δ

graveler/committed/iterator.go
71.73% <100.00%> (ø)

graveler/committed/unmarshal_iterator.go
68.00% <100.00%> (ø)

catalog/mvcc/cataloger_create_entry.go
94.73% <0.00%> (-5.27%)
:arrow_down:

catalog/mvcc/cataloger_create_repository.go
59.25% <0.00%> (-3.71%)
:arrow_down:

catalog/mvcc/cataloger_create_branch.go
84.61% <0.00%> (+3.07%)
: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 542ae35...4406ad2. Read the comment docs.

🙏

Thanks!


Limit the scope of the uri type change

Description
Previously we will change the schema type to Uri if the property's name ends with Uri. This works well when the property is a string. However, there are some edge cases that a property uses Uri as the name suffix but is defined as Object type. Considering that all the properties marked as Object type will share the same schema, this change will result in that all the properties' type is changed to Uri, which is unexpected and wrong.
Checklist
To ensure a quick review and merge, please ensure:

[ ] The PR has a understandable title and description explaining the why and what.
[ ] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[ ] The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

[ ] Build is completely green

Submissions with test failures require tracking issue and approval of a CODEOWNER

[ ] At least one +1 review by a CODEOWNER
[ ] All -1 reviews are confirmed resolved by the reviewer

Override/Marking reviews stale must be discussed with CODEOWNERS first

In this PR, we introduced a configuration format-by-name-rule to control the type change behavior, which means that the type of properties end with Uri suffix will not be changed to Uri type automatically, so just close this PR.


Add capstone dependency

The xAPIC emulation requires the VMM to map in and decode
the guest instruction to be emulated.

Add capstone to depends to support disassembling in the VMM

Signed-off-by: Connor Davis<EMAIL_ADDRESS>

Is this needed for the base hypervisor, or can it be added to the EAPIs because dependencies can be added to any repo

I dont mind putting it in the ext. apis, although I will need some help to get it building I think. This patch adds the two .a .so libs to the LD_FLAGS in the cmake macro, which probably is the Wrong Way, especially if they are moved the eapis

No longer needed


adds outputs

Description
Adds some outputs to the vpe module
https://github.com/terraform-ibm-modules/terraform-ibm-vpe-module/issues/313
Types of changes in this PR
Changes that affect the core Terraform module or submodules

[ ] Bug fix
[ ] New feature
[ ] Dependency update

Changes that don't affect the core Terraform module or submodules

[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other

Release required?
Identify the type of release. For information about the changes in a semantic versioning release, see Release versioning.

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
If a release is required, replace this text with information that users need to know about the release. Write the release notes to help users understand the changes, and include information about how to update from the previous version.
Your notes help the merger write the commit message for the PR that is published in the release notes for the module.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
Merge by using "Squash and merge".

@ocofaigh If it's ok please approve and merge.

:tada: This PR is included in version 2.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


isFetched is true before the query is fetched when using query cache

Describe the bug
In developing one my Expo React Native apps, I was relying on the statuses and boolean flags to try to determine when a fresh object was loaded (not from cache), and I noticed that the isFetched query boolean is true before the query ever enters a fetching status, but it appears to only happen when using QueryCache (which I'm using with @tanstack/query-async-storage-persister). See the log progression here:

In order, the progression is as follows:

App hasn't yet let RQ know about the online state (idle)

App is pinging the outside world to determine if the internet is reachable, so RQ thinks it's offline (paused)

RQ pulls from cache and starts fetching, but isFetched is true prematurely (isFetching is also true here)

Fetch is done (idle)

This seems very misleading to me and doesn't seem intentional. It also doesn't match up with the fetch statuses. Can someone speak to this?
I'm currently on 4.2.3
Your minimal, reproducible example
https://snack.expo.dev/@wecreatedev/usequery-bug
Steps to reproduce
I'm unable to reproduce this in Expo Snack for some reason, even with query cache.
Expected behavior
isFetched shouldn't be true until the query has finished fetching
How often does this bug happen?
No response
Screenshots or Videos
No response
Platform
React Native
react-query version
4.2.3
TypeScript version
4.8.2
Additional context
No response

so when the query is in:
status: success, isFetched: true, fetchStatus: fetching
(line 7 in your screenshot), we can see that the initial fetching has finished already - user is no longer null.
fetchStatus being fetching could be for another reason, for example, because another component picks up the query and a background refetch is happening due to the default staleTime of zero.
Looking at the reproduction:

if you use persisters in react, please us the PersistQueryClientProvider

Thanks @TkDodo! It does appear that I had another instance of that hook elsewhere, but I think my issue with not being able to rely on isFetched had to do with me accidentally forgetting to use PersistQueryClientProvider. I swapped this in and it "appears" to be working now, even though I can't get the example to run with the same setup I have working in my app (No QueryClient set) for some reason - maybe I'm blind).
I'm closing this, since I don't think there's an actual issue with react-query. Thank you!


Opening playground from terminal doesn't work after upgrade

This issue pertains to the following package(s):

[x] GraphQL Playground - Electron App

What OS and OS version are you experiencing the issue(s) on?
MacOS Sierra
What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?
This happens with every version, for example 1.4.3 and 1.4.4.
What is the expected behavior?
After downloading the latest .dmg and installing it, I can open the Playground using prisma playground or graphql playground right away.
What is the actual behavior?
After downloading the latest .dmg and installing it, running prisma playground or graphql playground doesn't result in anything.
What steps may we take to reproduce the behavior?
Install an earlier version. Download the latest .dmg. Install it and open the Playground app for the first time. Close it. From your terminal, run prisma init, then prisma playground. Nothing happens.
Please provide a gif or image of the issue for a quicker response/fix.

Workaround:

Manually open the Electron App so the starting screen with recent projects comes up.
run prisma playground or graphql playround. This opens the project in the already opened app.

From now on, it works as expected again.

Fixed in the latest version. Please let us know if you still have that issue, then we reopen it!


🐛 command not found in macos

Issue description
I run  go get -u github.com/gofiber/cli/fiber, and then use fiber dev in the zsh,  but get the error "zsh: command not found: fiber".
How can I fix it?
Environment: macOS Monterey 12.1, go version go1.17.4 darwin/amd64.

what was your solution ?@vecpeng

what was your solution ?@vecpeng

I have the same issue, any suggestions?

nano ~/.profile
and add this lines
PATH="/usr/local/bin/go/bin:$PATH" GOPATH=$HOME/go GOROOT=/usr/local/go PATH="$HOME/go/bin:$PATH" PATH="$GOPATH/bin:$PATH"
save and
source ~/.profile

Hi,
my GOPATH and GOROOT are set correctly. Because of the go mod package system the "go get -u" does not work inside a go module as explained at the following link: https://stackoverflow.com/a/68559728
The following installation command did the trick:
go install github.com/gofiber/cli/fiber@latest

Hope this helps!


expand CEQR survey variable seed table

related to #486
I started to mock the final wide table that will show in the survey, but the column names are expected to be display values like "CATS Permits"
Whether it's queried or just a version-controlled reference, this seed file becomes a table and seems useful.
Recommend using the file view of the changes
all builds on this branch here

noting that I forgot to update the model of the table

Just to clarify, we aren't using seeds yet, correct?

Would like to get this merged because I'm going to iterate on it in my branch

@sf-dcp

Just to clarify, we aren't using seeds yet, correct?

I don't think any queries require them asap. But it's definitely useful as a DE reference for variable_type values and may be really helpful in the final pivot step


Doc(eos_designs, eos_cli_config_gen): Various doc improvements

Change Summary

Updates the landing page for GitHub and avd.arista.com
Put all examples in new section "Examples" as opposed to "Getting Started".
Augment details for custom templates with node type customization
Add information for default_node_types
Cut "Input Variables.md" from eos_cli_config_gen doc, no longer in use.
Fix TODOs in porting guide
Add tip to custom templates in eos_cli_config_gen
Fix mermaid diagram rendering

Had to cut custom name for the classes, as MKDOCs do not support it
Investigated alternate MKDOCs plugins to change version, but none were found.

Diagram for pyavd functions

Component(s) name
arista.avd.eos_designs
How to test
N/A

https://github.com/aristanetworks/ansible-avd/issues/3019 has been address with a2bbf1f


fixed util/isFunction bug

This removes the check for lodash/underscore from the util function and adds the missing isFunction function to the shim.

Thanks again for the PR

wtf, i didnt press the right buttons


The descriptions display incompletely in 'Connect File Share to VM' dialog

Storage Explorer Version: 1.11.1
Build: 20191220.2
Branch: master
Language: Japanese/ German
Platform/OS: Windows 10
Architecture: ia32
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer.
Open 'Settings' -> Application (Regional Settings) -> Select '日本語' -> Restart Storage Explorer.
Expand one storage account -> File Shares.
Open one file share -> Click localized 'Connect VM'.
Check 'Connect File Share to VM' dialog.

Expect Experience:
The descriptions display completely.
Actual Experience:
The descriptions display incompletely.

More Info:

This issue doesn't reproduce on Linux / MacOS.
ENU screenshot:

Localized 4months ago.
File: loc\en\src\Standalone\resources\ConnectFileShareDialog.json
ID: 0; "MessageConnectInstructions"
SRC: To connect to this file share, run the following command from any Azure Windows virtual machine:
TGT: このファイル共有に接続するには、任意の Azure Windows 仮想マシンから次のコマンドを実行してください:

@lukaschal This issue also reproduces in German.🙁

We're taking a further review

The title string resides in StorageExplorer\src\Standalone\app\dialogs\ConnectFileShare\ConnectFileShareView.html
Microsoft Azure Storage Explorer - Connect File Share to VM
@craxal, the html seems not exposed to localization

This issue also reproduces in Russian.

This issue also reproduces in French on Windows.

@craxal Problem is that lowest string is truncated or not visible when first sentence is larger than one line. Non-resizable on localization side.
File: loc\en\src\Standalone\resources\ConnectFileShareDialog.json
ID: 0; "MessagePrimaryKeyWarning"
SRC: Primary key could be used to do more than just read/write from the mounted drive.

We just need to increase dialog height.


"Tazlău" is listed in the drop-down menu

Description:
"Tazlău" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Tazlău" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Tazlău, NEAMȚ (Tazlău)" and "Comuna Tazlău, NEAMȚ".


react-static : Error while building the static site for production

I am doing a proof of concept for the static site building by react-static. I just have some basic setup mostly defaults (basic template) of react-static.
The only thing added extra into the basic is react-static-plugin-sass
Have scss files for every component/page and importing it from within the component.
Here is my static.config.js file
`
import path from 'path';
export default {
plugins: [
'react-static-plugin-sass',
[
require.resolve('react-static-plugin-source-filesystem'),
{
location: path.resolve('./src/pages'),
},
],
require.resolve('react-static-plugin-reach-router'),
require.resolve('react-static-plugin-sitemap'),
],
};
`
The site is working perfectly locally and also getting served locally after building. No issues there.
But when I try to build the production version of the site by:
react-static build --staging
The following errors are happening:
`
Importing directory routes from: /Users/shalsing/repos/personal-projects/law-firm/src/pages/**/*.{js,jsx}
{ has404: true }
[✓] Routes Built (0.3s)
Building Templates...
[✓] Templates Built
Copying public directory...
[✓] Public directory copied (0.4s)
Bundling App...
Error: No module factory available for dependency type: CssDependency
at addDependency (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:800:12)
at iterationOfArrayCallback (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:208:3)
at addDependenciesBlock (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:816:5)
at Compilation.processModuleDependencies (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:827:4)
at afterBuild (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:954:15)
at buildModule.err (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:998:11)
at callback (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:734:5)
at module.build.error (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:782:12)
at handleParseResult (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/NormalModule.js:478:12)
at doBuild.err (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/NormalModule.js:500:6)
at runLoaders (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/NormalModule.js:358:12)
at /Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/loader-runner/lib/LoaderRunner.js:373:3
at iterateNormalLoaders (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
at /Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/loader-runner/lib/LoaderRunner.js:186:6
at context.callback (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
at childCompiler.runAsChild (/Users/shalsing/repos/personal-projects/law-firm/node_modules/extract-css-chunks-webpack-plugin/dist/loader.js:199:12)
at compile (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compiler.js:343:11)
at hooks.afterCompile.callAsync.err (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compiler.js:681:15)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/HookCodeFactory.js:33:10), :15:1)
at AsyncSeriesHook.lazyCompileHook (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/Hook.js:154:20)
at compilation.seal.err (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compiler.js:678:31)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/HookCodeFactory.js:33:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/Hook.js:154:20)
at hooks.optimizeAssets.callAsync.err (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:1423:35)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/HookCodeFactory.js:33:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/Hook.js:154:20)
at hooks.optimizeChunkAssets.callAsync.err (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:1414:32)
at _promise1.then._result1 (eval at create (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/HookCodeFactory.js:33:10), :14:1)
at process._tickCallback (internal/process/next_tick.js:68:7)
/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/neo-async/async.js:16
throw new Error('Callback was already called.');
^
Error: Callback was already called.
at throwError (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/neo-async/async.js:16:11)
at /Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/neo-async/async.js:2818:7
at process._tickCallback (internal/process/next_tick.js:61:11)
`
PLEASE HELP. Stuck with it from last 2 days.
Thanks in advance...

It would be helpful if you copy-pasted your build & build --staging scripts here together with  your react-static version.
Is your problem gone when you run build (production script) or maybe disable css-plugins?

Thanks for replying @warloque .

My server runs locally fine with the react-static-plugin-sass. Thats why I have been developing from 2-3 days.
It build fine and also works when I serve the build to test locally.

The errors (problem) only comes when I am trying to stage the changes by --staging script.
But for better understanding, I am sending you outputs for both the build and build --staging scripts.
Here is the result of build script:
npm run build
`

law-firm@ build /Users/shalsing/repos/personal-projects/law-firm
react-static build

Bundling application for Production...
Cleaning dist...
[✓] Dist cleaned (0.1s)
Cleaning artifacts...
[✓] Artifacts cleaned
Building Routes...
Importing routes from directory...
{ has404: true }
[✓] Routes Built (0.2s)
Building Templates...
[✓] Templates Built
Copying public directory...
[✓] Public directory copied (0.3s)
Bundling App...
Version: webpack 4.43.0
Time: 3597ms
Built at: 05/22/2020 4:55:32 AM
Asset       Size  Chunks                         Chunk Names
main.2deec02a.js   9.57 KiB       7  [emitted] [immutable]  main
styles.e7717838.css   10.1 KiB       0  [emitted] [immutable]  styles
templates/react_static_root/src/pages/404.jsx.738e9d8d.js  251 bytes       1  [emitted] [immutable]  react_static_root/src/pages/404.jsx
templates/react_static_root/src/pages/about.jsx.b1ddc628.js  271 bytes       2  [emitted] [immutable]  react_static_root/src/pages/about.jsx
templates/react_static_root/src/pages/contact.jsx.27a9cf42.js   4.04 KiB       3  [emitted] [immutable]  react_static_root/src/pages/contact.jsx
templates/react_static_root/src/pages/faq.jsx.51812640.js   5.86 KiB       4  [emitted] [immutable]  react_static_root/src/pages/faq.jsx
templates/react_static_root/src/pages/index.jsx.32e4a28e.js   2.59 KiB       5  [emitted] [immutable]  react_static_root/src/pages/index.jsx
templates/react_static_root/src/pages/services.jsx.158552b0.js  255 bytes       6  [emitted] [immutable]  react_static_root/src/pages/services.jsx
templates/styles.02af4bcc.js  280 bytes       0  [emitted] [immutable]  styles
templates/vendors~react_static_root/src/pages/contact.jsx.4a7c05ec.js   24.1 KiB       8  [emitted] [immutable]  vendors~react_static_root/src/pages/contact.jsx
templates/vendors~main.3fef3fd3.js    246 KiB       9  [emitted] [immutable]  vendors~main
[0] /Users/shalsing/repos/personal-projects/law-firm/node_modules/react/index.js 189 bytes {9} [built]
[1]<EMAIL_ADDRESS>479 bytes {9} [built]
[3]<EMAIL_ADDRESS>147 bytes {9} [built]
[9] ../lib/browser/index.js 24.6 KiB {9} [built]
[16]<EMAIL_ADDRESS>427 bytes {9} [built]
[17] ../lib/browser/hooks/useStaticInfo.js 624 bytes {9} [built]
[43]<EMAIL_ADDRESS>1.15 KiB {9} [built]
[56] multi ../lib/bootstrapPlugins.js ../lib/bootstrapTemplates.js ../lib/bootstrapApp.js 52 bytes {7} [built]
[57] ../lib/bootstrapPlugins.js 513 bytes {9} [built]
[58] /Users/shalsing/repos/personal-projects/law-firm/artifacts/react-static-browser-plugins.js 643 bytes {7} [built]
[113] ../lib/bootstrapTemplates.js 763 bytes {9} [built]
[114] /Users/shalsing/repos/personal-projects/law-firm/artifacts/react-static-templates.js 5.18 KiB {7} [built]
[122] ../lib/bootstrapApp.js 1.48 KiB {9} [built]
[123]<EMAIL_ADDRESS>665 bytes {9} [built]
[125] /Users/shalsing/repos/personal-projects/law-firm/src/index.js 744 bytes {7} [built]
+ 146 hidden modules
WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
 Your site will still function, but you may achieve better performance by addressing the warnings above.
[✓] App Bundled (4.6s)
Fetching Site Data...
[✓] Site Data Downloaded
Fetching Route Data...
[======] 6/6 100% 6000/s 0.0s
[✓] Route Data Downloaded
Exporting HTML across 8 threads...
[======] 6/6 100% 286/s 0.0s
[✓] HTML Exported (9.5s)
Generating sitemap.xml...
[✓] sitemap.xml generated
Your app is now exported! Here's what we suggest doing next:

Upload your 'dist' directory to your favorite static host! We recommend using Netlify:

npx netlify-cli deploy

Analyze your app's webpack bundles

react-static bundle --analyze
`

ABOVE SCRIPT WORKS FINE

BUT ISSUE COMES WHEN I RUN FOLLOWING STAGING BUILD:

`
react-static build --staging
Bundling application for Staging...
Cleaning dist...
[✓] Dist cleaned (0.3s)
Cleaning artifacts...
[✓] Artifacts cleaned
Building Routes...
Importing routes from directory...
{ has404: true }
[✓] Routes Built (0.2s)
Building Templates...
[✓] Templates Built
Copying public directory...
[✓] Public directory copied (0.4s)
Bundling App...
Error: No module factory available for dependency type: CssDependency
at addDependency (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:800:12)
at iterationOfArrayCallback (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:208:3)
at addDependenciesBlock (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:816:5)
at Compilation.processModuleDependencies (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:827:4)
at afterBuild (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:954:15)
at buildModule.err (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:998:11)
at callback (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:734:5)
at module.build.error (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:782:12)
at handleParseResult (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/NormalModule.js:478:12)
at doBuild.err (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/NormalModule.js:500:6)
at runLoaders (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/NormalModule.js:358:12)
at /Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/loader-runner/lib/LoaderRunner.js:373:3
at iterateNormalLoaders (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
at /Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/loader-runner/lib/LoaderRunner.js:186:6
at context.callback (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
at childCompiler.runAsChild (/Users/shalsing/repos/personal-projects/law-firm/node_modules/extract-css-chunks-webpack-plugin/dist/loader.js:199:12)
at compile (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compiler.js:343:11)
at hooks.afterCompile.callAsync.err (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compiler.js:681:15)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/HookCodeFactory.js:33:10), :15:1)
at AsyncSeriesHook.lazyCompileHook (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/Hook.js:154:20)
at compilation.seal.err (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compiler.js:678:31)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/HookCodeFactory.js:33:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/Hook.js:154:20)
at hooks.optimizeAssets.callAsync.err (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:1423:35)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/HookCodeFactory.js:33:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/Hook.js:154:20)
at hooks.optimizeChunkAssets.callAsync.err (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/webpack/lib/Compilation.js:1414:32)
at _promise1.then._result1 (eval at create (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/tapable/lib/HookCodeFactory.js:33:10), :14:1)
at process._tickCallback (internal/process/next_tick.js:68:7)
/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/neo-async/async.js:16
throw new Error('Callback was already called.');
^
Error: Callback was already called.
at throwError (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/neo-async/async.js:16:11)
at /Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/neo-async/async.js:2818:7
at process._tickCallback (internal/process/next_tick.js:61:11)
`
Here is my static.config.js file:
`
import path from 'path';
export default {
plugins: [
'react-static-plugin-sass',
[
require.resolve('react-static-plugin-source-filesystem'),
{
location: path.resolve('./src/pages'),
},
],
require.resolve('react-static-plugin-reach-router'),
require.resolve('react-static-plugin-sitemap'),
],
};
`
Thanks for helping...

Don't know for sure, but it looks like some css-loader or a plugin uses some deprecated API and it's failing during build.
I strongly suggest you to find that failing piece of code by running node --trace-deprecation ./node_modules/.bin/webpack --bail --env dist -p firstly.
Maybe the bady guy here is the tapable plugin (judging by your log) which stops you, try to find who from the dependencies is using it. Google says it's deprecated.

@warloque
node --trace-deprecation ./node_modules/.bin/webpack --bail --env dist -p

Hash: 27eb5491d1c140a18d5d
Version: webpack 4.43.0
Time: 79ms
Built at: 05/22/2020 1:18:48 PM
 1 asset
Entrypoint main = main.js
[0] ./src/index.js 351 bytes {0} [built] [failed] [1 error]

ERROR in ./src/index.js 22:6
Module parse failed: Unexpected token (22:6)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|   const render = (Comp) => {
|     renderMethod(
>       <AppContainer>
|         <Comp />
|       </AppContainer>,

Also I deleted the package-lock.json and node-modules, and tried to clean install again.
Here were the deprecation list:
npm install

npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

><EMAIL_ADDRESS>install /Users/shalsing/repos/personal-projects/law-firm/node_modules/fsevents
> node install.js

  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node

><EMAIL_ADDRESS>install /Users/shalsing/repos/personal-projects/law-firm/node_modules/node-sass
> node scripts/install.js

Cached binary found at /Users/shalsing/.npm/node-sass/4.14.1/darwin-x64-64_binding.node

><EMAIL_ADDRESS>postinstall /Users/shalsing/repos/personal-projects/law-firm/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

><EMAIL_ADDRESS>postinstall /Users/shalsing/repos/personal-projects/law-firm/node_modules/core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"

><EMAIL_ADDRESS>postinstall /Users/shalsing/repos/personal-projects/law-firm/node_modules/ejs
> node ./postinstall.js

Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)

><EMAIL_ADDRESS>postinstall /Users/shalsing/repos/personal-projects/law-firm/node_modules/node-sass
> node scripts/build.js

Binary found at /Users/shalsing/repos/personal-projects/law-firm/node_modules/node-sass/vendor/darwin-x64-64/binding.node
Testing binary
Binary is fine
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"<8.10.0"} (current: {"node":"10.16.3","npm":"6.14.5"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| 2.x but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^1.7.0 but none is installed. You must install peer dependencies yourself.

added 1463 packages from 662 contributors and audited 1467 packages in 29.759s

50 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

MacBook-Pro-32:law-firm shalsing$

BUT as I said earlier its only happening during ---staging time. Working fine when I am working locally and serving locally!

@warloque  I also tried to create a brand new project.
script 1: react-static create
script 2: react-static build --staging
react-static -v : 7.2.3
STILL ERRORS :(

? What should we name this project? my-test
? Select a template below... basic
Creating new react-static project...

Using React Static template: basic
Installing dependencies with: NPM...
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"<8.10.0"} (current: {"node":"10.16.3","npm":"6.14.5"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| 2.x but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^5.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^5.3.0 but none is installed. You must install peer dependencies yourself.

[✓] Project "my-test" created (24.8s)

  To get started:

    cd "my-test"

    npm run start - Start the development server
    npm run build - Build for production
    npm run serve - Test a production build locally

MacBook-Pro-32:personal-projects shalsing$ cd my-test/
MacBook-Pro-32:my-test shalsing$ react-static build --staging
Bundling application for Staging...

Cleaning dist...
[✓] Dist cleaned
Cleaning artifacts...
[✓] Artifacts cleaned
Building Routes...
Importing routes from directory...
{ has404: true }
[✓] Routes Built (0.1s)
Building Templates...
[✓] Templates Built
Copying public directory...
[✓] Public directory copied
Bundling App...
Version: webpack 4.43.0
Time: 8058ms
Built at: 05/22/2020 1:36:58 PM
                             Asset       Size  Chunks               Chunk Names
                  main.ba6a50e4.js   10.6 KiB       0  [immutable]  main
               styles.3345f82a.css  361 bytes       1  [immutable]  styles
      templates/styles.3345f82a.js   82 bytes       1  [immutable]  styles
templates/vendors~main.701e8abc.js    239 KiB       2  [immutable]  vendors~main
  [0] /Users/shalsing/repos/personal-projects/my-test/node_modules/react/index.js 189 bytes {2} [built]
  [2]<EMAIL_ADDRESS>147 bytes {2} [built]
 [10] (webpack)/buildin/module.js 552 bytes {2} [built]
 [13]<EMAIL_ADDRESS>427 bytes {2} [built]
 [22] /Users/shalsing/repos/personal-projects/my-test/artifacts/react-static-browser-plugins.js 679 bytes {0} [built]
 [42]<EMAIL_ADDRESS>1.15 KiB {2} [built]
 [45] ../lib/browser/index.js 24.8 KiB {2} [built]
 [46] /Users/shalsing/repos/personal-projects/my-test/artifacts/react-static-templates.js 7.4 KiB {0} [built] [failed] [1 error]
 [50] multi ../lib/bootstrapPlugins.js ../lib/bootstrapTemplates.js ../lib/bootstrapApp.js 52 bytes {0} [built]
 [51] ../lib/bootstrapPlugins.js 472 bytes {2} [built]
[104] ../lib/bootstrapTemplates.js 722 bytes {2} [built]
[105] ../lib/bootstrapApp.js 1.48 KiB {2} [built]
[106]<EMAIL_ADDRESS>665 bytes {2} [built]
[108] ../lib/browser/hooks/useStaticInfo.js 624 bytes {2} [built]
[110] /Users/shalsing/repos/personal-projects/my-test/src/index.js 682 bytes {0} [built]
    + 103 hidden modules

ERROR in /Users/shalsing/repos/personal-projects/my-test/artifacts/react-static-templates.js
Module build failed (from ./babel-loader/lib/index.js):
TypeError: /Users/shalsing/repos/personal-projects/my-test/artifacts/react-static-templates.js: Property value expected type of string but got null
    at Object.validate (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/types/lib/definitions/utils.js:160:13)
    at validateField (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/types/lib/validators/validate.js:24:9)
    at validate (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/types/lib/validators/validate.js:17:3)
    at builder (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/types/lib/builders/builder.js:38:27)
    at Object.StringLiteral (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/types/lib/builders/generated/index.js:349:31)
    at idOption (/Users/shalsing/repos/personal-projects/my-test/node_modules/babel-plugin-universal-import/index.js:134:49)
    at PluginPass.Import (/Users/shalsing/repos/personal-projects/my-test/node_modules/babel-plugin-universal-import/index.js:241:13)
    at newFn (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/visitors.js:179:21)
    at NodePath._call (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/path/context.js:55:20)
    at NodePath.call (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/path/context.js:42:17)
    at NodePath.visit (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/path/context.js:90:31)
    at TraversalContext.visitQueue (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:112:16)
    at TraversalContext.visitSingle (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:84:19)
    at TraversalContext.visit (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:140:19)
    at Function.traverse.node (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/index.js:84:17)
    at NodePath.visit (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/path/context.js:97:18)
    at TraversalContext.visitQueue (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:112:16)
    at TraversalContext.visitMultiple (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:79:17)
    at TraversalContext.visit (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:138:19)
    at Function.traverse.node (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/index.js:84:17)
    at NodePath.visit (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/path/context.js:97:18)
    at TraversalContext.visitQueue (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:112:16)
    at TraversalContext.visitSingle (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:84:19)
    at TraversalContext.visit (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:140:19)
    at Function.traverse.node (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/index.js:84:17)
    at NodePath.visit (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/path/context.js:97:18)
    at TraversalContext.visitQueue (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:112:16)
    at TraversalContext.visitMultiple (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:79:17)
    at TraversalContext.visit (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:138:19)
    at Function.traverse.node (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/index.js:84:17)
    at NodePath.visit (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/path/context.js:97:18)
    at TraversalContext.visitQueue (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:112:16)
    at TraversalContext.visitMultiple (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:79:17)
    at TraversalContext.visit (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:138:19)
    at Function.traverse.node (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/index.js:84:17)
    at NodePath.visit (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/path/context.js:97:18)
    at TraversalContext.visitQueue (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:112:16)
    at TraversalContext.visitSingle (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:84:19)
    at TraversalContext.visit (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/context.js:140:19)
    at Function.traverse.node (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/index.js:84:17)
    at traverse (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/traverse/lib/index.js:66:12)
    at transformFile (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/core/lib/transformation/index.js:107:29)
    at transformFile.next (<anonymous>)
    at run (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/core/lib/transformation/index.js:35:12)
    at run.next (<anonymous>)
    at Function.transform (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/@babel/core/lib/transform.js:27:41)
    at transform.next (<anonymous>)
    at step (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/gensync/index.js:254:32)
    at gen.next (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/gensync/index.js:266:13)
    at async.call.value (/Users/shalsing/.nvm/versions/node/v10.16.3/lib/node_modules/react-static/node_modules/gensync/index.js:216:11)
 @ ../lib/bootstrapTemplates.js 7:16-64 15:20-68
 @ multi ../lib/bootstrapPlugins.js ../lib/bootstrapTemplates.js ../lib/bootstrapApp.js
Child extract-css-chunks-webpack-plugin css-loader/dist/cjs.js??ref--4-oneOf-2-1!postcss-loader/src/index.js??postcss!../../../../../../../../repos/personal-projects/my-test/src/app.css:
    [0] ./css-loader/dist/cjs.js??ref--4-oneOf-2-1!./postcss-loader/src??postcss!/Users/shalsing/repos/personal-projects/my-test/src/app.css 803 bytes {0} [built]
    [1] ./css-loader/dist/runtime/api.js 2.35 KiB {0} [built]

                => There were ERRORS during the prod build stage! :(
                => Fix them and try again!

Can you try react-static 7.3.0 for all packages?
Additionally, the error "Property value expected type of string but got null" is usually when there is something wrong with either the 404 page, a template or when there is some package that is trying to access DOM/window apis during build.

@SleeplessByte I tried updating all react-static packages to 7.3.0 but still the same issue. :(
There is nothing fancy with the site I am building. Only 1 extra thing I have is  **react-static-plugin-sass** . I am using individual scss for every component and importing it at the top of the respective component.
As I said earlier its only happening during ---staging time. Working fine when I am working locally STARTING AND BUILDING LOCALLY and serving locally!
Here are some of my files in my project:

static.config.js

import path from 'path';
export default {
  plugins: [
    'react-static-plugin-sass',
    [
      require.resolve('react-static-plugin-source-filesystem'),
      {
        location: path.resolve('./src/pages'),
      },
    ],
    require.resolve('react-static-plugin-reach-router'),
    require.resolve('react-static-plugin-sitemap'),
  ],
};

src/index.js

import React from 'react';
import ReactDOM from 'react-dom';
// eslint-disable-next-line import/no-extraneous-dependencies
import { AppContainer } from 'react-hot-loader';

// Your top level component
import App from './App';

// Export your top level component as JSX (for static rendering)
export default App;

// Render your app
if (typeof document !== 'undefined') {
  const target = document.getElementById('root');

  const renderMethod = target.hasChildNodes()
    ? ReactDOM.hydrate
    : ReactDOM.render;

  const render = (Comp) => {
    renderMethod(
      <AppContainer>
        <Comp />
      </AppContainer>,
      target,
    );
  };

  // Render!
  render(App);

  // Hot Module Replacement
  if (module && module.hot) {
    module.hot.accept('./App', () => {
      render(App);
    });
  }
}

App.jsx

import React from 'react';
import { Root, Routes } from 'react-static';
import { Router } from '@reach/router';
import Footer from './components/footer';
import Header from './components/header';
**import './app.scss';**

function App() {
  return (
    <Root>
      <div className="app">
        <Header />
        <div className="app-content">
          <React.Suspense fallback={<em>Loading...</em>}>
            <Router>
              <Routes default />
            </Router>
          </React.Suspense>
        </div>
        <Footer />
      </div>
    </Root>
  );
}

export default App;

package.json

{
  "name": "law-firm",
  "version": "1.0.0",
  "repository": {
    "type": "git",
    "url": "git@github.com:somewhere/law-firm.git"
  },
  "license": "ISC",
  "scripts": {
    "start": "react-static start",
    "stage": "react-static build --staging",
    "build": "react-static build",
    "analyze": "react-static build --analyze",
    "serve": "serve dist -p 3000",
    "es-lint": "npx eslint './src/**/*.{js,jsx}' --quiet",
    "es-lint:fix": "npm run es-lint './src/**/*.{js,jsx}' -- --fix"
  },
  "dependencies": {
    "@reach/router": "^1.2.1",
    "react": "^16.9.0",
    "react-dom": "^16.9.0",
    "react-hook-form": "^5.7.2",
    "react-static": "^7.3.0",
    "react-static-plugin-reach-router": "^7.3.0",
    "react-static-plugin-sitemap": "^7.3.0",
    "react-static-plugin-source-filesystem": "^7.3.0",
    "react-static-plugin-sass": "^7.3.0"
  },
  "devDependencies": {
    "babel-eslint": "^10.0.2",
    "eslint": "^6.1.0",
    "eslint-config-airbnb": "^18.1.0",
    "eslint-config-react-app": "^5.0.1",
    "eslint-config-react-tools": "^1.1.7",
    "eslint-plugin-flowtype": "^4.2.0",
    "eslint-plugin-import": "^2.18.2",
    "eslint-plugin-jsx-a11y": "^6.2.3",
    "eslint-plugin-react": "^7.14.3",
    "serve": "^11.1.0",
    "webpack-cli": "^3.3.11"
  }
}

.babelrc

{
  "presets": ["react-static/babel-preset.js"]
}

.eslintrc

{
  "extends": ["airbnb", "eslint:recommended", "plugin:react/recommended"],
  "parser": "babel-eslint",
  "parserOptions": {
    "ecmaVersion": 2018,
    "sourceType": "module",
    "ecmaFeatures": {
        "impliedStrict": true,
        "jsx": true
    }
  },
  "settings": {
    "react": {
      "pragma": "React",
      "version": "detect"
    }
  },
  "rules": {
    "no-console": "error",
    "semi": "error",
    "comma-dangle": ["error", "always-multiline"],
    "no-unused-vars": ["error", { "args": "none" }],
    "linebreak-style": 0,
    "react/jsx-filename-extension": [1, { "extensions": [".js", ".jsx"] }]
  },
  "globals": {
    "document": true,
    "module": true,
    "window": true,
    "Email": true,
    "requestAnimationFrame": true
  }
}

Please let me know if anyone need any more details to help me fix this issue.
Thanks
@warloque @tannerlinsley @SleeplessByte

just to make sure sass plugin is set up correctly, try to place react-static-plugin-sass-call just after react-static-plugin-source-filesystem and before react-static-plugin-reach-router.
if that does not help, try to build --stagewithout sass plugin at all or double check your scss files, maybe something is wrong with nested imports or mixins.
chokidar dependency has been failing for me some day, who knows, may be this is sass plugin for you now.

@warloque
This might sound weird.
When I run : npm run-script stage
The stage build succeeds
but when I run : react-static build --staging
The build fails with the above mentioned error
Even though  npm run-script stage runs the same script which fails.
Here is my package.json file
{
  "name": "law-firm",
  "version": "1.0.0",
  "repository": {
    "type": "git",
    "url": "git@github.com:somewhere/law-firm.git"
  },
  "license": "ISC",
  "scripts": {
    "start": "react-static start",
    "stage": "react-static build --staging",
    "build": "react-static build",
    "analyze": "react-static build --analyze",
    "serve": "serve dist -p 3000",
    "es-lint": "npx eslint './src/**/*.{js,jsx}' --quiet",
    "es-lint:fix": "npm run es-lint './src/**/*.{js,jsx}' -- --fix"
  },
  "dependencies": {
    "@reach/router": "^1.2.1",
    "react": "^16.9.0",
    "react-dom": "^16.9.0",
    "react-hook-form": "^5.7.2",
    "react-static": "^7.3.0",
    "react-static-plugin-reach-router": "^7.3.0",
    "react-static-plugin-sitemap": "^7.3.0",
    "react-static-plugin-source-filesystem": "^7.3.0",
    "react-static-plugin-sass": "^7.3.0"
  },
  "devDependencies": {
    "babel-eslint": "^10.0.2",
    "eslint": "^6.1.0",
    "eslint-config-airbnb": "^18.1.0",
    "eslint-config-react-app": "^5.0.1",
    "eslint-config-react-tools": "^1.1.7",
    "eslint-plugin-flowtype": "^4.2.0",
    "eslint-plugin-import": "^2.18.2",
    "eslint-plugin-jsx-a11y": "^6.2.3",
    "eslint-plugin-react": "^7.14.3",
    "serve": "^11.1.0",
    "webpack-cli": "^3.3.11"
  }
}

You might have react-static installed as global and that be a different version than 7.3.0. That would cause this behaviour.

@SleeplessByte I updated the global react-static to 7.3.0 but same issue:
When I run : npm run-script stage
The stage build succeeds
but when I run : react-static build --staging
The build fails with the above mentioned error
Even though npm run-script stage runs the same script which fails.

I am not able to resolve the build by react-static build --staging
but npm run-script stage is working as expected. Hence closing the issue.
Thanks everyone for helping.


Need No Read Ranges

could be a pain to add, but need to add the ability to forcefully exclude specific registers from the reading ranges.
some devices, such as my sigineer inverter will bug out / not reply when certain ranges are read, because they are "reserved" or protected from reading.

hmm.. i think i'm overthinking this a bit.
let's add a recommended variable screen. mask being additive, screen being subtractive.
move mask.txt and screen.txt to example.txt
if screen is empty, use protocol.screen.txt
that way theese are configurable; the main registers that are causing problems in sigineer protocol are the sigineer bms registers. , they are likely not responding because i'm not using sigineer batteries, but if someone is they may want to re-enable those registers.

https://github.com/HotNoob/InverterModBusToMQTT/commit/212a2855c0db81ed0593fc083db148b3c9656472#diff-da5b239f4593374f6ba0cfb8ae4bb8b681053eef6f5a1534a35430a9d15694aa
read/write can be controlled by the writable column now.
but i think i should still add a mask/screen feature for the light users.


[FEATURE] Support change admin password

Is your feature request related to a problem?
I don't see how to change admin password from the readme. For security enabled cluster, the default password for admin is too weak (it's admin by default). Seems we have no way to change the default password for admin now.
What solution would you like?
Provide some option to let user specify their own password
What alternatives have you considered?
No
Do you have any additional context?
No

This feature comes from Security plugin, will go through the existing code and try to figure out if the user details can be updated at cluster setup.

This PR should address this concern as users will be able to provide the configuration using additionalConfig flag.


fillOnMouseLeave doesn't get called

I'm using a <GEOJSONLayer/>  to display some polygons. I'm using a combo of mousemove and mouseleave to display a popup of the current polygon:
<GeoJSONLayer
  data={polygons}
  fillPaint={{
    'fill-color': '#333',
    'fill-opacity': 0.1,
  }}
  fillOnMouseMove={e => {
    console.log('MOUSE MOVE', e)
    if (!currentPolygon || currentNeighbourhoodHover.properties.id !== e.features[0].properties.id) {
      this.setState({
        currentPolygon: e.features[0]
      })
    }
  }}
  fillOnMouseLeave={e => {
    console.log('MOUSE LEAVE', e)
    this.setState({
      currentPolygon: null,
    })
  }}
  />

My problem is that fillOnMouseLeave event gets called only like 3/4 of time, and so I can't hide the popup displayed. It mostly relates to the speed the mouse is moving.
Previously, everything worked fine with the non react mapboxgl-js library like map.on('mouseleave', 'polygons-layer', mouseLeaveListener), so I'm guessing the problem is not from the core library.

+1

+1
Same thing with circleOnMouseLeave, does work only if no circleOnMouseEnter function is set.

Any update on this?

Move your event handlers outside the render function so they won't be recreated each time render when state changes. This fixed this for me.
Event re-registration code looks okay at first glance - https://github.com/alex3165/react-mapbox-gl/blob/master/src/geojson-layer.ts#L317, so maybe the leave event handler fires somewhere in between off and on...

any update on this, or workaround?

If anyone else is having this issue and using functional components/hooks, wrapping the fillOnMouseLeave in a callback seems to fix it.
e.g. something like:

const Map = ( ) => {
  const memoizedReset = useCallback(() => {
    //do something on mouse leave
  }, []);
  const onHover = e => {
    //do something on hover
  };

  return (

      <MapGL>
        <GeoJSONLayer
          fillOnMouseLeave={memoizedReset}
          fillOnMouseEnter={onHover}
        />
      </MapGL>

  );
};

I was able to get fillOnMouseLeave to work by binding the functions in the constructor instead of one-lining it like the example does. I'm not sure why it works like this.
  constructor(props) {

        super(props)

        this.state = {
            county: 'county name',
            center: {
                lng: -71.77,
                lat: 43.71
            },
            zoom: [6]
        }

        this.onClickFill = this.onClickFill.bind(this);
        this.onEnter = this.onEnter.bind(this)
        this.onExit = this.onExit.bind(this)
    }

  render() {

        return (

              <GeoJSONLayer
                    data={this.getGeojson()}
                    fillPaint={this.fillStyle()}
                    before='waterway-label'
                    fillOnClick={this.onClickFill}
                    fillOnMouseEnter={this.onEnter}
                    fillOnMouseLeave={this.onExit}
                    // not like this: fillOnMouseLeave={this.onExit.bind(this, 'grab')}

                        />

)
}

I'm in a functional component. If I try to useCallback(,[something]) with something in the dependency array, then fillOnMouseLeave does not work. I got around this by setting up const [leaveEvent, setLeaveEvent] = useState() and setting fillOnMouseLeave={setLeaveEvent} then putting my "real" handler in an effect like useEffect(()={}, [leaveEvent]) that runs when there is a new leaveEvent.


Conduits Extract by default

Is there an existing proposal for this?

[X] I did not find any existing requests.

Explain your idea
extracting on conduits should be set to always active by default like in eio 1.12
Why do you thing this feature belongs in Ender IO.
it used to be that way, and it avoided extra repetitive menuing
Are there any alternatives?
No response
Any Additional Information?
No response

That was never defualt behaviour on conduits.

Was this in relation to Item or Energy conduits? If it was Energy, this has been resolved as part of #817 and can be closed.
Thanks!

I'm going to close this as we've not received any replies - please reopen if needed. Thanks

nevermind i was wrong, i remembered it that way only because it was just a single right click to make it always active on exctract, contrary to now with submenus. my apology.

I would like a config option  to allow conduits to be 'always active by default'. it's just way too fiddly to set a bunch of conduits to active after placing them. of the thousands of conduits connections I have in my base, ZERO of them are 'never active', and approximately 100% of them are 'always active'. EVERY SINGLE ONE of them had to be reconfigured manually with at least 4 clicks/keypresses.


How can I create a custom Vue filter?

I'm trying to figure out how to create a custom Vue filter in this boilerplate, but I couldn't do it. Can anybody help me?
Thanks in advance.

i don't think it's any different than without this boilerplate. for a global filter, create it before instancing.
Vue.filter('wrapIt', function(val, before, after) { return before + val + after})

/* eslint-disable no-new */
new Vue({
  components: {
    App
  },
  router,
  store,
  template: '<App/>'
}).$mount('#app')

Nice, thanks for the detailed reply! :)


Natasha/listening duration

Adds listening duration to episode model
Adds listening duration to feed cells, episode cells, bookmark cells, and episode detail header view
Sends batch updates to backend for listening history durations
Removes all UI code for updating based off a change in the episode isPlaying flag. The views all update correctly when switching from another view back to that view.  This should integrate well with Drew's KVO branch (since we will be calling setupWithEpisode on every view that observes the episode isPlaying change)


Port history from casper-engine-test-support repo

This brings over changes which were applied to the casper-engine-test-support crate while it lived briefly in its own repo.
The move to its own repo has been cancelled, hence the history is backported.
Closes #2285.

bors merge


README examples not working

Whenever I try to run either of the examples in the README, I get an error similar to this:
Error

main.lua:18: bad argument #1 to 'NewFrame' (string expected, got table)

Traceback

[C]: in function 'NewFrame'
main.lua:18: in function 'update'
[C]: in function 'xpcall'

Yes, this happens with the 0.9 release version. I am also looking at this issue

Any luck ?

Hi, just in case somebody needs help:
I'm on MacOs and using the released bin from github gave me the same error. But building the library worked

I am trying to cross-reference patrickriordan's imgui_lua_bindings, which I believe this is based off of, and I'm trying to use the Drawlist from lua to no avail:
    imgui.DrawList_AddLine(
        imgui.DrawList_AddLine(0, 0, 100, 100, 0xFF0000FF, 2));

I'm trying to come up with an example as to how to use the drawlist but nothing has come up. An example in this repo would also be nice.


Body filepath

Summary

With this PR, we extend the functionality of the create release action by passing through the newly added option body-filepath, a string that points to the file that has the release notes instead of passing/storing the release notes on the body argument. Specifically, the current functionality as is, allows to pass the body of the release notes through the body argument of the action. We extend this functionality by introducing a new argument called body-filepath which points to a file to read from the release notes. This is useful in case we want to ensure that we don't reach the shell arguments limit which results in the too many arguments error.  The body-filepath extra argument is optional and has a priority only when the body argument is empty and the body-filepath is not.

We already use this action in our stack workflow https://github.com/paketo-community/ubi-base-stack/blob/main/actions/release/create/entrypoint/main.go

It does not change the default behaviour

Use Cases

With this PR we ensure that no error will occur in case of a newly added stack produces too many changes, e.g., on the added packages of the build and run image.
Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@ForestEckhardt Can you take a look whenever you have time?


Issue with local deployment

I served the code locally and it was showing nicely on the computer but it gives an error on the mobile. It says "can't access media"

If you are using localhost as server you must use and https connection because Chrome dont give accesss to camera on insecured hosts.
https://stackoverflow.com/questions/35127383/npm-http-server-with-ssl
There is a solucion using a ssl certificate with openssl and http-server module if you are using express or browser-sync or other server find how to use ssl on in and try again

funny enough I am using both browser-sync and express.
I have tried it on Mozilla on the phone and it doesn't display a thing

try to server it over localhost, just to be sure this is not a webrtc-https thing

I deployed it on Heroku. When I use Chrome on Mobile it still doesn't work

maybe you should contact heroku then

Android version? I have the same problem but was because Chrome on some older android versions dont work, when I use Chrome Canary of Firefox it works (again, check your browser options and see that camera permission is available)

When I launch the examples from this repo, they work fine. But my own project isn't working on mobile browsers. It's working on Mozilla though.

mmm so maybe is a Chrome issue or some miss configuracion when running it local

besides that the error "Cant access user media :(", if you see the code, is raising when cant use the camera (permissions problems 99% times)

It still shows the same error when I run it over Heroku, so it's not an SSL issue.

Sometimes when you run over heroku open your browser and see if it's https if not change it to https my give your a security warning but that's fine.
and sometimes it doesn't work on the chrome app try chrome beta.

Sometimes when you run over heroku open your browser and see if it's https if not change it to https my give your a security warning but that's fine.
and sometimes it doesn't work on the chrome app try chrome beta.

try to do that, go to ar.js code and search "cant access user media" (or the alert box that you see) put a breakdown point near there and refesh the browser then debug it to find if its something related to permissions or other issue

same here , cant access user media in chrome but works on mobile firefox browser running locally..

same here , cant access user media in chrome but works on mobile firefox browser running locally..

Here is a answer about the https getUserMedia. i hope it helps
https://jeromeetienne.github.io/AR.js/docs/misc/FAQ.html#cant-access-user-media-error

I'm trying to host a code on hostinger.
But it gives error(can't access user media :())
Hostinger use http and not https
What can I do to make it work on http???

It will not work on http as the browser disables the access of media decides on http with isn't considered secure

So isn't there any other way around?

Same here. Our IT manager set up a https web page for me to test and he wasn't able to get it to work.
We saw the fps graph and the text at the top of the page. We pulled down everything from github.
Still stuck.
Tony B.

For hosting make sure you acquire the required certificates from the vendor
But for locally I would suggest you read this
https://deliciousbrains.com/https-locally-without-browser-privacy-errors/

If your website is http , consider cloudflare to get a free https along
with other benefits, as for local deploy you could use ngrok tunnels which
are https .
https://www.cloudflare.com
https://ngrok.com
On Sat, Jul 29, 2017 at 10:23 AM, Pratik Sampat<EMAIL_ADDRESS>wrote:

For hosting make sure you acquire the required certificates from the vendor
But for locally I would suggest you read this
https://deliciousbrains.com/https-locally-without-browser-privacy-errors/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jeromeetienne/AR.js/issues/88#issuecomment-318804129,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH09QhRU6Io2ZlacPoJy_OFxDIAmm2M1ks5sSrq9gaJpZM4Nvd6O
.


WIP: feat: support file stat options

Types

[x] 🎉 New Features

Background or solution
Changelog

/publish


What was the difference bewteen the category 'Labs' of 'd_items' and 'd_labitems'?

For example, the albumin, in the category 'Labs' of 'd_items', its itemid was 227456,  in 'd_labitems', its itemid were 50862, 51542 and so on.  I can find results by the two types of itemid. I wonder what was the difference between them. Should I take all of them in my query? Thanks.

The data from d_labitems and labevents is from the hospital database. This is the recommended table to pull laboratory data from because:

the local staff are informed the lab database is the "ground truth" - any requested changes should be done to the laboratory data
it is available outside the ICU, where as chartevents is only available in the ICU
it has a specimen_id, allowing linking to labs drawn from the same specimen (more useful for other labs such as blood gases)

Thank you for your answer and your great work!


Persistent elements lifetime management

Related to https://github.com/uber/xviz/issues/64
Scope out the options for management of persistent objects, where the boundaries are and alternatives (custom layers) and how they would or would not be able to utilize XVIZ

Duplicate of https://github.com/uber/xviz/issues/64


The NPM published version is not JS

The publish version of this library (on NPM) is not JS.
If we use this library... ts will try to compile... and it will break.. if you have a different version, from the one built, and this lib is kind of old.
When publishing to npm you should publish only the build version (js), not the ts files.

I am sorry that you state things without checking whether they are true, because the library is published as javascript (check the package.json). It is indeed an old version of typescript, but it still is typescript.
Just exclude typescript from compiling the amqp-ts .ts source code in node-modules and it should work.

Wow... sry. I'm completely stupid.. I was looking for the js file and did not found it :(
Thanks


Validate invalid seasonal Address dates

Thread.
It's possible to have a Seasonal Start Date in the picklists on Address as February (2) 30, and it appears that there is no error thrown. Consider validation to prevent invalid Month/Day combinations.

**lurch: add

Salesforce has determined that this issue will not be explored further.


Fix /transaction.all slow responses

closes #589
Overview
This PR switches from using a double left join to using a single inner with a bunch of added indices for increased performance.
Note
Also cherry picked this commit to get it into 0.1 (it was preventing Docker from starting).

@pnowosie Merging without removing the tests (because we need the feature kinda right now), but happy to discuss further and potentially submit another PR :)

This has  generally improved response times across all of the watcher endpoints. 🙌

TODO

Cherry pick this into master


Add onClick-event to select all to amount input

When you add a new expense you always have to start by removing the placeholder 0 value that is already there.
I added an onFocus event to select the entire value so that you can just start writing the amount immediately

Works fine with Chrome, has issues though with Safari when selecting the input field by clicking into it:

first the onFocus event fires, selecting the text
after that the onClick event fires, deselecting it again

Suggestion
Use an onClick() event handler to select the text instead.

Good catch, I had only tested in safari on mobile and there it worked as expected. I think onClick might be good.

💯