[Bug] ECONNREFUSED connecting to minio

Is there an existing issue for this?

[X] Yes, I have searched the existing issues and none of them match my problem.

Product Variant
Self-Hosted
Current Behavior
App can't connect to minio storage. I have changed the ports.
/app/dist/apps/server/main.js:570

            throw new common_1.InternalServerErrorException(error);
...

    errno: -111,
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '<IP_ADDRESS>',
    port: 3002
  },
  status: 500,
  options: {}
}
Node.js v20.10.0
 ELIFECYCLE  Command failed with exit code 1.

Expected Behavior
Connection not refused. 200 return codes.
Steps To Reproduce

Copy and modify the simple.yml docker compose file.

version: "3.8"

services:
  # Database (Postgres)
  postgres:
    image: postgres:15-alpine
    restart: unless-stopped
    volumes:
      - postgres_data:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: postgres
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres -d postgres"]
      interval: 10s
      timeout: 5s
      retries: 5

  # Storage (for image uploads)
  minio:
    image: minio/minio
    restart: unless-stopped
    command: server /data
    ports:
      - 3002:9000
    volumes:
      - minio_data:/data
    environment:
      MINIO_ROOT_USER: minioadmin
      MINIO_ROOT_PASSWORD: minioadmin

  # Chrome Browser (for printing and previews)
  chrome:
    image: browserless/chrome:1.61.0-puppeteer-21.4.1
    restart: unless-stopped
    environment:
      TOKEN: chrome_token
      EXIT_ON_HEALTH_FAILURE: "true"
      PRE_REQUEST_HEALTH_CHECK: "true"

  # Redis (for cache & server session management)
  redis:
    image: redis:alpine
    restart: unless-stopped
    command: redis-server --requirepass password

  app:
    image: amruthpillai/reactive-resume:latest
    restart: unless-stopped
    ports:
      - 3001:3000
    depends_on:
      - postgres
      - minio
      - redis
      - chrome
    environment:
      # -- Environment Variables --
      PORT: 3001
      NODE_ENV: production

      # -- URLs --
      PUBLIC_URL: http://localhost:3001
      STORAGE_URL: http://localhost:3002

      # -- Printer (Chrome) --
      CHROME_TOKEN: chrome_token
      CHROME_URL: ws://chrome:3001

      # -- Database (Postgres) --
      DATABASE_URL: postgresql://postgres:postgres@postgres:5432/postgres

      # -- Auth --
      ACCESS_TOKEN_SECRET: access_token_secret
      REFRESH_TOKEN_SECRET: refresh_token_secret

      # -- Emails --
      MAIL_FROM: noreply@localhost
      # SMTP_URL: smtp://user:pass@smtp:587 # Optional

      # -- Storage (Minio) --
      STORAGE_ENDPOINT: minio
      STORAGE_PORT: 3002
      STORAGE_REGION: us-east-1 # Optional
      STORAGE_BUCKET: default
      STORAGE_ACCESS_KEY: minioadmin
      STORAGE_SECRET_KEY: minioadmin
      STORAGE_USE_SSL: "false"

      # -- Cache (Redis) --
      REDIS_URL: redis://default:password@redis:6379

volumes:
  minio_data:
  postgres_data:

docker-compose up -d

What browsers are you seeing the problem on?
No response
What template are you using?
None
Anything else?
I'm sure there is something I'm doing wrong here but couldn't find any documentation about how these env vars are used.

Try to change STORAGE_URL to http://localhost:3002/default

Try to change STORAGE_URL to http://localhost:3002/default/

This gives the same error unfortunately. Is there anything else I could try?

Hey I'd love to set this up but I am still running into 500 errors. Is there anything else I can try?

I'm also having the same issue.

I'm also having the same issue.

I found a solution to this. This is happening because of changing the port for minio. minio is having some issue taking the port number from the port specified in the docker compose. So I had to change the command of minio from "server /data" to " server /data ----address :"9001"  " with 9001 being the new port. So the new simple.yml looks like
version: "3.8"
In this Docker Compose example, it assumes that you maintain a reverse proxy externally (or chose not to).
The only two exposed ports here are from minio (:9000) and the app itself (:3000).
If these ports are changed, ensure that the env vars passed to the app are also changed accordingly.
services:
Database (Postgres)
postgres:
image: postgres:15-alpine
restart: unless-stopped
volumes:
- postgres_data:/var/lib/postgresql/data
environment:
POSTGRES_DB: postgres
POSTGRES_USER: postgres
POSTGRES_PASSWORD: postgres
healthcheck:
test: ["CMD-SHELL", "pg_isready -U postgres -d postgres"]
interval: 10s
timeout: 5s
retries: 5
Storage (for image uploads)
minio:
image: minio/minio
restart: unless-stopped
command: server /data --address :"9001"
ports:
- 9001:9001
volumes:
- minio_data:/data
environment:
MINIO_ROOT_USER: minioadmin
MINIO_ROOT_PASSWORD: minioadmin
Chrome Browser (for printing and previews)
chrome:
image: browserless/chrome:1.61.0-puppeteer-21.4.1
restart: unless-stopped
environment:
TOKEN: chrome_token
EXIT_ON_HEALTH_FAILURE: true
PRE_REQUEST_HEALTH_CHECK: true
Redis (for cache & server session management)
redis:
image: redis:alpine
restart: unless-stopped
command: redis-server --requirepass password
app:
image: amruthpillai/reactive-resume:latest
restart: unless-stopped
ports:
- 3000:3000
depends_on:
- postgres
- minio
- redis
- chrome
environment:
# -- Environment Variables --
PORT: 3000
NODE_ENV: production
  # -- URLs --
  PUBLIC_URL: http://localhost:3000
  STORAGE_URL: http://localhost:9001

  # -- Printer (Chrome) --
  CHROME_TOKEN: chrome_token
  CHROME_URL: ws://chrome:3000

  # -- Database (Postgres) --
  DATABASE_URL: postgresql://postgres:postgres@postgres:5432/postgres

  # -- Auth --
  ACCESS_TOKEN_SECRET: access_token_secret
  REFRESH_TOKEN_SECRET: refresh_token_secret

  # -- Storage (Minio) --
  STORAGE_ENDPOINT: minio
  STORAGE_PORT: 9001
  STORAGE_BUCKET: default
  STORAGE_ACCESS_KEY: minioadmin
  STORAGE_SECRET_KEY: minioadmin
  STORAGE_USE_SSL: false

  # -- Cache (Redis) --
  REDIS_URL: redis://default:password@redis:6379

volumes:
minio_data:
postgres_data:

@StarkZarn  I had the same issue as you and many others in here. The root "issue", or is not an issue per se, but docker cannot resolve "localhost" ie. <IP_ADDRESS> loopback address internally. You need to use the service name for each container.
I spent some time to replace all this hardcoded ports etc in each *.yml with environment variables instead so I can replace things in one place. Just a tip.

I'm also having the same issue.

I found a solution to this. This is happening because of changing the port for minio. minio is having some issue taking the port number from the port specified in the docker compose. So I had to change the command of minio from "server /data" to " server /data ----address :"9001" " with 9001 being the new port. So the new simple.yml looks like
version: "3.8"

# In this Docker Compose example, it assumes that you maintain a reverse proxy externally (or chose not to).
# The only two exposed ports here are from minio (:9000) and the app itself (:3000).
# If these ports are changed, ensure that the env vars passed to the app are also changed accordingly.

services:
  # Database (Postgres)
  postgres:
    image: postgres:15-alpine
    restart: unless-stopped
    volumes:
      - postgres_data:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: postgres
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres -d postgres"]
      interval: 10s
      timeout: 5s
      retries: 5

  # Storage (for image uploads)
  minio:
    image: minio/minio
    restart: unless-stopped
    command: server /data --address :"9001"
    ports:
      - 9001:9001
    volumes:
      - minio_data:/data
    environment:
      MINIO_ROOT_USER: minioadmin
      MINIO_ROOT_PASSWORD: minioadmin

  # Chrome Browser (for printing and previews)
  chrome:
    image: browserless/chrome:1.61.0-puppeteer-21.4.1
    restart: unless-stopped
    environment:
      TOKEN: chrome_token
      EXIT_ON_HEALTH_FAILURE: true
      PRE_REQUEST_HEALTH_CHECK: true

  # Redis (for cache & server session management)
  redis:
    image: redis:alpine
    restart: unless-stopped
    command: redis-server --requirepass password

  app:
    image: amruthpillai/reactive-resume:latest
    restart: unless-stopped
    ports:
      - 3000:3000
    depends_on:
      - postgres
      - minio
      - redis
      - chrome
    environment:
      # -- Environment Variables --
      PORT: 3000
      NODE_ENV: production

      # -- URLs --
      PUBLIC_URL: http://localhost:3000
      STORAGE_URL: http://localhost:9001

      # -- Printer (Chrome) --
      CHROME_TOKEN: chrome_token
      CHROME_URL: ws://chrome:3000

      # -- Database (Postgres) --
      DATABASE_URL: postgresql://postgres:postgres@postgres:5432/postgres

      # -- Auth --
      ACCESS_TOKEN_SECRET: access_token_secret
      REFRESH_TOKEN_SECRET: refresh_token_secret

      # -- Storage (Minio) --
      STORAGE_ENDPOINT: minio
      STORAGE_PORT: 9001
      STORAGE_BUCKET: default
      STORAGE_ACCESS_KEY: minioadmin
      STORAGE_SECRET_KEY: minioadmin
      STORAGE_USE_SSL: false

      # -- Cache (Redis) --
      REDIS_URL: redis://default:password@redis:6379

volumes:
  minio_data:
  postgres_data:

This fixed it for me. Thank you!


Options are not taken into account, remote_route don't work !

Hello I am stuck for 3 days on a strange problem.  I have the impression that the options are not taken into account !
I followed the documentation but it don't work.
I can display my form, but the ajax request does not point to the right route. Indeed instead of taking into account the route specified in the options it is another route that is used! Moreover I have the impression that the other options are not taken into account because the Ajax request starts as soon as we click on the input whereas I asked that it starts only from 4 characters. Does someone have an idea?
Here is the code
Help !!!
Mathieu
The Route that should be used in the ajax request.
datatype_coding_show_ajax_action:     path:  /show-ajax     defaults: { _controller: "MSFhirBundle:Coding:showAjax" }     requirements: { _method: get|post }     options:         expose: true
FormType
`<?php
namespace MS\FhirBundle\Form\DataType;
use Symfony\Component\Form\AbstractType;
use Symfony\Component\Form\FormBuilderInterface;
use Symfony\Component\OptionsResolver\OptionsResolver;
use Symfony\Component\Form\CallbackTransformer;
use Symfony\Component\Form\Extension\Core\Type\TextType;
use Symfony\Component\DependencyInjection\Container;
use Doctrine\Common\Persistence\ObjectManager;
use MS\FhirBundle\DataTransformer\IdTransformer;
use Symfony\Bridge\Doctrine\Form\Type\EntityType;
use Symfony\Component\Form\Extension\Core\Type\ChoiceType;
use Tetranz\Select2EntityBundle\Form\Type\Select2EntityType;
class CodeableConceptType extends AbstractType
{
/**
 * {@inheritdoc}
 */
public function buildForm(FormBuilderInterface $builder, array $options)
{
    $builder
		->add('codings', Select2EntityType::class, array(
        'multiple' => true,
		'minimum_input_length' => 4,
        'remote_route' => 'datatype_coding_show_ajax_action',
        'class' => 'MSFhirBundle:Coding',
        'primary_key' => 'id',
        'page_limit' => 10,
        'allow_clear' => true,

    ))
		->add('text')
			;
}

/**
 * {@inheritdoc}
 */
public function configureOptions(OptionsResolver $resolver)
{
    $resolver->setDefaults(array(
        'data_class' => 'MS\FhirBundle\Entity\DataType\CodeableConcept'
    ));
}

/**
 * {@inheritdoc}
 */
public function getBlockPrefix()
{
    return 'ms_fhirbundle_datatype_codeableconcept';
}

}
`
The URL used to have the form. This URL is not the URL that should be used in the Ajax request http://localhost:8888/app_dev.php/atcd/new (symphony name : actd_new) but you can see ajax request realised by the bundle

I setup a new test site today to work through some issues and got the same problem.  I "fixed" it by going back to jQuery 1.12.4. I'm very surprising that there are not lots of people reporting this problem. Surely other people are using jQuery 2.
Unfortunately I don't have much spare time to devote to this project these days but I'll try to do some debugging in the next week or so.

I've done some more testing and finding some quite weird results.
If I make a plain html file with this, it works.  That's nothing to do with Symfony except for my ajax endpoint.
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title>Title</title>
    <link href="https://cdnjs.cloudflare.com/ajax/libs/select2/4.0.6-rc.0/css/select2.min.css" rel="stylesheet" />
</head>
<body>

<select data-minimum-input-length="2" data-ajax--url="http://www.symtest.local/person.json"
        style="width: 200px;" class="js-data-example-ajax"></select>

<script
        src="https://code.jquery.com/jquery-1.12.4.min.js"
        integrity="sha256-ZosEbRLbNQzLpnKIkEdrPv7lOy9C27hHQ+Xp8a4MxAQ="
        crossorigin="anonymous"></script>

<script src="https://cdnjs.cloudflare.com/ajax/libs/select2/4.0.6-rc.0/js/select2.min.js"></script>

<script>
    $('.js-data-example-ajax').select2();
</script>
</body>
</html>

If I change it to jQuery 2.2.4, it does not work and I get the problem report here.  data-* attributes seem to have problems. With jQuery 2, if I change data-ajax--url to data-ajax-url it starts to work but minimum-input-length is ignored. But that's weird too because data-ajax-url is supposed to be a fix for data-ajax--url not working on jQuery 1.
I'll see if I can document the issue better and raise it in Select2 issues.

The problem seems to be with select2-4.0.6-rc.0.
select2-4.0.5 works fine with later versions of jQuery.  I'll report this to the select2 project.

Great !!! It seems to work fine ! Thanks a lot !
Best Wishes for a 2018


Guidance on overhead impact on EdgeOS device

Is there anyone that can give guidance on the impact of router performance with the additional overhead of running tailscale on EdgeOS devices?
Is there anyone that has run this on an EdgeRouter-X?

It's probably better to ask over on the Tailscale forums.
I don't have numbers, but I can tell you that on an ER4 there's no performance hit that I can tell.


Getting error for esp-idf modbus  slave example testing (IDFGH-5939)

Hello,
I am trying to run the esp-idf modbus slave examplewith modbus master/poll tool

getting read/write error in poll tool like above.

Hello @dimpalsharm,
The Break condition means that the transmitter is holding the line in zero state when transmittion is done for a long time. This often heppens when RS485 line drivers do not work correctly.

Please use the rs485 echo example to check interface connection first.
Flash the Modbus slave example `idf.py -p PORT flash monitor'.
Start modbus communication then use "Display communication traffic" option in the tool bar or menu of your "Modbus Master Poll" software. This will show communication log which will allow to recognize the problem. Please include the log here.
Include the mb_slave example log here.

Thanks.

@dimpalsharm,
Could you give the update for this issue?
Also, you are creating several test issues for Modbus that are related to each other that prevents to track them appropriately.

@dimpalsharm Thanks for reporting, would you please help share if any updates for the issue? Thanks.

@dimpalsharm Thanks for reporting, would you please help share if any updates for the issue? Thanks.

@dimpalsharm Thanks for reporting, will close due to short of feedback, feel free to reopen with more updates.


stdEnumerator compile error in 32 bit

Private Declare PtrSafe Function createEmptyArrayLongLong Lib "oleaut32" Alias "SafeArrayCreateVector" (Optional ByVal vt As VbVarType = vbLongLong, Optional ByVal lLow As Long = 0, Optional ByVal lCount As Long = 0) As LongLong()

Will raise a compiler error in 32 bit.
Fix, change to:
#If Win64 Then
    Private Declare PtrSafe Function createEmptyArrayLongLong Lib "oleaut32" Alias "SafeArrayCreateVector" (Optional ByVal vt As VbVarType = vbLongLong, Optional ByVal lLow As Long = 0, Optional ByVal lCount As Long = 0) As LongLong()
#End If

Additionally
CreateFromListObject needs a test as it failed on first try. v needs to be vData

Closed by fe11437


Wrongly set environment variable during debugging

Type: Bug
I am getting an FileNotFoundExecption due to a SSL_CERT_FILE path being set as environment variable. This only happens during debugging in VSCode. From the terminal, PyCharm or VSCode without the debugger everything runs smoothsly.
I have already written a Stackoverflow post with lots of details here
VS Code version: Code 1.77.0 (7f329fe6c66b0f86ae1574c2911b681ad5a45d63, 2023-03-29T10:02:16.981Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 x 1805)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.73GB (20.47GB free)

Process Argv
--crash-reporter-id 9a5c97e3-ae8b-4fd1-86a4-75c3456e616d

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

vscode-kubernetes-tools
ms-
1.3.11

python
ms-
2023.6.0

vscode-pylance
ms-
2023.4.10

jupyter
ms-
2023.3.1000892223

jupyter-keymap
ms-
1.1.0

jupyter-renderers
ms-
1.0.15

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

autodocstring
njp
0.6.1

vscode-yaml
red
1.12.2

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
nodejswelcome1cf:30587006
3biah626:30602489
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
a9j8j154:30646983
6233i204:30672705
vsccsb:30705552
pythonb192:30669360
defaultazurewalk:30687958
pythonms35:30701012

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.77.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.77.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Just updated - same error still remains in the latest version.

@TheRealRolandDeschain Could you please paste this information too?

Please show me the actual command when you Debug Python File.

Here is the Python Debug Console output in VS Code (with my username changed). For this I have removed the launch.json and started the debugger with Python:File
complete code:
import os
print(os.environ.get('SSL_CERT_FILE'))

console output:
(minio) PS C:\Users\myuser\Documents\source\Python\minio-project>  c:; cd 'c:\Users\myuser\Documents\source\Python\minio-project'; & 'C:\Users\myuser\Miniconda3\envs\minio\python.exe' 'c:\Users\myuser\.vscode\extensions\ms-python.python-2023.6.0\pythonFiles\lib\python\debugpy\adapter/../..\debugpy\launcher' '60007' '--' 'C:\Users\myuser\Documents\source\Python\minio-project\main.py'
C:\Users\MYUSER~1\AppData\Local\Temp\_MEI223042\certifi\cacert.pem

I copied the above output from my Stackoverflow post however, I just realized there before the actual terminal command to run the script there the following error displayed. Not sure however if it is related but for completeness, here is the full output after restarting VSCode and running the script:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

Loading personal and system profiles took 1885ms.
PS C:\Users\myuser\Documents\source\Python\minio-project> C:/Users/myuser/Miniconda3/activate
C:/Users/myuser/Miniconda3/activate : The term 'C:/Users/myuser/Miniconda3/activate' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ C:/Users/myuser/Miniconda3/activate
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:/Users/myuser/Miniconda3/activate:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\myuser\Documents\source\Python\minio-project> conda activate C:\Users\myuser\Miniconda3\envs\minio
(minio) PS C:\Users\myuser\Documents\source\Python\minio-project>  & 'C:\Users\myuser\Miniconda3\envs\minio\python.exe' 'c:\Users\myuser\.vscode\extensions\ms-python.python-2023.6.0\pythonFiles\lib\python\debugpy\adapter/../..\debugpy\launcher' '54362' '--' 'C:\Users\myuser\Documents\source\Python\minio-project\main.py'
C:\Users\MYUSER~1\AppData\Local\Temp\_MEI295522\certifi\cacert.pem
(minio) PS C:\Users\myuser\Documents\source\Python\minio-project>

Here is the Python Debug Console output in VS Code (with my username changed). For this I have removed the launch.json and started the debugger with Python:File
complete code:
import os
print(os.environ.get('SSL_CERT_FILE'))

console output:
(minio) PS C:\Users\myuser\Documents\source\Python\minio-project>  c:; cd 'c:\Users\myuser\Documents\source\Python\minio-project'; & 'C:\Users\myuser\Miniconda3\envs\minio\python.exe' 'c:\Users\myuser\.vscode\extensions\ms-python.python-2023.6.0\pythonFiles\lib\python\debugpy\adapter/../..\debugpy\launcher' '60007' '--' 'C:\Users\myuser\Documents\source\Python\minio-project\main.py'
C:\Users\MYUSER~1\AppData\Local\Temp\_MEI223042\certifi\cacert.pem

Maybe check your conda environments could help. Please feel free to check it here https://conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#viewing-a-list-of-your-environments

@TheRealRolandDeschain Since you activated minio, could be the envrionments defined in minio resulted this issue?

Running the command above gets me this result:

To be honest, I do not think the environment is the problem, since I have already tried to create and test with a new environment, tested with other existing environments (python 3.9), I have also reinstalled VSCode completely.
The only thing I could think of at this point is to use a local python environment, independent of conda, but apart from that I'm a bit out of ideas 😄

Running the command above gets me this result:

To be honest, I do not think the environment is the problem, since I have already tried to create and test with a new environment, tested with other existing environments (python 3.9), I have also reinstalled VSCode completely.
The only thing I could think of at this point is to use a local python environment, independent of conda, but apart from that I'm a bit out of ideas 😄

I'm using Python 3.10.7 and debugging the code snippet but cannot reproduct this issue. You'd better try a local pure Python installation to figure out where the issue could be.

Ok, I will do that next Tuesday and report back here. Thanks for the help in the meantime!

SSL_CERT_FILE

Never mind. Anyway, you can try to show all configurations by as https://docs.conda.io/projects/conda/en/latest/commands/config.html#Config Modifiers , such as conda config --show to check them.

This gives the following output
PS C:\Users\myuser> conda config --show
add_anaconda_token: True
add_pip_as_python_dependency: True
aggressive_update_packages:
  - ca-certificates
  - certifi
  - openssl
allow_conda_downgrades: False
allow_cycles: True
allow_non_channel_urls: False
allow_softlinks: False
allowlist_channels: []
always_copy: False
always_softlink: False
always_yes: None
anaconda_upload: None
auto_activate_base: False
auto_stack: 0
auto_update_conda: True
bld_path:
changeps1: True
channel_alias: https://conda.anaconda.org
channel_priority: flexible
channel_settings: []
channels:
  - defaults
client_ssl_cert: None
client_ssl_cert_key: None
clobber: False
conda_build: {}
create_default_packages: []
croot: C:\Users\myuser\Miniconda3\conda-bld
custom_channels:
  pkgs/main: https://repo.anaconda.com
  pkgs/r: https://repo.anaconda.com
  pkgs/msys2: https://repo.anaconda.com
  pkgs/pro: https://repo.anaconda.com
custom_multichannels:
  defaults:
    - https://repo.anaconda.com/pkgs/main
    - https://repo.anaconda.com/pkgs/r
    - https://repo.anaconda.com/pkgs/msys2
  local:
debug: False
default_channels:
  - https://repo.anaconda.com/pkgs/main
  - https://repo.anaconda.com/pkgs/r
  - https://repo.anaconda.com/pkgs/msys2
default_python: 3.9
default_threads: None
deps_modifier: not_set
dev: False
disallowed_packages: []
download_only: False
dry_run: False
enable_private_envs: False
env_prompt: ({default_env})
envs_dirs:
  - C:\Users\myuser\Miniconda3\envs
  - C:\Users\myuser\.conda\envs
  - C:\Users\myuser\AppData\Local\conda\conda\envs
error_upload_url: https://conda.io/conda-post/unexpected-error
execute_threads: 1
experimental: []
extra_safety_checks: False
fetch_threads: 5
force: False
force_32bit: False
force_reinstall: False
force_remove: False
ignore_pinned: False
json: False
local_repodata_ttl: 1
migrated_channel_aliases: []
migrated_custom_channels: {}
non_admin_enabled: True
notify_outdated_conda: True
number_channel_notices: 5
offline: False
override_channels_enabled: True
path_conflict: clobber
pinned_packages: []
pip_interop_enabled: False
pkgs_dirs:
  - C:\Users\myuser\Miniconda3\pkgs
  - C:\Users\myuser\.conda\pkgs
  - C:\Users\myuser\AppData\Local\conda\conda\pkgs
proxy_servers: {}
quiet: False
remote_backoff_factor: 1
remote_connect_timeout_secs: 9.15
remote_max_retries: 3
remote_read_timeout_secs: 60.0
repodata_fns:
  - current_repodata.json
  - repodata.json
repodata_threads: None
report_errors: None
restore_free_channel: False
rollback_enabled: True
root_prefix: C:\Users\myuser\Miniconda3
safety_checks: warn
sat_solver: pycosat
separate_format_cache: False
shortcuts: True
show_channel_urls: None
signing_metadata_url_base: None
solver: classic
solver_ignore_timestamps: False
ssl_verify: True
subdir: win-64
subdirs:
  - win-64
  - noarch
target_prefix_override:
track_features: []
unsatisfiable_hints: True
unsatisfiable_hints_check_depth: 2
update_modifier: update_specs
use_index_cache: False
use_local: False
use_only_tar_bz2: False
verbosity: 0
verify_threads: 1

Could you please look at environments in envs_dirs from former command output? And how about disable ssl_verify? It seems like urllib3 going to use this environment, right?

I'm not sure what's going on here, but vscode is not making up this environment variable. I doubt it's the python extension either, but if you aren't able to track it down to your environment, could you file this on the vscode-python repo?


Install Error

I'm install but i can't load mw(mw is not defined). I'm used laravel 5.0 - php version 5.4.12. Please help me. Thanks!

I suggest you contact support from our website. We'll help you debug the issue much more quickly than commenting on this issue, as there's probably something wrong with your setup and not the Microweber code.


[HoverCard] Use hover intent polygon method

Thinking about this deeply, we should use a combination of timeout and hover intent methods.

I am closing this for now. Not an urgent need for the hovercard.


Fix notebook tqdm

Our progress bar is created by tqdm, which has a separate version for working in notebooks: from tqdm.notebook import tqdm instead of from tqdm import tqdm. We would need to be able to tell whether the library is being imported from a notebook or not and change which tqdm we import.
It looks like tqdm also has an auto option, which should figure this out for us.

Is this that important? I think it just makes the progress bar prettier / in color.

Changed everything to tqdm.auto in #114


A.28.creation.date

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685
Comment
This test case was removed from GitHub?
There is still an open question whether to include this test case, as there is no explicit requirement in the technical guidelines.
Proposed Change
It is proposed to add an explicit requirement for metadata date in the MD TG. A corresponding test case must also be created.

we had a discussion about this file https://github.com/inspire-eu-validation/ats-metadata/blob/v0.5/A.28.md.creation.date.md at https://github.com/inspire-eu-validation/ats-metadata/pull/20. It is an interesting case, since iso19139 already required this element to be available, there seems no need to have also inspire tests check it, it should be enough to just indicate that the metadata should be valid against iso19139.

The requirement in the IR is not "at least one creation date", but "at most one creation date". Therefore the requirement 25 in the TG makes sense. But it should probably be clarified that it means that there shall not be more than one creation date.
I would suggest to add a test for TG req 25 checking that there is not more than one creation date.


#79 refactored the code to match the required in issue

PR for #79

Job #87 is now in scope, role is REV

This pull request #87 is assigned to @bahaaib/z, here is why; the budget is 15 minutes, see §4; please, read §27 and when you decide to accept the changes, inform @ammaratef45/z (the architect) right in this ticket; if you decide that this PR should not be accepted ever, also inform the architect; this blog post will help you understand what is expected from a code reviewer; @bahaaib/z is not a member of this project yet, but they can request to join, as §1 explains; there will be no monetary reward for this job

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @ammaratef45/z

@Bahaaib Okay, It's because of the const constructor
Which is prefered for immutable classes.

@rultor merge

@rultor merge

@bahaaib Thanks for your request. @ammaratef45 Please confirm this.

@rultor merge

@rultor merge

@ammaratef45 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@ammaratef45 Done! FYI, the full log is here (took me 6min)

Quality is low, no payment, see §31:

Job was finished in 7 hours, bonus for fast delivery is possible (see §36)

The job #87 is now out of scope

Payment to ARC for a closed pull request, as in §28: +10 point(s) just awarded to @ammaratef45/z


Use TB interface, rather than T pointer when doing test stuff

this will permit passing testing.B everywhere too!
/assign @markusthoemmes @dprotaso
🧹

/test pull-knative-pkg-unit-tests

/assign @evankanderson @tcnghia

(ノಠ益ಠ)ノ彡┻━┻
/test pull-knative-pkg-unit-tests


Fix menu wording

Changed from Data to Dataverse (see number 1 from image above)

@last72 Thanks for your feedback. Closing this without merging as the menu change is temporary and part of some usability testing. We will make this change globally once we get a go ahead from the team managing this change.


Uncordon node in a explicit sls action

This way we don't try to uncordon the node in the kubelet/init.sls file,
required for example by haproxy, that will end up in the machine trying
to early uncordon itself (when haproxy configuration hasn't been written
yet, and leading to early failure).
Splitting this action and called only when required (this is: the update
process) is safer.
Fixes: bsc#1080978

The upgrade worked with a pseudo-apply of this patch:
Summary for admin.infra.caasp.local_master
-------------
Succeeded: 64 (changed=46)
Failed:     0
-------------
Total states run:     64
Total run time: 1106.123 s

I will continue tomorrow testing this exact patch.

Upgrade is working.

By the way, have you checked this doesn't have any negative effect on node removal?

I haven't checked, but I don't see a relationship betwen the changed states/files and their relationship to node removal.


Gallery through collection, adding to a region

Hi there,
So i'm using a Collection to capture a gallery, I want to display lots of mini galleries on a page and thought this would be the easiest way. I want to output said galleries using a region and pulling it through from the Collection data. I have all the other fields working but can't get the gallery pulling through, could you help me out?
Thanks in advance!
Sam

could you please post your region code?

Hi Artur,
Heres' my region code so far:
@foreach(collection('Used Vehicles')->find() as $usedvehicles)

{{ $usedvehicles['vehicle_name'] }}

@endforeach
I want to add the gallery below the H1 tag.
Cheers!
Sam

$usedvehicles['vehicle_gallery'] is a name reference of a gallery as string, e.g "mycars"?

$usedvehicles is referencing the collection, the collection has a field in it that collects a gallery if that makes sense? (see image below)

@foreach($usedvehicles['gallery'] as $pic)

@endforeach

Perfect, thanks a lot Artur.

:+1:


Dependabot triggered Actions cant access secrets

Our checks for secrets fail:
Run vars_not_set=0
CELL_GITHUB not set
CELL_GITHUB_TOKEN not set
REGISTRY_URL not set
NAAVRE_API_TOKEN not set
JUPYTERHUB_USER not set
API_ENDPOINT not set
VLAB_SLUG not set
MODULE_MAPPING_URL not set
SEARCH_API_ENDPOINT not set
SEARCH_API_TOKEN not set
Exiting with error
CELL_GITHUB not set CELL_GITHUB_TOKEN not set REGISTRY_URL not set NAAVRE_API_TOKEN not set JUPYTERHUB_USER not set API_ENDPOINT not set VLAB_SLUG not set MODULE_MAPPING_URL not set SEARCH_API_ENDPOINT not set SEARCH_API_TOKEN not set
Error: Process completed with exit code 1.

Wait for dependabot to create a new PR to see if the fix worked.

Did not fix the problem. We still get:
Run vars_not_set=0
CELL_GITHUB not set
CELL_GITHUB_TOKEN not set
REGISTRY_URL not set
NAAVRE_API_TOKEN not set
JUPYTERHUB_USER not set
API_ENDPOINT not set
VLAB_SLUG not set
MODULE_MAPPING_URL not set
SEARCH_API_ENDPOINT not set
SEARCH_API_TOKEN not set
Exiting with error
CELL_GITHUB not set CELL_GITHUB_TOKEN not set REGISTRY_URL not set NAAVRE_API_TOKEN not set JUPYTERHUB_USER not set API_ENDPOINT not set VLAB_SLUG not set MODULE_MAPPING_URL not set SEARCH_API_ENDPOINT not set SEARCH_API_TOKEN not set
Error: Process completed with exit code 1.

@skoulouzis I just noticed there’s a Dependabot secrets section (repository settings > Secrets and variables > Dependabot). Maybe Dependabot expects the variables to be set from there?

@gpelouze  You are right. I added Dependabot secrets to organization secrets and selected the relevant resources.


Page not found in open source Job Boards -Apple.

@SaadAnsari17 would you like to go ahead with making the pr?

#79


Windows support

Happy to work with someone on this, but I don't have a Windows machine to test with.
Viteshot is already doing visual regression testing on Windows, but that's the smallest of my concerns for compatibility.

There are Windows releases as of v0.3.1.


dataset_ops.py batch() checks type immediately

Currently if you inadvertently pass a non integer value for batch_size you get a strangely cryptic error with a long trace:
  File "/home/ahundt/.local/lib/python2.7/site-packages/tensorflow/python/data/ops/dataset_ops.py", line 734, in batch
    return BatchDataset(self, batch_size)
  File "/home/ahundt/.local/lib/python2.7/site-packages/tensorflow/python/data/ops/dataset_ops.py", line 1392, in __init__
    batch_size, dtype=dtypes.int64, name="batch_size")
  File "/home/ahundt/.local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 932, in convert_to_tensor
    as_ref=False)
  File "/home/ahundt/.local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 1022, in internal_convert_to_tensor
    ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
  File "/home/ahundt/.local/lib/python2.7/site-packages/tensorflow/python/framework/constant_op.py", line 233, in _constant_tensor_conversion_function
    return constant(v, dtype=dtype, name=name)
  File "/home/ahundt/.local/lib/python2.7/site-packages/tensorflow/python/framework/constant_op.py", line 212, in constant
    value, dtype=dtype, shape=shape, verify_shape=verify_shape))
  File "/home/ahundt/.local/lib/python2.7/site-packages/tensorflow/python/framework/tensor_util.py", line 413, in make_tensor_proto
    _AssertCompatible(values, dtype)
  File "/home/ahundt/.local/lib/python2.7/site-packages/tensorflow/python/framework/tensor_util.py", line 328, in _AssertCompatible
    (dtype.name, repr(mismatch), type(mismatch).__name__))
TypeError: Expected int64, got 'dataset_reader.py' of type 'str' instead.

This PR hopes to clear that up by checking the type right at the call site.
If I made a mistake in the preferred approach to such a check I'd appreciate advice, I did some searching and I couldn't find obvious examples that can accept both integers and scalar tensors, there are always slight variations and acceptable imports depend on the code location.

Thanks for the contribution. Unfortunately I can't accept it because it would break backwards compatibility: types other than tf.Tensor and int are convertible into the tf.int64 argument for batch_size and this would incorrectly reject them.
I would be in favor of improving the argument handling for tf.data APIs in general, so if you come up with another way to do this I'd be happy to review another PR.


If slideshow is hidden, when it is re-shown, the _.slideCount = null

I have a slick 1.4.1 slideshow. Above the slideshow is a group of thumbnails that link to individual slides, using $('#TheSlideshowID').slick('slickGoTo', intTheSlideToShow);
These thumbnail links work the first time the slideshow is shown. If I hide the slideshow and then re-show it, the thumbnail links no longer work. The slideshow itself, however, does continue to work (prev/next, etc.).
I traced through the code and determined that where it hangs is inside Slick.prototype.slideHandler, where _.slideCount now equals null instead of equaling the total number of slides.
Is this a bug? Or do I need to call something to refresh the slideshow when it is re-shown?

Same problem here. Have a custom slide counter in my instance of slick that returns "null" (i.e.: 1/null) when the slider is first loaded. Then when i change slides, then the total # of slides appears (i.e.: 2/5)... It's not picking up the slideCount until the afterChange is fired. Help.


go/runtime/registry: Simplify creation of provisioners

Something is fishy with line config.GlobalConfig.Mode.IsClientOnly() && !isEnvSGX as it doesn't make sense. Do we run client with RuntimeEnvironmentELF and without DebugDontBlameOasis flag set?

Do we run client with RuntimeEnvironmentELF and without DebugDontBlameOasis flag set?

Yes I believe so: For example, running a ParaTime client node for an SGX-enabled ParaTime like Cipher doesn't require having SGX on the ParaTime client node..


BUG-Renaming a node moves it to its original position

Description
Renaming a node moves it to its original position
How to reproduce
Create a node in Taipy Studio, move it, and then rename it. It will move back to its original position.
Expected behavior
Renaming a node should not change its position
Runtime environment
Please specify relevant indications.

Taipy version: 2.2.0
OS: Windows

Better description of the issue in #70


Error in "npm start"

Hi,
I'm getting the following error when I run "npm start" command.
Running "less:layouts" (less) task
>> NameError: variable @dl-horizontal-breakpoint is undefined in public/vendor/bootstrap/less/type.less on line 214, column 22:
>> 213
>> 214   @media (min-width: @dl-horizontal-breakpoint) {
>> 215     dt {
Warning: Error compiling public/less/bootstrap-build.less Use --force to continue.

Aborted due to warnings.

npm version: 3.5.2
Any idea how to resolve the issue?

I managed to solve the problem by adding the following variables to the bootstrap-vars.less.
@dl-horizontal-offset:        @component-offset-horizontal;
@dl-horizontal-breakpoint:    @grid-float-breakpoint;

Seems these are added in the latest version of the bootstrap.


Exact match autocomplete preview: should this be a "contains" search?

I'm wondering whether the autocomplete previews for "exact matching" should show the results from a contains search. For instance, if I'm searching for NIAID, I think I would expect to see NIAID NIH HHS, National Institute of Allergy and Infectious Diseases (NIAID), NIAID, etc., so i could choose which one of those I would want to exact match.

Thoughts @candicecz @EmilyHaag ?

Changing it to options to "contains" makes sense to me as well, we can see what user feedback we get in the long run...
Let me know if I should go ahead and make the change.


Add cli option to Galley to allow metadata on outgoing sink connections.

For use with sinkAddress, outgoing connections to MCP sink servers
will have gRPC stream metadata attached as defined by sinkMeta.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jeffmendoza
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
2248eaf189c8e99f564d2196d6f226b2d7b2b4d0
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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
2248eaf189c8e99f564d2196d6f226b2d7b2b4d0
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
2248eaf189c8e99f564d2196d6f226b2d7b2b4d0
link
/test istio-pilot-multicluster-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.

/test istio-unit-tests

Can we support foo=bar style parameters? That should help with the len(items)%2==0 problem as well.

Ah ok, I see StringToString now, will give it a shot.
https://godoc.org/github.com/spf13/pflag#FlagSet.StringToStringVar

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2248eaf189c8e99f564d2196d6f226b2d7b2b4d0
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
36c918a3696fe71049ddd3cd87b97f77be21b8b3
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2248eaf189c8e99f564d2196d6f226b2d7b2b4d0
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
36c918a3696fe71049ddd3cd87b97f77be21b8b3
link
/test istio-unit-tests

prow/istio-presubmit.sh
36c918a3696fe71049ddd3cd87b97f77be21b8b3
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2248eaf189c8e99f564d2196d6f226b2d7b2b4d0
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
36c918a3696fe71049ddd3cd87b97f77be21b8b3
link
/test istio-unit-tests

prow/istio-presubmit.sh
36c918a3696fe71049ddd3cd87b97f77be21b8b3
link
/test istio-presubmit

prow/istio-integ-local-tests.sh
36c918a3696fe71049ddd3cd87b97f77be21b8b3
link
/test istio-integ-local-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.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jeffmendoza
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: hklai
If they are not already assigned, you can assign the PR to them by writing /assign @hklai in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2248eaf189c8e99f564d2196d6f226b2d7b2b4d0
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
36c918a3696fe71049ddd3cd87b97f77be21b8b3
link
/test istio-unit-tests

prow/istio-presubmit.sh
36c918a3696fe71049ddd3cd87b97f77be21b8b3
link
/test istio-presubmit

prow/istio-integ-local-tests.sh
f753302a2450aefcf344bbd4bf866141f5000304
link
/test istio-integ-local-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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2248eaf189c8e99f564d2196d6f226b2d7b2b4d0
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-local-tests.sh
f753302a2450aefcf344bbd4bf866141f5000304
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f753302a2450aefcf344bbd4bf866141f5000304
link
/test istio-integ-k8s-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.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jeffmendoza
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2248eaf189c8e99f564d2196d6f226b2d7b2b4d0
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
f753302a2450aefcf344bbd4bf866141f5000304
link
/test istio-integ-k8s-tests

prow/istio-integ-local-tests.sh
2248eaf189c8e99f564d2196d6f226b2d7b2b4d0
link
/test istio-integ-local-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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2248eaf189c8e99f564d2196d6f226b2d7b2b4d0
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
f753302a2450aefcf344bbd4bf866141f5000304
link
/test istio-integ-k8s-tests

prow/istio-integ-local-tests.sh
16a9afb8c9553983c6e771be2523e9598f282f4d
link
/test istio-integ-local-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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2248eaf189c8e99f564d2196d6f226b2d7b2b4d0
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-local-tests.sh
16a9afb8c9553983c6e771be2523e9598f282f4d
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
16a9afb8c9553983c6e771be2523e9598f282f4d
link
/test istio-integ-k8s-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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
16a9afb8c9553983c6e771be2523e9598f282f4d
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
16a9afb8c9553983c6e771be2523e9598f282f4d
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
16a9afb8c9553983c6e771be2523e9598f282f4d
link
/test istio-pilot-multicluster-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.

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jeffmendoza, ozevren
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS [ozevren]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
16a9afb8c9553983c6e771be2523e9598f282f4d
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
77e8e243ab855e05a0445739706e23d4cba6baf8
link
/test istio-integ-k8s-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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
77e8e243ab855e05a0445739706e23d4cba6baf8
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
77e8e243ab855e05a0445739706e23d4cba6baf8
link
/test istio-pilot-multicluster-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.

e2e-mixer-noauth-v1alpha3-v2 failure seems unrelated
2019-02-11T20:40:04.903963Z	error	Error starting port forwarder: failure running port forward process: error upgrading connection: error dialing backend: dial tcp: lookup default-3f86ccab-ef66-43ca-bbe8-78d78ad49872 on <IP_ADDRESS>:53: dial udp <IP_ADDRESS>:53: operation was canceled

/retest

/test istio-pilot-multicluster-e2e

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
77e8e243ab855e05a0445739706e23d4cba6baf8
link
/test istio-pilot-multicluster-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.

/retest

@wenchenglu this is ready to go


c# anonymous type breaks syntax highlight

c# disabled:

c# enabled:

and combined with a custom theme (https://marketplace.visualstudio.com/items?itemName=henrysoftware.theme-rage) equals:

This issue was moved to dotnet/csharp-tmLanguage#47


fix(aws-kinesisstreams-kinesisfirehose-s3): allow later versions of cdk lib by updating peerDependencies

Issue #, if available:
Addresses Issue 1094
Description of changes:
Update package.json for aws-kinesisstreams-kinesisfirehose-s3 and 6 other constructs/samples with the same issue.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: e08903f7f6839e343cd0df207ae80c03c2dcace3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


test changes

Semver
This project uses semver, please check the scope of this PR:

[x] #none#
[ ] #patch#
[ ] #minor#
[ ] #major#

CHANGELOG

test changes

@job13er do you mind approving this PR via the GitHub mechanism as well?  Thanks!


Fancyzone resets on boot

Microsoft PowerToys version
0.68.1
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
when booting my pc, the fancy zones layout seem to reset
✔ Expected Behavior
i expected my saved custom layout to be used on boot
❌ Actual Behavior
fancyzones resets to default layout and i have to open powertoys and turn it off and on to get my own custom layout
Other Software
No response

Came online to say I have the same issue


Hotfix/set offset bug

In a situation where the consumer class is able to fetch messages faster from a Kafka partition than the messages can be processed, setting the partition offset is ignored.
In the Consumer.ConsumeTopicPartitionAsync method the offset is retrieved in the beginning of the while loop and used afterwards. When handling the response and adding the messages to the _fetchResponseQueue, the task may block if the queue is full.
If the client of the consumer class sets the offset while the consumer is blocked waiting for free space in the _fetchResponseQueue, the consumer class will override the offset after having added all current messages to the queue.
foreach (var message in response.Messages)
{
	_fetchResponseQueue.Add(message, _disposeToken.Token); <-- While blocking, if offset is set with a call to the SetOffsetPosition method, it will be overwritten later

	if (_disposeToken.IsCancellationRequested) return;
}

var nextOffset = response.Messages.Max(x => x.Meta.Offset) + 1;
_partitionOffsetIndex.AddOrUpdate(partitionId, i => nextOffset, (i, l) => nextOffset); <-- Offset is overwritten here

Sorry, i think i may have introduced another bug. The last line in the code snippet above should be changed to
                                    _partitionOffsetIndex.AddOrUpdate(partitionId, i => new Tuple<long, bool>(nextOffset, false), (i, l) => l.Item2 ? new Tuple<long, bool>(l.Item1, false) : new Tuple<long, bool>(nextOffset, false));
So the code from my pull request is not quite good enough.


How is the Instagram Feed Kirby plugin affected by the changes at meta and do you plan on updating?

Instagram Basic Display API has been retired the 4th of December. Does the plugin entirely rely on that how is there a way to make it work with the new system? If not do you plan on updating the plugin?
https://developers.facebook.com/blog/post/2024/09/04/update-on-instagram-basic-display-api/

Hi @Julianoe
Instagram Basic Display API no longer supported. Please follow the steps:

Login to https://developers.facebook.com/
Create a new App
Make an App name
Choose "Other" for use case
Choose "Business" for app type
Confirm "Create App"
Add Instagram product to your App
Add client Instagram account to the Instagram API (client must have a business professional/creator account for this to work)
Generate a new token
Add this token to the site/config.php or other config environment file
Delete media folder and site/cache

Let me know when you done.


Dashboard image management

Allow to pick variants for images

Current coverage is 49.29%

Merging #470 into master will increase coverage by +0.62% as of 3f1e7ee

@@            master    #470   diff @@
======================================
  Files           88      88
  Stmts         3912    3976    +64
  Branches       396     408    +12
  Methods          0       0
======================================
+ Hit           1904    1960    +56
  Partial         35      35
- Missed        1973    1981     +8

Review entire Coverage Diff as of 3f1e7ee

Powered by Codecov. Updated on successful CI builds.

@patrys I sorted imports and used atomic as decorator instead of context manager

LGTM. Any takers for the JS counterpart? Otherwise merging will result in confusion.

@car3oon If you find a minute, the remaining work here is to automatically switch the carousel (product details page) to the appropriate image once a variant is picked.


feat(leverage): token supply limit

Description
Ref: #1227
NOTE: I decided to use Uint instead of Int. However it seams it has a problem with yaml serialization (one test failing - when using Int it was not failing). Maybe it's fixed in 0.46 . Will check it out.

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

OK, I see the reason why Uint doesn't work. Basically the type doesn't implement MarshalYAML. Falling back to Int.

I'm adding YAML support in SDK, we can change to Uint once this will be merged and backported to 0.46

After making a relationship with EnableMsgSupply tests starts to fail... so a bit more work :/

Codecov Report

Merging #1228 (f4dd1aa) into main (43c0441) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1228      +/-   ##
==========================================
+ Coverage   51.20%   51.26%   +0.05%
==========================================
  Files          67       67
  Lines        6659     6666       +7
==========================================
+ Hits         3410     3417       +7
  Misses       3009     3009
  Partials      240      240

Impacted Files
Coverage Δ

x/leverage/client/tests/tests.go
100.00% <100.00%> (ø)

x/leverage/types/token.go
72.15% <100.00%> (+2.28%)
:arrow_up:

Since it looks like we're going to want the option for unlimited supply, how about we interpret MaxTokenSupply = 0 + EnableMsgSupply = true as unlimited supply? Meanwhile, we can remove the requirement of "if supply disabled, max supply is 0"

how about we interpret MaxTokenSupply = 0 + EnableMsgSupply = true as unlimited supply?

Yes, I had the same idea. Now once Ming confirmed I will update this.

I've updated the meaning of max_supply=0


fix(deps): update module golang.org/x/mod to v0.21.0

This PR contains the following updates:

Package
Type
Update
Change

golang.org/x/mod
require
minor
v0.20.0 -> v0.21.0

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

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

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

The go directive was updated for compatibility reasons

Details:

Package
Change

go
1.22 -> 1.23.0

Let's put this on hold, as it may require further changes to upgrade to go 1.23

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: go.sum
Command failed: install-tool golang 1.23.3


GLOMAP is NOT parsing some of the input options

Hi,
I've been evaluating the behavior of GLOMAP when modifying some of the input parameters. I was surprised to find that, for some parameters, the performance of GLOMAP doesn't change at all, even when I input highly degraded configurations. For example:
glomap mapper \
    --database_path ${database} \
    --image_path ${rgb_path} \
    --output_path ${exp_folder_colmap} \
    --skip_view_graph_calibration 1 \
    --BundleAdjustment.optimize_intrinsics 0 \
    --BundleAdjustment.thres_loss_function 100000.0

After digging into the code, I suspect that some of these parameters are not being properly parsed. For instance, in glomap/glomap/estimators/bundle_adjustment.h:
BundleAdjusterOptions() : OptimizationBaseOptions() {
    thres_loss_function = 1.;
    loss_function = std::make_shared<ceres::HuberLoss>(thres_loss_function);
    solver_options.max_num_iterations = 200;
}

The thres_loss_function value is hard-coded there. Additionally, I suspect that even if I comment out that line, it won't work since the loss_function is set up before the thres_loss_function is parsed in exe/global_mapper.cc.
Could you help me confirm if my understanding is correct?
Thanks,

Resolved in #148


Update README.md

Added missing prop name.
I have no idea what Line 66 is. I didn’t add it

Thanks.. line 66 is a convention for our documentation site.


Add a mount and unmount timeout

Referencing
https://github.com/emccode/mesos-module-dvdi/issues/88#issuecomment-209152021
It would be good to add in a feature to enable a timeout for mount or unmount operations. In the case of mounts, a device discovery process may fail and it would be ideal to timeout at a specific interval to indicate the process is no longer trying to run. The same goes for the unmount operation where there may be (but shouldn't) scenarios where an unmount fails since the mount paths are still being used.

Hi @clintonskitson
it this problem may be related to this timeout problem ?
May 23 09:07:18 dfy3-slave1 rexray[8890]: time="2016-05-23T09:07:18Z" level=info msg="os driver initialized" moduleName=default-docker provider=linux
May 23 09:07:18 dfy3-slave1 rexray[8890]: time="2016-05-23T09:07:18Z" level=info msg="docker volume driver initialized" availabilityZone= iops= moduleName=default-docker provider=docker size= volumeRootPath="/data" volumeType=
May 23 09:07:18 dfy3-slave1 rexray[8890]: time="2016-05-23T09:07:18Z" level=debug msg="checking volume path cache setting" pathCache=true
May 23 09:07:18 dfy3-slave1 rexray[8890]: time="2016-05-23T09:07:18Z" level=info msg=vdm.List driverName=docker moduleName=default-docker
May 23 09:07:18 dfy3-slave1 rexray[8890]: time="2016-05-23T09:07:18Z" level=info msg="listing volumes" driverName=docker moduleName=default-docker
May 23 09:07:19 dfy3-slave1 rexray[8890]: time="2016-05-23T09:07:19Z" level=info msg=sdm.GetVolume driverName=Openstack moduleName=default-docker volumeID= volumeName=
May 23 09:07:21 dfy3-slave1 rexray[8890]: time="2016-05-23T09:07:21Z" level=info msg="timed out while monitoring module star"
May 23 09:07:21 dfy3-slave1 rexray[8890]: time="2016-05-23T09:07:21Z" level=error msg="default module(s) failed to start"
May 23 09:07:21 dfy3-slave1 rexray[8890]: time="2016-05-23T09:07:21Z" level=info msg="service sent registered modules start signals"

@sebmoule This is likely relating to the storage platform or amount of volumes coming back. There is a hard coded timeout of 3 seconds on the startup command (which includes a volume list). In 0.4 we bumped it to 10 seconds, and made it configurable.


error reading wallet.dat file: wallet can be read, but transaction data missing

Issue Template
Receiving an error when starting up Verge QT 4.0 “warning! Error reading Wallet.dat. All keys read correctly, but transaction data or address entries might be missing or incorrect
I hav tried already everything, from restoring an old wallet, trying older wallet.dat files,  I don't know what to do anymore.
I send coins from an old wallet that wasn't synked to another wallet. The wallet did not sync anymore, so I downloaded the blockchain, but it wouldn't sync then either. on telegram I was advised to upgrade the wallet, first saving the wallet.dat file.
I did, and replaced the wallet.dat.
this went well, but again the wallet did not want to sync.
Then I tried to upload the blockchain to jumpstart the syncing. This did not work.
Then I removed the wallets completely, installed the Q4 wallet again, replaced the wallet.dat again. and now I get this error.
Prerequisites

[ ] Are you running the latest version? yes

User Story:

"I'm submitting a ... "

[ ] bug report
[ ] feature request
[ x] support request
[ ] translation request

 Mac version 10.13.6
Possible Solution I still have the 15 word sees code, several wallets.dat files that I saved, and my private key. is there any way that I can install the mobile wallet?

Steps to Reproduce (for bugs)
 send coins from wallet when it isn't synced. Don't let it sync, but save the wallet.dat. Then reinstall wallet and see if this error occurs.
I can also send you the dat file.
Kind regards
Hefziba

what happens when you say ok to the warning? are you able to get into the debug console of the wallet? in the blockchain data directory, you have a file called debug.log. can you pastebin it and give us a link to it? maybe delete it first, open the wallet for a while, and then paste it to us so we can see exactly why its having this issue..

If I say ok the wallet force closes, so I can't get to the debut log
My first wallet.dat file I ever saved works , I can open the wallet and see the first transaction, but it is not syncing. In the debug file I get errors in this case. I tried to add the downloaded blockchain, and then it syncs  before opening the wallet, but after it says 100% the wallet freezes and is un-responsive.

what I mean is that with the newest wallet.dat files I cannot get into the wallet, I only see this error. With the old wallet.dat I can get into the wallet, but I will not sync.

ok, go back to the original wallet.dat that works but doesnt sync. the syncing is the problem. are you running other wallets at the same time, or in a country that blocks tor?

well justin beat me to it, but i'll post anyways 👍
There are some guides here for troubleshooting QT issues:
https://verge.zendesk.com/hc/en-us/sections/360002295772-QT-Wallet
Are you in a country that blocks Tor like Iran, Turkey, or China?
Just for troubleshooting purposes -- and to get your funds -- you could always try on a different computer.  Mac version of QT 4 seemed very unstable, and becomes unresponsive a lot.
But if you had access to a Windows or UNIX machine, your wallet.dat , as long as it's not corrupt, would work fine on Mac, Windows, and/or UNIX.

I am in the Netherlands, so I guess not, but could it be Sofos that is blocking it, a software I have installed myself?

Thank you both. Ok I will have a look at my options.

windows computer
go through the zen desk

Just for my knowledge, does it matter if I have an old or recent backup wallet.dat?

it should not, but it sounds like the copy you have that is giving you an error, is corrupt. please use the original one you have. the wallet.dat wont have an affect on syncing. the syncing problem is what we need to fix. port 21102 is the one verge qt uses, and tor is also running on it. if you have tor already running, that could be one problem.

each wallet.dat will have 1 or more "addresses".  If all of your coins are on addressXYZ, and your wallet.dat has addressXYZ ... then it doesn't matter if it's recent or old.
If you make transactions, sometimes some of your coins move to a "change address", we'll call it addressABC.  So if that was the case, your older wallet.dat might not have addressABC.
But yeah as Justin said -- your new Mac not getting any connections/sync'd at all is weird and i would check out those articles to see if you can do that.

This is more technical than i am used to. Where can I check if Tor is
already running or if port 21102 is already being used?
I need to go to sleep ( 3am here)  and will try to fix it tomorrow. But an
answer on above question is definitely appreciated.
On Thu, 16 May 2019 at 02:49, sunerok<EMAIL_ADDRESS>wrote:

it should not, but it sounds like the copy you have that is giving you an
error, is corrupt. please use the original one you have. the wallet.dat
wont have an affect on syncing. the syncing problem is what we need to fix.
port 21102 is the one verge qt uses, and tor is also running on it. if you
have tor already running, that could be one problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vergecurrency/VERGE/issues/907?email_source=notifications&email_token=AICC6PWLMPHEYSGUQ7RKP3LPVSVSBA5CNFSM4HNH2BAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQKYPQ#issuecomment-492874814,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AICC6PVOKAXHESUDGRKHDZTPVSVSBANCNFSM4HNH2BAA
.

if you dont have tor installed, then its probably not running, which is good, because its built into the app. i meant are you running other crypto coin wallets at the same time?

@jeff I might than have lost quite some coins. I made 3 backups of the
recent wallet, but all are corrupt.
And coins were send after the old wallet with an out of sync wallet. Coins
were out of my wallet, so probably send to an in between address.
We will see.
On Thu, 16 May 2019 at 02:56, Hefziba ten Brink<EMAIL_ADDRESS>wrote:

This is more technical than i am used to. Where can I check if Tor is
already running or if port 21102 is already being used?
I need to go to sleep ( 3am here)  and will try to fix it tomorrow. But an
answer on above question is definitely appreciated.
On Thu, 16 May 2019 at 02:49, sunerok<EMAIL_ADDRESS>wrote:

it should not, but it sounds like the copy you have that is giving you an
error, is corrupt. please use the original one you have. the wallet.dat
wont have an affect on syncing. the syncing problem is what we need to fix.
port 21102 is the one verge qt uses, and tor is also running on it. if you
have tor already running, that could be one problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vergecurrency/VERGE/issues/907?email_source=notifications&email_token=AICC6PWLMPHEYSGUQ7RKP3LPVSVSBA5CNFSM4HNH2BAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQKYPQ#issuecomment-492874814,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AICC6PVOKAXHESUDGRKHDZTPVSVSBANCNFSM4HNH2BAA
.

Thank you both for helping. Actually got a friend to respond in telegram, that I have known for a long time, but did not know he was part of verge: Kaspar_NL.    He helped me solve it and you can close the issue.
For others that had the same issue: I cleaned my whole library from any reminiscent verge wallet files, that were there. and installed the latest wallet from the verge website.
My last saved Wallet.dat file responded again, without an error, and wasn't corrupted.  However, the wallet did not want to sync and I downloaded the blockchain, as described in many help sections.  The wallet again stopped responding, but I reopened it and gave it time. Finally it opened and synced. My last transaction that was still pending went through when the blockchain was synced. If this hadn't worked I would've tried the last wallet.dat file on windows.  Also I learned that you can encrypt the wallet.dat file to make sure it doesn't get stolen and prevent it from getting corrupted.


Use ByteRange instead of FileRange in surface AST

Replaces FileRange (ByteRange + FileId) with ByteRange in all surface AST types produced by parsing and consumed by elaboration. This shaves 8 bytes off each surface Term, and only makes elaboration slightly more complicated, so ought to be a good performance win.

It does get a little strange when thinking about how multi-file elaboration fits in. Not sure the best approach there?

Multi-file elaboration should be fine: use a separate elab_context for each file/module, and share item_env (and any other global state` between them.


Alter guis removed with clearguis

Currently, clearguis deletes guis made by notify and pm, but does not remove guis made by the n command. I believe functionally it makes more sense to not remove notify and pm boxes, but to remove n (as h and m messages are removed).
I find myself usually using the clearguis command when I have accidentally used the m, h, or n commands, but not ever when I accidentally use the notify or pm commands. Using the clearguis command currently puts important pms or notify boxes at risk, when it really is used just to remove unnecessary n, m, h, or alert frames.

I agree with your suggestion; a change has been made accordingly and will be available in the next patch release.


Remove ProfileProviders

This looks like it can be easily removed because Slick already has same stuff out of the box. Should be investigated and replaced with Slick ones.

Cannot be done as Slick profiles doen't have such functionality.


bug-3635 fix generating kubeadmin-password for OKD preset

Fixes: Issue #3635
Solution/Idea
To generate the kubeadmin-password file because it is missing which is causing the bug
Proposed changes
After investigating I noticed there is a function that created the file but only for the OpenShift prefix.
Adding the OKD to it solved the issue.
This may be further improved if in the future that distinction will go away, for now this seems like a straight forward fix.
Testing
We need to test if the OKD 4.12 cluster start attempt does not fail on the missing kubeadmin_password file.
Clean:

crc delete -f

crc cleanup
Set prefix:

crc config set preset okd

crc setup

crc start --log-level debug

Note : I have an issue that I had before that does seem unrelated to my PR, this issue was already present in the branch, but is not present in the 2.19 binary that is in public release.
It might be a bug that is introduced in the current branch, I get :
Temporary error: ssh command error:
command : timeout 5s oc get nodes --context admin --cluster crc --kubeconfig /opt/kubeconfig
err     : Process exited with status 1

Again, this change did not affect that behaviour but needs to be verified.

/ok-to-test

The test in question failing is by my best understanding unrelated to the PR and also happens in the main branch without this change. It seems like a problem with the image, because the kube-apiserver does not start. Snippet from the log:

May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: E0526 08:32:57.184519   25372 kubelet.go:2471] "Error getting node" err="node \"crc-pmmhp-master-0\" not found"
May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: E0526 08:32:57.192886   25372 certificate_manager.go:471] kubernetes.io/kube-apiserver-client-kubelet: Failed while requesting a signed certificate from the control plane: cannot create certificate signing request: Post "https://api-int.crc.testing:6443/apis/certificates.k8s.io/v1/certificatesigningrequests": net/http: TLS handshake timeout
May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: E0526 08:32:57.285745   25372 kubelet.go:2471] "Error getting node" err="node \"crc-pmmhp-master-0\" not found"
May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: I0526 08:32:57.308305   25372 kubelet_node_status.go:376] "Setting node annotation to enable volume controller attach/detach"
May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: I0526 08:32:57.309190   25372 kubelet_node_status.go:590] "Recording event message for node" node="crc-pmmhp-master-0" event="NodeHasSufficientMemory"
May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: I0526 08:32:57.309224   25372 kubelet_node_status.go:590] "Recording event message for node" node="crc-pmmhp-master-0" event="NodeHasNoDiskPressure"
May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: I0526 08:32:57.309232   25372 kubelet_node_status.go:590] "Recording event message for node" node="crc-pmmhp-master-0" event="NodeHasSufficientPID"
May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: E0526 08:32:57.386912   25372 kubelet.go:2471] "Error getting node" err="node \"crc-pmmhp-master-0\" not found"
May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: E0526 08:32:57.488012   25372 kubelet.go:2471] "Error getting node" err="node \"crc-pmmhp-master-0\" not found"
May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: E0526 08:32:57.588968   25372 kubelet.go:2471] "Error getting node" err="node \"crc-pmmhp-master-0\" not found"
May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: I0526 08:32:57.646759   25372 patch_prober.go:29] interesting pod/kube-controller-manager-crc-pmmhp-master-0 container/cluster-policy-controller namespace/openshift-kube-controller-manager: Startup probe status=failure output="Get \"https://<IP_ADDRESS>:10357/healthz\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" start-of-body=
May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: I0526 08:32:57.646990   25372 prober.go:114] "Probe failed" probeType="Startup" pod="openshift-kube-controller-manager/kube-controller-manager-crc-pmmhp-master-0" podUID=5481dd520e901b88486c4151d59983b3 containerName="cluster-policy-controller" probeResult=failure output="Get \"https://<IP_ADDRESS>:10357/healthz\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
May 26 08:32:57 crc-pmmhp-master-0 kubenswrapper[25372]: E0526 08:32:57.690071   25372 kubelet.go:2471] "Error getting node" err="node \"crc-pmmhp-master-0\" not found"

I tried troubleshooting this but I can´t find the cause, because all point to oc commands that I find rely on the api server being up. kube-apiserver shows exited in crictl and it does not support starting so at the moment I have no direct idea on how to continue.
Again, this problem is unrelated to the PR, so perhaps a new ticket should be created to address that ?

Don't look too closely at e2e-crc, it's very unreliable :(

Don't look too closely at e2e-crc, it's very unreliable :(

hi, although not relevant for this case, the test might be useful, because I am unable to get the kubelet to start. So I think in this case it might be right? I am not sure because this is all first time for me. I built the crc binary with make release and used that for all the commands. Another thing that seems off is that crc status always indicates that setup needs to be run.
It may be that I missed something in the process, if I did I am happy to learn. As long as the setup for OKD gets tested I am sure it will be fine and at least this issue will be resolved. Thanks for approving!

I looked further into the issue of the server starting and found etcd also to be down. That turned out to be similar to : https://github.com/crc-org/crc/issues/1786 . In my case I changed <IP_ADDRESS> to <IP_ADDRESS> in /etc/kubernetes/manifests/etcd-pod.yaml . After a restart of the kubelet service, etcd started and kube-apiserver too checked by crictl ps.
Now the certificates are apparently not rotating because crc start gives:
INFO Starting kubelet service
INFO Kubelet client certificate has expired, renewing it... [will take up to 8 minutes]
Failed to renew TLS certificates: please check if a newer CRC release is available: Temporary error: certificate /var/lib/kubelet/pki/kubelet-client-current.pem still expired (x59)

That file actually does not exist in the VM. Stopping the api server did not help.
Here it says that it should be automatic: https://github.com/okd-project/okd/issues/1123 I guess that failed.
It would be useful to document the procedure.
I found a solution that says:
$ oc get csr | grep -i pending
$ for i in `oc get csr --no-headers | grep -i pending |  awk '{ print $1 }'`; do oc adm certificate approve $i; done

The first command showed expired certs, the second cannot execute because :
Error from server (Forbidden): secrets is forbidden: User "system:serviceaccount:openshift-machine-config-operator:node-bootstrapper" cannot list resource "secrets" in API group "" at the cluster scope
I am unable to login to the api as kubeadmin by using either kubeconfig so I cannot proceed.
Any solution and documentation of rotation commands is appreciated :) !

Just for completeness sake, I was able to get further but not succeed.
First issue was kubelet not wanting to rotate cert because no cert existed.
Needed to mkdir /var/lib/kubelet/pki - there I copied the certs from a running instance ( kubelet-client-current.pem and kubelet-server-current.pem ).
After that the pullsecret was not written to, the /var/lib/kubelet/config.json showed {}, to fix that I copied one from a working instance.
Last but not least, the config map here was missing:
ssh command error:
command : timeout 30s oc delete -n openshift-machine-config-operator configmap machine-config-controller --context admin --cluster crc --kubeconfig /opt/kubeconfig
err     : Process exited with status 1
[ubuntu@studiox360g5-lan linux-amd64]$ oc delete -n openshift-machine-config-operator configmap machine-config-controller --context admin --cluster crc --kubeconfig /opt/kubeconfig
error: stat /opt/kubeconfig: no such file or directory

I was able to fix that with on the node ( login : ssh -i /home/ubuntu/.crc/machines/crc/id_ecdsa -p 22<EMAIL_ADDRESS>) then:
oc create -n openshift-machine-config-operator configmap machine-config-controller --context admin --cluster crc --kubeconfig /opt/kubeconfig
Then there was another error :
INFO Loading bundle: crc_okd_libvirt_4.12.0-0.okd-2023-04-16-041331_amd64...
INFO Starting CRC VM for okd 4.12.0-0.okd-2023-04-16-041331...
INFO CRC instance is running with IP <IP_ADDRESS>
INFO CRC VM is running
INFO Configuring shared directories
INFO Check internal and public DNS query...
INFO Check DNS query from host...
INFO Verifying validity of the kubelet certificates...
INFO Starting kubelet service
INFO Waiting for kube-apiserver availability... [takes around 2min]
INFO Waiting until the user's pull secret is written to the instance disk...
INFO Changing the password for the kubeadmin user
INFO Updating cluster ID...
INFO Updating root CA cert to admin-kubeconfig-client-ca configmap...
INFO Starting okd instance... [waiting for the cluster to stabilize]
INFO 8 operators are progressing: dns, image-registry, ingress, kube-storage-version-migrator, network, ...
INFO 8 operators are progressing: dns, image-registry, ingress, kube-storage-version-migrator, network, ...
INFO 8 operators are progressing: dns, image-registry, ingress, kube-storage-version-migrator, network, ...
INFO 8 operators are progressing: dns, image-registry, ingress, kube-storage-version-migrator, network, ...
INFO 8 operators are progressing: dns, image-registry, ingress, kube-storage-version-migrator, network, ...
INFO 8 operators are progressing: dns, image-registry, ingress, kube-storage-version-migrator, network, ...
INFO 8 operators are progressing: dns, image-registry, ingress, kube-storage-version-migrator, network, ...
INFO 8 operators are progressing: dns, image-registry, ingress, kube-storage-version-migrator, network, ...
ERRO Cluster is not ready: cluster operators are still not stable after 10m0.712906048s
INFO Adding crc-admin and crc-developer contexts to kubeconfig...
ERRO Cannot update kubeconfig: Head "https://oauth-openshift.apps-crc.testing": dial tcp <IP_ADDRESS>:443: connect: connection refused
Started the OpenShift cluster.

I also noticed that the 2.19 version runs Fedora 36 en this new one 37.
In general it looks like a lot of permission/setup issues that someone with more experience and knowledge may be able to quickly spot?


Tower of Hanoi in python

Tower of Hanoi in python using recursive logic

Please assign this issue to me

@anomekumar08 can you please assign this issue to me

@anomekumar08 I have added the code.

okk... @theyashwanthsai

hey can you please assign it to me too.

Please check and merge my PR #98

Can you please assign this issue to me?


Housekeeping

It would be nice to have a button (on each repos settings page) to run a housekeeping operation. This operation is useful to clean a repository and decrease is size.
Usually these two commands are run:
git prune
git gc --aggressive

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38979600-housekeeping?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

I think there's a periodic routine doing those things, (why) do you also want a button ?

in any case, I guess if you provide a PR the approval process would be smoother :)

I think manual housekeeping is better than CRON task, cause is useless to run housekeeping on old / archived repos.

I don't think the periodic routine can be configured, atm.
I guess an overall review of the system is needed, are you up for that ?
Ideally we'd have:

Configurable periodic routine (frequency, exclusion list)
Record of when the routine last run, shown in admin panel
Button to force a run the routine for a single repository
Button to force a run of the periodic routine

admin UI have button to "housekeep" all repos and I think there also exist a cronjob

I'll close feel free to ask for reopen if i missed something


dropped content

Hi Gerrit,
attached are two idml test cases and the two corresponding hub.xml (conversion made with the latest git pull).
In the file test_no_mml.hub.xml everything is ok.
In the file test_with_mml.hub.xml the content of the para before the table is missing.
It seems that the issue arise only when you have mml and a Content and a Table in the same CharacterStyleRange, but not always, as I have files where only some paras gets dropped.
I have solved the problem by editing the source indd and making sure all tables are in their CharacterStyleRange with no other Content elements, but I think this should be investigated further.
test-case.zip

Hi Peppo,
Thanks for reporting it. We are all very busy right now, so I can’t promise when we will be able to analyze and fix it, and who is going to do it. I hope that some colleague can squeeze it in.
Gerrit

Hi Peppo,
I made a fix to MathTools processing and hope this will solve your issue.
Best, Martin

Yes, Problem solved!
Thanks Martin


Renaming Components and Build Order

Information

Qiskit Metal version: all
Python version: all
Operating system: all

What is the current behavior?
If we choose to rename the key of a component such as a Qubit, the key, value pair automatically gets moved to the end of the dictionary. This can cause disruptions in dependencies such as building the CPW before the transmon
Steps to reproduce the problem
Create some components, rename one, notice the order changes
What is the expected behavior?
The order does not change -- update occurs in place.
Suggested solutions

This is so integrated into the order of rebuild.  The workaround is to save the order in a Jupyter notebook or script.