Add search functionality to notes table view

solution: https://github.com/yoha/Thoughtless/commit/d382475270ec65a681d110177e973fcd6039af59

solution: https://github.com/yoha/Thoughtless/commit/5aaf18fd9362611f36a4eaab5f3f4733fe0f1004


Shift select stopped working

Seems to have started happening since the move to canvas.
OS: Linux
Host: VS Code

Can repro inside tmux.

I'm guessing this broke when I fixed https://github.com/sourcelair/xterm.js/issues/913, I think we need to stop propagation on the mousemove rather than the mousedown.


Godot 4 Mouse get locked after clicking an editable field in the editor

Godot version
4.0.beta16
System information
Debian GNU/Linux 11 (bullseye) x86_64
Issue description
The issue seems a bit random sometimes, but I have found that whenever I try to edit a field in the editor (position, scale, etc) after editing another one, the mouse get locked and I can't do anything until I press ESC or I click again.
Currently using beta16, but noticed it on earlier betas as well.
Steps to reproduce
The easiest way to reproduce the issue, but not the only one:
Edit one field, press ESC and click another field.
Short video demostration (24s):
https://youtu.be/6iNe30KnLhQ
Minimal reproduction project
N/A

Unable to replicate this on Windows.
The edited EditorSpinSlider doesn't receive the Left-MouseButton-Up event and so it assumes that mouse movements are meant to start dragging, so that MOUSE_MODE_CAPTURED is activated in EditorSpinSlider::gui_input.
Bisecting shows that this got introduced in #70052.

Hi, I can confirm this. I'm using Beta 16 on kubuntu 22.04.
In my case I had opened a PBR material. Had just changed the albedo and went to expand the emission section. Instead of expanding the emission it expanded Anisotropy. From then on all left clicks, even on the main menu items, kept flipping Anisotropy section. I got left click control back when I did a Projects save all with ctrl shift s.

Related to https://github.com/godotengine/godot/issues/72012.

@Reports1874  I am also on 17 now, I reproduced my steps as best I could from my description. I also tried a variety of other things and I can not make it happen again.

Bisecting shows that this got introduced in #70052.

fyi @bruvzg

This should be already fixed.


Problem with large network dialog box add peer

I configured an interface with class \16 and I encounter a problem in the dialog box when I try to add a peer and the browser freezes.
I deduce for the calculation in the drop-down menu of available IP addresses that are about 65,534.
If I use class 24 instead I have no problem.

Hi! Yes this is a known issue, and it will be fix in the next release. Sorry about that.


Update view command in UG/DG

Updates to be made to (but not limited to) user stories, use cases, implementation, features sections.
Tag teaming here, let's update each other on progress and see what we can get done! :)

tagging myself just for fyi that am working on the view command related sections atm! :)


Fix visionimg on pixel 3, Add android 9 header files.

Description
Root Cause:
GraphicBuffer constructor definition was changed in android 9.
All the android code should be built under android 9 header files.
How I made this fix:

Find the android 9 GraphicBuffer header files and dependencies for from blueline-pq3a OTA source code.
Add these headers file into third_party folder:
third_party/android_frameworks_native_9
third_party/android_hardware_libhardware_9
third_party/android_system_core_9

In SContruct file, ensure that all the modules will be built under android 9 headers files in case "getprop ro.build.version.release" return  version "9".
Also add a macro ANDROID_9 for c++ files.

Have to add more android 9 headers file due to selfdrive/hardware/eon/hardware.h build error under android 9 header files:
Have to build some HAL files because some headers files depend on some generated HAL header files.
Add android 9 hidl header files and generated HAL header files to third_party:
third_party/android_hardware_hidl_9

Fix compile warning for selfdrive/logcatd/logcatd_android.cc due to including deprecated log/logger.h

TODO:
How to do unit test for visonimg.cc without working camerad? Write a fake camera?
how to do unit test for set_display_power?
More generic android version detection in SContruct ?
The android 9 header files for pixel 3 are downloaded here:
https://android.googlesource.com/platform/frameworks/native/+archive/refs/heads/pie-qpr3-release.tar.gz
https://android.googlesource.com/platform/system/core/+archive/refs/heads/pie-qpr3-release.tar.gz
https://android.googlesource.com/platform/hardware/libhardware/+archive/refs/heads/pie-qpr3-release.tar.gz
https://android.googlesource.com/platform/hardware/interfaces/+archive/refs/heads/pie-qpr3-release.tar.gz
https://android.googlesource.com/platform/system/libhidl/+archive/refs/heads/pie-qpr3-release.tar.gz
How I built the HAL files and generate required c++ header files:
sudo apt install hidl-gen
mkdir libhidl & cd libhidl && mv ../libhidl-refs_heads_pie-qpr3-release.tar.gz ./ && tar zxf libhidl-refs_heads_pie-qpr3-release.tar.gz
cd ..
mkdir interface && cd interfaces && mv ../interfaces-refs_heads_pie-qpr3-release.tar.gz ./ && tar zxf interfaces-refs_heads_pie-qpr3-release.tar.gz
hidl-gen -v -o output -L c++-headers -r android.hidl.base:../libhidl/transport/base<EMAIL_ADDRESS>hidl-gen -v -o output -L c++-headers -r android.hidl.base:../libhidl/transport/base -r android.hidl.manager:../libhidl/transport/manager<EMAIL_ADDRESS>hidl-gen -v -o output -L c++-headers -r android.hardware.graphics.common:graphics/common -r android.hardware.media:media<EMAIL_ADDRESS>hidl-gen -v -o output -L c++-headers -r android.hardware.graphics.common:graphics/common<EMAIL_ADDRESS>hidl-gen -v -o output -L c++-headers -r android.hardware.graphics.common:graphics/common<EMAIL_ADDRESS>hidl-gen -v -o output -L c++-headers -r android.hardware.graphics.bufferqueue:graphics/bufferqueue
-r android.hardware.media:media -r android.hardware.graphics.common:graphics/common -r android.hidl.base:../libhidl/transport/base<EMAIL_ADDRESS>tar zcf output.tar.gz output/
Verification

Nice!
I'm not sure we want to put all these headers right in openpilot. Can you make it a repo and submodule, perhaps android_headers_9?

Nice!
I'm not sure we want to put all these headers right in openpilot, it's 86000 lines! Can you make it a repo and submodule, perhaps android_headers_9, with a script to regenerate it? This is also useful for building eglfs_surfaceflinger.
It is still a lot even I removed unused cpp files and header files. Will do this.

Merged #23955. If there's anything missing please resubmit.


Fix custom user agent not working

Signed-off-by: Kristaps V<EMAIL_ADDRESS>

I'm not aware of this header field being part of any email-related protocol.

Oh, then it can probably be removed from line 452 of system/libraries/Email.php
$this->set_header('User-Agent', $this->useragent);

Actually, will do both.
Neither of User-Agent and X-Mailer are standards-defined headers, and there's just one expired IETF RFC draft attempt to do that, but they do both appear to be de-facto standard headers for the purpose they serve.


How can I install VS Code with this file? It is impossible to select when installing.

@joaomoreno told me that I just need to install from zero VS Code, so that I need to setup Portuguese Brazilian when installing. Well, when I open the installer, the option pt-BR does not appear.
How can I make this good?
https://github.com/microsoft/vscode/blob/be61b7d3abc7e532ddacaa9e799b301c59aca4e6/build/win32/i18n/messages.pt-br.isl#L9

Oh it seems we never really exported the pt-BR for the setup: https://github.com/microsoft/vscode/blob/master/build/win32/code.iss#L47-L57

The following languages were missing: brazilian portuguese, hungarian and turkish.
Verification:
code-setup.exe /lang=brazilianPortuguese
code-setup.exe /lang=hungarian
code-setup.exe /lang=turkish


delegateUnwrap is nothrow

This fixes nothrow errors I received with LDC 1.6.0 (not with LDC 1.7.0).

Since LDC 1.6 is far behind us, I suppose we can close this.


Propagate exit code in adoption standalone script

In the standalone script we use a trap call to remove the temp directory
where we write the dynamically generated scripts. Make sure that the
code run in the trap exits with the return code, so we can catch
failures when deploying standalone.

/test images

/test install-yamls-deploy


Update SitemapUpdater.php

the spaces weren't displayed very well before

Hey @phptek ,
do you want to merge this? :) Otherwise I'll close it.
Spek

@spekulatius thanks a lot for your input - sorry but for some reason I missed the first auto-email from Github :-(.
While I haven't download the patch to check, AFAIK the tabs / spacings are incorrect in the module anyway. In order to comply with SilverStripe guidelines, all indents need to be tabs using a 4-space indentation (See: https://github.com/silverstripe/silverstripe-framework/blob/3/.editorconfig).
So if you raise an issue along the lines of "Convert module to SilverStripe coding guidelines", that would be v/helpful. Thanks!

@phptek I opened an issue. I'm happy to help out here. Let me know how you want to approach this.

Hello @phptek ,
do you think you want to merge this in? I opened a issue for other code style related stuff.
Spek


envoy: Update envoy 1.27.x to 1.28.3

This is as part of regular maintenance as Envoy v1.27 will be EOL-ed in coming July.
Upstream release: https://github.com/envoyproxy/envoy/releases/tag/v1.28.3
Upstream release schedule: https://github.com/envoyproxy/envoy/blob/main/RELEASES.md#major-release-schedule

/test-backport-1.15


RHCLOUD-35382 adds job to queries to differentiate from inventory

PR Template:
Describe your changes

updates Grafana queries to specify the job as inventory api will have the same metric values but with a different job name

Ticket reference (if applicable)
Fixes #
Checklist

[ ] Are the agreed upon acceptance criteria fulfilled?

[ ] Was the 4-eye-principle applied? (async PR review, pairing, ensembling)

[ ] Do your changes have passing automated tests and sufficient observability?

[ ] Are the work steps you introduced repeatable by others, either through automation or documentation?

[ ] If automation is possible but not done due to other constraints, a ticket to the tech debt sprint is added
[ ] An SOP (Standard Operating Procedure) was created

[ ] The Changes were automatically built, tested, and  - if needed, behind a feature flag - deployed to our production environment. (Please check this when the new deployment is done and you could verify it.)

[ ] Are the agreed upon coding/architectural practices applied?

[ ] Are security needs fullfilled? (e.g. no internal URL)

[ ] Is the corresponding Ticket in the right state? (should be on "review" now, put to done when this change made it to production)

[ ] For changes to the public API / code dependencies: Was the whole team (or a sufficient amount of ppl) able to review?

/lgtm


simulate_sparse_stc throws assertion error when n_dipoles > len(labels)

Describe the bug
simulate_sparse_stc   throws an assertion error when   n_dipoles > len(labels) .
It should generate   min(n_dipoles, len(labels))   dipoles.
Steps and/or code to reproduce
If you slightly modified the code of the following MNE example:
https://www.martinos.org/mne/stable/auto_examples/simulation/plot_simulate_evoked_data.html#sphx-glr-auto-examples-simulation-plot-simulate-evoked-data-py
by remplacing n_dipoles=2 by n_dipoles=4 ligne 58, whiwh I did here:
https://gist.github.com/QB3/6ac76962c9ab7b9f1b44c1026021cafe
an assertion error is thrown.
Expected results
As  len(labels) = 3   I expect 3 dipoles.
Actual results
assertion error from this line https://github.com/mne-tools/mne-python/blob/8b00fc96ec8574c364007ea6b9655eb288d464bb/mne/simulation/source.py#L210

I would suggest to raise an informative exception message rather than
silently using min(n_dipoles, len(labels))

OK then we will have to change also the current warning msg:
https://github.com/mne-tools/mne-python/blob/8b00fc96ec8574c364007ea6b9655eb288d464bb/mne/simulation/source.py#L180

hum so now you get a warning but it will always crash afterwards? Basically warn should be ValueError or the min(n_dipoles, len(labels)) should actually be implemented?

yes, current warning is  The number of labels is different from the number of dipoles. 2 dipole(s) will be generated, but then an assertion error is thrown

ok then I would make it a ValueError and not a warn

OK I will do this then:

n_dipoles > len(labels)  --->>> ValueError
n_dipoles < len(labels)  ---->>> keep the same gene

go for it @QB3


Google Assistant Android APP

Hi Everyone,
I need to Android Application that it has integration with google assistant.
For example;
there is a button on the page and when I click on it and say something. This app recognize my voice an then get the text and answer me?
is it possible?
# can someone help me in this matter?

This project has the EmbeddedAssistant class, which encapsulates the Google Assistant with the generated classes from protobufs.

Hi @Fleker,
I am new in Android mobile app development. I am trying to make an application with the Google Assistant SDK. But I can't with this sample, it crashed on Android device.
In this situation, I need your help. How can I do that? Can you please give me a descriptive guideline (such as step by step process, sample project, etc.).
Thanks in advance

demo projects\androidthings-googleassistant-master\shared\build\extracted-include-protos\main' specified for property '$3' does not exist.


Adding single cell GO enrichment tutorial

Under single-cell topic I added GO-enrichment tutorial
I added my name to contributors.yaml file
I added images in the tutorial to the single-cell images

@Mennayousef do you need help to fix the merge failures?

@bgruening thanks a lot for your help the merge failures no longer exist. I would really appreciate if you could help me with adding the workflow to IWC and creating the workflow test.

@Mennayousef did you try the PDKN thing I sent you for generating tests?

@nomadscientist yeah but it gives an empty folder

@bgruening many thanks for your help! I followed this link to create the test https://training.galaxyproject.org/training-material/faqs/gtn/gtn_workflow_testing.html but really do not know why it still gives this error that a test is missing although I added the file to the workflow folder.

@Mennayousef the filenames of your workflow and the workflow-test needs to match. For example foo_bar.ga then your test needs to be named foo_bar-tests.yml.

@Mennayousef I hope its ok that I tried to fix a few minor spelling mistakes.
@pcm32 is this ok for you to merge?

It would be nice to not hide this tuorial under single-cell, or maybe have a more general GO tutorial as well at some point. I'm super happy having such a tutorial now in the GTN thanks a LOT @Mennayousef!
If you are really adventurous, please consider to submit your workflow as well to the IWC: https://github.com/galaxyproject/iwc/blob/main/workflows/README.md#adding-workflows :)

@bgruening sure thing, I will submit to IWC and thanks again for your support! Maybe I will also try to create another general tutorial on functional enrichment analysis after I finish my second tutorial on gene co-expression analysis :)

🎉


Variables preserve transformer improvements

Fixed conflicts between generated names and names from untouched identifiers from source code.
Fixed https://github.com/javascript-obfuscator/javascript-obfuscator/issues/550
Fixed https://github.com/javascript-obfuscator/javascript-obfuscator/issues/549

This is WIP PR, still should optimize a few things

Coverage decreased (-0.1%) to 98.62% when pulling db908f7bceb1c4b3b7513c6e51aa806b982d3a47 on variable-preserve-improvements into 43b8fc9d7c578d01b0276ad0b00c40766a2965e8 on master.

Coverage decreased (-0.1%) to 98.62% when pulling db908f7bceb1c4b3b7513c6e51aa806b982d3a47 on variable-preserve-improvements into 43b8fc9d7c578d01b0276ad0b00c40766a2965e8 on master.

Finally


[Error] Downloading stash for Hardcore Perandus, details logged to DebugInfo.log

There's a problem with Perandus coins. I can't upload my log file, because the site doesn't support that file type.

Please see issue #506 on how to get around this error until a new release of Procurement is available.


⚠ Processors has degraded performance

In 14f299d, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 52 ms

Resolved: Processors performance has improved in 572ffb5.


Can Apollo 8.0 be installed on Raspberry Pi?

I want to use Raspberry Pi to make a self-driving car, is it possible to install Apollo 8.0 on Raspberry Pi? Or maybe Jetson Nano and Jetson Xavier?

The raspberry pi needs some optimization as it has limited computing power. But I think it's a good project and you can learn a lot from it
Jetson Nano or Jetson Xavier will much easy.
They all need arm support and are currently under development. We can discuss it in the community, I think it will be a good project

Thank you very much for your reply, I decided to learn about this project and start by buying a Jetson Nano. 😀

I was also curious about running Apollo on a cluster of raspberry pis! Glad to see others have the same interested and guess I’ll be getting a Jetson Nano as well!
@daohu527 just for clarification, arm support is currently under development, when do you think it will be available for us to run it on Jetson Nano?

Q1: arm support is currently under development, when do you think it will be available for us to run it on Jetson Nano?

Work completed in Q2, but release schedule may be discussed. You can pay attention to community releases

Q2: do you think a single raspberry pi is able to run just prediction + planning + SimControl?

I have run the traffic light program on the Raspberry Pi, but the prediction may be more difficult, and the planning should not be a big problem. prediction use a lot of models, it may be feasible to simplify it with traditional algorithms.
Docker is not necessary to run, we can install the environment directly on the host. This is another topic : )

@daohu527 those are very helpful information! I plan to test Apollo's planning module on Raspberry Pi later.
Where can I find documentation to directly install Apollo on the host? I am only aware of this guide that talks about docker. If I just run ./apollo.sh build I'll get The build operation must be run from within docker container


fix: use job_spec api to get schedule interval for sensors

sensors have been using admin build instance to fetch schedule interval, as a side effect of that optimus was registering a new job run instance. To fix that sensors are now made to use job spec api

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Files with Coverage Reduction
New Missed Lines
%

ext/notify/pagerduty/pagerdutynotifier.go
2
93.75%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
7342

Relevant Lines:
9502

💛  - Coveralls


Ignite-2.5.1-p141-pme-2

PR seems to be temporary for testing, closing it, for now, feel free to reopen if it is needed.


Edit text only block?

Is it possible to have a setting so we can edit text-only block on the page? So you can't choose styles etc. This will be useful when you just want to edit a heading which already has a predefined style

{% placeholder ordering title="Ordering information" type="text" %}
https://octobercms.com/docs/markup/tag-placeholder

@l3utterfly Hey, i have good news, i try something and its working! :)
With this you can define your "fixture" tag and it get converted to that specific tag without toolbox (only allowed redo, undo, delete)
{% component 'contenteditor' file="welcome.htm" fixture="h3" %}

@l3utterfly You can check commit for it :) https://github.com/Samuell1/contenteditor/commit/afc1cbe95f66bdb3555463d6d4e677cdd9b8b385


ObjectDisposedException when UvStreamHandle.ReleaseHandle

I am running a load test using beta7 Kestrel on Windows 10. At some point Kestrel stops with the following stacktrace and messagebox:
Unhandled Exception: System.ObjectDisposedException: Safe handle has been closed
   at System.Runtime.InteropServices.SafeHandle.DangerousAddRef(Boolean& success)
   at System.StubHelpers.StubHelpers.SafeHandleAddRef(SafeHandle pHandle, Boolean& success)
   at Microsoft.AspNet.Server.Kestrel.Networking.Libuv.async_send(UvAsyncHandle handle)
   at Microsoft.AspNet.Server.Kestrel.KestrelThread.PostCloseHandle(Action`1 callback, IntPtr handle)
   at Microsoft.AspNet.Server.Kestrel.Networking.UvHandle.ReleaseHandle()
   at Microsoft.AspNet.Server.Kestrel.Networking.UvStreamHandle.ReleaseHandle()
   at System.Runtime.InteropServices.SafeHandle.InternalFinalize()
   at System.Runtime.InteropServices.SafeHandle.Dispose(Boolean disposing)
   at System.Runtime.InteropServices.SafeHandle.Finalize()

The website i am using works with websockets. I am using the websockets 'out-of-spec' since I am doing 1 receive concurrent with multiple sends. When a close message is received, the websockets is closed (and disposed) on the server. Some sends might still be 'in-flight' at that time. I expected those to throw objectdisposed (instead of the webserver exiting).

@tmds Think you could provide a sample application that mimicks what you're doing?

I am trying to benchmark an asp.net 5 sockjs implementation I am developping. The benchmark consists of an test website (ASP.NET) and a sockjs benchmark (forked project, java).
The testwebsite lives here: https://github.com/tmds/Tmds.SockJS/tree/master/test/WebSites/TestWebSite.
dnx kestrel

The load program lives here (jar): https://github.com/tmds/sock-benchmarking/releases/download/v0.1.0/SocketIOLoadTester.jar
java -jar SockIOLoadTester.jar sockjs localhost:8081 logprefix

The load tests connects a number of clients (websockets) to the server. Then it sends a number of messages via those clients. When the server receives a message, it broadcasts it back to the clients. This is implemented here: https://github.com/tmds/Tmds.SockJS/blob/master/test/WebSites/TestWebSite/BroadcastMiddleware.cs.
The server implementation currently does one ReceiveAsync and (multiple) SendAsync concurrently on a WebSocket, which is 'undefined behaviour'. (see https://github.com/aspnet/WebSockets/issues/42)
Perhaps the error is the result of a scheduled write on the KestrelThread on a Stream which has been Disposed in the meanwhile.

Great! This will help reproduce the problem when we get someone to look at it.

@halter73 Please have a look when you have some time.

@halter73 do you have an idea when you'll have some time?

@tmds I haven't gotten a chance to run your repro website yet, but I definitely could see how a UvStreamHandle could be closed before WriteAllPending/uv_write runs. I think at this point we should check if the handle as been closed.
The handle can only be closed on the libuv thread, so there shouldn't be any thread safety issues. I'm working on HTTPS and some refactoring right now, but I hope to be able to fix this by next week.

@halter73 In case it has been closed, throwing ObjectDisposed on those pending operations is probably what should happen? When you've implemented this, I can verify the error no longer occurs in my scenario.

I'm fairly certain that this was fixed by @lodejard's refactoring. This change to SocketOutput checks that _socket.IsClosed is false before using the socket the Execute, StageTwo or StageThree methods.
This change will be in beta8.

@tmds I verified your app under beta8 and the issue went away. (under the same environment I could repo this issue under beta7). It looks the like exception is indeed fixed. I'm going to close this issue. Thanks.

Great! Thanks.

No problem. If you still encounter similar issue on beta8, please feel free to reopen this issue.


Azure Resource Graph query | get VM license benefit type

I can get a no of things about VMs from "resources | where type =~ 'Microsoft.Compute/virtualMachines'" and then expanding the properties. What I am looking for is the Windows license type. The same information is available on the portal under "Virtual Machines" - add Columns - "OS licensing benefit". The values are of type "Azure hybrid benefit", "Not enabled" etc.
I can get the same information for SQL Server on IaaS via properties.sqlServerLicenseType in microsoft.sqlvirtualmachine/sqlvirtualmachines, so guessing there is a way to get it for VMs? Any feedback will be greatly appreciated.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ac94b233-b387-fd3e-1942-83044d29fc80
Version Independent ID: f6554623-0d7b-f4cc-fc00-8616010f0714
Content: Advanced query samples - Azure Resource Graph
Content Source: articles/governance/resource-graph/samples/advanced.md
Service: resource-graph
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

@sayanghosh123 AFAIK below is the query you can use to fetch license type information.
resources | where type =~ 'Microsoft.Compute/virtualMachines'| extend licenseType = tostring(properties.['licenseType'])
If you opt ' Yes' as shown below then 'licenseType' property is provided in 'properties' column of the query's output.

Typical values for 'licenseType' property are ''Windows_Server" (for Windows server images like 2019 DC, etc.) and "Windows_Client" (for Windows client images like Win 10, etc.)

@sayanghosh123  Closing this issue for now. If there are further questions or feedback regarding referred Azure document then please let us know so that we will gladly continue the discussion.

Thanks @KrishnaG-MSFT - you are awesome! That seems to work. Just one final clarification -
This seems to show "Windows_Server" where AHB is used, and blank elsewhere.
Portal shows

"Not supported" for Linux (I assume query will show blank)
"Not enabled" for Windows where AHB is not used (I assume query will show blank)
"Azure hybrid benefit" for Windows where AHB is used (I assume query will show "Windows_Server")
Is that a correct read?
I do have similar questions about some other ARM graph queries, will open other issues for them.

@sayanghosh123 Sure. Below is my response.

"Not supported" for Linux (I assume query will show blank)

Yes, query will show blank under 'licenseType' column

"Not enabled" for Windows where AHB is not used (I assume query will show blank)

Yes, query will show blank under 'licenseType' column

"Azure hybrid benefit" for Windows where AHB is used (I assume query will show "Windows_Server") Is that a correct read?

Yes, query will show "Windows_Server" under 'licenseType' column

Thanks @KrishnaG-MSFT - you are awesome!

here a version to only get Windows VM and summarize the result:
Resources
| where type =~ 'Microsoft.Compute/virtualMachines' and properties.storageProfile.osDisk.osType =~ 'Windows'
| summarize count() by tostring(properties.['licenseType'])


Javadoc tasks send standard-doclet arguments to custom doclets

I maintain a build that has a Javadocs task using a custom doclet (specifically, https://github.com/MarkusBernhardt/xml-doclet). This build broke when upgrading Gradle from 5.6.4 to 6.0.1; the javadoc executable gave an error message javadoc: error - invalid flag: -notimestamp.
I'm not very familiar with the Javadocs ecosystem, but it seems -notimestamp is a flag of the standard doclet, not the core executable. I would expect it to not get sent if a custom doclet is used.
The Gradle code does already include this distinction (between javadoc arguments and standard-doclet arguments) in its structure, having both a StandardJavadocDocletOptions and a CoreJavadocOptions.
Expected Behavior
When a Javadoc task uses a custom doclet, don't send arguments that are specific to the standard doclet (namely, the -doctitle and -notimestamp arguments). Probably make an exception for anything manually specified.
Current Behavior
The -doctitle and -notimestamp flags are sent regardless of which doclet is used, sometimes causing javadoc errors.
Context
I can work around the issue by adding the following lines to the task config:
task buildXmlJavadoc(type: Javadoc) {
    // ...
    title = ''
    options.noTimestamp(false)
    // ...
}

Mostly the impact is that this was an unexpected failure when trying to upgrade, and there may be more instances of that in the future. (It also took a while to figure out the workaround.)
Steps to Reproduce
Repro here: https://github.com/AlexLandau/gradle-javadoc-notimestamp-error
Note that this specific repro needs to be run with Java 8. I used Azul: https://www.azul.com/downloads/zulu-community/
Your Environment
Run on MacOS with Java 8.

It's a serious regression for people using custom doclets. This commit is responsible for adding this: https://github.com/gradle/gradle/commit/9a2ee4817c30
@vlsi You added it - could you take a look?

Just in case, the current Gradle implementation is as follows:

Gradle always uses StandardJavadocDocletOptions class for the options no matter which doclet is used
Gradle builds all the options to the options file, and it launches javadoc with that
Of course, if the custom doclet is used, it might easily crash if an unexpected option is added to the file.

Note: doclet API does have a way to check if an option is supported at all or not.
That is optionLength method of the doclet
Note: it would require to load the doclet class in order to call optionLength. So there's no clear way to check if the option is supported or not. I don't think there's an API to tell the doclet to ignore unsupported options.
So I see the following options:
A) Just leave it as is and document the behavior (e.g. add warning at the execution time). That is, leave the configuration up to the users who configure custom doclets
B) Implement optionLength-based detection of unsupported options and do something if the option is not supported by the doclet
C) File a ticket to JavaDoc so they switch to notimestamp by default (I don't think it is feasible :( )
Note: I do think that the exclusion of timestamps by default helps a lot. There is extreme amount of projects that just configure javadoc, and they tend to produce gigabytes of timestamp-induced diffs.
I do see you have issues, and I recognize that is sad, however, I don't run in those issues, and I don't feel I want to implement optionLength-based approach.
Gradle's model for javadoc task is not ideal, however, it works, and workarounds are clearly available. So I don't think the issue must be a priority.
However, feel free to file a PR, and I might be happy to review it.

Well, this check could be moved to javadoc task: if no custom doclet is specified then you could emit notimestamp (if it doesn't have any value other than the default, unset state).
An alternative would be to allow javadoc task users to override the options with a different subclass than StandardJavadocDocletOptions. The field already has a "minimal" type anyway so I don't see the reason why StandardJavadocDocletOptions should be the enforced (unchangeable) default.

if no custom doclet is specified then you could emit notimestamp

That would be a non-tivial change, and it would result in different behavior depending on the doclet.
Suppose there's a user with a custom doclet that does support notimestamp option.
What would you suggest?
That is why I don't consider that approach.

StandardJavadocDocletOptions should be the enforced (unchangeable) default.

AFAIK that is the current implementation.
Of course, it might be smarter, however, that implementation requires effort to implement, and it would require some effort from the maintainers to review the change.

(unchangeable) default

I guess it is very well changable.
Have you tried tasks.withType<Javadoc>().configureEach { ... } ?
I think it should be able to override the options.
Note: current JavaDoc implementation does not support lazy configuration resolution for custom doclets.
So I would expect that the users of custom doclets would anyway use their workarounds there
For instance, here's what I have to activate lazy resolution (e.g. to avoid doclet resolution when I build regular jar only): https://github.com/autostyle/autostyle/blob/3edcb79a2ddd0c8e6a988d5b6d8fd3ee2f9a729a/buildSrc/src/main/kotlin/mdoclet.gradle.kts#L41-L45
I don't think adding notimestamp there would hurt much.

Well, you have already changed the default and this changed the behavior for everyone... Going back would revert the previous default (and javadoc tool default). You're force-feeding an option to javadoc that normally isn't there.
As for configuring javadoc, the options field's type isn't configurable.
https://github.com/gradle/gradle/blob/8df8e9b6746d7f8e7d34b802719e28754bdaa056/subprojects/language-java/src/main/java/org/gradle/api/tasks/javadoc/Javadoc.java#L100

behavior for everyone

Do you have estimates on the number of impacted projects?
Do you have estimates on the number of projects that use custom doclets?
My understanding is that the number of projects/builds with custom doclets is much less that the number of total projects and builds that use javadoc.
That is why I suppose that the removal of timestamps helps a lot of Gradle users.
The workaround is there, so I don't see why there must be a rush.
If you feel that javadoc task with custom doclets is important, please feel free to file a PR.
Frankly speaking, I don't have enough time and passion to improve that.

As for configuring javadoc, the options field's type isn't configurable.

I mean you can have the following workaround:
options.noTimestamp(false)

Note: if you support a custom doclet, then you might want to release a Gradle plugin that would configure javadoc task to use the doclet. The plugin could configure the relevant options as well.

Vladimir, you changed the default of each and every javadoc task invocation (unless timestamp option was explicitly set): previously it didn't add "-notimestamp" option to javadoc invocation, since your commit it does.
I understand the intention was to improve the "default" look and feel of generated documentation but I don't think this is the build tool's job to do so. It's "javadoc" not "javadocWithNiceDefaults". OpenJDK's javadoc-mailing list is the right place to try to change the tool defaults; downstream build tools like ant or gradle shouldn't just pick a set of options they deem "right" for people. Imagine a surprise when you upgrade the build tool and all of a sudden your outputs are different (on the same JDK).
I know there is a workaround but you could argue the exact opposite: if somebody doesn't like the default they can just as easily modify the defaults of all javadoc tasks in their projects with a single statement...
bq. Frankly speaking, I don't have enough time and passion to improve that.
My whole point is that it's not about improving the state of things. It's about reverting a perceived "improvement" that in my opinion isn't one. Javadoc task should behave the same between gradle updates on the same underlying JDK (because your expect the same set of options to be passed to the tool).
If you disagree, fine. I just expressed my opinion on the matter.

I agree with @dweiss, just wasted half an hour on finding this issue, added option.noTimestamp(false) as well.

This is even worse in the Kotlin DSL, where the noTimestamp option can't be accessed without a static typecast.  option.noTimestamp(false) thus becomes the rather cumbersome (options as StandardJavadocDocletOptions).noTimestamp(false).  This is not very discoverable, particularly if you don't know that's what you're looking for!
The Maven javadoc plugin solves this by simply providing a property useStandardDocletOptions, which defaults to true, but can be set to false when using a custom doclet.  This seems like a sensible compromise: the defaults can be whatever you judge best for most users, but there is a straightforward, obvious, and future-proof way to turn off the magic if it breaks things.

I'm glad this discussion exists or I would have spent a long time trying to figure out where that option was coming from.  I had assumed it was a misconfiguration in our complicated custom doclet invocations that was somehow exposed on upgrade.  I didn't expect it to be a new "feature" in 6.x.  This is an unintuitive change.
It is mentioned in the upgrade docs but I didn't notice that until after I understood what the problem was.  Adding a line to the upgrade docs about disabling the change with options.noTimestamp(false) for custom doclets would be helpful.

Greetings.
Apologies for coming late to the party. I have taken up the XML Doclet and amended it:

working around the missing options title and noTimestamp
works with any modern JDK as long as languageVersion.set(JavaLanguageVersion.of(11)) is set
outputs XML, Sphinx Restructured Text (and planned support for Markdown, Docbook and Ascii Doctor)

So the workarounds are not necessary anymore.
Cheers!


Problem: Integration tests not easy to setup

Current integration tests requires docker images and the ethereum built requires an ArchiveNode
Its a bit tricky to trigger on the CI as it built and push docker at every cycle.
Port cronos integration test using nix may be a better solution in long run
https://github.com/crypto-org-chain/cronos/tree/main/integration_tests

integration tests fixes in https://github.com/crypto-org-chain/gravity-bridge/pull/148


Add service provider

Description of the Change
This PR adds service provider, so other packages can toggle Fuzzy Finder with custom query text. Also it replaces changes from PR #137 and PR #181 can be implemented as a package.
Alternate Designs

As introduced in #137.
Everyone make their own implementation of Fuzzy Finder (like in related-files or related)

Benefits
Packages can toggle Fuzzy Finder with custom query.
Possible Drawbacks
No drawbacks
Applicable Issues
No issues
To Do

[x] Add service provider
[x] Add specs
[x] Add docs

Hey guys, can anyone provide some feedback about this one. I'd really like to see this going forward.
cc @50Wliu, @as-cii, @lee-dohm

So this service would open the fuzzy finder with pre-populated search text? I'm not sure how beneficial this would be to other package authors. The two packages you mention provide a different set of files to select from and pre-populated search text wouldn't necessarily help with that.

Hey @lee-dohm , thanks for your response!
Let me show you few cases:

User wants to search files with name similar to word under cursor, selected text or quoted text. Like in Rails we have <%= render 'path/to/partial' %> and with this service we'll be able to find this partial file in one click. I made little demo of this feature.
User wants to find files related to their current context. For example, in Rails if we are in model Post, with this service we'll be able find all files which start with posts.
User wants to search for a file in some directory. Like pre-populate fuzzy-finder with app/models and search only there.

Sorry for Rails-only cases, but I'm sure many users will benefit from future like this. Also, Sublime Text has similar feature 😉.


Library not working when spark job deployed in databricks 7.3 LTS

Library not working when spark job deployed in databricks 7.3 LTS with Spark 3.0.1 (Scala -2.12) + (net.heartsavior.spark:spark-sql-kafka-offset-committer_2.12:0.3.0-spark-3.0).
Following warning is displayed in the logs, however same is working in Local spark standalone cluster(with Apache Spark Distribution)
WARN KafkaOffsetCommitterListener: Cannot find query f835de4b-2919-4f60-b849-6082d294e4f7 from active spark session!
Is this library works fine with Kafka SASL SSL?
Please let me know what is the issue.

The project is not intended to support vendors' distribution. You may need to fork the project and fix it by yourself, or contact Databricks. Thanks for the interest.


Wizards starts WebUI when API not yet ready

The WebUI is started before the Raiden API is ready. It works after a minute but it is not very nice first thing to see is an API error in the webui.
The WebUI is reachable while the RestAPI in raiden is not started yet. This causes the errormessage shown.

Use the status endpoint as a trigger to start the webUI

[ ] Query status endpoint of Raiden and start WebUI after Raiden ist ready
[ ] This doesn't really fixes the problem, we need to get the UI / UX designers on that

Note: #124 fixes the start timing of the WebUI, by polling the /status api for a {"status": "ready"} response.
However, before that response, the same API can be used to return
{
   "status": "syncing",
   "blocks_to_sync": "130452"
}

which can (and probably should) be displayed on the waiting page.


Small area of the search button of the workbench does not work

Describe the bug
This is probably not the bug but maybe hope that some usability can be improved
To Reproduce
Steps to reproduce the behavior:

Go to workbench
Click on search button's lower right area
Check that it does not works

Expected behavior
The function should work on all areas of the squared search icon
Screenshots

Desktop (please complete the following information):

T-map DEV 3.0.6-20181029094533

Additional context

@eltriny
돋보기 아이콘 바깥쪽을 클릭하면 작동을 안하네요.
기능상 문제라 작업 우선순위를 높여야 할것 같습니다.


3 ➡ 4

➡ Forward port
Port ign-gui3 to ign-gui4
Branch comparison: https://github.com/ignitionrobotics/ign-gui/compare/ign-gui4...ign-gui3
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

Failed tests appear to be flaky. Can I go ahead and merge this @chapulina ?

Yup, go for it!


Rework getdevicelog() to handle fetching more when "has_next" is True

See discussion in #219

Thanks @uzlonewolf !
QQ: Should we add a warning in the README under Cloud that the free Tuya IOT account has restrictions on the number of API calls you can make, and to proceed with care?

That probably wouldn't be a bad idea.

I just tried this out. Thanks heaps. I'd have one recommendation for data integrity though. When multiple fetches are returned (i.e. the first one returns has_next=True) then the current_row_key entry becomes invalid or meaningless. I see three options to improve the integrity of the returned results (internal consistency):

Remove that key from the result
Set it to None or n/a or some indicator that there is no valid value
Replace it with a list that contains as many values as the 'fetches' key conveys

I lean towards 3.
It's small issue, as it won't impact what I'm doing one jot. But it just lept out at me as I looked at the first return with 3 fetches.

It is my understanding - granted, I have not verified this - that the current_row_key is the key for the very first row returned.  As such it should not change even if multiple requests are made to get every requested row since the very first row in the entire set remains the same.
What are you seeing?

I see value for it, but haven't checked what it means, as it's clearly irrelevant and doesn't apply to the logs anymore as they come from multiple rows. Which is why I'd recommend 1, 2 or 3 above. But could add:

rename 'current_row_key' to 'first_row_key'

Which is another option to improve integrity of the response.
P.S. Am working on catching all my logs in a database now, and producing uptime reports for the switches to get a feel for how long they stay up. Essentially my logs come in quadruplets, an online, and offline, a battery_state and a datareport (doorcontact_state) - in part because longer term I'd sort of prefer just to keep the data local and if there's any way in the future I can source by keeping a packet sniffer running on my gateway I'm in - might even block on-tranmission to the Tuya cloud come that day.

I'm still not seeing the issue.  If you call getdevicelog(..., size=1) getdevicelog(..., size=5) and getdevicelog(..., size=50) they will all return the exact same current_row_key, the only difference is how many log entries are in the result.  The loop this PR adds does nothing except extend size= virtually to work around the hard limit of 100 entries.  I'm not seeing why the behavior of getdevicelog(..., size=200) should be different than getdevicelog(..., size=100).
As for the key itself, I've got the format mostly worked out.  When you base64 decode it, you get 4 fields separated by an underscore.  The first field consists of 8 hex chars (4 bytes) followed by the reversed device ID (i.e. if the dev ID is 12345678, the first field will be<PHONE_NUMBER>654321).  The 2nd field is the maximum positive value of a signed 64-bit int minus the event_time (i.e. if the event_time is<PHONE_NUMBER>, the 2nd field will be<PHONE_NUMBER>854775807 -<PHONE_NUMBER> =<PHONE_NUMBER>183535464).  The 3rd field is the event_type, and the last field is the source DPS ID.

Wow, you're amazing diligent and awesome! Great reverse engineering.
I figured row_key was a unique way of identifying a "row" whatever that is at the server side. And so is associated with a given result set. Which means "current_row_key" if we're altering the result set (augmenting logs), then it becomes invalid.
As I said, I'm not much fussed as all I want is the logs ;-).  Which is behaving oddly at present almost as if its rate limited. When I fetch logs of 4 doors, only the first returns results. Mind you ,I'm experimenting with start and end of 0 and start of 0 and end of maxint. Both seem superficially to return all logs. Long run I'll stick to daily fetches, for now am experimenting with all logs.

And so is associated with a given result set. Which means "current_row_key" if we're altering the result set (augmenting logs), then it becomes invalid.

Except it's not, it's the key for the very first row in the set.  In addition to size= I mentioned earlier, you can also change start= to get a completely different result set and yet it will still have the same current_row_key.  As long as the very first row is the same then the current_row_key will also be the same regardless of whatever else changes.
I agree that first_row_key would be a better name, however TinyTuya generally does not rename stuff and deviate from the official Tuya documentation just because a different name would be more descriptive.  (See also: "boardcast" instead of broadcast, "ablilty" instead of ability).  If you can convince @jasonacox then I will be more than happy to change the code to search for and rename it.

Thanks for clarifying, that makes a lot of sense!
Not sure what the boardcast and ablity is about? So I search repo and now I get it. Amazing how clumsy Tuya is.


feat: extend GTF to support query region for ngs view

Support query region for GTF files called within ngs view.

This is now tracked here: https://github.com/orgs/stjude-rust-labs/projects/4/views/2?pane=issue&itemId=59611901.


Not issue but asking :)

Is there an option to serialize empty values too? Thanks for great plugin 👍

Duplicate of https://github.com/macek/jquery-serialize-object/issues/38, https://github.com/macek/jquery-serialize-object/issues/80


python: Update manifest to support arm64 and remove python-unpacked

What type of Apps related PR is this? (check all applicable)

[ ] ✨ Add Manifest
[x] ♻ Refactor
[ ] 🐛 Bug Fix
[x] 👷 Optimization
[ ] 🚩 Other

Description
Update the manifest to support ARM64 and adjust the notes to suggest using LessMSI for the installation process.
Remove the unnecessary manifest ‘python-unpacked’, since the use of LessMSI fixes the issue.
Related Tickets & Documents
none
[optional] What gif/emoji best describes this PR or how it makes you feel?
:recycle: :rocket: :lipstick:
Did you verify the followings
Add/Modify a description in the manifest?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Check URLs?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Update to the latest version?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Update Hashes?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Format the json manifest?

[ ] 👍 yes
[ ] 🙋 yes, but I need help
[x] 🙅 no, because they aren't needed

Did you identify extra steps
Notes in the manifest?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Application Dependencies?

[ ] 👍 yes
[ ] 🙋 yes, but I need help
[x] 🙅 no, because they aren't needed

Application Suggestions?

[ ] 👍 yes
[ ] 🙋 yes, but I need help
[x] 🙅 no, because they aren't needed

Pre-installation steps to perform?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Post-installation steps to perform?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

File persistence to perform?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Your changes do not pass checks.
python

[x] Description
[x] License
[x] Hashes
[x] Checkver
[x] Autoupdate
[ ] Autoupdate Hash Extraction

/verify

All changes look good.
Wait for review from human collaborators.
python

[x] Description
[x] License
[x] Hashes
[x] Checkver
[x] Autoupdate
[x] Autoupdate Hash Extraction


permission denied on folder for minitest-20.12

Hi,
The folder mentioned here
https://github.com/desihub/desitest/blob/20.12/mini/minitest.ipynb
doesn't seem to have the read permissions on NERSC:

ls /global/cscratch1/sd/sjbailey/minitest-20.12-test
ls: cannot open directory '/global/cscratch1/sd/sjbailey/minitest-20.12-test': Permission denied

 S

Ah.  /global/cscratch1/sd/sjbailey/minitest-20.12-test is where it was originally run, but the final archival location which should be visible to all DESI collaborators is at
/global/cfs/cdirs/desi/datachallenge/reference_runs/20.12/setup.sh
To do:

update notebook instructions for where the final archival directory is likely to be found even if the pre-release testing was run in $SCRATCH
update all references to /project/projectdirs/ -> /global/cfs/cdirs/
within setup.sh, use logic like desi/spectro/redux/mini/setup.sh to support moving the script without having to edit it, e.g. modifying this:

# Support the ability to move the production
#   - get abspath to directory where this script is located
#   - unpack proddir=$DESI_SPECTRO_REDUX/$SPECPROD

proddir=$(cd $(dirname "$BASH_SOURCE"); pwd)
export DESI_SPECTRO_REDUX=$(dirname $proddir)
export SPECPROD=$(basename $proddir)

Ah.  /global/cscratch1/sd/sjbailey/minitest-20.12-test is where it was originally run, but the final archival location which should be visible to all DESI collaborators is at
/global/cfs/cdirs/desi/datachallenge/reference_runs/20.12/setup.sh
To do:

update notebook instructions for where the final archival directory is likely to be found even if the pre-release testing was run in $SCRATCH
update all references to /project/projectdirs/ -> /global/cfs/cdirs/
within setup.sh, use logic like desi/spectro/redux/mini/setup.sh to support moving the script without having to edit it, e.g. modifying this:

# Support the ability to move the production
#   - get abspath to directory where this script is located
#   - unpack proddir=$DESI_SPECTRO_REDUX/$SPECPROD

proddir=$(cd $(dirname "$BASH_SOURCE"); pwd)
export DESI_SPECTRO_REDUX=$(dirname $proddir)
export SPECPROD=$(basename $proddir)

Ah, thanks.I was looking for some simulated files for the last run, and stumbled on the permission denied error and didn't  look further.

Ah, thanks.I was looking for some simulated files for the last run, and stumbled on the permission denied error and didn't  look further.


Fix usernames in commits

Done.

Not yet.

Guide to do it: https://help.github.com/articles/changing-author-info/

Done. Hopefully no more git push -f with master and development.


Doesn't work with --browserify option

Steps:

Run cordova emulate ios --browserify with installed cordova-plugin-wkwebview

Actual result:
It looks like js code of this plugin uses cordova.define function which is not available for --browserify build.
https://github.com/ionic-team/cordova-plugin-wkwebview-engine/blob/master/src/www/ios/ios-wkwebview-exec.js#L170
Expected result:
Plugin shouldn't use cordova.define and cordova.define.remove functions

Found an official issue https://issues.apache.org/jira/browse/CB-11311 and created a temporary workaround https://gist.github.com/stalniy/90202f09c6ededff54b959e79ae3962e


How to execute this script from console

Hi,
I was only running from X-Code Instruments so far.
I have continuos integration setup and would like to run this test from terminal.
Could you please provide the command ?

How do you collect results automatically when using this tool with your CI system?
Thanks.

@Ricardo1980 were you able to figure out how to use this tool with CI systems?


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/776 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit 140aef5:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-02-02-14-07-46 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Version install of dependencies

I was looking at these lines and realized that the current code will not fetch a newer version of MacNotify/PSNotifySend if one exists.
We should change this to:
(Get-Module -ListAvailable MacNotify).Version -gt x.x.x

where x.x.x is the minimum version required to use this module.
Today, we're ok, but for -SoundFile we'll have to take this into account because I added it in later to PSNotifySend

We'll need this issue fixed for https://github.com/Windos/PoshNotify/issues/9


Validation of data

AFAIK, there should be at least:

A machine-readable profile allowing the validation of datapackage.json
A machine-readable profile for the CSV data table (mandatory fields, ...)

For automatic validation, we might need custom tools if all the checks needed* are not available in the standard frictionless tooling - to be investigated)
*: I'm thinking of the guaranteed row order, for example.

Nico, can you describe what you want to test exactly? I suggest:

profile is valid json
table schema is valid json
an example vpts data package is valid against the specs

In practice, I'd love to have one single command that checks as many things as possible to ensure a given package is compliant.
I guess the frictionless-py tools already provide most of it:

ability to check datapackage is not only valid JSON, but also conforms to our specifications (required metadata, ...)
ability to check the table schema conforms to our specs

I haven't checked yet, but there might be points in our specs that can't be checked yet with the existing tools (for example the data row order - by datetime then altitude).
We might therefore implement a simple tool (vpts_validate under the vpts_tools repo?) that would be a thin wrapper around the existing validation tools, but also adding:

out custom checks
the ability to perform all checks with a single command

I would start with the default
frictionless validate datapackage.json

It does many things already

@niconoe picking this up again, but this issue might need to be moved to vptstools.
Validation can rely on frictionless, unless we create our own definition for what is a required field (#26). Below I'm using package level validation, but I'm pretty sure you can do resource level validation as well. You'd have to use the --schema-sync option, because our specs state that not all fields have to be included.
Valid example

example_vpts.csv (created as in #25)
A datapackage.json:

{
  "id": "example_vpts",
  "resources": [
    {
      "name": "vpts",
      "path": "example_vpts.csv",
      "profile": "tabular-data-resource",
      "format": "csv",
      "mediatype": "text/csv",
      "encoding": "utf-8",
      "schema": "https://raw.githubusercontent.com/enram/vpts/main/_data/vpts-table-schema.json"
    }
  ]
}

Validates with:
frictionless validate datapackage.json --schema-sync


[Boost] *Update to new rleases when they are released upstream

Do we have anybody updating all the Boost ports when new releases are released upstream?
If not I'm happy to do this.
Thanks,
Sean.

@ras0219-msft generally does it see #7959


feat: expose underlying client instance

🔗 Linked issue
#210
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[x] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Adds instance key to all drivers.

📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

I'm not able to add proper instance to mongodb though since it causes a build error because of this issue of unbuild.

Feel free to add for mongo too will try to fix build issue

@pi0 Hi! Would it be possible to release a new version soon to include this? I'm eagerly looking forward to using them in my project. Thanks in advance 🫶

Surely. it might be delayed for a little longer since is in parallel to other releases.


Lock account while logged in?

Some users are being douche bags and are logging into players who are already logged in which causes them to be kicked, can a command be added to /lockaccount which won't let anyone else login while they are authenticated?

Can you push this update to a new version? I don't know how to compile this into a jar file

Uploaded


Examples are failining on window os

#11 Action with windows os is failing on tests

closed with #11


feat: add vercel

Add vercel icon ▲ (U+25B2) so it should not need any special char added to a font.
I opened this but realized it's a dead repo 💀
https://github.com/vorillaz/devicons/pull/157

Run make to generate the alternate color.

Add vercel icon ▲ (U+25B2) so it should not need any special char added to a font.

Looks fine

I opened this but realized it's a dead repo 💀
vorillaz/devicons#157

Vercel is not on Nerd-Fonts but is on https://github.com/devicons/devicon, I think it could be a good option to merge it on NF but I think would need more feedback from devs/users to do it. Related comment: https://github.com/ryanoasis/nerd-fonts/issues/1616#issuecomment-2089384102

Icon responding to themes

LGTM, are we good to :shipit:?

LGTM, are we good to :shipit:?

I was just taking my time because it's the first PR I merge here, hahaha


Integration Test Grooming

Addresses some inconsistently passing tests on the 2.0 branch.   There are a few more than need addressing (primary in RecommissionedNodeTest).

Removing [wip] tag from this.  A few of the recent fixes were required to accommodate recent changes targeted for 2.0.12 and all the other changes seem to have positive impact.  Would be nice to get this merged in ahead of the release.


Nginx drupal rule for protect files and directories was missing leadi…

…ng slash for path.

Confirmed working after updating to 1.0.2 upstream.


Forwarding to ExternalNames ignores port

I have sought support on this issue, on stackoverflow and the slack channel
However, this appears to be a bug.
What did you do?
Added traefik to a cluster:
kubectl apply -f https://raw.githubusercontent.com/containous/traefik/master/examples/k8s/traefik-rbac.yaml
kubectl apply -f https://raw.githubusercontent.com/containous/traefik/master/examples/k8s/traefik-ds.yaml

And set an ingress for an externalname with an alternate port:
---
kind: Service
apiVersion: v1
metadata:
  name: gitlab-exp
  namespace: kube-system
spec:
  type: ExternalName
  ports:
  - name: app-port
    port: 4080
  externalName: <IP_ADDRESS>
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: gitlab-exp
  namespace: kube-system
  annotations:
    traefik.frontend.passHostHeader: "false"
    kubernetes.io/ingress.class: traefik
spec:
  rules:
  - host: gitlab.example.com
    http:
      paths:
      - backend:
          serviceName: gitlab-exp
          servicePort: app-port

What did you expect to see?
Traefik serving the externalname from 4080 on it's port 80
What did you see instead?
Traefik serving <IP_ADDRESS>'s port 80 and not port 4080
Output of traefik version: (What version of Traefik are you using?)
1.5.4
from the latest docker image:
traefik                                                  latest              fde722950ccf        7 days ago          49.7MB

What is your environment & configuration (arguments, toml, provider, platform, ...)?
default for kubernetes, the kubectl commands above have been run on many freshly built clusters on many different machines and data centers.  Including https://labs.play-with-k8s.com/ upon which this can be replicated easily.

to replicate on https://labs.play-with-k8s.com/ start up your first instance and:
curl https://gist.githubusercontent.com/joshuacox/ed8173a43659f01ede983fcbaa0dafe2/raw/8faf3eca30cff2cbc319b67e8fc420f5eea084b7/kubestart.sh | bash

create a second instance and:
curl https://gist.githubusercontent.com/joshuacox/bddac4a9e0595a8ff08b2735a05ff724/raw/a9a9fc86576d8538079a833248ae532d55c6db29/traefik-test.sh|bash

to create two nginx containers one on 80 (bad), and one on 4080 (good)
[node1 /]$ curl -s https://gist.githubusercontent.com/joshuacox/8c7a6ce9a44ba5b51ee89de656f98cfa/raw/b0caa39196a2369a74ae6e32bb1a41288446f8f3/addingress.sh > addingress.sh
[node1 /]$ chmod +x addingress.sh
[node1 /]$ ./addingress.sh <IP_ADDRESS>
[node1 /]$ curl gitlab.example.com
bad
[node1 /]$ curl <IP_ADDRESS>
bad
[node1 /]$ curl <IP_ADDRESS>:4080
good

Thanks for reporting!
This seems to be a duplicate of #1816.
I'll close the issue -- if you think it addresses a separate problem, please let us know.


Fixes build warning in integration-tests project

Updates integration-tests/pom.xml to fix the following warning during maven build:
[WARNING] Some problems were encountered while building the effective model for oracle.kubernetes:integration-tests:jar:4.0.0
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.codehaus.mojo:exec-maven-plugin @ line 196, column 21
It was caused by a change in PR 2715
jenkins run: https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/8203/
compared to jenkins run on main: https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/8204/

updated description with:
jenkins run: https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/8203/
compared to jenkins run on main: https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/8204/

This PR will conflict with PR 2732. Converting to draft to prevent merging.

Closing this PR as Sankar is including this change in PR 2732


Output topic level authorization key

How can we output a topic level authorization key?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4249cca5-05cd-cf9e-10f9-b9ed6b20e99b
Version Independent ID: fbe43e70-d4ba-0b14-1649-2a913c104a61
Content: Create a Service Bus authorization rule using Azure Resource Manager template
Content Source: articles/service-bus-messaging/service-bus-resource-manager-namespace-auth-rule.md
Service: service-bus-messaging
GitHub Login: @axisc
Microsoft Alias: aschhab

Hi @shashankkr - Thank you for your feedback! We will review and update as appropriate.

Hi @shashankkr - The API below returns the topic level keys: https://docs.microsoft.com/en-us/rest/api/servicebus/topics/listkeys
We will now proceed to close this thread for now. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Fails on 19.04.2022

I've just tried it:
(.venv) (base) boileau@m-boileau:  [master]  /tmp/agricas$ python --version && date && python agricas.py
Python 3.9.12
Mar 19 avr 2022 08:15:12 CEST
Traceback (most recent call last):
  File "/private/tmp/agricas/agricas.py", line 140, in <module>
    menu_lst = get_data()
  File "/private/tmp/agricas/agricas.py", line 57, in get_data
    assert date is not None
AssertionError

Fixed. It was because of some malformed date like "Monday" not followed by a day of the month.


update(freestyle): update eslint.rc to ignore dist folder after deployment

Issue Description
Issue #213
relevant to issue in App Gen where eslint doesn't cover deployed app dist folder and throws errors. This has since been rectified for Fiori-elements but is still presenting issues for fiori freestyle, as shown:

Checklist for Pull Requests

[x] Supplied as many details as possible on this change.
[x] The code conforms to the general development principles.
[x] This branch is appropriately named for the associated issue.

Hi @ciaradaly2021 thanks for the fix.
Can you please also create an issue https://github.com/SAP/open-ux-tools/issues/new/choose and link it to this pr

Hi @ciaradaly2021 thanks for the fix. Can you please also create an issue https://github.com/SAP/open-ux-tools/issues/new/choose and link it to this pr

Issue created: https://github.com/SAP/open-ux-tools/issues/213.

@ciaradaly2021 - would be best to run pnpm cset to create a patch release so that a new version is released after merge to main. And update snapshots for failing tests

I made this change on github as it is small, I don't have this repo locally but if needed I can. I won't be available again until Thursday so if this needs to be changed asap it will likely have to be performed by someone else, if not I can do on Thurs. Thanks.

Replaced by https://github.com/SAP/open-ux-tools/pull/227 closing. Thanks @ciaradaly2021


fix: sql test dont work in Postgresql because required alias

Postgres doesn't like our current test generation because it doesn't have an alias
called `Result::unwrap()` on an `Err` value: QueryError { query: "error returned from database: subquery in FROM must have an alias", error: "SELECT id, COUNT(*)\nFROM (WITH\ntest_source AS (SELECT * FROM other_schema.test_table),\ntest_model AS (SELECT id FROM test_source)\nSELECT * FROM (SELECT id FROM test_model) AS alias)\nGROUP BY id\nHAVING COUNT(*) > 1;\n" }
thread 'databases_postgres::tests::postgres_sql_test' panicked at rust/quary-databases/src/databases_postgres.rs:839:54:
called `Result::unwrap()` on an `Err` value: QueryError { query: "error returned from database: subquery in FROM must have an alias", error: "SELECT id, COUNT(*)\nFROM (WITH\ntest_source AS (SELECT * FROM other_schema.test_table),\ntest_model AS (SELECT id FROM test_source)\nSELECT * FROM (SELECT id FROM test_model) AS alias)\nGROUP BY id\nHAVING COUNT(*) > 1;\n" }

#262 fixes this issue in Postges


Improve initialization of wav2vec2/hubert model for pre-training

This PR improves the Wav2Vec2/HuBERT model regarding model pre-training.

The model initialization of positional embedding and transformer module is essential to model pre-training. The accuracy of unmasked frames should be higher than masked frames, as it is an easier task. but without the initialization, the accuracy of masked frames is higher than unmasked frames.
Compared the performance after two epochs with 16 GPUs.

With model initialization, the accuracies of masked/unmasked frames are 0.08/0.11.
Without model initialization, the accuracies of masked/unmasked frames are 0.06/0.04.

After adding the model initialization, the gradient is easy to overflow (aka nan gradient). In paper Self-Supervised Learning for speech recognition with Intermediate layer supervision the authors propose a simple but effective method to mitigate the overflow issue, by scaling down the multiplication of query and key and subtracting the maximum value from it (subtracting a constant value won't change the output of softmax). Then it guarantees the value won't be overflowed.
In the original fairseq, the mask indices are generated by numpy.random.choice. Here replace torch.multinomial with torch.randperm. (cc @carolineechen).

Other improvements within training scripts will be included in a separate PR.

should we gate the new parameter initialization scheme with some initializer arg to avoid disrupting existing dependent training flows?

Since the scope of code change is within Wav2Vec2/HuBERT, and without the model initialization there will be performance regression compared to the result in fairseq. I think it is fine to make the model initialization as default. what do you think?

@hwangjeff This PR is more like a bug fix to address performance degradation over the fairseq baseline. Also fortunately this recipe hasn't been adopted by others yet as far as we know. But let's definitely merge this PR after @nateanl validates WER results with changes here

Those are good points and I wonder if the parameter initialization can be logically separated from the implementation  view point, like putting it inside of build function, instead of model constructor. To me, even though it is commonly done, parameter initialization feels different kind from building computation graph, because it is mutation of model instance. Besides, adding that logic to constructor means that when a pre-trained models are built using torchaudio.pipelines module, the parameter initialization is performed even though it will be replaced right after.

Also fortunately this recipe hasn't been adopted by others yet as far as we know.

Actually, I adopted this recipe before changes were introduced in this PR (and #2744). I had made some minor changes (e.g. learn k-means on 10% of the data; use gradient accumulation to simulate 32 GPUs), and my results differed slightly:

WER% (Viterbi)
WER% (KenLM)

test-clean (mine pre-#2744)
11.8
4.6

test-clean (yours pre-#2744)
10.8
4.4

test-clean (yours post-#2744)
10.9
4.4

test-clean (as published)
N/A
4.3

test-other (mine pre-#2744)
18.7
9.9

test-other (yours pre-#2744)
18.5
10.1

test-other (yours post-#2744)
17.8
9.5

test-other (as published)
N/A
9.4

I look forward to trying the latest version of the recipe and hopefully can replicate your results (or at least improve mine)!

Hi @arlofaria thanks for trying the HuBERT training recipes. Please let me know if you meet any issue when training the model with the improved recipe.

Hi @arlofaria
Thanks for trying out the HuBERT recipe. The torchaudio team is wondering if we can learn about your use cases of recipe and general torchaudio. If you are open to (light weight) chat, could you email me at<EMAIL_ADDRESS>We highly appreciate your feedback.
Thanks,


Fixed Lab example

So.. it fails because "expect.js". My commit just changes README..

Thanks @Algiras :+1:


Majid is working but there is no sound

I think this channel is muted for some reason, it's currently working but without any sound for a couple of months now.
Majid.ae,Majid,,,,AE,,,c/AE,ara,kids,FALSE,,,,https://majid.ae/,https://i.imgur.com/TzOKMMy.png

Please use this form instead: https://github.com/iptv-org/iptv/issues/new?assignees=&labels=🛠+broken+stream&projects=&template=-----broken-stream.yml&title=Broken%3A+


Command li-flows does not report downstream flows from BNGs running in HA mode.

Describe the bug
Bngblaster command li-flows was found to be not reporting the downstream mirrored flows from one or both BNGs running in HA mode, having IPoE subscribers
To Reproduce
Start a few (say 10) IPoE subscribers with some of them targeted for lawful intercept. 5 subscribers are established on both BNGs and the same are seen in standby state on the other BNG.
Make sure that acl/tunnel/mirror programming is good and also the mirrored flows go out of the BNG towards BNG blaster. Execute the li-flows command on bngblaster & check if all the flows are recorded.
Version (bngblaster -v):
supervisor@SN-STD-27-192083107:/var/bngblaster/ipoe_subscribers $ bngblaster -v
Version: 0.8.39
Compiler: GNU (11.4.0)
IO Modes: packet_mmap_raw (default), packet_mmap, raw
supervisor@SN-STD-27-192083107:/var/bngblaster/ipoe_subscribers $

JSON configuration:
{
{
  "interfaces": {
    "tx-interval": 1,
    "rx-interval": 1,
    "lag": [
      {
        "interface": "lag1",
        "lacp": true,
        "lacp-timeout-short": true
      },
      {
        "interface": "lag11",
        "lacp": true,
        "lacp-timeout-short": true
      }
    ],
    "links": [
      {
        "interface": "SN-5-C1",
        "lag-interface": "lag1"
      },
      {
        "interface": "SN-6-C1",
        "lag-interface": "lag1"
      },
      {
        "interface": "SN-7-C1",
        "lag-interface": "lag1"
      },
      {
        "interface": "SN-11-C2",
        "lag-interface": "lag1"
      },
      {
        "interface": "SN-12-C2",
        "lag-interface": "lag1"
      },
      {
        "interface": "SN-13-C2",
        "lag-interface": "lag1"
      },
      {
        "interface": "SN-20-C1",
        "lag-interface": "lag11"
      },
      {
        "interface": "SN-21-C1",
        "lag-interface": "lag11"
      },
      {
        "interface": "SN-22-C1",
        "lag-interface": "lag11"
      },
      {
        "interface": "SN-23-C2",
        "lag-interface": "lag11"
      },
      {
        "interface": "SN-24-C2",
        "lag-interface": "lag11"
      },
      {
        "interface": "SN-25-C2",
        "lag-interface": "lag11"
      }
    ],
    "network": [
      {
        "interface": "SN-19-RR",
        "address": "<IP_ADDRESS>/24",
        "gateway": "<IP_ADDRESS>",
        "address-ipv6": "fc66:1337:7331::2",
        "gateway-ipv6": "fc66:1337:7331::1",
        "isis-instance-id": 1,
        "isis-level": 1,
        "ldp-instance-id": 1
      }
    ],
    "access": [
      {
        "interface": "lag1",
        "type": "ipoe",
        "outer-vlan-min": 1001,
        "outer-vlan-max": 2000,
        "inner-vlan-min": 1001,
        "inner-vlan-max": 1100
      },
      {
        "interface": "lag11",
        "type": "ipoe",
        "outer-vlan-min": 2001,
        "outer-vlan-max": 3000,
        "inner-vlan-min": 1001,
        "inner-vlan-max": 1100
      }
    ]
  },
  "sessions": {
    "count": 20,
    "max-outstanding": 800,
    "start-rate": 400,
    "stop-rate": 100
  },
  "access-line": {
    "agent-remote-id": "DEU.RTBRICK.{session-global}",
    "agent-circuit-id": "<IP_ADDRESS>/<IP_ADDRESS> eth 0:{session-global}",
    "rate-up": 2000,
    "rate-down": 16384,
    "dsl-type": 5
  },
  "dhcp": {
    "enable": true
  },
  "dhcpv6": {
    "ldra": true,
    "enable": true
  },
  "session-traffic": {
    "ipv4-pps": 1,
    "ipv6-pps": 1,
    "ipv6pd-pps": 1,
    "autostart": true
  },
  "ldp": [
    {
      "instance-id": 1,
      "lsr-id": "<IP_ADDRESS>",
      "keepalive-time": 30,
      "raw-update-file": "/home/supervisor/ldp_1000.ldp"
    }
  ],
  "isis": [
    {
      "instance-id": 1,
      "area": [
        "49.0002/24"
      ],
      "system-id": "0204.0000.0001",
      "router-id": "<IP_ADDRESS>",
      "hostname": "BBL-RR",
      "hello-padding": true,
      "teardown-time": 30,
      "external": {
        "mrt-file": "/home/supervisor/isis_1000.mrt",
        "connections": [
          {
            "system-id": "0300.1001.0001",
            "l1-metric": 10
          }
        ]
      }
    }
  ],
  "bgp": [
    {
      "__comment__": "RR1-C1-IPv4",
      "network-interface": "SN-19-RR",
      "local-ipv4-address": "<IP_ADDRESS>",
      "peer-ipv4-address": "<IP_ADDRESS>",
      "raw-update-file": "/home/supervisor/ipv4_nlri_nh1.bgp",
      "local-as":<PHONE_NUMBER>,
      "peer-as":<PHONE_NUMBER>
    },
    {
      "__comment__": "RR1-C1-IPv6",
      "network-interface": "SN-19-RR",
      "local-ipv4-address": "<IP_ADDRESS>",
      "peer-ipv4-address": "<IP_ADDRESS>",
      "raw-update-file": "/home/supervisor/ipv6_nlri_nh1.bgp",
      "local-as":<PHONE_NUMBER>,
      "peer-as":<PHONE_NUMBER>
    },
    {
      "__comment__": "RR1-C2-IPv4",
      "network-interface": "SN-19-RR",
      "local-ipv4-address": "<IP_ADDRESS>",
      "peer-ipv4-address": "<IP_ADDRESS>",
      "raw-update-file": "/home/supervisor/ipv4_nlri_nh1.bgp",
      "local-as":<PHONE_NUMBER>,
      "peer-as":<PHONE_NUMBER>
    },
    {
      "__comment__": "RR1-C2-IPv6",
      "network-interface": "SN-19-RR",
      "local-ipv4-address": "<IP_ADDRESS>",
      "peer-ipv4-address": "<IP_ADDRESS>",
      "raw-update-file": "/home/supervisor/ipv6_nlri_nh1.bgp",
      "local-as":<PHONE_NUMBER>,
      "peer-as":<PHONE_NUMBER>
    },
    {
      "__comment__": "RR2-C1-IPv4",
      "network-interface": "SN-19-RR",
      "local-ipv4-address": "<IP_ADDRESS>",
      "peer-ipv4-address": "<IP_ADDRESS>",
      "raw-update-file": "/home/supervisor/ipv4_nlri_nh2.bgp",
      "local-as":<PHONE_NUMBER>,
      "peer-as":<PHONE_NUMBER>
    },
    {
      "__comment__": "RR2-C1-IPv6",
      "network-interface": "SN-19-RR",
      "local-ipv4-address": "<IP_ADDRESS>",
      "peer-ipv4-address": "<IP_ADDRESS>",
      "raw-update-file": "/home/supervisor/ipv6_nlri_nh2.bgp",
      "local-as":<PHONE_NUMBER>,
      "peer-as":<PHONE_NUMBER>
    },
    {
      "__comment__": "RR2-C2-IPv4",
      "network-interface": "SN-19-RR",
      "local-ipv4-address": "<IP_ADDRESS>",
      "peer-ipv4-address": "<IP_ADDRESS>",
      "raw-update-file": "/home/supervisor/ipv4_nlri_nh2.bgp",
      "local-as":<PHONE_NUMBER>,
      "peer-as":<PHONE_NUMBER>
    },
    {
      "__comment__": "RR2-C2-IPv6",
      "network-interface": "SN-19-RR",
      "local-ipv4-address": "<IP_ADDRESS>",
      "peer-ipv4-address": "<IP_ADDRESS>",
      "raw-update-file": "/home/supervisor/ipv6_nlri_nh2.bgp",
      "local-as":<PHONE_NUMBER>,
      "peer-as":<PHONE_NUMBER>
    }
  ]
}
}

Steps to reproduce the behavior:

Start a few (say 10) IPoE subscribers with some of them targeted for lawful intercept. 5 subscribers are established on both BNGs and the same are seen in standby state on the other BNG.

Make sure that acl/tunnel/mirror programming is good and also the mirrored flows go out of the BNG towards BNG blaster. Execute the li-flows command on bngblaster & check if all the flows are recorded.

Expected behavior
All flows including both upstream/downstream should be seen in the output of li-flows command.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Working Branch:
https://github.com/rtbrick/bngblaster/pull/241/files

Fixed with 0.8.41!


Quantize model is slower than raw model

I test espnet_onnx with a conformer model, I eval 100 wav 10 times and calculate the RTF only forward time, the result is

cpu
gpu

fp32
0.0180668
0.00263397

quantize
0.0172804
0.0124609

quantize model is very slower than fp32 model on GPU and just a litter bit faster on cpu
System information:
torch /cuda / GPU: 11.0 / 11.6 / A100
cpu: AMD EPYC 7402 24-Core Processor
onnx: 1.10.1
onnxruntime-gpu : 1.13.1
espnet_onnx: 0.1.9
Have you tested the speed of the quantize model on GPU

Hi @jinggaizi, GPU inference of quantized model is not supported on onnxruntime, that's why it is slow.

thanks ，I will learn tensorRT to support this mode


Change scope and scroll to selected date

I am trying out your component and after a couple of issues, I got most of it working.
What I am trying to achieve is the following:

Display the .Month scope
User selects a date
Change scope of calendar to '.Week'
Show selected date in the week scope

Step 1 to 3 works, animated, so that looks great, but I can't seem to be able to scroll the .Week scope to the right page.
I implemented my code like this:
func calendar(calendar: FSCalendar!, didSelectDate date: NSDate!) {
	if (calendar.scope == FSCalendarScope.Month) {
		calendar.setScope(FSCalendarScope.Week, animated: true)
		calendar.selectDate(date, scrollToDate: true)
	}
	else {
		self.navigationItem.rightBarButtonItem = nil;
	}
}

The problem with this method is that it crashes with the following error message:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'request for number of items before section 2386 when there are only 1560 sections in the collection view'
*** First throw call stack:
(
	0   CoreFoundation                      0x0000000104e7b9b5 __exceptionPreprocess + 165
	1   libobjc.A.dylib                     0x000000010456ddeb objc_exception_throw + 48
	2   CoreFoundation                      0x0000000104e7b81a +[NSException raise:format:arguments:] + 106
	3   Foundation                          0x00000001041bab72 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 198
	4   UIKit                               0x00000001032988d0 -[UICollectionViewData numberOfItemsBeforeSection:] + 229
	5   UIKit                               0x000000010329897f -[UICollectionViewData globalIndexForItemAtIndexPath:] + 52
	6   UIKit                               0x000000010324ea98 -[UICollectionView cellForItemAtIndexPath:] + 111
	7   FSCalendar                          0x00000001027cb1e0 -[FSCalendar collectionView:shouldSelectItemAtIndexPath:] + 96
	8   FSCalendar                          0x00000001027cf7f2 -[FSCalendar selectDate:scrollToDate:forPlaceholder:] + 786
	9   FSCalendar                          0x00000001027cf4c9 -[FSCalendar selectDate:scrollToDate:] + 105
	10  Symagic                             0x000000010231fa78 _TFC7Symagic19MonthViewController8calendarfS0_FTGSQCSo10FSCalendar_13didSelectDateGSQCSo6NSDate__T_ + 568
	11  Symagic                             0x000000010231fca7 _TToFC7Symagic19MonthViewController8calendarfS0_FTGSQCSo10FSCalendar_13didSelectDateGSQCSo6NSDate__T_ + 71
	12  FSCalendar                          0x00000001027d12f1 -[FSCalendar didSelectDate:] + 369
	13  FSCalendar                          0x00000001027cae2f -[FSCalendar collectionView:didSelectItemAtIndexPath:] + 399
	14  UIKit                               0x000000010323e81b -[UICollectionView _selectItemAtIndexPath:animated:scrollPosition:notifyDelegate:] + 684
	15  UIKit                               0x000000010325f6bd -[UICollectionView touchesEnded:withEvent:] + 574
	16  UIKit                               0x0000000102c57173 forwardTouchMethod + 349
	17  UIKit                               0x0000000102c5723c -[UIResponder touchesEnded:withEvent:] + 49
	18  UIKit                               0x0000000102c57173 forwardTouchMethod + 349
	19  UIKit                               0x0000000102c5723c -[UIResponder touchesEnded:withEvent:] + 49
	20  UIKit                               0x0000000102acb15f -[UIWindow _sendTouchesForEvent:] + 835
	21  UIKit                               0x0000000102acbd4d -[UIWindow sendEvent:] + 865
	22  UIKit                               0x0000000102a802ae -[UIApplication sendEvent:] + 263
	23  UIKit                               0x0000000102a5c36c _UIApplicationHandleEventQueue + 6693
	24  CoreFoundation                      0x0000000104da7b21 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
	25  CoreFoundation                      0x0000000104d9da4c __CFRunLoopDoSources0 + 556
	26  CoreFoundation                      0x0000000104d9cf03 __CFRunLoopRun + 867
	27  CoreFoundation                      0x0000000104d9c918 CFRunLoopRunSpecific + 488
	28  GraphicsServices                    0x0000000108461ad2 GSEventRunModal + 161
	29  UIKit                               0x0000000102a6199e UIApplicationMain + 171
	30  Symagic                             0x00000001022f970d main + 109
	31  libdyld.dylib                       0x0000000105b7e92d start + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException

Any tips?

Why did you select a date which had already been selected?

Well, after the user selects the date, I want the scope to change and then scroll to the selected date, so I hoped I could force the week mode to scroll there.

OK, I'll take a look at it tomorrow.

The problem mentioned above isn't solely happening when selecting a date, but switching the scope of the calendar causes this error a lot of times for me.

Hi @depl0y
Can you use this as a temporary solusion?
- (void)calendar:(FSCalendar *)calendar didSelectDate:(NSDate *)date
{
    if (calendar.scope == FSCalendarScopeMonth) {
        [calendar setScope:FSCalendarScopeWeek animated:YES];
        dispatch_after(dispatch_time(DISPATCH_TIME_NOW, (int64_t)(0.3 * NSEC_PER_SEC)), dispatch_get_main_queue(), ^{
            calendar.currentPage = date;
        });
    }
}

You should translate it to swift.
I know it's not a appropriate way, but I'll find one eventually.

The issue also puzzle me a lot..

Fixed


Timestamp parsing is one month off

---
xmas: 2011-12-24
...

results in
{
     xmas: Mon, 23 Jan 2012 23:00:00 GMT
}

Confirmed this on the website

True. Thanks for your report.

Cool, thanks for fixing this so quickly :)
Would have done it myself but could not quite wrap my head around how the tests work


[Bug]: "Collection is not created" message despite being returned by list_collections method

What happened?
I am trying to get an existing ChromaDB collection with the get_or_create_collection method of a PersistentClient object but I get 'Collection "collection_name" is not created.'.
Here's a snippet of the source code:
client = chromadb.PersistentClient(path="/path/to/collection/directory")
print(f"Available collections: {client.list_collections()}")    # <- this returns the collection that I want to get
embedding_function = (embedding_functions.SentenceTransformerEmbeddingFunction("all-mpnet-base-v2","cuda"))
client.get_or_create_collection("test_collection", embedding_function)

I tracked down the source of the message and it is */chromadb/api/segment.py, line 189.
I also tried to reproduce the message by creating a copy of the project and changing the version of the chromadb Python package inside a pipenv environment. I could not get the message despite everything being the same (package version, collection directory path, collection name and embedding function) when I used version 0.4.24. I've asserted the values of all parameters and they are always correct. The message appears when I upgrade to the latest version 0.5.0.
It is possible to perform all actions with the collection such as creating one, inserting and deleting data and querying chunks from the collection despite the above message.
Expected behaviour: the message should not appear if the collection exists or it's getting created and there are no errors.
Versions
Chroma 0.5.0
Python 3.10.12
Ubuntu 22.04 (WSL 2)
Relevant log output
No response

Hey @hoosengold, thanks for pointing this out. This is just an info-level log message used for tracking the behavior of the get_or_create_collection() function semantics. It just lets you know that the call did not create a new collection but returned an existing one. I can see how this exact phrasing can be misleading and interpreted as an error.
Let us improve on the messaging.

Hi @tazarov, thank you for the fast reply!

It just lets you know that the call did not create a new collection but returned an existing one.

It seems like the message is always displayed, not just when getting the collection but also when creating it. That means that the created bool variable is always set to False by the _sysdb.create_collection() method for some reason. I hope that this does not indicate a more complex problem.
However, thanks again for the quick response and fixing the info message!

Thanks for this insight, @hoosengold. I will have a look in sysdb and fix that if necessary.

@hoosengold,
I just tested with:
import chromadb

client = chromadb.HttpClient()

client.get_or_create_collection("Test")

Results:
INFO:     [15-05-2024 13:57:01] Application startup complete.
INFO:     [15-05-2024 13:57:01] Uvicorn running on http://localhost:8000 (Press CTRL+C to quit)
INFO:     [15-05-2024 13:57:09] ::1:50449 - "GET /api/v1/tenants/default_tenant HTTP/1.1" 200
INFO:     [15-05-2024 13:57:09] ::1:50449 - "GET /api/v1/databases/default_database?tenant=default_tenant HTTP/1.1" 200
INFO:     [15-05-2024 13:57:09] ::1:50450 - "POST /api/v1/collections?tenant=default_tenant&database=default_database HTTP/1.1" 200
INFO:     [15-05-2024 13:57:17] ::1:50453 - "GET /api/v1/tenants/default_tenant HTTP/1.1" 200
INFO:     [15-05-2024 13:57:17] ::1:50453 - "GET /api/v1/databases/default_database?tenant=default_tenant HTTP/1.1" 200
DEBUG:    [15-05-2024 13:57:17] Collection Test already exists, returning existing collection.
INFO:     [15-05-2024 13:57:17] ::1:50454 - "POST /api/v1/collections?tenant=default_tenant&database=default_database HTTP/1.1" 200

As expected, the message was returned only when trying to get_or_create_collection() on an existing collection. The initial creation (INFO:     [15-05-2024 13:57:09] ::1:50450 - "POST /api/v1/collections?tenant=default_tenant&database=default_database HTTP/1.1" 200) of the collection did not trigger the message.

@tazarov
Thank you for the provided logs. I reproduced your test with a PersistentClient (with a basic FastAPI implementation) and it works as expected and described by you. Here's a snippet of the code:
import chromadb
client = chromadb.PersistentClient(path=os.path.join(os.getcwd(), "chroma"))
client.get_or_create_collection("Test")

Logs:
INFO:     Application startup complete.
INFO: Anonymized telemetry enabled. See https://docs.trychroma.com/telemetry for more information.
INFO:     <IP_ADDRESS>:53838 - "POST /api/v1/test HTTP/1.1" 200 OK
INFO: Collection Test is not created.
INFO:     <IP_ADDRESS>:33750 - "POST /api/v1/test HTTP/1.1" 200 OK

When I test it with the code from the initial issue, I get the info message no matter if the collection exists or not. I guess the problem is someplace else. I will update this comment (or write a new one) if I find where the problem is.
Thank you for the fast replies and for your time!

Closing this for bug hygiene. Feel free to create another issue if you find another issue.


Support for named modules

Define can have 3 arguments
example:
define('api', ['jquery', 'debug'], function ($, debug) {
https://requirejs.org/docs/api.html#modulename
however currently this errors with "too many arguments"

An interesting request. Sources usually consist of unnamed modules, because module names are necessary first when multiple modules are built into a module bundle. But I admit that it's possible to name the source modules already, if it has some benefit.
When named modules get converted to ESM, importing them by the abstract names should continue working. Support for module naming may differ among module bundlers, but as soon as import maps have been introduced for ESM, they should be supported as a standard.
Let me fix this and produce an import map with the explicitly named modules.

Released in [1.2.0(https://github.com/prantlf/requirejs-esm-converter/releases/tag/v1.2.0).
If named modules are detected, the import map will be printed on the console or to a specified file. File paths will be as specified on the command line, usually relatively to the project root. They may need to be adjusted according to the project deployment.
The API for the module conversion - the convert function - returns the module name as an optional name property.


Switch from curl to wget

There are several (10) packages that "curl" pulls in which are then never removed -- "wget" does not have this problem.

LGTM


Align ballerina runtime error messages

Purpose
$Subject.
Fixes #
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Temporary closing this PR as we need to finalize the error messages


[FancyZones] Canvas layouts scaling

Summary of the Pull Request
What is this about:
Enable canvas layouts scaling.
This allow us to remove resolution from device-id which causes many issues with layout resetting.
What is included in the PR:
How does someone test / validate:

Create and apply canvas layout.
Apply the same canvas layout on the monitor with different resolution, verify it looks the same.

Quality Checklist

[x] Linked issue: #14261
[ ] Communication: I've discussed this with core contributors in the issue.
[x] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[ ] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

Here is how it works with portrait orientation. The same canvas layout applied.

@stefansjfw PTAL, I pushed the fix.

@stefansjfw PTAL, I pushed the fix.

Looks good, give me few minutes to try it once again


Rely on promote instead of convert

This will alleviate the problem of not being able to do fft(1:5). Currently, the Int type is problematic, but I'd prefer if that didn't happen.

This should hopefully be fixed once #22 is closed.


docs(useSortBy): fix typo

Fix typo.
From directionfor to direction for.

@tannerlinsley really small PR here :)


Include tests in sdist

Include the test suite in sdist archives, in order to make it possible for distribution packagers to use them rather than generated GitHub archives.

Why do you want the tests included?

Can you provide some context on it?

I don't understand what you're asking for. Gentoo Linux provides packages for various Python, well, packages. As part of package building process, users can opt in to run test suites against their system and Python versions. This way they can reduce the risk of hitting breakage at runtime, particularly if they're running a less common setup.

Have you tried running the tests for this package? Can you provide me how to run tests in gentoo for this?
The tests here run commands against FakeRedis (ie, the package) and real redis and compare the results. How does gentoo runs redis server before running the tests?

Yes, we are running tests for quite a while. I admit there are a few known failures but most of them pass. We are starting a local redis server for the duration of the test suite. The code is here:
https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-python/fakeredis/fakeredis-2.10.2.ebuild#n66
To run ebuild with tests enabled, normally you run:
FEATURES=test emerge -1v dev-python/fakeredis

However, this will also enable tests on all dependencies which can be time consuming. You can enable it per package by defining e.g. /etc/portage/env/run-tests:
FEATURES="${FEATURES} test"

and then using in /etc/portage/package.env:
dev-python/fakeredis run-tests

Got you, ok, I see the need. I am not sure how to write a test for it here so I'll merge.

Thank you!


OpenSSL 3 bump for Chef 17

Description

install openssl 3.2.0 to backfill for custom openssl
Set OpenSSL version to 1.0.2zi for Windows due to FIPS challenges and 3.0.9 for others.
::File.exists? -> ::File.exist? for ssl_policies.rb
Fix EC and modulus length for OpenSSL 3 compatibility
OpenSSL validation checks

Related Issue

Types of changes

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

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

@tpowell-progress redo Gemfile.lock for root and omnibus

@tpowell-progress is there a timeline on Chef 17 supporting Openssl 3.0.7 on Rocky Linux 9?

@mikef-nl Chef-17 is tested on Rocky 8 and 9 currently. Not sure about the timeline for Openssl 3.0.7, we're working on it though. Do you need it soon?

@tpowell-progress is there a timeline on Chef 17 supporting Openssl 3.0.7 on Rocky Linux 9?

@mikef-nl working to get everything green... a few things have triggered failures in the builds, but we're compiling release notes for when we get everything passing. I think on "weeks" time scale still. Currently assessing what is still broken and how much of it we have known fixes for.

Merging since the remainder of issues are going to be addressed separately.


Add pagination to reply check

Nowhere near hitting the 200 tweet limit, but would be nice to future proof.

Triaged.


Add support for Python 3.12

Closes https://github.com/apify/apify-core/issues/12587

In the case of Playwright, blocked until v1.39.0 is not released on PyPI.

Blocked by https://github.com/apify/apify-actor-docker/issues/113