Implement the header to be a vue component

[ ] Build the breadcrumbs from a list of link objects (current implementation has no navigation back...)
[ ] Same as above, but for the links
[ ] Add :not(first-child):before CSS classes that add a stylized / between the items in the breadcrumbs
[ ] Replace all current usages of the header with this new component

Btw, the vue router hijacks the browser's back button, so hitting back should actually work as you expect, ie, hitting back from the Join screen will correctly load the TournamentPreview and so on. So the breadcrumbs might be nice, but you can probably do without them.

The header has been replaced by the sidebar, which is 100% a reusable compontent!


Why there a suspicious contact IP when i scan this app?

Steps to reproduce
https://www.virustotal.com/gui/file/9b6c1f3d67ec12a6ec219d1647a5ada67f3ff6ee7a9249e08af98917eb821287/relations
Expected behavior
Can you explain it
Actual behavior
Or someone explain it
Mangayomi version
V0.2.0
Device
Android 10
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[x] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated all installed extensions.

suspicious IPs don't mean much...
they could be merely flagged as malicious for simply not complying with anti-piracy laws


API report improvement / enhancement

At the moment API for post service is very limited.
Here's a few things we think its important, specially when using monitors to report.
POS size
To get more accurate and faster results about PoST
k2pow progress status
A simple started / ended would suffice for information
PoST read status
A percentage would be best, even if in reverse 100% --> 0% we can show user how much is left
Thank you all for your hard work

Regarding the service cli, I would like to add a suggestion:
Can the api methods StartSmeshing and StopSmeshing of SmesherService support the 1:n mode?
that's good to support enable/disable  one of POST  in full node.


workaround of AWQ for Turing GPUs

As far as I saw, only mma.sync.aligned.m16n8k16 op requires sm_80. For sm_75, using two mma.sync.aligned.m16n8k8 op can yield the same result.
It may not be optimal for performance but it works at least for who wants try AWQ with Turing GPUs.

example with tesla t4

from vllm import LLM, SamplingParams
from transformers import AutoTokenizer

model_name = "casperhansen/vicuna-7b-v1.5-awq"

llm = LLM(model=model_name, quantization="AWQ")

prompts = [
    "Hello, my name is",
    "The president of the United States is",
    "The capital of France is",
    "The future of AI is",
]
sampling_params = SamplingParams(temperature=0.8, top_p=0.95)

outputs = llm.generate(prompts, sampling_params)

# Print the outputs.
for output in outputs:
    prompt = output.prompt
    generated_text = output.outputs[0].text
    print(f"Prompt: {prompt!r}, Generated text: {generated_text!r}")

# Prompt: 'Hello, my name is', Generated text: " Dustin Nelson and I'm a writer and podcaster based in"
# Prompt: 'The president of the United States is', Generated text: ' elected indirectly through the Electoral College, which is composed of electors from'
# Prompt: 'The capital of France is', Generated text: ' Paris. At the center of Paris, you will find the Seine River. The'
# Prompt: 'The future of AI is', Generated text: ' a topic of much debate and speculation. Alteryx Inspire is'

@twaka Thanks for this work. Would you mind upstreaming this into AutoAWQ as well?

@casper-hansen I'm glad to see it added to autoawq and excellent benchmark results! To be honest, I was not yet familiar enough to find where need to be changed in autoawq codebase ;)

@twaka Hi, Thanks for sharing this walkaround. It works for me using 2 tensor parallism. When i use TP4, it will throw error: Group size should be a multiple of 32 in gemm kernel. And my awq model uses group size 128 and 4bit. Do you have ideas?

@esmeetu I'm happy to hear it works with TP2. Though I don't have environment to run with TP4, I think we can isolate your issue by running TP4 with Ampere GPUs to see if the error persists.

@twaka Yes, it should be a common problem. i opened a new issue about that.
Another question, Does the compution precision using m16n8k8 the same as m16n8k16?

I observed the same output from T4 vs other GPUs. I will see if I have time to measure perplexity before I merge it - I expect it to be the same.
4 vs 2 instructions is obviously going to be slower but it’s still decently fast on T4 to the point of being usable.

It's a bit tricky to test this branch. I had to fork my own branch and merge #1290 to be able to build, and set TORCH_CUDA_ARCH_LIST="7.0" to avoid #1225 but I still find myself with a RuntimeError: CUDA error: device-side assert triggered. (I'm in nvcr.io/nvidia/pytorch:22.12-py3 updated pip and git and uninstalled torch to let vllm install the correct version).
The root cause looks to be an Assertion error with csrc/quantization/awq/gemm_kernels.cu:33: void vllm::awq::gemm_forward_4bit_cuda_m16n128k32 -> Assertion false failed. See the full traceback here.
Has anyone found a reliable way to test this branch on Turing GPUs? Let me know I would gladly appreciate to test the AWQ export of my model with vLLM.

When you merged the PR into your fork, you forgot to merge the updated kernels from this PR @wasertech

It works! I’ve seen a remarkable improvement, going from approximately 39 tokens per second to a speedy 86! What’s even more impressive is that the model size is now less than 4 GB on disk. I’d like to extend a special shoutout to @casper-hansen for consistently steering me in the right direction and to @twaka for making the process of quantization on vLLM much more accessible. Of course, a heartfelt thanks to everyone who made this achievement possible!

@wasertech I am curious that which model do you use? I cannot achieve that speed on my T4. I have 35t/s for 7b-awq model and 7b-FP16 only have 16t/s.

@esmeetu , you’ve certainly doubled your token throughput 😅. I used to use assistant-llama2-7b-chat, but now I’m currently using assistant-llama2-7b-chat-awq , which are both fine-tuned models based on a peft adapter for QLoRA, from Photolens/llama-2-7b-langchain-chat.

@wasertech Yeah, but i meant how did you get 86tokens/s? Might batch size is 2?🫨

I’m using the default batch size, I took the server example code and slightly modified it here to only stream back the output and not the input with it.
I really think the GPU is the biggest difference at play here…

@wasertech Which GPU do you use?

@wasertech Thank you! I'm sorry that I missed that message you sent.😆
RTX titan is super fast.🤩

As I noted in my PR in AutoAWQ, this PR in vLLM enables older GPUs:

RTX 2000-series (+TITAN RTX)
RTX 1600-series
Quadra RTX (5000, 6000, 8000)
Tesla T4

BTW, I've also checked that this PR works for 1 and 2 T4 GPUs. @twaka Thanks for the great work!

@WoosukKwon Thanks, updated.

It's a bit tricky to test this branch. I had to fork my own branch and merge #1290 to be able to build, and set TORCH_CUDA_ARCH_LIST="7.0" to avoid #1225 but I still find myself with a RuntimeError: CUDA error: device-side assert triggered. (I'm in nvcr.io/nvidia/pytorch:22.12-py3 updated pip and git and uninstalled torch to let vllm install the correct version).
The root cause looks to be an Assertion error with csrc/quantization/awq/gemm_kernels.cu:33: void vllm::awq::gemm_forward_4bit_cuda_m16n128k32 -> Assertion false failed. See the full traceback here.
Has anyone found a reliable way to test this branch on Turing GPUs? Let me know I would gladly appreciate to test the AWQ export of my model with vLLM.

i also meet “RuntimeError: CUDA error: device-side assert triggered” How did you solve it?
code：
from vllm import LLM, SamplingParams
prompts = [
"Hello, my name is",
]
sampling_params = SamplingParams(temperature=0.8, top_p=0.95)
llm = LLM(model="/Yi/quantized_model", tensor_parallel_size=1, trust_remote_code=True)
outputs = llm.generate(prompts, sampling_params)
# Print the outputs.
for output in outputs:
prompt = output.prompt
generated_text = output.outputs[0].text
print(f"Prompt: {prompt!r}, Generated text: {generated_text!r}")
log：
RuntimeError: CUDA error: device-side assert triggered
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
 Now that its on main, you should be able to just use any pre-compiled binary.
Anyways, I don't really remeber what I did exactly, but here is the gist:
Using docker I built vLLM and that's all.
DOCKER_BUILDKIT=1 docker build . --target vllm --tag vllm --build-arg max_jobs=24

My mistake was to try to built with the wrong TORCH_CUDA_ARCH_LIST set in the env which prevented to build with the patches in this fork and so it gave me the assertion error.
In any case your issue might not be caused by the same situation. Best to probably open a new issue not tied to a PR merged 3 months ago. Also maybe your model (Yi-34B) doesn't support AWQ quantization atm? See there is so much difference from your case to mine, you should just open a proper issue.

我使用项目（https://github.com/casper-hansen/AutoAWQ）量化yi-34b-chat模型，然后我运行vllm demo也遇到“RuntimeError：CUDA错误：设备端断言触发”。你是怎么解决的？

@mingyangAbc作为@casper-hansen强烈指出： 我只是忘记为我的目标构建 vLLM，一旦我注意到我刚刚为正确的目标重建并且它工作完美。现在它位于 main 上，您应该能够使用任何预编译的二进制文件。
无论如何，我真的不记得我到底做了什么，但要点是：
我使用 docker 构建了 vLLM，仅此而已。
DOCKER_BUILDKIT=1 docker build . --target vllm --tag vllm --build-arg max_jobs=24

我的错误是尝试TORCH_CUDA_ARCH_LIST在环境中使用错误的设置进行构建，这阻止了使用此分支中的补丁进行构建，因此它给了我断言错误。
无论如何，您的问题可能不是由相同的情况引起的。最好打开一个与 3 个月前合并的 PR 无关的新问题。另外，也许您的型号（Yi-34B）不支持 AWQ 量化 atm？看到你的情况和我的情况有很大差异，你应该打开一个适当的问题。

ok, thanks. I will open a new issue.

I use the project(https://github.com/casper-hansen/AutoAWQ) quantification yi-34b-chat model, then i run vllm demo also meet “RuntimeError: CUDA error: device-side assert triggered”. How did you solve it?

@mingyangAbc as @casper-hansen greatly pointed out: I just forgot to build vLLM for my target, once I noticed I just rebuilt for the correct target and it worked flawlessly. Now that it's on main, you should be able to just use any pre-compiled binary.
Anyways, I don't really remember what I did exactly, but here is the gist:
Using docker I built vLLM and that's all.
DOCKER_BUILDKIT=1 docker build . --target vllm --tag vllm --build-arg max_jobs=24

My mistake was to try to built with the wrong TORCH_CUDA_ARCH_LIST set in the env which prevented to build with the patches in this branch and so it gave me the assertion error.
In any case your issue might not be caused by the same situation. Best to probably open a new issue not tied to a PR merged 3 months ago. Also maybe your model (Yi-34B) doesn't support AWQ quantization atm? See there is so much difference from your case to mine, you should just open a proper issue.

ok, thanks. I will open a new issue.

I was just wondering whether support can be extended to Pascal class GPUs such as P100? I'm not sure which intrinsics are missing compared to Turing (if any).

@cduk Unfortunately, your GPU has a compute capability score of 6.0, which is insufficient for AWQ quantization that requires a compute capability of 7.5 or above. The Pascal architecture lacks several key features present in more recent architectures like Turing, such as:

Tensor Cores: Essential for accelerating deep learning workloads.
Enhanced concurrent execution of floating-point and integer operations.
Faster memory support including GDDR6.
These advancements allow newer GPUs to handle more complex and demanding computational tasks efficiently such as quantisation.


Fix typo in entry for Tax Data API #3263

Unkown is now Unknown

[ X ] My submission is formatted according to the guidelines in the contributing guide
[ X ] My addition is ordered alphabetically
[ X ] My submission has a useful description
[ X ] The description does not have more than 100 characters
[ X ] The description does not end with punctuation
[ X ] Each table column is padded with one space on either side
[ X ] I have searched the repository for any relevant issues or pull requests
[ X ] Any category I am creating has the minimum requirement of 3 items
[ X ] All changes have been squashed into a single commit

Hi @jcork4real
Thanks for your contribution ;)
We have some problems with Public APIs, so we won't be able to review/add this improvement right now.
Read this issue for more information, please: https://github.com/public-apis/public-apis/issues/3104


Update the 0.17 upgrade guidelines for refactored helm chart

In https://github.com/keptn/keptn/pull/7678, the Keptn Helm Chart was refactored heavily. So much so, that we will need specific guidelines on how to upgrade to the next released version of Keptn.
Specifically, the helm values file needs to be adjusted by users and that needs to be documented.

I am in the process of creating a separate "Installation" section in the docs that has individual pages for the different topics.  Let me get that done and then we'll do this -- and looks at the whole mess, which I expect needs other work for 0.17.x

Fixed in https://github.com/keptn/keptn.github.io/pull/1286


Implement a use keyword in *.wit

This PR is not ready for review yet but I wanted to open it up to help prepare for the scale of change happening here. This is becoming a very large change, which is somewhat expected, and it's also not done yet! The current state of this PR is:

An AST intermediate format is created to represent use, basically moving a number of arenas into a Document. More-or-less the representation changes here are fairly simple and while they have a lot of knock-on effects it's relatively mechanical.
Support is added to wit-component to encode use statements in a component and additionally decode it. This includes translation of a use-using document into binary and back again as well as printing to the text format.
Support for parsing the text format is not included yet. @fibonacci1729 is working on that in parallel which will encompass pieces such as loading from the filesystem, resolution of a document, etc.
A simple fuzzer has been added to generate documents (in-memory, not text) and then work with them with wit-component. This is what I've primarily been using to develop this PR and there are still a number of outstanding issues.

There are quite a few changes here in this PR but my personal conclusion at least is that *.wit is still early-enough in its development that this scale of PR won't be helped much by breaking it up, mostly requiring a lot of extra work to try to keep everything working in the interim.
My rough plan is to continue fixing fuzz-bugs and working with @fibonacci1729 on the text format this week. We'll merge the text format into here and then ensure there are plenty of tests for use both for wit-parser and for wit-component. At the moment there are no tests other than the fuzzer since the text parser isn't implemented yet.

Ok I talked with Luke about  the remaining major feature here, which is wit-component support for an export interface which uses a type from another export interface. The short version is that the component model binary format doesn't give a way right now to encode this information easily in the types-only mode (and it's a bit wonky in "real"  mode too). The changes to the binary format coming with the introduction of resource types will fix this, however. My current plan is to leave this largely unimplemented where it'll just panic for now within the wit-component phases. This should be ok for now as it's not expected to come up with idiomatic wit for the time being and should be implemened by the time it does come up.
Otherwise in terms of staging for this PR, I think it may actually be reasonable to go ahead and land this. This doesn't break any existing use cases of wit-component and gets the AST in a state which host/guest generators can start updating to. @fibonacci1729's work to get the text parsing will make this all actually usable but should slot in nicely to the wit-parser crate and into the AST structure created here.
@peterhuene or @pchickey I realize this is a very large PR, would one of y'all be willing to review it? If you'd like I'm happy to talk over video about this and walk through the higher-level portions as well.

I'll try to tackle this PR today and will ping you if a chat is necessary.

Thinking about this I am leaning towards merging this as-is and continuing to iterate from here. Thanks again @peterhuene for going through all of this!
I've been talking with Luke and Brian about the design space here and while we may not end up exactly on what's written here I think the refactorings are nevertheless good to have and beneficial. Namely the change in wasm-tools component new to encode types as-we-go rather than all up-front I think will be crucial for any form of used types across interfaces, and that's a large chunk of this refactoring.
The next steps here are:

Finish design work on https://github.com/WebAssembly/component-model/pull/141, namely what use can do, how to write it down, how it relates to packages, and what the binary format looks like
Finish implementing the text parser and resolution in this repository to start adding tests (@fibonacci1729 is working on this)
Implement the binary format specified upstream and refactor how this works on the CLI as I mentioned above

In the meantime I believe @fibonacci1729 is working on parsing/resolution of a single file with use-between-interfaces, so not multi-file yet, and that should open up being able to write interesting tests here.

@alexcrichton That makes sense to me!


Cleanup the Java project gradle configuration

In the Java workshop build.gradle there are still elements for Kotlin configuration.

PR: https://github.com/foobaz42/fp-workshop-jvm/pull/29

Merged.


Material conversion problem

The attached Velociraptor.glb model file (converted from FBX via Sketchfab) does not display the Body_Mat correctly in SceneKit with either GLTF Viewer or our app. The model material is displayed as a mottled gray via SceneKit but it displays correctly in babylonjs.com, gltf-viewer.donmccurdy.com and Gestaltor. Sorry, but I haven't investigated it in any detail to determine what might be the problem.
Velociraptor.glb.zip

Something about the normal map is going very wrong here, but I haven't found the root cause yet.

The tangent frame values are insane in the shader. Probably not an issue with the normal map per se, but instead something to do with the normal/tangent data.

The tangent geometry source is full of zeros, leading to the incoming tangent and bitangent in the fragment shader to be NaNs.

Thanks for looking into this so quickly!

This is at least partially a regression in macOS Sonoma (and I presume iOS 17). The tangents produced by the morphing shader are all 0, leading to the tangent frame used for normal mapping being completely bogus. I've filed this as feedback with Apple (FB13340109).
I've also created a branch to explore possible improvements in our handling of skinning and morphing, but it's hard to know whether the changes there will improve anything until Apple fixes this blocker. In the meantime, perhaps the least invasive change is to disable normal mapping when morph targets are present.

The SceneKit bug indeed seems to be the problem. Using our app I verified that, after loading the model and removing either the normal map or the morpher will fix the lighting problem, of course with a loss of either fidelity or functionality.  I tested it and it's still broken on both macOS 14.2 Beta (23C5030f) and iPadOS 17.2 Beta (21C5029g).

Appreciate the further testing. I'd recommend filing your own feedback with Apple so this gets more visibility. Although it probably won't make the 14.2 GM, it's shallow enough and severe enough that we might see it fixed before the next major versions.

This seems to have been fixed in macOS Sonoma 14.3 Beta (23D5033f). I'll provide additional updates after additional testing.

I went ahead and merged my changes to morph target and skinning attributes as 0dec7e7. Current plan is to cut a release once it's had time to soak and I can test it on iOS 17.3 beta.

Verified on i(Pad)OS 17.3 beta (21D5026f).

Morph target improvements have been incorporated into release 0.5.5. Full resolution of this issue is pending on the GM release of macOS Sonoma 14.3 and iOS 17.3.

Thanks for the update @warrenm.

Now that our fixes have been incorporated and the relevant OS releases are widely available, I don't think there's anything left to do here. This issue will be closed in seven days if no further information or difficulties come to light.

Closing.


Update Kafka client and database library to expose resources and consumer-prefix-group

Addresses DPE-1342.
The kafka_client interface has recently changed with respect to:

optional requirer request of a certain consumer group ([MISC] Adding optional consumer-group-prefix to the set of parameters… by deusebio · Pull Request #44 · canonical/charm-relation-interfaces )

topic resource name is also provided by the provider ([ISSUE-42] Resource name on the provider side by deusebio · Pull Request #43 · canonical/charm-relation-interfaces )

@welpaolo please update your pinning to the versions proposed in https://github.com/canonical/data-platform-libs/pull/49
No need to stuck on old revisions! ;-)


Update hello-cert-trust-validate-pki.md

Corrected typos

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


add i-pendidikan.my dataset

dataset uploaded here
https://huggingface.co/datasets/hlmshkr/i-pendidikan.my


added error msg to SaaS APIs

improved error msg for SaaS create_table and create_index

ok i think the overall problem here is that LanceDB Cloud and LanceDB OSS are different in the API in meaningful ways. We can put a facade but now it means these warnings have to be everywhere. Or it means potentially the user migrating code from OSS will run into errors. Ultimately the question might be whether we optimize for each individual DX separately or optimize for the switchover.

It is to optimize for the switchover - oss users might not pay attention to our cloud API interfaces so when they switch over, such messages will remind them of what's avail in cloud APIs. For cloud users, they prob won't even using those parameters to begin with.


Link to sample spreadsheet is 'access denied'

Hi,
This looks like a great solution! An issue I encountered is that the Google Sheet included in "Copy this sample spreadsheet to your Google Drive" is access denied. Not sure if this is by design to monitor usage or incorrect sharing settings. Would be good to fix the link or explain the access process.
Thanks for sharing this!
Martin

Hi @mhawksey and thank you for the heads-up!👍 The access denied was a mistake left out in the sharing settings; I simply wanted everyone to be viewers so they can copy the file whenever they one to. This has now been fixed, and I'll follow up with adding a few more lines to the documentation later on😃

@ttsukagoshi thanks for the clarification and fix - a little tip, you can avoid File > Make copy by replacing /edit with /copy in the url e.g. https://docs.google.com/spreadsheets/d/1JvO090VcgvF-WwciNnzRb1_nonKJC5QHN73h_CXS1Cw/copy

👀 That makes a huge difference! Thank you again for your comment; I've changed the URL of the sample spreadsheet from ~/editto ~/copy in #53


Insufficient amounts of data

We need more data to compare new entries against, especially now that I'm nearing completion on the new backend which uses PostgreSQL to store entries in.

Is it okay if I use my brute-force program to add every single IP address to the dictionary?


Getting issue when I activate html5 mode on

Hi, I'm getting an issue for routing when I activate the html5 mode on.
Can you please tell me process for the html5 mode on?
Thanks

This sounds like a general support question. Please, use one of the appropriate support channels for these types of questions.
GitHub issues are reserved for bug reports and feature requests.
Thx!


Compilation time is too slow (more than 40s)

Example -> https://github.com/Farkal/test-wundergraph

Seems linked with rustc -> https://github.com/rust-lang/rust/issues/68796

It seems like you could easily half the compilation time by not having a lib.rs and a main.rs in the same crate. I assume this setup results in rustc building the crate twice. Without that a cargo check is from me less then 10 seconds, a cargo build less then 20 seconds when having only a lib.rs. So the right strategy here seems to be having two crates, one for the wundergraph definition, and one for the final binary.

Did you try with main in /bin ? (I did it and don't see any change but perhaps it work for you)
It's still not easy to dev large app :/


URL Redirection to Untrusted Site ('Open Redirect')

Hi Team
I found some open redirects at the lbry.tv,
URL :
https://lbry.tv////bing.com/?www.omise.co/?category=interview&page=1
https://lbry.tv//evil.com/?www.lbry.tv/
https://lbry.tv//evil.com/?www.lbry.tv/*
https://lbry.tv//bing.com/?www.lbry.tv/
Steps to Reproduce
Intercept the below url using Burp Suite & send it to repeater https://lbry.tv/
Use this attack pattern  //bing.com/?www.lbry.tv/ or //evil.com/?www.lbry.tv/*
Now it will redirect to bing.com or evil.com
Request
GET //bing.com/?www.lbry.tv/ HTTP/1.1
Host: lbry.tv
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,/;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: close
Cookie: __cfduid=dfcebb9451351645d50c441b6f88a74c11607278179; _pk_ref.3.42ca=%5B%22%22%2C%22%22%2C1607799009%2C%22https%3A%2F%2Ftemp-mail.org%2Fen%2Fview%2F41f863f2d7079abaa215d8ee9ce3ce97%22%5D; _pk_id.3.42ca=115bf5aca01b5766.1607278196.10.1607799350.1607796523.; auth_token=Gn61nFeCF98bdD2jarRjDFAkVjnjLJDg; _pk_ses.3.42ca=1
Upgrade-Insecure-Requests: 1
If-Modified-Since: Fri, 11 Dec 2020 22:20:01 GMT
Cache-Control: max-age=0
Supporting Material/References:
https://hackerone.com/reports/753399
https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html
Impact:
An attacker can use this vulnerability to redirect users to other malicious websites, which can be used for phishing and similar attacks
Users could get redirected to malicious domains .
Screenshot:

I Hope that you will fix this issue as soon as possible. Looking forward to hearing from you. Thank you .
Kind Regards,
fixitTeam
<EMAIL_ADDRESS>

Thanks for the report, we'll look into this. Users clicking a link already get a warning that an external site is going to be opened.

Thanks for your feedback , As this is the most critical issue for any web
application , I Hope that you will consider our hard work and hope that you
will fix this issue as soon as possible. Looking forward to hearing from
you. Thank you .
reference report :

https://hackerone.com/reports/753399

Regards,
Samuel Leach
(Security Researcher)
On Mon, Dec 14, 2020 at 11:24 AM Thomas Zarebczan<EMAIL_ADDRESS>wrote:

Thanks for the report, we'll look into this. Users clicking a link already
get a warning that an external site is going to be opened.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-desktop/issues/5175#issuecomment-744657067,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASDMHIITNLNALB5EANEJATTSUZQ7HANCNFSM4UZRRZRA
.

@fixit9211 working on this now

Hi,
We are glad to see that you have resolved this critical issue you were
facing with our findings. I hope that you will consider our hard work. I am
writing this email to request a fair reward/bounty from your end that will
motivate our team. You know it takes some time and effort to find a bug in
a website. We did it for you to make your website more secure and safe.
Looking forward to your positive response.
Regards,
Samuel Leach
On Thu, Dec 17, 2020 at 2:56 AM Sean Yesmunt<EMAIL_ADDRESS>wrote:

Closed #5175 https://github.com/lbryio/lbry-desktop/issues/5175 via
#5198 https://github.com/lbryio/lbry-desktop/pull/5198.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-desktop/issues/5175#event-4121958966, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASDMHILI3CHXKRVV3BEUY43SVEUINANCNFSM4UZRRZRA
.

Thanks so much! Please send an email to<EMAIL_ADDRESS>with this link to claim it.

sure thanks


default for flexDirection is CSS_FLEX_DIRECTION_COLUMN in layout.c, but in real CSS it is CSS_FLEX_DIRECTION_ROW

This was a conscious choice.
cc @vjeux

see https://github.com/facebook/css-layout#default-values


Align lattice vectors to xyz when writing PDB

PDB unit cell information assumes that it’s aligned to xy (or at least x), which is not always true in formats like POSCAR. VMD aligns lattice vector a to x and applies the same transformation to the coordinates. We should do this when writing a PDB but print a warning message when doing s

Fixed in affcb6d3f4a62ae631d793f09a3fce11c0c63333


How to change "Hostname" Insurgency Sandstorm ?

Hi
Is it possible to have an env to change the name of the server ?
Thanks

That should be easy enough. Currently things are pretty hardcoded, my general rule of thumb is to look at the official config for a game:
https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/config-default/config-lgsm/inssserver/_default.cfg
I look for a config name then manually add it in this file with LGSM_ on the front:
https://github.com/joshhsoj1902/linuxgsm-docker/blob/master/common.cfg.tmpl
I also likely need to update the base LGSM src for Insurgency since I think that was just added.
I might try to do this tonight, or more likely, I've been meaning to try to make the config building more dynamic, so that in this case you could have just set the env var "LGSM_SERVERNAME" and it would have automatically put into the common.cfg

I will wait thanks ;)

ok, so I don't own the game and can't actually test it myself, but using https://github.com/joshhsoj1902/linuxgsm-docker/blob/master/examples/docker-compose.inss.yml
seemed to start the server and it looked happy enough.
Right now you'll be able to set any setting in
https://github.com/GameServerManagers/LinuxGSM/blob/ac6320114417754e96b08487fcc508c8b30babfa/lgsm/config-default/config-lgsm/inssserver/_default.cfg
using env vars, So if you want to set the servername then use the env var LGSM_SERVERNAME.
If the setting you want to change is part of a config file, I could also add support for that, just tell me where the config file lives.

env var "LGSM_SERVERNAME" does not work for me.
I use "portainer"

After update "LGSM_PORT" not work for left 4 dead 2
It sets the default port "27015" ..

Your English is fine :)
Strange, admittedly I didn't test changing the ports after my change, I just used the default. I'll try it out tonight and see what I can find.
Same goes for L4D2, I've had a lot of trouble getting it to run inside this docker container, it always seems to fail for one reason or another...
I'll keep you posted!

I just tried starting up sandstorm with LGSM_SERVERNAME set.
My compose file looks like this:
version: '3.1'
services:
  game:
    image: joshhsoj1902/linuxgsm-docker:latest
    ports:
      - 27102:27102/udp
      - 27131:27131/udp
    environment:
      - LGSM_GAMESERVERNAME=inssserver
      - LGSM_UPDATEINSTALLSKIP=UPDATE
      - LGSM_SERVERNAME=foobar
    volumes:
      - "/home/steam/linuxgsm/logs"

I started it like this:
docker-compose -f examples/docker-compose.css.yml up

And it looks like the hostname is being set:
game_1  | Command-line Parameters
game_1  | ================================================================================
game_1  | ./InsurgencyServer-Linux-Shipping Oilfield?Scenario=Scenario_Oilfield_Push_Security?MaxPlayers=28?Port=27102?QueryPort=27131  -password= -hostname='foobar' -log

Are you seeing something different?

I will give up, the servers are still in beta for the moment ..
I'll be back !!

it works now !
Now it would be necessary to be able to change "defaultscenario" >__<
After an update they changed something about the name of the maps ..
Scenario_Refinery_Push_Security --> Scenario_Refinery_Push
So my server remains blocked to 8 players in coop .. :(

So you should be able to the default scenario the same way
https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/config-default/config-lgsm/inssserver/_default.cfg
(any fields in there should follow the same model)
LGSM_DEFAULTSCENARIO foo
Max players can be set the same way.
LGSM_MAXPLAYERS
I'll need to look at the code, something might be defaulting to 8 players instead of the 28 in the file above.

Oh Nice !
I did not know that "env" was walking like this.
Thanks ! Close issue :)


[YouTube] Unable to download own watchlater playlist

[x] I've verified and I assure that I'm running youtube-dl 2017.04.28
[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'-o', u'/mnt/pool/youtube/%(upload_date)s_%(uploader)s_-_%(title)s_%(id)s.%(ext)s', u'--restrict-filenames', u'--no-overwrites', u'--mark-watched', u'--socket-timeout', u'30', u'--retries', u'25', u'--fragment-retries', u'25', u'--no-call-home', u'--cookies', u'/root/scripts/youtube-sync.cookies', u'--download-archive', u'/root/scripts/youtube-sync.archive', u'--audio-format', u'm4a', u'--username', u'PRIVATE', u'--password', u'PRIVATE', u'https://www.youtube.com/playlist?list=WL']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.04.28
[debug] Python version 2.7.12 - Linux-4.4.0-72-generic-x86_64-with-Ubuntu-16.04-xenial
[debug] exe versions: ffmpeg 2.8.11-0ubuntu<IP_ADDRESS>, ffprobe 2.8.11-0ubuntu<IP_ADDRESS>, rtmpdump 2.4
[debug] Proxy map: {}
[youtube:watchlater] Downloading login page
[youtube:watchlater] Logging in
[youtube:watchlater] WL: Downloading webpage
ERROR: This playlist does not exist.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 760, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 429, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 2504, in _real_extract
    _, playlist = self._extract_playlist('WL')
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 2046, in _extract_playlist
    raise ExtractorError(message, expected=True)
ExtractorError: This playlist does not exist.

Description of your issue, suggested solution and other information
Since yesterday i can't download my own watchlater playlist from youtube anymore. Einstein from the IRC channel says the google login changed.

Post the output with --dump-pages.

I deleted my cookies file and now it is working.


Batch is broken in 0.9.1.RELEASE

Found a lot of tests failed when updating Micronaut Data to the latest version https://github.com/micronaut-projects/micronaut-data/pull/1385
The main problem is here https://github.com/r2dbc/r2dbc-h2/blob/main/src/main/java/io/r2dbc/h2/H2Statement.java#L102
I think the problem is that some of the bind methods like bind with index, bindNull don't set open = false.

This also pops up in the jOOQ integration tests. Simple reproducer:
create table t (i int)

And then:
System.out.println(
    Flux.from(cf.create())
        .flatMap(c -> c.createStatement("insert into t values ($1)")
            .bind(0, 1).add()
            .bind(0, 2).execute())
        .flatMap(it -> it.getRowsUpdated())
        .collectList()
        .block()
    );
;

Exception:
Exception in thread "main" java.lang.IllegalArgumentException: No unfinished bindings!
	at io.r2dbc.h2.util.Assert.requireTrue(Assert.java:50)
	at io.r2dbc.h2.H2Statement.execute(H2Statement.java:102)
	at io.r2dbc.h2.H2Statement.execute(H2Statement.java:39)
	at org.jooq.testscripts.R2DBC.lambda$0(R2DBC.java:48)
	at reactor.core.publisher.FluxFlatMap$FlatMapMain.onNext(FluxFlatMap.java:386)
	at org.jooq.test.setup.DatabaseSetup$1.lambda$2(DatabaseSetup.java:289)
	at org.jooq.impl.Internal$1.onNext(Internal.java:454)
	at reactor.core.publisher.StrictSubscriber.onNext(StrictSubscriber.java:89)
	at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:127)
	at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1815)
	at reactor.core.publisher.MonoSupplier.subscribe(MonoSupplier.java:61)
	at reactor.core.publisher.Mono.subscribe(Mono.java:4150)
	at org.jooq.test.setup.DatabaseSetup$1.lambda$0(DatabaseSetup.java:285)
	at reactor.core.publisher.FluxSource.subscribe(FluxSource.java:66)
	at reactor.core.publisher.Mono.subscribe(Mono.java:4150)
	at reactor.core.publisher.Mono.block(Mono.java:1702)
	at org.jooq.testscripts.R2DBC.main(R2DBC.java:51)
	Suppressed: java.lang.Exception: #block terminated with an error
		at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:99)
		at reactor.core.publisher.Mono.block(Mono.java:1703)
		... 1 more

An attempted fix is here: https://github.com/r2dbc/r2dbc-h2/pull/229

@lukaseder Does #229 fix this issue?

@gregturn I think it should be safe to assume it fixes @lukaseder's issue, since he raised the PR?
As to the original issue with the micronaut-data tests, the fix was done with the same identified root cause, so seems likely.
Still hoping to get a 0.9.2.RELEASE and/or Borca-SR2 with this included, as it's still not possible to use the 0.9/Borca release train (or later) with H2 due to this issue.

@gregturn My PR did, at the time, I think? I'm sorry, I have a lot on my plate, can't prioritise building the next snapshot of this for another test spin right now. If you don't hear from me (via new issues), then you can assume things are fine :)

Looking into the 1.0.0.RELEASE upgrade now, and I can confirm that this issue seems to have been fixed.

It’s fixed for me too


Fix bug: if the snapshot is no longer in engine CR, don't block the removal process

longhorn/longhorn#6298

@ejweber I think we still need to check with the engine process before removing the snapshot CR's finalizer. This PR will do that. What do you think?

We discussed my "competing" PR offline and are in agreement that this is the right approach.
We don't have a simple recreate, but I can use the same iterative test I opened the issue with to check whether my cluster continues to accrue snapshots with this fix.

@mergify backport v1.5.x

auto-cleanup-system-generated-snapshot was introduced in 1.4 as well, so we don't need to tackle this issue even thought the implementation is different than 1.5 which is using longhorn VA.

LGTM.
nit: is it possible to have an orphaned snapshot always unable to delete because it can't be deleted at a replica side somehow, so the volume keeps in an auto-attaching state (surely, ticket type snapshot should be interruptable, so it should not impact other operations ideally)?
cc @shuo-wu @derekbit

If the snapshot is stuck in the removed state in the replica, yes, the volume will remain attached due to the snapshot-controller attachment ticket.
If workload starts on different node, it will interrupt the snapshot AD ticket. For other operations that require attachment, they will request the same node as the snapshot AD ticket. So I think it is fine

Also, auto-cleanup-system-generated-snapshot was introduced in 1.4 as well, so we don't need to tackle this issue even thought the implementation is different than 1.5 which is using longhorn VA.

Sorry, could you elaborate more on this?
I think this issue should happen in 1.5.x only because of the new AD mechanism

Sounds good.

Also, auto-cleanup-system-generated-snapshot was introduced in 1.4 as well, so we don't need to tackle this issue even thought the implementation is different than 1.5 which is using longhorn VA.

Sorry, could you elaborate more on this?
I think this issue should happen in 1.5.x only because of the new AD mechanism

It has been clarified. All good.


Hospital Management [GSSOC'23]

Describe the project you want to add with tech stack
About
Hospital Management System using Object Oriented Programming in C++
Expected behavior
Hospital Management System is a system enabling hospitals to manage information and data related to all aspects of healthcare – processes, providers, patients, and more.
Additional context (optional )
Demonstrated Inheritance, Polymorphism, Abstraction & Data hiding OOP principles .Implemented Exception Handling and File Handline; used Virtual Base Class and Friend functions

@MohitGupta121 @pranjay-poddar @TusharKesarwani  , please assign me this issue under GSSOC'23.


Remove MyFnOnce

This is no longer needed, as Box<dyn FnOnce(...)> works on stable now since 1.35.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit ae4b792fa47933806428acaf13b92acc1cf40c7b has been approved by alexcrichton

:hourglass: Testing commit ae4b792fa47933806428acaf13b92acc1cf40c7b with merge cd1e4bf7e933bbd2c2b2a08e9fef3a0cd5315164...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: alexcrichton
Pushing cd1e4bf7e933bbd2c2b2a08e9fef3a0cd5315164 to master...


luci-proto-ipv6: Add DHCPv6 norelease menu option as default on

As recommended by RFC 9096: WPD-9, to reduce the risk of prefix changes

If I take your other luci changes for the options and have it emit a string (so as not to break backwards compat), would that still work with the underlying odhcp6c with your PR there?

Yeah that should be fine.
I'd change the default value of the defaultreqopts flag to 1, to avoid changing the current default behaviour, as it's no longer required to close the original issue.
And maybe move both options in the advanced tab?

Please fix these (might require changing github settings too):
: Author name (Det) need to be your real name 'firstname lastname'
: Commit subject line MUST start with '<package name>: ' (Add DHCPv6 norelease menu option as default on, as recommended by RFC 9096: WPD-9)
: Signed-off-by is missing or doesn't match author (should be 'Signed-off-by: Det<EMAIL_ADDRESS>

Ahh, giving it a try, but am probably messing it up.  Might be easier if I recreate it with fresh commits?

Ahh, giving it a try, but am probably messing it up. Might be easier if I recreate it with fresh commits?

However you do it. It shouldn't take more than a single commit.

  Should I open another one now, or wait for the other PR to change the UCI default first?

Just push the (one) commit without the default line.

Just push the (one) commit without the default line.

Done #6775


These should be local to the file rather than the functions to prevent excess object generation, and thus speed up processing

https://github.com/poiuedws/awesomedotfiles/blob/bdccd5f2d9fd88dc48c71c4302a80d590b118b5e/widget/music/mpd-music-updater.lua#L161

referring to require('widget.music.content.media-buttons') and PATH_TO_ICONS .. 'repeat-on.svg'


Form group description text (.form-info) has wrong color

Label information color for forms in figma is using #333333. The Green component for that text is using the secondary color which is a light gray color.
Todos:

[ ] Markup
[ ] Tokens
[ ] Story

Looks like this was fixed in #646


Make scriptedforms command without any parameters open the live documentation

After fixing the following issue:
https://github.com/SimonBiggs/scriptedforms/issues/54
Work on creating live docs. These live docs will be able to be started by running scriptedforms without any parameters, also available by navigating to /scriptedforms/docs. Make the "docs" button in the top left of the form take you to the docs page on the server.

Live docs will have two columns as well as a table of contents menu bar. Column on the left will have editable scripted forms which are inside what look like notebook cells.
Column on the right will have the resulting scripted form. Each example will boot up its own kernel.
Have the docs always be accessible at /scriptedforms/docs. Open up the docs for the first time will progressively start kernels -- work out how to optimise this for best user experience.

Have the live docs have a link to "Your forms" which is a glob of the forms in and below the current working directory.


remove duplicate/erroneous beacon attestation topic grafana metric guage

Under Lodestar Grafana Dashboard under "Gossip Stats"
remove the beacon_attestation metric in this screenshot

but keep this one

Fixed in current metrics


unmutable col_iter and row_iter

Extend the functional programming abilities by adding iterators over the columns and the rows.
Two new methods are added to Grid::grid

pub fn iter_rows(&self) -> GridRowIter<'_, T>
pub fn iter_cols(&self) -> GridColIter<'_, T>

Where the new structs GridRowIter and GridColIter are wrappers around the existing grid.iter_col and grid.iter_row that keep track of the current index.
This feature reduces the risk of index errors when iterating over rows or columns.
Feedback and criticism is welcome. I'm planning on adding a mutable version of the two iterators in the future.

Thx! Looks good on first brief look. Will merge later if I have a bit more time to read the code.


Ordinary reports template

Hi there!
I've done some work towards making package more universal.
Firstly I've added new title page template for ordinary reports. It's fields are:

Mandatory:

\workType{...} -- a type of work, e.g. "Отчёт по выполнению домашнего задания"
\discipline{...} -- discipline, which is placed after workType line
\student{...} -- the same as in diploma|research classes
\group{...}
\supervisor{...}

Optional:

\version{...} -- version of the work, by default is empty (not printed)
\noscorefield -- disable score field, which looks like one in research class

Example

Also I've added two optional header parameters:

\faculty{Faculty name}{FC} -- faculty name and code
\department{Department name}{DC} -- department name and code

The parameters are defaulting to <<Информатика и системы управления>> (ИУ) and <<Информационная безопасность>> (ИУ8).
P.S.
README.md is updated accordingly. I think the fields and macros should be documented not only as an example, but also as an another README.(md|tex|pdf) containing stuff like "macro - its description and how to use it". What do you think about it?

Current state of documentation can be found here, in another branch called MD-docs.

Many thanks!


3D Tiles - memory management

Hello everybody，
I have tried to convert some texture models into b3dm according to official documentation, and have successfully loaded into Cesium. When I zoom out, some distant models disappear (I guess it was cut off), but why the memory does not change.
I think since the model has been cut off, the memory should be reduced. is it a bug?
Anyone can help me? thanks.

Tiles that are out of view may still be cached and stay in memory. By default the maximum number of cached tiles is 256. What happens when you construct Cesium3DTileset with maximumNumberOfLoadedTiles : 0 ?

It works. Thanks a lot.


Add a filter view on the research page

Could filter based on current project status and research category.
Block by:

[ ] #18

I added a filter view in this commit 43512e7


Create new types - File and Rank

Extended int types, which define x and y coordinate axis of the chessboard, ranks and files respectively.

Finished.


tab switch animation RTL broken

Bug, feature request, or proposal:
bug
What is the expected behavior?
tabs switch animation in RTL should work in the correct direction:
when pressing a tab on the left, content should swipe-in from left
What is the current behavior?
content always swipes from right, and sometimes just appears
What are the steps to reproduce?
material demo for 5.0.0-rc.3
select RTL and switch any tabs
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
material 5.0.0-rc.3  (running demo-app)

Please re-open with a reproduction in stackblitz or plunker

any progress?

same problem.

this issue is still ongoing.
aside for cancelling animation is there a temporary bypass


Doesn't seem to scale windows properly with multiple monitors

chunkwm seems to work if I only have the internal laptop screen, but apparently it's not scaling the windows correctly if I connect external monitors with different resolutions. For example, it seems to think that the whole screen space (the space arranged after pressing alt + f) is just this space occupied by these two terminal windows, instead of the whole actual laptop screen space. This makes the windows extremely small and unusable.

On the external monitor, the application does seem to be scaled normally.

The following is my monitor configuration under this scenario:

The laptop screen is standard 13' MBP Retina (looks like 1280 x 800), while the monitor screen is 1920 x 1080.
I installed chunkwm just now, with the --HEAD option. I'm surprised that I don't seem to be able to find the same issue already reported here.

You can set the padding per monitor, it's probably somewhere in your $HOME/.chunkwmrc file.
For example, this sets a padding of 8 pt for every side:
chunkc set global_desktop_offset_top 8
chunkc set global_desktop_offset_bottom 8
chunkc set global_desktop_offset_left 8
chunkc set global_desktop_offset_right 8

However, this can be overridden per space/desktop like this, setting the padding for the space/desktop labeled "Desktop 1" to 20:
chunkc set 1_desktop_offset_top 20
chunkc set 1_desktop_offset_bottom 20
chunkc set 1_desktop_offset_left 20
chunkc set 1_desktop_offset_right 20

Note that these settings are space/desktop dependent and not depending on your monitor.

Thanks. Changing the offset and restarting chunkwm fixed it. I was surprised to find the following in the default configuration file (I don't think I edited it after copying at installation):
chunkc set 3_desktop_offset_top          190
chunkc set 3_desktop_offset_bottom       190
chunkc set 3_desktop_offset_left         190
chunkc set 3_desktop_offset_right        190

I think this might have caused the behavior. It seems to be quite unintuitive as a default configuration.

fixed on master.


support configuring the sorting buffer pool

This PR adds the ability to configure a buffer pool that parquet.SortingWriter instances use to allocate the buffer where their temporary files.
I have reused the parquet.PageBufferPool API for this purpose, but by default I kept the sorting buffers and column page buffers separated because they tend to be of very different sizes.
I'm open to naming suggestions, it seems parquet.PageBufferPool is not so representative now that we have a new use case for it.

I'm open to naming suggestions, it seems parquet.PageBufferPool is not so representative now that we have a new use case for it.

For lack of creativity I renamed parquet.PageBufferPool to parquet.BufferPool. I'm a bit concerned that it could get confusing since there is a parquet.Buffer type which has nothing to do with it, I'm considering moving parquet.BufferPool to a subpackage to avoid the confusion but haven't made up my mind on a name for the package either so for now this is the way.


ArangoDB High RAM Usage

My Environment

ArangoDB Version:        <IP_ADDRESS>-1
Storage Engine:            RocksDB
Deployment Mode:       Cluster
Deployment Strategy:   ArangoDB Starter
Configuration:               three nodes, baremetal
Infrastructure:               baremetal
Operating System:        Ubuntu 18.04
Total RAM in your machine:  64GiB
Disks in use:        ssd and hdd
Used Package:              Ubuntu.deb repo

Problem:
I have a three node cluster, and it is having ram issues.
They are consuming way too much RAM when compared to its typical behavour.
I also have about 15GBs of logs on each node, here is a sample.
arangodb.log

How do I troubleshoot this issue?

When you acquire curl coordinator/_admin/cluster/shardDistribution you can see, which collection is affected as there is a shard mapping for production-db/29192308. It seems as if we cannot complete the synchronisation for that shard.
could you then raise the log levels for cluster and maintenance topics  on the spamming cluster machine like so:
curl server:port/_admin/log/level -XPUT -d '{"cluster":"debug","maintenance":"debug"}'
for just a couple of minutes and provide us with that log, please

@kvahed
here is the output from the first curl command:
root@db1:~# curl --basic --user "${DBUSER}:${DBPASS}" -s http://localhost:8529/_admin/cluster/shardDistribution | jq .
{
  "results": {
    "_statistics15": {
      "Plan": {
        "s3010038": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010038": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_statistics": {
      "Plan": {
        "s3010035": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010035": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_appbundles": {
      "Plan": {
        "s3010029": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010029": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_aqlfunctions": {
      "Plan": {
        "s3010016": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010016": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_iresearch_analyzers": {
      "Plan": {
        "s3010009": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010009": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_modules": {
      "Plan": {
        "s3010007": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010007": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_fishbowl": {
      "Plan": {
        "s11020022": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s11020022": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_users": {
      "Plan": {
        "s3010004": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010004": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_graphs": {
      "Plan": {
        "s3010002": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010002": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_routing": {
      "Plan": {
        "s3010011": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010011": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_statisticsRaw": {
      "Plan": {
        "s3010032": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010032": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_queues": {
      "Plan": {
        "s3010020": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010020": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_jobs": {
      "Plan": {
        "s3010022": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010022": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_frontend": {
      "Plan": {
        "s3010018": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010018": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    },
    "_apps": {
      "Plan": {
        "s3010026": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      },
      "Current": {
        "s3010026": {
          "leader": "DBServer0002",
          "followers": [
            "DBServer0003"
          ]
        }
      }
    }
  },
  "error": false,
  "code": 200
}
root@db1:~#

^ im not quite sure what i should be looking for in here.
i have some hesitation about turning on the debugging logging without the knowledge on how to turn it back off.
@kvahed is there a way to query its current logging configuration so that i can change it back?

@kvahed i was able to grab the logs with DEBUG turned on, see attached.
arangod.log.gz

As discussed in https://github.com/arangodb/arangodb/issues/11577 exposing more options of rocksdb to the commandline seems to ease the memory situation.
Namely:

--rocksdb.cache-index-and-filter-blocks-with-high-priority
--rocksdb.pin-l0-filter-and-index-blocks-in-cache
--rocksdb.pin-top-level-index-and-filter

These have been added to the now released ArangoDB 3.7 - If you still experience this, please get back to us in a new issue.


Refactor Average Change in Profit/Losses

Refactor Average Change in Profit/Losses
User Story
As a boot camp student,
I want to correct the calculation of the rate of change,
so the Finacial Analysis outputs the correct average change value.
Acceptance Criteria

It's done when the rate of change (RoC) does not apply Math.abs() to the transaction amounts difference.
It's done when all rates of change (RoC) are stored in a variable than can be reused for future calculations.
It's done when the Financial Analysis outputs the correct average change value.

Average Change Pseudocode
// The average of the changes in Profit / Losses over the entire period.
// You will need to track what the total change in profits is from month to month and then find the average.
// (Total / Number of months)

  // for loop starting with i = 1
    //For Each iteration, subtract the data at position [1] of the previous element from the data at position [1] of the current element
    // Put that data into a new array variable
      // So, we need to arr.push() each new 'change' value to the new array

  // Add up the total in the new 'changes' array
    // Need a variable to store the rolling total for this array that's different that the rolling total of profits
    // for loop to iterate over the changes array
      // add each element in turn to the rolling total

  // Take that 'total changes amount' variable and divide it by the number of elements in the array
    // Look up how to limit the answer to two decimal points

Final Output with Average Change amend
Financial Analysis

Total Months: 86
Total: $38,382,578.00
Average Change: -$2,315.12
Greatest Increase in Profits: Feb-2012 ($1,170,593.00)
Greatest Decrease in Profits: Sep-2013 (-$1,196,225.00)


Move to functional components (Part II)

Description
Migrate the following from class-based components to functional components:

src/commons/dropdown/Dropdown.tsx
src/commons/editingWorkspace/EditingWorkspace.tsx
src/commons/editingWorkspaceSideContent/EditingWorkspaceSideContentTextAreaContent.tsx

Also removed unused width, height state variables

src/commons/sideContent/SideContentFaceapiDisplay.tsx

Also improved the code quality and reduce code duplication where applicable.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[x] Code quality improvements

How to test
NIL
Checklist

[x] I have tested this code
[ ] I have updated the documentation

@chownces it doesn't seem like EditingWorkspaceSideContentTextAreaContent is being used anywhere at the moment. What is it for?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

20 of 159 (12.58%)  changed or added relevant lines in 4 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.006%) to 32.959%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/commons/dropdown/Dropdown.tsx
18
20
90.0%

src/commons/sideContent/SideContentFaceapiDisplay.tsx
0
11
0.0%

src/commons/editingWorkspaceSideContent/EditingWorkspaceSideContentTextAreaContent.tsx
1
39
2.56%

src/commons/editingWorkspace/EditingWorkspace.tsx
1
89
1.12%

Files with Coverage Reduction
New Missed Lines
%

src/commons/editingWorkspace/EditingWorkspace.tsx
2
0.49%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
4332

Relevant Lines:
12229

💛  - Coveralls


Implement Topics

How new connections are injected into topics kbuckets and the local routing table, will probably have to be revised and optimised to avoid having to update the same connection in different kbuckets and to avoid cloning enrs.
A lot of code has been reused purposely to show which parts of the discv5 pre-topics logic tie into the discv5 topics logic. A topic is a 32 byte hash that can be converted into the key of a kbucket entry, just as a node id can. An ADNODES (topics discv5) response body is identical to a NODES (old discv5) response body.

Protocol outdated, closing.

this will take a bit longer after all


[BUG] Using scan helper method doesn't return all results

What is the bug?
When I try to use the scan helper, I'm not able to get all of the search results as it returns an error.
How can one reproduce the bug?
Run the code below with you're updated information (e.g. hostname for open search, profile name for boto3)
import boto3
from opensearchpy import OpenSearch, AWSV4SignerAuth, RequestsHttpConnection
from opensearchpy.helpers import scan

host = '<your_host_name>'
sso_profile = '<your_sso_profile_name>'

sess = boto3.Session(profile_name=sso_profile)
region = sess.region_name
credentials = sess.get_credentials()
auth = AWSV4SignerAuth(credentials, region, 'aoss')

open_search_client = OpenSearch(
    hosts=[{'host': host, 'port': 443}],
    http_auth=auth,
    use_ssl=True,
    verify_certs=False,
    connection_class=RequestsHttpConnection,
    pool_maxsize=20
)

query = {
  "query": {
    "match_all": {}
  }
}

results = scan(open_search_client, query=query, index='medications')

res_list = []
for result in results:
    print(result['_id'])

What is the expected behavior?
I should be able to return all of the results from the sample above.
What is your host/environment?
OS Version: Windows 10 Enterprise
Python Version: 3.10
Library Versions:

opensearch-py==2.3.2

Do you have any screenshots?
Traceback (most recent call last):
  File "C:\Users\nicholas.arquette\PycharmProjects\Trove\open_search\testing.py", line 16, in <module>
    for result in results:
  File "C:\Users\nicholas.arquette\AppData\Local\miniconda3\envs\ehrin\lib\site-packages\opensearchpy\helpers\actions.py", line 598, in scan
    resp = client.scroll(
  File "C:\Users\nicholas.arquette\AppData\Local\miniconda3\envs\ehrin\lib\site-packages\opensearchpy\client\utils.py", line 179, in _wrapped
    return func(*args, params=params, headers=headers, **kwargs)
  File "C:\Users\nicholas.arquette\AppData\Local\miniconda3\envs\ehrin\lib\site-packages\opensearchpy\client\__init__.py", line 1398, in scroll
    return self.transport.perform_request(
  File "C:\Users\nicholas.arquette\AppData\Local\miniconda3\envs\ehrin\lib\site-packages\opensearchpy\transport.py", line 409, in perform_request
    raise e
  File "C:\Users\nicholas.arquette\AppData\Local\miniconda3\envs\ehrin\lib\site-packages\opensearchpy\transport.py", line 370, in perform_request
    status, headers_response, data = connection.perform_request(
  File "C:\Users\nicholas.arquette\AppData\Local\miniconda3\envs\ehrin\lib\site-packages\opensearchpy\connection\http_requests.py", line 230, in perform_request
    self._raise_error(
  File "C:\Users\nicholas.arquette\AppData\Local\miniconda3\envs\ehrin\lib\site-packages\opensearchpy\connection\base.py", line 301, in _raise_error
    raise HTTP_EXCEPTIONS.get(status_code, TransportError)(
opensearchpy.exceptions.NotFoundError: NotFoundError(404, '')

Do you have any additional context?
I'm just trying to get all of the data returned so that I can parse the information and put it into a relational database.

Same issue happens when I try to use the scroll method as well.

What query is it making underneath that causes the 404? Turn this into a (failing) test?

Figured out the issue.  I'm using aws opensearch serverlist and it isn't a support operation. For Amazon OpenSearch Serverless collections, search_after will be used because neither point_in_time nor scroll are supported by collections.

Not a supported request type for aws opensearch serverless.


Update 12-mail.md

The first paragraph was missing its ending. I hope I've correctly added what you meant to say.

I haven't tested view-overrides with package-based emails ... but could you prefix the view for the email with the package's vendor prefix, so the end-user can override the content?
ie:
-        return $this->view('emails.welcome');
+        return $this->view('blogpackage::emails.welcome');

I haven't tested view-overrides with package-based emails ... but could you prefix the view for the email with the package's vendor prefix, so the end-user can override the content?
ie:
-        return $this->view('emails.welcome');
+        return $this->view('blogpackage::emails.welcome');

I just confirmed that your suggestion works! I'll update the section after merging your PR 👍

I just confirmed that your suggestion works! I'll update the section after merging your PR 👍

Cool. We both learned something! :)

Yeah exactly!

I just confirmed that your suggestion works! I'll update the section after merging your PR 👍

Cool. We both learned something! :)


[BUG] - test_create_lockfile_specification_auth compares two different lockfile specs

Describe the bug
There's a bug in test_create_lockfile_specification_auth. This test sends a POST to /specification/ which initiates a build; then it grabs the resulting lockfile produced by the build, and sends another POST to /specification/ containing the contents of the lockfile from the first build. The test then checks that the build_id is different for each build job, that the lockfiles for both jobs are identical, and that the second job has the expected dependencies that were sent as part of the first build job.
The problem is that the function that actually builds the environment, conda_store_server._internal.worker.build.build_conda_environment, produces lockfiles in two different ways:

If the build is created using a specification that just contains an environment with dependencies, conda-lock is used to solve the environment and write the lockfile, inside conda_store_server._internal.action.generate_lockfile.action_solve_lockfile
If the build is created using a specification that is really just a pre-existing lockfile, schema.LockfileSpecification is used to parse the lockfile, inside conda_store_server._internal.worker.build.build_conda_environment.

When this test runs, the two different lockfile specifications don't match because they can't - schema.LockfileSpecification is a pydantic model that is part of conda-store, and the other is whatever conda-lock spits out.
Expected behavior
We should probably validate the output of conda-lock inside action_solve_lockfile so that the lockfile spec produced matches the model that we use to parse and save it later on in subsequent builds.
How to Reproduce the problem?
Run test_create_lockfile_specification_auth.
Output
No response
Versions and dependencies used.
No response
Anything else?
No response

Fixed by https://github.com/peytondmurray/conda-store/pull/6, which has been merged into #985. So, going to close this issue


FunctionPlot wrong X bounds

If I pass an IFunctionSource into plot.Add.Function() which has specified RangeX to limit the function to the range, then this is ignored and the function will plot over the whole visible range.
I'm pretty sure its because the Min/Max are backwards here:
https://github.com/ScottPlot/ScottPlot/blob/5c02d82432cebe5018d22ebd8be41738e80f0ebc/src/ScottPlot5/ScottPlot5/Plottables/FunctionPlot.cs#L23-L24
I believe MinX should be the Max(...) of the two mins, and MaxX should be the Min(...) of the two maxs, from what I understand.
ScottPlot.Plot myPlot = new();
myPlot.Axes.SetLimits(-10, 10, -10, 10);
myPlot.Add.Function(new FunctionSource(x => x)
{
    RangeX = new CoordinateRange(-1.0, 1.0)
});
myPlot.SavePng("bug.png", 300, 300);

Hi @Matthew-Chidlow, thanks for reporting this issue! ... and drilling down to the lines of code that underlies it. I'll take a closer look within the next few days (but am happy to review a PR if someone gets to it before I do).
For added context, the present behavior is that the line is shown over the whole visible X range, but really it should only be drawn in the X range [-1, 1]
    [Test]
    public void Test_Function_Bounds()
    {
        FunctionSource fs = new(x => x)
        {
            RangeX = new CoordinateRange(-1.0, 1.0)
        };

        Plot myPlot = new();
        myPlot.Axes.SetLimits(-10, 10, -10, 10);
        myPlot.Add.Function(fs);

        myPlot.SaveTestImage();
    }

resolved in #3603


Add a worker option to skip execution

Client nodes are currently running the execution for all chains but almost certainly don't need to access the execution state of many of those. Notably for the senders of cross-chain messages to the user's chains, we only care about blocks and certificates.
We could also avoid updating other parts of the chain state such as the received_log, inboxes, etc.

I've been thinking about this recently: for the chains that are not "tracked" by a wallet, we may want to keep only the outboxes targeting the tracked chains, plus a LRU cache of downloaded certificates.

Looks like it was duplicated by #2025


trying to match training performance

The reported f-score for GCN-D (0.7, 0.75) is 79.26: https://github.com/yl-1993/learn-to-cluster#results-on-part1_test
I ran the provided training script, the f-score is 78.74.  This is very close, but still the difference could be a bug at my end. Could you please confirm these numbers, or suggest some ways to check if anything is going wrong?

@AruniRC Hi Aruni, thanks for trying our code. Your trained performance is close to my result, as reported in PR https://github.com/yl-1993/learn-to-cluster/pull/6. These setting is a demonstration and there are some other training skills to further increase the performance, e.g., more cluster proposals, larger epochs. For better performance, you can checkout the config dsgcn/configs/cfg_train_8_prpsl.yaml in dev branch.

Thank you. I think 78.74 (my recreation) and 78.80 (your results in PR) are close enough, so probably no setup/runtime bugs at my end.


[liblo] Fix filenames for linux in liblo portfile

Describe the pull request
Liblo currently doesn't build on Linux (and I assume Mac) due to some filenames in the portfile specifying "exe" filetype.

What does your PR fix?

Allows building on non-windows platforms

Which triplets are supported/not supported? Have you updated the [CI baseline]?

x64-linux, x64-windows, x64-osx

Does your PR follow the maintainer guide?

I think so

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

Yes

Depends on https://github.com/microsoft/vcpkg/pull/19633.

/azp run

What's left to get this merged? It looks like the checks have passed. Thanks

Awesome, LGTM! Thanks for the PR!


No gitignore included

There wasnt a gitignore included. Need to add a gitignore for a C# VS project,

Can we close this issue please. The ignore file was included over a year ago now.


ARROW-15328: [C++][Docs] Streaming CSV reader missing from documentation

Updates the C++ CSV reader docs to include documenting and an example of the streaming CSV reader (StreamingReader), as per the suggestion in ARROW-15328.
@westonpace could you look at this and let me know if this is what you were thinking?

@wjones127 Would you like to take a look and review this?

Thanks so much @pitrou for taking a look. I made all your suggested changes in atomic commits.

Thanks for the review @westonpace, this is really helpful. I have some language to work on and I'll update here when this is ready for another review.

Thanks for the feedback so far @westonpace and @pitrou. This is ready for another look when/if you have time, specifically the section on Tradeoffs (link to diff).


API Unit Tests are silently failing: Permission to write Cloud Trace telemetry

Problem
API Unit Tests are silently failing, such as:

PR: https://github.com/GoogleCloudPlatform/emblem/pull/791
Build Example: https://console.cloud.google.com/cloud-build/builds/74a703e3-8236-4ad5-b6eb-5d214f364931?project=97614911777

It appears that Content API Staging does not have permission to write telemetry to Cloud Trace.
Solution

[ ] Give the emblem-ci-ops service account for Content API the missing permission
[ ] Modify terraform to give this permission to future service accounts
[ ] Correct the API Unit Test to fail on permission error, which may be related to running with pytest or shell strict error handling

To fix the Cloud Trace issue, we should grant the builder service account role/cloudtrace.agent permissions.

API Unit Tests pass fine:
============================= test session starts ==============================
platform linux -- Python 3.11.3, pytest-6.2.4, py-1.11.0, pluggy-0.13.1
rootdir: /workspace/content-api
collected 7 items

main_approver_test.py ...                                                [ 42%]
main_nonapprover_test.py ....                                            [100%]

however, after the tests, a process kicks up to publish OpenTelemetry traces to Cloud Trace. I don't really care what that process is, as I noted above we probably don't want telemetry publishing to happen as part of these tests, but I'm using the fact that it's currently trying to make our CI system more robust.
So the important thing is there's an exception, and Cloud Build isn't aware of it:
Traceback (most recent call last):
  File "/builder/home/.local/lib/python3.11/site-packages/opentelemetry/exporter/cloud_trace/__init__.py", line 168, in export
    self.client.batch_write_spans(
  File "/builder/home/.local/lib/python3.11/site-packages/google/cloud/trace_v2/services/trace_service/client.py", line 554, in batch_write_spans
    rpc(
  File "/builder/home/.local/lib/python3.11/site-packages/google/api_core/gapic_v1/method.py", line 113, in __call__
    return wrapped_func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/builder/home/.local/lib/python3.11/site-packages/google/api_core/retry.py", line 349, in retry_wrapped_func
    return retry_target(
           ^^^^^^^^^^^^^
  File "/builder/home/.local/lib/python3.11/site-packages/google/api_core/retry.py", line 191, in retry_target
    return target()
           ^^^^^^^^
  File "/builder/home/.local/lib/python3.11/site-packages/google/api_core/timeout.py", line 120, in func_with_timeout
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/builder/home/.local/lib/python3.11/site-packages/google/api_core/grpc_helpers.py", line 74, in error_remapped_callable
    raise exceptions.from_grpc_error(exc) from exc
google.api_core.exceptions.PermissionDenied: 403 The caller does not have permission

The tests are run with python -m pytest, but when the exception happens something strange is going on: the exception is not being noted by the shell as an error or crash. This is a clue that python CLI is hiding the error from the rest of the system. Typically, tools will have some flag to say "treat errors as errors" if there's really some ambiguity on this, but I don't see anything in https://docs.python.org/3/using/cmdline.html that makes sense to me as that other than the fairly complex options around warning handling.
Is there something that should be done to make sure the process shutdown for pytest has exceptions properly raised and given an actionable exit code from python?

Merged in PR #931 - closing out


Add description string to job

Feature details
Along the lines of what was suggested in issue #121 , having the possibility of attaching a short description to each job would also help find old jobs that we would like to retrieve for some purpose. I believe qiskit has this feature as well.
Implementation
No response
How important would you say this feature is?
1: Not important. Would be nice to have.
Additional information
No response

Hi!
Are we thinking in some specific length? eg. stadard sentence (50-100 char), one paragraph (200-250 char),  old-tweet (240 char), new-tweet (280 char), 1,000 char ~2 KB,  max json length (2,097,152 char ~ 4MB)...

I guess standard sentence(50-100 char)  should be fine, people should be able to come up with their own identifying systems. For larger descriptions, if we want to allow the user to store more notes, I would maybe allow one paragraph on a separate variable description  or something like this, but this description sounds more like something the user should create on their own elsewhere because they may be interested in updating it later

I completely agree with your suggestion Javi! I will add an issue and we can refine it tomorrow!


Large screen - How it works

Describe the bug
How it works is in the same line with the main buttons when on large screens
To Reproduce
Steps to reproduce the behavior:

Go to https://beep.modus.app
Observe in landscape mode (width > height)

Expected behavior
How it works is at the bottom
Screenshots or videos

Fixed by #87


(URGENT) Perform strict validation and raise errors if Concept YAML files have a wrong structure

Write out a JSON Schema for the Concept YAML file and validate it before reading it. This is causing silent crashes in downstream applications, such as the metanorma glossarist plugin.
Originally from:

https://github.com/metanorma/iso-10303-2/pull/308

@ronaldtse I’m a little confused here do we need to define something like below and validate according to it when reading the concept file or do we need to add validation for datatype in each model separately?
{
  "termed": "String",
  "term": "String",
  "language": {
  "terms": [
    "type": "String",
    "normative_status": "String"
    "designation": "String"
    ]
    "definition": [
      "content": "String",
    ],
    "examples": [
      "content": "String",
    ],
    "notes": [
      "content": "String",
    ],
    "language_code": "<three_digint_language_code>",
    "entry_status": "valid"
    "sources": [
      "type": "String",
      "origin": {
        "ref": "String",
        "clause": "String",
        "link": "String",
      }
    ]
  }
}

There are few layers of validation, so structural validation is definitely the basic type of validation.
normative_status, type and entry_status are not just normal strings, but they accept only certain values. We will need to check for them in the model.

@ronaldtse every key in this config file  is already being validated for the allowed values here. So we only need to add structural validation in this ticket. Right?

@HassanAkbar technically yes. However, why does Glossarist not raise any errors when reading the Concept YAML files that are clearly violating the data definition? I want to see errors raised when a bad file is read.

@ronaldtse I've tested the glossarist gem and it is raising errors for the following

If we enter a field that is not in the model it will raise an error here.
If we enter the values outside of the defined values here.

What other errors do we need to handle? Can you provide an example of an invalid file that was not raising errors?

@ronaldtse I tried running Glossarist on the given commits and it raises the following error if the yaml file is not properly formatted.
Psych::SyntaxError ((<unknown>): could not find expected ':' while scanning a simple key at line 17 column 3)

Do we need to reword this so that it is better to understand?
Also by looking at the fix here the spaces in groups name are replaced by dashes do we need to add a validation for that as well?
The error is not raised for the files if they contains lines starting with # because they are considered comments and are ignored when parsing.

@HassanAkbar for this error how come it's not causing the metanorma-glossarist-plugin to crash?
Can we override Psych error with a Glossarist error, e.g. Glossarist::Error::ParseError?

spaces in groups name are replaced by dashes

Probably not, the groups could be strings with spaces I guess?

@HassanAkbar for this error how come it's not causing the metanorma-glossarist-plugin to crash?

@ronaldtse In metanorma-plugin-glossarist we are reading the concepts inside the render method which is being called by the liquid and all the errors are caught by liquid and rendered as Liquid error: internal.
It does set the errors in the template variable that we can check after rendering is done and can raise the error again. I'm making that change as well.


Pull IToByteArray up to ICanvas

So that we can write canvas.ToByteArray() instead of (canvas as IToByteArray)?.ToByteArray() thus ensuring that the returned byte[] is never null.
This may seem like an odd pull request so let me explain. I started playing with enabling Nullable reference types on this project. This generates a lot of warnings so I decided against a huge pull request and  instead, break them into smaller pull requests for easier reviewing.

While your proposed change would make the code somewhat simpler and cleaner, it's a breaking change. I'm unsure if it worth the improvement.
You mention the use of nullable reference types as a goal. This feature of C# 8.0 requires .NET Core 3 as the minimum. It's not supported on .NET Framework of any version. So this goal isn't achievable at the moment.
So at the moment, I'm not inclined to accept the pull request.

I was not sure if this was a breaking change or not. Anyway, a direct cast (IToByteArray)canvas would get rid of the warning and would not be a breaking change!

This feature of C# 8.0 requires .NET Core 3 as the minimum.

Actually, nullable reference types work on .NET Framework. I have them enabled in my current project targeting .NET Framework and using some .NET Standard 2.0 libraries. And if you need the new attributes, such as NotNullIfNotNullAttribute, you can use the Nullable NuGet package.
I think it would be really nice to enable them as they really help to catch bugs. I got caught by ValidationMessage.MessageParameters being null instead of empty a few minutes after I tried SwissQRBill.NET (I know it's documented, but still…).
Would accept pull request(s) knowing now that nullable reference types work on NET Standard >= 1.0 and .NET Framework >= 2.0?

Will this cause any interoperability issues such as:

The library can only be used with projects compiled with C# 8.0.
The library (compiled with the NuGet package for .NET Standard 2.0) cannot be used with .NET Core 3 as the attributes conflict.
The library can be used with .NET Core 3 but nullability diagnostics do not work as .NET Core 3 expects another set of attributes.

The library can only be used with projects compiled with C# 8.0.

No. You can compile a .NET Standard 2.0 library with nullable reference types and C# 8 and this library can be used on a project using any version of the C# language. Of course you won't get the benefits of compiler warnings when misusing nullable reference types if you don't enable C# 8.

The library (compiled with the NuGet package for .NET Standard 2.0) cannot be used with .NET Core 3 as the attributes conflict.

No. The library is perfectly usable in both a .NET Framework 4.7.2+ app and a .NET Core 3+ app.

The library can be used with .NET Core 3 but nullability diagnostics do not work as .NET Core 3 expects another set of attributes.

No. Diagnostics work as expected. You can even get diagnostics to work on a .NET Framework project by enabling nullable reference types and using C# 8 like this:
<PropertyGroup>
  <Nullable>enable</Nullable>
  <LangVersion>8.0</LangVersion>
</PropertyGroup>

I've created a branch nullability-annotations and merged your PR into it. On the branch, C# 8.0 and nullable reference types are already enabled.
We can work on this branch until the nullability work is complete.

Merged to branch "v3".

Closing since it was merged in commit 6602eef65b16c58d651cc1436a17508ec5381bb5.


Updated dependencies and correction as per updates

Python 3.6 is deprecated. I have set 3.11.5 just to put a version, but that could be changed. Also updated all dependencies and corrected issues raised by linting/mypy.

Hi,
we are currently using this project, and I wanted to add the ability to add ignore rules for lists and object list (same as #24 wanted). Right now I am using some bad hacks to do this.
But when trying to just install and run all tests, I found multiple issues.The changes in the PR are to correct those issues

Hi! Thx for u contribution!
Globally, everything is fine, but the minimal version of python scares me.
The python 3.11 is too new, and many users may have a broken installation that is still sitting on 3.9-3.11.
I suggest to setpython=^3.9.

Moved down to 3.9
Also py36-plus on add-trailing-comma no longer does anything
VERSION on the makefile doesn't seem to be used anywhere? Probably could be removed

VERSION on the makefile doesn't seem to be used anywhere? Probably could be removed

yeah

Done


updates ++snag to cast the product

as pointed out by @ohAitch on urbit-meta ...

Why the |-s anyway?

I think otherwise the $(a t.a) tends to break?
On Tuesday, 11 October 2016, Raymond Pasco<EMAIL_ADDRESS>wrote:

Why the |-s anyway?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/277#issuecomment-253064735, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhj2j27jU4vFlGdtFeV8NldrKpuRJks5qzAw9gaJpZM4KUE5G
.

I've dropped the |- -- I agree that it's unnecessary.
There's lots of other superfluous loops in other list processing gates ... Old code, or is there some reason to not recur into a wet arm?

I should have weighed in earlier.    Sometimes you even want the loop to expand nontrivially.  But usually you don't, and drying it out shows that clearly...
Sent from my iPhone

On Oct 11, 2016, at 6:08 PM, Joe Bryan<EMAIL_ADDRESS>wrote:
I've dropped the |- -- I agree that it's unnecessary.
There's lots of other superfluous loops in other list processing gates ... Old code, or is there some reason to not recur into a wet arm?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok, thanks for the details! I've added it back.

Thanks!
On Tue, Oct 11, 2016 at 7:02 PM, Joe Bryan<EMAIL_ADDRESS>wrote:

Ok, thanks for the details! I've added it back.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/277#issuecomment-253098622, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AALyAWLbGJt5SHQXiwgm7kLs2GlllIsWks5qzD_QgaJpZM4KUE5G
.


emplace, emplace_back, emplace_front

It would be great if vector and flex_vector supported emplace counterparts for set, push_back, push_front.

While it makes sense theoretically, and it may provide a small performance advantage when using transients, note that in general there is some ammount when pushing elements into an immutable vector (the neighbouring elements need often to be copied), so the advantage of such methods is tiny for immutable vectors.


Rewards for Linked Fishes and Mythical Flower quests

Edited Ridge Pond to make it more magically
Changed the fish in the Ridge Pond to pre-2.0 fish only (ie the ones Belinda asks for in the quest + the Pebble Back Crab that got left out)
Added letter and event where Belinda introduces player to pond after completing Linked Fishes quest
Changed Raeriyala's ring to spawn the spirit fox rather than the placeholder chicken
Added some frames to the fox's spritesheet so that its tail wags when it's idle
Tried to get Belinda's ring's companion (the spirits) to change every time the player changes location, but it's not really working...
Added rings to shop after player completes the Mythical Flower quest for 250 Spiritual Essence each
Added letter and event where Belinda introduces rings to player after completing the quest
Fixed a bug where Jio, Daia, and Kiwi couldn't be invited to the movies
Updated CP to 1.25

Also added some map strings to the boulders in the sewers that say, in kinder words than this, "You've found the sewers you special special genius you!

Patched PlayerDeath events so that the player ends up in Paula's Clinic when they die in Ridge Forest and Ridge Falls when they die in the Spirit Realm.


Add Code of Conduct

Based on the Contributor Covenant version 2.0.
As there is no email address available for the project, I'm proposing to use the WP Core Slack channel #core-coding-standards as the official channel to report violations. Depending on the violation, details can be shared in private via DMs if needed to protect the privacy of the parties involved.

As noted in https://make.wordpress.org/project/2022/04/29/discussion-contrib-handbook-part-2/, it sounds like a project Code of Conduct is coming.  Perhaps it would be better to inherit from that (though I admit that 10up uses Contributor Covenant for our projects as well)?

@jrfnl I can see the benefit of getting something in place and we can iterate once the larger project has formalized something to inherit to all downstream teams and components.

I'm not able to add myself as a review and note my approval of the PR, so leaving a comment to that effect: ✅ thanks for adding this, always good to allow people to know how we expect them to behave.


build_sphinx and build_docs

I ran python setup.py build_docs here and was confused that the autodoc RST files were generated in docs/api and the HTML output in build/sphinx/html. Wouldn't it be better to have all generated files go in one folder?
I also see that there's still build_sphinx configured here:
https://github.com/astropy/regions/blob/9d1a0bf77e997af19b4393f75d5c0a22d4ad4560/setup.cfg#L1
@bsipocz or anyone -  I thought since a year or two it should only be build_docs and build_sphinx is the old way that shouldn't be used any more? What would you recommend we do here?

This probably isn't important or still relevant, but @bsipocz - could you please have a look at the description above and comment whether this issue should be closed or some edit should be done?

Oh, I think I never really figured this out being the dinosaur who still prefers to use build_sphinx. Looking at it now.

OK, right, this is not the issue I had in mind.
It's possible to move the api dir relative to index.rst with setting automodapi_toctreedirnm in docs/conf.py. Moving it to docs/_build/api somehow broke all the auto generated intersphinx links though, so I don't think it's worth the hack.
Sadly build_docs and build_sphinx doesn't understand each others' config so ideally both should be listed in setup.cfg. We have added build_docs to be a convenience for astronomers not familiar with the standard way of build_sphinx, but nevertheless the latter is still the standard way for sphinx setuptools integration, so I would advise against removing it.

(and currently, for me, everything end up in docs/_build rather than in build/sphinx. I can't recall what triggered it to be build in the latter nor how/when it went away, but that was the issue I thought about first.)

This is horrible in Python, that there are no standards for tests and docs.
I recently learned a bit of Rust and there it's always simple and the same for any project, see https://doc.rust-lang.org/rustdoc/what-is-rustdoc.html
That's so nice.
If only someone wrote a PEP adding a standard recommended solution for Python...
I see you've added something here: https://github.com/astropy/regions/commit/3f69f368680ed52847bce9d117b1bb690c28cef7#diff-380c6a8ebbbce17d55d50ef17d3cf906R6
So I'll just close this issue now. If there's anything else do to, please re-open.

Well, retrospect we shouldn't have added build_docs just because build_sphinx was confusing. Anyway, the plan is to at least remove the deprecation warning. https://github.com/astropy/astropy-helpers/issues/481
I wish to learn Rust, too at some point. Is it indeed as good as people claim it to be?

I wish to learn Rust, too at some point. Is it indeed as good as people claim it to be?

I don't feel qualified at all to answer that yet. It's not what I expected - I thought it's a simplified and safe C - but really it's a complex language, not something I could learn quickly even though I know Python, C and C++ quite well. But yes, they have a lot of good things, e.g. speed, parallelism, good tools for build and docs and distribution, ...


Add Sort Command

Closes #111
Adds Sort Command which allows sorting by:

Name
Quantity
Bought Date
Expiry Date
Unit

NOTE: Code is severely undertested. Sorting appears to work at first glance, but will need more thorough testing, especially for sorting by multiple flags.

The markdown files are supposed to have FoodREM inplace of Address Book. I believe in a previous PR, they were reverted back from FoodREM to Address Book. I experienced merge conflicts while pulling from master. After clarifying with @yixiann, I believe I'll just retain the original FoodREM text in the markdown.

Codecov Report

Merging #158 (9b9b28d) into master (196730b) will decrease coverage by 3.04%.
The diff coverage is 8.86%.

@@             Coverage Diff              @@
##             master     #158      +/-   ##
============================================
- Coverage     66.16%   63.11%   -3.05%
  Complexity      416      416
============================================
  Files            82       90       +8
  Lines          1398     1475      +77
  Branches        129      141      +12
============================================
+ Hits            925      931       +6
- Misses          414      482      +68
- Partials         59       62       +3

Impacted Files
Coverage Δ

...main/java/seedu/foodrem/commons/core/Messages.java
0.00% <ø> (ø)

...rc/main/java/seedu/foodrem/logic/LogicManager.java
71.42% <0.00%> (-3.58%)
:arrow_down:

...java/seedu/foodrem/logic/commands/SortCommand.java
0.00% <0.00%> (ø)

...java/seedu/foodrem/logic/parser/FoodRemParser.java
88.88% <0.00%> (-11.12%)
:arrow_down:

.../seedu/foodrem/logic/parser/SortCommandParser.java
0.00% <0.00%> (ø)

src/main/java/seedu/foodrem/model/Model.java
100.00% <ø> (ø)

.../java/seedu/foodrem/model/item/ItemBoughtDate.java
69.56% <0.00%> (-3.17%)
:arrow_down:

.../java/seedu/foodrem/model/item/ItemExpiryDate.java
69.56% <0.00%> (-3.17%)
:arrow_down:

...c/main/java/seedu/foodrem/model/item/ItemName.java
72.72% <0.00%> (-7.28%)
:arrow_down:

...in/java/seedu/foodrem/model/item/ItemQuantity.java
60.00% <0.00%> (-30.00%)
:arrow_down:

... and 17 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more