Card submission option

Would it be possible to add an option where the media sent has the form of a card?

Hey @tonizemani. I am not fully sure what you mean by card. Could you elaborate a little more on this. Thankyou!

Hey @tonizemani. I am not fully sure what you mean by card. Could you elaborate a little more on this. Thankyou!

Hello, a card is an HTML component commonly referred to a collection of a title, image and or description. Below are some examples https://developer.mozilla.org/en-US/docs/Web/CSS/Layout_cookbook/Card

To display HTML cards in messages, all you need to do is use the html message property.
Example (JavaScript):
chatElementRef.initialMessages = [
  {
    html: `

A short heading

 The idea of reaching the North Pole by means of balloons appears to have been entertained many years ago.

    `,
  },
];

To style it, you will need to use the htmlClassUtilities property.
Example (JavaScript):
chatElementRef.htmlClassUtilities = {
  'card-image': {
    styles: {
      default: {
        objectFit: 'cover',
        width: '100%',
        height: '100%',
      },
    },
  },
};

If you can't change the response messages in the server, you can use the responseInterceptor property to help you.
Having read your message, if you mean that you want to send a message that would be in a form of a card. The closest to that is the use of the submitUserMessage method. However there is no direct way to change the message bubble into a card when the user hits the submit button or clicks enter. If this is what you need then you will have to clone/fork the project and augment the code to suit your needs. This is simple to do by following these detailed instructions.
Let me know if this helps. Thanks!

Thank you for the response, also amazing work with the whole module!


always run the docs task on post-merge

Signed-off-by: Brent Baude<EMAIL_ADDRESS>

/lgtm

/hold

LGTM

/hold cancel


collaborative strategy: client mode

What does this PR do?
Hivemind features a client mode for cases where a computer that is not reachable by the peers in a collaborative run is not reachable from them (e.g. behind a NAT). This exposes the client mode flag to the strategy.
Does your PR introduce any breaking changes? If yes, please list them.
No.
I'm unsure how to test this properly.

@SeanNaren ^^ :rabbit:

@SeanNaren Could you review this PR?

I think it is still relevant, I'll fix it.

I update things and filed https://github.com/Lightning-AI/lightning/pull/13761 , so this is obsolete. Thanks again.


MsBuild verions supporting .editorconfig

[Enter feedback here]
I am trying to find what is the lowest version of MsBuild that supports .editorconfig files, yet I am struggling to find an answer. In my humble opinion it could be a valuable information that could be put on this page.
After a lot of digging it seems I found that they are supported from VS 2019 version 16.3, and it looks to me that at that time the latest MsBuild was v16.7. I am not sure that, this is the correct answer, but It would be really nice to find the answer and if you agree, put it in somewhere in the documentation.

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

ID: 72f45eb4-3596-866a-2c16-ee225737d956
Version Independent ID: cea055e7-fe9b-95c7-6d25-086f182c01d2
Content: EditorConfig settings - Visual Studio
Content Source: docs/ide/create-portable-custom-editor-options.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @mikadumont
Microsoft Alias: midumont

@csaba-sagi-sonarsource -- Čaba, thank you for your well-researched feedback.  Please consider these resources:

Visual Studio on Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit

@mikadumont -- Mika, please look into this potential documentation issue.


led_strip_wifi_ble_RGB only has Binary entity

I've set up the integration for my led_strip_wifi_ble_RGB and all is good, Colour picker and brightness levels all work as expected from HA in Lovelace.
However the only device entity I have is a binary state, device only shows one entity which is the on/off switch.
I would like to use HA Automations to adjust brightness and colour automatically...HA knows how to set this in the integration as the panel works in Lovelace...but without a set of entites for brightness and colour I can't do anything other than turn the light on or off with the automations.

Questions about entities can be fed back to HA’s official tuya integration. smartlife will not change the relevant entity codes for the time being.


Plugin is not enabled after server restart 1.16.3

lugin version: '5.12.38'
Server type: 'Paper-1.16.3-build204.'
Server version: '1.16.3'
Describe the bug
Plugin is not enabled after server restart
https://hasteb.in/joriqawe.swift
Expected behavior
Enabled plugin
To Reproduce
Install the plugin
Start the server
See error https://hasteb.in/joriqawe.swift

Fixed in 6.0.0

Fixed in 6.0.0


Trying to solve this error: TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'

Hi I've been trying for a few weeks now, but keep running into the error trace below.
I'm assuming there is some error in my config and that the files can't be read or passed. I get this error both for local files and for wikipedia. The Wikipedia thing creates a file, but can't create graph.

Same error is seen both locally and on google cloud.
Error persists in DEV branch.

Error Trace
backend   | 2024-06-11 02:34:33,314 - wikipedia query ids = ['dermatitis']
backend   | 2024-06-11 02:34:33,314 - Creating source node for dermatitis, en
backend   | 2024-06-11 02:34:36,003 - creating source node if does not exist
backend   | 2024-06-11 02:34:36,122 - closing connection for url/scan api
backend   | 2024-06-11 02:34:41,955 - Total Pages from Wikipedia = 1
backend   | 2024-06-11 02:34:42,020 - Break down file into chunks
backend   | 2024-06-11 02:34:42,022 - Split file into smaller chunks
backend   | 2024-06-11 02:34:42,517 - dermatitis
backend   | 2024-06-11 02:34:42,517 - <src.entities.source_node.sourceNode object at 0xffff2001ca00>
backend   | 2024-06-11 02:34:42,517 - Update source node properties
backend   | 2024-06-11 02:34:42,580 - Update the status as Processing
backend   | 2024-06-11 02:34:42,731 - File Failed in extraction: {'message': 'Failed To Process File:dermatitis or LLM Unable To Parse Content ', 'error_message': "int() argument must be a string, a bytes-like object or a real number, not 'NoneType'", 'file_name': 'dermatitis', 'status': 'Failed', 'db_url': '[redacted]', 'failed_count': 1, 'source_type': 'Wikipedia'}
backend   | Traceback (most recent call last):
backend   |   File "/code/score.py", line 175, in extract_knowledge_graph_from_file
backend   |     result = await asyncio.to_thread(
backend   |   File "/usr/local/lib/python3.10/asyncio/threads.py", line 25, in to_thread
backend   |     return await loop.run_in_executor(None, func_call)
backend   |   File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
backend   |     result = self.fn(*self.args, **self.kwargs)
backend   |   File "/code/src/main.py", line 197, in extract_graph_from_file_Wikipedia
backend   |     return processing_source(graph, model, file_name, pages, allowedNodes, allowedRelationship)
backend   |   File "/code/src/main.py", line 253, in processing_source
backend   |     update_graph_chunk_processed = int(os.environ.get('UPDATE_GRAPH_CHUNKS_PROCESSED'))
backend   | TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'
backend   | 2024-06-11 02:34:42,733 - closing connection for extract api
backend   | 2024-06-11 02:34:43,452 - Exception in update KNN graph:list index out of range
backend   | Traceback (most recent call last):
backend   |   File "/code/score.py", line 228, in update_similarity_graph
backend   |     result = await asyncio.to_thread(update_graph, graph)
backend   |   File "/usr/local/lib/python3.10/asyncio/threads.py", line 25, in to_thread
backend   |     return await loop.run_in_executor(None, func_call)
backend   |   File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
backend   |     result = self.fn(*self.args, **self.kwargs)
backend   |   File "/code/src/main.py", line 376, in update_graph
backend   |     return graph_DB_dataAccess.update_KNN_graph()
backend   |   File "/code/src/graphDB_dataAccess.py", line 129, in update_KNN_graph
backend   |     if index[0]['name'] == 'vector':
backend   | IndexError: list index out of range

Backend Dockerfile:
FROM python:3.10
WORKDIR /code
ENV PORT 8000
EXPOSE 8000
COPY . /code
RUN apt-get update \
    && apt-get install -y libgl1-mesa-glx cmake \
    && apt-get install -y poppler-utils \
    && apt install -y tesseract-ocr \
    && export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu:$LD_LIBRARY_PATH \
    && pip install --no-cache-dir --upgrade -r /code/requirements.txt

# CMD ["uvicorn", "score:app", "--host", "<IP_ADDRESS>", "--port", "8000","--workers", "4"]
CMD ["gunicorn", "score:app","--workers","4","--worker-class","uvicorn.workers.UvicornWorker", "--bind", "<IP_ADDRESS>:8000", "--timeout", "300"]

Frontend Dockerfile:
# Step 1: Build the React application
FROM node:20 AS build
# ENV BACKEND_API_URL "https://dev-backend-dcavk67s4a-uc.a.run.app"
# ENV BACKEND_PROCESSING_URL "https://dev-processing-backend-dcavk67s4a-uc.a.run.app"
#ENV BLOOM_URL "https://bloom-latest.s3.eu-west-2.amazonaws.com/assets/index.html?connectURL={CONNECT_URL}&search=Show+me+a+graph"
ENV BLOOM_URL "https://workspace-preview.neo4j.io/workspace/explore?connectURL={CONNECT_URL}&search=Show+me+a+graph&featureGenAISuggestions=true&featureGenAISuggestionsInternal=true"
ENV REACT_APP_SOURCES ""
ENV LLM_MODELS ""
ENV TIME_PER_CHUNK 4
ENV ENV "DEV"
ENV GOOGLE_CLIENT_ID "[redacted]"
ENV CHUNK_SIZE 5242880
WORKDIR /app
COPY package.json yarn.lock ./
RUN yarn add @neo4j-nvl/base @neo4j-nvl/react
RUN yarn install
COPY . ./
RUN yarn run build

# Step 2: Serve the application using Nginx
FROM nginx:alpine
COPY --from=build /app/dist /usr/share/nginx/html
COPY nginx/nginx.conf /etc/nginx/conf.d/default.conf

EXPOSE 8080
CMD ["nginx", "-g", "daemon off;"]

Backend .env
OPENAI_API_KEY = "[redacted]"
DIFFBOT_API_KEY = "[redacted]"
NEO4J_URI = "[redacted]"
NEO4J_USERNAME = "[redacted]"
NEO4J_PASSWORD = "[redacted]"
NEO4J_DATABASE = "neo4j"
AWS_ACCESS_KEY_ID =  ""
AWS_SECRET_ACCESS_KEY = ""
EMBEDDING_MODEL = "text-embedding-ada-002" # I have tried "openai" here but same error
IS_EMBEDDING = "TRUE"
KNN_MIN_SCORE = ""
LANGCHAIN_API_KEY = "[redacted]"
LANGCHAIN_PROJECT = "default"
LANGCHAIN_TRACING_V2 = ""
LANGCHAIN_ENDPOINT = ""
NUMBER_OF_CHUNKS_TO_COMBINE = ""
# NUMBER_OF_CHUNKS_ALLOWED = ""
# Enable Gemini (default is True)
GEMINI_ENABLED = True|False
# Enable Google Cloud logs (default is True)
GCP_LOG_METRICS_ENABLED = True|False

Frontend .env
BACKEND_API_URL="http://localhost:8000"
BLOOM_URL="neo4j://localhost:7687"
REACT_APP_SOURCES=""
LLM_MODELS=""
ENV=""
TIME_PER_CHUNK=

Rootfolder .env
OPENAI_API_KEY = "sk-[redacted]"
DIFFBOT_API_KEY = "[redacted]"
NEO4J_URI = "[redacted]"
NEO4J_USERNAME = "[redacted]"
NEO4J_PASSWORD = "[redacted]"
BACKEND_API_URL = "http://localhost:8000"

@jexp saw some previous issues with a similar problem. Was a resolution found?

solved it.
The following have to have values in the .env file as there is no default set, also the numbers cannot be strings:
EMBEDDING_MODEL = "openai"
KNN_MIN_SCORE = 0.94
NUMBER_OF_CHUNKS_TO_COMBINE = 20
UPDATE_GRAPH_CHUNKS_PROCESSED = 20


why are you offering 3-clause bsd

is there ever any reason to prefer 3-clause over 2-clause?  all that does is enable you to be incompatible with the gpl, the world's most pointlessly difficult and ineffective license

Hey! Thanks for taking time to open this issue. While I do understand your concerns, I think its best for the user to decide what is best for them. I do understand that the consequences of choosing a poor license are not clearly highlighted in the questionnaire, so if you could, please link any source explicitly mentioning the demerits of the BSD-3-Clause license. If I do think it's worth to put up a warning, or remove it completely, I will. Or you could open a PR for that ;)
Nevertheless, please send a link, I'd really like to look into this. Thanks again!

a link to what?
the difference between the two-clause and the three-clause is that a comment requiring a mention of the regents of the state of california uc berkeley was removed
that requirement is in conflict with the gpl
the whole reason for that removal was to end the unnecessary conflict with the gpl
i am not aware of any circumstances under which the old one is preferred.  it's just to avoid gpl neckbearding.

https://en.wikipedia.org/wiki/BSD_licenses#2-clause_license_("Simplified_BSD_License"_or_"FreeBSD_License")

According to GNU's own docs, the Modified BSD (3-clause) and FreeBSD (2-clause) both are are GPL compatible licenses.
https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses


Create shim for workers automatically

Currently, gloo-worker / yew-agent works by creating a worker shim as an inline blob file:
importScript("http://localhost:8080/worker.js");
wasm_bindgen("http://localhost:8080/worker_bg.wasm");

However, this approach has a few limitations:

Non fully qualified URLs does not work with inline object url. Currently, if a non fully qualified path is provided, gloo-worker infers the path with window.location.href.
If a shim script is provided, gloo-worker can delegate path resolution to the browser.
ServiceWorker needs an URL to register.
SharedWorker can fail to connect to the same worker if the inline shim script becomes different between tabs due relative path resolution.

It would be helpful if trunk can emit a shim script automatically for web workers like the following:
importScript("./worker.js");
wasm_bindgen();

Hey Futur, thanks for the idea.
I'm not sure the Trunk team has the bandwidth right now but I'll give any PR priority if you decide to submit one, otherwise this will happen "when we get to it."


fix: support running in directories containing spaces

What this PR solves / how to test
Fixes https://github.com/cloudflare/workers-sdk/issues/5268
Author has addressed the following

Tests

[ ] TODO (before merge)
[x] Included
[ ] Not necessary because:

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[ ] Required / Maybe required
[x] Not required because: small bug fix that will not affect e2es

Changeset (Changeset guidelines)

[ ] TODO (before merge)
[x] Included
[ ] Not necessary because:

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s): https://github.com/cloudflare/cloudflare-docs/pull/...
[x] Not necessary because: bug fix

This has valid CI failures on windows:
Error: No such module "D:/a/workers-sdk/workers-sdk/node_modules/.pnpm/vitest@1.5.0_@types+node@20.8.3_@vitest+ui@1.6.0_vitest@1.2.2_/node_modules/vitest/dist/file:/D:/D:/a/workers-sdk/workers-sdk/node_modules/.pnpm/vitest@1.5.0_@types+node@20.8.3_@vitest+ui<EMAIL_ADDRESS>


Add matching of imu -- imu_temp messages

Add matching of imu -- imu_temp messages instead of assert.
It is usually single message shift in this flow of imu and imu_temp flow.
So, I would suggest to make check of neighbouring messages to imu message.
Pseudo-code:
if current_imu_message does not match current_imu_temp_message:
  if next_imu_message matches current_imu_temp_message:
    current_imu_message = next_imu_message
    ...
  elif current_imu_message matches next_imu_temp_message:
    current_imu_temp_message = next_imu_temp_message
    ...
  else:
    assert...

This is not urgent.

Not needed more


Fix qr code not fully visible

Fix #2
Demo: https://wafer.li

Could you merge it?
I have no write access to this repo.


Parse percent as bare type

Fixes #5.

Pull Request Test Coverage Report for Build 658080184

18 of 18 (100.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 89.293%

Files with Coverage Reduction
New Missed Lines
%

type.go
2
84.13%

Totals

Change from base Build 544884403:
-0.2%

Covered Lines:
417

Relevant Lines:
467

💛  - Coveralls


Custom commanding for explorer style integrations for per interaction customization

Description of the new feature / enhancement
Currently, the containing folder of a file/an app or the folder itself that's been found in the PT Run list can only be opened in the standard system file explorer. One should also be able to open the file/folder in a third-party file manager such as double commander.  In other words, this button's behavior can be customized:

Scenario when this would be used?
This is helpful for users who use double commander/total commander to manage files.
Supporting information
No response

I remember this getting brought up a while back. I tried searching for it but couldn’t seem to find it.
Do you have it set as your default file manager?  I can poke around the code tomorrow.

I also searched the existing issues and couldn't find a relevant issue, so filed this one.
I am using double commander and didn't set it as my default file manager. First, I don't know how to do that properly (a quick google reveals that it involves registry modification etc). Second, I don't really want to override the system default file explorer so that Win+E will still open the Windows File Explorer.
I am also using Everything to search local files and in Everything, the user can use his/her preferred file explorer to open file locations and folders, something like this:

Just verified with Files.  We do directly work with what is the default file explorer so what is listed above is supported to be clear.
While i think this could be powerful, this adds a ton of permutations and support matrix for helping users when stuff changes or is misconfigure.

+1 on this feature. I use OneCommander, and I have set up it as my main file explorer (patched the registry):
Double clicking a folder on my desktop for example opens OneCommander instead of windows explorer)
Also ctrl+clicking on the windows taskbar explorer icon opens OneCommander.
But hitting ctrl+shift+e after a search here still opens windows explorer. Which is far from ideal if you want to stick to an alternative file manager.
Hope than this can be bypassed somehow.

any updates on this?


npm run dev shows different output to running bun run start

Describe the bug
This is what it's supposed to look like when running npm run dev

But when run from a container use bun run start it looks like this:

The dockerfile looks like this:
FROM node:20.17.0-alpine3.20 AS deps

WORKDIR /app

COPY package.json package-lock.json .npmrc /

RUN npm ci

COPY . .

# RUN npm run check

FROM deps AS test

RUN npm run testci

FROM deps AS build

# ARG NODE_ENV=development

RUN npm run build

FROM oven/bun:1.1.29-alpine AS publish

COPY --from=build /app/build /out/

WORKDIR /out

ENTRYPOINT [ "bun", "run", "start" ]

tailwind.config looks like this:
import forms from '@tailwindcss/forms';
import typography from '@tailwindcss/typography';

/** @type {import('tailwindcss').Config} */
export default {
  content: [
    './src/**/*.{html,js,svelte,ts}',
    './node_modules/svelte-5-ui-lib/**/*.{html,js,svelte,ts}',
    './node_modules/flowbite-svelte-icons/**/*.{html,js,svelte,ts}'
  ],

  theme: {
    extend: {
      colors: {
        primary: {
          50: '#f0f9ff',
          100: '#e0f2fe',
          200: '#bae6fd',
          300: '#7dd3fc',
          400: '#38bdf8',
          500: '#0ea5e9',
          600: '#0284c7',
          700: '#0369a1',
          800: '#075985',
          900: '#0c4a6e'
        },
        secondary: {
          50: '#FFF5F2',
          100: '#FFF1EE',
          200: '#FFE4DE',
          300: '#FFD5CC',
          400: '#FFBCAD',
          500: '#FE795D',
          600: '#EF562F',
          700: '#EB4F27',
          800: '#CC4522',
          900: '#A5371B'
        }
      }
    }
  },

  plugins: [typography, forms]
};

svelte.config.js looks like this:
import adapter from 'svelte-adapter-bun';

/** @type {import('@sveltejs/kit').Config} */
const config = {
  compilerOptions: {
    runes: true
  },
	kit: {
		// adapter-auto only supports some environments, see https://svelte.dev/docs/kit/adapter-auto for a list.
		// If your environment is not supported, or you settled on a specific environment, switch out the adapter.
		// See https://svelte.dev/docs/kit/adapters for more information about adapters.
		adapter: adapter()
	}
};

export default config;

vite.config.js looks like this:
import { defineConfig } from 'vitest/config';
import { sveltekit } from '@sveltejs/kit/vite';

export default defineConfig({
	plugins: [sveltekit()],

	test: {
		include: ['src/**/*.{test,spec}.{js,ts}']
	}
});

my package.json:
{
  "name": "ui",
  "version": "0.0.1",
  "type": "module",
  "scripts": {
    "dev": "vite dev",
    "build": "svelte-kit sync && vite build",
    "preview": "vite preview",
    "check": "svelte-kit sync && svelte-check --tsconfig ./jsconfig.json",
    "check:watch": "svelte-kit sync && svelte-check --tsconfig ./jsconfig.json --watch",
    "format": "prettier --write .",
    "lint": "prettier --check .",
    "test:unit": "vitest",
    "testci": "vitest run",
    "test": "npm run test:unit -- --run"
  },
  "devDependencies": {
    "@sveltejs/adapter-auto": "^3.0.0",
    "@sveltejs/kit": "^2.0.0",
    "@sveltejs/vite-plugin-svelte": "^4.0.0",
    "@tailwindcss/forms": "^0.5.9",
    "flowbite-svelte-icons": "^2.0.2",
    "@tailwindcss/typography": "^0.5.15",
    "autoprefixer": "^10.4.20",
    "prettier": "^3.3.2",
    "prettier-plugin-svelte": "^3.2.6",
    "prettier-plugin-tailwindcss": "^0.6.5",
    "svelte": "^5.0.0",
    "svelte-check": "^4.0.0",
    "svelte-adapter-bun": "^0.5.2",
    "typescript": "^5.0.0",
    "tailwindcss": "^3.4.9",
    "vite": "^5.0.3",
    "vitest": "^2.0.4"
  },
  "dependencies": {
    "svelte-5-ui-lib": "^0.9.24",
    "js-yaml": "^4.1.0",
    "json-schema": "^0.4.0",
    "monaco-editor": "^0.49.0",
    "monaco-yaml": "^5.2.0"
  }
}

It really looks like something between the dev build and production build
Reproduction
I can't do a reproduction through stackblitz or anything.
But, it simply is just running npm run dev  compared to building the container and running it from there.
I've tried switching out the adapter for just the node adapter and get the same result.
So I assume this is something in the vite build process which is causing problems
So, I've just tried just doing npm run preview in the docker image, and that gives the bad output, where as doing npm run preview locally gives the correct output...
Version and System Info
System:
    OS: Linux 6.11 NixOS 24.11 (Vicuna) 24.11 (Vicuna)
    CPU: (22) x64 Intel(R) Core(TM) Ultra 7 155H
    Memory: 85.98 GB / 93.87 GB
    Container: Yes
    Shell: 5.2.32 - /run/current-system/sw/bin/bash
  Binaries:
    Node: 20.17.0 - ~/.nix-profile/bin/node
    npm: 10.8.2 - ~/.nix-profile/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
  npmPackages:
    @sveltejs/kit: ^2.0.0 => 2.7.3
    svelte: ^5.0.0 => 5.1.4
    svelte-5-ui-lib: ^0.9.24 => 0.9.24
    vite: ^5.0.3 => 5.4.10

was a problem in the .dockerignore, i wasn't ignoring the .svelte-kit and also, I wasn't copying package json to the right place


Remove password validation

In my company we dont' use username/passwords, instead we're using tokens for identification. Therefore, only the username is useful, but your plugin insists on having a password. Can we remove that? thanks.

If you use token you have to enter it in password field. This will be renamed in one of the next releases

what was the indention of the PR? Remove validation because you not need any credentials??


Training Dataset of HF Hub Checkpoint vs. Paper Models

Hello, the paper mentions several models, one trained on COCO, another on LVIS, a third on GoldG, O365, SBU and CC3M. As far as I understand, without retraining the model, you can download one of the ten checkpoints to use with the gligen_inference.py script.
My question is: on which dataset were these checkpoints trained? In particular, for "Box+Text+Image" modality with Generation and Inpainting mode.

I got a reply: The released checkpoint are only trained on GoldG+SBU+O365+CC3M, with no fine-tuning on COCO

Hi, have you trained the model yourself? I am trying to reproduce the text-box grounding generation on COCO2014, but even if I trained for 200k iters (the paper recommends 100K), the results do not follow the bbox. I do not know where it goes wrong, is it because the COCO2014 dataset is still not big enough?


ConnectionPool: unclear reuse behavior with different IP sets

I was a bit reluctant between a feature request and a bug, but since it's technically docummented, let's go with feature request for now.
We've run into some corner-case behavior which might warrant either some documentation improvement or maybe even some new feature. Context:
The documentation for ConnectionPool mentions this:

HTTP requests that share the same Address may share a Connection.

This means if we have two services whose DNS records point to some overlapping set of IPs (e.g. because they share a load-balancer), we might reuse a connection first used for service A when accessing service B later.
If we're using HTTP2 this can even happen over with TLS (HTTP1 would force a different connection to allow for SNI; HTTP2 can multiplex).
This seems like an unlikely scenario at first, but we ran into it while rolling out IPv6 support for some of our services:

our clients connect to a series of services in order
all services live behind a common HTTP2-capable load-balancer
one of them (S) was "dualstacked" before the others by getting an AAAA DNS record
service S actually needed the information "can this client speak IPv6?" (keeping the "why" out-of-scope; suffice to say it's the reason why it was prioritized over the other services)
service S almost never saw connections via v6 (even for clients we know had working v6 connectivity) :boom:

Looking back it's clear we were reusing an existing v4 connection to some previous service to talk to a dualstacked service, which "shadowed" v6 support in almost all cases (except when we happened to run into connection-pool limits between calls).
I'm reluctanct to call this  bug because in most cases an existing connection is what you want. However, I still see two possible improvements:

expand the docs to include a mention to this edge case. Something like:

"HTTP requests that share the same Address may share a Connection. Conversely, if one request resolves to address A, a subsequent request resolving to addresses A and B may never see any connections to address B."

optionally extend the ip-to-connection mapping to consider all resolved IPs (becoming maybe "hash-of-ips"-to-connection?). This would incur some minor overhead at the advantage of ensuring connection reuse is tried only when it's sane.

wdyt?

I'm not clear the connection coalescing is wrong, or should be improved. And while it could be configurable, we avoid this and try to implement something correct and inline with user agents like Firefox and Chrome. It's deliberate that if there is some overlap and and existing connection in that overlap, we will use it. From memory we are less aggressive that Firefox or Chrome (but I forget which).
So I think updating the documentation and perhaps adding a sample to highlight this is the way to go. The other aspect of this is observability, how using the EventListener or the new ConnectionListener to make it obvious what is going on.

Yes, I wouldn't say it's wrong either. Just slightly misleading if the setup is non-orthodox.
In hindsight the problem we ran into is pretty obvious, but unfortunately if you start debugging from the other end (it's always DNS, right? :grin: ), it takes a while to get down to the client's connection pooling.

Yep, I can believe this was very surprising! In general we’re also nondeterministic for dualstacked hosts. With OkHttp 5 and happy eyeballs OkHttp will attempt IPv6 first, and IPv4 concurrently after a brief delay.
I think we could write a bunch more documentation here. What did you read while you were looking into this? We should put the docs where people are already looking.


Cluster filter is missing in Gitpod  / Overview dashboard

This leads to duplicated datapoints, making it a little harder to understand
Old:

New(broken):

Looks even worse now that we have pluggable workspace clusters running!


fix(linux): include border and titlebars in Window::{outer_position, outer_size} and WindowEvent::Moved event

closes tauri-apps/tauri#11510

Tested on my Ubuntu 24.04 with Wayland
btw, I  found the doc of WindowEvent::Moved and outer_position says Wayland will always return (0,0), but it seems that it returns the actual position on my end.

Make sure you're running under Wayland, launching the example from within vscode usually runs the window under x11 even if the session is Wayland.

Tested on my Ubuntu 24.04 with Wayland
btw, I  found the doc of WindowEvent::Moved and outer_position says Wayland will always return (0,0), but it seems that it returns the actual position on my end.

Make sure you're running under Wayland, launching the example from within vscode usually runs the window under x11 even if the session is Wayland.

Oh, you're right. I was running from the vscode and it runs on X11 actually


feat(sweeps): Sweeps now has an expected_run_count for grid search

11226
Description
Adds an expected_run_count attribute to the sweeps object, which is the number of expected sweeps in a grid search. This just = the Cartesian product of the number of params.
Testing
test_public_api.py::test_sweep_api_expected_run_count
Checklist

[ ] Include reference to internal ticket "Fixes WB-NNNN" and/or GitHub issue "Fixes #NNNN" (if applicable)
[ ] Ensure PR title compliance with the conventional commits standards

One caveat to this PR is that the dummySweepOrchestrator in core doesn't handle nested parameters, whereas anaconda does. This leads to the nested param test failing (here) in wandb, but working in real environments that hit anaconda. 2 reasons this is fine:

The core side of this PR is already in, and passes the anaconda tests.
Nested parameters are very niche, the vast majority of sweeps use normal params.


Support google workload identity federation

Support for workload identity federation using credential configuration files.
Currently, if the credential configuration files is specified as secretAccessKeySecretRef, the following error will occur.
failed to create GCP secretmanager client: failed to process the provided JSON credentials: google: read JWT from JSON credentials: 'type' field is "external_account" (expected "service_account")

we have similar setup:

manually created workload identity federation pool (with expected audience)
attach connected service account
generate service account credentials (without secret)

sample:
{
  "type": "external_account",
  "audience": "//iam.googleapis.com/projects/<projectID>/locations/global/workloadIdentityPools/<poolName>/providers/<providerName>",
  "subject_token_type": "urn:ietf:params:oauth:token-type:jwt",
  "token_url": "https://sts.googleapis.com/v1/token",
  "service_account_impersonation_url": "https://iamcredentials.googleapis.com/v1/projects/-/serviceAccounts/<serviceAccountName>@<projectID>.iam.gserviceaccount.com:generateAccessToken",
  "credential_source": {
    "file": "/var/run/secrets/tokens/psat",
    "format": {
      "type": "text"
    }
  }
}

So need to exchange this credentials + SA token (see credential_source) for GCP token.
CRD might look something like:

apiVersion: generators.external-secrets.io/v1alpha1
kind: GCRAccessToken
metadata:
  name: gcr-gen
spec:
  projectID: "my-project"
  auth:
    jwt:
        workloadIdentityPool: foo
        provider: bar
	    serviceAccountRef:
	        name: service-account-token-to-use
	    	audience:
	    	  - foo
	    	  - bar

Let me reopen it, seems there is interest and this is a good opportunity to contribute :)

Any plans to support Workload Identity Federation?

Any updates on the matter?
It would be highly useful to let applications running on-premises or on other cloud providers use workload identity federation to authenticate to GCP secret Manager. (Also applies for GCRAccessToken generator)

I would also like to see support for this for similar reasons, but I think there are two different use cases here:

Use workload identity federation strictly to access secrets. For this I would propose a CRD extension. ESO should request a token using the K8s TokenRequest API for the specified k8s service account.
With this it is possible to specify the namespace of the service account in the principal.
Example:

apiVersion: external-secrets.io/v1beta1
kind: ClusterSecretStore
metadata:
  name: gcp-store
  namespace: external-secrets
spec:
  provider:
    gcpsm:
      projectID: project-id
      workloadIdentityFederation:
        serviceAccountRef:
          name: team-a
          namespace: team-a-ns # only for cluster stores

(Alternatively we could add a federated flag and still use the existing workloadIdentity).
This would mean we have to generate the GOOGLE_APPLICATION_CREDENTIALS ourselves, similar to https://github.com/external-secrets/external-secrets/issues/1946#issuecomment-1667630229

Add something that actually generates GCP tokens (i.e. does the token exchange) and provides it in a secret, so it can be used for applications that cannot be used with workload identity federation.
Sounds like an interesting idea, but feels a bit out-of-scope for ESO. I also have no idea how to do this token exchange.

Add something that actually generates GCP tokens (i.e. does the token exchange) and provides it in a secret, so it can be used for applications that cannot be used with workload identity federation.
Sounds like an interesting idea, but feels a bit out-of-scope for ESO. I also have no idea how to do this token exchange.

This can actually be a Generator. we have similar Generators for AWS regarding STS tokens being cooked.
However - it is good to mention that these type of features are really community driven. Maintainers will do that if they wish to do so - maintainer focus would either be things critical to the project or maintenance activities.
If you still need the feature, but don't have the in-house knowledge to contribute back to the project - I'd suggest to go for vendors/consultancy companies to do that for you. Or alternatively, reach out to one of the contributors/maintainers for and negotiate a bounty 😄

Sorry, my comment wasn't meant as a "please implement that for me" 😄  but rather as looking for feedback on the ideas, especially the CRD change and that these are two different things (re. original commenters). Should have phrased that differently.
I will probably tackle the first one myself, as I have use for that.

Sorry, my comment wasn't meant as a "please implement that for me" 😄 but rather as looking for feedback on the ideas, especially the CRD change and that these are two different ideas (re. original commenters). Should have phrased that differently.
I will probably tackle the first one myself, as I have use for that.

No worries!
Re: WorkloadIdentityFederation vs WorkloadIdentity - I think adding a new WorkloadIdentityFederation block works just fine, and it is easily forward/backwards compatible. However, do note the namespaces on ClusterSecretStores need to be a pointer, as if the user does not provide a namespace, we should use the namespace of the referrent ExternalSecret (this is a somewhat hidden feature of Referent Authentication)


[ChannelTabs] Issue: Crash on startup

Before you submit an issue please restart your discord. If the issue is still there feel free to write a bug report.
Describe the bug
On startup, ChannelTabs will immediately crash your instance of Discord.
To Reproduce
Steps to reproduce the behavior:
(Not officially sure if this is how it is supposed to reproduced as I cannot reproduce it without it crashing)

Go to ChannelTabs drop-down menu (Top right)
Go through some of the different menus
Crash will possibly occur

When restarting discord

Crash right after startup

Expected behavior
Discord will continue through startup and return to where you left off and ChannelTabs will work as intended
Screenshots
If applicable, add screenshots to help explain your problem.
Please also check the console by pressing Ctrl + Shift + I and send screenshots of errors (red messages)

I have a video recording of it happening but its too big to add into this bug report so I added it to a drive folder
https://drive.google.com/drive/folders/10c-abxVpHe02zdnjekI0jH1IgfQw_z1H?usp=share_link
Information (please complete the following information):

OS: MacOS
Plugin Version: 2.6.5
Discord version: PTB, Canary
Compact Mode enabled? No

Additional context
Add any other context about the problem here.

Closed issue due to being outdated plugin version

I have figured out how to replicate the crashing issue, though it will no longer constantly crash on startup possibly due to updated plugin version

Go to ChannelTabs drop-down menu (Top right)
Hover over Appearance tab

Uploading Screen Recording 2023-02-13 at <IP_ADDRESS>9.mov…
Another way that it can be caused is by adding a channel to favorites

Right-click channel you would like to add to favorites
Hover over ChannelTabs menu
Click on "Save Channel as Bookmark"

Uploading Screen Recording 2023-02-13 at <IP_ADDRESS>.mov…
Console error for the two is the same as listed before (React error)

I just downloaded the updated plugin from this repository, and my discord is still crashing on startup with the same as this person was getting..

Same, getting crashes on startup since yesterday. Discord update?

Typing Indicators (Show Typing) on all the badge visibility settings crashes discord solution for the time being is disable the show typing in the settings on all of the badge visibility sub options. Open the config file for the plugin and change all the TypingBadge from true to false.

Typing Indicators (Show Typing) on all the badge visibility settings crashes discord solution for the time being is disable the show typing in the settings on all of the badge visibility sub options. Open the config file for the plugin and change all the TypingBadge from true to false.

Worked, thanks!

Typing Indicators (Show Typing) on all the badge visibility settings crashes discord solution for the time being is disable the show typing in the settings on all of the badge visibility sub options. Open the config file for the plugin and change all the TypingBadge from true to false.

worked for me too thx!

Typing Indicators (Show Typing) on all the badge visibility settings crashes discord solution for the time being is disable the show typing in the settings on all of the badge visibility sub options. Open the config file for the plugin and change all the TypingBadge from true to false.

Where is located the config file ? What is the name of the file ?

@Skorflex
AppData\Roaming\BetterDiscord\plugins

@Skorflex AppData\Roaming\BetterDiscord\plugins

What should I change? I don't understand ..

@Skorflex If you don't know how to edit config/json files, you're properly better off by just running BetterDiscord setup again, and use the repair option - and dont use ChannelTabs plugin untill it's been updated.

@Skorflex If you don't know how to edit config/json files, you're properly better off by just running BetterDiscord setup again, and use the repair option - and dont use ChannelTabs plugin untill it's been updated.

😢😿

Typing Indicators (Show Typing) on all the badge visibility settings crashes discord solution for the time being is disable the show typing in the settings on all of the badge visibility sub options. Open the config file for the plugin and change all the TypingBadge from true to false.

Thanks its worked

legend! thank you so much

Typing Indicators (Show Typing) on all the badge visibility settings crashes discord solution for the time being is disable the show typing in the settings on all of the badge visibility sub options. Open the config file for the plugin and change all the TypingBadge from true to false.

Legend! Thank you so much

Typing Indicators (Show Typing) on all the badge visibility settings crashes discord solution for the time being is disable the show typing in the settings on all of the badge visibility sub options. Open the config file for the plugin and change all the TypingBadge from true to false.

This solution doesn't seem to work for me.
It is only these lines that should be set to false right?

Typing Indicators (Show Typing) on all the badge visibility settings crashes discord solution for the time being is disable the show typing in the settings on all of the badge visibility sub options. Open the config file for the plugin and change all the TypingBadge from true to false.

This solution doesn't seem to work for me. It is only these lines that should be set to false right?

Are you editing the config file that has your userid?

Are you editing the config file that has your userid?

I see! I was editing the wrong file. It's working now, thanks!

I cant even click the edit plugin button as i uninstalled the plugin, the moment i install it discord crashes, i then need to reinstall BetterDiscord from a fresh installation

Can you repair BetterDiscord after discord crashes making it disabled on startup? If not then while Discord crashes on startup you should still be able to navigate to the config folder in AppData and modify the file without having to open Discord at all.

I have repaired Better Discord,  Removed it and reinstalled, still the same problem occurs. Which file to i need to alter

I have repaired Better Discord, Removed it and reinstalled, still the same problem occurs. Which file to i need to alter

Go to your plugin folder, %appdata%/betterdiscord/plugins and edit the channel tabs config that has your username, and set the ones with Typing to false.

The only files i see are ChannelTabs.config.json and ChannelTabs.plugin.js
config file shows this:
{
    "currentVersionInfo": {
        "version": "2.6.6",
        "hasShownChangelog": true
    }
}

Typing Indicators (Show Typing) on all the badge visibility settings crashes discord solution for the time being is disable the show typing in the settings on all of the badge visibility sub options. Open the config file for the plugin and change all the TypingBadge from true to false.

Legend! Thank you so much

Thanks, this helps alot

The only files i see are ChannelTabs.config.json and ChannelTabs.plugin.js
config file shows this:
{
    "currentVersionInfo": {
        "version": "2.6.6",
        "hasShownChangelog": true
    }
}

For me, it was under a file named "ChannelTabs_new_#######.config.json" that contained a settings field with the typing indicator variables. Do you have a similar config file?

Typing Indicators (Show Typing) on all the badge visibility settings crashes discord solution for the time being is disable the show typing in the settings on all of the badge visibility sub options. Open the config file for the plugin and change all the TypingBadge from true to false.

yo thanks for this!


Projects For Beginners

Add some Projects for beginners in any language .
Projects should be easy and should contain working code.

Please assign it to me. I am a beginner

please assign this task to me

Why didn't you assign it to me?

 These are for beginner .
Sorry but try to understand.
I hope you'll Understand.
and also SIH winner Congratulations..... @dishantzaveri

That is development. I am a beginner to open source and competitive programming

I will add Some more issues for competitive programing and Love to assign it to you.

Still open you can
add If You want...


Code Example: Port Jax weights to PyTorch

Hi,
Thanks very much for your great work.
I noticed that you transfer many models' checkpoints from jax to pytorch.
I was wondering would mind sharing a code example? It will be greatly helpful.
Thanks in advance.

@ShoufaChen it's already in the vit model, it was added to support loading the 50K weights from How to train your ViT

Hi, @rwightman
Thanks for your example.
Have you ever ported the BatchNorm2d layer?
I found this layer behaves relatively differently using Jax and Pytorch.
Below is my transfer code:
target_torch['_input_preprocessor.convnet.layers.1.weight'] = jax_params['image_preprocessor/~/conv2_d_downsample/~/batchnorm']['scale']
target_torch['_input_preprocessor.convnet.layers.1.bias']   = jax_params['image_preprocessor/~/conv2_d_downsample/~/batchnorm']['offset']
target_torch['_input_preprocessor.convnet.layers.1.running_mean'] = jax_state['image_preprocessor/~/conv2_d_downsample/~/batchnorm/~/mean_ema']['average']
target_torch['_input_preprocessor.convnet.layers.1.running_var']  = jax_state['image_preprocessor/~/conv2_d_downsample/~/batchnorm/~/var_ema']['average']
assert jax_state['image_preprocessor/~/conv2_d_downsample/~/batchnorm/~/mean_ema']['counter'] == jax_state['image_preprocessor/~/conv2_d_downsample/~/batchnorm/~/var_ema']['counter']
target_torch['_input_preprocessor.convnet.layers.1.num_batches_tracked'] = jax_state['image_preprocessor/~/conv2_d_downsample/~/batchnorm/~/mean_ema']['counter']

I appreciate any hints from you.
Thanks in advance.

For BatchNorm, I noticed that there is a difference between Jax and Pytorch.
I.e.
Jax computation order:  (inputs - mean) *  (scale * rsqrt(var + eps))
Pytorch:  (inputs - mean) * scale * rsqrt(var + eps).
I know they are theoretically equivalent.
From your experience, does this make a significant difference?

Pls ignore this...
I found the problem lies in that I did not set model.eval().

@ShoufaChen yeah, that'll bite you w/ BN layers present, also check that the BN eps values are the same.

Thanks for your effort. But I want to inquire is the code still there? I open the link but found it is only the line of input parameters. And I only find how to initialize model weights in Jax way, rather than importing Jax weights to PyTorch.


Support packages that span multiple directories

I extracted this from #228 since it is unrelated to the rest of the changes.

@eltoder excellent work. After you rebase this branch, I can get to merging it.

let's see what the  'update branch' button does
...ah...a merge 😒

👀 did we just both rebase and force push? Anyways it looks like the commits are in order in the end 😄

@ariebovenberg looks like we did :)

@eltoder any other related features you have planned? If not, I'll bundle your improvements into a new release

@ariebovenberg That's it for now. Thank you for merging!

@eltoder thanks for your contribution 🤝

Release 0.19.0 is now out with the improved functionality 🚀


youtube downloading: don't check format download speed

Now that we're doing threading, probably no need to check format. Here's difference in metrics:


Change timeout?

Is it possible to change the timeout using the RIE? Currently it seems that it is set to 300s, however the Lambda functions can now run up to 15 minutes

You can configure the timeout through an Env Var. Details are in the our README.
"You can configure timeout by setting AWS_LAMBDA_FUNCTION_TIMEOUT to the number of seconds you want your function to timeout in."


pynapple dependency

Simplify tutorials by "remaining" in pynapple, example by adding pynapple as a dep, and silently convert back and forth to pynapple using decorators.
Implementation:

decorator @cast_jax: call as_array, and duck-type pynapple: check x.times() and x.data() methods and x.time_support attribute are present (just call and if that passes it's pynapple), revert back to pynapple including the time_support. only for predict, convolve;

pynapple integration resolved on nemos side. Data transfer is involved until pynajax is ready.


Support on conflict

PR Info
This PR exposes the ON CONFLICT support that was added in sea-query
Adds
Option for a new insert_or that allows you to specify an on-conflict behavior
Public API Rationale
I think there were 3 ways this could be exposed from a public API point of view:

Modify the existing insert function to add a new parameter
Keep the insert function as-is, but introduce some state in the ActiveModel to handle conflicts
Create a new function called insert_or

I didn't pick (1) because this feels like too big of a breaking change.
I didn't pick (2) because to be, handling conflict is something you do in a per-query basis and not in the model. For example, in some cases you may want to do nothing on a conflict, some cases you may want to error, some cases you may want to override.
(3) seemed like the best solution

Handling of return value
One of the conflict options is ON CONFLICT DO NOTHING. This doesn't work with the current API where the insert function is assumed to always have a return value (do nothing returns an empty SQL result if a conflict is found)
There are two ways this can be solved:

When using ON CONFLICT DO NOTHING, check if nothing was returned and then do a find to find the entry that caused the conflict and return that as the result of the insert
Make that when using insert_or, we have an optional return instead of a mandatory return

I picked (2) seems (1) probably has performance implications
TODO

[ ] When upgrading to sea-query 0.24.0 (which introduces the on-conflict support), I had to add window: None to a few functions. Is this correct? (see https://github.com/SeaQL/sea-query/pull/271)
[ ] When using do nothing, we can't call after_save since nothing was saved. Is this okay?
[ ] I'm not sure what to do about testing since it seems the insert functions are not directly tested either. Should it be done as an integration test in tests/relational_tests?
[ ] Add documentation for insert_or

I rebased on top of #673 to fix the bug with the 0.24.0 upgrade

@billy1624 I'm concerned that the performance implications of doing this probably aren't desired for cases where ON CONFLICT DO NOTHING is used (the only case where nothing is returned)
Rationale
ON CONFLICT can only be used on unique constraints. Although there are some tables with multiple unique constraints, most of the time your unique constraint is the primary key (possibly a composite key)
Example: A database with 3 tables:

Persons table
Jobs table
Some table that maps the many-many relation of <PersonId, JobId>

If you want to insert a new <PersonId, JobId> pair, you can just insert with an ON CONFLICT DO NOTHING because if row already exists, you already know all the data in the row so you don't care about the return value. Having sea-orm do a 2nd query to get the row provides no additional information and double the number of database roundtrips required

If you want to insert a new <PersonId, JobId> pair, you can just insert with an ON CONFLICT DO NOTHING because if row already exists, you already know all the data in the row so you don't care about the return value. Having sea-orm do a 2nd query to get the row provides no additional information and double the number of database roundtrips required

Make sense. I think the return type of insert_or is confusing, Result<Option<Model>, ...>, as you have said the return values doesn't matter, we could just return Result<(), ...>. However, one can't access the inserted ActiveModel anymore as it has been moved because the signature of insert_or<'a, C>(self, ...).
async fn insert_or<'a, C>(self, db: &'a C, on_conflict: &OnConflict) -> Result<Option<<Self::Entity as EntityTrait>::Model>, DbErr>

Hey @SebastienGllmt, sorry for the delay.
The ON CONFLICT features has been added to SeaORM on another PR:

https://github.com/SeaQL/sea-orm/pull/791

Thank you so much for the contributions. And do let us know if you have idea on improving it further :)


feat(FSD-2271): Update Coney

Accidentally pushed!

Hi @yolo-vikram! I can move the package/repo to the Yolo Group so you don't need the fork and the project gets better maintenance.
Would it be interesting to you?

Hey,
Thanks for reaching out. Yes, we are indeed interested in taking over the
maintenance of Coney. Let me know if anything is required from our side.
Best Regards,
Vikram
On Thu, Jun 20, 2024 at 10:44 PM Sasha Fomin @.***>
wrote:

Hi @yolo-vikram https://github.com/yolo-vikram! I can move the
package/repo to the Yolo Group so you don't need the fork and the project
gets better maintenance.
Would it be interesting to you?
—
Reply to this email directly, view it on GitHub
https://github.com/llxff/coney/pull/17#issuecomment-2181406537, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BGU2C6DHMVFJHZLFWKSUZQDZIMWIPAVCNFSM6AAAAABJRO33WWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBRGQYDMNJTG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Vikram Rathore
Elixir Developer
Mob: +372 55 643855
Email: @.***

Cool, then I need the GitHub and hex.pm organisation names

Hex: https://hex.pm/dashboard/orgs/coingaming
GitHub: https://github.com/coingaming
On Fri, Jun 21, 2024 at 10:48 AM Sasha Fomin @.***>
wrote:

Cool, then I need the GitHub and hex.pm organisation names
—
Reply to this email directly, view it on GitHub
https://github.com/llxff/coney/pull/17#issuecomment-2182197457, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BGU2C6H5RB23EUV2WU4LIJLZIPLC7AVCNFSM6AAAAABJRO33WWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBSGE4TONBVG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Vikram Rathore
Elixir Developer
Mob: +372 55 643855
Email: @.***

I transferred the package to Coingaming but can't transfer the repo because I don't have access to the org. I added you as a collaborator so you could do it yourself 👍

I'm sorry for the inconvenience. I am unable to transfer the repo because I
don't have access to settings. I appreciate if you transfer it to me then I
can make the transfer to Coingaming.
On Fri, Jun 21, 2024 at 3:04 PM Sasha Fomin @.***>
wrote:

I transferred the package to Coingaming but can't transfer the repo
because I don't have access to the org. I added you as a collaborator so
you could do it yourself 👍
—
Reply to this email directly, view it on GitHub
https://github.com/llxff/coney/pull/17#issuecomment-2182621758, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BGU2C6A65S2334HBXD57Y53ZIQJDLAVCNFSM6AAAAABJRO33WWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBSGYZDCNZVHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Vikram Rathore
Elixir Developer
Mob: +372 55 643855
Email: @.***

I've sent a request :+1:

Received and transferred to the coingaming. Thanks a lot.
On Fri, Jun 21, 2024 at 4:55 PM Sasha Fomin @.***>
wrote:

I've sent a request 👍
—
Reply to this email directly, view it on GitHub
https://github.com/llxff/coney/pull/17#issuecomment-2182804375, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BGU2C6G6ZK7IRTE7DUHKDQDZIQWGDAVCNFSM6AAAAABJRO33WWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBSHAYDIMZXGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Vikram Rathore
Elixir Developer
Mob: +372 55 643855
Email: @.***


readme: fix message type in Notification example

accordingly to spec Notification message should have type field equal to "notif.v1"

We haven't finished/concluded on if we need notif or not (it is not
implemented in our code today) so I'm going to remove it in the next update
soon.
On Sun, Jun 25, 2023 at 4:53 PM Dmitry Gurovich @.***>
wrote:

accordingly to spec Notification message should have type field equal to
"notif.v1"
You can view, comment on, or merge this pull request online at:
https://github.com/eclipse-uprotocol/uprotocol-spec/pull/7
Commit Summary

89b0c40
https://github.com/eclipse-uprotocol/uprotocol-spec/pull/7/commits/89b0c404f3eeb0f4539a0ea36c341b58ca933f29
readme: fix message type in Notification example

File Changes
(1 file https://github.com/eclipse-uprotocol/uprotocol-spec/pull/7/files
)

M up-l2/messages/v1/README.adoc
https://github.com/eclipse-uprotocol/uprotocol-spec/pull/7/files#diff-2c566f079a340eeaf2af8de47c42a988199eab23ca5d9c31afbc98bc9ca2113d
(4)

Patch Links:

https://github.com/eclipse-uprotocol/uprotocol-spec/pull/7.patch
https://github.com/eclipse-uprotocol/uprotocol-spec/pull/7.diff

—
Reply to this email directly, view it on GitHub
https://github.com/eclipse-uprotocol/uprotocol-spec/pull/7, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDANOVPPJRQI5ZEXUJTOKLXNCQODANCNFSM6AAAAAAZTLQYRE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
IMPORTANT: My e**mail address has changed to @.***
Please update your contact information, thank you.


Removed unneeded http header

For the Committer

[ ] I made sure that the site looks great and functions perfectly live
[ ] I ran splell check
[ ] I'm ready for these changes to be made live

For the Reviewer
General Review

[ ] All changes/updates requested were intentionally changed or added (no extraneous file or partial updates)
[ ] The live rendered page behaves and looks like intended.
[ ] All links work as intended. (click every link to make sure that it takes the user to the expected place).
[ ] The markdown was rendered to HTML as intended. (Tables look right, code samples are gated properly).
[ ] Any style or CSS changes are tested on multiple different pages to ensure nothing unexpected broke or changed.
[ ] I proof-read the live site (gitbook serve) and there are no oblivious splelling or grammer misteaks.

Gitbook Specific

[ ] Any new documentation pages have been added to the SUMMARY.md file so they are rendered to HTML.
[ ] Any links to other pages within this documentation use relative links ([read more about ...](guides/voice/voicemail.md)).
[ ] Gitbook can install and build the documentation (gitbook install & gitbook build)

Code Specific

[ ] All code has been tested against the live API.
[ ] All code can be run without throwing errors or new warnings.
[ ] All code is formatted correctly and consistently (spaces, tabs).
[ ] All code is legible and idiomatic to the language.
[ ] All code uses sensical method, function, and variable names.
[ ] All code samples use the appropriate syntax highlighting.
[ ] Any examples re-use same phone numbers, uuids, variable names, etc... throughout (IE don't have something like {from: '+19191231234', to: '+19191231234'} unless it's meant to show the same phone number calling/texting itself ).

TL;DR

[ ] I did these things
[ ] I'm ready for these changes to be made live

 Usabilla Feedback Item - This implies the header structure is listed but it is not.

Preview Changes at:
http://bw-apdocs-remove-unneeded-http-header.s3-website-us-east-1.amazonaws.com/


Enable --Xbonsai-limit-trie-logs-enabled by default

PR description
Enable --Xbonsai-limit-trie-logs-enabled by default, unless sync-mode=FULL.
More info: https://wiki.hyperledger.org/display/BESU/Limit+Trie+Logs+for+Bonsai
When sync-mode=FULL and data-storage-format=BONSAI you get a config validation error at startup...
besu --sync-mode=FULL --data-storage-format=BONSAI
2024-06-06 17:36:12.806+01:00 | main | INFO  | Besu | Starting Besu
2024-06-06 17:36:13.027+01:00 | main | ERROR | Besu | Failed to start Besu
...
Cannot enable --Xbonsai-limit-trie-logs-enabled with sync mode FULL

I will promote to a Stable option in a separate PR.
This option has been tested on our canaries and by the community since https://github.com/hyperledger/besu/releases/tag/24.3.0
Added a fallback value for the option otherwise specifying --Xbonsai-limit-trie-logs-enabled on the command line, without a value, toggles it back off again.
The minimalist-profile has been updated from bonsai-historical-block-limit=128 to bonsai-historical-block-limit=512 to avoid further code changes and because I believe there is only a ~60MB difference so using 128 has limited value, see https://github.com/hyperledger/besu/issues/6560#issuecomment-1953928253
I will conservatively set Xbonsai-limit-trie-logs-enabled=false in the enterprise profile for now as not sure it is desirable.
Fixed Issue(s)

Fixes https://github.com/hyperledger/besu/pull/6560
Thanks for sending a pull request! Have you done the following?

[x] Checked out our contribution guidelines?
[x] Considered documentation and added the doc-change-required label to this PR if updates are required.
[x] Considered the changelog and included an update if required.
[x] For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Commit LGTM - thanks @siladu for the last minute fixes.

FYI @siladu in PR https://github.com/hyperledger/besu/pull/7140 I was planning to change the fail-on-start behaviour if FULL sync mode is enabled and bonsai-trie-log-pruning-enabled is set, and instead set bonsai-trie-log-pruning-enabled to false if sync mode is FULL (with a log message to state that the default has been overridden).
Let me know if you have any concerns about that change - maybe via comments in that PR?


Missing total=False on some TypedDict with boto3-stubs>=1.28.3

Describe the bug
Some TypeDicts are not total=False anymore. With mypy-boto3-secretsmanger==1.28.3 the flag is gone in the TypeDef.
To Reproduce
Steps to reproduce the behavior:

Install mypy-boto3-secretsmanger==1.28.3
Run mypy/pyright on the following code sample

from mypy_boto3_secretsmanger.type_defs import RotationRulesTypeTypeDef

rules: RotationRulesTypeTypeDef = {"AutomaticallyAfterDays": 365}
...

Actual output
error: Missing keys ("Duration", "ScheduleExpression") for TypedDict "RotationRulesTypeTypeDef"  [typeddict-item]

Expected output
no error

Same issue seen with S3 for multiple TypedDicts, specifically CORSRuleTypeDef, ServerSideEncryptionByDefaultTypeDef, ServerSideEncryptionRuleTypeDef, LifecycleRuleTypeDef, LoggingEnabledTypeDef, TopicConfigurationTypeDef, MetricsConfigurationTypeDef.

Thank you for the report!
Looks like the issue is related to a new logic for marking output TypedDict shapes as total. However, some shapes are used both as input and output. The proper fix would be to generate two TypedDicts (e.g. RotationRulesTypeTypeDef and RotationRulesTypeOutputTypeDef).
I will take a look.

Fixed in mypy_boto3_builder 7.14.7 release. Please let me know if it works as it should.
I also published new packages with the hotfix included:

mypy_boto3_cognito_idp_package 1.28.3.post1
mypy_boto3_connect_package 1.28.3.post1
mypy_boto3_datasync_package 1.28.3.post1
mypy_boto3_dms_package 1.28.3.post1
mypy_boto3_ec2_package 1.28.3.post1
mypy_boto3_fsx_package 1.28.3.post1
mypy_boto3_iam_package 1.28.3.post1
mypy_boto3_mediatailor_package 1.28.3.post1
mypy_boto3_personalize_package 1.28.3.post1
mypy_boto3_proton_package 1.28.3.post1
mypy_boto3_s3_package 1.28.3.post1
mypy_boto3_sagemaker_package 1.28.3.post1
mypy_boto3_secretsmanager_package 1.28.3.post1
mypy_boto3_package 1.28.3.post1
boto3_stubs_package 1.28.3.post1
boto3_stubs_lite_package 1.28.3.post1

@vemel
The post1 is a breaking change for us. I started getting this error after the post1 version has been pushed:
    from mypy_boto3_ec2.type_defs import SubnetTypeDef
ImportError: cannot import name 'SubnetTypeDef' from 'mypy_boto3_ec2.type_defs'

@ecs-jnguyen Makes sense. I came up with a non-conflicting solution. I will release it in a few hours. Also, I am going to release post2 to affected packages.

@ecs-jnguyen Just released mypy-boto3-ec2 1.28.3.post2 with the fix included. Please test it and let me know if it works as it should.
Also, many other packages were updated, check 7.15.0 release notes.

LGTM. Thanks for your fast response and fixes.


test #4687 CI

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #4744 (6c186bc) into master (dcd96cc) will decrease coverage by 0.04%.
The diff coverage is 63.63%.

@@             Coverage Diff              @@
##             master    #4744      +/-   ##
============================================
- Coverage     65.50%   65.46%   -0.04%
+ Complexity     8151     8146       -5
============================================
  Files          1135     1135
  Lines         33236    33243       +7
  Branches       2967     2965       -2
============================================
- Hits          21771    21764       -7
- Misses         9735     9743       +8
- Partials       1730     1736       +6

Impacted Files
Coverage Δ

...a/org/apache/shenyu/admin/model/dto/PluginDTO.java
62.16% <ø> (ø)

...u/plugin/logging/common/AbstractLoggingPlugin.java
0.00% <0.00%> (ø)

.../shenyu/common/dto/convert/rule/RewriteHandle.java
47.36% <16.66%> (-12.64%)
:arrow_down:

...rg/apache/shenyu/plugin/rewrite/RewritePlugin.java
63.15% <66.66%> (-9.07%)
:arrow_down:

...ava/org/apache/shenyu/common/enums/PluginEnum.java
100.00% <100.00%> (ø)

...pache/shenyu/plugin/base/AbstractShenyuPlugin.java
57.81% <100.00%> (ø)

...u/plugin/base/condition/data/URIParameterData.java
100.00% <100.00%> (ø)

...nyu/plugin/global/DefaultShenyuContextBuilder.java
80.00% <100.00%> (+0.83%)
:arrow_up:

...in/logging/common/utils/LogCollectConfigUtils.java
74.41% <100.00%> (+0.60%)
:arrow_up:

...rg/apache/shenyu/plugin/metrics/MetricsPlugin.java
47.82% <100.00%> (ø)

... and 6 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Overlapping components

First off, thank you for this great project, it's awesome. I used it today and realized that other inputs of Datepickers overlap other Datepciker like this. I dunno if this is because of z-index or what. any ideas?

Hey @HosseinAlipour, can you provide a repro?

Hi Hossein,
You can easily fix this problem by giving a custom className to date picker or calendar using wrapperClassName or calendarClassName(by overriding z-index)

overriding z-index didn't help, I will provide a reproducible repo until night.

@HosseinAlipour if possible, provide an example on CodeSandbox

here you go

@HosseinAlipour as I told you, you can simply fix this by wrapperClassName: Here's the SandBox 😊

@HosseinAlipour as I told you, you can simply fix this by wrapperClassName: Here's the SandBox blush

I think it's better to set default z-index of .DatePicker__calendarContainer instead of wrapper.
default z-index of wrapper makes same problem on different situations
"از:" field is my custom renderInput

and I fixed with this css:
.DatePicker {
	z-index: initial !important;
}

.DatePicker__calendarContainer {
	z-index: 100;
}


DRUM-KIT MODIFIED

Hey @swapnilsparsh this is modified Drum-Kit
Fix #218

ok done, please check

ok done, please check

Remove the previous folder and keep the 01-drum kit only


Use nr-rrc dissector instead of lte-rrc

Names for dissectors were found here: https://gitlab.com/wireshark/wireshark/-/blob/00b86cf64d638e332228ed6433fec82366b14f90/epan/dissectors/packet-pdcp-nr.c#L2966

I will test it tomorrow.


enable flash detection

I am trying to enable flash in Firefox 52 like I changed the "plugin.scan.plid.all" to true and "plugin.state.flash" to 2 but flash in not detected in net.
I see the flash plugin in firefox addon page and is always activated. I am using the latest flash version.
It's there anything else, which I have to make so I can have enabled flash in firefox?

privacy.resistFingerprinting hides the contents of navigator.plugins - might be that, IDK

@earthlng thank you. Flash is working now.

ermmagerrrrrd... issue #666 was about Flash :imp:


feat(sozo): automatically authorize models to migrated systems based on models specified in overlays

fix: #1819

Let's follow up that with discussion for #1921. 👍


[0.8.0 Beta] fa_path.lua not found?

Running downlord's FAF client v0.8.0-beta from https://github.com/FAForever/downlords-faf-client/releases/download/v0.8.0-beta/dfc_windows_0_8_0-beta.exe
After patching, linking my steam account, locating my FA install directory I can launch and play custom games from the 'play' tab but I cannot launch Co-Op games.  I'm greeted by the following error when attempting to launch one, regardless of level selection.
Failed to setup initial search path.

Program : C:\ProgramData\FAForever\bin\ForgedAlliance.exe
Cmd line arguments : /init init.lua /nobugreport /log C:\ProgramData\FAForever\logs\game.log /gpgnet <IP_ADDRESS>:64566 /mean 1500.0 /deviation 500.0 /savereplay gpgnet://<IP_ADDRESS>:15001/8827288/Teledahn.SCFAreplay /country CA /numgames 0

Callstack:
	Unknown symbol (address 0x008cef50)

Last 100 lines of log...

warning: Running "C:\ProgramData\FAForever\bin\init.lua" failed: cannot read C:\ProgramData\FAForever\bin\..\fa_path.lua: No such file or directory
         stack traceback:
         	[C]: in function `dofile'
         	C:\ProgramData\FAForever\bin\init.lua(2): in main chunk

No mods or other changes.  Starting from current steam version of Forged Alliance and installing FAF with the above (Downlord 0.8.0 beta) client.  As the log states 'fa_path.lua' does not exist in the directory FAForever\bin.
Is there a known resolution to this?  Can I create the file myself?

Sorry for the inconvenience and thank you for reporting. This will be fixed in version 0.9.0-beta which I'm planning to release today.


failure to load script

Please open an issue on journalgd and please include more information than just an image.


Arduino: Add the "create text with" block

Currently this block is not implemented for Arduinos nor for Arduino like plugins. If one would like to collect sensor data this block is necessary to label and structure the measurement data e.g. for the "write serial" function.

It is possible to use the "append text" block, but it makes the program very complicated and the workaround is not easy to understand.

air, i would love to work on this issue.. so please assign me..

Hey, you can work on it without having it assigned. Did you get the project up and running yet? We have some documentation in the README.md and wiki.

Tested


Create better JavaDocs

Edit the JavaDocs so that these are better to read and more information is carried out.
Also there are no warnings anymore about missing comments or missing arguments.
To generate these JavaDocs the user needs to use the Maven JavaDocs plugin and just use mvn javadoc:javadoc. When created the JavaDocs will just generate in HTML format.

Check if there are any problems with it and then merge.


storage plugin: Container sometimes stuck in 'activating' state

Rancher Version: master
Docker Version: 1.12.3
OS and where are the hosts located? (cloud, bare metal, etc): n/a
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB) n/a
Environment Type: (Cattle/Kubernetes/Swarm/Mesos) cattle
Steps to Reproduce:

Create a cattle environment and register 1+ hosts
Create a nfsv4 server that is reachable by registered hosts
Launch the rancher-nfs template with host/export configuration
Create a few stacks with rancher-nfs volumes defined. This sample may be used.

Results: Some containers are in starting/activating state. Behind the scenes, the containers and their volumes are functional.
Expected: Containers are in running state.

What does the API show versus UI?

API shows state=starting, UI shows the same

@cjellick rancher-nfs, rancher-efs and rancher-ebs are all afflicted by this bug. It only sometimes happens.
If the container gets stuck, there will be 2 rows for a single volume, one in Inactive state and another in Detached state. This can be seen on the storage screen. Deleting this container will cause the Inactive volume to be deleted - the deletion logic is not triggered. Deleting the other Detached volume doesn't trigger the deletion logic either.
If the container enters running state, there is only 1 row for the volume in Active state. Deleting this container triggers the deletion logic (tested in rancher-ebs).

Figured this one out, changes are part of https://github.com/rancher/storage/pull/18/files. I plan to finish the refactor and test everything at once.

Duplicate of https://github.com/rancher/rancher/issues/3150


Open binary files directly without displaying the "Do you want to open it anyway?"

🚨 The issue tracker is not for questions 🚨
Is there any way to disable the warning when trying to open a binary file, i.e., the "Do you want to open it anyway?" warning.
I have LaTex-Workshop installed which can view PDFs but I would have to click on the warning to get a PDF viewed. It would be nice if could just disable this warning.

Not currently but the feature request falls under #82115


Sidekiq 7 limit not enforced

Hi,
Thanks for your work, the problem of #142  still seems to be present, here is my configuration.
Gemfile :
gem 'sidekiq'
gem 'sidekiq-limit_fetch'

Gemfile.lock :
sidekiq (7.0.2)
      concurrent-ruby (< 2)
      connection_pool (>= 2.3.0)
      rack (>= 2.2.4)
      redis-client (>= 0.11.0)
    sidekiq-limit_fetch (4.4.0)
      sidekiq (>= 6)

Sidekiq.yml :
:concurrency: 10
:max_retries: 0

:queues:
  - default
  - scan

:limits:
  default: 5
  scan: 2

The limit is well at 2 :
irb(main):001:0> Sidekiq::Queue['scan'].limit
2023-01-06T11:07:51.322Z pid=26 tid=13e6 INFO: Sidekiq 7.0.2 connecting to Redis with options {:url=>"redis://redis:6379/1", :size=>5, :pool_name=>"internal"}
=> 2

But if I launch 10 jobs, 10 workers are launched. It works as expected with Sidekiq 6 (6.5.8)
Let me know if you need more informations or if I can make more tests.
Regards

Maybe because of this: https://github.com/sidekiq/sidekiq/blob/main/docs/7.0-Upgrade.md#capsules

Ah, interesting. So it looks like Sidekiq basically has limiting built in, which is great to see.

Will capsules also work when having multiple Heroku workers each running a separate Sidekiq instance with concurrency 1? Since limiting through capsules seems to be focussed on threads within one Sidekiq instance, while with sidekiq-limit_fetch you can set a maximum amount of workers per queue.

Will capsules also work when having multiple Heroku workers each running a separate Sidekiq instance with concurrency 1? Since limiting through capsules seems to be focussed on threads within one Sidekiq instance, while with sidekiq-limit_fetch you can set a maximum amount of workers per queue.

@deanpcmad can you say anything about this? We are currently wondering whether to update sidekiq-limit_fetch or switch to Sidekiq Capsules.

Personally, I've moved to Sidekiq Capsules in one of my apps as it does what I need, which is limiting the number of jobs that execute in a queue

Personally, I've moved to Sidekiq Capsules in one of my apps as it does what I need, which is limiting the number of jobs that execute in a queue

Thanks for the reply. I think your needs are different then than ours. Am I correct in assuming you only have a single worker/server with a single Sidekiq process (but multiple threads) then? And you use capsules to limit the amount of threads certain queues have (while other queues have more threads available)?
In our situation we run multiple Heroku workers (amount is autoscaled) with a (single) Sidekiq process with the same configuration (concurrency 1 so a single thread per Heroku worker). We removed the limit_fetch gem and tried Sidekiq 7's capsules to see if we could limit the amount of concurrent jobs for some specific queues, but I did not work. As I feared, capsules only work to limit the concurrency within a single Sidekiq process, but not over multiple Sidekiq processes (on different servers). When I used capsules to say for example the heavy queue has concurrency 1, each of the Heroku workers had single thread to pick up jobs from the heavy queue next to a number of threads (default 5) to pick up jobs from the other queues. So the concurrency for the heavy queue would equal the amount of Heroku workers present at that moment, meaning we could still have multiple heavy jobs running at the same time (on different workers). So I'm afraid Capsules isn't a feasible solution for us, at least not without rethinking our complete Heroku sidekiq configuration and autoscaling set-up and maybe introducing extra (read) databases to limit/spread the load on our database.
Long story short: we still need something like sidekiq-limit_fetch to limit the concurrency of certain queues over all processes/servers. I tried updating both sidekiq (7.2.0) and sidekiq-limit_fetch (4.4.1) to the latest versions and it seems to still work for us. It makes sure only one Heroku worker picks up jobs from the super_heavy queue, while we have some available for the heavy queue and more for the other queues.
@JoshuaMart Not sure why it doesn't work in your set-up. Maybe it only works for us because we have concurrency of 1 in our sidekiq.yml for our global configuration (and use multiple workers to scale horizontally instead of threads).
@deanpcmad could you say anything about the continuity of the sidekiq-limit_fetch gem? Are you the only maintainer currently? And are you stopping maintenance now that you no longer need it?
Ps. I also found the sidekiq-throttled gem which also seems to solve this problem. Unfortunately however, it has no ActiveJob integration at all it seems. We use ActiveJob so it is not really an option for us, but maybe it is for others who are (or want) to use Sidekiq::Job classes.

Thanks for the reply. I think your needs are different then than ours. Am I correct in assuming you only have a single worker/server with a single Sidekiq process (but multiple threads) then? And you use capsules to limit the amount of threads certain queues have (while other queues have more threads available)?

Yep, I just use a single server. And with SolidQueue being released, I may end up moving to that instead.
I'm still happy to maintain this gem though. I just am unable to reproduce the issue. If anyone can reproduce it and create a PR, I'd be happy to merge and create a release.

@kreintjes I think your hypothesis is correct. My use case consists of a single Sidekiq process with multiple threads, processing several queues and limit_fetch was used to process one of the queues strictly sequentially (by limiting concurrency to 1 with limit_fetch) without having to run multiple Sidekiq processes.
This worked with Sidekiq 6 and broke in Sidekiq 7, so ended moving to the capsules.
Thank you for the tips and your work on this project guys!


chart-sync fails when user renames variables

If someone renames short name of a variable, e.g. from dummy_a to dummy_b and modifies a chart which uses that variable, then ETL deploy will fail after merging the staging server.
The way ETL works is that it adds variable dummy_b and then tries to remove unused variable dummy_a. The problem is that the chart hasn't been synced yet and still depends on dummy_a, hence cannot be deleted and ETL fails with the error message
ValueError: Variables used in charts will not be deleted automatically:

I don't have a good solution, but here are some options:

Change that error to a warning. ETL would finish and chart-sync would swap the variable. The only problem is that "ghost" variable would still be in Admin until next ETL run of that dataset
Make ETL deploy fail, but still run chart-sync
Separate "cleanup_ghost_variables" into a step after both ETL and chart-sync

Fixed by https://github.com/owid/etl/pull/2890


Hardware requirements to compile this project (training, evaluating)

I tried to run the  evaluation script, but a notification of fully consumed memory appeared and then the process crushed immediately.
Could you guys please tell me about the required hardware resources (RAM, CPU, GPU) to compile this project?
I run the project on a computer of 10 cores and with 16 GB RAM .

Hello ! It really depends on your input. A few GB will be enough to train a model with a few texts, like a demo. But if you have dozens of long texts, you will need far more than 16 GB of memory.
The requirements are really a factor of (1) the number of texts, (2) the length of the texts and (3) the length of the sentences in the texts (look especially for very long sentence). If you have memory issues, try to limit the length of the sentences (try to split the longest sentences) and the number of texts. You can make some trials by starting with a few texts and then adding more and more texts (and same for the sentence length).
Of course, this apply to the GPU memory has well if you use a GPU.
The speed of the CPU is not really important even if you don't use a GPU, provided you have enough time (of course, a few minutes of GPU will translate into hours or days of CPU, but this will not make the system crash, it will just take a very long time).
For the Democrat project, for example, I think we usually used at least 32 GB of memory (at least for the tests) but we had to upgrade to more memory to train the final model.

Hello,
You explained everything Mr. Bruno thank you so much
Best regards,
Le ven. 22 avr. 2022 à 6:42 a.m., Bruno Oberle @.***> a
écrit :

Hello ! It really depends on your input. A few GB will be enough to train
a model with a few texts, like a demo. But if you have dozens of long
texts, you will need far more than 16 GB of memory.
The requirements are really a factor of (1) the number of texts, (2) the
length of the texts and (3) the length of the sentences in the texts (look
especially for very long sentence). If you have memory issues, try to limit
the length of the sentences (try to split the longest sentences) and the
number of texts. You can make some trials by starting with a few texts and
then adding more and more texts (and same for the sentence length).
Of course, this apply to the GPU memory has well if you use a GPU.
The speed of the CPU is not really important even if you don't use a GPU,
provided you have enough time (of course, a few minutes of GPU will
translate into hours or days of CPU, but this will not make the system
crash, it will just take a very long time).
For the Democrat project, for example, I think we usually used at least 32
GB of memory (at least for the tests) but we had to upgrade to more memory
to train the final model.
—
Reply to this email directly, view it on GitHub
https://github.com/boberle/cofr/issues/3#issuecomment-1106065057, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASL5JZ6GD7QL72RXZZXLSILVGJC4NANCNFSM5T674GCQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Deleting optional string doesn't work with Datastore

Describe the bug
I save image on S3 and the url for the image on Dynamodb with optional String. When I delete image I tried to set it to undefined and I get following error
Field imageKey should be of type string, undefined received. undefined
Amplify CLI Version
4.17.1
To Reproduce

npx create-react-app test --use-npm --template typescript
amplify init
amplify add auth default everything
amplify add api Then add following schema

type Product @model
  @auth(rules:[
    {allow: owner}
  ]) {
  id: ID!
  owner: String!
  name: String!
  imageKey: String
}

Then I had image url saved in imageKey Now I deleted the image so I tried to set imageKey to undefined
const original = await DataStore.query(Product, id)

const results = await DataStore.save(
            Farmer.copyOf(original, updated => {updated.imageKey = undefined})
        )

I got following error
Field imageKey should be of type string, undefined received. undefined
Expected behavior
It should delete the key and set it as undefined
Desktop (please complete the following information):

OS: Ubuntu 18.04 with Windows WSL2
Node Version. 12.16.1

Additional context
I also tried with setting imageKey to '' string with nothing I also got another error. I will post it soon.

@apoorvmote Have you tried using null?

@ammarkarachi yes and no.

Yes I set updated.imageKey = null
No I didn't run because eslint gave me error with red squiggly and told me not to save it.

I tried it regardless. I got this error.
Type 'null' is not assignable to type 'string | undefined'

So the workaround is I set updated.imageKey = 'placeholder' And I have to check if imageKey is either undefined or placeholder then I know if image is null or not.
Technically it works however I still get following error in console.
DataStore - The source object is not a valid model
I have console logged the source object. It is absolutely valid. And even after the error the datastore makes graphql request and saves new object. So it does make correct update. However I still get this error in console.


not working when opening a new buffer with :vsplit $MYVIMRC

Hi, I think everything is in the title :)
if I'm working on a project and I want to quickly edit my init.vim I do :vsplit $MYVIMRC
which opens the init.vim in ~/.conf/nvim/init.vim which simlinks to another location

actually the issue was that I was opening a file that is a simlink, the confusion came from the fact that nerdtree was able to follow this simlink so when I was opening the tree I could find the .git folder. I installed the vim-symlink plugin and it solved the issue.


Better "batch" processing when reaching live

Right now, we always write batches containing 1000 blocks of content (maybe configurable value, I'm not sure). This is problematic as we reach live segments of the chain, it means data freshness slowly drift and at max will be 1000 blocks off (~250 min).
We need to update this to be near live. First part will be to think about what would be the solution here. Here two possibles things I thought of:

Change the batch flushing to be 1000 blocks (configurable) or each 15s (configurable)
We fix the problem rather easily with this solution but it's still not perfect, and drift will be 15s, so could be 2 blocks off. Also, for fast pace chain, this should be moved to 1s.
Based on block's timestamp, if near live, we change the batch write to be 1
The problem with this is that we Substreams response would need to contain the full block timestamp which I think it don't have today. So we would need to decide what to do.
Track live blocks using a "side" Firehose connection
We could do the tracking differently by having a "side" connection that tell us which block is actually live. Increase the load of the production server + operators will need to have Firehose running.

Once the solution is decided, implement it and properly document it!

We should apply the same thing to mongodb right away @colindickson


container issues: file mode in /data/bind/etc and db.root is very old

Hi. Thans for taking the time to make man of the docker container issues you use available. I'm using a couple of these as I learn the container environment.
I notice with the bind setup a couple of issues:

db.root is very old, dated 2016. It would be good to either update the settings or to maybe attempt to refresh them when the container is started. That is have a reasonably new version but the container start would try to pull a new version and if that's successful update the current file and reload the configuration.
file permissions in /data/bind/etc seemed to show most files as being executable. That makes no sense for files. Please adjust any scripting which setups file permissions on container startup to make these files something like mod 640 or equivalent.

I didn't really have time to look at this properly but a suggestion would be something like: https://gist.github.com/sjmudd/17dac1e6bec9d7c73a6083d4a5e91f1a.
Docker build of your current repo seemed to give me an error:
Reading state information...
E: Version '1.8*' for 'webmin' was not found
The command '/bin/sh -c rm -rf /etc/apt/apt.conf.d/docker-gzip-indexes  && apt-get update  && DEBIAN_FRONTEND=noninteractive apt-get install -y       bind9=1:${BIND_VERSION}* bind9-host=1:${BIND_VERSION}* dnsutils       webmin=${WEBMIN_VERSION}*  && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100

I don't have time now to follow up on this as still rather new with the container world. Hopefully the suggested patch or similar should fix one of the issues.


Add error server_address_mistmatch with The Things Stack CLI to Troubleshooting CLI documentation

Summary

The Things Stack CLI can be used for advanced actions. Accessing The Things Stack CLI requires the correct CLI configuration with the server addresses. After that users can perform actions on the entities that are registered on the same server address. If the users try to perform actions on the other server address, then the error error:cmd/ttn-lw-cli/commands:end_device_server_address_mismatch  will be observed. Please document the error and resolution in The Things Stack CLI troubleshootingguide.
Why do we need this ?

To assists users in resolving the issues on their own while using The Things Stack CLI.
What is already there? What do you see now?

Troubleshooting CLI

What is missing? What do you want to see?

Add the error error:cmd/ttn-lw-cli/commands:end_device_server_address_mismatch (Network/Application/Join Server address mismatch) to the Troubleshooting CLI documentation.
How do you propose to document this?

Insights:

Generally, the error error:cmd/ttn-lw-cli/commands:end_device_server_address_mismatch (Network/Application/Join Server address mismatch) occurs when the user tries to perform the actions on entities (i.e., devices, gateways, users, etc) using the CLI with the incorrect server address configured in the CLI configuration file. For example, if the user configured the CLI with the eu1 cluster server address and if they try to access the entities on the au1 cluster, then the error will be observed due to the mismatch of server addresses in the configuration file.
While configuring the server address in the CLI configuration, users need to ensure the correct cluster address to perform any operations on the entities registered in that specific cluster. So if the users want to perform operations on the entities registered in the eu1 cluster then they need to ensure the CLI configuration with the eu1 cluster.
Also, it is important to note that the Identity Server address in the CLI configuration should always be the eu1 cluster irrespective of the cluster that the user trying to access the entities registered on.

Can you do this yourself and submit a Pull Request?

No, @nejraselimovic

@Siva-7482: Why don't you just create a PR for this? All the required information is there in the issue description. cc: @ymgupta

Sure, @KrishnaIyer. Please review the below PR.
Ref: https://github.com/TheThingsIndustries/lorawan-stack-docs/pull/1309


Adds design system components and warning text

Context
We don't have a good way to put warnings. The Design System offers us this, among other things which will be useful in future.
Changes proposed in this pull request
Adds GOV.UK Design System components and implements a warning symbol by means of testing on the "Payment flow" page.
Guidance to review
Preview at https://govukpay-hammertime.cloudapps.digital/payment_flow_overview/#payment-flow

Going to reopen this with a better approach


Adding example for speaker identification with web assembly

Is there any reason that there isn't an example of deploying speaker identification for web assembly?

The only reason is that we don't have enough time. Would you like to contribute?
We have WebAssembly example for speaker diarization. Please see
https://github.com/k2-fsa/sherpa-onnx/tree/master/wasm/speaker-diarization
@truongdo


polygon winding order

I'm trying to use this with polygons to determine the winding order. However, it seems to be suited for a small number of points (triangles and such mostly?).
In Chrome, the following with a larger set of points (e.g. 20+) tends to crash the browser:
var orientation = require('robust-orientation')
orientation.apply(orientation, path)

Is there a module better suited for this?

This computes the orientation of d+1 points in d dimensions.  For a polygon, you would need to integrate over each triangle and then test the sum of all the areas to get the orientation.


Feature/azure

This PR adds Azure OpenAI generator support as garak/generators/azure.py.
To use this generator, put your Azure OpenAI API key in
an environment variable called AZUREAI_API_KEY. Put your Azure OpenAI endpoint
in an environment variable called AZURE_ENDPOINT

Thanks! Could you sign the DCO? Then we'll review :)

OK! Say something if there's anything we can do to help.

Hi @Sunforger !
We've added new OpenAI API compatibility which may be useful for things like Azure. There's an example, much simpler class doing this now; see the NIM generator for an example of how to structure it: https://github.com/leondz/garak/blob/main/garak/generators/nim.py
If you're still working on this, please use the new lightweight pattern - it might only be a couple of lines.

Thank you for the submission, closing in favor of #817