Visiting the site after a while, the site doesn't properly work

I was navigating to the site using this link .
The solution for me was to delete the Cache Storage data for Fable.io

Ok, so this is on https://fable.io/repl/ which we tough to have fixed. 😅
@alfonsogarciacaro Any new ideas? ^^

There is no way to invalidate that cache? To timestamp it at the last action in site and if is older than 5 days to just wipe it out?

Well, in theory we should not have the cache system anymore.
It was introduce in this PR https://github.com/fable-compiler/repl/pull/17/files but we removed the service-worker in a later version because it was causing problem.
Can you please check if you have a service-worker installed when navigating to https://fable.io/repl/
For example, me I don't:

If you use Firefox here are the instruction on how to find it: https://developer.mozilla.org/en-US/docs/Tools/Application/Service_workers
If you use another browser I found the instruction by searching "see service worker firefox" on google.

Found one just in Edge:
Scope: https://fable.io/repl/
Registration ID: 15 (unregistered)
Navigation preload enabled: false
Navigation preload header length: 4
Active worker:
Installation Status: ACTIVATED
Running Status: RUNNING
Fetch handler existence: EXISTS
Script: https://fable.io/repl/service-worker.js
Version ID: 41
Renderer process ID: 10784
Renderer thread ID: 2
DevTools agent route ID: 6
Client:
ID: 647c1488-8771-4efa-8a9f-37bd410b566f
URL: https://fable.io/repl/#?code=PYBwpgdgBAygngZwC5gLYFgBQpJQGICGARgDZgB0AwsAE5hY7SGkXV3kBSCAkhCjaAbhoAIQEB3BGBpDcY4JOnkAKnHAJZ0AKIlUASwQALLFgD0pqNQAmYKEmBQCVgiCRQOMO2hAkCKBHYOeADEUABmtKh+KFZQyDR6EADmGpiowFYArmRQyt6+KFAAvFhQdmq2ygRJADwA5MoAfMVQNmRJfrbAYXFINAgAXL0JyQDaALpQAFRQozUACgQ0BKgAgjTLcI2TSylDwEQAVhNQALTNDSaYZWRuAMZ0nVAAFEjVQ1W1DY0AlC9hqCQQzwkWixDIMD6iSSfyGDWKpTKUFuwwCRVyYAAHkhyAAlMBJbJLLSYkB0BAIPTACAIPEErHPAACACIAN4AHSsAGoAL7Mn7kGA+PRIZ4AnEgmhRJA-RE3MBuXZo8KA8gAcQV60JqEgSAQz1l1yRbyS5F4ADdgABrMDPeIIAA0jhoKUNZgsABkRVAiIkrNDUuksjkvW4SkakBUoAAJJCoEh5VA+J7oxL8MIEO62SCxcxQea+LOGYAkGwyTCIlGGOMkD75Toqao1WPxxPJlDNVNJ2hIACyaCI0igzOrSBAg3MmQgICtpruwFQphIItO1fjAH4g9kwMzKwqoHQIGWXkCYzW2wUwH9nmBazHlL2PTo0LqfkMp96uyAe-3UIOaMOo7jgMk7TrO5Dzouy5IKuNabhk267hWmB5jo+hGFA4gioYUChlgW45PMAhJMsqAIkaKJYUghihi8ehWEM8TQteZLACRKxDERbGkfUuxOnUQa3vxqAIEkTqhuQLYJvWHZvvmxE8XUfFQAJGRCSpIlibhIqSeeMlgJ2cpIiit4tPIig0OQAAiC7kFYwB3JkOp8OQSQKs+zlICIcDcFYzz0W6RpIsi+5SEgkJPIJJCtAYIB+HcOHhsFyUhW4KBJpe+IINkYbydxKzkOaehgOIUCsexZFRTFCBxUgCVGSlEmHse6XtmAWU5VAt5XClXEVeQVGGDACoRYUYWjbY5WkVcea8CKegEMuABetjUat+mOEejhQIYt7gOWVY1i0F4Ng8YBPBJa4kFckbgFAWjmrqVQuvug2Ijqf5DtRBjkAAaotmS2OiryGAYUADOuzTRg+Hq8CAmRIB5r6FQD9DIXmqwgCAWC3bYvZqdFSVIqyUD-SQgPg8M0JQDyN1Rr2onkcFAA+liGAQyRgGTFPdFTyRXCiiTegaLQk9zQPDgA6rQpbMjTTqUKgVjkBA1Jo1gKKZCAziFM8mkDAzMIvFFBsE38RNlNKCVQJpmHYUZrOUOznPi1AEAla75wNcTNsE3b1Gk6jLTu+Irs8grSsq2rAv7kVJW+201W1dbRNXVAAAkzJZ1gNT+uaUB3L4FJFMyUSJKc858AQiTSMyjSIjUiTw-cRcICXTcI0hwXmqjRSslFf2o7TQVQIyNpwFrfdhFOLxgOaQwPa+Zz1yPZRz+QbwvTi4ve8zzROxzbk76vUB70n8WGDyK8NzVHONNGt4kA4-cE4P5NgDyACENSmLfEArz-POK8s5ISwH1Ui5BUBWnASsKAQs3Bax1rYOO4gsBnxgagAa2FaLMlvOhQwpwXAgCQughSBUaBTiwEAA&html=DwCwLgtgNgfAUHUBTAhgE3gAm54ElgqbhgAOAtEgI4CuAlgG4C8A5AMID2AdmEj+QBUAnqSQtMAY268erXgA8wAenDQA3JJAoATgGcCTGmABm5ABwt4wFagwJgAIw5ohkqCl26mAIhSkKUjwodFxI2t5YOMBojJh0aD5IUBB0uiDkfqQR1jEMVkpOLvCIKpCwcEA&css=BYFwtgNgNAsAUAIwPYBMCeACA3vDeMBmSAdiALQDOAlgF4CmAXBgIwBsADgB4Dc8AvvHgA6MAEMqxMgGMSIccToAnbLnwoqFdhFFomBCHR6q8AdyooQwJswAMNgKS84+DMDpUA5qGt3HxjABWAK4UIFQEaNKydKRMUjEgSk4uohCeklSJYBRxCUn++oZk6op0UmEkcUgQQWDETgJwwhLsQSAqzvjsoijqxB5MQgBMAKylYMn4RKSUtIwsHEadpuaWTKM2XJN4YooeEmTIICBIYNbjDfBAA
Log:

Hum, you should delete it because we don't use it anymore.
But then it doesn't explain why the other browsers  broke. Next time, it happens could you please take a look at the console and see what error is reported.
Because we don't know if this is a cache problem or something else then.

@MecuSorin If you didn't visit the repl for a while, it may have happened the service worker was still active in your browser. We removed it some months ago because of these issues. Hopefully the next time we update the repl you won't have the same issue, could you please report if you see it again?

Closing this as we removed the service worker some time ago. Please feel free to reopen if you still have problems. Thanks!


SAK-47025 Student-uploads folder should be owned by admin

The first student to upload a file through the CKEditor using the direct-uploads
feature will be the owner of the student-uploads folder. This allows that
student to see all of the contents of that folder in Resources.

I'm totally disagree that these files should be stored in the "Content" tool of a site.
These files should be stored inside "attachments" folder in the Content Hosting Service.
Similar to this work from @ottenhoff : https://sakaiproject.atlassian.net/browse/SAK-46414

As I understand the upload of files via CKEditor are not deliverables in the way that submission attachment would be, maybe we need some clarification around this?

Now the folder has been created as admin. Testing on our 22.x branch.
I think it's not too difficult to guess where are the images of your colleagues... security problem

@jesusmmp lets not get to hasty there is a prop to control this feature content.direct.upload.enabled it maybe that we turn it off until we are satisfied with how this works for everyone?

I thought SAK-47024 was going to address the storage location and move student content to attachments (if that's the agreed upon location). This PR is just to fix the bug that it was using the current user's account as the creator of the student-uploads folder.

@davidpbauer @ern Then, we can merge this PR and create a new jira to disable it until SAK-47024 is resolved.


Fix(filewatcher): handle removed directories #8800

Description
When setting up manual recursive watching on folders (as is the case under Linux), the watching thread should not exit if a directory no longer exists. This is likely to occur within build output directories and it should not be the cause for interrupting the daemon.
Likely fixes https://github.com/vercel/turborepo/issues/8800 and https://github.com/vercel/turborepo/issues/8491
Testing Instructions
Unit tests suite
cargo test -p turborepo-filewatch
Test building of GitBulter
(Within a Fedora Linux VM)

Prerequisites

sudo dnf check-update
sudo dnf install webkit2gtk4.1-devel \
  openssl-devel \
  curl \
  wget \
  file \
  libappindicator-gtk3-devel \
  librsvg2-devel
sudo dnf group install "C Development Tools and Libraries"
curl --proto '=https' --tlsv1.2 https://sh.rustup.rs -sSf | sh

Obtain test project sources

git clone https://github.com/gitbutlerapp/gitbutler
cd gitbutler

Replace turbo with the turbo binary built from this branch, as an example:

diff --git a/package.json b/package.json
index 394d0f8e9..8f46a08e1 100644
--- a/package.json
+++ b/package.json
@@ -11,7 +11,7 @@
                "dev:ui": "pnpm --filter @gitbutler/ui storybook",
                "dev:web": "turbo watch --filter @gitbutler/web dev",
                "dev:desktop": "pnpm tauri dev",
-               "dev:internal-tauri": "turbo watch --filter @gitbutler/desktop dev",
+               "dev:internal-tauri": "/home/parallels/src/turborepo/target/debug/turbo watch --filter @gitbutler/desktop dev",
                "package": "turbo run package",
                "test": "turbo run test --no-daemon",
                "test:watch": "pnpm --filter @gitbutler/desktop run test:watch",

Build project

pnpm install
pnpm tauri dev

Hi @NicholasLYang - I noticed your comment here https://github.com/vercel/turborepo/issues/8765#issuecomment-2233469466 and also your name in git history and thought ping you on this PR for some feedback.
Background
Normally I build our project on Mac where we experience no issues, however recently had the need to build it in a Linux VM and noticed the turbo filewatcher misbehaving.
Subsequently, I noticed that other people were also struggling to build GitButler (a turbo project) on Linux (https://github.com/gitbutlerapp/gitbutler/issues/5039). With some more searching I discovered this issue https://github.com/vercel/turborepo/issues/8491 from another turbo project, as well as these two https://github.com/vercel/turborepo/issues/8800 https://github.com/vercel/turborepo/issues/8765
I did some manual with the projects mentioned but of course I wanted to reach out to see if there might be something I have not considered here.

Can confirm, this seems to have allowed me to run turbo watch on my Nix box finally! :partying_face:

Hi, I am one of those affected by the issue described here

How do I test this patch on my monorepo? Sorry to ask, as I don't know how to apply these changes to my exact repo.

Hi, I am one of those affected by the issue described here
How do I test this patch on my monorepo? Sorry to ask, as I don't know how to apply these changes to my exact repo.

Hey! If you have things set up you could build turborepo from source https://github.com/vercel/turborepo/blob/main/CONTRIBUTING.md using this branch and then in your on own project's build setup you can replace the references to turbo with the full path to the binary built from source.
Perhaps there is a way to create a binary with CI here, but as an external contributor I don't have permission to trigger CI

Allow CI Workflow Run

[ ] approve CI run for commit: f9e08fc34f1925e1176f8e6a64003e713e08db11

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

@dBianchii I'll try to get this merged ASAP so we can release a canary with it


fix: useMMKVStorage nextValue as a function

Hi, I upgraded from 0.6.12 to 0.7.2 after you closed #221 and I can confirm that the debugger is now working.
However since the bump I'm encountering type errors with hooks when setValue is a function. As it seems to still be supported this PR updates the type signature.

Published in v0.7.3! Thanks for the PR


zram: modprobe: ERROR: could not insert 'zram': Invalid argument

Describe the bug
After update zram-reloader.service can't properly reload zram module. Reproducible only with nixos-rebuild switch.
Job for zram-reloader.service failed because the control process exited with error code.
See "systemctl status zram-reloader.service" and "journalctl -xeu zram-reloader.service" for details.

journalctl -eu zram-reloader.service
Nov 17 14:42:19 Fujitsu-AH531-Laptop systemd[1]: Stopping Reload zram kernel module when number of devices changes...
Nov 17 14:42:19 Fujitsu-AH531-Laptop systemd[1]: zram-reloader.service: Deactivated successfully.
Nov 17 14:42:19 Fujitsu-AH531-Laptop systemd[1]: Stopped Reload zram kernel module when number of devices changes.
Nov 17 14:42:23 Fujitsu-AH531-Laptop modprobe[309454]: modprobe: ERROR: could not insert 'zram': Invalid argument
Nov 17 14:42:22 Fujitsu-AH531-Laptop systemd[1]: Starting Reload zram kernel module when number of devices changes...
Nov 17 14:42:23 Fujitsu-AH531-Laptop modprobe[309486]: modprobe: ERROR: could not insert 'zram': Invalid argument
Nov 17 14:42:23 Fujitsu-AH531-Laptop systemd[1]: zram-reloader.service: Main process exited, code=exited, status=1/FAILURE
Nov 17 14:42:23 Fujitsu-AH531-Laptop systemd[1]: zram-reloader.service: Failed with result 'exit-code'.
Nov 17 14:42:23 Fujitsu-AH531-Laptop systemd[1]: Failed to start Reload zram kernel module when number of devices changes.
Nov 17 14:42:23 Fujitsu-AH531-Laptop systemd[1]: Starting Reload zram kernel module when number of devices changes...
Nov 17 14:42:23 Fujitsu-AH531-Laptop systemd[1]: zram-reloader.service: Main process exited, code=exited, status=1/FAILURE
Nov 17 14:42:23 Fujitsu-AH531-Laptop systemd[1]: zram-reloader.service: Failed with result 'exit-code'.
Nov 17 14:42:23 Fujitsu-AH531-Laptop systemd[1]: Failed to start Reload zram kernel module when number of devices changes.

Steps To Reproduce
Steps to reproduce the behavior:

Enable zram and switch to 2fa862644fc15ecb525eb8cd0a60276f1c340c7c;
Reboot;
Then switch to 931ab058daa7e4cd539533963f95e2bb0dbd41e6;
See the logs.

Expected behavior
Successful module reload.
Screenshots
None.
Additional context
None.
Notify maintainers
@danbst
@lukegb
Metadata
❯ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.14.16-lqx1, NixOS, 21.11 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.5pre20211007_844dd90`
 - channels(root): `"nixos-21.11pre323790.5f0194220f2"`
 - nixpkgs: `/nix/store/66zlifjkdndc92mg0wbbcickzwwrvkjp-source`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
  - zramSwap.*
# a list of nixos modules affected by the problem
module:
  - config/zram.nix

i assume a reboot fixed this? its probably because the booted kernel and the updated kernel versions mismatched
i suspect that this line is causing it https://github.com/NixOS/nixpkgs/blob/34fdd877ea9cca8bc21edf557ae2ed7690a29bf3/pkgs/os-specific/linux/kmod/default.nix#L7
/run/current-system/kernel-modules when we should only look in /run/booted-system/kernel-modules

i assume a reboot fixed this?

Yes, after reboot everything works fine.

is uname -r different from what it was in nix-info Linux 5.14.16-lqx1?

No.
❯ uname -r
5.14.16-lqx1

I can't find zram in these paths:
~ on  laptop [✘!?]
❯ find /run/booted-system/kernel-modules/ -iname "*zram*"

~ on  laptop [✘!?]
❯ find /run/current-system/kernel-modules/ -iname "*zram*"

~ on  laptop

find doesn't follow symlinks
fd with -L does
fd -L "zram" /run/booted-system/kernel-modules
/run/booted-system/kernel-modules/lib/modules/5.14.14-xanmod2-cacule/kernel/drivers/block/zram
/run/booted-system/kernel-modules/lib/modules/5.14.14-xanmod2-cacule/kernel/drivers/block/zram/zram.ko.xz

https://github.com/NixOS/nixpkgs/pull/149244

Progress of the pr can be tracked at https://nixpk.gs/pr-tracker.html?pr=149244


[Icon Request]Payeer

Please, add Payeer to this awesome project. :-)

can't wait for it to be added


Allow audit_log_enabled to be configurable via values

I'd like to be able to switch audit_log_enabled via a configMap. I know that this is possible via environment variable as well. I was wondering if there's a reason why it's not available to do with the config map?

No reason other then just not getting implemented yet. Will prioritize this.

No need. I can make the update and create a PR by the end of the week. Thanks for the feedback.

@mcrors That would great.


Escape issues with elements in Dialog

Bug type
Component
Component name
MudDialog
What happened?
Recently many components got key bindings including Escape keys. These will have to prevent propagation to avoid Dialog closing when the key stroke is intended for the child component of the Dialog:

[x] MudSelect (already taken care of by #3393)
[ ] MudAutocomplete
[ ] MudCheckBox
[ ] MudPicker
[ ] MudSwitch

Expected behavior
Dialog should not close on Esc if these elements have focus. See #3393 as a template solution.
Reproduction link
TODO
Reproduction steps
TODO
Relevant log output
No response
Version (bug)
6.0.2
Version (working)
No response
What browsers are you seeing the problem on?
Other
On what operating system are you experiencing the issue?
Other
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Great thing @henon @mckaragoz

@MattChique do you agree with the UI design decision that if an element has focus Esc should not propagate? It is actually in contrast to what you did in your PR, where ESC on a focused Select will close the Dialog. Now we are not sure what is better.

Hm, no. An focused input could propagate esc, but only after it handled esc itself. If you have a dialog with inputs, how should the dialog be closeable if every input stops esc propagation.
I also looked at frameworks like vue, they behave like this.

I think each approach has pros and cons. Closeable dialog while focused input is the most fluent approach, but users may accidentally press esc twice, this time we may lost the all progress in dialog. If we choose the approach, we need to add some cancellation option for closing.
Actually i prefer the both first and second approach. Yes second esc key should close the dialog, but a better experience, first key should lost focus on input component, so users can undetstand that with the first esc they going out of the input and now they can close the dialog. Otherwise it is strange that closing dialog while you see a focused border style of an input. But how can we lost focus on first esc key?

@mckaragoz We discussed yesterday, that using Esc key in checkboxes and switches is not a good idea and should be changed. And the problem of accidentally pressing Esc twice in select Select must be handled in the application if necessary, not in MudBlazor. In many other toolkits I have worked with it is the same. If you press Esc the window will close, you can loose your input. All we need to do is add a callback to dialog so that applications can suppress the closing if there are unsaved changes.
So I need to roll back what I said above. The rule should be that Picker and Autocomplete should stop Esc propagation only if their dropdown is open, Select does that already. Switch and Checkbox should not bind Esc. The checkbox can use Del key to go to false or use Backspace to loop between null and false for tristate.

All we need to do is add a callback to dialog so that applications can suppress the closing if there are unsaved changes.

I already accomplished that for applications when I refactored the dialog service and related stuff.
I think there is already an example in the tests for it somewhere?

I already accomplished that for applications when I refactored the dialog service and related stuff.
I think there is already an example in the tests for it somewhere?

Yes i also have a cancellatiom mechanism in my app. But esc key a bit different, it automatically calls Close() so we need to add something in the library and let user to control closing process.

I already accomplished that for applications when I refactored the dialog service and related stuff.
I think there is already an example in the tests for it somewhere?

Yes i also have a cancellatiom mechanism in my app. But esc key a bit different, it automatically calls Close() so we need to add something in the library and let user to control closing process.

As I was saying. You have complete control over the closing of the dialogs and wether you want to cancel it or not.
In our app we have that exact mechanism that detects if a dialog has unsaved changes and if so, it prevents the dialog from closing and displays an infobox.
We can still add a more accesible feature but by registering a custom dialog service the desired behavior is also easily achievable.


readme: Add screenshots to readme.

Fixes:

https://github.com/zulip/zulip-mobile/issues/3322
which is also the last point from this one https://github.com/zulip/zulip-mobile/issues/3433

Added screenshots of the ios application to the README.md. I chose to add only these ones because the Android ones look the same, except from the toggles.

Thanks @alexandraciobica ! These look great.
For the README, a few comments:

Let's keep it to one row, of two or three screenshots.
I think one of the unreads screen, and one of the message list, will be good. We can skip the "All messages" message list (that's a less commonly used feature) and the settings screen.

One of those can be in light mode and one in dark mode.

I think I'd prefer to put the image(s) themselves in the repo, so it's self-contained.
Can you experiment with different compression settings and try to make the images smaller? One of them is currently 1.9 MB; our whole tree is 6.9 MB. This is mostly solid colors and some text (no big detailed photos), so I'd hope it can compress a lot better without losing much image quality. If we can't manage that, though, maybe it'll be best to leave the images outside the repo after all.

I managed to reduce the file sized to 96kb and 77kb respectively. And I think the quality is good enough too. I added them below so you can see the quality.
Where should I add them in the repo? Directly in the root, where also the readme is?
@gnprice

Thanks, @alexandraciobica! I'm closing this because the app looks different now; for example, we have a different primary color (#4544).


MacOS Monterey issue

Hi,
Just tried to install v0.3.0 from homebrew with OSX 12.2.1 and gltf or .glb files don't display.
When asking version with "brew list --versions gltfquicklook" , it returns nothing...

After many attempts, I can see .glb files but no .gtfl with .bin

Yep, I'm experiencing the same issue.

same here; haven't managed to get it to display anything

I have a .glb file also, but no quicklook. 12.4 here.


rtl TextInputs

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/22889579-rtl-textinputs?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github).

Text reshaping and rtl script support already has issues opened, closing this.


Merge main branch into dev-1.31

This PR syncs the dev-1.31 branch with the main branch to keep the dev-1.31 branch up to date.
cc: @chanieljdan @salaxander @MaryamTavakkoli @hacktivist123 @LaurentGoderre

/retitle Merge main branch into dev-1.31

/lgtm

/approve

sync looks good
/approve


Not able to target uaac url

Hi,
I have deployed cloudfoundry following this approach and it is working for me.
cf api https://api.local.micropcf.io --skip-ssl-validation
Setting api endpoint to https://api.local.micropcf.io...
OK
API endpoint:   https://api.local.micropcf.io (API version: 2.44.0)
User:           admin
Org:            micropcf-org
Space:          micropcf-space
But when I try to use the uaa url and try to target the uaa url, it fails.
uaac target https://uaa.local.micropcf.io --skip-ssl-validation
failed to access https://uaa.local.micropcf.io: Net::ReadTimeout
I am sitting behind a proxy but that doesn't restrict me when accessing cf api. Is it a problem with cf-uaac proxy settings ? What am I missing here?

@subhankarc Any progress? I'm also facing the same issue..

Hi @subhankarc and @alaviamir.
I can confirm that this works for me (without a proxy) from both outside of and inside of the MicroPCF VM. @alaviamir, is your host also behind a proxy?

@alaviamir Nope. @sclevine I have tried setting up no_proxy for the same but with no luck.

@subhankarc Any luck with the latest version of PCF Dev, or is this still an issue for you?

Closing due to inactivity. Feel free to re-open if this issue persists.


apache-md5 and apache-crypto

Can somebody detail the reason for using apache-md5 and apache-crypt instead of the standard node crypto.hash()  functions?
Is there any compatibility issue against the RFC HTTP Digest using one or the other ?

apache-md5 and apache-crypt are used for compatibility reasons with htpasswd utility ONLY for Basic Access Authentication.
Digest Access Authentication is not using those libraries anyhow.

OK. thanks
So then , maybe splitting module would make sense for those of us that only require digest auth  and ( like me) are used to work with a small as possible dependency tree

I will leave it like this, as it is simpler from usage perspective.

ok. no problem, just an idea


[DOM] Floating element flickers between different placements on smaller screen sizes

On small screen sizes when using either the flip or autoPlacement middleware alongside autoUpdate, the floating element will flicker between different placements without ever settling on a position.
https://user-images.githubusercontent.com/40346716/187103206-2c44e093-d6c0-4837-93b5-45773c05d6d2.mov
I think potentially this could be happening because of the ResizeObserver observing the floating element (which is definitely important to keep). When the position is updated on a small screen like this, the floating element size also changes, causing another update moving it again, causing another resize update and so on.
To reproduce

Visit https://codesandbox.io/s/async-fire-1382wl?file=/src/App.js:327-337&resolutionWidth=399&resolutionHeight=416
Scroll down
The floating element (text) will flicker between top and left positions.

It's not the ResizeObserver but the way the CSS layout acts upon the floating element when it changes placement/position coords.
The <body> element does not span the entire width of the container if you check DevTools, is the floating element's offsetParent, which is likely the root of the problem.
Giving position: relative to the width: "auto" container removes the flicker, as the floating element's width can correctly adjust for different placements.

Closing as in general this problem needs to be worked around by ensuring the floating element does not get resized due to the CSS layout when it changes placement.
This can involve making an ancestor element its offsetParent by giving it position: relative or such


Quidem release 0.9

Release quidem version 0.9.

Fixed in 682c274; the release hash is 8f28826 and release notes are here.


Manually setting z-index from Vue

Setting Z-index similar to color setting from Vue.

@viren-singh great! Everything working fine. Thanks for contributing.


#533 Add autocompletion of exit in ide shell

Closes #533
Implements:

When in ide shell 'exit' is now suggested when e is typed and tab is pressed
Pressing enter successfully aborts the shell

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

0 of 0   changed or added relevant lines in 0 files are covered.
38 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.04%) to 66.767%

Files with Coverage Reduction
New Missed Lines
%

com/devonfw/tools/ide/commandlet/ShellCommandlet.java
38
3.7%

Totals

Change from base Build<PHONE_NUMBER>6:
-0.04%

Covered Lines:
6259

Relevant Lines:
9030

💛  - Coveralls


Doesn't add quotes around ASN from SPI view

Elasticsearch version: 2.4
Moloch version: 0.18.2
OS name and version: Ubuntu 16.04
How was Moloch built/installed: (rpm, deb, singlehost built, ...) easybutton
Provide logs, stack traces and steps to reproduce:
When including or excluding an ASN name from SPI, it doesn't put quotes around the entry.  This causes a search error.
 Error retrieving data: Error: Parse error on line 1:
...& asn.dst != AS7743 JPMorgan Chase & Co.
-----------------------^
Expecting 'EOF', '&&', '||', ')', got 'STR'

it does appear to work (it adds the quotes) when doing it from the session screen

Seems to also apply to the quic useragent in SPI and the http useragent in both SPI and Sessions.  Trying to think of what other fields may have spaces in them...

In case this is a per field fix, here are some more
cert issuer cn
cert subject on
cert issuer on
email asn
email content-type
email subject
email x-mailer header
ssh version
http xff asn

👍  Thanks for the details!


can't add an application to a service..

create an application, create a service, go to add 'Add Components', under object Assignment
select 'Application', and it's empty; the application created 1st doesn't show up.
this is the latest version from pypi, using netbox-3.2.1

That fixed it.  thanks!


Support non-conforming meshes with BlockNonlinearForm and ParBlockNonlinearForm

This PR adds support for support non-conforming meshes with BlockNonlinearForm and ParBlockNonlinearForm. I made changes to ex19 and ex19p to provide test cases.
I changed the name and return type of an internal function in BlockNonlinearForm to reflect the functionality change.
The changes work in a dependent code as well.
Obligatory GLVis snapshot

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#1744
@jandrej
@tzanio
@jakubcerveny + @jamiebramwell + @mlstowell
09/08/20
⌛due 09/22/20
⌛due 09/29/20

LGTM

LGTM

Merged in next for testing...

Re-merged in next.

Re-merged in next.


Move some commands code into pkg

There is a bunch of code sat in the cmd/* directories that should really be in a pkg/cmd directory - just needs a bit of refactoring.
Along with this, we should consider a Makefile for building the binary locally should people want to head down that route.

Fixed in #14


[qt5-declarative] Build error with arm64 on macOS crosscompiled on x64 since #26354

Host Environment

OS: macOS

To Reproduce
Steps to reproduce the behavior:
./vcpkg install qt5-declarative:arm64-osx
Running on a x64 hardware
Failure logs
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:131 (message):
    Command failed: /usr/bin/make -j 4
    Working Directory: /Users/runner/mixxx-vcpkg/buildtrees/qt5-declarative/arm64-osx-min1100-dbg
    See logs for more information:
      /Users/runner/mixxx-vcpkg/buildtrees/qt5-declarative/package-build-arm64-osx-min1100-dbg-out.log
      /Users/runner/mixxx-vcpkg/buildtrees/qt5-declarative/package-build-arm64-osx-min1100-dbg-err.log

Additional context
This is the failing Run on GitHub:

https://github.com/daschuer/vcpkg/actions/runs/3868940153

Her it works again after reverting #26354:

https://github.com/daschuer/vcpkg/actions/runs/3873496046

The issue is that the build flags are applied twice. During the build of qt5-base the flags are collected in qtconf:
 -qtconf /Users/runner/mixxx-vcpkg/buildtrees/qt5-declarative/arm64-osx-min1100-dbg/qt.conf
But due to the change in configure_qt.cmake they are applied again in collision with the original Qt flags. Wen calling https://github.com/daschuer/vcpkg/blob/arm64-osx-min1100-qt5.15.7/ports/qt5-base/cmake/qt_build_submodule.cmake#L12

Unfortunately the logs are too long to attache. You find them in the workflow links above. Her only the relevant lines:
cd src/ && ( test -e Makefile || /Users/runner/mixxx-vcpkg/installed/x64-osx-min1012/tools/qt5/bin/qmake -o Makefile /Users/runner/mixxx-vcpkg/buildtrees/qt5-declarative/src/5.12.5-197f948223.clean/src/src.pro CONFIG-=release CONFIG+=debug QMAKE_CC=cc QMAKE_CXX=c++ QMAKE_AR=ar QMAKE_RANLIB=ranlib QMAKE_STRIP=strip QMAKE_NM=nm QMAKE_RC= QMAKE_MT= QMAKE_AR+=qc QMAKE_LINK=c++ QMAKE_LINK_SHLIB=c++ QMAKE_LINK_C=cc QMAKE_LINK_C_SHLIB=cc 'QMAKE_CFLAGS_DEBUG+=-fPIC -mmacosx-version-min=11.0 -arch arm64 -isysroot /Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk -mmacosx-version-min=11.0 -g' 'QMAKE_CXXFLAGS_DEBUG+=-fPIC -mmacosx-version-min=11.0 -arch arm64 -isysroot /Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk -mmacosx-version-min=11.0 -g' 'QMAKE_LFLAGS+=-arch arm64 -isysroot /Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk -mmacosx-version-min=11.0' 'QMAKE_LFLAGS_SHLIB+=-arch arm64 -isysroot /Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk -mmacosx-version-min=11.0' 'QMAKE_LFLAGS_PLUGIN+=-arch arm64 -isysroot /Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk -mmacosx-version-min=11.0' CONFIG-=shared 'CONFIG*=static' -qtconf /Users/runner/mixxx-vcpkg/buildtrees/qt5-declarative/arm64-osx-min1100-dbg/qt.conf ) && /Applications/Xcode_12.4.app/Contents/Developer/usr/bin/make -f Makefile

c++ -stdlib=libc++ -arch arm64 -isysroot /Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk -mmacosx-version-min=11.0 -headerpad_max_install_names  -arch x86_64 -Wl,-syslibroot,/Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk -mmacosx-version-min=10.12 -Wl,-dead_strip<EMAIL_ADDRESS>-o ../../bin/qmlcachegen .obj/qmlcachegen.o .obj/resourcefilter.o .obj/generateloader.o .obj/resourcefilemapper.o   /Users/runner/mixxx-vcpkg/buildtrees/qt5-declarative/arm64-osx-min1100-dbg/lib/libQt5QmlDevTools.a /Users/runner/mixxx-vcpkg/installed/x64-osx-min1012/tools/qt5/lib/libQt5Bootstrap.a -framework Foundation -framework CoreServices

make[1]: *** [sub-qmlmin-make_first] Error 2
ld: warning: ignoring file .obj/main.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /Users/runner/mixxx-vcpkg/buildtrees/qt5-declarative/arm64-osx-min1100-dbg/lib/libQt5QmlDevTools.a, building for macOS-arm64 but attempting to link with file built for macOS-x86_64
ld: warning: ignoring file /Users/runner/mixxx-vcpkg/installed/x64-osx-min1012/tools/qt5/lib/libQt5Bootstrap.a, building for macOS-arm64 but attempting to link with file built for macOS-x86_64
ld: entry point (_main) undefined. for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [../../bin/qmlimportscanner] Error 1
make[1]: *** [sub-qmlimportscanner-make_first] Error 2
ld: warning: ignoring file .obj/qmlcachegen.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file .obj/resourcefilter.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file .obj/generateloader.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file .obj/resourcefilemapper.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /Users/runner/mixxx-vcpkg/buildtrees/qt5-declarative/arm64-osx-min1100-dbg/lib/libQt5QmlDevTools.a, building for macOS-arm64 but attempting to link with file built for macOS-x86_64
ld: warning: ignoring file /Users/runner/mixxx-vcpkg/installed/x64-osx-min1012/tools/qt5/lib/libQt5Bootstrap.a, building for macOS-arm64 but attempting to link with file built for macOS-x86_64
ld: entry point (_main) undefined. for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [../../bin/qmlcachegen] Error 1
make[1]: *** [sub-qmlcachegen-make_first] Error 2
make: *** [sub-tools-make_first] Error 2

You see concurrent -arch arm64 and -arch x86_64 in the linker code which cause the failure.

My workaround is to use the a custom configure_qt from qt_build_submodule that doe not add any additional flags except qt.conf.
https://github.com/daschuer/vcpkg/commit/7cbfaed7e1b7d3a12aaa2122e4148387f37b1b2e
Could this be an upstream solution?

 Is x64-osx your host triplet? If yes i assume the wrong qt.conf is used?

Also are you sure that your qt5-base build is build for the correct architecture? It might be because we apply the flags now but I think that the qt.conf generated for arm64-osx does not know about that. which means qt itself does not know about it.

Also are you sure that your qt5-base build is build for the correct architecture?

I mean there is a post build check that verifies that.

This is my target triplet:
https://github.com/daschuer/vcpkg/blob/arm64-osx-min1100-qt5.15.7/overlay/triplets/arm64-osx-min1100.cmake
This is my host triplet:
https://github.com/daschuer/vcpkg/blob/arm64-osx-min1100-qt5.15.7/overlay/triplets/x64-osx-min1012.cmake
The it uses the qt.conf from the target triplet:
`/Users/runner/mixxx-vcpkg/buildtrees/qt5-declarative/arm64-osx-min1100-dbg/qt.conf``
The arch setting is comming from here:
https://github.com/microsoft/vcpkg/blob/master/ports/qt5-base/portfile.cmake#L278
and form vcpkg_configure_qmake.cmake via QMAKE_LFLAGS
qmlcachegen is a build tool, which requires the host triplet. This was working before the blamed patch
It receives the wrong flags form:
'QMAKE_LFLAGS+=-arch arm64 -isysroot /Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk -mmacosx-version-min=11.0'
And uses in addition the concurrent fags correctly configured via qt5-base:
-arch x86_64 -Wl,-syslibroot,/Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk -mmacosx-version-min=10.12
The issue is only one in case of cross compile, but even in the native case the fags are applied twice, which should not happen.
All Qt modules needs the same set of flags. This is realized by collecting them for qt5-base and reuses them for the submodules. If we apply additional flags to submodules it brakes that trick
Conclusion: We must only apply the flags from cmake once, during configuring qt5-base. Submodules can rely on qt.conf.
Implemented in https://github.com/daschuer/vcpkg/commit/7cbfaed7e1b7d3a12aaa2122e4148387f37b1b2e

in the native case the fags are applied twice, which should not happen.

That is a consistency check. QMAKE_LFLAGS come from the toolchain while qt.conf comes from the qt5-base build itself using the toolchain flags. From what you tell me: You target arm64 and the host is x64 -> so the x64 flags are wrong. This is a bit strange since the qt.conf for the target (CURRENT_INSTALL_DIR) should be passed to qmake.

Submodules can rely on qt.conf.

From your description the qt.conf is the one bringing the wrong x64 flags since your target is arm64. vcpkg should only ever build for the specified target triplet. The host is pulled in via a host dependency with the host target triplet.
It could very well be that qt5 requires more work to correctly reflect vcpkgs host/target style.

You target arm64 and the host is x64 -> so the x64 flags are wrong.

No, x64 is correct in this case, because in that particular call, we link a build tool that requires host architecture.

It could very well be that qt5 requires more work to correctly reflect vcpkgs host/target style.

Yes, from that point of view we need to split qt5-declarative into qt5-declarative and qt5-declarative-tools.
The following tools are effected:

qmllint
qmlmin
qmlimportscanner
qmlcachegen

But that fixes only a symptom of the root cause. Even if this is fixed we still have duplicated flags in the command line.
This is clearly introduced by the blamed PR and need to be fixed as well. If you like my proposal for it, I will issue a PR
Do you?

Yes, from that point of view we need to split

No need to split (see qt6). Just declare a host dependency on itself. That being said I never actually designed qt5 to be cross buildable and the fact that it worked was just by coincidence and not design.

Even if this is fixed we still have duplicated flags in the command line.

That did not create the error. As I said it is a consistency check and the flags should be equal. If at all the flags in the qt.conf needs to be removed since they are related to the toolchain used for qt5-base instead for qt5-declartive (which would still leave you with the wrong flags for your use case).

That did not create the error.

At least removing the double flag generation makes the port working again. That solves the error that beaks the port.
The case that the port builds host tools is orthogonal. There are by the way a few other ports building host tools.

As I said it is a consistency check and the flags should be equal.

I strongly disagree. I have never heard of a practice to apply command line flags twice as a consistency check. Normally the last flag wins there is no checking facility in the compiler.
But we should pass the flags correctly in the first attempt and not rely on this compiler nature.
In addition each port should be able to apply it's own special case handling regarding flags. In case of Qt this is done only once in the qt5-base ports. The other ports are re-using this. Applying the flags again blindly in the submodules without the sanity checks breaks this concept.

Aside from this discussion, what are your plans to make qt5-declatative build again?

Aside from this discussion, what are your plans to make qt5-declatative build again?

I don't do cross builds and such issues need to be resolved by a person doing cross builds. Most of the qt5 stuff was designed before --host-triplet existed and was never meant for cross builds. I mean I can remove the flags from qt.conf but that probably won't help your case.

There are by the way a few other ports building host tools.

it is against vcpkg policy to do so. You need to declare a host dependency and pull in host tools in that way.

... apply it's own special case handling regarding flags ....
.... Normally the last flag wins....

That is how it should be designed.

But we should pass the flags correctly in the first attempt and not rely on this compiler nature.

Unfortunately, that is not always possible.

I mean I can remove the flags from qt.conf but that probably won't help your case.

That will not work, because in qt5-base uses the qt.conf as well which it is properly configured from the flags discovered from CMake. It does not use vcpkg_configure_qmake.cmake(). Please explain why you propose to alter the established way how Qt is build, instead of removing one set of the recently introduced flags and carry on?

That is how it should be designed.

OK, but instead of design it the desired way, https://github.com/microsoft/vcpkg/pull/26354 applied the flags twice.
This is also an issue in non crosscompile builds using the x64-windows standard triplet like here for windows:
Before https://github.com/microsoft/vcpkg/pull/26354:
	cl
	-c -nologo -Zc:wchar_t -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -Zc:referenceBinding -Zc:__cplusplus -O2 -MD
	-std:c++17 -utf-8 /wd4530 /wd4577 -W3 -w34100 -w34189 -w44996 -w44456 -w44457 -w44458 -wd4577 -wd4467 -DUNICODE -D_UNICODE -DWIN32 -D_ENABLE_EXTENDED_ALIGNED_STORAGE -DWIN64 -DQT_NO_LINKED_LIST -DQT_NO_LINKED_LIST -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_USE_QSTRINGBUILDER -DNDEBUG -DQT_NO_EXCEPTIONS -DQT_NO_DEBUG -DQT_QMLDEVTOOLS_LIB -DQT_CORE_LIB -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\tools\qmllint -I. -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\include -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\include\QtQml -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\include\QtQml\5.15.7 -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\include\QtQml\5.15.7\QtQml -I..\..\include -I..\..\include\QtQml -I..\..\include\QtQml\5.15.7 -I..\..\include\QtQml\5.15.7\QtQml -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5\QtCore\5.15.7 -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5\QtCore\5.15.7\QtCore -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5 -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5\QtCore -I.moc\release -IC:\mixxx-vcpkg\installed\x64-windows\include -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5 -IC:\mixxx-vcpkg\installed\x64-windows\tools\qt5\mkspecs\win32-msvc -Fo.obj\release\ @C:\Users\RUNNER~1\AppData\Local\Temp\main.obj.6780.15.jom
main.cpp

After https://github.com/microsoft/vcpkg/pull/26354:
	cl.exe
	-c -nologo -Zc:wchar_t -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -Zc:referenceBinding -Zc:__cplusplus -O2 -MD
	-nologo -DWIN32 -D_WINDOWS -W3 -utf-8 -GR -EHsc -MP -MD -O2 -Oi -Gy -DNDEBUG -Z7
	-nologo -DWIN32 -D_WINDOWS -W3 -utf-8 -GR -EHsc -MP -MD -O2 -Oi -Gy -DNDEBUG -Z7
	-std:c++17 -utf-8 /wd4530 /wd4577 -W3 -w34100 -w34189 -w44996 -w44456 -w44457 -w44458 -wd4577 -wd4467 -DUNICODE -D_UNICODE -DWIN32 -D_ENABLE_EXTENDED_ALIGNED_STORAGE -DWIN64 -DQT_NO_LINKED_LIST -DQT_NO_LINKED_LIST -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_USE_QSTRINGBUILDER -DNDEBUG -DQT_NO_EXCEPTIONS -DQT_NO_DEBUG -DQT_QMLDEVTOOLS_LIB -DQT_CORE_LIB -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\tools\qmllint -I. -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\include -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\include\QtQml -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\include\QtQml\5.15.7 -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\include\QtQml\5.15.7\QtQml -I..\..\include -I..\..\include\QtQml -I..\..\include\QtQml\5.15.7 -I..\..\include\QtQml\5.15.7\QtQml -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5\QtCore\5.15.7 -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5\QtCore\5.15.7\QtCore -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5 -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5\QtCore -I.moc\release -IC:\mixxx-vcpkg\installed\x64-windows\include -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5 -IC:\mixxx-vcpkg\installed\x64-windows\tools\qt5\mkspecs\win32-msvc -Fo.obj\release\ @C:\Users\RUNNER~1\AppData\Local\Temp\main.obj.2604.16.jom
main.cpp

With the proposed patch https://github.com/daschuer/vcpkg/commit/6b45c7681fec2af36669653f3474c6c31cda968f applied:
	cl.exe
	-c -nologo -Zc:wchar_t -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -Zc:referenceBinding -Zc:__cplusplus -O2 -MD
	-nologo -DWIN32 -D_WINDOWS -W3 -utf-8 -GR -EHsc -MP -MD -O2 -Oi -Gy -DNDEBUG -Z7
	-std:c++17 -utf-8 /wd4530 /wd4577 -W3 -w34100 -w34189 -w44996 -w44456 -w44457 -w44458 -wd4577 -wd4467 -DUNICODE -D_UNICODE -DWIN32 -D_ENABLE_EXTENDED_ALIGNED_STORAGE -DWIN64 -DQT_NO_LINKED_LIST -DQT_NO_LINKED_LIST -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_USE_QSTRINGBUILDER -DNDEBUG -DQT_NO_EXCEPTIONS -DQT_NO_DEBUG -DQT_QMLDEVTOOLS_LIB -DQT_CORE_LIB -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\tools\qmllint -I. -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\include -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\include\QtQml -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\include\QtQml\5.15.7 -IC:\mixxx-vcpkg\buildtrees\qt5-declarative\src\5.15.7-7f3698f29e.clean\include\QtQml\5.15.7\QtQml -I..\..\include -I..\..\include\QtQml -I..\..\include\QtQml\5.15.7 -I..\..\include\QtQml\5.15.7\QtQml -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5\QtCore\5.15.7 -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5\QtCore\5.15.7\QtCore -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5 -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5\QtCore -I.moc\release -IC:\mixxx-vcpkg\installed\x64-windows\include -IC:\mixxx-vcpkg\installed\x64-windows\include\qt5 -IC:\mixxx-vcpkg\installed\x64-windows\tools\qt5\mkspecs\win32-msvc -Fo.obj\release\ @C:\Users\RUNNER~1\AppData\Local\Temp\main.obj.6856.16.jom
main.cpp

With the proposed patch https://github.com/daschuer/vcpkg/commit/6b45c7681fec2af36669653f3474c6c31cda968f applied:

these flags are coming from the toolchain set for qt5-base instead of the toolchain for the port. Also you should always use vcpkg_configure_qmake instead of supplying another function doing the same as vcpkg_configure_qmake.
I looked at how qt5-base tries to support cross builds. It is definitely not correctly designed for that. So that would require fixing first.

seems like the flags come from qmodule.pri
!host_build|!cross_compile {
    QMAKE_LIBS_PRIVATE+=$$[QT_INSTALL_LIBS]/bz2.lib
    QMAKE_LIBS_PRIVATE+=$$[QT_INSTALL_LIBS]/libpng16.lib
    QMAKE_LIBS_PRIVATE+=$$[QT_INSTALL_LIBS]/icuin.lib $$[QT_INSTALL_LIBS]/icutu.lib  $$[QT_INSTALL_LIBS]/icuuc.lib $$[QT_INSTALL_LIBS]/icuio.lib $$[QT_INSTALL_LIBS]/icudt.lib Advapi32.lib
    QMAKE_LIBS_PRIVATE+=$$[QT_INSTALL_LIBS]/zstd.lib
    QMAKE_CC=cl.exe
    QMAKE_CXX=cl.exe
    QMAKE_AR=lib.exe
    QMAKE_RANLIB=:
    QMAKE_STRIP=
    QMAKE_NM=
    QMAKE_RC=rc.exe
    QMAKE_MT=mt.exe
    QMAKE_LIB=lib.exe
    QMAKE_LINK=link.exe
    QMAKE_LIBS+=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib
    QMAKE_RC+=-c65001 -DWIN32
    QMAKE_CFLAGS_RELEASE+=-nologo -DWIN32 -D_WINDOWS -W3 -utf-8 -MP  -MD -O2 -Oi -Gy -DNDEBUG -Z7
    QMAKE_CXXFLAGS_RELEASE+=-nologo -DWIN32 -D_WINDOWS -W3 -utf-8 -GR -EHsc -MP  -MD -O2 -Oi -Gy -DNDEBUG -Z7
    QMAKE_LFLAGS+=-machine:x64 -nologo -DEBUG -INCREMENTAL:NO -OPT:REF -OPT:ICF
    QMAKE_LFLAGS_SHLIB+=-machine:x64 -nologo -DEBUG -INCREMENTAL:NO -OPT:REF -OPT:ICF
    QMAKE_LFLAGS_PLUGIN+=-machine:x64 -INCREMENTAL:NO
    QMAKE_LIBFLAGS_RELEASE+=-machine:x64 -nologo
}

I looked at how qt5-base tries to support cross builds. It is definitely not correctly designed for that. So that would require fixing first.

Since that is not broken for me, I have no interest to fix it. I expect that this is a quite hard task, because it is against the original design of the Qt build system.

these flags are coming from the toolchain set for qt5-base instead of the toolchain for the port.

Yes.

Also you should always use vcpkg_configure_qmake instead of supplying another function doing the same as vcpkg_configure_qmake.

Ok, would than a solution acceptable that adds another parameter to vcpkg_configure_qmake, to disable adding the CMake flags?

It started failing after https://github.com/microsoft/vcpkg/commit/d8e60ef4741584f2957788ed0786dd365c92c4d9

Qt5 in vcpkg isn't really supporting cross builds. The key problem is using host (triplet) tools with target mkspecs. It may have been somewhat hidden for osx, but it it is obvious when trying to build for mingw on linux.

For me it is kind of mood to discuss whether Qt5 supports cross compiling with vcpkg, because there is clearly a demand AND it was working. From that point of view we have a regression here and you are holding back a feature that is clearly supported by the Qt authors for some principles. But anyway in case of Mixxx we have all working as an overlay: https://github.com/mixxxdj/vcpkg/tree/2.4/overlay/osx

Nice that it works for your with osx/mixxx glasses on. But this is no the kind of feedback that motivates me to move forward the WIP work which I already have.

Oh sorry, I did not knew there is work in progress. Than go ahead and keep us informed. I am happy do help testing that we quickly get around the broken state.


ffmpegdecoder throws warning on end of file

Currently you run av_read_frame in ffmpegdecoder untill it throws an error, this is correct behavior, but EOF shouldn't be logged as a warning since it's expected behavior

Finally got around to fixing this: https://github.com/clangen/musikcube/commit/3b95b17753d3448b7ca6ccc460e4acdb7cd81884


Incomplete response with streaming

I have a chat system working perfectly. When I updated to version 4 of the gem, everything went well (it works normally). However, when I add the 'stream' option to the OpenAI API call, the content of the response is incomplete.
This code works normally:
response = openai_client.chat(
  parameters: {
    model: "gpt-4",
    messages: [
      {role: "system", content: system_prompt},
      {role: "user", content: user_prompt}
    ],
    temperature: 0.4,
    user: "user_#{user_id}"
  }
)
puts "RESPONSE: #{response}"
response.dig("choices", 0, "message", "content")

However, when adding the streaming option:
response = openai_client.chat(
  parameters: {
    model: "gpt-4",
    messages: [
      {role: "system", content: system_prompt},
      {role: "user", content: user_prompt}
    ],
    temperature: 0.4,
    stream: proc do |chunk, _bytesize|
      new_content = chunk.dig("choices", 0, "delta", "content")
      if new_content
        answer.content = (answer.content || "") + new_content
        answer.save!
      end
    end,
    user: "user_#{user_id}"
  }
)
puts "RESPONSE: #{response}"
response.dig("choices", 0, "message", "content")

Screenshot with responses:

Any clue as to why it could happen?

Rails <IP_ADDRESS>
Ruby 3.2.1
OS: macOS
Browser ARC/Chrome

Thanks for sharing on here! I don't have gpt-4 access and I don't know what your system prompt is, with gpt-3.5 I'm not able to reproduce this so far:
openai_client.chat(
  parameters: {
    model: "gpt-3.5-turbo",
    messages: [
      {role: "system", content: "Answer politely."},
      {role: "user", content: "What is the maximum weight allowed in the closed drawer or in combination of inside and on top of the open drawer?"}
    ],
    temperature: 0.4,
    stream: proc do |chunk, _bytesize|
      print chunk.dig("choices", 0, "delta", "content")
    end,
  }
)
#=> I'm sorry, but I don't have enough information to answer your question. Could you please specify which drawer or product you are referring to?

Are you able to print out all chunks and see if they are coming through correctly?

Hopefully you get access soon @alexrudall. In the meantime I've added a spec and tested this scenario in #252.

@rmontgomery429 thanks, that's really helpful! Seems like you couldn't reproduce the issue either?

@alexrudall Correct.

@deikka can you print all the chunks you're getting and share here? We can't reproduce this, it's a strange one

It's super strange... I'm receiving these incomplete chunks. Perhaps there's an installed gem causing interference?
As it appears:
According to applications innovative services human, public safety resource management,, and example, an provide information and contact analyze data from mobile and to understand behavior patterns include community linking mobile social.

Hey folks, I was just about to throw in the towel when I tried commenting out the helicone part. Now, everything is working like a charm!
require "openai"

OpenAI.configure do |config|
  config.access_token = Rails.application.credentials.dig(:openai, :access_token)
  config.organization_id = Rails.application.credentials.dig(:openai, :organization_id)
  # config.uri_base = "https://oai.hconeai.com/" # Optional
  config.request_timeout = 240 # Optional
end

Legend, that’s really good to know. Will try and reproduce in a test and then we can feed back to Helicone if the issue is on their end. Or you fancy doing it in your PR @rmontgomery429 ? 😎

@alexrudall My suggestion would be to merge that PR given that it confirms GPT-4 streaming is working and there are no specs for that now and address any changes required to accommodate Helicone in a separate PR.

Maybe @chitalian @ScottMktn have some insight they can share that would help troubleshoot this issue.

Never mind @alexrudall, I didn't realize that Helicone was in the readme so it's less orthogonal that I thought. I tried to reproduce the issue but to no avail. I've updated my PR to include those request specs as well.

Thanks for your efforts! Will try also :)
On Sat, 29 Apr 2023 at 20:52, Ryan Montgomery @.***>
wrote:

Never mind @alexrudall https://github.com/alexrudall, I didn't realize
that Helicone was in the readme so it's less orthogonal that I thought. I
tried to reproduce the issue but to no avail. I've updated my PR to include
those request specs as well.
—
Reply to this email directly, view it on GitHub
https://github.com/alexrudall/ruby-openai/issues/251#issuecomment-1528781337,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWXYXU53BWDSXA5BY7THALXDUFJVANCNFSM6AAAAAAXPBWLHI
.
You are receiving this because you were mentioned.Message ID:
@.***>

This is a simple testing case. When I use stream, the prompt is "please output 1 to 100". The content returned by Ruby OpenAI will lose some data.

In order to ensure that data is not overwritten incorrectly, I used the function of kredis to maintain order.
  def stream_proc(message:)

    answer = Kredis.list "message-#{message.id}"
    proc do |chunk, _bytesize|
      new_content = chunk.dig("choices", 0, "delta", "content")

      answer << new_content if new_content

      message.update(content: answer.elements.join("")) if new_content
    end

I can also contribute to "it's helicone" in my experience of this bug. Using Alex's example from the readme. Commenting/uncommenting uri_base produces the difference. I'm getting significant drop in chunks though, like every 3rd or 4th chunk is gone.
OpenAI.configure do |config|
  # config.uri_base = "https://oai.hconeai.com/"
  config.access_token = ENV.fetch("OPENAI_ACCESS_TOKEN")
  config.organization_id = ENV.fetch("OPENAI_ORGANIZATION")
  config.extra_headers = {
    "Helicone-Auth" => "Bearer #{ENV.fetch("HELICONE_API_KEY")}",
    "Helicone-Cache-Enabled" => "true"
  }
end

task scratch: :environment do
  client = OpenAI::Client.new
  client.chat(
    parameters: {
      model: "gpt-3.5-turbo", # Required.
      messages: [{role: "user", content: "Describe a character called Anna!"}], # Required.
      temperature: 0.7,
      stream: proc do |chunk, _bytesize|
                print chunk.dig("choices", 0, "delta", "content")
              end
    }
  )
end

Hi! I was able to recreate it locally and fixed it by setting this header:
"helicone-stream-force-format" => "true"
Let me know if this works, I will look into a fix that does not require that header.

@colegottdank thanks, that's very helpful! @ScotterC does that work for you?

Yup. On a small scale test and larger implementation it works. I'd love to better understand what's happening here @colegottdank
Here's the source https://github.com/Helicone/helicone/blob/5f1e190f84f01068649b11b014bac9f51bb5a5b5/worker/src/lib/HeliconeHeaders.ts#L105

Hey family, adding the header works perfectly for me too. I think we can consider this issue resolved, don't you think?

It looks like the effect is here. Seems it... queues chunks into an array? It seems like it either fixes or mostly fixes it. If you join the Helicone Discord here you can see any more discussion that comes out of this or request for updates.
I've also added a note to our README here to use this flag with Helicone for now. But yeah our work here is done, thanks for raising @deikka + others and for the fix @colegottdank!
client = OpenAI::Client.new(
    access_token: "access_token_goes_here",
    uri_base: "https://oai.hconeai.com/",
    request_timeout: 240,
    extra_headers: {
      "Helicone-Auth": "Bearer HELICONE_API_KEY", # For https://docs.helicone.ai/getting-started/integration-method/openai-proxy
      "helicone-stream-force-format" => "true", # Use this with Helicone otherwise streaming drops chunks # https://github.com/alexrudall/ruby-openai/issues/251
    }
)

The reason this issue manifests itself when accessing OpenAI through Helicone (or any other proxy-like intermediary) could be that the completion JSON chunks from OpenAI are being buffered/joined/split at non-JSON boundaries during transit. #332 should fix it.


Incorrect training data

Hi,
so I trained Kaldi using your (old) s5 script, and as a sanity check I tried to decode the training data.
When I compared the text file from the training data to my results, I noticed that there seem to be quite a number of errors in the texts.
I checked the audio and xml files and saw that the sentences were wrong.
I added a screenshot of a partial vimdiff of the text and my results.

Appears to be a mixup, as those sentences do exist, but in other audio files

Hi,
thanks for opening the issue. I'm was aware of this and I'm currently investigating this.
By running
https://github.com/tudarmstadt-lt/kaldi-tuda-de/blob/master/s5_r2/local/run_cleanup_segmentation.sh
from the new set of scripts in s5_r2 a cleaned training directory is generated. I've compared it to the train set and this seem to be the broken ids:
https://github.com/tudarmstadt-lt/kaldi-tuda-de/blob/master/s5_r2/local/cleanup/problematic_wavs.txt
The cleanup script also decodes the training set (with a biased language model built from the reference), so that's similar to what you did. The ids from s5_r2 are similar to s5, there is just a suffix added for the different microphones (a,b,c) since s5 didn't use all the available data.
Can you send me your diff and/or would you be able to fix the corpus XML's directly? Otherwise since this doesn't seem to be a lot of the total data (1.5%), I'd simply remove the broken data from the next release (v3) of the corpus.

If fixing the XML files needs some helping hands and makes sense, let me know.

Hi svenha!
That would be greatly appreciated! There is already a list of files with
wrong transcriptions in the cleanup folder in the repository. That should
be a good starting point!
I'm currently preparing v3 of the corpus, where I sorted these files out
into a separate folder. I can send you a link tomorrow.
svenha<EMAIL_ADDRESS>schrieb am Mo., 28. Mai 2018, 16:17:

If fixing the XML files needs some helping hands and makes sense, let me
know.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tudarmstadt-lt/kaldi-tuda-de/issues/15#issuecomment-392539088,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJRgetAq1txc8OE-8BcLKaUKG3Ve-HFxks5t3AbzgaJpZM4T37R6
.

Here is our planned v3 package where hopefully most of the bad utterances are moved into a separate folder: http://ltdata1.informatik.uni-hamburg.de/kaldi_tuda_de/german-speechdata-package-v3.tar.gz
@KlausBuchegger can you upload your diff and decoded output?

Two questions about the file problematic_wavs.txt.

It lists 730 files, but the directory train_removed/ contains 363 recordings (5 files per recording). Why?
Whats is the role of the transcript in problematic_wavs.txt? Is it the incorrect transcript from the current .xml file?

I think the uploads from Klaus might be helpful ...

Hello
I am trying to train deepspeech and I got two days ago a feeling it might lies on the data, that the model does not converge well. I checked also the the data and have a rather preliminary impression.
As I see some transcriptions got delete but some got mixed, so the text exists but is (was) assigned to other transcription (or of course the same text was spoken multiple times):
train/2014-03-17-13-03-33_Kinect-Beam.wav should have the same text as train/2014-05-08-11-48-47_Kinect-Beam.wav
What speaks for mixed (wrong) assignment is that sometimes I have the impression the text was just shifted:
train/2014-03-17-13-03-49_Kinect-Beam.wav should have the same text as train/2014-03-17-13-03-33_Kinect-Beam.wav
and
train/2014-03-17-13-04-15_Kinect-Beam.wav and train/2014-03-17-13-04-43_Kinect-Beam.wav
The dates are pretty close (they are in my training file neighbor lines).
Should we use some sort of work coordination sorting it out?

@fbenites Yes, it would be good to distribute the correction work. Benjamin (bmilde) offered to produce a list of problematic transcripts by running the recognizer on the train set. When this is done, let us partition the manual check work in two parts.

@fbenites @svenha thanks for offering to help. I'm running the decode on the train set right now and should have the results soon.
@svenha As for the number of problematic utterances in the proposed v3 tar: the numbers are different since I excluded all wav files of all microphones, whenever at least one decode of one microphone fails. There are multiple microphone recordings of the same utterance. Better safe than sorry. Still, only about 1.5% of all utterances are problematic. But the problematic files tend to be in the same recording session(s).
@fbenites Low RNN-CTC performance will probably remain, even if we fix all the problematic files. There is probably not enough data for end-to-end RNN training (40h x number of microphones, but that is more like doing augmentation learning on 40h of data). What kind of WERs are you seeing with DeepSpeech at the moment? Are you training with or without a phonetic dictionary? Utterance variance is unfortunately also fairly low, there are only about 3000 distinct sentences in train/dev/test combined, so I suggest using a phoneme dictionary if possible. I also suggesting adding German speech data from SWC (https://nats.gitlab.io/swc/), worked very well in the our r2 scripts in this repository (18.39% WER dev /  19.60% WER test now).

@bmilde Thanks, I will have a look at the wikipedia.
I am not certain, I removed some problematic files I am using also: github.com/ynop/audiomate to process which cover some files already, but I added the other 700 to blacklist.
I will have some results tomorrow. WER is also complicated see https://github.com/ynop/deepspeech-german sometimes the text is just missing some chars or spaces, which drops the WER a lot. I had some useful results only using voxforge contradicting the results with voxforge and tuda. I will check the phoneme dictionary in deepspeech, thx.

@fbenites  @svenha
I uploaded the decode of the tuda train set to: http://speech.tools/decode_tuda_train.tar.gz
This file might be interesting:
exp/chain_cleaned/tdnn1f_1024_sp_bi/decode_tuda_train/scoring_kaldi/wer_details/per_utt
or alternatively you can also diff e.g.:
diff exp/chain_cleaned/tdnn1f_1024_sp_bi/decode_tuda_train/scoring_kaldi/penalty_0.5/10.txt  exp/chain_cleaned/tdnn1f_1024_sp_bi/decode_tuda_train/scoring_kaldi/test_filt.txt
Though this doesn't look so pretty in standard diff, so some graphical diff-like tool like in the screenshot from Klaus is probably a better idea.

Thanks @bmilde . I investigated the file per_utt with a little script that sums the isd part of the "cisd" fields. I count all of them as errors of equal weight. Then I used an error threshold t. For t=4, 2490 affected files; for t=5, 1788 files, for t=6,1511 files. As we have only 2 annotators, I would suggest to use t=6. (We can repeat the decoding of the train set with the improved corpus and choose a second annotation round.) If you agree, I can produce the file list, sort it, and cut it in the middle. I would take the first half, @fbenites the second part?
@bmilde : How should we contribute the changes? We could edit the .xml files, collect all changed .xml files and send them to you. But I am open to other approaches, like a normal pull request (if the repo is not too large for this).
One final point: in per_utt, there are file names like 02dae8284f104451a8de85538da6fdec_20140317140355_a . Is it safe to assume that it corresponds 1:1 to an xml file derived from the date/time part, here 2014-03-17-14-03-55.xml ?

Many thanks @svenha !
Yes, it is safe to assume that 02dae8284f104451a8de85538da6fdec_20140317140355_a belongs to 2014-03-17-14-03-55.xml
02dae8284f104451a8de85538da6fdec is the speaker hash, the last letter indicates the microphone, between that the IDs contain the timestamp without the dashes. Note that it's also safe to assume that _a, _b, _c etc all belong to the same utterance and that they should contain the same transcription. If all of them decode to something else, it's safe to assume an incorrect transcription.
Maybe it's also a good idea to make the threshold t depended on the length of the transcription, there are some very short utterances, too. But I can also always rerun the decoding for you after getting corrected xml files.
Since the corpus is not hosted on Github, it's probably easier if you send me the corrected xml files directly. But you can also send me a pull request, containing only the corrected xml files, placed somewhere in a subfolder of the local directory. I can then also write a script that checks the corpus files and patches them if needed, so that it is not necessary to redownload the whole tar.gz file.
One final point: Note that the xml files have sentence IDs.
E.g. sentence_id 59 in:
<?xml version="1.0" encoding="utf-8"?><recording><speaker_id>02dae828-4f10-4451-a8de-85538da6fdec</speaker_id><rate>16000</rate><angle>0</angle><gender>male</gender><ageclass>21-30</ageclass><sentence_id>59</sentence_id><sentence>Rom wurde damit zur ‚De-Facto-Vormacht‘ im ö
stlichen Mittelmeerraum.</sentence><cleaned_sentence>Rom wurde damit zur De Facto Vormacht im östlichen Mittelmeerraum</cleaned_sentence><corpus>WIKI</corpus><muttersprachler>Ja</muttersprachler><bundesland>Hessen</bundesland><sourceurls><url>https://de.wikipedia.org/wiki/R|
ömisches_Reich</url></sourceurls></recording>

A text file with all of the sentence IDs and transcriptions is in the root of the corpus archive. Since there are multiple recordings per sentence ID, it is very unlikely that the correct sentence is not included. Maybe we can also just try to find the closest match automatically and check that its correct manually?

I switched from an absolute threshold to a relative threshold as suggested by @bmilde  : number_of_errors / number_of_words >= 0.2
I include an xml file only if all of its recordings (i.e. microphones a, b, c, and d) fufill this criterion.
This gave me 744 xml file names that I attach in two parts of 372 file names each below. I will check the first part (files1) now and send corrected xml files. (We will see how theses changes must be propagated to the SentencesAndIds files.)
tuda-20perc-err.files1.txt
tuda-20perc-err.files2.txt

tuda-20perc-err.files1.txt is finished. I will sent the files to @bmilde. Any volunteers for tuda-20perc-err.files2.txt? (If not, I might have time in August.)

Just to avoid duplicate work, I would let you know that I am working on files2.

The second half (i.e. files2) were finished some weeks ago. Is there a rough estimate of the release date of tuda v3?

Hey guys, huge thanks for the dataset!!
i was able to combine your dateset, voxforge, librivox and the swc corpus.
I put much effort in cleaning the datasets to make sure there are as little mistakes as possible.
I trained it with the deepspeech framework and 150.000 samples and got 12% WER.
Since then i corrected some other mistakes and fixed some more errors.
I just started the second round with 220.000 clean samples.
I hope i will get under 10% WER.
I will share the code and the results after the training.
Greets from Frankfurt :P

PS :
cat all_corpora_filtered_maryfied.txt | grep " hhe"

Great work @silenterus
Do you have an update on the WER?
Do you plan on including data from common voice?  They claim to already have 127 h of validated german voice https://voice.mozilla.org/

Okay sry to keep you guys so long wating.
First the bad news....
The graph had only 16% WER. I was really disappointed and ashamed because i misinterpreted the loss value .
See in all my previously trainings this value correlated with the resulting WER. The loss value was 14% when i reached 12% WER with my previous attempt.
But the good news i'm ready to share the the code and im pretty sure someone will find the right parameters to archive 10%.
I did implement an Common Voice parser but i couldn't find any German Corpus yet. If someone find one plz share link.
Installation :
sudo apt-get install sqlite3 -y
if you want to buld tri and binary (you need to install them otherwise the script wont find them)
git clone https://github.com/kpu/kenlm
cd kenlm
mkdir -p build
cd build
cmake ..
make -j 4
make install      # important !!!
cd ..
cd ..
git clone https://github.com/silenterus/deepspeech-cleaner
cd deepspeech-cleaner
pip3 install -r requirements.txt
if you want to use all the samples that are currently in my db you have to download these files. (keep traffic humane..it's a private server)
http://pia.servehttp.com:8100/de_DE.tgz #unchanged

deepspeech-cleaner/datasets/librivox/by_book/

http://pia.servehttp.com:8100/german-speechdata-package-v2.tar.gz #unchanged

deepspeech-cleaner/datasets/tuda/tuda/train
deepspeech-cleaner/datasets/tuda/tuda/dev
deepspeech-cleaner/datasets/tuda/tuda/test

https://pia.servehttp.com:8100/wiki.zip

deepspeech-cleaner/datasets/wiki/audio/

http://pia.servehttp.com:8100/vox.zip

deepspeech-cleaner/datasets/wiki/audio/

http://pia.servehttp.com:8100/audio.db

deepspeech-cleaner/

the server will be online for the next 7 days
all the parameters for sql query
python3 deepspeech-cleaner.py --help
creating training files in "training/defaulter" with default values without lm.binary + trie
python3 deepspeech-cleaner.py create_files
creating training files in "training/german300k" with default values without lm.binary + trie
python3 deepspeech-cleaner.py create_files --training german300k
creating training files in "training/german200k" with default values and lm.binary + trie
put all_corpora_filtered_maryfied.txt in

deepspeech-cleaner/cleaner

the paramater doesnt work yet
i used DeepSpeech Version 0.2.1-alpha.2 to generate the trie. I hope they didnt change the language model since then
python3 deepspeech-cleaner.py create_files --training german200k --trie True
start training in defaulter
bash start_train.sh defaulter
start training in german300k
bash start_train.sh german300k
and dont mind the warnings when you preprocessing
#WARNING:root:frame length (551) is greater than FFT size (512), frame will be truncated. Increase NFFT to avoid.
#WARNING:root:frame length (551) is greater than FFT size (512), frame will be truncated. Increase NFFT to avoid.
i did, and even after i red they arent harmful, i insist that i "repair" the wavs. So a resampled every wav. After that i got the 16% WER :P
that's hardly all but enough to start trainning.
i think an offline translator for several languages would be also possible and awesome :D
that's what im trying to archive. to make this git functional for multiple languages.
i working on a voxforge downloader for multiple languages
the module num2words supports many languages but not without some errors. for example 1. = erster
If you want to help i would be more than thankful. as you might have guessed, my english sucks.

Hi,
Sorry for the radio silence, I was caught up in other projects.
Where are the cleaned data? I would like to check them further. at http://speech.tools/ I get a 403.
Thanks again!

Hey,
so here are the trie, lm, alphabet and graph from my attempt with upper letters.
alphabet >>> https://drive.google.com/open?id=1hnINb5NQI6a1kG2COFrluRrkRaa8MRJy
graph >>> https://drive.google.com/open?id=1BQfXIplWQG0FB2PggeDFxzsbKxRNg07P
lm.binary >>> https://drive.google.com/open?id=1eQRowHTZoyHNvp6A4QA1MjotWH3p78XD
trie >>> https://drive.google.com/open?id=1pC0jRXZ6xUHiIxWq43t6EW59vXcuXyaj
i used DeepSpeech Version : 0.4.0-alpha.0
I took 28 h to export the graph. In this time my desktop froze and i couldn't see the resulting WER.
I tested the graph with a couple of wavs but i didn't evaluate the WER because i wanted to start directly a new training with only lowercase letters.
But i suppose it's something between 14-17%
Training with lowercase so far :
I Validation of Epoch 5 - loss: 27.686189
100% (883 of 883) |###############################################| Elapsed Time: 0:05:53 Time:  0:05:53
I Training epoch 6...
I Training of Epoch 6 - loss: 20.015966
100% (8241 of 8241) |#############################################| Elapsed Time: 2:12:24 Time:  2:12:24
I Validating epoch 6...
2% (20 of 883) |#
i prepared a git which automatically download and prepare the wavs. I hope nobody wasted the time with the current version. It's not functional.....
I just added the librivox downloader but didnt test it so far.
tuda/voxforge already tested from download till training.
I maybe i get it to work today and update the git. We will see

@silenterus: It would be nice to keep the discussion on-topic.  This bug is about mix-ups and errors in the data files.  Feel free to open a new bug about training deep speech with our data.
@fbenites: speech.tools is hosted by @bmilde afaik, maybe he can fix that.

Sry you are absolutly right.
I will put the results on my git.
Keep up the good work

Are there any plans to integrate all the 2018 corrections into a new corpus version?

@Alienmaster Thanks for picking this up. Please report your evaluation results :-)

Closing this, release 4 of the tuda dataset contains the fixes: http://ltdata1.informatik.uni-hamburg.de/kaldi_tuda_de/german-speechdata-package-v4.tar.gz
Our CV7 branch uses this already to train the models, together with the newest Common voice data. See https://github.com/uhh-lt/kaldi-tuda-de/tree/CV7


Bug: Double-click on column header to go to parent folder

Description
Double-clicking on a column header in the details layout navigates the page to the parent folder as if double-clicking on an empty space.
Steps To Reproduce

Double-clicking on a column header in the details layout.
It navigates the page to the parent folder.

Requirements
It shouldn't navigate the page, but should switch between ascending and descending order.
Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.2506
Log File
n/a

Hello, I am interested in working on this issue. I am writing this comment to help prevent duplicate efforts from others.

Hello, I am interested in working on this issue. I am writing this comment to help prevent duplicate efforts from others.

I actually want to say that I started working on this issue earlier. I am writing this comment to help prevent duplicate efforts from others

OK I think I fixed this issue, just need to make a pull request. Will do that in an hour or two

I actually want to say that I started working on this issue earlier. I am writing this comment to help prevent duplicate efforts from others

Okay, nevermind, good luck with the PR

I actually want to say that I started working on this issue earlier. I am writing this comment to help prevent duplicate efforts from others

Okay, nevermind, good luck with the PR

Ok, you  PR was faster. Should have mentioned earlier that I started working on the issue. My bad

I actually want to say that I started working on this issue earlier. I am writing this comment to help prevent duplicate efforts from others

Okay, nevermind, good luck with the PR

Wait, actually I tested your PR and it doesn't work for me. The issue is still there

OK so it's night and I will go to sleep soon so I would make my PR tomorrow. But I'm not really sure if I should do it or maybe let the @pomydoro figure it out because he was technically the first to tackle the issue and make a PR. Maybe @yaira2 could say if it's OK if I do it or I better leave the issue to @pomydoro

Wait what was that PR not from @pomydoro but from @yaira2 and was the comment from @pomydoro not sarcasm? I am utterly confused right now with all of this

@RieBi I stopped working on this after seeing the comment that you were.

@RieBi I didn't see your comments earlier, sorry for the confusion, now that I read my comment again, it sounds a little ambiguous, but no sarcasm was intended. And no, the PR is not mine.


Add support to Embedded Ansible for ssh user@host:path urls

@carbonin @NickLaMuro Please review.
This is using the same regex that the UI uses [1], since I couldn't find a "standard" one.
[1] https://github.com/ManageIQ/manageiq-ui-classic/blob/e737cc675ee006c11508bc23f038c3357a1fb089/app/assets/javascripts/directives/url_validation.js#L21

Ivanchuk backport details:
$ git log -1
commit 03a4c95a9558cc0d285501f845778f7c146e23bb
Author: Nick Carboni<EMAIL_ADDRESS>Date:   Fri Aug 9 14:07:45 2019 -0400

    Merge pull request #19129 from Fryguy/embedded_ansible_ssh_user_host

    Add support to Embedded Ansible for ssh user@host:path urls

    (cherry picked from commit 11ad9b8a4ae6690b03b6a62a5b51301bb3390d4d)


[ISSUE#809] readme - update broken links

Summary

Update of 2 broken links in README.md
Related Issues
Fixes #809

Checklist

[x] This pull request has a meaningful title and description.
[x] I have read and followed the Contributing guidelines.
[x] My code follows the conventions and coding style of this project.

@danielschuster-muc my pleasure! :)


Every time I run "flutter run" it uninstalls and reships the APK

Right now my edit/refresh cycle on Android is really slow.
My workflow is as follows:

Run a bash script that does the following:
Dump the results of the most recent run of flutter analyze --watch --write, which is running in the background.
Run flutter run -t lib/main.dart --route=/
Watch the logs, interact with the app, fix a bug.
Kill the bash script and return to step 1.

Step 3, flutter run, is taking forever each time. The output includes the line "Uninstalling old version...", and it shows that for several seconds, so that's what I'm blaming.
The verbose logs show the following steps as being expensive:
  900 ms • adb -s ZX1G22KJ3C shell pm list packages io.flutter.gallery
 1062 ms • adb -s ZX1G22KJ3C uninstall io.flutter.gallery
11791 ms • adb -s ZX1G22KJ3C install -r build/app.apk
  848 ms • zip -q .../app.flx snapshot_blob.bin assets/flutter_logo.png ...
 4822 ms • adb -s ZX1G22KJ3C push build/app.flx /data/local/tmp/dev.flx
 1000 ms • adb -s ZX1G22KJ3C shell am start -a android.intent.action.RUN ...

These steps happen every time even if I skip step 4 (i.e. even if I make no changes to anything).

@tvolkert, the uninstall/reinstall change happened here: https://github.com/flutter/flutter/commit/51d4ab33243c7329d816dce2466a906739bcb902 - can you give a bit of context for that? I'm working if there's some way to solve the issue you were facing w/o a full uninstall.
@Hixie, can you try hitting r / F5 in the console w/ flutter run running instead of stopping and starting the app? That'll effectively issue a flutter refresh against android devices.

Yeah, flutter install fails for iOS if you try to install over an existing app without uninstalling the old one first.  We could add a -[no]uninstall flag... if we did, could we make --uninstall the default on iOS but --nouninstall the default on Android?

Perhaps we can special case for iOS, and/or push the uninstalling-when-installing logic down into the iOS specific device code.

Uninstall actually appears to be destructive on Android, as my Application
directory is deleted.  I ran into this with:
https://github.com/eseidelGoogle/flutter/commit/2cea20512ccfc1843eb29f2ee47e27791da5ee35
On Wed, Jun 22, 2016 at 9:21 AM, Devon Carew<EMAIL_ADDRESS>wrote:

Perhaps we can special case for iOS, and/or push the
uninstalling-when-installing logic down into the iOS specific device code.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/4672#issuecomment-227797578,
or mute the thread
https://github.com/notifications/unsubscribe/ALTvi2Q60tn_XiJZbvUWSFHQj2qyJRImks5qOWDxgaJpZM4I7Owu
.

Hitting "r" doesn't work because the steps I'm running above are being run inside an Emacs compilation buffer, which is non-interactive. Also, I want the analysis results in there, so I have to first exit the 'flutter' tool to print the analysis options.
Is there any way to tell flutter to refresh a running instance without having the flutter tool be the same instance that started it?

Not currently, but that's something we could add.

@tvolkert, can you look into making the uninstall-on-install logic iOS specific?

Sure

Actually, the code path for flutter run that calls installApp() is only run for Android devices, so the fix is gonna be pretty simple...


[Snyk] Security upgrade @nextui-org/react from 1.0.8-beta.5 to 2.0.0

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

advanced/wallets/react-wallet-v2/package.json
advanced/wallets/react-wallet-v2/yarn.lock

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Malicious Package SNYK-JS-LEGACYSWCHELPERS-7647380
  691

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

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

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

:tada: Snyk checks have passed. No issues have been found so far.
:white_check_mark: security/snyk check is complete. No issues have been found. (View Details)
:white_check_mark: license/snyk check is complete. No issues have been found. (View Details)


Why enforcing to launch app as non-elevated after update ?

I have an app that runs elevated, but after update, its no longer elevated, causing all kinds of permissions issue. I looked at the source found it was in fact being forced to run as limited process. Why is that ? it should have some settings through arguments to do that or not to do that.

When clicking "Execute file after update" you can choose "Same as wyUpdate", "Not elevated" or "Elevated".
This isn't an issue. It's a question for our forum: https://wyday.com/forum/


tf.image.non_max_suppression produces wrong results in tf.function when the input is float16.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.7.0
Python version: 3.7.11
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: running on CPU
GPU model and memory: running on CPU

Describe the current behavior
tf.image.non_max_suppression will produce wrong results in tf.function when the input is float16.
Describe the expected behavior
The results should be equivalent to eager mode.
Contributing

Do you want to contribute a PR? (yes/no): no
Briefly describe your candidate solution(if contributing):

Standalone code to reproduce the issue
import tensorflow as tf
import numpy as np

argument = {'max_output_size':<PHONE_NUMBER>354746723,
            'scores': np.array([61920., 31020., 2234., 41280., -25490.], dtype=np.float16),
            'boxes': np.array([[-40500., -59940., -106.3, 41800.],
                               [-37700., 37500., -53630., 49920.],
                               [-44900., -5356., 28080., 24940.],
                               [-44770., -18110., 28940., 7900.],
                               [-32380., 36200., -40640., 22850.]], dtype=np.float16)}

fun = tf.image.non_max_suppression

output1 = fun(**argument)
print(output1)  # the results of eager mode is correct

@tf.function
def fun_wrapper(arg):
    return fun(**arg)

output2 = fun_wrapper(argument)
print(output2)  # the results of tf function is wrong

The results are:
tf.Tensor([0 3 1 2 4], shape=(5,), dtype=int32)
tf.Tensor([0], shape=(1,), dtype=int32)

@chunduriv Was able to replicate the issue on colab using TF v2.7.0 ,2.8.0 and tf-nightly, please find the attached gist here.Thanks!

Triage Notes: The maximum value that float16 can represent is 65504. The values in this example are large enough that it is a reasonable guess that overflow is occurring. This appears to be a testing only case to find numeric bounds, the box coordinates do not look like either typical absolute pixel coordinates in an image or [0,1] normalized coordinates. Using float32 avoids this bug. While the NonMaxSuppressionV3 currently does not support bfloat16, using bfloat16 instead of float16 might solve this problem.


Fix service account token fetching in ODS-CI for compatibility issue with OCP 4.11

oc serviceaccounts get-token will not work on OCP 4.11 anymore, so this PR is replacing it with oc serviceaccounts  new-token
Will test retro-compatibility with the supported OCP versions
Note. This will change again with OCP 4.12 when it will be released.
Signed-off-by: bdattoma<EMAIL_ADDRESS>

tested on OCP 4.10 by perform log in using a service account (see first row in the image) plus running ODS-509 which needs prometheus token to run successfully

tested on OCP 4.11 by performing the same test as 4.10
test on OCP 4.9 coming soon