Title and Excerpt line breaks

I'm pulling some ReadMe files from GitHub and the Excerpt / Titles seem to be saved in the YAML with line breaks and extra spaces that don't show in the Properties view, but is problematic when I try to rearrange property order using Linter.
Is this part of the known bug experiences?

could you post a link to the readme and a copy of the resulting output?

Of course! This one may also be a twofer in weirdness; when targeting the Readme file in GitHub repositories, I would sometimes get the content but sometimes I would get the GitHub wrapper instead. I'll try to structure some proper repeatable tests because my quick and dirty approach was to just retry "until it worked".

Example
excerpt and title have this issue if it's longer than a single line. Whether the entry is contained in quotes or not does not appear to have an impact.
Target: https://github.com/mouse0270/module-credits/blob/master/README.md
Frontmatter in Source Mode:
---
Source: https://github.com/mouse0270/module-credits/blob/master/README.md
site: GitHub
excerpt: Lists the authors of projects on the Manage Modules Window. If a url is
  provided in the module.json file, it will make the version tag link to the
  module url. - mouse0270/module-credits
twitter: https://twitter.com/@github
slurped: 2024-06-08T14:31:41.227Z
title: module-credits/README.md at master · mouse0270/module-credits
---

Properties view wrapping does not indicate that the extra spaces or line breaks are in excerpt:

Recent Log

#####<PHONE_NUMBER>468 | DEBUG | onValidate called, no changes detected
- Caller: `eval (plugin:settings-search:131:29)`

{
"hash":<PHONE_NUMBER>
}

#####<PHONE_NUMBER>021 | DEBUG | onValidate called, no changes detected
- Caller: `HTMLDivElement.<anonymous> (app://obsidian.md/app.js:1:2989173)`

{
"hash":<PHONE_NUMBER>
}

#####<PHONE_NUMBER>582 | DEBUG | onValidate called, no changes detected
- Caller: `HTMLSpanElement.<anonymous> (app://obsidian.md/app.js:1:2058099)`

{
"hash":<PHONE_NUMBER>
}

#####<PHONE_NUMBER>965 | DEBUG | onValidate called, no changes detected
- Caller: `HTMLDivElement.<anonymous> (app://obsidian.md/app.js:1:2989173)`

{
"hash":<PHONE_NUMBER>
}

#####<PHONE_NUMBER>216 | DEBUG | attempting to parse prop metadata
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

{
"enabled": true,
"custom": false,
"_key": "Source",
"_idx": 0,
"id": "link",
"metaFields": [
"url",
"og:url",
"parsely-link",
"twitter:url"
],
"defaultIdx": 0,
"defaultKey": "link",
"description": "Page URL provided or a permalink discovered in metadata."
}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"url"
"meta[name="url"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"og:url"
"meta[name="og:url"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"parsely-link"
"meta[name="parsely-link"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"twitter:url"
"meta[name="twitter:url"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | attempting to parse prop metadata
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

{
"enabled": true,
"custom": false,
"_key": "byline",
"_idx": 1,
"id": "byline",
"metaFields": [
"author",
"article:author",
"parsely-author",
"cXenseParse:author"
],
"defaultIdx": 1,
"defaultKey": "byline",
"description": "Name of the primary author or the first author detected."
}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"author"
"meta[name="author"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"article:author"
"meta[name="article:author"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"parsely-author"
"meta[name="parsely-author"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"cXenseParse:author"
"meta[name="cXenseParse:author"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | attempting to parse prop metadata
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

{
"enabled": true,
"custom": false,
"_key": "site",
"_idx": 2,
"id": "siteName",
"metaFields": [
"og:site_name",
"page.content.source",
"application-name",
"apple-mobile-web-app-title",
"twitter:site"
],
"defaultIdx": 2,
"defaultKey": "site",
"description": "Website or publication name."
}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"og:site_name"
"meta[name="og:site_name"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"page.content.source"
"meta[name="page.content.source"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"application-name"
"meta[name="application-name"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"apple-mobile-web-app-title"
"meta[name="apple-mobile-web-app-title"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"twitter:site"
"meta[name="twitter:site"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{
"0": {}
}

#####<PHONE_NUMBER>216 | DEBUG | adding metadata
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

{
"prop": {
"enabled": true,
"custom": false,
"_key": "site",
"_idx": 2,
"id": "siteName",
"metaFields": [
"og:site_name",
"page.content.source",
"application-name",
"apple-mobile-web-app-title",
"twitter:site"
],
"defaultIdx": 2,
"defaultKey": "site",
"description": "Website or publication name."
},
"elements": {
"0": {}
},
"metaFields": {},
"querySelector": "meta[name="twitter:site"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
}

#####<PHONE_NUMBER>216 | DEBUG | attempting to parse prop metadata
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

{
"enabled": true,
"custom": false,
"_key": "date",
"_idx": 3,
"_format": "d|YYYY-MM-DDTHH:mm",
"id": "publishedTime",
"metaFields": [
"article:published_time",
"parsely-pub-date",
"datePublished",
"article.published"
],
"defaultIdx": 3,
"defaultKey": "date",
"description": "Date/time that the page was initially published.",
"defaultFormat": "d|YYYY-MM-DDTHH:mm"
}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"article:published_time"
"meta[name="article:published_time"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"parsely-pub-date"
"meta[name="parsely-pub-date"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

#####<PHONE_NUMBER>216 | DEBUG | found prop elements
- Caller: `SlurpPlugin.slurp (plugin:slurp:12508:30)`

"datePublished"
"meta[name="datePublished"], meta[property="{s}"], meta[itemprop="{s}"], meta[http-equiv="{s}"]"
{}

When I target:
https://github.com/reyzor1991/foundry-vtt-pf2e-notification/blob/master/README.md
https://github.com/reyzor1991/foundry-vtt-pf2e-reaction/blob/main/README.md
I get github wrapper to the page, which I don't want.
when I target:
https://github.com/reonZ/pf2e-perception/blob/master/README.md
I get the readme content expected, which I do want.

the github wrapper thing is a bit weird. all three of those links work for me. i'll try it a couple more times to see if i can narrow it down but tbh, i think rather than troubleshooting this it would make more sense to handle this as a preprocessing hook (see #37). ie: if github link and ends with .md, use the raw md file content rather than the parsed output.
regarding the newlines, it looks like the yaml lib i'm using is adding those newlines without adding the yaml syntax for a multiline string. can you try replacing the excerpt property directly in source mode with the following and see if that fixes your issue?
excerpt: >
  Lists the authors of projects on the Manage Modules Window. If a url is
  provided in the module.json file, it will make the version tag link to the
  module url. - mouse0270/module-credits

That said, it's a loose standard at best.

I disagree completely. Multi-line strings are well-supported by YAML in multiple ways and Obsidian specifically states that note properties are YAML-formatted and can contain a subset of supported data types. The frontmatter style of capturing metadata is a common pattern among applications that use Markdown.

That doesn't help; any line breaks are parsed by other apps as separate frontmatter values. My understanding is that unless it's a list, each frontmatter property needs to be on a single line as line breaks are used to parse between them, especially if someone is using RegEx.

Another tangent is whether maintaining formatting of the excerpt is more important/useful than it possibly clashing with Obsidian Add-Ons. I can see reasons for and against that - it's not obvious to me which answer is the best one at this moment.

Lots of websites publish multiple paragraphs in their excerpt (eg: academic journals that put a paper's abstract into the excerpt metadata), so it's important for slurp to ensure that the YAML lib respects existing line breaks.
In this case, the YAML lib is adding line breaks and that might be a behaviour I can change.
Beyond that, Slurp's goal is to capture information, so it's important for Slurp to stay as true to the original content as possible.
If other plugins aren't handling well-formatted YAML when processing note properties, then I'd recommend requesting proper YAML support from them. YAML is a complex specification, relying solely on regex to parse it will be a lot of work to maintain.

That said, it's a loose standard at best.

I disagree completely. Multi-line strings are well-supported by YAML in multiple ways. Obsidian specifically states that note properties are YAML-formatted and they have nothing to say on multi-line strings.

I was probably unfair in the negative. I was referring to things like this: https://en.wikipedia.org/wiki/YAML#Criticism where StrictYAML and similar endevours came in response to.
All that said, I'm happy to agree with you and obviously Obsidian targets YAML as a standard.

That doesn't help; any line breaks are parsed by other apps as separate frontmatter values. My understanding is that unless it's a list, each frontmatter property needs to be on a single line as line breaks are used to parse between them, especially if someone is using RegEx.

Another tangent is whether maintaining formatting of the excerpt is more important/useful than it possibly clashing with Obsidian Add-Ons. I can see reasons for and against that - it's not obvious to me which answer is the best one at this moment.

Lots of websites publish multiple paragraphs in their excerpt (eg: academic journals that put a paper's abstract into the excerpt metadata), so it's important for slurp to ensure that the YAML lib respects existing line breaks.
In this case, the YAML lib is adding line breaks and that might be a behaviour I can change.
Beyond that, Slurp's goal is to capture information, so it's important for Slurp to stay as true to the original content as possible.
If other plugins aren't handling well-formatted YAML when processing note properties, then I'd recommend requesting proper YAML support from them. YAML is a complex specification, relying solely on regex to parse it will be a lot of work to maintain.

When this ticket started, I was not clear on exactly what "correct" was supposed to look like in the first place, so much of this was thinking out loud to some degree. I agree with you completely now. I went digging for some clarity over discord and the web and essentially ended where you are.
At this point, I've tested in multiple YAML validators to ensure what "correct" is supposed to be and what you output is supported by that, so the behavior issue is clearly with Linter in this case.
Thank you for working through that with me!


Add Responsive Footer

I would like to work on this, assign this to me!

I would like to make this footer of the page


test/e2e: Add the node selector Metering test installation higher up in the test table.

This test is causing frequent e2e flakes as we're adding this custom testing label
to the available sets of nodes in the prior to firing off any metering installations.
The result is that all of the metering installations fight for their pods to be scheduled,
which is fine as the machineautoscaler will provision new machines. With this node selector
test, that's problematic as the new machines that the machineautoscaler provisions will not
have the custom testing node label, so pods will never schedule.

Is it actually treated as an ordered list?

Is it actually treated as an ordered list?

Nope - I'm just going to disable this test for the time being once I have time to fix it.
    --- FAIL: TestManualMeteringInstall/ValidHDFS-ValidNodeSelector (1215.74s)
        metering_manual_install_tests.go:89:
            	Error Trace:	assert.go:112
            	            				metering_manual_install_tests.go:89
            	            				main_test.go:320
            	Error:      	Received unexpected error:
            	            	error waiting for metering pods to become ready: the pods failed to report a ready status before the timeout period occurred: timed out waiting for the condition
            	Test:       	TestManualMeteringInstall/ValidHDFS-ValidNodeSelector
            	Messages:   	expected there would be no error

/retitle test/e2e: Disable the node selector e2e test by default.


Persist search results

Summary
After this change, when you switch from the search results tab to added classes or map and back, it keeps the search results up. I also made queryWebsoc cache its results, so doing a search with the same parameters is faster.
Test Plan
Make some searches, switch to other tabs and back, check that the search results are still up.
Issues
Closes #124

I think a lot of these commits are from me using this branch instead of fix-warnings by accident. Most of the real changes are in the commits with messages "made queryWebsoc() return json body..." and "moved state of RightPane to RightPaneStore"

#239 is completed. Resolve the conflicts and you should be good to go! Check in with @kartik-bhagatwala if you have any questions about the ad banner stuff.

The cache is in JS memory, so it gets cleared every time they open the page or refresh. I don't see how having new enrollment data on every search is helpful because I can't think of why you would need the data more accurately than the number when you started your session. Can you elaborate on that use case further?

Can you elaborate on that use case further?

Scenario
Today's the day of your enrollment window.   Error: this class is full. What? AntAlmanac says there are still spots open.
Explanation
Some classes fill up quick during the enrollment period. It's a really bad user experience if AntAlmanac's numbers and websoc don't match up. We'd lose users' trust. I don't want people to have that thought in the back of their head - "is the data on AntAlmanac reliable?". They shouldn't  feel the need to check WebSoc to verify enrollment numbers.
Sure they could refresh the page but that's not great ux. Calling the API isn't time expensive, so each time they search for a class, it should be pulling the latest data from websoc.


chore(ci): fix flakiness, misc improvements

venv contains python. Caching whole venv instead of just pip cache means you are backing up python which is problematic and is probably causing python not being found randomly in the smoke tests. If it is causing issues with smoke tests it would also cause issues with metadata-ingestion so removing that too.
e.g. https://github.com/datahub-project/datahub/actions/runs/4433850334/jobs/7779664856 where log says
+++ dirname ./smoke-test/run-quickstart.sh
++ cd ./smoke-test
++ pwd
+ DIR=/home/runner/work/datahub/datahub/smoke-test
+ cd /home/runner/work/datahub/datahub/smoke-test
+ python3 -m venv venv
Error: [Errno 2] No such file or directory: '/home/runner/work/datahub/datahub/smoke-test/venv/bin/python3': '/home/runner/work/datahub/datahub/smoke-test/venv/bin/python3'

Python not being found is really odd as we have a setup python step. It is probably the venv cache after that which is messing things somehow.
Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Also it seems strange that we've seen issues in smoke test but not with metadata ingestion yet. Any ideas why that could be?


Add homebox to similar projects

Refs:

https://github.com/progmaticltd/homebox

Completed with 9b19044


Update workflows

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (011e339) to head (fb7ef47).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #191   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           68        68
  Lines         1453      1453
  Branches       156       156
=========================================
  Hits          1453      1453

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


linthesia: use latest SDL2_ttf; SDL2_ttf_2_0_15: remove

Description of changes
linthesia is the only user of SDL2_ttf_2_0_15, so update it to work with SDL2_ttf, then remove SDL2_ttf_2_0_15.
Things done
Have verified that the garbled text issue is resolved.

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Thank you.
Could we perhaps update to an unstable commit? Looks like some other minor things changed; [compare].
(Also, I need to add myself to maintainers for this soon, probably in another PR, sorry if I was a bit hard to track down.)


Warning: Using UNSAFE_componentWillReceiveProps in strict mode

I keep getting the following error:
index.js:1 Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://fb.me/react-unsafe-component-lifecycles for details.

Move data fetching code or side effects to componentDidUpdate.
If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state

Please update the following components: BootstrapTable, BootstrapTableContainer, DataProvider

Facing the same issue, any updates on progress?

I have the exact same issue. Any updates?

Same here, help

Same here. Love this table. Thank you.

Same here!

Please update this :(

Same here!

@AllenFang have you seen the messages ?

same here

same :(

Same here

Hello Any Update on this?

same here.. :(

nothing yet?

Well it's a well-known issue, its either get fixed or the library goes to deprecation

Same here, expecting to hear about it

Also facing the same issue here... Seems like deprecated v1 is more production trustable at this point...

Same heeerreeee

+1

+1

Same issue

same issue here

Looks like this is not supported any more.

Looks like this is not supported any more.

+1

+1

My Solution : let's try remove <React.StrictMode> from index.js

@AllenFang any update here? ty

https://github.com/react-bootstrap-table/react-bootstrap-table2/issues/1056 - I found this PR which was raised but I think the issue still persists. I too am facing the same issue

I use "react-bootstrap-table-next": "^4.0.3" the issue still exists. Is there any plan to fix?
Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://reactjs.org/link/unsafe-component-lifecycles for details.

Move data fetching code or side effects to componentDidUpdate.
If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://reactjs.org/link/derived-state

Please update the following components: BootstrapTable, BootstrapTableContainer, DataProvider, SearchBar, SearchProvider, SortProvider, ToolkitProvider

Same problem here as well. Any updates?

+1 same issue

+1 same issue.

+1 same issue

+1 same issue

+1

+1

+1

+1

+1

It has been more than a year already, any update on this?

+1

Same here, any Update?

+1

+1

+1

+1

+1

+1

+1

+1

+1 same issue

+1 same issue

+1

same issue facing

same issue

joining the sad train, +1, lib was by far the best, may still be, seems like its not supported anymore, last update 2 years ago.

+1 best lib

same here!

same here!

+1 here

+1

+1

+1 still here

As of React 16.8, it is recommended to change from a class structure to a hook structure. Yes, the current package.json for this project uses React 16.4.0, (Should be changed to React ^16.4.0 IMO), but should work with the new hook structure in theory, as 16.8.0 is not a breaking change.
ComponentWillUpdateProps has been deprecated. Please see this blog for some potentially useful information about using useEffect(() => {},[]} as a replacement.
The example from the blog:

// Gets called on mount all the time
React.useEffect(() => {
  // Side-effect logic gets executed any update happens to the component

  // The return statement is for componentWillUnmount
  return () => console.log('component will unmount')
}, []);

// ONLY trigger when a certain state or prop values gets updated

React.useEffect(() => {
  // Side-effect logic gets executed when values in array
  // only get updated
}, [arg]);

It should be noted that react hooks only work within react functional components.

The main maintainer guy seems to have stopped writing code altogether :-(


fix: Remove AWS IAM auth leftovers

As a follow-up for #1203, any reference to AWS access/secret key, and role ARN is being removed.

Super nice, thanks so much!


Enhancement: add allowDowngrade capability to UseLatestReleasesMojo, UseNextReleasesMojo, UseNextVersionsMojo

The three mojos in the summary did not have the "allowDowngrade" capability. Adding it for consistence.

@slawekjaranowski please review


add instance segmentation example for voc dataset from icedata

🚀 Feature

Motivation

I thought icedata.pets are not practical enough for users and
hope InstanceSegmentationData.from_voc  supports icedata compatibilities more.
Pitch

datamodule = InstanceSegmentationData.from_voc(
    provider='icedata'
    val_split=0.1,
    batch_size=1,
)

Alternatives

Additional context

I currently write code below for using icedata.voc.
data_dir = icedata.voc.load_data()

datamodule = InstanceSegmentationData.from_icedata(
    train_folder=data_dir / "JPEGImages",
    train_ann_file=data_dir / "Annotations",
    parser=icevision.parsers.VOCMaskParser,
    train_parser_kwargs={
        "class_map": icedata.voc.class_map(),
        "masks_dir": data_dir / "SegmentationObject",
    },
    val_split=0.1,
    batch_size=1,
)

But icevision has to solve some issues before make integration here.
I reported 2 issues in their repo.

https://github.com/airctic/icevision/issues/1072
https://github.com/airctic/icevision/issues/1073

Could you add new integration or example for icedata.voc in InstanceSegmentation after they solve that issues?

Hi @joowon-dm-snu Thanks for the question. Did you see the from_voc method? Here is it's docstring: https://lightning-flash.readthedocs.io/en/stable/api/generated/flash.image.instance_segmentation.data.InstanceSegmentationData.html#flash.image.instance_segmentation.data.InstanceSegmentationData.from_voc
It uses icevision internally so may still have the issues you linked, but might be worth a try :smiley:
Hope that helps!

@ethanwharris  thanks for reply. Your suggestion runs well and much more clear :)
here's memo for using icedata.voc directly
import icedata
from flash.image import InstanceSegmentationData

data_dir = icedata.voc.load_data()

datamodule = InstanceSegmentationData.from_voc(
    icedata.voc.data._CLASSES,
    train_folder=data_dir / "JPEGImages",
    train_ann_folder=data_dir / "Annotations",
    train_target_folder=data_dir / "SegmentationObject",
    val_split=0.1,
    batch_size=8,
)


baetyl-1547 compatible

Codecov Report

Merging #420 (7235451) into master (6544e15) will decrease coverage by 0.11%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #420      +/-   ##
==========================================
- Coverage   65.17%   65.05%   -0.12%
==========================================
  Files          91       91
  Lines        6630     6642      +12
==========================================
  Hits         4321     4321
- Misses       1688     1699      +11
- Partials      621      622       +1

Impacted Files
Coverage Δ

api/sync.go
25.45% <0.00%> (-3.12%)
:arrow_down:

Continue to review full report at Codecov.

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


SecurityInsights: ThreatIntelligence (TAXII) Data Connector API not round trip consistent

The taxiiLookbackPeriod is defined as a "date-time" format in Swagger, which represents a RFC3339 date time. Whilst, on return it is in format "01/02/2006 15:04:05".
The pollingFrequency is defined as an enum. When specifying it using one of the enum value (a string), it returns an integer (0, 1, 2) in response.
The issue exists for both TI and TI TAXII data connector resources, at least for 2022-10-01-preview.

This is killing the python SDK:
Unable to deserialize response data. Data: 01/01/1970 00:00:00, iso-8601

Thus I would like to encourage you to go for ISO-8601 instead of RFC3339, as ISO-8601 is a subset of RFC3339.

Service has fixed this API, closing it.


ValueError('cannot mmap an empty file')

FileExistsError: [Errno 17] File exists: '/000000_shard_access_times'
During handling of the above exception, another exception occurred:
InstantiationException: Error in call to target 'diffusion.datasets.laion.laion.build_streaming_laion_dataloader':
ValueError('cannot mmap an empty file')
full_key: dataset.train_dataset
ERROR:composer.cli.launcher:Rank 0 crashed with exit code 1.
Waiting up to 30 seconds for all training processes to terminate. Press Ctrl-C to exit immediately.
Global rank 0 (PID 34542) exited with code 1
ERROR:composer.cli.launcher:Global rank 0 (PID 34542) exited with code 1
I'm wondering why it need to write in the root directory?, it seems set self.local to empty, please help

Apologies for the delay! This might be from an ungraceful termination in the streaming process. Did you have have a previous run that failed?
Could you try streaming.base.util.clean_stale_shared_memory? This should remove any corrupted data


Check node version

Just an idea to check the node version as well. If you don't see that as a task for this project, feel free to decline it :slightly_smiling_face:
If you accept it, I would write a test for it later.
node 16
$ nvm use 16
Now using node v16.20.0 (npm v8.19.4)
$ npm run dev current

><EMAIL_ADDRESS>dev
> tsx ./src/cli.ts current

Your node version (16) is no longer supported since 2023-09-11.
All dependencies retrieved successfully. There are no deprecated dependencies.

node 18
$ nvm use 18
Now using node v18.20.2 (npm v10.5.0)
$ npm run dev current

><EMAIL_ADDRESS>dev
> tsx ./src/cli.ts current

Your node version (18) is supported until 2025-04-30.
All dependencies retrieved successfully. There are no deprecated dependencies.

Good idea!

I'm glad you like the idea. Okay, I've added a rudimentary test.

Maybe instead of just comparing major version, compare the entire version using semver?

Okay, thanks!


Migrate spring data cosmosdb sample

This pr migrates a sample of spring-data-cosmosdb to sdk/cosmos/azure-spring-data-cosmosdb/samples.

Due to the parent of sample project is org.springframework.boot: spring-boot-starter-parent, currently no verion tags are added in the pom.xml.

Hi @kushagraThapar , thanks for reminding me, I will rebase from master and re-push this PR after the src code PR gets merged

Close this PR for the commit history hash is different from the master


fix(types): handle readonly array correctly

The author should do the following, if applicable
My apologies that JSONParsed didn't convert ReadonlyArray type correctly. Types of methods disappeared

[x] Add tests
[x] Run tests
[x] bun run format:fix && bun run lint:fix to format the code
[ ] Add TSDoc/JSDoc to document the code

@m-shaka
Thanks! Merging now.


How to build TelloVideoDecoder dll

Hi @comoc could you please provide instructions on how to build the TelloVideoDecoder.dll
Does ffmpeg need to be built separately, if not, could you point to the files used.
I eventually got stuck at libavutil/avconfig.h not found during the build process in Visual Studio

Hi @joshferns,
In my case, I followed this document to build and install FFmpeg 64 bit version separately.
https://www.ffmpeg.org/platform.html#Native-Windows-compilation-using-MinGW-or-MinGW_002dw64
And you will need to choose the target platform as x64 in Visual Studio.

Thank you,

Thanks for this.


docs: add filedump docs

docs: add filedump docs
ref: https://github.com/cloudberrydb/filedump

Change logs

Describe your change clearly, including what problem is being solved or what document is being added or updated.

Contributor's checklist
Here are some reminders before you submit your pull request:

Make sure that your Pull Request has a clear title and commit message. You can take the Git commit template as a reference.
Sign the Contributor License Agreement as prompted for your first-time contribution (One-time setup).
Learn the code contribution and doc contribution guides for better collaboration.
Make sure that your changes deployment preview is successful.
List your communications in the GitHub Issues or Discussions (if has or needed).
Feel free to ask for the @cloudberrydb/doc team or other people to help review and approve.

Thanks for your great work! @TomShawn
Only two comments. FYI.


Virtual cockpit

hi guys
i am a big fan to orbiter
my dream is to build a physical virtual cockpit for XR2 and Delta glider iv …
i need to control every button on the panels by physical button
i am not talking here about hardware i am talking about there is no setting in the launcher that i can maping controls via external joystick buttons for example
i need more axis trans, rot, hover engines, rev .... to control via joystick
i need to connect more than one joystick
i need digital outputs that i can use to indicator leds
sorry about my english :)
hope to hear from u soon

Find existing solutions from Orbiter Forum.


SyntaxError

some error
  File "termgraph.py", line 163
    sys.stdout.write( f'\033[{color}m' ) # Start to write colorized.
                                     ^
SyntaxError: invalid syntax

i fix it by remove all "f"
sys.stdout.write( '\033[{color}m' )

@MGF15
What is the version of Python you are using?
"f-strings" are only supported Python 3.6 or newer.
If you are using 3.6 or newer, I want to reproduce this err.
So, please tell me the source code you ran.

i'm on python 2.7.6 & python 3.4.3

yes it's about "f-strings" .
thanks


int[] syntax sugar for array(int) constructor

The purpose of this feature request is to support the same syntax sugar that TypeScript has for Array type definition which is T[]. When user writes T[] in type position in AskScript, the parser should interpreter it as array(T) where T like int
Dear new contributor,
If you have any questions on how to start, please write a comment with a tag: @czerwinskilukasz1 or @mhagmajer, or join our Discord Community and let us know there. We will be very happy to help you start! :)
Cheers,
Łukasz (@czerwinskilukasz1)
AskQL Core Developer

We need to add here more description, it is hard to find out the scope of the task and not clear where to begin @mhagmajer

The scope of this task is to adapt the pegjs parser to accept the new 'int[]' syntax in addition to the current one.
As for the details of the syntax change proposal, we need to ask for Marcin's explanation and examples.

I could take care of that. I understand it is Peg.js related - I browsed code. However, I need some tips and methods to test it well.

@czerwinskilukasz1 can you help here?

I am taking it

Great, congrats, Filip :)
Feel free to ask questions here or contact with us on our Discord channel.

Filip, by the way, didn't you want to work on https://github.com/xFAANG/askql/issues/52 instead? ;) @Fifciu

Nope. However, as both are about synthetic sugar - maybe it will be my next step :)

Cool :)

Taking over!

Cool, @Tuhaj

Hi @Fifciu , would you like to take a look at this issue? :)

@Tuhaj , it's been a couple of weeks since you were assigned.  Any thoughts or progress on this one?


Move row_constructor vector function to special form

Currently row_constructor cannot be expressed with a function signature and thus needs to be moved to special form.

@kgpai Krishna, is there anything left to do here? If not, should we close this issue?

We can close this.


docs: add missing install on webpack

Hi @DonNicoJs,
I added this change due to when I use it, it sent me some error on compiling using the webpack

Hi @DonNicoJs,
Any issue with this pull request?


Add support for legible MIDI files 🎼

Issue: The repo appears to contain binary files in the git tree. 😞
Task: Add support for text based legible MIDI files to replace binary blobs! 😸

I am not really sure why the existing binary files are an issue, I will however try and look into supporting MIDI : )


[Snyk] Security upgrade org.apache.jena:jena-dboe-storage from 4.9.0-SNAPSHOT to 4.10.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

jena-tdb2/pom.xml

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

509/1000  Why? Has a fix available, CVSS 5.9
Improper Input Validation SNYK-JAVA-ORGAPACHECOMMONS-5901530
org.apache.jena:jena-dboe-storage:  4.9.0-SNAPSHOT -> 4.10.0
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Improper Input Validation

Checkmarx One – Scan Summary & Details – 5e1027fa-de28-4f2a-8905-0766276e411c
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2023-36478
Maven-org.eclipse.jetty:jetty-http-10.0.15
Vulnerable Package

CVE-2023-43646
Npm-get-func-name-2.0.0
Vulnerable Package

CVE-2023-45133
<EMAIL_ADDRESS>Vulnerable Package

CVE-2023-36479
Maven-org.eclipse.jetty:jetty-servlets-10.0.15
Vulnerable Package

CVE-2023-40167
Maven-org.eclipse.jetty:jetty-http-10.0.15
Vulnerable Package

CVE-2023-42503
Maven-org.apache.commons:commons-compress-1.23.0
Vulnerable Package

CVE-2023-44270
Npm-postcss-8.4.21
Vulnerable Package


feat(api,builder,bundle)!: Rewrote almost all

Create useful methods for client and builder
Rewrote almost all internal api
Rewrote as Symfony bundle

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

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

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


Table of Contents is collapsed with no hint that it could be expanded

I did eventually click on it but there might be enough users who will not find out that they can expand the table of contents.
I actually looked first at the top of the main area for a table of contents, much like in Wikipedia.
BTW: Should https://github.com/Debian/debiman/issues/72 be closed?

This is because of display: block on the summary and details elements: https://github.com/Debian/debiman/blob/38831b8b322b5818446765c3b7bd335b4974f425/assets/style.css#L251-L253
This line has been there since the initial commit, and I’m not sure why it was added.
When you change it to display: list-item, a drop-down arrow appears (at least in Chrome, not sure about Firefox).
I’m not sure if we can just change it, or if that will break anything else.

Issue #72 is related, but not obsolete. The list of languages is still not collapsed, but always displayed in full.


Fix error on string to array conversion

So you were converting the header variable into an array but not using it, which caused an error on a wrapper I'm building on toy of this library.
I'd recommend a linter, as this error would have been shown right away (arr was declared but never used).
A great linter is ESLint, you can get some really great style consistency and avoid obvious typos and errors with it.
Cheers

Sweet, thanks for spotting this one.


Remove deprecated Cassandra clients

Removes deprecated clients. Renames the cassandra2 module to cassandra.
closes #794

:+1:  Looks good to me.


Hook Detours

Don't think this is necessary for Safety at least for now. Someone can implement this in their own plugins


Improve codebase documentation

Improve the documentation of both the client and onchain codebase

Document important functions, their parameters, and their return values
Replace variables with type of any with the correct data type on the client codebase

@princeibs I'd love to work on this

@princeibs can I work on this?

I'll hop on this one

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hello, I am Ikem Peter contribute to over 4 projects on this platform,
Can I take this issue

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a technical writer
How I plan on tackling this issue
I will document everything you added in the description

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
@princeibs I'd love to work on this
How I plan on tackling this issue
I'd review the codebase and write a detailed documentation for each function.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
i'm a full stack developer, worked on seversl similar projects

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
love to work on this

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
i would
How I plan on tackling this issue
i would

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a frontend developer with experience in React.js,Cario, TypeScript, and various UI frameworks such as Mantine. My background in TypeScript and React.js provides a strong foundation for understanding and enhancing client-side codebases. Additionally, my familiarity with handling complex data types and UI components allows me to effectively document and refine both client and on-chain codebases.
In my previous projects, I've worked extensively with TypeScript, which has honed my skills in type inference and ensuring code accuracy. This experience is directly relevant to the task of replacing variables with the correct data types, as TypeScript's type system helps prevent bugs and enhances code readability. Moreover, my background in React and TypeScript equips me with the knowledge to properly document functions, their parameters, and return values, ensuring that both developers and future maintainers have a clear understanding of the code.
How I plan on tackling this issue
Document Important Functions:
Identify Key Functions: Start by reviewing the codebase to identify the most critical functions. Focus on those that are frequently used, complex, or have significant impact on the application's behavior.
Document Parameters and Return Values: For each key function, document the purpose of the function, its parameters, and return values. Use clear, concise language and include examples if necessary. This documentation should be added directly in the codebase as comments or in a separate documentation file.
Utilize TypeScript: Leverage TypeScript’s type annotations to provide clear information about the types of parameters and return values. This reduces ambiguity and helps with both documentation and development.
Replace any with Correct Data Types:
Audit the Codebase: Conduct a thorough review of the client codebase to find instances where any is used. This includes checking function signatures, variable declarations, and component props.
Determine Correct Data Types: Analyze the code and determine the correct data types for each any usage. This may involve understanding the data being handled and how it is used throughout the application.
Refactor and Test: Replace any with the appropriate types. Ensure that the refactoring does not introduce new bugs by running existing tests and adding new ones if necessary.
Update Documentation:
Consistent Documentation Format: Adopt a consistent format for documenting functions and their types across the codebase. This could be using JSDoc or other documentation tools that integrate well with TypeScript.
Review and Improve: Regularly review the documentation for accuracy and completeness. Update it as the code evolves to ensure it remains useful and relevant.
By leveraging my expertise in TypeScript and React, I can effectively enhance the clarity and usability of both the client and on-chain codebases. My approach ensures that functions are well-documented and type safety is enforced, leading to a more maintainable and robust codebase.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
i'm a technical writer in the web3 space please let me work on this
How I plan on tackling this issue
I will document everything you added in the description
Document Functions: Add clear comments to key functions, detailing their purpose, parameters, and return values.
Refine Types: Replace any types in the client codebase with accurate TypeScript types to enhance type safety and clarity.
Update README: Ensure the README files reflect these improvements, providing an overview of changes and usage instructions.
Please let me work on this

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a passionate and results-driven web developer, currently deepening my knowledge in web3 technologies, Cairo, and open-source development through Dojo Coding. My skill set includes expertise in JavaScript, React, HTML, CSS, C# with .NET Entity Framework, and more. I also have experience with tools like Git, GitHub, SQL Server, and Postman. My focus has been on building solid web applications, from task lists to full-fledged CRUD systems, with front-end, back-end, and database integration.
This will be my first contribution to the open-source ecosystem, and I am excited to learn and collaborate on innovative projects, particularly those involving Cairo.
How I plan on tackling this issue
First, I would review the client code and the onchain environment to understand how the key functions work. Then, I would start documenting each function, clearly describing its parameters and return values. As I go along, I would replace any any type variables with the correct data types, ensuring everything is properly typed. Finally, I would do a review to make sure the documentation and types are accurate and clear before committing and opening a Pull Request.


Noah emke contribution post

Added my contribution post

The devcade logo doesnt look great on a white background with the white text, but id consider that non-blocking. feel free to submit another PR if youd like to fix this


Bundle HTML with exec?

Currently compiling the executable makes it unmovable:
./mmsd
panic: html/template: pattern matches no files: `templates/*`

goroutine 1 [running]:
html/template.Must(...)
	/usr/local/go/src/html/template/template.go:372
main.main()
	/lib/go-mms/cmd/mmsd/main.go:29 +0x2de

Such that one must be in the go-mms folder to start the mmsd

https://github.com/rakyll/statik looks like a way to go

@mpejcoch Missing assignee. You on this?


tracking (internal and outbound)

[ ] which section are they choosing story from?
[ ] header join newsletter button click
[ ] which top nav do they click?
[ ] social icon sidebar clicks
[ ] topics sidebar choice
[ ] cta clicks
[ ] archives: did they use a filter
[ ] archives: did they click a tag
[ ] archives: did they use search


Installer should wait for status hook

If there's a status hook defined in the manifest, the installer should call it after the user application has been installed and wait until it succeeds before declaring the installation success.

Released in 6.1.24, 7.0.1.


These steps are not very discoverable.

I'm someone who doesn't use Git often. (My employer has decided to use TFVC instead.) Consequently, when I cloned a repo to my laptop I spent a long time trying to find a way of opening it in VS 2017, without opening the repo folder. I'm glad that you have the instructions under the heading, "Open a solution in Visual Studio from a cloned repo". But those steps are not easily discoverable. I'm glad I found this article, but I wish there was a way, through a menu in VS 2017 to do the same thing.

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

ID: 8b8a5b68-909f-126d-5f83-4659e0f55b85
Version Independent ID: f71ca2b9-c00d-0b2b-34bc-63d11b3576db
Content: Clone an existing Git repo
Content Source: docs/git/tutorial/clone.md
Service: unspecified
Product: devops
GitHub Login: @steved0x
Microsoft Alias: sdanie

@rfalanga Thank you for the feedback and I'm glad you were able to find the section that would help you. I'll see if I can make this more discoverable in the documentation (I may be able to add something here, and if you want. you could file a feature request with the product team to see if they can add this: I wish there was a way, through a menu in VS 2017 to do the same thing.

Thank you very much, Steve! I'll go to the feature request and add that now.


kernel_2d_fixed giving false assertion errors

Actual behavior

boost::gil::detail::kernel_2d_fixed gives false assertion errors during its initialization.
Expected  behavior
A 2D kernel with provided values and center co-ordinates should be created

C++ Minimal Working Example
https://wandbox.org/permlink/Q5uuWCLJo5eBH3Ai

#include <boost/gil.hpp>
namespace gil = boost::gil;
int main
{
    // your code
    std::vector<float> vec(25, 1.0f);
    gil::detail::kernel_2d_fixed<float, 5> kernel(vec.begin(), 0, 0); // Gives error
}

Environment

Compiler version: gcc 11.1.0
Version: Boost 1.76.0

A simple workaround for this problem is here. However, I think this issue can be dealt in a more reliable/generic manner.


missing namespace in several resources

hello
tried this chart using ArgoCD, getting these error
InvalidSpecError
Namespace for atlantis /v1, Kind=Service is missing.
3 minutes ago (Tue Apr 11 2023 17:20:01 GMT-0400)
InvalidSpecError
Namespace for atlantis /v1, Kind=ServiceAccount is missing.
3 minutes ago (Tue Apr 11 2023 17:20:01 GMT-0400)
InvalidSpecError
Namespace for atlantis apps/v1, Kind=StatefulSet is missing.
3 minutes ago (Tue Apr 11 2023 17:20:01 GMT-0400)
InvalidSpecError
Namespace for atlantis extensions/v1beta1, Kind=Ingress is missing.
3 minutes ago (Tue Apr 11 2023 17:20:01 GMT-0400)
InvalidSpecError
Namespace for atlantis-tests /v1, Kind=ConfigMap is missing.
3 minutes ago (Tue Apr 11 2023 17:20:01 GMT-0400)
InvalidSpecError
Namespace for atlantis-webhook /v1, Kind=Secret is missing.
3 minutes ago (Tue Apr 11 2023 17:20:01 GMT-0400)

would this project be open to namespace value configured via values.yaml?
thank you

@blbradley
I would think we would just default to
namespace: {{ .Release.Namespace }}

i was able to set the namespace through an ArgoCD parameter, upstream guidance from Helm suggests that chart do not need to set the namespace


could not get package information for the dependencies which have private repositories

Hello Team,
I am getting error in ORT while scanning that, 'could not get package information for the dependencies' This error is for those who have the private repositories which can not be accessed by everyone. What is the solution in such a case? is there any configuration needed to be added in the curation file for the same?

Hi @maanasiDivekar, depending on whether the private repository is accessed via HTTP(S) or SSH, you either need to configure credentials via a standard .netrc file, or by running an SSH agent. Regarding the .netrc file, you can see e.g. from the Jenkinsfile how to write a username and password to it.

Hi @maanasiDivekar, depending on whether the private repository is accessed via HTTP(S) or SSH, you either need to configure credentials via a standard .netrc file, or by running an SSH agent. Regarding the .netrc file, you can see e.g. from the Jenkinsfile how to write a username and password to it.

How does it work for repositories which have HTTP and not HTTPS. I was trying to scan some open-source projects using ORT
(Example: maven 3.6.3, spring-data-jdbc-1.0.11.RELEASE, terraform-master) but most of the time I got error as "com.here.ort.analyzer.managers.utils.MavenSupport - Unable to find 'org.apache.velocity:velocity:jar:sources:1.5' in any of [http://people.apache.org/repo/m2-snapshot-repository, https://repo.maven.apache.org/maven2]".

Let me try to clarify some possible misunderstandings here:

How does it work for repositories which have HTTP and not HTTPS.

Authentication-wise, there's no difference between HTTP and HTTPS. If you are talking about a source code repository (like a Git repository), then authentication needs to be configured via .netrc as described above. However, if you are talking about an artifact repository (like Artifactory) where Maven retrieves dependencies from, then authentication needs to be configured via your ~/.m2/settings.xml file.

What needs to be done for such cases?

That said, your above errors do not look like authentication errors. It more looks like ORT could not download the source code of the dependencies because the package's meta-data does not tell where from to download ("No VCS URL provided", "No source artifact URL provided"). In that cause you need to manually fixup the incomplete meta-data with so-called curations.

Hello, @sschuberth  Thank you so much for the clarification. I did check for the curations file and I am able to add the required metadata.
But, as I am scanning a few of the most commonly used open-source projects (like the spring framework)  via ORT,  the expectation is ORT to scan such projects without any need for any humans intervention.  Is there any alternative to do this process automated?

It's not possible to do this without human intervention if no one else has corrected that broken meta data before.
However, sharing such curations for broken meta data is exactly one of the purposes of the ClearlyDefined initiative, and ORT can leverage curations from ClearlyDefined if you pass the --clearly-defined-curations option to the analyzer.
So, if a curation has been created once (either on ClearlyDefined, or in ORT's own format), then all future scans of that package will run through without human intervention.

@maanasiDivekar, has your question been answered, and can this issue be closed?


Components/Input

when you find a compilation error, it bugs, you have to delete it and use it again to remove it. gives the following message in console:
Warning: Prop id did not match. Server: "nextui-input-egfefba1" Client: "nextui-input-d063o0if"
input
Styled.input
label
Styled.div
div
Styled.div
div
Styled.div
Input<@webpack-internal:///./node_modules/@nextui-org/react/esm/input/input.js:41:54
main
div
Home@webpack-internal:///./pages/index.js:24:72
MyApp@webpack-internal:///./pages/_app.js:38:21
ErrorBoundary@webpack-internal:///./node_modules/next/dist/compiled/@next/react-dev-overlay/client.js:8:20584
ReactDevOverlay@webpack-internal:///./node_modules/next/dist/compiled/@next/react-dev-overlay/client.js:8:23123
Container@webpack-internal:///./node_modules/next/dist/client/index.js:359:24
AppContainer@webpack-internal:///./node_modules/next/dist/client/index.js:793:20
Root@webpack-internal:///./node_modules/next/dist/client/index.js:915:21
See more info here: https://nextjs.org/docs/messages/react-hydration-error

Hey @Carlos6a have you implemented the CssBaseline.flush()? https://nextui.org/docs/guide/nextui-plus-nextjs

Hi, I run into the same issue in my project. It also appears when I run the nextjs example, see below:

react-dom.development.js?61bb:67 Warning: Prop `id` did not match. Server: "nextui-input-label-ak3qvtbo" Client: "nextui-input-label-1m9noum5"
    at label
    at Styled.label
    at div
    at Styled.div
    at eval (webpack-internal:///./node_modules/@nextui-org/react/esm/input/input.js:42:7)
    at div
    at Styled.div
    at Container (webpack-internal:///./node_modules/@nextui-org/react/esm/container/container.js:33:3)
    at div
    at Home
    at ThemeProvider (webpack-internal:///./node_modules/@nextui-org/react/esm/theme/theme-provider.js:35:10)
    at MyApp (webpack-internal:///./pages/_app.js:22:24)
    at ErrorBoundary (webpack-internal:///./node_modules/@next/react-dev-overlay/lib/internal/ErrorBoundary.js:26:47)
    at ReactDevOverlay (webpack-internal:///./node_modules/@next/react-dev-overlay/lib/internal/ReactDevOverlay.js:86:23)
    at Container (webpack-internal:///./node_modules/next/dist/client/index.js:160:5)
    at AppContainer (webpack-internal:///./node_modules/next/dist/client/index.js:648:24)
    at Root (webpack-internal:///./node_modules/next/dist/client/index.js:784:25)

Hey @jesusalber1 we are working on that 🙌🏻

Hey @jesusalber1 @Carlos6a a workaround for solving this until we release the new version is by setting your own id to the Input component, something like this

<Input id="email" placeholder="Enter your email" />

Hope it helps 🙌🏻

Hey @jesusalber1 @Carlos6a 🙌🏼 ,The new version was released, please try this in case it has not been resolved we reopen the issue, thank you very much! https://github.com/nextui-org/nextui/releases/tag/v1.0.2-beta.4

Hey there 👋🏻 ,
Thanks @jrgarciadev for this amazing UI lib! We ran into this issue today and it's still showing an error stating the Prop id isn't matching:
Warning: Prop `id` did not match. Server: "react-aria6856402524-19" Client: "react-aria4308185822-2"
Adding the id prop didn't help, it seems to be conflicting with the label prop for some reason?
This works:
<Input
  id="hey"
  type="email"
/>

This doesn't:
<Input
  id="email"
  type="email"
  label="Email"
/>

Hey @Gomah thank you for using it 🙌🏻
Did you include the NextUIProvider in your main file? https://nextui.org/docs/guide/getting-started#next.js

Hey @Gomah thank you for using it 🙌🏻
Did you include the NextUIProvider in your main file? https://nextui.org/docs/guide/getting-started#next.js

Yes, we followed the installation guide carefully, actually if you run the example from the nextui repo: https://github.com/nextui-org/nextui/tree/main/examples/create-next-app
Both label & labelPlaceholder props are prompting errors on the mismatch node: https://github.com/nextui-org/nextui/blob/main/examples/create-next-app/pages/index.js#L57

Hi, @Gomah I got the same issue as you.
I think the problem is with the id of the label, we can pass the input id through the prop, but when using the label, the id is automatically generated by useLabel.
With some research, I found out that SSRProvider may not support the react strict mode yet, I just disabled the strict mode for now.
Possibly it can be refactored by using new feat of React 18, such as React.useId (linked below).

https://github.com/adobe/react-spectrum/issues/2231#issuecomment-905824601
https://github.com/reactwg/react-18/discussions/111

Same issue in Dropdown.Trigger and Dropdown.Button, a workaround is setting an id to the Button or Trigger's child.

Running into this issue with the Table component as well.

I'm having issue with Input.Password
Warning: Prop id did not match. Server: "react-aria-1" Client: "react-aria-2"
at label
at Styled.label
at div
at Styled.div

Having same issue as well, with Navbar's links:
Warning: Prop `id` did not match. Server: "react-aria-1" Client: "react-aria-2"
li
Styled.li
NextUI.NavbarItem
NextUI.NavbarLink
LinkComponent
ul
Styled.ul
NextUI.NavbarContent
NavLocaleLinks
div
Styled.div
nav
Styled.nav
NextUI.Navbar

And if second link is active:
Warning: Prop `className` did not match. Server: "nextui-c-dIWzTP nextui-c-PJLV nextui-c-dIWzTP-iXPvBl-color-text nextui-c-dIWzTP-isWIbj-animated-true nextui-c-PJLV-gulvcB-isFocusVisible-false nextui-c-dIWzTP-icTVmtU-css nextui-link nextui-navbar-link" Client: "nextui-c-dIWzTP nextui-c-PJLV nextui-c-dIWzTP-iXPvBl-color-text nextui-c-dIWzTP-isWIbj-animated-true nextui-c-PJLV-gulvcB-isFocusVisible-false nextui-c-dIWzTP-ihuGhNP-css nextui-link nextui-navbar-link"
a
Styled.a
NextUI.Link
li
Styled.li
NextUI.NavbarItem
NextUI.NavbarLink
LinkComponent
ul
Styled.ul
NextUI.NavbarContent

I tried putting manual id props on everything but didn't help.
On latest module versions possible.

I can confirm the issue with the navbar

Having same issue as well, with Navbar's links:
Warning: Prop `id` did not match. Server: "react-aria-1" Client: "react-aria-2"
li
Styled.li
NextUI.NavbarItem
NextUI.NavbarLink
LinkComponent
ul
Styled.ul
NextUI.NavbarContent
NavLocaleLinks
div
Styled.div
nav
Styled.nav
NextUI.Navbar

And if second link is active:
Warning: Prop `className` did not match. Server: "nextui-c-dIWzTP nextui-c-PJLV nextui-c-dIWzTP-iXPvBl-color-text nextui-c-dIWzTP-isWIbj-animated-true nextui-c-PJLV-gulvcB-isFocusVisible-false nextui-c-dIWzTP-icTVmtU-css nextui-link nextui-navbar-link" Client: "nextui-c-dIWzTP nextui-c-PJLV nextui-c-dIWzTP-iXPvBl-color-text nextui-c-dIWzTP-isWIbj-animated-true nextui-c-PJLV-gulvcB-isFocusVisible-false nextui-c-dIWzTP-ihuGhNP-css nextui-link nextui-navbar-link"
a
Styled.a
NextUI.Link
li
Styled.li
NextUI.NavbarItem
NextUI.NavbarLink
LinkComponent
ul
Styled.ul
NextUI.NavbarContent

I tried putting manual id props on everything but didn't help. On latest module versions possible.

I am facing same issue with the Navbar's link. But after dynamic export the Component with ssr: false this error is gone.
I export my component like this.
export default dynamic(()=>Promise.resolve(ComponentName), {ssr: false})

Same issue as well...
Warning: Prop `id` did not match. Server: "react-aria-1" Client: "react-aria-2"
    at p
    at li
    at Styled.li
    at eval (webpack-internal:///./node_modules/@nextui-org/react/esm/navbar/navbar-item.js:16:91)
    at Styled.NextUI.NavbarItem
    at ul
    at Styled.ul
    at eval (webpack-internal:///./node_modules/@nextui-org/react/esm/navbar/navbar-content.js:14:91)
    at div
    at Styled.div
    at nav
    at Styled.nav
    at eval (webpack-internal:///./node_modules/@nextui-org/react/esm/navbar/navbar.js:15:91)
    at MainNavbar
    at div
    at $f57aed4a881a3485$var$OverlayContainerDOM (webpack-internal:///./node_modules/@react-aria/overlays/dist/module.js:745:55)
    at $f57aed4a881a3485$export$178405afcd8c5eb (webpack-internal:///./node_modules/@react-aria/overlays/dist/module.js:709:21)
    at $f57aed4a881a3485$export$bf688221f59024e5
    at $704cf1d3b684cc5c$export$9f8ac96af4b1b2ae (webpack-internal:///./node_modules/@react-aria/ssr/dist/module.js:23:64)
    at __webpack_exports__.default.disableBaseline (webpack-internal:///./node_modules/@nextui-org/react/esm/theme/theme-provider.js:15:138)
    at MyApp (webpack-internal:///./pages/_app.tsx:42:27)
    at ErrorBoundary (webpack-internal:///./node_modules/next/dist/compiled/@next/react-dev-overlay/dist/client.js:8:20742)
    at ReactDevOverlay (webpack-internal:///./node_modules/next/dist/compiled/@next/react-dev-overlay/dist/client.js:8:23635)
    at Container (webpack-internal:///./node_modules/next/dist/client/index.js:70:9)
    at AppContainer (webpack-internal:///./node_modules/next/dist/client/index.js:216:26)
    at Root (webpack-internal:///./node_modules/next/dist/client/index.js:407:27)

Having same issue as well, with Navbar's links:
Warning: Prop `id` did not match. Server: "react-aria-1" Client: "react-aria-2"
li
Styled.li
NextUI.NavbarItem
NextUI.NavbarLink
LinkComponent
ul
Styled.ul
NextUI.NavbarContent
NavLocaleLinks
div
Styled.div
nav
Styled.nav
NextUI.Navbar

And if second link is active:
Warning: Prop `className` did not match. Server: "nextui-c-dIWzTP nextui-c-PJLV nextui-c-dIWzTP-iXPvBl-color-text nextui-c-dIWzTP-isWIbj-animated-true nextui-c-PJLV-gulvcB-isFocusVisible-false nextui-c-dIWzTP-icTVmtU-css nextui-link nextui-navbar-link" Client: "nextui-c-dIWzTP nextui-c-PJLV nextui-c-dIWzTP-iXPvBl-color-text nextui-c-dIWzTP-isWIbj-animated-true nextui-c-PJLV-gulvcB-isFocusVisible-false nextui-c-dIWzTP-ihuGhNP-css nextui-link nextui-navbar-link"
a
Styled.a
NextUI.Link
li
Styled.li
NextUI.NavbarItem
NextUI.NavbarLink
LinkComponent
ul
Styled.ul
NextUI.NavbarContent

I tried putting manual id props on everything but didn't help. On latest module versions possible.

I am facing same issue with the Navbar's link. But after dynamic export the Component with ssr: false this error is gone. I export my component like this. export default dynamic(()=>Promise.resolve(ComponentName), {ssr: false})

Navbar exported successfully. WORK. THANK YOU

Warning: Prop aria-labelledby did not match. Server: "react-aria-:R2r9cq:-bitcoin-market_cap_rank" Client: "react-aria-:Rbd5j9:-bitcoin-market_cap_rank"
This still happens in Table related components


unable to wire observable into MatTableDataSource

Bug, feature request, or proposal:
bug
What is the expected behavior?
MatTable should be able to accept an observable
What is the current behavior?
I keep getting type error
What are the steps to reproduce?
no project as of yet I was wondering whsat best practice is for wiring ngrx state into mattabledatasource
What is the use-case or motivation for changing an existing behavior?
bug
Angular CLI: 1.7.3
Node: 9.3.0
OS: win32 x64
Angular: 5.2.9
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cdk: 5.2.4
@angular/cli: 1.7.3
@angular/flex-layout: 5.0.0-beta.13
@angular/material: 5.2.4
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.6.2
webpack: 3.11.0

I have a material 2 table component that ran nicely with plain RxJS and typed Array.
So I took it to next level using NGRX
my redux ngrx state is working beautifully spreading my typed array thru the reducer into my ngrx state nicely
at the component level I have a container that propagates users$ using @Input() as input to my table component and I construct an empty MatTableDataSource at construction
container component
<app-table [users$]="usersState$ | async"></app-table>
table component
@Input() users$: Observable<IUser[]>;
    displayedColumns = ['_id', 'emailAddress', 'password', 'createdAt', 'updatedAt'];
    dataSource = new MatTableDataSource();

I cannot get my ngrx state users: <IUser[]>
wired into MatTableDataSource properly
here is my RxJS logic
onChange(changes: SimpleChanges) {
        this.users$
            .map(users => this.dataSource.data = users);
}

action requested please
console error follows...
ERROR Error: Uncaught (in promise): TypeError: Cannot add property _resolvedData, object is not extensible
TypeError: Cannot add property _resolvedData, object is not extensible
    at MapSubscriber.eval [as project] (webpack-internal:///./node_modules/@angular/router/esm5/router.js:4038:34)
    at MapSubscriber._next (webpack-internal:///./node_modules/rxjs/_esm5/operators/map.js:82:35)
    at MapSubscriber.Subscriber.next (webpack-internal:///./node_modules/rxjs/_esm5/Subscriber.js:97:18)
    at ScalarObservable._subscribe (webpack-internal:///./node_modules/rxjs/_esm5/observable/ScalarObservable.js:53:24)
    at ScalarObservable.Observable._trySubscribe (webpack-internal:///./node_modules/rxjs/_esm5/Observable.js:178:25)
    at ScalarObservable.Observable.subscribe (webpack-internal:///./node_modules/rxjs/_esm5/Observable.js:166:93)
    at MapOperator.call (webpack-internal:///./node_modules/rxjs/_esm5/operators/map.js:60:23)

I tried several attempts to get the typed array out of the observable
.switchMap causes ERROR TypeError: this.users$.switchMap is not a function
.subscribe causes ERROR Error: Uncaught (in promise): TypeError: Cannot add property _resolvedData, object is not extensible
.map causes ERROR TypeError: this.users$.map is not a function
I am also wondering is there is a an unseen peer dependency lapse with libraries under the hood with RxJS

well I have torn down the code to bare bones minimum
taking the input which resolves to a typed array
I stuff it into new datasource onChanges()
and the console is just running away in infinite loop with this error
ERROR Error: Uncaught (in promise): TypeError: Cannot add property _resolvedData, object is not extensible
    ngOnChanges(changes: SimpleChanges) {
        this.dataSource = new MatTableDataSource(this.users$)
        this.dataSource.paginator = this.paginator
        this.dataSource.sort = this.sort
        this.resultsLength = this.dataSource.data.length
    }

I am closing this out due to my findings
somewhere in the NGRX pipeline (which doesnt seem fair since I am using TYPES here) my typed ARRAY is being morphed into an Object of Objects (with idices ? too)
So I am confident the MatTable will operate when I fix this lapse in TYPE
not impressed though

This was my browser safe solution
        this.dataSource = new MatTableDataSource(Object.keys(this.users$)
            .map(key => {
                return this.users$[key];
            }))

but whats happening over the NGRX store is questionable I have seen other STORES resorting to padding their state properties with stuff

this turned out to be errant packaging of the payload within the reducer
mat-table is fine it accepts typed arrays and observables

Hey, i have the same problem, have you found a solution ?

Hi Friend
its been too long for me to recall
best i can do is show you my reducer
and handling the payload
with types
best
Ken
export function usersReducer(
    state: UsersState = initialUsersState,
    action: UsersActionsUnion
): UsersState {
    switch (action.type) {
        case EUsersActions.Reset:
            return initialUsersState

        // singular
        case EUsersActions.FindSuccess:
            return action.payload
        case EUsersActions.ChangedSuccess:
            return action.payload
        case EUsersActions.UsersError:
            return action.payload

        // plural
        case EUserActions.CreateSuccess:
            return [...state, action.payload]

        case EUserActions.UpdateSuccess:
            return [
                ..._.filter(state, (user: any) => user._id !== action.payload._id),
                ...action.payload
            ]
        case EUserActions.DeleteSuccess:
            return [
                ..._.filter(state, (user: any) => user._id !== action.payload._id)
            ]
        default:
            return state
    }
}

to give you my best answer
my reducer was tripping up the input to my mat-table component
I was operating an observable as an @Input to my table
which mat-table is designed to handle alongside other components such as forms observables


fix(pingcap-qe/artifacts): fix cache sync task

User description
Signed-off-by: wuhuizuo<EMAIL_ADDRESS>
PR Type
Bug fix

Description

Added --delete -f flags to ks3util sync command in git-push.yaml to ensure proper cache synchronization.

Changes walkthrough 📝
Relevant filesBug fix

git-push.yamlFix cache sync task with additional flags

apps/prod/tekton/configs/triggers/triggers/PingCAP-QE/artifacts/git-push.yaml

Added --delete -f flags to ks3util sync command.

+1/-1

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

/approve


Feat/hide menu buttons

closes #15
I mucked up this PR becuase I forgot to make a new branch (and accidentally just pushed to my last merged branch (styling/message-component)... so I made a new branch and pulled everything in. so if the history looks weird that is why.
Screenshot

So I dont think we want to hide the message bar at the top all together. There is one button in the Wireframe to "Mark as done" that should stay up there

kk will update will keep the bar but not the buttons (i don't think they should be greyed out as it could confuse the user.

update screenshot:

LGTM


Using libs for our primary backend API's?

I'd like us to consider using external libraries for our primary backend interfaces rather than writing low level API functions in first class extensions that have to be documented, maintained, kept up to date, and tested. Originally there was no complete solution for GitHub's API, but there is now. Here's what I've found:
GitHub: @octokit/rest (docs)
GitLab: node-gitlab-api
Bitbucket: bitbucket-api-v2
These are all well-maintained libraries that should cover our needs. GitLab would need a bit of help to get some of the write methods in place, but the framework is in place so that doing so should be straightforward.
Again, the point is to keep our codebase, and thereby our maintenance overhead, as low as possible. Doing this should enable slimmer backend integrations where we're only creating high level methods for Netlify CMS specific actions.
Thoughts?

We'd want a library that is well-maintained, but didn't have to be updated too often. Of course, that's mostly dependent on the actual API itself, not the client.
(NOTE: The "official" (documented) GitLab client is node-gitlab, but node-gitlab-api may be just fine.)

A library may also be helpful for more complicated, implementation-specific things, like GL pagination.


fixes #1227 (https://github.com/yegor256/takes/issues/1227)

When socket.getInputStream().available() returns 0, parsing of the request headers will be aborted. I guess the assumption was that available is 0 only in case of "end of stream", which is not true:

public int available()
Returns an estimate of the number of bytes that can be read (or skipped over) from this input stream without blocking, which may be 0, or 0 when end of stream is detected.

I think the appropriate thing to do is to get rid of the code that checks available() altogether, which is what this PR does. In order to reliably determine whether we have reached the end of the stream, we need to read(). No way around it.

@EugenDueck I can't understand why github actions jobs are stuck. Can you please try to push something small into the branch, to restart them?

@EugenDueck it seems that your test is stuck. Did you run the build locally? It passes?

@yegor256  My bad! I hadn't run the other tests after fixing the issue.
So BkBasicTest.handlesTwoRequestInOneConnection() never finishes. I probably won't have the time to dig into it this weekend.
However, I noticed that the Content-Length of the first request in BkBasicTest.handlesTwoRequestInOneConnection() does not take into account the "\r\n" that Joined() adds after the body, so the Content-Length must be 13, rather than 11:
                socket.getOutputStream().write(
                    new Joined(
                        BkBasicTest.CRLF,
                        BkBasicTest.POST,
                        BkBasicTest.HOST,
                        "Content-Length: 11",
                        "",
                        "Hello First",
                        BkBasicTest.POST,
                        BkBasicTest.HOST,
                        "Content-Length: 12",
                        "",
                        "Hello Second"
                    ).asString().getBytes()
                );

This still does not make the test finish. I will dig deeper when I find the time, hopefully next week.

@yegor256
There was a deadlock in the test (the test waited for the server to close the socket, while the server waited for the client to close the socket). The commit I just pushed is supposed to fix that. With that, the tests all pass locally. As to the failing CI checks, I'm not sure how to read them. Looking at a couple of recent commits, most of them lead to failures and cancellations of one way or another.
However, looking into this issue lead me to discover a couple of issues that I would like to discuss, and therefore would like you to not merge this PR in its current form.

#649 introduced the use of InputStream.available() into RqLive.parse(), presumably as a means of checking whether the end of the stream has been reached (i.e. the other side has closed its side of the connection). Unfortunately, InputStream.available() can't be relied upon for that - see the quote in my first message of this PR as to why. So what can happen, and what actually does happen in #1227, hence this PR, is that RqLive.parse() stops parsing the request, because available() returns 0. So this needs to be fixed, even though up to now, we have only seen the bug manifest on Windows.

Also in #649, InputStream.available() was added to BkBasic.accept(), again, in order to check whether there is more data to come or not. This is after a request has been finished, waiting for the next request. So this means that Takes keeps the connection open only as long as the client can keep up "http pipelining" requests into the connection fast enough. The moment the client stops for just a tiny bit, Takes will disconnect. Which all but defeats the purpose of persistent connections. Http server implementations generally have a keep-alive timeout for persistent connections that defaults to anywhere between a couple of seconds and about 1 minute. Using .available(), the timeout is effectively "0". The tcpdump in the following screenshot, taken while doing

(echo -ne "GET /a HTTP/1.1\r\nHost: localhost:8100\r\n\r\n" ; cat) | nc localhost 8100
shows the immediate closure of the connection by Takes:

While looking into these issues, and wondering why BkBasicTest.handlesTwoRequestInOneConnection() succeeded even though the content length was wrong, I discovered #1295

I don't feel like it is a good idea to fix 1., without also addressing 2. I would like to have a reliable "persistent connection" implementation first, with tests that show that it works, before fixing this bug, while making sure that persistent connections still work.
Actually, my preferred approach would be to proceed in this order:

remove support for persistent connections altogether (effectively rolling back #649)
be happy (it will automatically fix this bug, but I would want to add a regression test to make sure it does and stays that way)
create a fresh "persistent connections" feature request for anyone willing to take up

Why do I suggest removing the persistent connections feature? Because that feature is barely working, as the tcpdump shows. And fixing the current implementation is not a trivial matter, in particular due to the need to implement a keep-alive timeout to prevent indefinite blocking of the connection and thread, which means coordinating with at least one more thread - unless of course we go NIO, which however would amount to a complete rewrite of the whole framework.
So we would just remove something that cannot be used in its current form, cannot be fixed easily, but introduces problems.
What do you think?


Release 1.0.0-beta.1

          2 Messages

:book:
iOS: Executed 1 test, with 0 failures (0 unexpected) in 0.004 (0.005) seconds

:book:
tvOS: Executed 1 test, with 0 failures (0 unexpected) in 0.003 (0.005) seconds

  Generated by :no_entry_sign: Danger


Reverse columns for displaying simultaneous morphemes in a gloss

The fields when editing are in the correct order, and it is saved correctly, but the headers and the saved data are in the reverse order. Please make everything like this: first Morpheme gloss, then Meaning in this sign.

Fixed. (Pushed to github master branch.)


Fraud alert / liability disclaimer

[ ] update the fraud alert to use i18n
[ ] add Japanese translation to fraud alert
[ ] Add further liability disclaimer to the About page
[ ] translate to Japanese

Generating key and JA translation now.

https://github.com/ourjapanlife/findadoc-localization/pull/61

A couple of resources to add here for reference:

A template for a medical disclaimer (UK):
https://seqlegal.com/free-legal-documents/medical-disclaimer

A doctor finding site's liability page (Japanese):
https://www.10man-doc.co.jp/warning/

I think both are useful references. In our case we'll want to have info from both sides, but lean heavily on the JP side since we are in JP.
I'd suggest we create a separate disclaimers page like they have on the latter, and link to it from the about page.


LESQ-934: New Content Banner Video

Description
Music year: 2000

Removes image from new content banner and replaces it with video

Issue(s)
Fixes #LESQ-934
How to test

Go to https://deploy-preview-2624--oak-web-application.netlify.thenational.academy
Click on the legacy option of any legacy subject that has new content (apart from Music)
You should see banner with video available to be played

Screenshots
How it used to look (delete if n/a):

How it should now look:
https://github.com/user-attachments/assets/ec6e2209-c13b-4050-a12b-f64f879ca194
Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner
[ ] Does this PR update a package with a breaking change

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


Remove CMD from Dockerfile

Hello,
I'm currently using your docker image and I would like to know why you included the line: https://github.com/allinurl/goaccess/blob/7d231a24077a042d8aa112b5a48d082aeb5f76be/Dockerfile#L33 in the Dockerfile ?
I use docker-compose to deploy goaccess. The file look like this:
services:
  goaccess:
    image: allinurl/goaccess:1.4.1
    command: ["/var/log/nginx/access.log" ]
    volumes:
      - ./goaccess/goaccess.conf:/etc/goaccess/goaccess.conf
      - ./goaccess/report:/goaccess/report
      - ./logs/nginx-proxy:/var/log/nginx:ro
    expose:
      - "7890"

I have to add the line: command: ["/var/log/nginx/access.log" ] because I need to overwrite the command statement (--help) from the Dockerfile. My goaccess.conf is already specifying the log file so this is kinda redundant and I didn't find a way to remove the statement. (I can't use command: [""] because it will give an empty string to goaccess which will fail to parse the corresponding log because the filename is empty).
I can open a PR with a fix and a rewrite of the corresponding doc if you want :)
Thanks for your work on goaccess !

I'll have to defer this Docker question to @err931 as he probably has a better answer for you.

Hi, I'll answer about that issue.
The reason for the CMD is to suppress the error displayed if you do not specify any arguments when running directly from the container.
I don't think there is anything wrong with removing it.
Best Regards,

Hello @err931,
I understand but we should see the lack of command as an error imo. The user should either pass an argument manually or create a config file.
@allinurl Let me know if you need me to create a PR to change the CMD line

Thanks @err931. @Byh0ki Yeah, feel free to submit a PR. Thanks!

Closing this. Feel free to reopen it if needed.


[Bug]: Blank webpage when compiling from source

Describe the bug
The server starts without error and accessing http://localip:3000 shows a blank page with a small black circle in the top left. Web logs are showing that a bunch of script (in http://localip:3000/_next/static/) could not be loaded.
I have nut-client installed and working locally (server runs on another machine), and returning the UPS data on upsc command
Debug Output
GET
http://<IP_ADDRESS>:3000/_next/static/media/c9a5bc6a7c948fb0-s.p.woff2
[HTTP/1.1 404 Not Found 168ms]

Steps to reproduce
I followed the steps to build from source on a fresh Ubuntu 22.04 LXC:
as root:
apt install git
curl -fsSL https://deb.nodesource.com/setup_21.x | bash - && apt-get install -y nodejs
git clone https://github.com/Brandawg93/PeaNUT.git
cd PeaNUT
npm i -g pnpm
pnpm i
pnpm run build
node .next/standalone/server.js

Device Type
Ubuntu 22.04 LXC
UPS Device
CyberPower over USB
Last Working Version
No response

@Brandawg93 Do I need to install nut manually? And will it work if nut is configured as netclient only (I already have a nut server running on another machine)

Yes, you will need to install nut manually. And I do believe it has to be in server mode to work properly. If you change it, and it works let me know and I'll update the docs.

Chiming in here that I also wanted to use PeaNUT to display the stats for an already-configured NUT remote server. I've only figured out how to query the device via the api by appending NUT_HOST= before the node .next/standalone/server.js command. However when navigating to the main page it is still blank with the black circle as OP describes.

I submitted a PR (#55) that fixes this issue. Not a dev, just someone who spent too much time googling what was happening. 😄

Cool! If someone else can confirm this fixes the issue for them, I will merge it into the main branch. I do think I may need to rework the Dockerfile to accommodate this, so just want to make sure this fix works for others.

Actually I think you don't need to change the Dockerfile (not sure as I don't use Docker) because the copy commands are already there.
The fact that the files are not copied when server.js is run is mentioned here, in a section where they talk about files being automatically copied. I find that kind of misleading even if they do mention it.
Oh and I also tested PeaNUT with a NUT server running on a different server, and as long as I specify the NUT_HOST it will work, so @remz1337 it will work as a client-only setup too.

I read that as well regarding copying. Ironically, the static folder is automatically copied on my Mac but not on the docker builds of Ubuntu. Not sure why it’s different for Linux. Either way, I always like to get a second outside confirmation just in case.

I went ahead and merged as I don't think this will need a new release for those compiling from source. If anyone still has issues, feel free to reopen.

tested successfully. Thank you


⚖ Register  Lavender.Five Nodes :bee: Validator

Register new validator gentx on the drunemeton-1 network.

Please close this PR as we will be opening a new issue.


⚠ Bofrost.lu has degraded performance

In 5e0187d, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1799 ms

Resolved: Bofrost.lu performance has improved in d833e94 after 6 minutes.


What’s the best approach for a current call handling when app is terminated?

Before filing an issue please check that the issue is not already addressed by the following:

Voice SDK Guides
GitHub Issues
Changelog

We are wondering if there is a better approach for this behavior: when killing the app with a call connected, the current call will leave the other user connected for another minute.
Steps to Reproduce

On a call, connected status
Killing the app
The other user stay connected for another minute.

Code
// Code that helps reproduce the issue

Expected Behavior
Anything we can do to make the experience better?
Ideally we want to disconnect the call right away if possible.
Actual Behavior
The call stays connected for 1 minute on the other device.
Reproduces How Often
100%
Logs
// Log output when the issue occurs

Versions
All relevant version information for the issue.
Voice iOS SDK
4.0
Xcode
10.3
iOS Version
All
iOS Device
All

Hi @jocelynlih
One suggestion is to call .disconnect() but unfortunately in the case of app being terminated, the app won't get enough time to send out the disconnect message and terminate the call properly using the [UIApplication beginBackgroundTaskWithExpirationHandler:] method.
Without doing anything, the Twilio Voice service will terminate the call if it detects silence for longer than 1 minute, which is exactly what you have observed on the other side of the call.
-bobie


Foreign key error when adding tenant to user in the multi tenant example

Link to reproduction
https://github.com/timoconnellaus/payload-tenancy-test
Describe the Bug
I have converted the mutli tenance example from the payload repo to postgresql and attempted to run it
The issue I experience occurs in two places:

When running the seed there will be mulitple errors related to inserting data into the DB
When adding a tenant to a user and setting their role a FK error will occur

error: insert or update on table "users_tenants_roles" violates foreign key constraint "users_tenants_roles_parent_id_users_tenants_id_fk"
at /Users/tim/repos/payload-tenancy-test/node_modules/.pnpm/pg@8.11.3/node_modules/pg/lib/client.js:526:17
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at /Users/tim/repos/payload-tenancy-test/node_modules/.pnpm/drizzle-orm@0.28.5_@libsql+client@0.3.6_pg@8.11.3/node_modules/src/node-postgres/session.ts:64:19
at upsertRow (/Users/tim/repos/payload-tenancy-test/node_modules/.pnpm/@payloadcms+db-postgres@0.1.11_payload@2.0.14/node_modules/@payloadcms/db-postgres/src/upsertRow/index.ts:275:7)
at Object.updateOne (/Users/tim/repos/payload-tenancy-test/node_modules/.pnpm/@payloadcms+db-postgres@0.1.11_payload@2.0.14/node_modules/@payloadcms/db-postgres/src/update.ts:66:18)
at updateByID (/Users/tim/repos/payload-tenancy-test/node_modules/.pnpm/payload@2.0.14_@types+react@18.0.21_esbuild@0.18.20_typescript@4.8.4_webpack@5.89.0/node_modules/payload/src/collections/operations/updateByID.ts:262:16)
at updateByIDHandler (/Users/tim/repos/payload-tenancy-test/node_modules/.pnpm/payload@2.0.14_@types+react@18.0.21_esbuild@0.18.20_typescript@4.8.4_webpack@5.89.0/node_modules/payload/src/collections/requestHandlers/updateByID.ts:36:17)
To Reproduce

clone the linked repo
pnpm i
cp .env.example .env
set DATABASE_URL variable in env file
Set PAYLOAD_SEED variable to true
pnpm run dev - this will reproduce the issues on seed. Some data will be inserted but not all
set PAYLOAD_SEED variable to false
pnpm run dev - should start successfully
add a new user in the CMS and add a tenant to that user. Should see an error relating to FK relationships

Payload Version
2.0.14
Adapters and Plugins
db-postgres, bundler-webpack

Some more info on this. If you drop the FK relationship allowing the data to be inserted it looks like the table users_tenants_roles is attemping to set the FK to users id and not the users_tenants id. This would explain the FK error
ALTER TABLE users_tenants_roles
DROP CONSTRAINT users_tenants_roles_parent_id_users_tenants_id_fk;
SELECT * FROM users_tenants_roles

Note: parent_id = 5
SELECT * FROM users_tenants

Note: id = 6544062d02479b2b7164ae1b


Dont's send despawns to hidden entities

We need to check if the despawned entity is visible for each client before sending a despawn for it.

Closed by #366.


replace complete-restore.sh with go code

Signed-off-by: Steve Kriss<EMAIL_ADDRESS>

Updated with lots of comments

@ncdc I'm happy with the matching/moving approach & code as implemented now. let me know if you feel otherwise.

Ok I’ll take a closer look over the weekend or Monday
On Fri, Jun 8, 2018 at 5:59 PM Steve Kriss<EMAIL_ADDRESS>wrote:

@ncdc https://github.com/ncdc I'm happy with the matching/moving
approach & code as implemented now. let me know if you feel otherwise.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/heptio/ark/pull/534#issuecomment-395903236, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAABYt5twLLcghIxZIEWJPBWSpLxtp4Eks5t6vPFgaJpZM4UfFE-
.

We should add unit tests 😄

Sgtm
On Mon, Jun 11, 2018 at 12:39 PM Steve Kriss<EMAIL_ADDRESS>wrote:

@skriss commented on this pull request.
In pkg/controller/pod_volume_restore_controller.go
https://github.com/heptio/ark/pull/534#discussion_r194469006:

// giving errors about renames not being allowed across filesystem layers in a container. This is occurring

// whether /restores is part of the writeable container layer, or is an emptyDir volume mount. This may
// be solvable but using the shell works so not investigating further.
//
// Glob patterns:
// 	[^.]*  : any non-dot character followed by anything (regular files)
// 	.[^.]* : a dot followed by a non-dot and anything else (dotfiles starting with a single dot, excluding '.')
// 	..?*   : two dots followed by any single character and anything else (dotfiles starting with two dots, excluding '..')
if err := moveMatchingFiles(restorePath, volumePath, "[^.]", ".[^.]", "..?*"); err != nil {

return errors.Wrapf(err, "error moving files from restore staging directory into volume")

}

// The staging directory should be empty at this point since we moved everything, but
// make sure.
if err := os.RemoveAll(restorePath); err != nil {

return errors.Wrap(err, "error removing restore staging directory and its contents")

I think it makes sense just to add a warning to the server log here -
since this should just be removing the empty staging directory. Do you
think that's reasonable?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/heptio/ark/pull/534#discussion_r194469006, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAABYlNwZycaLlqTFznHpLDaOYdfhO5Pks5t7p0xgaJpZM4UfFE-
.

Do you want to block on units? I need to do that across all of the new code, so would prefer to get this merged for the alpha and then circle back holistically on units.

No need to block

LGTM


[Task] Add/Fix the doc strings for TF based session based API documentation

Related: https://github.com/NVIDIA-Merlin/Merlin/issues/433

Completed review of API documentation (generated by docstrings in code) for Merlin Models codebase. Details are available here: https://docs.google.com/document/d/1v4rk2-pW34swfbDWz_d41ADlXjUcT9Yoc_xO3YgN02U/edit


[Bug]

Community Note

Please use a 👍 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Describe the bug
Database fails to synchronize on connection setup. HTTP calls fail with "400 Bad Request and no gremlin script supplied" and "405 Method Not Allowed" errors. Setup

OS: MacOS 14.3
Browser: Google Chrome
Graph Explorer Version: 1.5.1
Graph Database & Version: JanusGraph 1.0.0-rc2 (WsAndHttpChannelizer)

To Reproduce
Steps to reproduce the behavior:

Follow the steps of the README to run graph explorer via docker
Go to https://localhost in web browser
Accept certificate warnings
Add connection for Gremlin to http://localhost:8182
Attempt to synchronize the database

Gremlin server is up and responding correctly
curl http://localhost:8182/\?gremlin\=g.V\(\).count\(\)
{"requestId":"8b96bc56-528a-4793-9198-bd69584fd1b7","status":{"message":"","code":200,"attributes":{"@type":"g:Map","@value":[]}},"result":{"data":{"@type":"g:List","@value":[{"@type":"g:Int64","@value":0}]},"meta":{"@type":"g:Map","@value":[]}}}%

Expected behavior
Database synchronization should succeed

This appears to be an issue with 1.5.1 - Reverting to 1.4.0 works for me.


Fix onSuccess exception handling in FileTools.RequestFile

Background
If put under .gltf extension a non-json file and try to load it this await never resolves and leaves scene in loading state forever:
try {
  await SceneLoader.AppendAsync('https://some.site.com/models/', 'bad_non_json_file.gltf', scene);
  console.log('Model loading success');
} catch (e) {
  console.log('Model loading failed');
}

None of console.log is never called in such case.
It is because onSuccess callback throws exception SyntaxError: JSON.parse: unexpected character ... here: https://github.com/BabylonJS/Babylon.js/blob/6626433abbee8f1d1e82499915645cc54b785a50/loaders/src/glTF/glTFFileLoader.ts#L546
Solution
The solution is to avoid pitfalls like this one globally by fixing FileTools.RequestFile to behave more like a promise and call onError if onSuccess fails.

I like it, let s see what @bghgary thinks about it ?

Probably it is better to re-throw error if error handler is missing:
if (onError) {
    onError(e);
} else {
    throw e;
}

@bghgary, you are right. I added onOpened error handling because exception in it also breaks promise flow. Please check.
Error handling of onProgress can be skipped since it doesn't hang promise.
In overall type of error handler onError?: (error: RequestFileError) => void looks incorrect to me because RequestFile method can throw not only RequestFileErrors.
Because of this I don't know a good way to add error handling to offline branch of this method - there is no WebRequest object required by RequestFileError constructor.
Looks like it is a good idea to change error handler type to onError?: (error: unknown) => void that touches about 5 files in the project and can be done in separate PR.

Error handling of onProgress can be skipped since it doesn't hang promise.

I suppose that is true. To be consistent, we shouldn't do it in the SceneLoader either.

In overall type of error handler onError?: (error: RequestFileError) => void looks incorrect to me because RequestFile method can throw not only RequestFileErrors.
Because of this I don't know a good way to add error handling to offline branch of this method - there is no WebRequest object required by RequestFileError constructor.
Looks like it is a good idea to change error handler type to onError?: (error: unknown) => void that touches about 5 files in the project and can be done in separate PR.

It's a bit more complicated than it seems as this will propagate all the way to the scene loader plugins. I'm not sure updating this is worth it.

Tests are failing :(

I reran them to make sure it's not from yesterday's bug.

Merged with master again. Test pass.


feat: add endpoint to create product

Description
An endpoint to create new product

Link to issue here
#84
Changes proposed
What were you told to do?

Create a backend endpoint to handle product creation requests.
Validate input data to ensure all necessary fields are provided and correctly formatted.
Ensure proper error handling and response statuses.
Update any related data or references accordingly.

What did you do?

Implemented an endpoint to create new product
created new dto for product creation

Check List (Check all the applicable boxes)
🚨Please review the contribution guideline for this repository.

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.
[x] I am making a pull request against the dev branch (left side).
[x] My commit messages styles matches our requested structure.
[x] My code additions will fail neither code linting checks nor unit test.
[x] I am only making changes to files I was requested to.

Screenshots/Videos

@Ace2489,  @chimaihueze

@NdubuisiJr