Cache inconsistency when using esp_partition_mmap and esp_partition_write_raw (IDFGH-11558)

Board
ESP32 Dev Module
Device Description
Using an ESP32 Dev Module with 4MB of flash
Hardware Configuration
No additional hardware required
Version
latest master (checkout manually)
IDE Name
Arduino IDE
Operating System
Windows 10
Flash frequency
80 Mhz
PSRAM enabled
no
Upload speed
921600
Description
Now this gets a bit complicated, I hope I can explain it in an understandable way. I have a (large) program that uses esp_partition_write_raw to write data sequentially to a special flash partition. That partition is simultaneously mapped to RAM using esp_partition_mmap, so that I can read from it as if it was RAM.
For safety, I am doing a memcmp after writing each block, to make sure the data gets written correctly. With Arduino Core V2.X this always worked flawlessly, but now with 3.X I suddenly get comparison errors between what I've written to the flash and what I read back. When using esp_partition_read_raw to force a read from the flash, the comparison always succeeds.
I first thought I had a broken flash chip, so I wrote the attached flash test program, that first didn't show any error at all, but then I reduced the block size and whoa, the bug showed up. (see comment in line 55, "int writeLen = ...")
At the moment, I have no other explanation than assuming that writing to flash doesn't update the CPU cache line we've just been reading from. Is there a way to force invalidating the CPU cache? As said, I have never observed this issue with the 2.X core.
The sample code below requires this partitions.csv file:
# ESP32 partition map. Total flash size reserved 4 MiB
# Name        | Type     | SubType | Offset  | Size    | Flags
nvs,            data,      nvs,      0x9000,   0x6000,
phy_init,       data,      phy,      0xf000,   0x1000,
factory,        app,       factory,  0x10000,  0x64000,
remaining,      data,      0x06,0x74000,  0x38C000,

Sketch
#include "esp_partition.h"
const char* FLASH_TAG = "Flash";
const esp_partition_t* partition; // the test partition
size_t length; // The partition length
size_t blockSize; // the size of a flash block
byte* testBuf;
byte* mappedAddress; // Base address of memory mapped region
uint32_t map_handle; // Memory map handle
void setup() {
  Serial.begin(115200);
  delay(100);
  // Find the test partition
  partition = esp_partition_find_first(ESP_PARTITION_TYPE_DATA, ESP_PARTITION_SUBTYPE_ANY, "remaining");
  if (partition == nullptr)
  {
    ESP_LOGE(FLASH_TAG, "FATAL: Could not locate test partition.");
    return;
  }
  length = partition->size;
  blockSize = partition->erase_size;
  ESP_LOGI(FLASH_TAG, "Test partition has size %d", length);
  testBuf = (byte*)malloc(blockSize);
  if (length % blockSize != 0)
  {
    ESP_LOGW(FLASH_TAG, "Partition length is not a multiple of %d", blockSize);
  }

  const void* tempPtr;
  // Memory-map the test partition (note: max size 4MB)
  esp_err_t error = esp_partition_mmap(partition, 0, length, ESP_PARTITION_MMAP_DATA, &tempPtr, &map_handle);
  if (error != 0)
  {
    ESP_LOGE(FLASH_TAG, "Unable to map memory. Error %d", error);
  }
  mappedAddress = (byte*)tempPtr;
  ESP_LOGI(FLASH_TAG, "Mapped partition with size %d to address 0x%x", length, mappedAddress);

  delay(5000);
}

// Calculates the memory address for a flash partition offset
void* GetAddressFromOffset(int32_t offset)
{
  return mappedAddress + offset;
}

void TestPattern(byte pattern)
{
  for (int i = 0; i < blockSize; i++)
  {
    testBuf[i] = pattern;
  }
  size_t offset = 0;

  int writeLen = blockSize; // Everything is fine with large blocks (blockSize is 4096), but if this is changed to 40, errors start happening.

  // Flasht the whole block
  while (offset < length)
  {
    ESP_LOGI(FLASH_TAG, "Flashing pattern 0x%x to offset 0x%x", (int)pattern, offset);
    esp_err_t errNo = esp_partition_write_raw(partition, offset, testBuf, writeLen);
    if (errNo != 0)
    {
      ESP_LOGE(FLASH_TAG, "Error flashing block: %d", errNo);
      delay(10000);
    }

    void* readFrom = GetAddressFromOffset(offset);
    if (memcmp(testBuf, readFrom, writeLen) != 0)
    {
      // This error happens repeatedly when writeLen is 40
      ESP_LOGE(FLASH_TAG, "Error verifying flash with mapped access");
      delay(10000);
    }

    offset += writeLen;
  }

  offset = 0;

  // Read back the whole block
  while (offset < length)
  {
    // ESP_LOGI(FLASH_TAG, "Verifying pattern 0x%x at offset 0x%x", (int)pattern, offset);
    esp_err_t errNo = esp_partition_read_raw(partition, offset, testBuf, blockSize);
    if (errNo != 0)
    {
      ESP_LOGE(FLASH_TAG, "Error reading block");
      delay(10000);
    }
    for (int i = 0; i < blockSize; i++)
    {
      if (testBuf[i] != pattern)
      {
        ESP_LOGE(FLASH_TAG, "Flash error at offset 0x%x. This is bad", offset + i);
        delay(5000);
        break;
      }
    }
    offset += blockSize;
  }

  ESP_LOGI(FLASH_TAG, "Pass with pattern 0x%x successful", pattern);
}

void loop() {
  ESP_LOGI(FLASH_TAG, "Clearing memory");
  esp_err_t errNo = esp_partition_erase_range(partition, 0, length);
  if (errNo != 0)
  {
    ESP_LOGE(FLASH_TAG, "Error: Could not erase flash: %d", errNo);
  }
  TestPattern(0x75);
  delay(2000);
  TestPattern(0x0);
  delay(60000);
}

Debug Message
=========== Before Setup Start ===========
Chip Info:
------------------------------------------
  Model             : ESP32
  Package           : D0WD-Q5
  Revision          : 100
  Cores             : 2
  Frequency         : 240 MHz
  Embedded Flash    : No
  Embedded PSRAM    : No
  2.4GHz WiFi       : Yes
  Classic BT        : Yes
  BT Low Energy     : Yes
  IEEE 802.15.4     : No
------------------------------------------
INTERNAL Memory Info:
------------------------------------------
  Total Size        :   389092 B ( 380.0 KB)
  Free Bytes        :   358512 B ( 350.1 KB)
  Allocated Bytes   :    23448 B (  22.9 KB)
  Minimum Free Bytes:   353036 B ( 344.8 KB)
  Largest Free Block:   122868 B ( 120.0 KB)
------------------------------------------
Flash Info:
------------------------------------------
  Chip Size         :  4194304 B (4 MB)
  Block Size        :    65536 B (  64.0 KB)
  Sector Size       :     4096 B (   4.0 KB)
  Page Size         :      256 B (   0.2 KB)
  Bus Speed         : 80 MHz
  Bus Mode          : QIO
------------------------------------------
Partitions Info:
------------------------------------------
                nvs : addr: 0x00009000, size:    24.0 KB, type: DATA, subtype: NVS
           phy_init : addr: 0x0000F000, size:     4.0 KB, type: DATA, subtype: PHY
            factory : addr: 0x00010000, size:   400.0 KB, type:  APP, subtype: FACTORY
          remaining : addr: 0x00074000, size:  3632.0 KB, type: DATA, subtype: UNDEFINED
------------------------------------------

------------------------------------------
Software Info:
------------------------------------------
  Compile Date/Time : Nov 25 2023 17:30:34
  Compile Host OS   : windows
  ESP-IDF Version   : v5.1.1-686-gb6a66b7d8c-dirty
  Arduino Version   : 3.0.0
------------------------------------------
Board Info:
------------------------------------------
  Arduino Board     : ESP32_DEV
  Arduino Variant   : esp32
  Arduino FQBN      : espressif:esp32:esp32:UploadSpeed=921600,CPUFreq=240,FlashFreq=80,FlashMode=qio,FlashSize=4M,PartitionScheme=default,DebugLevel=verbose,PSRAM=disabled,LoopCore=1,EventsCore=0,EraseFlash=none,JTAGAdapter=default,ZigbeeMode=default
============ Before Setup End ============
[   670][V][esp32-hal-uart.c:409] uartBegin(): UART0 baud(115200) Mode(800001c) rxPin(3) txPin(1)
[   779][I][ESP_FlashTest.ino:21] setup(): [Flash] Test partition has size 3719168
[   787][I][ESP_FlashTest.ino:35] setup(): [Flash] Mapped partition with size 3719168 to address 0x3f414000
=========== After Setup Start ============
INTERNAL Memory Info:
------------------------------------------
  Total Size        :   389092 B ( 380.0 KB)
  Free Bytes        :   352220 B ( 344.0 KB)
  Allocated Bytes   :    29372 B (  28.7 KB)
  Minimum Free Bytes:   346800 B ( 338.7 KB)
  Largest Free Block:   122868 B ( 120.0 KB)
------------------------------------------
GPIO Info:
------------------------------------------
                  1 : UART_TX
                  3 : UART_RX
============ After Setup End =============

  5864][I][ESP_FlashTest.ino:101] loop(): [Flash] Clearing memory
[ 22132][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0x0
[ 22141][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0x28
[ 22150][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0x50
[ 22158][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0x78
[ 22167][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0xa0
[ 22176][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0xc8
[ 22185][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0xf0
[ 22194][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0x118
[ 22202][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0x140
[ 22211][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0x168
[ 22220][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0x190
[ 22229][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0x1b8
[ 22238][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0x1e0
....
.... Many lines....
....
[ 33148][E][ESP_FlashTest.ino:67] TestPattern(): [Flash] Error verifying flash with mapped access
[ 43156][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0xc030
[ 43165][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0xc058
[ 43173][E][ESP_FlashTest.ino:67] TestPattern(): [Flash] Error verifying flash with mapped access
[ 53182][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0xc080
[ 53191][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0xc0a8
[ 53199][E][ESP_FlashTest.ino:67] TestPattern(): [Flash] Error verifying flash with mapped access
[ 63208][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0xc0d0
[ 63217][I][ESP_FlashTest.ino:56] TestPattern(): [Flash] Flashing pattern 0x75 to offset 0xc0f8
[ 63225][E][ESP_FlashTest.ino:67] TestPattern(): [Flash] Error verifying flash with mapped access
....
.... More stuff

Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide

[X] I confirm I have checked existing issues, online documentation and Troubleshooting guide.

Thanks for reporting the issue @pgrawehr. We do have a test for this scenario, but seems like it uses the legacy spi_flash_write* API. Perhaps there is a difference in the behavior of esp_flash_* API which we didn't consider. We'll investigate this.
https://github.com/espressif/esp-idf/blob/master/components/spi_flash/test_apps/flash_mmap/main/test_flash_mmap.c#L438-L451

I have the same problem as @pgrawehr . Any news or workaround on this?

@polhenarejos No, I did not really find a workaround yet. The problem doesn't seem to occur for me if I don't read the memory until everything is written. But there's no guarantee for that, I suppose.

What I'm doing to "flush" is to unmap() and mmap() again, but I am not sure how intensive is this.

If I remember correctly, that didn't help for me. But you can try it with the sketch above.


I have some problems with the docker compose deployment.

version: '3.4'

services:
  api:
    depends_on:
      - elasticsearch
      - redis
    build:
      context: .
      target: api
    image: exceptionless/api-ci:latest
    environment:
      EX_AppMode: Production
      EX_ConnectionStrings__Cache: provider=redis
      EX_ConnectionStrings__Elasticsearch: server=http://elasticsearch:9200
      #EX_ConnectionStrings__Email: smtps://user:password@smtp.host.com:587
      EX_ConnectionStrings__MessageBus: provider=redis
      #EX_ConnectionStrings__Metrics: provider=statsd;server=statsd;
      EX_ConnectionStrings__Queue: provider=redis
      EX_ConnectionStrings__Redis: server=redis,abortConnect=false
      EX_ConnectionStrings__Storage: provider=folder;path=/app/storage
      EX_RunJobsInProcess: 'false'
    ports:
      - 5050:80
    volumes:
      - C:/docker/volume/exceptionless/appdata:/app/storage

  jobs:
    depends_on:
      - api
    build:
      context: .
      target: job
    image: exceptionless/job-ci:latest
    command: run-all
    environment:
      EX_AppMode: Production
      EX_ConnectionStrings__Cache: provider=redis
      EX_ConnectionStrings__Elasticsearch: server=http://elasticsearch:9200
      #EX_ConnectionStrings__Email: smtps://user:password@smtp.host.com:587
      EX_ConnectionStrings__MessageBus: provider=redis
      #EX_ConnectionStrings__Metrics: provider=statsd;server=statsd;
      EX_ConnectionStrings__Queue: provider=redis
      EX_ConnectionStrings__Redis: server=redis,abortConnect=false
      EX_ConnectionStrings__Storage: provider=folder;path=/app/storage
    volumes:
      - C:/docker/volume/exceptionless/appdata:/app/storage

  ui:
    image: exceptionless/ui-ci:latest
    environment:
      AppMode: Development
      EX_ApiUrl: http://localhost:5050
    ports:
      - 5100:80

  elasticsearch:
    image: exceptionless/elasticsearch:1
    environment:
      cluster.name: 'exceptionless'
      bootstrap.memory_lock: 'true'
      discovery.type: single-node
      ES_JAVA_OPTS: '-Xms512m -Xmx512m'
      xpack.security.enabled: 'false'
      xpack.graph.enabled: 'false'
      xpack.watcher.enabled: 'false'
    ports:
      - 9200:9200
      - 9300:9300
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - C:/docker/volume/exceptionless/esdata:/usr/share/elasticsearch/data

  # kibana:
  #   depends_on:
  #     - elasticsearch
  #   image: exceptionless/kibana:1
  #   environment:
  #     xpack.security.enabled: 'false'
  #   ports:
  #     - 5601:5601

  redis:
    image: redis:alpine
    ports:
      - 6379:6379

api have some problems when i search infomation
[08:31:14 ERR] Error getting mapping for index events
Server Error (Index=events Type=index_not_found_exception): no such index
[404] GET /events/_mapping/events
[08:31:14 ERR] Error getting mapping for index events
Server Error (Index=events Type=index_not_found_exception): no such index
[404] GET /events/_mapping/events

this is es log

Can you hit Elasticsearch on port 9200? I'd make sure that's exposed and you can hit it.

Visible in the browser

If you run GET _cat/indicies in elastic search is there any indices. It's like it cannot talk to it. That docker compose file won't even run on my machine. Have you just tried using ours as is? Can you do docker-compose up elasticsearch redis and then clone this repository and copy some of the config to the yaml file in the web project and start debugging? It might say a different error (I'm really curious what the error is).

400 bad request

Here is the link to documentation: https://www.elastic.co/guide/en/elasticsearch/reference/5.6/cat-indices.html

Here is the link to documentation: https://www.elastic.co/guide/en/elasticsearch/reference/5.6/cat-indices.html

I encountered the same problem, however, the elasticsearch _cat/indices command runs successfully:

It seams like  index "events“ not built in  elasticsearch  ?

version: '3.4'

services:
  api:
    depends_on:
      - elasticsearch
      - redis
    image: exceptionless/api-ci:latest
    container_name: ex_api
    environment:
      EX_AppMode: Production
      EX_ConnectionStrings__Cache: provider=redis
      EX_ConnectionStrings__Elasticsearch: server=http://elasticsearch:9200
      #EX_ConnectionStrings__Email: smtps://user:password@smtp.host.com:587
      EX_ConnectionStrings__MessageBus: provider=redis
      #EX_ConnectionStrings__Metrics: provider=statsd;server=statsd;
      EX_ConnectionStrings__Queue: provider=redis
      EX_ConnectionStrings__Redis: server=redis,abortConnect=false
      EX_ConnectionStrings__Storage: provider=folder;path=/app/storage
      EX_RunJobsInProcess: 'false'
    ports:
      - 5000:80
    volumes:
      - C:/docker/volume/exceptionless/appdata:/app/storage

  jobs:
    depends_on:
      - api
    image: exceptionless/job-ci:latest
    container_name: ex_job
    command: run-all
    environment:
      EX_AppMode: Production
      EX_ConnectionStrings__Cache: provider=redis
      EX_ConnectionStrings__Elasticsearch: server=http://elasticsearch:9200
      #EX_ConnectionStrings__Email: smtps://user:password@smtp.host.com:587
      EX_ConnectionStrings__MessageBus: provider=redis
      #EX_ConnectionStrings__Metrics: provider=statsd;server=statsd;
      EX_ConnectionStrings__Queue: provider=redis
      EX_ConnectionStrings__Redis: server=redis,abortConnect=false
      EX_ConnectionStrings__Storage: provider=folder;path=/app/storage
    volumes:
      - C:/docker/volume/exceptionless/appdata:/app/storage

  ui:
    image: exceptionless/ui-ci:latest
    container_name: ex_ui
    environment:
      AppMode: Development
      BaseUrl: http://localhost:5000
      EX_ApiUrl: http://localhost:5000
    ports:
      - 5100:80

  elasticsearch:
    container_name: ex_es
    image: docker.elastic.co/elasticsearch/elasticsearch:5.6.16
    environment:
      cluster.name: 'exceptionless'
      bootstrap.memory_lock: 'true'
      discovery.type: single-node
      ES_JAVA_OPTS: '-Xms512m -Xmx512m'
      xpack.security.enabled: 'false'
      xpack.graph.enabled: 'false'
      xpack.watcher.enabled: 'false'
    ports:
      - 9200:9200
      - 9300:9300
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - C:/docker/volume/exceptionless/esdata:/usr/share/elasticsearch/data

  # kibana:
  #   depends_on:
  #     - elasticsearch
  #   image: exceptionless/kibana:1
  #   environment:
  #     xpack.security.enabled: 'false'
  #   ports:
  #     - 5601:5601

  redis:
    container_name: ex_redis
    image: redis:alpine
    ports:
      - 6379:6379

Still have problems

Were you able to resolve this issue?

Were you able to resolve this issue?

not yet   :<

你能解决这个问题吗？

I don't need to deploy it with docker.

I'm looking into this now with docker-compose. Can you clone our repository and use the latest docker compose file (I fixed a bunch of issues as well as added configuration settings that can be modified to set api/base url). Also I'd recommend opening up kibana and running delete * and restart all the docker containers to start over just to be safe. Please note running the previous command will remove all elasticsearch data, so only do that if you have nothing else inside of elastic. Can you let me know how if you are still running into errors.

still no work after following your instructions:
1.pull the latest repo
2.run cmd:docker-compose up
3. delete * in kibana
4.restart containers
5. the same error still happens
api log:

client log:

ps: I found that the container 'job' will automatically shut down:

thx!

still no work after following your instructions:
1.pull the latest repo
2.run cmd:docker-compose up
3. delete * in kibana
4.restart containers
5. the same error still happens
api log:

client log:

ps: I found that the container 'job' will automatically shut down:

thx!

delete * in kibana:

Are you using the exact docker-compose file we ship with?

it works now!  I can see the exceptions in dashboard.   However, after modify the ui and api url from localtest.me to an internet IP, the login api call failed with 403 http code:

Are you using the exact docker-compose file we ship with?

It works now! I can see the exceptions in dashboard.  Thanks! :)
However, after modify the ui and api url from localtest.me to  address  in the internal network, the login api call failed with 403 http code:

docker-compose file:

All that looks correct, what happens when you hit http://<IP_ADDRESS>:5000/api/v2/about?

All that looks correct, what happens when you hit http://<IP_ADDRESS>:5000/api/v2/about?

auto redirect to https://<IP_ADDRESS>/api/v2/about
and the result is : ERR_CONNECTION_REFUSED

Can you even ping that IP address? That's an internal address and I doubt it will work out of the network it's hosted on? Are you on the same network? You should check out the updated docker wiki. We added an ssl section which gives you free ssl and does ssl termination as well you can easily host exceptionless behind a domain name :)

Can you even ping that IP address? That's an internal address and I doubt it will work out of the network it's hosted on? Are you on the same network? You should check out the updated docker wiki. We added an ssl section which gives you free ssl and does ssl termination as well you can easily host exceptionless behind a domain name :)

yes,  command "telnet  <IP_ADDRESS> 5000 ”   works fine!
all the snapshot images above are  in the same host server with IP "<IP_ADDRESS>"
when login,  API log  is (notice the last log):

Can you even ping that IP address? That's an internal address and I doubt it will work out of the network it's hosted on? Are you on the same network? You should check out the updated docker wiki. We added an ssl section which gives you free ssl and does ssl termination as well you can easily host exceptionless behind a domain name :)

Here is a work around solution,    add
<IP_ADDRESS>  ex-ui.localtest.me
<IP_ADDRESS>  ex-api.localtest.me
in hosts  file
:)
Now, everything works fine finally ~:)
thanks!

Can you even ping that IP address? That's an internal address and I doubt it will work out of the network it's hosted on? Are you on the same network? You should check out the updated docker wiki. We added an ssl section which gives you free ssl and does ssl termination as well you can easily host exceptionless behind a domain name :)

hi, email verification not works.  :(
I can  receive a validation email,  from the mail, click "Verify Address", enter the website without error. However, still did not verify the state of the mailbox.

Can you look in your browser and see what the end point it called? You may need to try again as every time you click verify it creates a new token and invalidates the last.

This is an HSTS thing. You need follow the instructions here: https://really-simple-ssl.com/knowledge-base/clear-hsts-browser/

Can you look in your browser and see what the end point it called? You may need to try again as every time you click verify it creates a new token and invalidates the last.

hi, I repeated procedure again:

click "verify":
the url is http://ex-ui.localtest.me:5100/account/verify?token=/RPcSOYWSWtFiT3CaP206hKzCbc4P6ZC7sQfKHp0t#!/type/error/dashboard

This is an HSTS thing. You need follow the instructions here: https://really-simple-ssl.com/knowledge-base/clear-hsts-browser/

thanks! I will try it. :)


Changing @vue/cli-service": "^4.5.13 version in package.json , getting bellow error when running npm run install

npm run serve

<EMAIL_ADDRESS>serve C:\Users\NarayanaReddyAnnapur\git\Digi\digihome-ui
vue-cli-service serve

INFO  Starting development server...
WARN  A new version of sass-loader is available. Please upgrade for best experience.
98% after emitting CopyPlugin
ERROR  Failed to compile with 1 error                                                                                7:11:19 PM
error  in ./src/css/main.css
Syntax Error: Error: PostCSS plugin tailwindcss requires PostCSS 8.
Migration guide for end-users:
https://github.com/postcss/postcss/wiki/PostCSS-8-for-end-users
@ ./src/css/main.css 4:14-162 15:3-20:5 16:22-170
@ ./src/main.js
@ multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080&sockPath=/sockjs-node (webpack)/hot/dev-server.js ./src/main.js
Could you please help on this issue , thank you in Advance.

@vue/cli 4.5.3 doesn't support PostCSS 8, which is required for latest Tailwind. @vue/cli 5 is recommended.
To use Tailwind with PostCSS 7 check https://tailwindcss.com/docs/installation#post-css-7-compatibility-build

I did same thing , but it's not working me .
Could you please what i should modify in package.json. Could you please help on this.
Please please
Than you in advance

Just clone the repo from scratch. It contains correct versions.


I'm trying to block the /admin URL from outside.

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

No

I'm trying to block the /admin URL from outside. Completely blocked from outside and from the local network
Nginx Proxy Manager Version v2.11.1
Menu
Custom Nginx Configuration
location ~ ^/(admin) {
allow <IP_ADDRESS>/24;
deny all;
}
Completely blocked from outside and from the local network

I'm not sure where you /admin is supposed to point but my "admin" answers on port 81 only (Via the default Docker image) unless you have some kind of redirection/different Docker-Compose file,  in place.


Process bar does not expand to full width in production but does in development

Hey @NightCatSama
I've implemented the slider and got it working as needed in development, but when I build for production the process bar ends up with an extremely small width - maybe only one pixel.  The dot barely moves either, just enough for the tooltip to render 0, NaN and 100 - so maybe 3 pixels?
I even tried copying one of the examples in, but I got the same result

Development

Production

The code I've got is here"
slid: {
        value: 0,
        formatter: '{value}%',
        lazy: true,
        tooltip: 'always',
        piecewise: false,
        style: {
          'marginBottom': '30px'
        },
        bgStyle: {
          'backgroundColor': '#fff',
          'boxShadow': 'inset 0.5px 0.5px 3px 1px rgba(0,0,0,.36)'
        },
        sliderStyle: {
          'backgroundColor': '#f05b72'
        },
        tooltipStyle: {
          'backgroundColor': '#3498db',
          'borderColor': '#3498db'
        },
        processStyle: {
          'backgroundImage': '-webkit-linear-gradient(left, #f05b72, #3498db)'
        }
      }

As far as I can tell, I don't have any CSS styles that might interfere, but even if I did, wouldn't I have the same problem in development?
Thanks

Have you figured it out @ZeroGodForce? I have similar issue that only happens in production.

@PatrykTucki I'm not too sure, I tried so many things I lost track, but I got something working in the end.  I'll go over my code, find out what it is and let you know ASAP

It is no longer necessary to call refresh in the latest version.

@PatrykTucki I think discovered a css class clash - which only happened when the production process concatenated all of the styles into one stylesheet (something that doesn't happen in development).  As a possible result (I can't be 100% sure as I've moved on to a couple of other projects since then) the working code I ended up with looks like this:
slid: {
        value: 0,
        formatter: this.getFormat(),
        lazy: true,
        tooltip: 'always',
        piecewise: false,
        style: {
          'marginBottom': '30px'
        },
        bgStyle: {
          'backgroundColor': '#fff',
          'boxShadow': 'inset 0.5px 0.5px 3px 1px rgba(0,0,0,.36)'
        },
        width: '100%',
        tooltipClass: 'custom-vue-slider-tooltip-style',
        processClass: 'custom-vue-slider-process-style'
      }
    }
  }

As you can see, I added some custom additional classes to increase the wrapping elements' Sith Power (specificity) and added width: '100%' as a main property.  Between these, I think that's what forced the correct style to render.  Don't know if that will help it might be worth a try regardless.
Good hunting.


Updating docs to use google tag manager

We added the GTM script to the upstream sphinx theme:
https://github.com/stormpath/stormpath-sphinx-theme/pull/3
As such, removing the old scripts in the local layout override.  Optimizely does need to stay in the fodder.

Coverage remained the same at 69.416% when pulling 3a62564bd62ac284b1ad91f96f4ec7bdb11d86b3 on docs-google-tag-manager into f49fd4841aa69d65cc64fd6995a3ff1941bbd9ae on master.


Add NSBogan blog

Thanks for this!
I get an SSL error when visiting the site, I tried it without HTTPS, but it redirects to the HTTPS site :) Is there a temporary problem?

Dave

Oh, my. I changed it to point directly to https://mgrebenets.github.io
Will have to figure out the cert issue for domain names later.

Thanks!


In CI, fail on incorrect formatting

As we agreed in Slack, we should fail the build on incorrect formatting. At the same time we want compile to automatically format the code -> we need to run this before the ci pipeline starts.

ok this is passing and it should not be passing (thx. @takirala ) so I am investigating...


Allow custom classes

I thought badgeStyle would allow me to change the color of the badges, but it did not. I think it would be interesting to add the functionality for own classes or styles, and that badgeStyle would not have a default value.
After seeing issue #39 I thought it would be possible by using badgeClass, but it didnt work.
let opt = this._selectElement.querySelector('option[value="' + value + '"]');
if (opt) {
     data = opt.dataset;
}
...
classes.push(...data.badgeClass.split(" "));
...
span.classList.add(...classes);

As far as I can see in the code, the badgeClass attribute is obtained from the option tag instead of the select tag. Is this behavior correct? In my case I don't have option tags, just the select element.
<select class="form-select" id="validationTagsNew" name="tags_new[]" multiple data-badge-class="testing" data-allow-new="true"></select>
Best regards.

I didn't find it before, but I see it was done in #39 . I didn't see it documented and thought it wasn't possible.

I don't think I understand very well how badgeClass works. What I propose is to offer freedom to the user to apply their own styles, and only apply "bg-primary" by default.
Perhaps what I'm proposing doesn't make much sense, since it seems contradictory to use this project, which works with Bootstrap, and then want to overwrite it. My current need was to modify the primary color for a custom color. Also I was trying to modify the size to test if it fixes a visual bug, since using the Source Sans Pro font the text looks blurry on badges.
Feel free to close this issue if you are not convinced. Thanks anyway for your project!

this should do what you need
https://github.com/lekoala/bootstrap5-tags/releases/tag/1.4.36
i've updated the demo.html accordingly. i didn't notice any issue with the source sans font, although the bold doesn't help that much.

@lekoala That's exactly what I was proposing, thank you very much for your interest.
If you agree, I would add these small changes:

With these new changes, if base-class is defined, the badge style is eliminated. I think it is better to leave the badge style fixed (bootstrap's own, and as the first style), from here I would add the user classes (base-class), which you can even overwrite badge if necessary. This ensures a minimum of visual stability, otherwise you may notice how it visually breaks attributes like allowClear. (Perhaps you prefer to leave documented that using base-class is at your own risk, but the badge style I consider necessary always). (Solution below)

This point removes the myCustom-primary class (I don't see it necessary here), and adds support for several classes.

Line 890 from classes = [...classes, this.baseClass + "-" + badgeStyle]; to classes.push(...this.baseClass.split(" "));.
Line 880 to let classes = ["badge"]; (This would include the previous item, so the default value in line 60 should be deleted too, leave array empty if you do not want to include.)

Thanks again!!

i see. i also think it's better to keep the badge class.
here it is https://github.com/lekoala/bootstrap5-tags/releases/tag/1.4.37

No further suggestions for the moment. Thank you very much @lekoala!


Provide auto-complete candidates for TypeScript string literal type when double quote is typed

VSCode Version: 1.11.2
OS Version: Windows 10

Steps to Reproduce:
type Color = "Red" | "Green" | "Blue";
let color: Color = " <-- No auto-complete until I press Ctrl+Space

When I type the double quote, the auto-complete popup should be showed. It should work like when I type the dot after an object name, the auto-complete popup is showed without Ctrl+Space.

We do also provide intellisense once you start typing a ltter. To enable this, make sure to enable editor.quickSuggestions inside of strings by setting:
"editor.quickSuggestions": {
        "other": true,
        "comments": false,
        "strings": false
    }

As for actually showing the suggestions when you first type ", this is a more difficult problem that I don't think we can solve using the current vscode APIs. We can currently only register a completion trigger character such as . or " to show intellisense, but in cases where you are typing " for a normal string, we do not want to automatically trigger suggestions.
@jrieken Any thoughts on context-aware completion triggering besides just listening to keypresses? #21543 tracks a very similar problem

I don't think context aware triggered can be done in the main side with information from the ext host side. The rule is that IntelliSense gets triggered often and in ways the extension cannot control and therefore the extension is free to return undefined/null when it cannot completion with anything meaningful. Exposing more information to the provider, like the trigger character (which is already in the document anyways), is tracked here: #752

Part of the problem might be how type information is exposed here:
interface Meta {
	color: 'Red' | 'Green' | 'Blue';
}

const meta: Meta = { color: 'Red' };  // property typed as string

type Color = 'Red' | 'Green' | 'Blue';
interface Meta2 {
	color: Color;
}

const meta2: Meta = { color: 'Red' }; // property typed as Color

From my understanding, both of these should be typed as 'Red' | 'Green' | 'Blue' by IntelliSense, yet it seems IS's insight is being limited here.

Depends on https://github.com/Microsoft/TypeScript/issues/21012

@zackschuster Looks like that issue may have been fixed in the last year -- in both of those cases color is a string literal union and we give you only those 3 completions inside of either string literal.

can confirm, my test case is working as expected. thanks for the heads-up!


qsize and not stream

Hi ParisNeo.
First of all, thank you for share awesome project. I just check it for parallel requests with Ollama. I found this repo from Ollama issue.
I've run two Ollama instances and run ollama_proxy_server. And I found two problem. One is that's not working with stream response. It works just send last data. Other is qsize couldn't get right. I attached screenshot.

It's just first try. I'll test it more and give feedback more.
Thanks.

HI.
I have a server with two ollama instances and I use streaming mode from my clients.
My client uses the /generate endpoint and it works. Here I see you are using chat endpoint instead. The only endpoint that uses the double queues is the /generate I have to take a look at that endpoint I think that's why it is not working. I'll check out this and add the /chat endpoint to the queued management.
Thanks for informing me

OK, just went through threir doc and now I added the chat endpoint to the list of queued endpoints

Thank you for response. I will check /chat endpoint again. And I think streaming issue is not cause this source. I'm not sure though it should be langchain issue. I'll test it also.

Even using /generate, the output break into many responses but all responses show together. Streaming is not work.

Even using /generate, the output break into many responses but all responses show together. Streaming is not work.
What client are you using? I just tested using lollms.


Add a field to set the path to the Ansible binaries directory

based in https://github.com/rundeck-plugins/ansible-plugin/pull/288

Hi @pierrecarre,
I created a new PR with your change.
Please let me know if you have time to take a look. I added small changes in the docker environment and I added the attribute to the resource model plugin
Thanks
Luis

does this fix #51 ?


catalog-operator: wrap catalogsource pods in Deployments

Description of the change:
Updates the operator to produce Deployments instead of standalone Pods
backing CatalogSources. This enables a node to be drained properly
without forcing the catalog pods off the node.
Motivation for the change:
Multiple upstream and downstream bugs reported for this issue.
Architectural changes:

Testing remarks:

Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Bug fixes are accompanied by regression test(s)
[ ] e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
[ ] tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
[ ] Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
[ ] Docs updated or added to /doc
[ ] Commit messages sensible and descriptive
[ ] Tests marked as [FLAKE] are truly flaky and have an issue
[ ] Code is properly formatted

Does this deserve it's own tracking issue that we can slate into the next minor version release? It seems like the motivation is geared towards a bug fix, but I'd worry about backporting these changes to a stable release, vs. a net new thing. Thoughts?

Yes, I'm not super thrilled about backporting this to stable release at this point either. I think, since it is a change in behavior, it should probably be slated to the next minor version downstream. I'm not sure about tracking this in an issue upstream though.
We have several issues already about this behavior:

https://github.com/operator-framework/operator-lifecycle-manager/issues/2709
https://github.com/operator-framework/operator-lifecycle-manager/issues/1514


AMBARI-23402. Make nproc and nolimit values configurable through infra-solr-env config

What changes were proposed in this pull request?
Some issues are really often come up with our Infra Solr, OutOfMemory can occur even if you have enough memory (nproc problem) or it cannot open more files, there values by default are low, so from this point we should be able to configure this. (and also use higher default values), the solution is similar that ambari uses for hdfs.
How was this patch tested?
With mvn clean test -DskipSurefireTests -Dpython.test.mask="*test_infra_solr*"
Total run:3
Total errors:0
Total failures:0
OK
[INFO]
[INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle) @ ambari-server ---
Downloading: https://maven.atlassian.com/repository/public/org/apache/ambari/ambari-utility/<IP_ADDRESS>-SNAPSHOT/maven-metadata.xml
Downloading: http://download.java.net/maven/2/org/apache/ambari/ambari-utility/<IP_ADDRESS>-SNAPSHOT/maven-metadata.xml
Downloading: https://repository.apache.org/content/repositories/snapshots/org/apache/ambari/ambari-utility/<IP_ADDRESS>-SNAPSHOT/maven-metadata.xml
Downloading: http://download.java.net/maven/glassfish/org/apache/ambari/ambari-utility/<IP_ADDRESS>-SNAPSHOT/maven-metadata.xml
Downloading: http://repository.apache.org/snapshots/org/apache/ambari/ambari-utility/<IP_ADDRESS>-SNAPSHOT/maven-metadata.xml
[INFO] Starting audit...
Audit done.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:07 min
[INFO] Finished at: 2018-03-29T14:01:30+02:00
[INFO] Final Memory: 109M/1707M
[INFO] ------------------------------------------------------------------------

Please review @g-boros @zeroflag @smolnar82

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1497/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1498/
Test FAILed.
Test FAILured.


Migration failing when trying to install swarfarm on Ubuntu 18.04

Hey,
I have been trying to deploy a dev installation of swarfarm on Ubuntu 18.04. I am currently seeing an error when trying to run the migration:
Traceback (most recent call last):
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
psycopg2.errors.UndefinedTable: relation "bestiary_scalingstat" does not exist
LINE 1: ..._desc", "bestiary_scalingstat"."description" FROM "bestiary_...

Full traceback is here:
Traceback (most recent call last):
  File "manage.py", line 12, in <module>
    execute_from_command_line(sys.argv)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/core/management/base.py", line 361, in execute
    self.check()
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/core/management/base.py", line 390, in check
    include_deployment_checks=include_deployment_checks,
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 65, in _run_checks
    issues.extend(super()._run_checks(**kwargs))
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/core/management/base.py", line 377, in _run_checks
    return checks.run_checks(**kwargs)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/core/checks/registry.py", line 72, in run_checks
    new_errors = check(app_configs=app_configs)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/core/checks/urls.py", line 13, in check_url_config
    return check_resolver(resolver)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/core/checks/urls.py", line 23, in check_resolver
    return check_method()
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/urls/resolvers.py", line 399, in check
    for pattern in self.url_patterns:
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/utils/functional.py", line 80, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/urls/resolvers.py", line 584, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/utils/functional.py", line 80, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/urls/resolvers.py", line 577, in urlconf_module
    return import_module(self.urlconf_name)
  File "/root/.pyenv/versions/3.6.8/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/root/swarfarm/swarfarm/urls.py", line 28, in <module>
    url(r'^api/v2/', include('apiv2.urls', namespace='v2')),
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/urls/conf.py", line 34, in include
    urlconf_module = import_module(urlconf_module)
  File "/root/.pyenv/versions/3.6.8/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/root/swarfarm/apiv2/urls.py", line 8, in <module>
    from data_log.api_urls import router as data_log_router
  File "/root/swarfarm/data_log/api_urls.py", line 3, in <module>
    from . import views
  File "/root/swarfarm/data_log/views.py", line 8, in <module>
    from .game_commands import active_log_commands, accepted_api_params
  File "/root/swarfarm/data_log/game_commands.py", line 5, in <module>
    from bestiary.parse.dungeons import dispatch_dungeon_wave_parse
  File "/root/swarfarm/bestiary/parse/__init__.py", line 5, in <module>
    from .skills import skills, homonculus_skills
  File "/root/swarfarm/bestiary/parse/skills.py", line 169, in <module>
    _defense = ScalingStat.objects.get(com2us_desc='DEF')
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/models/manager.py", line 82, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/models/query.py", line 402, in get
    num = len(clone)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/models/query.py", line 256, in __len__
    self._fetch_all()
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/models/query.py", line 1242, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/models/query.py", line 55, in __iter__
    results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/models/sql/compiler.py", line 1140, in execute_sql
    cursor.execute(sql, params)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/backends/utils.py", line 99, in execute
    return super().execute(sql, params)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/backends/utils.py", line 67, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/utils.py", line 89, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/root/.pyenv/versions/swarfarm-3.6.8/lib/python3.6/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: relation "bestiary_scalingstat" does not exist
LINE 1: ..._desc", "bestiary_scalingstat"."description" FROM "bestiary_...

Let me know if you have any idea how to solve this

Looks like I managed to get the migrations to run by commenting out 3 lines in
bestiary/parse/skills.py
169 _defense = ScalingStat.objects.get(com2us_desc='DEF')
170 _target_hp = ScalingStat.objects.get(com2us_desc='TARGET_TOT_HP')
171 _max_hp = ScalingStat.objects.get(com2us_desc='ATTACK_TOT_HP')

Thanks, I didn't realize those would cause an issue when running management commands.

Fixed with 8e63743158daca4faab74696cf5e41dff2850986


Add external collaborator's ARN to project bucket access list

This PR adds the ARN of Jackson Jacobs, our collaborator at Emory on the MC2 Digital Pathology QC supplement, to the relevant bucket so that they can access results directly.

@zaro0508 would you be able to review this one?

Thank you @zaro0508! Are you able to also help with merging and moving through to prod?


Tracking clicks on forms

An interesting form tracking use case is analyzing if users are actually selecting something when they open a drop-down menu, or typing something when they click on a text field. This would allow us to see which fields are adding more friction to the conversion funnel - and hopefully lower it over time :)
I tried to implement this using a click event listener on the relevant elements. Problem is this listener is triggered both by the click that opens the drop-down, but also by clicking on an option. This is why I'm passing { 'once': true } into the listener - tracking the first click is enough for this use case.
Thoughts?

@bernardosrulzon has signed the Individual Contributor License Agreement

Hi Bernardo,
Form completion tracking is very useful. I think what you're after are the
on blur events. These events fire when users move away from a field.
They're the opposite of on focus.
At that point you should be able to detect if a selection or input was made
within a field.
Is that what you're looking for?
https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/onblur
On Sun., 16 Apr. 2017, 4:50 am Snowplow CLA bot<EMAIL_ADDRESS>wrote:

@bernardosrulzon https://github.com/bernardosrulzon has signed the
Individual Contributor License Agreement
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/snowplow/snowplow-javascript-tracker/pull/579#issuecomment-294311372,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQILJarY_3RM1k2rQm8YhkL3p96R4kJks5rwRFjgaJpZM4M-P_f
.

Hey Rob! Thanks, that was exactly what I was looking for - focus works perfectly for this use case.
Schema is here: https://github.com/snowplow/iglu-central/pull/548


Closing Sockets and Reopening Sockets

On a connection failure or connection timeout, I would like to close and reopen the socket.  For Pub, and Sub sockets, I tried called the deconstructor, and it seems to work.  When I call RepRouter's deconstructor the app hangs.
What is the best way to close and reopen a socket or sockets?
Thanks,
Robert

You may need to use setShutdownWaitTime, which sets the ZMQ_LINGER time on the socket.

I'm not sure if you should be explicitly closing/reopening to work around connection issues though. The underlying libzmq should take care of ensuring there is always a connection if possible.

Hi Karneges,
I wasn’t sure how zmq manages the connections.  So I implemented sync and heartbeat functions as keep a live.  If heartbeat fails, I restart the sockets, and wait for the sync before continuing.
Also, Setting socket linger to 0 solved the hanging issue.
I'm calling the class destructor for each socket.
I noticed that the zmq.close was not exposed in qzmq for closing sockets, so that is why I used the class destructors for closing the sockets.
Thanks for the help,
Robert

On Dec 2, 2019, at 11:44 AM, Justin Karneges<EMAIL_ADDRESS>wrote:
I'm not sure if you should be explicitly closing/reopening to work around connection issues though. The underlying libzmq should take care of ensuring there is always a connection if possible.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/jkarneges/qzmq/issues/2?email_source=notifications&email_token=AHHFZEWM3NTZXDMS5RAN5GTQWU3NRA5CNFSM4JTSCKT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFUDQ2Q#issuecomment-560478314, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHHFZEUKQY6SJ32QJRAZZZLQWU3NRANCNFSM4JTSCKTQ.

Sure. You might consider enabling TCP keepalives on the socket to achieve a similar effect.


Stable merge for week 26 of 2022

New packages

linux-mainline - 5.18.0-1 (#488)

Mainline linux kernel for the rM2 only

Updated packages

koreader - 2022.05-1 (#590)
display rm2fb-client - 1:0.0.19-1 (#592)(#597)

Added support for version <IP_ADDRESS>8
Added support for version <IP_ADDRESS>1

ddvk-hacks - 33.02-1 (#593 #598)

Support OS <IP_ADDRESS>6 for rM1
Support OS <IP_ADDRESS>8 for rM2
Support OS <IP_ADDRESS>1 for both rM1 and rM2

folly - 0.0.1-3 (#587)
remux - 0.2.3-1 (#588)

Make palm filtering a config option

harmony - 0.2.1-1 (#558)

More layer dialog improvements
Sort import dialog by file date
Refactor pressure / tilt events to use hardware values

wireguard - 1.0.20210219-3 (#488)

Move to kernel section

fuse - 1.0.0-4 (#488)

Move to kernel section

thanks for opening! can you also include the PRs that matteo accepted last week?

https://github.com/toltec-dev/toltec/commit/f17336fa607809d02084f2b7c87e47feb1a60730
https://github.com/toltec-dev/toltec/commit/de887138ec78c5748c79f8febf5e6402f171ccbf
https://github.com/toltec-dev/toltec/commit/b671b5af88d42557aebb77e4835130f1cb7cbbb2

@raisjn Since they were only merged 5 days ago, I was holding off on this first stable merge. @matteodelabre any concerns with pulling those forward as well?

Thanks for the PR. Yes, I think it would be worthwhile to include the commits that raisjn mentioned.

@matteodelabre @LinusCDE @raisjn poke

There is a PR for <IP_ADDRESS>6 rm2fb support already open to testing. I agree about just editing the file instead of waiting for a new release. There are issues open on the rm2fb repo with ideas to simplify things, they just need to be implemented.

Right. Just noticed that. Tested and merged it.

@LinusCDE I've pulled in the latest commits for <IP_ADDRESS>6 support

Sure, I can take a look! Sorry for the delay.

(Note: I fixed the display version number in your original PR comment.)
Tested on rM1 and rM2, 2.14.0 and 2.14.1.

linux-mainline currently instructs users to make a backup of the stock kernel files to the /opt/boot-backup directory, but this directory will get removed by toltecctl uninstall. We should change this to recommend backing up to a folder under /home/root instead.
Can confirm the issue mentioned by @LinusCDE with harmony on rM2. This makes it a bit difficult to draw (ping @raisjn)
fuse and wireguard do not require testing as they are just being moved to a different section.

Everything else is working correctly as far as I can tell.

Fuse and wireguard will require testing with the mainline kernel and the latest OS kernel at some point to make sure they work properly. They've been broken for a while but the latest OS kernel should start working again.

Fuse and wireguard will require testing with the mainline kernel and the latest OS kernel at some point to make sure they work properly. They've been broken for a while but the latest OS kernel should start working again.

Fuse may give issues with linux-mainline since it already has CONFIG_FUSE_FS=y.
Maybe we should re-think the whole idea of making packages with single modules
because it may lead to a lot of confusion whit alternative kernels. Moreover installing things in /lib/modules is definitely going to make kernelctl much more complicated than already is.

It should be possible to make package variations for each kernel that Toltec provides, and for example mark fuse as conflicting with the mainline kernel/depending on the stock kernel.

It should be possible to make package variations for each kernel that Toltec provides, and for example mark fuse as conflicting with the mainline kernel/depending on the stock kernel.

Not really a straightforward path: suppose you install linux-mainline but do not enable it, or possibly temporarily decide to switch to the upstream kernel: you will have to install/uninstall the package just to switch. Moreover, how is kernelctl going to know which files in /lib/modules/ belong to the kernel and which to the package? I mean, it is possible but not in a clean way.


database disconnects are not handled

I have not found a way to catch and handle ECONNRESET errors from the tedious library in sqlssb
This happens when the database restarts or the network connection between the server and database drops or any reason why SQL Server may disconnect clients.
Does this exist and I do not see it?
Does it not yet exist?

same issue here, any updates?

we switched to using an event based backend to avoid polling for events


dicom_ocr - check it handles rotated text

readtext has rotation_info (list, default = None) - Allow EasyOCR to rotate each text box and return the one with the best confident score. Eligible values are 90, 180 and 270. For example, try [90, 180 ,270] for all possible text orientations.
Try also DBnet reader = easyocr.Reader(['en'], detect_network = 'dbnet18')

Rotated text was often detected anyway, but this commit makes it much more reliable https://github.com/SMI/dicompixelanon/commit/8e151bde7869b954b3fe347835e3744bad45956f
(Not tried DBnet yet though)

Will open a new issue to try DBnet


Angular:dev not starting Angular

Detailed description of how to reproduce the problem
Running angular:dev on the root tries to start angular, but results in an error
Upload a screenshot
N/A
Describe the development framework
N/A
Expected behavior
Angular runs properly
Additional information
No response

Cannot reproduce anymore


feat: added diagnostic settings support for traffic manager.

Description

If you haven't already, read the full contribution guide. The guide may have changed since the last time you read it, so please double-check.
Enable GitHub Worksflows in your fork to enable auto-generation of assets with our GitHub Action.
To trigger GitHub Actions after auto-generation, add a GitHub PAT as a secret in your forked repository called PAT.
Adding a new module

[ ] A proposal has been submitted and approved.
[ ] I have included "Closes #{module_proposal_issue_number}" in the PR description.
[ ] I have run brm validate locally to verify the module files.
[ ] I have run deployment tests locally to ensure the module is deployable.

Updating an existing module

[ ] This is a bug fix:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[x] I have run brm validate locally to verify the module files.
[x] I have run deployment tests locally to ensure the module is deployable.
[ ] I have read the Updating an existing module section in the contributing guide and updated the version.json file properly:

[ ] The PR contains backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json.
[x] The PR contains backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] The PR contains breaking changes, and I have bumped the MAJOR version in version.json.

[ ] I have updated the examples in README with the latest module version number.

@shenglol @dciborow please review. thanks!

@dciborow should we do the same for TM name as default value?
@description('Prefix of Traffic Manager Profile Name')
param prefix string = 'traf'

@description('Name of Traffic Manager Profile Resource')
param name string = '${prefix}-${uniqueString(resourceGroup().id, subscription().id)}'

@shenglol  will you please check this!

Can we bump the minor version in version.json? Otherwise, the changes look good to me.

Can we bump the minor version in version.json? Otherwise, the changes look good to me.

done!


[PE-D] No indication on the baseline for labelling FET as late.

When using the app, I noticed that 22 Oct 2021 is the benchmark to determine whether FET is late.
It is not clear (or not obvious) in the UG that perhaps the previous Friday is the benchmark?
More information needs to be given to make this clear to users.

Labels: type.DocumentationBug severity.High
original: eeliana/ped#16

I think this issue is here because the tester was not aware of the one week validity period of last fet, maybe can include it in the doc

Yes, please do


Add-to-Wiki: Parse Migration Tool to PushBots

We (PushBots) have created an automatic migration tool to smooth transition. Would it be possible to add to your Wiki community links? Thanks
https://pushbots.com/parse

This seems like a third party service that is not related to parse-server.

Now that there's a push adapter in place, @amrsobhy you can look ar developing this for pushbots


Nested Virtualized Lists in opposing directions firing all onViewableItemsChanged

Description
Nested Bidirectional FlatList onViewableItemsChanged Issue

App Image
Layout Image

The above images describe the layout where this problem has arisen. Essentially it's a 2D FlatList.
When the Vertical FlatList mounts and the onViewableItemsChanged prop callbacks fire for only the elements on the screen, the expected behavior is working.
However, once the nested FlatLists mount, instead of firing the onViewableItemsChanged callback for only the nested Horizontal FlatList items that are within the visible viewport, it fires for all rendered list items (including those that are out of the viewport). It seems that the correct viewability is determined on horizontal lists, however, the VirtualizedList doesn't check if those horizontal lists are vertically visible.
Below, I've illustrated the expected vs actual behavior with images/emojis
🎇 - Vertical FlatList onViewableItemsChanged callback fires
🔥 - Horizontal FlatList onViewableItemsChanged callback fires

Expected
Actual

I provided a minimum setup repo below you can clone. Only changed the App.tsx file to recreate the above steps.
React Native Version
0.71.0
Output of npx react-native info
System:
    OS: macOS 12.6
    CPU: (10) arm64 Apple M1 Max
    Memory: 204.02 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.18.0 - ~/.nvm/versions/node/v16.18.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.18.0/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v16.18.0/bin/npm
    Watchman: Not Found
  Managers:
    CocoaPods: Not Found
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0
    Android SDK:
      API Levels: 29, 30, 31, 32, 33
      Build Tools: 29.0.3, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 33.0.0, 33.0.0
      System Images: android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom_64, android-29 | Google Play ARM 64 v8a, android-29 | Google Play Intel x86 Atom_64, android-31 | Google Play ARM 64 v8a, android-32 | Google APIs ARM 64 v8a, android-32 | Google Play ARM 64 v8a, android-33 | Google Play ARM 64 v8a
      Android NDK: Not Found
  IDEs:
    Android Studio: 2021.3 AI-213.7172.25.2113.9014738
    Xcode: 14.0.1/14A400 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.11 - /Users/vvella/.jenv/shims/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.1.0 => 18.1.0
    react-native: 0.70.4 => 0.71.0
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to reproduce

Create a vertical FlatList that contains a 2D data array with a length long enough to make the list run off of your screen and require scrolling
Create another FlatList (horizontal) to be rendered in the renderItem prop of the parent FlatList
Add an onViewableItemsChanged to the nested (horizontal) FlatList
Observe that all items rendered (regardless of vertical viewability) fire their onViewableItemsChanged callback

Snack, code example, screenshot, or link to a repository

Taken from the tester app
See that InnerViewable shows "56,57,58"
All of which are horizontally viewable but not vertically shown in the viewport
Snack: https://snack.expo.dev/@vincentvella/great-almond
Repo: https://github.com/vincentvella/bidirectional-virtualized-list-issue

Confirmed this is still an issue on the latest release.

Confirming issue is not fixed on 0.72.4


Compute Instance fails, where's the logs??

When a compute instance fails, where are the logs of the creation for troubleshooting??   I don't see that documented anywhere...

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

 Thanks.

@swieder we'll review your feedback and get back to you shortly. Thanks.

Hello @swieder are you getting error messages?

Hello @swieder are you getting error messages?

Yes, creating a compute instance gives an error.   But there is no detail on what the error was and I can’t find any logs to see why the deployment failed in the portal and I don’t see anything documented on where to check for deployment errors.
Thanks,
Steve Wiederrich
Mobile:<PHONE_NUMBER>
From<EMAIL_ADDRESS>Sent: Friday, January 8, 2021 9:44 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Compute Instance fails, where's the logs?? (#68561)
Hello @swiederhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fswieder&data=04|01||0b4031efd0994165d8c108d8b3ec520e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637457174855144226|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Lx4C48ramUJPPgWxhiIRuZ6%2FJ9OVvNCGJTVyhQw7uao%3D&reserved=0 are you getting error messages?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F68561%23issuecomment-756825278&data=04|01||0b4031efd0994165d8c108d8b3ec520e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637457174855154179|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=4C71lbcPWQ1azQJcjG3sa3QNGHoWeFqu9Zhm3P39%2B1c%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF2PHPQS56UFIMKNAUTBZWLSY4R6XANCNFSM4VZGOVRA&data=04|01||0b4031efd0994165d8c108d8b3ec520e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637457174855154179|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=jeK83OOxKzFE7of8M3uBM0VjPzGf883Bdgk96u7XYYQ%3D&reserved=0.

Yes, creating a compute instance gives an error.   But there is no detail on what the error was and I can’t find any logs to see why the deployment failed in the portal and I don’t see anything documented on where to check for deployment errors.
Thanks,
Steve Wiederrich
Mobile:<PHONE_NUMBER>
From<EMAIL_ADDRESS>Sent: Friday, January 8, 2021 9:44 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Compute Instance fails, where's the logs?? (#68561)
Hello @swiederhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fswieder&data=04|01||0b4031efd0994165d8c108d8b3ec520e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637457174855144226|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Lx4C48ramUJPPgWxhiIRuZ6%2FJ9OVvNCGJTVyhQw7uao%3D&reserved=0 are you getting error messages?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F68561%23issuecomment-756825278&data=04|01||0b4031efd0994165d8c108d8b3ec520e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637457174855154179|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=4C71lbcPWQ1azQJcjG3sa3QNGHoWeFqu9Zhm3P39%2B1c%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF2PHPQS56UFIMKNAUTBZWLSY4R6XANCNFSM4VZGOVRA&data=04|01||0b4031efd0994165d8c108d8b3ec520e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637457174855154179|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=jeK83OOxKzFE7of8M3uBM0VjPzGf883Bdgk96u7XYYQ%3D&reserved=0.

Please can you try recreating and share the error message?

Please can you try recreating and share the error message?

“The deployment failed.”
I’m unable to find any more information on why it failed and there is no documentation that I can see on how to troubleshoot a failed deployment.   Are there any logs anywhere that will give the details of why the deployment failed that you can documents??
Thanks,
Steve Wiederrich
Mobile:<PHONE_NUMBER>
From<EMAIL_ADDRESS>Sent: Friday, January 8, 2021 9:22 PM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Compute Instance fails, where's the logs?? (#68561)
Please can you try recreating and share the error message?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F68561%23issuecomment-757086926&data=04|01||0c39d378471b4497b6cc08d8b44dc0f3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637457593323411121|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=JirlNAHKgbP2yZ6tdIfO0mY0Xh8W57ap%2Fb%2FMpt%2FbzbY%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF2PHPWKC5POEPWILRBAQOTSY7DWFANCNFSM4VZGOVRA&data=04|01||0c39d378471b4497b6cc08d8b44dc0f3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637457593323421078|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=H%2FbKmxm8Ptc14girBaexbBb2Bs2PLMwr7VmU87ilcGc%3D&reserved=0.

“The deployment failed.”
I’m unable to find any more information on why it failed and there is no documentation that I can see on how to troubleshoot a failed deployment.   Are there any logs anywhere that will give the details of why the deployment failed that you can documents??
Thanks,
Steve Wiederrich
Mobile:<PHONE_NUMBER>
From<EMAIL_ADDRESS>Sent: Friday, January 8, 2021 9:22 PM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Compute Instance fails, where's the logs?? (#68561)
Please can you try recreating and share the error message?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F68561%23issuecomment-757086926&data=04|01||0c39d378471b4497b6cc08d8b44dc0f3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637457593323411121|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=JirlNAHKgbP2yZ6tdIfO0mY0Xh8W57ap%2Fb%2FMpt%2FbzbY%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF2PHPWKC5POEPWILRBAQOTSY7DWFANCNFSM4VZGOVRA&data=04|01||0c39d378471b4497b6cc08d8b44dc0f3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637457593323421078|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=H%2FbKmxm8Ptc14girBaexbBb2Bs2PLMwr7VmU87ilcGc%3D&reserved=0.

@swieder thanks for providing more details. It doesn't seem like detailed log information is stored/shared publicly (verifying this information). Usually a failed deployment will have additional details printed out in the error message. Also, if you go to Azure ML Studio > Compute > Compute Instances tab > Select Compute > Status > Click on icon with "-", you'll see more details about the error as shown below.

Feel free to share the detailed error message suing the above steps so we can investigate further, otherwise, you may have to follow the steps to contact Azure support to identify the root cause.
@sdgilley please consider above feedback for doc enhancement.

@swieder thanks for providing more details. It doesn't seem like detailed log information is stored/shared publicly (verifying this information). Usually a failed deployment will have additional details printed out in the error message. Also, if you go to Azure ML Studio > Compute > Compute Instances tab > Select Compute > Status > Click on icon with "-", you'll see more details about the error as shown below.

Feel free to share the detailed error message suing the above steps so we can investigate further, otherwise, you may have to follow the steps to contact Azure support to identify the root cause.
@sdgilley please consider above feedback for doc enhancement.

Hello @swieder quick follow-up. Also, if you can share the name of your compute instance by sending an email to<EMAIL_ADDRESS>we'd be glad to investigate further on why the compute instance is failing. Thanks.

Hello @swieder quick follow-up. Also, if you can share the name of your compute instance by sending an email to<EMAIL_ADDRESS>we'd be glad to investigate further on why the compute instance is failing. Thanks.

We are already working with Support with my customer (I’m a Microsoft CSA working with ArcBest).  I filed the issue as there is not any documentation on how to troubleshoot a failed deployment.
Thanks,
Steve Wiederrich
Mobile:<PHONE_NUMBER>
From<EMAIL_ADDRESS>Sent: Monday, January 11, 2021 9:34 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Compute Instance fails, where's the logs?? (#68561)
Hello @swiederhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fswieder&data=04|01||b43578093e134d4d001d08d8b6465625|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459760493087715|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3OGPtSPNnY6OZNnHzHWUjzGfs7fJle3%2FVVtW9WuVAfg%3D&reserved=0 quick follow-up. Also, if you can share the name of your compute instance by sending an email to "AzCommunity<EMAIL_ADDRESS>we'd be glad to investigate further on why the compute instance is failing. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F68561%23issuecomment-758027054&data=04|01||b43578093e134d4d001d08d8b6465625|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459760493087715|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=d2szDi5qZVddPzI9Dw2HOUJatnHbmceK9j1cLJJS0SU%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF2PHPSQD6OKY4D37GC2QZ3SZMK67ANCNFSM4VZGOVRA&data=04|01||b43578093e134d4d001d08d8b6465625|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459760493097672|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=P2%2Bj3alPLTPEYAgloBuNOyvTRDgb4ap%2B2GkQcaUNe5E%3D&reserved=0.

We are already working with Support with my customer (I’m a Microsoft CSA working with ArcBest).  I filed the issue as there is not any documentation on how to troubleshoot a failed deployment.
Thanks,
Steve Wiederrich
Mobile:<PHONE_NUMBER>
From<EMAIL_ADDRESS>Sent: Monday, January 11, 2021 9:34 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Compute Instance fails, where's the logs?? (#68561)
Hello @swiederhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fswieder&data=04|01||b43578093e134d4d001d08d8b6465625|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459760493087715|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3OGPtSPNnY6OZNnHzHWUjzGfs7fJle3%2FVVtW9WuVAfg%3D&reserved=0 quick follow-up. Also, if you can share the name of your compute instance by sending an email to "AzCommunity<EMAIL_ADDRESS>we'd be glad to investigate further on why the compute instance is failing. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F68561%23issuecomment-758027054&data=04|01||b43578093e134d4d001d08d8b6465625|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459760493087715|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=d2szDi5qZVddPzI9Dw2HOUJatnHbmceK9j1cLJJS0SU%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF2PHPSQD6OKY4D37GC2QZ3SZMK67ANCNFSM4VZGOVRA&data=04|01||b43578093e134d4d001d08d8b6465625|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459760493097672|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=P2%2Bj3alPLTPEYAgloBuNOyvTRDgb4ap%2B2GkQcaUNe5E%3D&reserved=0.

Thanks, there was not any other detailed information.   Just that it failed.   The detailed error message was “The deployment failed”   in the same place as your picture below where it says “The specified account has reached VM Series core quota ….”
Thanks,
Steve Wiederrich
Mobile:<PHONE_NUMBER>
From<EMAIL_ADDRESS>Sent: Monday, January 11, 2021 9:11 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Compute Instance fails, where's the logs?? (#68561)
@swiederhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fswieder&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711583311|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=D%2FUcmF4aEvCX2OSAfaRS9UDs4orKBfOIAHPN0JMphGQ%3D&reserved=0 thanks for providing more details. It doesn't seem like detailed log information is stored/shared publicly (verifying this information). Usually a failed deployment will have additional details printed out in the error message. Also, if you go to Azure ML Studio > Compute > Compute Instances tab > Select Compute > Status > Click on icon with "-", you'll see more details about the error as shown below.
[image]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F51332022%2F104198401-30283880-53f4-11eb-9053-93ac1e306a58.png&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711593267|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Ecv%2FCEvuCuh7tCSu%2BON7rdejEV4nq86f9Gdt%2BBvtxns%3D&reserved=0
[image]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F51332022%2F104198457-3f0eeb00-53f4-11eb-8daf-18d2c61c951a.png&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711593267|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=2vTdsRs6%2FZDC5gbbcf5SEZNuwuC5K3Gx7%2FbHqS9YkrM%3D&reserved=0
Feel free to share the detailed error message suing the above steps so we can investigate further, otherwise, you may have to follow the steps to contact Azure supporthttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-portal%2Fsupportability%2Fhow-to-create-azure-support-request&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711593267|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=8Y6FY%2BK1vxxhyvv4U6NCkg%2F9JYP0414Q%2BecyOl92cXI%3D&reserved=0 to identify the root cause.
@sdgilleyhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsdgilley&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711603218|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3ZXyo568JXLd3psLnyuDb%2FK8dI3ErN%2FBC%2Bj6p77ixqQ%3D&reserved=0 please consider above feedback for doc enhancement.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F68561%23issuecomment-758012559&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711603218|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=kSLPKUax1Fte9Llu5GBsJllKdBitQBIjYhy5zZZ%2BJx4%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF2PHPSZLN3ML36ASBJRNB3SZMIIZANCNFSM4VZGOVRA&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711613175|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=T9yp%2BiaerbrWU0ECdVG8MedL6CGjz1RTmTIkabnmuJ0%3D&reserved=0.

Thanks, there was not any other detailed information.   Just that it failed.   The detailed error message was “The deployment failed”   in the same place as your picture below where it says “The specified account has reached VM Series core quota ….”
Thanks,
Steve Wiederrich
Mobile:<PHONE_NUMBER>
From<EMAIL_ADDRESS>Sent: Monday, January 11, 2021 9:11 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Compute Instance fails, where's the logs?? (#68561)
@swiederhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fswieder&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711583311|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=D%2FUcmF4aEvCX2OSAfaRS9UDs4orKBfOIAHPN0JMphGQ%3D&reserved=0 thanks for providing more details. It doesn't seem like detailed log information is stored/shared publicly (verifying this information). Usually a failed deployment will have additional details printed out in the error message. Also, if you go to Azure ML Studio > Compute > Compute Instances tab > Select Compute > Status > Click on icon with "-", you'll see more details about the error as shown below.
[image]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F51332022%2F104198401-30283880-53f4-11eb-9053-93ac1e306a58.png&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711593267|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Ecv%2FCEvuCuh7tCSu%2BON7rdejEV4nq86f9Gdt%2BBvtxns%3D&reserved=0
[image]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F51332022%2F104198457-3f0eeb00-53f4-11eb-8daf-18d2c61c951a.png&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711593267|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=2vTdsRs6%2FZDC5gbbcf5SEZNuwuC5K3Gx7%2FbHqS9YkrM%3D&reserved=0
Feel free to share the detailed error message suing the above steps so we can investigate further, otherwise, you may have to follow the steps to contact Azure supporthttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-portal%2Fsupportability%2Fhow-to-create-azure-support-request&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711593267|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=8Y6FY%2BK1vxxhyvv4U6NCkg%2F9JYP0414Q%2BecyOl92cXI%3D&reserved=0 to identify the root cause.
@sdgilleyhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsdgilley&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711603218|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3ZXyo568JXLd3psLnyuDb%2FK8dI3ErN%2FBC%2Bj6p77ixqQ%3D&reserved=0 please consider above feedback for doc enhancement.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F68561%23issuecomment-758012559&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711603218|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=kSLPKUax1Fte9Llu5GBsJllKdBitQBIjYhy5zZZ%2BJx4%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF2PHPSZLN3ML36ASBJRNB3SZMIIZANCNFSM4VZGOVRA&data=04|01||ba7c85db9ab9419ad86808d8b6432087|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637459746711613175|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=T9yp%2BiaerbrWU0ECdVG8MedL6CGjz1RTmTIkabnmuJ0%3D&reserved=0.

Will proceed to close this thread since issue is being reviewed with the product team.

Will proceed to close this thread since issue is being reviewed with the product team.


Dropdown features

open on focus
disabled
auto width
keyboard
close after clicking inside the popup or persist it
manual toggle
placement for the popup
activator and popup elements
can merge with a button
offset/distance menu
merges with the list/list-item component or has its own component
indicator element with 2 slot open and close
trigger action (hover, click, touch)

https://getbootstrap.com/docs/4.0/components/dropdowns/
https://atlassian.design/components/dropdown-menu/examples
https://anvil.servicetitan.com/components/action-menu/
https://clarity.design/documentation/dropdowns
https://garden.zendesk.com/components/menu
https://biings.design/#/dropdown
https://at-ui.github.io/at-ui/#/en/docs/dropdown
https://comet.discoveryeducation.com/components/dropdown-menus.html
https://mesosphere.github.io/cnvs/components/dropdowns/#


Missing packages in Ubuntu Xenial

Hi there,
we were using the Ubuntu Trusty image and now want to use the Ubuntu Xenial image. Within our bosh deployment, we use the capi-release to mount a NFS share. But the Ubuntu Xenial image does not include the nfs-common package, so the mount fails. The Ubuntu Trusty image does. Is there a reason why it's missing in the Trusty image? Or is it possible to get the package on some other ways into the stemcell?
BR
Onke

@Onke we've decided to remove these packages from the stemcell as they are not needed by 99% of releases (we've been planning to do so for some time now but just did not want to do it on trusty stemcell). more targeted solution here is for capi-release (or some additional release) to include nfs bits instead of relying on the stemcell to have them.
capi team is aware of this change in xenial stemcell and will be working to address it at some point. i would recommend reaching out to them via slack or filing issue against their repo.


Parse spaceapi.json file

Parse the local spaceapi.json file to use for testing
Hints:

https://stackoverflow.com/questions/61505904/how-can-i-parse-a-local-json-file-to-a-listview-in-swiftui-new-to-app-developme
https://www.avanderlee.com/swift/json-parsing-decoding/

load the single Hackspaces in the struct BrowseView


Crawl specs in same process for easier debugging

@tidoust this is what I did to be able to debug https://github.com/tidoust/reffy/issues/205. Would you like to have something like this checked in, or is it not worth it? The mode will probably break if it's not used by any tests...

Thanks @foolip! I just pushed an update that incorporates your code to create a debug mode for Reffy, see commit message for details. Note that I also made the crawling sequential in that mode to further ease debugging.

Thanks @tidoust, those changes look good, and I'll try it the next time I need to debug!


Printer configuration options

As far as I can tell, there's no way to configure what options are available for the client. For instance, the only supported paper sizes are Letter and A4 on the client, even though the printer properties on the server have A3 available. Is this solution Letter and A4 only as of now?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8c4e7221-25fc-1aff-75e4-47ce9ac6c285
Version Independent ID: 36236322-05f4-8cf8-dfa2-a4943dc5bb58
Content: Windows Server Hybrid Cloud Print overview
Content Source: WindowsServerDocs/administration/hybrid-cloud-print/hybrid-cloud-print-overview.md
Service: w10
GitHub Login: @TrudyHa
Microsoft Alias: TrudyHa

Hi LarsErikK,
we are facing the same issue. It seems to be related to the default driver which is distributed to the Client "MicrosoftEnterpriseCloudPrintClassDriver". We also are searching for a solution to provide the printing properties e.g. the right driver for the right printer instead of the "CloudPrint***-Driver".
Did you already get a response from Microsoft?

No, not yet. I've got a case open with Microsoft Premier support to get a straight answer to a really simple question; "can you add additional paper sizes so they're available for the client?". But so far they don't seem to know or understand the difference between Hybrid Cloud Print and the regular windows print solutions with a directly connected print server. I'll update you when and if I get an answer.

Just implemented this as part of a move to Intune and came across this limitation. Seems strange that basic options like paper size and colour/greyscale selection wouldn't be supported from the start.

Hi @ all, we also had contact to Microsoft. We got the information that the cloud print support for printers will be extended with windows server 2019.
Regards,
Nils

Hello @ all - now that Windows Server 2019 is GA, where might one read about the updates around the cloud print support?

Hi @adrianwells ,  for WS2019, Hybrid Cloud Print now offers support for printer preferences. Documentation is not available yet. The team is working on prioritizing it.
Thanks,
Corey

@coreyp-at-msft, OK.  That is good to know.  Look forward to seeing it soon.


test: update k8s testing versions to v1.12.10, v1.13.8 and v1.14.4

Signed-off-by: André Martins<EMAIL_ADDRESS>

test-me-please

Coverage decreased (-0.009%) to 44.468% when pulling 83ba956ebd649431311895fcf220ecc9e24f82a6 on pr/update-k8s-test-versions into 9254431c761069565ca9a0b56cf62a55d318a1fe on master.


Update README.md

Help make the manual installation steps a bit more robust for copy n pasters' out there.

Warnings

:warning:

Please include an updated CHANGELOG.md file.This way we can keep track of all the contributions.

  Generated by :no_entry_sign: dangerJS


Failed to load the irc package

[Enter steps to reproduce:]

...
...

Atom: 1.19.2 x64
Electron: 1.6.9
OS: Mac OS X 10.12.6
Thrown From: irc package 0.4.0
Stack Trace
Failed to load the irc package
At The super constructor to "inherits" must not be null or undefined

TypeError: The super constructor to "inherits" must not be null or undefined
    at Object.exports.inherits (util.js:961:11)
    at /packages/irc/node_modules/irc/lib/irc.js:575:6)
    at /packages/irc/node_modules/irc/lib/irc.js:956:3)
    at Module.get_Module._compile (/Applications/Atom.app/Contents/Resources/app/src/native-compile-cache.js:106:36)
    at Object.value [as .js] (/Applications/Atom.app/Contents/Resources/app/src/compile-cache.js:239:29)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (Applications/Atom.app/Contents/Resources/app/static/index.js:47:45)
    at require (/Applications/Atom.app/Contents/Resources/app/src/native-compile-cache.js:66:33)
    at /packages/irc/lib/connector.coffee:2:7)
    at /packages/irc/lib/connector.coffee:1:1)
    at /packages/irc/lib/connector.coffee:1:1)
    at Module.get_Module._compile (/Applications/Atom.app/Contents/Resources/app/src/native-compile-cache.js:106:36)
    at Object.value [as .coffee] (/Applications/Atom.app/Contents/Resources/app/src/compile-cache.js:239:29)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (Applications/Atom.app/Contents/Resources/app/static/index.js:47:45)
    at require (/Applications/Atom.app/Contents/Resources/app/src/native-compile-cache.js:66:33)
    at /packages/irc/lib/irc.coffee:5:10)
    at /packages/irc/lib/irc.coffee:1:1)
    at /packages/irc/lib/irc.coffee:1:1)
    at Module.get_Module._compile (/Applications/Atom.app/Contents/Resources/app/src/native-compile-cache.js:106:36)
    at Object.value [as .coffee] (/Applications/Atom.app/Contents/Resources/app/src/compile-cache.js:239:29)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (Applications/Atom.app/Contents/Resources/app/static/index.js:47:45)
    at require (internal/module.js:20:19)

Commands

Non-Core Packages
atom-asana 0.0.0
atom-autocomplete-php 0.25.6
atom-beautify 0.30.5
atom-laravel-log 0.0.0
atom-ternjs 0.18.3
atom-translator 0.2.1
data-atom 0.25.2
emmet 2.4.3
git-time-machine 1.5.9
gpp-compiler 3.0.7
highlight-selected 0.13.1
irc 0.4.0
merge-conflicts 1.4.5
minimap-highlight-selected 4.6.1
php-cs-fixer 4.1.0
phpfmt 1.0.0
RebelChat 0.8.1
termination 0.6.0

This appears to be a problem in the node-irc dependency. I submitted a fix here:
https://github.com/martynsmith/node-irc/pull/521

It doesn't look like the node-irc package is being updated or responding to pull requests / issues, which prompted me to create a fork, "irc-upd" (it can be found on GitHub here and on NPM here). I've been adding a bunch of tests, fixing some of the more major bugs, and trying to keep the development more active. (I created the fork mostly to improve the stability of a project that used node-irc as a dependency, discord-irc, but it looks like there might be some independent interest.)
I'm not sure if there would be inclination to swap, but I've added a commit which should fix this here. A new version hasn't been released yet, so it won't work if you just point at the library, and it's also under a different name, so references to irc would have to be updated, but if you use the commit hash and do that you might be able to get it working in the meantime.


Docs site appears to be out of date.

I just updated to the latest version of spek 1.0.9 and now the Spek constructor wants a body.

This is tripping me up too.

Looks like this is the new syntax:
class ContextGivenOnTest : Spek({
  given("a calculator") {
  }
})

Yes. Will be getting it all updated and ready for release.


refactor: remove LoadCheckpointError and ApplyLogError

Description
This PR removes LoadCheckpointError and  ApplyLogError as well as moves some more checkpoint related functions into the checkpoint module.
Aside from cleaning up errors, this moves us a little bit closer to isolating log handling related logic in preparation for some upcoming work.
Related Issue(s)
part of: #1136

and everyting in delta-rs just returns a DeltaError ...

@roeap I think that sounds great. Right now there are a few things that return different errors so you can't use ? if they are in the same scope.
Is there the possibility to create a class of errors Retryable? Things for transient errors like 5xx from object stores?


fix: table hover state

#1283

Fixes table link hover state to show darker color when hovering over the link or row
Adds caret that shows next to the link on hover

Demo

Looks great!


Notifications via stdout

A bunch of improvements to ease using yubikey-touch-detector as part of a pipe, for example in bash:
yubikey-touch-detector -no-socket -stdout | while read -r L; do
  if [ "${L}" = "GPG_1" ] || [ "${L}" = "U2F_1" ]; then
    # Show alert
  fi
done

Fixes #31

Thanks! Looks good overall, I pushed a small commits with various nitpicks, could you tell me if all that looks good to you, and if yes I'll proceed with the merge?

Yeah, that all seems very sensible to me---let's merge it.


How can I see the changelogs of this plugin ?

Everything is in the title. Thanks

check the commit history

Thank you SO much, I NEVER thought about it


Makes portfolio captions configurable

Adds a portfolio configuration option that controls whether
the item titles are shown when hovering over the images or as
captions under the images.
Also uses item titles for the alt field in the img tag,
improving accessibilty.

Hi!
Thanks for the PR, however I wouldn't to have too many flags on and off, because it might get confusing.
If somebody doesn't want the caption, I guess they'd just edit the theme portofolio.html and remove it. I'll close it for now, however if I see a growing interest from other users in that feature, I will reconsider it :wink: