Project setup

nuxt project setup , i18n setup, store setup, vue test utils setup, eslint setup, add task feature

I couldn't run the test locally. Could be an issue with package installation.
Few generic points,

[ ] Use yarn instead of npm
[ ] Add the DS files to gitignore as they're mac specific
[ ] Consider separating assets, i.e. svg icons and stylesheets from the component, easier to review and maintain.


Correctly expose the visual hierarchy of accessibility nodes

From FlutterSemanticsToAndroidAccessibilityBridge.java:
        // TODO(ianh): use setTraversalBefore/setTraversalAfter to set
        // the relative order of the views. For each set of siblings,
        // the views should be ordered top-to-bottom, tie-breaking
        // left-to-right (right-to-left in rtl environments), height,
        // width, and finally by list order.

This shouldn't be so hard on Android, because we already have the global coordinates for every box so it's "just" a matter of sorting the list and calling the API.

This has been fixed.


Local $require support

Currently Jasonette supports local JSON as views and mixins. But no support for $require yet.
Support this

And now it's supported https://github.com/Jasonette/JASONETTE-iOS/commit/0bee94b8c9bb9cc753afceb8c87999880b6ec717


[Automation] Generate Fluent Lite from devcenter#package-2024-02

[Automation] Generate Fluent Lite from devcenter#package-2024-02

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure.resourcemanager:azure-resourcemanager-devcenter


nodeos will not stay in sync on 2.0.0-rc2

When running nodeos 2.0.0-rc2 on EOS Mainnet on a public p2p endpoint with around 30 incoming connections, nodeos will sometimes not stay in sync.  It sometimes falls behind by 1 or 2 minutes.  After a (a few hours) it will catch up again.  It is not predictable what is going on as it is accepting incoming connections from the general public.
Server is not too fast: Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
Server has lots of RAM and is using the following configuration
wasm-runtime = eos-vm-jit
eos-vm-oc-enable = true
database-map-mode = locked

This problem was not experienced on 1.8.x.  (Although of course EOS Mainnet transaction volume does change).  Upgrade to 2.0.0 occurred on Nov 14.
The server is connected to other peers (locally on the same network) that are in sync.
Logs are available if required.

is this issue solved?

Work in progress.  See https://github.com/EOSIO/eos/pull/8229

The PR referenced above definitely helps.

Resolved by #8229


feat: enable the github action bot to read and execute commands from comments

What problem does the new feature solve?
Occasionally, the Continuous Integration (CI) process might become stuck, displaying a "waiting for status to be reported" message. In such scenarios, the only option is to trigger CI again by submitting a new commit which may be an empty commit though. Certain open-source projects, like Apache Doris, have implemented a GitHub Action bot specifically for this purpose. It allows users to manually initiate CI and benchmarking by issuing commands through GitHub comments.
What does the feature do?
Enable the github action bot to read and execute commands from github comments.
Implementation challenges
No response

May I give it a try?

@LYZJU2019   Not sure if this is still a required feature. You can directly @ the project maintainers.

Occasionally, the Continuous Integration (CI) process might become stuck, displaying a "waiting for status to be reported" message.

@LYZJU2019 We already addressed this problem, so we don't need a bot to trigger CI now. I'll close this issue, and you can find other issues that you are interested in.


The issue of IE compatibility requires everyone's help

"I have a Vue2 project that uses module federation. It needs to be compatible with IE, and it can run normally in Google Explorer. However, in IE, when it loads js modules shared by other applications, the IP address it loads is incorrect. The port of the main application is 9700, and the port of other applications is 9702.",

"I don't understand why the port he loaded is not 9700, but 9702."

Now the request port for this 404 is 9700. I hope it is 9702


Unhandled nmap

L.S.,
When fireing up everything looks great. When browsing to the url I get a fatal error
dontbug: Using config file:/home/xxx/.dontbug.yaml
dontbug: No <docroot-dir> argument provided. Assuming its the same as <php-source-root-dir>
dontbug: No --install-location specified. Defaulting to $GOPATH/src/github.com/sidkshatriya/dontbug
dontbug: Using --install-location "/home/xxx/.go/src/github.com/sidkshatriya/dontbug"
dontbug: Using php from path /usr/bin/php
dontbug: Using rr from path /usr/bin/rr
dontbug: Generating /home/xxx/.go/src/github.com/sidkshatriya/dontbug/ext/dontbug/dontbug_break.c for all PHP code in: /home/xxx/yyy/yyy-api/public
dontbug: 1 PHP files found
dontbug: Code generation complete. Compiling dontbug zend extension...
dontbug: Successfully ran 'make distclean' in dontbug zend extension directory
dontbug: Successfully ran phpize in dontbug zend extension directory
dontbug: Running configure in dontbug zend extension directory
dontbug: Successfully ran configure in dontbug zend extension directory
dontbug: Successfully compiled the dontbug zend extension
dontbug: -- Recording. Ctrl-C to terminate recording if running on the PHP built-in webserver
dontbug: -- Recording. Ctrl-C if running a script or simply wait for it to end

rr: Warning: Your CPU frequency governor is 'powersave'.  rr strongly
    recommends that you use the 'performance' governor.  Not using the
    'performance' governor can cause rr to be at least 2x slower
    on laptops.

    On Fedora-based systems, you can enable the 'performance' governor
    by running the following commands:

    $ sudo dnf install kernel-tools
    $ sudo cpupower frequency-set -g performance

rr: Saving execution to trace directory `/home/xxx/.local/share/rr/php-7'.
dontbug zend extension: dontbug.so successfully loaded by PHP
PHP 7.0.8-0ubuntu<IP_ADDRESS> Development Server started at Thu Oct 13 12:32:13 2016
Listening on http://<IP_ADDRESS>:8088
Document root is /home/xxx/yyy/yyy-api/public
Press Ctrl-C to quit.
[FATAL /home/roc/rr/rr/src/util.cc:626:should_copy_mmap_region() errno: EACCES] Unhandled mmap /home/xxx/yyy/yyy-api/storage/framework/views/eb787bc5b0d00e38b5b2c5b312898d82c9820e4b.php(prot:0x1;SHARED); uid:33 mode:33188
dontbug: fatal error: base.go:428: record.go:207: signal: aborted

Do you have any clue? The directoy /home/xxx/yyy/yyy-api/storage/ has chmod 777

Some questions:

Are you running in a Linux VM or on normal Linux?
What does $ rr --version say ?
You're using Ubuntu 16.04 right?

Try doing the following as a test
$ rr record ls
$ rr replay

How old is your laptop approximately?

A gdb prompt should appear. Now type in continue followed by the enter key do you get the directory listing again?

Also, did you build rr from source or did you just download the binary?

Basically I think there is a problem with rr and not Dontbug. So I'm going to ask you some additional questions to get enough information to troubleshoot this:

What does $ uname -a say?
Does Dontbug work if you do:

sudo apt-get install cpufrequtils
sudo cpufreq-set -g performance

(See https://github.com/mozilla/rr/wiki/Usage#getting-the-best-performance-on-your-machine-especially-laptops )

What do you see if you do:

$ sudo apt install linux-tools-common
$ perf list

What does the following command say?

$ cat /proc/sys/kernel/perf_event_paranoid

(See https://github.com/mozilla/rr/wiki/Building-And-Installing#hardwaresoftware-requirements )

What does the following command say?

$ cat /proc/cpuinfo

@django23 As suggested by @khuey is user xxx the same user thats running the command? Probably want to make sure this is not some permissions issue.
(Though you mention that /home/xxx/yyy/yyy-api/storage/ is chmod 777 )
Better still... if the users are different -- can you try debugging a script in your home directory to eliminate a source of error?
Sorry if you're overwhelmed by the number of things we're requesting from you... :-)

If the permissions are 777 I would expect https://github.com/mozilla/rr/blob/master/src/util.cc#L578 to return true ...

I reverted the changes, but wil try to send you al the information needed.

This issue has been closed as its been inactive for some time now. It can be reopened when there is more information.


Update dependencies

The CI failures are unrelated:
Error: Error: Unexpected HTTP response: 500

in "Install CMake"


workflows: Compare encodings using git

This pull request adds validation, via git, of the encodings generated by our LLVM-to-SMT workflow, for all the recent LTS kernels.
@harishankarv You will probably want to check the last commit, as I removed all encodings we previously had.
Fixes: https://github.com/bpfverif/agni/issues/48.

Removing all the encodings is fine by me, I was never a fan of it anyway. A couple of thoughts:
The reason for keeping 5.9 instead of an LTS one (e.g. 5.10), is that 5.9 is used by bpf-verifcation workflow. Thinking if might just be cleaner to change the bpf-verificatoin workflow to run on 5.10 instead? That way, we only have LTS kernels (as a rule). Just a thought, this is definitely not pressing. Of course, we also have 6.10 as an exception, so 5.9 is also okay.
I also was wondering if it might be worth to store all encodings in a separate git repository, and add that as a submodule to this repository. That way, we decouple the encodings and the code that generates them. The workflows will also have to be re-engineered to clone the submodules first before comparing the encodings. Again, just a thought.
Anyway, as the plan is to focus on getting a stable CI, we should keep these as future nice-to-haves.
Other than that, the PR looks good to me, please feel free to merge it!

The reason for keeping 5.9 instead of an LTS one (e.g. 5.10), is that 5.9 is used by bpf-verifcation workflow. Thinking if might just be cleaner to change the bpf-verificatoin workflow to run on 5.10 instead? That way, we only have LTS kernels (as a rule). Just a thought, this is definitely not pressing. Of course, we also have 6.10 as an exception, so 5.9 is also okay.

Yep, that's a good point. I'm planning to look into this as part of adding a check for the BPF verification workflow. We may be a bit limited in terms of what we can use as a kernel because we likely want something where violations are found.

I also was wondering if it might be worth to store all encodings in a separate git repository, and add that as a submodule to this repository. That way, we decouple the encodings and the code that generates them. The workflows will also have to be re-engineered to clone the submodules first before comparing the encodings. Again, just a thought.

That's definitely possible, although submodules are a bit of a pain to work with sometimes in my experience. Are you worried about bloating the git repository? As long as we keep to a few LTS kernels like this and the encodings themselves don't get 10x bigger, I think git should be able to handle it.


CVAT GUI showing rotated and stretched images. SAM recognises "correct" image

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce
I created a folder of images, zipped it and uploaded to CVAT.
Some images are rotated and stretched, see attached images. Left is image courtesy of CVAT and the mask is courtesy of SAM. Right is the original image.
I double checked the raw images, unzipping the file and checking those images.
So far 4 frames have had this behaviour, I am 36 images through a dataset of 248.

I have logged out and in of CVAT and restarted the browser, re-zipped and re-uploaded the images, problem persists.
Expected Behavior
No response
Possible Solution
No response
Context
No response
Environment
- Using web server app.cvat.ai
- Ubuntu 20.04
- Chromium browser

Hi @serena-mou
Please, share task ID from app.cvat.ai

Hello,
Task #381197
Thank you

@serena-mou
Thank you, I am investigating the problem. For now I'd recommend delete such broken images from the task.


Any way to add a custom stylesheet?

Hi @plouc, just a general question.
I'd like to use http://fizzed.com/oss/font-mfizz on my dashboard.
Is there a simple way to inject je CSS file?
What do you suggest?
Thank you.

@tomav, unfortunately, Mozaïk v1 doesn't provide a way to simply add css/fonts, Mozaïk v2 is on its way and will allow this by simply import the resource from the main app.

BTW it seems that font-awesome which is included by default provides similar icons.

And if you want transitionable svg icons, you should have a look at this :)

I was looking for icons per programming languages, not bundled in FA default set.
Thanks anyway, I'll have a look to Mozaik 2. I was working on a basic NewRelic extension but will probably postpone to make it work later with Mozaik 2.

My approach would be to create a custom theme.


Exit with error code when ls with filter yields no results

Summary
It would be handy if gopass ls filter would exit with a non-zero status code if there are no results. This allows to query for the existence of an entry without actually decrypting any secrets.
Steps To Reproduce
Run gopass ls some-nonexistent-prefix. Check $? and see code 0.
Expected behavior
echo $? yields a non-zero code.
(I am running gopass 1.6.11-git+HEAD go1.9.5 linux amd64, but according to release notes this has not been changed.)

Thanks for raising this issue.
I agree with you, we should change the exit code to ExitNotFound.


Uncaught TypeError: Cannot read property 'hidden' of undefined(…)

Hi,
I am creating "bubble" chart type and passing the data that you can see on the image from the attachment. Constantly I am getting this issue on line 9273 ( if (isNaN(value) || meta.data[index].hidden) {... ) in file Chart.js

@milostimotic can you create a fiddle that reproduces this so that we can debug?

Hi Evert,
Thanks for quick replay.
I've created JSFiddle where everything works fine. This issue is happening in my project but I am sure that I am passing data in same structure I did in JSFiddle - https://jsfiddle.net/milostimotic/87msyj22/8/
On line 9271
helpers.each(dataset.data, function(rawValue, index) {
rawValue is 3, and index is x, (first element of array dataset) it seems that meta.data array is empty and because of that JS error occurs.
You can take a look at meta object on this image:

@milostimotic I think I see the issue.
In your first image, you have multiple datasets but each data in the dataset is not an array. It's just an object. In your fiddle, you have 1 object inside an array and then it works.

Hi Evert,
Thanks, that was the problem. Sorry for this. I will close this issue.

No worries, glad I could resolve it :)

same situation :D
thx for solving


Covariant return type change detected

When running mvn clean install -Passembly on JDK11 (so probably related to #1148), animal sniffer reports:
(and maybe https://github.com/mojohaus/animal-sniffer/issues/61)
[INFO]
[INFO] --- animal-sniffer-maven-plugin:1.16:check (default) @ rdf4j-sail-nativerdf ---
[INFO] Checking unresolved references to org.codehaus.mojo.signature:java18:1.0
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/btree/Node.java:450: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.limit(int) has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.limit(int)
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/btree/Node.java:463: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.limit(int) has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.limit(int)
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/btree/BTree.java:283: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.rewind() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.rewind()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/btree/BTree.java:1053: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.rewind() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.rewind()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/btree/BTree.java:1086: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.rewind() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.rewind()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/btree/BTree.java:1110: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.clear() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.clear()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/DataFile.java:117: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.rewind() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.rewind()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/HashFile.java:114: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.rewind() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.rewind()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/HashFile.java:201: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.rewind() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.rewind()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/HashFile.java:214: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.rewind() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.rewind()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/HashFile.java:220: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.clear() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.clear()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/HashFile.java:292: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.rewind() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.rewind()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/HashFile.java:329: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.rewind() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.rewind()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/HashFile.java:407: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.flip() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.flip()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/HashFile.java:409: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.clear() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.clear()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/HashFile.java:421: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.rewind() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.rewind()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/HashFile.java:425: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.clear() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.clear()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/HashFile.java:446: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.clear() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.clear()
[INFO] /rdf4j/core/sail/nativerdf/src/main/java/org/eclipse/rdf4j/sail/nativerdf/datastore/HashFile.java:512: Covariant return type change detected: java.nio.Buffer java.nio.ByteBuffer.clear() has been changed to java.nio.ByteBuffer java.nio.ByteBuffer.clear()
[INFO]

I went through these just now - in none of these method calls do we actually do anything with with return value. As far as I can tell we can safely ignore this.


Tip for citext extension

Alert beginners about citext extension.

For a lot of columns types this note is needed, making the documentation longer. But you're right, if someone doesn't know PostgreSQL that good it's not clear the extension needs to be activated. Give me a few days to think whether I can find a better solution ;)

Thanks for your work, I had a lot of things to do so I didn't find any time before. I've updated the wording a little bit and added your note to all other column types which do need an extension installation too.


acecore DM support

acecore cant be used in DMs yet. has to be fixed also checking if the guild id is present and if not disable a few commands in DMs

maybe also adding a bool to the command structure if it should even be registered with the empty string that makes it global (also DMs then) but if not it could make the command registering a lot faster eliminating rate limits


Support disable specific platform

Signed-off-by: renfeiw<EMAIL_ADDRESS>

tested locally and internal grinder: Grinder_TKG/1031


Remove OES-AP installation mode

Changing this in all other files was not required....in case it comes back :-(

I thought removing in other files restricts users from using OES-AP as installation mode


Add PackageSourceUrl to all nuspecs

With the enhancement of the chocolatey nuspec to include other metadata parameters, we should at least add the packageSourceUrl to each nuspec.

Actually, looks like this was already taken care of.
Used this:
Get-ChildItem C:\github\Organisations\chocolatey\chocolatey-coreteampackages -Recurse -Include *.nuspec |
    ForEach-Object {
        if(-not(Select-String -InputObject $_ -Pattern "<packagesourceurl>")){
            Write-Host "Found $_";
        }
    }

And only found one nuspec that didn't have it.


library updates

Update libuv from 1.41.0 to 1.44.1.

The CMAKE_RULE_MESSAGES=OFF option is no longer needed.

Update sqlite from 3.34.1 to 3.38.2.

The -DSQLITE_ENABLE_JSON1 option is no longer needed.
The log-db migrate mat now checks for upgrade-db failures instead of silently ignoring them.
SQLite now stores its column type in all capital letters.

What do you think about excluding the SQLite serialize/deserialize interface as proposed here?
This had been optional but was enabled by default in 3.36.0 and Swish doesn't use it.

It's fine to omit the serialize/deserialize interface. Thanks for suggesting it!

FWIW, SQLite 3.38.3 was released recently so I'm waiting for the next shoe to drop.


[operator] Manage kube-state-metrics

How to categorize this PR?

/area dev-productivity delivery
/kind enhancement
What this PR does / why we need it:
With this PR, gardener-operator is enhanced to manage kube-state-metrics.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/7016
Special notes for your reviewer:
/cc @ScheererJ @timuthy @istvanballok @rickardsjp
Release note:

The `gardener-operator` does now also manage `kube-state-metrics`.

/assign

/hold
I'm still waiting for some feedback from the monitoring colleagues about https://github.com/gardener/gardener/blob/454ad5ba2d67e99bbd4d0ce278b8fef838cb6ff6/pkg/operation/botanist/component/kubestatemetrics/resources.go#L219. Most likely, we want to specify this flag for KSM in the garden cluster, but with the current changes we would.
Let's see what their feedback will be, but adapting it will be little effort, i.e. the vast majority of this PR is already final/ready for review.

Copying the answer from the colleagues in an out-of-band channel:

By default, none of the annotations are exported by the ksm as metric labels. This allow list says that the shoot.gardener.cloud/uid annotation (if exists), should be exposed as a label.
We need it so that we can map the k8s namespace to the shoot uid.
It is fine to have that in the garden runtime cluster as well, although it is not used there.

Hence, the PR is fine as is and we can proceed.
/retest-required
/unhold

/approve


Add hostname to config values of the chart

I had to configure the hostname to <IP_ADDRESS> to be able to reach the langfuse ui outside of my aks cluster with a port-forwarding. I think it makes sense to add hostname as a configurable value in the helm chart.

@mautini what do you think about this change? To me it seems like this is technically not necessary as this could be passed also via langfuse.additionalEnv. Currently Langfuse does not default to this, is there a downside to defaulting to <IP_ADDRESS>?

Hi Nicolas,
thanks a lot for your quick review of this change. I agree that we should not add this explicitly to avoid replicating the documentation of the container in this helm chart. The docs already include a full list of available optional ENV variables.
I agree. Let's avoid changing the default to <IP_ADDRESS> outside of a major version, as it could be a breaking or security-impacting change for some users.
Let's keeping this pull request open to consider merging it as part of the upcoming v3 change, which will also involve a more significant change to this Helm chart to reflect new services.

@Eulenator can you pass hostname via langfuse.additionalEn in the meantime or is there another reason to add hostname explicitly to the chart?

@Eulenator can you pass hostname via langfuse.additionalEn in the meantime or is there another reason to add hostname explicitly to the chart?

Sure. I was not aware of this option.
Without setting the hostname to <IP_ADDRESS>, the Langfuse server was virtually unusable in a Kubernetes cluster.

Then let's close this issue as additionalEnv is the way to go here


[docs] Add a VISION.md file

The WHY and WHAT of this project.

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

@rosskevin All good with that version ❤

Is anyone needed more time to review it? Otherwise I will merge it.


Scary outdated java

The java version in the artifactory-pro:latest (6.5.2 at this point) image is still OpenJDK 8 u131, from like 18 months ago. Please update the "FROM" line on Dockerfile.artifactory (actually all of them) to a more recent version.
~tommy
PS: I appreciate that the Dockerfile is embedded within the image, but it would be good if it were in a public facing repo (perhaps this one) so that we could submit PR's for updates.

Example: https://github.com/TJM/artifactory-docker-examples/blob/standalone/standalone/Dockerfile
Also, for giggles, check out the Alpine Linux based Dockerfile:
https://github.com/TJM/artifactory-docker-examples/blob/standalone/standalone/Dockerfile.alpine

@TJM - thanks for the feedback and examples. As you noted, the base versions are old and we are working on a more recent version. Also the Alpine is a great idea (already discussed internally), but there are customers not willing to use it, so we use a more accepted base. I hope we'll have more to share in the following weeks.

@eldada Thanks for the response! We can't use the currently published version due to all the security vulnerabilities in it. Please do update the base (FROM), and preferably, don't "COPY" zip files into the image. It would be best to convert them to .tar.gz and use "ADD" or just expand them and COPY the contents in. It appears that this is being built from the "source" dir (since its just standalone.zip), so instead of grabbing that archive, just copy the contents of the "build" directory (or whatever) that the archive was created from.
RE: Alpine -  I would recommend publishing both versions, similar to how the openjdk images are produced.
Honestly, I would personally rather use Enterprise Linux (CentOS) than Debian, but I think we are supposed to not really care what is in the image, right? :-/
Given the opportunity to decrease the size of the image by ~1GB, I would think people would be willing to give alpine a try. It's not like you need the other GB of "tools" installed on the base OS, right?
Are the maintainers  of the artifactory docker image looking at these repos, or should we email them directly (or submit a support ticket?)
~tommy

Hey Tommy. We are already working on the new Java version. Should be in one of the coming releases.
All your comments are valid and make good sense. If there's a particular one you think should be pushed, go ahead and open a JIRA ticket and our teams will evaluate it. You can also get some voters and help push a specific change you feel is important.
RE: Adding an Alpine distribution. We are evaluating this as well.
RE: Base OS. We use the official openjdk image, which by default is based on Debian.
RE: Size. I strongly agree, but as mentioned before, this is not a strong requirement.

I'm happy to update that Artifactory 6.9.0 now comes with Java 11 based on the distroless base image.
This also dramatically reduced the size of the image.

@eldada - Thanks for your efforts, but it does not appear to be in 6.9.0.
$ docker ps
CONTAINER ID        IMAGE                                           COMMAND                  CREATED             STATUS              PORTS               NAMES
e544c5f71e01        docker.bintray.io/jfrog/artifactory-pro:6.9.0   "/entrypoint-artifac…"   55 seconds ago      Up 52 seconds       8081/tcp            ecstatic_volhard
$ docker exec -it e544c5f71e01 bash
artifactory@e544c5f71e01:/$ cat /docker/artifactory-pro/Dockerfile.artifactory
FROM docker.bintray.io/jfrog/openjdk:8u181

LABEL maintainer<EMAIL_ADDRESS>

Oooppssss.... I messed it up with an internal version, which will be released soon. sorry for the confusion.

Now we have it... Artifactory 6.9.1 has a new base image and Java 11.


Nested functions causing strange text replacement error

I have two functions:
  - isUser(uid): root.authUserIndex[auth.userid] === uid || isShopper()
  - isShopper(): root.users[root.authUserIndex[auth.uid]].isShopper === true

along with the following rule:
   - location: "/users/$userid/"
    read: isUser($userid)
    write: isUser($userid)

it LOOKS like that the isShopper() function is getting replaced into the isUser(uid) function, and since uid is a parameter in the first function, the resulting rule comes out to be:

".read":"false||false||root.child('authUserIndex').child(auth.$userid).val()===$userid||root.child('users').child(root.child('authUserIndex').child(auth.$userid).val()).child('isShopper').val()===true"

(notice the auth.$userid part). I believe this is a bug, and the obvious workaround is to rename my variables (which I did), but just wanted to make you guys aware of a potential issue here.

scoping on function params is still a bit weird but this particular issue is now resolved in 0.0.26


[v2] Plugins not loaded as in v1

My zplug v1 install yields:
  Loaded /home/agross/.dotfiles/bin/path.zsh
  Loaded /home/agross/.dotfiles/git/path.zsh
  Loaded /home/agross/.dotfiles/ruby/path.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/path.zsh
  Loaded /home/agross/.dotfiles/atom/aliases.zsh
  Loaded /home/agross/.dotfiles/cygwin/aliases.zsh
  Loaded /home/agross/.dotfiles/cygwin/cygwin.zsh
  Loaded /home/agross/.dotfiles/esxi/aliases.zsh
  Loaded /home/agross/.dotfiles/etckeeper/aliases.zsh
  Loaded /home/agross/.dotfiles/git/aliases.zsh
  Loaded /home/agross/.dotfiles/git/editor-windows.zsh
  Loaded /home/agross/.dotfiles/git/git-sh-aliases.zsh
  Loaded /home/agross/.dotfiles/git/rapid-git-aliases.zsh
  Loaded /home/agross/.dotfiles/ruby/aliases.zsh
  Loaded /home/agross/.dotfiles/ssh/ssh-agent.zsh
  Loaded /home/agross/.dotfiles/systemd/aliases.zsh
  Loaded /home/agross/.dotfiles/vim/aliases.zsh
  Loaded /home/agross/.dotfiles/wget/aliases.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/aliases.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/cdpath.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/correction.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/directories.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/exports.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/fpath.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/history.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/jobs.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/key-bindings.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/ls-colors.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/prompt.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/rm.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/terminal-title.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/urls.zsh
  Loaded /home/agross/.dotfiles/zsh/themes/agross.zsh-theme
  Loaded bobthecow/git-flow-completion/git-flow-completion.plugin.zsh
  Loaded robbyrussell/oh-my-zsh/plugins/ssh-agent/ssh-agent.plugin.zsh
  Loaded rapid-git/rapid-git/rapid-git.sh
  Loaded Tarrasch/zsh-bd/bd.plugin.zsh
  Loaded /home/agross/.dotfiles/ssh/postinit.zsh
  Loaded /home/agross/.dotfiles/cygwin/completion.zsh after running compinit
  Loaded /home/agross/.dotfiles/node/completion.zsh after running compinit
  Loaded /home/agross/.dotfiles/travis/completion.zsh after running compinit
  Loaded /home/agross/.dotfiles/zsh/lib/completion.zsh after running compinit
  Loaded knu/z/z.sh after running compinit

± zplug list
knu/z  =>  of:z.sh, nice:10, dir:/home/agross/.cache/zplug/repos/knu/z
/home/agross/.dotfiles  =>  from:local, nice:9, of:**/postinit.zsh, dir:/home/agross/.dotfiles
zsh-users/zsh-syntax-highlighting  =>  nice:10, if:[[ windows != windows ]], dir:/home/agross/.cache/zplug/repos/zsh-users/zsh-syntax-highlighting
/home/agross/.dotfiles  =>  from:local, nice:10, of:**/completion.zsh, dir:/home/agross/.dotfiles
/home/agross/.dotfiles/zsh/themes  =>  from:local, nice:-18, of:agross.zsh-theme, dir:/home/agross/.dotfiles/zsh/themes
b4b4r07/zplug  =>  dir:/home/agross/.cache/zplug/repos/b4b4r07/zplug
Tarrasch/zsh-bd  =>  dir:/home/agross/.cache/zplug/repos/Tarrasch/zsh-bd
bobthecow/git-flow-completion  =>  dir:/home/agross/.cache/zplug/repos/bobthecow/git-flow-completion
plugins/ssh-agent  =>  from:oh-my-zsh, ignore:oh-my-zsh.sh, dir:/home/agross/.cache/zplug/repos/robbyrussell/oh-my-zsh/plugins/ssh-agent
/home/agross/.dotfiles  =>  from:local, nice:-19, of:**/(^(zprofile|path|completion|postinit)).zsh, dir:/home/agross/.dotfiles
plugins/sudo  =>  from:oh-my-zsh, ignore:oh-my-zsh.sh, if:((0)), dir:/home/agross/.cache/zplug/repos/robbyrussell/oh-my-zsh/plugins/sudo
plugins/systemd  =>  from:oh-my-zsh, ignore:oh-my-zsh.sh, if:((0)), dir:/home/agross/.cache/zplug/repos/robbyrussell/oh-my-zsh/plugins/systemd
holman/dotfiles  =>  as:command, of:bin/e, dir:/home/agross/.cache/zplug/repos/holman/dotfiles
/home/agross/.dotfiles  =>  from:local, nice:-20, of:**/path.zsh, dir:/home/agross/.dotfiles
rapid-git/rapid-git  =>  if:((1)), of:rapid-git.sh, dir:/home/agross/.cache/zplug/repos/rapid-git/rapid-git

zplug v2:
  Loaded /home/agross/.dotfiles/bin/path.zsh
  Loaded /home/agross/.dotfiles/git/path.zsh
  Loaded /home/agross/.dotfiles/ruby/path.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/path.zsh
/home/agross/.dotfiles/zsh/themes/agross.zsh-theme:2: zgitinit: function definition file not found
  Loaded /home/agross/.dotfiles/zsh/themes/agross.zsh-theme
  Loaded b4b4r07/zplug/init.zsh
  Loaded bobthecow/git-flow-completion/git-flow-completion.plugin.zsh
  Loaded robbyrussell/oh-my-zsh/plugins/ssh-agent/ssh-agent.plugin.zsh
  Loaded robbyrussell/oh-my-zsh/plugins/ssh-agent/ssh-agent.plugin.zsh
  Loaded rapid-git/rapid-git/rapid-git.sh
  Loaded Tarrasch/zsh-bd/bd.plugin.zsh
  Loaded knu/z/z.sh after compinit

$ zplug list
knu/z  =>  use:z.sh, nice:10
/home/agross/.dotfiles  =>  from:local, nice:9, use:**/postinit.zsh
zsh-users/zsh-syntax-highlighting  =>  nice:10, if:[[ windows != windows ]]
/home/agross/.dotfiles  =>  from:local, nice:10, use:**/completion.zsh
/home/agross/.dotfiles/zsh/themes  =>  from:local, nice:-18, use:agross.zsh-theme
b4b4r07/zplug  =>  at:v2, hook-build:zplug update --self
Tarrasch/zsh-bd  =>  nil
plugins/ssh-agent  =>  from:oh-my-zsh, ignore:oh-my-zsh.sh
bobthecow/git-flow-completion  =>  nil
/home/agross/.dotfiles  =>  from:local, nice:-19, use:**/(^(zprofile|path|completion|postinit)).zsh
plugins/sudo  =>  from:oh-my-zsh, ignore:oh-my-zsh.sh, if:((0))
plugins/systemd  =>  from:oh-my-zsh, ignore:oh-my-zsh.sh, if:((0))
holman/dotfiles  =>  as:command, use:bin/e
/home/agross/.dotfiles  =>  from:local, nice:-20, use:**/path.zsh
rapid-git/rapid-git  =>  if:((1)), use:rapid-git.sh

It seems my zplugs with these use tags are not loaded:
nice=-19; zplug "$DOTFILES", from:local, nice:$nice, use:'**/(^(zprofile|path|completion|postinit)).zsh'

I also tried making paths absolute:
nice=-19; zplug "$DOTFILES", from:local, nice:$nice, use:"$DOTFILES/**/(^(zprofile|path|completion|postinit)).zsh"

For zplug v1 I added this to my .zshrc before defining plugins:
  setopt extended_glob

Also note that robbyrussell/oh-my-zsh/plugins/ssh-agent/ssh-agent.plugin.zsh is loaded twice with zplug v2.
Repos for you to test:
zplug v1: https://github.com/agross/dotfiles/tree/master
zplug v2: https://github.com/agross/dotfiles/tree/zplugv2

This issue is probably fixed; please try it out.

Not yet:
...
[0K ==> Installation finished successfully!
zplug: total wall-time 36.542005 sec.
[zplug] no matching file or directory: /home/agross/.dotfiles
plugins/sudo: (not loaded)
plugins/systemd: (not loaded)
  Loaded /home/agross/.dotfiles/bin/path.zsh
  Loaded /home/agross/.dotfiles/git/path.zsh
  Loaded /home/agross/.dotfiles/ruby/path.zsh
  Loaded /home/agross/.dotfiles/zsh/lib/path.zsh
/home/agross/.dotfiles/zsh/themes/agross.zsh-theme:2: zgitinit: function definition file not found
  Loaded /home/agross/.dotfiles/zsh/themes/agross.zsh-theme
  Loaded b4b4r07/zplug/init.zsh
  Loaded bobthecow/git-flow-completion/git-flow-completion.zsh
  Loaded robbyrussell/oh-my-zsh/plugins/ssh-agent/ssh-agent.plugin.zsh
  Loaded robbyrussell/oh-my-zsh/plugins/ssh-agent/ssh-agent.plugin.zsh
  Loaded rapid-git/rapid-git/rapid-git.sh
  Loaded Tarrasch/zsh-bd/bd.zsh
  Loaded /home/agross/.dotfiles/ssh/postinit.zsh
  Loaded /home/agross/.dotfiles/cygwin/completion.zsh after compinit
  Loaded /home/agross/.dotfiles/node/completion.zsh after compinit
  Loaded /home/agross/.dotfiles/travis/completion.zsh after compinit
  Loaded /home/agross/.dotfiles/zsh/lib/completion.zsh after compinit
  Loaded knu/z/z.sh after compinit
_prompt_agross_scm_branch:1: command not found: zgit_isgit
_prompt_agross_scm_status:1: command not found: zgit_inworktree
_prompt_agross_symbol:1: command not found: zgit_isgit

agross@AXL /scratch
$ zplug list
knu/z  =>  use:z.sh, nice:10
/home/agross/.dotfiles  =>  from:local, nice:9, use:**/postinit.zsh
zsh-users/zsh-syntax-highlighting  =>  nice:10, if:[[ windows != windows ]]
/home/agross/.dotfiles  =>  from:local, nice:10, use:**/completion.zsh
/home/agross/.dotfiles/zsh/themes  =>  from:local, nice:-18, use:agross.zsh-theme
b4b4r07/zplug  =>  at:v2, hook-build:zplug update --self
Tarrasch/zsh-bd  =>  nil
plugins/ssh-agent  =>  from:oh-my-zsh, ignore:oh-my-zsh.sh
bobthecow/git-flow-completion  =>  nil
/home/agross/.dotfiles  =>  from:local, nice:-19, use:**/(^(zprofile|path|completion|postinit)).zsh
plugins/sudo  =>  from:oh-my-zsh, ignore:oh-my-zsh.sh, if:((0))
plugins/systemd  =>  from:oh-my-zsh, ignore:oh-my-zsh.sh, if:((0))
holman/dotfiles  =>  as:command, use:bin/e
/home/agross/.dotfiles  =>  from:local, nice:-20, use:**/path.zsh
rapid-git/rapid-git  =>  if:((1)), use:rapid-git.sh

@agross Please provide us with a minimal .zshrc with steps to reproduce.

@NigoroJr
OK, I think I could trace this down.
In my .zshrc I use extended globs to get the "load everything but" functionality:
zplug "/home/agross/.dotfiles", from:local, nice:$nice, use:"**/(^(zprofile|path|completion|postinit)).zsh"

...which translates to /home/agross/.dotfiles/**/(^(zprofile|path|completion|postinit)).zsh.
When base/sources/local.zsh gets to evaluate the pattern it doesn't find any files because I have $options[extended_glob] disabled.
In zplug v1, I enable extended globs just for zplug.
zplug v2 doesn't see that option because the glob is evaluated in a subshell:
load_patterns+=( $(zsh -c "echo $expanded_path/$zspec[use]" 2>/dev/null) )

Essentially, all user-defined options like my extended globs settings would be invisible to the subshell, right? Could you possibly change the code to use the current shell to evaluate the pattern like zplug v1 does?

@agross Thanks for elaborating. I get the problem, and I'm perfectly fine with changing the code so that it uses the current shell.
https://github.com/NigoroJr/zplug/commit/1f5a9de9f5044ce298f3d63022792aabe37bf99a
Here is a rough (and possibly naive) implementation of that. If extended_glob is set, it should evaluate that expression accordingly. I feel like there's a more elegant way of dealing with this that I may be missing. @b4b4r07 Any ideas?

Thanks for reporting. I got it very well!
This time, I propose the following methods (please write these settings to your .zshrc):
zstyle ':zplug:config' subshell \
  'extended_glob'

Maybe this is what you want.

@b4b4r07 Since :zplug:config subshell is specifically for setopt, maybe rename it to subshell_opts?

@b4b4r07 and I have discussed this on slack. Summary of the points made:

If there are many options that users might want to enable only in sub shells (e.g. extended_glob, dot_glob) then :zplug:config subshell or :zplug:config subshell_opts is okay (latter is preferable because it won't confuse the users into thinking they can do things other than just setting the options).
If there are only a few of those options, creating individual zstyle for each of them (e.g. zstyle :zplug:config extended_glob) is a possible alternative.
Another approach is to enable all the options that are on in the current shell for each sub shell that's executed. This way the implementation of zplug is hidden from the users and the user can write zplug statements as normal.

Concern: how much is the overhead for enabling options enabled in the current shell for each sub shell invocation?

fix-149 works. Many thanks!

@NigoroJr How is this way?
I have implemented ":zplug:config:setopt" context and will introduce same_curshell and only_subshell.

@b4b4r07 This looks good to me. I'm not sure, however, whether we should default same_curshell to yes or no. My thought on this is that it's more common for people to want to use the same options as the current shell, so have it yes by default and if no, use only_subshell.

I see. In my opinion, both are implemented because same_curshell should default to no. Also, people who want to enable the option should change this to yes, I think.

#160 is merged.


Bug

运行环境：Windows
运行代码
from lmqg import TransformersQG
model = TransformersQG(
model="lmqg/t5-base-squad-qg",
model_ae="lmqg/t5-base-squad-qg-ae"
)
x = """William Turner was an English painter who specialised in watercolour landscapes. One of his best known pictures is a view of the city of Oxford from Hinksey Hill."""
model.generate_qa(x)
报错信息
Traceback (most recent call last):
File "E:/Pythonworksplace/knowledge/lmqg_tools/generate.py", line 4, in
model = TransformersQG(
File "E:\Anaconda3\envs\knowledge\lib\site-packages\lmqg\language_model.py", line 341, in init
self.spacy_module = SpacyPipeline(language)
File "E:\Anaconda3\envs\knowledge\lib\site-packages\lmqg\spacy_module.py", line 35, in init
self.nlp = spacy.load(model)
File "E:\Anaconda3\envs\knowledge\lib\site-packages\spacy_init_.py", line 50, in load
return util.load_model(
File "E:\Anaconda3\envs\knowledge\lib\site-packages\spacy\util.py", line 324, in load_model
return load_model_from_package(name, **kwargs)
File "E:\Anaconda3\envs\knowledge\lib\site-packages\spacy\util.py", line 357, in load_model_from_package
return cls.load(vocab=vocab, disable=disable, exclude=exclude, config=config)
File "E:\Anaconda3\envs\knowledge\lib\site-packages\en_core_web_sm_init_.py", line 10, in load
return load_model_from_init_py(file, **overrides)
File "E:\Anaconda3\envs\knowledge\lib\site-packages\spacy\util.py", line 517, in load_model_from_init_py
return load_model_from_path(
File "E:\Anaconda3\envs\knowledge\lib\site-packages\spacy\util.py", line 392, in load_model_from_path
nlp = load_model_from_config(config, vocab=vocab, disable=disable, exclude=exclude)
File "E:\Anaconda3\envs\knowledge\lib\site-packages\spacy\util.py", line 429, in load_model_from_config
nlp = lang_cls.from_config(
File "E:\Anaconda3\envs\knowledge\lib\site-packages\spacy\language.py", line 1672, in from_config
nlp.add_pipe(
File "E:\Anaconda3\envs\knowledge\lib\site-packages\spacy\language.py", line 774, in add_pipe
pipe_component = self.create_pipe(
File "E:\Anaconda3\envs\knowledge\lib\site-packages\spacy\language.py", line 660, in create_pipe
resolved = registry.resolve(cfg, validate=validate)
File "E:\Anaconda3\envs\knowledge\lib\site-packages\thinc\config.py", line 746, in resolve
resolved, _ = cls._make(
File "E:\Anaconda3\envs\knowledge\lib\site-packages\thinc\config.py", line 795, in _make
filled, _, resolved = cls._fill(
File "E:\Anaconda3\envs\knowledge\lib\site-packages\thinc\config.py", line 850, in _fill
filled[key], validation[v_key], final[key] = cls._fill(
File "E:\Anaconda3\envs\knowledge\lib\site-packages\thinc\config.py", line 849, in _fill
promise_schema = cls.make_promise_schema(value, resolve=resolve)
File "E:\Anaconda3\envs\knowledge\lib\site-packages\thinc\config.py", line 1057, in make_promise_schema
return create_model("ArgModel", **sig_args)
File "pydantic\main.py", line 990, in pydantic.main.create_model
File "pydantic\main.py", line 299, in pydantic.main.ModelMetaclass.new
File "pydantic\fields.py", line 411, in pydantic.fields.ModelField.infer
File "pydantic\fields.py", line 342, in pydantic.fields.ModelField.init
File "pydantic\fields.py", line 451, in pydantic.fields.ModelField.prepare
File "pydantic\fields.py", line 550, in pydantic.fields.ModelField._type_analysis
File "E:\Anaconda3\envs\knowledge\lib\typing.py", line 774, in subclasscheck
return issubclass(cls, self.origin)
TypeError: issubclass() arg 1 must be a class
I also got the same error when running trainer code; At first, I thought it was a system problem, but running it on the server couldn't solve it.
Hope to get the author's answer.

It looks like an issue with the spacy library.
Please have a look the following link.
https://stackoverflow.com/questions/77037891/typeerror-issubclass-arg-1-must-be-a-class


[tool_crash] ArgumentError: Invalid argument(s) (replacement): Must not be null

Command
flutter run

Steps to Reproduce

...
...
...

Logs
ArgumentError: Invalid argument(s) (replacement): Must not be null
#0      _StringBase.replaceAll (dart:core-patch/string_patch.dart:637:30)
#1      LocalizationsGenerator._generateBaseClassFile (package:flutter_tools/src/localizations/gen_l10n.dart:856:8)
#2      LocalizationsGenerator._generateCode (package:flutter_tools/src/localizations/gen_l10n.dart:944:46)
#3      LocalizationsGenerator.writeOutputFiles (package:flutter_tools/src/localizations/gen_l10n.dart:1005:5)
#4      generateLocalizations (package:flutter_tools/src/build_system/targets/localizations.dart:66:9)
#5      GenerateLocalizationsTarget.build (package:flutter_tools/src/build_system/targets/localizations.dart:123:5)
#6      _BuildInstance._invokeInternal (package:flutter_tools/src/build_system/build_system.dart:801:27)
<asynchronous suspension>
#7      _BuildInstance.invokeTarget.<anonymous closure> (package:flutter_tools/src/build_system/build_system.dart:744:35)
#8      new Future.sync (dart:async/future.dart:223:31)
#9      AsyncMemoizer.runOnce (package:async/src/async_memoizer.dart:43:45)
#10     _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:744:21)
<asynchronous suspension>
#11     FlutterBuildSystem.build (package:flutter_tools/src/build_system/build_system.dart:566:36)
#12     generateLocalizationsSyntheticPackage (package:flutter_tools/src/dart/generate_synthetic_packages.dart:64:30)
#13     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:949:13)
<asynchronous suspension>
#14     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:836:33)
<asynchronous suspension>
#15     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart)
#16     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:29)
#17     _rootRun (dart:async/zone.dart:1190:13)
#18     _CustomZone.run (dart:async/zone.dart:1093:19)
#19     _runZoned (dart:async/zone.dart:1630:10)
#20     runZoned (dart:async/zone.dart:1550:10)

[✓] Flutter (Channel stable, 1.22.3, on Mac OS X 10.15.7 19H2, locale en-KH)
    • Flutter version 1.22.3 at /Users/mengheang/.flutter/flutter
    • Framework revision 8874f21e79 (3 weeks ago), 2020-10-29 14:14:35 -0700
    • Engine revision a1440ca392
    • Dart version 2.10.3

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/mengheang/Library/Android/sdk
    • Platform android-30, build-tools 29.0.2
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor
      --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.9.1

[!] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.48.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.14.1

[✓] Connected device (1 available)
    • iPhone 11 Pro (mobile) • B4FC1842-3F92-4458-855E-870DBC700BDE • ios •
      com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)
    ! Error: Parker is not connected. Xcode will continue when Parker is connected. (code
      -13)

! Doctor found issues in 2 categories.

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 7a4c33425ddd78c54aba07d86f3f9a4a0051769b
Plugins
connectivity-0.4.8+1
connectivity_macos-0.1.0+1
devicelocale-0.3.3
flutter_facebook_auth-1.0.1
flutter_libphonenumber-0.3.11
flutter_plugin_android_lifecycle-1.0.11
flutter_secure_storage-3.3.1+1
fluttertoast-7.1.1
geocoder-0.2.1
geolocator-5.3.2+2
google_api_availability-2.0.4
google_maps_flutter-1.0.6
google_sign_in-4.5.6
google_sign_in_web-0.9.2
location_permissions-3.0.0+1
path_provider-1.6.24
path_provider_linux-0.0.1+2
path_provider_macos-0.0.4+6
path_provider_windows-0.0.4+3
shared_preferences-0.5.12+4
shared_preferences_linux-0.0.2+4
shared_preferences_macos-0.0.1+6
shared_preferences_web-0.1.2+4
shared_preferences_windows-0.0.1+3
sqflite-1.3.2+1

Crashing line is locale replacement:
https://github.com/flutter/flutter/blob/8dfd42f6b7194598eb93985fbbd7eaf58588f918/packages/flutter_tools/lib/src/localizations/gen_l10n.dart#L856
#53374

\cc @shihaohong

Hi @mengheangrat could you share a minimal reproducible sample here? What particular use case causes this failure?

I believe that the absence of "@variable": {} for every "variable": "translation" in .arb files causes the crash

I just encountered one of these.  and i'm using artemis client package. everything seems okay except i get the same error. does this happen due to reserved keywords?

I just encountered one of these.  and i'm using artemis client package. everything seems okay except i get the same error. does this happen due to reserved keywords?

I just encountered one of these. and i'm using artemis client package. everything seems okay except i get the same error. does this happen due to reserved keywords?

could you share a minimal reproducible sample here? What particular use case causes this failure?
Edit: Judging from the clue that the crashing line is locale replacement, it has something to do with how the locale/language is defined in the arb file when using the gen-l10n tool

I just encountered one of these. and i'm using artemis client package. everything seems okay except i get the same error. does this happen due to reserved keywords?

could you share a minimal reproducible sample here? What particular use case causes this failure?
Edit: Judging from the clue that the crashing line is locale replacement, it has something to do with how the locale/language is defined in the arb file when using the gen-l10n tool

I'll try to reproduce. I can't say that it has something to do with artemis. but this one query gives me errors when it gave me a value of null.
when I tried it this morning, it works now. the problem with my end might be that there are null values that my package won't allow to be fetched.

I'll try to reproduce. I can't say that it has something to do with artemis. but this one query gives me errors when it gave me a value of null.
when I tried it this morning, it works now. the problem with my end might be that there are null values that my package won't allow to be fetched.

@mengheangrat This is a tools crash we'd like to track down and fix.  Please keep open for investigation.

I'd like to give feedback regarding this issue. It seems that the  json_serializable occurs an error when a date is nullable from the REST API and cannot parse it.
From:
DateTime dateFromJson(String dateTime){
   return DateTime.parse(dateTime);
}

To:
DateTime dateFromJson(String dateTime){
  if(dateTime == null){
   /// return something;
   }
  return DateTime.parse(dateTime);
}

I had also experience this issue when the filename or @@locale value is not in the iso language code. eg: Japanese I put jp and it is ja in iso.

Hi @jmagman, can this be considered fixed? The code for describeLocale method has gone through some changes. See https://github.com/flutter/flutter/blob/ffea970ce8c5513f28f8058ac4714f31e535fd84/packages/flutter_tools/lib/src/localizations/localizations_utils.dart#L196
Also, if I create a .arb file with the wrong locale I get this error
Generating synthetic localizations package failed with 1 error:

Error: The following .arb file's locale could not be determined:
/Users/nexus/projects/nevercode/bot/lib/l10n/app_js.arb
Make sure that the locale is specified in the file's '@@locale' property or as part of the filename (e.g. file_en.arb)

If I add the locale key but I specify it incorrectly, I get this error (from the current describeLocale method)
Generating synthetic localizations package failed with 1 error:

Error: "js" is not a supported language code.
See https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry for the supported list.

So far, the tool hasn't crashed for me.


Get current software language

AS A User
I WANT to see all text appears on GUI on the language configured in a config file at deployment
SO THAT I can set localization of my product

For that task we need 2 elements :

[ ] an application configuration file with default language & available languages

[ ] Frontend : implement i18next & i18next react

[ ] API one route to get global configuration


Remove dependency on sox to split/trim wave files

If desired we could implement a pure python standard library only version of functions like trim_wav_ms by using the wave module https://docs.python.org/3/library/wave.html

That would be good but I agree with your labelling this low-priority. Calling sox for now is fine.

I guess one thing is that sox may be a whole lot faster depending on how the standard library is wave module is implemented. This might be a good first issue for someone to contribute?

Sure, since it's pretty orthogonal to everything else.

It seems as though Kaldi needs sox anyway

I think this might be a situation where it makes sense to use this standard library function as a fallback only if sox is not available.


A bug with an infinite loop on the reissue of the token

To determine that the token has expired, the methods use a simple exception hvac.exceptions.Forbidden.
Since the exception is too general, there may be a situation when, for example, an incorrectly configured policy for approle and the module accesses a secret to which it does not have access.
Thus, we get into an infinite loop in which the token will be reissued indefinitely due to incorrectly configured rights.
https://github.com/obervinov/vault-package/blob/main/vault/vault.py#L472

done
https://github.com/obervinov/vault-package/pull/27/commits/f3e830d2b77eb1d14d5c0390fc1a9a6f7627b00a


dislike markets

especially if likes are ever used as a market quality signal:
https://manifold.markets/IsaacKing/will-this-market-have-at-least-50-l

an emphatic +1

https://github.com/manifoldmarkets/manifold/commit/2fb408321bb60ea8b88ba2e0ab6c720c068f250f


feat!: Revert deprecating retrieve_token, adding support of environment variables

Closes #39
Removing the deprecation that was introduced in #11.
Also adding support of environment variables: GH_ENTERPRISE_TOKEN, GITHUB_ENTERPRISE_TOKEN, GH_TOKEN, and GITHUB_TOKEN. It will be preferred than the token from hosts.yaml file or the secure storage.

Will be shipped in 0.4.0 as this PR contains some breaking changes.

Looks good! I was implementing this feature myself, and took a different approach for separating different methods of retrieving tokens. could you take a look of mine and tell me what you think?
https://github.com/siketyan/gh-config-rs/compare/GH-39...s3i7h:gh-config-rs:feat/brush-up-token-handling?expand=1
Though after reading go-gh I found my implementations are not correct about handling enterprise tokens, so treat my code like a pseudo code.  e.g. the order of resolution is actually enterprise env > enterprise config > gh env > gh config (last config look up is a no-op because it's the same as the one before) so maybe combining retrieve_token_from_env and retrieve_token_from_config might be a way etc.
https://github.com/cli/go-gh/blob/dbd982eba2a041d88d398cce01cb708c4c3503f7/pkg/auth/auth.go#L63

@s3i7h Noticed my implementation does not handle them correctly too. However I would not like to combine loading from environment variables and loading from the hosts.yaml file tbh. Also gh-config-rs never have no grantee for the consistency with go-gh. Thus I would like to keep the order of GH_ENTERPRISE_TOKEN, GITHUB_ENTERPRISE_TOKEN > GH_TOKEN, GITHUB_TOKEN > hosts.yaml > secure storage. Any thoughts about this?

I too think that order will be more concise (as it can completely  isolate interactions with envs and config)
The only case this implementation breaks behavior is when yml has the specified host's token but (GITHUB|GH)_TOKEN is also present, and IMO both implementations favoring each other makes sense, so I think we can make it a decision to go with the implementation you suggested 👍
I still prefer to separate each retrieve_token_from_* functions and iterate them inside retrieve_token though

I decided that keeping the current implementation in this branch as each functions has reusability themselves without depending on impls on the Hosts struct. The Hosts struct should be loaded only if we need to access ~/.config/gh/hosts.yml.
Thank you for your review and idea anyway!

@siketyan hmm, so are you suggesting to separate token handling from Hosts struct entirely?
I support the decision but won't it involve a lot of breaking changes? If so, I'd prefer to implement the decisions we made above as Hosts impl for the time being, and make the migration a different issue. What do you think? I can put my hands on either of it :)

@siketyan ping ↑

@s3i7h No, retrieve_token method itself will remain in the impl of Hosts struct (at least for now). However retrieve_token_from_env and retrieve_token_secure functions are placed on top-level as loading Hosts can be omitted while reading token from environment variables or from the secure storage. As the diff shows, retrieve_token_secure method in Hosts struct is an only thing that will be a breaking change in this changes.

Ah I somehow overlooked the actual changes. Makes sense and looks good to me now 😌 sorry for taking up your time


[Regression]V2 - Project Console - Able to create CLA group at foundation level when CLA Group already exists at project level

Observed that user is able to create CLA Group at foundation when CLA Group already exists at project level. Also observed that the CLA Group is converted to foundation level CLA Group. User should not be allowed to create foundation level CLA group when CLA group already exists at project level
When I created project level CLA Group  foundationLevelCLA flas is false (It has 2 CLA Groups)
Later when created CLA Group at foundation level, foundationLevelCLA is set to true for existing CLA groups at project level
{
    "list": [
        {
            "ccla_enabled": true,
            "ccla_pdf_url": "https://cla-signature-files-dev.s3.amazonaws.com/contract-group/225dd49f-81fb-4167-8190-95b2a19dae1a/template/ccla.pdf",
            "ccla_requires_icla": true,
            "cla_group_description": "Description ProjectLevel2childprojectsChild1",
            "cla_group_id": "225dd49f-81fb-4167-8190-95b2a19dae1a",
            "cla_group_name": "ProjectLevel2childprojectsChild1",
            "foundationLevelCLA": true,
            "foundation_name": "ProjectLevel2childprojectsParent",
            "foundation_sfid": "a0902000000A2DGAA0",
            "icla_enabled": true,
            "icla_pdf_url": "https://cla-signature-files-dev.s3.amazonaws.com/contract-group/225dd49f-81fb-4167-8190-95b2a19dae1a/template/icla.pdf",
            "project_list": [
                {
                    "project_name": "ProjectLevel2childprojectsChild1",
                    "project_sfid": "a0902000000A2DLAA0",
                    "repositories_count": 0
                },
                {
                    "project_name": "ProjectLevel2childprojectsChild2",
                    "project_sfid": "a0902000000A2DQAA0",
                    "repositories_count": 0
                },
                {
                    "project_name": "ProjectLevel2childprojectsParent",
                    "project_sfid": "a0902000000A2DGAA0",
                    "repositories_count": 0
                }
            ],
            "repositories_count": 0,
            "root_project_repositories_count": 0,
            "total_signatures": 0
        },
        {
            "ccla_enabled": true,
            "ccla_pdf_url": "https://cla-signature-files-dev.s3.amazonaws.com/contract-group/41396aa0-a5e3-4971-9dab-a4b674c2ac1e/template/ccla.pdf",
            "ccla_requires_icla": true,
            "cla_group_description": "Description ProjectLevel2childprojectsChild2",
            "cla_group_id": "41396aa0-a5e3-4971-9dab-a4b674c2ac1e",
            "cla_group_name": "ProjectLevel2childprojectsChild2",
            "foundationLevelCLA": true,
            "foundation_name": "ProjectLevel2childprojectsParent",
            "foundation_sfid": "a0902000000A2DGAA0",
            "icla_enabled": true,
            "icla_pdf_url": "https://cla-signature-files-dev.s3.amazonaws.com/contract-group/41396aa0-a5e3-4971-9dab-a4b674c2ac1e/template/icla.pdf",
            "project_list": [
                {
                    "project_name": "ProjectLevel2childprojectsChild1",
                    "project_sfid": "a0902000000A2DLAA0",
                    "repositories_count": 0
                },
                {
                    "project_name": "ProjectLevel2childprojectsChild2",
                    "project_sfid": "a0902000000A2DQAA0",
                    "repositories_count": 0
                },
                {
                    "project_name": "ProjectLevel2childprojectsParent",
                    "project_sfid": "a0902000000A2DGAA0",
                    "repositories_count": 0
                }
            ],
            "repositories_count": 0,
            "root_project_repositories_count": 0,
            "total_signatures": 0
        },
        {
            "ccla_enabled": true,
            "ccla_pdf_url": "https://cla-signature-files-dev.s3.amazonaws.com/contract-group/7de696cb-7cb3-4e87-855f-ed0d69eb1dbb/template/ccla.pdf",
            "ccla_requires_icla": true,
            "cla_group_description": "Description ProjectLevel2childprojectsParent",
            "cla_group_id": "7de696cb-7cb3-4e87-855f-ed0d69eb1dbb",
            "cla_group_name": "ProjectLevel2childprojectsParent",
            "foundationLevelCLA": true,
            "foundation_name": "ProjectLevel2childprojectsParent",
            "foundation_sfid": "a0902000000A2DGAA0",
            "icla_enabled": true,
            "icla_pdf_url": "https://cla-signature-files-dev.s3.amazonaws.com/contract-group/7de696cb-7cb3-4e87-855f-ed0d69eb1dbb/template/icla.pdf",
            "project_list": [
                {
                    "project_name": "ProjectLevel2childprojectsChild1",
                    "project_sfid": "a0902000000A2DLAA0",
                    "repositories_count": 0
                },
                {
                    "project_name": "ProjectLevel2childprojectsChild2",
                    "project_sfid": "a0902000000A2DQAA0",
                    "repositories_count": 0
                },
                {
                    "project_name": "ProjectLevel2childprojectsParent",
                    "project_sfid": "a0902000000A2DGAA0",
                    "repositories_count": 0
                }
            ],
            "repositories_count": 0,
            "root_project_repositories_count": 0,
            "total_signatures": 0
        }
    ]
}

Discovered issue - working on the solution.

Submitted PR to resolve this issue: https://github.com/communitybridge/easycla/pull/1783

Submitted and merged PR to resolve this issue: https://github.com/communitybridge/easycla/pull/1783

Verified that the issue is fixed


Metaphlan Conda Repository

The Metaphlan conda repository depends on
samtools >=0.1.19,<1.0 .
I am wondering if this can be changed to the most recent samtools version ? Why is it limited to 1.0 ?

Hi @MichWeb75,
the requirements you mentioned here is related to MetaPhlAn2, which had to use a specific version of samtools since StrainPhlAn was requiring a specific output format that was kept only to such versions.
If you are not interested in using StrainPhlAn, you can upgrade samtools to a more recent version. The usage of samtools is limited to StrainPhlAn, since MetaPhlAn2 does not uses it internally.
In the latest MetaPhlAn 3.0 recipe, you can use the latest version of samtools


Add lat/lng bounding box param to hotspots API

With the number of hotspots on the network growing at a fast clip, it's getting too expensive to fetch and store all hotspots in memory. And Algolia's geospatial search while fast, is pricey, only gives us a limited number of hotspots within a radius, and isn't integrated with helium-js to return Hotspot objects. Therefore it'd be great to allow our existing hotspots route to take a bounding box which would be the currently viewed map area, and return a cursor-paginated list of hotspots within that bounding box.
I'd propose a bounding box be defined as the SW + NE coordinates to be consistent with Mapbox. If indexes are added to the lat/lng columns, then it should be relatively efficient to do a BETWEEN query:
WHERE lat BETWEEN :minLat AND :maxLat AND lng BETWEEN :minLng AND :maxLng

We can choose to address the wrapping issue at 180 degrees longitude if we want, or just do the above as a first pass at a solution, given that we don't expect m/any queries to be made over the pacific in that geography.

Fixed by https://github.com/helium/blockchain-http/pull/206


Feature request: Add reverse continue for TimeTravel Debugging feature for Node

This request builds on the following work that was done earlier to support TTD for Node in VSCode

UI support for TimeTravel Debugging for Node
Adding step back capability to VSCode node-debug adapter for TTD
UI support for TimeTravel Debugging

According to some internal usability testing, we discovered a need to have a reverse continue button on the debug bar in order to enhance the usability of the time travel debugging for more complex scenarios.
/cc: @Weinand, @isidorn, @roblourens, @mrkmarron

@aruneshchandra please explain the semantics of "reverse continue"

"Reverse continue" is suppose to work exactly like the "Debug Continue" with the difference being that it goes backwards and is only available while debugging a TTD trace.  So, when the debugger is broken into while debugging a TTD trace, hitting reverse continue should execute backwards until the first (previous) break point is hit.  To enable this VSCode can pass a stepback:continue command to the debug adapter and the TTD enabled runtime should handle the rest.
@mrkmarron - do you have anything else to add ?

@roblourens are you supporting back-in-time debugging in node-debug2 too?

I don't think Node-chakra supports --inspect yet, although I think they're working on it.

@roblourens is right, --inspect is not supported in Node-ChakraCore yet , but we do plan to support it.
/cc: @digitalinfinity @agarwal-sandeep

any update on this ?

This is planned for the November release.

cool - when is the Nov release ? do we have a date ?

@aruneshchandra the plan with the dates will be posted soon on GitHub - to get notified on each iteration plan you can follow Erich on twitter https://twitter.com/erichgamma?lang=en

Do we know when this might show up in Nightlies ? We will be showing a demo at NodeInteractive at the end of this month and wanted to see this in action before that.

We can make this happen.

@aruneshchandra what is the exact name for the stepaction attribute of the continue that is passed to chakra? For stepping back it was 'back'. The stepback:continue that you've mentioned above does not look proper.

Since the command is continue stepaction:"reverse" may be appropriate. @aruneshchandra @mrkmarron?

node-debug uses a value reverse for the stepaction attribute of the continue request.

@aruneshchandra 'reverse continue' has arrived in the Insiders build. If you install the "Mock Debug" extension, you can try the feature:

Thanx @weinand and @isidorn - this is great!


[3.x][iOS] Fix touch handling for overlay views

Fixes https://github.com/godotengine/godot/issues/56417
GodotView class now uses custom method names so iOS doesn't trigger UIView touch input directly via UIWindow on creating or showing overlay UIViews.
GodotViewGestureRecognizer now also filters out any input that's not coming from GodotView class which also helps when there is an overlay UIView on game view.

Thanks!

Cherry-picked for 3.4.3.


Displayed and charged donation values are highly inconsistent

For small donation application displayed value something like "46 RUB", but actual donation was for "1.49 USD" (which is about 83 RUB nowadays).
SMS Backup Plus need to display either in currency that will be charged (e.g. in USD in my case), or charge in currency that is being displayed (e.g. in RUB in my case).
Also I don't see donation option anymore, is it possible to do another donation?

Thanks, I'll check, maybe the rates don't auto-adjust. The donation option disappears once you have donated, it's not possible to donate again.

The rates don't adjust automatically and thus were stuck in 2014.
Now they should reflect the current exchange values:
1.29€ (RUB 109.00, USD 1.49) / 4€ (RUB 339.00, USD 4.99) / 7.90€ (RUB 690.00, USD 9.99)


Handle empty UrlBase when reading from config

Hi, I use a reverse proxy and handle all my k8s ingress as subdomains (e.g. sonarr.something.com). As such my UrlBase remains empty. I am not proficient in go but I think if we were able to check for a null/empty value here we could account for these scenarios.
Currently I see these errors in my logs which lead me to believe the url is simply malformed.
sonarr [Info] Auth: Auth-Unauthorized ip <IP_ADDRESS> url 'http://localhost:8989//api/v3/history'

https://github.com/onedr0p/exportarr/blob/a2a66246bd05cb345baa08c487eb94395eb04526/internal/client/client.go#L47-L65

Nevermind! I see that we are leveraging v0.6.1 and that this was in fact remedied... Sorry for the inconvenience


Background images on mobile not showing

A few months ago I used version 1.3.15 and used background images instead of the normal img tag to fill the slider. This worked fine on mobile. Today I'm building a new site using version 1.5.6 and using background images does not render the images on mobile. It works fine for desktop though. The difference I'm seeing is that the slick track's width is set to zero as oppose to version 1.3.15. I'm trying to go through the code to figure it out but do you have any thoughts on this?
Thanks

@kenwheeler If you see this, I figured out what the problem is but not exactly what lines. If you deem it worthy, maybe it can be fixed in the code but if not I understand.
For those who run into this same problem, I found out that the ".slick-list" width was not being set. For me, CSS fixes it easily where I can set width to be 100% on mobile. It seems like this is always the case, but I don't know the slider's code well enough to say.

It's being set to 0 when?

Hey I'm going to close this because it doesn't have a test case per the contribution guidelines.. If you can recreate it in a fiddle, we can look at reopening. Thanks!


Browser crashing with 5000*5000 data points.

I am using pivottable.js from long time, we are using pagination to show 100 records per page. For one specific need, we want to remove the pagination and want to show all the data. for 10001000 though its taking time we are able to see the data but when we move to 50005000 browser is crashing. Is there any way to show whole data may be by using lazy loading or something?

This library is not designed to display 5k x 5k tables... That's 25 million cells. As I said in a previous issue (#599), if each cell was 1px by 1px, you would need a grid of 3 by 5 HDTVs to render it, and I just don't think that this kind of thing gives a reasonable user experience, so I'm not interested in supporting this use-case.

@roopesh95 how did you manage to add pagination? I´ve been trying to add it but without success so far.


[tinyply] update to 2.3.4

Update tinyply port to version 2.3.4

What does your PR fix?
Version update for tinyply port.

Which triplets are supported/not supported? Have you updated the CI baseline?
No changes

Does your PR follow the maintainer guide?

Yes

Thanks for the update!


Started to add default profiles

This is only an example file. We should discuss which kind of profiles we would like to deliver. E.g. there should be something like a "pure" profile which does not enhance with fabric8 specific annotations. Other profiles could select specific generators only. Suggestions for profiles are highly appreciated.

[lgtm] merge

Just mingled up with @ceposta PR which I rebased (forgot to make new branch). Going to merge this PR nevertheless ;-)

[lgtm] merge

[merge]

[merge]

lgtm [merge]


Add SCROLL-TO-TOP-BUTTON

we can add a scroll to top button
@akshitagupta15june

I will add the scroll to the top button

assign this issue to me

please assign this issue to me

I am interested in contributing to this project by enhancing it with a visually appealing scroll-to-top button. Could you kindly assign me the task?

This issue has been inactive for a long time
I would like to work on this issue
Please assign

@akshitagupta15june ...please assign it


[1.3.6][dolphinscheduler-api] DataSourceController create mysql version 8.0 fail

It is only compatible with MySQL version 5.7, but not version 8.0

@cpbeast  Can you describe your operation and provide the error log?I think this can work well with MySQL 8.0.
I have tested on MySQL 8.0.22, it will print a warning log, this is caused by ssl, if you also meet this problem, you can try to set  useSSL=false
https://github.com/apache/dolphinscheduler/blob/bc22ae7c91c9cbd7c971796ba3a45358c2f11864/dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/datasource/mysql/MysqlDatasourceProcessor.java#L54

Can you describe your operation and provide the error log? I think this can work well with MySQL 8.0.
I have tested on MySQL 8.0.22, it will print a warning log, this is caused by ssl, if you also meet this problem, you can try to set useSSL=false

I just started to learn. I used docker compose deployment on MAC, and there was no change. From the log, it was the driver problem of connecting to MySQL. Version 8.0 should be com.mysql.cj.jdbc.driver

@cpbeast I think this is caused by the driver missing, have you downloaded the MySQL connector lib? Maybe you can follow the tip in How to support MySQL https://dolphinscheduler.apache.org/en-us/docs/latest/user_doc/docker-deployment.html

I understand. After downloading the source code, I should modify < mysql. Connector. Version > 8.0.21 < / MySQL. Connector. Version >. When loading the driver, I should change com.mysql.jdbc.driver to com.mysql.cj.jdbc.driver,then build docker images and deployed using docker compose

@cpbeast I think you need to download the connector lib

Of course, you can choose a higher version of the connector, but what I want to say is that the current version can also work. It may be a good idea to provide version options when adding data sources, because sometimes different versions of Driver may not be compatible.

@cpbeast I think you need to download the connector lib

Of course, you can choose a higher version of the connector, but what I want to say is that the current version can also work. It may be a good idea to provide version options when adding data sources, because sometimes different versions of Driver may not be compatible.

大哥，你是上海的吗，你刚刚说的项目跑起来使用mysql的数据库吧，我是使用postgresql

在页面 创建数据源，添加mysql数据源的时候，报错，看日志说是驱动的问题
如果自己修改了源码，然后build镜像，取个自己的tag，然后使用docker-compose部署，应该可以吧


Missing timeoutSeconds in probes in stacks' app-deploy.yaml causes error when creating Knative Service

Describe the bug
Knative Serving v0.8 adds a validator for readinessProbe: https://github.com/knative/serving/blob/release-0.8/pkg/apis/serving/k8s_validation.go#L424-L459
With this validator, if readinessProbe.periodSeconds is defined, timeoutSeconds also has to be defined in the probe definition.
Otherwise, Knative admission webhook gives an error like the following:
 Warning  ProcessingError  1s (x15 over 45m)  appsody-operator  Internal error occurred: admission webhook "webhook.serving.knative.dev" denied the request: mutation failed: expected 1 <= 0 <=<PHONE_NUMBER>: spec.template.spec.containers[0].readinessProbe.timeoutSeconds

As of now, some of the stacks don't have readinessProbe.timeoutSeconds defined. e.g. https://github.com/appsody/stacks/blob/ed928495d5e860e92daa96f3d09c7c4e2bc4b74f/incubator/java-microprofile/image/config/app-deploy.yaml#L15-L21
Note: I didn't find any validator for livenessProbe that checks for this.
To Reproduce
Steps to reproduce the behavior:

On a cluster with Knative Service v0.8+, deploy the following app-deploy.yaml:

apiVersion: appsody.dev/v1beta1
kind: AppsodyApplication
metadata:
  name: gdpr2
spec:
  # Add fields here
  version: 1.0.0
  applicationImage: ykoyfman/gdpr2
  stack: java-microprofile
  createKnativeService: true
  service:
    type: NodePort
    port: 9080
    annotations:
      prometheus.io/scrape: 'true'
  readinessProbe:
    failureThreshold: 12
    httpGet:
      path: /health/ready
      port: 9080
    initialDelaySeconds: 5
    periodSeconds: 2
  livenessProbe:
    failureThreshold: 12
    httpGet:
      path: /health/live
      port: 9080
    initialDelaySeconds: 5
    periodSeconds: 2

Expected behavior
Expected a Knative Service gets created.
Actual behaviour
Instead an error happened.
If applicable please specify:

CLI version: N/A
Stack you are using: java-microprofile and any other stack that defines readinessProbe

Making a list of stacks that use the readiness probe to tick off as added:

[ ] Java Microprofile
[ ] Java Spring Boot 2
[ ] Java Spring Boot with Liberty
[ ] Vertx
[ ] Node.js Functions
[x] Node.js Express
[ ] Node.js Loopback

@Kamran64 can we close this now?

Closed, as we have implemented this change in several stacks. There are a couple of stacks remaining however we will leave this to the stack maintainers themselves. Separate issues have been raised to address this.


Experimental Component Feedback - UI Shell

@tomlroach
4. UI Shell http://www.carbondesignsystem.com/experimental/ui-shell/code
The expanding left side panel on the UI shell has some unpleasant behaviour - when a user moves their mouse over one of the icons, the shell slides out, but also expands, which in many cases leaves the user hovering over a different area to the one they moved their mouse into. Perhaps a slower vertical transition could make the experience better, although I'm not sure that would be enough. I think the component has some issues. I think perhaps it ought to be a mouse over to initiate the horizontal slide, and then a click on a subtitle causes the vertical expand, rather than doing both in a single motion.

Yeah I think part of the problem is the full bar is not supposed to be shrinking upward and definitely makes it more jarring. I think this is a product of imbedded view port.
Preview should look something more like this:

Yes, ideally/eventually we will want a full view preview for this I think instead of squishing it into the component viewport.


Es6 module support & plugin system

So this PR is probably larger than PRs normally should be, but refactoring wavesurfer to work with a module system turned out to required some extra steps.
Since I realize I've been very opinionated please consider this as a base for discussion.
TL;DR

bundling with webpack/grunt was removed

es 6 transpiling with babel
linting with eslint

plugin api

standardised plugin definition structure
new api for dynamic adding, initialising and destroying plugins
config api for automatic plugin initialisation on wavesurfer initialisation

There are breaking changes :pensive:

Due to a limitation with webpack the plugins on the global object are now lowercase (window.WaveSurfer.elan, not window.WaveSurfer.ELAN)
All module systems now use the module name WaveSurfer (AMD as well)
Using the old API to add plugins (e.g. timeline.init()) doesn't work anymore mostly works, but in some cases may not anymore
I haven't managed to get the coverage reporting to work with webpack yet

Updated build system
Previously all parts of the library (and its plugins) relied on the global WaveSurfer object to attach themselves to. Working this way with a module bundler means exposing this object which defeats the purpose of dependency injection and module bundling. The library needed to be refactored to use dependency injection so that there was no need for a global object.
Achieving this without some kind of build tool would have be a tedious task. So I opted for webpack, which provides convenient features to build multi-part libraries. Also it has an inbuilt dev server with livereloading etc. (Currently webpack 2, which is in beta, but apparently only until the docs are finished)
jscs and jshint, which were currently being used for linting have merged as eslint, so it only made sense to change to that linter (as a webpack loader).
I also updated karma to work with webpack.
So now there was really no reason to continue using grunt at all, so I removed it. Instead all the scripts are aliased from package.json.
Wavesurfer can be accessed like this:

script-tags approach/global object:

<script src="my/path/dist/wavesurfer.js"></script>
<script src="my/path/dist/plugin/wavesurfer.regions.js"></script>
<script>
    alert(window.WaveSurfer);
    alert(window.WaveSurfer.regions);
</script>

commonjs/requirejs

const WaveSurfer = require('wavesurfer.js');
const Regions = require('wavesurfer.js/dist/plugin/wavesurfer.regions.js');

ES6 imports

import WaveSurfer from 'wavesurfer.js';
import Regions from 'wavesurfer.js/dist/plugin/wavesurfer.regions.js';

Development workflow changes
The new dev tasks are:

npm start – Transpile the plugins and start the dev server at localhost:8080 (reloading only works with the core lib currently)
npm run build
npm run test

Plugin system
The plugins were written in a way which basically just added to the WaveSurfer global variable. To be able to implement this in a truly modular fashion there had to be some process of registering plugins, allowing them to augment the library without having to have that globally available. To achieve this I defined a standard plugin definition format. (See an example further below)
Adding, initialising and destroying plugins
There are three ways to add a plugin:

Adding and initialising plugin immediately (this will do in 99% of the cases):

var wavesurfer = WaveSurfer.create({
    container: '#waveform',
    waveColor: 'violet',
    plugins: [
        WaveSurfer.timeline({
            container: '#wave-timeline'
        })
    ]
});

Adding a plugin immediately and initialising it dynamically:

var wavesurfer = WaveSurfer.create({
    container: '#waveform',
    plugins: [
        WaveSurfer.timeline({
            container: '#wave-timeline',
            deferInit: true // stop the plugin from initialising immediately
        })
    ]
});
wavesurfer.initPlugin('timeline');

Adding and initialising a plugin dynamically:

var wavesurfer = WaveSurfer.create({
    container: '#waveform',
    waveColor: 'violet'
});
// adding and initialising a plugin after initialisation
wavesurfer.addPlugin(WaveSurfer.timeline({
    container: '#wave-timeline',
})).initPlugin('timeline');

Also a plugin can be destroyed like this:
wavesurfer.destroyPlugin('timeline');

Apart from that the public plugin API has not changed.
Standard plugin definition format
The definition object is being returned in a function, this allows us to pass in parameters during wavesurfer initialisation. A custom built plugin could just as well be an object passed in during initialisation.
A plugin definition now looks like this:
export default function(params) {
    return {
        // (required) plugin name, this is the namespace under which the instance of the
        // plugin instance is added to the wavesurfer instance
        name: 'myplugin',

        // defer the initialisation until later, can either be set
        // or depend on the params like this ...
        deferInit: params && params.deferInit ? params.deferInit : false,

        // static properties and methods are applied to the wavesurfer instance`
        static: {
            // example of a legacy initPlugin function,
            // it's  basically just an alias for this.addPlugins
            functionAttachedToWavesurfer() {
                // this refers to the wavesurfer instance
            },
        },

        // (required)
        // 1) plugin instance is instantiated and added to the wavesurfer
        //    instance under the "name" namespace
        //
        // 2) init is run:
        // - before the ready event: plugins now need to add a listener to the
        //   ready event if they need to do something after it has been triggered)
        // - after all the plugins have been instantiated, so init can for
        //   example check for the existence of this.regions
        instance: {
            // (required)
            init(wavesurfer) {
                // this refers to the instance of plugin at wavesurfer.myplugin
                this.params = params;
                this.wavesurfer = wavesurfer;

                this.methodOfThePlugin();
            },
            // (required)
            destroy() {
                // destroy this plugin
            },
            methodOfThePlugin() {
                console.log('Plugin haz been initialized!')
            }
        }
    };
}

Next steps
Depending on how this is received there would/could be a few next-steps

Updating documentation
Adding tests for the plugin system API methods
Adding generic tests for the plugins (if they follow the format)
Refactoring the code base to use es6 syntax (adding arrow functions, spread operator etc.)
We could consider refactoring multicanvas drawer into a plugin (any maybe even the mediaelement backend) since they are not part of the immediate core of the library to reduce file size.

This is a huge refactor and it's too breaking as it is now. I would have to make a lot of changes in my code to simply support ES6 (which my code does not use). -1 for now. This whole refactoring of the plugins should be done later, let's first focus on the core (and try to not break anything).

For example, you write:

jscs and jshint, which were currently being used for linting have merged as eslint, so it only made sense to change to that linter (as a webpack loader).

Let's start with a single PR for this task for example. If we want to merge this PR I think it have to be broken into many separate PRs, otherwise it's too much to review and too easy to break stuff.

This is awesome! I welcome all of the changes. @thijstriemstra is right, however, that the plugin refactoring it's a bit scary and could be done as a separate PR.
Nevertheless, I think we should dive in and work on the quality. This is a great base to start off. We could keep the 1.x version on it's own stable branch and merge this PR to master.

I think maintaining the 1.x branch and exchanging fixes between v2 and v1 would be a good idea. I think that is probably a good compromise.
I wanted to add a PR which as a whole is functional, that's why it turned out to be so big. I could split this PR into smaller ones which each render the bundle non-functional (but in the end result in changes identical to this PR) but I think this would not really be less overwhelming or less work (to review) than working with this monster-PR.
I honestly think it's pretty stable (and I would rather invest the time which I would spend on splitting into multiple PRs into debugging and enhancing the code), so I agree with you @katspaugh – I would rather use this PR as a starting point for further development.

Id say put it in a v2 branch first and have many release candidates before making it master

@mspae OK, cool! I've created a copy of master called next. Can you fix the conflicts and create another PR to this new next branch?

yes. will do!


Fix documentation

Reread doc to do a 2nd pass on it to clarify and fix some mark up problems

https://github.com/erlang/otp/pull/8308


Pin state change event

monitor multiple pins on their state change high or low.

Is this is a feature request? I see that state change is listed in the "Coming Soon" section of the Readme.
I too am interested in this feature. I'm not clear about implementation strategy, but if @AlexSartori can flesh out the design here, I would be willing to have a go at coding it.

Hi, thanks for the interest in my project. I was implementing it in a second branch ('statechange-events_beta'). You can take a lookat that, but I have not tested it, so I don't know if it works... Anyway, it simply uses a FileSystemWatcher object to monitor the changes of the file where the value of the pin is written by the OS, and it triggers events. @umasgn @rykerwilliams


Refactory the concepts “codec” to "cipher+transformation"

Since the concepts of Codec,Decryptor and Encryptor are hard to add new algorithm, the better abstraction should be cipher and transformation, the cipher also could be used as general cipher, not only for stream-base encryption.

https://github.com/intel-hadoop/chimera/pull/5 is the pull request for the refactory


[tests] Ensure that virt-handler watcher can reach the apiserver after outage

What this PR does / why we need it:
Do not only ensure that the readiness check, which tries to reach the
apiserver succeeds, but also ensure that at least the config watchers
resume their work. Due to repreated failed connects, they can have
accumulated some back-off penalty, therefore give it a bigger grace
period to resume.
Doing this gives us two things:

We also test that the watchers indeed reconnect
We ensure in the follow-up test, that config changes are updated within a reasonable amount of time

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Fixes one of our more flaky tests (https://storage.googleapis.com/kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flakefinder-2022-03-20-168h.html#row2) which is executed after the test in question.
The symptoms typically are something like
Tests Suite: [rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine [Serial]A mutated VirtualMachine given [test_id:3312]should set the default MachineType when created without explicit value expand_less	28s
tests/vm_test.go:133
Timed out after 10.001s.
Unexpected error:
    <*errors.errorString | 0xc002602700>: {
        s: "resource & config versions (52127 and 49900 respectively) are not as expected. component: \"virt-handler\", pod: \"virt-handler-m9jw2\" ",
    }
    resource & config versions (52127 and 49900 respectively) are not as expected. component: "virt-handler", pod: "virt-handler-m9jw2"
occurred
tests/vm_test.go:138

Release note:

NONE

/cc @enp0s3

/assign

/retest

/lgtm

/lgtm cancel
Test is not stable yet. At least it fails now on the correct test :D

/retest

@rmohr Looks like It still fails because tests.UpdateKubeVirtConfigValueAndWait waits only 10 secs.

@rmohr Looks like It still fails because tests.UpdateKubeVirtConfigValueAndWait waits only 10 secs.

Oh I get it now. Thanks @enp0s3 and @xpivarc

/retest


[ENHANCEMENT] Dark Mode For Card Elements

Will implement dark mode even on card elements that are missed out when dark mode is applied.

Not just change up the color it would be cool if you come up with new UI that looks cool in dark mode retaining the card format.

Sure sir, on it!

#189

@abhay-raj19 sir any updates?


out of heap hemory in V8 (Ineffective mark-compacts near heap limit)

My Environment

ArangoDB Version:        3.6.3-1 community
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:   Manual Start
Configuration:               16G memory 100G harddisk
Infrastructure:
Operating System:        centos 7.6
Total RAM in your machine:        16GB
Disks in use:        100G
Used Package:

Component, Query & Data
Affected feature:

AQL query (if applicable):

AQL explain (if applicable):

Dataset:

Size of your Dataset on disk:

20GB
Replication Factor & Number of Shards (Cluster only):

Steps to reproduce

Problem:
export data using aql in foxx; many geneaolgy success; only one fail, this one has 40K node, not the most.
Expected result:
how deal with this problem.

What is the approximate size of the failing request/response? V8 has a hard upper limit for string length, which is 1GB I believe (but there might be a lower default setting), and you might hit it when the reply is serialized to JSON.

@caozku Can you provide some more information please?


Add [rollouts] to .flowconfig

What is it?

What is it?

The final commit will have a much more descriptive commit message. I'll also document it.
Internal builds of Flow log a lot of perf info (we stub it out for OSS). So when we launch a new behavior (e.g. experimental.abstract_locations=true) we look at how the perf changes. But the repositories we test on also change over time, so it's not a great way to A/B test.
This [rollouts] feature of the .flowconfig will let us turn it on for 50% of our internal users. Then we can have cleaner data about the effects of a launched change.
I'm not sure how useful this will be for OSS users though.

I thought that it is env-related, like
[ignore]
(ignore_everything=true) *.js

$ export ignore_everything=true
$ flow check