Jest TextEncoder missing, Uint8Array failing instanceof checks workaround

When using jsdom environment the tests sometimes fail with Uint8Array is not defined etc.
You can workaround this by setting a testEnvironment in your jest.config.js:
...
testEnvironment: `${__dirname}/commands/jest/customizedTestEnvironment.js`,
...

Impl a custom environment:
const { TestEnvironment } = require('jest-environment-jsdom')

/**
 * Jest creates a new VM context for each test and doesn't add in all
 * the node globals.
 * We rectify this here.
 */
class CustomizedTestEnvironment extends TestEnvironment {
  constructor(config, context) {
    super(config, context)
  }

  async setup() {
    await super.setup()

    // These seem to be needed for @noble/hashes
    this.global.TextEncoder = globalThis.TextEncoder
    this.global.Uint8Array = globalThis.Uint8Array
  }
}

module.exports = CustomizedTestEnvironment

It would be nice if didn't need to do this. May need to patch the jsdom environment?
In any case leaving this here in case it helps others.

It would be nice if didn't need to do this.

What's your suggested solution?

Not sure there is much you can do other than document it ?(this issue
hopefully enough, even if closed). When I get a chance I will open a PR for
the jsdom environment.

I'll edit issue to remove fetch mentions when not on mobile. Opened when
tired trying to be good citizen. Fetch is irrelevant

On mobile, will look tomorrow. For now, can say Jest creates VM contexts to
run the tests. So where you set up the globals probably matters.

global.TextEncoder = TextEncoder;
global.Uint8Array = Uint8Array;

I think that's essentially a noop ?

I don't think you can supply a testEnvironment option
Annoying!
Been a while since I used CRA, but can you mess with jest cli args ?
https://jestjs.io/docs/cli#--envenvironment

Yeah, for anyone who face this problem in the future, here is how I managed to get it working.
1- Add a env flag to your test script: "test": "react-scripts test --env=./src/utils/testing/jest-environment-jsdom.js",
2- Create a jest env file that has the following:
const { TextDecoder, TextEncoder } = require("util");

const JsdomEnvironment = require("jest-environment-jsdom");

export default class CustomJsdomEnvironment extends JsdomEnvironment {
  async setup() {
    await super.setup();

    if (!this.global.TextDecoder) {
      this.global.TextDecoder = TextDecoder;
    } else {
      throw new Error(`Unnecessary polyfill "TextDecoder"`);
    }

    if (!this.global.TextEncoder) {
      this.global.TextEncoder = TextEncoder;
      this.global.Uint8Array = Uint8Array;
    } else {
      throw new Error(`Unnecessary polyfill "TextEncoder"`);
    }
  }
}

Only overriding the TextEncoder/Decoder wasn't enough for me, I had to also add Uint8Array.

What's your suggested solution from the noble-hashes end?

@paulmillr One thing that noble-hashes can do to help developers avoid this problem is:
by not using data instanceof Uint8Array.
Instead, maybe use the isUint8Array that is provided by utils/types.
I tried it, and it seems to be working fine.
https://nodejs.org/api/util.html#utiltypesisuint8arrayvalue

@MTG2000 noble-hashes is not node.js library. It is cross-platform. There is no utils/types in browser.
Every solution wrt uint8array type check has its drawbacks. We have tried changing logic in the past.

@MTG2000
 if (!this.global.TextDecoder) {
      this.global.TextDecoder = TextDecoder;
    } else {
      throw new Error(`Unnecessary polyfill "TextDecoder"`);
    }

    if (!this.global.TextEncoder) {
      this.global.TextEncoder = TextEncoder;
      this.global.Uint8Array = Uint8Array;
    } else {
      throw new Error(`Unnecessary polyfill "TextEncoder"`);
    }

Your logic looks strange here

Your logic looks strange here

Why??
(And btw, this is not something I came up with, this is how someone else facing the same problem fixed it)

Nevermind, I was looking while busy.
On second glance it seems OK
But you might want to create a whole new block (with specific error) for the Uint8Array?

Hi, I don't know if I am the issue or not. However, at one point in my Blockchain/crypto endeavors I was able to validate my account and it was referencing unit8 however, somehow all of my funds disappeared right before my very eyes in metamask while on a mobile device. Since that point nothing I do seems to yield profits. I apologize profusely if I have somehow caused this problem. Also, I don't know if anyone can or would be willing to assist me in the recovery of my account which I am sure is a lost cause now. I am trying to move forward in life in every way possible even with my repeated knock downs. I am a humble person so it takes a lot to ask for assistance but I don't know what to do anymore aside from admit defeat and begin anew. Thank you for hearing me out and I appreciate any advice.


feat: add data source smartENERGY

I have implemented the supplier smartENERGY.at as an additional data source.
I would be delighted if the code is reviewed and accepted!

Thanks for your contribution.


Set up deployment in S3 bucket

Set up an AWS S3 bucket so that the react app can be hosted publicly when doing a release or deployment for production.
AWS Codepipeline could be set up so that when a push is made to the main branch, the app is automatically deployed to the bucket.

Will probably end up using CloudFlare or Netlify for hosting the react app.
Closing this ticket.


Move autoround from generate.py to eval.py

As Auto-Round is an algorithm focused on improving accuracy instead of perf, move it from generate.py to eval.py.
cc @thuang6

Hi @HDCharles @jerryzh168, please have a look, thanks!

I added evaluations.sh into a PR a few hours ago, can you move evals.sh into there?

Ready for merge.


Learning-to-Compare-Relation-Network-for-Few-Shot-Learning

issue引用https://github.com/BUPT/awesome-chatbot/issues/77

Poster
论文说明
few-shot learning 中效果比较好的模型

There are conflicts in _sidebar.md. You should "git pull" first before you make any change.

I have fix the conflict. Thx for informing that


ERROR: Memory: bad allocation size 943194112 bytes

plis help, this error is displayed on the screen when i try to open a model with skeleton:
ERROR: Memory: bad allocation size 943194112 bytes
appMalloc:size=943194112 (total=65 Mbytes) <- FArray::Empty:16842752 x 56 <- TArray::Serialize:0/0 <- FStaticLODModel4<< <- TArray::Serialize:0/1 <- USkeletalMesh4::Serialize <- LoadObject:SkeletalMesh4'Pickaxe_BatSickle.Pickaxe_BatSickle', pos=1708, ver=513/0 (unversioned), game=ue4.16 <- UObject::EndLoad <- CUmodelApp::ShowPackageUI <- UIMenuItem::HandleCommand <- UIMenuItem::HandleCommand <- CUmodelApp::WndProc <- VisualizerLoop <- Main:umodel_build=761
this error is displayed at moment of extrat or open any object (model with skeleton(mesh))of Fortnite:

can u help me?.

I see mistakes in your usage. However, providing you a direct answer won't help you, you'll return here with any other noob error. For the beginning, I'd recommend you to learn how to use google. Most likely you'll find this thread after that:
http://www.gildor.org/smf/index.php/topic,3317.0.html
And I hope you will notice the very first in that thread, it is marked with large bold colored text, saying that it MUST be read.

thanks, sorry for the loss of time.


TypeError: Cannot read properties of null

          Hey! Thanks for the fix! I updated mqdockerup and now I see all containers in Home Assistant, but some of them are just filled with unknown values, some are fine. also in container log I get this error, the container restarts every time:

><EMAIL_ADDRESS>start
> node dist/src/index.js
  __  __       ____             _             _   _
 |  \/  | __ _|  _ \  ___   ___| | _____ _ __| | | |_ __
 | |\/| |/ _` | | | |/ _ \ / __| |/ / _ \ '__| | | | '_ \
 | |  | | (_| | |_| | (_) | (__|   <  __/ |  | |_| | |_) |
 |_|  |_|\__, |____/ \___/ \___|_|\_\___|_|   \___/| .__/
            |_|                                    |_|
Starting MqDockerUp V0.14.5 ...
24.03.2023 14:57:09 [info] 	Connected to MQTT broker
24.03.2023 14:57:09 [info] 	Checking for new/old containers...
24.03.2023 14:57:10 [info] 	Checking for image updates...
24.03.2023 14:57:10 [info] 	Image micrib/mqdockerup:latest is up-to-date
24.03.2023 14:57:10 [info] 	New version available for image nbr23/youtube-dl-server:yt-dlp
24.03.2023 14:57:11 [warn] 	Failed to find new digest for image vonproteus/podcast-generator:latest
24.03.2023 14:57:11 [error] 	MqDockerUp stopped due to an error
24.03.2023 14:57:11 [error] 	object
24.03.2023 14:57:11 [error] 	TypeError: Cannot read properties of null (reading 'data')
    at Function.<anonymous> (/app/src/services/HomeassistantService.ts:236:23)
    at Generator.next (<anonymous>)
    at fulfilled (/app/dist/src/services/HomeassistantService.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Originally posted by @PeteSSMMSS in https://github.com/MichelFR/MqDockerUp/issues/21#issuecomment-1482945505

Created this issue, I am experiencing the exact same behaviour after the update

Same issue here.

Thanks for opening a new issue.
Im looking into it, might be just a simple oversight.

This may be fixed now so that MqDockerUp is not stopped when it occurs, it should additonally output more information to the logs.
If you see any related errors please feel free to contact me

This may be fixed now so that MqDockerUp is not stopped when it occurs, it should additonally output more information to the logs. If you see any related errors please feel free to contact me

Cool thanks! Can you update the docker container on DockerHub to v0.14.6 so I can test it?

Created a release right now, images should be up in 2-3 minutes

Same error with 0.14.6.
  __  __       ____             _             _   _
 |  \/  | __ _|  _ \  ___   ___| | _____ _ __| | | |_ __
 | |\/| |/ _` | | | |/ _ \ / __| |/ / _ \ '__| | | | '_ \
 | |  | | (_| | |_| | (_) | (__|   <  __/ |  | |_| | |_) |
 |_|  |_|\__, |____/ \___/ \___|_|\_\___|_|   \___/| .__/
            |_|                                    |_|
Starting MqDockerUp V0.14.6 ...

29.03.2023 16:40:27 [info] 	Connected to MQTT broker
29.03.2023 16:40:27 [info] 	Checking for new/old containers...
29.03.2023 16:40:27 [info] 	Checking for image updates...
29.03.2023 16:40:28 [info] 	Image micrib/mqdockerup:latest is up-to-date
29.03.2023 16:40:29 [info] 	Image esphome/esphome:latest is up-to-date
29.03.2023 16:40:30 [error] 	MqDockerUp stopped due to an error
29.03.2023 16:40:30 [error] 	object
29.03.2023 16:40:30 [error] 	TypeError: Cannot read properties of null (reading 'data')
    at Function.<anonymous> (/app/src/services/HomeassistantService.ts:237:19)
    at Generator.next (<anonymous>)
    at fulfilled (/app/dist/src/services/HomeassistantService.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

same :(

hey! 0.14.8 seems to work for me, can see some of my containers in HA - some are still missing, this are the container logs:

29.03.2023 18:29:15 [warn] 	Failed to find new digest for image vonproteus/podcast-generator:latest
29.03.2023 18:29:15 [error] 	No Images found:
29.03.2023 18:29:15 [error] 	null
29.03.2023 18:29:15 [warn] 	Failed to find new digest for image php:7-fpm-alpine
29.03.2023 18:29:15 [warn] 	Failed to find new digest for image radhifadlillah/shiori:latest
29.03.2023 18:29:16 [info] 	New version available for image joplin/server:latest
29.03.2023 18:29:16 [error] 	No Images found:
29.03.2023 18:29:16 [error] 	null
29.03.2023 18:29:16 [warn] 	Failed to find new digest for image postgres:latest
29.03.2023 18:29:16 [error] 	No Images found:
29.03.2023 18:29:16 [error] 	null
29.03.2023 18:29:16 [warn] 	Failed to find new digest for image docker.io/library/postgres:13
29.03.2023 18:29:16 [error] 	No Images found:
29.03.2023 18:29:16 [error] 	null
29.03.2023 18:29:16 [warn] 	Failed to find new digest for image ghcr.io/paperless-ngx/paperless-ngx:latest
29.03.2023 18:29:17 [error] 	No Images found:
29.03.2023 18:29:17 [error] 	null
29.03.2023 18:29:17 [warn] 	Failed to find new digest for image docker.io/library/redis:6.0
29.03.2023 18:29:17 [info] 	New version available for image benkl/firefly-iii-fints-importer:latest
29.03.2023 18:29:17 [error] 	No Images found:
29.03.2023 18:29:17 [error] 	null
29.03.2023 18:29:17 [warn] 	Failed to find new digest for image alpine:latest
29.03.2023 18:29:17 [info] 	New version available for image fireflyiii/core:latest
29.03.2023 18:29:18 [error] 	No Images found:
29.03.2023 18:29:18 [error] 	null
29.03.2023 18:29:18 [warn] 	Failed to find new digest for image redis:latest
29.03.2023 18:29:18 [info] 	Image gotify/server:latest is up-to-date
29.03.2023 18:29:18 [info] 	Image portainer/portainer-ce:latest is up-to-date
29.03.2023 18:29:19 [info] 	New version available for image fmartinou/whats-up-docker:latest
29.03.2023 18:29:19 [info] 	New version available for image wger/apache:latest
29.03.2023 18:29:19 [info] 	Image sissbruecker/linkding:latest is up-to-date
29.03.2023 18:29:19 [error] 	No Images found:
29.03.2023 18:29:19 [error] 	null
29.03.2023 18:29:19 [warn] 	Failed to find new digest for image docker.io/library/postgres:13
29.03.2023 18:29:20 [info] 	New version available for image louislam/uptime-kuma:latest
29.03.2023 18:29:20 [error] 	No Images found:
29.03.2023 18:29:20 [error] 	null
29.03.2023 18:29:20 [warn] 	Failed to find new digest for image postgres:latest
29.03.2023 18:29:20 [warn] 	Failed to find new digest for image philhawthorne/ha-dockermon:latest
29.03.2023 18:29:23 [info] 	New version available for image grafana/loki:latest
29.03.2023 18:29:23 [info] 	Finished checking for image updates
29.03.2023 18:29:23 [info] 	Next check in 5 minutes

and in home assistant log these here:

2023-03-29 17:05:52.248 WARNING (MainThread) [homeassistant.components.mqtt.discovery] Received message on illegal discovery topic 'homeassistant/sensor/ghcr.io_paperless-ngx_paperless-ngx_latest/docker_id/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/docs/mqtt/discovery/#discovery-topic
2023-03-29 17:05:52.248 WARNING (MainThread) [homeassistant.components.mqtt.discovery] Received message on illegal discovery topic 'homeassistant/sensor/ghcr.io_paperless-ngx_paperless-ngx_latest/docker_name/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/docs/mqtt/discovery/#discovery-topic
2023-03-29 17:05:52.249 WARNING (MainThread) [homeassistant.components.mqtt.discovery] Received message on illegal discovery topic 'homeassistant/sensor/ghcr.io_paperless-ngx_paperless-ngx_latest/docker_status/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/docs/mqtt/discovery/#discovery-topic
2023-03-29 17:05:52.250 WARNING (MainThread) [homeassistant.components.mqtt.discovery] Received message on illegal discovery topic 'homeassistant/sensor/ghcr.io_paperless-ngx_paperless-ngx_latest/docker_uptime/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/docs/mqtt/discovery/#discovery-topic
2023-03-29 17:05:52.255 WARNING (MainThread) [homeassistant.components.mqtt.discovery] Received message on illegal discovery topic 'homeassistant/sensor/ghcr.io_paperless-ngx_paperless-ngx_latest/docker_ports/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/docs/mqtt/discovery/#discovery-topic
2023-03-29 17:05:52.258 WARNING (MainThread) [homeassistant.components.mqtt.discovery] Received message on illegal discovery topic 'homeassistant/sensor/ghcr.io_paperless-ngx_paperless-ngx_latest/docker_image/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/docs/mqtt/discovery/#discovery-topic
2023-03-29 17:05:52.259 WARNING (MainThread) [homeassistant.components.mqtt.discovery] Received message on illegal discovery topic 'homeassistant/sensor/ghcr.io_paperless-ngx_paperless-ngx_latest/docker_tag/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/docs/mqtt/discovery/#discovery-topic
2023-03-29 17:05:52.261 WARNING (MainThread) [homeassistant.components.mqtt.discovery] Received message on illegal discovery topic 'homeassistant/sensor/ghcr.io_paperless-ngx_paperless-ngx_latest/docker_registry/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/docs/mqtt/discovery/#discovery-topic

With the new release I have 4 of 16 containers working. The others are removed after finished task.
29.03.2023 18:31:05 [info] 	Image esphome/esphome:latest is up-to-date
29.03.2023 18:31:05 [error] 	No Images found:
29.03.2023 18:31:05 [error] 	null
29.03.2023 18:31:05 [warn] 	Failed to find new digest for image ghcr.io/home-assistant/home-assistant:stable

esphome is also not available, but the state seems ok in the log.

For me it is still not working:
  __  __       ____             _             _   _
 |  \/  | __ _|  _ \  ___   ___| | _____ _ __| | | |_ __
 | |\/| |/ _` | | | |/ _ \ / __| |/ / _ \ '__| | | | '_ \
 | |  | | (_| | |_| | (_) | (__|   <  __/ |  | |_| | |_) |
 |_|  |_|\__, |____/ \___/ \___|_|\_\___|_|   \___/| .__/
            |_|                                    |_|
Starting MqDockerUp V0.16.1 ...

24.04.2023 19:51:02 [info] 	Connected to MQTT broker
24.04.2023 19:51:02 [info] 	Checking for new/old containers...
24.04.2023 19:51:02 [info] 	Checking for image updates...
24.04.2023 19:51:02 [info] 	Image micrib/mqdockerup:latest is up-to-date
24.04.2023 19:51:03 [error] 	No Images found:
24.04.2023 19:51:03 [error] 	null
24.04.2023 19:51:03 [warn] 	Failed to find new digest for image ghcr.io/home-assistant/home-assistant:stable
24.04.2023 19:51:03 [error] 	No Images found:
24.04.2023 19:51:03 [error] 	null
24.04.2023 19:51:03 [warn] 	Failed to find new digest for image ghcr.io/esphome/esphome:latest
24.04.2023 19:51:03 [warn] 	Failed to find new digest for image nodered:latest
24.04.2023 19:51:03 [info] 	New version available for image zwavejs/zwave-js-ui:latest
24.04.2023 19:51:04 [info] 	Image koenkk/zigbee2mqtt:latest is up-to-date
24.04.2023 19:51:04 [info] 	New version available for image dpage/pgadmin4:latest
24.04.2023 19:51:04 [error] 	No Images found:
24.04.2023 19:51:04 [error] 	null
24.04.2023 19:51:04 [warn] 	Failed to find new digest for image lscr.io/linuxserver/code-server:latest
24.04.2023 19:51:04 [info] 	New version available for image acockburn/appdaemon:latest
24.04.2023 19:51:05 [info] 	Image hkotel/mealie:api-v1.0.0beta-5 is up-to-date
24.04.2023 19:51:05 [info] 	Image hkotel/mealie:frontend-v1.0.0beta-5 is up-to-date
24.04.2023 19:51:05 [error] 	No Images found:
24.04.2023 19:51:05 [error] 	null
24.04.2023 19:51:05 [warn] 	Failed to find new digest for image lscr.io/linuxserver/cloud9:latest
24.04.2023 19:51:05 [info] 	New version available for image portainer/portainer-ce:latest
24.04.2023 19:51:06 [warn] 	Failed to find new digest for image rhasspy/rhasspy:latest
24.04.2023 19:51:06 [warn] 	Failed to find new digest for image postgres:14.1-alpine
24.04.2023 19:51:06 [info] 	New version available for image eclipse-mosquitto:latest
24.04.2023 19:51:06 [info] 	Finished checking for image updates
24.04.2023 19:51:06 [info] 	Next check in 5 minutes
24.04.2023 19:51:06 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant
24.04.2023 19:51:06 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant
24.04.2023 19:51:06 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant
24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant

For me it is still not working:

  __  __       ____             _             _   _

 |  \/  | __ _|  _ \  ___   ___| | _____ _ __| | | |_ __

 | |\/| |/ _` | | | |/ _ \ / __| |/ / _ \ '__| | | | '_ \

 | |  | | (_| | |_| | (_) | (__|   <  __/ |  | |_| | |_) |

 |_|  |_|\__, |____/ \___/ \___|_|\_\___|_|   \___/| .__/

            |_|                                    |_|

Starting MqDockerUp V0.16.1 ...

24.04.2023 19:51:02 [info] 	Connected to MQTT broker

24.04.2023 19:51:02 [info] 	Checking for new/old containers...

24.04.2023 19:51:02 [info] 	Checking for image updates...

24.04.2023 19:51:02 [info] 	Image micrib/mqdockerup:latest is up-to-date

24.04.2023 19:51:03 [error] 	No Images found:

24.04.2023 19:51:03 [error] 	null

24.04.2023 19:51:03 [warn] 	Failed to find new digest for image ghcr.io/home-assistant/home-assistant:stable

24.04.2023 19:51:03 [error] 	No Images found:

24.04.2023 19:51:03 [error] 	null

24.04.2023 19:51:03 [warn] 	Failed to find new digest for image ghcr.io/esphome/esphome:latest

24.04.2023 19:51:03 [warn] 	Failed to find new digest for image nodered:latest

24.04.2023 19:51:03 [info] 	New version available for image zwavejs/zwave-js-ui:latest

24.04.2023 19:51:04 [info] 	Image koenkk/zigbee2mqtt:latest is up-to-date

24.04.2023 19:51:04 [info] 	New version available for image dpage/pgadmin4:latest

24.04.2023 19:51:04 [error] 	No Images found:

24.04.2023 19:51:04 [error] 	null

24.04.2023 19:51:04 [warn] 	Failed to find new digest for image lscr.io/linuxserver/code-server:latest

24.04.2023 19:51:04 [info] 	New version available for image acockburn/appdaemon:latest

24.04.2023 19:51:05 [info] 	Image hkotel/mealie:api-v1.0.0beta-5 is up-to-date

24.04.2023 19:51:05 [info] 	Image hkotel/mealie:frontend-v1.0.0beta-5 is up-to-date

24.04.2023 19:51:05 [error] 	No Images found:

24.04.2023 19:51:05 [error] 	null

24.04.2023 19:51:05 [warn] 	Failed to find new digest for image lscr.io/linuxserver/cloud9:latest

24.04.2023 19:51:05 [info] 	New version available for image portainer/portainer-ce:latest

24.04.2023 19:51:06 [warn] 	Failed to find new digest for image rhasspy/rhasspy:latest

24.04.2023 19:51:06 [warn] 	Failed to find new digest for image postgres:14.1-alpine

24.04.2023 19:51:06 [info] 	New version available for image eclipse-mosquitto:latest

24.04.2023 19:51:06 [info] 	Finished checking for image updates

24.04.2023 19:51:06 [info] 	Next check in 5 minutes

24.04.2023 19:51:06 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant

24.04.2023 19:51:06 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant

24.04.2023 19:51:06 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container lscr.io/linuxserver/cloud9:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container eclipse-mosquitto:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container dpage/pgadmin4:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container koenkk/zigbee2mqtt:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container nodered:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container ghcr.io/esphome/esphome:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant

24.04.2023 19:51:07 [info] 	Removed missing container rhasspy/rhasspy:latest from Home Assistant

Are you getting anything shown in homeassistant? What exactly is Not working? There are some errors in the logs because it can't find the current version of some images. Currently only dockerhub images are supported.

Hi,
most of them are from Docker Hub, but only a few ones are in HA. Because they are removed from mqdockerup.
For example:
mosquitto
28.04.2023 17:05:40 [info] 	New version available for image eclipse-mosquitto:latest
28.04.2023 17:05:40 [info] 	Finished checking for image updates
28.04.2023 17:05:40 [info] 	Next check in 5 minutes

But the container gets removed.

@frittes alot of the images where removed because of a missing :latest tag when running container.
In the code i added it so that i new which tag to check for in dockerhub.
Now when it checks if a previously running container is still running it compares it correctly.
In future ill rewrite this, instead of using the container name i should use the container id.
Thanks for bringing this to my attention. Feel free to reopen the issue if it still does not work.


Flake8 test the whole repo

There are Python files elsewhere in the repo that are worth testing.
See the issues in #6 which have the potential to raise NameError at runtime.

I'm happy to take this with patches that also address the issues. It currently doesn't pass travis.


Add narrative about where to find the API documentation

In both the R and python notebooks, add some narrative about where to find the API documentation and which requests we used for the data retrieval steps.
Brynn if you do this first, I will incorporate into the .rmd file

Specify if this is the runtime NMDC API

OK if we add link to NMDC_Documentation repo for now, can redirect to front facing documentation later.


Speech_Audio Alignment

Hi. I am trying to understand you approach and I still don't quite see how alignments are done for unrelated text and speech corporas. Could you please explain that and point out the files in the code that implement it ?

Thanks for your answer.
How about pseudo-transcript self-training? How is it done ? and why was it necessary in your system? also how does it fit in the GAN architecture ?


Literature evidence widget crashing occasionally

Bibliography widget in this page is crashing (second row):
non-small cell lung carcinoma - EuropePMC

Fixed in latest UI version


Fixed bug of mismatched weight shapes

The if condition checking for list(shape) != list(weights.shape)  always raises a value error because the segment of code just above it does this
                weights = np.zeros(                     (char_embed_weights.shape[0] + 1,                      char_embed_weights.shape[1]),                     dtype=DTYPE                 )
I have removed the condition checking for matching weight shapes and everything seems to work fine.

This check is important to ensure the weight and options files are compatible, and will pass if everything is configured properly.  Removing it may lead to silent errors.


Persisted state doesn't update when calling this.$reset() and then setting state values

Minimal example:
export const useStore = defineStore('main', {
  state: () => ({
    counter: 0,
  }),
  persist: true,
  actions: {
    // If this function is not async with await on $reset, the localstorage doesn't update (even though pinia does update)
    // If F5 is pressed after setCounter has been called, counter will go back to previous state instead of 100
    setCounter100() {
      this.$reset();
      this.counter = 100
    },
  },
})

Hi, what versions are you running ? I tried with the examples given in the repo (using vite + vue3) and with your exact store it works fine and properly saves counter as 100 in the storage, and rehydrates properly.
If you could provide a complete repo with your problem so it can be investigated. thanks :)

Sorry it took me so long, here is an example repo of the issue
https://github.com/christianlmc/bug-pinia-plugin-persistedstate

Okay, i investigated a bit, and there seems to be some off behaviour with the $reset method. The way mutations are committed is not the same on the very first time, and the following ones.
If you put this in your HomeView.vue

<template>

    <button @click="setCounter100">do thing</button>

Counter

    {{ counter }}
    <input v-model="counter" />

Look at Local Storage, on the 'Application' tab on the Inspector

It shows {"counter":0} (Tested on Chrome 99)

</template>

After loading the page, the first click on the button will give you 2 subscription events, and the state will be store in localStorage properly, but if you click again, only 1 subscription event  containing everything is emitted, and the state is not persisted correctly. Reloading the page resets this behaviour every time. This seems more like a pinia issue/behaviour im not aware of.
Also it seems suspiciously tied to this issue https://github.com/vuejs/pinia/issues/1129

or this one https://github.com/vuejs/pinia/issues/992

Thank you @prazdevs, I will keep using the await this.$reset workaround for the time being

Same here, not working with await. But for me it's not even resetting the pinia store on .$reset
I disabled the persistedstate plugin and I still have the same issue with .$reset not working, could this be a pinia issue?


feat: Add PWA (Progressive web app) in ProjectsHut

What feature?
Hey, I want to add the PWA to this site so it's also installable.
If you need this feature then can you please assign it to me?
Add screenshots

Record

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

yeah @SubhamB2003  we can do this assigned to you


chore: release 0.0.16

It looks like Andrew and Thea are the two people with permissions to publish this package. https://pypi.org/project/gcp-devrel-py-tools/


Verify routing requests to the global DNS

Test: Execute an example request to the global DNS and see the corresponding logs on the upstream cluster showing evidence of the routed HTTP request.


Template parameters can contain xml tags

Template parameter keys and values can contain xml tags.

Codecov Report

Merging #58 (8e14bf1) into main (4739554) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #58   +/-   ##
=========================================
  Coverage     82.03%   82.03%
  Complexity      365      365
=========================================
  Files            50       50
  Lines           963      963
  Branches         59       59
=========================================
  Hits            790      790
  Misses          144      144
  Partials         29       29

Flag
Coverage Δ

unittest
82.03% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[cryo] Use mysql options file for setting password

Reduce the risk of leaking the MySQL password.
@jtai

And @philsnow

Thanks Phil. Your expertise is always appreciated :)

I will use Tempfile but still explicitly unlink the file.

When a Tempfile object is garbage collected, or when the Ruby interpreter exits, its associated temporary file is automatically deleted. This means that’s it’s unnecessary to explicitly delete a Tempfile after use, though it’s good practice to do so: not explicitly deleting unused Tempfiles can potentially leave behind large amounts of tempfiles on the filesystem until they’re garbage collected. The existence of these temp files can make it harder to determine a new Tempfile filename.

Thanks Phil. Updated with your recommendations.

:+1:
is mysqldump clever enough to not need the final newline in its .cnf file ?

Yup! I tested this in the actual program.


Add full TFLite pipeline for FastSpeech and MBMelgan

I have added a notebook to convert mb-melgan also to tf-lite form and test full pipeline for TFLite inference.
Note: This notebook uses FastSpeech.v3 and requires tf-nightly 2.4dev.

@sujeendran thanks :)), i also updated the fastspeech2 conversion on google colab, can you update ur notebook also to check the Quality of FastSpeech2 ?

@dathudeptrai Sure I will try it.

@sujeendran also don't forget to add the code to hear audio generated at the end of the notebook :)), i think float16 or float32 is ok but for int8 i think the performance will drop much :)).

Hi I have added FastSpeech2 TFLite also based on your updated notebook. Please check.
BTW, i noticed the prepare input function in your notebook is missing the f0 and energy ratios fields. I had to add it in my notebook to get it working. I have added Audio() function to listen to audios generated.

@dathudeptrai In case you face trouble viewing the notebook here is the colab link for the same: https://colab.research.google.com/drive/1DTmxxhYy69UgVyPlfaTD85h_UZT9Qi25?usp=sharing

@sujeendran give me some times, i will merge soon

@dathudeptrai i can add streaming part in this notebook.

@manmay-nakhashi you can add streaming part on separate folder in examples dir. Maybe we should implement something like client/server :)). Also i think this streaming should add non-commercial license. At this time, anything about android app or server-side should licensed under non-commercial License rather than Apache2.0.

@dathudeptrai sure sounds good to me :)

@dathudeptrai In case you face trouble viewing the notebook here is the colab link for the same: https://colab.research.google.com/drive/1DTmxxhYy69UgVyPlfaTD85h_UZT9Qi25?usp=sharing

Is the TFlite model quantized? Does that mean there are large amounts of latency? Hence the long runtimes.
If porting this to be (near) realtime what should the steps forward involve.

@MegaPanchamZ hi, FastSpeech2+Mb-melgan is already faster than real-time. And yes, the model converts to 8bit so the size reduces 4x times but because tflite optimize not yet optimize for x86 so the inference time will be very slow.

FYI, you're missing a dependency


Add display of additional details for affiliation term matches

For the affiliation type-ahead search, display additional information along with the name matches to help users choose the right entity.
ROR's recommendations: https://ror.readme.io/docs/create-ror-powered-typeaheads#show-information-beyond-the-primary-organization-name
These include displaying in addition to the primary name:

addresses.geonames_city.city (City name)
coutnry.country_name (country)
organization type (I don't think we need this)
acronyms
aliases
labels (these are names in other languages)

I'm concerned that this might get kind of a lot to display, but I don't know what the data look like.
The ROR example shows it laid out like this:

Note that they currently have a field that include US states but they are getting rid of it in the near future, so it doesn't seem worth including it now. State information will not be directly available in ROR -- we would have to look up the states using the geonames for the cities.

@astridu Do you have time to look at mocking up what this might look like for us?

How does this look? https://invis.io/NP138M0QX7T3#/473166568_add_Affiliation

@astridu State will not be included, only city and country. How will it look when there are multiple entries for acronyms, aliases and names in other languages?

Adding design needed label and moving to backlog for now. @amyehodge can you remove that label and move it back to ready when this is good to go?

Here is the mockup: https://invis.io/NP138M0QX7T3#/473166568_add_Affiliation


bw_plex watch errors

Hi, I've installed everything that was required and I've setup the config file to what I believe is correct.
So I've tried running bw_plex watch but I'm getting these errors.
I'm on Windows 7.
File "c:\Python27\Scripts\bw_plex-script.py", line 11, in <module>   load_entry_point('bw-plex', 'console_scripts', 'bw_plex')() File "c:\python27\lib\site-packages\click\core.py", line 722, in __call__   return self.main(*args, **kwargs) File "c:\python27\lib\site-packages\click\core.py", line 697, in main   rv = self.invoke(ctx) File "c:\python27\lib\site-packages\click\core.py", line 1063, in invoke   Command.invoke(self, ctx) File "c:\python27\lib\site-packages\click\core.py", line 895, in invoke   return ctx.invoke(self.callback, **ctx.params) File "c:\python27\lib\site-packages\click\core.py", line 535, in invoke   return callback(*args, **kwargs) File "c:\users\patrick\src\bw-plex\bw_plex\plex.py", line 176, in cli   verify_ssl=verify_ssl) File "c:\users\patrick\src\bw-plex\bw_plex\misc.py", line 44, in get_pms   PMS = PlexServer(url, token, sess) File "c:\python27\lib\site-packages\plexapi\server.py", line 102, in __init_   data = self.query(self.key, timeout=timeout) File "c:\python27\lib\site-packages\plexapi\server.py", line 348, in query   return ElementTree.fromstring(data) if data.strip() else None File "<string>", line 124, in XML lementTree.ParseError: not well-formed (invalid token): line 20, column 56
Then I tried installing pip again incase something was missing and I got these errors.
File "c:\Python27\Scripts\bw_plex-script.py", line 11, in <module>   load_entry_point('bw-plex', 'console_scripts', 'bw_plex')() File "c:\python27\lib\site-packages\click\core.py", line 722, in __call__   return self.main(*args, **kwargs) File "c:\python27\lib\site-packages\click\core.py", line 697, in main   rv = self.invoke(ctx) File "c:\python27\lib\site-packages\click\core.py", line 1063, in invoke   Command.invoke(self, ctx) File "c:\python27\lib\site-packages\click\core.py", line 895, in invoke   return ctx.invoke(self.callback, **ctx.params) File "c:\python27\lib\site-packages\click\core.py", line 535, in invoke   return callback(*args, **kwargs) File "c:\users\patrick\src\bw-plex\bw_plex\plex.py", line 176, in cli   verify_ssl=verify_ssl) File "c:\users\patrick\src\bw-plex\bw_plex\misc.py", line 44, in get_pms   PMS = PlexServer(url, token, sess) File "c:\python27\lib\site-packages\plexapi\server.py", line 102, in __init_   data = self.query(self.key, timeout=timeout) File "c:\python27\lib\site-packages\plexapi\server.py", line 348, in query   return ElementTree.fromstring(data) if data.strip() else None File "<string>", line 124, in XML lementTree.ParseError: not well-formed (invalid token): line 20, column 56

Thanks for trying. This is a parser error while trying to logon to your plex server. Can you double check your config file
url needs to be in: http://ip:port
and token is simpley the token. https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/

I seem to have fixed the config I believe.
but I'm getting Aborted! now
`PS C:\Users\patrick> bw_plex watch
2018-05-23 17:43:08,868 :: bw_plex :: DEBUG :: Getting server patrick-PC
2018-05-23 17:43:08,871 :: bw_plex :: DEBUG :: Getting hashtable
2018-05-23 17:43:09,953 :: bw_plex :: INFO :: Loading existing files in db
Aborted!
PS C:\Users\patrick> bw_plex watch
2018-05-23 18:56:37,944 :: bw_plex :: DEBUG :: Getting server patrick-PC
2018-05-23 18:56:37,946 :: bw_plex :: DEBUG :: Getting hashtable
2018-05-23 18:56:39,048 :: bw_plex :: INFO :: Loading existing files in db
Aborted!`

It’s just to given you a notice that you have cancel the cli using control c. Try letting it run for a while

it gives me that aborted! immediately after typing in bw_plex watch without touching anything else.

Hm, i have no idea why that happens. Can you try to upgrade bw_plex? pip install -U bw_plex
Delete the hashes.pklz file and try again.
What python version is this? Is it 64 or 32  bit? You can find this by executing python -V in cmd/shell
What happens if you try another command line bw_plex process -n SOME_SHOW_NAME ?

2.7.13 python version, 64 bit
So, I tried pip install -U bw_plex and it just said 'Requirement not upgraded as not directly required:'
for everything.
Then I deleted the hashes.pklz and tried bw_plex watch again and I'm getting the first error in my first post again with the parser errors.
I try bw_plex watch again. I'm getting the second errors saying its !aborted. So I'm guessing I somehow don't have my config file correct.
I tried bw_plex process -n Archer since I know I have some of those episodes.
It displays
2018-05-24 09:51:46,634 :: bw_plex :: DEBUG :: Getting server patrick-PC

0 Archer (2009)

Select what show to process:

I click 0 and it brings up the episodes, I click the number for the episode and I get the same error below.
2018-05-24 09:57:06,131 :: bw_plex :: DEBUG :: Getting hashtable
2018-05-24 09:57:06,375 :: bw_plex :: INFO :: Loading existing files in db

Aborted!

I'll give a general idea of what my config file looks like without giving away my info and you let me know if something is out of place.
url = http://ip:port
token = mytoken
verify_ssl = False
servername = patrick-PC
debug = False
username = myusername
password = mypassword
thread_pool_number = 10
check_for_theme_sec = 600
words = previously on, last season, last episode
ignore_show = ,
level = debug
users = ,
clients = ,
mode = skip_only_theme
theme_source = all
check_credits = False
check_credits_action =
check_credits_start_next_ep = True
check_credits_sec = 120
process_recently_added = False
process_deleted = False

I'll keep fiddling with it and seeing if something else works.

Config looks good. I don’t get why this happens. Only think I could think on some exceptions getting swallowed while loading the hash table. Is there any themes in the theme and temp themes folder if so can you delete them and the hashtable file and try to run the program in cmd.exe? If this doesn’t I’ll work I’ll write a branch with more logging

Nothing in either theme folder sadly. Let me know if you update the branch, Thanks!

These are the only logs I found in your .config folder https://gist.github.com/notnicecream/5873fcf2ac29980fc16726d0f2597c93
But I also copied over the errors from my cmd to this gist for you as well
https://gist.github.com/notnicecream/38b88f312acfdff930973f84073515c2

Awesome. The logs indicate a memory errror (generally this means you have to little memory in general or that the process used to much memory. How much memory do you have on your computer? Do you have several python versions installed? Python 32 and 64 bit python 3 and python 2?

I have 16gbs of memory, I had around 7gbs of free memory when I first tried it. I stopped running everything else just incase it needed more than 7gbs and its still giving the same memory error.
I'm 95% sure I only have python 2.7 64bit
As for running python plex.py watch, it's giving me basically the same error, see below.
PS C:\Users\patrick\src\bw-plex\bw_plex> python plex.py watch
2018-05-24 13:25:17,246 :: bw_plex :: DEBUG :: Getting server patrick-PC
2018-05-24 13:25:17,247 :: bw_plex :: DEBUG :: Getting hashtable
2018-05-24 13:25:17,486 :: bw_plex :: INFO :: Creating new hashtable db
2018-05-24 13:25:17,487 :: bw_plex :: DEBUG :: Saving HashTable
Traceback (most recent call last):
  File "plex.py", line 924, in <module>
    cli()
  File "c:\Python27\lib\site-packages\click\core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "c:\Python27\lib\site-packages\click\core.py", line 697, in main
    rv = self.invoke(ctx)
  File "c:\Python27\lib\site-packages\click\core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "c:\Python27\lib\site-packages\click\core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "c:\Python27\lib\site-packages\click\core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "plex.py", line 858, in watch
    HT = get_hashtable()
  File "c:\users\patrick\src\bw-plex\bw_plex\misc.py", line 650, in get_hashtable
    HT.save(FP_HASHES)
  File "c:\users\patrick\src\bw-plex\bw_plex\misc.py", line 596, in save
    pickle.dump(self, f, pickle.HIGHEST_PROTOCOL)
MemoryError

If you just write python in cmd it should start idle. The version type is listed at the top. Highest memory usage I have seen so far is around 2 gb. 7 should be plenty.

Ok, so I had 32 bit python apparently. I went on to uninstall everything and reinstall everything but using python 64 bit 2.7.15.
It seems to be running now. the only thing is I get the warning below.
2018-05-24 15:23:29,144 :: bw_plex :: WARNING :: Scanning for credits is not supported. Install the package with pip ins
tall bw_plex[all] or bw_plex[video]
2018-05-24 15:23:29,167 :: bw_plex :: WARNING :: Extracting text from images is not supported. Install the package with
pip install bw_plex[all] or bw_plex[video]

I tried doing pip install bw_plex[all] but it says everything is already downloaded.
But besides the warning it is now finding what show I am watching, granted I've only tried a few shows so far but they are all saying
 Failed to find ratingkey 16975 in the db
All different rating key numbers but they all fail. and it doesn't skip any intro's or credits yet, so i'll keep at it trying to figure out what to do.

Try doing pip install -U bw_plex[all]
Some of the optional package can be abit painfull to install so i have made something optional in order to make it simpler to test.
As for the message Failed to find ratingkey 16975 in the db that just to let you know that bw_plex has never seen that file before. And as a result it should start downloading and analyze that episode (and the next one) to figure out when the intro starts and ends. You just need to wait until the message Added showname sxx eyy to db. Then you can start playback on that item and see it it skips as it should.

I tried pip install -U bw_plex[all]
It didn't seem to download anything new for myself it's just saying Requirement not upgraded as not directly required
How long does it usually take to analyze and add a show? Because I've had it running for over a day now and it hasn't said anything besides Failed to find ratingkey 16975 in the db on any episode I start watching.
Thanks for the help so far, I appreciate it.

That depends on how big the file we analyze what what you want to analyze, when i do it on my i7, it usually takes like 2-4 minutes for each item.
Try hitting control c one time and see if you you get some traceback or something. if you do please post it.
You should see stuff in the console, like:
2018-05-24 22:47:30,194 :: bw_plex :: DEBUG :: Failed to find ratingkey 34402 in the db
2018-05-24 22:47:30,394 :: bw_plex :: DEBUG :: Download the first 10 minutes of The.Arrangement.(2017).s02e04 as .wav
2018-05-24 22:47:30,410 :: bw_plex :: DEBUG :: Checking if we can reach The.Arrangement.(2017).s02e04 directly
2018-05-24 22:47:30,442 :: bw_plex :: WARNING :: Downloading from pms..
2018-05-24 22:47:30,486 :: bw_plex :: DEBUG :: calling ffmpeg with ffmpeg -i http://<IP_ADDRESS>:32400/library/parts/42120/1522657929/file.mkv?download=1&X-Plex-Token=<TOKEN>-ac 1 -ar 11025 -ss 0 -t 600 -acodec pcm_s16le C:\Users\alexa\AppData\Local\Temp\offset_07byy7ao.wav
....
....

I have an I7 as well, and I checked ffmpeg on my cmd.exe and it's working as well.
I kept it running all weekend hoping it would maybe start working. But it's just the same.
2018-05-25 16:18:55,805 :: bw_plex :: DEBUG :: Failed to find ratingkey 6522 in the db
2018-05-25 16:18:55,831 :: bw_plex :: DEBUG :: Download the first 10 minutes of Archer.(2009).s06e05 as .wav
2018-05-25 16:18:55,832 :: bw_plex :: DEBUG :: Checking if we can reach Archer.(2009).s06e05 directly
2018-05-25 16:18:55,832 :: bw_plex :: DEBUG :: Found E:\Plex Video Files\movies_tv\tv\Archer (2009)\Season 06\Archer (2009) - S06E05 - Vision Quest HDTV-1080p.m4v

Eventually near the end it just stopped even trying. Just outputting this without even trying to download the first 10 minutes.
2018-05-25 21:23:15,437 :: bw_plex :: DEBUG :: Failed to find ratingkey 21514 in the db
2018-05-27 20:19:02,871 :: bw_plex :: DEBUG :: Failed to find ratingkey 21499 in the db

Not really sure what else to do.

Can you post the entire log to a gist? remember to remove any plex-api token.

Sure. - https://gist.github.com/notnicecream/749ae396723234843d4142dcd0137cd6

Thanks, so it reaches process_to_db then "nothing happens" so, can you try to run
bw_plex process -n Archer
select the archer using the number press enter then select the first episode and see what happens (remove the log, the hashes file and media.db first) then post the log again.

ok, here's the gist file of what happened. https://gist.github.com/notnicecream/7db906d207770e47a3c22e16332737cb

Ok, i have no idea why that happend.
Are you using the version on pypi or from github? If its not from github
pip uninstall bw_plex
git clone https://github.com/Hellowlol/bw_plex.git
enter the folder
python setup.py install -e . (note the dot)
cd into the bw_plex subfolder then do python plex.py process -n Acher

Your my hero, thanks :)

Here's my most recent gist :) https://gist.github.com/notnicecream/e76bdb3bb0497f10aac9e19aab956bf8
I have no problem testing stuff, I just don't have much if at all experience with python so I'm winging it.

Sorry, it was pip install -e . Not python setup.py -e . Sorry my bad.

mmk, newest gist - https://gist.github.com/notnicecream/f6205ac327d1f5f865ea0aafa002332e

Only thing i can think if is a ffmeg error. Can you try to execute:
/6488/theme/1527137051?X-Plex-Token=<YOUR TOKEN HEREE> -ac 1 -ar 11025 -acodec pcm_s16le archer.wav``` and see what it returns/does ? If this doesnt work ill have to create a new branch with additional logging.

Looks like that did something. here - https://gist.github.com/notnicecream/5fcfc63a6defac7a9410e174810b9845

latest gist - https://gist.github.com/notnicecream/8f509f634d8cdd102e60408289032ca4

I got that exact same error earlier today. TypeError: unsupported operand type(s) for -: 'str' and 'int'
The only thing that helped was removing my entire .config/bw_plex folder and then running plex.py again to let it create everything in a fresh folder.
Deleting just logs, hashes and media.db resulted in the same error, I had to remove config.ini, temp_themes and themes aswell.
Just backup the config.ini and restore it later. Might be a fluke in my case, but maybe it needs to create a new config after install or something?

I have forced that value to int now. Dunno why it happened

The version your using dont have addition logging, there is also a bug where that make this uncompat with python 2 (what your using.)
To fix this your need to update the package from github. Delete log, hashes.pklz and the db (there was some db changes) and do:
git pull

Ionno, I've reinstalled everything again.
Here's the Gist - https://gist.github.com/notnicecream/e81817938b938ff2f167e459bfde41e7

Nothing usefull in the log. Okei i have created a new branch where we dont to any threading, this should show the entire traceback. Since you have installed from source you should be able to just use git.
git pull
git checkout ffs
cd bw_plex
python plex.py test_show archer -s 6 -e 1

Docker support was just added. :)

The only time I have encountered a quick exit is if there is a hashes.plkz file but it’s like 1 kB. Try the docker

I tried it again. removed everything started from scratch, getting these errors when I run bw_plex watch.
https://gist.github.com/notnicecream/a3c89274d20dfa7792b604a0c7ba9d82


Creative Theme

Sorry i am pretty new to rail.
I've followed the instructions in the read.md but the creatives theme is installed but not displayed.
If you can give me some hints. Thanks
that's my system:
Rails version	4.2.5
Ruby version	2.2.3-p173 (x86_64-darwin15)
RubyGems version	<IP_ADDRESS>
Rack version	1.6.4
JavaScript Runtime	JavaScriptCore
Middleware
Rack::Sendfile
ActionDispatch::Static
Rack::Lock
#ActiveSupport::Cache::Strategy::LocalCache::Middleware:0x007fa48a415088
Rack::Runtime
Rack::MethodOverride
ActionDispatch::RequestId
RequestStore::Middleware
Rails::Rack::Logger
ActionDispatch::ShowExceptions
WebConsole::Middleware
ActionDispatch::DebugExceptions
ActionDispatch::RemoteIp
ActionDispatch::Reloader
ActionDispatch::Callbacks
ActiveRecord::Migration::CheckPending
ActiveRecord::ConnectionAdapters::ConnectionManagement
ActiveRecord::QueryCache
ActionDispatch::Cookies
ActionDispatch::Session::CookieStore
ActionDispatch::Flash
ActionDispatch::ParamsParser
Rack::Head
Rack::ConditionalGet
Rack::ETag

Thanks for the comment :smile:
Did you go to localhost:3000/creatives/index?  What was the error message you got?  Thanks!

No error: there the Theme is up :)

i think the issue is in route.rb but i followed your explanation and i pasted the get 'creatives/index'
I am also running a CMS: Casein and there is already a generated code for it in the route.rb

It sounds like everything is working properly :)
Thanks!


Ensure Swift track is ready for v2 launch

There are a number of things we're going to want to check before the v2 site goes live. There are notes below that flesh out all the checklist items.

[ ] The track has a page on the v2 site: https://v2.exercism.io/tracks/swift
[ ] The track page has a short description under the name (not starting with TODO)
[ ] The "About" section is a friendly, colloquial, compelling introduction
[ ] The "About" section follows the formatting guidelines
[ ] The code example gives a good taste of the language and fits within the boundaries of the background image
[ ] There are exercises marked as core
[ ] Exercises have rough estimates of difficulty
[ ] Exercises have topics associated with them
[ ] The first exercise is auto_approve: true

Track landing page
The v2 site has a landing page for each track, which should make people want to join it. If the track page is missing, ping @kytrinyx to get it added.
Blurb
If the header of the page starts with TODO, then submit a pull request to https://github.com/exercism/swift/blob/master/config.json with a blurb key.  Remember to get configlet and run configlet fmt . from the root of the track before submitting.
About section
If the "About" section feels a bit dry, then submit a pull request to https://github.com/exercism/swift/blob/master/docs/ABOUT.md with suggested tweaks.
Formatting guidelines
In order to work well with the design of the new site, we're restricting the formatting of the ABOUT.md. It can use:

Bold
Italics
Links
Bullet lists
Number lists

Additionally:

Each sentence should be on its own line
Paragraphs should be separated by an empty line
Explicit <br/> can be used to split a paragraph into lines without spacing between them, however this is discouraged.

Code example
If the code example is too short or too wide or too long or too uninteresting, submit a pull request to https://github.com/exercism/ocaml/blob/master/docs/SNIPPET.txt with a suggested replacement.
Exercise metadata
Where the v1 site has a long, linear list of exercises, the v2 site has organized exercises into a small set of required exercises ("core").
If you update the track config, remember to get configlet and run configlet fmt . from the root of the track before submitting.
Topic and difficulty
Core exercises unlock optional additional exercises, which can be filtered by topic an difficulty, however that will only work if we add topics and difficulties to the exercises in the track config, which is in https://github.com/exercism/swift/blob/master/config.json
Auto-approval
We've currently made any hello-world exercises auto-approved in the backend of v2. This means that you don't need mentor approval in order to move forward when you've completed that exercise.
Not all tracks have a hello-world, and some tracks might want to auto approve other (or additional) exercises.
Track mentors
There are no bullet points for this one :)
As we move towards the launch of the new version of Exercism we are going to be ramping up on actively recruiting people to help provide feedback. Our goal is to get to 100%: everyone who submits a solution and wants feedback should get feedback. Good feedback.
If you're interested in helping mentor the track, check out http://mentoring.exercism.io/

When all of the boxes are ticked off, please close the issue.
Tracking progress in https://github.com/exercism/meta/issues/104

Things which can already be checked off:

The track has a page on the v2 site: https://v2.exercism.io/tracks/swift
Exercises have rough estimates of difficulty
Exercises have topics associated with them
The first exercise is auto_approve: true

Things which need to be completed:

Add a blurb to config.json
Update the about section to be friendly, colloquial, compelling introduction, and follow the formatting guidelines
Update the code snippet to fit within the box (10 lines with up to 42 characters each)
Set ~8 exercises as core, and add unlocked_by to non-core exercises


docs(samples): Adding code samples for log reading

Preparing code samples for this page.

@kurtisvg I applied some of your comments and suggestions. I kept the log retrieving as 2 separate function for easy testing and so that people can easily copy the log retrieving part for their code. Please let me know if you can accept this division.


New event endpoint

Payload change

Event Builder Test Cases modified and added for new payload

Test cases modified for uuid

Added assertion failure messages

I would like this pull request to also delete these OPTLYEventParameterKeys.m+.h symbols:
* "OPTLYEventParameterKeysActivationId"
* "OPTLYEventParameterKeysUserFeatures"
* "OPTLYEventParameterKeysIsGlobalHoldback"
* "OPTLYEventParameterKeysMetricName"
According to the Avro *.avsc specification I've seen, these aren't used.
According to the Objective-C code I've seen, these aren't used in any significant way
in code.

ADDITIONAL ITEMS IN OPTLYEventParameterKeys.m+.h THAT SHOULD BE REMOVED
Purpose of the P.R. is reorg of the JSON event information sent to new V3 endpoint including event batching, drift towards snake_case keys away from camelCase keys, and some moves described in JIRA OASIS-1867 .  Granting this, there should be no vestiges of "eventEntityId", "eventName", nor "eventFeatures" left around in the objective-c-sdk code, but there are still such vestiges.
We believe these items in OPTLYEventParameterKeys.m+.h should be removed:
{code:title=Objective-C|borderStyle=solid}
NSString * const OPTLYEventParameterKeysEventEntityId                   = @"eventEntityId";
NSString * const OPTLYEventParameterKeysEventType                       = @"eventType";
NSString * const OPTLYEventParameterKeysEventName                       = @"eventName";
NSString * const OPTLYEventParameterKeysEventFeatures                   = @"eventFeatures";     // nonnull
NSString * const OPTLYEventParameterKeysEventMetrics                    = @"eventMetrics";      // nonnull
NSString * const OPTLYEventParameterKeysRelatedEvents                   = @"relatedEvents";
NSString * const OPTLYEventParameterKeysLayerStates                     = @"layerStates";       // nonnull
NSString * const OPTLYEventParameterKeysActiveViews                     = @"activeViews";
NSString * const OPTLYEventParameterKeysRelatedEventsEventId            = @"eventId";
NSString * const OPTLYEventParameterKeysRelatedEventsRelationship       = @"relationship";
{code}

REGARDING @"eventId" CLEANUP
The fate of @"eventId" is a bit more complicated.  However, if we
search the "reference" python-sdk for either of "eventId" or "event_id", we don't find these.
Instead, we find "entity_id" in python-sdk's optimizely/event_builder.py
   EVENT_ID = 'entity_id'

All unreferenced items of OPTLYEventParameterKeys.m+.h has beed removed and reordered them to their respective object.

REMAINING OCCURRENCES OF LITERAL STRINGS @"eventEntityId" ETC. SHOULD BE GONE TOO
Most of the literal string offenders are in OptimizelySDKShared/OptimizelySDKSharedTests/OPTLYDataStoreTest.m .
These grep commands in the source code directory should be producing empty output:
grep -r \"eventEntityId\" .
grep -r \"eventName\" .
grep -r \"eventFeatures\" .
grep -r \"eventMetrics\" .
grep -r \"layerStates\" .

Footnote to the above: Mixpanel code is third party, is fine, and don't change it
when addressing @"eventName" .  At first glance, the keyMapper code in
OptimizelySDKCore/OptimizelySDKCore/OPTLYEvent.m might appear suspect,
but actually it is fine, and we don't want to change this code either.

TEST:

sh ./Scripts/build_all.sh PASSED
sh ./Scripts/local_travis.sh PASSED
2 iOS & 2 tvOS Clean / Build / Analyze PASSED
8 iOS test suites PASSED
OptimizelySDKiOSUniversalTests PASSED
6 tvOS test suites PASSED but 1 tvOS test suite FAILED

(void)testTVOSSDKInitializedWithOverrides

OptimizelySDKTVOSUniversalTests PASSED
iOS & tvOS DemoApp's PASSED

The one test failure in OptimizelySDKTVOSTests "- (void)testTVOSSDKInitializedWithOverrides"
looks rather minor, is not due to P.R. #202, and I or someone else will see to getting that
test to pass in some future P.R.  There is a similar at risk test in OptimizelySDKiOSTests.m which is just getting lucky up to now.
CONCLUDE: We're going to APPROVE the P.R. #202 .

This was OASIS-1867 .


Bug with TapCallbacks & camera.zoom or camera.flow

when i use both TapCallbacks and camera.zoom or camera.flow , containsLocalPoint always give me the wrong point ,
easy test
'/flame/examples/lib/stories/input/tap_callbacks_example.dart'
`
@override
Future onLoad() async {
add(TappableSquare()..anchor = Anchor.center);
add(TappableSquare()..y = 350);
// add this
camera.zoom = 0.5;

}
`

I would recommend using the CameraComponent if you are using TapCallbacks, I'm not sure that the TapCallbacks fully take the old camera into consideration. If you don't want to use the CameraComponent another workaround could be to use Tappable instead of TapCallbacks.
https://docs.flame-engine.org/1.7.0/flame/camera_component.html

I don't think that would work for nested components.

have some issue.

i just wont override some getter in TapCallbacks mixin, like
set positionType (PositionType value)=>
and choose, my component can be moved/scaled and i need to calculate its position by local or global

I don't think that would work for nested components.

Yes, I agree. Nested components may need to traverse up to each parent until the root parent, and then calculate accordingly.

I don't know if it will be for the same reason or not, but I have noticed that when I apply "TapCallbacks" to a "PositionComponent" it works perfectly but if it is a "BodyComponent" it seems to completely ignore the tap.

but if it is a "BodyComponent" it seems to completely ignore the tap.

Unfortunately gestures combined with the CameraComponent isn't fully fixed in flame_forge2d yet, but I have an ongoing branch for it which I will finish up once Flutter & Friends is over.


After Update i get Couldn't build model xxxxxxxxxxxx.bin : 'gpu_layers'

Expected Behavior
Loading of model ....
Current Behavior
When i try to start it i get the following Error-Message:
******************* Building Binding from generation Process *************************
Loading binding c_transformers install ON
Binding loaded successfully
Loading model : d:\dalai\lollmsdata\models\c_transformers\starchat-beta.ggmlv3.q4_1.bin
Couldn't build model starchat-beta.ggmlv3.q4_1.bin : 'gpu_layers'
Context
Its the current windows version, worked last friday and stopped today after updating,

Sorry, it is a new field added to configuration file. Either add an entry to your configuration file gpu_layers:20 (for example) or remove the configuration file and it will be regenerated.
If you chose the default installation path it should be on your home/Documents/lollms/configs.


runtime: segmentation fault on linux/amd64

There's been a slew of segmentation fault (core dumped) failures (without additional context) on various linux/amd64 builders as of 961aab2 (AFAICT).
2021-11-04T21:52:51-1e0c3b2/linux-amd64
2021-11-04T21:52:51-1e0c3b2/linux-amd64-bullseye
2021-11-04T21:52:36-8ad0a7e/linux-amd64
2021-11-04T21:52:36-8ad0a7e/linux-amd64-fedora
2021-11-04T21:52:36-8ad0a7e/linux-amd64-staticlockranking
2021-11-04T21:52:06-37634ee/linux-amd64-fedora
2021-11-04T21:33:23-71fc881/linux-amd64-unified
2021-11-04T20:01:10-9b2dd1f/linux-amd64-sid
2021-11-04T20:00:54-961aab2/linux-amd64-unified
Notably, the failure always seems to pop up in the same place in the runtime tests (around 5.2 to 5.5 seconds), probably because it's the same single test failing. I've been unable to reproduce it on my VM, or on the gomotes, despite many all.bash runs.
My guess is that this is another failure related to a bad test that previously never had a GC run during the test, but now because of 961aab2 and the smaller minimum heap size, does (I have fixed 4 failures like this so far; it's not proof, but it does appear to be part of the pattern).

I'm trying to reproduce this with 10 gomotes, ignoring other flakes and failures on the dashboard. I upgraded my tooling for this so I should be able to run it indefinitely and get back a core file when it does actually fail.

I reproduced it but failed to produce a core.

Reproduced again, no core file. Trying a different strategy to try to get the core file to be produced...

Great news! I have cores. The problem is I have 97 of them, but all of them are indeed from this test run. So one of them should capture the failure. In theory.

OK, that was easier than I thought. Backtrace:
#0  runtime.gcWriteBarrier ()
    at /usr/local/google/home/mknyszek/tmp/dlgo-linux-amd64/go/src/runtime/asm_amd64.s:1622
#1  0x00000000004726e7 in runtime.gcWriteBarrierCX ()
    at /usr/local/google/home/mknyszek/tmp/dlgo-linux-amd64/go/src/runtime/asm_amd64.s:1697
#2  0x00000000004679d4 in runtime.(*debugCallHandler).inject (h=0x657350, info=0xc000115bf0,
    ctxt=<optimized out>, gp2=<optimized out>)
    at /usr/local/google/home/mknyszek/tmp/dlgo-linux-amd64/go/src/runtime/export_debug_test.go:133
#3  0x0000000000475172 in runtime.(*debugCallHandler).inject-fm ()
    at /usr/local/google/home/mknyszek/tmp/dlgo-linux-amd64/go/src/runtime/export_debug_test.go:109
#4  0x000000000044fdc4 in runtime.sighandler (sig=5, info=<optimized out>, ctxt=<optimized out>,
    gp=0xc0000f8048) at /usr/local/google/home/mknyszek/tmp/dlgo-linux-amd64/go/src/runtime/signal_unix.go:606
#5  0x000000000044f8e5 in runtime.sigtrampgo (sig=5, info=0xc000115bf0, ctx=0xc000115ac0)
    at /usr/local/google/home/mknyszek/tmp/dlgo-linux-amd64/go/src/runtime/signal_unix.go:465
#6  0x0000000000474d8e in runtime.sigtrampgo (sig=5, info=0xc000115bf0, ctx=0xc000115ac0) at <autogenerated>:1
#7  0x00000000004741dd in runtime.sigtramp ()
    at /usr/local/google/home/mknyszek/tmp/dlgo-linux-amd64/go/src/runtime/sys_linux_amd64.s:361

Sadly, this is something I'm aware of. The debug call injection tests are riddled with write barriers that are not safe to execute. The quick fix here is to disable the GC for these tests. Notably some of these tests call runtime.GC in the call injection handler -- that's totally fine, the issue is if a GC is currently executing while the handler is running.
Note also that this is a test-only failure. Real-world implementations of the debug call protocol (like in delve) don't have this problem, because the handler is implemented in another process. In the past I made an effort to remove these write barriers, but it's surprisingly difficult. There are a lot of them, and arranging for something different for all of them would be a pain.
I propose disabling the GOGC-based GC during the test to unblock the longtest builder, and then taking some time later to rewrite this entire handler to be careful not to use write barriers (and to be annotated with go:nowritebarrierrec). Another useful note: in theory the handler should already have had write barriers turned off! It's called from a signal handler. Unfortunately it's called indirectly, so the static analysis that enforces this fails.

CC @prattmic who I discussed this with in the past.

In investigating the root causes for #49680, #49695, and #45867, I discovered that the logic behind the fix here was erroneous. In fact, I suspect that the cause of these failures was that just one of the tests was missing a call to SetGCPercent(-1) and that the additional runtime.GC calls are actually pointless. I'm not going to pull them out for 1.18 because that risks introducing flaky tests, but I sent a CL that leaves TODOs to remove them.


Update scalaz-concurrent, scalaz-iteratee to 7.2.27

Updates

org.scalaz:scalaz-concurrent
org.scalaz:scalaz-iteratee

from 7.2.26 to 7.2.27.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a nice day!

Codecov Report

Merging #251 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #251   +/-   ##
======================================
  Coverage    97.2%   97.2%
======================================
  Files          23      23
  Lines         786     786
  Branches       58      58
======================================
  Hits          764     764
  Misses         22      22

Continue to review full report at Codecov.

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


Missing word 'veriest'

Veriest (𐑝𐑧𐑮𐑾𐑕𐑑) - used to emphasize the degree to which a description applies to someone or something.

As mwgamera suggests,  𐑝𐑧𐑮𐑦𐑩𐑕𐑑 would be a better spelling, consistent with other Readlex entries.

Added, thanks.


Efficiency per outside temperature & updates

Is your feature request related to a problem? Please describe.
Feature requests:
Two Grafana feature requests - previous version next to updated version on the ‘Updates’ dashboard
Outside temperature efficiency table (per 10°) similar to that of TeslaFi (never personally used, only seen the table).
Describe the solution you'd like
See above. Believe the previous version is easy. Really not sure how easy the per 10° table is. Also considering my efficiency ratings do not come in, I cannot be much help in testing. Hopefully Tesla can resolve (see #125). Opened correspondence with Tesla.
Describe alternatives you've considered
None. New feature.

I'm confused, it seems like it currently has the efficiency vs outside temperature there.

Also seems to have the update versions next to each other.
Am I missing something?

I'm confused, it seems like it currently has the efficiency vs outside temperature there.

Also seems to have the update versions next to each other.
Am I missing something?

 Thanks a ton for the screenshots. I am happy to see both are built in! As mentioned, my efficiency dashboard (among others) does not work nor does it display any data. I still think this is related to the 999 API value that my car is reporting.

Ah! Gotcha, unfortunately, I have not a clue when it comes to elixir, so I can't help you much there. Hopefully Adrian chimes in. Best of luck!

@adriankumpf so heard back from Tesla - they claim (and this is a direct copy and paste):

We have checked all relevant values and verified they are reporting correctly. I highly recommend against the use of any third party scripts/software/hardware as any issues arising from them will not be covered under warranty. If you have an issue that affects the normal use of the vehicle, we would be happy to look into it. Thank you.

Obliviously, I am not concerned about TeslaMate breaking my car. However, I am curious about your thoughts around the "ideal_battery_range" reading 999. Is this messing with my dashboards? Are the Grafana dashboards configured to use this value to calculate some of the efficiencies? I feel like I know the answer to that is a yes, but just trying to brainstorm a solution.

Adrian, the efficiency calculations still seem to be off and driving an unrealistic range on my car both for charging reports as well as Degradation display.  Specifically, efficiency page says the car is using a .189 efficiency factor but the derived efficiency factors are .142, .134 and .129.  I think that this is still related to the Model S 90D sending the MDL3 code and, while now correctly identified as a Model S, the grafana tables are treating the car as a Model 3.
Any ideas of a fix?  Possibly going in and manually overriding the database in some way?  I'm familiar with SQL tables (MYSQL) but have never used Grafana and am not sure of the way to interact with/change the Postgres database.  I'm open to ideas but suspect this is why many of us are seeing incorrect ranges displayed in some of the grafana pages.

@drklain, it's correctly identified as Model S 90D if it says so on the web interface below the car's name. II don't have the time to go into it in detail right now. To state the Changelog:

Display the default and derived efficiency factor on the Efficiency dashboard to detect inaccuracies and to crowdsource the correct factors:

Note: If there is no default efficiency factor or you think the default factor for your vehicle might be wrong, please open an issue and attach a screenshot of the table showing the efficiency factor(s) for your vehicle.

@drklain what value are you seeing in some of your dashboards? Not sure how connected our issues might be, but for example on the degradation page I see 1000+ projected miles.

I see a 348 mile projected range.  I think the question is the efficiency factor.    I believe the problem is related to Teslas change in codes where some Model S 90Ds are now reporting a MDL3 code and being treated as Model 3s.  Have you pulled your option codes to see what your car is reporting?  It's possible it is being mis-identified or put in a null-value state...

I see a 348 mile projected range. I think the question is the efficiency factor.  I believe the problem is related to Teslas change in codes where some Model S 90Ds are now reporting a MDL3 code and being treated as Model 3s. Have you pulled your option codes to see what your car is reporting? It's possible it is being mis-identified or put in a null-value state...

I did here https://github.com/adriankumpf/teslamate/issues/123#issuecomment-526357955

Not to throw this off further, but here are my codes:
"AD15,MDL3,PBSB,RENA,BT37,ID3W,RF3G,S3PB,DRLH,DV2W,W39B,APF0,COUS,BC3B,CH07,PC30,FC3P,FG31,GLFR,HL31,HM31,IL31,LTPB,MR31,FM3B,RS3H,SA3P,STCP,SC04,SU3C,T3CA,TW00,TM00,UT3P,WR00,AU3P,APH3,AF00,ZCST,MI00,CDM0"
I own: 2019 (Raven) Model S, black exterior, white interior, 19" carbon slipstream, non-performance
It is definitely not a Model 3 (MDL3), it has more than 75 kWh (BT37), it does not have the Model 3 wood decor (ID3W), does not have the Model 3 glass roof (RF3G) - although, they could go to a single code for the glass roof, it is not RWD (DV2W), I hope it is better than AP firmware 2.0 (APF0) and actually AP HW3 which apparently has a code but seems I have hardware 2.5 (APH3), claims I have the Model 3 48amp charger (CH07), no HEPA filter (AF00).
Yes. I went through all my codes. ¯_(ツ)_/¯

Referenced against https://tesla-api.timdorr.com/vehicle/optioncodes

Yep, it looks like you are also a victim of the option code fiasco…ugh.
From: cwanja<EMAIL_ADDRESS>Reply-To: adriankumpf/teslamate<EMAIL_ADDRESS>Date: Friday, September 6, 2019 at 9:55 AM
To: adriankumpf/teslamate<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [adriankumpf/teslamate] Efficiency per outside temperature & updates (#143)
I see a 348 mile projected range. I think the question is the efficiency factor.  I believe the problem is related to Teslas change in codes where some Model S 90Ds are now reporting a MDL3 code and being treated as Model 3s. Have you pulled your option codes to see what your car is reporting? It's possible it is being mis-identified or put in a null-value state...
I did here #123 (comment)
Not to throw this off further, but here are my codes:
"AD15,MDL3,PBSB,RENA,BT37,ID3W,RF3G,S3PB,DRLH,DV2W,W39B,APF0,COUS,BC3B,CH07,PC30,FC3P,FG31,GLFR,HL31,HM31,IL31,LTPB,MR31,FM3B,RS3H,SA3P,STCP,SC04,SU3C,T3CA,TW00,TM00,UT3P,WR00,AU3P,APH3,AF00,ZCST,MI00,CDM0"
I own: 2019 (Raven) Model S, black exterior, white interior, 19" carbon slipstream, non-performance
It is definitely not a Model 3 (MDL3), it has more than 75 kWh (BT37), it does not have the Model 3 wood decor (ID3W), does not have the Model 3 glass roof (RF3G) - although, they could go to a single code for the glass roof, it is not RWD (DV2W), I hope it is better than AP firmware 2.0 (APF0) and actually AP HW3 which apparently has a code but seems I have hardware 2.5 (APH3), claims I have the Model 3 48amp charger (CH07), no HEPA filter (AF00).
Yes. I went through all my codes. ¯_(ツ)_/¯
Referenced against https://tesla-api.timdorr.com/vehicle/optioncodes
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Obliviously, I am not concerned about TeslaMate breaking my car. However, I am curious about your thoughts around the "ideal_battery_range" reading 999. Is this messing with my dashboards? Are the Grafana dashboards configured to use this value to calculate some of the efficiencies? I feel like I know the answer to that is a yes, but just trying to brainstorm a solution.
I asked Tesla to go "on the record" (with a screenshot I provided, via a Terminal window with the API call) that the returned value is "reporting correct". See what they come back with. For some reason, I find that not to be the case.

Yes, it is related to the invalid ideal_battery_range reading as you suspected @cwanja. The ideal range is used to calculate the projected range and efficiency, for example.
I'm not surprised that Tesla doesn't see any problem and they're kind of rightsince the bad reading does not "affect the normal use of the vehicle".
In the medium term, it will be possible to switch from ideal to rated range within TeslaMate. The rated range is already recorded. That means you won't lose any data until then.

Thanks for the response @adriankumpf - I saw that in your comment in another thread. Yea, I see how it is not affecting the vehicle, but it kind of surprises me that they have no desire to investigate to figure out why it is reporting that. Much less the other API values I provided to them.
Look forward to being able to toggle the rate in a future update of TeslaMate. Appreciate all your support, feedback and updates!


Adding files for rdf calculations

Added CMakelist, mc_demo.cpp, mcrun.py python_mc.py

Hello, I think something went wrong with your merging/rebasing. Can you please give me access to your branch settings -> collaborators so that I can fix this?

https://github.com/dibyendu92/SSS_2017_QuESt/invitations
Please accept the invitations.
Dibyendu
On Mon, Aug 7, 2017 at 6:50 AM, Daniel Smith<EMAIL_ADDRESS>wrote:

Hello, I think something went wrong with your merging/rebasing. Can you
please give me access to your branch settings -> collaborators so that I
can fix this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_MolSSI-2DSSS_SSS-5F2017-5FQuESt_pull_28-23issuecomment-2D320668999&d=DwMCaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=wVKT8AKXoca3C-qZQ1mM3A&m=W_B_Wp-Adp5_H8wpudhmStPS0poVYv9yXgQvOjMls4c&s=qS1jazOCtFY1cXzfQsIjGifLOkBXqustIN4rMbtNyik&e=,
or mute the thread
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AczenlbP3WDuBZFAG7gzvMGgDfPsfE0Qks5sVxY1gaJpZM4OrinG&d=DwMCaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=wVKT8AKXoca3C-qZQ1mM3A&m=W_B_Wp-Adp5_H8wpudhmStPS0poVYv9yXgQvOjMls4c&s=RAKBXJP7gDS_-ulq9S043Q51ASyhqHkYU0iPQ9EaXlA&e=
.

--
Dibyendu Mondal
Graduate student
Department of Chemistry
University of Southern California, USA

I have merged in your changes, please see issue #58.


[WIP] feat(ui): implement new channel header

Description:
Implement new channel header
Motivation and Context:
Fix #2332
How Has This Been Tested?
Manually
Types of changes:
UI enhancement
Checklist:

[ ] My code follows the code style of this project.
[ ] I have reviewed and updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[ ] My commits have been squashed into a concise set of changes.

Nice @mrfelton!
Few comments:
I feel like the header is too close to the 3 Window buttons in the top left and adding some top padding would be good. Thoughts?
The refresh icon is thicker and not the icon that is in Zeplin. We also should maybe change the icon in the Activity search header thing if we are going to change it here? (For the record, I like the thinner refresh button)

Is the order arrow icon separated from the other icons on purpose? If so, I wonder what everyone thinks about that. Grouping all the icons would probably be cleaner in my opinion
Lastly, we discussed in Slack the need to create space between the subheader/channel cards and the search bar thingy. Do we still want to do that? I think so personally

Coverage decreased (-0.02%) to 20.323% when pulling 04d3e98f28f7a5f775b1060ac27f2215d7e272e3 on mrfelton:feat/2332-new-chnanel-header into 9f10632f57ec7ab4428d3ca8bd47d64edb7698c0 on LN-Zap:next.


Assign "party_id" to records in Candidacy OCD model

Done.

Excellent!
On Mon, May 8, 2017 at 8:28 AM James Gordon<EMAIL_ADDRESS>wrote:

Done.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/california-civic-data-coalition/django-calaccess-processed-data/issues/67#issuecomment-299900334,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAnCX4mJnmhTuFZljA_EjIOxNCP-ZL8ks5r3zSDgaJpZM4M6Vwd
.


Changed BodyStream parameter in upload functions from pointer to refe…

Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[x] C++ Guidelines
[x] Doxygen docs
[x] Unit tests
[x] No unwanted commits/changes
[x] Descriptive title/description

[x] PR is single purpose
[x] Related issue listed

[x] Comments in source
[x] No typos
[x] Update changelog
[x] Not work-in-progress
[x] External references or docs updated
[x] Self review of PR done
[x] Any breaking changes?

/azp run cpp - storage

What about some of these static methods in blob_rest_client.hpp (found 5 places). Everything else looks to be fixed:
https://github.com/Azure/azure-sdk-for-cpp/blob/1b316d3b44f8c38c3de80b2115f2050496d646d0/sdk/storage/azure-storage-blobs/inc/azure/storage/blobs/protocol/blob_rest_client.hpp#L6693-L6696


BAEL-[8622] Round Robin and AtomicInteger in Java

This PR contains files related to BAEL-[8622] Round Robin and AtomicInteger in Java.

retest this please

comment to reopen the pr.

retest this please

retest this please

Comment to retest

retest this please


Try catch in main for handling timeout failure

Yes. Log the errors and continue. No attempt to recover that iteration, just keep going.
This only handles the 10 minute ones, maybe not the deposit initiated ones. Could do that too


SNOW-1170171: snow procedure init overwrites files without warning

SnowCLI version
SnowCLI Version: 0.2.5
Python version
Python 3.11.6
Platform
macOS-14.3.1-arm64-arm-64bit
What happened
I ran snow procedure init in my cwd while I was working on a project, and thought it would create a subdir in my current directory, but it overwrote my requirements.txt
Console output
-

How to reproduce
No response

Would suggest we warn before overwriting.

I installed 2.1.0rc0 and this behavior persists, but also it seems to create an app.toml instead of the new yaml format.

My mistake. An older version of snowcli was on my path. The latest release is actually showing no such command 'procedure'

Found latest version of the command, and it creates a new dir:
(venv) (base) ➜  gdocs-import git:(main) ✗ snow snowpark init
Initialized the new project in example_snowpark/

Will close this out as resolved, thanks!


Select default return code automatically

説明 / Description
usi-csa-bridge の --return-code オプションのデフォルト値を OS に応じて自動的に選択します。
チェックリスト / Checklist

MUST

[x] npm test passed
[x] npm run lint was applied without warnings
[x] changes of /docs/webapp not included (except release branch)
[x] console.log not included (except script file)

MUST (for Outside Contributor)

[ ] understand プロジェクトへの関わり方について

RECOMMENDED (it depends on what you change)

[ ] unit test added/updated
[ ] i18n

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 73.89%. Comparing base (75aebea) to head (72e1e8a).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #775   +/-   ##
=======================================
  Coverage   73.89%   73.89%
=======================================
  Files          87       87
  Lines       12476    12476
  Branches     1719     1719
=======================================
  Hits         9219     9219
  Misses       3234     3234
  Partials       23       23

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add function to pause computations

fixed in https://github.com/steren/webgl-path-tracing/commit/23c3ff36600659cabdc3d79cfcd284136b668382


Challenge 25: Contradictory instructions

You are required to write code below where it says, // change code above this line.

got it!

These comments are written in JS style instead of JSX style.

You're right about that, I've just updated it locally here. Thanks!


Mounting a volume with a rancher/lb-service-haproxy

I'd like to add a custom HAPROXY configuration acl whitelist that reads the whitelisted IP's from a file.
e.g. acl white_list src -f /var/files/ip-whitelist, tcp-request inspect-delay 2s, tcp-request content accept if white_list,  tcp-request content reject
We had this configuration with standard docker but I can't see how to mount a volume with rancher/lb-service-haproxy as that tab isn't available in the load balancer UI
Any suggestions as to how I can do this, or would this be a new feature for rancher/lb-service-haproxy?

I'm interested in this. I'm trying to redesign the rancher/lb-service-haproxy just so I can mount a volume.
Use case: My certificates are maintained by an external service and dropped onto an NFS volume.

If it's interesting to anyone, here are the changes that I think would most improve the 1.6 lb-service-haproxy:
A self-signed default cert, so you can add https proxies without having a real cert specified.
A volume mount so you can add custom directives that require external files, such as (in my case) certificates which are externally maintained.
Periodic (configurable) -HUP signals, so that the proxy will occasionally perform a graceful restart and pay attention to any new files on the volume.


Suggestion - Workflow activity to delete record audit

When record auditing is enabled you can view the record audit and delete the audit history for that record.
A workflow activity to do this would be a great addition to the toolkit.

I didn't used it in the past...but maybe it can be done using this method: https://docs.microsoft.com/en-us/dotnet/api/microsoft.crm.sdk.messages.deleterecordchangehistoryrequest?view=dynamics-general-ce-9
to my backlog ;)
thanks

Is coming in the next <IP_ADDRESS> version. :)

Great news, thanks Demian.
Regards, Adam
Sent from my iPhone
On 18 Dec 2018, at 12:00, Demian Adolfo Raschkovan <notifications<EMAIL_ADDRESS>wrote:
Is coming in the next <IP_ADDRESS> version. :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdemianrasko%2FDynamics-365-Workflow-Tools%2Fissues%2F108%23issuecomment-448197121&data=02|01||1466b21c0f3547d3c81108d664e06152|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636807312192707839&sdata=FwI%2FdMZLT2T3oK7W663XNK9XVlprwRClKofz3lrL9%2F4%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAafCVfol4RbNYa_PnbfjhRI7x4wHOXAQks5u6NjSgaJpZM4Y2ZOt&data=02|01||1466b21c0f3547d3c81108d664e06152|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636807312192707839&sdata=neagU%2Ba%2FCX%2BxLW5IzBvAm7sw0TN371FUCoEMvHPb1lg%3D&reserved=0.