Current state

Heya!
I wanna potentially work on fitting this and jerry rigging an app for vr headsets with the purpose of hunting, what is the current state of this before I purchase one? Not hoping for like picture captures and such, just hoping for basically red is hot functionality.

Without any custom software, the P2 Pro is already "just a webcam" out of the box. It already does some image processing internally and provides a processed image (in addition to the raw data).
By default the palette is white is hot.
If you want to change the palette to another built-in one, you can do so with the command pseudo_color_set in P2Pro_Cmd, assuming you have libusb-based access to the camera. Although the exact implementation depends on your system, ofc.
Otherwise you can always just map the black/white image to a color palette manually.
Additionally, I fear that the latency of this camera might pose a problem in a VR application.
I did not test the end-to-end latency and don't know which access method would provide the lowest latency, but it's easily in the 100s of ms, I'd guess. Which would be way too high for most VR applications, in my experience.
(I'll close this issue for now, as it's not an issue with this tool, but you can still comment)


Removed unused variable

I noticed that mvn -Panalysis clean install was failing due to an unused variable.

Thanks


Arn 948 add gp pracice name based on arn 770

@wood-n I imagine we can close this PR as we rebased and merged these changes Friday?


stability of tacotron

I was seeing multiple issue as described in the original paper, like wrong pro, repeat word, or unstoppable case, anyone trying any solution to fix this?

@begeekmyfriend any insight or experiment?

Never meet those issues unless there are no location sensitive attention and stop token prediction.

I tested a large corpus, where there're more patterns that the training corpus haven't seen,  in this situation, even with location sensitive attention and stop token prediction, there's issues like above;

What is that corpus?

like abnormal input, or too long input, or script that are not clean, anyway, I am talking that there's bad aligned case in tacotron

Hi, sorry to interrupt. I also run into the problem of unstoppable generation. It says  I am training M-AILABS en-US male voice. The target_length would always be max_iters*r. It seems no element in stop_tokens ever goes up to 0.5? Have you guys seen this? I am using the default hparams. Do you think it is a corpus-specific problem?


[UI] User preferences page MUI v5 migration

Notes for Reviewers

This PR successfully migrates user preferences page to MUIv5 compatible code.

Signed commits

[x] Yes, I signed my commits.

@sudhanshutech based on this slack message I left formControl as it is without changing.
import {FormLabel} from '@material-ui/core';

FormLabel API in Material UI.

import {FormLabel} from '@mui/material/FormLabel update the import statement :).

@shanu your review here is encouraged.


Add W3C GeoRSS in Rss and Atom

Sorry for not replying for so long. This PR is too old and I am closing it.


datafusion_proto::physical_plan_to_bytes has a problem with characterlength function

Describe the bug
there is issue when physical plan is deserialized from bytes, it looks like the issue is with specific function, length in this case
To Reproduce
reproduction is simple:
use datafusion::prelude::{SessionContext, CsvReadOptions};
use datafusion::error::Result;
use datafusion_proto::bytes::{physical_plan_to_bytes, physical_plan_from_bytes};

let ctx = SessionContext::new();
ctx.register_csv("example", "example.csv", CsvReadOptions::default()).await?;
let logical_plan = ctx.state().create_logical_plan("select length(c0) as l from example").await?;
let physical_plan = ctx.state().create_physical_plan(&logical_plan).await?;
let blob = physical_plan_to_bytes(physical_plan)?;

// Error: Plan("There is no UDF named \"characterlength\" in the registry")
let _physical_plan = physical_plan_from_bytes(&blob, &ctx)?;

error "There is no UDF named \"characterlength\" in the registry" is raised. Which is odd as length is not an udf.
wondering if characterlength should be character_length?
Expected behavior
other functions work ok, like trim:
let logical_plan = ctx.state().create_logical_plan("select trim(c0) as l from example").await?;
let physical_plan = ctx.state().create_physical_plan(&logical_plan).await?;

let blob = physical_plan_to_bytes(physical_plan)?;
let _physical_plan = physical_plan_from_bytes(&blob, &ctx)?; // All OK

Additional context
tested with datafusion, and datafusion-proto, version 23 and 24

Thanks for the report @milenkovicm  -- I agree this is strange

wondering if characterlength should be character_length?

I agree this sounds likely. A quick look through the code didn't bring up anything obvious though
https://github.com/search?q=repo%3Aapache%2Farrow-datafusion characterlength&type=code

I think this looks like a fairly good first issue as there is a clear description and reproducer . Marking it as such

thanks @alamb ,
Got some time to have a look at this.
I believe this is problem with serialization, which serialize it as ScalarUdf thus deserialization can't find it in UDF registry.
to elaborate a bit, at:
https://github.com/apache/arrow-datafusion/blob/412867aa2596a2df93635b6ac31d48aa14111c40/datafusion/proto/src/physical_plan/to_proto.rs#L324
expr.name() for length returns characterlength which is then matched in
https://github.com/apache/arrow-datafusion/blob/98839dbceb835c9e78154a27bb96c9dad58de7c6/datafusion/expr/src/built_in_function.rs#L326
which is expecting character_length, and as it does not match it will jump to else branch
https://github.com/apache/arrow-datafusion/blob/412867aa2596a2df93635b6ac31d48aa14111c40/datafusion/proto/src/physical_plan/to_proto.rs#L339
if i'm not mistaken.
at the end deserialization gets a wrong expression type.
I guess there may be a bit problems with function names with _ in the name, but did not investigate further at this stage.

@milenkovicm  your analysis makes sense to me --  maybe we need to store both the original name and the display name on ScalarFunction 🤔

I might say nonsense, we could just match all variants like we have with pow?

I am not quite sure what you mean, but sounds worth a try

Apologies,
What I meant, change
"character_length" => BuiltinScalarFunction::CharacterLength

To
"character_length" | "characterlength"=> BuiltinScalarFunction::CharacterLength

Not sure if it is correct solution but would definitely work 😀

Seems reasonable to be 👍

if we add characterlenght to list of functions in from_str we would probably expose them as sql function
well based on other usage of from_str
https://github.com/apache/arrow-datafusion/blob/19af95253d990283be95544bf7d47530524b59d1/datafusion/sql/src/expr/function.rs#L50
we would be able to do
select characterlength("a")

and
select character_length("a")

not sure if it that would be great thing to do.
wdyt @alamb ?

Thanks for the ping @milenkovicm  -- I think we have to try some of the solutions and see how they look

It works for length and concat_ws, just checked it now.

I'm closing this issue, looks like #6448 fixed it, feel free to reopen it if you believe this issue should be addressed in some other way @alamb

(thanks @2010YOUY01 👍 )


Some problem on the Installtion of library  LNK2001

I download the zip from the web, my environment is VS2017 + OpenCV 2.143. but if I want to build the solution, the compiler will tell me the error in the release mode.
Main.obj : error LNK2001: unresolved external symbol "public: void __thiscall bgslibrary::VideoAnalysis::start(void)" (?start@VideoAnalysis@bgslibrary@@QAEXXZ)
1>Main.obj : error LNK2001: unresolved external symbol "public: bool __thiscall bgslibrary::VideoAnalysis::setup(int,char const * *)" (?setup@VideoAnalysis@bgslibrary@@QAE_NHPAPBD@Z)
1>Main.obj : error LNK2001: unresolved external symbol "public: __thiscall bgslibrary::VideoAnalysis::~VideoAnalysis(void)" (??1VideoAnalysis@bgslibrary@@QAE@XZ)
1>Main.obj : error LNK2001: unresolved external symbol "public: __thiscall bgslibrary::VideoAnalysis::VideoAnalysis(void)" (??0VideoAnalysis@bgslibrary@@QAE@XZ)
1>C:\bgslibrary\bgslibrary\Release\bgslibrary.exe : fatal error LNK1120: 4 unresolved externals
1>Done building project "bgslibrary.vcxproj" -- FAILED.
And I can run the basic test.cpp in this mode, so can you give me some suggestion.

Hi @JohnnySorry , this is a linking error, it seems that VideoAnalysis.cpp file are not included in your compilation. I suggest you to use CMake to build a VS2017 + OpenCV 2 project, you can follow this tutorial: https://github.com/andrewssobral/bgslibrary/wiki/Compiling-BGSLibrary-with-OpenCV-2.4.x-and-Visual-Studio-2013-from-CMAKE (just change the parameters from VS2013 to VS2017).
UPDATE: i checked that OpenCV 2 there is no pre-built binaries/libs for VS2017 (only for VS2015). If you want to use VS2017, the best is to switch to OpenCV 3.


compact: deal with thanos-receive HA blobs

Thanos, Prometheus and Golang version used:
v0.10.1
Object Storage Provider:
AWS S3
What happened:
We've set up 3 HA thanos-receive nodes with --receive.replication-factor=3 and --label=replica="$(NAME)".
On thanos-query side this works fine with --query.replica-label=replica.
But this leads to 3x space used on S3:
|            ULID            |        FROM         |        UNTIL        |  RANGE   | UNTIL-DOWN |  #SERIES  |   #SAMPLES    |   #CHUNKS   | COMP-LEVEL | COMP-FAILED |          LABELS          | RESOLUTION |  SOURCE   |
|----------------------------|---------------------|---------------------|----------|------------|-----------|---------------|-------------|------------|-------------|--------------------------|------------|-----------|
| 01E0DJRTRCQM3ZVQ3XWVSFKBGV | 23-01-2020 00:00:00 | 06-02-2020 00:00:00 | 336h0m0s | -296h0m0s  | 2,698,507 | 5,147,591,926 | 210,376,397 | 5          | false       | replica=thanos-receive-1 | 0s         | compactor |
| 01E0DPB9G08FQ2D33AWBTNDPC0 | 23-01-2020 00:00:00 | 06-02-2020 00:00:00 | 336h0m0s | -296h0m0s  | 2,670,996 | 5,154,572,850 | 200,780,620 | 5          | false       | replica=thanos-receive-2 | 0s         | compactor |
| 01E0DV7VAZGK657RXSTCPVNGHC | 23-01-2020 00:00:00 | 06-02-2020 00:00:00 | 336h0m0s | -296h0m0s  | 2,695,844 | 5,149,216,439 | 232,443,752 | 5          | false       | replica=thanos-receive-0 | 0s         | compactor |

What you expected to happen:
Would be great to have some option on compactor side to deduplicate blobs against some replica-label.

This is a dupe of #1014 . I very much agree this is something we should have (and it's actively being worked on)! :)


increase timeout for nested concurrent test...

… that is still intermittently timing out in travis.
/cc @davidopp @guenter

LGTM

Test change. Merging. Thank you.


Reporter is not ready. name="InternalDataplaneMainLoop"

Reporter is not ready. name="InternalDataplaneMainLoop"
Expected Behavior
run correctly!
Current Behavior
I added this,
            - name: FELIX_LOGSEVERITYSCREEN
              value: "debug"

when I run kubectl logs calico-node-kl227 -n kube-system it had the following log:
felix/health.go 266: Reporter is not ready. name="InternalDataplaneMainLoop"

and my server memory increasely quickly:

Possible Solution
update os version? I ran it correctly in ubuntu20. I do not know why.
Your Environment

Calico version 3.25
Orchestrator version (e.g. kubernetes, mesos, rkt): k8s 1.26.5
Operating System and version: ubuntu16

@xfyan0408 could you post the full calico logs (with debug enabled preferably), so we can have more info to try to pinpoint a root cause for this failure? thanks!


Add Codeowners

Add Codeowners

Test URLs:
N/A

Codecov Report

Merging #140 (5d8ee06) into main (2ccfaff) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #140   +/-   ##
=======================================
  Coverage   96.36%   96.36%
=======================================
  Files           6        6
  Lines         468      468
=======================================
  Hits          451      451
  Misses         17       17

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


Remove references to "kur" and "tgl", add "fil" to man page

Ran into this after building a language mapping from the man page. These languages are not available in tessdata.
"kur" no longer exists, might be named "kur_ara" (the old "kur_ara" is
now "kmr", which is actually Latin) now, but "kur" is not present in
tessdata_fast nor in tessdata_best. [1] [2]
"tgl" (Tagalo) is now named "fil" (Filipino) [3]
[1] https://github.com/tesseract-ocr/langdata/issues/124
[2] https://github.com/tesseract-ocr/tessdata_best/issues/23
[3] https://github.com/tesseract-ocr/langdata/issues/84

Please see https://tesseract-ocr.github.io/tessdoc/Data-Files-in-different-versions.html

In general it is not clear to me what the authoritative source on all the
"officially" supported/included languages is. I used to think the man page,
but now I assume the tessdata repos themselves.

The man pages may not have been updated with all changes.

Would you like me to also submit an update for that page?

Yes, that would be great.

If it helps I can try to automatically match all the other languages in
the man page (or the wiki link) to the ones installed by ubuntu packaging
and what is available in tessdata.

Actually, they may need to be matched to what's in tessdata, tessdata_best
and tessdata_fast. In fact, tessdata_fast is what has been packaged for the
distributions.
On Wed, Dec 2, 2020 at 3:34 PM Merlijn Wajer<EMAIL_ADDRESS>wrote:

@MerlijnWajer commented on this pull request.
In doc/tesseract.1.asc
https://github.com/tesseract-ocr/tesseract/pull/3165#discussion_r534041953
:

@@ -277,7 +277,6 @@ following languages:
tat (Tatar),
tel (Telugu),
tgk (Tajik),
-tgl (Tagalog),

@Shreeshrii https://github.com/Shreeshrii - not sure why my comment
went to this thread (I clicked quote reply), but my above comment is in
reply to your message.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/pull/3165#discussion_r534041953,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABG37I2VGRJKBEYJRVBNLLDSSYGLHANCNFSM4UJVASZA
.

--

भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com

OK, I will try to do that this week and update this PR if appropriate.

OK, I will try to do that this week and update this PR if appropriate.

Please make a new PR for any followup changes.


Integration with Vector DB

This PR provides scripts to interact with the Vector DB endpoints.
Updates the grounding logic based on the results of the semantic similarity search

/check-enforcer override

/check-enforcer override

/check-enforcer override


fix(deps): Remove dependency org.glassfish.web:el-impl

There is no need for this dependency.
An el-impl is already provided by Spring Boot/tomcat-embed-el. tomcat-embed-el is also used for other servlet containers.
Related: https://github.com/spring-projects/spring-boot/issues/24744

Please rebase and resolve the conflicts


feat: normalise directory output for snapshots

Before (master)

This change

@mallison I've recreated the change found in the 6.1.1 tag. Is this file path what you expected to see now? It seems to duplicate the cypress/e2e part of the path. But if this makes it consistent then it seems fine to me.
Do I need another test to run to see the difference in outputs?

It seems to duplicate the cypress/e2e part of the path. But if this makes it consistent then it seems fine to me.

I'd probably strip the leading cypress part to be consistent with screenshots (I can imagine people might have tooling that'd break if there are multiple cypress directories too!)
Thanks for looking at this!

Do I need another test to run to see the difference in outputs?

Yeah if you had something like
cypress/e2e/common/path/matchImageSnapshot.cy.ts
cypress/e2e/common/path/subdir/matchImageSnapshot.cy.ts

With your original code I believe that test that runs last would overwrite the snapshot from the first.
With Cypress's path stripping behaviour you'd get
cypress/snapshots/matchImageSnapshot.snap.png
cypress/snapshots/subdir/matchImageSnapshot.snap.png

(it may preserve the e2e part but it'll definitely strip the common/path part)

Adding a comment here for my own reference.
Given this test:
cypress/e2e/nested/test/matchImageSnapshot.cy.ts

The ideal output for snapshots is:
cypress/snapshots/nested/test/matchImageSnapshot.cy.ts

Alongside the other folders within cypress.
Issue is currently residing in this section of code
  const snapshotsDir = customSnapshotsDir
    ? path.join(process.cwd(), customSnapshotsDir, specFileRelativeToRoot)
    : path.join(screenshotsFolder, '..', 'snapshots', specFileRelativeToRoot)

Looking at the example with no customSnapshotsDir, the snapshot is written to:
cypress/snapshots/cypress/e2e/nested/test/matchImageSnapshot.cy.ts

This is due to the specFileRelativeToRoot including the cypress/e2e path:
cypress/e2e/nested/test/matchImageSnapshot.cy.ts

When joining this to ../screenshots (or process.cwd()) it means we take the existing cypress/e2e path and duplicate it
Need to find a way to remove the highlighted part, taking into account it can be any structure from the Cypress config:
cypress/snapshots[/cypress/e2e]/nested/test/matchImageSnapshot.cy.ts
Looking at this now

Is there an easy way of trying this?
I'm a little newbie in the world of node and cypress.

Easiest way is to clone the repository, checkout the branch and build it. Then link the newly cloned repo into your application directory with yarn link
https://classic.yarnpkg.com/lang/en/docs/cli/link/
Just note this branch isn't finished yet, but early feedback is welcome!

Thanks for working on paths! In the original Jared Palmer version a different folder structure is used/generated when all tests were executed vs when only a single spec file was started. Does this branch fix that issue as well?
I have not tested this behavior in the latest 7.0.0 version of this package, maybe it is already fixed. 🤞

Yeah, the goal of this PR is to paper over that annoying issue from Cypress. I'm back from vacation now so will be addressing issues this week

I think I've found a fix for this annoying issue.
After digging through the many issues on the Cypress repo about this I couldn't see an easy fix, so I've opted to have a default option called specFolder which is set to cypress/e2e/. Then I just strip that from the specFileRelativeToRoot value. That results in a clean directory structure like this:

I believe that this works fine in open mode, run mode and with --spec as well.

@balassy @mallison Would be great if you could try it out and see if it works as expected
https://github.com/simonsmith/cypress-image-snapshot/releases/tag/8.0.0-beta.1

Have tested this beta tag on a fairly large work project and it seems to work fine. It's definitely a breaking change because it can affect the directory paths, but at least they're more sane in this version

Thanks for publishing the beta!
I'm trying to figure out how shall I set the new specFolder parameter. This is how we use Cypress currently:

We run component tests (not e2e)
Cypress' specPattern configuration parameter is not set, it uses the default **/*.cy.{js,jsx,ts,tsx}
We run Chrome, Electron and Firefox tests, so there are browser specific Cypress config files with browser specific videosFolder and screenshotsFolder.
Our tests are in the stories folder.

This is our folder hierarchy now:
/
  - cypress
    - chrome
      - screenshots
      - snapshots
        - button
          - button.cy.tsx (folder)
            - *.png files
      - videos
  - stories
    - components
      - button
        - button.cy.tsx (file)

Could you please advise how shall I set the new specFolder parameter?
Thank you.

Ah, you raise an interesting case I hadn't considered which is component testing. I didn't realise it has a separate specPattern that is different. This would make sense though as typically in the codebases I work in the component tests are located alongside the components as .spec.ts files.
It might be in this case that there is no issue as the component tests files are written to the cypress folder based on their existing folder structure.
What gets generated if you just run the tests without changing that option?

I'm sorry, I realized that I cannot help testing this branch until I figure out how to fix #12 . :(
We currently use the original jaredpalmer version, and the problem we see is that running a single spec file uses different snapshot and output folders than running multiple spec files. It is very annoying because of course in CI we run all tests, but when a developer works on a component (s)he just wants to update the snapshots of that particular component, and definitely should not update the snapshots of other components.

Ah yes, okay. I will add a few component tests to this repo so I can test against them as well 👌🏻

(Tested with 8.0.0-beta.1)
If I don't set the new specFolder param and run the component tests from only the button.cy.tsx file (see my folder structure in my previous post) the snapshot images are generated into the cypress/chrome/snapshots/stories/components/button/button.cy.tsx folder.
The same folder structure is used when I run all tests which is a huge improvement to the original jaredpalmer package that used different folders when all tests are executed and when the --spec param was used to run only a single .cy.tsx file.
Instead of calculating the output path, wouldn't it be easier to introduce a new snapshotsFolder parameter similarly to Cypress' videosFolder and screenshotsFolder?
Thank you!

Instead of calculating the output path, wouldn't it be easier to introduce a new snapshotsFolder parameter similarly to Cypress' videosFolder and screenshotsFolder?

We do actually allow such a property already, called customSnapshotsDir. The issue lies with how Cypress provides us the paths.
So this snippet:
  const snapshotsDir = customSnapshotsDir
    ? path.join(process.cwd(), customSnapshotsDir, specFileRelativeToRoot)
    : path.join(screenshotsFolder, '..', 'snapshots', specFileRelativeToRoot)

Say you pass cypress/snapshots as the customSnapshotsDir but we also want to preserve the directory structure of the test we have to deal with this value from Cypress.spec.relative:
cypress/e2e/nested/test/matchImageSnapshot.cy.ts

So now if I path.join cypress/snapshots with the above we get:
cypress/snapshots/cypress/e2e/nested/test/matchImageSnapshot.cy.ts

My difficulty has been in getting rid of the cypress/e2e part, because that can be completely changed by the user in the Cypress config options.

After some more testing I think the issue I outlined above only really affects the E2E tests. I'm pretty happy with how the component tests are written to the same path that they exist in. I have a codebase where the component tests are stored alongside the components all within in a src directory and this sort of structure is created:

Merged in https://github.com/simonsmith/cypress-image-snapshot/commit/1939e25461e5811f2e683e51415653707fd24f03

Nice work @simonsmith. Thanks for getting this change in. I can go back and resurrect all my image snapshot tests now!


👷♂ Working published core-react with eds-utils

resolves #1949
Suggest keeping the -dev version names as its the latest versions that are published under the next tag which is what is in development

Looks good 👍🏻 But we should have a discussion on package.json version numbers in the develop branch, you had some strong opinions about that a little while ago. Personally I don’t think it matters that much until the next release, and makes it easier to remember to bump to the right next version.

My opinion was more that we never knew which version incrementation (major, minor or patch) the next released version would have so it was easier to do that once we knew what the next release would be judging by the "summary" we've made in the changelog prior to a release. I agree now however that we can be more lenient on just increasing it to a patch, minor or even major base on what changes we do in a PR or even something like that.

I have made an issue for following up your request @vnys #1964
Now we need this PR approved as its blocking for our next release 😅


Combining yolov8 with midas

How do i apply midas to a particular pixel such that it inly applies to the centroid of the bounding box of an object detection label of yolo v8

If I understood your request correctly, then the easiest way is to apply midas to the entire image, take a box crop, and then inside the crop, either select the center pixel, or find the pixel with the highest value (for example, using np.max or cv.minMaxLoc)

@ElNino9495 Hello, I also tried to combine yolov8-seg with the midas model so that the output contains the features of both networks. As shown in the figure below：

but I don’t know how to do it specifically. Have you made any progress?I would be grateful if you can provide any help.


Crawl hangs since over a week

Describe the bug
A crawl was started but it doesn't ever finish. The UI only shows "Crawling...". This status has lasted for over a week now.
Fully stopping docker and starting it again didn't help. I'm not sure where to find debug information for this issue, therefore excuse the vagueness. Please let me know which information I can add.
To Reproduce
No steps to reproduce, happens randomly. So far only twice, both projects during the same day. Since then it hasn't occurred again.
Expected behavior
Crawl either finishes successfully or breaks on no activity after a certain amount of time or after a configured max timeout. An option to cancel the crawl would be a nice feature to have (as in https://github.com/StJudeWasHere/seonaut/issues/4). The option to delete the project (and thus also cancel the crawl) could also be available at all times, even when a crawl is running.

The issue you describe could be caused by the crawler crashing at some point or by SEOnaut being restarted while crawling a site. Once SEOnaut restarts, the crawler doesn't automatically start, but the unfinished crawl is still marked as "crawling" in the database. If this happens again, you can check the Docker logs to see the error stack trace. That would help us pinpoint the issue.
On the other hand, make sure you are using the latest code available, as some bugs have been fixed in this regard. Also, I pushed a change today, so restarting SEOnaut will cleanup the database if needed.
Adding an option to cancel a crawl is in the backlog too, and it will be added at some point.
I'm closing the issue as I think this is already fixed in the latest code, but feel free to open it again if this keeps happening.
Thanks for reporting the issue.


Database hygiene

In some cases the database will contain outdated records, and the only way to 'update' it is to remove the database (~/.mentat/chroma). One case in particular is if you change between chunker_line and chunker_llm, it won't update the db record.
Potential solutions:

[ ] Add more fields or a checksum to the collection name
[ ] Add chunker-type-specific data so 'Chunker[type].is_complete' checks for a record of that type specifically
[ ] Refresh the database every time 'version' is updated.

If you cancel while it's chunking, it leaves a corrupt record

New plan:

[ ] db record fields should be annotator-specific, e.g. 'chunks_llm' or 'chunks_line', so they can maintain a single record.
[ ] put everything in a single collection, tagged to ragdaemon minor version
[ ] add db scripts to backup, inspect, and recover from corrupted records (go thru all records and validate one-by-one).

Conventions to follow:

A file/chunk record should only depend on itself, not any other nodes. This way if two repos have the same doc (like an empty src/__init__.py, using the same db record is fine.


Typescript SDK using ADLAdapter SharedKey throws "Invalid character in header content ["Authorization"]"

tried using ADLSAdapter typescript and its failing in Authorization while reading the manifest.cdm.json file.
Err Info:
code:"ERR_INVALID_CHAR"
message:"Invalid character in header content ["Authorization"]"
stack:"TypeError [ERR_INVALID_CHAR]: Invalid character in header content ["Authorization"]
at ClientRequest.setHeader (_http_outgoing.js:529:3)
at new ClientRequest (_http_client.js:241:14)
at Object.request (https.js:314:10)
at C:\Users\Arun\source\repos\BMCL_Adf\CDM-Typescript\bmcl_cdm\libs\CDM-master\objectModel\TypeScript\lib\Storage\request.js:54:29
at new Promise ()
at C:\Users\Arun\source\repos\BMCL_Adf\CDM-Typescript\bmcl_cdm\libs\CDM-master\objectModel\TypeScript\lib\Storage\request.js:35:16
at Generator.next ()
at C:\Users\Arun\source\repos\BMCL_Adf\CDM-Typescript\bmcl_cdm\libs\CDM-master\objectModel\TypeScript\lib\Storage\request.js:10:71
at new Promise ()
at __awaiter (C:\Users\Arun\source\repos\BMCL_Adf\CDM-Typescript\bmcl_cdm\libs\CDM-master\objectModel\TypeScript\lib\Storage\request.js:6:12)"
ADLSAdapter.ts ->
private applySharedKey(sharedKey: string, url: string, method: string, content?: string, contentType?: string): Map<string, string>
3rd header item of Authorization has malformed or someting...
need some info to proceed further and it would be really helpful.

After comparing to c# code have corrected typescript code in ADLSAdapter.ts below function Line no starting 324
    private applySharedKey(sharedKey: string, url: string, method: string, content?: string, contentType?: string): Map<string, string> {
        const headers: Map<string, string> = new Map<string, string>();

        // Add UTC now time and new version.
        headers.set(this.httpXmsDate, new Date().toISOString());
        headers.set(this.httpXmsVersion, '2018-06-17');

        let contentLength: number = 0;

        const uri: URL = new URL(url);

        if (content) {
            contentLength = Buffer.from(content).length;
        }

        let builder: string = '';
        builder += `${method}\n`; // verb;
        builder += '\n'; // Content-Encoding
        builder += ('\n'); // Content-Language.
        builder += (contentLength !== 0) ? `${contentLength}\n` : '\n'; // Content length.
        builder += '\n'; // Content-md5.
        builder += contentType ? `${contentType}; charset=utf-8\n` : '\n'; // Content-type.
        builder += '\n'; // Date.
        builder += '\n'; // If-modified-since.
        builder += '\n'; // If-match.
        builder += '\n'; // If-none-match.
        builder += '\n'; // If-unmodified-since.
        builder += '\n'; // Range.

        for (const header of headers) {
            builder += `${header[0]}:${header[1]}\n`;
        }

        // Append canonicalized resource.
        const accountName: string = uri.host.split('.')[0];
        builder += '/';
        builder += accountName;
        builder += uri.pathname;

        // string accountName = uri.Host.Split('.')[0];
        // builder.Append("/");
        // builder.Append(accountName);
        // builder.Append(uri.AbsolutePath);

        // Append canonicalized queries.
        if (uri.search) {
            const queryParameters: string[] = uri.search.split('&');

            for (const parameter of queryParameters) {
                const keyValuePair: string[] = parameter.split('=');
                builder += `\n${keyValuePair[0]}:${keyValuePair[1]}`;
            }
        }

        // hash the payload
        const dataToHash: Buffer = Buffer.from(builder.trimRight());
        const bytes: Buffer = new Buffer(sharedKey);

        const hmac: crypto.Hmac = crypto.createHmac('sha256', bytes);
        const signedString: string = `SharedKey ${accountName}:${hmac.digest('base64')}`;
        headers.set(this.httpAuthorization, signedString);

        // hmac.on('readable', () => {
        //     const data: string | Buffer = hmac.read();
        //     if (data) {
        //         const signedString: string = `SharedKey ${accountName}:${data.toString('base64')}`;
        //         headers.set(this.httpAuthorization, signedString);
        //     }
        // });

        // hmac.write(dataToHash);
        // hmac.end();

        return headers;
    }

Getting 'timeout' exception in below location
protected async executeRequest(httpRequest: CdmHttpRequest): Promise
in NetworkAdapter.ts line no 87
its throwing TimeOut exception

ADLSAdapter.txt
Fixed the above issue, please find the code attached in the .txt file..
Now I am facing other issue,
PersistenceLayer | Failed to write to the file 'digitalTwin.manifest.cdm.json' for reason Error: Could not create folder for document /manifest/digitalTwin/digitalTwin.manifest.cdm.json | saveDocumentAsAsync

hi, does /manifest/digitalTwin/ folder exist?

This issue i had fixed in the typescript code,

the date for the date header  was in ISO instead of UTC (line 328)
in line 342 where, the string build  with some extra ()
missing the account name in the string (line 358-361)
the sharedKey was not converted from base64 before using in hmac
the whole lines of hash creation was messed (382-385)

ADLSAdapter.txt
Plz find the code changes from attached file.
After fixing this I am getting other issues.

Not able to save the manifest.cdm.json file

TypeScript SDK: Fixes sharedKey signature creation for ADLS access #160
This issue fixed by above changes.

hi, does /manifest/digitalTwin/ folder exist?

Yes, it exist.

Ok. Thank you for your note. We will look into and get back to you.

Hi Akkilz,
Sorry for the late response. And sorry for not saying in advance but we currently do not support accepting PRs from GitHub. The fix for Typescript sharedkey header exception is now published to this repo. Most of your changes are included except the line builder += ('\n').
Are you still getting the error when saving the manifest file now? Can you please open a new issue to differentiate with this Typescript auth issue if it is still happening so that we can better track it?
Thanks,
Yijing


Improve: add upload dialog with DatasetDialogUploadComponent for file uploads

Description

What does this PR do?
This PR introduces a new DatasetDialogUploadComponent to handle file uploads in a dedicated dialog.
Breaking changes

Code review focus

Ensure the DatasetDialogUploadComponent is properly integrated and functions as expected.
Verify dialog closure logic in DatasetDialogUploadComponent.

Dependencies

Checks

[ ] Summary updated
[ ] Version view updated
[ ] Documentation added
[ ] Tests added
[ ] E2e tests created
[ ] Successfully ran e2e tests before merge

closes GH-

Functionality is all there, the new upload dialog makes the application more consistent and user friendly.
Before we can merge it, I would like to address two things:

The bug mentioned in the issue still occurs. This is probably caused by the fitsServiceAvailable variable not being loaded correctly.

If we want to change our main button type to FAB, we have to keep it consistent in the whole application. This should be discussed with the whole team. I am in favor of not changing our standard button design. The main purpose of FAB buttons is to enable the main action of an app, like save e.g. Read more here in the styleguide.

Functionality is all there, the new upload dialog makes the application more consistent and user friendly.
Before we can merge it, I would like to address two things:
* The bug mentioned in the issue still occurs. This is probably caused by the fitsServiceAvailable variable not being loaded correctly.

* If we want to change our main button type to FAB, we have to keep it consistent in the whole application. This should be discussed with the whole team. I am in favor of not changing our standard button design. The main purpose of FAB buttons is to enable the main action of an app, like save e.g. Read more here in the [styleguide](https://m3.material.io/components/floating-action-button/overview).

@ValentinFutterer,
Thank you for your feedback! Here’s my input regarding the points mentioned:
1.	Bug with fitsServiceAvailable:

I’ll investigate this further to ensure that the fitsServiceAvailable variable is loaded correctly and the issue does not persist. Maybe we can have a meeting for it.
2.	FAB Button Design Consistency:
already posted in our chat group about this decision, and your reaction indicated agreement. But happy to revisit this topic again.
Let me know if there are other concerns or clarifications required!

About the preview bug, maybe you can take inspiration from this: https://github.com/tuwien-csd/damap-frontend/pull/392
Yes i didnt look at it in depth back then. I researched FAB buttons today, i didnt know about this either.


Enable RPC forward

The Replica could be used to submit txs

Codecov Report

Merging #381 (8490b1e) into develop (0667c10) will increase coverage by 16.02%.
The diff coverage is n/a.

:exclamation: Current head 8490b1e differs from pull request most recent head 23d5733. Consider uploading reports for the commit 23d5733 to get more accurate results

@@             Coverage Diff              @@
##           develop     #381       +/-   ##
============================================
+ Coverage    71.15%   87.18%   +16.02%
============================================
  Files           68       34       -34
  Lines         2330     1116     -1214
  Branches       351      160      -191
============================================
- Hits          1658      973      -685
+ Misses         672      143      -529

Flag
Coverage Δ

batch-submitter
?

contracts
87.18% <ø> (ø)

core-utils
?

data-transport-layer
?

message-relayer
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...itter/src/batch-submitter/state-batch-submitter.ts

...ices/l1-ingestion/handlers/transaction-enqueued.ts

packages/core-utils/src/common/hex-strings.ts

packages/core-utils/src/alias.ts

packages/core-utils/src/watcher.ts

packages/core-utils/src/l2context.ts

packages/core-utils/src/coders/sequencer-batch.ts

packages/core-utils/src/common/misc.ts

packages/message-relayer/hardhat.config.ts

packages/data-transport-layer/src/utils/common.ts

... and 24 more

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 0667c10...23d5733. Read the comment docs.


fix docs references

What does this PR do?
fix missing refences
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests? [not needed for typos/docs]
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[ ] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Hello @Borda! Thanks for opening this PR.

In the file docs/source/conf.py:

Line 46:5: E265 block comment should start with '# '

Do see the Hitchhiker's guide to code style

Hello @Borda! Thanks for opening this PR.

In the file docs/source/conf.py:

Line 46:5: E265 block comment should start with '# '

Do see the Hitchhiker's guide to code style


Refactor: Remove @LegacyFileIO and Make DelegationRefreshToken use new cluster.yaml

Summary
Let's start refactoring the old code out 🙌
There are two refactors:

Remove old FileIO instance provisioned via FsStorageProvider

// old code
public class MainApplicationConfig
  @Bean
  public FileIO provideIcebergFileIO() {
         return new HadoopFileIO(fsStorageProvider.storageClient().getConf())
  }

DelegationTokenRefresher should use the new cluster.yaml

 // new cluster yaml
storages:
  default-type: "hdfs"
  types:
     hdfs:
        rootpath: "/tmp/unittest"
        endpoint: "hdfs://localhost:9000"
        parameters:
           token.refresh.enabled: "true"             <----------- THIS
           token.refresh.schedule.cron: "* * * * * ?"          <----------- THIS

There are no major changes to code otherwise.
Changes

[X] Refactoring
[X] Tests

Testing Done
✅ Added unit tests for token refresh that were missing before 🥳
✅ mint build and existing tests pass
✅ manually tested token refresh code in docker setup
✅ manually tested fileIO code in docker setup

cc: @ctrezzo


EDP API : edb.components.set_solder_ball, height depends on the diameter.

Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

Description of the bug
The height of the solder ball is depending on the diameter:

Steps To Reproduce
The height of the solder ball is depending on the diameter.
Which Operating System are you using?
Windows
Which Python version are you using?
3.8
Installed packages
pyaedt 0.7

@Ouam74 , I fixed this bug. Please wait for the merge.


Running gemini against Node 8 and npm 5

In the one of the company's project, it is configured to use the stable version of Node on Travis build. It was working with the previous version (node 7.10.0 and npm 4.2.0), but as now the stable version resolves to node 8.1.2 and npm 5.0.3, the building cannot be done due error while runing gemini test test/visual.
Gemini version is 4.19.3:
"gemini": {
   "version": "4.19.3",
   "resolved": "https://registry.npmjs.org/gemini/-/gemini-4.19.3.tgz",
   "integrity": "sha1-xm+jNz/3RVlwNfspd7T7BOi2Y/4=",
   "dev": true
}

Below is the log taken from Travis:
Updating nvm
nvm.install
$ nvm install stable
Downloading and installing node v8.1.2...
Downloading https://nodejs.org/dist/v8.1.2/node-v8.1.2-linux-x64.tar.xz...
######################################################################## 100.0%
Computing checksum with sha256sum
Checksums matched!
Now using node v8.1.2 (npm v5.0.3)
cache.1
Setting up build cache
$ export CASHER_DIR=$HOME/.casher
0.03s$ Installing caching utilities
0.00s
attempting to download cache archive
fetching PR.56/cache-linux-trusty-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855--node-stable.tgz
found cache
adding /home/travis/build/vaadin/vaadin-board-demo/node_modules to cache
creating directory /home/travis/build/vaadin/vaadin-board-demo/node_modules
$ node --version
v8.1.2
$ npm --version
5.0.3
$ nvm --version
0.33.2
install.1
$ npm install
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN board-demo@ No repository field.
npm WARN board-demo@ No license field.
up to date in 8.952s
install.2
$ npm install -g bower
npm WARN deprecated<EMAIL_ADDRESS>..psst! While Bower is maintained, we recommend Yarn and Webpack for *new* front-end projects! Yarn's advantage is security and reliability, and Webpack's is support for both CommonJS and AMD projects. Currently there's no migration path but we hope you'll help us figure out one.
/home/travis/.nvm/versions/node/v8.1.2/bin/bower -> /home/travis/.nvm/versions/node/v8.1.2/lib/node_modules/bower/bin/bower
+<EMAIL_ADDRESS>added 1 package in 3.983s
install.3
$ npm install gemini-sauce
npm WARN board-demo@ No repository field.
npm WARN board-demo@ No license field.
+<EMAIL_ADDRESS>updated 1 package in 8.265s
install.4
$ bower install
$ gemini test test/visual
module.js:598
  return process.dlopen(module, path._makeLong(filename));
                 ^
Error: The module '/home/travis/build/**/node_modules/png-img/build/Release/png_img.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 51. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).

@DiegoCardoso
According to the log:
Error: The module '/home/travis/build/**/node_modules/png-img/build/Release/png_img.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 51. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).

It seems that you have installed all node_modules of gemini using one version of node and npm,  but then you try to run gemini on another.
Do you use any cache for node_modules in travis?

@eGavr I noticed the cache in Travis, but I couldn't try yet to remove it in order to test again. When I am able to test it, I'll try to remove all the cache and see if it works. Hopefully this is the problem. Then I'll give you the feedback about that.
Thanks!

@DiegoCardoso
Did you manage to solve your problem with caches in travis? Can I close this issue?

@DiegoCardoso ping ;)

Closed due to no activity


Feature/support x json stream

Pulled everything from develop into the feature branch, made sure all changes were there and looked at the json that was sent to the server.
@chrwend It's be cool if you look at it and confirm that it's working. :) Thx buddy!

closing -> master branch instead of develop. Sorry!


Fix mmperf and sharktank to use A100 runner

Since - gpu is will use T4 GPU runner, change MMPerf and SharkTank workflow to use - machine-type=a2-highgpu-1g to get the exact spec of A100 GPU runner, as they are doing benchmarking

Both workflows are already failing (but runners are correct). Filed the bug #14287


SSH tunnel in oracle url connection with more than one port forwarding needed

Is your feature request related to a problem? Please describe.
I'm trying to setup a connection to an oracle db in high availability that I can't connect directly. To connect to it I need to use an ssh tunnel but I have to use the url connection and it has 2 separate endpoints that needs to be tunneled. The main issue is that right now I can't configure more than one port forwarding with SSHj when I need both to make the connection work well. Is there a way that I'm missing?
Describe the solution you'd like
It might be nice to have a method to add multiple ports for single ssh tunnel
Describe alternatives you've considered
Right now I can make it work only with putty externally that opens me a tunnel with more than one port.

Hello @phate89
Did you try to use Jump SSH Server?

https://github.com/dbeaver/dbeaver/wiki/SSH-Configuration#configuring-gateway-host

That's exactly what I'm trying to use. But I'm using a url connection with 2 servers in it. Url connection requires a manual configuration of port forwarding and afaict there's only space for one port forwarding..I need two because the DB is balanced and I can't connect to only one of the two


Drops Refactor

Similar to the way we worked on integrating Nuxt3 in a separate branch until all bugs were cleared and then we merged
i propose we do same for drops
Problem
I find the drops related code much harder to read and maintain compare to other parts of our app
here are some of the reasons why

too many props passed, example: mint button props are being passes PaidGenerative ->GenerativeLayout -> GenerativePreview -> MintButton and finally into NeoButton
i don't see a good reason for this pattern. state should be calculated close to where it is used, info can be shared via composables,
like we do elsewhere in the app
long long components, probably as side affect of 1, PaidGenerative again for example is too long
complicated computed props, for example, PaidGenerative -> mintButtonDisabled is hard to read
function props: this looks like react pattern and not something i've seen elsewhere in the code. like GenerativeLayout props.handleSelectImage. this should be done via event emit, composable, or if really needed, Provide/Inject API

Call To Action
@kodadot/internal-dev  please feel free to

add to the list above
break this down to smaller tasks and grab them

PR's to Drops Refactor branch
cc @vikiival @yangwao

I Agree, i also find it very hard to read and any small change takes me quite a time to find and implement.

props drilling

I would not find is as an issue, however lot of code mess comes from Hack it as you go :).
I expect that any major schema change is not going to happen, so it is a right time to refactor stuff

too many props passed

I completely agree with this one. I put the title "little bit clean up" in this PR: https://github.com/kodadot/nft-gallery/pull/9534 because I want to raise the same thing about this. Finally, someone feels the same way.

this should be done via event emit, composable, or if really needed, Provide/Inject API

I agree. We also can use shared state/store 👍🏻
For me, I put event emit on the last option (I don't think it is suitable for the props drilling case). But, as long as it can help and does not drill down the props too deep, it is still good to go for me.
refs:

https://vuejs.org/guide/components/provide-inject
https://vuejs.org/guide/reusability/composables.html#composables
https://nuxt.com/docs/getting-started/state-management

I put event emit on the last option

sure, i didn't list it on order of preference
anything to get us out of this props drill mess in a nice, readable, clear maintainable way is good
shared store with maybe some util composables on top will probably work nicely

Tasks:

[ ] Unify minting across variations (ref)

Closing for the sake of #9575
Duplicate of #9575


Icons in the glance card

Icon size in the glance card is larger than in entities card

As designed. Why not?

It seems to me that icons of the same size will look better

I'll try. But on the web glance card icons looks too small for me.

Ultimately, you decide. Thank you


Fix alignment issue with default container width

@tisto @sneridagh Screenshots

@jackahl also tell me if this is acceptable giving the initial specs of the block, and if it's going to affect existing projects.

Maybe I don't fully get how flexbox works. However, won't the size of the logo affect this? On the screenshot, it looks pretty good though.

Maybe I don't fully get how flexbox works. However, won't the size of the logo affect this? On the screenshot, it looks pretty good though.

No, my current implementation only changes the alignments of logo.

@sneridagh screenshots

Did you check on mobile? I guess it would be no margin now.

I fixed it now. Margin is already removed.

I tested it with two logos, I don't think this is what we have in mind:
@tisto we can't go full width with the logos, can we meet and specify it a bit better?

@jackahl which was the initial spec?

@iFlameing I decided with Timo that this will go in .com only. We will use this solution for blocks >= 3, and the current solution for below this. So close this one, I will add a ticket for the .com site.

@iFlameing I just realised that we didn't implement this. We decided that we will go with this fix (images tight with the container in .com only.


Docs/art gallery dockerization research

Initial commit for dockerization research notes

Hi Chloe, this one has a few Vale formatting errors, please see below:
docs/ArtGallery/DockerizationResearchNotes.md:
Line 57, position 25 (rule thothtech.SentenceSpacing)
error: "r.B" must contain one and only one space.
More information: TBA
docs/ArtGallery/DockerizationResearchNotes.md:
Line 57, position 46 (rule thothtech.SentenceSpacing)
error: "r.S" must contain one and only one space.
More information: TBA
docs/ArtGallery/DockerizationResearchNotes.md:
Line 57, position 55 (rule thothtech.SentenceSpacing)
error: "s.A" must contain one and only one space.
More information: TBA
docs/ArtGallery/DockerizationResearchNotes.md:
Line 60, position 3 (rule thothtech.SentenceSpacing)
error: "p.M" must contain one and only one space.
More information: TBA


Button for "Next Page"

Describe the feature you'd like
A clear description of the feature you'd like implemented in BookStack.
As of now, when a page was read, it is necessary to scroll back to the top and click on the next page on the left-hand navigation. To make this more intuitive and more booklike, IMO there should be a button to get to the next page automatically - without the need to ask yourself where you are again.
The same actually applies for a "previous page" button, but "next page" is more important ;)
A button with a simple arrow would suffice I guess.
Describe the benefits this feature would bring to BookStack users
Bookstack wants to be a simple virtual library - or so I have understood. When reading a book, I don't go back to the list of contents after each page/chapter to see where I should go next, but just flip the page. This feature should be somewhat simple to implement (at least from my newbie perspective) and would bring a more or less basic feature for an awesome software with the word "book" in its name :)

Thank you for the fast feedback! Somehow I missed that on my search... 👍🏻


[MINOR] Update arrow-rs dependencies

Bring in the latest arrow-rs branch
I will eventually automate this process, but for now I will do it manually.

@alamb I think you also need to update the other crates

@alamb I think you also need to update the other crates
Good call @Dandandan  will do

Please take a look at the related https://github.com/apache/arrow-datafusion/pull/23

@alamb Would it make sense for DataFusion to re-export Arrow so that dependent crates automatically get the same Arrow version?

@alamb Would it make sense for DataFusion to re-export Arrow so that dependent crates automatically get the same Arrow version?

This would make things much easier for consumers, +1 from me :)
On the automation front, has anyone else used Dependabot for this kind of thing before? I've started using it recently for Python, Rust, and the actual actions in my GHA workflows, and it's really nice, e.g. open dependency PRs for my convergence crates as defined with some trivial metadata.

@alamb Would it make sense for DataFusion to re-export Arrow so that dependent crates automatically get the same Arrow version?
This would make things much easier for consumers, +1 from me :)

Good idea @andygrove  and @returnString  -- I filed https://github.com/apache/arrow-datafusion/issues/36 to do so

On the automation front, has anyone else used Dependabot for this kind of thing before?

I have not, but it sounds like a good idea to me. Filed https://github.com/apache/arrow-datafusion/issues/37


Fix/anchor link

This PR fixes this issue #1482
By fixing this issue, I realized we can refactor the code to add a common layout for all pages except the errors pages.

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


[csolution] Add a flag/command to retrieve the created-for value from csolutions

Csolution projects now have a created-for flag e.g. https://github.com/Arm-Examples/Hello_MIMXRT1064-EVK/blob/855f0389a1044bb27c70b139d335786cceec024e/hello.csolution.yml#L3 to describe the minimum version of tools to use so that they understand the project definition. This piece of data is really valuable to know which projects are supported by our tools and we would like to retrieve it in a sustainable way. Thus, we would like to request a flag or a command on the csolution binary so that this value can be returned

Conceptually a consumer should read the created-for node before choosing which tool version to use. It sounds odd having to run the tool to retrieve this info.
We should guarantee a reasonable immutability of this node during the whole tool's life-cycle.

I suggest that tools tolerate missing information to some level. created-for is optional an just an indicator.
Attached is an example of how tools should react.
Hello-Broken.zip
When using cbuild there are clear error messages:
C:\Test\Hello-Broken>cbuild hello.csolution.yml
info cbuild: Build Invocation 2.1.0 (C) 2023 Arm Ltd. and Contributors
error csolution: compiler: value not set
error csolution: processing context 'Hello.Debug+AVH' failed
error csolution: compiler: value not set
error csolution: processing context 'Hello.Release+AVH' failed
error cbuild: exit status 1

@brondani, that is what we are trying to achieve, but the consumer is indirect, via the website/services. In the development of the website we are trying to establish a fixed interface between the backend services and the CMSIS ecosystem to expose the information to the end consumer.
This would enable us not only to provide an indication to the user of which version of the tools they might require, but it would also allow any validation CI to use the most suitable tools. @ReinhardKeil I agree that if the information is not there, then this shouldn't be breaking, but I hope that for our official examples we would make the effort to include this information and improve the UX.
For context, maintaining the services is an overhead so we try to automate as much as possible. Updating our services to automatically pull in updated tools that understand multiple schema versions and are maintained in line with schema updates, is much more sustainable than updating the service to support new schemas.

See #1177


Model 1 results for warping is unexpected

I implemented the code as mention in this repo and cp-vton repo.
Everything is working fine, but the model results from the part 1 model is not as expected,
Would like to if there is a specific formats of input one has to give, I have kept all inputs as per your code and data preparation code from cp-vton repo.

for simple inputs like
image

and
image

Could you give me more information?

How did you obtain warp-person.jpg? Is it a warped cloth layered on the person image?
What did you input? You need cloth mask, parsed person (by LIP) and pose (by OpenPose) in addition to the pair of person and cloth.

Also, I'm not sure about the extrapolation performance of VITON-GAN. The dataset I used only contains female models.

Hi @shionhonda @pratiklodha95 I got the same results. Even on the original test files, using the provided GMM epoch 99 file.

Thoughts?

Thanks for reporting @jakubLangr .
That is weird because the result in my local repository looks fine.

I might have provided different GMM model file. Let me check.

I did reproduce the successful result by 1) cloning this repository, 2) downloading the dataset and the trained model gmm_epoch_99.pth, and 3) running python run_gmm.py.
Could you check if the trained model is successfully loaded, please? I doubt if TPS transform is really working in your case.

Hi @shionhonda I went ahead and trained your algorithm from scratch. These are the results from my training run over the weekend. The images seem within norms so it seems that the training code for GMM is working on my machine.

However, I am fairly confident that the pretrained epoch_99 checkpoint is used correctly, as I do not get any file not found errors or similar and the path seems to match the requirement.
I do agree with your suggestion that it is likely that TPS is not working, but I am not sure why.
I am now re-running it on the freshly re-trained model.
Out of curiosity, what setup are you using (Pytorch / Cuda versions?) & OS?

On re-run with my re-trained model the results are somewhat better. But I am still confused as to why the neck gets removed?

@jakubLangr
Glad to see that your re-running looks fine. But I'm not sure why as well.
I used the setup like:

PyTorch 1.2.0 (it should be fine if > 1.0)
CUDA 9.0
Ubuntu 16.04

Necks are removed in LIP.
http://sysu-hcp.net/lip/parsingchallenge.php


Build pipeline

This configuration builds the application and produces builds for both Debug and Release configurations.

This configuration builds the application and produces builds for both Debug and Release configurations.


Project deletion from modal seems broken

Steps to reproduce:

go to https://demo.unpoly.com/projects
click on any project
click delete

the modal now shows all companies. It should (imo) close the modal and go back to the previous projects page (preferably with a flash message that the project was removed successfully) and update the projects page to no longer include that project.

 I wonder if we should redirect to projects_path here instead.
https://github.com/unpoly/unpoly-demo/blob/f33743ecda448c0bb193138701da8b5dfb696f93/app/controllers/projects_controller.rb#L35

That would be a band-aid at least. From an UX perspective I think it should get closed and the user should somehow be informed about it. I know that those issues might seem minor, but it would nicely show how to properly use unpoly


remove jupyter_kernel.lock files

seem to be introduced by #1060
@tanujkhattar

mea culpa. This file shows up because of my unreliable solution to get the notebooks to run in parallel


Source code instead of content

Hey!
We have been running nextra for almost two years. Now we found out, that it shows source code instead of content.
{
  "name": "docs",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "scripts": {
    "dev": "next",
    "start": "next start",
    "build": "next build"
  },
  "dependencies": {
    "add": "^2.0.6",
    "next": "11.1.2",
    "nextra": "1.1.0",
    "nextra-theme-docs": "1.2.6",
    "react": "17.0.1",
    "react-dom": "17.0.1"
  }
}

Build is ok, but after running server it shows in the browser:
import { useRouter } from 'next/router' import Page_0 from './index.cs.md?nextra-raw' import Page_1 from './index.en.md?nextra-raw'
export default function I18NPage (props) { const { locale } = useRouter() if (locale === 'cs') { return <Page_0 {...props}/> } else if (locale === 'en') { return <Page_1 {...props}/> } else { return <Page_1 {...props}/> } }

Do you know how to handle this?
Thank you.

Hi! I believe this is not happening in the latest @beta or @alpha, could you try upgrading the package? (We are going to release the latest @alpha as stable soon!)

2.0.0-beta.5 works. Thanks.


'React/Core/RCTConvert.h' file not found

After migration to the RN version 0.60.5 i was trying to follow the main installation guide but first got an error that RNFastImage is not found in native modules.
So then I find the issue on the repo and made pod install with adding to my pod file this:
rn_fast_image_path = '../node_modules/react-native-fast-image'

pod 'RNFastImage', :podspec => "#{rn_fast_image_path}/RNFastImage.podspec"

After that, I got another bug "'React/Core/RCTConvert.h' file not found"
Expected behavior
No errors in building in xcode
Dependency versions

React Native version: 0.60.5
React version: 16.8.6
React Native Fast Image version: 7.0.0 (initially i was trying the current 7.0.2) version

I have exactly the same problem. Did anybody find the solution ?

I confirm. This is an issue on my end too.

I have same problem. I can't solve it. HELP!!!

I'm having this issue, but using an older version of react native:
Dependency versions
-React Native version: 0.59.10
-React version: 16.8.3
-React Native Fast Image version: 7.0.2

same

I had the same issue with other packages after upgrade.
The error was gone only when I created a new repo in the new version and copied my files over.


rename_forward tests

I have added test_functional suite that reuses scenarios from linked_data app.
test_forms suite from linked_data seems useless for rename_forward app since it won't test any other functionality.
I am thinking of writing tests that checks if Select2 widget is rendered correctly, especially the forward configuration part (perhaps we can add something like that to linked_data app). The other good thing to test can be LinkedDataView to check if we're running functional tests with properly working view (the forward feature itself does not add any features to DAL views).

Codecov Report

Merging #833 into master will increase coverage by 0.72%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #833      +/-   ##
==========================================
+ Coverage   96.31%   97.04%   +0.72%
==========================================
  Files         123      124       +1
  Lines        2092     2099       +7
==========================================
+ Hits         2015     2037      +22
+ Misses         77       62      -15

Impacted Files
Coverage Δ

test_project/rename_forward/test_functional.py
100% <100%> (ø)

src/dal/widgets.py
98.7% <0%> (+2.59%)
:arrow_up:

test_project/rename_forward/models.py
100% <0%> (+10%)
:arrow_up:

src/dal/forward.py
96.15% <0%> (+19.23%)
:arrow_up:

test_project/rename_forward/urls.py
92.85% <0%> (+50%)
:arrow_up:

Continue to review full report at Codecov.

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

I can't find a way to assert that a particular url was used with an AJAX request with the python/selenium we have. Perhaps the only way to test it is to make the view only returns choices if a particular field was renamed and forwarded completely.
You don't need the other tests from linked data I think. It looks like just a scenario like:

open rename_forward admin form,
fill in some field that will be forwarded+renamed,
type something in the autocomplete,
have the view return something expected if the forward+rename worked,
assert that the select2 widget has the right value.

What do you think ? That's just one functional test but I think it would cover the rename feature for the next year(s).

You don't need the other tests from linked data I think. It looks like just a scenario like:

open rename_forward admin form,
fill in some field that will be forwarded+renamed,
type something in the autocomplete,
have the view return something expected if the forward+rename worked,
assert that the select2 widget has the right value.

This is exactly what linked_data.test_functional.AdminLinkedDataTest.test_filter_options do. And this scenario works for rename_forward. Other scenarios test the same functionality in inline forms and I think that these scenarios can be actual in rename_forward (something can go wrong with interferenction of get_forwards() and inline forms JS).

Do you mean that this test should fail if we remove the JS bit that does
the rename ?
Le 25 avr. 2017 8:38 PM, "Kirill Gagarski"<EMAIL_ADDRESS>a
écrit :

You don't need the other tests from linked data I think. It looks like
just a scenario like:

open rename_forward admin form,
fill in some field that will be forwarded+renamed,
type something in the autocomplete,
have the view return something expected if the forward+rename worked,
assert that the select2 widget has the right value.

This is exactly what linked_data.test_functional.Ad
minLinkedDataTest.test_filter_options do. And this scenario works for
rename_forward. Other scenarios test the same functionality in inline
forms and I think that these scenarios can be actual in rename_forward
(something can go wrong with interferenction of get_forwards() and inline
forms JS).
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/yourlabs/django-autocomplete-light/pull/833#issuecomment-297125495,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFxrK2myR7DNPoiYnEIHAgZL0v03emiks5rzj2JgaJpZM4M-Yof
.

If owner is not renamed to possessor by JS and 42 is not forwarded as
secret, then these tests will fail.
On Apr 25, 2017 21:58, "∞"<EMAIL_ADDRESS>wrote:

Do you mean that this test should fail if we remove the JS bit that does
the rename ?
Le 25 avr. 2017 8:38 PM, "Kirill Gagarski"<EMAIL_ADDRESS>a
écrit :

You don't need the other tests from linked data I think. It looks like
just a scenario like:

open rename_forward admin form,
fill in some field that will be forwarded+renamed,
type something in the autocomplete,
have the view return something expected if the forward+rename worked,
assert that the select2 widget has the right value.

This is exactly what linked_data.test_functional.Ad
minLinkedDataTest.test_filter_options do. And this scenario works for
rename_forward. Other scenarios test the same functionality in inline
forms and I think that these scenarios can be actual in rename_forward
(something can go wrong with interferenction of get_forwards() and inline
forms JS).
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<https://github.com/yourlabs/django-autocomplete-light/
pull/833#issuecomment-297125495>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAFxrK2myR7DNPoiYnEIHAgZL0v03emiks5rzj2JgaJpZM4M-Yof>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/yourlabs/django-autocomplete-light/pull/833#issuecomment-297131227,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGD-gEUmXe8qMOVblTigRzLwYlQqKKj6ks5rzkI3gaJpZM4M-Yof
.

if we remove the JS bit that does
the rename ?

BTW, currently it's hard to imagine because non-renaming forward now is a particular case of renaming forward. Renaming forward is "Take value from owner field and pass it to DAL view with key possessor". Non-renaming is "Take value from owner field and pass it to DAL view with key owner"

Yesss ! In this case of course please by all means merge this B)
I'm trying to test it as i'm speaking but I got some unrelated errors.

@jpic I am still thinking of adding python tests which ensure that widget is rendered correctly, especially forward configuration (and maybe one like this in linked_data).

That would be surely good value for DAL, but this PR already covers your changes so perhaps you want it merged rather sooner than later ?


Ensure Kernel#open remains private

Appears to fix #312.

:+1: and it looks more understandable than #313.

Build will be fixed by #320.

LGTM

@eventualbuddha can we get this merged ?

@smtlaissezfaire can we get this merged ?


[9.0.2] Issue when adding container layout using bootstrap5 grid

Affected Version of Concrete CMS
9.x
Description
I am attempting to split my are Area using custom layout but I keep getting an unexpected behavior.
How to reproduce
I did the following steps
Area > Add Layout > choose Bootstrap5 As grid option > Trying to split the layout on two equal columns by dragging the handles.

This has already been fixed in 9.0.2.

In the future please try to copy the version of the site you're demonstrating – I strongly suspect it's 9.0 or 9.0.1.

Yes my bad!
The core version 9.0.2 indeed, but I was using an old version of bedrock which caused the problem.

I'm still experiencing that issue (exactly the same behavior as shown above) on version 9.1.1.
It's impossible to set grid container layout colums using Bootstrap5.

I am having this issue with version 9.12 - would really love to find a solution its making using layouts impossible.
Concrete Version
Core Version - 9.1.2
Version Installed - 9.1.2
Database Version -<PHONE_NUMBER>4900
Hostname
ds1665.tmddedicated.com
Environment
production
Database Information
Version: 10.3.36-MariaDB
SQL Mode:
Concrete Packages
Cycle2 Slide Show (1.1), Modena Theme (2.0.4)
Concrete Overrides
None
Concrete Cache Settings
Block Cache - Off
Overrides Cache - Off
Full Page Caching - Off
Full Page Cache Lifetime - Every 6 hours (default setting).
Server Software
Apache
Server API
cgi-fcgi
PHP Version
7.4.30
PHP Extensions
bcmath, bz2, calendar, cgi-fcgi, Core, ctype, curl, date, dba, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imap, intl, json, ldap, libxml, mbstring, mysqli, mysqlnd, odbc, openssl, pcntl, pcre, PDO, pdo_mysql, PDO_ODBC, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, Reflection, session, shmop, SimpleXML, snmp, soap, sockets, SPL, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib
PHP Settings
max_execution_time - 300
log_errors_max_len - 1024
max_file_uploads - 20
max_input_nesting_level - 64
max_input_time - 600
max_input_vars - 1000
memory_limit - 2048M
post_max_size - 512M
upload_max_filesize - 512M
ldap.max_links - Unlimited
mbstring.regex_retry_limit - 1000000
mbstring.regex_stack_limit - 100000
mysqli.max_links - Unlimited
mysqli.max_persistent - Unlimited
odbc.max_links - Unlimited
odbc.max_persistent - Unlimited
pcre.backtrack_limit - 1000000
pcre.recursion_limit - 100000
pgsql.max_links - Unlimited
pgsql.max_persistent - Unlimited
session.cache_limiter - no value
session.gc_maxlifetime - 7200
soap.wsdl_cache_limit - 5
unserialize_max_depth - 4096


Signature Help not provided for the langlib functions

Description:
Consider the following source snippet
function testFunction() {
   http:Client testClient = new("http://localhost:9090");
   testClient.toString(<cursor>)
}

Do not get the signature help at the cursor position
Affected Versions:
v1.2.0-SNAPSHOT at least

when invoking toString() on a any value there is no pending parameter to be passed thus signatureHelp is not shown. However when there's langlib functions with more than one parameter it is correctly shown omitting first parameter.

thus i think this is the correct behaviour. wdyt?

This issue has been resolved with the latest implementation revamp. Hence closing the issue


Avoid compiler warning if no-strict-overflow is disabled

Codecov Report

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

@@           Coverage Diff           @@
##           master    #8986   +/-   ##
=======================================
  Coverage   52.25%   52.25%
=======================================
  Files         196      196
  Lines       24802    24802
  Branches     5155     5155
=======================================
  Hits        12961    12961
  Misses       9762     9762
  Partials     2079     2079

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 5d1b57f...3307ce3. Read the comment docs.


End Screens for Various Victory/Failure Endings

Suggestion: add a mark in the quest system for triggering particular end states, which create the screen, and end the game.  Create end screens with display text, graphics, and restart buttons, along with whatever else is needed for a full game loop.

I'll work on this

QuestStage currently has a field isWinState, but this should probably be replaced with something other than a boolean since we want to support multiple endings. The actual check of whether the player has achieved a quest state should probably happen at the end of Game.updateQuestState()

Generic structure and logic for these screens added in PR #33

I've closed PR #33 because we agreed at the meeting to take a different approach.
The design I have in mind is:

an Ending class with title: string and description:string (and we might add additional pieces to this later
remove the boolean isWinState from QuestStage because we want to allow many different types of endings
instead, give quest stages an optional field of type Ending | undefined that defaults to undefined, where if you reach a stage where it is defined the game ends with that ending
check for whether the player has reached a stage with an ending inside of Game.updateQuestState() since we want to perform the check any time a quest is advanced
a single UI page for endings, where the constructor takes in an Ending object and displays the title and description text provided by that ending object

But if anything about that sounds suboptimal to you feel free to propose a different plan.

resolved in PR #43 , which was merged. This issue can likely be closed pending further changes to the EndScreens, such as injection of arbitrary components (for HTML injections, displaying stats, etc)

oh also a note on PR #43 so we have a paper trail. We had to violate the access patterns in Game (Game has to call GameWindow.show) to get the ending state to update, and violate the privacy of questStage (via a getter function) to get cheats to work. The latter is already tracked in a comment in the source, but both should be made aware for any future refactoring.


pickupand dropoff location text not showing untill typed in

on program load

after typing and erasing text

also incorrect language placeholder

Thank you for reporting an issue. I will delete this Placeholder in the new version in the patch.
This text wasn't supposed to be there.
I will close this issue as soon as I fix this and replace the .exe file

Problem was fixed in pushed commit
You can download an exe from the last release to get an updated version


PermissionLevel/RoleDefinition selector

Category
[ x] Enhancement
[ ] Bug
[ ] Question
Version
We could use a PermissionLevel selector to let an admin select a PermissionLevel/RoleDefinition.

Looks like this has already been implemented as part of a previous pull request. #268

@russgove - could you please check if the implemented control fits your needs?


.NET 6 API Example Failing with Middleware Order Issue

I set up a basic example of a .NET 6 Web API with just WatchDog installed.  When I try to run the application, I get the following message:

System.InvalidOperationException
HResult=0x80131509
Message=EndpointRoutingMiddleware matches endpoints setup by EndpointMiddleware and so must be added to the request execution pipeline before EndpointMiddleware. Please add EndpointRoutingMiddleware by calling 'IApplicationBuilder.UseRouting' inside the call to 'Configure(...)' in the application startup code.

I have tested it on the example code, and I get a similar error. Here is the code from my Program.cs file:
using WatchDog;

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddControllers();
builder.Services.AddWatchDogServices();
builder.Services.AddEndpointsApiExplorer();
builder.Services.AddSwaggerGen();

var app = builder.Build();

app.UseWatchDogExceptionLogger();

app.UseWatchDog(opts =>
{
    opts.WatchPageUsername = "admin";
    opts.WatchPagePassword = "admin";
});

if (app.Environment.IsDevelopment())
{
    app.UseSwagger();
    app.UseSwaggerUI();
}

app.UseHttpsRedirection();

app.UseAuthorization();

app.MapControllers();

app.Run();

The error occurs on the app.UseWatchDog line.
Is there something I am missing?

That works. Thanks for the quick update!


Adding myself and OGA

Is this the right way to do things? I'm not very familiar with Git.

anonymous


Table of contents

I think it can be good to start with the structure of our awesome list. Choosing categories we will make it easier to find resources.
My suggestions:

[ ] Official Spark AR Pages
[ ] 3rd-party wikis and documentation
[ ] Tutorials and examples
[ ] Open source patches
[x] Snippets
[x] Gumroad sellers
[ ] Other relevant resources (blender etc.)

Here is my proposed table of content:

Official documentation and links
Patches
2a. Free patches
2b. Paid patches
Scripts
Tutorials
4a. Videos
4b. Articles
4c. Streams
Miscellaneous resources and collections (Such as Billy's Spark AR TV, and the wiki pages)

@recursiveIceCreamEater @hongweitang What do you guys think?

Yes! Though I eventually if we get a lot of patches maybe having them subdivided into groups could be really helpful, same with scripts. Eg:

Free patches
2.1 SDFs
2.2 3d related
2.3 Image retouching

(Fomated as 2.n and not 2.1.n because I can't figure out how to make GitHub markdown display it properly)

Free patches
2.1 SDFs
2.2 3d related
2.3 Image retouching

This might get to nested? I think following the requirement "Entries have a description unless the title is descriptive enough by itself." is the key. So we have to make it clear what the Patch does instead of categorizing them too much.

Here is my proposed table of content:

Official documentation and links
Patches
2a. Free patches
2b. Paid patches
Scripts
Example Projects
Tutorials
5a. Videos
5b. Articles
5c. Streams
Miscellaneous resources and collections (Such as Billy's Spark AR TV, and the wiki pages)

@recursiveIceCreamEater @hongweitang What do you guys think?

Markdown isn't really great for sub numbered lists (stronghold of tools such as LaText).
Yeah I like that list. I wonder if tutorial section is more relevant than resources to download? The focus can be on education first?

Free patches
2.1 SDFs
2.2 3d related
2.3 Image retouching

For the beginning it doesn't need to be this specific list of free patches. We can explain the content for the beginning. The categories here are quite specific.

Yeah, in any case, there aren't that many patches, you could just read all the titles in a minute. But as you said:

the requirement "Entries have a description unless the title is descriptive enough by itself." is the key

I wonder if tutorial section is more relevant than resources to download? The focus can be on education first?

Yeah, maybe this should go up on the 2nd place, and be named "Learning"? Same with "Example projects" before patches and scripts maybe?

For the beginning it doesn't need to be this specific list of free patches. We can explain the content for the beginning. The categories here are quite specific.
I agree. I also think we can make subcategories later if the list gets super big.

So the current proposal now is (numbers is just for order, and not needed in final ToC):

Official documentation and links
Tutorials/Learning
2a. Videos
2b. Articles
2c. Streams
Example Projects
Patches
4a. Free patches
4b. Paid patches
Scripts
Miscellaneous resources and collections (Such as Billy's Spark AR TV, and the wiki pages)

Yeah, maybe this should go up on the 2nd place, and be named "Learning"? Same with "Example projects" before patches and scripts maybe?

I agree, I'd rather have a learning section at the top, it'd be more friendly to beginners, who may not even know how to use GitHub (I myself only started a few months ago). I like the current proposal.
My question regarding patches now is the following: What to do with profiles/repositories with multiple things? Shall we get the links to every individual repo/folder and link them?

@recursiveIceCreamEater @hongweitang I've created a new repo for this in the branch awesome-spark-ar/structure-v2.
As you see we have a bit of a job writing descriptions for the content, but I think it's a good idea that we should not add links without titles and descriptions into that branch so we keep it clean from the start before we merge it into master.

My question regarding patches now is the following: What to do with profiles/repositories with multiple things? Shall we get the links to every individual repo/folder and link them?

Yes, I think that is the best. Take the latest stuff that we know is working with the  4-5 latest versions of Spark AR. We don't have to add all of it, but maybe the popular ones we get enough to have a good example of how things should be added. Then people can add their own title, description, and links in the future. We also need an contributing.md, I'll create an issue for that ASAP.

Yeah contributing.md will be great for that.
Exactly we should reduce it to relevant content or if its on youtube we can copy the link to playlists which are working as a series of lectures.
What you guys think about content like that? https://www.instagram.com/p/CBCZjsfjmsO/
Should that be added as some form of "Quick Tips" under tutorials?

Yeah, I think YouTube playlists should be fine, but channels are very different. Playlists can go under videos e.g. [TITLE OF PLAYLIST IF IT'S CLEAR]/(LINK) - DESCRIPTION OF SERIES. Maybe a rule can be that we only add playlists on a specific topic, such as Sohail's latest Scripting and Shaders?

What you guys think about content like that? https://www.instagram.com/p/CBCZjsfjmsO/
Should that be added as some form of "Quick Tips" under tutorials?

I think maybe Quick Tips / Tips and Tricks can be a top category as it's often different from a full tutorial.

Closing this issue as it looks like we have it well structured now.


Send ROUTE with bookmarks

bolt3 is not concerned by this change, since bookmarks are only needed in the scenario of a previous command creating a database (multi-database is not available in Neo4j 3.x-).
I added a change to include bookmarks when calling the procedure. Thanks!


SQL Connection w/Kerberos - Linux Ubuntu - Error Code 139

Description

I'm upgrading an app from .NET 5 to 6. Our SQL servers supports Kerberos. In Windows and macOS the .NET 6 upgraded app works fine, but in Linux Ubuntu 20.04 the dotnet watch run shows: watch : Exited with error code 139 when the app tries to execute a query against the SQL server.
The connection string I am using is this:
"Server=our-sql-server.com;Database=our-db;MultipleActiveResultSets=True;Max Pool Size=300;Trusted_Connection=True;"
Configuration

Which version of .NET is the code running on? 6.0.102
What OS and version, and for Linux, what distro? Linux Ubuntu 20.04
What is the architecture (x64, x86, ARM, ARM64)? x64
Do you know whether it is specific to that configuration? I tried on a Mac Mini w/ M1 and Dell w/ i7 and works fine

Regression?

Did this work in a previous build or release of .NET, or from .NET Framework? I tried it with .NET 5.0.405 and works fine everywhere.

Other information
About the stack trace, there is none. When run with debug it simply dies with no message. When run with dotnet run it just quits with no error. When run with dotnet watch run it shows: watch : Exited with error code 139.
I do not have any works around. I've been trying different connections strings options, but no luck!
With this simple app throws the error:
using Microsoft.EntityFrameworkCore;

var contextOptions = new DbContextOptionsBuilder<AppDbContext>()
    .UseSqlServer(@"Server=our-sql-server.com;Database=our-db;MultipleActiveResultSets=True;Max Pool Size=300;Trusted_Connection=True;")
    .Options;

await using var context = new AppDbContext(contextOptions);
var response = await context.Database.ExecuteSqlRawAsync("SELECT * FROM AnyTable"); // <-- this makes the app crash with no message

Console.WriteLine(response);

internal class AppDbContext : DbContext
{
    public AppDbContext(DbContextOptions<AppDbContext> options) : base(options)
    {

    }
}

maybe https://github.com/dotnet/SqlClient/issues/1390

maybe #1390

@danmoseley my google skills failed me on this one. Thanks for the issue #.

@ebeltran1981 no problem, there are many dupes - it's confusing. The workarounds are either change to Microsoft.SqlClient (nice if it's an option, as it's where new features are shipped) or stay on 5.0 (goes out of support in May) or paste in something like this until it's serviced in System.Data.SqlClient 6.0


Update rssm.c

Separate counters for udp and tcp query and response sizes

Oops, I have a typo in this PR. I'll resubmit it.


Extensions

📦 Pull Request
Provides a base implementation for extensions to Magic APIs
🗜 Versioning
(Check one!)

[ ] Patch: Bug Fix?
[x] Minor: New Feature?
[ ] Major: Breaking Change?

✅ Fixed Issues

No associated issue

🚨 Test instructions
Run yarn test
⚠ Update CHANGELOG.md

[x] I have updated the Upcoming Changes section of CHANGELOG.md with context related to this Pull Request.

https://github.com/MagicHQ/magic-js/blob/80e0aae510a055d7d1d06f4adc241e791014f234/src/types/core/json-rpc-types.ts#L8
Can we change this type to params: any;.
otherwise, lgtm.

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


authorizations not presented in human readable form for type 4 (EIP-7702) txs.

file: blockchain_tests/prague/eip7702_eoa_code_tx/eoa_code_txs/set_code_to_self_caller.json
this is a segment from the above file for a tx in block number 1. It has no authorization list, though the rlp contains such a list.
"transactions": [
                   {
                       "type": "0x04",
                       "chainId": "0x01",
                       "nonce": "0x00",
                       "maxPriorityFeePerGas": "0x00",
                       "maxFeePerGas": "0x07",
                       "gasLimit": "0x989680",
                       "to": "0xa94f5374fce5edbc8e2a8697c15331677e6ebf0b",
                       "value": "0x00",
                       "data": "0x",
                       "accessList": [],
                       "v": "0x00",
                       "r": "0x0e6c8f4d73b175887e1f21cc00bf0f8243af18aed208ec0a4562ee60e7f85736",
                       "s": "0x3f8e8f1b01fcd6d3a988877e80dc17fad16274447f4211ed74b41e8789ae70cd",
                       "sender": "0x8a0a19589531694250d570040a0c4b74576919b8"
                   }
               ],

Fixed in these commits:
https://github.com/ethereum/execution-spec-tests/pull/621/commits/4ff3adda68eef2ff223863f04c576312a4aea92d
https://github.com/ethereum/execution-spec-tests/pull/621/commits/382586a0527f43882a4de6618f395369f0743f8d


A proper way of using sync.Cond

Hello, there! I'd like to say this package shows great work!
According to the doc comments in go pkg, I doubt whether this is a proper way of using conditional variable, since I see no p.cond.L.Lock() before calling p.cond.Wait(). I haven't make any test, but won't be a problem there?
https://github.com/panjf2000/ants/blob/dbcb6a104f23b1a6a7521796b30515230353283e/pool.go#L244

https://github.com/golang/go/blob/go1.16.2/src/sync/cond.go#L52-L58

Ah, I missed the p.lock part. Excuse me... :(


feat(ssr): implement ssr for webpack esnext skeleton

webpack esnext skeleton is a major boilerplate for aurelia applications built using es6 and higher versions of javascript and it was missing server side rendering support

@EisenbergEffect Please have a look at this.
Thanks

We've got a specific skeleton for SSR support. You need to use that one. In the future, we're adding SSR to the CLI and then will use the CLI to generate a set of skeletons on GitHub so that we'll have a single source of truth.


Don't try to produce regex objects under Rhino to avoid uncatchable exceptions.

Merged with 649bf8f2daf89ac8d38fbbf243e2cd49a8bcd3e8.

I'm not really convinced. Shouldn't the problem (regexp syntax errors apparently crashing the interpreter) be reported and fixed on the Rhino side? What if someone happens to have a global called Packages? Is it okay for our AST to suddenly be missing the regexp objects in that case?

What if someone happens to have a global called Packages?

Valid point; this particular check is from r.js, but feel free to suggest a more robust one.

I don't have a more robust one -- I've never used Rhino.
I feel this should be reverted and solved in Rhino. @RReverser Do you have a strong opinion on the issue?

Not really a strong opinion (personally fine with any resolution), but I think that if someone uses Rhino and we can make Acorn work there, we should probably do it. Workarounds for specific issues in specific engines is usually a pretty common thing in web development, so users might expect lib to "just work".

I've installed Rhino and refined the check to reduce the chance of false positives to an acceptable level.

Please note that String(Packages) will throw if Packages is prototype-less object hash (Object.create(null)). This might be rare, but worth considering.

Also: if object has own toString, it will be called instead.

Sure, see attached patch.


TaskIt: Introduce BlUseAsyncFeatures to dynamically convert async actions into sync actions

At this moment, we have several places in the GT where UI is computed in a background. While this is an important feature, it is also required being able to execute async actions synchronously. One example is when we want to generate a UI picture.
For this reason we introduce a BlUseAsyncFeatures dynamic variable to control the async actions per Process.

This is a cool direction!

It is introduced for BlAsyncElement, Inspector extensions, Text Editor, and Spotter. If we find other places, we open new issue.


Apply for open source status on Zulip

We should add an 'acknowledgement' to zulip before applying for sponsorship (see: https://zulip.com/help/linking-to-zulip-website).

I have applied for the Zulip sponsorship for Open source projects, and it has been approved - thank you Zulip!


Improve Powerline Folder Display

Not sure if this is a Vaffle issue or a Powerline issue, however the reported folder has //0// before it, it would be nicer if this could be cleaner:

That prefix is required to use Vaffle with multi-window. According to the Vim specification, buffers with the same name cannot exists at the same time.


Cl minor model change

Made sure are many-to-many fields are plural and foreignkey fields are singular

Verified branch works on my local. Merging. Team will need to migrate after.


Faraday::ConnectionFailed: connection refused: localhost:9200

View details in Rollbar: https://rollbar.com/trystant/BOW/items/279/

Errno::ECONNREFUSED: Connection refused - connect(2) for "localhost" port 9200
  File "/Users/msnyon/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb", line 879, in initialize
  File "/Users/msnyon/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb", line 879, in open
  File "/Users/msnyon/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb", line 879, in block in connect
  File "/Users/msnyon/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/timeout.rb", line 89, in block in timeout
  File "/Users/msnyon/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/timeout.rb", line 99, in call
  File "/Users/msnyon/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/timeout.rb", line 99, in timeout
  File "/Users/msnyon/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb", line 878, in connect
  File "/Users/msnyon/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb", line 863, in do_start
  File "/Users/msnyon/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb", line 858, in start
  File<EMAIL_ADDRESS>line 700, in start
  File<EMAIL_ADDRESS>line 631, in connection_for
  File<EMAIL_ADDRESS>line 994, in request
  File<EMAIL_ADDRESS>line 26, in perform_request
  File<EMAIL_ADDRESS>line 40, in block in call
  File<EMAIL_ADDRESS>line 22, in with_net_http_connection
  File<EMAIL_ADDRESS>line 32, in call
  File<EMAIL_ADDRESS>line 139, in build_response
  File<EMAIL_ADDRESS>line 377, in run_request
  File<EMAIL_ADDRESS>line 21, in block in perform_request
  File<EMAIL_ADDRESS>line 187, in call
  File<EMAIL_ADDRESS>line 187, in perform_request
  File<EMAIL_ADDRESS>line 20, in perform_request
  File<EMAIL_ADDRESS>line 115, in perform_request
  File<EMAIL_ADDRESS>line 99, in index
  File<EMAIL_ADDRESS>line 44, in store
  File<EMAIL_ADDRESS>line 24, in block in store_with_instrumentation
  File<EMAIL_ADDRESS>line 164, in block in instrument
  File<EMAIL_ADDRESS>line 20, in instrument
  File<EMAIL_ADDRESS>line 164, in instrument
  File<EMAIL_ADDRESS>line 23, in store_with_instrumentation
  File<EMAIL_ADDRESS>line 86, in reindex_record
  File<EMAIL_ADDRESS>line 79, in reindex
  File<EMAIL_ADDRESS>line 432, in block in make_lambda
  File<EMAIL_ADDRESS>line 253, in call
  File<EMAIL_ADDRESS>line 253, in block in conditional
  File<EMAIL_ADDRESS>line 506, in call
  File<EMAIL_ADDRESS>line 506, in block in call
  File<EMAIL_ADDRESS>line 506, in each
  File<EMAIL_ADDRESS>line 506, in call
  File<EMAIL_ADDRESS>line 92, in __run_callbacks__
  File<EMAIL_ADDRESS>line 778, in _run_commit_callbacks
  File<EMAIL_ADDRESS>line 314, in committed!
  File<EMAIL_ADDRESS>line 89, in commit_records
  File<EMAIL_ADDRESS>line 153, in commit
  File<EMAIL_ADDRESS>line 175, in commit_transaction
  File<EMAIL_ADDRESS>line 194, in within_new_transaction
  File<EMAIL_ADDRESS>line 213, in transaction
  File<EMAIL_ADDRESS>line 220, in transaction
  File<EMAIL_ADDRESS>line 348, in with_transaction_returning_status
  File<EMAIL_ADDRESS>line 286, in block in save
  File<EMAIL_ADDRESS>

This was caused by temporary Elasticsearch connectivity problems. Elasticsearch has been configured on Travis, both Heroku instances and our local boxes, so we can close this.