text:
Diagnostic and codeActions for missing/outdated Smithy version

We were wondering what would be a good way to push users towards adding the $version statement in their Smithy file. By default, if it's missing, smithy-model assumes 1. But most Smithy files could be using 2 so we discussed a way to have this in the IDE.
The flow is basically: if you don't have a version, we suggest/help to define it explicitly (to 1), and if you use version 1, we suggest/help to update it to 2.
The end result looks like this in VS Code:
https://user-images.githubusercontent.com/5230460/212099585-8f00378d-e1b5-495a-b3f2-c78b2cca5ebf.mov
It works by:

publishing a diagnostic if the version is missing
publishing a diagnostic if the version is found but it contains an older version (1 here)
implement codeAction to generate TextEdit if the diagnostic above are found

For 1, and 2, we read the top part of the Smithy file (in this PR I read 5 lines but this is an arbitrary amount). Then we look for a line starting with $version. If not found we publish a diagnostic, if found but equal to 1, we publish a diagnostic.
Those diagnostic are added on top of any diagnostic generated from validating the model.
The TextEdit are simple:

rewrite the version if it is found (we can reuse the range from the diagnostic to build the TextEdit)
append $version: "1" at the top of the file, explicitly setting the version for the user

On top of that, this PR includes (those could be separated PRs):

a typo fix in some java doc
a fix when using findToken on an empty document

This is great.
What's the rational for defaulting to 1 instead of 2 when no version is defined?
It looks like the 1 to 2 upgrade is suggested regardless of whether the model will work as a 2 model. Is the intent that they will get diagnostics on anything that isn't compatible with 2 and be able to make the other needed changes on their own?
It'd be awesome if the CodeAction could handle making more of those changes with a preview of what it would change, but maybe that could be added later. I think at a minimum, it'd be helpful to have the 1 to 2 suggestion include some additional context. Perhaps link to the migration guide?

It'd be awesome if the CodeAction could handle making more of those changes with a preview of what it would change, but maybe that could be added later. I think at a minimum, it'd be helpful to have the 1 to 2 suggestion include some additional context. Perhaps link to the migration guide?

Do you mean that it could be valuable to have a custom action to update all files (to insert a version, or update a version)?

I think at a minimum, it'd be helpful to have the 1 to 2 suggestion include some additional context.

Good idea, I'll see if I can add that

Do you mean that it could be valuable to have a custom action to update all files (to insert a version, or update a version)?

I meant that for a given file, the code action which is changing 1 to 2 would also be able to do the 1 to 2 migration on that file. For example, it could detect set shapes and change them to list shapes.

Do you mean that it could be valuable to have a custom action to update all files (to insert a version, or update a version)?

I meant that for a given file, the code action which is changing 1 to 2 would also be able to do the 1 to 2 migration on that file. For example, it could detect set shapes and change them to list shapes.

Ahhh ok I see what you mean. I think I prefer to scope code action per diagnostic. In practice that means that once you move to version 2. You'll get a new set of diagnostic. If you use set you'd get one for that.  We could have an independent code action that does that: turn set into uniqueItems on list. Similarly, we could have a codeaction to rewrite enum I believe.

I think at a minimum, it'd be helpful to have the 1 to 2 suggestion include some additional context.

Regarding the note, I think I can add some context to the diagnostic, but not the code action. See the following examples from the Shellcheck extension:

Regarding the note, I think I can add some context to the diagnostic, but not the code action. See the following examples from the Shellcheck extension:

Adding to the diagnostic sounds good.

Implemented the href code description:

It requires an update on the client side because it's only supported as of LSP 3.16.0

This is awesome, thanks for doing it. Would you mind splitting up the other changes you mentioned into separate PR's so it is easier to review?

Refactored code action and diagnostic for the version in their own file and created a test suite for the whole version refactoring feature (code action and diagnostic for version)

authors: daddykotex milesziemer srchase

repo: awslabs/smithy-language-server


text:
[GIT PULL] man/io_uring_internal: Man page about high lvl inner workings of io_uring

This adds the first of the new man 7 pages suggested in #1241
It contains a high lvl overview of what needs to be done on the kernel side for all requests, who does the work with a given configuration, explains the async punt and describes what io_uring kernel threads exist in which case.
Let me know if I got anything wrong, smth is missing etc..
Also, wasn't sure about the name of the page.

git request-pull output:
The following changes since commit 206650ff72b6ea4d76921f9c91ebfffd9902e6a0:

  test/fixed-hugepage: skip test on -ENOMEM (2024-09-27 10:27:10 -0600)

are available in the Git repository at:

  https://github.com/CPestka/liburing man_internals

for you to fetch changes up to fc5266b9626ac9798dce455f031871f4817c7cea:

  man/io_uring_internal: Add man page about relevant internals for users (2024-10-05 15:00:14 +0200)

----------------------------------------------------------------
CPestka (1):
      man/io_uring_internal: Add man page about relevant internals for users

 man/io_uring_internals.7 | 225 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 225 insertions(+)
 create mode 100644 man/io_uring_internals.7

Click to show/hide pull request guidelines
Pull Request Guidelines

To make everyone easily filter pull request from the email
notification, use [GIT PULL] as a prefix in your PR title.

[GIT PULL] Your Pull Request Title

Follow the commit message format rules below.
Follow the Linux kernel coding style (see: https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst).

Commit message format rules:

The first line is title (don't be more than 72 chars if possible).
Then an empty line.
Then a description (may be omitted for truly trivial changes).
Then an empty line again (if it has a description).
Then a Signed-off-by tag with your real name and email. For example:

Signed-off-by: Foo Bar <foo.bar@gmail.com>

The description should be word-wrapped at 72 chars. Some things should
not be word-wrapped. They may be some kind of quoted text - long
compiler error messages, oops reports, Link, etc. (things that have a
certain specific format).
Note that all of this goes in the commit message, not in the pull
request text. The pull request text should introduce what this pull
request does, and each commit message should explain the rationale for
why that particular change was made. The git tree is canonical source
of truth, not github.
Each patch should do one thing, and one thing only. If you find yourself
writing an explanation for why a patch is fixing multiple issues, that's
a good indication that the change should be split into separate patches.
If the commit is a fix for an issue, add a Fixes tag with the issue
URL.
Don't use GitHub anonymous email like this as the commit author:
123456789+username@users.noreply.github.com

Use a real email address!
Commit message example:
src/queue: don't flush SQ ring for new wait interface

If we have IORING_FEAT_EXT_ARG, then timeouts are done through the
syscall instead of by posting an internal timeout. This was done
to be both more efficient, but also to enable multi-threaded use
the wait side. If we touch the SQ state by flushing it, that isn't
safe without synchronization.

Fixes: https://github.com/axboe/liburing/issues/402
Signed-off-by: Jens Axboe <axboe@kernel.dk>

By submitting this pull request, I acknowledge that:

I have followed the above pull request guidelines.
I have the rights to submit this work under the same license.
I agree to a Developer Certificate of Origin (see https://developercertificate.org for more information).

Thanks for kicking this off! I'll add some comments in the diff.

@axboe  Thanks for the notes! I left some comments and will type up the corrections tomorrow if i get to it.

Ok, finally got around to address your comments @axboe. The main things, I guess, are: I added a small section for explaining the io threads separately and expanded the explanation for scenarios during submission. Also a couple of other minor rewordings etc. Let me know if I missed smth or got something wrong in the corrections :)

Thanks, I'll take another look!

source: gharchive/pull-request

authors: CPestka axboe

repo: axboe/liburing

license: mit

license_type: permissive

license_source: bigquery


text:
docs: add tsdoc comments for the Axiom client

improve visibilty of the client type and params using TSDoc

Very very good, good JSDocs make using the library so much nicer 👍👍

authors: bdsqqq schehata

repo: axiomhq/axiom-js

license: MIT

license_source: github-api


text:
PerfEventArray only supports 32 bit datatypes

Hallo,
I tried to adapt the example for tc-egress to work also with IPv6. Thus, I adapted the PackageLog structure to be the following:
pub struct PacketLog {
    pub ipv6_address: u128,
    pub action: i32,
}

However, when running the program, I get a similar error to the following that happens when loading the eBPF program:
Error: the BPF_PROG_LOAD syscall failed. Verifier output: func#0 @0
0: R1=ctx(off=0,imm=0) R10=fp0
0: (bf) r6 = r1                       ; R1=ctx(off=0,imm=0) R6_w=ctx(off=0,imm=0)
1: (bf) r3 = r10                      ; R3_w=fp0 R10=fp0
2: (07) r3 += -16                     ; R3_w=fp-16
3: (b7) r2 = 12                       ; R2_w=12
4: (b7) r4 = 2                        ; R4_w=2
5: (85) call bpf_skb_load_bytes#26
last_idx 5 first_idx 0
regs=10 stack=0 before 4: (b7) r4 = 2
6: R0_w=scalar() fp-16=??????mm
6: (15) if r0 == 0x0 goto pc+3        ; R0_w=scalar()
7: (b7) r7 = 2                        ; R7_w=2
8: (bf) r0 = r7                       ; R0_w=2 R7_w=2
9: (95) exit

from 6 to 10: R0_w=0 R6_w=ctx(off=0,imm=0) R10=fp0 fp-16=??????mm
10: (b7) r7 = 3                       ; R7_w=3
11: (69) r1 = *(u16 *)(r10 -16)       ; R1_w=scalar(umax=65535,var_off=(0x0; 0xffff)) R10=fp0
12: (55) if r1 != 0x8 goto pc-5       ; R1_w=8
13: (bf) r3 = r10                     ; R3_w=fp0 R10=fp0
14: (07) r3 += -16                    ; R3_w=fp-16
15: (bf) r1 = r6                      ; R1_w=ctx(off=0,imm=0) R6_w=ctx(off=0,imm=0)
16: (b7) r2 = 30                      ; R2_w=30
17: (b7) r4 = 4                       ; R4_w=4
18: (85) call bpf_skb_load_bytes#26
last_idx 18 first_idx 0
regs=10 stack=0 before 17: (b7) r4 = 4
19: R0=scalar() fp-16=????mmmm
19: (55) if r0 != 0x0 goto pc-13      ; R0=0
20: (61) r9 = *(u32 *)(r10 -16)       ; R9_w=scalar(umax=4294967295,var_off=(0x0; 0xffffffff)) R10=fp0
21: (bf) r1 = r6                      ; R1_w=ctx(off=0,imm=0) R6=ctx(off=0,imm=0)
22: (85) call bpf_get_socket_uid#47   ; R0_w=scalar()
23: (bf) r8 = r0                      ; R0_w=scalar(id=2) R8_w=scalar(id=2)
24: (dc) r9 = be32 r9                 ; R9_w=scalar()
25: (63) *(u32 *)(r10 -16) = r9       ; R9_w=scalar() R10=fp0 fp-16=????mmmm
26: (bf) r2 = r10                     ; R2_w=fp0 R10=fp0
27: (07) r2 += -16                    ; R2_w=fp-16
28: (18) r1 = 0xffff91ee7a810400      ; R1_w=map_ptr(off=0,ks=4,vs=4,imm=0)
30: (85) call bpf_map_lookup_elem#1   ; R0=map_value_or_null(id=3,off=0,ks=4,vs=4,imm=0)
31: (b7) r7 = 3                       ; R7_w=3
32: (15) if r0 == 0x0 goto pc+1       ; R0=map_value(off=0,ks=4,vs=4,imm=0)
33: (b7) r7 = 2                       ; R7_w=2
34: (b7) r1 = 0                       ; R1_w=0
35: (6b) *(u16 *)(r10 -4) = r1
last_idx 35 first_idx 31
regs=2 stack=0 before 34: (b7) r1 = 0
36: R1_w=P0 R10=fp0 fp-8=??00????
36: (63) *(u32 *)(r10 -8) = r8        ; R8=scalar(id=2) R10=fp0 fp-8=??00mmmm
37: (63) *(u32 *)(r10 -16) = r9       ; R9=scalar() R10=fp0 fp-16=????mmmm
38: (63) *(u32 *)(r10 -12) = r7       ; R7_w=2 R10=fp0 fp-16=mmmmmmmm
39: (bf) r4 = r10                     ; R4_w=fp0 R10=fp0
40: (07) r4 += -16                    ; R4_w=fp-16
41: (bf) r1 = r6                      ; R1_w=ctx(off=0,imm=0) R6=ctx(off=0,imm=0)
42: (18) r2 = 0xffff91ed5ad70000      ; R2_w=map_ptr(off=0,ks=4,vs=4,imm=0)
44: (18) r3 = 0xffffffff              ; R3_w=4294967295
46: (b7) r5 = 16                      ; R5_w=16
47: (85) call bpf_perf_event_output#25
invalid indirect read from stack R4 off -16+14 size 16
verification time 128 usec
stack depth 16
processed 45 insns (limit 1000000) max_states_per_insn 0 total_states 3 peak_states 3 mark_read 2

Caused by:
    Permission denied (os error 13)

I can though do to the following and it runs:
pub struct PacketLog {
    pub ipv6_address: [u32;4],
    pub action: i32,
}

It is just a minor thing (for me) as I have a workaround, but I wonder if it is intended to work only with u32/i32 for PerfEventArray, if this  is a missing feature or some limitation in the Linux Kernel itself?
Thanks a lot!

It is just a minor thing (for me) as I have a workaround, but I wonder if it is intended to work only with u32/i32 for PerfEventArray, if this is a missing feature or some limitation in the Linux Kernel itself?

The eBPF VM doesn't support 128-bit values - u128 - which is likely the issue that you're seeing.
u64 or i64 will work just fine in a PerfEventArray.
In the case of IPv6 though you'll be better served with [u16;8] or [u8;16] though since these can easily be converted to an [std::net::Ipv6Addr](https://doc.rust-lang.org/stable/std/net/struct.Ipv6Addr.html).

source: gharchive/issue

authors: dave-tucker jornfranke

repo: aya-rs/aya


text:
[mason-tool-installer] black:failed to install

我在每次打开nvim后在右边弹出几个信息框，上面的信息如下:
[mason-tool-installer] black:installing
[mason-tool-installer] black:installing
[mason-tool-installer] black:failed to install
[mason-tool-installer] black:failed to install

根据wiki里的教程，我使用的是ssh来安装和更新插件。
我是第一次使用nvim，这个是在下载某个插件失败了吗，我应该如何操作来修复这个？
BTW：我想问一下如何在neovide中修改字体大小，我尝试修改了vim.api.nvim_set_option_value("guifont", "JetBrainsMono Nerd Font:h15", {})里面h15的值，但是并未成功。

for black installation error, check #295.

Just as @CharlesChiuGit mentioned, black requires a series of python dependencies to complete the installation. Make sure you have completed dependencies installation according to #295, and the executable file is located under the $PATH environment variable (i.e., can be accessed directly through typing the command name)
If you can't accurately troubleshoot the error, try using python -m pip --disable-pip-version-check install -U black to install black yourself and if the installation fails, you may then provide the error log to us when you need any further help 👍
Looks like your system isn't ready to use any Nerd Font, and more specifically, JetBrainsMono Nerd Font. What is the output of :set guifont?? (p.s., you need to use the "command" mode of vim to see the output. Make sure you're currently in normal mode. If not, pressing ESC quits from insert mode to normal mode, where you can press : to type in a command.) If the font(s) listed in guifont are not found, vim will then use the default font, no matter how this option is set (including font size). Please install the font correctly here first (this link is for JetBrainsMono Nerd Font), and then modify the font size. The format is:

vim.api.nvim_set_option_value("guifont", "your_font_name(may include spaces):hsize(size is a number)", {})

2. Please follow the instructions to install your desired font correctly here first (this link is for JetBrainsMono Nerd Font), and then modify the font size.

我在windows中安装好链接里的字体后可以正常修改了，感谢。
后续还有一个问题，修改了字体的大小，所有的字体都会变大。是否可以通过某种方式，分别设置不同部分的字体大小（比如代码区域，弹出的提示框等）。因为我修改了字体的大小后弹出的提示框也变得很大，经常弹出的提示框会遮住代码部分，比较影响体验。

for black installation error, check #295.

fixed，thanks.

Please follow the instructions to install your desired font correctly here first (this link is for JetBrainsMono Nerd Font), and then modify the font size.

我在windows中安装好链接里的字体后可以正常修改了，感谢。 后续还有一个问题，修改了字体的大小，所有的字体都会变大。是否可以通过某种方式，分别设置不同部分的字体大小（比如代码区域，弹出的提示框等）。因为我修改了字体的大小后弹出的提示框也变得很大，经常弹出的提示框会遮住代码部分，比较影响体验。

@Lonjiazeng There is no better solution at present. AFAIK neovide renders text properties using the global table vim.opt.guifont. If you change this value, all buffers will be affected. At present, there is no better way to achieve independent text rendering, since vim/neovim is built on a classic terminal model, for TUI (text based user interfaces) based rendering, the entire screen must be completely monospaced. There's no way to control the size of the text independently in different parts of the screen. More's the pity. You may see :h 'guifont' for more details.

There is no better solution at present.

All right, thanks for all.

authors: CharlesChiuGit Jint-lzxy Lonjiazeng

repo: ayamir/nvimdots


text:
🛑 Digizoo is down

In 0ed276d, Digizoo (https://www.digizoo.com.tr/) was down:

HTTP code: 503
Response time: 942 ms

Resolved: Digizoo is back up in cfb6ea3 after 25 minutes.

repo: aydgn/upptime


text:
Install Serge (LLaMa) and evaluate the service

Let's follow https://github.com/nsarrazin/serge to have a local service based on LLaMa (optimized LLM).
The goals are:

Understand the resources needed
Understand the conversations richness and accuracy, compared with ChatGPT3
Answser the question: are these optimized LLMs a real alternative?
Play with the remote API

Nothing better than starting using the docker version.
docker run -d -v weights:/usr/src/app/weights -v datadb:/data/db/ -p 8008:8008 ghcr.io/nsarrazin/serge:latest

It seems that now, we need to download the models. So the docker is just the client and the server (FastAPI) which will use the LLM for the conversations.

The first try was disappointing.

Let's try the 13B model!

About the API, it has the doc where FastAPI provides it: http://localhost:8008/api/docs

The models downloaded are stored in weights:
root@alicita:/var/lib/docker/volumes# du -sh *
0	backingFsBlockDev
301M	datadb
24K	metadata.db
12G	weights

And now, let's compare with the real ChatGPT:

My impression is that LLaMA 7B an 11B models are no comparable with ChatGPT. And they are more dangerous according to their answers.

Trying the 30B model ... it does not work!

So it is time to play with other alternatives!

repo: aylabs/chatgpt


text:
"Error: NotFoundException: Something wrong"

See in screenshot

@aslbekkucharov ty, fixed

authors: aslbekkucharov azabroflovski

repo: azabroflovski/mxik-js


text:
Bug: (sort-classes) Overloads are not properly sorted.

Describe the bug
It's seems like there is an error in the way you handle overloads. The top most overload is always treated as a separate function and because it has no body, TypeScript doesn't like this.
Code example
For example, it turns this:
class X {
    setBackground(color: number, hexFlag: boolean): this
    setBackground(color: Color | string | CSSColor): this
    setBackground(r: number, g: number, b: number, a?: number): this
    setBackground(color: ColorArgument, arg1?: boolean | number, arg2?: number, arg3?: number): this {
        <body>
    }
}

into this:
class X {
    setBackground(r: number, g: number, b: number, a?: number): this
    setBackground(color: CSSColor | Color | string): this
    setBackground(color: ColorArgument, arg1?: boolean | number, arg2?: number, arg3?: number): this {
        <body>
    }
    setBackground(color: number, hexFlag: boolean): this
}

ESLint version
8.45.0
ESLint Plugin Perfectionist version
1.5.0
Additional comments
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Thanks for the issue! I'll fix this problem soon.

Fixed in c4939b44de0ea9e77a98cee76d4043926d3a02a8.
Release coming soon.

Released in v2.0.0

authors: ElPrudi azat-io

repo: azat-io/eslint-plugin-perfectionist


text:
Add websocket endpoint api-server

This endpoint should accept websocket connections and be able to forward messages to clients. This should use server-side websockets from akka http.

If we really plan to use WebSockets in the application, I think that it would be valuable to evaluate a WebSocket service vs. rolling our own. Although I believe that ALBs support WebSockets, we'd be getting ourselves into the business of managing long-lived connections on the backend, plus supporting infrastructure to pass messages back via the existing WebSocket connections (what if we want to send a message back from an Airflow worker?)
The last time we went partially down this road (nothing was ever implemented), we narrowed down the field to:

https://www.pubnub.com/
https://pusher.com/

This could be used to solve https://github.com/azavea/raster-foundry/issues/2082#issuecomment-310165140

authors: hectcastro jisantuc jmorrison1847

repo: azavea/raster-foundry


text:
Flow and job events

Added upload related attributes to Flow events.
Added projectName and attemptID in job events.

Pull Request Test Coverage Report for Build 5298

7 of 17 (41.18%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 40.799%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

azkaban-common/src/main/java/azkaban/project/ProjectFileHandler.java
2
3
66.67%

azkaban-exec-server/src/main/java/azkaban/execapp/FlowRunner.java
4
13
30.77%

Totals

Change from base Build 5295:
0.01%

Covered Lines:
13189

Relevant Lines:
32327

💛  - Coveralls

Are there any unit tests that can be updated for this?
Noted a few other questions/concerns in comments. (Looks fine otherwise)

Unit tests cant be updated as data needs to be fetched from DB.

repo: azkaban/azkaban


text:
Return NaN statistics if fit fails

Currently if the fit fails (e.g. column of 0s in the predictors) then coefficients will return nan/inf, but statistics will panic
This PR makes statistics also return NaNs
I'm a rust beginner, so apologies if this isn't the greatest rust code.

Thanks a lot for your PR @alexscordellis, your changes look great.
Running tests and will ✅

Great, thanks.
When do you expect to next tag a release?
Thanks again for providing a really useful library.

authors: alexscordellis azmyrajab


text:
Its Rocket Science

Please take a look.
cc: @bruno-morel

good job. we like it

authors: bruno-morel dhilipkumars

repo: b-yond-infinite-network/amaze-us


text:
Add visidata config

Add a config for visidata which supports XDG since https://github.com/saulpw/visidata/pull/1420

Thanks very much!


text:
Add additional chat templates to dllama-api

I've added a few of the most common chat templates, namely llama2, llama3, chatml and openchat.
This should make a lot more models compatible with distributed-llama's API
Also added an additional argument to AppArgs to let you specify the chat template used by the model on startup instead of on a per request basis.

I need to add openchat3 template as openchat currently should work with this model
https://huggingface.co/openchat/openchat-3.5-0106
but not with their latest which uses a similar template to llama 3
https://huggingface.co/openchat/openchat-3.6-8b-20240522

I was able to successfully test openchat-3.6-8b and it worked correctly with the openchat3 chat template
-> https://huggingface.co/openchat/openchat-3.6-8b-20240522
Converted it using convert-hf.py and converted the tokenizer with convert-tokenizer-llama3.py
I was not able to test openchat-3.5 as although I could convert the model using convert-hf.py, I could not convert the tokenizer.

I am having the weirdest issue, if I run Hermes-2-Theta-Llama-3-8B using the llama 3 converted tokenizer, it works fine, although it is missing some tokens since it's from a different model of the same architecture, Hermes-2-Theta-Llama-3-8B doesn't have a tokenizer.model so I was a bit in a jam as to what to do.
I put together a convert-tokenizer-hf.py script that's meant to do the same except it uses transformers AutoTokenizer to pull all the neccessary data to build the tokenizer.t file
But I think I am doing something wrong as when I run dllama with the generated tokenizer.t file it crashes when encoding text.
convert-tokenizer-hf.py
import sys
import struct
from transformers import AutoTokenizer

if __name__ == '__main__':
    if len(sys.argv) < 2:
        print('Invalid usage')
        exit(1)

    tokenizer_path = sys.argv[1]
    tokenizer = AutoTokenizer.from_pretrained(tokenizer_path)

    bos_token = tokenizer.bos_token
    eos_token = tokenizer.eos_token

    bosId = tokenizer.convert_tokens_to_ids(bos_token)
    eosId = tokenizer.convert_tokens_to_ids(eos_token)

    tokens = []
    scores = []

    # Get vocab size and tokens
    for token_id in range(tokenizer.vocab_size):
        token = tokenizer.convert_ids_to_tokens(token_id)
        bytes = token.encode('utf-8')
        tokens.append(bytes)
        scores.append(float(token_id))

    # Get special tokens
    special_tokens = tokenizer.added_tokens_decoder
    special_token_index = tokenizer.vocab_size
    for token_id in special_tokens:
        token = tokenizer.convert_ids_to_tokens(token_id)
        bytes = token.encode('utf-8')
        score = special_token_index
        tokens.append(bytes)
        scores.append(float(score))
        special_token_index += 1

    vocab_size = len(tokens)
    max_token_length = max(len(t) for t in tokens)

    with open('dllama_tokenizer_llama3.t', 'wb') as outputFile:
        outputFile.write(struct.pack('IIIiii',
                                     0x567123,
                                     vocab_size,
                                     max_token_length,
                                     bosId,
                                     eosId,
                                     -1))

        for i in range(vocab_size):
            outputFile.write(struct.pack('fI', scores[i], len(tokens[i])))
            outputFile.write(tokens[i])

        print(f'maxTokenLength={max_token_length}')
        print(f'bosId={bosId}')
        print(f'eosId={eosId}')
        print(f'vocabSize={vocab_size}')

I'm wondering if this is a good direction. I mean for sure the source code should not include all possible templates. Maybe this is something that should be moved to the tokenizer file.
Basically now the tokenizer contains: magic|n_words|max_token_length|bos_id|eos_id|pad_id|<dictionary>. But we could add a new optional fields like:

chat_role_start llama3 = <|start_header_id|>
chat_role_end llama3 = <|end_header_id|>
chat_eos llama3 = <|eot_id|>

So this design assumes there may be differences in the chat mode.
At the end the converter would be responsible for setting correct values. So this would be not a responsibility of DL.
WDYT?

I've tried to type a reply twice but keep getting an blue screen just as I'm about to send :/
Converting the tokenizer is very quick so, in the long run it's probably good to use that route, I just wanted to add a few of the common chat templates ie llama 2, llama 3 and chatml as that already covers the majority of models.
The bigger issue I have is with the script I showed above, I cannot create tokenizers for some models as they do not have the tokenizer.model file, for instance this model: https://huggingface.co/NousResearch/Hermes-2-Theta-Llama-3-8B

@DifferentialityDevelopment please check this PR. This may solve the problem for different models.

@DifferentialityDevelopment probably this would require update the tokenizer in your repository on HuggingFace. Please don't do this until the PR is not merged. Later I want to test a different model.

@DifferentialityDevelopment can you update the tokenizer file in your HF repository to the new format?


text:
fix: submit button/input element submits form

Closes #996

I added a bunch more tests, I figured there were some other edge cases we were not handling. Let me know what you think @linkdotnet .

repo: bUnit-dev/bUnit


text:
Gulpfile changes

Uses gulpfile.babel.js
Bumps gulp
Starts to use ES6

Finally I also started moving all the contents of tasks into functions. There's more refactoring work to do here, but you'll notice that there's a bunch of extra tasks that people create when writing gulp when you can actually just use normal functions. I started the work of moving things over like this:
function clean(dir, cb) {
  del([dir], cb);
}

gulp.task('clean', done => clean(destinationFolder, done));
gulp.task('clean-tmp', done => clean('tmp', done));

Again, more refactoring can be done here, but for now everything lives within separate functions than their tasks.

Hmm, for some reason istanbul is getting all upset

Opened an issue in Babel

Sry, updated the Gulpfile this morning @thejameskyle :speak_no_evil:

@thejameskyle want to split this out into smaller, easier-to-merge PRs? This is good stuff.

ping @thejameskyle

Opened two issues for the changes here: #211 and #212

authors: jmeas thejameskyle

repo: babel/babel-library-boilerplate


text:
Unused class declaration is not removed

If you minify the following functions only one of the unused class declarations is removed.
function fn(base) {
  class foo extends base {}
}
function fn2(base) {
  class bar extends base.prop {}
}

Becomes:
function fn(a){}
function fn2(a){class b extends a.prop{}}

Obviously this is a contrived example but in my application this is causing a large tree of unused classes to make it into the client bundle.
I'm just testing on the command line with babel:
cat example.js | babel --presets=babili

This is because base.prop can have side-effects.
const base = {
  get prop() {
    // side-effect
    console.log("Foo");
    return class {};
  }
};
fn2(base);

This has already been discussed - about an option in babili pureGetters to treat getters as pure.
Duplicate #498.

What about this one:
function fn() {
  class foo {
    get prop() {}
  }
}

Becomes:
function fn(){class a{get prop(){}}}

That can be removed. Not sure why it's not. I'll check that. Thanks.

@boopathi The original example should get minified to this:
function fn(a){}
function fn2(a){a.prop}

Well if we're truly being pedantic about side-effects I don't think you can remove either one. Extending a class explicitly invokes some checks on the base class which get skipped when you prune the definition. Consider:
// This an awesome function which will return `true` if the passed value
// can be invoked with the `new` operator.
function isConstructor(val) {
  try {
    class foo extends val {};
    return true;
  } catch (err) {
    return false;
  }
}

console.log(isConstructor(function() {}));
console.log(isConstructor({}));

This application will log "true false" but after you run it through Babili it logs "false false". This example feels more pedantic than treating getters as impure but I can't come up with a formal definition for why.

authors: boopathi j-f1 laverdet

repo: babel/babili


text:
Add oid column to information_schema_tsql.columns for internal use only

Description
This PR fixes two things

Fix JOIN conditions which used TABLE_NAME by replacing it with OID instead.
INFORMATION_SCHEMA_TSQL.COLUMNS should return original name for TABLE_NAME & COLUMN_NAME

(Use case from DMS) Currently if we create a table with mixed case name(quoted) from PG endpoint and use same name to create another table from babelfish endpoint with certain combination of datatypes, system procedure sp_columns_100 starts failing with case not found error for this table. Root cause is the join condition used on information_schema_tsql.columns in sp_columns_100_view. We ended up picking datatype of babelfish endpoint table but typmod of PG created table.
JOIN information_schema_tsql.columns t4 ON (pg_class.relname::sys.nvarchar(128) = t4."TABLE_NAME" AND ext.orig_name = t4."TABLE_SCHEMA")
Here pg_class.relname can be a different table (mixed case) but will get through since we are using server default collation for comparison which is case insensitive (usually).
As a fix,
We create a new internal catalog information_schema_tsql.columns_internal which will contain the OID of table as well.
The actual information_schema_tsql.columns is just a wrapper view on this. (To mask the OID column).
Issues Resolved
[BABEL-4553]
Cherry Picked From
https://github.com/babelfish-for-postgresql/babelfish_extensions/pull/2265
No merge conflicts except upgrade script and schedule files.
Sign Off
Signed-off-by: Tanzeel Khan tzlkhan@amazon.com
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build 7708496940

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 72.057%

Totals

Change from base Build 7699702601:
0.0%

Covered Lines:
40187

Relevant Lines:
55771

💛  - Coveralls


text:
Compatibility with laravel 5.5

I added compatibility trait that makes this package compatible with both Laravel 5.5 and 5.4. Also fixed tests that failed in phpunit 6.
I am not sure that support of multiple versions is a good decision instead of create a new branch and tag it like 2.0, so please review.

Also I thought about a CommandInterface with handleCommand method but leave it as is for now.

Hi @zarianec, thank you for your contribution! I've decided to take your advice and make 2.0 version. Basically I took your code and tested all the features and commands. Thank you again, good work!

authors: babenkoivan zarianec

repo: babenkoivan/scout-elasticsearch-driver


text:
🛑 SM Service is down

In a84ee9f, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in 996f5f2.

repo: bachmannschumacher/upptime


text:
🛑 SM Service is down

In 818a27d, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in 107cb93.


text:
💬 RFC: Informing users about external links on the navigation

🔖 Need
It is possible to add an external link to the main navigation, but there's no clear indication for users whether this item is a standard internal link or one that will open an external site.
This ambiguity may surprise users unexpectedly when the navigation item unexpectedly opens a different website.
🎉 Proposal
If an external link is added to the navigation:

Include an icon next to the navigation item
Enable the option to open it in a new tab

〽 Alternatives
No response
❌ Risks
No response
👀 Have you spent some time to check if this RFC has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Hey :wave:
I think that there's already some existing logic that we can maybe hook into the back of in the existing Link component
I was wondering if we could also optionally render the external icon here too and do it inline?
Might be a nice solution to apply it Backstage wide rather than just in the sidebar. Would be good to call out that these things are external in things like Techdocs etc too.

authors: ShiranHi benjdlambert

repo: backstage/backstage


text:
Add config option to use GitHub org namespace with single org

Hey, I just made a Pull Request!
If you only list a single org in the GitHub org provider config, the generated group entities will use the default namespace, otherwise they will use the org name as the namespace. There is no way to configure this behavior from config.
We have multiple GitHub orgs but for our Proof-of-concept app we are consuming from a single org. All the generated group entities will have default namespace. In the future, we will want to expand the orgs we consume from but don't want to be left with orphaned entities from the default namespace. We also want the group entities namespace to match the org name for demo purposes, which more easily demonstrates the capability of consuming from multi orgs.
This PR adds a new optional config option neverUseDefaultNamespace to GitHub provider. If this flag is set, it will always use the org name as the namespace even if only a single org was provided.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

When you switch from a single org to multiple orgs there will be no orphaned users left, as the providers will take care of cleaning up the entities.
Does this solve your problem?

Thanks, it solves the problem of the orphaned entities! But what if I just prefer to use the org as namespace instead of default? I suppose you could override the default behavior in a custom transformer but is that better than a config option?

When you switch from a single org to multiple orgs there will be no orphaned users left, as the providers will take care of cleaning up the entities.
Does this solve your problem?

Thanks, it solves the problem of the orphaned entities! But what if I just prefer to use the org as namespace instead of default? I suppose you could override the default behavior in a custom transformer but is that better than a config option?

You are correct in saying that using a config is easier than using a custom transformer. However, we need to be mindful about the features we add, as this will entail extra costs in maintenance and code size. Given that I don't believe many adopters will utilize this feature (you also mentioned that this would be a temporary feature for you until you transition to using multiple organizations), and considering that a custom transformer can help you achieve this, I don't see the need to add this extra feature.

When you switch from a single org to multiple orgs there will be no orphaned users left, as the providers will take care of cleaning up the entities.

Does this solve your problem?

Thanks, it solves the problem of the orphaned entities! But what if I just prefer to use the org as namespace instead of default? I suppose you could override the default behavior in a custom transformer but is that better than a config option?

You are correct in saying that using a config is easier than using a custom transformer. However, we need to be mindful about the features we add, as this will entail extra costs in maintenance and code size. Given that I don't believe many adopters will utilize this feature (you also mentioned that this would be a temporary feature for you until you transition to using multiple organizations), and considering that a custom transformer can help you achieve this, I don't see the need to add this extra feature.

Totally understood and I agree. I'll close this PR. Appreciate your reviews as always!

authors: stephenglass vinzscam


text:
Update exported member of module 'msw' from rest to http

Hey, I just made a Pull Request!
Follow the instruction from Testing Remote Service Interactions, I got the error
"module 'msw' has no exported member rest"

for my import import { rest } from 'msw'.
The migration doc said that use http instead of rest.
https://mswjs.io/docs/migrations/1.x-to-2.x/

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

ooops, nevermind, we can specify msw version, seems backstage is using ver 1. Then docs should be correct. Closing the PR.

You can choose per package. Some use 1, some use 2

authors: freben truongnmt


text:
catalog-backend: flesh out and tweak the config schema

It would be nice if we could keep this in sync with code somehow.

@Rugvip ach ... added!


text:
Updated backend-tasks readme

Signed-off-by: Andre Wanlin awanlin@rapidrtc.com
Hey, I just made a Pull Request!
Updated the backend-tasks README based on usage:

It did not like dashes in the id, changed that to an underscore
The timeout is required, added that to the example
Added a note about tasks not running as expected for local development using persistent database

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

@freben some changes based on my usage. Not sure if the timeout example is clear, happy to change

Ready for another review or for these changes to be approved and merged 👍

Thanks and happy new year!

authors: awanlin freben


text:
reduce shuffle join probe scopes

What type of PR is this?

[ ] API-change
[ ] BUG
[ ] Improvement
[ ] Documentation
[ ] Feature
[ ] Test and CI
[ ] Code Refactoring

Which issue(s) this PR fixes:
issue #
What this PR does / why we need it:

https://github.com/matrixorigin/ci-test/actions/runs/10130373836


text:
In Windows Firefox, labels and status text in badges overlap and push outside boundaries

Here are a few examples from shields.io website, to illustrate whats happening in projects Im involved in, clearly this is now a global issue.

Would you guys consider adding padding to left and right of label portion and left and right of status portion?

anyone?

this is todays coverity, it is pretty much unreadable...
@badges is there a point reporting issues here on GH issue tracker or? just no replies at all... makes one wonder

Could you provide us with a list of fonts available on your computer among the following names, please?

DejaVu Sans
Verdana
Geneva

Could you also provide us with an exact version number corresponding to your operating system and one corresponding to your browser?
Thanks a lot for reporting this!

The issue is visible on Windows 7 sp1 all up-to-date + Firefox 47.0.1 its not always been the case.
LInux ubuntu variant 16.04 + Firefox 47.0 is OK
Fonts available (checked) The others are not available on Windows by default.

[ ] DejaVu Sans
[x] Verdana
[ ] Geneva

I also tried to using a font revert thing for GitHub...
@-moz-document regexp("^https?://((gist|guides|help|raw|status|developer)\.)?github\.com((?!generated_pages\/preview).)*$"), domain("render.githubusercontent.com"), domain("raw.githubusercontent.com") {

body, .markdown-body {

    font-family: Helvetica, arial, nimbussansl, liberationsans, freesans, clean, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol" !important;

  }

}

Which reverts the fonts GitHub currently uses, however shield IO badges are unaffected. with or without the issue is there.
Screenshot of Vanilla windows...

@espadrine any advance on this?

are these people even alive?

are these people even alive?

Clearly its not an important issue to them like paying the bills or world hunger etc.

it actually looks decent on Safari (MacOS)... this must be a browset-specific issue... <>

This isnt a OSX or Linux issue

There seems to have been only relatively small updates since i started following this project.
assume its just lack of people with privileges to accept PR's ect. as there seems to be lots of people willing to work in this and create PR's but nothing is getting done about them.

Firefox 49.01 and Win 7 sp1 still same issue.

I joined the project a few weeks ago and have been steadily merging PRs. Thaddée has been deploying the updates.
Some further research was done in #797. Would be great if someone could dig into this problem further.
If we can isolate the problem, maybe running some tests on Sauce Labs would help diagnose the problem thoroughly and prevent a regression.
cc @aburgd @mralexgray

I've found that the badges are showing up properly on my laptop running WX
with Chrome.
On Apr 17, 2017 5:52 PM, "Paul Melnikow" notifications@github.com wrote:

I joined the project a few weeks ago and have been steadily merging PRs.
Thaddée has been deploying the updates.
Some further research was done in #797
https://github.com/badges/shields/issues/797. Would be great if someone
could dig into this problem further.
If we can isolate the problem, maybe running some tests on Sauce Labs
would help diagnose the problem thoroughly and prevent a regression.
cc @aburgd https://github.com/aburgd @mralexgray
https://github.com/mralexgray
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/badges/shields/issues/746#issuecomment-294618572, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGA4He7SQx0zqkgpSn16cBEWZhfsI0vuks5rw-0cgaJpZM4JOcmy
.

@paulmelnikow
I just noticed this problem and came looking for a report or make my own.
Ive not tested in other OS's
The issue exists with svg badges only as far as I cant tell, with png badges the issue is gone, but of course the text is quite small in comparison.
My environment:
Windows 10
Firefox 56 64bit

Issue test

as above
[![Scrutinizer](https://img.shields.io/scrutinizer/g/filp/whoops.svg)]()
[![Scrutinizer](https://img.shields.io/scrutinizer/g/filp/whoops.png)]()

Screenshot as I see it.

Thanks for the info.
Could you include your answer to Thaddée's question in https://github.com/badges/shields/issues/746#issuecomment-236384036?

The issue exists with svg badges only as far as I can tell, with png badges the issue is gone, but of course the text is quite small in comparison.

Yea, that's right, it's only with the svg badges. The png badges are rasterized on the server, so they look the same everywhere.

@paulmelnikow request dupe-reply here

@paulmelnikow
I just noticed this problem and came looking for a report or make my own.
Ive not tested in other OS's
The issue exists with svg badges only as far as I can tell, with png badges the issue is gone, but of course the text is quite small in comparison.
My environment:
Windows 10
Firefox 56 64bit

Issue test

as above
[![Scrutinizer](https://img.shields.io/scrutinizer/g/filp/whoops.svg)]()
[![Scrutinizer](https://img.shields.io/scrutinizer/g/filp/whoops.png)]()

Screenshot as I see it.

It looks like you tried to reply but I'm not seeing it. I mean: which of those fonts do you have installed?

Its Windows, doubtful it will have Dejavu Sans or any Dejavu or Geneva, verdana yes.
DejaVu Sans -- No
Verdana -- Yes
Geneva --No

It's rendering with Verdana on my Mac OS machine too. I'm not sure why the size is so different.
[![Scrutinizer](https://img.shields.io/scrutinizer/g/filp/whoops.svg)]()
[![Scrutinizer](https://img.shields.io/scrutinizer/g/filp/whoops.png)]()

Here's what I'm seeing:

Is the problem observed in Firefox, and not in Chrome or IE?

There's a known issue with minimum font size. Do you have that turned on? (#848)

There's a known issue with minimum font size. Do you have that turned on? (#848)

You nailed it, that seems to be the problem. 👍 🍾 🥇 disable minimum size and issue is gone. 😊
Im not sure when or why that setting changed here but its off now.
One thing though, #848 report doesnt mention which browser or version, even no OS or version either

Is the problem observed in Firefox, and not in Chrome or IE?

If you have read through both tickets, https://github.com/badges/shields/issues/797#issuecomment-249511923 and https://github.com/badges/shields/issues/797#issuecomment-249436383 cover those questions.
But Firefox side you now know that is the minimum size thing.

@RedSparr0w has a brilliant fix! Could you help us test it @the-j0k3r, by turning min-font-size back on till the problem comes back, and then screenshotting this page?
http://whois.paulmelnikow.com/extra/1132.html

My pleasure, to help out, least I can do :)

This issue is still present, I though once PR was merged it would go away.

Doesn't look like the change has gone live yet, it can take a few weeks after being merged to the master branch before it is pushed through.
Sent from my iPhone
On 21/10/2017, at 6:35 PM, the-j0k3r <notifications@github.commailto:notifications@github.com> wrote:
This issue is still present, I though once PR was merged it would go away.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/badges/shields/issues/746#issuecomment-338365759, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AG82ApW3vk2s_Qd1RXJVBpCmFHmlDoT1ks5suYKNgaJpZM4JOcmy.

Ah, well lets hope thats soon.

repo: badges/shields


text:
More TypeScript in the frontend

A couple issues:

[x] Lint config for .d.ts files outside of frontend/
[ ] Fix import of svg in tests (or find a different way to get the types right)

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS against 57e040a920452c3e3ae510975066c31bbe00356b

I'm trying to get my head around what needs to happen to fix this failing test. babel-plugin-inline-react-svg is supposed to turn the logo into a React component, and that seems to be working correctly in Gatsby. I added a declare module for .svg files which appeased the TypeScript type checker. So now it's just ts-mocha that's not working.
What I'm not clear on is:

Whether the Babel plugin is actually running on the svg file
The best way to fix this

Since the tests of the frontend components are just testing renders and making the most basic assertion about contents, the main value they provide is checking that the code still runs after something has changed.
TypeScript checks for an absence of type errors – which is close enough to "this code runs without errors" that I suggest we might remove the rest of these component tests for now, rather than pour more effort into maintaining them.
I'm not opposed to the idea of having tests for the frontend code. I do think there is value in testing the helper functions, and think we should keep these.
Though personally, I would rather spend time improving the functionality of the site – literally, changing its behavior – rather in than testing today's behavior, and I'm not yet convinced that writing tests of the components actually accelerates development of features.

I'm still working my way through some of the files in here, but could you elaborate a bit more on the removal of the tests?
Are they making the switch to TypeScript problematic? Hypothetically, if we weren't moving the frontend to TypeScript, do you still think it would be best to remove them?
I don't have strong feelings one way or the other on those specific tests, but do want to make sure I fully understand the rationale.

I'm still working my way through some of the files in here, but could you elaborate a bit more on the removal of the tests?
Are they making the switch to TypeScript problematic? Hypothetically, if we weren't moving the frontend to TypeScript, do you still think it would be best to remove them?

Yes, there's a tooling issue relating to babel-plugin-inline-react-svg. I'm not sure the exact cause but I wrote a bit about it in https://github.com/badges/shields/pull/3742#issuecomment-513327029. I spent a while  trying to solve it and I'm not sure it's creating a lot of value so I'm not really interested in digging in further, though if anyone else feels like fixing it, I wouldn't object to keeping these tests around.
I posted my rationale on removing the tests here https://github.com/badges/shields/pull/3742#issuecomment-515710380 and sort of reiterated it in https://github.com/badges/shields/pull/3742#discussion_r314193804.

Thanks for reviewing @calebcartwright!

Cool, thanks for reviewing and testing. Glad to be getting this merged!

authors: calebcartwright paulmelnikow shields-ci


text:
Support for Bintray version badge.

Addresses #58 by supporting a badge showing the latest version of
a Bintray package.
Ran a test locally and it seemed to work fine. You'd need to get an API key from Bintray to put in secret.json and work with them on the rate limit question.

Thanks a lot!

Thanks for merging!

authors: ajoberstar espadrine


text:
Fix [Testspace] with new "untested" value in case_counts array

Hello,
I noticed that all Testspace badges started returning "invalid response data" recently. The cause was a recent change in the response object of the Testspace web API: the case_counts array in the Results object now has length 5 instead of 4. A new integer was appended to the end which represents the number of untested tests, which are manual tests that have not been run yet.

Live example
Screenshot for posterity

The API docs haven't been updated yet as of 2022-10-17, but I contacted the Testspace developers and figured out what the new value means.
To fix the invalid error, this change updates the schema for the Testspace API response with the new array length. It also adds a new metric parameter value (untested) to the TestspaceTestCount service and includes it in the internal object returned by TestspaceBase.transformCaseCounts(), as well adding it to the total value in that object. The documentation URLs have also changed.
I didn't add untested to the TestspacePassRatio or TestspaceTests services, since those already didn't use skipped and errored, respectively, and it didn't seem like it would make sense to start including untested manual cases there.
I think I've covered all the requirements for contributing, but let me know if I missed anything or if any other changes need to be made.
Thanks!

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @Aldaviva!

  Generated by :no_entry_sign: dangerJS against b05feb78f4e6cc8d6b779043ec6d535f9720b288

authors: Aldaviva shields-ci


text:
External Database

Hei there
A long time ago I forked your repo and added support for an external database, e.g. using dokku-postgres. Are you interested in this? If so I would clean up the code / commits and open a PR.
All the best
Noe
Btw. thanks a lot for this plugin!

I'd love this. I was just visiting the issues about to ask for the same. I'd love to have the option to have both redis and postgres pulled out and allow using the redis and postgres plugins to provision them for the web-only discourse install.

authors: noeleont rsmithlal

repo: badsyntax/dokku-discourse


text:
Unable to see or run an example

You should be able to see an example of the counters without having to install and run the code locally.
Currently, you are unable to run the code locally due to bower/npm/grunt dependancy issues.
Therefore, I cannot actually see an example in action.

I've added a demo site in which one can pass an URL and see the related shared metrics for the respective social networks.

NIce one @bahaaldine

authors: bahaaldine ttbarnes

repo: bahaaldine/angular-social-count


text:
Vee-validate with scopes in child components

Versions

vee-validate: 2.0.9 - 2.1.0-beta.8
vue: 2.5.17

Describe the bug
Validator method validateAll doesnt work on scoped child component fields, but method validate without params work fine, and parent component fieldBug method clear doesnt work without scopeName propetry.
To Reproduce
Steps to reproduce the behavior:

Create Parent and child component, pass thru props data and scopeName from parent to child form and inject parent validator;
Call $validator.validateAll from parent;

Expected behavior
Parent errorBag will be filled with children errors.
Demo Link
codepen
Desktop (please complete the following information):

Browser [chrome]

my misstake

validateAll validates all "scopeless" fields, so it doesn't validate any scoped field. The name is confusing I admit but I can't do anything about that now than to encourage using the validate method for all validation purposes. This doesn't have anything to do with your component tree structure.
validate validates everything by default, so it does not have the same behavior as validateAll, the clear method follows the same pattern, to clear a scope you need to specify its name.
Another way to clear the validation state (errors, flags) you could do this:
 this.$validator.reset();

repo: baianat/vee-validate


text:
Validation ignores first input on dynamic data

Versions

vee-validate: 2.1.4
vue: 2.5.21

Describe the bug
To reproduce
Steps to reproduce the behavior:

Have a template that uses v-models that load after initialization of the component
Load the data, possible asynchronously
Input a character into the template's input. At this point the v-models are bound to the data.
No validation is run.
Add another character(in my case), click outside the field(in the supplied example. I don't know why these cases are different.
Validation is run correctly.

Expected behavior
Validation is ran on first input.
Demo link
https://jsfiddle.net/c4brw3so/
Validation is only ran when the input loses focus
Compared to:
https://jsfiddle.net/eyf8b06q/9/
Here it validates correctly on the first input.
Desktop (please complete the following information):

OS: Windows 10 latest
Browser: Chrome/ Firefox
Version: Latest

Additional context
My data object is loaded asynchronously by a promise through Axios from a server. This shouldn't be a problem though because the template for the inputs isn't there(with a simple v-if) until the data is added.
https://imgur.com/a/py1dG4D
It seems addValidationListeners doesn't work correctly when the data isn't there yet(when the component is initialized/ whatever), this get's reran on the first input but then the listener isn't triggered so it only triggers on the second input.

Found it after a day of looking.
https://github.com/baianat/vee-validate/blob/e6385f1b7f364a118f2b2d14787365ca4f2b96b5/src/core/field.js#L612
Comment this and it runs correctly the first time.

This isn't really a v-validate bug. Vue can only properly track items in the data object that are there from the start.
For a better description of reactivity in Vue, see https://vuejs.org/v2/guide/reactivity.html#Declaring-Reactive-Properties.

@DM2489 I manually set my variables with this.$set before the input elements exist and the problems persist in my case. This happens asynchronously after the instantiating of the vue component that uses the validator. ( I get validation specs from a server and 'translate' those to vee-validate validation rules)
It's not directly a reactivity issue.
I'll try to replicate this directly.

like @DM2489 mentioned this happens because of the models not being defined initially in the component data. What exactly happens is that vee-validate detects that the field is bound by a v-model and the model name can be watched via the $watch method so it filters out the input event as it would cause conflicts and sync issues with the field and the model. One of this issue is that validation would finish before the model is updated and cause the input to be locked with its initial value.
Now, vee-validate cannot tell if the model exists or not, nor it could tell if it got added later by the $set method. I understand that the server sends the validation specs to the client, but you could define the data beforehand in the data object. These are some limitations of the directive API.
However, You could use Validation Components that were introduced in 2.1 which can handle this case, I would recommend using them from now on instead of the directive:
Here is the same example re-written in them
https://jsfiddle.net/vwd895a7/
Note that the second field rule won't be dynamic because the email is not reactive, so it will always be required.

@DM2489 @Blanen  When vue component first renderered, then data-vv-validate-on="input" isn't  trigger.

authors: Blanen DM2489 gongph logaretm


text:
Function calc_flops does not contain backward flops.

Hi, in DeepBench/code/intel/convolution/mkl_conv/std_conv_bench.cpp: function calc_flops only calculate the forward flops, it did not contain backward flops, is this a bug ?

@rsdubtso , @dmudiger , can you please comment?

Beg my pardon for the delay... The backward flops are equal to the forward flops.

Thanks.

authors: etaf rsdubtso sharannarang

repo: baidu-research/DeepBench


text:
Error after some period using QR or token login

i update to 2.14.1, issue with QR login is fixed, but i'm still having the issue of expiration after few hours (last time 6h)
2024-09-19 17:20:19,026 - pronote-rest - ERROR - Unknown error from pronote: 8 | La page a expiré ! (1)
2024-09-19 17:20:19,026 - pronote-rest - ERROR - Unknown error from pronote: 8 | La page a expiré ! (1)
Traceback (most recent call last):
  File "/home/app/.local/lib/python3.10/site-packages/pronotepy/clients.py", line 1061, in post
    return self.communication.post(function_name, post_data)
  File "/home/app/.local/lib/python3.10/site-packages/pronotepy/pronoteAPI.py", line 179, in post
    raise PronoteAPIError(
pronotepy.exceptions.PronoteAPIError: Unknown error from pronote: 8 | La page a expiré ! (1)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/app/.local/lib/python3.10/site-packages/flask/app.py", line 880, in full_dispatch_request
    rv = self.dispatch_request()
  File "/home/app/.local/lib/python3.10/site-packages/flask/app.py", line 865, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)  # type: ignore[no-any-return]
  File "/home/app/app.py", line 312, in data_period
    tmp = getattr(p, type)
  File "/home/app/.local/lib/python3.10/site-packages/pronotepy/dataClasses.py", line 528, in grades
    response = self._client.post("DernieresNotes", 198, json_data)
  File "/home/app/.local/lib/python3.10/site-packages/pronotepy/clients.py", line 1070, in post
    return self.communication.post(function_name, post_data)
  File "/home/app/.local/lib/python3.10/site-packages/pronotepy/pronoteAPI.py", line 179, in post
    raise PronoteAPIError(
pronotepy.exceptions.PronoteAPIError: Unknown error from pronote: 8 | La page a expiré ! (1)

To try to fix this, i added cron every minute to refresh session using  client.session_check() but did not solve. Still having this page expired :(

I'm having the same issue even when i'm sending requests to pronote every 5 minutes to check for new homework or grades.
i don't know what is the problem.

authors: SleepInfinity bdbogjoe


text:
🛑 Quill is down

In 7b3c8a1, Quill (https://quill.im) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Quill is back up in a437e76 after 11 minutes.

repo: baizhiheizi/upptime


text:
Refactor integration test

extract example to separate snapshot
prefer Pytest fixtures over unittest
remove --save flag from generate command, print YAML by default

@sujuka99 Please have look too!

authors: disrupted raminqaf

repo: bakdata/kpops


text:
Increase space between unconnected components

It is quite hard to identify connected components in the overall view because nodes are equidistantly placed

Changing Graphviz's ranksep and/or nodesep through settings.graph_layout_arguments unfortunately doesn't help in this case as it controls the spacing between all nodes. What we would need is a way of configuring the margin around clusters (our pipeline subgraphs). Without hacks there doesn't seem to be a solution for this at the moment unfortunately.

Couldn't you calculate every connected component/pipeline layout independently and merge them afterward by updating the y values by an offset?

authors: VictorKuenstler disrupted philipp94831

repo: bakdata/streams-explorer


text:
Feature/deployment and address management

Add deployment functionality to governance.
Adapt integration tests to have deployments through governance
Add integration tests for deployment through vote transactions

Merging into arb call since maintaining both branches are a lot of work

repo: balancednetwork/balanced-java-contracts


text:
[Vulkan] Image barriers cause some images to become incorrectly trashed

Description
Despite not transitioning to or from LAYOUT_UNDEFINED, some images are becoming "trashed" (filled with the text "UNDEFINED") in RenderDoc only. For example, this image (gDepth) is perfectly fine before the start of the pass "HZB Build Pass" (pardon the gaudy marker colors):

At the beginning of HZB Build Pass, there is a pipeline barrier (two actually- the first is just a global VkMemoryBarrier) to ensure gDepth is no longer being used and is in the correct layout (READ_ONLY_OPTIMAL) before, well, building the HZB. That said, the transition is from READ_ONLY_OPTIMAL to READ_ONLY_OPTIMAL, so the image contents should be preserved. However, this is how the image looks after clicking on "HZB Build Pass" (the image is read in the first dispatch and unused by the rest of the pass):

The barrier is visible in the API inspector.
A similar issue happens to another image, "VSM Physical Pages":

For synchronization, I am using solely constructs from VK_KHR_synchronization2: vkCmdPipelineBarrier2, VkImageMemoryBarrier2. Every stage mask is ALL_COMMANDS_BIT and every access mask is MEMORY_READ_BIT | MEMORY_WRITE_BIT, i.e. every barrier is a gigabarrier and I only have to worry about image layout transitions. The validation layer does not report any sync or API usage issues.
Steps to reproduce
capture.zip
To reproduce the issue, open the capture and go to the resource inspector. Search for "gDepthPrev" (this image swaps with "gDepth" each frame), open the image view in the texture viewer, then browse the event timeline for "HZB Build Pass". Observe that the image has been trashed.
The issue can be reproduced for the image "VSM Physical Pages" by similarly searching for the image view, opening it, then browsing to "Virtual Shadow Maps" -> "VSM Enqueue and Clear Dirty Pages", then alternating between actions 38 and 39, observing how the image becomes trashed by the latter despite there only being a GENERAL->GENERAL layout transition.
The application can be run locally by compiling and running my renderer at this commit: https://github.com/JuanDiegoMontoya/Frogfood/commit/ab0bcbc6d3644d4be83ffefc39f8ebafcc46f7e1. Compilation should be fairly straightforward with CMake as dependencies are automatically fetched and a simple test model (the one shown in the images) is included.
Environment

RenderDoc version: 1.33
Operating System: Windows 10
Graphics API: Vulkan
GPU: AMD 7900 XTX
Driver: Adrenalin 24.5.1

Miscellaneous
I suspect this may be an AMD-only issue, but I don't have an Nvidia GPU to test with right now.

I believe this is an AMD driver bug I've seen reported before. The patterns you are seeing are not done (directly) by RenderDoc which is why they are inconsistent and not fully and clearly filled with UNDEFINED but a trashed version (if you see the bottom half of the image for example).
Could you do a test and change any barriers which have the same layout before and after, and duplicate them into two barriers that go A -> B and B -> A where B is any other layout that would be valid for the image? If this is the same bug, it only happens when using sync2 and identical-layout transitions. I was going to try and compile your program to test that myself but it doesn't build for me.

Thanks for the quick response, and apologies for the app not building.
I tried your suggestion and it worked for both the cases I showed. Transitioning to a different layout and back makes the images not lose their contents. I suppose I can work around this in my abstraction by simply emitting a VkMemoryBarrier2 instead of VkImageMemoryBarrier2 when the old and new layouts are the same.

Thanks for verifying, sounds like it is indeed the same AMD driver bug I've seen before. Unfortunately I'm not aware of any workaround on RD's side that would be feasible so this needs to be fixed on their side.

authors: JuanDiegoMontoya baldurk

repo: baldurk/renderdoc


text:
Update to WPE WebKit 2.22.5 and Poky Sumo

This pull request enables building the latest 2.22-release of WPE WebKit.
If you don't want to compile yourself, just pull the finished image from marhoy/balena-wpe:latest
Major changes:

Update the build system to poky sumo
Change layer from meta-wpe to meta-webkit from Igalia
Update recipe to build the latest 2.22-release of WPE WebKit
Enable all hardware decoding tricks for the raspberrypi3

Minor improvements:

Add Tohora in the same way as balena-dash
Add timezone-data to the image to you can specify the TZ-variable as usual
Update to latest version of fbcp

I gave the pre-built image a test and it seems to work nicely. Great stuff @marhoy ! @imrehg and @petrosagg if you two are happy with the code, then lets get it merged.

I also have an image compiled with all the latest stable versions: wpewebkit-2.24.1, libwpe-1.2 and cog-0.3, based on poky thud. (See marhoy/balena-wpe:raspberrypi3-2.24.1-test and -test2 (-test2 is built using openembedded-core instead of yocto poky)).
But for some reason, I have problems with an webpage that uses Google fonts. I wrote an issue about it in the meta-webkit project.
Any ideas about why it's like that?
What's wrong and how do I fix it?

Sending keyboard strokes to the WPE messes up the image, at least for me..
Gives me following error:
xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb

Sending keyboard strokes to the WPE messes up the image, at least for me..
Gives me following error:
xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb

I connected a keyboard to my (normally keyboardless) rpi3, but 'm not able to reproduce.

Are you using the latest 22.2-image? (2.22-latest -> raspberrypi3-2.22.5-75db63d
Can you explain a bit more what you are doing to get these errors?

Note that X11 is not compiled/installed, so don't expect X-applications to work.

Sending keyboard strokes to the WPE messes up the image, at least for me..
Gives me following error:
xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb

Can you try the latest build (tag raspberrypi3-2.22.5-b0c7448 (== 2.22-latest)?
I have added xkeyboard-config to the image, which seems to solve the problem for me.
Martin

Sending keyboard strokes to the WPE messes up the image, at least for me..
Gives me following error:
xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb

Can you try the latest build (tag raspberrypi3-2.22.5-b0c7448 (== 2.22-latest)?
I have added xkeyboard-config to the image, which seems to solve the problem for me.
Martin

Can confirm that it's working now. Thank you for this, it's awesome to see this being alive again.

cannot build using balena build in a multicontainer setup with this latest commit:
[Error]   Build failed
Error: (HTTP code 400) unexpected - No build stage in current context
reverting to a32216e2885528d900142a6ad164f84856de2469 and it builds fine.

@bitmorse Maybe a stupid question, but: You have replaced line 2 of balena-wpe/Dockerfile with something meaningful, right?

thanks for the hint, indeed. I was relying on this project a git submodule and included in my own docker-compose.yml.

@marhoy @bitmorse I just updated the master branch with a prebuilt image

@marhoy did you have any issues with YouTube on this new version? I'm looking at rolling all the updates into the balena-dash project but found when testing that YouTube videos don't play when using the update.

@chrisys I don't think I tried :)
Can you test withmarhoy/balena-wpe:2.24-latest (poky warrior and wpewebkit 2.24.2)?
I've changed my dashboard to that image and youtube seems to work there.
Can you give an example of a URL that does not work?

@marhoy your image works great. It was any YouTube video I tried; for example I use the trick of putting a - between the t and the u in a YouTube URL to get a fullscreen looping video, e.g.: https://www.yout-ube.com/watch?v=4jXEuIHY9ic
Can you PR your latest changes?

@chrisys OK, pull request made.

authors: bitmorse chrisys cpdbogo marhoy petrosagg shaunmulligan

repo: balena-io-projects/balena-wpe


text:
Warnings building on CentOS 7

When building on CentOS 7.6.1810, I get the following warnings:
$ cargo version
cargo 1.34.0
$ cargo build
   Compiling version_check v0.1.3
[...snip...]
   Compiling params v0.8.0
   Compiling wifi-connect v4.2.5 (/home/rwood/Documents/GitHub/wifi-connect)
warning: use of deprecated item 'iron::Error::cause': replaced by Error::source, which can support downcasting
   --> src/errors.rs:5:1
    |
5   | / error_chain! {
6   | |     foreign_links {
7   | |         Io(::std::io::Error);
8   | |         Recv(::std::sync::mpsc::RecvError);
...   |
101 | |     }
102 | | }
    | |_^
    |
    = note: #[warn(deprecated)] on by default
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: use of deprecated item 'iron::Error::cause': replaced by Error::source, which can support downcasting
   --> src/errors.rs:5:1
    |
5   | / error_chain! {
6   | |     foreign_links {
7   | |         Io(::std::io::Error);
8   | |         Recv(::std::sync::mpsc::RecvError);
...   |
101 | |     }
102 | | }
    | |_^
    |
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

    Finished dev [unoptimized + debuginfo] target(s) in 3m 16s

Can these warnings be safely ignored?

It appears so, since wifi-connect built on CentOS 7 appears to "just work" (although the prebuilt binaries from the GitHub releases require a newer GLibc than available on CentOS.

The warnings could be ignored indeed. You are right about the glibc version. You should be fine with a built done on CentOS. You may do a cargo build --release and then strip target/release/wifi-connect to get a less-bloated binary.

authors: majorz rhwood

repo: balena-io/wifi-connect


text:
Update contracts digest to 103037c

This PR contains the following updates:

Package
Update
Change

contracts
digest
9b8811f -> 103037c

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

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

This PR has been generated by Renovate Bot.

Can one of the admins verify this patch?

authors: balena-ci resin-jenkins

repo: balena-os/balena-radxa


text:
balena-yocto-scripts: Update to v1.14.9

Update balena-yocto-scripts from 1.7.1 to 1.14.9
Changelog-entry: Update balena-yocto-scripts from v1.7.1 to v1.14.9
Signed-off-by: Alex Gonzalez alexg@balena.io

@balena-ci rebase

@balena-ci rebase

@balena-ci I self-certify!


text:
Update contracts digest to 79998a2

This PR contains the following updates:

Package
Update
Change

contracts
digest
cbc450a -> 79998a2

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

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

This PR has been generated by Renovate Bot.

Can one of the admins verify this patch?


text:
Union Type field access after casting throws error

Description:
I have a ballerina program as below.
public type Component record {
    map<TCPIngress|GRPCIngress|HttpApiIngress|WebIngress> ingresses?;
};

public type TCPIngress record {|
    int port;
    int targetPort;
|};

public type GRPCIngress record {|
    *TCPIngress;
    string protoFile?;
|};

public type HttpApiIngress record {|
    int port;
    string context;
    boolean authenticate = true;
|};

public type WebIngress record {|
    int port;
|};

Component mycomp = {
    ingresses: {
        http: <HttpApiIngress>{
            port: 8080,
            context: "hr-api"
        }
    }
};

public function main(string... args) {
    string context = (<HttpApiIngress>(mycomp.ingresses.http)).context;
    int ingressPort = (<HttpApiIngress>(mycomp.ingresses.http)).port;
}

This throws following error:
error: .::test.bal:39:63: mismatched input '.'. expecting {'is', ';', '?', '+', '-', '*', '/', '%', '==', '!=', '>', '<', '>=', '<=', '&&', '||', '===', '!==', '&', '^', '...', '|', '?:', '->>', '..<'}
error: .::test.bal:40:64: mismatched input '.'. expecting {'is', ';', '?', '+', '-', '*', '/', '%', '==', '!=', '>', '<', '>=', '<=', '&&', '||', '===', '!==', '&', '^', '...', '|', '?:', '->>', '..<'}

It works when main method is changed as below.
public function main(string... args) {
    HttpApiIngress ing = <HttpApiIngress>(mycomp.ingresses.http);
    int ingressPort = ing.port;
    string context = ing.context;
}

Steps to reproduce:

Compile the above program.

Affected Versions: 0.990.3
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Root cause is https://github.com/ballerina-platform/ballerina-lang/issues/10736

authors: anuruddhal rdhananjaya

repo: ballerina-platform/ballerina-lang


text:
WebSocket service suggestion still uses WebSocket listener

Description:
The WebSocket service creation suggestion in tooling still uses the WebSocketListener. The WebSocketListener has been removed and http:Listener is used in WebSocket as well.
A similar issue can be observed in Test generation as well
Steps to reproduce:

Affected Versions:
Ballerina 1.0.0 alpha 3

This has been resolved in the 1.0 release


text:
Disabled a Signature Help Test Case

Description:
Following test case has been disabled due to the change introduced by #23884
Earlier, error type was available as a visible symbol and with the changes, that is not available in the visible scope entries. We need to find an alternative way to handle this.
https://github.com/chiranSachintha/ballerina-lang/pull/1/files#diff-1d03f5b2b9b6d2b4794013ea427d3636R119

Closing the issue since the new implementation has been addressed this.


text:
Interop doesn't work with readonly

Description:
$title.
Affected Versions:
slp1

Current workaround is to use (any|error) & readonly as the type where readonly would be used. This would cover the same value space.


text:
An API to execute Ballerina stream next function in standard libraries

Description:
Ballerina gRPC library has a requirement to execute next function in a stream at native level. ATM, a stream comes to the native side as a StreamValue object. The StreamValue is an internal object, and hence it is not accessible to the stdlib native code.
Therefore, it would be better to have a direct API to execute the next function in a stream. Perhaps as a synchronous API and asynchronous API.
Related Discussions
[1] https://ballerina-platform.slack.com/archives/C9WMA6QDC/p1609926111194400
[2] https://ballerina-platform.slack.com/archives/C9WMA6QDC/p1609856798190700
Affected Versions:

SLP9

@manuranga @warunalakshitha Can you prioritize this and add support to read the next value from the stream object, please.

@manuranga @warunalakshitha Can you prioritize this and add support to read the next value from the stream object, please.

BStream already have a api to get iterator object and then you can call next method using Runtime.invokeMethodAsync method. ATM we do not have a synchronous api. @manuranga Shall we add sync api to so it will be direct call to object method without scheduler.  But we need to make sure object method doe not have any async code.

BStream already have a api to get iterator object and then you can call next method using Runtime.invokeMethodAsync method. ATM we do not have a synchronous api. @manuranga Shall we add sync api to so it will be direct call to object method without scheduler.  But we need to make sure object method doe not have any async code.

@BuddhiWathsala @daneshk is this still a high priority ? is Buddhi's current approach working ?

@BuddhiWathsala @daneshk is this still a high priority ? is Buddhi's current approach working ?

Yes, it is working as expected ATM. We can proceed with it.

Yes, it is working as expected ATM. We can proceed with it.

I am closing this as per the last comment.

authors: BuddhiWathsala daneshk manuranga warunalakshitha


text:
[Bug]: "cannot create new error value" error when the error type reference in the error constructor is loaded via the BIR

Description
$title.
Workaround is to use the type in the contextually-expected type.
Steps to Reproduce
maryam/myproj
public type E1 distinct error;

public type E2 distinct (E1 & error<record {|anydata body;|}>);

Usage
import maryam/myproj;

public function main() {
    myproj:E2 e = error("", body = ""); // OK
    error e2 = error myproj:E2("", body = ""); // compilation error: cannot create a new error value from 'myproj:E2'
}

Affected Version(s)
2201.2.1
2201.3.0-SNAPSHOT
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Refer the duplicate issue https://github.com/ballerina-platform/ballerina-lang/issues/39542 for more information.


text:
Update README files of Tool Plugins

Purpose
This is to update the below files to link them to the respective content in the Ballerina website.
[1] /tool-plugins/intellij/README.md
[1] /tool-plugins/vscode/README.md
Fixes #
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

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

@@           Coverage Diff           @@
##           master   #17491   +/-   ##
=======================================
  Coverage    9.68%    9.68%
=======================================
  Files          46       46
  Lines        1476     1476
  Branches      239      239
=======================================
  Hits          143      143
  Misses       1320     1320
  Partials       13       13

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 c7745bd...db9b27a. Read the comment docs.

Shall we add the requested changes? :)

Done.

authors: codecov-io praneesha


text:
Fix retry request implementation of OAuth2 outbound authentication

Purpose
Fix retry request implementation of OAuth2 outbound authentication.
Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[x] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

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

@@           Coverage Diff           @@
##           master   #18453   +/-   ##
=======================================
  Coverage   15.15%   15.15%
=======================================
  Files          48       48
  Lines        1254     1254
  Branches      197      197
=======================================
  Hits          190      190
  Misses       1050     1050
  Partials       14       14

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 c34009c...21ff6a1. Read the comment docs.

authors: codecov-io ldclakmal


text:
Add type checker changs for client resource access action

Purpose
$title
Part of: #36024
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@rdulmina The commit messages and PR heading is not according to the best practices. Please correct them.
A properly formed Git commit subject line should always be able to complete the following sentence:
If applied, this commit will your subject line here
Refer [1] for more details.
[1] https://github.com/ballerina-platform/ballerina-lang/blob/master/CONTRIBUTING.md#submit-your-contribution

The build is failing will fix

authors: anupama-pathirage rdulmina


text:
Time zone APIs won’t work as expected

Description:
The expected behaviour of the newly added time zone API is as follows.
import ballerina/time;
import ballerina/io;

public isolated function main() returns error? {

    time:Zone systemZone1 = check time:loadSystemZone();
    time:Civil currentSystemCivil = systemZone1.utcToCivil(time:utcNow());
    io:println(currentSystemCivil);

    time:Zone? systemZone2 = time:getZone("Asia/Colombo");
    if systemZone2 is time:Zone {
        time:Civil currentSystemCivil1 = systemZone2.utcToCivil(time:utcNow());
        io:println(currentSystemCivil1);
    }

}

But it won't work as above due to this lang level issue in swan lake beta 06.
However, it will work as the following workaround. When ballerina language fixes the abovementioned issue, this workaround won't break.
import ballerina/time;
import ballerina/io;

public isolated function main() returns error? {

    time:TimeZone systemZone1 = check time:loadSystemZone();
    time:Civil currentSystemCivil = systemZone1.utcToCivil(time:utcNow());
    io:println(currentSystemCivil);

    time:Zone? systemZone2 = time:getZone("Asia/Colombo");
    if systemZone2 is time:TimeZone {
        time:Civil currentSystemCivil1 = systemZone2.utcToCivil(time:utcNow());
        io:println(currentSystemCivil1);
    }

}

Affected Versions:

SL beta 06
Time version 2.1.0

Related Issues (optional):
https://github.com/ballerina-platform/ballerina-lang/issues/34280

Closing this issue since it is working in the latest Ballerina version(2201.10.0).

authors: BuddhiWathsala TharmiganK

repo: ballerina-platform/ballerina-library


text:
Change frontend color scheme via configuration.yaml

This is 100% a wishlist item, so don't feel bad about saying no :).
I was wondering if it might be possible to have a configuration setting for the frontend color scheme?  I don't dislike the current color scheme, but I do dislike that when I'm in a dark room (aka, I just woke up and the sun isn't up yet) that the HA screen has so much white.  Doubly so since we already have a sun tracker, so if we could expose the color scheme into the configuration file it'd, in theory, be pretty simple to write some automation to handle color.

This issue comes up from time to time in the chat too. It is not going to be implemented.
Adding colors will add a lot of extra development effort on every extra feature that is being developed for the frontend, because now it has to look good in whatever combination the user can pick. That's just not worth the cost.

Just chiming in to agree that the white and light blue at night is very jarring. I hope this gets looked at eventually.

balloob,
That's a fair sentiment, what if we just limited it to a single "Night Time" mode?

Sorry to dredge up a closed issue, but a night time mode would be very handy. Full themeability probably isn't worth the effort I agree, but I'd like to have HA on an old tablet in my living room as a sort of central information panel and the white/blue interface (while quite pretty) is way too bright in the dark. I imagine I'm not the only one wanting to do this.
I'd suggest something like the colorscheme Grafana uses, but anything on a black or otherwise dark background works for me.

@balloob Can you at least agree that a single night/dark mode would be very useful? We can't be the only ones who are using this on our tablets at night to check the status of things or in a dark room when watching a movie.

I agree with this request, I open HA on my iphone when we're going to sleep to see if everything has run and a darker theme would be nicer to view then

Op 25 feb. 2016 om 13:58 heeft David Thomas notifications@github.com het volgende geschreven:
@balloob Can you at least agree that a single night/dark mode would be very useful? We can't be the only ones who are using this on our tablets at night to check the status of things or in a dark room when watching a movie.
—
Reply to this email directly or view it on GitHub.

I completely agree. A simple night-mode esque theme would be great. Based on a user-set schedule in configuration.yaml or with a button on the front-end. Loving HA so far. Keep up the good work.

One more vote for a simple night mode using a darker color scheme.

At least night mode (white on black) would be very helpfull!!

authors: Bart274 balloob betonmoewe blasmat csouers iwoloschin jasonmhite synth3tk

repo: balloob/home-assistant


text:
First cut of switch.template

A first implementation of the meta component described here https://github.com/balloob/home-assistant/issues/949. This is in the same family as sensor.template.
The main purpose is to allow you to integrate several devices into a single switch, but I expect it will have other uses.
The state of the switch is set from a template. Either a logical value, or on / off will set the value of the switch in the gui. Turning on or off the switch will fire an action in the same format as automation.
Best to make sure firing the on or off actions will update the template, otherwise it doesn't make much of a switch!
Here is an example that turns on and off a script (just as a demo)
switch:
    - platform: template
      switches:
          test_switch:
              friendly_name: 'Slow script'
              value_template: "{{ states.script.slow.state }}"
              turn_on:
                service: script.turn_on
                entity_id: script.slow
              turn_off:
                service: script.turn_off
                entity_id: script.slow

Here is something I expect to use. My skylight has a sensor to show if it's open or closed - and two momentary switches to operate the open and close. I can replace my custom component with something like this:-
switch:
    - platform: template
      switches:
          skylight:
              value_template: "{{ states.sensor.skylight == 'tripped' }}"
              turn_on:
                service: switch.turn_on
                entity_id: switch.skylight_open
              turn_off:
                service: switch.turn_on
                entity_id: switch.skylight_close

Looks great :dolphin:

authors: balloob pavoni


text:
Can internal project release already the rebrand version?

@alexsoeres

@joachimprinzbach is that possible?

Discuss with Michael Besel first

website of design system will still be password protected until go live
repositories can be merged sooner, packages can be aligned before go live

Internal applications: OK to go live before October 28th.

repo: baloise-incubator/design-system


text:
Feature: Matplotlib backend

[x] Matplotlib tick boxes update correctly
[x] Matplotlib radio buttons properly displayed (mimicks a dropdown menu)

license: Unlicense


text:
Fix for new @import statements being ignored

Adding an @import statement in a .less file fails to update the list of imports for that file, which means that any subsequent change to the imported file(s) does not cause the .less file with @import statements to be recompiled. This fix changes the way the main watchStream works so that the callback is wrapped and the @imports of all changed files are compared.
There is an [open issue for this in the original gulp-watch-less] (https://github.com/Craga89/gulp-watch-less/issues/7).

I tried on both gulp 3.9.0 and gulp 4, there is no problem.
The following changes will trigger the .less file to recompile and get the result as expect.

Add new @import statement(s) to .less file
Change less code in the imported file
Reorder the @import list in the .less file
Delete @import statement(s) in the .less file
Change less code in the .less file

The problem only seems to manifest itself when a new .less file is involved. For example, if you add a new file and then add @import statements to an existing .less file to import the new file:

Add a new .less file.
Add an @import statement to an existing .less file to import the new file.
Change less code in the new .less file.

In the third step both the new and existing .less files should be compiled, but only the new .less file is compiled.
Additionally, adding @import statements to new files doesn't work as it should:

Add a new .less file.
Add an @import statement to the new file to import an existing .less file.
Change less code in the existing .less file.

In the third step both the new and existing .less files should be compiled, but only the existing .less file is compiled.
I'm using gulp 3.9.0.

@marsupialmouse  Can you show your gulp task code? And which Gulp Cli version do you use?

The CLI is also 3.9.0. Here's the task:
gulp.task('less-watch', function () {
    return gulp
         .src('content/less/**/*.less')
         .pipe(watchLess('content/less/**/*.less', { verbose: true }))
         .pipe(less())
         .pipe(gulp.dest('content/css'));
});

I have some .less files directly in content/less that import files from sub directories and some in subdirectories that import .less files from other subdirectories.

Ok, you mix the less files and import files.
You should use a filter in you gulp src like this:
var lessGlobs = ['content/less/main-*', 'content/less/**/main-*'];
gulp.task('less-watch', function () {
  return gulp.src(lessGlobs)
        .pipe(watchLess(lessGlobs, {verbose: true}))
        .pipe(less())
        .pipe(gulp.dest('content/css'));
});

Only files start with prefix main- will be compiled and watched.
It should also work fine to use negative filter like gulp.src(['content/less/**/*.less', '!content/less/_*.less']) when import file name are begin with _.

Thanks - using a more specific glob fixes the problem of importing new files. Unfortunately it also uncovers some other problems.
Let's say I have this directory structure:
content/less/desktop.less                   (imports about.less and home.less)
content/less/desktop/includes/colours.less  (contains colour variables)
content/less/desktop/pages/about.less       (just styles, no imports)
content/less/desktop/pages/home.less        (just styles, no imports)
content/less/desktop/pages/search.less      (styles + import colours.less)

We only need to compile the .less files in the base content/less directory, so we use this task:
gulp.task('less-watch', function () {
    return gulp
         .src(['content/less/*.less'])
         .pipe(watchLess('content/less/*.less', { verbose: true, base: 'content/less' }))
         .pipe(less())
         .pipe(gulp.dest('content/css'));
});

Change home.less to import colours.less (recompiles desktop.less - right)
Change variable in colours.less (does nothing - wrong: should recompile desktop.less)
Remove import statement from home.less (recompiles desktop.less - right)
Change variable in colours.less (does nothing - right)
Change desktop.less to import search.less (recompiles desktop.less - right)
Change variable in colours.less (recompiles desktop.less - right)
Remove import statement from search.less (recompiles desktop.less - right)
Change variable in colours.less (recompiles desktop.less - wrong: colours.less is no longer imported by any .less files)
Delete desktop.less (error on line 23 of index.js - process terminated - wrong)

Renaming desktop.less (instead of deleting it) results in the same error.
It looks like my pull request doesn't work properly with the simplified glob anyway, so I'll close this.

@marsupialmouse Thank you for testing it so detailed, can you move this to a new issue? I will fix these in the next version.

Thanks, will do.

authors: bammoo marsupialmouse


text:
Resolves #12 : Configured react-i18next and added fallbacks

resolves #12

closes #12

repo: bancodobrasil/stop-analyzing-embed