can not see any 'projects' in the projects page with docker compose depoly

If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with documentation (for small docs fixes please send a PR instead).
The form below must be filled out.

System information

centos 7.4:
docker 18.09.5:

Describe the problem
as the READEME describe, I deployed the doccano use the docker-compose method,after the system  started,:

login
click 'projects'
and I cannt see anything in this page like this

and I open the developer console, a js file cannot find by the system, like this

also I cannot find this js file in the app/server folder, but in the app/server/static
Source code / logs
docker node logs:
Starting webpack

><EMAIL_ADDRESS>start /src/app/server
> cross-env HOT_RELOAD=1 DEBUG=1 webpack-dev-server

ℹ ｢wds｣: Project is running at http://<IP_ADDRESS>:8080/
ℹ ｢wds｣: webpack output is served from http://<IP_ADDRESS>:8080/
ℹ ｢wdm｣: wait until bundle finished: /static/js/
ℹ ｢wdm｣: Hash: 3f63afd2adca1b8d0559
Version: webpack 4.12.0
Time: 4963ms
Built at: 2019-05-21 08:35:39
                          Asset      Size                        Chunks             Chunk Names
                       index.js  1.52 MiB                         index  [emitted]  index
           demo_named_entity.js  1.93 MiB             demo_named_entity  [emitted]  demo_named_entity
            demo_translation.js  1.88 MiB              demo_translation  [emitted]  demo_translation
     document_classification.js  4.19 MiB       document_classification  [emitted]  document_classification
            download_seq2seq.js   4.1 MiB              download_seq2seq  [emitted]  download_seq2seq
  download_sequence_labeling.js  4.09 MiB    download_sequence_labeling  [emitted]  download_sequence_labeling
download_text_classification.js   4.1 MiB  download_text_classification  [emitted]  download_text_classification
                   guideline.js  1.94 MiB                     guideline  [emitted]  guideline
    demo_text_classification.js  1.91 MiB      demo_text_classification  [emitted]  demo_text_classification
                       label.js   1.9 MiB                         label  [emitted]  label
                    projects.js  1.86 MiB                      projects  [emitted]  projects
                     seq2seq.js  4.15 MiB                       seq2seq  [emitted]  seq2seq
           sequence_labeling.js  4.22 MiB             sequence_labeling  [emitted]  sequence_labeling
                       stats.js  4.42 MiB                         stats  [emitted]  stats
              upload_seq2seq.js   4.1 MiB                upload_seq2seq  [emitted]  upload_seq2seq
    upload_sequence_labeling.js   4.1 MiB      upload_sequence_labeling  [emitted]  upload_sequence_labeling
  upload_text_classification.js   4.1 MiB    upload_text_classification  [emitted]  upload_text_classification
Entrypoint index = index.js
Entrypoint sequence_labeling = sequence_labeling.js
Entrypoint document_classification = document_classification.js
Entrypoint seq2seq = seq2seq.js
Entrypoint projects = projects.js
Entrypoint stats = stats.js
Entrypoint label = label.js
Entrypoint guideline = guideline.js
Entrypoint demo_text_classification = demo_text_classification.js
Entrypoint demo_named_entity = demo_named_entity.js
Entrypoint demo_translation = demo_translation.js
Entrypoint upload_seq2seq = upload_seq2seq.js
Entrypoint upload_sequence_labeling = upload_sequence_labeling.js
Entrypoint upload_text_classification = upload_text_classification.js
Entrypoint download_seq2seq = download_seq2seq.js
Entrypoint download_sequence_labeling = download_sequence_labeling.js
Entrypoint download_text_classification = download_text_classification.js
 [1] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/sequence_labeling.js 52 bytes {sequence_labeling} [built]
 [2] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/document_classification.js 52 bytes {document_classification} [built]
 [3] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/seq2seq.js 52 bytes {seq2seq} [built]
 [4] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/projects.js 52 bytes {projects} [built]
 [5] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/stats.js 52 bytes {stats} [built]
 [6] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/label.js 52 bytes {label} [built]
 [7] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/guideline.js 52 bytes {guideline} [built]
 [8] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/demo/demo_text_classification.js 52 bytes {demo_text_classification} [built]
 [9] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/demo/demo_named_entity.js 52 bytes {demo_named_entity} [built]
[10] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/demo/demo_translation.js 52 bytes {demo_translation} [built]
[11] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/upload_seq2seq.js 52 bytes {upload_seq2seq} [built]
[12] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/upload_sequence_labeling.js 52 bytes {upload_sequence_labeling} [built]
[13] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/upload_text_classification.js 52 bytes {upload_text_classification} [built]
[14] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/download_seq2seq.js 52 bytes {download_seq2seq} [built]
[16] multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./static/js/download_text_classification.js 52 bytes {download_text_classification} [built]
    + 567 hidden modules
 ｢wdm｣: Compiled successfully.

python logs:
Installing dependencies
Requirement already satisfied: applicationinsights==0.11.7 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 1)) (0.11.7)
Requirement already satisfied: dj-database-url==0.5.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 2)) (0.5.0)
Requirement already satisfied: Django==2.1.7 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 3)) (2.1.7)
Requirement already satisfied: django-filter==2.0.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 4)) (2.0.0)
Requirement already satisfied: django-heroku==0.3.1 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 5)) (0.3.1)
Requirement already satisfied: django-webpack-loader==0.6.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 6)) (0.6.0)
Requirement already satisfied: django-widget-tweaks==1.4.2 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 7)) (1.4.2)
Requirement already satisfied: django-polymorphic==2.0.3 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 8)) (2.0.3)
Requirement already satisfied: django-rest-polymorphic==0.1.8 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 9)) (0.1.8)
Requirement already satisfied: djangorestframework==3.8.2 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 10)) (3.8.2)
Requirement already satisfied: djangorestframework-csv==2.1.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 11)) (2.1.0)
Requirement already satisfied: djangorestframework-filters==0.10.2 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 12)) (0.10.2)
Requirement already satisfied: environs==4.1.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 13)) (4.1.0)
Requirement already satisfied: djangorestframework-xml==1.4.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 14)) (1.4.0)
Requirement already satisfied: Faker==0.8.8 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 15)) (0.8.8)
Requirement already satisfied: flake8==3.6.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 16)) (3.6.0)
Requirement already satisfied: furl==2.0.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 17)) (2.0.0)
Requirement already satisfied: gunicorn==19.9.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 18)) (19.9.0)
Requirement already satisfied: mixer==6.1.3 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 19)) (6.1.3)
Requirement already satisfied: model-mommy==1.6.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 20)) (1.6.0)
Requirement already satisfied: psycopg2-binary==2.7.7 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 21)) (2.7.7)
Requirement already satisfied: python-dateutil==2.7.3 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 22)) (2.7.3)
Requirement already satisfied: pytz==2018.4 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 23)) (2018.4)
Requirement already satisfied: six==1.11.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 24)) (1.11.0)
Requirement already satisfied: seqeval==0.0.6 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 25)) (0.0.6)
Requirement already satisfied: social-auth-app-django==3.1.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 26)) (3.1.0)
Requirement already satisfied: social-auth-core[azuread]==3.0.0 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 27)) (3.0.0)
Requirement already satisfied: text-unidecode==1.2 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 28)) (1.2)
Requirement already satisfied: tornado==5.0.2 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 29)) (5.0.2)
Requirement already satisfied: unittest-xml-reporting==2.5.1 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 30)) (2.5.1)
Requirement already satisfied: whitenoise[brotli]==4.1.2 in /src/venv/lib/python3.6/site-packages (from -r /src/tools/../requirements.txt (line 31)) (4.1.2)
Requirement already satisfied: psycopg2 in /src/venv/lib/python3.6/site-packages (from django-heroku==0.3.1->-r /src/tools/../requirements.txt (line 5)) (2.8.2)
Requirement already satisfied: unicodecsv in /src/venv/lib/python3.6/site-packages (from djangorestframework-csv==2.1.0->-r /src/tools/../requirements.txt (line 11)) (0.14.1)
Requirement already satisfied: marshmallow>=2.7.0 in /src/venv/lib/python3.6/site-packages (from environs==4.1.0->-r /src/tools/../requirements.txt (line 13)) (2.19.2)
Requirement already satisfied: python-dotenv in /src/venv/lib/python3.6/site-packages (from environs==4.1.0->-r /src/tools/../requirements.txt (line 13)) (0.10.2)
Requirement already satisfied: defusedxml>=0.3 in /src/venv/lib/python3.6/site-packages (from djangorestframework-xml==1.4.0->-r /src/tools/../requirements.txt (line 14)) (0.6.0)
Requirement already satisfied: pycodestyle<2.5.0,>=2.4.0 in /src/venv/lib/python3.6/site-packages (from flake8==3.6.0->-r /src/tools/../requirements.txt (line 16)) (2.4.0)
Requirement already satisfied: setuptools>=30 in /src/venv/lib/python3.6/site-packages (from flake8==3.6.0->-r /src/tools/../requirements.txt (line 16)) (41.0.1)
Requirement already satisfied: mccabe<0.7.0,>=0.6.0 in /src/venv/lib/python3.6/site-packages (from flake8==3.6.0->-r /src/tools/../requirements.txt (line 16)) (0.6.1)
Requirement already satisfied: pyflakes<2.1.0,>=2.0.0 in /src/venv/lib/python3.6/site-packages (from flake8==3.6.0->-r /src/tools/../requirements.txt (line 16)) (2.0.0)
Requirement already satisfied: orderedmultidict>=1.0 in /src/venv/lib/python3.6/site-packages (from furl==2.0.0->-r /src/tools/../requirements.txt (line 17)) (1.0)
Requirement already satisfied: numpy>=1.14.0 in /src/venv/lib/python3.6/site-packages (from seqeval==0.0.6->-r /src/tools/../requirements.txt (line 25)) (1.16.3)
Requirement already satisfied: requests-oauthlib>=0.6.1 in /src/venv/lib/python3.6/site-packages (from social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (1.2.0)
Requirement already satisfied: PyJWT>=1.4.0 in /src/venv/lib/python3.6/site-packages (from social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (1.7.1)
Requirement already satisfied: python3-openid>=3.0.10; python_version >= "3.0" in /src/venv/lib/python3.6/site-packages (from social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (3.1.0)
Requirement already satisfied: oauthlib>=1.0.3 in /src/venv/lib/python3.6/site-packages (from social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (3.0.1)
Requirement already satisfied: requests>=2.9.1 in /src/venv/lib/python3.6/site-packages (from social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (2.22.0)
Requirement already satisfied: cryptography>=2.1.1; extra == "azuread" in /src/venv/lib/python3.6/site-packages (from social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (2.6.1)
Requirement already satisfied: Brotli; extra == "brotli" in /src/venv/lib/python3.6/site-packages (from whitenoise[brotli]==4.1.2->-r /src/tools/../requirements.txt (line 31)) (1.0.7)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /src/venv/lib/python3.6/site-packages (from requests>=2.9.1->social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (3.0.4)
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /src/venv/lib/python3.6/site-packages (from requests>=2.9.1->social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (1.25.2)
Requirement already satisfied: certifi>=2017.4.17 in /src/venv/lib/python3.6/site-packages (from requests>=2.9.1->social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (2019.3.9)
Requirement already satisfied: idna<2.9,>=2.5 in /src/venv/lib/python3.6/site-packages (from requests>=2.9.1->social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (2.8)
Requirement already satisfied: asn1crypto>=0.21.0 in /src/venv/lib/python3.6/site-packages (from cryptography>=2.1.1; extra == "azuread"->social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (0.24.0)
Requirement already satisfied: cffi!=1.11.3,>=1.8 in /src/venv/lib/python3.6/site-packages (from cryptography>=2.1.1; extra == "azuread"->social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (1.12.3)
Requirement already satisfied: pycparser in /src/venv/lib/python3.6/site-packages (from cffi!=1.11.3,>=1.8->cryptography>=2.1.1; extra == "azuread"->social-auth-core[azuread]==3.0.0->-r /src/tools/../requirements.txt (line 27)) (2.19)
Initializing database
Database unavailable on attempt 1/60: could not connect to server: Connection refused
        Is the server running on host "postgres" (<IP_ADDRESS>) and accepting
        TCP/IP connections on port 5432?
Operations to perform:
  Apply all migrations: admin, auth, contenttypes, server, sessions, social_django
Running migrations:
  Applying contenttypes.0001_initial... OK
  Applying auth.0001_initial... OK
  Applying admin.0001_initial... OK
  Applying admin.0002_logentry_remove_auto_add... OK
  Applying admin.0003_logentry_add_action_flag_choices... OK
  Applying contenttypes.0002_remove_content_type_name... OK
  Applying auth.0002_alter_permission_name_max_length... OK
  Applying auth.0003_alter_user_email_max_length... OK
  Applying auth.0004_alter_user_username_opts... OK
  Applying auth.0005_alter_user_last_login_null... OK
  Applying auth.0006_require_contenttypes_0002... OK
  Applying auth.0007_alter_validators_add_error_messages... OK
  Applying auth.0008_alter_user_username_max_length... OK
  Applying auth.0009_alter_user_last_name_max_length... OK
  Applying server.0001_initial... OK
  Applying sessions.0001_initial... OK
  Applying social_django.0001_initial... OK
  Applying social_django.0002_add_related_name... OK
  Applying social_django.0003_alter_email_max_length... OK
  Applying social_django.0004_auto_20160423_0400... OK
  Applying social_django.0005_auto_20160727_2333... OK
  Applying social_django.0006_partial... OK
  Applying social_django.0007_code_timestamp... OK
  Applying social_django.0008_partial_timestamp... OK
Superuser created successfully.

I tested the docker-compose setup with WSL+Ubuntu-16.04 (docker-compose 1.24.0 and docker 18.06.1-ce) as well as a real install of Ubuntu-18.04 (docker-compose 1.21.2 and docker 18.09.6) and everything works fine. Perhaps there's something different about CentOS.
A couple of avenues to investigate:

What's the version of docker-compose on your system?
Can you access http://<IP_ADDRESS>:8080 in your browser?

@c-w thanks for attention, and the version of docker-compose is docker-compose version 1.24.0, build 0aa59064
and the http://<IP_ADDRESS>:8080 like this

@littleji I'm unable to reproduce the behavior you reported on a fresh CentOS 7.5 install (see the steps below for my setup) so there may something particular with your machine. Could you please confirm that the steps look reasonable to you?
Step 1: Create a new CentOS VM on Azure and open ports 22, 8000 and 8080
# create a new virtual  machine
$ az group create -n {SOME_GROUP_NAME} -l eastus
$ az vm create -n {SOME_VM_NAME} -g {SOME_GROUP_NAME} --image Centos

# open ports for doccano docker-compose deployment
$ az vm open-port -n {SOME_VM_NAME} -g {SOME_GROUP_NAME} --priority 100 --port 22
$ az vm open-port -n {SOME_VM_NAME} -g {SOME_GROUP_NAME} --priority 101 --port 8000
$ az vm open-port -n {SOME_VM_NAME} -g {SOME_GROUP_NAME} --priority 102 --port 8080

Step 2: Connect to the VM
$ az vm list-ip-addresses -n {SOME_VM_NAME} -g {GROUP_NAME} -o table
$ ssh {INSERT_IP_OF_VM_HERE}
>>> cat /etc/centos-release
CentOS Linux release 7.5.1804 (Core)

Step 3: Setup Docker (guide)
>>> sudo docker version
Client:
 Version:           18.09.6
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        481bc77156
 Built:             Sat May  4 02:34:58 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.6
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       481bc77
  Built:            Sat May  4 02:02:43 2019
  OS/Arch:          linux/amd64
  Experimental:     false

>>> sudo docker-compose version
docker-compose version 1.24.0, build 0aa5906
docker-py version: 3.7.2
CPython version: 2.7.5
OpenSSL version: OpenSSL 1.0.2k-fips  26 Jan 2017

Step 4: Setup doccano
# fetch code
>>> curl -LfsSO https://github.com/chakki-works/doccano/archive/ad01f527a2128a18149bef30edbc1f1f1f3a887c.zip
>>> unzip ad01f527a2128a18149bef30edbc1f1f1f3a887c.zip
>>> cd doccano-ad01f527a2128a18149bef30edbc1f1f1f3a887c

# ensure webpack output can be accessed remotely
>>> sed -i 's@`http://<IP_ADDRESS>:@`http://{INSERT_IP_OF_VM_HERE}:@g' app/server/webpack.config.js

# run doccano
>>> sudo docker-compose pull
>>> sudo docker-compose up

Step 5: Access projects page
Go to http://{INSERT_IP_OF_VM_HERE}:8000/projects/ and log in with admin:password.

I am having the same issue, when i did a fresh install. Everything was working fine before but now i got the same error as mentioned in the above. project call is happening on port ip:8000 and projects.js call is happening on localhost:8080.
@littleji where you able to solve that ?

I am having the same issue, when i did a fresh install. Everything was working fine before but now i got the same error as mentioned in the above. project call is happening on port ip:8000 and projects.js call is happening on localhost:8080.
@littleji where you able to solve that ?

sorry to say I still suffer this issue, I have already went back  and use the older version, this is the docker compose file
version: '3'
services:
  doccano:
    image:  chakkiworks/doccano
    container_name: doccano
    hostname: doccano
    restart: always
    ports:
      - "18080:8080"
      - "10080:80"
    networks:
      - dev
networks:
  dev:
    driver: bridge
    ipam:
      driver: default

That docker-compose file doesn't look like the one in the repo. Any particular reason why you're not using or adapting the docker-compose file in the repo?

I have used the docker image to deploy and did a fresh install, couldn't solve using doccano compose.

Is the intention to keep on using Webpack dev server in production? 10 minutes of debugging this led me to believe the root cause of this is that the bundle needs to be referred with a full url, as the webpack server runs on another port.
Best way to fix this would probably be to build the assets before the web server starts / release with assets already build. First aid for this specific issue could also be to assign a new Django route that proxies requests to the webpack dev server. After this the web browser wouldn't have to specifically know where the dev server is located and you could refer javascript assets with relative paths.

@rikukissa As mentioned in the readme, the docker-compose file included in this repository is intended for development purposes. For production usage, please use the Docker image which does not use webpack at runtime.

Hello,
may be change host value "<IP_ADDRESS>" to variable ${webpackHost}. Thus, it will allow to set the external address.
https://github.com/chakki-works/doccano/blob/master/app/server/static/webpack.config.js#L28
And into docker-compose setup WEBPACK_HOST: "<IP_ADDRESS>" as external address.

I am facing the same issue. Is there a workaround for this?

I have not yet seen a way to reproduce this unfortunately. If someone can share the exact steps that lead to the error in a way that I can reproduce it, I can look into investigating this more.

Yeah typically this problem arises during upgrades on existing installations. Its so easy to miss building the server static pages with the npm build commands.

We're currently caching node_modules and the python virtualenv in the docker-compose file to speed up the development loop. This means that if any of the project's dependencies changed, a clean stop via docker-compose down --volumes is required.
The docker-compose file is intended as a development tool only, not as a production deployment mechanism. For production deployment, I'd recommend to use the official Docker build.

The topic is drifted to another issue. Please raise a new issue if you want to improve deployment.


Changing behavior of the HTML tables/headings/cells to left aligned as default.

This PR will fix the issue of "https://github.com/microsoft/vscode/issues/131339"
Changed all table cells/headings in HTML output of notebooks to left aligned as default.

Appreciate the PR but the issue #131339 is marked as "under-discussion" so the team needs to decide on what to do here before we proceed. We likely need a better solution where Jupyter notebooks can get a special tag added to the output to determine alignment.


Flipper Hermes Debugger doesn't connect on custom metro port

Description
I am trying to connect flipper with a metro server running on 8085. I am able to see the react-native logs and the react devtools but when I open Hermes debugger it shows me "Metro is connected but no Hermes apps were found". This however works completely fine if I am using default metro port (8081).
The targeted list comes as an empty array if I manually go to http://localhost:8085/json
Steps To Reproduce
Enable hermes in a react native project

npx react-native start --port=8085
npx react-native run-android
Open Flipper via terminal: env METRO_SERVER_PORT=8085 open /Applications/Flipper.app

Environment
React Native Version: 0.65.1
React Version: 17.0.2
Version of flipper SDK to use with React Native: 0.93.0

I've got the same issue. Here's my react-native info:
System:
    OS: macOS 11.6.1
    CPU: (8) x64 Apple M1
    Memory: 22.46 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.17.6 - /usr/local/bin/node
    Yarn: 1.22.11 - /usr/local/bin/yarn
    npm: 7.24.1 - /usr/local/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.2 - /opt/homebrew/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
    Android SDK:
      API Levels: 24, 29, 30, 31
      Build Tools: 28.0.3, 29.0.2, 30.0.2, 31.0.0
      System Images: android-24 | ARM 64 v8a, android-24 | ARM EABI v7a, android-24 | Google APIs ARM 64 v8a, android-25 | Google APIs ARM 64 v8a, android-29 | Google APIs ARM 64 v8a, android-29 | Google Play ARM 64 v8a, android-30 | Google APIs ARM 64 v8a, android-30 | Google Play ARM 64 v8a, android-31 | Google APIs ARM 64 v8a, android-31 | Google Play ARM 64 v8a, android-32 | Google Play ARM 64 v8a
      Android NDK: Not Found
  IDEs:
    Android Studio: 2020.3 AI-203.7717.56.2031.7621141
    Xcode: 13.1/13A1030d - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.10 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: ^6.1.0 => 6.1.0
    react: 17.0.2 => 17.0.2
    react-native: =0.66.4 => 0.66.4
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found


Automatic download happens too late

The following bit of code (build.gradle method in the README) downloads the translations into the source AFTER the project was built and not before:
build {
        dependsOn downloadTranslations
}

Also I think the .timestamp file might be useless when using that method?

Yes, the .timestamp file shouldn't be there. The fact that it gets generated is a bug; it should only be generated if you're using this as a mod so it doesn't try every time someone starts Minecraft.
But I can't reproduce the "downloads the translations AFTER the project was built" part. I cloned one of my mods into a new directory, ran gradle build, and verified that the output jar had the translation files (so was built after downloading was complete):
git clone git@github.com:gbl/DurabilityViewer.git
cd DurabilityViewer/
git submodule init
git submodule update
~/SoftwareProjects/MyProjects/MinecraftMods/Fabric/gradlew build

jar tf build/libs/durabilityviewer-1.16.4-fabric0.25.1-1.9.jar

the jar file included all of the language json files.
(The submodule stuff is just because I keep the versioning for all my mods in a separate submodule so I don't have to edit a ton of settings files, all in the same way, whenever MC or Fabric updates, it has nothing to do with the crowdin process And for the same reason, I keep gradle in a central place so I don't have to pollute each and every repo with gradle file copies).
Could you verify this, and if it's reproducable, give me an example where it fails?

 My last example worked because the language files are commited to the repo. If I remove them just before building, they're not in the jar. Going to check into that.


Email/SMS notifications and a VPN

First of all, i want to thank you guys for making such a useful and simple software.
The only real issue i have is that my notifications work fine when i'm on my actual machine but when i switch to a VPN, none of these notifications work.
This is the error i receive: couldn't send email Invalid login: 534-5.7.14
I'm using Gmail and i already set it up to allow less trustworthy sign-ins.

Odd, I have mine going through a VPN and everything is working perfectly fine. Are you sure you have your .env set up correctly?

Yeah. I have it working fine when I'm going through my regular machine. I
just get an error when using nord vpn.
Here is a screenshot of on and Off.
But listen, I'll deal with it. I don't want you to have to focus on this
issue if a solution is not on hand.
Again, thank you for creating this open software.
On Wed, Sep 30, 2020, 2:09 AM gonkar193<EMAIL_ADDRESS>wrote:

Odd, I have mine going through a VPN and everything is working perfectly
fine. Are you sure you have your .env set up correctly?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jef/nvidia-snatcher/issues/370#issuecomment-701177790,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALWF4UFJTLNMI3F4GOUBFFTSILDSBANCNFSM4R5ASQFQ
.

Maybe the smtp relay is blocking the VPN external IP?

Firstly, thank you for creating the wonderful piece of software. I've tried all the solutions and I still cannot get the program to notify me via email or sms. I've turned on less secure app access. I've tried plugging in the default smtp info for gmail. What am I doing wrong? any suggestions?

That's gotta be frustrating. Are you also running in a VPN?

Hello Jef,
no problem somebody in your discord helped me out. We both don't know what
it was copied his config and everything worked.
P.S. I know you are busy is there any chance you will add more Canadian
stores to the project in the future? Like Canada Computers, Memory Express
On Tue, Nov 3, 2020 at 1:15 AM Jef LeCompte<EMAIL_ADDRESS>wrote:

That's gotta be frustrating. Are you also running in a VPN?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jef/nvidia-snatcher/issues/370#issuecomment-720926252,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARNA4QCOW7YDSCW6NSNZHATSN6NZ5ANCNFSM4R5ASQFQ
.

I don't know all of those stores and rely a lot on contributors. But it's definitely a possibility!

Where should I put the suggestion?
On Tue., Nov. 3, 2020, 17:59 Jef LeCompte<EMAIL_ADDRESS>wrote:

I don't know all of those stores and rely a lot on contributors. But it's
definitely a possibility!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jef/nvidia-snatcher/issues/370#issuecomment-721418391,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARNA4QHJ377U2VXUIIGCT4LSOCDOLANCNFSM4R5ASQFQ
.

If you want to create a new issue there, that works great.


Sum aggregates nullable to non-nullable

Shouldn't null + null be null and not 0?
public static IObservable<Decimal> Sum<T>(this IObservable<IChangeSet<T>> source, Func<T, Decimal> valueSelector) {...}

public static IObservable<Decimal> Sum<T>(this IObservable<IChangeSet<T>> source, Func<T, Decimal?> valueSelector) {...}

The overload 2 can be covered by valueSelector when using overload 1. The null sum scenario however is impossible at the moment.

That's a fair point.
I will take a look at it as soon  as i can,  unless of course you would like to contribute?

I am a basic git user, but I will try to see how easy Microsoft made it for people like me in VS 2015.

Github for Windows combined with the visual studio add in are excellent tools for the job

No need for this anymore.


[docs] List slots in MUI Base components documentation

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

Closes  #35791
Changes:

For every Base component, this PR creates ${ComponentName}Slots interface for slots prop (inside the interface, it has the JSDoc default value and description for each slot).
Parses the JSDoc for ${ComponentName}Slots interfaces and updates API JSON files
Create a UI for "Slots" section in API Doc, which displays name, type, default and description of each slot
For every Base component, this PR sets default value for slots prop and add JSDoc default value for slots (hence slots in "Props" section of the API doc now has a default value); UPDATE: Reverted this after realising that setting default values to slots prop brings implementation changes

Preview: https://deploy-preview-36104--material-ui.netlify.app/base/api/select-unstyled/#slots <- SelectUnstyled API Doc

Perhaps it wouldn't be that difficult to get to the description of {ComponentName}UnstyledProps.slots directly instead.

Are you suggesting that we add default value for slots prop like { root: 'span', badge: 'span' } and use this to parse default values of each slot?

Instead of Type column, should it be class name instead? I think it is more useful because Type will always be ElementType for all slots. cc @michaldudak

Are you suggesting that we add default value for slots prop like { root: 'span', badge: 'span' } and use this to parse default values of each slot?

Only in JSDoc, though (unless it will cause linting errors saying that the prop must be also initialized in code).

Instead of Type column, should it be class name instead? I think it is more useful because Type will always be ElementType for all slots.

Great idea! We don't have slot class names documented anywhere, so it'll come in handy for sure.

Only in JSDoc, though (unless it will cause linting errors saying that the prop must be also initialized in code).

Yes, the code and the types declared in JSDoc must match to avoid the errors

I added to the documentations the slot class names as @siriwatknp suggested.

Looks good! I'll do a more thorough review a bit later.
What do you think about changing the "Global class" title to "Default class"? Soon, these classes will have the possibility of being removed (#35963), so IMO it makes sense to underline they are applied by default.

What do you think about changing the "Global class" title to "Default class"? Soon, these classes will have the possibility of being removed (https://github.com/mui/material-ui/pull/35963), so IMO it makes sense to underline they are applied by default.

Yes, it sounds better. On my way.

Now that I look at it, the "Default" column feels a bit unclear next to "Default classes":

Perhaps changing "Default" to "Default value" could make it easier to undersdtand.

Agree. I renamed it.


Issue 285

Added "-keepattributes EnclosingMethod" proguard rule that suppresses "Ignoring InnerClasses attribute for an anonymous inner class" warning.
Additionally updated gradle plugin and wrapper version, build tools version, compile sdk, target sdk and appcompact version to latest final version.

Ok for proguard fix.
As for gradle update, wrapper and build tools update, @moagrius will decide on this. Although i also updated the version like you for my personal use, i just added those modifications to my git stash so i can go back and forth when i need to make a PR.

i'm not comfortable upgrading gradle to 2.0 yet - we're still on 1.x at work since there were problems with plugins still lingering...  if you reduce this to just the proguard stuff, i'll merge.
thanks for contributing

Reverted the gradle update commit.

Thank you!

Thank you @AndrazP  I add "-keepattributes EnclosingMethod" in my proguard file, and it works. Thanks.

Worked for me too :)


Ignore SIGPIPE

I had initially included two other changes in this:

Stopping the deliverSignals goroutine when the process exists.
Iterating over the received signals so multiple are delivered.

It might be worth tackling these later.


✨ Support multi line +ignore directive

What are you trying to do?
Currently, +ignore doesn't support multi-line declaration so I need to declare it on a single line. What I want to purpose is make it support multi-line. For example:
// +ignore=[
//      "**/*",
//      "!generated/",
//      "!src/",
//      "!scripts/",
//      "!composer.json",
//      "!composer.lock",
//      "!LICENSE",
//      "!README.md"
//  ]

Why is this important to you?
Single-line ignore is hard to read when they're grow larger. :(
How are you currently working around this?
No response

/cc @jedevc

I asked for this here:

https://github.com/dagger/dagger/pull/7744#issuecomment-2274122714

Feedback:

I need to check how I can parse that but that must be possible.

Hm, you want parsePragmaComment. This is tricky, currently it's all assumed in one line with a regexp.
Being able to do opening/closing braces means the language is no longer regular, so we won't be able to use regexp for it. I'm not confident there's a simple way to do it (but I'm happy to do it in a follow-up) - I don't think we should delay this PR for that though.

@helderco Yeah, I open it after discussed with Justin at https://discord.com/channels/707636530424053791/708371226174685314/1282767180311695382.


Graphical applications aren't responding to mouse inputs on specific monitor configurations

Windows Version
Microsoft Windows [version 10.0.22621.1992]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 22.04
Other Software
Any X Server based applications installed in a WSL distro
Tested with:
JetBrains DataGrip 2020.3.2
virt-manager 4.0.0
Firefox 116.0
Repro Steps

Have 3 monitors, primary monitor next to the secondary and a third configured on top of the primary one.
Start any graphical application
Use mouse on the interface

Expected Behavior
When the third monitor is configured as "under" the primary monitor, mouse interactions are working as shown on this screenshot:

Actual Behavior
When the third monitor is configured as "on top" of the primary monitor, the window can't be interacted with the mouse as shown on this screenshot:

Diagnostic Logs
No response

I have the same issue. I work with laptop screen and external monitor - the issue occur no matter of displays arrangement or which is set as primary. It works only when I unplug the external monitor.
I can confirm the issue is related with the cursor - whenever I want to click on task bar it actually clicks few line below on menu bar, in the editor when I click on specific line it set cursor a few lines below...
Also I noticed that WSLg window does not have that frame around any more, like below, so it might be related

Intellij IntelliJ IDEA 2023.2
Windows 11 22H2 - Version 10.0.22621 Build 22621
WSL version: <IP_ADDRESS>
WSLg version: 1.0.51

I downgraded IntelliJ to version 2023.1 and this issue does not occur. Also that white window frame got back.
Then I thought that it might be an issue with New UI of IntelliJ. I got back to 2023.2, disabled New UI in settings, restarted it and it worked. Then I re-enable New UI and restarted IntelliJ and it works without any issue now.


Add support for React v16 in react-router v3

Thank you for building react-router, it's amazing!
I'm using react-router v3 on a project and the jump to v4 is quite significant so I'll be putting it off for a while.
At the moment, React v16 + react-router v3 seem to have an issue because of the usage of PropTypes directly from React (support dropped in React v16).
I get this error when compiling my project:
path/to/myproject/node_modules/react-router/lib/PropTypes.js:8
var func = _react.PropTypes.func,

Could there please be a v3.x patch released to support React v16?

Already done. Check version 3.2.0

Sweet, you're the best!

I got the same issue on React v16 + react-router v4.2.0. Please check it out! Thank you.


Add correct VRF field to InterfaceForm, other DCIM form fixes

Closes: #4709
What's Changed

Change a number of DCIM forms ModelChoiceField to DynamicModelChoiceField.
Make device-component edit forms include the device as a regular form field so that it can be used in query_params.

This is the base change needed to address #4709.

Add correctly filtered VRF field (referencing the device field via query_params) to InterfaceForm.
Make VMInterface edit form include the VM as a regular form field so that it can be used in query_params.
Add missing ip_addresses field to InterfaceCreateForm.
Add missing label/help_text to mtu field in InterfaceCreateForm.
Change order of fields in interface edit template to match the order in the interface create view.

TODO

[x] Explanation of Change(s)
[x] Added change log fragment(s) (for more information see the documentation)
[x] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
n/a Documentation Updates (when adding/changing features)
n/a Example Plugin Updates (when adding/changing features)
n/a Outline Remaining Work, Constraints from Design

Change a number of DCIM forms ModelChoiceField to DynamicModelChoiceField.

Should this be added to our best practices and/or nautobot-pylint? If so, can you do that, since if I do that I am not able to understand the nuance if this is always preferred.

Change order of fields in interface edit template to match the order in the interface create view.

Same as previous.

Change a number of DCIM forms ModelChoiceField to DynamicModelChoiceField.

Should this be added to our best practices and/or nautobot-pylint? If so, can you do that, since if I do that I am not able to understand the nuance if this is always preferred.

Not a bad idea. There will always be exceptions, but in general yes the DynamicModelChoiceField and DynamicModelMultipleChoiceField should preferred as they avoid the server-side overhead of pre-rendering all possible options of a non-dynamic Model(Multiple)ChoiceField.

Change order of fields in interface edit template to match the order in the interface create view.

Same as previous.

This is a fairly narrow special case (we don't often have a different template/form for "create" versus "edit" operations) so I don't think so.

From your summary:

Add missing label/help_text to mtu field in InterfaceCreateForm

That should be mode right?

From your summary:

Add missing label/help_text to mtu field in InterfaceCreateForm

That should be mode right?

Yup!


Expose API to iov-wallet (in process)

We need to deprecate weave-js and have the iov-wallet team use web4. To do so, they need to reproduce the current functionality with the new library.

[x] Review iov-wallet code to see what they need
[x] Meet with iov-wallet team to coordinate on the effort
[x] Implement missing endpoints (wrappers over our functionality)
[x] Integrate on a branch of iov-wallet
[x] Package and release (0.0.1? 0.1.0?) so they can use this code externally

Done :)


  So, moving to a more meaningful string to describe successful completion of the submission.

manually tested:
17:43 $ make check
>>> endorsement-provisioning: OK

manually tested:
17:43 $ make check
>>> endorsement-provisioning: OK

This change needs an equivalent change in the README.md file also.  Could you please make the change together ?


[Feature] RedisConfig::from_url should handle redis+unix scheme

Describe the solution you'd like
The function RedisConfig::from_url does not seem to handle URLs specifying UNIX socket connections. As such, a URL with the redis+unix scheme such as redis+unix:///run/redis/redis.sock will fail to be parsed. We should handle this scheme accordingly.

Thanks @LordMZTE, added in https://github.com/aembke/fred.rs/releases/tag/v9.1.0

Thank you!


Update 2018-07-06 ~ Annotated Bibliography R1

@opentecture/the-brains
Story
This is the beginning of a tool to help flesh out the open resources repository.
I started to add data to a fork of the repository by hand. This involved much repeated cutting and pasting of text. I quickly came the conclusion that this would generally be a waste of time and effort. And that there must be better ways of gathering and maintaining links to interesting web sites.
I think this little project - to create interactive annotated visual 'bibliographies' needs several more updates before we decide if it is meeting its mission. When it's beginning to look good then we can decide whether or not ta a a build version to the 'open resources' repo.
Concept
There are many excellent lists on the web, For example:

https://frontendmasters.com/books/front-end-handbook/2018/tools/css.html
https://github.com/sindresorhus/awesome
https://github.com/asciimoo/ListOfGithubLists

You can spend many enjoyable hours exploring the links in these lists.  There are several issues with this.

Given hundreds of links, how can you prioritize what you want to see?
Having seen a number of good pages, how can you come back to the list and return to the pages you like and not return to the pages you did not feel are useful to you?
Given hundreds of links, how can you use search tools to help you find sites of current interest?

Mission
An annotated visual bibliographies of web pages may be of use in helping you research a project, come up to speed in a field you are unfamiliar with and help give you reminders of what you have seen already.
Full Screen: Annotated Bibliography R1

Given a JavaScript array of URLs
Fetches the content of the home page
Parses text using DOMParser
Extracts and displays the title and description
Displays the favicon - very work in progress
Displays thumbnails of images from the home page

Issues / To Do

Add ability to export data to a Markdown file so it can become part of a series of static pages

The idea being that the static page might be regenerated and updated several times a year

The title 'annotated bibliography' may cause people to think this project is about gathering citations to printed books. It is not.
The favicon feature should not display and empty image if the favicon is not found
Currently on only a single sort of favicon is searched for. There are several common ways of linking to favicons. The script should add more of the ways of capturing them
Currently only images with absolute URLs are displayed, An ability to display images with relative URLs should be added
Currently no body text is searched for or displayed. This could be added
Add ability to add data from a Gist or other external file to particular entries
Add ad hoc query capabilities

@opentecture/the-brains
Annotated Bibliography R2
Getting better


Adding the possibility to disable the PlayerInteractEvent use in the config

This PR is incomplete compared to https://github.com/Zrips/Jobs/pull/1278
(this only remove lore check, not name check)


Enable to specify project id in OpenStack OIDC auth

Enable to specify project id in OpenStack OIDC auth
Description
In current implementation the OpenStack OIDC auth the first project available is selected.
This PR enables to specify the project id using the domain_name (as the tenant_name attribute is used to specify the protocol). The domain_name attribute can be used either to select the domain name in case of domain scoped token or to select the project name in case of project scoped token
Status

done, ready for review

Checklist (tick everything that applies)

[x] Code linting (required, can be done after the PR checks)
[ ] Documentation
[x] Tests
[x] ICLA (required for bigger changes)

Codecov Report

Merging #1293 into trunk will increase coverage by <.01%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##            trunk    #1293      +/-   ##
==========================================
+ Coverage   85.95%   85.95%   +<.01%
==========================================
  Files         359      359
  Lines       73911    73916       +5
  Branches     6705     6708       +3
==========================================
+ Hits        63530    63535       +5
+ Misses       7699     7698       -1
- Partials     2682     2683       +1

Impacted Files
Coverage Δ

libcloud/test/common/test_openstack_identity.py
98.06% <50%> (ø)
:arrow_up:

libcloud/common/openstack_identity.py
75.89% <71.42%> (-0.11%)
:arrow_down:

libcloud/test/compute/test_ec2.py
97.9% <0%> (+0.16%)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks for the contribution.
Can you please also open a PR with a corresponding documentation change (ideally with a code example on how to specify a project)?

I went ahead and merged it into trunk, but I would appreciate if you can open a new PR with corresponding documentation and tests change.


feat: include all features when pulling metadata

Optional package dependencies are not included when pulling metadata. In
some cases these packages are still required to actually build even when
those flags are turned off.
This change effectively adds --all-features to the call of cargo
metadata.
I don't know if this is due to a change in behavior from cargo build,
however, it seems prudent to include all possible dependencies.
Possibly fixes #31

I don't think it is desirable to add all features for any package by default, although there should be an option to choose which features to enable.

This is not actually enabling features, just including all of the crate uri definitions so the files are downloaded by portage in the eventual ebuild.
The offline version of cargo build performed by the cargo.eclass will fail if it cannot retrieve files for optional dependencies even if they are not enabled.  I discovered this while developing an ebuild for i3status-rust. In this case, the Cargo.toml includes an optional profile flag which depends on cpuprofiler and profiling. The proto ebuild generated by cargo-ebuild omitted the crate entries for these components and several of their dependencies. Once I included them via the change in this pull request the class built successfully.
The ebuild author still has to control the feature flags which are provided to cargo_src_compile to actually cause these components to build.

But what if you enable a feature that actually removes a dependency and adds another?
Please try generating the ebuild using the latest git version (0.3.2), as now it uses Cargo.lock to retrieve the dependency tree.

Ah. They now seem to be generating the same code so I'm not sure whether my change actually does anything.
At some level I think we're talking past each other, although, perhaps I'm not fully understanding rust.
As the features are enabled at compile time what possible harm is there to downloading additional crates which might not be used by the enabled features? As I understand it, the crate URIs are simply used by cargo.eclass to retrieve relevant sources. I think I've seen ebuilds in which use flags also change the sources which are downloaded, however, that seems needlessly complicated to manage, particularly for something like rust crates.
I think it's actually desirable to have all the crates as an ebuild author may configure features dynamically via use flags. Obviously they'll still need to ensure that use flags which would enable conflicting features cannot be enabled simultaneously but this is nothing new.

I'm just trying to understand possible edge cases so that no cargo-build users would suffer from regressions.
As I've been finding out, there is no way to remove a dependency by enabling a feature, which means that the edge case that I've mentioned can't really happen.
However, the new version which uses Cargo.lock to resolve dependencies already contains any optional dependencies that could be enabled by features or even different architectures, which should already fix the problem that you are facing.

I'm just trying to understand possible edge cases so that no cargo-ebuild users would suffer from regressions.
As I've been finding out, there is no way to remove a dependency by enabling a feature, which means that the edge case that I've mentioned can't really happen.
However, the new version which uses Cargo.lock to resolve dependencies already contains any optional dependencies that could be enabled by features or even different architectures, which should already fix the problem that you are facing.

@cardoe I've tested this patch with rust-analyzer which wasn't working properly before v0.3.1 and surprisingly it leads to the same results as v0.3.2 which uses cargo-lock. So, could this be a better fix for the dependency resolution problems?

Hi there,
I've recently been introduced to this project from the forum. I'm new to Gentoo but have previously been using the cargo tree command to get the required dependencies.
cargo tree --all-features --target all --prefix none

I found this to actually catch all the features required and have tested this against the packages in the repositories and in some of the Bugzilla posts.
Using the --all-features flag is the only way to catch all of these dependencies required by the rebuild to actually build. In effect, this enables all the dependencies from all of the possible features and will duplicate any dependencies if different versions are required.
Somewhat stupidly I actually implemented this myself before checking for any issues or PRs here. After testing that my theory about using the --all-features does this with the cargo ebuild command it will generate the same output as manually adding the dependencies as they're suggested by the ebuild itself.
I would strongly suggest that this change could be highly valuable and solve some of the issues with missing features.  In essence --all-features is a bad name for this flag as it is better described as all possible dependencies, which in my limited experience is what is required by ebuild.

this project has been moved to https://gitweb.gentoo.org/proj/cargo-ebuild.git
and mirrored to https://github.com/gentoo/cargo-ebuild for pull requests.
this repo still remains but should be marked as deprecated soon.
I've merged this PR and tagged 0.3.2
https://gitweb.gentoo.org/proj/cargo-ebuild.git/commit/?id=148fc783d6c6d00ea35e56e861cb5bc42d8a49c2
it seems to be catching deps better now.
thanks for doing the work.


error ./node_modules/ts-logger-node/dist/index.mjs:2:0 Module not found: Can't resolve 'fs'

I got this error in a next.js project

Are the components server-side or are they client-side?
Client-side won't support 'fs' do to it being a node module requiring access to the file system, not a browser-native package.

I had the logger error in a file that solely contained functions and api calls, not any components. However, the functions were being called in a server component. The package worked as expected in my server components

So you only had an issue in a file that exported functions / API calls but not in actual server components?
I'm just trying to grasp exactly where the problems are experienced and where there are no issues.
I'll try and recreate the issue and see what I can do!

I was trying to call the logger in this file: https://github.com/lritter79/deck-builder-app/blob/main/src/app/functions/cardFunctions.ts
I’m using a function from this file in this server component: https://github.com/lritter79/deck-builder-app/blob/main/src/app/components/deck/deckComponent.tsx

After forking the repo I removed all instances of the ts-logger-node package and received the following build errors:

When I add the following options to your next.config.js I resolve the 'fs' errors.
`const nextConfig = {
webpack5: true,
webpack: (config) => {
config.resolve.fallback = { fs: false };
return config;

},
}`

After forking the repo I removed all instances of the ts-logger-node package and received the following build errors:

When I add the following options to your next.config.js I resolve the fs errors.
const nextConfig = {
  webpack5: true,
  webpack: (config) => {
    config.resolve.fallback = { fs: false };

    return config;
  }
}

Adding this info to the docs for now, will try and add a Next option to the install.


Rconcmd Issue

All commands issued with rconcmd produce the response "Empty response at -e line 12."
arkmanager rconcmd "broadcast Hello" @server1 is the syntax that I have been using.
Any ideas as to what could be causing this response?

Does the ServerAdminPassword in your config contain any special characters?  Is the ServerAdminPassword set?

The ServerAdminPassword is set for both servers. Neither one uses anything outside of A-Z, 0-9.

What is the output of arkmanager --version

Version: 1.6
Channel: master
Commit: 0a02cc2
Release Tag: v1.6.03
Blob SHA: 9a322896756f522a84997fe882bb8c0470cbedd2

Please try upgrading arkmanager to v1.6.04

That appears to have worked, Thanks!


Provide options for different SQL dialects

Please provide an option switch for generating the SQL statement for different SQL dialects like PostgreSQL, SQLite, or MySQL/MariaDB.

I've made a few updates regarding this, please have a look and let me know if this is the direction you were referring to.

Awesome. Yes, that's what I was thinking of. Works great.
Thank you.


Databricks notebook task not found

Describe the bug
Databricks notebook task not found
To Reproduce
Steps to reproduce the behavior:

run-through Purview-ADB-Lineage-Solution-Accelerator
Databricks objects, look for Databricks Notebook Tasks

Expected behavior
Expecting 67 objects loaded:

Only finding 3:

Expecting Databricks notebook tasks:

Unable to find:

Logs

Please include any Spark code being ran that generates this error
Please include a gist to the OpenLineageIn and PurviewOut logs
See how to stream Azure Function Logs

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows, Mac]
OpenLineage Version: [e.g. name of jar]
Databricks Runtime Version: [e.g. 6.4, 9.1, 10.1]
Cluster Type: [e.g. Job, Interactive]
Cluster Mode: [e.g. Standard, High Concurrency, Single]
Using Credential Passthrough: [e.g. Yes, No]

Additional context
Add any other context about the problem here.

@isantillan1 Thank you so much for going through the solution accelerator!  To generate this situation, did you run the notebook sample provided in the Demo deployment?
If so, you will only see the Notebook and it's Databricks Process child(ren) and not at Notebook Task.  Notebook Task represents a Databricks Notebook job / task as created through the Jobs API.
Does that fit your scenario?

Yes, ran through the 1st step in the Using the Connector to "Run all".
The following steps specifically asks to look for "Notebook Tasks" which is not found.

Click on the "Databricks" section, then click on the "Databricks Notebook" tile which corresponds to the notebook you ran. In the Properties or Related tabs select one of the "Notebook Tasks" which represent a task in a Databricks job.

This is great feedback as well.  @mattsavarino and I will coordinate on addressing this in the README for our next week's release.


Sandbox v1

Hi @eminokic , I'm closing this PR as it currently deletes a README for the de localization.
Feel free to re-open this PR if you can provide context and justification to delete README-de.md
If this is intended to be a draft PR, you can change the state to draft
/close


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-26-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2217

Questions ?
Please refer to the Backport tool documentation


appcenter distribute release failing with "Error: Bearer token authorization is required"

In Bitrise, I do the following script step

npm install -g appcenter-cli
...
appcenter -v
appcenter version 2.14.0
appcenter login --token [REDACTED]
Logged in as XXXXXX
appcenter distribute release -f /bitrise/deploy/app-debug-bitrise-signed.apk -r test -a XXXX/XXXX-QA -g Collaborators --quiet
Error: Command 'distribute release -f /bitrise/deploy/app-debug-bitrise-signed.apk -r test -a XXXX/XXXX-QA -g Collaborators --quiet' failed with exception "Error: Bearer token authorization is required"

This was all working until yesterday. Any ideas?

This ended up being a Bitrise connection issue.


Fix wxextension matching

Changes
asdf-2.14.0+ returns two Extension instances matching the pattern in get_weldx_extension(). So we allow this now and add a version mismatch check.
Another minor change is to add caching to the function, as it is being called for some types, each time one of these types is being serialized. The cache hits, if the extension tuple matches (based on id(), I'd guess).
Related Issues
Closes #825
Checks

[ ] updated CHANGELOG.rst
[ ] updated tests
[ ] updated doc/
[ ] update example/tutorial notebooks
[ ] update manifest file

I am not sure if this is a bug on the asdf side or if something is wrong with the way we implemented our extension
It would be good to test the caching with the quality standard implementation to see if that has any effect

Taking a look in the debugger, other extensions, including asdf standard extensions have this splitted pattern of one extension carrying the tags and another containing the converters. So I doubt that you did something wrong adopting the new pattern (a manifest extension, right?)

If you are afraid, that caching breaks something, I can also just remove the implementation. Probably it doesn't make any difference.
How would I test against the quality standard? I thought the default is activated on import time.

I expect that asdf changes the entrypoint listing implementation, so we do not have duplicates in this list.


build failing?

Indeed: https://travis-ci.org/gnab/remark/builds/327573306

@gnab, any idea?

Duplicate of #502.


Tests fail on macOS: Invalid BAM magic string, Header is not yet read

R version 4.2.3 (2023-03-15) -- "Shortstop Beagle"
Copyright (C) 2023 The R Foundation for Statistical Computing
Platform: powerpc-apple-darwin10.8.0 (32-bit)

> library(testthat)
> library(ompBAM)
>
> test_check("ompBAM")
i Loading ompBAMExample
Exports from /opt/local/var/macports/build/_opt_PPCRosettaPorts_R_R-ompBAM/R-ompBAM/work/.tmp/RtmplqO65p/filef5109cb8fed/ompBAMExample/src/main.cpp:
   int idxstats_pbam(std::string bam_file, int n_threads_to_use = 1, bool verbose = true)

/opt/local/var/macports/build/_opt_PPCRosettaPorts_R_R-ompBAM/R-ompBAM/work/.tmp/RtmplqO65p/filef5109cb8fed/ompBAMExample/src/RcppExports.cpp updated.
/opt/local/var/macports/build/_opt_PPCRosettaPorts_R_R-ompBAM/R-ompBAM/work/.tmp/RtmplqO65p/filef5109cb8fed/ompBAMExample/R/RcppExports.R updated.
i Re-compiling ompBAMExample (debug build)
-- R CMD INSTALL ---------------------------------------------------------------
* installing *source* package ‘ompBAMExample’ ...
** using staged installation
Configuring OpenMP compiler / linker flags for MacOS
** libs
/opt/local/bin/g++-mp-12 -std=gnu++14 -I"/opt/local/Library/Frameworks/R.framework/Resources/include" -DNDEBUG  -I'/opt/local/Library/Frameworks/R.framework/Versions/4.2/Resources/library/Rcpp/include' -I'/opt/local/Library/Frameworks/R.framework/Versions/4.2/Resources/library/zlibbioc/include' -I'/opt/local/Library/Frameworks/R.framework/Versions/4.2/Resources/library/RcppProgress/include' -I'/opt/local/var/macports/build/_opt_PPCRosettaPorts_R_R-ompBAM/R-ompBAM/work/ompBAM/ompBAM.Rcheck/ompBAM/include' -isystem/opt/local/include/LegacySupport -I/opt/local/include  -fopenmp  -fPIC  -pipe -Os -arch ppc  -UNDEBUG -Wall -pedantic -g -O0 -c RcppExports.cpp -o RcppExports.o
/opt/local/bin/g++-mp-12 -std=gnu++14 -I"/opt/local/Library/Frameworks/R.framework/Resources/include" -DNDEBUG  -I'/opt/local/Library/Frameworks/R.framework/Versions/4.2/Resources/library/Rcpp/include' -I'/opt/local/Library/Frameworks/R.framework/Versions/4.2/Resources/library/zlibbioc/include' -I'/opt/local/Library/Frameworks/R.framework/Versions/4.2/Resources/library/RcppProgress/include' -I'/opt/local/var/macports/build/_opt_PPCRosettaPorts_R_R-ompBAM/R-ompBAM/work/ompBAM/ompBAM.Rcheck/ompBAM/include' -isystem/opt/local/include/LegacySupport -I/opt/local/include  -fopenmp  -fPIC  -pipe -Os -arch ppc  -UNDEBUG -Wall -pedantic -g -O0 -c main.cpp -o main.o
/opt/local/bin/g++-mp-12 -std=gnu++14 -dynamiclib -Wl,-headerpad_max_install_names -undefined dynamic_lookup -single_module -multiply_defined suppress -L/opt/local/Library/Frameworks/R.framework/Resources/lib -Wl,-headerpad_max_install_names -Wl,-rpath,/opt/local/lib/libgcc -L/opt/local/lib -lMacportsLegacySupport -arch ppc -o ompBAMExample.so RcppExports.o main.o -L/opt/local/lib/libgcc -lgomp -F/opt/local/Library/Frameworks/R.framework/.. -framework R -Wl,-framework -Wl,CoreFoundation
installing to /opt/local/var/macports/build/_opt_PPCRosettaPorts_R_R-ompBAM/R-ompBAM/work/.tmp/RtmplqO65p/devtools_install_f510baddd99/00LOCK-ompBAMExample/00new/ompBAMExample/libs
** checking absolute paths in shared objects and dynamic libraries
* DONE (ompBAMExample)
Invalid BAM magic string
Header is not yet read
Invalid BAM magic string
Header is not yet read
[ FAIL 2 | WARN 0 | SKIP 0 | PASS 0 ]

══ Failed tests ════════════════════════════════════════════════════════════════
── Failure ('test-examples.R:14:3'): test_ompBAM ───────────────────────────────
.test_idxstats(1, "Unsorted") (`actual`) not equal to 0 (`expected`).

  `actual`: -1
`expected`:  0
Backtrace:
    ▆
 1. └─ompBAM (local) .test_ompBAM() at test-examples.R:14:2
 2.   └─testthat::expect_equal(.test_idxstats(1, "Unsorted"), 0) at test-examples.R:8:2
── Failure ('test-examples.R:14:3'): test_ompBAM ───────────────────────────────
.test_idxstats(2, "scRNAseq") (`actual`) not equal to 0 (`expected`).

  `actual`: -1
`expected`:  0
Backtrace:
    ▆
 1. └─ompBAM (local) .test_ompBAM() at test-examples.R:14:2
 2.   └─testthat::expect_equal(.test_idxstats(2, "scRNAseq"), 0) at test-examples.R:9:2

[ FAIL 2 | WARN 0 | SKIP 0 | PASS 0 ]
Error: Test failures
Execution halted

Hi Sergey,
Seems ompBAM is passing checks and tests on Bioconductor: http://bioconductor.org/checkResults/devel/bioc-LATEST/ompBAM/ . I'm not sure what the problem is on your end.
Platform: powerpc-apple-darwin10.8.0 (32-bit) - I am not familiar with this platform and don't have the capability/resources to troubleshoot why there seems to be problems compiling the test example on this platform. In any case Bioconductor does not support 32-bit platforms as far as I know.

Feel free to experiment with the example package. FYI the "configure" file is inspired by that from R's data.table package and it is used to detect OpenMP compiler on MacOS: https://github.com/Rdatatable/data.table/blob/master/configure

P. S. Maybe there are implicit assumptions of little-endianness?
You may be right.

Feel free to experiment with the example package. FYI the "configure" file is inspired by that from R's data.table package and it is used to detect OpenMP compiler on MacOS: https://github.com/Rdatatable/data.table/blob/master/configure

Yeah, it is broken and I had to fix it for Macports :)

P. S. Maybe there are implicit assumptions of little-endianness?
You may be right.

Could you please advise on how to fix this? I can handle OpenMP, but not sure how to fix endianness.

Could you please advise on how to fix this? I can handle OpenMP, but not sure how to fix endianness.
P. S. Perhaps bitness can be safely ignored: there are plenty of 64-bit Big endian systems, so it makes sense to fix it for those.

You may be right. I will have to look into it and implement a fix in the header files. It may take a while.

@barracuda156 If you are aware of a way to setup a GitHub action on a big endian machine, that would be very helpful as I can't otherwise test any changes

@barracuda156 If you are aware of a way to setup a GitHub action on a big endian machine, that would be very helpful as I can't otherwise test any changes

@alexchwong Unfortunately, no idea on that :(
I can say which archs and which OSs use/support BE, but not sure if GH actions support any of those hardware-wise.
I can do testing on my end however, and normally can do it within a day or maximum two.

Ok. I will have to look into it then, thanks for the bug report.
I'll let you know when I have a fix but it may take a while as I have other work priorities right now, sorry!

@alexchwong Sure, whenever it is convenient for you. Thanks again!

@barracuda156 If you are aware of a way to setup a GitHub action on a big endian machine, that would be very helpful as I can't otherwise test any changes

@alexchwong Could you try Qemu? See: https://blog.r-project.org/2020/05/29/testing-r-on-emulated-platforms/
(There ppc64le is chosen, but several Linux and BSD support ppc32 and ppc64be, and Qemu can emulate those.)

@alexchwong Any update on this?


null variable is converted to 'null' instead of NULL

The docs states this: undefined / null are converted to NULL
I'm using v2.13.0 of this plugin and only undefined values are converted to NULL.
null values are converted to 'null' string, which seems to be a bug, according to the docs.

hi @dekelev the conversion is done via https://github.com/mysqljs/sqlstring library. Can you reduce example to SqlString.format() call and post issue there?

hi @sidorares the issue does not reproduce with a pure example using the sqlstring or mysql modules.
I'll debug the original code tomorrow and will either post the results or close this issue.

@sidorares sorry, my mistake, the variable was wrapped in JSON.stringify before it was added to the query.


Add a boolean indicating if the content of

See http://crbug.com/462209

Hey Benjamin,
I've added some basic tests, made it optional and fit this in into the nice _TOKENS object.

@kalman I've addressed all your feedback except the script tags for the moment.
Please let me know what you think before going further.

@kalman Fixed 80 characters line issue.

For info, here's https://help.github.com/articles/github-flavored-markdown/


Feature to organize Apps in Folders

Describe the solution you'd like
We have a lot of builds in our My Apps pages and it would be great if we could organize the apps inside folders
Describe alternatives you've considered
Better experience on Categorize apps
Additional context
nothing to say

Thanks for the feedback! We don't have any short term plans to add this functionality but we'll consider this in our future planning.
Linking a few other similar requests:
https://github.com/microsoft/appcenter/issues/1752
https://github.com/microsoft/appcenter/issues/352


Fish Token Details

Tasks:

[x] Brownie Updated
[x] FISH Token Contract Added (TO BE VERIFIED by @dharkmattr )
[x] Scripts added for:

[x] FISH Token
[x] Multisig
[x] Staking
[x] Vesting

[x] Basic README Added (to be improved)
[x] General refactoring and formatting.

All the scripts have been moved to this PR for unified experience: https://github.com/DistributedCollective/origins/pull/1


Fix void reader when using numpy 1.15.0

Unittest was not working anymore with Python3 and numpy 1.15.0.

LGTM


Place existing periodic caching behind interface

Goal
Places existing periodic caching behind an interface to obscure the implementation details. I've altered PayloadCachingService so that the interface mostly follows the existing logic for caching right now.
Testing
Relied on existing test coverage.

@bidetofevil I agree - I plan on updating this in a future PR.


Migrate https://github.com/fmi-faim/eicm to faim-ipa.

Closes https://github.com/fmi-faim/eicm/issues/11.

See https://github.com/fmi-faim/faim-ipa/issues/191.


Cannot download the weights for both slim and full

Describe the bug
Cannot download the weights for both slim and full
To Reproduce
Steps to reproduce the behavior:

execute "wget --cut-dirs=5 -nH -r --no-parent --reject "index.html*" https://the-eye.eu/public/AI/models/GPT-NeoX-20B/slim_weights/ -P 20B_checkpoints"
no responding

Expected behavior
can download the weights
Environment (please complete the following information):

GPUs:
Configs:

Additional context
Add any other context about the problem here.

It works for me. What's the error you're getting?

it works now, thanks


Dont delete shared pools when an agent is removed

If a storage pool agent container goes unhealthy, it will get removed
and replaced. This causes the associated agent to get removed and
replaced. This change prevents the storage pool assocaited with the
agent from being removed so that when the new storage pool agent
container comes online, it can be associated with the existing pool.
The logic for associating a new agent container with an existing pool
is already in place in ExternalEventCreate.java
Addresses: https://github.com/rancher/rancher/issues/3333

LGTM


NodeAgent send CSR to CA and writes cert into file.

In NodeAgent server.go, when WorkloadAdded invoked, send CSR request to CA; save the response to file by SecretServer. Currently the server.go implementation lives in node_agent/, will merge with node_agent/na/nodeagent.go later.
Manually tested E2E workflow, found the /etc/certs/root-cert.pem present with expected content.
Next step is to save key cert into paths based on service account and configure the workload to mount directory correspondingly in yaml file.

@incfly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
26bfc631a69d36426ccbdf55e860dd5c11e1d965
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
26bfc631a69d36426ccbdf55e860dd5c11e1d965
link
/test istio-unit-tests

prow/istio-presubmit.sh
26bfc631a69d36426ccbdf55e860dd5c11e1d965
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
26bfc631a69d36426ccbdf55e860dd5c11e1d965
link
/test istio-presubmit

prow/istio-unit-tests.sh
62feb60fd1aa527e8972c428e059d819355b6e56
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
62feb60fd1aa527e8972c428e059d819355b6e56
link
/test istio-unit-tests

prow/istio-presubmit.sh
62feb60fd1aa527e8972c428e059d819355b6e56
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b422f93f1843c23bc97e9f62b9dcf69d03ee8df4
link
/test istio-unit-tests

prow/istio-presubmit.sh
b422f93f1843c23bc97e9f62b9dcf69d03ee8df4
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
b422f93f1843c23bc97e9f62b9dcf69d03ee8df4
link
/test istio-presubmit

prow/istio-unit-tests.sh
b951fe2380b749a364838f087b01c4d0b0bb1745
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b951fe2380b749a364838f087b01c4d0b0bb1745
link
/test istio-unit-tests

prow/istio-presubmit.sh
b951fe2380b749a364838f087b01c4d0b0bb1745
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
200a3c71713c1c8176227a11b59bfb57ab3ee7ee
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Manually tested again to verify cert file expected at /etc/certs/cert-chain.pem, submitting.


Intellisense not suggesting tokens in the same assembly, but different namespace while not having the using statement yet

Environment data
dotnet --info output:
.NET SDK (reflecting any global.json):
 Version:   6.0.101
 Commit:    ef49f6213a

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  12.1
 OS Platform: Darwin
 RID:         osx.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/6.0.101/

Host (useful for support):
  Version: 6.0.1
  Commit:  3a25a7f1cc

.NET SDKs installed:
  3.1.415 [/usr/local/share/dotnet/sdk]
  3.1.416 [/usr/local/share/dotnet/sdk]
  6.0.100 [/usr/local/share/dotnet/sdk]
  6.0.101 [/usr/local/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 3.1.21 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.22 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.1.21 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.22 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.1 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET runtimes or SDKs:
  https://aka.ms/dotnet-download

VS Code version: 1.63.2
C# Extension version: ?
OmniSharp log
Received response for /v2/blockstructure but could not find request.
Received response for /v2/blockstructure but could not find request.
Received response for /v2/getcodeactions but could not find request.

Steps to reproduce
Have an exception class AuthenticationException in namespace Api.Exceptions.
Have a controller SomeController in namespace Api.Controllers.
In SomeController start typing (but do not finish) AuthenticationException without having a using Api.Exceptions at the top of the file.
VSCode will not suggest to autocomplete and automatically add the using statement.
Finish typing AuthenticationException.
VSCode will show a code action (lightbulb at start of line) to add the using Api.Exceptions statement for you.
Expected  behavior
VSCode should suggest autocompleting AuthenticationException after typing a few letters and on pressing tab to accept the autocomplete, it should automatically add the using statement.
Actual behavior
Only suggests via code actions to add the using statement after typing the complete name of the class. For comparison, Jetbrains Rider suggests the correct autocomplete after only typing the first two letters ("Au").
If I already have the using Api.Extensions statement in the file, the autocomplete works correctly after typing a few letters.

Closing as C# extension now supports unimported type completion.


[Hub Generated] Publish private branch 'gachauhan-iprangenew'

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM (Control Plane) API Specification Update Pull Request

Tip: overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

 Click here to see the details of Step 1
Breaking changes review (Diagram Step 1)
If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

 Click here to see the details of Step 2
ARM API changes review (Diagram Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

 Click here to see the diagram footnotes
Diagram footnotes
[1] ARM review queue (for merge queues, see [2])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.

Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[ ] New API version. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[ ] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[ ] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the Diagram Step 2, "ARM API changes Review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

The PR is created based on the updates in the private branch. The updates in the PR has already been reviewed and approved with this PR Azure/azure-rest-api-specs-pr/16281

/azp run typespec requirement

@gachauhan - Please fill out the intake form at the top.

@gachauhan - Signing off for ARM with comments.

/pr RequestMerge

There are a bunch of 'breaking changes have been detected in comparison to the latest preview version' - are those intentional?
https://github.com/Azure/azure-rest-api-specs/pull/27329/checks?check_run_id=20331239163

Merging is blocked
Merging can be performed automatically with 1 approving review.

There are a bunch of 'breaking changes have been detected in comparison to the latest preview version' - are those intentional?
https://github.com/Azure/azure-rest-api-specs/pull/27329/checks?check_run_id=20331239163

The one which is compared to stable version is the expected one but why there is a comparsion between stable and preview version ?

why there is a comparsion between stable and preview version ?

True, it doesn't make as much sense as comparing preview versions with old versions. I think we can ignore it as long as you don't see anything accidentally forgotten.


Handle Ctrl-Key events in EditView & some general, small improvements

Hi!
First of, thank you for cursive!
A rather important thing that popped up while implementing the new TUI-based installer for Proxmox was that the EditView does not handle ^U, ^K etc.
This implements that, plus some tests on top as well.
Also included is the addition of a .get_cursor() method, as well as the clamping of the length in .remove(), two things that would be quite useful to have.
Thanks in advance!

Hi, and thanks for the PR!
I wonder if these could be added with just an OnEventView wrapper around an EditView?
I'm not entirely sure these shortcuts are idiomatic for all users. So I'd love to make it easy for your app to use define them, but I don't think they belong in the default EditView configuration.

Thanks for taking a look!

I wonder if these could be added with just an OnEventView wrapper around an EditView?

Sure, that wouldn't be much trouble either.

I'm not entirely sure these shortcuts are idiomatic for all users.

Well, there pretty much universal across TTY, CLIs and ncurses(-ish) applications/TUIs, so it is somewhat reasonable to expect them to work here too. Thus they are really not idiomatic w.r.t our usecases, that's why I chose to try to get them implemented upstream.

So I'd love to make it easy for your app to use define them, but I don't think they belong in the default EditView configuration.

In a sense that EditView should be a rather "dumb" view, only implementing the bare necessities for text editing? I get that.
I'll drop the relevant commits if that's the way forward.
Are the other two commits (7538f11463a04940d928feb10e1077a7f9436770 and 120c19cb36b9e3fc631ed0408bc97c7673c30a37) acceptable? Especially the former, the latter would be simply nice to have.

Thanks for the work!


Add the ability to cd into target folder

Since a bower-git usually is followed by a cd into that folder and then an npm install or similar, we should consider adding a flag that will cd in to the target directory.

Good idea. Any suggestions of what the flag should be?


Fix leaving lobby issues

Due Date
March 17th
Priority
Medium
Description
When leaving the lobby, the player doesn't actually leave the lobby and is unable to create/join a new lobby
Associated Requirement*
FR-JG1-5
FR-ER1-5

Completed in commit: 9d2db7b83dc36f3aad027d25a0f97d8b6903f539


Cannot write tilde on Portuguese layout keyboard

Using Portuguese layout keyboard on a Yosemite (10.10.5), when I type ~ nothing occurs.
It is kinda problematic because I often want to change directory to cd ~/folder/anotherFolder and I have to do cd; cd folder/anotherFolder for now...

Duplicate. Same problem is discussed here: #213

Yes, this is a duplicate. Closing and we can continue discussion in #213.


check if the font is fully loaded in safari (and not using question mark boxes)

check if the font is fully loaded in safari (and not using question mark boxes)
this is a fix/workaround for #370

Thanks! Do you have a bug report for Safari? I'd like to understand this bug better.

Hi Bramstein, I've reported my bug at https://www.apple.com/feedback/safari.html I hope I get some reply from that. I've tried reproducing this bug without webfontloader but I couldn't reproduct it yet.

Hi @bramstein , I've reported my bug at https://www.apple.com/feedback/safari.html I hope I get some reply from that. I've tried reproducing this bug without webfontloader but I couldn't reproduct it yet.

Struggling with the same problem. Hopefully the fix gets accepted.

@bramstein I didn't get any response from my bug report at Apple, as stated below I cannot report this bug at webkit.
Note: Safari is not WebKit. Safari bugs should be reported to Apple.
https://webkit.org/reporting-bugs/
Do you have some other suggestion?
I think this is fixed in the technology preview because there we can use the native font loading API.
BTW I've got a report this fix doesn't work for Chrome on iOS (where this is fixed in Safari). Chrome on iOS doesn't use the Chrome rendering/javascript engine but the iOS system version of webkit.

Seems like this fix doesn't help me (Sierra, safari 10.1.1) :(

@AvaelKross I'm using the same version and it works, maybe you've got a retina display and use hidpi scaling? If you add console.info(a) to line 282 at src/core/fontwatchrunner.js you might find your "magic number" (please share it with us!).

Looks like '2410' is a magic number for me; retina 15" display. My situation: I'm using webfontloader for a text element on canvas, and on page reload, [?] boxes appear for a second and then replaced with needed font. But different font size breaks text positioning on canvas (because [?] boxes are usually wider than the original symbols). Sometimes box wasn't replaced with needed font, and I guess this case should be fixed now with your code. So actually it may help someone.

My team has struggled with this quite a bit. It seems to me that some workaround (potentially this one, as it is also working for us) should be accepted into this library (with documented edge cases, or maybe an opt-in implementation). Especially in situations where load state accuracy is very important (e.g. drawing on a Canvas) this is a very problematic bug.

@bramstein any updates when this is going to be merged?


Clarify wording, address Issue #45

@csantanapr can you double check to make sure this preserves the original intension.


Importer field names

I'm making Access templates for CoLDP and name in the VernacularName table is a reserved word. I changed the field name to vernacularName in the Access template. Will the importer be able to recognize vernacularName as VernacularName.name? Are there vocab mappings for the field names that I can update?

Access complains about the Name table name being a reserved word, too.

How is this MS Access problem related to the backend? You need to provide an export to CSV/TSV files for the backend importer to work with. And in that process you can rename the fields/table names you had to change because auf reseved names in Access. The importer will not recognize VernacularName(.csv).vernacularName if that is the question


[Bug report] themeConfig is not work

Description
I've configured the navbar, but it didn't work
config.js
module.export = {
  base: '/',
  title: 'VuePress Starter',
  description: 'VuePress Starter Project in Stackblitz',
  themeConfig: {
    navbar: [
      {
        text: '123',
        link: '/guide/',
      },
    ],
  },
};

Reproduction
https://stackblitz.com/edit/vuepress-3tndek?file=docs/.vuepress/config.js
Used Package Manager
npm
System Info
❯ vuepress info

  System:
    OS: Linux 5.0 undefined
    CPU: (4) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: Unknown - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.10 - /bin/yarn
    npm: 7.17.0 - /bin/npm
  Utilities:
    Git: Not Found
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmPackages:
    @vuepress/bundler-vite:  2.0.0-beta.43
    @vuepress/bundler-webpack: Not Found
    @vuepress/cli:  2.0.0-beta.43
    @vuepress/client:  2.0.0-beta.43
    @vuepress/core:  2.0.0-beta.43
    @vuepress/markdown:  2.0.0-beta.43
    @vuepress/plugin-active-header-links:  2.0.0-beta.43
    @vuepress/plugin-back-to-top:  2.0.0-beta.43
    @vuepress/plugin-container:  2.0.0-beta.43
    @vuepress/plugin-docsearch: Not Found
    @vuepress/plugin-external-link-icon:  2.0.0-beta.43
    @vuepress/plugin-git:  2.0.0-beta.43
    @vuepress/plugin-google-analytics: Not Found
    @vuepress/plugin-medium-zoom:  2.0.0-beta.43
    @vuepress/plugin-nprogress:  2.0.0-beta.43
    @vuepress/plugin-palette:  2.0.0-beta.43
    @vuepress/plugin-prismjs:  2.0.0-beta.43
    @vuepress/plugin-pwa: Not Found
    @vuepress/plugin-pwa-popup: Not Found
    @vuepress/plugin-register-components: Not Found
    @vuepress/plugin-search: Not Found
    @vuepress/plugin-shiki: Not Found
    @vuepress/plugin-theme-data:  2.0.0-beta.43
    @vuepress/plugin-toc: Not Found
    @vuepress/shared:  2.0.0-beta.43
    @vuepress/theme-default:  2.0.0-beta.43
    @vuepress/utils:  2.0.0-beta.43
    vue:  3.2.33
    vue-loader: Not Found
    vue-router:  4.0.15
    vuepress: ^2.0.0-beta.43 => 2.0.0-beta.43
    vuepress-vite:  2.0.0-beta.43
    vuepress-webpack: Not Found

https://github.com/vuepress/vuepress-next/blob/main/CHANGELOG.md#200-beta40-2022-04-25


Unable to save the canvas background color.

I am trying to save the canvas along with its background color and use it elsewhere to prepare a collage. But, I only get to see a black background. Any help to get this resolved greatly appreciated.
Regards

hey @Ben76, thanks for submitting an issue! how are you creating the background colour? The canvas should be transparent by default, so you need to draw a fillRect(0, 0, canvas.width, canvas.height) first.

closing this issue as it hasn't been active for a few years


added get_server_details

https://trafficcontrol.incubator.apache.org/docs/latest/development/traffic_ops_api/v12/server.html
#Endpoint - GET /api/1.2/servers/hostname/:name/details

Can one of the admins verify this patch?


[PKG-5426] Update to 0.2.2

imbalanced_ensemble 0.2.2 :snowflake:
Destination channel: Snowflake
Links

PKG-5426
[Upstream repository](https://github.com/ZhiningLiu1998/imbalanced-ensemble
doc_url: https://imbalanced-ensemble.readthedocs.io/)

Explanation of changes:

Simple update. Hash, deps, and removed test skips.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_e4khkvv5b1/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:63: invalid_url: https://imbalanced-ensemble.readthedocs.io/ : Not reachable: 403
===== Final Report: =====
1 Error and 0 Warnings were found

The linter's complaining about a broken link, but it works fine for me.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_8414kqohqs/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:63: invalid_url: https://imbalanced-ensemble.readthedocs.io/ : Not reachable: 403
===== Final Report: =====
1 Error and 0 Warnings were found


(ja) Fix typo on the top page

Type of Change

[ ] Enhancement
[ ] Content
[ ] Improvement / Suggestion
[x] Bug
[ ] Other (please clarify below)

Summary
There are some simple typos on the top page of the Japanese version.
Details

ゲートキーバー → ゲートキーパー

Perhaps this typo exists in three places

管理化に囚われ → 管理下に囚われ

maybe 管理化≒managerialization, 管理下≒under control

Thanks for the careful review. Yes, these are clearly my typos 😅 I'll create a PR to fix them later today (if you're not working yet).


chore: don't require approvals for any updates

Also removes ignorePaths so that test Dockerfiles are Renovated

Also removes ignorePaths so that test Dockerfiles are Renovated

Should I disable automerge completely until we are sure?

Should I disable automerge completely until we are sure?

Should I disable automerge completely until we are sure?

test/ path should be enough

Should I disable automerge completely until we are sure?

test/ path should be enough


fix: open deep link from main thread as required by UIKit

While QA testing https://linear.app/customerio/issue/MBL-138/[bug]-ios-customers-receive-callbacks-from-3rd-party-sdks-for-pushes, I noticed Xcode give a warning that we were opening deep links from a background thread instead of main thread. UIKit operations must be executed on a main thread.
Because our proxy is creating a new async Task that by default runs on a background thread, the proxy will forward all push handling events on a background thread which is what causes this issue. We can fix this by telling Swift to run the async block on the main thread.
Testing performed:

manual QA testing on iOS sample apps to verify the 3rd party callback functions were called on main thread for a push sent from CIO.

Note: I do not think we can write an automated test to assert that the Task was called on main thread. From my experience on previous projects, I have not had reliable results testing what thread a piece of code was called on. Especially when running suite on simulator.

Stack:

#634
#633 ⬅
#601
#590
#584
#583

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

✓ Commit merged in pull request #634