What is the complete Polymer Public API?

I've read pretty much all there is at https://www.polymer-project.org/docs/polymer/polymer.html. I've also stepped through and poked through a fair amount of the code base. There are several element and instance methods that are accessible, and do not have a leading nor trailing underscore, implying they're not private. However none of them are in any documentation I can find.
Realizing Polymer is still "pre-release" and anything could change at anytime, is there some convention or other document that might clarify which, if any, other accessible methods and functions are considered part of the public API and are safe to use?

I recommend to use the version 0.5.4 for now. But there will huge changes with the next release 0.8.
https://divshot.com/blog/web-components/polymer-0-8-sneak-peek/

We've talked about the need for an API Reference for a while. At the moment it's on the list of things we want but doesn't have an ETA. cc @nevir and @arthurevans

I think it's unlikely that we'll have an API reference in time for 0.8; probably closer to 0.9 timeframe.
As for 0.5 goes, we're not as consistent as we'd like with underscore prefixed properties. I would assume private unless documented or stated elsewhere (not great, I know). In 0.8 we're doing a lot better marking things as actually private, so it should hopefully be more clear even before the docs land

Thanks for the replies! New to Polymer, and didn't quite realize 0.6 and 0.7 had been skipped and a rather different 0.8 was around the corner. I'm sure you guys will get there with docs, but understand it's a bit easier to write docs around API's that have some future of not changing, than while their signature's may be in flux. You guys are doing great stuff, and anyway you can indicate accessibility in the source is just extra nice stuff.
Somewhat as a tangent; has anyone given any thought at all to potential problems from element names having to live in a global namespace? I doesn't seem like this is on anyone's radar, probably because there just aren't that many elements around yet and therefore there doesn't seem to be a problem. I just know from experience with lots of different languages, that unless something fundamental changes, and assuming Polymer really takes off at some point, we're going to dealing with multi-hyphenated, long element names, that may still end up conflicting.
I made a proof-of-concept for 0.5.5, that lets element importers specify the name they want to use for the element within their app, as opposed to be forced to use the name the element author thought they should use. Just this simple thing would eliminate any problems with name clashes, and also enable running different versions of the same element side-by-side; also another problem sure to arise should many Polymer Elements, and compositions of them, end up appearing all over the place.
Just curious is all.. Is the thinking that there just won't ever be that many elements, and/or having multi-hyphenated names to effectively namespace everyone away from each won't really be that bad to use and read?
Anyways, Thanks!

@phestermcs there's been discussion about this but I'm not sure if there are any immediate plans to address it. @dglazkov may know more

Namespacing is tracked by https://www.w3.org/Bugs/Public/show_bug.cgi?id=24578 spec bug.


Add C4

Adding a Dataset

Name: C4
Description: https://github.com/allenai/allennlp/discussions/5056
Paper: https://arxiv.org/abs/1910.10683
Data: https://huggingface.co/datasets/allenai/c4
Motivation: Used a lot for pretraining

Instructions to add a new dataset can be found here.
Should fix https://github.com/huggingface/datasets/issues/1710

Update on this: I'm computing the checksums of the data files. It will be available soon

Added in #2575 :)


Handle explicit infinity values for unbounded constraints

Using math.inf or float('inf') for bounds results in problems with de/serialization, varying somewhat depending on the chosen solver. Infinities should be handled as when the bound is not specified.
Here is a minimal reproducible example with glpk, which will successfully serialize but not deserialize:
from optlang.glpk_interface import Model, Variable, Constraint, Objective
from swiglpk import *
import math
import pickle

x1 = Variable('x1', lb=0)
x2 = Variable('x2', lb=-math.inf)
c = Constraint(x1 + x2, ub=100)
model = Model()
model.add([c])

with open('pickle', 'wb') as f:
    pickle.dump(model, f)

with open('pickle', 'rb') as f:
    model = pickle.load(f)

Exception message:
Exception: The GLPK file /tmp/tmp75yn29e3.glpk does not seem to contain a valid GLPK problem:

Output from glpk:
p:4: error: column lower bound/fixed value missing or invalid

Generated GLPK problem file:
p lp min 1 2 2
i 1 u 100
n i 1 38ffbf5a-f244-11e8-a2ad-0242ac130002
j 1 d -inf 10
n j 1 x2
n j 2 x1
a 1 1 1
a 1 2 1
e o f

Are there any situations where specifying an infinite bound instead of None would be necessary/preferable?
In my head an inequality like x > -inf is mathematically pointless, so I do not necessarily agree that infinities should be handled as when the bound is not specified.
Instead of introducing code to handle infinities in a consistent way, I would lean towards specifying in the documentation that bounds should be finite numbers or None.


Thanks for this great app !!!

I found about the soundaura on f-droid, this is most useful productivity app i can ever dream of !!!
😊😊😊
By background playback i can hear my fav piano track while watching lecture...
This application is underrated..Keep your work going !!
if i had to rate this apk, i would have rated 5/5 stars....
Thanks a lot...
Regard Heartlog

Thanks a lot, I'm glad you like it 😊


fix: use patch while setting the new primary instance

Note for reviewers

This patch removes an unnecessary update on the status sub-resource that could cause an error and a retry due to the latest observed generated version change (e.g., the instance manager could update the status while the reconciliation is running).

This sort of optimistic lock could be used for the operator to proper set the primary, in that case it is good that we discover the potential race condition while we execute this operation to further think how to fix it properly

/test limit=local


Submodule llm/llama.cpp/ggml did not contain 9e232f0234073358e7031c1b8d7aa45020469a3b.

Hi,
I've got an older linux server I'm working on and I need to build ollama from scratch in a docker (since I don't have sudo access). The ollama docker build dies with the invalid instruction which I believe is probably fixed in  #871. So I've created a docker that downloads the repo and the pr and then builds. But during the build I get.
 > [stage-0 13/13] RUN /usr/local/go/bin/go generate ./...     && /usr/local/go/bin/go build .:
0.514 go: downloading github.com/pbnjay/memory v0.0.0-20210728143218-7b4eea64cf58
0.516 go: downloading github.com/dustin/go-humanize v1.0.1
0.517 go: downloading github.com/pdevine/readline v1.5.2
0.517 go: downloading github.com/spf13/cobra v1.7.0
0.517 go: downloading github.com/olekukonko/tablewriter v0.0.5
0.517 go: downloading golang.org/x/sys v0.11.0
0.520 go: downloading golang.org/x/crypto v0.10.0
0.521 go: downloading golang.org/x/term v0.10.0
0.532 go: downloading github.com/gin-contrib/cors v1.4.0
0.532 go: downloading github.com/gin-gonic/gin v1.9.1
0.533 go: downloading golang.org/x/exp v0.0.0-20230817173708-d852ddb80c63
0.534 go: downloading golang.org/x/sync v0.3.0
0.540 go: downloading github.com/mattn/go-runewidth v0.0.14
0.543 go: downloading github.com/mitchellh/colorstring v0.0.0-20190213212951-d06e56a500db
0.818 go: downloading github.com/rivo/uniseg v0.2.0
0.866 go: downloading github.com/spf13/pflag v1.0.5
0.903 go: downloading golang.org/x/net v0.10.0
0.903 go: downloading github.com/gin-contrib/sse v0.1.0
0.903 go: downloading github.com/ugorji/go/codec v1.2.11
0.903 go: downloading github.com/pelletier/go-toml/v2 v2.0.8
0.903 go: downloading google.golang.org/protobuf v1.30.0
0.903 go: downloading github.com/mattn/go-isatty v0.0.19
0.904 go: downloading github.com/go-playground/validator/v10 v10.14.0
0.904 go: downloading gopkg.in/yaml.v3 v3.0.1
1.028 go: downloading golang.org/x/text v0.10.0
1.028 go: downloading github.com/leodido/go-urn v1.2.4
1.028 go: downloading github.com/go-playground/universal-translator v0.18.1
1.029 go: downloading github.com/gabriel-vasile/mimetype v1.4.2
1.111 go: downloading github.com/go-playground/locales v0.14.1
2.685 Submodule 'llm/llama.cpp/ggml' (https://github.com/ggerganov/llama.cpp.git) registered for path 'ggml'
2.686 Submodule 'llm/llama.cpp/gguf' (https://github.com/ggerganov/llama.cpp.git) registered for path 'gguf'
2.726 Cloning into '/go/src/github.com/jmorganca/ollama/llm/llama.cpp/ggml'...
4.131 fatal: remote error: upload-pack: not our ref 9e232f0234073358e7031c1b8d7aa45020469a3b
4.131 fatal: Fetched in submodule path 'ggml', but it did not contain 9e232f0234073358e7031c1b8d7aa45020469a3b. Direct fetching of that commit failed.
4.132 fatal:
4.133 llm/llama.cpp/generate_linux.go:5: running "git": exit status 128

Following the discussion in #495 I ran the following:
root@acb15d98c3de:/go/src/github.com/jmorganca/ollama# git submodule init
Submodule 'llm/llama.cpp/ggml' (https://github.com/ggerganov/llama.cpp.git) registered for path 'llm/llama.cpp/ggml'
Submodule 'llm/llama.cpp/gguf' (https://github.com/ggerganov/llama.cpp.git) registered for path 'llm/llama.cpp/gguf'
root@acb15d98c3de:/go/src/github.com/jmorganca/ollama# git submodule update --force
Cloning into '/go/src/github.com/jmorganca/ollama/llm/llama.cpp/ggml'...
Cloning into '/go/src/github.com/jmorganca/ollama/llm/llama.cpp/gguf'...
fatal: remote error: upload-pack: not our ref 9e232f0234073358e7031c1b8d7aa45020469a3b
fatal: Fetched in submodule path 'llm/llama.cpp/ggml', but it did not contain 9e232f0234073358e7031c1b8d7aa45020469a3b. Direct fetching of that commit failed.
fatal:

I'm assuming this commit is no longer available, though I'm not sure how to check. Any suggestions?

Oh bitten by the submodule recursive error.
For anyone who comes upon this in the future, The docker RUN that clones the github needs to have --recursive-submodules flag.
RUN gh repo clone jmorganca/ollama /go/src/github.com/jmorganca/ollama -- --recurse-submodules


[MG06] Error adding polygon

Context
Tried to add another polygon to a layer even tho it gets properly reflected on the map, it doesn't show on the table.
Steps to Reproduce

Add a polygon layer
Use the Add geometry feature to add another polygon to that layer
3.Take a look at the table

Current Result

Notice how there's not cartodb_id 4 on the table (or 3!)
Expected result
The added polygon should be properly reflected on the table.
Browser and version
Chrome Version 56.0.2924.87 (64-bit)
.carto file
Untitled map (on 2017-03-28 at 10.17.29).carto.zip
Additional info
Smoke test MG06

Same problem than https://github.com/CartoDB/cartodb/issues/11857. Already reported.


panic when listing exported crds with wildcard logical cluster (missing 'apis.kcp.dev/identity' annotation)

Describe the bug
After adding a crd to a workspace using an APIBinding, any immediate wildcard requests to list that resource type fail and cause a panic in kcp.
$ kubectl get --raw https://<IP_ADDRESS>:6443/clusters/*/apis/kuadrant.dev/v1/dnsrecords
Unable to connect to the server: stream error: stream ID 1; INTERNAL_ERROR

Server error:
E0512 09:18:23.659023 2574017 wrap.go:58] "apiserver panic'd" method="GET" URI="/clusters/%2A/apis/kuadrant.dev/v1/dnsrecords" audit-ID="fd3162b7-b580-4566-861e-ab4d10fdecd5"
http2: panic serving <IP_ADDRESS>:59260: missing 'apis.kcp.dev/identity' annotation
goroutine 51387 [running]:
k8s.io/apiserver/pkg/server/filters.(*timeoutHandler).ServeHTTP.func1.1()
	/home/mnairn/go/pkg/mod/github.com/kcp-dev/kubernetes/staging/src/k8s.io/apiserver@v0.0.0-20220502152525-1ac78681cb61/pkg/server/filters/timeout.go:105 +0xb0
panic({0x2b00b20, 0xc004417940})
	/home/mnairn/sdk/go1.17.7/src/runtime/panic.go:1038 +0x215
k8s.io/apiextensions-apiserver/pkg/registry/customresource.newREST({{_, _}, {_, _}}, {{0xc004309530, 0xc}, {0xc004309518, 0x2}, {0xc004309e90, 0x9}}, ...)
	/home/mnairn/go/pkg/mod/github.com/kcp-dev/kubernetes/staging/src/k8s.io/apiextensions-apiserver@v0.0.0-20220502152525-1ac78681cb61/pkg/registry/customresource/etcd.go:108 +0x73c
...

Making a request to a specific logical cluster will work:
$ kubectl get --raw https://<IP_ADDRESS>:6443/clusters/root:default:kcp-glbc/apis/kuadrant.dev/v1/dnsrecords
{"apiVersion":"kuadrant.dev/v1","items":[],"kind":"DNSRecordList","metadata":{"continue":"","resourceVersion":"344"}}

and subsequent wildcard requests from then on will now work:
kubectl get --raw https://<IP_ADDRESS>:6443/clusters/*/apis/kuadrant.dev/v1/dnsrecords
{"apiVersion":"kuadrant.dev/v1","items":[],"kind":"DNSRecordList","metadata":{"continue":"","resourceVersion":"355"}}

All wildcard requests fail until you make at least one request to a specific logical cluster.
To Reproduce
Steps to reproduce the behavior:

Start kcp
Create a workspace
Add an apiresourceschema and apiexport for some CRD(https://github.com/Kuadrant/kcp-glbc/tree/main/utils/kcp-contrib)
Create an APIBinding
Make a wildcard request to list the resources kubectl get --raw https://<IP_ADDRESS>:6443/clusters/*/apis/kuadrant.dev/v1/dnsrecords

Expected behavior
No panic.
Additional context
Only tested on release-0.4 and v0.4.0-alpha.0, i have not tried main yet.

This is certainly a bug and should result in some 40x or 50x error. Note that wildcards requests for APIBinding resource need an identity being passed. Compare https://github.com/kcp-dev/kcp/blob/main/test/e2e/apibinding/apibinding_test.go#L194 how this works. cc @ncdc

Will be fully fixed when the apiexport virtual workspace is in. Will look into this in the meantime.

Here is what's happening:

Try to do a wildcard list

It finds the CRD in system:bound-crds (it's from an APIExport/APIBinding)
But because it's a wildcard list request without identity (i.e. it's not /clusters/*/apis/kuadrant.dev/v1/dnsrecords:$identity), and we don't have the virtual workspace for APIExports implemented yet, we don't know which APIBinding this is for, so we don't know the identity (it could come via multiple APIExport identities)
panic

Do a list against a specific logical cluster

This is a non-wildcard request, so it is able to determine the identity, and when it creates the serving info for the CRD, it includes the identity annotation
All subsequent requests, including wildcards, reuse the same serving info, which has the identity


De-listed Maven Central versions

Description
Versions previously listed in Maven Central artifacts metadata (maven-metadata.xml) are no longer listed, breaking workflows that rely on automatically identifying available versions (with or without locking).
Examples:

spring-cloud-stream-dependencies

Available 3.1.* versions: 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5
3.1.* versions listed in maven-metadata.xml: 3.1.0, 3.1.1

spring-cloud-bus-dependencies

Available 3.0.* versions: 3.0.0, 3.0.1, 3.0.2, 3.0.3
3.0.* versions listed in maven-metadata.xml: 3.0.0, 3.0.1

Sample
build.gradle.kts
plugins {
    `java-library`
}

repositories {
    mavenCentral()
}

dependencies {
    implementation(platform("org.springframework.cloud:spring-cloud-stream-dependencies:[3.1.2,3.2)"))
    implementation("org.springframework.cloud:spring-cloud-starter-stream-kafka")
}

tasks {
    wrapper {
        gradleVersion = "7.3.1"
    }
}

gradle build output:
> Task :compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> Could not resolve all files for configuration ':compileClasspath'.
   > Could not find any version that matches org.springframework.cloud:spring-cloud-stream-dependencies:[3.1.2,3.2).
     Versions that do not match:
       - 3.2.1
       - 3.2.0
       - 3.1.1
       - 3.1.0
       - 3.0.3.RELEASE
       - + 41 more
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/org/springframework/cloud/spring-cloud-stream-dependencies/maven-metadata.xml
     Required by:
         project :
   > Could not find org.springframework.cloud:spring-cloud-starter-stream-kafka:.
     Required by:
         project :

Workaround: switch to statically defined version / manual version locking
References
https://docs.gradle.org/current/userguide/single_versions.html
https://maven.apache.org/pom.html#Dependency_Version_Requirement_Specification

Moving to spring-cloud-build as spring-cloud-release-tools is some automation for us, it doesn't have anything to do with maven besides just running ./mvnw.
I still don't know what the issue is or how we could fix it. I think that file is generated by nexus by sontatype where we deploy, not by anything we control.

From past experiences with maven-deploy-plugin with private repositories (also using Sonatype Nexus), the Maven plugin itself will first download maven-metadata.xml, in order to upload an updated version which includes the artifact being published (in addition to actually uploading the main artifact). In other words, the repository is initially not involved into generating the maven-metadata.xml content, unless specifically requested to (Nexus has "Maven metadata repair" feature).
Unfortunately, I have no experience with Maven Central publishing, so I don't know whether that knowledge applies to it.

At its core, the issue is:

spring-cloud-stream-dependencies 3.1.3 does exist (as seen here or here)
So it should be listed under maven-metadata.xml, but it is not

(I also observed similar situation with other Spring Cloud subprojects)

I still don't think there's anything we can do.

Should I request Maven Central to repair Spring Cloud artifacts metadata?
My concern is that:

I cannot claim ownership of the affected artifacts
I will not be able entertain their reply if they challenge me about how those artifacts were published, as I don't know the intrinsic of Spring Cloud releasing (which credentials, which tool, which plugins, which version, what configuration, what changed, logs of the previous publications/uploads, etc.)

We can make the request


User Profile

I read that there are user profiles in the premium templates.
Is there any possibility to get a user profile template for AdminLTE aswell? I would even pay for it (as a plugin maybe)?

There is a plan to implement a user profile page. I am not sure when I will have the time for this feature but it will probably be available with AdminLTE 2.3.0.

Okay, cool. Thanks for replying.

:+1:

:+1:

This issue was solved in v2.3.0 81aa879d3a4489213888e24975b073c7478f0447


Undefined symbols for architecture x86_64

MAC OS, I first use this tool but encountered a problem.

brew install gflags
test.cpp
1 #include
2 #include <gflags/gflags.h>
3
4 using namespace std;
5
6 DEFINE_int64(deu, 64, "test");
7 int main() {
8     cout << FLAGS_deu << endl;
9     return 0;
11 }
g++ test.cpp -o test

the error log:
Undefined symbols for architecture x86_64:
"google::FlagRegisterer::FlagRegisterer(char const*, char const*, char const*, long long*, long long*)", referenced from:
___cxx_global_var_init in gflags_prac-571fbd.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Thank you!

I meet the same problem, did anyone find a solution?


[BUG] Link for graduation criteria is broken

Link for graduation creteria is broken in https://github.com/kubernetes-sigs/network-policy-api/blob/main/site-src/enhancements.md

What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:

/kind documentation

/assign


How To Convert Date

Hi,
I just want convert date field in my db. Like php I wonder that How can I convert this "2018-11-27 16:16:49" to "11.27.2018"
Thanks

Hey @senocak! 👋
Please, use the forum or our Discord Server to ask this kind of question.
Also, ensure to read the documentation of Lucid on same to see if that answer your question.
https://adonisjs.com/docs/4.1/lucid#_dates


Thordan Unreal

Current progress is right before Meteors.
I'm not sure how to properly add the repeating casts to the Adelphel&Janlenoux part, or if its even necessary beyond the mitigation hint.

I'm planning to implement new unreal/extreme asap - was on vacation for the last two weeks - so I'll merge this PR and work from it. Thanks!


Update "AlwaysSnapToGrid" to work with groups.

When https://github.com/comfyanonymous/ComfyUI/pull/3393 is applied, this would be required for always snapping groups as well.

Yes please!

This is a great improvement.
But this aligns the group's top border, while [ Fit Group to Nodes ] aligns the bottom border, so the relative positions of the group and it's nodes also changes, after moving the group.
Could it be possible to do this final tweak, to fix it:
https://github.com/pythongosssss/ComfyUI-Custom-Scripts/issues/261


Implement strprintf::fmt as a Rust macro

The title says most of it. Reviewers are advised to start by reading the large comment at the beginning of lib.rs, and looking through the docs in the other two modules. That'll give you the overview of goals and the design. I rewrote the history to make it appear like I came up with all the ideas first, and then just implemented them methodically.
Closes #447.

Coverage remained the same at 39.829% when pulling e5ff4f4c9c8c4ba871c29e0ca32bfe46f4ce0574 on feature/rust-strprintf into a8972c6d7e6cdb500861d5bc058c62732387553c on master.

Okay, I replaced CString with Vec. It was much easier than I expected! @kpcyrd, please take a look, and then I can finally merge this.

looks good to me :)

Thank you very much for the review, @kpcyrd!
I've got some feedback about this over on lobste.rs, so I'm going to make another PR soon applying some of the suggestions and bringing this even closer to the C++ version.


Expiration hyper links in docs.

Describe the bug
Hi,  following basic-configuration.md in intro, there is a 404 ChartAPI link on bottom.
The reason is the link (https://github.com/project-nv/night-vision/blob/main/guide/api/chart-api) is outdate, for now (2022.12.22) it should be ChartAPI
Maybe author forgot to update hyper links after path changed?
Reproduction
https://github.com/project-nv/night-vision/blob/main/guide/api/chart-api
Steps to reproduce
At the end of page  basic-configuration.md, click the ChartAPI.
Javascript Framework
no-framework (vanilla-js)
Logs
No code there.
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a NightVision issue and not a framework-specific issue.
[X] The provided reproduction is a minimal reproducible example of the bug.

Interesting, this work on the site https://nightvision.dev/guide/intro/basic-configuration.html
(which I'm recommending, bc we have a great search bar now)

Interesting, it works on the site https://nightvision.dev/guide/intro/basic-configuration.html (which I'm recommending, bc we have a great search bar now)

Thanks, I just know that!


Reschedule service if instance deploy_rev does not match

@jnummelin @nevalla ping

Looks good

Let's close this one, with stacks we need to change the logic anyway.


python310Packages.pynuki: 1.6.0 -> 1.6.1

Diff: https://github.com/pschmitt/pynuki/compare/1.6.0...1.6.1
Description of changes

Things done

Built on platform(s)

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

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

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

[ ] 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/)
23.05 Release Notes (or backporting 22.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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 219036 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.nuki
python310Packages.pynuki
python311Packages.pynuki


CouchbaseLiteException: getViewID() < 0, Status: 404 (HTTP 404 not_found)

Reported by @kombadzomba
https://github.com/couchbase/couchbase-lite-java-core/issues/1312#issuecomment-263731998
We have published an app update these days with CBL 1.3.1-90 and we have received for the first time errors like this:
Android OS: 6.0.1
AbstractView( 6667): Error querying view reminder_by_status_view.
Caused by: com.couchbase.lite.CouchbaseLiteException: getViewID() < 0, Status: 404 (HTTP 404 not_found)
at com.couchbase.lite.store.SQLiteViewStore.updateIndexes(SQLiteViewStore.java:250)
at com.couchbase.lite.View.updateIndexes(View.java:321)
at com.couchbase.lite.View.updateIndex(View.java:294)
at com.couchbase.lite.Database.queryViewNamed(Database.java:2442)
at com.couchbase.lite.Query.run(Query.java:446)
at net.dzomba.termin3.model.couchdb.dbviews.AbstractView.refresh(AbstractView.java:60)
... 24 more

The views that are mentioned in these errors are the one that did not exist before in the previous versions of our app and users that we get these errors from have already used the app, i.e. they have updated the app.
I've seen the milestone 1.3.1 for this issue. Am I using the wrong CBL version or there may be something else going on?
Thanks!

Hi @hideki,
I was wondering if this issue may be the cause of #985 SQLiteDatabaseCorruptException. I am suggesting this since we got the SQLiteDatabaseCorruptException from the same user one hour after the  getViewID() < 0 error.
Thanks.

Hi @kombadzomba,
It is interesting. When getViewID() < 0 error occurs, the database corruption could be occurred. Is it possible to capture logcat from the user's device?
Thanks!

Hi @hideki,
Here is the logcat. Last 100 lines is all we have.
Thanks!


Add logo and GitHub avatar logo

Should address and close #48.

I am adding it to the README as well.


Contact Us Section

@akshitagupta15june ,I would like to change the UI of contact us section Because it is not looking good. Please Assign this issue to me

Please assign this project to me. I will fix the issue.

please assign this task to me under GSSOC'23


RAVCOM-444_Upgrade_Core_Module_Sql_Package

This PR is only for the dialect sub-package.

Changes look good to me, so merging it.


ThreedDS2Utils is not defined

Magento version: <IP_ADDRESS>
Plugin version: 2.16.0
Description: the module seems to be not compatible with multishipping
steps to reproduce :

add a product to cart
view shopping cart
click on "checkout with multiple addresses"
continue to billing information
on the checkout/multishipping/billing/ page, console displays the fllowing javascript error message : "ReferenceError: ThreedDS2Utils is not defined"

Hi @royarthur-dev
I created a pull request referencing this issue,
can you please check if it solves the issue?
Thanks,
Alessio
Adyen


Skip file when no new lines added and lines-changed-only is asserted

I think the current change can stop adding --line-filter arg in clang-tidy when lines is empty.
But to skip adding annotation for such situation (only delete code), I guess need to change func range_of_changed_lines to get an empty list, but I am not sure how to change it. @2bndy5 could you help when you have time?
https://github.com/cpp-linter/cpp-linter/blob/f53976ac55b114584dab3bf2a49a3da12075fc25/cpp_linter/run.py#L890
I used this test job to reproduce #18

Codecov Report

Merging #21 (43f7fe9) into main (f53976a) will decrease coverage by 0.12%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main      #21      +/-   ##
==========================================
- Coverage   80.68%   80.55%   -0.13%
==========================================
  Files           6        6
  Lines         647      648       +1
==========================================
  Hits          522      522
- Misses        125      126       +1

Impacted Files
Coverage Δ

cpp_linter/run.py
78.93% <50.00%> (-0.23%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

The solution for this is going to need more than just a few lines changed. I'll start hacking it...

This branch is now overwritten by my changes to properly address #21. Coverage report seems to have suffered (for some unforeseen reason), but most of thread_comments.py is not actually used in production.

The unit tests agree with you. If released, this would be a patch version bump. I'm ready when you are.

FYI, I added your p_enemy.c file to the unit test for precision.

So I need to keep p_enemy.c file always in the test-repo? at least I need to keep test-repo always existing, I think I will not delete it.

You shouldn't need to since the file's "added" state is specific to the commit that was pushed to the remote. I don't think GitHub deletes orphaned branches/commits.

We could always change the file to a new file in this repo's demo src. Ironically, the name p_enemy.c is also used in chocolate-doom (which we also use in the unit test), but there's no conflict because chocolate-doom's file is located in src/hexen/p_enemy.c (your file is in the supposed repo-root).


Problems compiling the manual in latex

Dear Sergio,
I tried to compile the manual using the script "compile" and derived scripts adapted to my system (including Pygments library in my python interpreter, etc.), but I couldn't get it. Could you include the manual in pdf format, please?
I appreciate any help you can provide.
jose luis

Sorry,
The repo was growing quickly with every change in the pdf, so I kept it out...
There's still a lot of work to do on the documentation, but in the meantime you can use the one I'm attaching.
manual.pdf

Sorry,
The repo was growing quickly with every change in the pdf, so I kept it out...
There's still a lot of work to do on the documentation, but in the meantime you can use the one I'm attaching.
manual.pdf

Hi!
I've updated the examples for the oxy-cope reaction in water.
manual.pdf

Hi!
I've updated the examples for the oxy-cope reaction in water.
manual.pdf

Hi Sergio!
Thank you for your help

Hi Sergio!
Thank you for your help

manual.pdf


Added optional allowedCards value to Zibal driver.

Description
Added optional allowedCards value to the $data array in Zibal driver.
Motivation and context
This addition allows users to send optional allowed bank cards for their zibal payment.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My pull request addresses exactly one patch/feature.
[x] I have created a branch for this patch/feature.
[x] Each individual commit in the pull request is meaningful.
[ ] I have added tests to cover my changes.
[ ] If my change requires a change to the documentation, I have updated it accordingly.

does it work correctly? have you test it?

does it work correctly? have you test it?

thanks for your contribution.

thanks for your contribution.


Issues with PSAvoidUsingWriteHost

The message guides folks to use Write-Output but Write-Output has no equivalent of -BackgroundColor/-ForegroundColor/-NoNewLine.  Perhaps this rule shouldn't fire when any of these parameters are present?  However when it does fire, shouldn't it be pointing folks to use Write-Information instead - at least when they are on PowerShell V5?
I have helped quite a few folks with PowerShell functions where they were using Write-Output (implicitly) in their function to notify users of what's going on in the function.  Then they were confused by the fact that their function returned a collection instead of the single value they intended.  They're usually even more surprised because they used "return $result" and expected that to be the only return value.
Telling a script analyzer user to use Write-Output instead of Write-Host, significantly changes semantics in a way that could break their script.  Seems like this tool should obey that tenant of the Hippocratic oath - do no harm.  :-)

I we all agreed that Write-Host doesn't kill kittens after all ;-)

The original purpose of this rule was to enable scripts to be used in an automated environment. Write-Host emits to the display and will interfere when used during a pipeline scenario.
Using Write-Host is ok when only UX is involved - in this case suppress the rule application using -ExcludeRule parameter/SuppressRule attribute/Profile
Write-Verbose would be a good candidate if Write-Output is confusing users with pipeline data.
Maybe we need to reword the warning to include usage of Write-Verbose, if the intent is to convey information to the user?

Write-Verbose would be a good candidate if Write-Output is confusing users with pipeline data.
You might also mention that Write-Information is the most direct replacement but that it is only available on PowerShell v5.

No, @rkeithhill -- Write-Information is not a replacement for Write-Host -- EVER?
It doesn't have any output anywhere.

It's exists to provide a justification for _how_ they re-engineered Write-Host, and so that third-party hosts can _hypothetically_ implement cool things -- but since they prevent Write-Information from setting the tags that Write-Hosts sets, you cannot ever use Write-Information to replace Write-Host.

In fact, as far as I have seen, there still isn't a (documented) way for third-party hosts to distinguish Write-Host output from other console text output (Out-Default), unless they completely replace the formatting sub-system starting with Out-Default.

The bottom line here is that Write-Host is THE ONLY way to provide anything other than a blue-and-white text for user interface. If you want to highlight something, colorize output, etc., it is not only THE ONLY WAY -- it is THE RECOMMENDED WAY!!
Warning scripters to stop using it is just ridiculous.
TEACHING NEWBIES the difference between Write-Output and Write-Verbose and Write-Host is not the purpose of a linting tool.

We will discuss further in the meeting today, but I'd still like to capture my baseline thoughts:
Write-Host can be okay to use, but only in specific instances where are you very deliberately trying to build a UI of some kind, and can have a reasonable expectation of the host in which PowerShell is executing. For instance, PSReadline employs colored syntax highlighting as a feature of the module, but it can do some wonky stuff in the ISE (which is why we didn't enable it by default there in Windows 10). In these cases, global rule suppression makes the most sense, but it's still an edge case.
Generally speaking, scripts and modules should cater to a non-interactive context by default. (Obviously, there are some exceptions to this that use $ConfirmPreference = High, but we have -Force as a trapdoor to script writers.) We've built a set of functionality for capturing different kinds of outputs to appropriate places (e.g. Write-Progress is for long-running tasks without clogging up the pipeline, Write-Error will populate the error records, Write-Verbose only shows up when the user asks for it, etc., or you should be emitting a structured object to the pipeline) Therefore, the guidance that Write-Host should always be replaced by Write-Output is wrong because there's more nuance than that. It's not just that Write-Host shouldn't be used, but that string output should be used in different ways depending on the scenario.
I'm not exactly sure how to tackle that through our existing rules, but we should talk about it today.

The guidance was updated in the rule output:
https://github.com/PowerShell/PSScriptAnalyzer/pull/349

Here is the current wording after installing the module from the gallery:
File 'Test.ps1' uses Write-Host. Avoid using Write-Host because it might not work in all hosts, does not work when there is no host, and (prior to PS 5.0) cannot be suppressed, captured, or redirected. Instead, use Write-Output, Write-Verbose, or Write-Information.

If we run Write-Information -? in powershell 5 we will see:
Starting in Windows PowerShell 5.0, Write-Host is a wrapper for Write-Information . You can now use Write-Host to emit output to the information stream, but the $InformationPreference preference variable and InformationAction common parameter do not affect Write-Host messages

The message has  a couple of problems. First it states that "Write-Host because it might not work in all hosts" and that one should use instead Write-Information. This sounds wrong, since Write-Host is a wrapper around  Write-Information.
does not work when there is no host is dubious either for similar reasons.
Finally, if my script has #Requires -Version 5 the Analyzer may safely conclude that I do not interested in the warning at all, since it's not applicable to this version of Powershell.
@rkeithhill @Jaykul Do you think the wording needs to be re-considered again?


Bridge

Hello!
This is the implementation of #1117. It is not ready to be merged yet - I need to change all binvecs in bridge(use_double_dummy_result=false).txt to reflect the change of the order of the tricks (from [previous, current] to [current, previous]). As suggested by @elkhrt, I didn't introduce absolute_order parameter.
If this approach is fine with you, I'll update the tests and the PR will be ready to be merged.

Fixed the tests. Since I swap the current and the previous tricks, I needed to swap those in the binary representations.
Here's the script that takes bridge(use_double_dummy_result=false).txt and modifies hex values for state observations only for the playing phase (hence condition idx > 700). I used this script to patch the tests.
def change_order(hex_value):
    int_value = int(hex_value, 16)  # Convert the hex string to an integer
    binary_str = bin(int_value)[2:]  # Convert the integer to binary and remove the '0b' prefix
    length_required = 571
    binary_str_padded = binary_str.zfill(length_required)
    index_previous_start, index_previous_end = 129, 337
    index_current_start, index_current_end = 337, 545
    new_string_binary = binary_str_padded[:index_previous_start] + binary_str_padded[index_current_start:index_current_end] + binary_str_padded[index_previous_start: index_previous_end] + binary_str_padded[index_current_end:]
    int_value_from_binary = int(new_string_binary, 2)
    hex_str = hex(int_value_from_binary)
    return hex_str

file_path = "./bridge(use_double_dummy_result=false).txt"

with open(file_path, 'r') as file:
    lines = file.readlines()

for idx, line in enumerate(lines):
	# only apply to lines after bidding
    if "binvec" in line and idx > 700:
        hex_value = line.split(', ')[-1].split(')')[0]  # Extract the hex value
        new_hex_value = change_order(hex_value)
        lines[idx] = line.replace(hex_value, new_hex_value)  # Replace old hex value with the new one

with open(file_path, 'w') as file:
    file.writelines(lines)

Taken @MattX's review into account

Thanks for this and to @MattX for the review.
We should be able to pull this in soon. I'll just quickly run it by Ed early next week.

BTW @ZiggerZZ, you can always simply regenerate those playthroughs given the new implementation using this script: https://github.com/google-deepmind/open_spiel/blob/master/open_spiel/scripts/regenerate_playthroughs.sh

Thanks @lanctot! I wanted to verify the correctness of the implementation by writing that logic of modifying the existing observation tensors.


@enum TimeDataType and FreqDataType names are confusing

I think there is potential for a number of renamings:
strain_only -> could be something like strain_time as it includes strain and time.
stress_only -> could be something like stress_time as it includes strain and time.
strain_and_stress -> could be something like full as it includes all data fields.
frec_only -> should probably be freq_only, the c looks like a mispelling?
Note that I don't mind what they are changed to, but just wanted to point out which ones are confusing and why.

Happy with clarifying this, I see your point.
But maybe we can talk about it together later on. I'd prefer calling them
"time", "strain", "stress" and "stress_strain", but these keywords may be
also used for other things.
frec_only is a typo indeed! embarrassing...
On Sun, 21 Jul 2019 at 16:58, Louis Kaplan<EMAIL_ADDRESS>wrote:

I think there is potential for a number of renamings:
strain_only -> could be something like strain_time as it includes strain
and time.
stress_only -> could be something like stress_time as it includes strain
and time.
strain_and_stress -> could be something like full as it includes all data
fields.
frec_only -> should probably be freq_only, the c looks like a mispelling?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/JuliaRheology/RHEOS.jl/issues/22?email_source=notifications&email_token=AA6B24SVU3HTTIQYDE64GRDQASBT3A5CNFSM4IFSYME2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HAPZI4Q,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6B24WQW6HT7SZATRL36RLQASBT3ANCNFSM4IFSYMEQ
.

Sure happy to discuss the time data types further.
I amended the frequency data type so this issue is partially concluded, see commit e95d27159bf7f611cbf328fc62e1fb0e6871cb8e

I have been playing with ideas in my head for a while now and I can't settle on anything that I think is clearer. (I agree, using time stress and stress_strain would be clear but probably not a good use of the namespace.)
Closing for now.


ARPNET is not making sense

this is no a issue

Currently i do not have time but the solution is probablt in Node.cs in the planet clipping.

I think the problem is that you remove the satellites, but the reference is still there

@dani0105 i have not removed any sats from  the above image but thay are just in different places on their orbit.


Inconsistency with the existential operator

Quicky shown in one code:
if varname? then
varname2 = "hi"
if varname2? then
delete varname2
if varname2? then

Compiles to
var varname2;

if (typeof varname !== "undefined" && varname !== null) {}

varname2 = "hi";

if (varname2 != null) {}

delete varname2;

if (varname2 != null) {}

The last one doesn't check for undefined, even though the variable was deleted. I think it's bad for CoffeeScript to decide to not check for undefined based on how the script was during compiling.

Luckily enough it's not a problem in JS where you cannot delete vars!
Have a look at @kangax http://perfectionkills.com/understanding-delete/ awesome article.

Thanks to #2021, that syntax won't even be allowed anyway. But yeah, as @yuchi says, delete won't remove anything from scope that was added in a variable declaration, as all variables (known to the scope check) in coffeescript are. Not a bug.


What does this error mean

Describe your problem here.

I get this a lot while making scripts, and i still dont know what it means
please help
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

💀


Probe label

Pull Request Test Coverage Report for Build 888663020

42 of 174 (24.14%)  changed or added relevant lines in 15 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.9%) to 60.114%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/Babylonian-UI.package/BPProbeMorph.class/instance/updateFrom..st
0
1
0.0%

packages/Babylonian-UI.package/BPStyler.class/instance/unstyledTextFrom..st
0
1
0.0%

packages/Babylonian-UI.package/BPProbeMorph.class/instance/setLabelButtonClicked.st
0
6
0.0%

packages/Babylonian-UI.package/BPProbeMorph.class/instance/updateExpressionMorphIfNecessary.st
0
19
0.0%

packages/Babylonian-UI.package/BPProbeMorph.class/instance/newAddLabelMorph.st
0
20
0.0%

packages/Babylonian-UI.package/BPProbeMorph.class/instance/defaultLabel.st
0
23
0.0%

packages/Babylonian-UI.package/BPProbeMorph.class/instance/newLabelMorph.st
0
31
0.0%

packages/Babylonian-UI.package/BPProbeMorph.class/instance/updateLabelMorphIfNecessary.st
0
31
0.0%

Totals

Change from base Build 882191095:
-0.9%

Covered Lines:
4312

Relevant Lines:
7173

💛  - Coveralls


Update MD file on new branch 2017-20-10_07-11-54

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Mapping array of Mappable Objects

I have a JSON array like this:
[ {     "id" : 1,     "field" : "somevalue" }, {     "id" : 2,     "field" : "somevalue" } ]
I find no way to map it to an array of mappable objects, when I try
let result = Mapper<[MyObject]>().map(json)
I get the following error: Type Array does not conform protocol Mappable

Nevermind I just find out you have a mapArray function, my bad :)

@fcruzsbtv  what is your function to map it to an array of mappable objects?


Failure compiling PyTorch ResNet50 on x86_64

What happened?
Error when compiling PyTorch ResNet50 on x86_64:
iree-compile --output-format=vm-bytecode --iree-hal-target-backends=llvm-cpu --iree-input-type=none --iree-llvmcpu-target-triple=x86_64-unknown-linux-gnu --iree-llvmcpu-target-cpu=cascadelake Resnet50PTBatch1.mlir -o module.vmfb

2023-05-12T01:53:39.8457500Z iree-compile: /work/third_party/llvm-project/llvm/include/llvm/ADT/SmallVector.h:294: llvm::SmallVectorTemplateCommon::reference llvm::SmallVectorTemplateCommon<long, void>::operator[](llvm::SmallVectorTemplateCommon::size_type) [T = long]: Assertion `idx < size()' failed.

Full error: Resnet50PTBatch1_error.txt
Steps to reproduce your issue

Download https://storage.googleapis.com/iree-model-artifacts/pytorch/torch_models_20230401.795_1680469670/RESNET50/batch_1/linalg.mlir

Compile:

iree-compile --output-format=vm-bytecode \
    --iree-hal-target-backends=llvm-cpu --iree-input-type=none \
    --iree-llvmcpu-target-triple=x86_64-unknown-linux-gnu \
    --iree-llvmcpu-target-cpu=cascadelake linalg.mlir -o module.vmfb

What component(s) does this issue relate to?
Compiler
Version information
e85a7c82792fcb4083154879e206cf765a74d7e6
Additional context
No response

once it is fixed should we add this to pre-submit ?

@MaheshRavishankar Bumping this up since it is P0. Can you take a look?

yeah, next on my list....

Looked into this a bit. Here is a small repro of the error
hal.executable private @repro {
  hal.executable.variant public @embedded_elf_x86_64, target = <"llvm-cpu", "embedded-elf-x86_64", {cpu = "cascadelake", cpu_features = "+mmx,+popcnt,+sse,+sse2,+sse3,+ssse3,+sse4.1,+sse4.2,+avx,+avx2,+fma,+avx512f,+bmi,+bmi2,+aes,+pclmul,+avx512vl,+avx512bw,+avx512dq,+avx512cd,+avx512vnni,+adx,+clflushop\
t,+clwb,+cx16,+cx8,+crc32,+f16c,+fsgsbase,+fxsr,+invpcid,+lzcnt,+movbe,+pku,+prfchw,+rdrnd,+rdseed,+sahf,+x87,+xsave,+xsavec,+xsaveopt,+xsaves", data_layout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128", native_vector_size = 32 : index, target_triple = "x86_64-unknown-unknown-\
eabi-elf", ukernels = false}> {
    hal.executable.export public @forward_dispatch_3_pooling_nchw_max_1x64x56x56x3x3_f32 ordinal(0) layout(#hal.pipeline.layout<push_constants = 0, sets = [<0, bindings = [<0, storage_buffer, ReadOnly>, <1, storage_buffer>]>]>) {
    ^bb0(%arg0: !hal.device):
      %x, %y, %z = flow.dispatch.workgroup_count_from_slice
      hal.return %x, %y, %z : index, index, index
    }
    builtin.module {
      func.func @forward_dispatch_3_pooling_nchw_max_1x64x56x56x3x3_f32() {
        %c3846080 = arith.constant 3846080 : index
        %c0 = arith.constant 0 : index
        %cst = arith.constant -3.40282347E+38 : f32
        %0 = hal.interface.binding.subspan set(0) binding(0) type(storage_buffer) alignment(64) offset(%c3846080) flags(ReadOnly) : !flow.dispatch.tensor<readonly:tensor<1x64x114x114xf32>>
        %1 = hal.interface.binding.subspan set(0) binding(1) type(storage_buffer) alignment(64) offset(%c0) : !flow.dispatch.tensor<writeonly:tensor<1x64x56x56xf32>>
        %2 = flow.dispatch.tensor.load %0, offsets = [0, 0, 0, 0], sizes = [1, 64, 114, 114], strides = [1, 1, 1, 1] : !flow.dispatch.tensor<readonly:tensor<1x64x114x114xf32>> -> tensor<1x64x114x114xf32>
        %3 = tensor.empty() : tensor<1x64x56x56xf32>
        %4 = tensor.empty() : tensor<3x3xf32>
        %5 = linalg.fill ins(%cst : f32) outs(%3 : tensor<1x64x56x56xf32>) -> tensor<1x64x56x56xf32>
        %6 = linalg.pooling_nchw_max {dilations = dense<1> : vector<2xi64>, strides = dense<2> : vector<2xi64>} ins(%2, %4 : tensor<1x64x114x114xf32>, tensor<3x3xf32>) outs(%5 : tensor<1x64x56x56xf32>) -> tensor<1x64x56x56xf32>
        flow.dispatch.tensor.store %6, %1, offsets = [0, 0, 0, 0], sizes = [1, 64, 56, 56], strides = [1, 1, 1, 1] : tensor<1x64x56x56xf32> -> !flow.dispatch.tensor<writeonly:tensor<1x64x56x56xf32>>
        return
      }
    }
  }
}

and command
iree-opt --pass-pipeline="builtin.module(hal.executable(hal.executable.variant(iree-llvmcpu-lower-executable-target)))" repro.mlir

I get the following stack trace
0.      Program arguments: /usr/local/google/home/ravishankarm/iree/build/Debug/tools/iree-opt --pass-pipeline=builtin.module(hal.executable(hal.executable.variant(iree-llvmcpu-lower-executable-target))) repro.mlir
 #0 0x00007f560a15ad8d llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) /usr/local/google/home/ravishankarm/iree/iree/third_party/llvm-project/llvm/lib/Support/Unix/Signals.inc:602:11
 #1 0x00007f560a15b20b PrintStackTraceSignalHandler(void*) /usr/local/google/home/ravishankarm/iree/iree/third_party/llvm-project/llvm/lib/Support/Unix/Signals.inc:675:1
 #2 0x00007f560a1594a6 llvm::sys::RunSignalHandlers() /usr/local/google/home/ravishankarm/iree/iree/third_party/llvm-project/llvm/lib/Support/Signals.cpp:104:5
 #3 0x00007f560a15ba25 SignalHandler(int) /usr/local/google/home/ravishankarm/iree/iree/third_party/llvm-project/llvm/lib/Support/Unix/Signals.inc:413:1
 #4 0x00007f55f7a5af90 (/lib/x86_64-linux-gnu/libc.so.6+0x3bf90)
 #5 0x00007f55f7aa9ccc __pthread_kill_implementation ./nptl/./nptl/pthread_kill.c:44:76
 #6 0x00007f55f7a5aef2 raise ./signal/../sysdeps/posix/raise.c:27:6
 #7 0x00007f55f7a45472 abort ./stdlib/./stdlib/abort.c:81:7
 #8 0x00007f55f7a45395 _nl_load_domain ./intl/./intl/loadmsgcat.c:1177:9
 #9 0x00007f55f7a53df2 (/lib/x86_64-linux-gnu/libc.so.6+0x34df2)
#10 0x00007f55fed9e3e9 llvm::SmallVectorTemplateCommon<long, void>::operator[](unsigned long) /usr/local/google/home/ravishankarm/iree/iree/third_party/llvm-project/llvm/include/llvm/ADT/SmallVector.h:0:5
#11 0x00007f5600cb930d mlir::iree_compiler::setConvRootConfig(mlir::func::FuncOp, mlir::linalg::LinalgOp, llvm::ArrayRef<long>, long) /usr/local/google/home/ravishankarm/iree/iree/compiler/src/iree/compiler/Codegen/LLVMCPU/KernelDispatch.cpp:1613:21
#12 0x00007f5600cbb74f mlir::iree_compiler::setConvNchwRootConfigImpl(mlir::func::FuncOp, mlir::linalg::LinalgOp) /usr/local/google/home/ravishankarm/iree/iree/compiler/src/iree/compiler/Codegen/LLVMCPU/KernelDispatch.cpp:1752:10
#13 0x00007f5600cbc0ce mlir::iree_compiler::setRootConfig(mlir::func::FuncOp, mlir::linalg::PoolingNchwMaxOp) /usr/local/google/home/ravishankarm/iree/iree/compiler/src/iree/compiler/Codegen/LLVMCPU/KernelDispatch.cpp:1767:10

So this is a pooling_nchw_max op that is using the same config as Conv. But the pooling op has 6 loops, and conv has 7 loops.
So here https://github.com/openxla/iree/blob/0d9f457f48dde7d6689bdba251fa682a0f587310/compiler/src/iree/compiler/Codegen/LLVMCPU/KernelDispatch.cpp#L1610 the targetTileSizes is of size 7, while the numLoops, and as a result flowTileSizes, is of size 6.  The loop two lines below goes from [0-7) and segfaults while accessing flowTileSizes.
Looking at the caller of this method https://github.com/openxla/iree/blob/0d9f457f48dde7d6689bdba251fa682a0f587310/compiler/src/iree/compiler/Codegen/LLVMCPU/KernelDispatch.cpp#L1751 I dont quite follow the targetTileSizes. If I understand correctly, this is an nchw op, so the loops for the conv would be
Batch, OutputFilter, OutputHeight, OutputWidth, InputChannel, FilterHeight, FilterWidth

so setting targetTileSizes = {1, vectorSize * 2, 1, 8, 8, 1, 1} is setting the filter for the output at vectorSize * 2, when it isnt the fastest varying dimension.
In any case for the pooling op, the loops are (https://github.com/llvm/llvm-project/blob/7bbe512362edd1dbd3947ff71212f3ae815a0836/mlir/python/mlir/dialects/linalg/opdsl/ops/core_named_ops.py#L933)
Batch, Filter, OutputHeight, OutputWidth, FilterHeight, FilterWidth

The fix here is to drop one of the entries in targetTileSizes, but I dont know which one.
@hanhanW should be a simple fix, but I think I need your input on this.

cc @vmurali since you probably know some details as well.

Sorry that I was distracted, looking now..


Polygons should only close when completed

Expected behaviour
The polygon tool should only close when the worker clicks on the initial marking, completing the loop.
Current behaviour
Closing a polygon can be done by clicking on the starting point or the most recent marking, leading to accidental polygon closure for high-resolution polygons.

Side effects:

This will affect behaviour for all projects using this polygon tool - we'll have to revert this change if we want things to go back
It'll be possible to submit unclosed polygons

Is it not already possible to submit unclosed polygons?

I can't remember if it closes them automagically. Probably not, come to think of it

IT TOTALLY DOES

Is that desired behaviour? Should we allow the submission of unclosed polygons?

If you have an open polygon and click "Done", it gets closed

On reflection, changing this wouldn't have affected that either way, derp


Switch Play 2.4 example to use Play-Slick

The example Play 2.4 project now uses the recommended Play-Slick integration library.
Changes

Scala bumped from 2.11.6 to 2.11.7
README → README.md
dbConfig is now used to provide db and also the driver's api which makes code independent of H2
Play-Slick's SlickComponents is used in place of DBComponents and HikariCPComponents which provides SlickApi which internally builds its own HikariCP pool
Changed getAll to fetchAll because it confuses IntelliJ into thinking it's an accessor method
A few typo fixes

Closes #89

Thanks! The failing build is due to env variables not being visible to PRs, I'll fix that

Ah, righto. Cheers!


Don't require schema as parameter to the database constructor

The schema is only used in the create_database method and the various migration methods. It could be passed as a parameter to these methods instead of to the database constructor.
The downside is that it would not be possible to change the schema to not use the hard-coded id, created_at and last_updated_at columns. This effectively means isqlite would not be usable for most existing SQLite databases, which is a rather significant drawback.

Another possibility is adding auto_created_at and auto_last_updated_at parameters to the database constructor and create and update methods.
The only places where the id column is treated specially are when an integer is passed instead of a query and the query is written as q.Equals("id", pk). This could also be handled by a constructor-level auto_id column.


[5.7] SIL Optimizer: add the OptimizeHopToExecutor in the late pipeline.

This is important to remove redundant hop_to_executor instructions after inlining.
rdar://95796233
This is a cherry-pick of https://github.com/apple/swift/pull/60153

@swift-ci test

It would be really helpful for future reference to add information to the top of each pass about pipeline dependencies and intentions for future pipeline reshuffling. The strategy for running OptimizeHopToExecutor followed by LowerHopToActor isn't clear. Presumably these passes have a dependency. But is there a potential benefit of lowering to actors earlier? Will we always want to lower actors after the last round of inlining? What sort of optimizations are useful after lowering actors?

@atrick The LowerHopToActor pass runs inside the IRGen preparation pipeline. So the dependencies with non-lowering passes should be pretty clear. If it makes sense to run this pass in the regular optimization pipeline is a different question, but not related to this change.

@tkremenek The change in the test is just a fix of the test, but does not test this change.
For correctness testing we have existing tests for the OptimizeHopToExecutor pass. Also, the correctness is tested by running the test suite with optimizations (that's done in the linux PR testing).
The other thing is: a test which checks that we see the expected result of adding the optimization pass. It's a bit hard to do this as a lit test. The best test for this would be a benchmark for AsyncBufferedByteIterator (unfortunately we don't have the infrastructure for async benchmarks yet).


Interface::getVersionIntegers doesn't return the full version

Hi,
I noticed that in the latest MaterialX version, a new version of the standard surface was introduced. It's labeled as version "1.0.1" and the previous one is "1.0.0".
Unfortunately the Interface::getVersionIntegers helper only returns the first 2 numbers, which makes it a bit awkward to use :)
Not a very big issue, but it would be nice if that method would return the 3 numbers, like the getVersionIntegers found in the MaterialXCore/Utils.h header.
Regards,
Damien.

Hi Damien,
This is most likely due to assumed "usage". This utility is used to get the MaterialX document version of which the patch version in a major.minor.patch string only returns the major and minor versions. The version on a definition (nodedef) can be anything so this utility "fails" to parse the last digit. (Both nodedef and document are derived from interface).
@jstone-lucasfilm , what do you think about this? Should a document have a specific derived class version which limits parsing to major.minor and the default one on interface does as many as it can find. The caveat is of course that version is a string and I believe it's only a suggestion as to the format to use.
Another way to handle this is that I've written utilities to accept a "template" and basicaly based on the template the utility attempts to extract out the digits. e.g. if a version can use this template: `my_version.#.#" would parse out 2 digits.
Of course don't want to over-complicate things but want to keep the versioning and upgrade logic "safe".
Thoughts?

Hi,
The helper doesn't need to cover all usages, far from me to suggest that! (I'm generally more a "the simpler the better" person) No need to make an overly complicated version parser to handle all cases, it's just a matter of making the utility at least match the usage in the official libraries: since the version string is provided anyway, anyone can still write his own "version parser". Which I did. But it just felt wrong to have to do that for the "official" nodes :p
So basically just adding the patch number would be enough I think.

@ix-dcourtois @bernardkwok Good points, and perhaps our getVersionIntegers method should return three integers for all Interface elements, with the final integer set to zero when not present in the string.  This would be consistent with the global getVersionIntegers method, which returns the major, minor, and build versions of the MaterialX codebase itself.

This sounds like a good to not-prefilter the patch version number in case it's desired.
I want to double check this is true:

A Document write will not store patch version so the utility would return the previous release e.g. 1.38.0 always as 1.39 is not released. Once released all files will be 1.39 when extracted returns 1.39.0. A user can still override this and write out with a patch version but it is still ignored for upgrade logic.

The current distribution / library version is part of the build so includes patch version so
1.39.3 is what's hard-coded. This is what's returned from the global query.

Any nodedef can store version in any format but to have this utility parse the numbers out of the string, it's assumed it's: <major>.<minor>.<patch>. Thus the 2 versions of std surface will parse properly.

For 3. For generalized nodedef version string to numeric support, If there is interest I can put up a "template" parsing proposal issue, so you have something like getVersionIntegers(strong template = "<major>.<minor>.<patch>);


Enable tests for production template

Fixes #12

@jpkrohling or @objectiser could you please review? What is strange though is that ignored test is not listed in Skipped.
Once this is approved I will create an issue of the ignored test

Tests look pretty stable:
https://travis-ci.org/jaegertracing/jaeger-kubernetes/builds/253595020
https://travis-ci.org/jaegertracing/jaeger-kubernetes/builds/253599580
I will merge


How can i print the contents of the tweets?

Hi want to send text content of tweet as caption to insta.
Can you please help how can i get the contents of the tweet ?

The package is only to screenshot operations. You can lookup another package for this.

there must be tweet contents passing through some variable,
It would be great if you help to access it.
it will help me to add as a caption to insta image.


B 18112 update source of duty location and pay grade information in profile to show values from orders table

Agility ticket
Summary
This PR is to ensure the orders table information for pay grade and current/origin duty location are shown on the profile and edit profile page, rather than the service member rank and duty location table information.
The edit profile page at this point is still updating the service member rank and duty location before updating the orders table. I believe that link will be broken with future work to move the entry point that customers will provide their pay grade and duty location to the orders portion of the move process.
Verification Steps for the Author
These are to be checked by the author.

[x] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[x] Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

How to test

Access the milmove app as a customer.
Create a move and enter in a pay grade and duty location.
Put in orders.
Navigate to the profile page and ensure that you see pay grade and duty location information that matches the orders table columns of "grade" and "origin_duty_location_id". As a further test, you can edit the service_members rank column to be some other value than the orders grade value and refresh the page to make sure that you are still seeing the orders table value.

Test coverage on client failed.
Last run: Tue 26 Dec 2023 06:34:37 PM UTC
Refer to this report to see coverage details for the client app.
Documentation for test coverage can be found at this link.

Warnings

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

  Generated by :no_entry_sign: dangerJS against 56700598c63f136dfdc01c141166544f589af833

Do we not still want the text Pay grade? E1-9 and O1-10 are pay grades not ranks

Do we not still want the text Pay grade? E1-9 and O1-10 are pay grades not ranks

Yeah the focus of this story is to remove where the info is coming from. End goal is to get rid of rank entirely and instead use pay grade.

Approved Happo checks

Do we not still want the text Pay grade? E1-9 and O1-10 are pay grades not ranks

Which file are you talking about? We do want rank to become pay grade as rank is an outdated term.

Marking this as a draft for now as I have some more work to do here. To be continued!

Test coverage on client failed.
Last run: Wed 03 Jan 2024 06:31:02 PM UTC
Refer to this report to see coverage details for the client app.
Documentation for test coverage can be found at this link.

It looks like some values have disappeared in the Happo checks - might need to take a look at storybook components of the most recently updated push of code.

It looks like some values have disappeared in the Happo checks - might need to take a look at storybook components of the most recently updated push of code.

I believe this is due to now showing the order tables info on the profile page rather than the service member info. At certain points in the process, the orders table won't be updated yet. For example, creating a new move and before adding orders, this is what I see:

and then reviewing at that point:

However, when I go ahead and put in orders:

I can now see values.

Thoughts? I can for sure fix it, but it also serves as a visual way for the testers to see that the info is now coming from the orders table. And, this info may be moving around/not even in the profile page in my next story.

It looks like some values have disappeared in the Happo checks - might need to take a look at storybook components of the most recently updated push of code.

I believe this is due to now showing the order tables info on the profile page rather than the service member info. At certain points in the process, the orders table won't be updated yet. For example, creating a new move and before adding orders, this is what I see:  and then reviewing at that point:
However, when I go ahead and put in orders:  I can now see values.
Thoughts? I can for sure fix it, but it also serves as a visual way for the testers to see that the info is now coming from the orders table. And, this info may be moving around/not even in the profile page in my next story.

Ahhh gotcha. Makes sense. You should be able to update the test values in the storybook component and that should fix the happo checks. Looks like you're down to one, src/components/Customer/Review/ProfileTable/ProfileTable.stories.jsx

LGTM LGTM LGTM!!!!

@danieljordan-caci Checking in on this PR, I see you requested the data references to rank to be changed to pay grade. I don't know if this is the best approach as our backend is entirely structured around the "rank" parameter. It was to my knowledge we would continue referencing the data as "rank" until even the backend is updated to reflect "pay grade", while just visually displaying it as pay grade for the customer. This creates a discrepancy where frontend is talking about pay grade and the backend is talking about rank, while in the database it's rank. Additionally, even endpoints for GHC/Prime use "rank".

@danieljordan-caci Checking in on this PR, I see you requested the data references to rank to be changed to pay grade. I don't know if this is the best approach as our backend is entirely structured around the "rank" parameter. It was to my knowledge we would continue referencing the data as "rank" until even the backend is updated to reflect "pay grade", while just visually displaying it as pay grade for the customer. This creates a discrepancy where frontend is talking about pay grade and the backend is talking about rank, while in the database it's rank. Additionally, even endpoints for GHC/Prime use "rank".

I do remember that conversation. With this story and with 18111, it is more of transitioning from the service member value of rank to the order value of grade, and relying on that grade value in the backend. I tried to leave instances of service member rank as rank and anything related to orders as grade. What are your thoughts? Would you mind taking a look at 18111 and seeing what you think? My understanding of 18111 is to no longer even fill out the service member rank value during the customer flow and instead fill out the order grade value, so everything involving service member rank would need to reflect that change.


constants: update RuboCop version.

As usual, all warnings here and in Homebrew/homebrew-core will be fixed before merge.

Method parameter must be longer than 3 characters.

I'd favor disabling this rule over complying with it.

@ilovezfs Agreed 👍

CC @reitermarkus earlier on this one: the cask cop will need updated as usual.


Unexpected end of JSON input while parsing near '...uid":"~1.4.0","qs":"~'

can you help me?
when i run : npm install --global --production windows-build-tools,
the error as follow,
Unexpected end of JSON input while parsing near '...uid":"~1.4.0","qs":"~'

It sounds like you have a syntax error in your package.json file. Try checking it with a tool like package-json-validator.com. I am pretty sure this is unrelated to windows-build-tools.


Unicode \u2028 character crashing vue

Vue.js version
2.0.8
Reproduction Link
http://jsfiddle.net/3hmp0e16/1/
Steps to reproduce
Run the JSFiddle above and you will see that content is not visible.
What is Expected?
I would expect the app to run regardless of the Unicode characters, without errors.
What is actually happening?
Uncaught TypeError: Cannot set property 'isStatic' of undefined
for Vue 2.0.8 when \u2028 character is in DOM element attribute on creating new Vue instance.

[Vue warn]: failed to compile template:

  <img src="http://placehold.it/350x150" alt="hello

Related to #3895

Thanks! It's the same as #3895. I'll fix it


Haskell implementation

https://github.com/amarpotghan/crjdt-haskell#readme :)

Cool!

Thanks, I will submit PR to add link to your README later and will add this project's link in haskell version too.


Short Links are 1-digit incrementing numbers

Hey folks,
running the latest git from yourls and everything is fine except that all the created links (except manually created ones) are "just"increments of the last auto-increment, ie 1,2,3,4... I don't want everyone to snoop around in all my links if i hand out a short url.
I noticed that in the config you can set base36. In my understanding a random string is produced uppon creating a new short url.
Am I mistaken or missing something?
Cheers,
-Chris.

You may want to take a look at https://github.com/YOURLS/random-keywords

@R0Bzombie Thanks! :kissing:
@christianreiss Everything is said!

Even risking re-opening this issue: But I cant let this close and stand without saying a proper thank you! Issue s of course solved and this was lightning fast support. Kudos!


Sudoku Solver

Describe the project you want to add with tech stack
A Sudoku Solver made using backtracking.
Used Technologies:
HTML5
CSS3
JavaScript
Expected behavior

Screenshots (optional)

Additional context (optional )

@TusharKesarwani Please assign this issue to me under GSSOC'23

i have very good experience in fronted part, i did some good projects related to fhis so, could you please assaign it to me i will do it

is anyone cuurently working on this project? I would like to contribute to this project


Python 3: subprocess is broken on Windows

What a strange behavior of..?
Example

Windows 10 (14986)
Python 3.5.2
(g)Vim 8 (1-109)
grep and grep-like tool: rg, ag and etc.

grep.js
const message = 'grepme';

proc.py
import subprocess
import os

class Process():
    def __init__(self, commands):
        cwd = None
        startupinfo = None
        if os.name == 'nt':
            startupinfo = subprocess.STARTUPINFO()
            startupinfo.dwFlags |= subprocess.STARTF_USESHOWWINDOW
        proc = subprocess.Popen(commands,
                                stdout=subprocess.PIPE,
                                stderr=subprocess.PIPE,
                                startupinfo=startupinfo,
                                cwd=cwd)
        print(proc.communicate())

Process(['rg', '--version'])
Process(['rg', '--vimgrep', '--no-heading', '--', 'grepme'])

Output
cmd
python proc.py
(b'ripgrep 0.3.2\n', b'')
(b"grep.js:1:18:const message = 'grepme';\nproc.py:57:52:Process(['rg', '--vimgrep', '--no-heading', '--', 'grepme'] )\n", b'')

Vim
:py3file proc.py<CR>
(b'ripgrep 0.3.2\n', b'')
(b'', b'')

is this only broken on Windows?

@chrisbra currently tested only on Windows.
Which is odd, this case does not work only in Vim version for GUI.
Vim version for console works fine on Windows and Linux.

Works for me. You need to chdir to where grep.js is located first.

@char101 please describe more details.
What's your Windows environment and GVim version?

Gvim, Windows 7, Python 3.5.2, compiled with VS 2015

Oh, I can actually reproduce that when the filename is omitted. But it works when the filename is given on the command line.

I have tested. It works when specifying the directory.
@char101 thank you.

So I run process monitor and it seems that rg looks for '-' when the file is not specifed. Maybe rg can detect that it was being piped when run from vim/python but instead of reading from stdin it treats - as the filename.

Actually I knew that on Windows for such tools need to specify a directory (dot as current directory).
But grep..
Thanks for the hint.


[Questions] About back slash support in URI

This is related to issue https://github.com/OData/RESTier/issues/414
Now we have a URL with back slash in it, when the service receive the request, I find Web Api will auto convert back slash to slash, and slash is not "%5C" but becomes the character ''.
I did some search, I find this configuration,
  < uri>
    < schemeSettings>
      < add name="https" genericUriParserOptions="DontUnescapePathDotsAndSlashes"/>
      < add name="http" genericUriParserOptions="DontUnescapePathDotsAndSlashes"/>
    < /schemeSettings>
  < /uri>

This does not work for me, I see there is an option DontConvertPathBackslashes, but when I set here, it indicates this is not correct setting.
Can you help to advise how I can configure a request with back slash? Or this is not supported?
For our project, it is created  via
"C# > Web > ASP.NET Web Application.", and
In the New ASP.NET Project dialog box, select the Empty template.
Check the Web API check box.
If this is not right space for question, can you help to advise where I should ask this question.

Ask this question github.com/dotnet/corefx

@davidfowl thanks

Seems this issue is more related to ASP .NET, so I reopen the issue.

This is a behavior of Http.Sys/IIS. I assume you're running in IIS?

@Tratcher Yes, I am using IIS, is there any configuration I can disable this convert? thanks.

No, there's no way to change this in IIS right now.

@Tratcher thanks, I close the issue as this is not supported.


Site doesn't load

Crunchyroll website is stuck on loading while the extension is enabled the moment it is disabled it starts displaying content back again.
Tried reloading page multiple times.
While it is enabled->

Thanks for the report, this behavior is known to be caused by the proxied token request not getting through. I'll take a look into it as soon as I got time for it!

The proxy server lost all outgoing internet connectivity, I restarted the instance and traffic seems to be normal again. Thanks again for the report :)

The proxy server lost all outgoing internet connectivity, I restarted the instance and traffic seems to be normal again. Thanks again for the report :)

No problem & thanks for this extension.


Add "ChromeOS" detection support.

This will detect ChromeOS on Chromebooks. Here's a user agent that's been captured on a ChromeOS:
Mozilla/5.0 (X11; CrOS x86_64 8872.76.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.105 Safari/537.36
However, I'm not sure how to detect its version since I didn't find a list of possible user agents on Chromebooks.

While I've clearly documented which browsers this library will/will not detect, I have not done so for operating systems. If test coverage for operating systems is to meet the same level of coverage as the browsers, then it would require roughly 98.32% of the StatsCounter GlobalStats for worldwide market share.
Based on that, then the following operating systems should be properly detected and should have test coverage.

OS
%

Android
37.15

Win7
18.12

iOS
13.16

Win10
12.53

OS X
5.06

Win8.1
3.68

Unknown
2.63

WinXP
2.18

Win8
1.15

Linux
0.78

Nokia Unknown
0.75

Windows Phone
0.56

Series 40
0.46

WinVista
0.46

The % column is percent of global market share as reported by StatCounter for January 2017.
Unfortunately, for this specific issue, Chrome OS is not on that list, however, it is literally next on the list as of January 2017. Unfortunately, over the last twelve months it's market share has bounced around between 0.18 and 0.35 without a obvious trend. However, the overall trend may be slightly up and I, personally, wouldn't be surprised if it makes the list soon.
With that in mind, please add a test (or two) to ensure ChromeOS is properly detected.
As for the version number, the Wikipedia entry for Chrome OS references the browser version number as the OS version number.

Hi Keith.
I think it's done. It can now detect the Chrome OS version (which as you suggested is as same as the browser version). I also added 2 tests to make sure that it works fine.

This looks good. I will pull this in. I would like to update the Coverage section in the readme with a paragraph about OS coverage based on our conversation here. I'm current busy, so if you could write a first draft that would be helpful.

OS coverage added.
BTW, I believe, you need to refactor so many of those ifs and add some "else" there. For example, instead of having this:
if (userAgent.indexOf("Edge") >= 0) {
    report.browser.name = "Edge";
}
if (userAgent.indexOf("UCBrowser") >= 0) {
    report.browser.name = "UC Browser for Android";
}
if (userAgent.indexOf("SamsungBrowser") >= 0) {
    report.browser.name = "Samsung Internet";
}

it's better to have this (in terms of performance, of course):
if (userAgent.indexOf("Edge") >= 0) {
    report.browser.name = "Edge";
} else if (userAgent.indexOf("UCBrowser") >= 0) {
    report.browser.name = "UC Browser for Android";
} else if (userAgent.indexOf("SamsungBrowser") >= 0) {
    report.browser.name = "Samsung Internet";
}

But, for now, it's good to go.

Thanks again for creating this pull request! Your changes will be in the next release, version 2.2.11.


Cleanup the repository

Over the last year, the repository has gone through a process of upgrading and it was almost rewritten. While working on the upgrade, the old code wasn't touched to be able to test the old features and make sure the new implementation is not removing any features.
Now it's the time to do some cleanup and separate the old files. Going forward, only the upgraded version should be used by deployment. We can keep the old files for future references but shouldn't be easily accessible. In the following I will list the changes that I think we should make:

[ ] Remove pview.html as it's not used at all.
[ ] Cleanup README.md to remove any mention of pview.html and replace it with mview.html.
[ ] Move mview.html and all of its fonts, js, and css dependencies to a folder called old_viewer.

We don't want to completely remove the old files. This will allow us to test the old implementation.
Make sure to only move the ones that are used by mview.html. Don't move the ones that are used by index.html.
Make sure the old_viewer/mview.html is functional. You might need to modify the src and href of these dependencies after moving.
Don't move the vendor files that are used by index.html.

[ ] Rename index.html to mview.html.

In some deployments and also during debugging we're still using mview.html. By making this change, we'll make sure that the new code is always used.

[ ] Remove any unused file. This includes the sample#.png files.

This is a work in progress. I will update the issue based on the new findings

I've pushed the refactored code on the OSD branch name refactored. Since viewer app needed some changes with respect to these changes, there is a branch name refactored on chaise as well that aligns with the osd changes.

@RFSH close this issue after the code is merged.


env: error while loading shared libraries: libspdlog.so.1

So after I installed according to the instructions everything went smoothly.. when I wanted to install genshin impact an error appeared like this
https://user-images.githubusercontent.com/76796784/210211587-04a174f2-e701-431f-9fbf-3ee8a05619d8.mp4
I don't know if other games are like this but this is a bit strange, when I install it on other arch distros like Endeavour it runs smoothly.
OS: ArcoLinux
Kernel: Linux 6.1.1-273-tkg-pds
CPU: Intel i5-6300U (4) @ 3.000GHz
GPU Driver: i915

Hi, can you try to do the following?
sudo ln -sfr /usr/lib/libspdlog.so.1.11 /usr/lib/libspdlog.so.1

Oh yeah this one too, I've tried to install GE-Proton and it always fails

after creating a simlink, an error with a libspdlog.so.1 appears?

No, after I downloaded the package and chose Proton GE, it always failed, I don't know why it always failed, and after that I installed Lutris-GE-Proton because there was no other choice.

what version of spdlog do you have?

1.11.0-1

It's all weird... Something is wrong with your system. At the moment I have a clean archlinux installed with the latest updates and there is no such problem.
You can try to download a test version of Lutris Wine based on my runimage container:
curl -L https://github.com/VHSgunzo/runimage/releases/download/v0.38/runimage.superlite -o lwrun
chmod +x lwrun
./lwrun {lutris-wine args}

But this is at the beta stage, some errors may occur, and so far there is no support for calling root commands from the container, which will be needed to apply some patches, including for the genshin.

You can also try downgrading the spdlog package.

@UIsystem-code
Have you tried installing the Lutris Wine version in the RunImage container using the command from the comment above?

Closing due to inactivity