text:
[Bug]: ZSH fails to install

Feature id and version
ghcr.io/devcontainers-contrib/features/zsh-plugins:0
Devcontainer base Image
ubuntu:22.04
What happened?
My dev container won't come up using the ZSH plugin. Before I begin, just want to say ❤ thanks to this repo's maintainers! 😄
Steps to reproduce
devcontainer.json
{
	"name": "Existing Docker Compose (Extend)",
	"dockerComposeFile": [
		"docker-compose.yml"
	],
	"service": "pocketknife",
	"workspaceFolder": "/workspaces",
	"features": {
		"ghcr.io/devcontainers-contrib/features/zsh-plugins:0": {},
		"ghcr.io/devcontainers/features/aws-cli:1": {},
		"ghcr.io/devcontainers/features/git:1": {},
		"ghcr.io/devcontainers/features/node:1": {},
		"ghcr.io/mpriscella/features/sops:1": {},
		"ghcr.io/devcontainers-contrib/features/apt-get-packages:1": {},
		"ghcr.io/devcontainers-contrib/features/curl-apt-get:1": {},
		"ghcr.io/devcontainers-contrib/features/npm-package:1": {},
		"ghcr.io/devcontainers-contrib/features/pipenv:2": {},
		"ghcr.io/devcontainers-contrib/features/wget-apt-get:1": {},
		"ghcr.io/eitsupi/devcontainer-features/jq-likes:1": {},
		"ghcr.io/guiyomh/features/vim:0": {},
		"ghcr.io/jungaretti/features/make:1": {},
		"ghcr.io/devcontainers/features/java:1": {}
	}
}

docker-compose.yml
version: '3'
services:
  pocketknife:
    container_name: pocketknife_dev
    image: ubuntu:22.04
    network_mode: host
    volumes:
      - ..:/workspaces:cached
      - $HOME/.aws:/root/.aws
      - $HOME/.ssh:/root/.ssh
    restart: always
    command: sleep infinity

With these placed inside a .devcontainer directory from a project's root, opening the project via VSCode causes a failure with the attached logs.
Question
One thing I don't understand is why the installer would expect anything to be at /root/.zshrc. Isn't the purpose of the plugin to install everything associated with ZSH? Maybe I'm misunderstanding the design though.
Relevant log output
> [dev_containers_target_stage 13/31] RUN chmod -R 0755 /tmp/dev-container-features/zsh-plugins_1 && cd /tmp/dev-container-features/zsh-plugins_1 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh:
#0 0.262 ===========================================================================
#0 0.262 Feature       : ZSH Plugins
#0 0.262 Description   : Install (Oh-My-)ZSH plugins
#0 0.262 Id            : ghcr.io/devcontainers-contrib/features/zsh-plugins
#0 0.262 Version       : 0.0.2
#0 0.262 Documentation : http://github.com/devcontainers-contrib/features/tree/main/src/zsh-plugins
#0 0.262 Options       :
#0 0.262     PLUGINS=""
#0 0.262     OMZPLUGINS=""
#0 0.262     USERNAME=""
#0 0.262 ===========================================================================
#0 0.269 sed: can't read /root/.zshrc: No such file or directory
#0 0.270 ERROR: Feature "ZSH Plugins" (ghcr.io/devcontainers-contrib/features/zsh-plugins) failed to install! Look at the documentation at http://github.com/devcontainers-contrib/features/tree/main/src/zsh-plugins for help troubleshooting this error.
------

@tyrannosaurus-becks  thanks for reporting!
Seems like the original intend for this feature is just installing plugins for an already installed zsh. therefor the scripts assumed zsh already installed and configuration is there. The script also assumed an image with git and ca-certificates already installed, which is not the case with plain ubuntu.
I have added a logic which install zsh if it does not exists and create the configuration file is created if is not exists.
I have also added a test to check clean ubuntu image
Please try latest version : ghcr.io/devcontainers-contrib/features/zsh-plugins:0.0.4

That is awesome! Thanks @danielbraun89 !!!!

repo: devcontainers-contrib/features


text:
Fix jsx renderer double closing elements

Fixes #34

Also added a test case for that.

source: gharchive/pull-request

repo: developit/preact-render-to-string

license: mit

license_type: permissive

license_source: bigquery


text:
preact@8.4.1 and preact-portal: Maximum call stack size exceeded

Howdy! I was excited to test the new release of preact@8.4.1 today but my App won't run because it makes heavy use of preact-portal which seems to now cause an infinite loop when rendered.
Reproduction: https://jsfiddle.net/bfqxrghu/2/

Looks like this is because the mount queue only gets emptied after iteration. Because preact-portal uses componentDidMount() to render a second tree, that tree appends an entry to the mount queue, which causes the indices to shift and Portal.componentDidMount() to be called again (repeated).

Was due to #1211.

Fixed in 8.4.2!

source: gharchive/issue

repo: developit/preact


text:
WIP Change runner image to use nodejs18+go

What does this PR do?
What issues does this PR fix or reference?
Is it tested? How?

PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

Thanks for working on this @musienko-maxim :) Please ping me when you're ready for me to review this PR.

/test v8-devworkspace-operator-e2e

/test v8-devworkspace-operator-e2e

authors: AObuchow musienko-maxim

repo: devfile/devworkspace-operator

license_source: github-api


text:
Preview Post mode Instagram

Describe the feature
Nossa aplicação tem os previews que é o meio da pessoa ver como o post dela vai estar em certa rede social, nessa tarefa deverá ser feito o preview da rede social Instagram.
Implementation Details
O componente deve ser exatamente igual a um post da rede social Instagram deverá conter o texto do post, a foto e o nick da conta.
Atenção: O componente deverá se comportar exatamente igual ao tipo de Preview selecionado, por exemplo, se selecionar o Preview de celular, o Preview deve estar do mesmo jeito de como tiver em um celular, como as mesmas medidas, formatações de texto e encaixe do layout. O componente deverá ser adaptativo, pois ele tem que estar com as medidas exatamente iguais ao Preview selecionado.
Deve se atentar que os arquivos de mídia, devem ir para o preview também, e ficar igualzinho ao post mode do Instagram.
A cor padrão do Preview deve ser a Branca, como mostra no visual concepts
Visual Concepts
Você deverar fazer essa parte, porem igual ao do Instagram.

Assim:

Se atente a fazer o layout para cada Preview:

Obrigado por abrir a issue
Verifique os nossos guidelines:

Código de conduta
Contribuição
Guia de Estilo

eu quero!!!

eu quero!!!

eu quero!!!

eu quero!!!

eu quero!!!

authors: Alecell JpBurgarelli PiluVitu mateusdtakayama muritadb

repo: devhatt/octopost

license: MIT


text:
How to configure TLS for filebeat

Problem description
Refer to the TLS certificates,  I have successfully started the ELK cluster using the files of the tls branch. But I encountered a problem, which certificate should I use in the filebeat configuration to connect to the ES cluster normally. The filebeat log tells me Get "https://x.x.x.x:9200": x509: certificate signed by unknown authority
I saw this article on the ES official website, but I don’t have the files cert.pem and cert.key in the example, How can I get them, thanks.

Extra information
Stack configuration

Docker setup

$ docker version

Client: Docker Engine - Community
 Version:           20.10.12
 API version:       1.41
 Go version:        go1.16.12
 Git commit:        e91ed57
 Built:             Mon Dec 13 11:45:41 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.12
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.12
  Git commit:       459d0df
  Built:            Mon Dec 13 11:44:05 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.12
  GitCommit:        7b11cfaabd73bb80907dd23182b9347b4245eb5d
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

$ docker-compose version

Docker Compose version v2.2.2

Container logs

$ docker-compose logs

[OUTPUT HERE]

Good catch, Filebeat isn't configured properly for TLS.
The configuration should look like this:
https://github.com/deviantony/docker-elk/blob/9e280d8dc3a56174e1406bab7824d4e179256469/extensions/metricbeat/config/metricbeat.yml#L34-L39
I'll fix it!

Fixed on the tls branch (diff)

authors: GRiverone antoineco

repo: deviantony/docker-elk


text:
Issue when subscribing several clients to the same network in the multi tenant environment

Subscription of several clients fails with 500 status code (Internal Server Error) when there is minimal delay between request
Error log:
http rest error. status: 500, response: "{\n  \"error\": 500,\n  \"message\": \"Object of class [com.devicehive.model.Network] with identifier [1]: optimistic locking failed; nested exception is org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) : [com.devicehive.model.Network#1]\"\n}"

Expected behaviour:
Implementation of this logic, table locks, database scheme, concurrency approach should be reviewed and changed if possible to prevent such errors.
If changing the logic is not possible or desirable server should return 412 or 428 error (Precondition Failed)

Script to reproduce this issue:
#!/bin/bash

DH_URL="http://localhost:8080/api/rest"
DH_TOKEN="1jwKgLYi/CdfBTI9KByfYxwyQ6HUIEfnGSgakdpFjgk="
DH_NETWORK_ID=1

echo "Create 2 new clients..."

FIRST_CLIENT_ID=$(curl -X POST -H "Content-Type: application/json" -H "Authorization: Bearer $DH_TOKEN" -s $DH_URL/user -d '{ "login":"login1", "role":1, "status":0, "password":"password" }' | grep -Po '"id":[ ]*(\d*)' | awk -F ':[ ]*' '{print $2}')
SECOND_CLIENT_ID=$(curl -X POST -H "Content-Type: application/json" -H "Authorization: Bearer $DH_TOKEN" -s $DH_URL/user -d '{ "login":"login2", "role":1, "status":0, "password":"password" }'  | grep -Po '"id":[ ]*(\d*)' | awk -F ':[ ]*' '{print $2}')
THIRD_CLIENT_ID=$(curl -X POST -H "Content-Type: application/json" -H "Authorization: Bearer $DH_TOKEN" -s $DH_URL/user -d '{ "login":"login3", "role":1, "status":0, "password":"password" }'  | grep -Po '"id":[ ]*(\d*)' | awk -F ':[ ]*' '{print $2}')

echo "\nClient id's: $FIRST_CLIENT_ID, $SECOND_CLIENT_ID, $THIRD_CLIENT_ID."

echo "Assign clients to the default netwotk:\n"

curl -X PUT -H "Content-Type: application/json" -H "Authorization: Bearer $DH_TOKEN" -v $DH_URL/user/$FIRST_CLIENT_ID/network/$DH_NETWORK_ID &
curl -X PUT -H "Content-Type: application/json" -H "Authorization: Bearer $DH_TOKEN" -v $DH_URL/user/$SECOND_CLIENT_ID/network/$DH_NETWORK_ID &
curl -X PUT -H "Content-Type: application/json" -H "Authorization: Bearer $DH_TOKEN" -v $DH_URL/user/$THIRD_CLIENT_ID/network/$DH_NETWORK_ID &

Example output:
........
Create 2 new clients...

Client id's: 115, 116, 117.
Assign clients to the default netwotk:

{
  "error": 500,
  "message": "Object of class [com.devicehive.model.Network] with identifier [1]: optimistic locking failed; nested exception is org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) : [com.devicehive.model.Network#1]"
}{
  "error": 500,
  "message": "Object of class [com.devicehive.model.Network] with identifier [1]: optimistic locking failed; nested exception is org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) : [com.devicehive.model.Network#1]"
}

Quick and dirty fix is to retry the operation and then fail if retry fails. On the other hand we can change many-many to one-many&many-one model, this will allow us to avoid such nasty problems in mostly all operations which modify user-network associations. Other operations could suffer due to increased memory consumption and additional entity to be created between network and user.

authors: SorJEF zubrabubra

repo: devicehive/devicehive-java-server


text:
React components in Nuxt

Hello, any experience to integrate react components in nuxt?
I'll try a bit but I always had some errors.

Is there any error message? @sndrgb

It fails to parse the pages

@sndrgb @anaibol @ekkaiasmith
Try veaury@^2.5
https://github.com/gloriasoft/veaury?tab=readme-ov-file#using-veaury-in-the-ssr-projects

authors: anaibol devilwjp sndrgb

repo: devilwjp/veaury


text:
WEBJS - add poll API and events

Relates to https://github.com/devlikeapro/whatsapp-http-api/issues/131

Up

Up

Hey @allburov, it seems that the send poll functionality is now available in Whatsapp-webjs https://github.com/pedroslopez/whatsapp-web.js/issues/2615.
Can you please check and let me know if you plan to implement it soon?
Thanks.

@KKshitiz great news!
The problem right now that with webjs you can send a poll, but you can't get votes for that :( https://github.com/pedroslopez/whatsapp-web.js/pull/1887
Does it make sense for you to only send polls without getting the answers? I'd wait the full support first before starting working on that

authors: KKshitiz allburov devlikepro

repo: devlikeapro/whatsapp-http-api


text:
Loading Issues

When loading kencadima.eth there's an error.

This appears to be an issue with the OpenSea API. I've made identical queries (outside of the app) to the one causing the issues, but with different addresses and they work fine. I reported the issue to them.


text:
#744: Fix MAVEN_ARGS by separating arguments

Fixes: #744
This quick bug fixes the MAVEN_ARGS variable. The reason for the bug was a missing whitespace that separates the arguments.

Pull Request Test Coverage Report for Build 11720925999
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 66.948%

Totals

Change from base Build 11720645119:
0.0%

Covered Lines:
6311

Relevant Lines:
9085

💛  - Coveralls

authors: alfeilex coveralls

repo: devonfw/IDEasy


text:
Support XDG_CONFIG_HOME on linux for config files

Hi, thanks for the great tool!
On linux there's a shift towards storing config files in the $XDG_CONFIG_HOME directory, normally configured as $HOME/.config, to keep the home directory less cluttered. It would be great if target-cli could store it's configs in $XDG_CONFIG_HOME/target instead of $HOME/.target.
XDG base directories spec: https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
Go stdlib supports this out of the box: https://pkg.go.dev/os#UserConfigDir

Thanks for opening this feature request. I'll be glad to take a look at this. I'm thinking of a way to make this happen without breaking the Mac support. Currently $HOME works for both Mac and Linux. Let me look at this a bit more and see what solutions I can come up with. Also feel free to suggest an approach or open a PR. Thanks again for this @googol

authors: devops-rob googol

repo: devops-rob/target-cli


text:
duclair create new files

WELCOME TO DEVOPS-EASY-LEARNING PULL REQUEST SYSTEM
Description of the change

Detailed description here

Checks and balances

[ ] Tests added and run
[ ] (External) Interfaces documented
[ ] Has security implications (describe below)

Type of change

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)

Related stories, issues and pulls

Links to Pivotal Tracker stories, JIRA tickets or other pull requests here

Security considerations

Describe any security impact this change may have

great job duclair

you branch has conflicts


text:
No-op endpoint does not forward query params automatically?

Describe what are you trying to do
Use no-op proxy endpoints.
Your configuration file
{
      "endpoint": "/test/{route}/{params}/{work}/{correctly}",
      "output_encoding": "no-op",
      "backend": [
        {
          "url_pattern": "/test/{route}/{params}/{work}/{correctly}",
          "host": "{{ env "SERVICE_HOST_TEST" }}",
          "encoding": "no-op"
        }
      ]
    },

Commands used
Via the krakend docker image (dev/watcher version):
version: "3"
services:
  service-slice-gateway:
    image: devopsfaith/krakend:config-watcher
    environment:
      # KrakenD vars
      - FC_ENABLE=1
      - FC_SETTINGS=config/settings
      - FC_PARTIALS=config/partials
      - FC_TEMPLATES=config/templates
      - FC_OUT=debug_config.json
      - KRAKEND_CONFIG=config/krakend.json
      - SERVICE_HOST_TEST=${SERVICE_HOST_TEST:-http://example}

    ports:
      - "2000:8080"
    volumes:
      - .:/etc/krakend
    working_dir: /etc/krakend

When running a no-op endpoint, my experience has been that query parameters sent to the endpoint are not automatically passed to the backend. They seem to have to be specified in the querystring_params config.
In the no-op docs it states the following under "Key Concepts":

The KrakenD endpoint works just like a regular proxy

Headers passing to the backend still need to be declared under headers_to_pass, as they hit the router layer first.

With no mention of query params or anything else that might need to be manually specified, I naturally assumed they would be passed to the backend automatically. Is this not intended to be the case? If so, I think this should probably be stated in these docs alongside the point about headers.
Thanks

Hello @EthanML . No parameters are forwarded to the backend by default. It's documented here but we will add it to the section you are referring to.
Thanks

authors: EthanML alombarte

repo: devopsfaith/krakend-ce


text:
bug：idea等图标无法正常展示。建议：每次搜索重新读取项目。

pycharm项目和idea项目的图标都显示为空白。如下。

可能是 getFileIcon 输入的路径有空格的时候获取图标会失败。
另外，能不能每次使用搜索重新读取一次所有项目，消耗应该没多大，但是新建项目就不用重启utools了。

每次唤醒插件时重建项目列表 以发布应用市场最新版本
图标问题后续处理

v1.0.8 版本中修复，应用市场已送审

authors: devotion-coding enximi


text:
Configure django container to reload on file change

The django container currently runs this command from the Dockerfile:
CMD ["gunicorn", "--bind", "0.0.0.0:8000", "devroast.wsgi"]
This doesn't reload when the files inside the container change, so therefore the container has to be restarted.
https://docs.docker.com/compose/django/
This recommends adding a volume mount for the django code and overriding the command to use runserver instead of gunicorn.

I'll work on this issue.

repo: devroastproject/devroastproject


text:
Add description and hidden field to profiles

Currently, we construct a devspace yaml file by having the default dev profile simply define an empty structure, and then all other profiles patch it. Some profiles are building block profiles, others are "public" profiles. This request is for two features:

Add an optional hidden field to profiles. This would make it so that they do not show up under devspace list profiles. Currently, we use a leading underscore in the profile name to separate "public" from "private" profiles. Alternatively, do not list profiles with a leading underscore in the name. "hidden" profiles would still be usable as parent profiles, even across projects.
Add an optional description field to profiles. This could show up when you list profiles so that people have a better understanding on how to use the profile and what it is doing.

@JamesHutchisonCarta thanks for creating this issue! That makes a lot of sense, I agree that we should add this.

The Devspace project currently lacks enough contributors to adequately respond to all issues. After 90d of inactivity,  the issue is closed. You can re-open this issue if you still want help.

authors: FabianKramm JamesHutchisonCarta zerbitx

repo: devspace-sh/devspace


text:
Python virtualenv pip dependencies not archived

Our application is setup in a separate virtualenv environment with quite a few pip installed dependencies. It would be nice if blueprint could somehow capture this.

Blueprint tries to grab packages from the currently active virtualenv per the VIRTUAL_ENV environment variable.  Is that set in your environment after sourcing bin/activate?
In general, however, Blueprint encourages users to install things system-wide (using virtual machines or containers for full-stack isolation).

Thank you. I may not have activated by venv. Which makes sense.  Note: The reason I am using a virtualenv is my ubuntu has a different python interpreter installed (2.6.5) and I want to use (2.7.1) on my application without messing up the OS dependencies.

That's a totally fair reason to use virtualenv.  I hope that just creating blueprints while the virtualenv is active is enough to solve the problem.

authors: jzcoder rcrowley

repo: devstructure/blueprint


text:
[UI][Chart-store Search]We are hitting wrong URL of API on search functionality of chart-store

Summary
We are hitting wrong URL of API on search functionality of chart-store
Steps To Replicate

Go to Chart Store
Now try to search any chart via search box visible
Hit Enter and observe the n/w calls

Actual Output
We are hitting wrong URL of Search API because of which there is 301 redirection
/orchestrator/app-store/discover?appStoreName=deepak&includeDeprecated=1
Expected Output
We should correct URL:
/orchestrator/app-store/discover/?appStoreName=deepak&includeDeprecated=1

This has been fixed and deployed.

repo: devtron-labs/devtron


text:
Bug: Intermittent terminal disconnection issue

📜 Description
Intermittent terminal disconnection issue. There are some times when people aren't able to connect to terminal but after some time it starts working again automatically

👟 Reproduction steps
NA
👍 Expected behavior
It should work all the time
👎 Actual Behavior
Intermittently it stops working
☸ Kubernetes version
EKS 1.23
Cloud provider

AWS

🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

AB#2837

Closing as it wasn't reproduced and it can happen due to transient network issues.

reopening this issue, as params are made configurable only, need to check after some tuning.


text:
dexie cloud auth restrictions

Trying to understand how to use the zero-config authentication while at the same time not opening up the ability for users to create their own account without paying my app.
Basically i only want my app to allow users to create their own login after they checkout with Stripe or some sort of payment service. Is the only way to do this with custom auth?  I see that Stripe integration is on your roadmap, is that a feature integration for apps or just a way for apps to pay Dexie cloud for its services?  Thanks and really appreciate all your work and great software!

Thanks for a good question that resembles a lot of how I've designed the subscription model. The docs is not updated about this but I posted a blog post about it. Need to get started with the docs, so I start by answering this question (so I can copy paste to the docs later). The short summary is:
Default licensing behavior

Unknown users that logs in to your app will get evaluation accounts. They do not occupy any paid seat.
You decide when to lift a user to a production account. Either manually (when you get paid for example), or programmatically using a new REST API, for example to call from your Stripe hooks
Evaluation Accounts below for what happens when evaluation accounts expired

So until you have some payment solution in place, you could advertise expiring users to contact you and manually upgrade selected users to production accounts. To have something that scales, you should use a Stripe web hook and programmatically update users through dexie cloud's new users API when they create a subscription with you.
Evaluation Accounts

Evaluation accounts have full functionality with sync but expire after X number or days.
You configure the length of each user's evaluation period - between 1 and 30 days.
You configure whether evaluation day count will pause when users don't use your app, or if they shall be a fixed number of days.
When a evaluation period ends for a user, their app turns into permanent offline mode, until you lift them to production. This means that they may continue to use the app but without sync - the same behavior as if they would unplug their network.

New API's
The existing client-side API will be extended with new props that reveals whether the user is on evaluation or production, when the evaluation ends (if fixed date) or how many active evaluation days there are left. Your app should inspect these properties and warn or advertise user to purchase a subscription when the end of the evaluation period closes in.
The user retrieve from db.cloud.currentUser has the new license property:

export interface UserLogin {
  ...

  license?: {
    type: 'demo' | 'eval' | 'prod' | 'client';
    status: 'ok' | 'expired' | 'deactivated';
    validUntil?: Date;
    evalDaysLeft?: number;
  }

  ...
}

A new REST API where you may enumerate, search, update and delete users will be on https://<dbID>.dexie.cloud/users.  This API should be managed from a server-side application, such as a Stripe hook:
export interface DBUserJsonModel {
  readonly userId: string;
  readonly created: ISODateTimeString;
  readonly updated: ISODateTimeString;
  readonly maxAllowedEvalDaysLeft?: number; // Starts at 30 and counts down on active days.
  readonly lastLogin?: ISODateTimeString | null;
  type: 'eval' | 'prod'; // Updating this field maintains seats
  validUntil?: ISODateTimeString; // Updating this field checks against maxAllowedEvalDaysLeft
  evalDaysLeft?: number; // Updating this field checks against maxAllowedEvalDaysLeft
  deactivated?: ISODateTimeString; // Updating this field maintains seats
  data: {
    displayName?: string;
    email?: string;
    [key: string]: any;
  }
}

Example React component to show warning 7 days before eval ends
import React from 'react';
import { useObservable } from 'dexie-react-hooks';
import { db } from './db';

const DAYS = 24 * 60 * 60_000;

function LicenseWarning() {
  const user = useObservable(db.cloud.currentUser);

  if (!user.license) return null; // Backward compat.

  const isLicenseOk = user.license.status === 'ok';

  const showLicenseWarning = user.license.validUntil
    ? user.license.validUntil < new Date(Date.now() + 7 * DAYS)
    : user.license.evalDaysLeft
    ? user.license.evalDaysLeft < 7
    : false;

  return isLicenseOk
    ? showLicenseWarning
      ?
Your account is about to expire. Please upgrade your account

      : null
    :
License expired or user was deactivated. Please upgrade your account
;
}


text:
Breaks dependency between Buf and Array

Doing this so I can use Buf to implement Array functions that require local mutation.

FWIW, seems like the right (re)direction of the module dependencies.  I had considered this same change myself, for the same reason.  Thanks @kritzcreek!

authors: kritzcreek matthewhammer

repo: dfinity/motoko-base


text:
Add error codes and explanations to type checking diagnostics

This PR integrates error code explanations from the motoko npm package into Monaco's diagnostic tooltips.
Progress:

[x] Patch moc.js to include error codes with existing diagnostic information
[x] Show explanations as plain text
[x] Evaluate whether it's feasible to add custom Markdown rendering for explanations

Nontrivial but seems possible using a hover provider

If we end up including these error explanations in the developer docs, we could include a nicely formatted link to the relevant webpage using a target URI in the diagnostic's code property.

Yep; the replacement moc.js is equivalent to 0.9.1 with the addition of https://github.com/dfinity/motoko/pull/3991.

repo: dfinity/motoko-playground


text:
refactor(frontend): optimize formatSecondsToNormalizedDate

Motivation
As mentioned by @peterpeterparker in https://github.com/dfinity/oisy-wallet/pull/3526#discussion_r1841610934 , we could optimize function formatSecondsToNormalizedDate , avoiding creating a new formatter every time.
From MDN

When the method is called many times with the same arguments, it is better to create a Intl.DateTimeFormat object and use its format() method, because a DateTimeFormat object remembers the arguments passed to it and may decide to cache a slice of the database, so future format calls can search for localization strings within a more constrained context.

[OISY-130]

repo: dfinity/oisy-wallet


text:
conan package

Is it possible to consume the package through conan? I can't find it in conan center

Hi,
I need to fix the conanfile.py but yes it should be possible to use it with conan (I doing it at my job).
I have not try to add it to conan-center (nor plan to make it). May be later. I am not sure I know how to to that anyway ;)

so you suggest to clone the repo and run conan create from it? that's possible but I think is against the idea of using a package manager.
I can try to add it to conan-center as I already added some packages there.
Do you plan to cut a release soon so it can be versioned properly?

Yes, since I just fix the recipe, it should work by cloning and launch a conan create. (https://github.com/dfleury2/beauty/commit/a5b9c266787889b93627d7987511312e521e02b2)
Yes against a centralized package manager. I am used to create conan recipe for third parties which do not belong to conan-center.
I will see how I can add it to conan-center myself so I can learn how to to it ;) In case of trouble, I can still ask you advice.
Soon I will tag a first rc release. I still need to fix an issue on the asynchronous client.

tag 1.0.0-rc1 created.
conan-center-index package is done (need to test it) but I need to be accepted to push first.

Hi,
conan package review is in progress. Waiting for 3 reviewer approvals.
https://github.com/conan-io/conan-center-index/pull/10956

Done
https://conan.io/center/beauty


text:
Add substrate data to reports

@stoyelq: is this issue still relevant? or we could cancel it?

Right issues should come with context:
Proposed Change/Activity
Substrate data was identified as a potential high value record in the Melford terminal report and has ben mentioned in a couple other places as well.  I can definitely see how it might be a nice complementary data source to add to the report, so I added this to the wish list items, but we can drop it if it's outside the scope of the project.
Why is this important
ADDING MORE DATA! Even if it's not species data, substrate information may be relevant and useful to many of the reports end users.
Action Items
Wait to see if more people want this/just add it in available time.
Mention this as an option to new/existing users to gauge interest.

repo: dfo-mar-odis/shinySpatialApp


text:
Add frame number as input

Currently there doesn't seem to be a way to get the current frame number as integer. It's possible to approximate by multiplying the elapsed time by the framerate limit, but it's not very accurate.
Also sorry for making a bunch of requests, these are just the problems I ran into while playing with shadered.

Added! Thanks for the suggestion and just keep the request coming - don't worry!
There is now a FrameIndex system variable available for all integers!

Works perfectly, thanks!

authors: CptPotato dfranx

repo: dfranx/SHADERed


text:
Fixed segmentation fault

Caused by access of null pointer in case ShaderPass
does use Window as Output and not a RenderTexture.

Yes, found the same issue. Good solution.

authors: Slamy oelison


text:
[0.2] Fix: Query parameters are not rehydrated

The problem is the cache, which is used to keep track of the query param values. This cache is not shared between the application and the engine, but the routing is entirely done in the application. This causes the hydrating of unspecified query parameters during transitioning to fail, because the query param value is actually stored in the engine cache, but the hydration is done from the application cache.
My first PR for this addon, so any feedback is welcome. If you think this is correct fix I can try to add an acceptance test as well.

@dnachev unsure about correctness (I'll defer to @dgeb), but it would be good to go ahead and add a previously failing test to prevent regressions.

@trentmwillis I've added a test, although I'm not sure it recreates the problem in issue #163. However, it fails and my change fixes the test, so at least this case should be handled. I wouldn't be surprised if it fixes the query params reset from the issue as well, but I have no guarantees for it.

This looks like the right fix to me.
@rwjblue - r?

Yes, this seems correct to me.  The bucket cache should be shared.
@dnachev - Can you please submit this patch to Ember also?  Somewhere in here: https://github.com/emberjs/ember.js/blob/master/packages/ember-application/lib/system/engine-instance.js#L180-L183

Published in v0.2.8

@dnachev I added https://github.com/dgeb/ember-engines/issues/168 to track the push upstream. Please comment there if you plan to take this on. Thanks!

authors: dgeb dnachev rwjblue trentmwillis

repo: dgeb/ember-engines


text:
Remove Route.prototype.mount.

Per discussion at core team meeting, removing this.mount from within an Ember.Route. In general, manual usage of this.mount can be replaced by more declarative usage of {{mount}}.

@rwjblue does it means that routable engines will be sunset?

@bugant no, both routable and route-less engines will continue to be supported.
This PR simply removed one method of mounting route-less engines from within a Route. Instead we'll just support mounting route-less engines in templates via {{mount}}.

authors: bugant dgeb rwjblue


text:
Improve article 2302.04761

Figure 4 cannot be loaded.

Thank you for the report!
We need latexml support for spverbatim.sty here.


text:
v23.0.0 Update & Clean PR #2: Dgraph Client Refactor

Most of the changed files contain simple style, formatting, and naming cleanup.
Functional changes are mainly related to aligning this client to the dgo client and are concentrated in these classes/interfaces:

DgraphCloudChannel

The static Create method implements the dgo DialCloud logic.

DgraphClient
IDgraphClient

Users will interact with this interface instead of the DgraphClient class directly.

Transaction

Added a Do method similar to the dgo implementation.

ITransaction

Again, users will interact with this interface instead of the Transaction class directly.

IQuery

Represents a read-only transaction.
Transaction class is hidden behind this interface when creating it with client.NewReadOnlyTransaction

RequestBuilder
MutationBuilder

README.md is also heavily rewritten to match the dgo readme as closely as possible.
Note: The tests will fail until PR #34 is merged.

I was able to merge the first PR, please do a rebase and we will review this PR.

Tests fail right now. Is that expected?

@all-seeing-code yeah, next PR will fix it

authors: all-seeing-code mangalaman93 sachyco


text:
{'error': "An error occurred: 'functools._lru_cache_wrapper' object has no attribute 'ticker'"}

Trying to look up some financial statement info for a specific ticker but getting a bit confused...
I have this function:
def handle_financial_info_request(ticker: str, statement_type: str, year: Optional[int] = None) -> Dict[str, Any]:
    try:
        company = Company.ticker(ticker)

        if statement_type == "balance_sheet":
            financial_data = company.xbrl().balance_sheet
        elif statement_type == "cash_flow":
            financial_data = company.xbrl().cash_flow
        elif statement_type == "income_statement":
            financial_data = company.xbrl().income_statement
        else:
            return {"error": f"Invalid statement type: {statement_type}"}

        df = pd.DataFrame(financial_data)
        df = df.set_index('Unnamed: 0')

        if not year:
            return df.to_dict()

        if str(year) in df.columns:
            return df[str(year)].to_dict()
        else:
            return {"error": f"Data for year {year} not available"}
    except Exception as e:
        return {"error": f"An error occurred: {str(e)}"}

But for the error I get 'functools._lru_cache_wrapper' object has no attribute 'ticker' Halp! What to do?

Try
company = Company(ticker)

I have to apologize for this... Yep, you're right -- shortly after opening the issue, I tried that and it worked and forgot about the open issue. Sorry about that, my mistake!

authors: dgunning marwinsteiner

repo: dgunning/edgartools


text:
[Proof Of Concept] Enable plugin mode

@amcgee @KaiVandivier @Birkbjo This is just a proof of concept of what we have been discussing these days. It is very rough - we are still keeping the header, button, etc. which ideally we would like to hide with some props (this can be done in our fork as I understand it may not be interesting for you). For us, it would be great if we could have this infrastructure in capture-app, dashboard and potentially some other apps. This is how it looks like in our app. I am happy to show you the example in the DHIS2 instance if we have time later. Thank you!

@tokland thanks for this!

Hey Adrian — thanks for the proposal! It definitely did start a conversation 😊
The main thing we can say is that we’re moving toward a general app architecture that should end up achieving what you want here: we’re moving toward a “global shell” way of loading apps in an iframe, which will entail building each app in plugable way (i.e. without the header bar and with a communication channel from its parent), which seems like it would satisfy the intention of this PR 👍  so I think that will be useful to the use case you have here!
In the mean time, as our tech is now, we don’t think it’s the right thing to build an entire app as a plugin, but I have some advice below on making it easy to implement in your fork if you like!
These are our main reasons for holding off on this plugin build in the core repository:

If we made this change, we would end up undoing it soon when we move to the global shell way of “pluginifying” apps
It would be a little weird to have this available for some apps, but not all of them (we would also want a standardized “props interface” to pass from parent to child if we were to do that, which again would change with the global shell)
Plugins as they are now have a bit of a special meaning and usage in the platform, and having a whole app as a plugin may confuse consumers of Capture and Dashboard plugins
Plugin building is unoptimized right now, and building a whole app as a plugin would end up making basically two apps in the bundle, which is a bit clunky (this will get better with Vite though)

If you want make a plugin build like this in your own fork, however, it can actually be just a small change, so hopefully it’s easy to maintain 🙂  Here are some tips:

The only change you really need to make is in d2.config.js, which is to add a plugin entry point that is just the same as the app’s:

entrypoints: { app: './src/App.js', plugin: './src/App.js' }
All the other changes in this PR seem to be copied over from a Dashboard plugin, which needs to handle some complicated offline features, so fortunately the same logic wouldn’t be needed for the Data Approvals app

In the app that will be consuming the plugin, you can use the Plugin component from the App Runtime, which adds some nice utilities: https://developers.dhis2.org/docs/app-runtime/components/Plugin

The examples linked at the bottom of the page are a useful guide for how they’re used
The Dashboard plugins like the one this PR got copied were made before this component was released; they’re being migrated to using this component now which makes them simpler
(If you don’t want to use the Plugin component, you can use the skipPluginLogic: true config option in the d2.config.js of the app with a plugin entrypoint to skip some of the communication & prop handling that’s added to the plugin)

And another tip: If you’re using the Data Approval app in an iframe, you can take advantage of the deep linking feature if you want to load the app with a particular context selection already selected by providing a URL to the iframe with the right parameters: https://play.im.dhis2.org/dev/dhis-web-approval/index.html#/?ou=%2FImspTQPwCqd%2FO6uvpzGd5pu%2FYuQRtpLP10I%2FDiszpKrYNg8&ouDisplayName=Ngelehun CHC&pe=202412&wf=rIUL3hYOjJc

Hopefully these things help you out and make it easy to do what you want to do! 🙏
Thanks again for your input here! We value hearing your use case, and it’s helpful to get new ideas and perspectives. Let us know if you have any other questions or ideas!

Hi @KaiVandivier Thanks for your thoughtful response! It helps a lot. We have been testing some of your ideas and we have some comments:

It is true the build size increases a bit: app (2050K) -> app+plugin (2470K)
Thanks for this tip: entrypoints: { app: './src/App.js', plugin: './src/App.js' } We tested and it worked!
The Plugin component from the App Runtime works nicely and seems to be useful. The only thing is that we had to update the @dhis2/cli-app-scripts dependency to 10.4.0 so that the parent and approval app dependencies are aligned.
Deep linking: it worked. In the URL, I guess you meant plugin.html instead of index.html. In this case, we are missing only two parameters: attributeOptionCombo=ID and hideSelectors=true. We understand the hideSelectors parameter is something for our fork but is it reasonable to add the attributeOptionCombo in this app?
Once again, many thanks for your help! We really appreciate having your input on this.

Hey Adrian! Glad to hear the plugin is working for you! 🎉
Ah yeah, I forgot to mention the cli-app-scripts version to support the plugin logic — sorry about that, and glad you got it working 🙂
For the deep linking, that’s right that you would use plugin.html for the iframe src 👍 for attributeOptionCombo, is that for the Data Approval app? I’m not very familiar with the app myself, but it doesn’t seem to use an attribute option combo anywhere — let me know if there’s something else that you mean by that, and I can inquire further 🔍
For the Data Entry app, the attributeOptionCombo can be deep-linked using the query param format attributeOptionComboSelection=<categoryOneId>-<categoryOptionOneId>_<categoryTwoId>-<categoryOptionTwoId>…, e.g. this one: https://play.im.dhis2.org/dev/dhis-web-aggregate-data-entry/index.html#/?attributeOptionComboSelection=LFsZ8v5v7rq-C6nZpLKjEJr_yY2bQYqNt0o-i4Nbp8S2G6A&dataSetId=lyLU2wR22tC&orgUnitId=DiszpKrYNg8&periodId=202403 — maybe that can be helpful; I think I remember you mentioning you use that one as a plugin as well?
Happy to help out with anything else if I can 🙂

Hi @KaiVandivier !
Sorry for the delay, we finally got the opportunity to integrate Data Approval as an iframe in our our apps (using query strings) and is working great (we just needed the minor modifications we discussed), thanks for all your help!

for attributeOptionCombo, is that for the Data Approval app? I’m not very familiar with the app myself, but it doesn’t seem to use an attribute option combo anywhere — let me know if there’s something else that you mean by that, and I can inquire further 🔍

As you know, aggregated data values are associated to some attributeOptionCombo (one of the COCs of the dataSet categoryCombo), so typically we will need to disaggregate on these dimension. In 2.36, the old Data Approval App showed a selector:

However, no such selector exist in the new React Data Approval App (or we have missed it!)

Ahh - am I understanding right that you're looking for that feature in the new Approvals app, where you can disaggregate data by the AoC too?
If so, I can do a little research to find out why that isn't included in the new app, and if it's possible to add! 🙂

@tokland Aha, this actually known to be a missing feature, and there is interest in adding it (here is one issue about supporting it in the backend, for example) -- I'll chime in  to the discussion with your use case, which will help prioritize it 🙂
I'll try to share updates!

you're looking for that feature in the new Approvals app

Yes, that would be great! For the moment, we've added the filter ourselves (https://github.com/EyeSeeTea/approval-app/pull/3/files#diff-5f723d69ee9cc69ee25c7a33059f7a22668a657886975d1b82976bcf57b63fe9R22), so passing for example filter: "ao:COCID" shows only the data we are interested in.
It was our understanding that the backend supports approving by the tuple orgUnit/dataSet/aoc/period:
https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/data-approval.html#webapi_data_approval_approve_data

https://dhis2.atlassian.net/browse/DHIS2-11518)

Cool, we didn't know about this one, we'll be watching it!

authors: KaiVandivier adrianq tokland


text:
feat(type): system font stack

Description
We are moving from Inter to using a system font stack.

Replaced @define-ff-custom-name value with new font stack
Removed @ff-inter and @ff-inter-italic variables
Removed Inter from font declaration
Removed Inter font files from font folder
Added Adjusted Segoe font

Changes noticed

Before
After

Pull Request Checklist

[x] Ask the contributors if a similar effort is already in process or has been solved.
[x] Review the contribution guidelines.
[ ] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[x] Ensure all gulp scripts successfully compile.
[ ] Update, remove, or extend all affected documentation.
[ ] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).

Obligatory GIF (super important!)

@juliodialpad,
While we're at it, let's go ahead and update our Mono from Roboto to SFMono, including its equivalent weights, i.e. in less/variables/typography.less...
@ff-sf-mono: {
  400: SFMono-Regular;
  700: SFMono-Bold;
};

authors: francisrupert juliodialpad

repo: dialpad/dialtone


text:
Make the README.md more editable on github.com

Currently the markdown used for tables is too wide to edit easily using the github.com editor because of linebreaks:

I'd propose a minimalistic style where the headers don't have to match with the content rows + merging map and address into a single location field with a link:
Wifi | Power | Location | Open Hours
---- | ----- | -------- | ----------
✔ | ✔ | [Boldhusgade 6, 1062 København K](https://goo.gl/maps/nN7zjHsSmcU2) | Mon - Fri 7.30-17.00, Sat 11.00 - 17.00

which will render like so:

Wifi
Power
Location
Open Hours

✔
✔
Boldhusgade 6, 1062 København K
Mon - Fri 7.30-17.00, Sat 11.00 - 17.00

I'll make pull request if you agree :smiley:

+1

:+1: like it :D thank you

authors: diasdavid ralphtheninja watson

repo: diasdavid/awesome-hacking-spots


text:
Show opening hours in a different format

Opening hours was recently added to the entries, but as the last column on the table. Some places have the same opening hours each week which makes it easy to add to a table, but some (like the one just added in #30) have 6 different times per week.
I'd suggest either making linebreaks for each diffrent time or moving it outside the table.
What do you guys think?

I agree to this :+1: I had commented on the PR that we might/should take that direction it if starts looking messy

Having a separate time table and a link to an always updated timetable (because they change through the year), for example to the place website, google place page, foursquare, zomato, etc, would be the better solution, otherwise we might create falsy expectations

@diasdavid Yeah, I'm pretty worried that it's tough to keep up to date. On the other hand, some places don't advertise anything them selfs, so it's nice to have in those cases.

I think we should also agree on a format. I suggest:

3 letter abbreviations for days with first letter uppercase (e.g. Mon instead of Monday)
24 hour clock (i.e. no am or pm)
Colons between hours and minutes (e.g. 13:00 instead of 13.00)

agreed, and I would prefer a 2xRow 7xColumn layer, to avoid making the scrolling incredibly large, what about:
Sun | Mon | Tue | Wed | Thu | Fri | Sat
:--: | :--: | :--: | :--: | :--: | :--: | :--: |
9:00 - 14:00 | 9:00 - 18:00 | 9:00 - 19:00 | 9:00 - 20:00 | 10:00 - 13:00 | 9:00 - 16:00 | 9:00 - 14:00 |

@watson thoughts on latest proposal? Shall we proceed? :)

Being non-american I'd personally like Monday to be the first day of the week :wink: - ISO 8601 agrees, but I'm open to suggestions.
Testing different formats:

Mon
Tue
Wed
Thu-Fri
Sat
Sun

9:00-14:00
9:00-18:00
9:00-19:00
9:00-20:00
10:00-13:00
closed

Mon
9:00-19:00

Tue
9:00-20:00

Wed
10:00-13:00

Thu
9:00-16:00

Fri-Sat
9:00-14:00

Sun
closed

Mon: 9:00-19:00
Tue: 9:00-20:00
Wed: 10:00-13:00
Thu: 9:00-16:00
Fri-Sat: 9:00-14:00
Sun: closed

Mon:      9:00-19:00
Tue:      9:00-20:00
Wed:     10:00-13:00
Thu:      9:00-16:00
Fri-Sat:  9:00-14:00
Sun:          closed

I like the one inside '`', takes less space.
Let's go with ISO 8601

@diasdavid the code comment version you mean?

yes :)

@diasdavid It's a tiny bit taller though than the horizontal table, only if a lot of they days have different opening hours. I think most of the opening hours will only be a 2-3 lines in which case the code comment is gonna be smallest

authors: diasdavid watson


text:
t项目中使用了DoraemonKit，导致了项目中UITextView和UITextField不能复制粘贴了,这个问题还是比较影响我们项目使用的

Please complete the following informations.

Expected behavior and actual behavior.
Steps to reproduce the problem.
Android or iOS? OS version? Brand?
More informations such as error messages and stack traces are welcomed.

请补充如下信息。

期望的表现和实际的表现。（如有）
问题重现的步骤。（如有）
Android 还是 iOS？系统版本是多少？手机品牌是什么？（如有）
其他的错误信息和堆栈信息如果有也可以一并提供出来。（如有）
最好给我们提供可以复现问题的Demo

刚试了，没有影响

刚试了，没有影响

嗯，我排查发现 [[CJDeveloperEnvironmentManager shareInstance] install];
这段代码导致复制粘贴功能失效的，把上面这句代码放在[self.window makeKeyAndVisible];后面就可以了，具体原因我还不知道，估计是window导致的
------------------ 原始邮件 ------------------
发件人:                                                                                "didi/DoraemonKit"                                                                                <notifications@github.com>;
发送时间: 2021年1月26日(星期二) 上午9:44
收件人: "didi/DoraemonKit"<DoraemonKit@noreply.github.com>;
抄送: "灿烂人生"<2649154231@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [didi/DoraemonKit] t项目中使用了DoraemonKit，导致了项目中UITextView和UITextField不能复制粘贴了,这个问题还是比较影响我们项目使用的 (#728)
刚试了，没有影响
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

嗯，我排查发现 [[CJDeveloperEnvironmentManager shareInstance] install];
这段代码导致复制粘贴功能失效的，把上面这句代码放在[self.window makeKeyAndVisible];后面就可以了，具体原因我还不知道，估计是window导致的
------------------ 原始邮件 ------------------
发件人:                                                                                "didi/DoraemonKit"                                                                                <notifications@github.com>;
发送时间: 2021年1月26日(星期二) 上午9:44
收件人: "didi/DoraemonKit"<DoraemonKit@noreply.github.com>;
抄送: "灿烂人生"<2649154231@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [didi/DoraemonKit] t项目中使用了DoraemonKit，导致了项目中UITextView和UITextField不能复制粘贴了,这个问题还是比较影响我们项目使用的 (#728)
刚试了，没有影响
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

authors: canlanrensheng songhongkang

repo: didi/DoraemonKit


text:
[功能需求] 支持国际化

包括：

console输出
extension menu文本
extension control文本
其他一些message和标题等

十分感谢你们的贡献。我目前有开发英文GUI绘图软件的需求，这个框架十分合适。如果支持国际化该框架使用范围一定会更广泛，请予以考虑。

感谢反馈，我们会讲国际化排上日程。目前extension建议自定义应该也能满足国际化。另外，也欢迎一起大家参与进来，给LogicFlow提PR，我们对PR持开放态度。

我可以尝试开发国际化相关功能，提供一个t函数根据key查找各语言翻译。但是想请问按现在的core与extension两个package并列的情形，若要共享国际化代码，是否可以且有必要添加一个与这两个package的新package？

可以考虑一个新package，具体看你实现。需要注意目前core是umd格式，请不要把非中文的内容打包进行，国际化支持最好做成按需引入。

@THUzxj 以发布到v1.2.0-alpha.2版本，您可以试试。

authors: THUzxj towersxu

repo: didi/LogicFlow


text:
feat: 支持动态修改画布背景配置

1、支持动态修改画布背景配置
2、增加动态修改画布背景配置示例

cool，我们看下

authors: CWsuper DymoneLewis


text:
feat(textarea-item): hide delete icon when blur #589

背景描述
#589 这次在交互上改进下
主要改动
小叉叉在失去焦点就消失, foucs的时候又重新显示焦点

Codecov Report

Merging #593 into dev will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             dev     #593      +/-   ##
=========================================
+ Coverage   81.1%   81.11%   +0.01%
=========================================
  Files         98       98
  Lines       2821     2823       +2
  Branches     550      550
=========================================
+ Hits        2288     2290       +2
  Misses       376      376
  Partials     157      157

Impacted Files
Coverage Δ

components/textarea-item/index.vue
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-io msdlisper

repo: didi/mand-mobile


text:
🛑 heimv-demo is down

In 1d43ba4, heimv-demo (https://demo.heimv.ch) was down:

HTTP code: 403
Response time: 330 ms

Resolved: heimv-demo is back up in 1c66737 after 42 days, 15 hours, 59 minutes.

repo: diegosteiner/heimv-monitor


text:
How to use future builder inside silverlist;

SliverList(
delegate: SliverChildBuilderDelegate((_, index) {
final song = songs[index % songs.length];
return ListTile(
leading: Image.network(
song.image,
height: 30,
fit: BoxFit.cover,
),
title: Text(
song.title,
),
trailing: IconButton(
onPressed: () => null,
icon: Icon(
Icons.add,
color: Colors.pinkAccent,
),
),
);
}, childCount: 20),
),
inside this one,got it from your file

This should be in stackoverflow

This should be in stackoverflow

Dear you have done it, i m using your exapmles, but you have used static list and i m getting data from api, so i need to use future builder inside that sliverlist,if you can help please

I could help you. Drop me a mail to this gowthamseafret@gmail.com

gowthamseafret@gmail.com

i have sent you an email, please have a look !

authors: GowthamF atta1234 diegoveloper

repo: diegoveloper/flutter-samples


text:
Add custom error type for infallible::checked and remove clippy annotations

Motivation
Change the error type returned by checked from String to a custom type that implements Error.
This also removes the unnecessary annotations to ignore clippy arithmetic errors, they are not needed and were causing errors when using the macro.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Manually tested by creating dummy code and running cargo clippy -- -W clippy::integer_arithmetic
Related PRs
https://github.com/diem/diem/pull/7423#pullrequestreview-583585006

LGTM

/land

authors: msmouse rgamba

repo: diem/diem


text:
Allow to rename table columns in table! macro and do it automatically for invalid names

I have a table with a column named "mod", which is not valid identifier in Rust.
Even for valid identifiers, I want to be able to use different name than what database provides,
is that possible?
Same thing should be applied to table names.

Yes, this is something we want to allow. There is a previous discussion (probably outdated a bit by now) in #424.
@Fiedzia do you have a concrete suggestion for the syntax to rename columns in table!?

The naive solution would be to add some for of "real name" as foo -> Integer,
but ideally table! enhancement should take into account other things one may want to set there.
I consider Django ORM to be a golden standard in this regard because it incorporates
a lot of domain knowledge in this aspect (among other reasons), and for example here are some of the things it allows to set in field definition:

nullability
can the value be blank
choices (this one is also important for me)
column name
if an index should be created for this field (multifield indexes are property of a table)
tablespace
default value
if it is primary key (multifield indexes are property of a table)
human-readable field name
validators
(some other django-related bits I'll ignore here)

as well as properties specific for particular field type:

precision (for decimal fields)
max_length for text fields

https://docs.djangoproject.com/en/1.11/ref/models/fields/
Perhaps not all of it makes sense for Diesel, but I'd prefer to have generic and extensible solution for setting field and table attributes.
As  for syntax, I'd suggest something similar to Django:
table! {
users {
id -> Integer(primary_key: true),
name -> VarChar(db_column: "username", max_length:120),
properties:
indexes: ...
db_table: "user"
}
}
(I find ":" more readable than "=")

Let's keep the feature focused. The use case we want to support here is renames, we don't need to complicate things by adding a bunch of other information that Diesel does not care about (and likely never will).
I'm more in favor of using attributes for this, but want to make sure the naming makes it very clear what is the Rust side and what is the SQL side.
table! {
    users {
        id -> Integer,
        #[database_name="username"]
        name -> Text
    }
}

I'd also like to see a concrete proposal for the conventional renames for Rust keywords.

#[database_name="username"]

I don't mind the format for setting attributes, but I'd prefer to all this attribute column_name or database_column_name - that makes clear what it does even for someone not familiar with diesel.

I'd also like to see a concrete proposal for the conventional renames for Rust keywords.

Django adds _field sufix in this case. Since Diesel uses column name, that would be _column.
https://github.com/django/django/blob/master/django/core/management/commands/inspectdb.py#L202
However, this is inconsistent with column names being numbers, which need to prefixed, so perhaps just always prefixing would be better. Therefore my proposal would be:
"ops" => column_ops
"12345" => column_12345
I'd be happy if whole normalization (and adding comments to explain it) would be stolen from Django.

I'd rather not establish a convention for column names containing only numbers (or any other column which is not valid as an unquoted identifier in SQL)

You will need to have some convention, interact with user or generate code that doesn't compile (as it is now). Of those three, I'd definitely prefer convention. Interacting with database tool for some large database is not something I'd enjoy doing. I am working with a system that has dozens of databases and thousands of tables. I have no idea how many of those are not valid identifiers in Rust, but I do not want to go through all of them and make a decision how it should be renamed for every case.

Why should we special case numbers but not spaces? Or other characters that aren't valid identifiers? We would have to conventionally handle any arbitrary sequence of characters. infer_schema! does not need to handle absolutely every possible edge case, as long as we provide the tools for users to make it work on their own. Providing renames does that.
That said, the issue with Rust keywords (notably type) is incredibly common, and a frequent source of friction that does warrant special casing.

Why should we special case numbers but not spaces?

My opinion is that Diesel should handle everything - I've linked to Django as it covers a lot of cases (I am not sure if all, but many more than just numbers and keywords).

infer_schema! does not need to handle absolutely every possible edge case, as long as we provide the tools for users to make it work

The problem is that this can be extremely tedious and user-unfriendly work. There is no point in users doing it at all.

There is no point in users doing it at all.

I agree, which is why the overwhelming majority of the time, you won't see column names that aren't valid SQL identifiers.

I agree, which is why the overwhelming majority of the time, you won't see column names that aren't valid SQL identifiers.

They do exist though, I can't ignore that, and I want the tools I am using to deal with that without involving me. I do not want for example to break my build scripts just because someone decided to add some column that Rust doesn't like. This is trivial problem to solve and I see no reason why a database tool should ever expose such issues to users. Perhaps look at this in context of creating web project as a whole, which includes using multiple tools. Preferably all of them should work as smoothly and automatically as it is possible.

I'm not claiming that they don't exist, I'm saying that they're not common enough to warrant any sort of convention for automatically renaming them, especially since columns that are invalid SQL identifiers are by definition breaking convention. The issue is already going to be exposed to the user when they have to figure out what we renamed their column to.
Anyway we're not getting anywhere by debating that further. I think you've made your position very clear. What I'd like to move forward with for the time being is an annotation to allow renames (something like database_column_name sounds good I think), and then a separate PR that introduces the conventional column renames for Rust keywords. I'm not sold on column_ as a prefix, but we can discuss that in the PR.

Great, thanks.

Also interesting: Column names that collide with type names that are in scope: #1018

Apologies for missing this issue; apparently my google-foo isn't as good as I'd hoped.
In terms of re-name syntax, I'm not massively familiar with writing macros, but is it possible to do something like this:
table! {
    users {
        id -> Integer,
        name as username -> Text
    }
}

@Measter It is possible, but I do not like that syntax. Which side is the rust side? Which is the SQL side? I'd strongly prefer something that uses an attribute (for consistency with Rust's syntax), and makes it clear in the name which side is which.

@sgrif And I think it wouldn't look good with keywords (if it even works), type as type_ vs
#[column_name="type"]
type_

Agreed

Fixed by #1084 and #1110

I don't think this issue should have been closed. The initial poster specifies:

Same thing should be applied to table names.

But the fix in #1084 only applies to column names. I also am interested in a fix that applies to table names as well.

Can you open a new issue for renaming table names?

authors: Eijebong Fiedzia Measter kardeiz killercup sgrif

repo: diesel-rs/diesel


text:
Add a contains method for postgres range types

Fixes #2210
(I've just needed this method, so I can simply put it into upstream
because it's probably useful for others too)

How to allow nullable Range?
I add
impl<ST> RangeHelper for Nullable<Range<ST>> {
    type Inner = ST;
}

But how impl<T, ST> PgRangeExpressionMethods for T for nullable range?

@a1ien It's already implemented for Nullable<Range<ST>>, but not released yet.


text:
Workflow for KI-Assistert Dokumentasjon mellom Figma, GitHub og Storybook

Mål:
Som basert på erfaringer fra #2850 skal jeg utforske hvordan man kan etablere en enkel, men repeterbar prosess for dokumentasjon med KI-støtte, som fungerer for å involvere både designere og utviklere
1. Kartlegge kilder og faktorer:

[x] Lag en liste over alle dagens kilder (f.eks. Word-dokumenter, Markdown-filer, Storybook) og noter hva slags informasjon de inneholder.
[x] Definere faktorer for hva som gjør dokumentasjon “god” (f.eks. konsistens, klarhet, oppdaterthet).
[x] Samle kilder for inspirasjon, dokumentasjon og accessibility.
[ ] Skisse ut rammeverk-workflow
[ ] Scrape-dokumentasjon fra Storybook (Takket være Benjamin Brodie sitt verktøy!)

2. Eksperiment med KI for én komponent

[ ] Velge én komponent og bruk KI til å lage et førsteutkast av dokumentasjon basert på tilgjengelige kilder.
[ ] Hold malen enkel og lett å forstå, slik at både KI og mennesker kan forholde seg til den.

3. Utforme et enkelt flytskjema:

[ ] Tegn opp en enkel flyt for hvordan dokumentasjon skal gå fra kilde -> KI-utkast -> manuell validering -> publisering.
[ ] Identifiser hvor og når faktorer/kilder brukes i denne prosessen.

4. Vurder alternativer for å samle kilder

[ ] Se på om GitHub kan fungere som en “source of truth” for dokumentasjonstekst.
[ ] Noter hvilke endringer som må til for å gjøre dette mer strømlinjeformet (f.eks. standardmal, mappe-struktur, lenker til Figma).

5. Få tilbakemelding fra teamet

[ ] Presenter funn og forslag for kolleger (designere, utviklere, interne/eksterne).
[ ] Be om innspill på brukervennlighet, verktøy og forbedringspunkter. Avdekke blockers.
[ ] Juster planen basert på konstruktive tilbakemeldinger før neste runde med testing og implementering.

Disse oppgavene bygger videre på de avsluttede erfaringene, men fokuserer på å utforske og konkretisere nye løsninger uten å binde seg til en endelig prosess med én gang.

Takk for meg i designsystemet! Utforsker dette videre i R&D Lab, og markere den som closed.

repo: digdir/designsystemet


text:
Add a SourceBuilderInterface along with two basic implementations

The FileSourceBuilder just does \file_get_contents() on a file, so it's not that useful unless we change the API to accept only Source and not string.
The DirectorySourceBuilder is more interesting since it allows people to split their giant SDL files into multiple logic units (e.g. one for Relay, one for common sorting/ordering stuff, etc.).

It's based on the minor-fixes branch so it'll need a rebase once that one's gone in. @crisu83 what do you think about this? I've tested it locally in a small project and the directory source builder works as intended.

Rebased

The DirectorySourceBuilder could perhaps be more useful if instead of reading a directory it just took an array of absolute paths to files. This way it would be possible to include partial schema files from dependencies (e.g. our Relay implementation) without having to copy-paste definitions.

This is actually more a reader than a builder, am I correct? So maybe we should call it SourceReader instead. What do you think @Jalle19?

I'll think of something

@crisu83 I changed DirectorySourceBuilder to MultiFileSourceBuilder. Should I update the public API too? We need to decide that before I do any README changes.

Let's change the public API later. However, we should use the builder instead of file_get_contents in our examples.

Okay, I'll update the PR

Addressed all the comments and updated the README

repo: digiaonline/graphql-php


text:
Should this be used in production?

Should this repo be used in production or is this purely for developing purposes? How do you do upgrades and database migrations?

I could find the answer by myself:
It seems this is used in an production environment.
Source: http://digital.deichman.no/blog/2015/01/12/working-with-koha-at-oslo-public-library/

Hi, thanks for your interest!
Actually it has been production ready for a while, but we will have an official launch in about a month. It is part of a larger setup with docker compose and docker containers including elasticsearch, fuseki and self-produced patron interface and cataloguing tools. The main metadata repository is moved out of Koha to a RDF store and a service which propagates the neccessary data for Koha to work as a circulation system. We believe firmly that Koha and its MARC-centric bibliographic system is insufficient for providing and presenting modern library metadata.
The full project is at https://github.com/digibib/ls.ext (library system extended), but in short, it is mainly isolated microservices in a docker network. Mysql and the database, for instance, are separate containers and volumes that are easily exchanged.
Upgrading in production is as easy as switching containers, yet, of course, as long as db upgrade between koha versions work.
Please get in touch if you have more questions!
Benjamin
Oslo Public Library

authors: bensinober foobarable

repo: digibib/koha-docker


text:
Pades-URL endringer

Hei dere.
Opplever en litt merkelig sak relatert til Pades-URL'ene vi får tilbake når vi henter status på signerings-jobber.
Det er litt tilfeldig om vi ved første status-request etter fullført signering får en URL som følger formatet
https://api.signering.posten.no/api/org-nummer/archive/documents/job Id--j/pades
eller
https://api.signering.posten.no/api/org-nummer/archive/documents/32-tegns GUID/pades
Hvis man kjører en ny status-oppdatering på jobber med Job-id i URL'en så endres de til en GUID-basert URL etter noe tid.
I tillegg så virker det som at det eksisterer en redirect fra gammel job-id URL til ny GUID URL og denne skaper litt trøbbel for oss da plattformen vår integrasjon kjører i ikke ser ut til å håndtere redirecten på en god måte.
Rimelig sikker på at redirect-problemet ligger på vår ende men for å komme fram til en god løsning så hadde det vært hjelpsomt med litt informasjon fra dere:

Er det slik at Pades-URL'en endres på et eller annet punkt etter signering og hvordan er i så fall timingen på dette?

Flyt-diagrammet for direkte-signering (https://raw.githubusercontent.com/digipost/signature-api-specification/main/integrasjon/flytskjemaer/synkron-maskin-til-maskin.png) spesifiserer at man skal "bekrefte ferdig prosessering" før dokumentene lastes ned mens teksten spesifiserer det motsatte (Step 4 - Get Signed Documents. Step 5 - Confirm finished processing). Hva er riktig rekkefølge?

Pades-URL endres på et punkt, etter at et oppdrag er ferdigsignert, slik du opplever. Da vil "gammel" URL gi tilbake en standard 301 Moved Permanently-respons med den nye URL-en med UUID/GUID. Redirects er et standard aspect i HTTP, og burde være mulig å skru på i HTTP-klienten man bruker, om det ikke er skrudd på by default.

Timingen vil være noe ulik fra gang til gang, og er egentlig ikke noe man lene seg på.
Det du ev. kan gjøre, dersom du ikke får skrudd på "follow redirect" i klienten du bruker, er å inspisere URL-en du får etter at jobben er ferdigsignert, og forkaste statusoppdateringen inntil du får en URL som ikke inneholder <jobId>--j, og kan da anta at dette er "final" URL. Dette er egentlig ikke å anbefale, da API-et i prinsippet på et senere tidspunkt kan gi en ny redirect-respons, og da vil ~hacken~ workarounden ikke fungere lenger. Dog er nok dette svært lite sannsynlig at det vil dukke opp mer redirects her.

"bekrefte ferdig prosessering" betyr egentlig at status-responsen er mottatt, og trenger ikke å bli utlevert lenger fra API-et. Ideelt sett bør prosessering av en statusrespons være så rask og enkel som mulig, typisk bare å persistere den, slik at man på et senere tidspunkt kan gjøre handlinger knyttet til håndteringen av status på jobben, f.eks. laste ned ferdigsignert dokument (PAdES). Men det er ikke noe i veien for å gjøre nedlasting av PAdES samtidig som man får en status-respons og prosesserer responsen, det blir litt opp til hver enkelt integrasjon. I øyeblikket man "bekrefter ferdig prosessering" så signaliserer du til API-et at denne status-oppdateringen ikke skal bli utlevert lenger. Dersom man ikke "bekrefter ferdig prosessering" vil statusoppdateringen bli utlevert på nytt. Dette er for å forhindre at man "mister" en statusoppdatering i tilfelle man har en feil (exception) i håndteringen.

Lukker denne. Åpne den igjen om du har behov for det.

authors: adoermenen runeflobakk

repo: digipost/signature-api-specification


text:
🛑 Query API is down

In b1ce3f3, Query API (https://datasette.planning.data.gov.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Query API is back up in 1de3dc5.

repo: digital-land/service-status


text:
what I did wrong?

`git clone https://github.com/digitalbirdo/BT-LinkkeySync
Cloning into 'BT-LinkkeySync'...
remote: Enumerating objects: 42, done.
remote: Total 42 (delta 0), reused 0 (delta 0), pack-reused 42
Unpacking objects: 100% (42/42), done.
Mac-Pro-Rodion:src rodion$ cd BT-LinkkeySync/
Mac-Pro-Rodion:BT-LinkkeySync rodion$ chmod +x BT-LinkkeySync.py
Mac-Pro-Rodion:BT-LinkkeySync rodion$ sudo ./BT-LinkkeySync.py
Password:
BT-Linkkeysync by DigitalBird

get Bluetooth Link Keys from macOS and store it to blued.plist
convert exported list from binary to xml
parse the converted plist
Convert the Link Keys and store them to btkeys.reg
Bluetooth 2.0:    1 Links keys found
Traceback (most recent call last):
File "./BT-LinkkeySync.py", line 52, in
f.write('\r\n"'+device.replace("-","")+'"=hex:'+ convertToWinRep(pl["LinkKeys"][adapter][device].data.hex()))
AttributeError: 'str' object has no attribute 'hex'
`

btkeys.reg.zip
blued.plist.zip
Here are files

btkeys.reg.zip
blued.plist.zip
Here are files

it works much better from Windows to macOS
setup all the devices in Windows
export reg
`Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BTHPORT\Parameters\Keys\001a7dda7113]
"d49a207f0a02"=hex:9b,40,75,a7,66,77,d1,cd,26,28,05,d4,59,2a,98,02`
convert to blued.plist
{     LinkKeys =     {         "00-1a-7d-da-71-13" =         {             "d4-9a-20-7f-0a-02" = <02982a59 d4052826 cdd17766 a775409b>;         };     }; }
and copy to its place

it works much better from Windows to macOS
setup all the devices in Windows
export reg
`Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BTHPORT\Parameters\Keys\001a7dda7113]
"d49a207f0a02"=hex:9b,40,75,a7,66,77,d1,cd,26,28,05,d4,59,2a,98,02`
convert to blued.plist
{     LinkKeys =     {         "00-1a-7d-da-71-13" =         {             "d4-9a-20-7f-0a-02" = <02982a59 d4052826 cdd17766 a775409b>;         };     }; }
and copy to its place

the calculator from 9b,40,75,a7,66,77,d1,cd,26,28,05,d4,59,2a,98,02 to 02982a59 d4052826 cdd17766 a775409b
#!/bin/sh read s s=$(echo $s | tr -d ',') for i in {15..0} do result=$result${s:$(( i * 2 )):2} done echo ${result}

the calculator from 9b,40,75,a7,66,77,d1,cd,26,28,05,d4,59,2a,98,02 to 02982a59 d4052826 cdd17766 a775409b
#!/bin/sh read s s=$(echo $s | tr -d ',') for i in {15..0} do result=$result${s:$(( i * 2 )):2} done echo ${result}

from Windows BTKeys.reg to Mac blued.plist
`cd "$(dirname "$0")"
/usr/libexec/PlistBuddy -c "Add LinkKeys dict"   /tmp/temp.plist
input=BTKeys.reg
while IFS= read -r line
do
if [[ "$line" == 'HKEY_LOCAL_MACHINE' ]]
then
s=$(echo ${line:78:12} | sed 's/.{2}/&-/g')
s=${s%?}
t=$s
/usr/libexec/PlistBuddy -c "Add LinkKeys:$t dict"   /tmp/temp.plist
fi
if [[ "$line" == '=' ]]
then
s=$(echo ${line:1:12} | sed 's/.{2}/&-/g')
s=${s%?}
key=$s
s=$(echo ${line:19:47} | tr -d ',')
value=$s
echo $key $value
echo $value | xxd -r -p > /tmp/bin
/usr/libexec/PlistBuddy -c "Import LinkKeys:$t:$key /tmp/bin" /tmp/temp.plist
plutil -convert binary1 /tmp/temp.plist
fi
done < "$input"
cp /tmp/temp.plist ./`

from Windows BTKeys.reg to Mac blued.plist
`cd "$(dirname "$0")"
/usr/libexec/PlistBuddy -c "Add LinkKeys dict"   /tmp/temp.plist
input=BTKeys.reg
while IFS= read -r line
do
if [[ "$line" == 'HKEY_LOCAL_MACHINE' ]]
then
s=$(echo ${line:78:12} | sed 's/.{2}/&-/g')
s=${s%?}
t=$s
/usr/libexec/PlistBuddy -c "Add LinkKeys:$t dict"   /tmp/temp.plist
fi
if [[ "$line" == '=' ]]
then
s=$(echo ${line:1:12} | sed 's/.{2}/&-/g')
s=${s%?}
key=$s
s=$(echo ${line:19:47} | tr -d ',')
value=$s
echo $key $value
echo $value | xxd -r -p > /tmp/bin
/usr/libexec/PlistBuddy -c "Import LinkKeys:$t:$key /tmp/bin" /tmp/temp.plist
plutil -convert binary1 /tmp/temp.plist
fi
done < "$input"
cp /tmp/temp.plist ./`

`git clone https://github.com/digitalbirdo/BT-LinkkeySync
Cloning into 'BT-LinkkeySync'...
remote: Enumerating objects: 42, done.
remote: Total 42 (delta 0), reused 0 (delta 0), pack-reused 42
Unpacking objects: 100% (42/42), done.
Mac-Pro-Rodion:src rodion$ cd BT-LinkkeySync/
Mac-Pro-Rodion:BT-LinkkeySync rodion$ chmod +x BT-LinkkeySync.py
Mac-Pro-Rodion:BT-LinkkeySync rodion$ sudo ./BT-LinkkeySync.py
Password:
BT-Linkkeysync by DigitalBird

get Bluetooth Link Keys from macOS and store it to blued.plist
convert exported list from binary to xml
parse the converted plist
Convert the Link Keys and store them to btkeys.reg
Bluetooth 2.0:    1 Links keys found
Traceback (most recent call last):
File "./BT-LinkkeySync.py", line 52, in
f.write('\r\n"'+device.replace("-","")+'"=hex:'+ convertToWinRep(pl["LinkKeys"][adapter][device].data.hex()))
AttributeError: 'str' object has no attribute 'hex'
`

run it with python3

run it with python3

thanks
I already did the entire script in bash, no python required  :)
https://github.com/digitalbirdo/BT-LinkkeySync/issues/18

run it with python3

python3 BT-LinkkeySync.py
BT-Linkkeysync by DigitalBird

get Bluetooth Link Keys from macOS and store it to blued.plist
Password:
convert exported list from binary to xml
parse the converted plist
Traceback (most recent call last):
File "/Volumes/Untitled/BT-LinkkeySync-master/BT-LinkkeySync.py", line 27, in
pl = readPlist("./blued.plist")
NameError: name 'readPlist' is not defined
Mac-Pro-Rodion:BT-LinkkeySync-master rodion$
the same. deleted as useless

@roddy20 of you're Russian or speak Russian please write me on telegram, username the same with GitHub, need help with your script, can't import

repo: digitalbirdo/BT-LinkkeySync


text:
Add API from SUMM.AI to create easy-understable German

Motivation
Summ.ai is an MT-service for easy understable german. They developed an API-service for us so that we can offer municipalities https://summai.notion.site/SUMM-API-Documentation-external-fc41fa5ef1434ad2b311be4876b4685a
Proposed Solution
Implement the Summ.ai API in a similar way to the DeepL API from Johannes' Project. The Summ-Team asked as if we can deliver the "instance slug" as user (muenchen, augsburg, lkaugsburg) so that they can track which city uses the API most often.
credentials for the API are in Passbolt
Alternatives

Additional Context

Is this sth. we good handover to kiitos or @JoeyStk ?
Still got one deadline for 30th September 2022

repo: digitalfabrik/integreat-cms


text:
Change flags for Kurdish, Kurmanji and Sorani

Motivation
Kurmanji is spoken in many countries, currently we use the Syrian flag, we should use a non-political flag. Sorani is spoken in two countries, one being the autonomous region of Kurdistan, maybe it would also be good to change the flag.
Proposed Solution
Create a flag/flags similar to the Arabic and Farsi flags - theoretically we only need Kurmanji and Sorani, but for that to work we need issue INFRA-214 closed (merging Kurdish and Kurmanji).
Alternative
Only substitute Kurmanji - Sorani is only spoken in two countries and we have those flags in the system.

Just for reference: New flags have to be added to my fork of the flagpack library before we can use them in the Integreat CMS:
https://github.com/timoludwig/flagpack-dart-sass

authors: osmers timoludwig


text:
Create manual for simulations

We need a manual that helps person to input the correct data, especially object types.

We should add example images for boats and corresponding type in opendrift
Common must haves:

12m rubberboat
small aluminium fishing boat

authors: julled svenseeberg

repo: digitalfabrik/opendrift-leeway-webgui


text:
Libvirt locks on getResponse()

Hi,
I have some goroutines:

One for listening and processing domain lifecycle events. Call DomainGetState for each domain from event;
Multiple for handling start/stop VM's and wait until state become to required sequentially call DomainGetState;
One for collecting and processing metrics for every domains. Use DomainBlockStats, DomainInterfaceStats and etc. function for collecting metrics.

I faced with an next issue: sometimes, when I request to start or stop multiple domain at once, all those goroutines is stuck. I try to dig into this issue and find out that all goroutines is blocked on digitalocean/go-libvirt.Libvirt.getResponse() because cannot read message from channel. Unfortunately this is a floating bug and I cannot find how to reproduce it.
For now I use this workaround:
const getResponseTimeout = 5 * time.Second

func (l *Libvirt) getResponse(c chan response) (response, error) {
	timer := time.NewTimer(getResponseTimeout)
	defer timer.Stop()

	var resp response
	select {
	case <-timer.C:
		return response{}, fmt.Errorf("cannot get response from libvirt within %s", getResponseTimeout)
	case resp = <-c:
	}
	if resp.Status == StatusError {
		return resp, decodeError(resp.Payload)
	}

	return resp, nil
}

Anyone have some thoughts why this happens?

Ok, I will try to reproduce and dump goroutines.

Goroutines dump in attached file.
goroutines.txt

thanks, how much vm i can ran to may be reproduce this issue? 50 is enough?

We reproduce this bug with 5 VMs. The main thing that all operations should perform in parallel.

https://github.com/digitalocean/go-libvirt/pull/98 fix this

Looks like we found why we got a random hang on libvirt connection. We use the same connection for sending commands and for receiving events. And we got an idea that this is a key to the problem. So now we use two different connections. One is read-only for events and second for the commands and everything looks good.

authors: WanLinghao dshemin freedemster vtolstov

repo: digitalocean/go-libvirt


text:
HTML code when creating device role?

Issue type: Bug

Python version: 2.7.12
NetBox version: 1.9.5

I just added a device role and in the green box after creation I got this:
Created device role Storage  Add a device role

Same when creating a device type:
Created device type DS216J

Looks potentially related to #1061, but that change was made in 1.9.6. Please upgrade to 1.9.6 and see if it resolves the issue.

Hmm.. ok I think I'm running 1.9.6, however at the bottom of the screen it still shows 1.9.5, even if I try flushing my browser, incognito, different browser... but when I look in settings:

root@netbox1:~# grep VERSION /opt/netbox/netbox/netbox/settings.py
VERSION = '1.9.6'

Am I missing something?

root@netbox1:/opt/netbox# git pull
Already up-to-date.

root@netbox1:/opt/netbox# cat .git/config
[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        url = https://github.com/digitalocean/netbox.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
        remote = origin
        merge = refs/heads/master

Did you restart the WSGI service? E.g. supervisorctl restart netbox?

Ok yes restarting 'supervisor' did the trick for me!  I don't see the HTML code anymore.
I wonder if adding a note to the upgrade.sh to restart it manually or having it check to see if we are using supervisor and restart it?

Restarting the WSGI service is already called out pretty prominently in the docs. Unfortunately it's not something we can automate because not everyone implements it the same way.

authors: jeremystretch mzac

repo: digitalocean/netbox


text:
span tests - new tests tab next to the errors tab

Add a new tab next the the errors tab with the name "Tests"
This tab should contain JCEF control
please add comment with the branch name to issue #https://github.com/digma-ai/digma-ui/issues/356 so we can start working on the UI side

Closed in #1563

authors: kshmidt-digma shaykeren

repo: digma-ai/digma-intellij-plugin


text:
Dashboard Menu Typo Fix

Fixed ‘dashboard’ typo in menu. Removed duplicates in language JSONs.

Thanks!

authors: dignajar joryphillips

repo: dignajar/bludit


text:
fix couchdb2 requirement

:( had the wrong repo
@mkangia thisis important to fix and do a  ansible-galaxy install --force

@emord actually the problem is (i think) that the couchdb-cluster repo requires the couchdb repo, but not the latest one, so it keeps pulling the one which doesn't create the parent dir :( We can get around it, re-installing the appropiate couchdb repo manually. or fixing this in your repo.

@javierwilson I think we could also require the both repositories in our requirements yml?

yes, as long as we require the cloudb-cluster repo first, it will work, still a force install is required. testing and commiting...

@emord this fixes the requirements issue, there's still an issue regarding the data directory not existing, but that will go in a different PR

@javierwilson ah. i think I know what happened with the data directory. originally I had the data directory created by the ansible task, but the maintainer asked me to put it in the init script. I removed that when I discovered that that would create the directory even if the encrypted drive wasn't mounted. I probably didn't add that back to the ansible task.

authors: emord javierwilson

repo: dimagi/commcarehq-ansible


text:
Upgrade to apache-superset==3.1.0

Upgrades hq_superset to apache-superset==3.1.0
This required a few tweaks:

superset.dataset.commands moved to superset.commands.dataset
is_user_admin() became security_manager.is_admin()
get_sqla_engine() method became get_sqla_engine_with_context() context manager.
The parameters of a couple of commands changed

That was about it.

Nice!


text:
NPM release with recent changes

[x] I have checked existing issue and found none that could answer my question.

When will the new NPM release happen? Will it happen? For example graphql version 16 support is something we're looking forward to receive. We'd want to keep using graphql-shield untill we get some time to migrate from it to more maintained options.

@dimatill @maticzav

@hayksaryan it will happen. we're working on it. it should happen either this week or in a few weeks

Thanks for the information 🙏

recent changes were released. graphql v16 support is there

authors: dimatill hayksaryan

repo: dimatill/graphql-shield


text:
Handle errors in async handlers

Any chance you could support handling errors in async handlers? I use express-async-errors with express to avoid the ugly try catch next block in every handler. It would obviously have to be in an option since it's not normal express behavior.

router.js
第487行
 out.catch(err => {      throw err; });
改为
                             out.catch(err => {                                 this._handleError(err, req, res);                                 return resolve(true);                             });

There's now an option to support async errors: app.set('catch async errors', true) in 1.3.0

authors: dimdenGD dwbboy hillac

repo: dimdenGD/ultimate-express


text:
🛑 android-14.0.0_r2 is down

In 2c17178, android-14.0.0_r2 (http://aospxref.com/android-14.0.0_r2/) was down:

HTTP code: 404
Response time: 644 ms

Resolved: android-14.0.0_r2 is back up in 4618cdf after 9 minutes.

repo: dimenspace/aosp-uptime


text:
Improve collision masks API

Currently collision masks just raw bits. It would be great to have a macro as in heron for enums to convert members to bits. This will allow to have a lot of convenient methods in InteractionGroups. In heron it named CollisionLayers:
So basically my suggestion is to make masks API similar to heron.

On second thought maybe it's better to use an external crate for it, like https://github.com/bitflags/bitflags


text:
add location of image in the cluster

Adds more information as requested in #7

nice change. thanks!

authors: dims yashodhanmohan

repo: dims/community-images


text:
pXY loss not dropping

Hi! Many thanks for the cool repo and paper. I'm training the network on a custom dataset, but pXY is not dropping, and therefore the results are not satisfactory. While you were training your networks, did you face such an issue? Do you have any recommendations to improve this? Many thanks in advance!

Thanks for your interest in our work! I didn't encounter any issue regarding the object center offset regression (delta_Pxy). Regressing delta_Pxy is a relatively easy sub-task compared to other components because it is just the object's origin projection offset percent (usually within [-0.5, 0.5]) from the cropped image center.
Please make sure that the ground-truth labels for delta_Pxy are correctly calculated, for example, by visually checking the ground-truth.

Thanks!!

authors: dingdingcai shervn


text:
Bootstrap path in cache command

In Laravel 5.2.23 (I think), a new bootstrapPath() method was added to the application container to allow for updating where the bootstrap directory lives. Today I ran into errors when using the api:routes command because my bootstrap directory isn't at the root like the cache command expects.
I was about to send a pull request to update the cache command to use the new method, but when I saw the Composer file referenced some 5.1 components, I wasn't sure it would be accepted since the method was only recently added.
Is there a chance of being able to use the bootstrapPath() method instead of hard-coding the path in? If so, would you want me to check for a Laravel version or for the existence of the bootstrapPath() method?
Appreciate your feedback!

@agentphoenix The package currently supports Laravel 5.1 and 5.2. Pull requests are more then welcome though if you are still having this issue/are interested in doing so.
I think checking for the existence of the bootstrapPath() method would be the way to go. Also since 5.2 is the LTS version, I might bump the package from 5.1 and 5.2 to 5.2 only for version 1.0.0. Don't quote me on that though

@hskrasek I ended up putting a PR in a while back that did that (#1043). When you get around to looking at PRs, just let me know if you want anything changed!

authors: agentphoenix hskrasek

repo: dingo/api


text:
Call directly functions form Arr and Str

Call directly functions form Arr and Str

Unless you can provide a really good reason as to why I shouldn't use the functions I don't see a point in merging this.

Hey @jasonlewis
The purpose is to avoid unnecessary calls, in the array_* and string_* helper functions case, we call and helper function which is doing nothing but calling the real \Suppor\Arr:: or \Suppor\Str:: function.
If the helper function was doing something on the input or the output, it would make sense.
But in this situation not; it is making things slower (and some might think a bit less OO too)

What sort of overhead are we talking about exactly?

Calls to array_ and str_ helpers functions have been removed in favor of \Suppor\Arr:: or \Suppor\Str:: functions in laravel/framework. The functions are directly called without using the helper function (a function calling another function).
Was it the meaning of your question ?

Calling the function directly makes more sense anyway right, instead of the helper?
Even if the overhead is not that high it still would be less efficient to call the helper which would just call the function anyway?

The only plausable reason to change this imo, would be to avoid potential clashes with other function declarations of the same name. But since this is a laravel specific package, that doesn't apply.
I also think any performance consequences of calling a function that calls a method are negligible, especially given the many micro optimisations that could also be made elsewhere in a php application.
Aside from that I do prefer to use the classes directly though, as it feels a little cleaner. Just my thoughts :)

Both you guys @pulkitjalan and @tymondesigns are right indeed.

I cave.
:wink:

authors: jasonlewis lucasmichot pulkitjalan tymondesigns


text:
Wrong example for ignored_files

Thanks for your plugin!
At readme file used next example for ignored files
xcode_summary.ignored_files = '**/Pods/**'

but in code we send relative path to function that check ignore state here link to the code.
Mate, I just spent an hour to understand where I'm wrong :)
I can made PR with example fix or with code fix :)

Good catch @makadaw!
We'll be glad if do the PR.

authors: diogot makadaw


text:
MAC Big Sur logic pro X compatibility

Hello,
Thanks a lot for your work.
Could you please tell me if this plugin works on MAC Big Sur Logic pro X 10.6.1.
I download your mac zip file (spleeter-dj.vst3) and put it in  dans Library/Audio/Plug-Ins/VST3
And I don't see it in Logic pro X...
Do you have an idea ?
Thank you
Have a nice day
Noliverte

Same issue on Catalina.

Maybe try https://github.com/diracdeltas/vstSpleeter/issues/4#issuecomment-634195448 ?

Logic Pro doesn't support VST plugins. You might be able to get it working using an AU wrapper.

authors: RenanDiaz diracdeltas noliverte patrickrushton

repo: diracdeltas/vstSpleeter


text:
Use fetch method from stores

Proposed Semver Increment Bump: [MAJOR/MINOR/PATCH]
Changes Proposed in this Pull Request (List new items in CHANGELOG.MD)

(If Applicable) What Issue does it fix?
channel.fetchMessage, client.fetchUser, guild.fetchMember are no longer available => replaced in Resolver by [store].fetch

This isn't really needed atm since package-locks lock us in to a commit prior to this breaking change.
Will leave this open though

It seems to be already usable :

Komada is using a different Discord.JS version than yours, that's why.

But I do not use Discord.JS directly anymore, only through Komada. It is not in my package.json.

Can you give us the package-lock hash for Discord.JS

{
  "dependencies": {
    "discord.js": {
      "version": "https://registry.npmjs.org/discord.js/-/discord.js-11.1.0.tgz",
      "integrity": "sha1-U1HVnjeY9TbeGXXpLK5NEa89kmY=",
      "requires": {
        "long": "https://registry.npmjs.org/long/-/long-3.2.0.tgz",
        "prism-media": "https://registry.npmjs.org/prism-media/-/prism-media-0.0.1.tgz",
        "snekfetch": "https://registry.npmjs.org/snekfetch/-/snekfetch-3.1.7.tgz",
        "tweetnacl": "https://registry.npmjs.org/tweetnacl/-/tweetnacl-0.14.5.tgz",
        "ws": "https://registry.npmjs.org/ws/-/ws-2.3.1.tgz"
      }
    },
    "komada": {
      "version": "github:dirigeants/komada#2c3d69870f780b714ee929a7fe836c006d7c877f",
      "requires": {
        "chalk": "2.1.0",
        "discord.js": "github:hydrabolt/discord.js#3c532f16bc48175597a7bbed4fbba4637812184d",
        "fs-nextra": "0.2.0",
        "moment": "2.18.1",
        "moment-duration-format": "1.3.0",
        "performance-now": "2.1.0"
      },
      "dependencies": {
        "discord.js": {
          "version": "github:hydrabolt/discord.js#3c532f16bc48175597a7bbed4fbba4637812184d",
          "requires": {
            "long": "3.2.0",
            "prism-media": "0.0.1",
            "snekfetch": "3.2.9",
            "tweetnacl": "1.0.0",
            "ws": "3.1.0"
          }
        }
      }
    }
  }
}

It looks like I forgot to npm prune.
But my version was based on NPM package, not master branch.

NPM Komada shouldn't even be this far into d.js
You also have d.js 11.1
And the underlying d.js within your Komada install does not match the package-lock in the repository
In fact, it's at least 10 commits ahead,

I meant my d.js version was from NPM

Regardless, you have two version of d.js installed.
For the purpose of debugging, I want you to ensure ur package.json only has Komada in it.
And I want you to delete node_modules and package-lock.json
Run npm install and test the fetchMessage and messages.fetch for me.

Removed node_modules and package-lock.json. Only komada in package.json :
package.json
{
   ...
  "dependencies": {
    "discord-emoji": "^1.1.1",
    "komada": "github:dirigeants/komada#master",
    "moment": "^2.18.1",
    "moment-duration-format": "^1.3.0",
    "ytdl-core": "^0.17.0"
  },
}

The other dependencies were installed by komada on the first run
package-lock.json
{
  "dependencies": {
    "komada": {
      "version": "github:dirigeants/komada#2c3d69870f780b714ee929a7fe836c006d7c877f",
      "requires": {
        "chalk": "2.1.0",
        "discord.js": "github:hydrabolt/discord.js#b7c55f02c20bee5dab107ff453a6d3ea1a4a776a",
        "fs-nextra": "0.2.0",
        "moment": "2.18.1",
        "moment-duration-format": "1.3.0",
        "performance-now": "2.1.0"
      },
      "dependencies": {
        "discord.js": {
          "version": "github:hydrabolt/discord.js#b7c55f02c20bee5dab107ff453a6d3ea1a4a776a",
          "requires": {
            "long": "3.2.0",
            "prism-media": "0.0.1",
            "snekfetch": "3.2.9",
            "tweetnacl": "1.0.0",
            "ws": "3.1.0"
          }
        }
      }
    }
  }
}

hmm, I have no idea why, but it's completely ignoring komada's package-locks.
What version of npm

$ npm -v
5.3.0
$ node -v
v8.3.0

NPM seems to be ignoring the package-locks.
Going to manually merge this with a updated package-lock.
Komada will increase to 0.20.8

authors: CyberiumShadow Pandraghon kyranet

repo: dirigeants/komada


text:
TypeError: this.commands.filterArray is not a function

Hello,
Anybody have an idea about that error?
TypeError: this.commands.filterArray is not a function

I'm having the same issue, I don't know why it's closed as it seems this issue is around with the test bot to.

me too

Same for me

Same with me 😭😭

What worked for me is using version 12 npm install discordjs/Commando
See also
https://discordjs.guide/commando/

still not solved... why not they update commando like it is pretty old tbh

THANK YOU SO MUCH @BIRD-UP73 THAT WAS MY ISSUE 😭
I updated from discord.js v11 to v12 and that was the issue

repo: discordjs/Commando


text:
feat(FormattingPatterns): add timestamp

Please describe the changes this PR makes and why it should be merged:
Timezone formatted timestamps!!!!! (but the regex matches)
Reference Discord API Docs PRs or commits:
https://github.com/discord/discord-api-docs/pull/3135

Discord calls them flags: docs

style would probably be a better name, feel free to change the docs lol

authors: advaith1 ckohen devsnek

repo: discordjs/discord-api-types


text:
Problem with agreeing

What is your username and discriminator?
itsrobby#3043
Why did you join Discord Linux?
I am a recent information systems graduate and am familiarizing myself with linux. Currently starting out on ubuntu and running virtual box in there to use Mac OSX and xcode. Really would like a place to find like minded people who may be able to add insight.
Where did you hear about Discord Linux?
I heard about it at a reddit post.
linked:
https://www.reddit.com/r/linuxmasterrace/comments/8yz8y7/anyone_know_any_good_linux_discord_servers/e2f11sk?utm_source=share&utm_medium=web2x
What is the passphrase that was assigned to you by the bot?
6tt5lopvbxf56 <-- this is what literally was in the link. after clicking the link no additional password verification was given. I did read all of the rules and was checking for additional instructions

From simonizor#0420 :
This form is only for people who do not have a phone to verify with Discord. Please read the message that mentions you in the welcome channel.

authors: DiscordLinuxBot itsrobby

repo: discordlinux/rules


text:
Members update

counting deleted topics in assignment_counts issue solved

Would be good to add a ruby test for this as well to check that deleted topics are not included in either count

authors: Ahmedgagan davidtaylorhq

repo: discourse/discourse-assign


text:
Scroll top

Scroll-top on username-filter change

Another conflict here ^^
Also, just checking, does this code run when you click "back" in the browser? We don't want to reset the topicListScrollPosition in that case.

Another conflict here ^^
Also, just checking, does this code run when you click "back" in the browser? We don't want to reset the topicListScrollPosition in that case.

Yaa in that case code works fine😃