using vllm to answer in Qwen-7B-Chat, there is a recurring issue of answers being repeated multiple times,

When using vllm to answer in Qwen-7B-Chat, there is a recurring issue of answers being repeated multiple times, which is not present when not using vllm.
GPU: 2  T4
MODEL: Qwen-7B-Chat
PROMPT:  <指令>根据已知信息，简洁和专业的来回答问题。如果无法从中得到答案，请说 \n"根据已知信息无法回答该问题，请使用随手拍进行提问，随手拍使用路径：手机移动办公-工作台-数字直通车"。不允许在答案中添加编造成分，答案请使用中文，结果以markdown的形式输出。</指令>\n\n<已知信息>问题：是否可以先开户、后面再补上门核实和法人开户意愿核实工作？ 答案：上门核实可以后补，法人开户意愿核实需要提前或同步完成。\n问题：客户签约财资需要哪几个步骤（大步骤，具体的步骤可以参考操作文档） 答案：1、客户确认签约财资的方案；\n2、上级单位与下级单位完成账户使用授权（如无下级单位或关联单位，则跳过这一步）；\n3、在前台签署相关协议，录入系统；\n4、经办行引导客户登录财资，并协助客户配置相关设置及参数；\n问题：营业执照刚刚注册好，工商系统还查不到，能开户吗？ 答案：在风险可控的情况下，确定客户开户信息真实，可以开户。</已知信息>\n\n<问题>企业开户流程</问题>

INFO 11-20 08:54:05 async_llm_engine.py:370] Received request 8b2eab1b928747abb9d544a6b2a5a37a: prompt: '<|im_start|>system\nYou are a helpful assistant.<|im_end|>\n<|im_start|>user\n<指令>根据已知信息，简洁和专业的来回答问题。如果无法从中得到答案，请说 \n"根据已知信息
无法回答该问题，请使用随手拍进行提问，随手拍使用路径：手机移动办公-工作台-数字直通车"。不允许在答案中添加编造成分，答案请使用中文，结果以markdown的形式输出。</指令>\n\n<已知信息>问题：是否可以先开户、后面再补上门核实和法人开户意愿核实工作？ 答案：上门核实可以后补，法人开户意愿核实需要提前或同步完成。\n问题：客户签约财资需要哪几个步骤（大步骤，具体的步骤可以参考操作文档） 答案：1、客户确认签约财资的方案；\n2、上级单位与下级单位完成账户使用授权（如无下级单位或关联单位，则跳过这一步）；\n3、在前台签署相关协议，录入系统；\n4、经办行引导客户登录财资，并协助客户配置相关设置及参数；\n问题：营业执照刚刚注册好，工商系统还查不到，能开户吗？ 答案：在风险可控的情况下，确定客户开户信息真实，可以开户。</已知信息>\n\n<问题>企业开户流程</问题><|im_end|>\n<|im_start|>assistant\n', sampling params: SamplingParams(n=1, best_of=1, presence_penalty=0.0, frequency_penalty=0.0, repetition_penalty=1.0, temperature=0.0, top_p=1.0, top_k=-1, min_p=0.0, use_beam_search=False, length_penalty=1.0, early_stopping=False, stop=['<|im_start|>', '<|endoftext|>', '<|im_end|>'], ignore_eos=False, max_tokens=7908, logprobs=None, prompt_logprobs=None, skip_special_tokens=True, spaces_between_special_tokens=True), prompt token ids: None.2023-11-20 08:54:05 | INFO | httpx | HTTP Request: POST http://<IP_ADDRESS>:20002/worker_generate_stream "HTTP/1.1 200 OK"
INFO 11-20 08:54:05 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.0 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 9.4%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:10 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 27.2 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 13.6%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:15 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.9 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 18.3%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:20 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.7 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 22.5%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:25 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.7 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 27.2%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:30 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.7 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 31.4%, CPU KV cache usage: 0.0%
2023-11-20 08:54:31 | INFO | model_worker | Send heart beat. Models: ['Qwen-7B-Chat']. Semaphore: Semaphore(value=4, locked=False). call_ct: 1. worker_id: bc0bc8a3.
2023-11-20 08:54:31 | INFO | controller | Receive heart beat. http://<IP_ADDRESS>:20002
2023-11-20 08:54:31 | INFO | stdout | INFO:     <IP_ADDRESS>:57204 - "POST /receive_heart_beat HTTP/1.1" 200 OK
INFO 11-20 08:54:36 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.5 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 35.6%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:41 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.4 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 40.3%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:46 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.8 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 44.5%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:51 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.5 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 48.7%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:56 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.3 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 53.4%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:01 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.9 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 57.6%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:06 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.9 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 61.8%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:11 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.8 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 66.0%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:16 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.7 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 70.2%, CPU KV cache usage: 0.0%
2023-11-20 08:55:16 | INFO | model_worker | Send heart beat. Models: ['Qwen-7B-Chat']. Semaphore: Semaphore(value=4, locked=False). call_ct: 1. worker_id: bc0bc8a3.
2023-11-20 08:55:16 | INFO | controller | Receive heart beat. http://<IP_ADDRESS>:20002
2023-11-20 08:55:16 | INFO | stdout | INFO:     <IP_ADDRESS>:57220 - "POST /receive_heart_beat HTTP/1.1" 200 OK
INFO 11-20 08:55:21 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.7 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 74.3%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:26 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.5 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 78.5%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:31 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.6 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 82.7%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:36 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.7 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 86.9%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:41 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.2 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 91.1%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:46 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.1 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 95.3%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:51 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.5 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 99.5%, CPU KV cache usage: 0.0%

same problem


x86_64 ADD r/m64,imm32

Master.
There might be an issue with https://github.com/NationalSecurityAgency/ghidra/blob/ca6c01268e4f9bc09e276420fb21f21d99e27ab3/Ghidra/Processors/x86/data/languages/ia.sinc#L2285
Add imm32 sign-extended to 64-bits to r/m64 and it's currently an unsigned 32-bit, and at least the add rax insn is also broken

Looks like ADD, AND, CMP, and SUB have this issue.  ADC, MOV, and TEST have this similar format, but are correct.


Don't allow snapshots for postgres:9, fixes #3583

The Problem/Issue/Bug:
Snapshots don't work with postgres:9. Nobody has really stepped up to study it, and postgres:9 is probably a very limited case anyway, so just don't let people use snapshots there.
Manual Testing Instructions:

[x] ddev snapshot and ddev snapshot restore on a project with database=postgres:9

No, your problem would be that you're using omit_containers: [db]. Perhaps you're using the old, old way of using postgres, where it's not configured via DDEV but via a separate add-on service? You probably have a .ddev/docker-compose.postgres.yaml and probably have omit_containers: [db].

Yes, but your snapshot has no data unless you exported from the old system and imported into the new, you'll have to migrate your data from the old db to the new one.

Oh, and until you remove the docker-compose.postgres.yaml and change your db to postgres:11, you won't be using the ddev-built-in facility. I'm sure you already know that.

The snapshot was made on the old system and it appears it has some data in but I also have dump done with drush sql:dump to play it safe.
Yes, I'm aware that all the old references of postgres need to be removed to use the built-in one. Thanks.


spirv-fuzz: Avoid out-of-bounds access

Fixes #4389.

The CI failure seems to have to do something with the re2 dependency.


fix gap between #sidebar and #footer

Currently #sidebar has bottom: 48px and the #footer has height: 45px. This should fix the gap.

Actually, I looked at this quickly, and because of themes, this is not as straightforward. I'll take a closer look and get back to you soon @realies. Good catch though!!

@astorije I looked through the themes, and it's not an issue anywhere, so it's fine.

I was also having a hard time figuring what I meant, but it's actually the "Example" theme that I was talking about: because of this line, the fix in this PR doesn't apply to "Example".
@realies, am I assuming correctly that your screenshot is for Morning? The fix works for this theme indeed.
Could you update example.css#L14 to be 49px instead of 52? (I tried and anything under 49 will make sidebar/footer overlap).

@astorije I thought the margin around footer in example theme is fine because footer has margin on all sides, not just top.

Aaah, that's a very fine point. I was missing it because all I was playing with... was the window zoomed at the maximum :) Perfect illustration of the expression "missing the big picture" :D
Anyway, that's perfect then. Thanks @realies, sorry it took me so long to react and then notice my mistake!


Changing Editor Settings Asset library URLS doesn't update editor

Godot version:
3.2.4-rc5
OS/device including version:
N/A
Issue description:

I change asset library urls in editor settings, but the editor dropdown is not updated. This is because of missing functionality in  #45202. Restarting the editor updates with new settings, but this should not require a restart.
Steps to reproduce:
Initial:

Update settings, for example add new entry or modify current entries:

Editor doesn't update with new ones:

After editor restart, we see our changes:

Minimal reproduction project:
New/empty project is all you need.

NOTIFICATION_EDITOR_SETTINGS_CHANGED can be used in _notification() for this purpose. Here's an example: https://github.com/godotengine/godot/blob/942f5f0cb282cbc2b3fb766e3c7614e82b98dd9b/editor/editor_help_search.cpp#L112-L114


feat(dispatch-api,auth): required permissions to get metadata for all run, documented APIs

closes #3035
closes #3036
closes #3037
closes #3040

This change breaks the platform front end since it is using the metadata endpoint for now

This also prevents the api from starting up due to missing dependencies

Its important to keep unpublished projects private. Our example simulations can be published. The platform should not display other simulations.
The getAllMetadata method and associated endpoint could be restricted to published projects. In that case, the permissions can be removed.

:tada: This PR is included in version 5.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Startup crash when Scout is open

Not a serious issue but hxScout (Windows build 0.5.1) crashes when i run it next to Scout.
When i start Scout and have hxScout open, Scout complains about not being able to open port 7934, so maybe that's the problem?

Thanks. Issue #89 on the hxScout repo.

@sh-dave - one question: If you were using hxScout next to Scout, were you using Scout for profiling a SWF app and hxScout for profiling an hxcpp app?

Yes, i had Scout open yesterday while i profiled the flash build of my app, and then wanted to give hxScout a try for a native build today.


Bot not online , process split , all 3 intents given , ticket reopen

Describe the bug
So I already made a ticket about this in the discord , the prosses split into 2 and bot never comes online
To Reproduce
Steps to reproduce the behavior:

idk , I just compiled and ran the executable from the builder as ussual

Expected behavior
So it just splits the prosses into 2 and bot not coming online , and YES I DID GIVE ALL 3 INTENTS
So here is screenshot of proccess splitting into 2 (Retard.exe)

Desktop (please complete the following information):

OS: , Windows 10 pro , Ghost spectre edition (legacy , no defender) let me know if you want download link
Python version: Latest

Additional context
Sometimes it doesn't even add to startup but sometimes it just freezes at 70% CPU usage and sometimes it freezes at 1%

That profile picture is offensive.

May you opened it twice

I only did once , it freezes and doesnt work after that

That profile picture is offensive.

Suggest a different one then

splitting the process into 2 is normal becuz of asyncio
Make sure your serverid and bot token are valid for now

splitting the process into 2 is normal becuz of asyncio
Make sure your serverid and bot token are valid for now

I did but I figured out its the IS so this ticket can be closed


Create website for testing Token generation #16

Brief summary of the change made

added index.html file  which includes everything for OpenPaygo token website

Are there any other side effects of this change that we should be aware of?
none
Describe how you tested your changes?

by referring to the unit tests.  token matches the format of the token generated in the browser

Pull Request checklist
Please confirm you have completed any of the necessary steps below.

[x] Meaningful Pull Request title and description
[x] Changes tested as described above
[x] Added appropriate documentation for the change.
[x] Created GitHub issues for any relevant followup/future enhancements if appropriate.

@dmohns can i get your review

Nice, thanks @munyanezaarmel the website look good.
However, you are essentially hardcoding the entire repositories code into the HTML file, which is not exactly what we want.
Could me make it more like this:

Use a JavaScript website framework of your choice
Install the OpenPAYGO-js using npm

Build the website using npm production build.

Hello @dmohns,
Thank you for your review. I've decided to proceed with React/Next.js for my project. However, I'm encountering an issue with package accessibility. Despite successful installation, I'm unable to access the package in my code.
A significant concern is the absence of an index.js file that clearly shows which functions are available to be called. This omission is causing confusion, as it's unclear which functions are intended for use and which are not.
Could you please provide documentation on how to properly use this package? Specifically, it would be helpful to have:

A clear list of exported functions and their purposes
Examples of how to import and use these functions
Any configuration or setup required

For reference, I'm looking for something similar to the documentation style found on the npm website for packages like 'decoders' (https://www.npmjs.com/package/decoders).


grafana alert to alertmanager: some alertrules resolved in grafana but still firing in the alertmanager

alertmanager version:  0.21.0
Recently, I found something interesting and i cannot understand the alert mechanism.

Alert rules A,B,C and D trigger alarm。 When rule B is outrange (830, 1620), the alert resolved. But the alert rule B was still firing in the alertmanager.  And we receive the email which is A,C,D is resolved and B was firing.  I cannot understand the alert mechanism.

sorry but I'm not familiar with Grafana alerting. Maybe ask them directly?

sorry but I'm not familiar with Grafana alerting. Maybe ask them directly?


Feature: File Actions Don't Support Atom chown

There's at atom for managing the owner and group of files, but no actions support this.

issue #502 is related, its the reason for the draft implementation in #506 requires sudo/doas/run0 when running the comtrya binary for it to work.

With #506 complete, just need to implement for the directory set of actions.

Should we also support chown for copy the action or does the implementation of the Chown action and optional fields in file.download address this?

I think that pretty much covers all the ones that could benefit from it. Will close the issue.


Add OpenAPI Spec - To Cover the Context Boundry

Develop an Open API Spec to initialize a contract for future UI development
It will be good to document all the available services and Domain Model

I have given a start here
https://app.swaggerhub.com/apis-docs/VinodhThiagarajan1309/hostel-pass-management/0.0.1
Let me know if you want to develop further - @NishkarshRaj

@VinodhThiagarajan1309 I would definitely look into this and revert.


Small typo in pylama/lint/extensions.py

Should read compatibility rather than compability.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Thank you for the feedback. The issue has been fixed.


Removed a second reference to testrpc.

We shouldn't need the double of the testrpc module. I wanted to have a pull request reviewed just to make sure I didn't delete anything we wanted.

That's odd


Support undecidable generics

It should be possible to use undecidable generics types in function definitions.
e.g.
sealed trait WeirdGADT[+A]
case class IntValue(value: Int) extends WeirdGADT[Int]
case class SomeValue[+A](value: A) extends WeirdGADT[A]
case class SomeOtherValue[+A, +B](value: A, value2: B) extends WeirdGADT[A]

// This fails on unknown type params
def printsWeirdGADT(g: WeirdGADT[String]): String = g match
  case SomeValue(value) => s"SomeValue($value)"
  case SomeOtherValue(value, value2) => s"SomeOtherValue($value, $value2)"

This fails, because SomeOtherValue cannot be fully constructed based on parent's type params.
Either some default will have to be used or a new type of form element introduced - one that lets the user pick any supported type.

This is an extension of #28


Error Corrected: Incorrect Syntax at HBase-Spark Module Scala / Java Examples

This pull request has corrected syntax error at HBase-Spark Module Scala / Java examples.

hbaseContext.bulkGet method requires String as a Tablename instead of org.apache.hadoop.hbase.TableName type otherwise throws compilation error.

Hey Chetan,
Based on your earlier email to dev@, it looks like you've discovered that Apache HBase uses patches attached to Jira issues as the means by which you can contribute changes to the project. As such, would you mind closing this pulling request, please?

Sure


[Feature] Start NotificationService on app start even if there's no Wi-Fi connection

ConnectionStateService checks if there is an active Wi-Fi connection and starts other services


Backend changes for pod actions - 2

Continued from here: https://github.com/praekelt/casepro/pull/51
New PR to avoid merge issues with previous PR.

:+1: when travis is happy


Karma tests fail

@Johann-S: opening this to track the problem. Is it reported upstream?

OK, it seems it's https://github.com/travis-ci/travis-ci/issues/8836
I'll try some of the workarounds.


Empty 'Title' not possible

I don't like a job title in the about me page of my personal website. So I'd like to leave it empty. However, saving an empty value in the admin panel will show the plugin default for Santa.
A workaround is to save a space character which shows up empty. But this renders a <h3> section with the space.
Since reverting to the plugin default is standard Grav behaviour, I think the only option to really suppress the job title would be to create a toggle for this. If you allow a PR for this, I will submit one.

In deed I suppose a toggle would be the right option here.
If you have time to make a PR, that's great, I'll merge it whenever I can, thank you.

I will submit a PR in the coming day(s). You could wait with a new release and include this as well.

Thank you.
My thought exactly ;)

That was not too difficult. I just love Grav.


Want to join forces?

I have committed the initial API to my repository. Please have a look and let me know if you want to join forces.

That's quite a lot of code you have there, shame you haven't push that earlier. I wouldn't start writing my own. :) And it seems there are quite substantial differences so maybe let's just keep a close eye on each others repos and maybe some day they will become similar enough to try merging. Does it sound reasonable?

We can still merge, I've only been working on the request portion of the API. It seems that you've done most of your work on parsing and presenting the response. Merging ought to be easy.

It seems that you've done most of your work on parsing and presenting the response.

Just the ephemeris and ids of the bodies and it still needs some polishing around error handling since it unwraps a lot. My goal was to implement minimal set of features allowing someone to write newtonian simulator of the system. So just the vectors, masses and names with hard-coded units and reference point.

but wasn't really motivated to finish and polish it

Yeah, JPL does know how to demotivate someone to use their API :)

I can already see how we could integrate 95% of your code without any changes.

Cool. Let me know how'd you like to do it.

Okay, I will elaborate my plans tomorrow, because it's midnight in India right now.

Firstly, most of the parsing code can be moved immediately. The module tree would be split into two main areas, request and response. The code from ephemeris.rs and utilities.rs can be moved into the response module right now (if you consent to it). client.rs would require some modification to use the api provided by request, but it can otherwise be moved to request.
Here's how the tree would look:
src/
├─ lib.rs
├─ request/
│  ├─ presets.rs (client.rs)
│  ├─ .../
├─ response/
│  ├─ utilities.rs
│  ├─ ephemeris.rs
│  ├─ .../

If I have your consent, I shall open a commit the code from those files into my repo with your name under the commit authors list.

Of course, please go ahead.

If csv output is available, shouldn't we be parsing in csv format instead of text?

It would simplify a lot, but I didn't know it's even available.
You can select a JSON in the API, but it's just the same text wrapped in an object. :)

Parser more or less works, therefore I would rather leave it for later as a totally different task. CI and MVP should have the priority before under-the-hood changes. To be honest, some roadmap would be nice for this lib too. Working in the team has some boilerplate unfortunately.

In my opinion, the MVP should only include state vectors for now. Parsing could be as simple as detecting $$SOE$$ and $$EOE$$ and deserialising everything between them using the CSV crate.
I also think that we should choose an HTTP client for the library user, but take inspiration from tower's Service trait. But we can do that after MVP.
Let me know what you think.

I don't know. I mean, usually I do appreciate ability to inject or swap stuff, but over the years I've also started to appreciate things that just work without questions asked. I'd rather imagine that users of this library would be some scientists or something, who might not want to care about choosing a HTTP library.
I've been thinking a lot before writing this kind of tests. They don't mock out the client, nor set up a fake server, instead they talk to the real thing. Sure, they will brake when API changes or won't work at all if someone doesn't have Internet access or is behind some proxy (I don't know if reqwest can read the system config) etc. But ultimately I've concluded that benefits outweigh the risks. And they already payed off. It turned out that JPL's API fails a lot and retries are needed.

Are you continuing development of this crate?

Not as actively as before, but I will accept some PRs and make releases if something pops in.

Just cleaning up old tickets.


Add pigz to all containers containing dcm2niix as default

Can you see any issue with doing this @stebo85 ?
$ sudo apt install pigz  [On Debian/Ubuntu]
$ sudo dnf install pigz  [On CentOS/RHEL/Fedora]
$ sudo pacman -S pigz    [On Arch/Manjaro Linux]
OR
$ yay -S pigz

yes, that's possible. Which containers contain dcm2niix?

bidscoin/3.7.0
bidstools/1.0.0
I guess mricron also uses dcm2niix?
Should also make a dcm2niix container! Can't believe we are missing this one!
QSMxT?
MRTrix?
Nipype?


Preset rune pages

It'd be cool if you were able to just save a rune page on the app and view it at any time, so that those who can't afford extra rune pages don't have to go through the pain of having to memorize or look up guides.

I've labeled this as an enhancement since this seems like a really good idea.
I will take a look if and how it's possible to to make this a real thing soon!

Sounds really good


Using phantomjs 1.9.x binary with phantom 2.x

Due to a few environmental issues, I couldn't get phantomjs 2.1.1 to run on my machine, so I'm trying to use phantomjs 1.9.x.
I tried passing binary in the options:
phantom.create([], {port: 12345, binary: "path to 1.9.x binary"). This resulted in an EPIPE error.
It worked fine when I manually copied phantomjs 1.9.x binary into phantomjs-prebuilt folder, but I'd like to know if there's a way to pass custom binary path as an option to phantom?
Environment

OS: RHEL 5.5
Node version (node -v): 4.4.1
package version: 2.0.10

That's not supported. I removec binary feature because a lot of tests depend on the latest version.

I think your best bet is going to build locally by changing the phantomjs dependency in package.json

Closing this ticket because there has been no response. We can reopen if needed.

Thanks, I couldn't find time to post an update. Unfortunately, none of the older versions of phantomjs-prebuilt is fetching 1.9.x of phantomjs for me to build locally. I guess for now, I will go with manually copying the phantomjs binary into nodemodules.


Detection for runner in script

I have checked the following:

[X] I've searched existing issues and found nothing related to my issue.

Describe the feature you want to add
As mentioned in #2397 I would like to have a possibility to determine wether the current request is triggered by a runner or as a single request. This will be beneficial especially when using with #2116 and a skip request function.
Usage is like this
bru.isRunner()
Returns either true or false
Mockups or Images of the feature

Just merged the PR #3200
New api is bru.getExecutionMode()
This will return

standalone - when single request is being run
runner - during collection runner is in progress

Just merged the PR #3200
New api is bru.getExecutionMode() This will return

standalone - when single request is being run
runner - during collection runner is in progress

Thank you so much @helloanoop!
Just one remark, it's req.getExecutionMode() not bru.getExecutionMode(). This does totally make sense, just not to confuse anyone passing by this ticket.


Peer dependency conflict with react-json-view in<EMAIL_ADDRESS>

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
While testing 3.0.0-alpha.0, a warning popped up regarding the overriding of a peer dependency. Here's the warning I encountered:
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving<EMAIL_ADDRESS>npm WARN Found<EMAIL_ADDRESS>npm WARN node_modules/react
npm WARN   peerOptional react@">= 16.8.0 < 19.0.0" from<EMAIL_ADDRESS>npm WARN   node_modules/@docsearch/react
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN     node_modules/@docusaurus/theme-search-algolia
npm WARN   33 more (@docusaurus/core, @docusaurus/mdx-loader, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>|| ^16.3.0 || ^15.5.4" from<EMAIL_ADDRESS>npm WARN node_modules/react-json-view
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   node_modules/@docusaurus/plugin-debug

Reproducible demo
No response
Steps to reproduce

Start with a fresh installation.
Patch package.json to use 3.0.0-alpha.0:

  "dependencies": {
    "@docusaurus/core": "3.0.0-alpha.0",
    "@docusaurus/preset-classic": "3.0.0-alpha.0",
    "@mdx-js/react": "^2.0.0",
    "clsx": "^1.2.1",
    "prism-react-renderer": "^2.0.0",
    "react": "^18.0.0",
    "react-dom": "^18.0.0"
  },
  "devDependencies": {
    "@docusaurus/module-type-aliases": "3.0.0-alpha.0"
  },

Run npm install

Expected behavior
Installation should pass without warnings.
 See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility

Your environment

Docusaurus version used: 3.0.0-alpha.0
Environment name and version: Node.js 16.20.0, npm 8.19.4
Operating system and version: MacOS 12.5.1

Self-service

[ ] I'd be willing to fix this bug myself.

Looks like react-json-view will remain in React 17 and forks like https://github.com/YYsuni/react18-json-view begin to appear ... Is it something that will be solved in 3.0.0-alpha.1 ?

Thanks for reporting
Yes we want to fix it, not sure how yet.
Original issue with a good amount of alternatives mentioned: https://github.com/mac-s-g/react-json-view/issues/403


Source code is not available directly from projects

Unable to view the source code from projects directly.

@Abhimanyu14 does it affecting any performance? Library is OSS and you always can look in source code in this repo.

Thanks for responding.
There are no performance issues.
Some libraries like Jetpack Compose have source code available in the IDE itself.
This makes the library source code navigation easier.
Any particular reason for this lib to not have that?
If not, is it possible to do so?
Thanks.


added whack-a-mole game

@madihamallick Great work!. Let me know if you can embed the game to the base design as done in the other games.


"Insert note" to insert frontmatter from template

Please select if your request is either something new or an enhancement

[x] Enhancement of an existing Feature.
[ ] Request of a new feature.

Please select the area your request applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[ ] Workspace - VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup - Dendron's Lookup Command
[ ] Views - Dendron Preview, Tree View, Side Panels in the UI
[x] Schema - Dendron Schemas
[ ] Pod - Data import from / export to Dendron
[ ] Publish - External Site Publish
[ ] Markdown - Markdown features, such as syntax support and features

Is your feature request related to a problem? Please describe
Not a problem, just enhancement.
Describe the solution you'd like
When inserting note, it will be useful to insert the frontmatter also
Describe alternatives you've considered
Obviously, I can use schemas, but (for now) it's too confusing for me. :-(

Adding this to our backlog as a good first task for newcomers

The community has selected this issue as this week's CROP winner. 🎉

Looks like this is complete, can we mark this as closed? @kevinslin @aleksey-rowan

@bpathakota, yeap, this is done. I can confirm that frontmatter is being inserted as well. Note that the insert note command got replaced by the Apply Template command.
@abunavas, could you please check if the new command is working the way you expect?


Error on parsing arguments

The new version of the compiler just have broken part of the parsing of arguments. In the previous version, I had a makefile to compile my application and I was able to use lsc -cb ./src/main.ls -o ./bin and have the expected result. In 1.4, The application tries to identify either -o or --output as files because of its position.
lsc -cb ./src/main.ls -o ./bin will throw Can't find: -o.ls, while lsc -cb -o ./bin ./src/main.ls works fine.

LS 1.4 fixed a regression introducted in 1.3.
See #610


Swift Support

Please add swift support

I have managed to implement this in swift if you would like to take a look at my repo for it. Not all calls have been implemented just the basics.

Oh. Superb! 👍


Create nodes for alias templates and fix alias naming [phab:D702]

Created by zarko at 2016-02-10 00:39:37:
This diff creates abs nodes for alias templates
(template  using X = T). It also fixes
naming for regular aliases, where talias nodes were
being generated that had names that disagreed with
what NodeIdForDecl was expecting.
Type aliases bind together nominal and structural names.
This means that any semantic node for a given
using Foo = int is indistinguishable from any other
using Foo = int in the graph. If this is not desirable,
we will possibly need to make changes to the schema.
This addresses #977.

jdennett wrote at 2016-02-10 00:50:35:
I'm fine with saying that any two aliases from the same type to the same name are "the same alias".

jdennett accepted this revision at 2016-02-10 00:51:32

zarko closed via commit 06fb296a66e45d907285a92289e38be8d80f0310 at 2016-02-10 01:13:16


YoutubeDL Not Find Config File

Checklist

[x] I'm asking a question
[x] I've looked through the README and FAQ for similar questions
[ ] I've searched the bugtracker for similar questions including closed ones

Question

WRITE QUESTION HERE
YoutubeDL Not Find Config File So He place Music and Videos in C/Users i dont know why

nobody can help me ?


Add className prop

Right now, styling the editor container requires knowing react-monaco-editor-container as the magic class name for the element. This makes it difficult for someone to apply styles to the container in a clean and modular way.
Request

Expose an optional className prop
When defined, the emitted <div /> includes both react-monaco-editor-container ${this.props.className}

Can't you just wrap the element in another div with a class?
Are there other components that expose className? If so, I'm happy to accept a PR.

Can't you just wrap the element in another div with a class?

I'll try that. My team started exposing the prop when intermediate container elements made sizing difficult, for a variety of reasons.

That worked wonders.


Finding fragments residing in node_modules

(I copied this question from https://github.com/jimkyndemeyer/js-graphql-intellij-plugin/issues/74 as that one was closed, and it probably wasn't a good place for a new question any way).
I'm using and including fragments from a separate package residing in node_modules. Is there a way to tell the plugin to scan for fragments in that package as well, so I can get completions/no not found-errors etc?
I guess it'd mean I'd need to be able to set multiple paths for fragment scanning, as well as make the plugin scan .js.flow-files in addition to .js files, as all the .js-files will have had their actual fragment definitions removed, but the .js.flow-files won't have.
Thanks in advance, and a big thank you for this plugin + the Relay Modern support. It's very pleasant to work with! :)

This actually seems to work already if you unmark the specific package folder in node_modules for exclusion. I'll go ahead and close this one.


ServiceWorkerRegistration.update() is unclear when uninstalling flag set

Step 2 of update() says:

If registration's uninstalling flag is set, abort these steps.

Clearly the intention is to stop immediately.  This is a promise-returning function, though.  I assume we want to reject the promise here.
What error should we reject with?  InvalidStateError?  TypeError?

This has long been in my TODO list since the return type was changed. Thanks for reminding!


why use new in this part rather than smart pointer?

because transport::Participant need a raw pointer in constructor ？

We'd better paste the code instead of the picture. Seems the problem solved


Wrong sbt resolution does not include minor and artifacts fail to download

Just letting you know that I had to use the following:
libraryDependencies += "org.scalameta" % "semanticdb-scalac-core_2.13.4" % "4.4.6",

Instead of:
libraryDependencies += "org.scalameta" %% "semanticdb-scalac-core" % "4.4.6",

For the artifacts to be downloaded and my build proceed.

Thank you for reporting! The semanticdb-scalac-core artifact is cross-published against the compiler version instead of the library version. The standard way to depend on this artifact is to use this sbt syntax
libraryDependencies += "org.scalameta"  "semanticdb-scalac-core" % "4.4.6" cross CrossVersion.full

@olafurpg  , thanks for your reply and work!
It might be relevant to say that this is not available for 2.13.4, which is the version supported by the latest Scala Native.
I was able to compile this locally from the 2.13.3 with zero modifications and it worked out of the box for 2.13.4. You might want to publish this...
Feel free to close this issue.

We do publish for 2.13.4, but we don't yet publish for Scala Native, which might be the issue here.


Typo "**Services)"→"Services)"

https://docs.microsoft.com/en-us/azure/azure-sql/migration-guides/virtual-machines/sql-server-availability-group-to-sql-on-azure-vm
#PingMSFTDocs

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change. @rahugup

@hyoshioka0128 - thanks for catching this.


Expose liberty's support for generating a keyStore / trustStore from pem certs

In #58 we add support for handing the IBM FHIR Server a keystore / truststore.
However, its kind of a pain to create those and upload them to kubernetes secrets.
What might be nice is to expose Liberty's support for generating keystores by either:
A. mounting a secret that has tls.key, tls.crt, and ca.crt to TLS_DIR (/etc/x509/certs/); or
B. setting SEC_IMPORT_K8S_CERTS to true so that the .crt files under /var/run/secrets/kubernetes.io/serviceaccount will be imported into the truststore file
The only documentation I've found for these features is at https://github.com/OpenLiberty/ci.docker/blob/master/SECURITY.md#providing-custom-certificates-20003
What would be nice is if we could easily support establishing TLS between the IBM FHIR Server and a postgresql server from its subchart (and keycloak too?).

As a single datapoint, on IBM Cloud Kubernetes Service (IKS), the cluster cert also uses keys tls.key and tls.crt.
Not clear if that is universal in kubernetes or not.
The bitnami postgresql subchart uses cert.crt, cert.key, and ca.crt instead.

To add a datapoint: tls.key and tls.cert are also used by secrets of type TLS (https://kubernetes.io/docs/concepts/configuration/secret/#tls-secrets).
I generelly think if TLS between many services is desirable, mTLS via a service mesh may be less complex to setup.


Skip RSA key validation

That wasn't a real issue, I just forgot to upgrade cryptography locally.

That wasn't a real issue, I just forgot to upgrade cryptography locally.


code-completion suggestions need context

I've posted about this before and it was ignored (https://github.com/microsoft/vscode/issues/123356)
Code completion is offering suggestions that are out of context...
here is an example:

I'm importing a module and typing in the path, but getting suggestions for snippet creators that make no sense.
This makes these suggestions useless and actually annoying.
Suggestion: VSCode should be passing some kind of context on to the plugins to ensure suggestions are valid.
Note: I'm not familiar with how VSCode interacts with plugins.

Suggestion: VSCode should be passing some kind of context on to the plugins to ensure suggestions are valid.

Snippets aren't dynamically computed by extensions but retrieved from static files and always shown without context.

Unfortunately, we cannot use token information to further limit static snippets.
You can control/disable this with the editor.snippetSuggestions setting.

J


Make ConjunctionDISI package-private and add ConjunctionUtils factory class

ConjunctionDISI is really an internal implementation of DocIdSetIterator,
and would ideally be package-private.  However, it is used in a few
other places:

directly in ConjunctionSpans
as a utility in the facet and join modules

This commit refactors Spans to use their own copy of ConjunctionDISI,
and adds a public helper class ConjunctionUtils that allows easy
intersection of iterators for use by other modules.  This means that
ConjunctionDISI itself can become package-private.  It also removes
a reference to Spans from core classes, which will make it easier to
migrate Spans to the queries module.

+1 to this change -- looks great!  But:

refactors Spans to use their own copy of ConjunctionDISI

it looks like you didn't have to do this (fork / make a full copy of ConjunctionDISI for spans)?  It looks like spans just also use the new (public) ConjunctionUtils, which provide (safe) public access to the package-private ConjunctionDISI?

It looks like spans just also use the new (public) ConjunctionUtils, which provide (safe) public access to the package-private ConjunctionDISI?

Unfortunately no, if we do this then Spans don't use two-phase iteration any more.  What might work instead though would be to make ConjunctionDISI.createConjunction(List<DocIdSetIterator>,List<TwoPhaseIterator>) public through ConjunctionUtils - I'll give that a try and report back!

We need to add three more methods to ConjunctionUtils but it does mean that we can remove the specialised Spans class, so I think it's a win.  It should also be possible to re-use these for intervals as well, which have a similar specialised implementation.

I've pushed the intervals change as well, turns out it's very simple and allows us to remove more duplication.


Add SigmaDimensions

FYI @Sigma88
min_version for ModuleManager is from this comment.
@Sigma88 is there a newer minimum or a minimum required version for Kopernicus?
Since there is no KSP 1.1.x compatible version at the moment, this will currently generate the most recent version compatible with KSP 1.0.5.
Output from ckan show on my test KSP 1.0.5 install.
D:\Users\Dwayne\Projects\CKAN\NetKAN [feature/sigma_dimensions]> ckan show SigmaDimensions --ksp test-<IP_ADDRESS>8
Sigma Dimensions: A universal rescale mod

Module info:
- version:      0.4.3
- authors:      Sigma88
- status:       development
- license:      restricted

Depends:
- ModuleManager, min: 2.6.16
- Kopernicus

Provides:
- SigmaDimensions

Resources:
- homepage: http://forum.kerbalspaceprogram.com/index.php?/topic/126548-/
- repository: https://github.com/Sigma88/Sigma-Dimensions

Filename: 62E1DDD0-SigmaDimensions-0.4.3.zip

Showing 72 installed files:
- GameData/Sigma
- GameData/Sigma/Dimensions
- GameData/Sigma/Dimensions/Configs
- GameData/Sigma/Dimensions/Configs/Bodies
- GameData/Sigma/Dimensions/Configs/Bodies/AllowUserDefined.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Bop.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Dres.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Duna.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Duna_atmo.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Eeloo.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Eve.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Eve_atmo.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Gilly.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Ike.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Jool.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Jool_atmo.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Kerbin.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Kerbin_atmo.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Bop.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Dres.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Duna.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Eeloo.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Eve.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Gilly.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Ike.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Jool.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Kerbin.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Laythe.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Minmus.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Moho.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Mun.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Pol.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Sun.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Tylo.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/KittopiaExports/Vall.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Laythe.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Laythe_atmo.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Minmus.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Moho.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Mun.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Pol.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Sun.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Sun_atmo.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Tylo.cfg
- GameData/Sigma/Dimensions/Configs/Bodies/Vall.cfg
- GameData/Sigma/Dimensions/Configs/General
- GameData/Sigma/Dimensions/Configs/General/caseSensitivityFix.cfg
- GameData/Sigma/Dimensions/Configs/General/diameterFix.cfg
- GameData/Sigma/Dimensions/Configs/General/gravityFix.cfg
- GameData/Sigma/Dimensions/Configs/General/groundTextures.cfg
- GameData/Sigma/Dimensions/Configs/General/massFix.cfg
- GameData/Sigma/Dimensions/Configs/General/removeDuplicates.cfg
- GameData/Sigma/Dimensions/Configs/General/removePQSMods.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension
- GameData/Sigma/Dimensions/Configs/ReDimension/advancedSettings.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/applySettings.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/atmoScale.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/groundScatters.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/newCacheFiles.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/physicsModifier.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/rescaleSCANsat.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/resizeClouds.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/resizeKonstructs.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/resizePQSMods.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/setAsteroids.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/setDimensions.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/setKSCSwitcher.cfg
- GameData/Sigma/Dimensions/Configs/ReDimension/setPQSlevels.cfg
- GameData/Sigma/Dimensions/Configs/Sigma-Dimensions.version
- GameData/Sigma/Dimensions/README.txt
- GameData/Sigma/Dimensions/Settings.cfg

current release is for KSP 1.0.5 and Kopernicus 0.6.3
I'm working on an update that will bring it up-to-speed with KSP 1.1.2 and Kopernicus 1.0.3

@Sigma88 Thanks a lot!
I've updated the metadata with some overrides so that:

Version 0.4.3 will depend on ModuleManager>=2.6.19 and Kopernicus>=0.6.3
Versions >0.4.3 will depend on ModuleManager>=2.6.23 (the version which added the & operator according to the changelog) and Kopernicus>=1.0.3.

@plague006 This should be good to go.

Rather than coding the depends for the next version into the override can we put them in the main body and just use an override for 0.4.3? Makes maintenance easier.

@plague006 Done.

:+1:

out of curiosity, does CKAN gather any information about downloads?
like, which planet packs are downloaded the most alongside SD and stuff like that?

No user tracking at the moment nor in the near future. It would be "neat" but we'd probably constantly be accused of spying on people.

It's been proposed as an opt-in mechanism KSP-CKAN/CKAN#1566 and I actually like the idea. It's similar to what pkgstats does on Arch Linux.

Honestly the moment you use an internet connection to download stuff you should expect that your download will be registered. KerbalStuff did it, spacedock does it, and github does that as well. But I know what you mean about people complaining, this choice is probably for the best.


Logging in

I am trying to log in but it does not recognise my credentials, below is the message I receive:

I am not sure, for the key I use the key provided by IG, for identifier I tried both my live account id and an id that I specifically set for my demo account. Similarly I tried both passwords and still I am not able to connect.

I will close this issue, the problem is with the demo account.


Sample code for Watson and Facebook Integration

Hi I tried to no avail to find up-to-date documentation about integrating Facebook and Watson Assistant. Most links direct me here but it's only for Slack. Is there anywhere with such documentations? Thanks!

If you look at the base botkit repo you can see sample code for all of the things botkit can connect to. We've simply written a middleware that relies on the base botkit repo.
That being said, we have a built in, hosted, connector to facebook in the integrations tab of the Watson Assistant product.

The botkit documentation links to this Github page for IBM middleware. I'm still trying to integrate with it but I'm having some trouble with the packages now. These seems to be 2 packages Link 1 and Link 2 and I'm still trying both and am not sure which to use.
With regards to the Facebook Integrations with Watson, there is no native support for Facebook Handoff Protocol. This means that in usage, when I attempt to hand off to a live agent in Facebook inbox and start chatting through there, to the end user it seems like the handoff is already completed but every single message you type still gets routed to the bot even while the human is replying which is absurd and hence I'm trying to build a middleware to get around this issue.
Hope you can advice more on this. Thanks!

The second link is just the standard ibm-watson SDK, not related to botkit. Bokit likely pulls it in I can't remember exactly, but you probably want to focus on the first link.
Its been a long time since I've looked into this, and botkit has since been acquired by microsoft and updated a lot of their repo, but I think it should be this:

Start with base botkit repo
Pull in Watson Assistant middleware, which can be seen in the botkit core readme
Pull in the botkit Facebook adapter https://github.com/howdyai/botkit/tree/master/packages/botbuilder-adapter-facebook

The second link is just the standard ibm-watson SDK, not related to botkit. Botkit likely pulls it in I can't remember exactly, but you probably want to focus on the first link.

It doesn't, the only way Botkit relates to ibm-watson is through this middleware.


Plugin code contribution guidelines file.

Description

Add guidelines for plugin code contribution.

Fixes appsmithorg/appsmith #2323
Type of change

This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Hi @mohanarpit  I have addressed the review comments. Can you please review again ?


added kubernetes deployment spec

These changes won't affect EventUI currently running in PPE.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #89   +/-   ##
=======================================
  Coverage   52.24%   52.24%
=======================================
  Files          96       96
  Lines        1405     1405
=======================================
  Hits          734      734
  Misses        671      671

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 e851c3f...9976f06. Read the comment docs.

Coverage remained the same at 48.746% when pulling 9976f061d3a1713469116b50246fc6eba8d02834 on k8s_deployment into e851c3fa71ca37eca4ed290aea15ab46baed749d on master.


task(importAccount): Store Recovery seed in Warp/give user option to delete

Issue:
Like the title says, we want to store the Users recovery phrase into warp, and give them the option in settings to clear that phrase from Warp

This can be done by adding config.save_phrase = true to  https://github.com/Satellite-im/Uplink/blob/3328f3ab0f641584335691b1390442340d37a0f6/common/src/warp_runner/mod.rs#L383 and add config.save_phrase = true;  and then the phrase can be access from tesseract under the name "mnemonic". Note that if an account created or imported without that flag set, it will not be set in tesseract and would require the user to have the phrase at hand.


Crash when changing permissions in iOS Settings app

If I set a closure as below, then open the iOS Settings app and change the permission there, the app will crash
permission.request { status in     switch status {     case .Authorized:    print("authorized")     case .Denied:        print("denied")     case .Disabled:      print("disabled")     case .NotDetermined: print("not determined")     } }

You have to use a real device, not the simulator for this :/
https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/iOS_Simulator_Guide/TestingontheiOSSimulator/TestingontheiOSSimulator.html

I did get this crash on both the simulator and testing on device

After install the app on a device, click "Stop the running scheme or application" in Xcode and then reopen your app. Unfortunately, you won't have access to the log messages...

Got it. Thanks a lot!

@mathiasgithub @delba  Still crash, I am doubtful that it's the iOS bug.

@KittenYang is right. Its crashing on device, even stopping the app on Xcode and reopening.

This is what I get on device logs:
Quitting application (APP BUNDLE ID HERE) in response to privacy settings change
Its not a crash, but a SIGKILL
Its not "Permission" fault at all.


Remove settings option

Remove settings option

I will fix it, frend

i will try to fix it from jwoc 2019

Proceed @satyamroy001


Deprecation warnings when building Cesium for Unreal

I'm seeing a couple deprecation warnings when building Cesium for Unreal

1>C:...\Plugins\cesium-unreal\Source\CesiumEditor\Private\CesiumIonTokenTroubleshooting.cpp(326): warning C4996: 'FEditorStyle::GetBrush': FEditorStyle::GetBrush() is deprecated, use FAppStyle::GetBrush() instead. Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.

1>C:...\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumTextureUtility.cpp(362): warning C4996: 'RHICreateTexture2D': FRHITexture2D is deprecated, please use RHICreateTexture(const FRHITextureCreateDesc&). Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.

Which version of Unreal is this for?

Unreal Engine 5.2


Avoid writing manifest to disk for unit tests

In #617 we added tests to verify that the manifest resources that we were emitting were suffixed with v0. We don't like hitting the disk for unit tests like this so we want to figure out a way that we can intercept actual I/O from the Utf8JsonWriter and write to memory instead and then read that data back for our assertions.

Did you do this one @mitchdenny ?

Yes


How do you setup this package after I downloaded from bower in Angular?

It would be nice if you could write this on the readme file.

Hi @klaoha06,
You can take a look at the usage or the demo code.
Basically, you need:

Include the angular-timeago script (e.g. https://github.com/yaru22/angular-timeago/blob/master/demo/index.html#L41)
Specify the dependency on angular-timeago module (e.g. https://github.com/yaru22/angular-timeago/blob/master/demo/main.js#L4-L6)
Create a date object in the controller (e.g. https://github.com/yaru22/angular-timeago/blob/master/demo/main.js#L11)
Use it in the Angular template like {{ dateObject | timeAgo}} (https://github.com/yaru22/angular-timeago/blob/master/demo/index.html#L33)

Hope this helped.


CI: Measure coverage of benchmark.py.

Coverage of asv/benchmark.py isn't measured as the script is executed in a subprocess from a virtual environment -- without sitecustomize.py or .pth hook installed. See http://pytest-cov.readthedocs.io/en/latest/readme.html#limitations and https://coverage.readthedocs.io/en/latest/subprocess.html.
pytest-coverage points to pytest-cover, which in turn claims to have been merged into  pytest-cov.

Coverage increased (+14.09%) to 72.331% when pulling 6c18d4ab8890e40f1a94919efbc3ddefe4bff076 on wrwrwr:benchmark-coverage into aa11c73c6cc478931ba9fe3824aac1e9e2637e3a on spacetelescope:master.

Coverage increased (+14.09%) to 72.331% when pulling 5e92243984119c673d734e2224246640be676b2d on wrwrwr:benchmark-coverage into aa11c73c6cc478931ba9fe3824aac1e9e2637e3a on spacetelescope:master.


FIX DerivativesDataSink warning when it has multiple source files

My contribution to fix #572

Hello @HippocampusGirl, Thank you for updating!

In the file niworkflows/interfaces/bids.py:

Line 5:1: F401 'collections.abc.Sequence' imported but unused

To test for issues locally, pip install flake8 and then run flake8 niworkflows.

I uploaded a test just now. I have never used pytest parameterizations before, so I would appreciate your feedback on that :-)

@HippocampusGirl have you added your name to fMRIPrep's contributors file?
I think this contribution deserves that you add your name there, so feel invited to do so. For more info: https://www.nipreps.org/community/

Thank you @oesteban! I would be honored to add my name to the list. How does it work? Should I submit a separate pull request?

Yes, please send a PR to https://github.com/nipreps/fmriprep modifying the file https://github.com/nipreps/fmriprep/blob/master/.maint/contributors.json
The ordering of contributors is alphabetical there.

Would it be possible to also merge this on maint/1.3.x, or would that be a separate pull request?

We can cherry pick it in, if we haven't already. Or you can do it and submit a PR.


build: allow getting version from VERSION file

When no git environment is available, the SPIRV-Tools version cannot be computer correctly.
This was possible before with the CHANGES file.
The reason to move away from the CHANGES file was to have 1 source or truth (the git history), and prevent mistakes as the PR to update the CHANGES file had to be done on the commit we release.
Moving to a git-only method was fine, as long as users were cloning the git repo. In the case of a github release, this is bad, as the git history is not present in the zip files.
To solve the problem, the idea is to allow a VERSION file to be present at the root of the project.
This file is by default not present. This file will be added on the release branches, allowing the GitHub releases to correctly report their version.
For users relying on SPIRV-Tools, but having no history, the creation of a VERSION file (if not using the releases) can be an alternative.

The reason to move away from the CHANGES file was to have 1 source or truth

Before we had 1 source of truth. With this change we will have 2. I'm also wondering if we are still making too many assumption about how people will get the source code. At first I was okay with the change because I assumed everybody would have the git tags available. As we have been going through this, I realize that is not true. The problem is more than just the releases. People have to checkout spirv-tools a particular way to make sure they have the tags. They cannot clone with --no-tags or --depth or any of other option that truncates the history.
I am starting to wonder if the extra burden on our users is worth it. How often did new commits get added between the release candidate was chosen and the testing was finished?

I am starting to wonder if the extra burden on our users is worth it. How often did new commits get added between the release candidate was chosen and the testing was finished?

Yeah, I agree this is not going as planned initially... But for instance, we had an issue during the last release IIRC (changes file updated, but tests not done yet, etc).

Before we had 1 source of truth. With this change we will have 2
The real and unique version number is the sha1 (which we show when we can).
The rest is just something arbitrary and our major/minor doesn't reflect the kind of change in the release.
What we could say is: we do it using the CHANGES file, don't care if the major.minor version is wrong for a couple commits, as it doesn't mean anything strong.
Don't time the CHANGES PR, just update it, start the release process, and that's it.

People have to checkout spirv-tools a particular way
Not to build it. But if they want to make a "release", then I find that reasonable to require some additional constraints.

The idea here was to provide a "supported" way to link the git history to the build, with no git history.

الو


Kernal getting died after every few minutes with simple code of execution

Describe the bug
A clear and concise description of what the bug is.
While running basic Python CPU code, the kernel dies and due to this not able to work here.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Hi, thank you for reporting the issue.

While running basic Python CPU code

Do you mind sharing the code in this issue? We need it to find the root cause.

@itsmerajat
Thank you for reporting this issue. I've tried the CPU mode and I assume the problem has been resolved. If you're still experiencing any difficulties, please feel free to reopen the issue. I'm here to help and want to ensure you have a positive experience. Have a great day!


[hub] default environment variables for development

Closing and including defaults as part of virtual funding work.


Feature Request: Google Flogger

Sorry if this is the wrong place for feature requests.
Lombok is great, and the concept of @Log and other loggers is very good. However, out of the many logger options, it doesn't include the best logger: Flogger. Compare the other loggers:

Log, Log4j, and CommonsLog have no support for parameters at all
Log4j2, Slf4j, and XSlf4j use {} instead of %s. This can be confusing when you have String.format() statements in the same file.
JBossLog isn't Flogger

Flogger is very fast (including optimized parameterized logging) and includes features like:
// Log 1 in 100 messages to avoid spamming the logs.
logger.atInfo().every(100).log("My message", args);
// Log at most once every 5 seconds.
logger.atInfo().atMostEvery(5, SECONDS).log("My message", args);
// This obviates the need to create exceptions just to see the stack
logger.atInfo().withStackTrace(LARGE).log("Message");

Thanks for consideration.

I didn't realize that was the reasoning behind the log annotations. I thought it was to reduce boilerplate.
Are you certain the stack trace call is expensive? I ask because everything else in Flogger is highly optimized, and the main two operations are a single, cached reflective Class.forName() call, and a Throwable.getStackTrace() call, which should be quicker than the expensive Thread.getStackTrace.
I would definitely use it if it were added to Lombok, as I have used it in other projects. I think other users might enjoy it, too. :)

Are you certain the stack trace call is expensive?

I can't speak for him, but I'm sure, it's relatively expensive. It'd very bad for performance when done for every log line, but it hardly matters when done once per class. I guess, it can (and will) be optimized using JEP 259, but I'd bet, hardly anybody will notice.


aix: don't EISDIR on read from directory fd

Remove the artificial EISDIR that was generated when trying to
uv_fs_read() from a file descriptor that refers to a directory.
We don't do that on the BSDs either (where reading from a directory
is allowed) and it introduces an extra stat() call for every read.
Refs: https://github.com/libuv/libuv/pull/2023#issuecomment-427759265

I couldn't find tests that check for the presence/absence of EISDIR. If the CI run turns up green, I'll see about adding some.

I tried to implement a test for the same in https://github.com/libuv/libuv/pull/2023. Perhaps we could use that?

Landed in https://github.com/libuv/libuv/commit/25a3894c8d59fada12253d3cb1befd14e18ecd75. Thanks Ben!

Thanks!


[ITensors] [BUG] timeit_debug_enabled not defined

Description of bug
The @timeit_debug decorator from TimerOutputs does not to seem to function properly as timeit_debug_enabled is not defined in ITensors. See also screenshot of README from TimerOutputs.

Minimal runnable code
using Pkg
Pkg.add("TimerOutputs")

using ITensors, ITensorMPS, TimerOutputs
TimerOutputs.enable_debug_timings(ITensors)
const timer = TimerOutput()

# Build MPO
J = 4.0
h = 1.0
L = 15
ampo = AutoMPO()
for j in 1:(L - 1)
  add!(ampo, -J, "Sz", j, "Sz", j + 1)
  add!(ampo, -h, "Sx", j)
end
add!(ampo, -h, "Sx", L)
sites = siteinds("S=1/2", L)
ham = MPO(ampo, sites)

# Do DMRG
psi0 = MPS(sites, "Up")
nsweeps = 20
maxdim = 15
cutoff = 0

@timeit_debug timer "dmrg" energy, _ = dmrg(ham, psi0;
                 nsweeps=nsweeps,
                 maxdim=maxdim,
                 mindim=maxdim,
                 cutoff=cutoff,
                 outputlevel=0)
println("Run $i: $energy")
println(timer)

Output of minimal runnable code
root@8506b93efb68:/opt/project/examples# julia tmp.jl
   Resolving package versions...
  No Changes to `~/.julia/environments/v1.10/Project.toml`
  No Changes to `~/.julia/environments/v1.10/Manifest.toml`
ERROR: LoadError: UndefVarError: `timeit_debug_enabled` not defined
Stacktrace:
 [1] enable_debug_timings(m::Module)
   @ TimerOutputs ~/.julia/packages/TimerOutputs/Lw5SP/src/TimerOutput.jl:187
 [2] top-level scope
   @ /opt/project/examples/tmp.jl:5
in expression starting at /opt/project/examples/tmp.jl:5
root@8506b93efb68:/opt/project/examples#

Version information

Output from versioninfo():

julia> versioninfo()
Julia Version 1.10.5
Commit 6f3fdf7b362 (2024-08-27 14:19 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: Linux (aarch64-linux-gnu)
  CPU: 8 × unknown
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-15.0.7 (ORCJIT, generic)
Threads: 1 default, 0 interactive, 1 GC (on 8 virtual cores)
Environment:
  JULIA_GPG = 3673DF529D9049477F76B37566E3C7DC03D6E495
  JULIA_VERSION = 1.10.5
  JULIA_PATH = /usr/local/julia

Output from using Pkg; Pkg.status("ITensors"):

julia> using Pkg; Pkg.status("ITensors")
Status `~/.julia/environments/v1.10/Project.toml`
  [9136182c] ITensors v0.6.17

I don't think we have many timers inside the codebase right now anyway, what were you hoping to time?
As an alternative, I would recommend using a profiler.

I wanted to time dmrg, i.e., how much time dmrg spends in the subroutines, e.g., truncating, eigenvalue solve, etc. You do use the timeit_debug decorators, but I couldn't find tests for it. Did you test it?

I don't remember testing it, I haven't used TimerOutputs in a long time, we were mostly using it in the codebase for debugging some performance issues early on when developing the package. Probably we should remove it at this point, it isn't really meant for external users.

I'll keep this issue open as a reminder to remove TimerOutputs from the codebase.
@MazenAli to summarize, I would recommend using a profiler instead, or dev'ing the package and adding your own timers with TimerOutputs if you prefer to use TimerOutputs.


Long text doesn't wrap but widens the editor

When you type long text in an editor, for example holding down a key until it fills a couple of lines of text, at first the text will wrap correctly to the next line. But when you toggle the HTML-mode on and off, you'll see the editor window expands to fit all of the text on a single line.
Usually that won't happen a lot, but when the editor is re-opened with saved data from before already in it, it opens with all that text on a single line as well. This will happen for example with long Google Drive links.
The part in blue is the highlighted element in Chrome's developer tools. It shows the size the editor should be, but as you can see it is wider and goes on beneath the other editor next to it. If the text is long enough, I can even see it go off screen on the right.
Edit Autogrow is not enabled.

Browser: Chrome 54
OS: Windows 10

That's a WYSIWYG: if it's broken in the editor, it's broken in your website.
You should add something like word-wrap:break-word;

I'm sorry, but I don't get your answer. If my trumbowyg editor is set to have a width of 500 pixels and I type or paste a very long string (not with seperate words, so like a link) it wraps correctly, but if I load the editor with that string already as it's value, trumbowyg does not wrap but becomes wider. I think this is a bug, right?

Maybe it's a bug, but if it is, it is a CSS bug, so it's not on my end. Maybe your backend change something or your CSS is different or something.
I can't help you more than that, because it's contextual, not generic.


seekTo() is not an function

Describe the bug
While using setTimeStamp for any time amount I get:
"[   2729922] [b2802_GTAProce]        CrBrowserMain/ Uncaught TypeError: this.yPlayer.seekTo is not a function (@xsound/html/scripts/SoundPlayer.js:320)"
and also
"[   2730032] [b2802_GTAProce]        CrBrowserMain/ Error with Permissions-Policy header: Unrecognized feature: 'ch-ua-form-factor'. (:0)" when I open log file.
To Reproduce
Steps to reproduce the behavior:
xsound = exports.xsound
xsound:PlayUrl("localCar", url, 0.3, true)
xsound:setTimeStamp("localCar", 30)
Expected behavior
Seek to timestamp after playing
Screenshots

Additional context
I saw the #38 issue and I have ensured that I am using xsound-1.4.3
I also tried to research on the YouTube iframe and found this:
player.seekTo(seconds:Number, allowSeekAhead:Boolean):Void
So I tried to edit SoundPlayer.js to be:
this.yPlayer.seekTo(time, true);
but that didn't change the error.

After testing, it seems this is just an issue of the player not being loaded before the set duration is called right way. Currently trying to figure out a good way to wait until the player has fully loaded...

After testing, it seems this is just an issue of the player not being loaded before the set duration is called right way. Currently trying to figure out a good way to wait until the player has fully loaded...

Hey simply use event
onPlayStart("localCar", function()      setTimeStamp("localCar", 30) end)


Web Vital Metrics for Single Page Applications

In React Single page Application(SPA), First Input Delay and Largest Contentful Paint are only measured once on Initial Load. Additionally, Cumulative Layout Shift does not reset to 0 throughout the session. This means CLS could reach to very high value , if user continues to navigate though logical pages like homepage -> search -> Product Listing -> Product Page -> Basket -> Checkout and so on.
Based on current implementation, pageshow event resets CLS to 0 and it also captures FID and LCP for subsequent page loads.
In React Single Page Application, Could we consider route change event for the new logical page load and reset CLS to 0. This would also enable us to capture FID and LCP on every logical page of the application.
If Web Vital Metrics would be considered for page ranking, the proposed implementation would give React SPA fair comparison.

Hi there !
Had the same question, the docs need some context for SPAs.
For example, there should be a way to manually reset the values based on a trigger or event.

Hi there !
Had the same question, the docs need some context for SPAs.
For example, there should be a way to manually reset the values based on a trigger or event.

I had wondered whether subsequent page loads with an SPA are even (or should be) considered wrt web-vitals? Either way I'd be interested in seeing some guidance on how to handle web-vital measurement for SPAs

I had wondered whether subsequent page loads with an SPA are even (or should be) considered wrt web-vitals? Either way I'd be interested in seeing some guidance on how to handle web-vital measurement for SPAs

Unfortunately, accounting for SPA route transitions in Core Web Vitals metrics is not currently possible. There are a few primary reasons for this, both technical reasons and practical reasons.
The technical reason is that the Web APIs that measure page load specific Core Web Vitals metrics (LCP and FID) do not re-emit entries after a SPA route change occurs. For FID we could use the same polyfill we use in the case of a bfcache restore, but for LCP we could not, since route changes typically involve loading additional content, and polyfilling LCP to handle those cases would be near impossible (and it would certainly affect performance).
Also, as you point out, in the case of CLS we could reset the metric value to 0 (as we do for a bfcache restore), but this is where the practical issues come into play: what counts as an SPA route change?

Should every call to history.pushState() be considered a route change?
What about history.replaceState()?
What about apps that still use hash URLs for SPAs? (A lot of those still exist.)

While I understand it's probably quite easy for you to determine what should be considered a "logical page load" for your specific app. Making that determination for any given web page is pretty much impossible.
Finally, and perhaps the most challenging of the practical issues is that both Google Chrome and Google Search are creating incentives around these metrics, which means it's absolutely critical that they can't be easily gamed.
If we consider every call to history.pushState() to be a new page load, then developers would have a strong incentive to use that API, even in cases where a user wouldn't consider it a "logical page load".
For example, you could easily imagine some code like this:
// Create a new "page load" any time CLS gets close to crossing the 0.1 threshold...
If (cls > 0.09) {
  history.pushState({...}, document.title, location += '&addendum=1)
}

Similarly, developers might try calling history.pushState() during idle periods to increase the likelihood of LCP and FID being super fast.

Hopefully this helps explain why Core Web Vitals metrics currently don't consider SPA route transitions. But rest assured we are aware of this problem and looking into solutions. Here are two concrete examples:

We plan to update CLS in the near future to be more fair to long-lived pages (including SPAs).
We're working to spec a new version of the history API that might enable us to more accurately identify SPA route changes in the future.

Unfortunately, accounting for SPA route transitions in Core Web Vitals metrics is not currently possible. There are a few primary reasons for this, both technical reasons and practical reasons.
The technical reason is that the Web APIs that measure page load specific Core Web Vitals metrics (LCP and FID) do not re-emit entries after a SPA route change occurs. For FID we could use the same polyfill we use in the case of a bfcache restore, but for LCP we could not, since route changes typically involve loading additional content, and polyfilling LCP to handle those cases would be near impossible (and it would certainly affect performance).
Also, as you point out, in the case of CLS we could reset the metric value to 0 (as we do for a bfcache restore), but this is where the practical issues come into play: what counts as an SPA route change?

Should every call to history.pushState() be considered a route change?
What about history.replaceState()?
What about apps that still use hash URLs for SPAs? (A lot of those still exist.)

While I understand it's probably quite easy for you to determine what should be considered a "logical page load" for your specific app. Making that determination for any given web page is pretty much impossible.
Finally, and perhaps the most challenging of the practical issues is that both Google Chrome and Google Search are creating incentives around these metrics, which means it's absolutely critical that they can't be easily gamed.
If we consider every call to history.pushState() to be a new page load, then developers would have a strong incentive to use that API, even in cases where a user wouldn't consider it a "logical page load".
For example, you could easily imagine some code like this:
// Create a new "page load" any time CLS gets close to crossing the 0.1 threshold...
If (cls > 0.09) {
  history.pushState({...}, document.title, location += '&addendum=1)
}

Similarly, developers might try calling history.pushState() during idle periods to increase the likelihood of LCP and FID being super fast.

Hopefully this helps explain why Core Web Vitals metrics currently don't consider SPA route transitions. But rest assured we are aware of this problem and looking into solutions. Here are two concrete examples:

We plan to update CLS in the near future to be more fair to long-lived pages (including SPAs).
We're working to spec a new version of the history API that might enable us to more accurately identify SPA route changes in the future.

Above is really good explanation on why current route change identification alone is not sufficient for the web vitals that must not be gamed, but at the same time very critical that it's measured accurately, since this would impact page ranking in May 2021 unless the timeline is changed.
It is really great that the team is actively looking for the solution and the official documentations around SPA have started to surface recently.

Above is really good explanation on why current route change identification alone is not sufficient for the web vitals that must not be gamed, but at the same time very critical that it's measured accurately, since this would impact page ranking in May 2021 unless the timeline is changed.
It is really great that the team is actively looking for the solution and the official documentations around SPA have started to surface recently.

Thanks for the response! I would just add that or part of that to the docs for the package.
Even if vitals don't apply, there are natural questions that get asked: "how does this apply to SPAs?" That it would answer cleanly.

Thanks for the response! I would just add that or part of that to the docs for the package.
Even if vitals don't apply, there are natural questions that get asked: "how does this apply to SPAs?" That it would answer cleanly.

FYI: we're working on some content related to SPAs for web.dev/vitals. Once that's published we can link to it from this repo.

Wow, I've spent months pondering why google search console flags so many of our SPA's pages as having poor CLS but lab data (lighthouse) and performance traces (Chrome dev tools) suggest it's very good.
On first load we generally see web-vitals report 0, but with each SPA navigation we see our CLS creep up and up which is why we're seeing such crazy (and unfair?) values; all we're really garnering from CLS is how long somebody is on the site for 🤦🏻♂
I think the layout shifts which are being accumulated across SPA navigations are those caused by a successful network response after navigation because, like many SPAs, on click we show a blank screen with a loading indicator while fetching the data, and then when the data arrives we render it to screen causing a layout -- if the page data being navigated to is already in memory then I've observed the CLS isn't reported, I guess because it's the direct result of a click handler -- https://www.paradeworld.com/
In the meantime we're going to only report the first CLS value reported by web-vitals, but it's terrifying to think google search is going to factor in CLS over the entire session and penalise SPAs offering a decent user experience?

Hey @richardscarrott, see the post on how we plan to update CLS that I mentioned above to address your concern about how the value just keeps increasing the longer the user is  on the page.
As for the the technique of showing a loading spinner and then filling in the content once the network request completes, this may still be counted as layout shifts—if it's the case that elements on the page are shifting as new content is being added.
I'd recommend updating your SPA transition logic to either:

Reserve the required space for all new content (if the dimensions are known) ahead of time, or
hide the content as it's loading (via using dipslay:none, visibility:hidden , or opacity:0) and then only show it once it's all available.

HI @philipwalton thanks for the advice.
I had a bit of a think about your last point re: hiding the content while it's loading and realised I had initially thought the layout shift was merely counting the layout of the new content rendered to screen but of course it's the footer which get's shifted further down the page.
It wasn't immediately obvious to me because we do render the footer offscreen while loading by reserving the height of the viewport while loading; this was done specifically to prevent the footer flashing into view while loading. e.g.

And I guess, although unlikely imo, a user could scroll the footer into view during the loading period and then genuinely experience a layout shift. I guess layout shifts don't discriminate against things inside vs outside the viewport 🤔.
I tested with the footer hidden while loading and as you've suggested this solves the issue so we're seeing almost 0 CLS reports during the page lifecycle.
Of course, we still have the issue of the now rarer layout shifts accumulating over the SPA session but I'll give that article another read and look forward to hearing about improvements on this.

I am just getting started with measuring of CLS and LCP for my React based SPA and came across web vitals module and this thread.
I just played around with the api getCLS and getLCP for my SPA by including a call in one of my pages when the page component is loaded by JS.But I do not see CLS score LCP score printed on console.LCP gets printed once after I interact with the page, like a simple click on the UI. CLS never gets logged at all.

@Midhun-Carousell

LCP gets printed once after I interact with the page, like a simple click on the UI and no amount of route changes prints it again.

This is expected. LCP is only measured at page load, and this is intentional for the reasons I mentioned above. Also, the reason you're seeing LCP logged to the console after you interact is because that is the point when LCP observation stop waiting to see if a larger element gets added to the DOM (we can't log the value before that point).

CLS never gets logged at all.

CLS is only logged when the page is backgrounded or unloaded, so if you switch tabs you should see it logged. You'll also see it logged if you check the preserve log option in devtools and reload the page (it will log CLS for the previous page).
For both LCP and CLS, if you want to log the metric value every time it changes, you can do that with the reportAllChanges option.

Is the conclusion of this particular thread that for SPAs, web-vitals module may not work as expected?

I suppose it depends on what you consider "expected", but based on what you've described, it sounds like it's working exactly as intended.
If you were expecting all the Web Vitals metrics to re-emit after a route change in an SPA, that is not expected to happen.

@richardscarrott thanks for the update.

UPDATE2: So there obviously had to be a reason it was 20px specifically and I think it's because we have a negative margin on a child element in our footer to compensate for some third party styles, so although visually it didn't appear to be in the viewport it's bounding box did creep in by 20px.

This library is just collecting what the underlying Layout Instability API is reporting. If you think this behavior is confusing or wrong, I'd recommend filing an issue on the spec highlighting your use case, and it will be discussed there.

@philipwalton even after the new update I can still see the same page id when I navigate btw pages in a SPA. This means that the cumulative CLS is summed to the initial page.
On a flow: search page => category page all the CLSs have the same id. Is this expected?

Just to add to this conversation, this is an email I had sent previously to the Chrome Speed team in Feb 2021:

I would like to discuss with you two scenarios, both Ajax-related, that have been affecting my website's CLS score.
Scenario 1:
My website / PWA uses Ajax navigation, which keeps Header/Footer and triggers pushState(), every time someone clicks a link to navigate.
When a navigation happens, the URL changes, and the contents (except Header and Footer) are replaced with the new page.
I noticed that the CLS score increases because the Footer is pushed up or down, when the main contents are updated.
This makes CLS increasing "forever", while my users are on my website, causing a Red/Bad CLS on my domain overall.
Any idea how I can go around that, and reset CLS score every time a user navigates?
I'd say that if, within approx. 3~5 seconds:

User clicked a link/button
pushState() happened
An HTTP request happened
DOM was updated

Then CLS could be reset, or at least "ignored".
Scenario 2:
Think about Comments on a Post.
And users can reply to the comments (nested replies).
We do something similar to Facebook/Instagram, where we show the last 3 nested comments, but you can "View X more comments".
Clicking on that button, we do an Ajax request to load the previous 10 comments (between the Parent comment and the already-loaded nested comments).
Since this is an async behavior, it causes CLS issue by default (as it moves the DOM below, to load the new comments above other comments in the page).
No problem, we can reserve some space on the screen as soon as the user clicks. The problem is that the system needs to know in advance how much space those comments (to be loaded) need... otherwise, if we reserve too little space, CLS will be an issue after the comments load; but if we reserve too much space, then there will be empty/blank space in between the new comments and the old comments.
If we reserve some space and then remove the excess after the comments load, CLS is an issue again.
How can we make "Google/CLS" happy here? I hope you understand my position here.
Our users have never complained about "layout shifting" here. It's a user action, but because it's an async request, it causes CLS in Google's view.
I believe a solution similar to the suggested in Scenario 1 might help, although in this case we wouldn't do pushState().

I think I'm mostly curious about whether we should even be tracking web vitals one page transitions within SPAs. When google uses vitals scores, is it accounting for internal navigation within a site, or is it simply comparing the scores from the initial page load of each individual page as an entry point? Clearly, the entry point load is always going to have worse scores than any internal transition, as there is some framework boilerplate that you need on the initial load of a page that won't happen if you transition to that same page after initially entering the app on another page (ie, scores for going directly to example.com/about would be worse than scores computed transitioning to /about after already loading the example.com homepage, right?).
Correct me if I'm wrong, but my understanding is that google measures the vitals on the page from the entry point perspective (ie someone clicks a link from google directly to a page) and thus measuring metrics of internal page transitions are just going to conflate your aggregations to a much more favorable number than what google is actually ranking you for, no?

To provide an update to everyone, we recently published a post on web.dev with answers to common questions about how SPA architectures affect Core Web Vitals: https://web.dev/vitals-spa-faq/
The post includes a section re: what is Google doing to address the SPA issue with some specific plans. Once there's more progress on those proposals I'll update this library to incorporate any changes here.

Please note there is experimental support of this in the soft-navs branch as detailed here: https://developer.chrome.com/blog/soft-navigations-experiment/

I can understand why TTFB, LCP, etc aren't reset on SPA navigations, but I can't figure out why INP stops logging, even with reportAllChanges being set to true. What about the way its calculated makes it stop logging on SPA nav?

I used the web Vitals extension Google browser plugin to observe SPA single page routing switching and found that it can collect changes in CLS and LCP indicators, but calling the onCLS and onLCP methods with web Vitals does not work

Yes we have not released a version of the extension with this experimental branch yet because it is still experimental and subject to change.

Yes we have not released a version of the extension with this experimental branch yet because it is still experimental and subject to change.

I'm very sorry!  I probably didn't express the issue clearly .
I installed the web Vitals plugin in Chrome browser; The name of the plugin is' web vitals extension'
the browser plugin link https://github.com/GoogleChrome/web-vitals-extension
My question is:
The browser plugin can detect SPA router change values, why can't I use web Vitals in the code to obtain these change values .
Examples:
step 1. pageload show metrics

step 2. SPA router change show metrics

The web vitals extension always shows the current URL when the Heads Up Display (HUD) is opened. This has not changed and was always the case. Perhaps we should change this, to make it more obvious it's based on the initial page.
LCP for an SPA is measured across all the soft navigations. However LCP is finalised when a click happens, so normally you wouldn't see an LCP change (assuming you do a click to initiate the soft navigation?). However, if there was an automatic change in SPA route, without an interaction, then yes the LCP would still continue to take the latest one if it is bigger. Chrome will also measure this as a new LCP but report it back based on the initial URL.
The experimental branch, however, "resets" LCP so it is logged on the second and subsequent SPA page even if it is not bigger. So that's why it's different.

Coming here after I realize that INP and CLS are fired on window unload (and after reading web vitals faq)
Just want to add on our specific use case.
The specific issue for our specific use case:

User lands on /foo/bar/*. LCP and FCP are emitted with trackingId as /foo/bar*.
User navigates away with a click, lands on /whatever/:title.
User closes the tab or refreshes the browser, whatever action to trigger INP and CLS metric emission. Now it is emitted with trackingId as /whatever/:title.
If we want to utilize these 4 metrics to calculate our custom scoring system, then we will have conflicting trackingId.

Like many have said, would be great to see them fired as well on route (history?) change, that way we would be able to calculate our custom scoring with the same trackingId / route.

Unfortunately, accounting for SPA route transitions in Core Web Vitals metrics is not currently possible. There are a few primary reasons for this, both technical reasons and practical reasons.
The technical reason is that the Web APIs that measure page load specific Core Web Vitals metrics (LCP and FID) do not re-emit entries after a SPA route change occurs. For FID we could use the same polyfill we use in the case of a bfcache restore, but for LCP we could not, since route changes typically involve loading additional content, and polyfilling LCP to handle those cases would be near impossible (and it would certainly affect performance).
Also, as you point out, in the case of CLS we could reset the metric value to 0 (as we do for a bfcache restore), but this is where the practical issues come into play: what counts as an SPA route change?

Should every call to history.pushState() be considered a route change?
What about history.replaceState()?
What about apps that still use hash URLs for SPAs? (A lot of those still exist.)

While I understand it's probably quite easy for you to determine what should be considered a "logical page load" for your specific app. Making that determination for any given web page is pretty much impossible.
Finally, and perhaps the most challenging of the practical issues is that both Google Chrome and Google Search are creating incentives around these metrics, which means it's absolutely critical that they can't be easily gamed.
If we consider every call to history.pushState() to be a new page load, then developers would have a strong incentive to use that API, even in cases where a user wouldn't consider it a "logical page load".
For example, you could easily imagine some code like this:
// Create a new "page load" any time CLS gets close to crossing the 0.1 threshold...
If (cls > 0.09) {
  history.pushState({...}, document.title, location += '&addendum=1)
}

Similarly, developers might try calling history.pushState() during idle periods to increase the likelihood of LCP and FID being super fast.
Hopefully this helps explain why Core Web Vitals metrics currently don't consider SPA route transitions. But rest assured we are aware of this problem and looking into solutions. Here are two concrete examples:

We plan to update CLS in the near future to be more fair to long-lived pages (including SPAs).
We're working to spec a new version of the history API that might enable us to more accurately identify SPA route changes in the future.

@philipwalton Hi I was wondering is there any update on this? Is there any metrics that is accurate on SPA from the improvements? I'm particulary interested in FID and INP

@philipwalton Hi I was wondering is there any update on this? Is there any metrics that is accurate on SPA from the improvements? I'm particularly interested in FID and INP

This is the most recent update: https://developer.chrome.com/docs/web-platform/soft-navigations-experiment

@philipwalton thanks for you comments here, I understand why web-vitals package or chrome by itself can't identify what is a SPA page transition that should trigger a reset. Having said that, it would be amazing if the web-vitals package itself had an API that can be used when the website owner knows it's a SPA page transition and it's now time to reset cumulative metrics and re-emit FID on this page load.
I hope that makes sense to add to the existing package or create a separate package which will add this support.
Thanks


[BugFix] null date and datetime value for spark load is not consistent

Signed-off-by: xyz<EMAIL_ADDRESS>What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #9496
Problem Summary(Required) ：

For broker/stream load, null value for date and datetime is DefaultValueGenerator<DateValue/TimestampValue>, however, for spark load, it is not so.
So when we create a aggregate table, we first perform broker load, and then perform spark load on the same data
(here assuming the data has null value), and query by select count(*) from table, the result will contain two null value.
In this pr, we let the null date and datetime value for spark load to be consistent with broker/stream load

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test


Support for Bit based micro front-ends

Does Google build packs support building https://github.com/teambit/bit based micro front-ends ? If so can you reference some documentation on the usage ?

It depends. As long as the application source is written in one of the 7 supported languages, you should be able to build using GCP Buildpacks. Curios to know if you tried and what you found.


merge from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 -x 'tests/**/*.mjs' --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp
chore(package): add main from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/*-test.mjs' as in template
chore(package): set $.ava.extensions='mjs' as in template
chore(package): remove unknown value for main ({{main}})

Pull Request Test Coverage Report for Build 2202

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

Totals

Change from base Build 2198:
0.0%

Covered Lines:
361

Relevant Lines:
375

💛  - Coveralls


Fix playback.

WHAT
I am not sure why I was using runBlocking here, assuming I was just testing at
first, and left that in.
WHY
Playback can't block main thread.  Must return immediately.
HOW
Checklist :clipboard:

[ ] Add explicit visibility modifier and explicit return types for public declarations
[ ] Run spotless check
[ ] Run tests
[ ] Update metalava's signature text files

Fixes https://github.com/google/horologist/issues/276


Recent changes to the pharo zero-conf api have broken all pharo builds

One of the failure mechanisms  ... one of many

This build failure implies that the os prereqs for Pharo 4.0 have changed ... consider putting back in the travis zero conf target since I've been assured that it is up-to-date (will find out if it is up-to-date relative to this recent change) ...

don't think this an issue any longer