.Net: Using the VectorStoreGenericDataModel when the Key data type is unknown at compile time

Assume a scenario where the vector store record definitions are loaded from a a configuration file. For example:
{
    "collections": [
        "articles":  {
            "Key": "string",
            "Name": "string",
            "Title": "string",
            "Body": "string",
            "BodyEmbedding": "float[384]"
        },
        "glossary":
        {
            "Key": "int",
            "Term": "string",
            "Definition": "string",
            "DefinitionEmbedding": "float[1536]"
        }
   ]
}

This file is read at runtime to create a VectorStoreRecordDefinition for a given collection. Notice that the Key property has different data types for each collection, string and int respectively.
string collectionName = "articles";

// Load the definitions from configuration and define a schema for the specified collection
VectorStoreRecordDefinition vectorStoreRecordDefinition = LoadVectorDefinitionForCollection(collectionName);

Once a record definition has been created, it's time to operate on the corresponding collection. The generic data model is meant to be used in scenarios where the database schema is unknown at compile time. However, it's key data type needs to be known at compile time.
// get a reference to the collection
var collection = vectorStore.GetCollection<string, VectorStoreGenericDataModel<??????>>(collectionName, vectorStoreRecordDefinition);

How do you use it when the key data type needs to be specified at runtime. Is there a pattern that you recommend in such a scenario?

Thanks for the scenario @f2bo, we haven't really considered it before.
A possible solution would be to support object as a key type with the VectorStoreGenericDataModel and casting back and forth to the key type defined in the VectorStoreRecordDefinition. E.g.
var collection = vectorStore.GetCollection<object, VectorStoreGenericDataModel<object>>(collectionName, vectorStoreRecordDefinition);

Note that if the VectorStoreRecordDefinition says that the key type is int, an int would have to be supplied as the key for methods such as GetAsync even though the signature would accept an object. E.g.
object key = 5;
await collection.GetAsync(key);

We would need to do some prototyping on this, and add support in each vector store implementation, but let us know if this would work for your use case.

let us know if this would work for your use case.

I hadn't used the generic data model before and only just started experimenting with an idea when I noticed this problem, so it's too early to tell. It does feel less robust but I imagine that it would work.
I'll report back if I find that using object is impractical.
Thank you!

It does feel less robust

@f2bo, did you also have another solution in mind or do you just mean object is less robust than using the strongly typed key types?

Sorry. Don't attach too much weight to my comment. I did mean it felt less robust than using a strongly typed key type but I suppose that given that the data type is determined at runtime, you probably can't do better than this. As I said, I don't yet have a complete picture of where I'm going with this.


⚠ ClamAV has degraded performance

In b3ddce1, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 54 ms

Resolved: ClamAV performance has improved in d833ff6.


Trying to disable Klipper LB but k3s server crash with message "flag provided but not defined: -disable servicelb"

Version (k3OS / kernel)
k3os version v0.21.1-k3s1r0
5.4.0-73-generic #82 SMP Thu Jun 3 02:29:43 UTC 2021
Architecture
x86_64
Describe the bug
I'm trying to disable Klipper LB passing this argunment to config.yaml   "--disable servicelb"
To Reproduce
This is my config.yaml
#Master
hostname: k3os-master
k3os:
k3s_args:
- server
- "--disable servicelb"
Expected behavior
Klipper LB should be disable
Actual behavior
k3s server crashing with this error in k3s-service.log
time="2021-06-23T20:03:12Z" level=fatal msg="flag provided but not defined: -disable servicelb"

@ogandoe from the README at https://github.com/rancher/k3os#k3osk3s_args:

My config.yaml was wrong.
to disable this service the correct configuration should be set in this way
#Master
hostname: k3os-master
k3os:
k3s_args:

server
"--disable"
"servicelb"

@ogandoe from the README at https://github.com/rancher/k3os#k3osk3s_args
k3os.k3s_args
Arguments to be passed to the k3s process. The arguments should start with server or agent to be valid.
k3s_args is an exec-style (aka uninterpreted) argument array which means that when specifying a flag with a value one
must either join the flag to the value with an = in the same array entry or specify the flag in an entry by itself
immediately followed the value in another entry, e.g.:
# K3s flags with values joined with `=` in single entry
k3os:
  k3s_args:
  - server
  - "--cluster-cidr=<IP_ADDRESS>/23"
  - "--service-cidr=<IP_ADDRESS>/23"

# Effectively invokes k3s as:
# exec "k3s" "server" "--cluster-cidr=<IP_ADDRESS>/23" "--service-cidr=<IP_ADDRESS>/23"

# K3s flags with values in following entry
k3os:
  k3s_args:
  - server
  - "--cluster-cidr"
  - "<IP_ADDRESS>/23"
  - "--service-cidr"
  - "<IP_ADDRESS>/23"

# Effectively invokes k3s as:
# exec "k3s" "server" "--cluster-cidr" "<IP_ADDRESS>/23" "--service-cidr" "<IP_ADDRESS>/23"

Thanks @dweomer  my mistake!!
Regards
Emiliano


implement Debug for regex_syntax::Error

It's a minor papercut that I can't call unwrap on a Result<foo, regex_syntax::Error> -- times I have I wanted to do this include tests, or with hard-coded regexs, or when converting literals into a regex.

...and, I am just confused. The problem was on my end. Sorry about that. :)


Metadata schema update - Add ontology to file_content_ontology.json

We need an update on the metadata schema for the content_description field of files, so we can use the newly incorporated branch "information entity".
File to update:
file_content_ontology.json
Update to perform
Add Information Entity,  IAO:0000030 (EFO HCA subset)

"ontology": {
"description": "An ontology term identifier in the form prefix:accession.",
"type": "string",
"graph_restriction":  {
"ontologies" : ["obo:edam", "obo:efo"],
"classes": ["data:0006", "IAO:0000030"],
"relations": ["rdfs:subClassOf"],
"direct": false,
"include_self": false
},
"example": "data:3497; data:0863",
"user_friendly": "Content description ontology ID"
},

The relevant ticket in the metadata-schema repo is here: https://github.com/HumanCellAtlas/metadata-schema/issues/1450

This ticket is not needed anymore

[x] The term and its child terms have been added to the next HCAO release
[x] The metadata schema update is in progress https://app.zenhub.com/workspaces/operations-5fa2d8f2df78bb000f7fb2b5/issues/ebi-ait/hca-ebi-wrangler-central/695

Moving it to done :)


<EMAIL_ADDRESS>https://etherscan.io/address/0x3cd751e6b0078be393132286c442345e5dc49699

https://github.com/Chia-Network/chia-blockchain/issues/11374#issue-1221806013

add too account
<EMAIL_ADDRESS>

If it does not start with 0x0 it’s not legit.
On Sat, Apr 30, 4 Reiwa at 1:16 AM arty000 @.***> wrote:

Chia-Network/chia-blockchain#11374 (comment)
https://github.com/Chia-Network/chia-blockchain/issues/11374#issue-1221806013
—
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/24950, or unsubscribe
https://github.com/notifications/unsubscribe-auth/APXLM3KNXNBWVUQH2RGO3I3VHUI7PANCNFSM5UYG4LAA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
ios 2011 m1

Why?

why

Why not


Github actions pipeline to cut a release in Wave

Closes https://github.com/h2oai/wave/issues/399

Publish to Pypi was tested with Test Pypi: https://test.pypi.org/manage/project/h2o-wave/releases/

Publish to Pypi was tested with Test Pypi: https://test.pypi.org/manage/project/h2o-wave/releases/

0.10.0 release was created using this pipeline here - https://github.com/h2oai/wave-ci-dummy/releases
Publish to Pypi was tested with Test Pypi

0.10.0 release was created using this pipeline here - https://github.com/h2oai/wave-ci-dummy/releases
Publish to Pypi was tested with Test Pypi


Embedded resources

Hi,
is there a way to specify embedded resources for vNext Class Library?
Thanks,
Dusan

yes and this has changed a bunch depending on what version of the dnx you are using.

Well, I am using the version that is bundled with VS CTP 6.


drop ahead-of-time gzip/Brotli compression, add async compression

[x] drop opt.gzippedBuffer/opt.gzippedEtag & opt.brotliCompressedBuffer/opt.brotliCompressedEtag
[x] refactor _serveBuffer code to support async intermediate steps
[x] add opt.gzip: async buf => ({compressedBuffer, etag}) with default implementation
[x] add opt.brotliCompress: async buf => ({compressedBuffer, etag}) with default implementation
[x] support disabling compression by passing opt.gzip: false/opt.brotliCompress: false
[x] add optional caching using WeakMap? https://github.com/derhuerst/facilities-gtfs-rt-feed/blob/6b908ab37a6fa026e0a0e57f570bc4a1474efefd/lib/serve-buffer-compressed.js#L20-L33

Published as<EMAIL_ADDRESS>🎉


uninstall report

How to uninstall vs code its extensions and erase all data and reinstall it again

Which OS are you on? I see some results when searching the web that might help: https://www.bing.com/search?q=uninstall+vscode
@joaomoreno Would it be worthwhile documenting this? (Can't find it right now.)

https://code.visualstudio.com/docs/setup/setup-overview#_how-can-i-do-a-clean-uninstall-of-vs-code


update index.md

added basic info about PHP Expressions.

[x] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

LGTM
We would welcome future pull requests from you.
Thank you and happy coding.


Fix clipping from flooring scrollcontainer position

Regression from #46409
Fixes? https://github.com/godotengine/godot/issues/46850

The code for updating the scroll container dimensions got shuffled around in https://github.com/godotengine/godot/commit/b8610dbd3159985f007deb0424a64df386832d07 but stayed the same otherwise. This code in master does call update_dimensions on ready, so I backported this to 3.2 and tested with the supplied project but the issue persists.
So the crucial change must be elsewhere.

So the crucial change must be elsewhere. The project looks fine on master.
I suspect this commit 1adea98 might be it.

I agree that the change must be elsewhere, but I don't think 1adea98 is related since it was not backported to 3.2 (although get_content_height() does look suspicious).
I also checked bruvzg's other recent PRs for 3.2 and none of them seem related. https://github.com/godotengine/godot/pulls?q=is%3Apr+is%3Aclosed+author%3Abruvzg+milestone%3A3.2


[2.x] Cleanup phpunit.xml

The develop branch requires PHP 8.1, therefor the phpunit.xml can be simplified.

I reserving this changes as we might need to introduce tests specifically for 8.4, will revisit this once  we finalise PHP 8.4 supports

@crynobone I will also open up this for review, because there were no PHP 8.4 specific tests added.


Execution on local device with npm run test:e2e

Hi team,
I wanted to check the driver.
I followed following steps to test the library

clone the repo
set the env files
change npm run test:e2e -> point to functional tests

Started getting the following error.
Can any one help
Thanks
> mocha --timeout 40s --slow 10s "./test/functional/**/*.spec.js"

  RokuDriver
WARN Appium Appium encountered 1 warning while validating drivers found in manifest /Users/pmadival/Automation/appium-roku-driver/node_modules/.cache/appium/extensions.yaml
WARN Appium Driver "roku" has 1 potential problem:
WARN Appium   - Driver "roku" (package `@headspinio/appium-roku-driver`) has 1 invalid or missing field ("installType") in `extensions.yaml`; this may cause upgrades done via the `appium` CLI tool to fail. Please reinstall with `appium driver uninstall roku` and `appium driver install roku` to attempt a fix.
[Appium] Welcome to Appium v2.0.0-beta.46 (REV d73b7a304bde841918d0d74999c061841cbddc46)
[Appium] Non-default server args:
[Appium] {
[Appium]   address: '<IP_ADDRESS>',
[Appium]   port: 8765
[Appium] }
[Appium] Attempting to load driver roku...
[Appium] Could not load driver 'roku', so it will not be available. Error in loading the driver was: Could not find a driver installed at /Users/pmadival/Automation/appium-roku-driver/node_modules/@headspinio/appium-roku-driver
[debug] [Appium] ReferenceError: Could not find a driver installed at /Users/pmadival/Automation/appium-roku-driver/node_modules/@headspinio/appium-roku-driver
[debug] [Appium]     at DriverConfig.require (/Users/pmadival/Automation/appium-roku-driver/node_modules/appium/lib/extension/extension-config.js:527:13)
[debug] [Appium]     at map (/Users/pmadival/Automation/appium-roku-driver/node_modules/appium/lib/extension/index.js:83:46)
[debug] [Appium]     at Array.map (<anonymous>)
[debug] [Appium]     at getActiveDrivers (/Users/pmadival/Automation/appium-roku-driver/node_modules/appium/lib/extension/index.js:80:10)
[debug] [Appium]     at main (/Users/pmadival/Automation/appium-roku-driver/node_modules/appium/lib/main.js:305:25)
[debug] [Appium]     at Context.<anonymous> (/Users/pmadival/Automation/appium-roku-driver/test/functional/driver.e2e.spec.js:34:14)
[Appium] Appium REST http interface listener started on <IP_ADDRESS>:8765
[Appium] Available drivers:
[Appium]   -<EMAIL_ADDRESS>(automationName 'Roku')
[Appium] No plugins have been installed. Use the "appium plugin" command to install the one(s) you want to use.
[HTTP] --> POST /session
[HTTP] {"capabilities":{"alwaysMatch":{"default":{"appium:rokuHost":"<IP_ADDRESS>","appium:rokuEcpPort":8060,"appium:rokuWebPort":80,"appium:rokuUser":"rokudev","appium:rokuPass":"1234","appium:rokuHeaderHost":"<IP_ADDRESS>","appium:keyCooldown":1250,"appium:automationName":"Roku","appium:platformName":"Roku"}},"firstMatch":[{}]},"desiredCapabilities":{"default":{"appium:rokuHost":"<IP_ADDRESS>","appium:rokuEcpPort":8060,"appium:rokuWebPort":80,"appium:rokuUser":"rokudev","appium:rokuPass":"1234","appium:rokuHeaderHost":"<IP_ADDRESS>","appium:keyCooldown":1250,"appium:automationName":"Roku","appium:platformName":"Roku"}}}
[debug] [AppiumDriver@d68a] Calling AppiumDriver.createSession() with args: [{"default":{"appium:rokuHost":"<IP_ADDRESS>","appium:rokuEcpPort":8060,"appium:rokuWebPort":80,"appium:rokuUser":"rokudev","appium:rokuPass":"1234","appium:rokuHeaderHost":"<IP_ADDRESS>","appium:keyCooldown":1250,"appium:automationName":"Roku","appium:platformName":"Roku"}},null,{"alwaysMatch":{"default":{"appium:rokuHost":"<IP_ADDRESS>","appium:rokuEcpPort":8060,"appium:rokuWebPort":80,"appium:rokuUser":"rokudev","appium:rokuPass":"1234","appium:rokuHeaderHost":"<IP_ADDRESS>","appium:keyCooldown":1250,"appium:automationName":"Roku","appium:platformName":"Roku"}},"firstMatch":[{}]}]
[debug] [AppiumDriver@d68a] Event 'newSessionRequested' logged at<PHONE_NUMBER>688 (22:43:14 GMT+0530 (India Standard Time))
[Appium] Could not parse W3C capabilities: All non-standard capabilities should have a vendor prefix. The following capabilities did not have one: default
[debug] [AppiumDriver@d68a] Event 'newSessionStarted' logged at<PHONE_NUMBER>691 (22:43:14 GMT+0530 (India Standard Time))
[debug] [AppiumDriver@d68a] Encountered internal error running command: InvalidArgumentError: All non-standard capabilities should have a vendor prefix. The following capabilities did not have one: default
[debug] [AppiumDriver@d68a]     at parseCaps (/Users/pmadival/Automation/appium-roku-driver/node_modules/@appium/base-driver/lib/basedriver/capabilities.js:238:11)
[debug] [AppiumDriver@d68a]     at processCapabilities (/Users/pmadival/Automation/appium-roku-driver/node_modules/@appium/base-driver/lib/basedriver/capabilities.js:317:43)
[debug] [AppiumDriver@d68a]     at parseCapsForInnerDriver (/Users/pmadival/Automation/appium-roku-driver/node_modules/appium/lib/utils.js:134:21)
[debug] [AppiumDriver@d68a]     at AppiumDriver.createSession (/Users/pmadival/Automation/appium-roku-driver/node_modules/appium/lib/appium.js:241:26)
[debug] [AppiumDriver@d68a]     at commandExecutor (/Users/pmadival/Automation/appium-roku-driver/node_modules/@appium/base-driver/lib/basedriver/driver.js:126:9)
[debug] [AppiumDriver@d68a]     at AppiumDriver.executeCommand (/Users/pmadival/Automation/appium-roku-driver/node_modules/@appium/base-driver/lib/basedriver/driver.js:143:15)
[debug] [AppiumDriver@d68a]     at processTicksAndRejections (node:internal/process/task_queues:95:5)
[debug] [AppiumDriver@d68a]     at defaultBehavior (/Users/pmadival/Automation/appium-roku-driver/node_modules/appium/lib/appium.js:668:16)
[debug] [AppiumDriver@d68a]     at AppiumDriver.executeWrappedCommand (/Users/pmadival/Automation/appium-roku-driver/node_modules/appium/lib/appium.js:762:16)
[debug] [AppiumDriver@d68a]     at AppiumDriver.executeCommand (/Users/pmadival/Automation/appium-roku-driver/node_modules/appium/lib/appium.js:684:17)
[debug] [AppiumDriver@d68a]     at asyncHandler (/Users/pmadival/Automation/appium-roku-driver/node_modules/@appium/base-driver/lib/protocol/protocol.js:346:19)
[HTTP] <-- POST /session 400 19 ms - 1703
[HTTP]
    1) "before all" hook in "RokuDriver"
[HTTP] Waiting until the server is closed
[HTTP] Received server close event

  0 passing (2s)
  1 failing

  1) RokuDriver
       "before all" hook in "RokuDriver":
     Error: Failed to create session.
All non-standard capabilities should have a vendor prefix. The following capabilities did not have one: default
      at startWebDriverSession (node_modules/webdriver/build/utils.js:73:15)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at Function.newSession (node_modules/webdriver/build/index.js:46:45)
      at remote (node_modules/webdriverio/build/index.js:77:22)
      at startSession (test/functional/driver.e2e.spec.js:21:10)
      at Context.<anonymous> (test/functional/driver.e2e.spec.js:35:14)

Resolved after changing caps = caps.default
Started facing this error


MM-23042: Fix select teams when there are no teams

Summary

When there are no teams, then handleScroll does not
get called which does not allow it to set isEndOfData = true.
So we also check if isFetching is set to true or not,
which won't show the loader screen until it first gets set
to true when handleScroll gets called.
We also remove the unncessary CSS settings which made the
component to be wider.
This regression was introduced in 07b847a4f3b3710b86842a3ae8c97d0ce658ffba.
Thanks to @jespino and @ethervoid for helping me work on this. :)
Ticket Link

https://mattermost.atlassian.net/browse/MM-23042
/cc @AGMETEOR

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-5041.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

@ogi-m - I think that's a bit outside the scope of the PR. The PR was just about fixing the infinite spinner. Granted I made 2 small css changes, but anything more needs a separate ticket.

Test server destroyed

@hmhealey - It would be good to get this in 5.22 if possible. Any chance you could take a look ? Thanks.

/update-branch


普通类型至struct类型转换不成功

1. What version of Go and system type/arch are you using?

go version go1.14.6 windows/amd64
2. What version of GoFrame are you using?

gf v1.15.3
3. Can this issue be reproduced with the latest release?
4. What did you do?

func main() {
    var v g.Var

    v.Set("123")

    fmt.Println(v.Val())

    // struct转换
    type Score struct {
        Value int
    }
    s := new(Score)
    v.Struct(s)
    fmt.Println(s)
}

5. What did you expect to see?
文档表示输出
123
&{123}

6. What did you see instead?
但实际输出为：
123
&{0}

@magicostly 你好，从某个版本开始，为保证转换的严谨性，这种不带属性名称的struct转换已经不支持了，示例代码没有来得及更新，感谢反馈。


feat: added 2.0.0beta.2 features

Fixes: #[Add issue number here]
Changes: features from 2.0.0beta.2

[x] added theme switch enabled code blocks

Screenshots of the change:
Earlier code block was only having dark theme

now it has both light and dark theme

cc @juzhiyuan @Yiyiyimu


treewide: remove licenses.gpl2

Description of changes
Removed licenses.gpl2 in favor of gpl2Only and gpl2Plus, also in some cases the license was incorrectly GPL2.
Method used
First, I dumped all attributes that had meta.license = gpl2;  like so:
nix-eval-jobs --meta --force-recurse pkgs/top-level/release.nix 2> /dev/null \
	| jq ' select(.meta.license.shortName=="gpl2") | .attrPath | del(.[-1]) | join(".")' \
    -r --unbuffered 2> /dev/null | tee gpl2attrs

I wrote a script to go through them afterwards:
while true; do
	attr=$(head -n 1 gpl2attrs)
	if [ -z $attr ]; then
		break
	fi

    echo "Checking sources for $attr"
    NIX_PATH=nixpkgs=. \
        nix-build  --keep-failed --expr "let pkgs = import ./. {}; in  pkgs.srcOnly pkgs.$attr" && rg "any later version" result
    checkPid=$!
    echo "nix-build for $attr done"

    attrFile=$(NIX_PATH=nixpkgs=. nix eval --impure --expr "with import <nixpkgs> {}; pkgs.$attr.meta.position" --raw \
        | sed 's/\:.*$//')

    # Check if file has only one match for 'gpl2'
    matchCount=$(rg -wc "gpl2" $attrFile)
    echo $attr is defined in $attrFile
    if [[ $matchCount == "1" ]]; then
        echo "Press 'o' for gpl2Only, 'p' for gpl2Plus; or just Enter to do nothing (edit manually):"
        read -r choice
        if [ $choice == "o" ]; then
            sed -i 's/gpl2/gpl2Only/g' $attrFile
        fi

        if [ $choice == "p" ]; then
            sed -i 's/gpl2/gpl2Plus/g' $attrFile
        fi
    else
        echo "Found $matchCount matches, edit manually, and Enter when done:"
        read -r vuota
    fi

    sed -i "/$attr/d" gpl2attrs
done

This got around 90% of the cases, afterwards I just grepped the repo for "gpl2" and went through them more manually.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I'm a big :-1: on removing licenses.gpl2'. It has distincly different SPDX id: GPL-2.0vsGPL-2.0-only. This field is useful to map data from external packaging tools like pyproject.toml` to Nix.

There is no GPL-2.0 anymore, it has been deprecated. https://spdx.org/licenses/

Would you please split the PR into several smaller ones, probably a dozen, and defer the changes to lib/licenses.nix? That way you can have multiple reviewers working in parallel, and changes can be checked and merged more quickly.

As already said, please split this into smaller PRs as this one is way to big to review and we also pinged already way to many people which is the reason I am going to close this one, not because the change is not wanted or desired.
Also it is probably a good idea to search if for this there is already a tracking issue and if not we can open one and discuss the process there.


Intellisense in JSX is not good as is in JS

To me it's looks like JSX is JS+ and Intellisense should work at least like what it does in JS but in practice it doesn't.

Duplicate of #140


[ArPow Stage 4] Remove any prebuilts and enable regression block for command-line-api

See ArPow stage descriptions for details.

This issue is superseded by https://github.com/dotnet/source-build/issues/3017.


[video_player] Add support GstEGLImage to improve playback performance

Hello.
I added GstEGLImage support to improve video_player playback performance.
If gst_is_dmabuf_memory() is TRUE, GstEGLImage can be used to improve performance without gst_buffer_extract().
Relevant issue: #64
This requires the following PR:
sony/flutter-embedded-linux#327
and the option -DUSE_EGL_IMAGE_DMABUF is required at build time.

I agree to delegate all rights related to this PR to Sony.

I fixed code.


[Snyk] Upgrade pnpm from 8.13.0 to 8.13.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade pnpm from 8.13.0 to 8.13.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2023-12-26.

Release notes

Package name: pnpm

8.13.1 - 2023-12-26Minor Changes

New commands added for inspecting the store:

pnpm cat-index: Prints the index file of a specific package in the store. The package is specified by its name and version:
pnpm cat-index <pkg name>@<pkg version>

pnpm cat-file: Prints the contents of a file based on the hash value stored in the index file. For example:
pnpm cat-file sha512-mvavhfVcEREI7d8dfvfvIkuBLnx7+rrkHHnPi8mpEDUlNpY4CUY+CvJ5mrrLl18iQYo1odFwBV7z/cOypG7xxQ==

(EXPERIMENTAL) pnpm find-hash: Lists the packages that include the file with the specified hash. For example:
pnpm find-hash sha512-mvavhfVcEREI7d8dfvfvIkuBLnx7+rrkHHnPi8mpEDUlNpY4CUY+CvJ5mrrLl18iQYo1odFwBV7z/cOypG7xxQ==

This command is experimental. We might change how it behaves.

Related issue: #7413.

A new setting added for symlinking injected dependencies from the workspace, if their dependencies use the same peer dependencies as the dependent package. The setting is called dedupe-injected-deps #7416.

Use --fail-if-no-match if you want the CLI fail if no packages were matched by the command #7403.

Patch Changes

pnpm list --parseable should not print the same dependency multiple times #7429.
Fix error message texts in the pnpm env commands #7456.
Better support for light themed terminals by the pnpm update --interactive command #7439.
Fix EPERM error that occasionally happened on Windows during renames in the store #7213.
Fix error as in update -i -r with Git specifiers #7415.
Added support for boolean values in 'bundleDependencies' package.json fields when installing a dependency. Fix to properly handle 'bundledDependencies' alias #7411.

Our Gold Sponsors

Our Silver Sponsors

8.13.0 - 2023-12-14

    from pnpm GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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

Comparison is base (11c0a15) 77.83% compared to head (a3bbe0a) 77.84%.
 Consider uploading reports for the commit 290e842 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2041   +/-   ##
=======================================
  Coverage   77.83%   77.84%
=======================================
  Files          40       40
  Lines        3086     3087    +1
  Branches      625      626    +1
=======================================
+ Hits         2402     2403    +1
  Misses        479      479
  Partials      205      205

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


feat: ripple effect with color props

Feature Request
Ionic version:

[x] 5.x
Describe the Feature Request

Right now you will get same ripple color as your text content color. Can we add color props to have different ripple color than text color.
Describe Preferred Solution

Do not inherit color from parent div text color.
So new syntax can be
      <ion-ripple-effect type="unbounded" color="yellow"></ion-ripple-effect>

Describe Alternatives

Related Code

Additional Context

Thanks for the feature request. I am going to close this as customizing the ripple effect is already possible via CSS.
CodePen example: https://codepen.io/liamdebeasi/pen/yLYNGMB
To use the Ionic theme colors, you can use the CSS variables provided in the documentation.
Themes: https://ionicframework.com/docs/theming/themes
Color Generator: https://ionicframework.com/docs/theming/color-generator


Question: Problem with StackNavigator

Question:
Hello Community!
I hope my question isn't missplaced here!
I am new to RN and I am trying to implement react-navigation StackNavigator
I encountered this error:

Maybe someone have a hint what I am doing wrong?
This is the code:
import React, { Component } from 'react';
import {
  AppRegistry,
  Text,
  View
} from 'react-native';
import StackNavigator from 'react-navigation';
import { Button } from 'react-native-elements'
import Drawer from 'react-native-drawer'
import Startpage from './src/container/startpage'
import Home from './src/container/home'

const Test = StackNavigator({
  Home: {screen: Home},
  Start: {screen: Startpage},
},{
  initialRouteName: 'Start',
  headerMode: 'none',
});

AppRegistry.registerComponent('Test', () => Test);

If you need more code, I can provide you the container Startpage & Home.

import { StackNavigator } from 'react-navigation';


Fix references to docker container

Closes #1796
Remove outdated references to dockerhub and instead point all docker
references to the ghcr location.

Codecov Report

Merging #1797 (186ee87) into unstable (8c15134) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           unstable    #1797      +/-   ##
============================================
- Coverage     76.86%   76.84%   -0.03%
============================================
  Files           383      383
  Lines         11831    11831
  Branches        571      571
============================================
- Hits           9094     9091       -3
- Misses         2737     2740       +3

Impacted Files
Coverage Δ

...a/at/forsyte/apalache/tla/lir/TlaLevelFinder.scala
97.36% <0.00%> (-2.64%)
:arrow_down:

...he/io/annotations/parser/CommentPreprocessor.scala
94.50% <0.00%> (-2.20%)
:arrow_down:

Continue to review full report at Codecov.

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


Modify: Betterbird.Betterbird version 115.15.0

Created by 🥟 Dumplings.
Microsoft Reviewers: Open in CodeFlow

URL:
Invalid URI: The hostname could not be parsed.
(Automated message - build 896)


Tag management

As a moderator, it would be nice to have the ability to curate tags. If users are making a lot of similar tags (like 'plugin' and 'plugins'), moderators ought to be able to delete or rename tags to make it easier to organize questions.

I am out of the office until 05.02.2015.
In dringenden F�llen, kontaktieren Sie bitte
ErwinTratargebitde oder
TomKraussgebitde.
Note: This is an automated response to your message  "[mamute] Tag
management (#141)" sent on 04.02.2015 16:19:49.
This is the only notification you will receive while this person is away.

Just checking for interest, is this something the Mamute team would want in the application? We want it and we're likely going to be adding it to our fork's codebase, but we'd be happy to share :)

Its a useful feature! Just make sure to add it the the existing admind
interface and we will probably accept your PR
Em 17:01 qui, 12/02/2015, monitorjbl<EMAIL_ADDRESS>escreveu:

Just checking for interest, is this something the Mamute team would want
in the application? We want it and we're likely going to be adding it to
our fork's codebase, but we'd be happy to share :)
—
Reply to this email directly or view it on GitHub
https://github.com/caelum/mamute/issues/141#issuecomment-74130332.

@monitorjbl any news here?

We had to reprioritize some work on our end, so this hasn't been worked on yet. We're still interested in this feature though.

Ok, I'll leave the issue open


Signal differences in program return code like regular diff

It would be useful to leverage the program return code to determine whether or not inputs have differences.

Changed my mind. Removed this. You can always fail your script if there's no output.


Add Hackage and GHC ecosystems.

Part of #1418.

LGTM, but should we also be adding hackage to our purl helpers in this PR?

Great catch, added!


SAM-3205 Add average score to Samigo pub Noti

Add average score to Samigo's publication notification which goes
out to students.

The publishAssessment.jsp changes need to be reviewed as they are new.


Total downloads bug

Total downloads still view incorrect value in next page https://www.nuget.org/packages?q=ukrguru
and Ctrl+F5 not helped. see more  in screenshots. thanks,

Seems like a product issue than a docs one.

If you continue to face an issue, please feel free to open a new issue. Thanks!


[zh] Sync scheduling-eviction/*.md

Update 3 files:
content/zh-cn/docs/concepts/scheduling-eviction/_index.md
content/zh-cn/docs/concepts/scheduling-eviction/api-eviction.md
content/zh-cn/docs/concepts/scheduling-eviction/topology-spread-constraints.md

/lgtm

There are still conflicts.

There are still conflicts.

Fixed, thanks.


Jupyter extension activation fails

OS: Mac OS Catalina (10.15.7)
Version: 1.75.1
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
Date: 2023-02-08T21:34:59.000Z (5 days ago)
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.6.0
Sandboxed: No
When opening a Python file or setting the language of a new file to Python, an attempt to load the Jupyter extension is triggered and fails (Running manual Jupyter notebooks from a system terminal works without problems) with the following error message being displayed at the bottom right corner:

Extension activation failed run the 'Developer: Toggle Developer Tools' command for more information
Source: Jupyter (Extension)

The associated console dump can be found here
log.ts:398  WARN Via 'product.json#extensionEnabledApiProposals' extension 'github.vscode-pull-request-github' wants API proposal 'commentsResolvedState' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
notificationsAlerts.ts:42 Extension activation failed, run the 'Developer: Toggle Developer Tools' command for more information.
c @ notificationsAlerts.ts:42
(anonymous) @ notificationsAlerts.ts:28
invoke @ event.ts:701
deliver @ event.ts:908
fire @ event.ts:869
addNotification @ notifications.ts:204
notify @ notificationService.ts:175
(anonymous) @ mainThreadMessageService.ts:77
d @ mainThreadMessageService.ts:42
$showMessage @ mainThreadMessageService.ts:36
N @ rpcProtocol.ts:455
M @ rpcProtocol.ts:440
H @ rpcProtocol.ts:370
G @ rpcProtocol.ts:296
(anonymous) @ rpcProtocol.ts:161
invoke @ event.ts:701
deliver @ event.ts:908
fire @ event.ts:869
fire @ ipc.net.ts:671
Z.onmessage @ localProcessExtensionHost.ts:615
log.ts:404   ERR [Extension Host] extension activation failed TypeError: e.endsWith is not a function
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:1785581
  at Array.filter (<anonymous>)
  at new ra (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:1785567)
  at t.resolveInstance (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:518676)
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:520614
  at t.resolve (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:520877)
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:506724
  at e._get (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:506490)
  at e.get (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:505133)
  at Hg.get (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:378419)
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:876375
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:876752
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:876760
  at DE (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:878320)
  at Ui.db (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:14818)
  at Ui.cb (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:14519)
  at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:12519
  at async f.n (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:6818)
  at async f.m (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:6781)
  at async f.l (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:6238)
console.ts:137 [Extension Host] extension activation failed TypeError: e.endsWith is not a function
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:1785581
  at Array.filter (<anonymous>)
  at new ra (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:1785567)
  at t.resolveInstance (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:518676)
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:520614
  at t.resolve (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:520877)
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:506724
  at e._get (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:506490)
  at e.get (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:505133)
  at Hg.get (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:378419)
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:876375
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:876752
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:876760
  at DE (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:878320)
  at Ui.db (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:14818)
  at Ui.cb (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:14519)
  at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:12519
  at async f.n (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:6818)
  at async f.m (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:6781)
  at async f.l (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:6238)
I @ console.ts:137
$logExtensionHostMessage @ mainThreadConsole.ts:39
N @ rpcProtocol.ts:455
M @ rpcProtocol.ts:440
H @ rpcProtocol.ts:370
G @ rpcProtocol.ts:296
(anonymous) @ rpcProtocol.ts:161
invoke @ event.ts:701
deliver @ event.ts:908
fire @ event.ts:869
fire @ ipc.net.ts:671
Z.onmessage @ localProcessExtensionHost.ts:615
console.ts:137 [Extension Host] rejected promise not handled within 1 second: TypeError: e.endsWith is not a function
I @ console.ts:137
$logExtensionHostMessage @ mainThreadConsole.ts:39
N @ rpcProtocol.ts:455
M @ rpcProtocol.ts:440
H @ rpcProtocol.ts:370
G @ rpcProtocol.ts:296
(anonymous) @ rpcProtocol.ts:161
invoke @ event.ts:701
deliver @ event.ts:908
fire @ event.ts:869
fire @ ipc.net.ts:671
Z.onmessage @ localProcessExtensionHost.ts:615
console.ts:137 [Extension Host] stack trace: TypeError: e.endsWith is not a function
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:1785581
  at Array.filter (<anonymous>)
  at new ra (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:1785567)
  at t.resolveInstance (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:518676)
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:520614
  at t.resolve (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:520877)
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:506724
  at e._get (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:506490)
  at e.get (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:505133)
  at Hg.get (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:378419)
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:876375
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:876752
  at /Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:876760
  at DE (/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:878320)
  at Ui.db (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:14818)
  at Ui.cb (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:14519)
  at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:12519
  at async f.n (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:6818)
  at async f.m (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:6781)
  at async f.l (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:6238)
I @ console.ts:137
$logExtensionHostMessage @ mainThreadConsole.ts:39
N @ rpcProtocol.ts:455
M @ rpcProtocol.ts:440
H @ rpcProtocol.ts:370
G @ rpcProtocol.ts:296
(anonymous) @ rpcProtocol.ts:161
invoke @ event.ts:701
deliver @ event.ts:908
fire @ event.ts:869
fire @ ipc.net.ts:671
Z.onmessage @ localProcessExtensionHost.ts:615
mainThreadExtensionService.ts:79 [[object Object]]e.endsWith is not a function
$onExtensionRuntimeError @ mainThreadExtensionService.ts:79
N @ rpcProtocol.ts:455
M @ rpcProtocol.ts:440
H @ rpcProtocol.ts:370
G @ rpcProtocol.ts:296
(anonymous) @ rpcProtocol.ts:161
invoke @ event.ts:701
deliver @ event.ts:908
fire @ event.ts:869
fire @ ipc.net.ts:671
Z.onmessage @ localProcessExtensionHost.ts:615
mainThreadExtensionService.ts:80 TypeError: e.endsWith is not a function
  at vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:1785581
  at Array.filter (<anonymous>)
  at new ra (vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:1785567)
  at t.resolveInstance (vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:518676)
  at vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:520614
  at t.resolve (vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:520877)
  at vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:506724
  at e._get (vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:506490)
  at e.get (vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:2:505133)
  at Hg.get (vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:378419)
  at vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:876375
  at vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:876752
  at vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:876760
  at DE (vscode-file://vscode-app/Users/marcolangiu/.vscode/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:878320)
  at Ui.db (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:14818)
  at Ui.cb (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:14519)
  at vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:12519
  at async f.n (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:6818)
  at async f.m (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:6781)
  at async f.l (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:6238)
$onExtensionRuntimeError @ mainThreadExtensionService.ts:80
N @ rpcProtocol.ts:455
M @ rpcProtocol.ts:440
H @ rpcProtocol.ts:370
G @ rpcProtocol.ts:296
(anonymous) @ rpcProtocol.ts:161
invoke @ event.ts:701
deliver @ event.ts:908
fire @ event.ts:869
fire @ ipc.net.ts:671
Z.onmessage @ localProcessExtensionHost.ts:615
log.ts:392  INFO [perf] Render performance baseline is 35ms

Additionally, when running any Jupyter-related commands such as Jupyter: Create Interactive Window I get error messages of the following type:

Command 'Jupyter: Create Interactive Window' resulted in an error (command 'jupyter.createnewinteractive' not found)

I already tried deleting the ~/.vscode folder, and only installing the Python and Jupyter extensions, both in the current release as well as the pre-release and older versions (latest from 2022), none of wich resolved the issue.

Same for me on Windows, I also cannot open Developer Tools any more... same version of VS code, using Python 3.8.  Jupyter notebook succeeds in finding my python environment (using conda) but I get an infinite progress bar at the top of the window and my Jupyter Output window contains:
Visual Studio Code (1.75.1, undefined, desktop)
Jupyter Extension Version: 2023.1.2010391206.
Python Extension Version: 2023.2.0.
Workspace folder d:\temp\face_segmentation
User belongs to experiment group 'jupyterTestcf'
User belongs to experiment group 'jupyterEnhancedDataViewer'
info 13:28:14.205: LSP Notebooks experiment is enabled
info 13:28:14.531: Find preferred kernel for d:\temp\face_segmentation\test.ipynb with metadata {"orig_nbformat":4,"language_info":{"name":"python"}} & preferred interpreter c:\Users\clovett.REDMOND\Anaconda3\envs\archai\python.exe
info 13:28:14.531: Find preferred kernel for d:\temp\face_segmentation\test.ipynb with metadata {"orig_nbformat":4,"language_info":{"name":"python"}} & preferred interpreter c:\Users\clovett.REDMOND\Anaconda3\envs\archai\python.exe
info 13:28:14.545: Find preferred kernel for d:\temp\face_segmentation\test.ipynb with metadata {"orig_nbformat":4,"language_info":{"name":"python"}} & preferred interpreter c:\Users\clovett.REDMOND\Anaconda3\envs\archai\python.exe
info 13:28:14.556: Find preferred kernel for d:\temp\face_segmentation\test.ipynb with metadata {"orig_nbformat":4,"language_info":{"name":"python"}} & preferred interpreter c:\Users\clovett.REDMOND\Anaconda3\envs\archai\python.exe
info 13:28:16.451: Preferred kernel .jvsc74a57bd0799abcba35f70097d02fca042963180a03ec3451fe1b7671ac5d22383cd0232c.c:\Users\clovett.REDMOND\Anaconda3\envs\archai\python.exe.c:\Users\clovett.REDMOND\Anaconda3\envs\archai\python.exe.-m#ipykernel_launcher is exact match or top match for non python kernels, (false, [object Object], false, false)
info 13:28:16.452: PreferredConnection: .jvsc74a57bd0799abcba35f70097d02fca042963180a03ec3451fe1b7671ac5d22383cd0232c.c:\Users\clovett.REDMOND\Anaconda3\envs\archai\python.exe.c:\Users\clovett.REDMOND\Anaconda3\envs\archai\python.exe.-m#ipykernel_launcher found for NotebookDocument: d:\temp\face_segmentation\test.ipynb
info 13:28:16.673: Process Execution: > ~\Anaconda3\envs\archai\python.exe -m pip list
> ~\Anaconda3\envs\archai\python.exe -m pip list

So maybe it is stuck on the pip list, when I run this myself in my own terminal it responds just fine.  Probably because of this infinite progress lock, I cannot bring up Developer Tools.  I'm using these versions of jupyter things:
jupyter                  1.0.0
jupyter_client           8.0.2
jupyter-console          6.5.1
jupyter_core             5.2.0
jupyter-events           0.6.3
jupyter_server           2.2.1
jupyter_server_terminals 0.4.4
jupyterlab-pygments      0.2.2
jupyterlab-widgets       3.0.5
ipykernel                6.21.2
ipython                  8.10.0
ipython-genutils         0.2.0
ipywidgets               8.0.4
scipy                    1.10.0

I've tried all my other older conda environments, none of them work today.  I use jupyter notebooks every day in vscode, so something is very broken....  strangely I get the same infinite progress bar even with code . --disable-extensions as shown
below:

Ah, interesting, a complete uninstall/reinstall of VS code resolved the issue for me.  Seems uninstall/reinstall does not remove all the extensions, so it kept all my extensions and the empty jupyter notebook opens just fine and infinite progress is gone:

This is what was supposed to happen after the pip list line that got stuck:
info 13:37:57.464: Process Execution: > ~\Anaconda3\envs\coyote\python.exe -m ipykernel_launcher --ip=<IP_ADDRESS> --stdin=9003 --control=9001 --hb=9000 --Session.signature_scheme="hmac-sha256" --Session.key=b"356cd457-929f-418c-b95a-144ff172be7f" --shell=9002 --transport="tcp" --iopub=9004 --f=c:\Users\clovett.REDMOND\AppData\Roaming\jupyter\runtime\kernel-v2-42076iOgwHZ93zVUc.json
> ~\Anaconda3\envs\coyote\python.exe -m ipykernel_launcher --ip=<IP_ADDRESS> --stdin=9003 --control=9001 --hb=9000 --Session.signature_scheme="hmac-sha256" --Session.key=b"356cd457-929f-418c-b95a-144ff172be7f" --shell=9002 --transport="tcp" --iopub=9004 --f=c:\Users\clovett.REDMOND\AppData\Roaming\jupyter\runtime\kernel-v2-42076iOgwHZ93zVUc.json
info 13:37:57.464: Process Execution: cwd: d:\temp\face_segmentation
cwd: d:\temp\face_segmentation
info 13:37:57.681: ipykernel version & path 6.15.2, ~\Anaconda3\envs\coyote\lib\site-packages\ipykernel\__init__.py for c:\Users\clovett.REDMOND\Anaconda3\envs\coyote\python.exe
info 13:37:58.730: Started Kernel coyote (Python 3.10.6) (pid: 47764)
info 13:37:58.761: Process Execution: > ~\Anaconda3\envs\coyote\python.exe ~\.vscode\extensions\ms-toolsai.jupyter-2023.1.2010391206\pythonFiles\printJupyterDataDir.py
> ~\Anaconda3\envs\coyote\python.exe ~\.vscode\extensions\ms-toolsai.jupyter-2023.1.2010391206\pythonFiles\printJupyterDataDir.py

The uninstallation and installation pointed me to a solution!
On Mac systems VS code stores data in $HOME/Library/Application Support/Code, so a full reinstallation would need to delete this folder.
This indeed resolved the issue for me, but to avoid redoing all of my setup I narrowed down the exact cause cause by selectively deleting parts of that folder. In my case the culprit was the settings.json file in the User subdirectory.
Particularly, I had the lines
"jupyter.experiments.optInto": [
    false
    ],

in there.
I don't remember whether I selected an appropriate setting at some point.
Possibly this might be an outdated setting from an older version of the jupyter extension.
In any case, deleting these lines resolves this issue.


Update 0000.md and Create 0030.md

Please check 0030.md on https://beta.programming.in.th/render first before committing (it is not working right now)


Idea: Wouldn't it be possible for Tokenmonster to stop when it reaches the idea vocab size?

Just an idea. When I train Tokenmonster with an immensely big dataset, I realize at a certain small vocab size, the workers struggle to remove anymore from the vocab. I take it as a sign that the vocab-size is already approaching optimal when it reaches that state.
What do you think?

I see. Thank you for explaining!


Having issue using 4x-Ultrasharp in postprocessing

I'm having an issue upscaling with 4x-Ultrasharp in postprocessing. This is the total progress after after batch 1 and then the error:
Batch 1/1
0% 0/50 [00:00<?, ?it/s]
2% 1/50 [00:00<00:07,  6.55it/s]
4% 2/50 [00:00<00:07,  6.64it/s]
6% 3/50 [00:00<00:07,  6.62it/s]
8% 4/50 [00:00<00:06,  6.68it/s]
10% 5/50 [00:00<00:06,  6.72it/s]
12% 6/50 [00:00<00:06,  6.72it/s]
14% 7/50 [00:01<00:06,  6.67it/s]
16% 8/50 [00:01<00:06,  6.70it/s]
18% 9/50 [00:01<00:06,  6.70it/s]
20% 10/50 [00:01<00:05,  6.70it/s]
22% 11/50 [00:01<00:05,  6.71it/s]
24% 12/50 [00:01<00:05,  6.72it/s]
26% 13/50 [00:01<00:05,  6.72it/s]
28% 14/50 [00:02<00:05,  6.70it/s]
30% 15/50 [00:02<00:05,  6.70it/s]
32% 16/50 [00:02<00:05,  6.71it/s]
34% 17/50 [00:02<00:04,  6.69it/s]
36% 18/50 [00:02<00:04,  6.68it/s]
38% 19/50 [00:02<00:04,  6.68it/s]
40% 20/50 [00:02<00:04,  6.67it/s]
42% 21/50 [00:03<00:04,  6.67it/s]
44% 22/50 [00:03<00:04,  6.65it/s]
46% 23/50 [00:03<00:04,  6.67it/s]
48% 24/50 [00:03<00:03,  6.69it/s]
50% 25/50 [00:03<00:03,  6.68it/s]
52% 26/50 [00:03<00:03,  6.68it/s]
54% 27/50 [00:04<00:03,  6.66it/s]
56% 28/50 [00:04<00:03,  6.69it/s]
58% 29/50 [00:04<00:03,  6.67it/s]
60% 30/50 [00:04<00:02,  6.67it/s]
62% 31/50 [00:04<00:02,  6.67it/s]
64% 32/50 [00:04<00:02,  6.69it/s]
66% 33/50 [00:04<00:02,  6.64it/s]
68% 34/50 [00:05<00:02,  6.64it/s]
70% 35/50 [00:05<00:02,  6.63it/s]
72% 36/50 [00:05<00:02,  6.67it/s]
74% 37/50 [00:05<00:01,  6.64it/s]
76% 38/50 [00:05<00:01,  6.64it/s]
78% 39/50 [00:05<00:01,  6.63it/s]
80% 40/50 [00:05<00:01,  6.65it/s]
82% 41/50 [00:06<00:01,  6.65it/s]
84% 42/50 [00:06<00:01,  6.59it/s]
86% 43/50 [00:06<00:01,  6.60it/s]
88% 44/50 [00:06<00:00,  6.54it/s]
90% 45/50 [00:06<00:00,  6.53it/s]
92% 46/50 [00:06<00:00,  6.42it/s]
94% 47/50 [00:07<00:00,  6.43it/s]
96% 48/50 [00:07<00:00,  6.54it/s]
98% 49/50 [00:07<00:00,  6.60it/s]
100% 50/50 [00:07<00:00,  6.65it/s]
Error completing request
Arguments: ([[0, ' ((Best quality)), ((masterpiece)),((realistic)),lord of the rings hobbit village, blue sky on top, scenic, masterpiece'], ['3', '((Best quality)), ((masterpiece)),((realistic)),lord of the rings lush green mountain forest with small river, blue sky on top, scenic, masterpiece'], ['6', '((Best quality)), ((masterpiece)),((realistic)),lord of the rings mountain valley in the alps, blue sky on top, scenic, masterpiece']], 'frames, borderline, text, character, duplicate, error, out of frame, watermark, low quality, ugly, deformed, blur  bad-artist', 8, 7, 50, None, None, 30, 1, 0, 0, 1, 0, 2, False, 0, 2, 512, 512, 1, 'Euler a', True, '4x-UltraSharp', 2) {}
Traceback (most recent call last):
File "/content/stable-diffusion-webui/modules/call_queue.py", line 56, in f
res = list(func(*args, **kwargs))
File "/content/stable-diffusion-webui/modules/call_queue.py", line 37, in f
res = func(*args, **kwargs)
File "/content/stable-diffusion-webui/extensions/infinite-zoom-automatic1111-webui/scripts/infinite-zoom.py", line 242, in create_zoom
result = create_zoom_single(
File "/content/stable-diffusion-webui/extensions/infinite-zoom-automatic1111-webui/scripts/infinite-zoom.py", line 352, in create_zoom_single
do_upscaleImg(current_image, upscale_do, upscaler_name, upscale_by)
File "/content/stable-diffusion-webui/extensions/infinite-zoom-automatic1111-webui/scripts/infinite-zoom.py", line 102, in do_upscaleImg
ups.process(
File "/content/stable-diffusion-webui/scripts/postprocessing_upscale.py", line 94, in process
upscaled_image = self.upscale(pp.image, pp.info, upscaler1, upscale_mode, upscale_by, upscale_to_width, upscale_to_height, upscale_crop)
File "/content/stable-diffusion-webui/scripts/postprocessing_upscale.py", line 64, in upscale
image = upscaler.scaler.upscale(image, upscale_by, upscaler.data_path)
File "/content/stable-diffusion-webui/modules/upscaler.py", line 63, in upscale
img = self.do_upscale(img, selected_model)
File "/content/stable-diffusion-webui/modules/esrgan_model.py", line 154, in do_upscale
img = esrgan_upscale(model, img)
File "/content/stable-diffusion-webui/modules/esrgan_model.py", line 225, in esrgan_upscale
output = upscale_without_tiling(model, tile)
File "/content/stable-diffusion-webui/modules/esrgan_model.py", line 204, in upscale_without_tiling
output = model(img)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/content/stable-diffusion-webui/modules/esrgan_model_arch.py", line 62, in forward
return self.model(feat)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/container.py", line 204, in forward
input = module(input)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/content/stable-diffusion-webui/extensions-builtin/Lora/lora.py", line 201, in lora_Conv2d_forward
return lora_forward(self, input, torch.nn.Conv2d_forward_before_lora(self, input))
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/conv.py", line 463, in forward
return self._conv_forward(input, self.weight, self.bias)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/conv.py", line 459, in _conv_forward
return F.conv2d(input, weight, bias, self.stride,
RuntimeError: Given groups=1, weight of size [64, 3, 3, 3], expected input[1, 4, 192, 192] to have 3 channels, but got 4 channels instead
Traceback (most recent call last):
File "/usr/local/lib/python3.9/dist-packages/gradio/routes.py", line 337, in run_predict
output = await app.get_blocks().process_api(
File "/usr/local/lib/python3.9/dist-packages/gradio/blocks.py", line 1018, in process_api
data = self.postprocess_data(fn_index, result["prediction"], state)
File "/usr/local/lib/python3.9/dist-packages/gradio/blocks.py", line 935, in postprocess_data
if predictions[i] is components._Keywords.FINISHED_ITERATING:
IndexError: tuple index out of range
I use a colab. I don't know if that has anything to do with it. I have already created other infinite zoom videos, so this the next thing I am testing.

LORA is maybe the key here.
please provide prompts ("export prompt" or screenshot). I assume you use a LORA in your prompts.
If yo, please try again with easy prompt "like 0,cat,1,dog"

I ran it again without the LORA prompt. It gave the same error messages for 4x-Ultrasharp, so I ran it with upscalers Lanczos and Nearest. They worked, but I prefer to use 4x-Ultrasharp.

ok, btw automatic is dedicated strictly to python 3.10.6
you run for some reason 3.9
maybe you clean your venv and setup it new to ensure basic compatibility
on our dev machines is nonissue about 4x uktrasharo, so therefore i assume some specific reason on your setup. let try the ox 3.10.6 now

I didn't create the colab. It was made Camenduru.

sorry, we support only Automatic1111 and since recent days Vladmandics fork.
collabs and derivates or completely differten platforms COULD work, but I dont see we cant support em all


[CC-30333] auth: use JWT for authentication

This PR allows using the Terraform Provider via JWT authentication, in addition to API Keys. The JWT auth mechanism requires a CC_VANITY_NAME env capturing the vanity name of the org with the corresponding JWT Issuer. In case the JWT is issued against multiple identities, it also requires a CC_USERNAME env capturing the user / service account to impersonate. Eventually, we will add a CI stage for running acceptance tests via this auth mechanism.
Commit checklist

[x] Changelog
[x] Doc gen (make generate)
[x] Integration test(s)
[ ] Acceptance test(s)
[x] Example(s)

This one seems a bit off, but lets fix the message in another round.  We can fix later.  It's talking about both JWT Issuer and Invalid API key.
    jwt_issuers_test.go:148: Step 1/3 error: Error running apply: exit status 1

        Error: Error creating JWT Issuer

          with cockroach_jwt_issuer.test,
          on terraform_plugin_test.tf line 12, in resource "cockroach_jwt_issuer" "test":
          12: resource "cockroach_jwt_issuer" "test" {

        Could not create JWT Issuer: invalid API key
--- FAIL: TestAccJWTIssuerResource (0.34s)

@pritesh-lahoti i just noticed the commit message needs to be updated with the new env var names.

This one seems a bit off, but lets fix the message in another round. We can fix later. It's talking about both JWT Issuer and Invalid API key.
    jwt_issuers_test.go:148: Step 1/3 error: Error running apply: exit status 1

        Error: Error creating JWT Issuer

          with cockroach_jwt_issuer.test,
          on terraform_plugin_test.tf line 12, in resource "cockroach_jwt_issuer" "test":
          12: resource "cockroach_jwt_issuer" "test" {

        Could not create JWT Issuer: invalid API key
--- FAIL: TestAccJWTIssuerResource (0.34s)

It is talking about JWT issuer because the test deals with cockroach_jwt_issuer resource. Apologies for the confusion.


Refactor last 2 paladin spells

Test changes are just from RNG; crit roll now occurs always, instead of only for non-demon/undead targets.


support offline install

can support offline install?
[root@minio-1 ~]# rclone rcd --rc-web-gui
2020/12/27 17:32:56 NOTICE: A new release for gui is present at https://github.com/rclone/rclone-webui-react/releases/download/v2.0.3/currentbuild.zip
2020/12/27 17:32:56 NOTICE: Downloading webgui binary. Please wait. [Size: 4750769, Path :  /root/.cache/rclone/webgui/v2.0.3.zip]

yep, I also request this feature, because network problems


Update google_riscv-dv to google/riscv-dv@59dcd8c

This updates the vendored riscv-dv, which should fix up the part of https://github.com/lowRISC/ibex/pull/1284 that we don't want to patch locally. Once this is merged, we can rebase that PR and hopefully that will be good to go.
Update code from upstream repository https://github.com/google/riscv-
dv to revision 59dcd8c813484eb6dcca67e7e36089fe772b9cc8

Update scripts for Metrics CI regression:  bug fixes, change ISS to
spike in CI regression (Aimee Sutton)
Add illegal and load store instruction (aneels3)
Avoid generating hint instruction when RV32C is turned off
(google/riscv-dv#787) (taoliug)
Fix illegal opcode issue in the cov_test (google/riscv-dv#786)
(taoliug)
[questa] Remove -access=rwc from vlog command line arguments (Rupert
Swarbrick)
[ci] temporarily disable CI flow (Udi Jonnalagadda)
fix issue with rcs for num_of_harts (aneels3)
fix multi-hart label issue (aneels3)
add multi_hart test (ishita71)
Fix minor issues (aneels3)
Add riscv_signature_pkg (aneels3)
add gen_signature_handshake (ishita71)
Add gen_interrupt_vector_table (aneels3)
Remove the unnecessary lines (Anil Sharma)
fix issue with riscv_rand_instr_test (aneels3)
Add multiprocessing code block (aneels3)

Signed-off-by: Rupert Swarbrick<EMAIL_ADDRESS>

Note to self: Once this is merged, go back to #1284 and ask the original author to rebase and test.


[EmbeddingAPI-usecase] Add usecase for XWalkResourceClient API onRece…

…ivedHttpAuthRequest
-Add usecase for XWalkResourceClient API onReceivedHttpAuthRequest
-Cover the XWalkActivity and XWalkInitializer two ways
Impacted tests(approved): new 2, update 0, delete 0
Unit test platform: [Android]
Unit test result summary: pass 2, fail 0, block 0
https://crosswalk-project.org/jira/browse/XWALK-3477

@Shao-Feng please help to review.

LGTM


Build fail: Rollup failed to resolve import

Describe the bug
I try to integrate slidev into my blog.
slidev folder at : https://github.com/keaising/keaising.github.io/tree/source/share/git
I can run npx slidev  --open --remote and npx slidev export successfully in Ubuntu, but npx slidev build failed with these error message:
$ npx slidev build

  ●■▲
  Slidev  v0.21.3

  theme   ./theme
  entry   /home/taiga/code/github.com/keaising/keaising.github.io/share/git/slides.md

vite v2.3.8 building for production...
✓ 64 modules transformed.
[vite]: Rollup failed to resolve import "merge.gif" from<EMAIL_ADDRESS>This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
Error: [vite]: Rollup failed to resolve import "merge.gif" from<EMAIL_ADDRESS>This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
    at onRollupWarning (/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/vite/dist/node/chunks/dep-0ed4fbc0.js:45533:19)
    at onwarn (/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/vite/dist/node/chunks/dep-0ed4fbc0.js:45323:13)
    at Object.onwarn (/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/rollup/dist/shared/rollup.js:20281:13)
    at ModuleLoader.handleResolveId (/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/rollup/dist/shared/rollup.js:19636:26)
    at /home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/rollup/dist/shared/rollup.js:19583:22
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 1)
    at async ModuleLoader.fetchStaticDependencies (/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/rollup/dist/shared/rollup.js:19581:34)
    at async Promise.all (index 0)
    at async ModuleLoader.fetchModule (/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/rollup/dist/shared/rollup.js:19557:9) {
  watchFiles: [
    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/index.html',
<EMAIL_ADDRESS>    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/vue/dist/vue.runtime.esm-bundler.js',
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    '/@windicss/devtools',
    '/@slidev/styles',
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/theme/styles/index.ts',
<EMAIL_ADDRESS>    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/@slidev/client/App.vue?vue&type=script&setup=true&lang.ts',
<EMAIL_ADDRESS><EMAIL_ADDRESS>    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/vue-router/dist/vue-router.esm-bundler.js',
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/theme/styles/layouts.css',
    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/theme/styles/prism.css',
    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/theme/styles/shiki.css',
    '/@slidev/routes',
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/vue-demi/lib/index.esm.js',
    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/<EMAIL_ADDRESS>    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/<EMAIL_ADDRESS>    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/popmotion/dist/es/index.js',
<EMAIL_ADDRESS>    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/@slidev/client/internals/Play.vue?vue&type=script&setup=true&lang.ts',
    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/@slidev/client/internals/Presenter.vue?vue&type=script&setup=true&lang.ts',
    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/node_modules/@slidev/client/internals/Presenter.vue?vue&type=style&index=0&scoped=true&lang.postcss',
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/theme/layouts/cover.vue',
    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/theme/layouts/full-image-right.vue',
<EMAIL_ADDRESS>    '/home/taiga/code/github.com/keaising/keaising.github.io/share/git/theme/layouts/quote.vue',
<EMAIL_ADDRESS><EMAIL_ADDRESS>    '@vite-icons/carbon/arrow-right',
    '@vite-icons/mdi/alert-circle'
  ]
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

There are some environments:
Δ node -v
v16.4.0

Δ npm -v
7.18.1

Δ npx -v
7.18.1

Δ npx slidev -v
0.21.3

I'm sure the file merge.gif in error message exists. Even if I comment the merge.gif, the later images in <img> such as *.gif / *.png / *.jpg will produce the same error too
To Reproduce
Steps to reproduce the behavior:
You can find Github Action stage named Build shares, they have the same error message with build results in my local Ubuntu

Github Action with Ubuntu: https://github.com/keaising/keaising.github.io/runs/2920953166?check_suite_focus=true
Github Action with macOS: https://github.com/keaising/keaising.github.io/runs/2920962508?check_suite_focus=true

Github Action config I use as below, you can find full config in https://github.com/keaising/keaising.github.io/blob/source/.github/workflows/publish.yml
      - name: Build shares
        run: |
          cd share/git
          node --version
          npm --version
          yarn install
          yarn build

Desktop (please complete the following information):

OS: Ubuntu 20.04
Browser: Chrome
Slidev version: 0.21.3

I have searched for [vite]: Rollup failed to resolve import, many results show that maybe it is a bug of vite, but I'm not familiar with both vite and the integration of slidev and vite.

Add leading slash to the path:
https://sli.dev/guide/syntax.html#static-assets


Using Cellrank for metabolic-labelling-based RNA velocity

...
Hi Marius,
I am wondering whether CellRank can be directly used for the metabolic-labeling experiments, and the labeling RNA velocity computed with Dynamo, which is released recently on Cell.
Thanks

Hi @117999, thanks for your question. As long as dynamo gives you high-dimensional velocity vectors, this should work by simply applying the VelocityKernel to it. This is quite an interesting application, so please keep us up to date with your experiments and let us know in case you encounter difficulties along the way.

Hi Marius,
Thanks a lot for your timely reply. I have tried to apply the VelocityKernel and compute the transition matrix. However, warnings appeared that WARNING: KNN graph is not symmetric
and upon computing the transition matrix, it shows that ValueError: Matrix is not row-stochastic. The following rows don't sum to 1
I am wondering why would the KNN graph not symmetric, and what's the interpretation for my data?
Thank you

How did you compute the KNN graph?

(in my analogy, x and y are cells)

Hi @117999, did my post above help in any way?

Hi Marius,
Sorry for my late response. I have followed your suggestions to use the connectivities. It appeared that this works well for the expression profile. However, the problem arises when I tried to compute the transition matrix from the VelocityKernel.
Here follows my code.
sc.pp.neighbors(adata) vk_n = VelocityKernel(adata,vkey='velocity_T',xkey='X_total') print(vk_n) vk_n.compute_transition_matrix()
It turns out that ValueError: Matrix is not row-stochastic.  Are there Nan's in velocity_T or X_total? What are the dimensions of these matrices, etc?  Do some sanity checks before feeding into the velocity kernel please

Closing due to inactivity.


Login with custom cookieDomain not working

I found a strange behaviour when a custom cookie domain is set in the cookie store. If I try to login, an instant redirect back to my login page is triggered and the cookie will not be set. Setting a cookie directly with plain js via the console works flawlessly. Is there a known bug or did I miss something in my configuration?
// app/session-stores/application.js

import CookieStore from 'ember-simple-auth/session-stores/cookie';
import config from '../config/environment';

const twoDays = 2 * 60 * 60 * 24;

export default CookieStore.extend({
  cookieName: 'app-backend-session',
  cookieExpirationTime: twoDays,
  cookieDomain: `${config.APP.cookieDomain}`
});

// app/config/environment.js

module.exports = function(environment) {
  let ENV = {
...
    APP: {
      cookieDomain: '.domain.com'
      // Here you can pass flags/options to your application instance
      // when it is created
    },
...
  };

  return ENV;
};

Nevermind, found the bug. Tourned out, something with the name of my cookie wasn't right. Closing this now.


[MAISTRA-695] Roll back changes to the build system

did you really want to revert maistra-430?

@rcernich I believe it is one of the issues which came after the switch to Makefile so it will need to be reopened.


cannot use int64(value) (type int64) as type string in field value

hello, when i try to run the examples/client.go .     the error is :
github.com/OpenBazaar/spvwallet
......\pkg\mod\github.com!open!bazaar\spvwallet@v0.0.0-20200112224336-39f04e8d6d34\mock.go:235:3: cannot use int64(value) (type int64) as type string in field value
......\pkg\mod\github.com!open!bazaar\spvwallet@v0.0.0-20200112224336-39f04e8d6d34\mock.go:325:3: cannot use 1000000 (type untyped int) as type string in field value
......\pkg\mod\github.com!open!bazaar\spvwallet@v0.0.0-20200112224336-39f04e8d6d34\mock.go:341:17: cannot use 4 (type untyped int) as type string in assignment
check the version :
<EMAIL_ADDRESS><EMAIL_ADDRESS>there are some type values not match in this two projects.

solved, my go environment is wrong.


Add macOS to CI matrix builds

This hopefully avoids issues like https://github.com/rpki-client/rpki-client-portable/issues/84 in the future.

Merged this and did some further cleanup in the compiler matrix.
There is little point in testing older compilers since we're interested in new warnings and errors.
Also only do the test run on linux systems.


Derive MongoDB content store from Postgres

The content store is being migrated from MongoDB to Postgres. See
https://github.com/alphagov/content-store/pull/1085.
Closes #514.  Trello.
This is a first attempt to adapt to using the Postgres version.

Restore the backup of the Postgres database.
Export the content_items table as lines of JSON.
Import the JSON into MongoDB.
Query as before.

Easy to develop, similar to existing steps in the data pipeline

Avoids translating the MongoDB queries into Postgres ones

Not in the spirit of GOV.UK's policy to stop using MongoDB

Extends the data pipeline in both time and complexity

Misses the opportunity to improve the whole pipeline, such as by using
the Publishing API database for everything, instead of using the
Content Store for some things.

Structure of the PR
.github/workflows
The PR introduces a new docker image, which must be built.  These GitHub Actions do so in each environment.
docker/content
A new docker image for restoring the backup file of the new postgres implementation of the Content Store database, and exporting the data as JSON, to be loaded into MongoDB.
It is similar to the other images, by fetching a script run.sh from a copy of the HEAD of this repository that is synced to a bucket, and executing it.
run.sh
This is similar to the run.sh script of the postgres image, as far as fetching and restoring the database backup file.  Having done that, it does a few straightforward steps.  There is no Makefile.

Exports the content_items table as as JSON file, and uploads it to a bucket.
Creates an instance of the mongodb virtual machine, which will fetch that JSON file from the bucket, load it, and then proceed as it always used to do.
Exports the content_items table as a CSV file, and uploads it to a bucket.
Wipes and repopulates the content.content_items table in BigQuery from that file in the bucket.
Deletes itself.

docker/mongodb
The script run.sh has been altered to use the JSON file that was created by the content virtual machine, instead of the backup file of the MongoDB implementation of the Content Store.  An unnecessary command at the end has also been removed.
src/content
These postgres configuration files are for the same purpose as their counterparts in src/postgres.  It takes ages to restore database backup files unless postgres is configured to optimise it for writing rather than for resilience.  Once the backup has been restored, postgres is restarted with a more resilient configuration.
src/mongodb
A step has been removed, which was to export the whole content_items collection to a JSON file and upload it to a bucket.  The content virtual machine now does this step instead, as a CSV file.
A few queries have been tweaked to omit documents that have a null value of a given field, rather than that field not existing at all. This is necessary because when Postgres expresses a row of data as JSON, it emits every field every time, even when the value is null, whereas the original MongoDB implementation usually didn't include a field at all if its value was null.
terraform-dev, terraform-staging, terraform
A new virtual machine, content, gets its own service account, which is given access to various things, similarly to its counterparts for the postgres and mongodb virtual machines.  The virtual machine is configured similarly to the postgres one.  In particular, it has a local SSD (solid-state disk) so that the database restore task runs much, much quicker.
The content.content_items table gets a new schema, because it now resembles the postgres table rather than the MongoDB collection.  The actual data is the same.
The workflow govuk-integration-database-backups.yaml gets a new entry to run the new content virtual machine when a backup file of the new postgres implementation of the content store database becomes available.  The entry for running the mongodb virtual machine is removed.  GitHub's diff makes a meal of this, but that's what has happened.  One section removed, one section added.

Thanks @guilhem-fry, I've implemented your suggestion in https://github.com/alphagov/govuk-knowledge-graph-gcp/pull/546/commits/f71da5a9a8a246c55722134a7faaa3af5900c150


are to ar?

the word 'are' is stemming to 'ar'; are there configs/ways to handle strange cases?

I think you can try instantiating your classifier with the other bundled
stemmer object (it uses porter stemmer by default).
You could always patch porter stemmer or fork your own version that
contains a blacklist of words not to stem then pass that in. I've been
considering this myself.
On Aug 8, 2016 1:33 PM, "Dave Edelhart"<EMAIL_ADDRESS>wrote:
the word 'are' is stemming to 'ar'; are there configs/ways to handle
strange cases?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NaturalNode/natural/issues/300, or mute the thread
https://github.com/notifications/unsubscribe-auth/AItvdZSxUurDHmCPoyAL_mwg5ewburhwks5qd5EsgaJpZM4JfcGC
.

thanks; I believe I am using porterStemmer
      return natural.PorterStemmer.stem(word.toLowerCase());

Np. I hope this enables you to do what you're looking to do!
On Aug 16, 2016 11:28 AM, "Dave Edelhart"<EMAIL_ADDRESS>wrote:

thanks; I believe I am using porterStemmer
  return natural.PorterStemmer.stem(word.toLowerCase());

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NaturalNode/natural/issues/300#issuecomment-240193533,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AItvdeXjFtWuFJCZLjX0cJmCdhCt_tgpks5qggFCgaJpZM4JfcGC
.

seems like nltk has something to handle 'are':
>>> stemmer = PorterStemmer()
>>> stemmer.stem("are")
u'are'

pretty sure it must be something like what @jburb described because other implementations still seem to stem are to ar


MyPy plugin

It is possible that code implemented using new API will fail to validate with MyPy because of its magicalness. If this is the case, we will have to explore implementing a custom MyPy plugin for supporting GraphQL types defined using the library.

This is solved by type annotations, if there will be a need in the future to have MyPy plugin I will reopen this issue


provide contributor guidelines

It would be good to know how the okhttp community wants new contributors to proceed, preferably as a typical CONTRIBUTING doc alongside the README.
A decent template can be found here: https://github.com/nayafia/contributing-template
A good real-world example can be seen here: https://github.com/chef/chef/blob/master/CONTRIBUTING.md

Yep.
Many open source projects are quite welcoming to new contributors. I’m reluctant to solicit new contributors because I want this project to remain small and focused. I prefer to produce a very high-quality artifact over building a flourishing community of contributors.
That said, if you’re a potential contributor, our contributing guide is this video:
https://www.youtube.com/watch?v=PCxz2LEmuL4

Hey Jesse, not to keep bringing up the subject, but would it be worth including what you mentioned above either in the project read me, or perhaps on the OKHttp site, or link the contributing portion of the site in the readme?

@swankjesse @JakeWharton Can I work on this?

I'd like to do this myself. It's about defining our policy and it's not a good fit for contributors.

Voila: https://github.com/square/okhttp/blob/master/CONTRIBUTING.md


readdir_r not found

Please add support for https://linux.die.net/man/3/readdir_r

Great idea!  I added readdir_r().  Can you try if it works OK?

Thanks for the update. I'll try it out and let you know


List of models that animate incorrectly

chr005
chr777

Suspected cause is the bone masks

Animations were correct in alpha.4 - something has changed whilst implementing more animation features that broke them!!


Various Improvements

Hi, so these are some changes I did while starting to dive deeper into the crate.  No functional changes so far, just structural ones.  I have some ideas for functional changes but I wanted to get these other things out of the way first.
I know this is quite a large changeset and I understand if you don't like some of the changes I did.  I tried keeping each change in a separate commit, so you'll have an easier time reviewing this PR by going through it commit by commit.  If you don't like something, I can drop the related commit again.
Importantly, there are breaking changes in here.  I would suggest to not release them right away as I want to send you some more PRs with functional changes that are also API breaking...  Although I cannot promise a timeframe for that, so you'll have to decide how you want to proceed...

I've shuffled some items in the crate around to (in my eyes) clean-up the crate structure a bit.
I've adjusted the GitHub Actions workflow again for the changes and to fix some things I missed last time around.
And finally I've updated the README to reflect the changes and to fix some issues in it (README preview).  I've also moved the changelog into its own file so it is easier to find.

Please let me know what you think of this!

Thanks for the huge work. I am going to review all the commits next week. As there are lots, it could take some time.

Don't worry, take your time.

Modbus context size is a disputable thing. I agree to make small as the default one (with increasing crate minor ver) but "full context" is not clear. I'm going to merge that commit but I'll add two features instead to set the size: modicon (the classic one, with 10k registers per type) and full (65535, max allowed currently)

I agree to make small as the default one

Careful, right now the "full" (10k) context is still the default because the fullcontext feature is enabled by default.  I only did this change so the feature complies with the "additive only" design.

Ah, ok. That's fine then let's keep it as-is


LETI, 9381, LockFree Ordered LinkedList. Ready.

Thanks you very mush but it is not lock-free list.
That code will not work properly in multi-threaded environment.
Lock-free stuff must use atomic primitive - atomic load/store, atomic CAS - from STL.
You should use some kind of safe memory reclamation schema like Hazard Pointer or user-space RCU to prevent memory corruption when one thread is trying to remove list's node and another is reading the same node. And so on...
If you need more comments please email me at<EMAIL_ADDRESS>


Fails to run on Mac SDL2 dependency and OpenGL

I forgot the exact command, but I think it's -glcore33 or something like it that I have to add in order to use any Sokol related libraries.   I'm using an older Mac from 2011, so you may not want to support it.
I also had to do a "brew install pkg-config sdl2" for the first error.
Here is the last error.
Assertion failed: (desc->context.metal.device), function _sg_mtl_setup_backend, file sokol_gfx.h, line 10752.
Edit: It does run with the proper command.   v -d darwin_sokol_glcore33

Yes macOS is not very well tested yet. My own mac is very old and I do not have access to other hardware so mac development is slow.
Linux, Windows and Android is what I have the best access to currently so development is leaning towards those platforms. I know that all dependencies should work under mac, including using metal for rendering - it just needs time

Yes my MBP is from and 2011, so anything above that should support metal. I'll keep this mind when testing your framework.  Thanks for the response and your work!

I've just commited dbfa590.
This makes it so you can do e.g. v run  ~/.vmodules/shy/examples/image/image.v without specifying any -d flags, and thus use OpenGL core 3.3 on macOS per default.
I think for now it is best to to make metal opt-in via -d metal. Please not that I haven't had time to actually implement proper Metal support. But it is on my (long) TODO list :sweat_smile:

Running my test project puzzle_vibes works and isn't too demanding:


Achievements gallery size

hello,
Would it be possible to modify the gallery size for achievements section? I want to change the layout?

I found the JS functtion :).


Delete near.panic()

near.panic('Message') is doing exactly the same as throw new Error('message'). Let's delete near.panic('Message'), mentions that this env.panic() API is not used and refactor examples/tests.

Good idea!

@ailisp
nomicon.io says that panic does not accept any arguments. Only panic_utf8 does.
https://nomicon.io/RuntimeSpec/Components/BindingsSpec/MiscellaneousAPI
but in our code, both functions accept message parameters:
export function panic(msg?: string): never {
  if (msg !== undefined) {
    env.panic(msg);
  } else {
    env.panic();
  }
}

export function panicUtf8(msg: string): never {
  env.panic_utf8(msg);
}

Can I delete both of them? Can we replace all edge cases with throw new Error(message)?

Can I delete both of them? Can we handle all edge cases with throw new Error(message)?

For panic, it's covered by throw new Error and can be safely deleted. For panicUtf8, I think practically it's not useful, can be dropped, although in theory not all edge cases are handled.
In detail, panicUtf8 takes a decoded bytes, nearcore encode it back to UTF-8 and prints. In panic it takes JS string, log as is. For example, utf8 decode 水 is [0xe6, 0xb0, 0xb4]. near.panicUtf8(bytes('\xe6\xb0\xb4')) prints 水. near.panic('水') prints 水, near.panic(bytes('\xe6\xb0\xb4')) prints 'æ°´' (char 0xe6, char 0xb0, char 0xb4). You can check more cases in test_log_panic_api.ava.js


Build from 'builder.dockerfile' if exists

This change allows to track the used Builder tag in a Dockerfile. This is useful for using Dependabot to keep the builder version up to date.
Users of the Builder who wish to use Dependabot will need to create a builder.dockerfile next to their build script with the following contents:
FROM ghcr.io/gardenlinux/builder:SHA

Where SHA will be updated by dependabot if configured correctly.
also users will need to set the container_image value in build to localhost/builder

Superseded by #1874


Migrate core time-travel logic to Elm

The intention is for all time-travel state and interaction to be managed within Elm, and for this Elm core to only interact with the runtime system through a small API involving:

outgoing: restoring and taking snapshots, and replaying events.
incoming: storing new events and snapshots

Part of #106. The hope is that fixes for time travel & swapping bugs will become more clear when this logic is in Elm.

Closed in favor of #135


It seems that ACR does not perform well on single-hand image

This might be caused by the image quality. I would strongly recommend you use RGB as input. The better the image quality, the better the performance (You can try the provided demo.mp4. As you can see from the gif on the README, it performs pretty well on single-hand image from random YouTube videos.)
Please don't hesitate to post your updates when you tried input with better image quality

This might be caused by the image quality. I would strongly recommend you use RGB as input. The better the image quality, the better the performance (You can try the provided demo.mp4. As you can see from the gif on the README, it performs pretty well on single-hand image from random YouTube videos.)
Please don't hesitate to post your updates when you tried input with better image quality

There is no doubt that it performs well in the provided demo.mp4. But when I tryed a new RGB video with only single-hand, it still often outputs two-hand results.
bad

good

Here is result video: https://drive.google.com/file/d/1Ba7jmtGqcdpPgYocD49N3mlw2qo2gdMc/view?usp=sharing


Convert pip-checker to use ERB templates for questions

Looks good to me.

I've rebased on master and force pushed in preparation for merging.


New/Open Project doesn't work anymore

macOS 14, pyxy3d 61065143e92da658883e716fffe8e2e6b56878f4.
When I select "New/Open Project" in the menu, nothing happens.

Hi @rgov,
I'm in the final stages of getting the pre-recorded workflow organized in the GUI (literally working on it right now). In a day or two I might have things ready to test and find problems. I'll reply again to this issue and @ you when it's ready to go.
Mac

Cool. Fwiw, this was broken in 7056781 due to removal of the call to connect_menu_actions().

@rgov
The current main (as well as the 0.3.0 version on PyPI have been updated such that the launching of the workspace should be operable now.
There are some known issues with how the capture volume widget is handled (this is where you can inspect that solution from the extrinsic parameter calibration and set the origin), and I hope to clear that up in the next day or two.
I'm going to out together a sample workflow with some old webcam recorded footage and maybe post a quick video walk through.
In the meantime, many things should be working. In particular, the first stage of the calibration (intrinsic camera setup) should be working. Within workspace/calibration/intrinsic, you can have individual files named port_1.mp4, port_2.mp4, etc. These should be videos with the charuco board being moved through the field of view so that individual frame grabs can be selected to provide the input for the intrinsic camera calibration.
Just wanted to point that out as something that I believe is fully functional and can be played around with. I'd be very interested in your thoughts on the user experience with that portion of the calibration.

@rgov...just a note that I was likely premature in suggesting it might be ready to look at. I'm going through the workflow from scratch with some stuff and finding lots of little GUI-hanging issues that I need to clean up. I'll check back in when I have things stable...

@rgov,
Just wanted to mention that the current version is (to my knowledge) usable. I've thrown a couple patches up tonight to fix things that I saw during this demo video, but in general the workflow functions:

https://www.youtube.com/watch?v=XDfuQ_7m1oQ

I did a walk-through of the required underlying file structure here:

https://youtu.be/dvosFrFVDsU

ASIDE: The RMSE of reprojections in this walk through are definitely larger than they would be with a higher quality board/cameras. I was just trying to throw some demo footage together with what was easily accessible.


Mega-meta-test script.

We need a script that runs all the following tests:

unit tests
bibliopixel demo
bibliopixel run
BiblioPixelAnimation tests

(probably the last one is just a smoke test like all_test.py)

On that note... we should create a new requirements.txt type file that
includes the necessary packages for ALL BPA animations. Which would help
with all this.
On Sun, Aug 13, 2017 at 12:59 PM, Tom Swirly<EMAIL_ADDRESS>wrote:

We need a script that runs all the following tests:

unit tests
bibliopixel demo
bibliopixel run
BiblioPixelAnimation tests

(probably the last one is just a smoke test like all_test.py)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/364, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AA6a6lydEvrJojv4fWGka3yxseNY0EmOks5sXyuFgaJpZM4O1vQk
.

Just as a note - it turns out that there aren't very many packages for BPA, and one of them, pyaudio, cannot be installed in Travis so is no good.

Oh, this is done!  :-)


Invalid fix. Closed. You should not use os:timestamp() as random seed.

@redink  @emqplus #31 shall be the correct fix


Missing step075-vanilla branch?

I'm having trouble finding the code example for the vanilla version of https://eliemichel.github.io/LearnWebGPU/basic-3d-rendering/texturing/loading-from-file.html. Sorry if I'm overlooking something stupid.
Thanks so much for this project! It's a lifesaver!

Yep sorry Vanilla branches are not all ready, I put the priority on non-vanilla ones at the time. In the ongoing wave of update (currently at step037) I try to systematically provide it though. Any particular reason why you need to consult this one in particular that I could help with?

I was trying to figure out how to get texturing working. It's a little easier to follow the full examples than to try and combine all the snippets from the post, but I figured it out.
The reason I'm interested in the vanilla branch is that I'm writing a clojure wrapper which uses webgpu-native as a shared library.
This project has been super helpful! I guess I'll close this issue for now since the vanilla versions are still in progress. Thanks again!